HDMI display problem

I have a custom jetson tx2 nx board. I modified the sor0 from DP to HDMI. Due to design problems, the hdmi of sor1 of our custom carrier board cannot be used. So we want to use the HDMI of the sor0 as output. After modifying the dtb file and flashing, the hdmi interface corresponding to sor0 can display the ubuntu wallpaper but cannot display the login interface when connected to the monitor. I put the core board with the modified Image on the carrier board of the standard jetson nano kit, and the sor1 HDMI of the carrier board of the kit can show the login interface . After logining, xrandr show

Screen 0: minimum 8 x 8, current 2560 x 1080, maximum 32767 x 32767
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 530mm x 300mm
   1920x1080     60.00*+  74.98    59.95    50.00  
   1680x1050     59.96  
   1600x900      60.00  
   1440x900      59.89  
   1280x1024     75.03    60.00  
   1280x800      59.81  
   1280x720      60.00    59.94    50.00  
   1024x768      75.03    60.01  
   800x600       75.00    60.32  
   720x576       50.00  
   720x480       59.94  
   720x400       70.04  
   640x480       75.00    59.94  
HDMI-1 connected 640x480+1920+0 (normal left inverted right x axis y axis) 0mm x 0mm
   640x480       60.00*+

I try to execute command xrandr --output HDMI-1 --same-as HDMI-0 to make HDMI-1(sor0) has the same output as HDMI-0(sor1) , and then put the core board on our custom carrier board again, but hdmi output of the sor0 doesn’t change.
I’m guessing something is wrong with the monitor system configuration, but I can’t find a reference on the forums. Can you give me some suggestions?

I put the core board with the modified Image on the carrier board of the standard jetson nano kit, and the sor1 HDMI of the carrier board of the kit can show the login interface . After logining, xrandr show

You don’t need to do that. What you need to do is dump ther log from your serial console log on your custom board.

Here is the log file from my custom board.
serial_port.log (33.6 KB)

please remove “quiet” from /boot/extlinux/extlinux.conf and dump log again.

Currently, the kernel log is in silent mode so didn’t get printed.

Here is a new log file.
serial_portv2.log (107.6 KB)

What is the xrandr result from this situation?

xrandr command return Can't open display

export DISPLAY=:0 before running xrandr. And please do not run as sudo.

Here is the return content.

[14:57:49:038] No protocol specified␍␊

[14:57:49:038] Can't open display :0␍

please directly share me the result of /var/log/Xorg.0.log

Also, I don’t quite understand. If your SOR1 is not able to use, then why do you still have SOR1 enabled in your device tree?

Here is Xorg.log file.
Xorg.log (27.7 KB)

Subsequent products will modify the circuit design, and temporarily use sor0 for testing. I will disable sor1 and recompile the device tree file and try again.

yes, please dump above logs with sor1 disabled.

It will not fix the issue, but it will be easier to me to check logs…

When I disable sor1, the sor0 can work normally. Thank you very much.

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