Jetson Orin Nano Flashing Problem

Hello,

I bought a Waveshare Custom Board for my Jetson Orin Nano 8GB module, but I keep getting the same error when trying to install it with SDK Manager. I’m using Ubuntu 22.04 and trying to install JetPack 6.1 (rev1). When I install to the SD card, the installation succeeds in all sections, but the flashing section gets stuck at 99.83. When I try to install to NVMe (I was advised to install to NVMe even though I have an SD card), I get the following error:

ERROR: Flash Jetson Linux - flash: [exec_command]: /bin/bash -c /home/fethi/.nvsdkm/replays/scripts/JetPack_6.1_Linux/NV_L4T_FLASH_JETSON_LINUX_COMP.sh; [error]: Job for nfs-server.service canceled.
16:16:28 INFO: Flash Jetson Linux - flash: [ Component Install Finished with Error ]
16:16:28 INFO: Flash Jetson Linux - flash: [host] [ 6.73 MB used. Disk Avail on Partition /dev/nvme0n1p4: 11.29 GB ]
16:16:28 INFO: Flash Jetson Linux - flash: [ NV_L4T_FLASH_JETSON_LINUX_COMP Install took 21s ]
16:16:28 ERROR: Flash Jetson Linux - flash: command error code: 11
16:16:28 ERROR: Flash Jetson Linux - flash: command terminated with error
16:16:28 SUMMARY: Flash Jetson Linux - flash: Installation failed.

Here log file:

SDKM_logs_JetPack_6.1_(rev._1)_Linux_for_Jetson_Orin_Nano_8GB_2025-08-23_16-15-39.zip (945.7 KB)

When I try to install it manually (I also got this error in the SDK Manager), I get the following error:
[ 0.3336 ] Sending blob
[ 0.4283 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-3 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Cleaning up…

*** Please note that this reply is generated by LLM automatically ***

Based on the provided context, it appears that you are experiencing issues with flashing your Jetson Orin Nano 8GB module on a Waveshare Custom Board using the SDK Manager. You’ve tried installing to both the SD card and NVMe, but encountered errors in the flashing section.

To address your issue, let’s break down the possible causes and solutions:

  1. SD card installation: The installation succeeds in all sections except the flashing section, which gets stuck at 99.83%. This could be due to a variety of reasons, such as:
    • Insufficient power supply to the module.
    • Incorrect SD card configuration or compatibility issues.
    • Firmware or software issues with the module or SD card.

To troubleshoot, try using a different SD card or checking the power supply to the module. You can also try flashing the module using a different method, such as using the flash.sh script.

  1. NVMe installation: When trying to install to NVMe, you encounter an error message indicating that the installation failed with error code 11. This could be due to:
    • Incompatible NVMe configuration or firmware.
    • Insufficient disk space or incorrect partitioning.
    • Software or firmware issues with the module or NVMe.

To troubleshoot, check the NVMe configuration and firmware version. Ensure that the disk space is sufficient and the partitioning is correct. You can also try flashing the module using a different method, such as using the flash.sh script.

Comparison with similar issues:

  • In the provided context, there are several topics related to flashing and installation issues on Jetson modules. For example, “Timeout when flashing Jetson Orin Nano 8G module” and “Error: flash.idx is not found Jetson Orin Nano reflash” may be related to your issue.
  • Another topic, “Flash Orin image to NVME Jetson AGX Orin hw, reflash, board-design, level3”, discusses flashing the Orin image to NVMe, which may be relevant to your issue.

Recommendations:

  • Try using a different SD card or NVMe configuration to rule out hardware issues.
  • Check the power supply to the module and ensure it is sufficient.
  • Use the flash.sh script to flash the module instead of the SDK Manager.
  • Verify the firmware and software versions on the module and NVMe to ensure compatibility.
  • Consult the Jetson Linux documentation and NVIDIA forums for further troubleshooting and support.

By following these steps and comparing your issue with similar topics, you should be able to resolve the flashing issue with your Jetson Orin Nano 8GB module on the Waveshare Custom Board.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

Just some notes:

  • Waveshare probably uses their own flash software, or possibly a patch to the NVIDIA flash software. You need to check their docs.
  • USB errors usually occur when using a VM. The USB will disconnect and reconnect during a flash, and most VMs fail to get the USB back during a reconnect. That’s something the VM vendor would have to help with configuring.
1 Like

I don’t use a VM. There is no information about this on the Waveshare site. It shows via SDK Manager and manual Flash. I tried both and couldn’t get over this USB Timeout error

What is your manual flash command? And what is the full log for that?

You might move the USB cable to a different port, or try a different cable. If a HUB is involved, try without the HUB. If Waveshare says to use the default NVIDIA flash software, then it should work. The log WayneWWW is asking about might reveal which part of the hardware is failing to respond when you see the timeout. If you flash on command line (such as initrd flash or just manual use of flash.sh), then you can log by appending " 2>&1 | log_flash.txt". Example:
sudo ./flash.sh .... 2>&1 | tee log_flash.txt
(then attach log_flash.txt to the forum)

Note that JetPack has a button to export logs. Additionally, you can log the serial console of the Jetson itself during a flash and save that log. Logging serial console too gives both sides of the log story.

1 Like

I don’t use any hubs. But I also tried using it, I don’t think there is a problem with USB ports. I’m adding the log you want below, and my flash command is:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 -p “-c ./bootloader/generic/cfg/flash_t234_qspi.xml” -c ./tools/kernel_flash/flash_l4t_t234_nvme.xml --showlogs --network usb0 jetson-orin-nano-devkit-super external 2>&1 | tee log_flash.txt

log_flash.txt (277.8 KB)

Could you try if rel-36.4.4 could flash it with manual command?

1 Like

the same problem persists. Here is the log file:

log_flash.txt (277.4 KB)

please enable serial console log from device and dump it during flash.

The failure happened in a unexpected timing.

1 Like

This is result:

[0001.024] E> MSS: Failed to initialize SDRAM. [0001.028] C> Task 0x2f failed (err: 0x48480112) [0001.032] E> Top caller module: MSS, error module: MSS, reason: 0x12, aux_info1 [0001.040] C> Boot Info Table status dump : 01111111001110001111111111111111111111111111101

When I try to flash it, this error appears in the debug console again:

[0086,762] E> MSS: Failed to initialize SDRAM.
[0086,767] C> Task 0x2f failed (err: 0x48480112)

@malatyali44 Instead of trying the SDK flash method, which in your case seems to fail, burn the jetpack image on the SD using your host computer, then finish the installation on the Jetson.

Download https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v4.0/jp61-orin-nano-sd-card-image.zip or https://developer.nvidia.com/downloads/embedded/L4T/r36_Release_v4.0/jp61-rev1-orin-nano-sd-card-image.zip and unzip. After use dd if on Linux, or rufus if on Windows, and burn sd-blob.img to the SD.

Boot using the SD card then repeat the process on the Jetson to burn the image to the NVMe drive. Before restarting edit /boot/extlinux/extlinux.conf on the NVMe and change root partition to root=/dev/nvme0n1p1 otherwise it will still look for a root partition on the SD and boot will fail without the SD present.

1 Like

There is no update from you for a period, assuming this is not an issue anymore.
Hence, we are closing this topic. If need further support, please open a new one.
Thanks
~0924

Please attach full log of host and uart log. Not just few lines.

Using sdcard image won’t work. The error happens in bootloader which is still far away from booting the storage.