Orin Nano - SD Card does not boot when in a new Module

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

I obtained a second Jetson Orin Nano setup, featuring 36.4.3 firmware (board 2).

My first setup was already upgraded to 36.4.4 firmware and runs from SD Card (board 1).

I did not have second card available right now, so I took the SD card from the working board 1 and inserted it into the board 2. To my surprize the SD card would not boot at all on the board 2, telling “attempting recovery” at UEFI screen, then displaying blank screen with blinking cursor.

Please explain what happens? I expected the SD card to boot the new device, is it broken then?

6

Hi,

Please provide the serial log when you boot board2 with sd card.

Thanks

7

Thanks for reply, my USB to serial cable arrived today and I started debugging.

Well, I ran impatient before, and I bought two 64 GB cards yesterday and started experimenting.
I programmed one with JetPack 6.2.1 (sd-blob.img) and it did not boot - let us call it JP6 for short.
I programmed another SD Card with JetPack 5.1.3 (sd-blob.img) and it did not boot - let us call it JP5 for short.
I did not do more tries, may be I should…

Now, the magic happened when I connected the USB to serial today, first I booted Jetson when I still had my JP5 card installed, I got

L4TLauncher: Attempting Direct Boot
EFI stub: Booting Linux Kernel...
EFI stub: ERROR: Invalid header detected on UEFI supplied FDT, ignoring ...
EFI stub: Generating empty DTB
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services and installing virtual address map...

then the device stopped responding, needed poweroff

Next, I removed JP5 and inserted JP6 card and powered on, I got Linux booting until this point:

[    9.849807] pci 0008:00:00.0:   bridge window [io  0x300000-0x300fff]
[    9.849812] pci 0008:00:00.0:   bridge window [mem 0x3528000000-0x35280fffff]
[    9.849930] pcieport 0008:00:00.0: Adding to iommu group 8
[    9.850024] pcieport 0008:00:00.0: PME: Signaling with IRQ 189
[    9.850340] pcieport 0008:00:00.0: AER: enabled with IRQ 189
[   17.402398] ERROR: nvme1n1p1 not found

I see this both coming from UART and from HDMI screen

The Linux Terminal drops into “bash-5.1#“ recovery shell.

So obviously still somewhere is reference to nvme1n1p1…

Well, in my Jetson 1 device I have both M2. slots populated with SSDs, and seems this is the tripping point now, shall I update GRUB somehow to understand that the disks are not there?

8

I provided at least partial logs.

As I think of it further, the Linux boot log - even if it was recovery boot - was redirected to UART. Why so? At the same time the HDMI output just displays a blinking cursor. I think it could be improved somehow, by telling “check UART now, because it was selected as your boot output interface …“

The boot log in the UART told me that L4T was still trying to find boot device at nvme1n1p1 though it was placed at nvme0n1p1 in the new device… After patching the etc/fstab it boots now.

Secondly, can you please direct me to the L4T specific UEFI Boot Options documentation, I guess in my attempts to find the solution I messed the configuration somehow…
My conclusion though is that one does not necesserily need x86 Linux machine to make Jetson Orin boot from SSD, in fact on SD card or even another bootable SSD on the Jetson itself may be sufficient to get another Jetson up and running.

9

you can refer to Jetson AGX Orin, Orin NX and Orin Nano Boot Flow — NVIDIA Jetson Linux Developer Guide

11

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