Open yrzr opened 1 year ago
The legend says:
Amicus Lumiae, [11/17/22 7:53 PM] https://t.me/UEFIonRockchip/545
It seems like Rockchip's plan was originally to go with a full featured build of uboot for SystemReady compliance, before realizing uboot's UEFI implementation is too immature for that
Amicus Lumiae, [11/17/22 7:54 PM] https://t.me/UEFIonRockchip/546
So they crippled uboot in compile-time configuration, and pivoted to edk2 for SystemReady
So I'd assume bootefi
is currently broken in the source code and is unlikely to be fixed by Rockchip.
The above comment is not from Rockchip, but community speculation based on publicly available source code.
As said above Rockchip is working on a EDK2 implementation for UEFI boot though.
This seems to work fine on rockpro64-rk3399
Perhaps the bug was fixed, or this is specific to rk3388 ?
I think this is specific to RK3588. However, we are closely following upstream U-Boot development, and we are looking to use that for our RK3588 based products later on. Upstream U-Boot should not have this issue.
You are right. With upstream:
=> bootefi hello
Card did not respond to voltage select! : -110
Booting /MemoryMapped(0x0,0xeff94d70,0x31b0)
Hello, world!
Running on UEFI 2.10
Have SMBIOS table
Have device tree
Load options:
How far away is your downstream tree from upstream?
Further than a galaxy far, far away. Once upstream U-Boot is good for our use case we will fully switch to it instead of backporting parts of it to Rockchip U-Boot.
I enabled
CMD_BOOTEFI
in u-boot config:build and write the u-boot into sdcard:
try to boot efi with command
bootefi hello
:ERROR occurs, and the u-boot cannot boot efi.
Any idea how to solve the problem?