[AGX Thor / R38.4] Hard power-off always halts at UEFI Setup menu instead of auto-booting the OS

Hardware / software

  • NVIDIA Jetson AGX Thor T5000 on a custom carrier
  • L4T R38 (REVISION 4.0), UEFI firmware in the 38.x line
  • Boot device: internal NVMe SSD (Samsung 990 PRO), booting \EFI\BOOT\BOOTAA64.efi

Problem
When the board loses power abruptly (hard power-off / battery cut — from the board’s point of view an unexpected power loss), the next boot always stops at the UEFI Setup menu (Boot Manager / Boot Maintenance Manager / Device Manager / Continue / Reset). It waits there indefinitely and only proceeds to the OS after a human selects “Continue”. This happens on every hard power-off, not intermittently.

This blocks our use case: the device is battery powered and the battery can be cut at any time. Every such power cut must result in an unattended, automatic boot into the OS. Manual intervention at the UEFI menu is not acceptable.

Works vs. doesn’t

  • Normal reboot (sudo reboot) → boots straight into the OS, no Setup menu.
  • Hard power-off (abrupt power removal) → always halts at UEFI Setup, requires manual Continue.

Already tried (none solved it)

  1. efibootmgr: the SSD only had an {auto_created_boot_option} entry, so I registered a proper entry pointing to \EFI\BOOT\BOOTAA64.efi and set BootOrder to put the SSD entries first (e.g. 0004,0001), removing “Enter Setup” from the front. After a normal reboot BootCurrent correctly used the new entry, but the firmware re-appends the other entries (0000 Enter Setup, etc.) on every reboot, and a hard power-off still lands in Setup.
  2. UEFI menu → Device Manager → NVIDIA Configuration → Boot Configuration: set “Enable UEFI Quick Boot” = Enabled and “Add new devices to” = bottom. No effect.
  3. Auto boot time-out = 10s. On a normal boot the pre-boot screen auto-continues after the timeout, but once it has dropped into the Setup menu the timeout no longer applies — it waits for manual input.
  4. Disconnected ALL USB peripherals (cameras, USB audio, everything) and did a hard power-off — still halts at UEFI Setup. So it is not caused by a peripheral sending console/serial data during boot.

UEFI variables checked from the OS (all look normal)

  • L4TDefaultBootMode = 1 (default/normal)
  • BoardRecoveryBoot = 0 (not recovery)
  • OsIndications is not present (only OsIndicationsSupported exists)

So every OS-visible boot variable looks normal, yet a hard power-off still lands in the Setup menu. This suggests the Setup-halt is triggered by firmware-internal unclean-shutdown detection rather than by any boot variable I can control from the OS.

Questions

  1. Is there a UEFI variable or Boot Configuration setting that stops the board from entering the Setup menu after an unexpected power loss, so it auto-boots the default OS entry?
  2. Is “Simple UEFI” (single boot device, minimal BDS) the recommended approach for a battery-powered embedded deployment that must survive abrupt power cuts and always auto-boot? Any caveats for AGX Thor T5000 on a custom carrier?
  3. Is this a known behavior of the R38.x UEFI on Thor when it detects an unclean shutdown, and is there an official, non-destructive way to disable the “halt at Setup” fallback?

Any guidance on guaranteeing unattended auto-boot after a hard power-off would be greatly appreciated. Thanks.

Hi hs95.yoon,

Is the issue specific to your custom carrier board powered by the battery?
Would you reproduce the similar issue on the devkit when your cut the power?

Could you share the full serial console log with debug UEFI logs enabled?

Hi hs95.yoon

Could you also attach complete UEFI serial logs from both a successful warm reboot and a failing cold boot? We would like to check whether the NVMe is detected before UEFI tries to boot from it.

Could you also please check the following?

  1. Does the issue reproduce with other NVMe models?

  2. Does your bootloader include any customizations?

  3. In your build output, could you locate L4TConfiguration.dtbo, decompile it, and attach the resulting DTS file? We would like to check whether any UEFI or boot-order settings could be affecting the boot process.

Daniel Chaves
Embedded SW Engineer at RidgeRun
Contact us: support@ridgerun.com
Developers wiki: https://developer.ridgerun.com
Website: www.ridgerun.com