Orin NX Unable to Flash

Robotics & Edge Computing Jetson Systems Jetson Orin NX
,
1

I have an Orin NX 16GB on a custom carrier board.

I’ve tried to flash using the SDKManager and the flash script from the Quick Start Guide:

$ sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
  -c tools/kernel_flash/flash_l4t_t234_nvme.xml -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" \
  --showlogs --network usb0 jetson-orin-nano-devkit internal

But both results in the process hanging in the same spot:

01:19:17.230 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: ***************************************
01:19:17.230 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: *                                     *
01:19:17.230 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: *  Step 3: Start the flashing process *
01:19:17.230 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: *                                     *
01:19:17.230 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: ***************************************
01:19:17.261 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Waiting for target to boot-up...
01:19:18.291 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Waiting for target to boot-up...
01:19:19.322 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Waiting for target to boot-up...
01:19:20.352 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Waiting for target to boot-up...
01:19:21.385 - info: NV_L4T_FLASH_JETSON_LINUX_COMP@JETSON_ORIN_NX_TARGETS: Waiting for target to boot-up...

-until it fails. I have attached the serial console log and flash output log:
nx_serial_console_log.txt (90.6 KB)
sdkm-2025-03-18-01-13-20.log (714.4 KB)

I’ve read from other forum posts such as the following where if my device trees are not configured correctly initrd will not boot successfully to complete the flash:

Please correct me if I’m wrong, but it looks from the serial log it’s booted up and there are no errors. What am I missing? What are the “default setting” peripherals that are required for the SDKManager devkit conf to flash successfully?
I’ve read the Bring Up Guide but it does not answer these questions.

2

@WayneWWW @KevinFFF please advise.

3

Just to clarify. Did this host ever flash any Jetson Orin Nano or NX on NV devkit by using initrd flash before?

I just want to make sure the setting on this host is fine.

For example, I notice some errors like below. This is related to your host but not Jetson.

/home/acs/nvidia/nvidia_sdk/JetPack_6.1_Linux_JETSON_ORIN_NX_TARGETS/Linux_for_Tegra/tools/kernel_flash/l4t_initrd_flash.sh: line 46: /sys/module/usbcore/parameters/autosuspend: Permission denied

4

I have not used this host to flash an Orin Nano or NX on NV devkit before, but I’ve been able to flash an Orin AGX multiple times successfully.

5

Orin AGX does not matter. That one is not using initrd flash unless you are flashing Orin AGX nvme or usb drive.

6

Currently I do not have a working NV devkit to test this on.

The logs are from WSL, but I’ve also tried on a Ubuntu system that ran into the same “Waiting for target to boot-up…” issue.

What are some next steps you can suggest to narrow down the problem source?

7

  1. Please do not use WSL to flash Orin NX and Nano. There are known issues on it.
    As Orin NX and Nano are all using external storage.

    image
    image787×236 20 KB

  2. “Waiting for target to boot-up…” is just like any general errors you’ve heard when you used a electrical product like “my phone is dead” or “my computer is dead”. There could be any kind of reasons behind this.

As your previous log is based on WSL, it is not needed to be checked anymore. You should share the log based on your real ubuntu system. They could be all “Waiting for target to boot-up…” but the reasons behind them could be different. So you need to really dump the log out to check.