Cannot flash older JP5.1.1 on brand new Orin NX modules

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

Hi Nvidia team,

Some customers asked me to ship them Orin NX based industrial computers with JP5.1.1. historically, I had no issue with that (we have been flashing them in 5.1.1 for a year), but with the latest batch of Orin NX modules I got, the flash fails with a

ERROR: might be timeout in USB write.
Error: Return value 3

You will find the flash logs below. My flash command is the following:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --external-device nvme0n1p1 \
        -c tools/kernel_flash/flash_l4t_external.xml -p "-c bootloader/t186ref/cfg/flash_t234_qspi.xml" \
        --showlogs --network usb0 p3768-0000+p3767-0000 internal

I know the flash directory is in good shape because I tried to flash an Orin NX module from an older batch and everything went fine. Also, for both tests I used the same setup: an Orin Nano devkit carrier board with the same SSD attached.

I also tried on other flash computer, all running Ubuntu 20.04 LTS, without success. I also tried multiple modules from new batches on several carrier board without success.

Also, I tried to only flash the QSPI, and it failed with the same message, I imagine the fail is always when we try to flash the QSPI anyway.

Is there something new on latest batches that would explain such behavior?

Thanks for your help.

error3.txt (257.1 KB)

3

Hi louis.guerlin
It seems like the custom board.
Are these custom boards your own design or purchased from a vendor?

4

Hi DavidLLL,

Thanks for your help, it is not a custom board, it is an official devkit.

I also tried with the command sudo ./flash.sh jetson-orin-nano-devkit-nvme nvme0n1p1 and the result is the same: all goes well with an older module and I get an error with the latest modules I received:

I also tried with and without the Overlay_PCN210361_PCN210100_r35.3.1.tbz2 patch and with and without setting the cvb_eeprom_read_size to 0 in bootloader/t186ref/BCT/tegra234-mb2-bct-misc-p3767-0000.dts, without success.

5

Just do this test first.

If you flash jetp5.1.4 on this module with this carrier board, will it pass or not?

1 Like
6

Did you try to disable usb autosuspend or using another USB port/cable?

sudo su
echo -1 > /sys/module/usbcore/parameters/autosuspend

7

This issue has nothing to do with usb autosuspend.

Only the error right after BR_CID log printed is related to usb auto suspend.

1 Like
8

I always setup my flash host like that, so as WayneWWW says, it is not the solution.

9

Hi Louis

Probably this is because of PCN209760.
You need an overlay for JetPack 5.1.1 from NVidia.

Kind regards

1 Like
10

Thanks Severin, this does sound like the kind of answer I would expect, I will try WayneWWW method nonetheless (flashing to 5.1.4 then to 5.1.1)

11

If your module can get flashed with jetpack5.1.4 then this module is fine.

And that will indicate you may need PCN overlay.

1 Like
12

I confirm I need a PCN overlay, the flash is a success with JP5.1.2. I will check with customer if I can make him update to a newer JP version.

If not, how shall I proceed to get the overlay?

13

please contact your local NV contact window for it.

14

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