Jetson Orin NX Flash flash failure

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

We’re using a Nvidia Jetson Orin NX module with external NVMe memory and the SDKManager running on an Ubuntu 22.04.

When downgrading from JetPack 6.2.1 to JetPack 6.1 using the SDKManager the flashing fails, see attached logs.

SDKManager2.log (12.7 KB)

2

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

Based on the provided context, it appears that you are experiencing issues with downgrading from JetPack 6.2.1 to JetPack 6.1 using the SDKManager on a Nvidia Jetson Orin NX module with external NVMe memory, running on an Ubuntu 22.04 system.

The error logs you provided are not visible, but I can offer some general guidance and potential solutions.

Comparison with similar issues:

  1. OTA Update causing unbootable state: There is a similar issue reported on the Nvidia forums, where an OTA update caused the Jetson Orin Nano to become unbootable. The solution involved reflashing the device using the flash.sh script.
  2. Flash Jetson Orin NX: The provided context includes a section on flashing the Jetson Orin NX, which involves using the l4t_initrd_flash.sh script. This script is used to flash the device, and it may be helpful to try this approach to resolve the issue.

Potential solutions:

  1. Reflash the device: Try reflashing the Jetson Orin NX using the l4t_initrd_flash.sh script, as described in the provided context. This may help resolve any issues caused by the downgrade.
  2. Check the SDKManager logs: Review the SDKManager logs to identify any specific error messages or issues that may be causing the flashing process to fail.
  3. Verify the external NVMe memory: Ensure that the external NVMe memory is properly configured and recognized by the system.
  4. Try a different downgrade method: Instead of using the SDKManager, try downgrading the JetPack version manually using the flash.sh script or other command-line tools.

Additional information:

  • The provided context mentions that the Jetson Orin NX is using external NVMe memory. Ensure that the NVMe memory is properly configured and recognized by the system.
  • The context also mentions that the SDKManager is running on an Ubuntu 22.04 system. Ensure that the system is up-to-date and that all dependencies are properly installed.

If none of these solutions work, please provide more information about the error logs and the specific issues you are experiencing, and I will do my best to assist you further.

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

4

Hi @eos !

You could try disabling your firewall and try reflashing again with the SDK Manager.

sudo ufw disable

Log message:

flash: Either the device cannot mount the NFS server on the host or a flash command has failed. Check your network setting (VPN, firewall,…) to make sure the device can mount NFS server.

If flashing still fails and your goal is to use JetPack 6.1 on NVIDIA Jetson Orin NX with devkit, try downloading the sources from NVIDIA’s official page: NVIDIA JetPack 6.1 sources download and flashing with the l4t_initrd_flash.sh. script.

Nico
Best regards
Embedded Software Engineer at ProventusNova

5

Hera are more logs:

tmp.95KqBDVAGN.log (5.8 KB)

SDKManager.log (11.5 KB)

serial.log (92.0 KB)

6

More information:

I successfully flashed another Jetson Orin NX module using SDK Manager, so the exact same setup worked perfectly with the other module. This was done from scratch—no downgrading involved

7

Hi @eos,

I found this on NVIDIA Jetson Linux release notes (Version 36.4.4) for known issue when flashing Jetpack 6.2.1.

nfsserver
nfsserver615×270 29.1 KB

When downgrading this may be causing the issue.

Also, I would recommend you do a clean flash using the l4t_initrd_flash.sh..

Nico

8

Thanks for the help, Nico.

It seems that the firewall was causing the trouble. At first, I only checked the firewall with the command below, and since it said that the firewall was inactive, I thought that must be okay.

> sudo ufw status
> inactive

But later I did

> sudo ufw disable

After that, everything worked.