修改L4TLauncher.c编译后烧录,但在UEFI启动时调用的不是修改后的L4TLauncher。详情如下:
此图是手动进入uefi shell下,调用FS0:L4TLauncher.efi的信息。
打印信息中可以看到修改后的日志”L4TLauncher: Attempting 11111111111111111”
表明UEFI确实已烧录,但并未调用新烧录的L4TLauncher。
编译指令:edk2-nvidia/Platform/NVIDIA/Tegra/build.sh --init-defconfig edk2-nvidia/Platform/NVIDIA/Tegra/DefConfigs/t26x_general.defconfig
替换文件:nvidia-uefi/images/uefi_t26x_general_DEBUG.bin > thor_l4t_bsp_sdk/bootloader/uefi_t26x_general.bin
烧录指令:sudo ./l4t_initrd_flash.sh --qspi-only jetson-agx-thor-ultron internal
(整包编译整包烧录都试过,依然会有以上问题)
Hi wanglingce,
Are you using the devkit or developing the custom Thor carrier board?
The L4TLauncher is included in BOOTAA64.efi which is stored in esp partition rather than UEFI binary(uefi_t26x_general.bin).
You can run the following command to build it.
$ edk2_docker edk2-nvidia/Platform/NVIDIA/L4TLauncher/build.sh
And please refer to the following steps to update it.
$ ls -al /dev/disk/by-partlabel|grep esp
lrwxrwxrwx 1 root root 15 Sep 3 05:34 esp -> ../../nvme0n1p6
lrwxrwxrwx 1 root root 16 Sep 3 05:34 esp_alt -> ../../nvme0n1p12
$ sudo mount /dev/nvme0n1p6 /mnt
$ cd /mnt/EFI/BOOT/
$ replace BOOTAA64.efi under /mnt/EFI/BOOT/
$ sudo reboot
OK,it’s worked. Thank you!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.


