Re: [edk2-devel] [HELP] EDK2 on Raspberry Pi 3 B+

["Pete Batard" <pete@akeo.ie>]

Hi,

You may be interested with the pre-built Raspberry Pi 3 UEFI images 
from: https://github.com/pftf/RPi3

At the very least it should tell you if your serial setup works or not, 
as, if properly configured (115200 bauds), you should get some serial 
output regardless of whether you are using RELEASE or DEBUG.

I would first try to use these pre-built images (make sure to replace 
all the files, including config.txt and start.elf as it may matter) and 
check that everything works as expected, before using a custom build.

Now to answer some of your points:

On 2020.05.19 22:54, raingloom wrote:
> Hi!
> 
> I'm trying to get EDK2 working on a Raspberry Pi 3 B+ and am running
> into some issues.
> 
> Setup:
> First, I created a Guix package for EDK2, to make it nice and
> reproducible. It can be found on
> https://git.sr.ht/~raingloom/guix-packages in bootloaders.scm.

You can see how we build the firmware using AppVeyor/Ubuntu here:
https://ci.appveyor.com/project/pbatard/RPi3?fullLog=true

> It took a few tries to compile it, after which I copied RPI_EFI.fd to
> the USB flash drive / microSD card (tried both), alongside the
> necessary blobs and configs, and the miniuart overlay, and finally the
> contents of the latest ARM64 Debian netinst image.
> 
> 
> Problem:
> USB boot straight up doesn't work.

Known issues: https://github.com/pftf/RPi3/issues/13 & 
https://github.com/pftf/RPi3/issues/14

We'll be working on enabling boot without SD, but there's no telling 
when that will happen.

> microSD does get me into GRUB, but none of my USB keyboards work, so
> it's just stuck there. I can't get into the EFI settings either,
> obviously.

This used to be an issue when using the latest Raspberry Pi Foundation 
start.elf before we applied the commits referenced in version 1.24:
https://github.com/pftf/RPi3/releases/tag/v1.24

Are you sure your edk2-platforms repository is up to date?

> I tried debugging it over UART, so I bought my first ever USB UART
> adapter (from a verified RPi reseller in Hungary, who advertised it as
> compatible), wired it up according to the docs, launched screen with
> the right baud rate, and... nothing.

As I mentioned, you should always get some output, regardless of how you 
build the firmware, as the TF-A blob, will produce some. So if you're 
not seeing anything, you need to check your serial connection.

Regards,

/Pete