Agx orin flash failed: ERROR: might be timeout in USB write

when I flash 35.3.1 image to jetson agx orin, it failed at “ERROR: might be timeout in USB write.” The carrier board is custom. On the same carrier board, the orin module early flashes well, but the recently newly buying orin module flashing failed. The flashing log refers to the flash.log
flash.log (72.6 KB)

Hi,
If the device cannot be flashed/booted, please refer to the page to get uart log from the device:
Jetson/General debug - eLinux.org
And get logs of host PC and Jetson device for reference. If you are using custom board, you can compare uart log of developer kit and custom board to get more information.
Also please check FAQs:
Jetson AGX Orin FAQ
If possible, we would suggest follow quick start in developer guide to re-flash the system:
Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation
And see if the issue still persists on a clean-flashed system.
Thanks!

Please dump the serial console log during flash failure.

orin_flash_fail.txt (7.9 KB)
orin_flash_success.txt (116.7 KB)
orin_flash_fail.txt is the debug uart log when flash failed, orin_flash_success.txt is the log when flash success. the carrier board and the operation are both the same, the only difference is the module, the normal one is purchased three months ago, the abnormal one is purchased last week from the same retailer

Hi,

This might be a similar situation to the one discussed in this topic. Please try flashing your newly buying orin module with either Jetpack 5.1.4 or Jetpack 6.1 instead.

Thanks.

For me, this was nothing to do with USB but actually a corrupt system.img. Look at

~Linux_for_Tegra_xxx/tools/kernel_flash/images/external/system.img

If it’s small, mine was 10KB, then it didn’t create properly. You’d also see this in the flash command output (yet the script will still finish and say it succeeded!)

Copying APP image into  /home/user/Linux_for_Tegra_5.1.2/tools/kernel_flash/images/external/system.img.raw
tar: ./: Cannot savedir: Bad message
tar: Exiting with failure status due to previous errors

sudo rm it and try again.

1 Like

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