AGX will not boot after flashing

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

Hello,

I’m struggling to get my newly unboxed AGX 32G to boot. This is the history:

  1. I used the SDK manager (v2.3.0.12626) to flash the OS as well as install some components like the container runtime. But this failed on component install with an error saying something about the target image version was incompatible (sorry, I no longer have that error).

  2. I flashed the device using the instructions in the Quick Start (r36.4.4). This worked and I was able to use the OS. But I messed up the manual container install and decided just to try again with a fresh flash. BAD DECISION!

  3. I have tried the same manual re flashing process several times now without luck. I’ve also tried the SDK with just the flash (no components) and no luck. In both cases the console says everything is great (manual logs below), but I never get any video or other signal the computer is ready. (I tested the video cable and it works fine).

One potential clue is that after installation the device still shows up on lsusb, as if it’s still in recovery mode?

[ 708.2991 ] Flashing completed

[ 708.2992 ] Coldbooting the device
[ 708.3004 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 708.3015 ] MB2 version 01.00.0000
[ 708.3730 ] Coldbooting the device
[ 708.3740 ] tegrarcm_v2 --chip 0x23 0 --reboot coldboot
[ 708.3749 ] MB2 version 01.00.0000
*** The target generic has been flashed successfully. ***
Reset the board to boot from internal eMMC.

user@puget-251514:~/Downloads/jetson_setup/Linux_for_Tegra$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 248a:8367 Maxxter Telink Wireless Receiver
Bus 001 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 001 Device 028: ID 0955:7223 NVIDIA Corp. APX
Bus 001 Device 004: ID 0b05:19af ASUSTek Computer, Inc. AURA LED Controller
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

HELP!!!

2

Hello @milan17,

Sorry to hear you are having issues with your new board.

Yeah, it seems like the board is stuck in recovery mode.

Can you power cycle the board (into recovery mode), then re-flashiing and sharing the whole flashing log ?

Also, can you connect with board through UART ? This would give us access to more logs.

best regards,
Andrew
Embedded Software Engineer at ProventusNova

3

Thank you for the fast response. How do I send the flash logs? It’s too much data for this window. How do I get into UART?

4

flash_log.txt (102.1 KB)

5

Hello @milan17,

Sure, no problem!

Let me answer your questions 1 by 1:

  1. How do I send the flash logs?

Try capturing the output of the flash command into a file. Then share the file.

<YOUR FLASH COMMAND> | tee -a flash_log.txt
  1. How do I get into UART?

You will need to connect the board to your computer via USB through Port 9 here in the image:

image
image932×868 107 KB

Then you can install a tool like minimum in your PC:

apt install minicom

And use it to access the board:

minicom -D /dev/ttyACM0 -8 -b 115200

Please let me know if you have any further questions.

best regards,
Andrew
Embedded Software Engineer at ProventusNova

6

I sent you the logs from the previous command line flash. I can do the same for the SDK flash if needed.

I installed minicom, but unsure how to connect to the AGX. I don’t see a /dev/ttyACM0 device. I tried using the device number reported in lsusb, but that doesn’t seem to do anything. And even once I do connect, I’m not sure what steps to take to reset the board. I wish there was just a “factory reset” button somewhere…

Thanks again for your help.

7

I tried to install again this morning, this time repeating the process of installing the additional software components via the SDK. It got past the flash phase (as it normally does), but complains during a “readiness check” before installing the components. It passed all checks except “Device image version matching requirement”. It complains:

Detected unsupported device image version on your target device for PREREQUISITE_DEVICE_IMAGE_VERSION_TARGET. The supported device image version to install current target components is 36.4.4-20250616085344.

To fix this issue, please flash the device with the matching device image version, or install the components that match current device image version on device.

Note that 36.4.4 is the version I tried to flash directly from the Ubuntu terminal (logs earlier attached in this thread). Perhaps that’s a clue to the problem?

8

I just re-flashed from the Ubuntu terminal with R36.4.4. As always, the program claims everything is successful but I get nothing when the machine boots. Just a blank monitor. Logs attached.

R36_4_4.txt (102.0 KB)

9

@proventusnova , I just noticed that I don’t have port 9 as in your diagram. I guess that’s the USB-mini that I’ve read people are using to connect, but that’s not on my hardware. I only have a USB-C that I used to flash, which is next to a 40 pin header. I also have the two regular USB-A ports near the ethernet jacks. I also do not have that little arched cutout near the power buttons. Mine is flat all the way around.

Do I have an old board or a new board?

11

My kit looks like the one pictured here. https://www.seeedstudio.com/AGX-Orin-32GB-H01-Kit-p-5569.html?srsltid=AfmBOooxk3KHojZz8I7TxT3Teqkxh8CSVBbS7GiB6Bled8TkgoRYXUBI , it’s the 32GB version that doesn’t have a mini-USB.

12

I contacted Andres Campos from @proventusnova . He helped me understand that I needed to install the carrier board drivers in addition to the regular Jetson stuff. Those guys are great. Thanks Andres!

1 Like
13

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