Previously, it was reported [1] that
commit f3866909e350 ("distro_bootcmd: call EFI bootmgr even without having /EFI/boot")
introduced a regression for am335x_evm_defconfig (BeagleBone Black board). Namely, an attempt to execute EFI binary from USB mass storage device has been ending up with the following issue:
data abort pc : [<9ce0b6d0>] lr : [<9ffab7c7>] reloc pc : [<7d69d6d0>] lr : [<8083d7c7>] sp : 9df44e28 ip : 9ffdfe90 fp : 00000003 r10: 9ffe3300 r9 : 00000000 r8 : 9df6fe88 r7 : 00000000 r6 : 9ce5da08 r5 : 9ce571f8 r4 : 9ce2c040 r3 : 00000000 r2 : 00000001 r1 : 9ce56598 r0 : 00000000 Flags: NzCv IRQs off FIQs on Mode SVC_32 Code: e3500000 0a000015 e590000c eb00f96e (e5d03000) UEFI image [0x9ce46000:0x9cf28fff] '/efi\boot\bootarm.efi' Resetting CPU ...
This issue is always reproduced when U-boot is stored on MMC, loaded via UART, or USB RNDIS.
An attempt to fix this issue revealed a design issue in EFI subsystem [2], so unlikely the satisfactory fix will be proposed quickly.
In this patch we disable CMD_BOOTEFI_BOOTMGR which is enabled by default and never worked correctly for this board as a temporarly workaround for the issue.
Reference: https://lists.denx.de/pipermail/u-boot/2021-June/451486.html Reference: https://lists.denx.de/pipermail/u-boot/2021-June/452297.html Signed-off-by: Matwey V. Kornilov matwey.kornilov@gmail.com --- configs/am335x_evm_defconfig | 1 + 1 file changed, 1 insertion(+)
diff --git a/configs/am335x_evm_defconfig b/configs/am335x_evm_defconfig index ef8de5999e..c229b6acd6 100644 --- a/configs/am335x_evm_defconfig +++ b/configs/am335x_evm_defconfig @@ -91,3 +91,4 @@ CONFIG_WDT=y CONFIG_DYNAMIC_CRC_TABLE=y CONFIG_RSA=y CONFIG_LZO=y +# CONFIG_CMD_BOOTEFI_BOOTMGR is not set