RPi4 VS RPi3

Correct. It does not as shipped. However, the use of this project will bring the firmware into system ready spec, so it can boot with a standard aarch64 UEFI image: https://github.com/pftf/RPi4

are you using the uefi firmware from https://github.com/pftf/RPi4 or are you trying to boot through the gpio serial header?I don't think the pi can boot on its own through uboot unless your using a serial/usb connection

Looks like you can use Grub on UEFI ARM systems, but Raspberry Pi isn't natively running UEFI. https://github.com/pftf/RPi4

The rpi4 has uefi firmware available, this allows you to boot any generic uefi aarch64 image, you no longer need rpi specific images.

https://github.com/pftf/RPi4

Straight out of the box, the image wouldn't boot, said that start.elf was invalid, so I went to https://github.com/pftf/RPi4/releases as suggested in the Readme.md file in the EFI partition. I installed that (version 1.34) over the existing EFI partition and tried again. That booted up the kernel, but it apparently died when it enabled the interrupt controller. The last messages are about armgic0.

Maybe similar discussion on github:

You can use these firmware images for UEFI as well as install with the arm ISO. I didn't have graphics acceleration that way, but it might be an easy fix.

I'm guessing these are not SystemReady certified with UEFI firmware and require "bespoke" preinstalled arm images?

https://www.arm.com/architecture/system-architectures/system...

https://developer.arm.com/documentation/102677/0100/UEFI-req...

I have three SystemReady arm devices and it's pretty awesome to be able to just boot an aarch64 live ISO and install. The experience is the same for running vms via ESXi arm edition.

Nvidia Jetson AGX Xavier - https://developer.nvidia.com/embedded/downloads#?search=uefi

Honeycomb LX2 - https://github.com/SolidRun/lx2160a_uefi

RPI4 - https://github.com/pftf/RPi4

It can be tedious building/provisioning the firmware but once complete they are ready for any aarch64 uefi iso.

What is annoying however is when distros don't ship an aarch64 uefi iso - but instead choose to build a zillion device specific "preinstalled" arm images. (looking at you manjaro)

The list of supported devices for ESXi arm edition is a great place to start for identifying options and is constantly updated.

https://flings.vmware.com/esxi-arm-edition

  Raspberry-Pi-4

The only reason why I am was trying to build the image was because I wanted to move stuff as mainline as possible and was worried that any installation made with the help of RPi4 UEFI firmware would stop booting after a while.

Most ARM hardware is cellphones, raspberry pi and the Mac M1, which certainly aren't that type.

But a lot of ARM hardware is that type. The keywords are SBSA / SBBR / SystemReady. If your hardware is SBBR compatible then Fedora and Ubuntu's ARM64 iso, and Windows ARM64, downloaded from their website, will at least boot fine (drivers are a different question as always).

There's a good list of supported hardware in the lower half of https://community.arm.com/arm-community-blogs/b/architecture... . Many systems from Avantek, Gigabyte, NXP, Marvell, Solidrun etc are standardizing on this way of booting.

DeviceTree is low-level enough that you can implement UEFI on top of it. There's a UEFI port for the Raspberry Pi 4 at https://rpi4-uefi.dev/ that produces an SBBR layer, allowing it to boot any off-the-shelf ARM64 SBBR distro.

Projects like Tow-Boot, a distribution of U-Boot, provide a nice boot menu and allow you to boot the "generic ARM" ISOs that are usually just UEFI. On the Raspberry Pi 3 and 4, you can put Tianocore EDK2 onto the SD card and boot any UEFI image, including Windows 10 or 11 for ARM.

The approach I used is very different from the conventional setup. Most setups will rely on the default boot loader stack that the Raspberry Pi uses, but this project instead relies on the UEFI images provided by https://github.com/pftf/RPi3/ and https://github.com/pftf/RPi4 instead. There are two reasons for this.

> Isn't a faster boot what everybody wants?

I’ll rather have slow boot and proper UEFI support so I can boot any vanilla ARM64 Linux distro (Debian proper), instead of images/distros which have been crafted to be device-specific (Raspbian).

I boot this thing once every second month at most. I honestly couldn’t care less about boot-times.

Luckily for me, there are solutions to my problem too ;)

https://github.com/pftf/RPi3

It's been manually implemented for many devices - the Renegade Project and Raspberry Pi 3 implementation do exactly this.

Odd to see using UEFI to NetBoot not considered an option at all.

It should eliminate the timing-bug and leave you in a more reliable (and scriptable!) pre-boot environment. What more do you need?!?

Both the RPi3 and 4 can be UEFI booted, so this is definitely a real-world option.

Links:

- https://github.com/pftf/RPi3

- https://github.com/pftf/RPi4