kotovalexarian-likes-gitlab/bztsrc--bootboot
1
0
Fork 0
mirror of https://gitlab.com/bztsrc/bootboot.git synced 2023-02-13 20:54:32 -05:00
Code Releases Activity
bztsrc--bootboot/aarch64-rpi
History
bzt ad79bc6666 Remove ./ from initrd paths
2020-06-15 06:21:29 +02:00
..
boot.S Support for RPi4 2020-02-26 12:54:20 +01:00
bootboot.c Remove ./ from initrd paths 2020-06-15 06:21:29 +02:00
font.psf Initial commit 2018-06-05 20:34:03 +02:00
fs.h Remove ./ from initrd paths 2020-06-15 06:21:29 +02:00
link.ld Initial commit 2018-06-05 20:34:03 +02:00
Makefile Recompiled with gcc 8.2.0 2019-02-22 17:11:29 +01:00
mkboot.c Support for RPi4 2020-02-26 12:54:20 +01:00
OLVASSEL.md Support for RPi4 2020-02-26 12:57:02 +01:00
raspbootcom.c Initial commit 2018-06-05 20:34:03 +02:00
README.md Support for RPi4 2020-02-26 12:57:02 +01:00
tinf.h Initial commit 2018-06-05 20:34:03 +02:00
tinflate.c Initial commit 2018-06-05 20:34:03 +02:00

README.md

BOOTBOOT Raspberry Pi 3 / 4 Implementation

See BOOTBOOT Protocol for common details.

On Raspberry Pi 3+ board the bootboot.img is loaded from the boot (or firmware) partition on SD card as kernel8.img by start.elf. For separating firmware and boot partitions see documentation.

Machine state

In addition to standard mappings, the MMIO is also mapped in kernel space:

   -128M         MMIO      (0xFFFFFFFFF8000000)

Code is running in supervisor mode, at EL1 on all cores. Dummy exception handlers are installed, but your kernel should use it's own handlers as soon as possible.

File system drivers

For boot partition, RPi3 version expects FAT16 or FAT32 file systems (if the initrd is a file and does not occupy the whole boot partition). The initrd can also be loaded over serial line, running raspbootcom or USBImager on a remote machine.

Gzip compression is not recommended as reading from SD card is considerably faster than uncompressing.

Installation

  1. Copy bootboot.img to FS0:\KERNEL8.IMG.

  2. You'll need other firmware files as well (bootcode.bin, start.elf, fixup,dat).

  3. If you have used a GPT disk with ESP as boot partition, then you need to map it in MBR so that Raspberry Pi firmware could find those files. The mkboot utility will do that for you.

Limitations

  • Initrd in ROM is not possible
  • Maps only the first 1G of RAM.
  • Cards other than SDHC Class 10 not supported.
  • Raspberry Pi does not have an on-board RTC, so always 0000-00-00 00:00:00 returned as bootboot.datetime.
  • Only supports SHA-XOR-CBC cipher, no AES