Re: KHADAS EDGE V booting hangs if I install UEFI instead of u-boot

Mark Millard <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Aug 5, 2025, at 21:46, Mario Marietto <[email protected]> wrote:

> . . .
> 
> https://github.com/andreiw/rk3399-edk2
> 
> does not talk about how to fill this partition at all.
> 
> . . .

Nor should the material about building RK3399_SDK_UEFI.img
also talk about the "efi esp" content, which is a separate
thing.

In:

Number  Start (sector)    End (sector)  Size       Code  Name
   1              64            8063   3.9 MiB     FFFF  loader1   <-- Rk3399Pkg/Tools/Bin/idbloader.bin
   2            8064            8191   64.0 KiB    FFFF  reserved1
   3            8192           16383   4.0 MiB     FFFF  reserved2
   4           16384           24575   4.0 MiB     FFFF  loader2   <-- RK3399_SDK_UEFI.img
   5           24576           32767   4.0 MiB     FFFF  atf       <-- Rk3399Pkg/Tools/Bin/trust.img
   6           32768          262143   112.0 MiB   EF00  efi esp

"efi esp" is a particular type of msdosfs file system
that is to contain FreeBSD's EFI Boot Loader (FreeBSD
aarch64 context used below, not what you were using):

EFI/BOOT/bootaa64.efi

That file is a copy of FreeBSD's aarch64 /boot/loader.efi :

# diff /boot/loader.efi  /boot/efi/EFI/BOOT/bootaa64.efi
#

So: no differences. In the context for the above,
/boot/efi is the mount point where the file system in
the "efi esp" was mounted to be visible in the FreeBSD
file system.

Note: the EFI/BOOT/ capitalization convention is my
personal one, not necessarily what FreeBSD normally
uses.

RK3399_SDK_UEFI looks for any finds that
EFI/BOOT/bootaa64.efi and then loads and
uses it.

===
Mark Millard
marklmi at yahoo.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.