U-Boot UEFI fails on ls1046afrwy

[nodeh]

Here is a U-Boot console trace

NOTICE: Fixed DDR on board

NOTICE: 4 GB DDR4, 64-bit, CL=15, ECC on
NOTICE: BL2: v1.5(release):LSDK-20.04-update-290520
NOTICE: BL2: Built : 13:52:31, May 18 2020
NOTICE: INITIALIZING SEC
NOTICE: Verifying RSA
NOTICE: ROTPK is not deployed on platform. Skipping ROTPK verification.
NOTICE: Verifying RSA
NOTICE: ROTPK is not deployed on platform. Skipping ROTPK verification.
NOTICE: Verifying RSA
NOTICE: ROTPK is not deployed on platform. Skipping ROTPK verification.
NOTICE: BL31: v1.5(release):LSDK-20.04-update-290520
NOTICE: BL31: Built : 13:52:31, May 18 2020
NOTICE: Welcome to LS1046 BL31 Phase

U-Boot 2021.01+fsl+gc4fddedc48 (Jan 11 2021 - 18:11:43 +0000)

SoC: LS1046AE Rev1.0 (0x87070010)
Clock Configuration:
CPU0(A72):1600 MHz CPU1(A72):1600 MHz CPU2(A72):1600 MHz
CPU3(A72):1600 MHz
Bus: 600 MHz DDR: 2100 MT/s FMAN: 700 MHz
Reset Configuration Word (RCW):
00000000: 0c150010 0e000000 00000000 00000000
00000010: 30400506 00800012 60040000 c1000000
00000020: 00000000 00000000 00000000 00038800
00000030: 20044100 24003101 00000096 00000001
Model: LS1046A FRWY Board
Board: LS1046AFRWY, Rev: B, boot from SD
SD1_CLK1 = 100.00MHZ, SD1_CLK2 = 100.00MHZ
DRAM: 3.9 GiB (DDR4, 64-bit, CL=15, ECC on)
SEC0: RNG instantiated
Using SERDES1 Protocol: 12352 (0x3040)
Using SERDES2 Protocol: 1286 (0x506)
NAND: 512 MiB
MMC: FSL_SDHC: 0
EEPROM: NXID v1
In: serial
Out: serial
Err: serial
Net:
MMC read: dev # 0, block # 18432, count 128 ...
Fman1: Uploading microcode version 108.4.9
FM1@DTSEC1, FM1@DTSEC5, FM1@DTSEC6, FM1@DTSEC10
Hit any key to stop autoboot: 0
=> printenv -e
Scanning disk esdhc@1560000.blk...
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
** Unrecognized filesystem type **
Found 14 disks
PlatformLang:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
NV|BS|RT, DataSize = 0x6
00000000: 65 6e 2d 55 53 00 en-US.
Boot0001:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
NV|BS|RT, DataSize = 0x8c
00000000: 01 00 00 00 7e 00 4d 00 4d 00 43 00 00 00 01 04 ....~.M.M.C.....
00000010: 14 00 b9 73 1d e6 84 a3 cc 4a ae ab 82 e8 28 f3 ...s.....J....(.
00000020: 62 8b 03 1a 05 00 00 03 1a 05 00 00 04 01 2a 00 b.............*.
00000030: 01 00 00 00 00 00 02 00 00 00 00 00 00 08 00 00 ................
00000040: 00 00 00 00 c6 df 51 b4 00 00 00 00 00 00 00 00 ......Q.........
00000050: 00 00 00 00 01 01 04 04 32 00 5c 00 45 00 46 00 ........2.\.E.F.
00000060: 49 00 5c 00 42 00 4f 00 4f 00 54 00 5c 00 62 00 I.\.B.O.O.T.\.b.
00000070: 6f 00 6f 00 74 00 61 00 61 00 36 00 34 00 2e 00 o.o.t.a.a.6.4...
00000080: 65 00 66 00 69 00 00 00 7f ff 04 00 e.f.i.......
BootOrder:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
NV|BS|RT, DataSize = 0x2
00000000: 01 00 ..
SecureBoot:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x1
00000000: 00 .
SetupMode:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x1
00000000: 01 .
AuditMode:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x1
00000000: 00 .
DeployedMode:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x1
00000000: 00 .
VendorKeys:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x1
00000000: 00 .
PlatformLangCodes:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x6
00000000: 65 6e 2d 55 53 00 en-US.
OsIndicationsSupported:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x8
00000000: 00 00 00 00 00 00 00 00 ........
SignatureSupport:
8be4df61-93ca-11d2-aa0d-00e098032b8c EFI_GLOBAL_VARIABLE_GUID
BS|RT|RO, DataSize = 0x20
00000000: 26 16 c4 c1 4c 50 92 40 ac a9 41 f9 36 93 43 28 &...LP.@..A.6.C(
00000010: a1 59 c0 a5 e4 94 a7 4a 87 b5 ab 15 5c 2b f0 72 .Y.....J....\+.r
=> mmc read 0x85000000 7800 400

MMC read: dev # 0, block # 30720, count 1024 ... 1024 blocks read: OK
=> fdt addr 0x85000000
=> bootefi bootmgr 0x85000000
Cannot use 64 bit addresses with SDMA
Invalid DOS Signature
Loading Boot0001 'MMC' failed
EFI boot manager: Cannot load any image
=>

(The unrecognised filesystem types are squashfs - not relevant to this, as the first partition is FAT/EFI)

However, I can do:

=> fatload mmc 0:1 0x84000000 efi/boot/bootaa64.efi
193272 bytes read in 31 ms (5.9 MiB/s)
=>

So this issue is specific to U-Boot's UEFI implementation for that board, as U-Boot works OK with non-UEFI functionality.

I have added extra config items to the defconfig for that board:

CONFIG_CMD_BOOTEFI_HELLO=y
CONFIG_CMD_BOOTEFI_SELFTEST=y
CONFIG_CMD_ENV_FLAGS=y
CONFIG_CMD_NVEDIT_EFI=y
CONFIG_CMD_NVEDIT_INFO=y
CONFIG_CMD_NVEDIT_LOAD=y
CONFIG_CMD_EFIDEBUG=y
CONFIG_EFI_LOADER_BOUNCE_BUFFER=y
CONFIG_PARTITION_TYPE_GUID=y
CONFIG_EFI_SECURE_BOOT=y
# CONFIG_EFI_VARIABLES_PRESEED is not set
# EFI_VAR_SEED_FILE is not set

We know that the chip itself cannot to DMA to addresses above the 4GB 32-bit threshold, and setting CONFIG_EFI_LOADER_BOUNCE_BUFFER should fix that, but it doesn't.

[nodeh]

Yes, I did that and it didn't work.

[nodeh]

I am not doing UEFI instead of U-Boot. I am doing UEFI from U-Boot. I am using a U-Boot config.

[Pavel]

This configuration is not supported in LSDK 2012. See message below on the following command:

flex-builder -i mkfw -m ls1046afrwy -b sd -B uefi

INSTRUCTION: mkfw

MACHINE: ls1046afrwy

BOOTTYPE: sd

BUILDARG: uefi

uefi_sdboot on ls1046afrwy: unsupported!

[Pavel]

See the following pages for your problem:

https://www.linaro.org/blog/enabling-uefi-secure-boot-on-u-boot/

https://u-boot.readthedocs.io/en/stable/uefi/uefi.html