OrinNx flash JP5.1.2 ok，setup fail

Robotics & Edge Computing Jetson Systems Jetson Orin NX
1

9c31c999959905805180a66594c18548
9c31c999959905805180a66594c185481080×1920 160 KB

cd workspace
tar xvf Jetson_Linux_R35.4.1_aarch64.tbz2
sudo tar xvpf Tegra_Linux_Sample-Root-Filesystem_R35.4.1_aarch64.tbz2 -C Linux_for_Tegra/rootfs/
cd Linux_for_Tegra/
sudo ./apply_binaries.sh
sudo ./tools/l4t_flash_prerequisites.sh

flash cmd：

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 jetson-orin-nano-devkit internal

Previously, the device could successfully boot up after a factory reset. However, after a new factory reset (and the reset was successful), the device failed to boot up and kept getting stuck on this screen.

2

*** Please note that this reply is generated by LLM automatically ***

The issue you’re experiencing with your Jetson Orin NX device failing to boot up after a factory reset could be related to the boot flow or the partition configuration. Let’s break down the boot flow for the Jetson Orin NX and compare it with the Jetson AGX Orin to identify potential differences.

Jetson AGX Orin Boot Flow:

  1. BootROM
  2. PSCROM
  3. MB1
  4. MB2 (includes MB2 Applet and MB2)
  5. UEFI

Jetson Xavier NX and Jetson AGX Xavier Boot Flow:

  1. BootROM
  2. Bootloader Components (includes Common Driver Framework and Microboot1)
  3. TegraBoot (includes TegraBoot-BPMP and TegraBoot-CPU)
  4. UEFI

Comparing the two boot flows, we can see that the Jetson Orin NX uses a different bootloader component (TegraBoot) compared to the Jetson AGX Orin (MB2). This could potentially cause issues if the bootloader is not properly configured or if there are compatibility issues with the new factory reset.

Partition Configuration:

The partition configuration for the Jetson Orin NX is also different from the Jetson AGX Orin. The Jetson Orin NX uses an external storage device partition (nvme0n1p1) for the root file system, whereas the Jetson AGX Orin uses the internal storage (mmcblk0p1).

To troubleshoot the issue, you can try the following:

  1. Verify that the bootloader is properly configured and that the partition configuration is correct.
  2. Check the boot logs to see if there are any error messages that can help identify the issue.
  3. Try flashing the device again using the flash.sh script, but this time use the --no-flash option to only update the bootloader and not the root file system.
  4. If the issue persists, try using a different bootloader configuration or partition layout to see if that resolves the issue.

Command Comparison:

The commands you provided for flashing the Jetson AGX Orin and Jetson Orin NX are different. The Jetson AGX Orin uses the flash.sh script with the ROOTFS_ENC=1 option, whereas the Jetson Orin NX uses the l4t_initrd_flash.sh script with the --external-device option.

Here are the commands again for comparison:

Jetson AGX Orin:

sudo ROOTFS_ENC=1 ./flash.sh -i "./ekb.key" jetson-agx-orin-devkit mmcblk0p1

Jetson Orin NX:

sudo ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --showlogs -p "-c bootloader/generic/cfg/flash_t234_qspi.xml" -i ./ekb.key --no-flash jetson-orin-nano-devkit internal
sudo ROOTFS_ENC=1 ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --showlogs --no-flash --external-device nvme0n1p1 -S 16GiB -c ./tools/kernel_flash/flash_l4t_t234_nvme_rootfs_enc.xml --external-only --append -i ./ekb.key jetson-orin-nano-devkit external
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --network usb0 --showlogs --flash-only

Note that the Jetson Orin NX commands use the --external-device option to specify the external storage device partition (nvme0n1p1), whereas the Jetson AGX Orin command uses the mmcblk0p1 partition.

I hope this helps you identify and resolve the issue with your Jetson Orin NX device.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

Hi,

Please try below commands instaed.

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

Thanks