Nvautoflash r36.4.3 jetpack6.2 stucked

What’s wrong with nvautoflash and my system?

$ wget https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v4.3/release/Jetson_Linux_r36.4.3_aarch64.tbz2
$ wget https://developer.nvidia.com/downloads/embedded/l4t/r36_release_v4.3/release/Tegra_Linux_Sample-Root-Filesystem_r36.4.3_aarch64.tbz2
$ tar xf Jetson_Linux_r36.4.3_aarch64.tbz2
$ sudo tar xpf Tegra_Linux_Sample-Root-Filesystem_r36.4.3_aarch64.tbz2 -C Linux_for_Tegra/rootfs/
$ cd Linux_for_Tegra/
$ sudo ./tools/l4t_flash_prerequisites.sh
$ sudo ./apply_binaries.sh
$ sudo sysctl net.ipv6.conf.all.disable_ipv6=0
$ sudo sysctl net.ipv6.conf.default.disable_ipv6=0
$ sudo ./nvautoflash.sh

Then I got stucked here:

[  24.5527 ] Retrieving storage infomation
[  24.5537 ] tegrarcm_v2 --chip 0x23 0 --oem platformdetails storage storage_info.bin

More than 10 mins, I killed the script. Any idea?

Detailed log: nvautoflash_r36.4.3.log (94.7 KB)

PS: I had nvautoflash issue too on r35.6.0 Jetpack5.1.4.

EDIT: check dmesg again, there are a few line’s of printf, but I don’t know what it might be. Just for log.

[15013.513164] usb 4-1: USB disconnect, device number 12
[15019.487973] usb 4-1: new high-speed USB device number 13 using ehci-pci
[15019.619607] usb 4-1: New USB device found, idVendor=0955, idProduct=7523, bcdDevice= 4.01
[15019.619621] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15019.619626] usb 4-1: Product: APX
[15019.619631] usb 4-1: Manufacturer: NVIDIA Corp.
[15048.864208] usb 4-1: USB disconnect, device number 13
[15049.116998] usb 4-1: new high-speed USB device number 14 using ehci-pci
[15049.246653] usb 4-1: New USB device found, idVendor=0955, idProduct=7523, bcdDevice= 4.01
[15049.246665] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15049.246669] usb 4-1: Product: APX
[15049.246671] usb 4-1: Manufacturer: NVIDIA Corp.
[15055.965096] usb 4-1: USB disconnect, device number 14
[15056.222970] usb 4-1: new high-speed USB device number 15 using ehci-pci
[15056.355517] usb 4-1: New USB device found, idVendor=0955, idProduct=7523, bcdDevice= 4.01
[15056.355529] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15056.355532] usb 4-1: Product: APX
[15056.355534] usb 4-1: Manufacturer: NVIDIA Corp.
[15094.596173] loop17: detected capacity change from 0 to 115343360
[15095.577673] EXT4-fs (loop17): mounted filesystem fff5deba-3c28-46c7-b4c0-4023afb12215 r/w with ordered data mode. Quota mode: none.
[15761.496744] EXT4-fs (loop17): unmounting filesystem fff5deba-3c28-46c7-b4c0-4023afb12215.
[16012.441124] loop17: detected capacity change from 0 to 131072

EDIT2: I have sucessfully flashed system with following commands:
flash_4-1_0_20250126-144142.log (47.5 KB)

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

please dump serial console log from UART during flash.

See above log files, they are from seiral console.

They are not serial console from UART… Those are just log from your host PC which we don’t need.

Please read below

Did you check those logs???

Yes, I did. As I already told, these are not serial console log from UART.

Serial console log from UART means the log from Jetson itself. What you provided are all host side log.

OK.

From above discription I have provided:

  • step with nvautoflash
  • current host side logs

Is there anything wrong ?

We need the device side log to see why flash gets failure. What you provided are just half the information.

This half information is not sufficient to check this error.

And we have this device under dev, I don’t have time to give you the uart log asap.

Since I have met this issue at least three times.

Is there any thing wrong with host side log and steps for nvautoflash from dev’s view?

Hi daniel2008_12,

per previous topic 312359 with r35.6.0, we’ve suggested using initrd script to flash external NVMe SSD.

Yes, it’s OK with initrd script as I used to do.

I just tried nvautoflash for r36.4.3, bad luck too.

nvautoflash.sh is just a wrapper of flash.sh.

Flash.sh cannot flash things to external drive. Only initrd flash can. Thus, nvautoflash won’t work on Orin NX and Orin Nano because these 2 by their nature only have external boot medium.

1 Like

Is there any build-in Flash module, such as SPI-Flash etc?

There is SPI-FLASH memory on the module itself, but it is just for bootloader software.
The file system is located on the external drive.

flash.sh can flash the bootloader software on the SPI flash but it cannot flash anything to the external storage.

1 Like