No DP display on xavier-nx

Autonomous Machines Jetson & Embedded Systems Jetson Xavier NX
#1

Hi,

We are using Xavier-NX-emmc with Xavier-EVK for test.
There is not DP display with default Jetpack(32.7.1).

Here is some information:

  1. device-tree
root@a-desktop:/home/a# cat /proc/device-tree/nvidia,dtsfilename
/dvs/git/dirty/git-master_linux/kernel/kernel-4.9/arch/arm64/boot/dts/../../../../../../hardware/nvidia/platform/t19x/jakku/kernel-dts/tegra194-p3668-all-p3509-0000.dts

root@a-desktop:/# cat ./sys/bus/platform/devices/15210000.nvdisplay/of_node/status                                                                                                                                                                                                                
ok
  1. proc/interrupts
# plug in/ out hdmi
  73:      24801          0          0          0     GICv2  185 Level     15200000.nvdisplay
...
  73:      24943          0          0          0     GICv2  185 Level     15200000.nvdisplay

# plug in/ out dp
  74:          0          0          0          0     GICv2  186 Level     15210000.nvdisplay
...
  74:          0          0          0          0     GICv2  186 Level     15210000.nvdisplay

Please help to fix the issue.

By the way, Nano with evk works, and we don’t have Xavier-NX-SD on hand for reference.

#3

Hi,

Could you connect only the DP monitor, boot up and show me the dmesg?

#4

log.txt (65.1 KB)

#5

Hi,

Is this Xaiver NX devkit or your own custom board?

#6

No, its Xavier-NX-emmc on EVK.

#7

May I ask what does “EVK” mean here? Your own custom board or NV devkit p3509? Whether the module is emmc or sdcard does not matter. Just want to clarify the carrier board info here…

請問一下你的"EVK"意思是…? 自己做的底板還是 NV出的p3509? 你上面用的module是emmc或是sdcard其實不是太重要. 我只是需要確認底板的資訊

#8

It’s 180-13509-DAAF-A01.

#9

請問你有其他的3509底板, DP cable還有螢幕可以做測試嗎？ 從你的log上來看, 連螢幕熱插拔都沒偵測到

Do you have other p3509 carrier board, DP cable and display that can test? Based on your log, even display hotplug is not detected.

#10

No, only one.
Our custom board has the same problem.

#11

那你的DP cable跟螢幕在其他平台是可以用的嗎 比方說x86 PC 上面
目前看來這是單一個案, 不是軟體的問題 所以如果你沒有辦法做交叉驗證, 我只能請你RMA你的module或底板

Is your DP cable able to work fine on other platform? For example, x86 PC?
It looks like a single case so not a software problem. If you cannot do cross validation, I can only ask you to RMA your module or carrier board.

#12

Yes, DP cable and monitor works on nano-evk.

I have tried 3 pieces of Xavier-NX-emmc modules, and got the same result.
Our custom baseboard has two DP out put. (One of them is changing from hdmi.)
And that baseboard works on sor1 not for sor0.

We can’t tell if the issue cames from modules of baseboard.

#13

Hi,

如果你確認 devkit + pure jetpack software這個狀況下 SOR0上的DP還是不會動, 那可能是底板有點狀況
或是你可以試試看其他版本的jetpack

If you are sure SOR0 DP would still not work on devkit + pure jetpack software situation, then it would be base board issue.
Or you could try other version of jetpack.

#14

Hi

We found the other devkit in different place.
We will update the test later.

#15

Hi,

Got the result, the p3509 baseboard DP port is broken.
Our baseboard is using the Head0->SOR1->DP, and not working.

We followed this article and still not working

image

The pin 18 is high when plug the DP monitor, but got no interrupt.

 73:          0          0          0          0     GICv2 185 Level     15200000.nvdisplay
 74:          0          0          0          0     GICv2 186 Level     15210000.nvdisplay
 75:          0          0          0          0     GICv2 191 Level     tegra_dp
 76:          0          0          0          0     GICv2 192 Level     tegra_dp

Origin DP is working

 73:          0          0          0          0     GICv2 185 Level     15200000.nvdisplay
 74:      18044          0          0          0     GICv2 186 Level     15210000.nvdisplay
 75:          2          0          0          0     GICv2 191 Level     tegra_dp
 76:          0          0          0          0     GICv2 192 Level     tegra_dp
#16

Make sure your pinmux setting is correct.

#17 
root@a-desktop:/home/a# cat /sys/kernel/debug/tegra_pinctrl_reg |grep dp
Bank: 0 Reg: 0x02440030 Val: 0x00000450 -> dp_aux_ch0_hpd_pm0
Bank: 0 Reg: 0x02440038 Val: 0x00000150 -> dp_aux_ch1_hpd_pm1
Bank: 0 Reg: 0x02440040 Val: 0x00000416 -> dp_aux_ch2_hpd_pm2
Bank: 0 Reg: 0x02440048 Val: 0x00000416 -> dp_aux_ch3_hpd_pm3
#18

Please compare your pinmux result with the one on devkit. The hpd pin shall have same value.

#19

It’s different from the pinmux file in bootloader.

pinmux.0x02440030 = 0x00000450; # dp_aux_ch0_hpd_pm0: dp, tristate-enable, input-enable, io_high_voltage-disable, lpdr-disable
pinmux.0x02440038 = 0x00000450; # dp_aux_ch1_hpd_pm1: dp, tristate-enable, input-enable, io_high_voltage-disable, lpdr-disable

I thinks that’s the problem.

#20

Yes, then please update your pinmux in the bct cfg file…

#22

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