HDMI Blank Screen Issue on Nvidia Jetson Orin Nano Dev Board

Issue Overview

Users are experiencing a blank HDMI screen when resuming their Nvidia Jetson Orin Nano 8G device running L4T363. The issue manifests after the device resumes from sleep or low-power states, where the HDMI output fails to recover even after re-plugging the HDMI cable, necessitating a full reboot of the device. Users have tested multiple HDMI monitors (more than four different types) and confirmed that the issue is consistent across all devices. There are no visible error messages in the logs, although one user noted a specific error message related to GPU timeout:

[ 107.758172] nvgpu: 17000000.gpu pmu_wait_message_cond:664 [ERR] PMU wait timeout expired.

This issue significantly impacts user experience as it disrupts workflow and requires manual intervention to reboot the device.

Possible Causes

1. Hardware Incompatibilities or Defects: The problem may arise from compatibility issues between the Orin Nano and specific HDMI monitors or cables.
2. Software Bugs or Conflicts: There could be bugs in the L4T363 version that affect HDMI functionality during resume operations.
3. Configuration Errors: Incorrect device tree settings (dtsi and dtbo files) might lead to improper hardware initialization.
4. Driver Issues: Outdated or incompatible GPU drivers may cause the system to fail in handling HDMI signals correctly after resuming.
5. Environmental Factors: Power supply inconsistencies or overheating could affect device performance and functionality.
6. User Errors or Misconfigurations: Users might inadvertently misconfigure settings that impact HDMI output during resume.

Troubleshooting Steps, Solutions & Fixes

1. Check Monitor Compatibility:

   • Test with different HDMI monitors to confirm if the issue persists across various devices.

2. Review Logs for Errors:

   • Analyze system logs for any errors related to GPU or HDMI output:

     dmesg | grep nvgpu
     

3. Update Configuration Files:

   • Ensure that the correct device tree source files (dtsi and dtbo) are being used for L4T363. Users reported success by correcting these files:
     • Verify that you are using the appropriate configuration files for your specific hardware setup.

4. Update Software and Drivers:

   • Ensure that your system is running the latest version of JetPack and L4T. If not, follow these steps to update:

     sudo apt update
     sudo apt upgrade
     

5. Force Recovery Mode:

   • If issues persist, try putting the device into recovery mode and re-flashing with JetPack:

     # Connect pins for recovery mode
     sudo reboot --force forced-recovery
     

6. Power Supply Check:

   • Verify that you are using a compatible power supply (19V for Orin Nano) and that it is functioning correctly.

7. Testing with Different Configurations:

   • Isolate the issue by testing with minimal configurations (e.g., disconnecting peripherals) to identify potential conflicts.

8. Seek Community Support:

   • Engage with community forums for additional insights or similar experiences from other users.

9. Documentation Reference:

   • Refer to official Nvidia documentation for further troubleshooting steps and configuration guidelines:
     • Jetson Orin Nano Developer Kit User Guide
     • NVIDIA Jetson Linux Developer Guide

10. Recommended Approach:

    • Many users found success by ensuring they were using the correct dtsi and dtbo files, which resolved their HDMI issues.

Unresolved aspects may include further investigation into specific hardware interactions or deeper software bugs within L4T363 that require Nvidia’s attention for a permanent fix.