Orin nano UEFI开机屏幕显示L4TLauncher: Attempting Direct Boot无法关闭

Robotics & Edge Computing Jetson Systems Jetson Orin Nano
1

开发板：orin nano4G 开发套件

固件：r35.6.2

参考：UEFI Adaptation — NVIDIA Jetson Linux Developer Guide 1 documentation
UEFI源码拉取：edkrepo clone nvidia-uefi NVIDIA-Platforms r35.6.3

修改内容：L4TLauncher.c文件中删除了 DEBUG ((DEBUG_INFO, “%a: Attempting Direct Boot\r\n”, _FUNCTION_));。

编译：./edk2-nvidia/Platform/NVIDIA/Jetson/build.sh

文件替换：cp images/uefi_Jetson_RELEASE.bin \

/home/ys/nvidia/35.6.2/Linux_for_Tegra/bootloader/uefi_jetson.bin
刷机指令：sudo ./flash.sh -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvme0n1p1

最终结果：开机屏幕上还是显示L4TLauncher: Attempting Direct Boot。

Orinnx reboot repeatly but it switch to B unexpectly
2

*** Please note that this reply is generated by LLM automatically ***

The provided context does not contain information about the “Jetson Orin Nano orin nano4G r3562 UEFI Adaptation NVIDIA Jetson Linux Developer Guide 1 documentation.” However, I can provide some general information about the Jetson Orin Nano and its documentation.

The Jetson Orin Nano is a system-on-module (SOM) developed by NVIDIA, which is part of the Jetson Orin series. It is designed for edge AI and robotics applications, offering high performance and low power consumption.

The NVIDIA Jetson Linux Developer Guide is a comprehensive documentation that provides information on developing and deploying applications on the Jetson platform, including the Jetson Orin Nano. The guide covers topics such as:

  • Setting up the development environment
  • Building and flashing the operating system
  • Developing and deploying applications
  • Optimizing performance and power consumption

The guide is available on the NVIDIA website, and it is regularly updated to reflect changes and improvements in the Jetson platform.

Regarding the “r3562” and “UEFI Adaptation” mentioned in the question, it is likely that these refer to specific versions or configurations of the Jetson Orin Nano. However, without more information, it is difficult to provide a detailed answer.

In comparison to other Jetson modules, the Jetson Orin Nano offers a unique combination of performance, power efficiency, and size. It is designed to be used in a variety of applications, including robotics, autonomous vehicles, and smart cities.

Here is a summary of the key features of the Jetson Orin Nano:

  • NVIDIA Ampere GPU architecture
  • Up to 8 GB of LPDDR5 memory
  • Up to 128 GB of eMMC storage
  • Support for USB 3.2, PCIe, and Gigabit Ethernet
  • Operating temperature range: -20°C to 80°C
  • Size: 87 mm x 37 mm x 6 mm

Overall, the Jetson Orin Nano is a powerful and versatile module that is well-suited for a wide range of edge AI and robotics applications.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

3

你的回答不正确！

5

Hi,

Please try to do To flash only QSPI on Jetson Orin series:

Thanks

6

我尝试过使用sudo ./flash.sh -k A_cpu-bootloader -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvme0n1p1
sudo ./flash.sh -k B_cpu-bootloader -c bootloader/t186ref/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit nvme0n1p1

问题依旧存在

7

Hi,

We suggest to full flash the qspi partition.

$ sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml <board> <rootdev>

Thanks

8

感谢您的回复！
请问这个指令就可以了吗？sudo ./flash.sh -c bootloader/t186ref/cfg/flash_t234_qspi.xml --no-systemimg jetson-orin-nano-devkit nvme0n1p1

9

Hi,

Please try

$ sudo ./flash.sh --no-systemimg -c bootloader/generic/cfg/flash_t234_qspi.xml jetson-orin-nano-devkit internal

Thanks

10

