This directory hosts the Generic Bootloader Library project. A Bazel workspace is setup for building the library as well as an EFI executable that can be loaded directly from the firmware.
The GBL project are intended to be built from the Android Bootloader super project checkout.
To build the EFI application:
./tools/bazel run //u-boot:gbl_efi_dist --extra_toolchains=@gbl//toolchain:all
The above builds the EFI application for all of x86_64, x86_32, aarch64 and riscv64 platforms.
To run the set of unit tests:
./tools/bazel test @gbl//tests --extra_toolchains=@gbl//toolchain:all
If you have a main AOSP checkout and is setup to run Cuttlefish, you can run the EFI image directly with:
launch_cvd --android_efi_loader=<path to the EFI image> ...
The above uses the same setting as a normal launch_cvd run, except that insted of booting Android directly, the emulator first hands off to your EFI application.
Note: For x86 platform, use the EFI image built for x86_32.
If you simply want to test the EFI image as a standalone application on QEMU directly:
Install EDK, QEMU and u-boot prebuilts
sudo apt-get install qemu-system ovmf u-boot-qemu
Depending on the target achitecture you want to run:
For x86_64:
mkdir -p /tmp/esp/EFI/BOOT && \
cp <path to EFI image> /tmp/esp/EFI/BOOT/bootx64.efi && \
qemu-system-x86_64 -nographic \
-drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd \
-drive format=raw,file=fat:rw:/tmp/esp
For aarch64:
mkdir -p /tmp/esp/EFI/BOOT && \
cp <path to EFI image> /tmp/esp/EFI/BOOT/bootaa64.efi && \
qemu-system-aarch64 -nographic -machine virt -m 1G -cpu cortex-a57 \
-drive if=pflash,format=raw,readonly=on,file=/usr/share/AAVMF/AAVMF_CODE.fd \
-drive format=raw,file=fat:rw:/tmp/esp
For riscv64:
mkdir -p /tmp/esp/EFI/BOOT && \
cp <path to EFI image> /tmp/esp/EFI/BOOT/bootriscv64.efi && \
qemu-system-riscv64 -nographic -machine virt -m 256M \
-bios /usr/lib/u-boot/qemu-riscv64/u-boot.bin \
-drive format=raw,file=fat:rw:/tmp/esp,id=blk0 \
-device virtio-blk-device,drive=blk0