Jetson Orin Nano Flash Failure - no SSH after mid-flash restart

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

Hardware configuration is:
P3767-0005 with P3768-0000, no SD Card Installed, 4TB NVMe
OS L4T R36.4.3
When I use the SDK Manager or the following command line…
$ 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-super internal
…everything moves along until the script reaches the first reboot so it can finish the flash process. The module boots and the fan comes on, but on the host, then I get:
Waiting for target to boot-up…
Waiting for device to expose ssh …Waiting for device to expose ssh …Run command: flash on fc00:1:1:0::2
Device should have booted into initrd kernel now. However, the host cannot connect to its ssh server

HOWEVER if I use sudo flash.sh jetson-orin-devkit-nvme internal, flashing is successful, BUT when Ubuntu comes up, Chromium won’t install during the onboarding process, the desktop is lacking the app-dock, and the configuration for apt has an incorrect source information file. Also, everytime I reboot, the onboard process kicks in again.

I’ve tried other NVMe and I’ve used these NVMe modules on another Tegra devices successfully, so I am 100% certain it’s not the NVMe.

I’ve seen others with both of these issues, but it usually looks like people gave up and the topic got closed.
Any ideas as to what I’m doing wrong?

2

Looking through tools/kernel_flash/README_initrd_flash.txt …
In the example for “Flash an NVMe SSD and use APP partition on it as root filesystem” the command line given is:
sudo ADDITIONAL_DTB_OVERLAY_OPT=“BootOrderNvme.dtbo” --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_external.xml --showlogs jetson-xavier nvme0n1p1
…that’s wrong, correct?

To clarify my original query, I’m just trying to flash the kit using no SDCard, and a 4TB NVMe and the full R36.4.3 build.

3

I don’t consider this a solution, but I made progress by abandoning l4t_initrd_flash.sh – a friend suggested flash to SDCard using ./flash.sh jetson-orin-nano-devkit-super mmcblk0p1 (it was his only path to success) and I have a working kit now, but I would like to have it working with my 4TB NVMe rather than a 128Gig SDCard.

4

Hello @billrehbock,

Hope everything is going great!

Just out of curiosity, could you please try with the following 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-super-nvme.conf internal

Please let us know how it goes.

best regards,
Andrew
Embedded Software Engineer at ProventusNova

5

Hi Andrew, thanks for the suggestion. I am waiting for another Jetson Orin Nano DevKit to arrive and I will attempt your suggestion when it arrives. Now that I have one system working, I need to do some testing on that.

6

Hey @billrehbock,

Thanks for getting back.

Sounds like a good plan.
Keep us posted.

Also, don’t hesitate to reach back out if you encounter any further issues while testing.
We might be able to help.

best regards,
Andrew
Embedded Software Engineer at ProventusNova

7

I used SDK Manager to flash a NVMe SSD. Jetson Linux was flashed successfully, then, SDK Manager continued to flash Jetson Runtime Components was failed which stayed at 50.4%. My host pc had lost that connection with Orin Nano Super. The Orin Nano Super had been frozeen, not working.

When I re-boot Orin Nano Super, Power LED, Ethernet LEDs stayed on all the time, DP doesn’t output anything, USB-A are no response, Host PC cannot connect with Orin Nano Super via USB-C, Fan rotates twice(once about 10 seconds.).

Now, I cannot do anything on it. Has it been damaged?
My post:

1 Like