1.2017 ] Retrieving EEPROM data
[ 1.2018 ] tegrarcm_v2 --oem platformdetails eeprom cvm /home/ys/nvidia/35.6.2/Linux_for_Tegra/bootloader/cvm.bin --chip 0x23 0
[ 1.2040 ] MB2 Applet version 01.00.0000
[ 1.2602 ] Saved platform info in /home/ys/nvidia/35.6.2/Linux_for_Tegra/bootloader/cvm.bin
[ 1.3539 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 1.3553 ] MB2 Applet version 01.00.0000
[ 1.4163 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 1.4180 ] MB2 Applet version 01.00.0000
[ 1.4697 ] Dumping customer Info
[ 1.4714 ] tegrarcm_v2 --chip 0x23 0 --oem dump bct tmp.bct
[ 1.4730 ] MB2 Applet version 01.00.0000
[ 1.5323 ] Saved bct in tmp.bct
[ 1.5924 ] tegrabct_v2 --brbct tmp.bct --chip 0x23 0 --custinfo /home/ys/nvidia/35.6.2/Linux_for_Tegra/bootloader/custinfo_out.bin
[ 1.5939 ] C[ 1.5957 ] ustomer data saved in /home/ys/nvidia/35.6.2/Linux_for_Tegra/bootloader/custinfo_out.bin successfully
[ 1.5959 ] Rebooting to recovery mode
[ 1.5982 ] tegrarcm_v2 --chip 0x23 0 --ismb2
[ 1.6550 ] tegrarcm_v2 --chip 0x23 0 --ismb2applet
[ 1.6565 ] MB2 Applet version 01.00.0000
[ 1.7151 ] Booting to recovery mode
[ 1.7171 ] tegrarcm_v2 --chip 0x23 0 --reboot recovery
[ 1.7190 ] MB2 Applet version 01.00.0000
Board ID(3767) version(301) sku(0004) revision(G.1)
Chip SKU(00:00:00:D6) ramcode(5) fuselevel(fuselevel_production) board_FAB(301)
emc_opt_disable_fuse:(0)
Error: missing cfgfile ().

