Timeout while flashing Orin Nx

[sy14]

Hello,

I am trying to flash the Orin NX using the following command which I found in the documentation and several other forum posts.

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 p3509-a02+p3767-0000 internal

However, the flashing process seems to timeout and I am getting the following error.

***************************************
*                                     *
*  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 device to expose ssh ......RTNETLINK answers: File exists
RTNETLINK answers: File exists
Waiting for device to expose ssh ...Run command: flash on fc00:1:1:0::2
SSH ready
mount.nfs: Connection timed out
Flash failure
Cleaning up...

Both Flash orin failed with Nvme and Flashing AGX Orin on NVMe JP5.0.2 do not help fix the issue. Any thoughts on what the issue could be? Thanks.

[WayneWWW]

First, tell us if you are using custom board.

Basically, analyzing such problem is all the same procedure as Flash orin failed with Nvme.

Replying my question first and I can tell what might happen here or I can share the next item to check.

[sy14]

Thanks @WayneWWW for the reply and your help. I did see that post but it looked like it was for the AGX and was not sure to the final solution. I am using this kit https://www.seeedstudio.com/reComputer-J4012-p-5586.html. I believe the carrier board is this one reComputer J401 Carrier Board for NVIDIA Jetson Orin NX/Nano module - Seeed Studio.

[WayneWWW]

Yes, then it is a custom board. Please contact with the board vendor for their customized BSP first because sdkmanager tool only supports devkit.

[KimHendrikse]

Does the flashing process from the SDK manager change anything on the module itself? (Such as doing something to aid the uefi boot process)

Because if it does not, then the flashing process is just changing data on disk and for systems that boot from nvme or last did before they require reflash it seems to me that an alternative installation approach could be adopted that just requires writing to disk partitions for those that get stuck.

Kim Hendrikse

[WayneWWW]

Hi,

It is a complicated one to explain.

If you ever use any of the previous platform which has internal emmc, for example, Orin AGX. And flash with “flash.sh” tool, what you said is correct for such platform.

But for any attempt to flash external drive, it is initrd flash tool instead. And this tool will take the device tree as input before flashing. The flash process from this tool is different from flash.sh. It will flash the bootloader software into QSPI flash on the board first with traditional flash.sh. Then, it will boot into initrd, initrd will then flash the data to the external drive.

So, the problem comes. If your custom board disable or change anything which is different from default setting, then flash process may not work.

For example, if your custom board does not have micro usb enabled for device mode, which is needed for the flash process here, then this flash will fail.

Also, another example, if the custom board does not use same PCIe design as devkit, then default setting may not work either.

[sy14]

Just wanted to give an update as I was able to successfully flash the Orin NX in the reComputer J401 Carrier Board for NVIDIA Jetson Orin NX/Nano module - Seeed Studio

My problem was that I was using an Ubuntu 22.04 machine to do the flashing which seems to not work with the initrd flashing. I was previously using the flash.sh script to flash the AGX Orin Dev Kit on Ubuntu 22.04 without any issues. After switching to an Ubuntu 20.04 machine the flashing of the Orin NX worked without any issues.

The RT patches are working on the Orin NX as well.

Linux nx 5.10.104-rt63-tegra #1 SMP PREEMPT RT Wed Mar 29 13:16:13 CDT 2023 aarch64 aarch64 aarch64 GNU/Linux

Thanks again for the help!

[sy14]

Another update. Being determined to be able to flash from an Ubuntu 22.04 machine I started digging into the scripts to see what they were actually doing.

It turns out the actual problem causing the mount.nfs: Connection timed out error was not the fact I was using Ubuntu 22.04, but rather just that the firewall was enabled and seems to be blocking the mounting of NFS needed for flashing. I disabled the firewall and the flashing worked from an Ubuntu 22.04 machine.

Hope this helps.