Hi Nvidia Team,
We are building custom board with L4T 36.4.3.
When performing compatibility testing, I encountered the following issue:
After connecting the Custom Board’s HDMI to the ASUS XG32UQ and then disconnecting it and reconnecting to the ASUS VG279Q1A, there is no display output.
(It seems like it keeps retrying to output the display,
causing the monitor to repeatedly cycle through: signal light turns on → screen shows “no signal” → signal light turns off…)
From the console, the following error message can be seen.
However, if I connect directly to either the ASUS XG32UQ or the ASUS VG279Q1A, the display works normally.
xrandr (ASUS VG279Q1A)
xrandr (ASUS XG32UQ)
*** Please note that this reply is generated by LLM automatically ***
Based on the provided context, I’ll attempt to provide a comprehensive answer to the issue you’re experiencing with your custom board using L4T 3643.
Issue Summary
You’re experiencing a display output issue when connecting your custom board’s HDMI to different monitors (ASUS XG32UQ and ASUS VG279Q1A) in a specific sequence. The issue doesn’t occur when connecting directly to either monitor.
Possible Causes
- HDMI Signal Quality: The issue might be related to the HDMI signal quality. When you disconnect and reconnect the HDMI cable, the signal might not be stable, causing the monitor to cycle through the signal light.
- EDID (Extended Display Identification Data) Issue: The EDID is a data structure that contains information about the monitor’s capabilities. When you switch between monitors, the EDID might not be updated correctly, leading to display output issues.
- HDMI Hotplug Detection: The Jetson Orin NX module might not be detecting the HDMI hotplug event correctly, causing the display output to malfunction.
Comparison with Similar Issues
In the provided context, there are no direct matches for this specific issue. However, there are some related issues that might be relevant:
- USB Cable Issue: Although not directly related to HDMI, this issue highlights the importance of signal quality and stability.
- Known Issues: This list might contain relevant information about known issues with L4T 3643, but it’s not explicitly mentioned in the provided context.
Tools and Services
To debug this issue, you might want to use the following tools and services:
- Oscilloscope: To measure the HDMI signal quality and stability.
- HDMI Compliance Software: To test the HDMI signal compliance and detect any potential issues.
- nvidia-l4t-factory-service: To ensure that the GPU driver is installed correctly and functioning properly.
Recommendations
- Verify HDMI Signal Quality: Use an oscilloscope to measure the HDMI signal quality and stability when connecting and disconnecting the HDMI cable.
- Update EDID: Try updating the EDID data manually or using a tool to ensure that the correct EDID is being used for each monitor.
- Check HDMI Hotplug Detection: Verify that the Jetson Orin NX module is detecting the HDMI hotplug event correctly. You can use the
xrandr command to check the display output and detect any potential issues.
By following these recommendations and using the mentioned tools and services, you should be able to identify and resolve the issue with your custom board’s HDMI output.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
hello kevin.chen5,
just for confirmation, can this issue reproduce by reverting the sequence?
for instance,
please try connect to the ASUS VG279Q1A first, and then disconnecting it and reconnecting to the ASUS XG32UQ for testing?
connect to ASUS VG279Q1A first → Display OK,
disconnect and reconnect to ASUS XG32UQ → Display OK,
disconnect and reconnect toASUS VG279Q1A → Hit the issue
hello kevin.chen5,
all right, it seems the failure only reproduced after connect to this 32-inch display.
it might be EDID issue, do you have other display monitor for testing?
or.. could you please try revise display outputs to limit it as 1920x1080@60-fps for testing?
In fact, we already tried several displays as the table below
It’s the only combination to hit the issue.
We also tried to set the display output to Full-HD(1920x1080@60Hz) from UI, it still no display output.
hello kevin.chen5,
please setup a serial console to gather the complete UART logs to disconnect/reconnect with these monitors.
you may save the logs as single text file, and attach it here for reference.
Do you need all of the combinations?
What logs do you need?
We only see the error message from kernel(dmesg) with the combination ASUS XG32UQ → ASUS VG279Q1A.
hello kevin.chen5,
please share the complete UART log regrading to above.
Hi,
Does any of the monitor here support Gsync?
Looks like XG32UQ is the problem here as we don’t support Gsync.
Will this happen with XG32UQ first and then other non-Asus monitors?
No, non-ASUS monitor(AOC U2879VF) works after connecting to XG32UQ.
Hi Sirs,
Does this one issue have any analyze to update?
