Jetson orin nano - flashing issues

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

I’m trying to flash Jetson orin nano dev kit with Jetpack 6.2.1 using SDK manager (Host machine: Ubuntu 20.04). The flashing is not successful, throwing the message “taking too longer to install the package”. How can this issue be resolved?

image
image1022×522 38.6 KB

2

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

To resolve the issue of flashing the Jetson Orin Nano dev kit with Jetpack 6.2.1 using SDK Manager on a host machine running Ubuntu 20.04, where the flashing process is not successful and throws a message indicating it’s taking too long to install the package, follow these steps:

  1. Check the Hardware and Software Requirements: Ensure that your host machine meets the minimum requirements for flashing the Jetson Orin Nano. This includes having a compatible operating system (in this case, Ubuntu 20.04), sufficient disk space, and the correct version of the SDK Manager.

  2. Update SDK Manager: Make sure you are using the latest version of the SDK Manager. NVIDIA frequently updates the SDK Manager to fix bugs and improve performance. An outdated version might cause issues during the flashing process.

  3. Verify the Image: Ensure that you are using the correct image for the Jetson Orin Nano and that it is not corrupted. You can try re-downloading the image to rule out any issues with the download process.

  4. Check the USB Connection: The flashing process requires a stable USB connection between the host machine and the Jetson Orin Nano. Try using a different USB port or cable to rule out any issues with the connection.

  5. Disable Secure Boot (if enabled): Secure Boot can sometimes interfere with the flashing process. If Secure Boot is enabled on your system, try disabling it to see if it resolves the issue.

  6. Increase the Timeout Value: The error message indicates that the process is taking too long. You can try increasing the timeout value in the SDK Manager settings. This will give the flashing process more time to complete, which might help if the issue is due to the process taking longer than expected.

  7. Reboot and Retry: Sometimes, simply rebooting both the host machine and the Jetson Orin Nano and then retrying the flashing process can resolve the issue.

  8. Check for Conflicting Processes: Other processes running on your host machine might be interfering with the flashing process. Try closing all unnecessary applications and background processes before attempting to flash the device again.

  9. Use the Command Line: Instead of using the graphical interface of the SDK Manager, try flashing the device using the command line. This can provide more detailed output and might help in diagnosing the issue.

  10. Seek Additional Help: If none of the above steps resolve the issue, it might be helpful to seek additional assistance from NVIDIA’s official forums or support channels. There, you can find more specific advice or even patches for known issues.

Comparison with Other Platforms:

  • Jetson TX2 Series: If you have experience with the Jetson TX2 series, note that the Orin Nano has different hardware and software requirements. Ensure you’re following the guidelines specific to the Orin Nano.
  • x86_64 with RTX 4090: This platform is significantly different from the Jetson Orin Nano, as it involves an x86 architecture with an NVIDIA RTX 4090 GPU. Flashing and setup processes will be entirely different and are not directly comparable.
  • AGX Orin: While the AGX Orin is part of the same NVIDIA Jetson family as the Orin Nano, it’s designed for more complex and demanding applications. The flashing process might share some similarities but will have distinct requirements and steps.

Additional Tips:

  • Always refer to the official NVIDIA documentation for the most current and detailed instructions.
  • Ensure your host machine’s BIOS is up to date, as this can sometimes affect USB connectivity and performance.
  • If possible, try the flashing process on a different host machine to isolate if the issue is with the machine or the Jetson Orin Nano itself.

By methodically going through these steps and considering the specifics of your setup, you should be able to resolve the issue and successfully flash your Jetson Orin Nano dev kit with Jetpack 6.2.1.

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

3

please stop the sdkamanger flash process and click the “export logs” button on it and attach the full logs.

5

SDKM_logs_2025-07-22_10-35-54.zip (11.3 MB)

Hi Wayne,
The flashing stuck at 99% and I’ve attached the log file above.

6

I got a similar issue with the GPT table corrupt and I did all troubleshooting and it is still an issue. I got the same message. The system finished displaying OK but I do not understand why is showing that error. Besides, when I run from the Jetson Orin Nano, I am not able to run the browser. I got a video from jetsonhackings in youtube and I resolved the browser issue but the flashing issue is still there.

7

The log file you shared only has the jetpack5 log inside. Are you sure this is the correct log?

8

Yes Wayne. For your reference, I’m sharing the recent log file here.
SDKM_logs_2025-07-22_15-33-08.zip (11.3 MB)
SDKM_logs_JetPack_6.2.1_Linux_for_Jetson_Orin_Nano_[8GB_developer_kit_version]_2025-07-22_14-40-21.zip (1.5 MB)

9

I don’t see any “command error code :137” in your text log here.

It looks like you are flashing the sdcard. Do you have other boot medium that can flash? For example, the usb drive or nvme to test.

Or have you tried other sdcard?

10

I don’t have Nvme or USB drive. May be I’ll try with another SD card. But, Is that the issue causing Flash failure?

11

It could be. Your process of flashing is already in the later stage.

12

Hi Wayne,
I can able to flash with NVMe 128 GB. Thanks for your support. But “GPT table corrupt” error is still existing. May I know what could be the possible reason?

14

The message backup GPT table corrupt could just be a harmless log.
Were you able to access the system after the SDK Manager finished flash?

17

Hi,

I’ve flashed a jetsn orin nano module using SSD and it is working fine. But, when I try to use the same SSD for another nano module, it is not booting up. Do I need to flash the module with SDK manager? May I know what could be the reason and where the bootloader and rootfs will be stored while flashing?

18

Hi,

The MB1/MB2 is stored in QSPI on the Orin Nano module.

Therefore, if your other Orin Nano module has not been flashed yet, it may not be able to boot.

Thanks

19

Hi,

Just to add my experience: the developer kit Orin Nano modules I’ve bought have always come with QSPI pre-flashed, so they boot out of the box.
By contrast, the production SOMs I’ve purchased from various distributors have all shipped blank (no QSPI image), and must be flashed (MB1/MB2/UEFI + board config) before they will boot.

Best Regards.

20

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