Unable to flash the NVME (r36.2 Jetpack 6.0DP)

Robotics & Edge Computing Jetson & Embedded Systems Jetson Orin Nano
1

I am unable to flash the NVME on a Jetson Orin Nano Dev Kit. I am using r36.2 (Jetpack 6.0DP) which is a requirement as we needed the exact Linux kernel on this release. I am using the instructions here Quick Start — NVIDIA Jetson Linux Developer Guide 1 documentation on an Ubuntu 20.04 computer.

These are the files used (from Jetson Linux 36.2 | NVIDIA Developer):

  • Jetson_Linux_R36.2.0_aarch64.tbz2
  • Tegra_Linux_Sample-Root-Filesystem_R36.2.0_aarch64.tbz2

I am specifically using the command

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

Running this command, it always times out and i kept on getting the message:

***************************************
*                                     *
*  Step 3: Start the flashing process *
*                                     *
***************************************
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Waiting for target to boot-up...
Timeout
Cleaning up...

Attached is the log from the serial of Jetson Nano

putty.log (78.0 KB)

Also, i tried the following:

  • Flashing the internal emmc works using sudo ./flash.sh -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal I was able to boot-up the Jetson Nano without the NVME nor SD card.
  • Using SDK Manager 2.2.0, I was able to flash the NVME using Jetpack 6.0 Rev 2. Unfortunately, we need the Jetpack 6.0 DP.
  1. What could be the reason as to why the l4t_initrd_flash.sh command didn’t work?
  2. I prefer using the command from the quickstart but since the SDK Manager was able to flash the NVME, is there a way to be able to see Jetpack 6.0DP on the SDK Manager as we need the exact Linux kernel version on 6.0DP? Only 6.0 Rev 2 is accessible on the SDK manager.

thanks

2

The R36.2 is a Developer Preview quality release, which is not suggested to use for product development, and no plan to fix any issue on that version.
Please use the latest JetPack 6.2.

Thanks

4

as much as we would like to use the latest Jetpack, unfortunately, we have a vendor for a hardware device that have drivers that uses the Linux kernel version (5.15.122) specifically used on Jetpack 6.0DP (r36.2). We don’t have a choice as of the moment and we don’t know when will the vendor update their drivers to the latest kernel.

I was able to flash the NVME before with the 6.0DP, but on this newly formatted machine with Ubuntu 22.04, I wasn’t able to do that using the same instructions on the quickstart. I tried flashing the orin nano dev kit with r36.3 on the NVME and it was able to flash successfully but that isnt using 5.15.122.

Basically, we need a Jetpack that is using kernel version 5.15.122 on nvme. What other options do I have? is there a way to make the 6.0DP appear on SDKManager?

for now, our plan is to continue with the internal development with 6.0DP 5.15.122. The 6.0DP ISO works with the SDcard, but we need it to be on nvme. I tried flashing the iso on the nvme and it failed on bootup as the image on the ISO is looking for references for nvme0n1p1.

5

solved it. there is a problem on l4t_initrd_flash.sh of 36.2