Display Errors and Boot Time Delays on TX2 NX

DamonXcd · April 28, 2024, 3:55am

Issue Description

When using the official L4T 32.7.1 (non-customized) to flash the TX2 NX core board, there are log differences observed on our carrier board. The logs from the abnormal core board display a series of errors related to nvdisplay. However, the logs from the normal core board are relatively clean and do not show similar errors.
The occurrence of the first issue is due to the flashing of our modified L4T 32.7.1 onto the abnormal core board during the production process. Subsequently, we noticed an unusually long system boot time and encountered numerous “edid invalid” errors in the system logs. To address this issue, we initiated troubleshooting steps.
Multiple abnormal core boards have still been observed recently.
We are still experiencing the issue with L4T 32.7.4.

Differences Logs in Official L4T 32.7.1

Example of logs from the abnormal core board:

$ journalctl|grep nvdisplay
Apr 26 04:13:25 abcd kernel: [    0.415768] iommu: Adding device 15200000.nvdisplay to group 29
Apr 26 04:13:25 abcd kernel: [    0.416078] iommu: Adding device 15210000.nvdisplay to group 30
Apr 26 04:13:25 abcd kernel: [    0.923450] tegradc 15200000.nvdisplay: disp0 connected to head0->/host1x/sor1
Apr 26 04:13:25 abcd kernel: [    0.923556] tegradc 15200000.nvdisplay: DT parsed successfully
Apr 26 04:13:25 abcd kernel: [    0.923578] tegradc 15200000.nvdisplay: Display dc.ffffff800b3e0000 registered with id=0
Apr 26 04:13:25 abcd kernel: [    0.929427] tegradc 15200000.nvdisplay: vblank syncpt # 8 for dc 0
Apr 26 04:13:25 abcd kernel: [    0.929432] tegradc 15200000.nvdisplay: vpulse3 syncpt # 9 for dc 0
Apr 26 04:13:25 abcd kernel: [    0.931989] tegradc 15200000.nvdisplay: hdmi: invalid prod list prod_list_hdmi_board
Apr 26 04:13:25 abcd kernel: [    0.931993] tegradc 15200000.nvdisplay: hdmi: tegra_hdmi_tmds_range_read(bd) failed
Apr 26 04:13:25 abcd kernel: [    0.935407] tegradc 15200000.nvdisplay: probed
Apr 26 04:13:25 abcd kernel: [    0.935747] tegradc 15200000.nvdisplay: fb registered
Apr 26 04:13:25 abcd kernel: [    0.936530] tegradc 15210000.nvdisplay: disp1 connected to head1->/host1x/sor
Apr 26 04:13:25 abcd kernel: [    0.936663] tegradc 15210000.nvdisplay: DT parsed successfully
Apr 26 04:13:25 abcd kernel: [    0.936694] tegradc 15210000.nvdisplay: Display dc.ffffff800b4a0000 registered with id=1
Apr 26 04:13:25 abcd kernel: [    0.936893] tegradc 15210000.nvdisplay: vblank syncpt # 11 for dc 1
Apr 26 04:13:25 abcd kernel: [    0.936898] tegradc 15210000.nvdisplay: vpulse3 syncpt # 12 for dc 1
Apr 26 04:13:25 abcd kernel: [    0.948120] tegradc 15210000.nvdisplay: probed
Apr 26 04:13:25 abcd kernel: [    0.948289] tegradc 15210000.nvdisplay: fb registered
Apr 26 04:13:25 abcd kernel: [    0.952887] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    0.954071] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    0.955533] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    0.957127] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    0.964207] tegradc 15210000.nvdisplay: dp: Failed for I2C write addr:80, size:1, stat:0x10000100
Apr 26 04:13:25 abcd kernel: [    0.979019] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    0.980474] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    0.981967] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    0.983422] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    0.990496] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.000201] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    1.001548] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    1.003004] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    1.004457] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    1.011525] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.021230] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    1.022686] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    1.024141] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    1.025596] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    1.032662] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.042378] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    1.043846] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    1.045313] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    1.046783] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    1.053838] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.062882] tegradc 15210000.nvdisplay: dp: failed to exit panel power save mode (0xfffffff2)
Apr 26 04:13:25 abcd kernel: [    1.182102] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    1.183565] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    1.185027] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    1.186491] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    1.193546] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.203251] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    1.204715] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    1.206180] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    1.207643] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    1.214694] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.224401] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    1.225866] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    1.227329] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    1.228819] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    1.235883] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.245605] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 2
Apr 26 04:13:25 abcd kernel: [    1.247063] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 1
Apr 26 04:13:25 abcd kernel: [    1.248518] tegradc 15210000.nvdisplay: dp: aux write retry (0x10000100) -- 0
Apr 26 04:13:25 abcd kernel: [    1.249984] tegradc 15210000.nvdisplay: dp: aux write got error (0x10000100)
Apr 26 04:13:25 abcd kernel: [    1.257047] tegradc 15210000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
Apr 26 04:13:25 abcd kernel: [    1.266098] tegradc 15210000.nvdisplay: dp: failed to exit panel power save mode (0xfffffff2)
Apr 26 04:13:25 abcd kernel: [    2.282897] tegradc 15210000.nvdisplay: blank - powerdown
Apr 26 04:13:28 abcd kernel: [    5.339820] tegradc 15200000.nvdisplay: blank - powerdown
Apr 26 04:13:28 abcd kernel: [    5.339828] tegradc 15210000.nvdisplay: blank - powerdown

