This repository contains a TF-A + EDK2 UEFI firmware port for Raspberry Pi 5.
Check the Supported peripherals and Supported OSes sections to see what's currently possible with this firmware.
-
Note: For OS, it is highly suggested to use a quality drive with good random I/O performance. In SD terms this means an A1/A2-rated card.
-
Depending on the peripherals you use, more power may be needed. The recommended official power supply provides 5.1V 5A (25 W).
Note: Using an inadequate supply can cause all sorts of issues, from underclocking to random crashes.
-
The device may thermal throttle otherwise.
Optionally, if display is not available or for debugging purposes, an UART serial adapter compatible with the special connector. Configuration is 115200 8n1
.
The latest version can be obtained from Releases.
Prepare an empty boot drive by formatting the first partition as FAT32, then extract the archive downloaded above to the root of this partition.
Note: do not rename or delete any of the boot files.
You should first see a QR code screen, then shortly after, a centered Raspberry Pi logo with progress bar at the bottom. This indicates that the UEFI firmware has loaded.
At this stage, you can press Esc to enter the firmware setup, F1 to launch the UEFI Shell, or, provided you also have an UEFI bootloader/app on a storage device, you can let the system automatically run that, which is the default behavior if no action is taken.
Check the configuration options described below, some of which may need to be changed depending on the OS used.
The UEFI provides options that can be viewed and changed using the UI configuration menu.
Configuration through the user interface is fairly straightforward and help/navigation information is provided around the menus.
-
For maximum SD card performance, go to
Device Manager
->Raspberry Pi Configuration
->ACPI / Device Tree
and setCompatibility Mode
toFull Bay Trail
, then untickLimit UHS-I Modes
.Warning: this may affect other OSes!
-
If you're getting a Synchronous Exception when booting certain distros, go to
Device Manager
->EFI Memory Attribute Protocol
and untickEnable Protocol
.
Only devices relevant to the firmware are listed below.
Device | Status | Notes |
---|---|---|
RP1 USB | 🟢 Working | |
RP1 Ethernet | 🔴 Not working | |
RP1 GPIO | 🔴 Not working | |
RP1 PWM | 🔴 Not working | Fan control |
PCIe | 🔴 Not working | RP1 is left configured by the VPU. |
SD | 🟢 Working | SD cards up to SDR104. eMMC support is unknown. |
Display | 🟢 Working | HDMI, driven by the VPU firmware. |
UART | 🟢 Working | PL011 available on the dedicated connector at 115200 8n1. |
GPIO | 🟢 Working | GIO/AON, pin function. |
RTC | 🟢 Working | Get/set time, wake up alarm. |
RNG | 🔴 Not working | |
EEPROM | 🔴 Not working | Needed for proper NVRAM. |
ACPI support is currently under development and limited to a few devices that have existing driver bindings.
OS | Version | Tested/supported hardware | Notes |
---|---|---|---|
Windows | 11 (including insider) | Display, USB, SD, SDIO | * USB may corrupt data, especially when used for booting. * SD is limited to DDR50. |
Linux | tested Ubuntu 22.04, kernel 5.15.0-75-generic | Display, USB, SD, SDIO (incl. Wi-Fi) | * SD is limited to HS by default. See Configuration settings - Linux. * Wi-Fi may require manual firmware installation. |
FreeBSD | 13.2 | Display, USB, SD | * SD is limited to HS. |
NetBSD | recent daily build | Display, USB | * SD fails to communicate with the card. |
VMware ESXi Arm Fling | 1.15 | Display, USB | * Requires compatible USB network adapter. |
This process assumes a Linux machine. On Windows, use WSL.
-
Install required packages:
For Ubuntu/Debian:
sudo apt install git gcc g++ build-essential gcc-aarch64-linux-gnu iasl python3-pyelftools uuid-dev
For Arch Linux:
sudo pacman -Syu sudo pacman -S git base-devel gcc dtc aarch64-linux-gnu-binutils aarch64-linux-gnu-gcc aarch64-linux-gnu-glibc python python-pyelftools iasl --needed
-
Clone the repository:
git clone --recurse-submodules https://github.com/worproject/rpi5-uefi.git cd rpi5-uefi
-
Build the image:
./build.sh
Append
--help
for more details.
If you get build errors, it is very likely that you're still missing some dependencies. The list of packages above is not complete and depending on the distro you may need to install additional ones. In most cases, looking up the error messages on the internet will point you at the right packages.
Most files are licensed under the default EDK2 license, BSD-2-Clause-Patent.
For TF-A, see: https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/license.rst