618
edits
Booting Raspberry Pi 3: Difference between revisions
no edit summary
| [unchecked revision] | [unchecked revision] |
No edit summary |
No edit summary |
||
| (20 intermediate revisions by 6 users not shown) | |||
Line 1:
{{Tone}}
{{Spelling}}
{{FirstPerson}}
{{You}}
{{Rating|1}}
This is a tutorial on bare-metal OS development on the Raspberry Pi 3 (RPi 3).
'''THIS IS NOT A PRACTICAL IMPLEMENTATION NOR A REFERENCE! It'S SIMPLY SOMETHING TO BE BUILT UP ON!'''
== Preamble ==
Line 20 ⟶ 24:
https://aur.archlinux.org/packages/aarch64-elf-newlib-linaro-bin/
====
Firmware is required for the RPi 3 to boot properly. The firmware needed can be found at
https://github.com/raspberrypi/firmware/blob/master/boot/start.elf
https://github.com/raspberrypi/firmware/blob/master/boot/bootcode.bin
There is also another file required to boot properly. A config.txt file must be supplied to provide configuration details for the device and the OS. Here are the only
<syntaxhighlight lang="ini">
boot_delay=1
force_turbo=1
enable_uart=1
</syntaxhighlight>
More details about booting and configuration can be found at thse links.
https://elinux.org/RPi_Software#Overview
https://raspberrypi.stackexchange.com/a/10595
https://www.raspberrypi.org/documentation/configuration/config-txt/
https://wiki.beyondlogic.org/index.php?title=Understanding_RaspberryPi_Boot_Process (although a bit old, is still useful)
When loading the OS onto an SD card, these file must be included in the boot partition.
Line 43 ⟶ 56:
By now you should have your cross compiler set up. The compiler binaries have the same name as they usually would with "aarch64-elf-" prefixing them (e.x. aarch64-elf-gcc). For this example, three files are used:
*linker.ld - Linker script
*start.S - Setup the environment and call the kernel
*kernel.c - Kernel entry and use
This article is written so that segments of the code will be presented with an explaination, with the full code in the Conclusion section.
== Linking the Kernel ==
Linker script allows us to segment, organize, and align our kernel image. More information about linker scripts can be found osdev's [https://wiki.osdev.org/Linker_Scripts Linker Scripts].
'''The start address and alignment are for the RPi3. Use whatever is applicable to you.'''
<syntaxhighlight lang="c">
SECTIONS
{
. = 0x80000;
.text : {
KEEP(*(.boot));
*(.text*)
}
.rodata ALIGN(16) : {
*(.rodata*)
}
.data ALIGN(16) : {
*(.data*)
}
.bss (NOLOAD) : {
*(.bss*)
}
}
</syntaxhighlight>
== Booting the Kernel ==
For the RPi 3, after the start.elf finishes, the CPU and SRAM have been enabled and control is given to the kernel image. But there are a few things we must do in order to set up a basic C environment. This is known as a bootstrap stage which initializes our OS and programming environment on startup and hands control to the kernel. Keep in mind that this is for a minimalistic development environment on a single core.
<syntaxhighlight lang="asm">
.section .boot
.global _start
_start:
mrs x4, mpidr_el1
and x4, x4, #3
cbz x4, _init
0: wfe
b 0b
</syntaxhighlight>
The mrs instruction loads data from specialty registers into a standard register. This special register in question is called the MPIDR or the Multiprocessor Affinity Register. Caring only about the first two bits only we use a bitwise and to weed out any core ID's that aren't zero. Then we apply the cbz instruction, which is a shorthand instruction for comparing the x4 register with 0 and branching if they are equal, i.e. core 0.
If the core ID is 0, we branch to another section that will initialize the environment and will hand control over to the kernel. For now, the C function for our kernel will simply by kern_main.
<syntaxhighlight lang="asm">
_init: ldr x4, =_start
mov sp, x4
b kern_main
</syntaxhighlight>
Note that with the latest firmware, this is not necessary, as only the primary core runs. It is enough to set up stack and branch to kern_main.
<syntaxhighlight lang="asm">
// for latest firmware, after 2020-01-01
.section .boot
.global _start
_start: ldr x4, =_start
mov sp, x4
b kern_main
</syntaxhighlight>
== Writing the Kernel ==
The kernel is as simple as creating a kern_main function for the bootstrap stage to transfer control to. You notice that in start.S we have the program branch into the function. All we need to do is provide one.
<syntaxhighlight lang="c">
#include <stdbool.h>
void
kern_main(void)
{
while (true);
}
</syntaxhighlight>
== Conclusion ==
At the time of writing, QEMU does not yet emulate the RPi 3. The only way to test is to hook up the RPi 3 to an HDMI monitor. If start.elf was successfully able to run, then a square with interpolated colors will appear on the screen. That paird with the ACT (green LED) flashing even after the square shows means that it most likely has loaded the kernel and started executing. As this lacks a UART example, it will be difficult to get concrete proof that the kernel has booted.
== See Also ==
=== Articles ===
* [[Raspberry Pi Bare Bones]] - a much more detailed introduction to booting on Raspberry Pi
[[Category:Raspberry Pi]]
[[Category:Booting]]
| |||