I debugged the hardware development board we designed, using Orin nano as the core board, but the following print appears after startup:
UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (EDK II, 0x00010000)
Mapping table
FS1: Alias(s):F1:
MemoryMapped(0xB,0x16E600000,0x16E8AFFFF)
FS0: Alias(s):F0:
Fv(49A79A15-8F69-4BE7-A30C-A172F44ABCE7)
Press ESC in 5 seconds to skip startup.nsh or any other key to continue.
Shell>
Then I found a similar answer on the forum( Jetson Orin Nano Boot Error - Encountering UEFI Interactive shell instead - Jetson & Embedded Systems / Jetson Orin Nano - NVIDIA Developer Forums). After I followed the forum reply, I found that the development board still could not start normally. I tried to press escape again, and the development board no longer responded to the key. It stopped after running to the above log. I tried to press F11 but did not respond.
The core board and SSD on the development board I debugged were removed from the NVIDIA standard development board I purchased and operated normally on the standard development board.
How to determine the boot item configuration of Orin nano? I want to configure boot from SSD or eMMC. I guess it may be an exception caused by the incorrect boot position of the board.
Hi:
The jetpack version I burned to SSD is 5.1.3.
I saw in the document that you can customize the boot mode here, but when my board starts up, pressing Esc on the boot prompt interface does not respond. Why is this? I should be able to modify the L4T Boot Mode to SSD or eMMC boot.
Orin NX/Nano modules don’t have eMMC any more, and there are also no SDIO signals any more on the slot. Only the devkit version of Orin Nano can boot from the SD card on the module. For production modules you always need an NVMe SSD.
Sorry for the late response.
Please follow the instructions provided in the Build UEFI guide to build the corresponding BSP version of UEFI.
After completing the build process, replace the file Linux_for_Tegra/bootloader/uefi_jetson.bin with uefi_Jetson_DEBUG.bin.
Once this is done, please attach the log again for further review