videocoreiv
rpi4-osdev
| videocoreiv | rpi4-osdev | |
|---|---|---|
| 4 | 17 | |
| 806 | 3,331 | |
| - | - | |
| 0.0 | 6.7 | |
| about 5 years ago | 16 days ago | |
| Python | C | |
| - | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
videocoreiv
- Assembly coding without OS
- reversing pi 4b (arm64) firmware
- VideoCore IV Processor Manual (Raspberry Pi GPU)
-
Taking a Stand in the War on General-Purpose Computing
Interesting, the VC firmware is ThreadX based, indeed[1]! The number of platforms this runs on is absolutely mind-blowing (from an engineering perspective).
[1] https://github.com/hermanhermitage/videocoreiv
rpi4-osdev
- Tutorial: Writing a bare metal operating system for Raspberry Pi 4
-
Assembly coding without OS
GitHub - isometimes/rpi4-osdev: Tutorial: Writing a "bare metal" operating system for Raspberry Pi 4
-
[RPI4B] Error allocating framebuffer with mailbox
Basically i can compile and run this -> https://github.com/isometimes/rpi4-osdev/tree/master/part5-framebuffer (and i'm sure every other implementation) just fine but only if i load it with gdb through jtags and then hit continue (c). If i put the exact same kernel (kernel8.img) on the sd and disconnect any hw debugger, it gets stuck at the rainbow spash screen and won't continue. This is wheter enable_jtag_gpio is set to 0 or 1. This makes absolutely no sense to me and i'd love to get an opinion on why it behaves this way and if it underlines a bigger problem.
-
What projects can an individual do that you would like seeing on a resume?
Something like this would be probably in the top 1% of hobby projects and as far as I can tell, it involves zero EE work: Writing a "bare metal" operating system for Raspberry Pi 4.
-
How do I work towards interacting with Raspberry Pi peripherals directly?
This might be of help: https://github.com/isometimes/rpi4-osdev (it’s for the RPi4, but I imagine most of it being applicable to the RPi1).
-
Writing an open source GPU driver – without the hardware
IMO the best way to get into this type of low-level tinkering is by writing a simple operating system.
https://github.com/isometimes/rpi4-osdev
There are other courses/projects for other boards. The keyword is usually “baremetal”.
For Linux drivers specifically there are training material from Bootlin for instance.
- Writing a “bare metal” operating system for Raspberry Pi 4
- Tutorial: Writing a “bare metal” operating system for Raspberry Pi 4
What are some alternatives?
rpi-open-firmware - Open source VPU side bootloader for Raspberry Pi.
rust-raspberrypi-OS-tutorials - :books: Learn to write an embedded OS in Rust :crab:
rpi-open-firmware - Open source VPU side bootloader for Raspberry Pi.
linux - Linux kernel source tree
java-keyring - Copy of Java Keyring library from bitbucket.org/bpsnervepoint -- with working CI in for osx/linux/windows keystore.
circle - A C++ bare metal environment for Raspberry Pi with USB (32 and 64 bit)
Raspberry_Pi4-B_Assembler - How to code Bare Metal with Assembly language
cs140e-20win - cs140e course materials.
firmware - This repository contains pre-compiled binaries of the current Raspberry Pi kernel and modules, userspace libraries, and bootloader/GPU firmware.
rust-raspberrypi-OS-tutoria
duckduckgo-locales - Translation files for <a href="https://duckduckgo.com"> </a>
tools