bzt 586ddf60ac Updated FS/Z | 11 ماه پیش | |
---|---|---|
.. | ||
Makefile | 2 سال پیش | |
OLVASSEL.md | 4 سال پیش | |
README.md | 4 سال پیش | |
boot.S | 3 سال پیش | |
bootboot.c | 3 سال پیش | |
font.psf | 6 سال پیش | |
fs.h | 11 ماه پیش | |
link.ld | 3 سال پیش | |
mkboot.c | 3 سال پیش | |
raspbootcom.c | 4 سال پیش | |
tinf.h | 6 سال پیش | |
tinflate.c | 6 سال پیش |
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.
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.
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.
Copy bootboot.img to FS0:\KERNEL8.IMG.
You'll need other firmware files as well (bootcode.bin, start.elf, fixup,dat).
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.