I found during testing on our AGXorin customized carrier board that,
- If the HDMI cable is connected right after booting up, then when I reboot the system, at the last moment of the reboot, a white screen will definitely appear,
- If you don’t connect the HDMI cable when booting up, wait until the system completes booting and insert the HDMI cable, then reboot the system. This will result in a torn logo, but there will be no white screen image
May I ask what could be causing these two issues? We have replaced many monitors of different brands and resolutions, and we have encountered these two problems
*** Please note that this reply is generated by LLM automatically ***
The issues you’re experiencing with your customized Jetson AGX Orin carrier board, specifically the appearance of a white screen or a torn logo when connecting an HDMI cable at different times during the boot process, can be attributed to several factors. To address these issues, let’s break down the potential causes and compare them:
-
HDMI Connection Timing: The timing of when you connect the HDMI cable seems to affect the outcome. Connecting the HDMI cable right after booting up results in a white screen, while connecting it after the system has completed booting leads to a torn logo. This suggests that the issue might be related to the initialization process of the HDMI interface or the display settings.
-
Display Settings and EDID: The Extended Display Identification Data (EDID) is a data structure provided by the display to the graphics card, describing the display’s capabilities. Issues with reading or interpreting the EDID can lead to display problems. The fact that you’ve tried different monitors and resolutions suggests that the problem might not be specific to the display but rather how the Jetson AGX Orin handles display settings.
-
Custom Carrier Board Design: Since you’re using a customized carrier board, there might be design-specific issues affecting the HDMI output. This could include problems with signal integrity, power supply to the HDMI port, or incorrect configuration of the HDMI interface in the device tree or kernel settings.
-
Kernel and Device Tree Configuration: The kernel and device tree configurations play a crucial role in defining how hardware components, including the HDMI interface, are initialized and managed. Incorrect or incomplete configurations could lead to the issues you’re experiencing.
-
Firmware and Software: Firmware and software updates can sometimes resolve issues related to hardware initialization and interface management. Ensuring that your Jetson AGX Orin is running the latest firmware and software might help resolve the problem.
Comparison with Similar Issues:
- The problem of a “white screen” or display issues on boot is not unique to your setup. Similar issues have been reported in various contexts, including with other Jetson modules and different Linux distributions.
- The fact that changing the timing of the HDMI connection affects the outcome suggests a timing or initialization issue, which is consistent with some of the reported problems in the context of Linux and display settings.
Recommendations:
- Review your device tree and kernel configurations to ensure that the HDMI interface is properly configured.
- Check for firmware and software updates for your Jetson AGX Orin.
- Verify that your customized carrier board design does not introduce any issues with the HDMI signal or power supply.
- Consider testing with a different HDMI cable or a different display to further isolate the problem.
- If possible, compare the behavior with a standard Jetson AGX Orin developer kit to see if the issue is specific to your customized carrier board.
By systematically addressing these potential causes and comparing your setup with known configurations and behaviors, you should be able to identify and resolve the issue affecting your Jetson AGX Orin’s HDMI output.
*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***
We tested ORIN OrinNX and Orinnano, we found that as long as the display interface is configured as HDMI, this phenomenon will occur
May I confirm what is your method to configure HDMI?
We have confirmed pinmux config set pin to hdmi ,and added the following content in the flash config
Which Jetpack release is in use here?
Are you talking about issues that happen during shutdown/reboot or you are talking about issues during boot process?
version is jetpack 6.2
Both of these issues occur during the process of reboot or shotdown