Usage: sudo ./flash.sh [options] t186ref internal
options:
-c ---------- Flash partition table config file.
-d ---------- device tree file.
-f --------- Path to flash application (tegraflash.py)
-h -------------------- print this message.
-i – key for disk encryption support.
-k ----- partition name or number specified in flash.cfg.
-m ------ MTS preboot such as mts_preboot_si.
-n --------- Static nfs network assignments
:::
-o ---------- ODM data.
-r -------------------- skip building and reuse existing system.img.
-t -------- tegraboot binary such as nvtboot.bin
-u ------ PKC key used for odm fused board.
-v ------ Secure Boot Key (SBK) key used for ODM fused board.
-w ---------- warm boot binary such as nvtbootwb0.bin
-x ---------- Tegra CHIPID.
-B ---------- BoardId.
-C ---------- Kernel commandline arguments.
WARNING:
Each option in this kernel commandline gets
higher preference over the values set by
flash.sh. In case of NFS booting, this script
adds NFS booting related arguments, if -i option
is omitted.
-F ---------- Flash server such as cboot.bin.
-G -------- Read partition and save image to file.
-I ----------- initrd file. Null initrd is default.
-K ----------- Kernel image file such as zImage or Image.
-L ------- Bootloader such as cboot.bin or u-boot-dtb.bin.
-M --------- MTS boot file such as mts_si.
-N ---------- i.e. :/my/exported/nfs/rootfs.
-R ------- Sample rootfs directory.
-S ------------- Rootfs size in bytes. Valid only for internal
rootdev. KiB, MiB, GiB short hands are allowed,
for example, 1GiB means 1024 * 1024 * 1024 bytes.
-T —The number of the sectors of the external storage device.
The default value is 122159104 if this option is not set.
-Z -------------------- Print configurations and then exit.
–no-flash ------------ perform all steps except physically flashing the board.
This will create a system.img.
–external-device------ Generate flash images for external devices
–sparseupdate--------- only flash partitions that have changed. Currently only support SPI flash memory
–no-systemimg -------- Do not create or re-create system.img.
–bup ----------------- Generate bootloader update payload(BUP).
–single-image-bup Generate specified single image BUP, this must work with --bup.
–bup-type ----- Generate specific type bootloader update payload(BUP), such as bl or kernel.
–multi-spec----------- Enable support for building multi-spec BUP.
–clean-up------------- Clean up BUP buffer when multi-spec is enabled.
–usb-instance — Specify the USB instance to connect to;
= USB port path (e.g. 3-14).
–no-root-check ------- Typical usage of this script require root permissions.
Pass this option to allow running the script as a
regular user, in which case only specific combinations
of command-line options will be functional.
–uefi-keys <keys_conf> Specify UEFI keys configuration file.
–rcm-boot ------------ Do RCM boot instead of physically flashing the board.
–sign ---------------- Sign images and store them under “bootloader/signed”
directory. The board will not be physically flashed.
–image --------------- Specify the image to be written into board.
–boot-chain-flash Flash only a specific boot chain (ex. "A, “B”, “all”).
Defaults to “all”, inputs are case insensitive.
Not suitable for production.
–boot-chain-select Specify booting chain (ex. “A” or “B”) after the board is flashed.
Defaults to “A”, inputs are case insensitive.
–pv-crt -------------- The certificate for the key that is used to sign cpu_bootloader
–with-systemimg ------ Generate system images also when using -k option
–pv-enc <enc_key>----- The encryption key that is used to encrypt cpu_bootloader.
–uefi-enc <uefi_enc_key> Key file (0x19: 16-byte; 0x23: 32-byte) to encrypt UEFI payloads
–uda-dir-------------- Directory to store user data that will be encrypted in UDA partition.
–separate-rcmboot-binary ------ Enable use of different binaries for rcmboot and coldboot.
–generic-passphrase – Use generic passphrase for disk encryption.
–disable-random-iv — Disable generation of random IV, SALT1, SALT2 and DERSTR.
–read-info ----------- Read and display board related info, fuse info (based on fuse_t234.xml),
and EEPROM content.
–reuse-uuid --------- Reuse uuid which is already generated first time.
–debug -------------- Enable debug mode.
For now, the debug mode will enable saving of unencrypted and unsigned files
for UEFI encryption/signing debugging.

ys@ubuntu:~/nvidia/35.6.2/Linux_for_Tegra$

这个指令不行

11

Hi,

We verified that the commands work on our Orin Nano Developer Kit using the official BSP and rootfs from Jetson Linux Release 36.4.4 | NVIDIA Developer.

Please make sure you follow the Quick Start — NVIDIA Jetson Linux Developer Guide to setup your bsp.

Thanks

12

我是使用的是35.6.2版本的bsp和rootfs。开发板使用orin nano4GB 套件。

26

我是使用的是35.6.2版本的bsp和rootfs。开发板使用orin nano4GB 套件。

27

Hi,

Similar commands referred in


sudo ./flash.sh --no-systemimg -c  bootloader/t186ref/cfg/flash_t234_qspi.xml  jetson-orin-nano-devkit internal

Thanks

28

我使用这个指令刷机了，但是屏幕上任然有L4TLauncher: Attempting Direct Boot。
需要提供那些信息，方便你能帮助我排查？

31

您好！在吗？我这个问题处理不了吗？

32

Hi,

We will set up the device and follow your steps to verify whether the issue occurs. This may take some time, and we will update you once the process is complete.

Thanks

33

好的 谢谢！静候你们的消息！

34

你好！请问这边有验证完吗？有解决办法了吗？

35

您好！请问这个问题怎么解决？

37

Sorry for the late response.
Is this still an issue to support? Any result can be shared?