AGX Orin Recovery Boot

Autonomous Machines Jetson & Embedded Systems Jetson AGX Orin
1

My board have got stuck to the recovery boot:
L4TLauncher: Attempting Recovery Boot
I have seen this way:
Hi, Please try below method and it will go back to direct Boot again. Press ESC to enter UEFI Menu, then choose Device Manager → NVIDIA Configuration → L4T Configuration → OS chain A status → (The value is Unbootable if UEFI attemps recovery kernel) choose Normal → Save and exit, reboot, UEFI will…

but my uefi is Jetson UEFI firmware (version 1.0-d7fb19b built on 2022-08-10T20:18:13-07:00),
the uefi have not that menu, how to boot the normal way?

3

Then the only thing you can do is to re-flash the bootloader partition.

sudo ./flash .sh -k A_cpu-bootloader jetson-agx-orin-devkit internal

4

I have reflashed the A_cpu-bootloader, but it doesn’t work.

5

What do you mean with it doesn't work?
If it still gets stuck after re-flashing the bootloader partition, maybe your rootfs or kernel is corrupted so it just cannot boot up.

6

It still int this bootmode:L4TLauncher: Attempting Recovery Boot,but the rootfs is ok in the Recovery Boot. I have mounted the rootfs in the bash console of Recovery Boot mode, and the /boot/image of rootfs is also ok.

7

Can you please re-flash again and put the flashing log here?
What L4T version are you using?

8

Jetson Linux 35.1

20231128141905
202311281419051920×1440 314 KB

20231128141927
202311281419271920×1440 272 KB

orin_startup.log (1.7 MB)

9

orin_uefi_flash.log (61.3 KB)

10

Hi,

Please check the following setting in UEFI menu:

Device Manager → NVIDIA Resource Configuration → L4T Boot Mode

If it shows Recovery Parition, change it back to Application Default or ExtLinux and reboot to see if it gets back to normal boot.

11

I have set Device Manager → NVIDIA Resource Configuration → L4T Boot Mode, the default value is Application Default, and I have changed to other mode, the same result.

12

Then I can only say please try a full re-flash.

13

** WARNING: Test Key is used. **

L4TLauncher: Attempting GRUB Boot
L4TLauncher: Attempting Direct Boot
L4T boot options
0: primary kernel
1: primary kernel
Press 0-1 to boot selection within 3.0 seconds.
Press any other key to boot default (Option: 0)
EFI stub: Booting Linux Kernel…
EFI stub: Using DTB from configuration table
///////////////////////////////////////////////////////////////////
the normal log above.
maybe grub is bad? which partion is grub in?

14

I think UEFI by default uses ExtLinux but not GRUB.
I don’t know how you configured it before.

15

I used the r35.1 jetson_uefi.bin, I haven’t change the config, the default boot mode is “Application Default”, and it show “L4TLauncher: Attempting GRUB Boot,L4TLauncher: Attempting Direct Boot”

16

ExtLinux.conf is also valid in this condition

17

What do you mean with OK and valid here?
Are you sure the setting really gets saved in UEFI?

18

when in the recovery boot, I mount rootfs and all relevant directory files in rootfs exist. In the extlinux.con, I have config LINUX /boot/Image, the md5sum is right,So rootfs is not damaged. After I made the changes, I restarted and checked again, so it must have been saved

19

I cannot say.
Please just try a whole re-flash.

20

This machine belongs to our customer, and we need to find the cause to prevent it from happening again next time.

21

I will check internally and get back to you later.
However, it’s still better if you can upgrade to a newer L4T release; 35.1 is a bit outdated now.