Our team is working on our board with Orin Nano SOM. And we are trying to output the DP1 signal to a LVDS IC which is RTD2136R.
We can see there is a logo from the begining. And after booting done, the screen becomes black. In the meantime, we can see the backlight is still working.
I pluged-in-out the HPD on our board and checked my Xorg.0.log. The message showed me only the DFP-0 is changed. The DFP-1 status always disconnected. Our /var/log/Xorg.0.log
And there is a strange thing is I checked the card1-DP-1 status. It showed me connected. That doesn’t make sense.
root@tegra-ubuntu:/sys/class/drm/card1-DP-1# cat status
connected
Also I do another test.I put the same ssd on Nano devkit. Then pluged-in-out the DP-to-HDMI cable again. The Xorg.0.log showed me only the DFP-1 is changed. Nano devkit /var/log/Xorg.0.log
Also the card1-DP-1 status is still connected.
root@tegra-ubuntu:/sys/class/drm/card1-DP-1# cat status
connected
Do we have misunderstood on DP1 design?
My Jetpack version
R36 (release), REVISION: 4.0, GCID: 37537400, BOARD: generic, EABI: aarch64, DATE: Fri Sep 13 04:36:44 UTC 2024
Does it mean that we do not need to be concerned about which DFP is connected? Once the /sys/class/drm/card1-DP-1/status changes and AUX_P/AUX_N receive the proper EDID, the DP1 signal should function correctly?"
Just a suggestion first. If you want to share a log, could you just attach full log as attachment instead of such screenshot?
And back to the question itself, is the EDID shown in the xorg log the one that RTD2136R provided to you? or it is not? It is hard to read what is the EDID from RTD2136R based on your screenshot.
Could you just tell what is the exact EDID that your RTD2136R provided? I am not sure if I can interpret your i2c data flow correctly by reading such trace?
Thank you, Wayne.
After reviewing the EDID files, we determined that the RTD2136R’s 128-byte EDID is insufficient for the Orin Nano’s DP, which requires 256 bytes to function correctly.