Stock Image with SB don't detect the SSD

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

Hi,

I want to deploy and image using secure boot on the nano devkit using an orin nx module on 35.6.2. It works well on the xavier devkit, agx orin devkit or our own carrier board but on the nano devkit don’t detect the SSD and then swith to network boot. Without secure boot, it works without problem though.

I am using the following commands:

// Deploy the environment
tar xpf Jetson_Linux_R35.6.2_aarch64.tbz2
tar xpf ota_tools_R35.6.1_aarch64.tbz2
cd Linux_for_Tegra/rootfs
sudo tar xpf ../../Tegra_Linux_Sample-Root-Filesystem_R35.6.2_aarch64.tbz2
cd ..
sudo ./apply_binaries.sh

// Create internal image
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --no-flash --network usb0 -u pkc.pem -v sbk.key --uefi-keys uefi/uefi_keys.conf --uefi-enc sym.key jetson-orin-nano-devkit-nvme internal

// Create External image
sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml --external-only --append --network usb0 -u pkc.pem -v sbk.key --uefi-keys uefi/uefi_keys.conf --uefi-enc sym.key jetson-orin-nano-devkit-nvme external

// Flash the image
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --network usb0 --flash-only

Is jetson-orin-nano-devkit-nvme the right target in my setup?
Is there some limitation that prevent to boot with SSD when SB is enabled on the nano devkit?

Can you provide some insight why it works on all other devkit and custom board but not on the nano devkit? Is there some specific steps to be involved?

Can you confirm this is supported?

Thanks

5

Hi sebastien.schertenleib,

Please use jetson-orin-nano-devkit as board config instead of jetson-orin-nano-devkit-nvme.

Please share the full logs when you flash the board and also the serial console log during boot.

6

Hi Kevin,

I tried with jetson-orin-nano-devkit as board config but the same problem occurs. Please find in attachment the full log.

Thanks

nanodevkit.log (212.2 KB)

flashnano.txt (45.4 KB)

7

From the serial console log you shared, it seems booting into UEFI and stuck before the reset triggered.

The flash log looks good to me that you have enabled rootfs a/b in your case.

Could you also add ROOTFS_AB=1 to the first command to create internal image?
and also BootOrderNvme.dtbo for the second command to create external image.

// Create internal image
sudo ROOTFS_AB=1 ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs -p “-c bootloader/t186ref/cfg/flash_t234_qspi.xml” --no-flash --network usb0 -u pkc.pem -v sbk.key --uefi-keys uefi/uefi_keys.conf --uefi-enc sym.key jetson-orin-nano-devkit internal

// Create External image
sudo ROOTFS_AB=1 ADDITIONAL_DTB_OVERLAY_OPT="BootOrderNvme.dtbo" ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --no-flash --external-device nvme0n1p1 -c ./tools/kernel_flash/flash_l4t_nvme_rootfs_ab.xml --external-only --append --network usb0 -u pkc.pem -v sbk.key --uefi-keys uefi/uefi_keys.conf --uefi-enc sym.key jetson-orin-nano-devkit external

// Flash the image
sudo ./tools/kernel_flash/l4t_initrd_flash.sh --showlogs --network usb0 --flash-only
8

Hi Kevin,

Thanks for the investigation and tips. I will try and let you know the outcome.

Thanks again.

9

Hi Kevin,

Alas, using the above commands trigger the same issue. Do you have other suggestion I may try?

Can you confirm that using an orin nx on the nano devkit with SB + FDE on 35.6.2. is supported?

Thanks

10

We’ve verified them on the devkit. I have to double-confirm the release with internal team.

As you said it is working on the AGX Orin devkit, could you also share the full flash log and the serial console log in this case?

11

Hi Kevin,

Please find the log for the AGX Orin.

Thanks

agx.log (43.0 KB)

agx.boot.log (93.2 KB)

13

Hi Kevin,

Were you able to check the provided logs? Did you spot something strange?

Thanks

14

These logs look good to me.

For NVMe not detected issue on Orin Nano, could you help to clarify if the issue is specific to one or multiple NVMe SSD?

Please also help to provide the log with UEFI debug messages enabled to check if there might be further clues.