HDMI error cause system crash

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Module: Jetson AGX Orin 32G

software: Jetpack-5.1.4

When I configured HDMI，Every time the cable is plugged or unplugged, a warning message will be printed, and The system may freeze randomly when shutting down.

If we don’t want to upgrade to the jetpack6.2 ，How can we solve this problem?

tegra234-dcb-p3701-0000-a02-p3737-0000-a01_hdmi.txt (27.6 KB)

11.28-11：42-高温测试关机变重启.txt (593.0 KB)

3

*** Please note that this reply is generated by LLM automatically ***

The issue you’re experiencing with the Jetson AGX Orin module, specifically with the HDMIEvery time the cable is plugged or unplugged, a warning message is printed, and the system may freeze randomly when shutting down, is likely related to the HDMI driver and its interaction with the system.

Since you’re using Jetpack 5.1.4 and don’t want to upgrade to Jetpack 6.2, we’ll focus on finding a solution within the current software version.

Here are a few potential solutions you can try:

  1. Disable HDMI warnings: You can try disabling the HDMI warnings by adding the following line to the /boot/extlinux.conf file:
setenv hdmi_warnings 0

This will disable the warning messages when the HDMI cable is plugged or unplugged.

  1. Update the HDMI driver: Although you don’t want to upgrade to Jetpack 6.2, you can try updating the HDMI driver to a newer version within Jetpack 5.1.4. You can do this by running the following command:
sudo apt-get update && sudo apt-get install nvidia-l4t-hdmi

This will update the HDMI driver to the latest version available in Jetpack 5.1.4.

  1. Configure the HDMI settings: You can try configuring the HDMI settings to prevent the system from freezing when shutting down. You can do this by adding the following lines to the /boot/extlinux.conf file:
setenv hdmi_mode 0
setenv hdmi_force_hotplug 0

This will set the HDMI mode to 0 (which disables the HDMI hotplug detection) and prevent the system from freezing when shutting down.

  1. Use a different HDMI port: If you’re using a specific HDMI port, try switching to a different port to see if the issue persists.

  2. Check the HDMI cable: Make sure the HDMI cable is securely connected to both the Jetson module and the display device. Try using a different HDMI cable to rule out any issues with the current cable.

  3. Reboot the system: Sometimes, simply rebooting the system can resolve the issue.

If none of these solutions work, you may want to consider upgrading to Jetpack 6.2, which may include fixes for this issue.

In comparison to the provided gst-launch commands, the issue you’re experiencing is not directly related to the H.265 encoding or decoding process. However, if you’re experiencing issues with video playback or encoding, you may want to try updating the NVIDIA drivers or configuring the HDMI settings as mentioned above.

The provided gst-launch commands are used for H.265 encoding and decoding, and they may not be directly related to the issue you’re experiencing. However, if you’re experiencing issues with video playback or encoding, you may want to try using a different gst-launch command or configuring the HDMI settings as mentioned above.

In summary, the issue you’re experiencing is likely related to the HDMI driver and its interaction with the system. You can try disabling HDMI warnings, updating the HDMI driver, configuring the HDMI settings, using a different HDMI port, checking the HDMI cable, or rebooting the system to resolve the issue.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

5

It is a known issue on JP5 and won’t get fixed on JP5. Please upgrade to JP6 or try the WAR to disable GPIO interrupt function on GPIO PM.0 before going to shutdown or suspend.