osblog VS awesome-riscv

How to automate building and running the project using make; in particular, leveraging variables in the Makefile to elegantly apply the same command line options for compiling each file in the codebase - because trust me, you'll need a ton of command-line options ;-) For this, I based my initial Makefile on that found in the source code for "The Adventures of OS", e.g. this

I would like to thank the authors of RISC-V from scratch and The Adventures of OS for their high-quality articles that go into great detail on how RISC-V works. Without their well-written articles, I wouldn't have known how to get started with kernel development on RISC-V. My initial project setup - the minimal C runtime crt0.s in assembly and the linker script riscv64-virt.lds - is based on the former, while my UART driver code is adapted from the latter and I intend to closely follow the latter going forward.

Here's an example of an interrupt routine (m_trap_vector): https://github.com/sgmarz/osblog/blob/master/risc_v/src/asm/trap.S

Github seems like a good option for this (or codeberg), creating something like awesome risc-v where other people can make suggestions and improvements.

The lists out there are out of date, but this isn't a bad place to start.

In general, I've been seeing quite a few interesting open-source implementations; what RISC-V has brought to the table is a community and an ISA that open CPU implementors can get behind, and vice versa, which has led to a lot of advancements in open CPU development.

If you'd like to learn first-hand, why not look at a few open-source implementations for yourself? I think that's one of the incidental benefits of RV - people implementing their own FOSS cores with a shared instruction set!

RISC-V is about to take off! https://github.com/drom/awesome-riscv