Initrd flashing for Orin Nano Super Developer Kit

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

Hi,

I’m trying the initrd flash method for the Orin nano super developer kit and getting stuck at the “Waiting for target to boot-up…” step when trying to flash NVME. Here’s my process.

First I set up the SDK by unpacking Jetson_Linux_R36.4.0_aarch64.tbz2, then unpacking Tegra_Linux_Sample-Root-Filesystem_R36.4.0_aarch64.tbz2 to Linux_for_Tegra/rootfs. I ran apply_binaries.sh, then tools/l4t_create_default_user.sh.

Referring to this doc page, I ran the suggested default flashing command.

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

At this point, the target manages to boot its minimal system but the USB networking never comes up. lsusb on the host shows no NVIDIA devices when the target is in this state.

I attached the resulting logs from the host, and the UART port of the target.
host.log (285.2 KB)
target.log (81.9 KB)

Some other possibly relevant info:

  • The host is Ubuntu 24.04.
  • I disabled the host’s firewall, as I remember this script trying to use NFS in the past after rebooting the target.
  • I was encountering that USB timeout issue, so have USB autosuspend temporarily disabled (echo -1 > /sys/module/usbcore/parameters/autosuspend)
  • I tried the flash.sh method (sudo ./flash.sh jetson-orin-nano-devkit-nvme internal) as a debugging step, and it works, just no MAXN mode. I would satisfied with using this method if the MAXN mode can be made available there.
  • SD card slot is empty.

Thanks

3

Hi,

To configure the super mode, you need change the jetson-orin-nano-devkit to jetson-orin-nano-devkit-super.
Please refer to the quick start Jetson Orin Nano Developer Kit with Super Configuration (NVMe) section

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

Thanks

4

Hi, thanks for your quick reply.

Do I need to download something else to get that config? I downloaded the BSP from here .

I have only jetson-orin-nano-devkit-nvme.conf and jetson-orin-nano-devkit.conf, and if I run that flash command I get Error: Invalid target board - jetson-orin-nano-devkit-super.

5

Hi,

Sorry for inconvenience.
The BSP download will release at next release.
You could reach out the sdk manager to download super mode.
some instructions could follow this topic

Thanks

7

Do you have an estimate date for releasing the fix in the BSP?

8

Hi,

Please refer to the new release page.

Thanks

9

Thanks for the followup, just managed to get the 36.4.3 release flashed to NVMe with initrd method after trying different USB-C cables.

For posterity, if you’re having issues with initrd method this also seems to work, documented here:
sudo ./flash.sh jetson-orin-nano-devkit-super-nvme internal

One question, the command I used was

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

At the end I have external instead of internal. Is NVMe considered internal or external in this context? I have seen instructions (for older releases) written both ways.

10

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