Jetson Orin AGX 16GB Developer Kit Not Booting

As of last week my Jetson AGX was working without issues but this week it won’t get past the boot screen even after following the reset options. I have tried entering the boot manager screen as well with both ESC key and F11 approaches for which it then freezes and never gets to the boot manager screen. I would Flash it but I only have an M1 Mac for which you cannot run the SDK Manager on an M1 Mac, given the ARM architecture . So what other options do I have to help restore my Jetson Orin AGX to its original state?

Hi,

Since your AGX Orin not booting, we need you prepare a native ubuntu to full flash or record a serial console log.

Thanks

Hey @DavidDDD thanks for the reply. I spent some time this weekend and got an Ubuntu VM running on my Mac where I was able to remote into the Jetson device. In doing this I was able to clean some things up and getting the Jetson booting back up again. However, to get the state of the device to support the latest Jetson containers and capabilities it seems like I need to upgrade to Ubuntu 22.04.

I have started following the guide below and am up to the point where I’m using the Ubuntu VM (running 22.04) on my Mac and running the commands to flash the Jetson with a NVIDIA and Ubuntu approved 22.04 version. However, when I run the backup_restore command using the parameters suggested in the guide, I get the following output. In doing some research it seems like the issue is related to the fact that my Mac has an ARM architecture vs an expected x86 architecture, which is causing the issue with the flashing? Would be great to get your feedback on this approach knowing that I’m running an Ubuntu 22.04 VM on my Mac with an ARM architecture as my host, trying to flash the Jetson with a upgraded Ubuntu 22.04 OS.

parallels@ubuntu-linux-2404:~/Downloads/Linux_for_Tegra$ sudo ./tools/backup_restore/l4t_backup_restore.sh -r --raw-image ubuntu-22.04-preinstalled-server-arm64+tegra-jetson.img -e mmcblk1 jetson-agx-orin-devkit
Please install the Secureboot package to use initrd flash for fused board

#Entry added by NVIDIA initrd flash tool
/home/parallels/Downloads/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1(rw,nohide,insecure,no_subtree_check,async,no_root_squash)
rpcbind: another rpcbind is already running. Aborting
Export list for localhost:
/home/parallels/Downloads/Linux_for_Tegra/tools/kernel_flash/tmp 127.0.0.1
/home/parallels/Downloads/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash_internal.sh --no-flash --initrd --showlogs jetson-agx-orin-devkit internal


Step 1: Generate rcm boot commandline


ROOTFS_AB= ROOTFS_ENC= /home/parallels/Downloads/Linux_for_Tegra/flash.sh --no-flash --rcm-boot jetson-agx-orin-devkit mmcblk0p1
############################################################################
L4T BSP Information:
R36 , REVISION: 4.3
User release: 0.0
############################################################################
/home/parallels/Downloads/Linux_for_Tegra/flash.sh: line 674: ./tegrarcm_v2: cannot execute binary file: Exec format error
ECID is
Board ID() version() sku() revision()
Preset RAMCODE is
Chip SKU(00:00:00:D0) ramcode() fuselevel(fuselevel_production) board_FAB()
Error: Unrecognized module SKU
Cleaning up…

Guide I’m following: Quick Start — Jetson Linux Developer Guide documentation

/home/parallels/Downloads/Linux_for_Tegra/flash.sh: line 674: ./tegrarcm_v2: cannot execute binary file: Exec format error

Yes, this error comes because you are not using the expected arch host to flash.

Okay, so the only way to flash the Jetson is to buy an Ubuntu 22.04 laptop and connect through that machine? Is there any specific laptop you recommend for this? Even the latest RTX 5090 and 5080 laptops use Windows. The chip architecture is x86 but doesn’t have the correct OS to flash the Jetson. Unless there is now Windows support to be able to flash the Jetson? Would WSL running on Windows 11 Home work for this?

We need x86 arch to flash your device.
You could try dual boot with your windows machine.

Thanks

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.