Ard Biesheuvel 8977ff44a5 Platform/RaspberryPi4: remove ASIX 88772b driver | 4 years ago | |
---|---|---|
.. | ||
RPi4.dsc | 4 years ago | |
RPi4.fdf | 4 years ago | |
Readme.md | 4 years ago |
This is a port of 64-bit Tiano Core UEFI firmware for the Raspberry Pi 4B platform.
This is intended to be useful 64-bit TF-A + UEFI implementation for the Raspberry Pi variants based on the BCM2711 SoC, which should be good enough for most kind of UEFI development, as well running consumer Operating Systems.
Raspberry Pi is a trademark of the Raspberry Pi Foundation.
The RPi4 target supports Pi revisions based on the BCM2711 SoC:
Please see the RPi3 target for the BCM2837-based variants, such as the Raspberry Pi 3B.
This firmware is still in development stage, meaning that it comes with the following major limitations:
Build instructions from the top level edk2-platforms Readme.md apply.
RPI_EFI.fd
firmware onto the partitionbcm2711-rpi-4-b.dtb
fixup4.dat
start4.elf
overlays/miniuart-bt.dbto
or overlays/disable-bt.dtbo
(Optional)Create a config.txt
with the following content:
arm_64bit=1
enable_uart=1
enable_gic=1
armstub=RPI_EFI.fd
disable_commandline_tags=2
device_tree_address=0x1f0000
device_tree_end=0x200000
Additionally, if you want to use PL011 instead of the miniUART, you can add the lines:
dtoverlay=miniuart-bt
Note: doing so requires miniuart-bt.dbto
to have been copied into an overlays/
directory on the uSD card. Alternatively, you may use disable-bt
instead of
miniuart-bt
if you don’t require Bluetooth.
Insert the uSD card and power up the Pi.
The TF-A binary was compiled from the latest TF-A release. No aleration to the official source has been applied.
For more details on the TF-A compilation, see the relevant
Readme
in the TrustedFirmware/
directory from edk2-non-osi
.
By default, UEFI will use the device tree loaded by the VideoCore firmware. This depends on the model/variant, and relies on the presence on specific files on your boot media. E.g.:
bcm2711-rpi-4-b.dtb
(for Pi 4B)You can override the DTB and provide a custom one. Copy the relevant .dtb
into the root of
the SD or USB, and then edit your config.txt
so that it looks like:
(...)
disable_commandline_tags=2
device_tree_address=0x1f0000
device_tree_end=0x200000
device_tree=your_fdt_file.dtb
Note: the address range must be [0x1f0000:0x200000]
. dtoverlay
and dtparam
parameters are also supported.
bootargs
This firmware will honor the command line passed by the GPU via cmdline.txt
.
Note, that the ultimate contents of /chosen/bootargs
are a combination of several pieces:
cmdline.txt
.The Raspberry Pi has no NVRAM.
NVRAM is emulated, with the non-volatile store backed by the UEFI image itself. This means that any changes made in UEFI proper are persisted, but changes made from within an Operating System aren’t.
The Rasberry Pi has no RTC.
An RtcEpochSeconds
NVRAM variable is used to store the boot time.
This should allow you to set whatever date/time you want using the Shell date and
time commands. While in UEFI or HLOS, the time will tick forward.
RtcEpochSeconds
is not updated on reboots.
This UEFI supports both the USB3 xHCI ports (front ports), and the Pi 3-style DesignWare USB2 controller via the Type-C port (host only).
The following only apply to the Type-C port:
OS support for ACPI description of Pi-specific devices is still in development. Not all functionality may be available.