|Stefan Naumann 91b9831250||2 years ago|
|boards||2 years ago|
|include/pios||3 years ago|
|lib||3 years ago|
|source||2 years ago|
|.gitignore||3 years ago|
|.gitmodules||3 years ago|
|LICENSE||4 years ago|
|Makefile||2 years ago|
|README.md||3 years ago|
|ftdi.cfg||3 years ago|
|qemu.ld||3 years ago|
|raspi.cfg||3 years ago|
|rpi.ld||3 years ago|
|startQemu.sh||2 years ago|
Simple prototype operating system for the Raspberry Pi. It aims to be a simple operating system for learning and teaching the ins and outs of operating system development in general and the architecture of a real world System on a Chip (BCM2835) in particular.
The main goal of the project is to learn loads of interesting facts about operating system development. Maybe it will be possible to use the operating system in OS-classes for teaching and experimenting.
The operating system will probably not become stable enough to use in real-life. You’ve been warned.
Maybe this can become a set of drivers and features which can be used as a static library by other embedded programming projects on the Raspberry Pi. They probably all exist already somewhere else, like in the RaspberryPi-Repository of dwelch67.
The code is currently being updated and rewritten in C. The following drivers are tested and work well:
The following device-drivers might not work as expected:
I’m thinking about an interface for adding functions to specific interrupt service routines and also about a generic driver interface.
First you have to decide what target you want to build for. See the subdirectory boards. For example, you may want to build for a QEMU virtual machine, then go into the folder boards/qemu/ and take every file (board.mk and pios_port_config.h) and put it into the root-folder of the repository.
Then go ahead and:
git submodule init && git submodule updatefor fetching the newlib-sources
make newlibfor building newlib
makefor building the libpios-Library and the operating system kernel
If you only want to build libpios.a then you just need to call
Make sure to always build with a consistent board.mk and pios_port_config.h-definitions! Changing or swapping these half way through might result in unexpected behaviour, but that is to be expected then.
PiOS supports JTAG-debugging. You need to initialize the correct Pins of the Raspberry Pi with
pios_jtag_init, these are the following pins:
|BCM Pin Number||Pin-number on the header||JTAG-Pin Use||ALT-value|
I personally use the FT232H mini module and use the openocd-configuration files included (
ftdi.cfg). I took the wiring from RaspberryPi-Repository of dwelch67, who proposes the following wiring (if you need the long form, read there):
|JTAG||FT board||Raspberry Pi|
|Raspi to Raspi:|
|FTDI board to FTDI board:|
OpenOCD debugger opens up port 3333 for
arm-none-eabi-gdb to connect to. Please refer to the gdb-manual on how to do that and how to debug a program.