Booting Raspberry Pi 3: Difference between revisions

Jump to navigation Jump to search
[unchecked revision][unchecked revision]
Content deleted Content added
No edit summary
No edit summary
Line 62: Line 62:
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].
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.
'''The start address and alignment are for the RPi3. Use whatever is applicable to you.'''
<pre>
<pre>
SECTIONS
SECTIONS
Line 93: Line 93:
== Booting the Kernel ==
== Booting the Kernel ==


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 on startup and hands control to the kernel. Keep in mind that this is for a minimalistic development environment on a single core.
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.


When the CPU starts running the kernel, all cores will be executing the same code. This can be tricky for multiple reasons, which will be described later. For now, all we want is just one core running the kernel. To do that, we need get the core identification number and set all but one core to run an infinite loop.
When the CPU starts running the kernel, all cores will be executing the same code. This can be tricky for multiple reasons, which will be described later. For now, all we want is just one core running the kernel. To do that, we need get the core identification number and set all but one core to run an infinite loop.
Line 120: Line 120:


== Writing the Kernel ==
== 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.

<pre>

#include <stdbool.h>

void
kern_main(void)
{
while (true);
}
</pre>


== Conclusion ==
== 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.
Here is the code for all of the files.


====How to Proceed====
start.S
<pre>
.section .boot


If you are new to operating system development, I encourage you to take the time and read '''Basic Information''' section of OsDev's [https://wiki.osdev.org/Main_Page Main Page]. You should know they developing an operating system, even a microkernel, is difficult. The lack of explicit documentation is enough to frustrate novices and even experienced developers (which is exactly the main purpose of this series). The goal is to be patient and understand that what may be ahead is fun but also challanging. Continuing forward also means that you must be accustomed to and aware of the functionalities an operating system must provide. I also recommend that you take the time to go through the resources in Extra Resources to make sure you are acquainted with operating systems and their engineering for beginners and those who are familiar.
.global _start


That being said, if you have committed to the project then take note that from this point on I will be focusing on RPi 3 development.
_start:
mrs x0, mpidr_el1
and x0, x0, #3
cbz x0, _init
0: wfe
b 0b


====Extra Resources====
_init:
* [https://pdos.csail.mit.edu/6.828/2017/xv6/book-rev10.pdf Short book on operating systems with reference implemenation]
b kern_main
* [https://ocw.mit.edu/courses/electrical-engineering-and-computer-science/6-828-operating-system-engineering-fall-2012/ MIT OpenCourseWare class on operating system engineering]
</pre>