Example of logs from the normal core board:

$ journalctl|grep nvdisplay
Apr 26 03:43:49 abcd kernel: [    0.416483] iommu: Adding device 15200000.nvdisplay to group 29
Apr 26 03:43:49 abcd kernel: [    0.416798] iommu: Adding device 15210000.nvdisplay to group 30
Apr 26 03:43:49 abcd kernel: [    0.861516] tegradc 15200000.nvdisplay: disp0 connected to head0->/host1x/sor1
Apr 26 03:43:49 abcd kernel: [    0.861619] tegradc 15200000.nvdisplay: DT parsed successfully
Apr 26 03:43:49 abcd kernel: [    0.861638] tegradc 15200000.nvdisplay: Display dc.ffffff800b3e0000 registered with id=0
Apr 26 03:43:49 abcd kernel: [    0.867523] tegradc 15200000.nvdisplay: vblank syncpt # 8 for dc 0
Apr 26 03:43:49 abcd kernel: [    0.867528] tegradc 15200000.nvdisplay: vpulse3 syncpt # 9 for dc 0
Apr 26 03:43:49 abcd kernel: [    0.868481] tegradc 15200000.nvdisplay: Bootloader disp_param detected. Detected mode: 1920x1080 (on 0x0mm) pclk=148350937
Apr 26 03:43:49 abcd kernel: [    0.870446] tegradc 15200000.nvdisplay: hdmi: invalid prod list prod_list_hdmi_board
Apr 26 03:43:49 abcd kernel: [    0.870451] tegradc 15200000.nvdisplay: hdmi: tegra_hdmi_tmds_range_read(bd) failed
Apr 26 03:43:49 abcd kernel: [    0.872569] tegradc 15200000.nvdisplay: probed
Apr 26 03:43:49 abcd kernel: [    0.884195] tegradc 15200000.nvdisplay: fb registered
Apr 26 03:43:49 abcd kernel: [    0.951971] tegradc 15200000.nvdisplay: hdmi: tmds rate:148351K prod-setting:prod_c_hdmi_111m_223m
Apr 26 03:43:49 abcd kernel: [    0.952395] tegradc 15200000.nvdisplay: hdmi: get RGB quant from REG programmed by BL.
Apr 26 03:43:49 abcd kernel: [    0.952405] tegradc 15200000.nvdisplay: hdmi: BL set VIC 0
Apr 26 03:43:49 abcd kernel: [    0.952408] tegradc 15200000.nvdisplay: hdmi: get YCC quant from REG programmed by BL.
Apr 26 03:43:49 abcd kernel: [   11.141796] tegradc 15210000.nvdisplay: disp1 connected to head1->/host1x/sor
Apr 26 03:43:49 abcd kernel: [   11.141879] tegradc 15210000.nvdisplay: DT parsed successfully
Apr 26 03:43:49 abcd kernel: [   11.141898] tegradc 15210000.nvdisplay: Display dc.ffffff800ba90000 registered with id=1
Apr 26 03:43:49 abcd kernel: [   11.142040] tegradc 15210000.nvdisplay: vblank syncpt # 11 for dc 1
Apr 26 03:43:49 abcd kernel: [   11.142044] tegradc 15210000.nvdisplay: vpulse3 syncpt # 12 for dc 1
Apr 26 03:43:49 abcd kernel: [   11.148944] tegradc 15210000.nvdisplay: probed
Apr 26 03:43:49 abcd kernel: [   11.149076] tegradc 15210000.nvdisplay: fb registered
Apr 26 03:43:49 abcd kernel: [   11.152258] tegradc 15210000.nvdisplay: blank - powerdown
Apr 26 03:43:52 abcd kernel: [   14.999985] tegradc 15200000.nvdisplay: unblank
Apr 26 03:43:52 abcd kernel: [   14.999999] tegradc 15210000.nvdisplay: blank - powerdown

