Flashing Orin Nano Dev Kit NVMe hangs at 99%

I’ve been attempting to use SDK manager to flash a new Orin Nano Developer Kit (via USB) without luck. The flashing process shows progress, which slows down when it gets to around 90%. It stays at 99% for a long time and then asks if I want to re-try.

  • Using Ubuntu 20.04 host OS, not in a VM
  • Tried several different USB cables and ports on the host
  • Used SDK Manager from both the Docker container and .deb installer, same results
  • The Nano boots with an SD card pre-flashed and I can see the NVMe SSD drive

Are there recommendations about what to try next?

Also, I’ve seen guidance on here to find another x86_64 (bare metal) host and install Ubuntu 18.04. For me, it would be a significant investment of time to find such a sacrificial system, so I don’t want to do it unless it’s 100% that will work. (And then, why would the documentation claim Ubuntu 20.04 is supported?)


Please at least dump the log from SDK Manager, or there is nothing we can help with information like which slows down when it gets to around 90%.

I temporarily gave up on SDK Manager and switched to try to use Jetson Linux Quick Start (Quick Start — Jetson Linux Developer Guide documentation), as I just want to get the OS installed. Downloaded release 35.4.1 and followed the instructions.

I’ve attached the log produced by the l4t_initrd_flash.sh script.

flash_1-3_0_20231108-102307.log (6.2 KB)

Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
mount.nfs: Connection timed out
Flash failure
Cleaning up...

@DaveYYY, I am happy to try SDK Manager again if you think that would provide better diagnostics. Can you provide an example of outputting the logs using the CLI in docker? It launches a text user interface that makes bulk copying the log difficult.

I’m closing this topic due to there is no update from you for a period, assuming this issue was resolved.
If still need the support, please open a new topic. Thanks

Please also dump the serial console log as indicated here: