AGX ORIN OTA update disaply

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

Hi,
We are using the AGX Orin device.
After running sudo ./nv_ota_start.sh /ota/ota_payload_package.tar.gz and rebooting, there is a long period with no display output.
Is there any way to enable a progress indicator during this phase?

Thank you in advance for your support!
Best regards

2

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

The issue you’re experiencing with the Jetson AGX Orin device, where there’s a long period with no display output after running and rebooting, suggests a potential problem with the boot process or the display configuration. To address your question about enabling a progress indicator during this phase, let’s break down the possible approaches and compare them where necessary.

  1. Understanding the Boot Process: The Jetson AGX Orin, like other Jetson devices, uses a complex boot process involving the bootloader, kernel, and system initialization. The absence of a display output during boot could be due to issues at any of these stages.

  2. Serial Console: One of the most straightforward ways to get insights into what’s happening during boot is to use a serial console. By connecting to the device via a serial terminal, you can see boot messages that might indicate where the process is getting stuck. This method is particularly useful for diagnosing early boot issues.

  3. Boot Log: Checking the boot log can provide detailed information about the boot process. For Jetson devices, you can often find boot logs in the system’s syslog or by using specific commands like dmesg after the system has booted (if it eventually does).

  4. HDMI Configuration: Since you’re experiencing issues with display output, ensuring that the HDMI configuration is correct is crucial. The Jetson AGX Orin supports HDMI, and there are tools and configurations available to troubleshoot HDMI issues. For example, you can try using the hdmi tool or checking the device tree configuration related to HDMI.

  5. Progress Indicator: Enabling a progress indicator during boot can be challenging because it typically requires modifying the bootloader or kernel to output status messages or indicators. For some devices, modifying the bootloader (like U-Boot) to display a boot splash screen or progress bar is possible. However, this approach requires a good understanding of the device’s bootloader and may not be straightforward.

  6. Comparison with Other Jetson Devices: It’s worth noting that other Jetson devices, like the Jetson Nano or Jetson Xavier NX, might have similar issues or solutions. For instance, the Jetson Xavier NX has known issues with HDMI display after replacing boot.img and dtb files, which might be relevant if your issue is related to a similar configuration change.

  7. NVIDIA Support and Documentation: NVIDIA provides extensive documentation and support forums for Jetson devices. Checking the official NVIDIA Jetson AGX Orin documentation, developer guides, and support forums can yield specific solutions or workarounds for display issues during boot.

  8. Debugging Tools: Utilizing debugging tools like sudo -s # cat /sys/kernel/debug/bpmp/debug/clk/clk_tree can provide insights into the system’s state during boot, though this might require the system to be partially booted to access such interfaces.

In conclusion, while enabling a progress indicator during the boot phase of the Jetson AGX Orin might be complex and require low-level modifications, there are several diagnostic approaches and tools you can use to troubleshoot and potentially resolve the issue of no display output during boot. These include using serial consoles, examining boot logs, configuring HDMI settings, and consulting NVIDIA’s documentation and support resources. If the issue persists, comparing notes with solutions for similar Jetson devices or seeking help from NVIDIA’s support forums might provide additional insights.

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

4

Hi,

Do you mean you could access the system but not display output?
If can access the system, please dump

  1. dmesg
  2. lsmod | grep nvidia
  3. /var/log/Xorg.0.log

for us to review

5

Hi,
During the OTA update process, there’s a long period in the middle of the update where the display shows nothing — the screen goes completely black.
From the debug console log, we can see the system is running this command automatically:
Run source /mnt/ota_work/nv_ota_rootfs_updater.sh -p /dev/mmcblk0p1 -d /mnt/ota_work /mnt/ota_work/internal_device/system.img 2>&1 | tee -a /mnt/ota_log/ota_19700101-000011.log
However, during this time, the screen remains black for several minutes, which may confuse end users.
Is there any way to show a splash screen or visual progress indicator during this OTA update period?

  1. dmesg log is attached.
    AGX_Orin-dmesg.txt (64.1 KB)
  2. lsmod | grep nvidia
ubuntu@ubuntu:~$ lsmod |grep nvidia
nvidia_drm             94208  1
nvidia_modeset       1261568  4 nvidia_drm
nvidia               1458176  7 nvidia_modeset
nvidia_vrs_pseq        16384  0
tegra_dce              98304  2 nvidia
drm_kms_helper        278528  4 tegra_drm,nvidia_drm
tsecriscv              32768  1 nvidia
host1x_nvhost          40960  10 nvhost_isp5,nvhost_nvcsi_t194,nvidia,tegra_camera,nvhost_nvdla,nvhost_capture,nvhost_nvcsi,nvhost_pva,nvhost_vi5,nvidia_modeset
drm                   602112  12 drm_kms_helper,nvidia,tegra_drm,nvidia_drm
nvidia_p2p             20480  0
host1x                180224  9 host1x_nvhost,host1x_fence,tegra_se,nvgpu,tegra_drm,nvhost_nvdla,nvidia_drm,nvhost_pva,nvidia_modeset
mc_utils               16384  3 nvidia,nvgpu,tegra_camera_platform
  1. /var/log/Xorg.0.log log is attached.
    Xorg.txt (20.6 KB)

Any suggestion or workaround would be appreciated.

Thanks!

6

Hi,

At the moment, only support displaying information on the debug console log.
If you have experience working with displays, feel free to apply their solution to the OTA code since this code is fully open source.

Thanks