Orin NX flashing fails non-qspi storage

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

Hey all,

I am having issues with flashing an Orin NX on Xavier NX devkit carrierboard with version 35.3.1
I went up from 35.2.1 to 35.3.1 and this breaks the flashing process.
I am using this flash command
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 p3509-a02+p3767-0000 internal for an Orin NX with nvidia devkit and 500GB nvme ssd
On 35.2.1 no issues, when I am using 35.3.1 It gets stuck on the last step (3) and hangs and then stops.
Logs of 35.2.1
Flashing35.2.1 (248.8 KB)
Logs of 35.3.1
Flashing35.3.1 (261.6 KB)
I am using these steps:
https://docs.nvidia.com/jetson/archives/r35.2.1/DeveloperGuide/text/IN/QuickStart.html#to-flash-the-jetson-developer-kit-operating-software

What would be the issue?

2

You may refer to the R35.3.1 document to see if can help.
Please note, we don’t support that combination(Orin NX on Xavier NX devkit carrierboard) anymore once we have Orin Nano carrier board.

3

But it should still work currently. What changed in R35.3.1 that causes this issue? And how can I resolve it?

Could this be the issue?
3941437 If a Jetson device does not have Internet access by using a connected LAN
cable, the OEM configuration screen will take about 4 minutes to display at first
boot.
We suggest that you connect the LAN cable with Internet access to the Jetson
device at first boot, which will shorten the waiting time for the OEM configuration
screen.

4

I have tried reflashing with ethernet connected, no succes

5

Is there a fix for this?

7

What do you get from UART?
Can you try 35.4.1 to see if it works?

9

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