After flashing the gui gets stucks after hardware configuration

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
1

I created a LinuxforTegra directory and packaged it as a tar file. When I extract the L4T and flash it on the same host PC, everything works fine. However, if I use the same package and extract it on a different PC, it gets stuck during the process. I can log into the system using UART and complete the initial setup, but when I plug in the HDMI, it hangs.

I checked the permissions of the OEM configuration files, and there seems to be no issue there. Here are the commands I used to create and extract the package:

sudo tar -jcvpf quick_start.tar.bz2 Linux_for_Tegra/
sudo tar -jxvpf quick_start.tar.bz2

Could this be related to permission issues, or is there something else I should investigate? Any insights would be greatly appreciated!

image
image1223×694 41.3 KB

2

Hi there @abisheak.p and welcome to the NVIDIA developer forums.

Which Jetson platform are you using? We have dedicated forum categories for Jetson and with that information I could refer you to the best fitting one.

Thanks!

3

Hi @MarkusHoHo , I am using nvidia AGX orin 32 GB model

NVIDIA Jetpack and L4T Version
JP_5.1.2 & L4T_35.4.1

1 Like
5

Hi abisheak.p,

Are you using the devkit or custom board for AGX Orin?

Do you mean that the issue is specific to your 2nd host PC?

Have you referred to Quick Start — Jetson Linux Developer Guide documentation (nvidia.com) to setup the BSP package and rootfs on your host PC again?

Please also share the full serial console log for us to check the hang issue.

6

Hi @KevinFFF

  • For first point the issue is recreating in both the development kit and the custom board for the AGX Orin.
  • The issue is not limited to a single host PC; when I share the L4T tarball created on one PC (running Ubuntu 22.04) to another PC (running Ubuntu 20.04), it also gets stuck. I only copy the images and device tree binaries (DTBs) to the L4T and modules, and I’ve confirmed that the problem persists even when the binaries are excluded. The HDMI drivers are working correctly.
  • Regarding the third point, we consistently use the same steps to set up our Board Support Package (BSP) and root filesystem (rootfs).
  • Will there be any changes to the tarball or L4T if the package is prepared on a different Ubuntu version and shared or copied to other ubuntu versions, such as from 22.04 to 20.04?
    logs from the stuck PC taken from uart
    journalctl_log.txt (447.3 KB)
    dmesh_log.txt (138.6 KB)