ps:
I’m unable to upload the log files in TXT and ZIP format here. If you need them, please provide me with your email address, and I’ll send them to.

WayneWWW · April 28, 2024, 9:11am

What does your “core board” mean here when you already used the other term “module”?

DamonXcd · April 28, 2024, 9:49am

I described it poorly and have now change “module” to “core board”.

WayneWWW · April 28, 2024, 9:50am

Do you have Xavier NX devkit carrier board that can check if it is broken module since you keep mentioning there are working and non-working modules.

DamonXcd · April 29, 2024, 7:53am

了解到这里可以使用中文交流。
我们使用了Xavier NX devkit 载板做验证，异常核心板没有上述问题。

WayneWWW · April 29, 2024, 7:57am

Hi,

請問你的custom board也是DP+HDMI 2個port的設計嗎

DamonXcd · April 29, 2024, 8:56am

没有使用HDMI和DP口，载板上DP和HDMI都是悬空的。

WayneWWW · April 29, 2024, 9:09am

請問你確定你講的是對的嗎… 你的log跟你說的看起來不太符合…

Apr 26 03:43:49 abcd kernel: [ 0.951971] tegradc 15200000.nvdisplay: hdmi: tmds rate:148351K prod-setting:prod_c_hdmi_111m_223m
Apr 26 03:43:52 abcd kernel: [ 14.999985] tegradc 15200000.nvdisplay: unblank

以上log代表你至少HDMI port有做出來…

DamonXcd · April 29, 2024, 9:48am

仔细确认了原理图，可以确认下面引脚号均为浮空：

引脚号	名称	引脚号	名称
41	DP0_TXD0	65	DP1_TXD0 (HDMI_TXD2)
39	DP0_TXD0	63	DP1_TXD0 (HDMI_TXD2)
47	DP0_TXD1	71	DP1_TXD1 (HDMI_TXD1)
45	DP0_TXD1	69	DP1_TXD1 (HDMI_TXD1)
53	DP0_TXD2	77	DP1_TXD2 (HDMI_TXD0)
51	DP0_TXD2	75	DP1_TXD2 (HDMI_TXD0)
59	DP0_TXD3	83	DP1_TXD3 (HDMI_TXC)
57	DP0_TXD3	81	DP1_TXD3 (HDMI_TXC)
92	DP0_AUX	100	DP1_AUX_P (HDMI_DDC_SCL)
90	DP0_AUX	98	DP1_AUX_N (HDMI_DDC_SDA)
88	DP0_HPD	96	DP1_HPD (HDMI_HPD)
		94	HDMI_CEC

WayneWWW · April 29, 2024, 9:49am

ok… 那就請你把沒在使用的nvdisplay跟SOR關掉… 這條就純粹這樣而已

DamonXcd · April 29, 2024, 9:57am

我们想知道，为什么这个TX2 NX核心板和之前的核心板有不一样，因为同样的产品我们已经生产了2年+，在硬件软件都未变更的情况下，最近的买到的核心板频繁出现这样的问题。

WayneWWW · April 29, 2024, 10:00am

你之前的軟體這樣配置就是會有問題不是說以前沒問題你的軟體就是對的…

沒有在使用的東西就請你關掉

system · May 13, 2024, 10:00am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Jetson TX2 custom board HDMI problem Jetson TX2 board-design , hdmi	36	2557	October 18, 2021
DisplayPort on TX2-NX Jetson TX2 dp-display	3	664	December 28, 2022
TX2i tegra_nvdisp_head_enable fails if HDMI is connected after boot Jetson TX2 kernel	7	1528	October 18, 2021
Dual DP output on custom board Jetson TX2 board-design , dp-display	8	1244	December 15, 2021
DP errors writing to i2c address Jetson Xavier NX dp-display	17	2616	November 17, 2021
TX2 development kit : 4K doesn't work (boot fails) Jetson TX2	40	4691	October 18, 2021
Display port not working on custom board Jetson AGX Xavier board-design , dp-display	9	539	November 6, 2023
Jetson TX2i HDMI is not working on custom board Jetson TX2	19	1380	December 19, 2019
Jetson Xavier NX GPU lib Report Error Jetson Xavier NX board-design , gpu	41	1486	July 13, 2022
No DSI MIPI data on custom carrier board Jetson TX2 dsi-display	46	2269	February 28, 2022

Display Errors and Boot Time Delays on TX2 NX

Issue Description

Differences Logs in Official L4T 32.7.1

Related topics