Why an RTOS: From the Super Loop to ZerOS

Status: rolling out progressively

Overview

If you are arriving from the F103 series, you can already write bare-metal code and drive Renode — but you have never touched a kernel. This station first lays out the three structural problems of a foreground/background system (no guaranteed response time, no task priorities, synchronization managed entirely by hand), then presents a concept map for the whole hand-rolled series, with every concept tagged by the ZerOS commit where it will land; after that it explains why this kernel keeps C++23 on bare metal, and what each of the four verification environments — host, Renode, QEMU, and real hardware — is responsible for.

Articles in This Station

STARTFINISHFrom the Super Loop to an RTOS: Why We Need One, and How to Verify It→STARTFINISHProject Bring-up: From an Empty Repo to the First Line of Renode Output→

The first station, The World Without a Heap, is already live: head into 01-heapless-memory/ and let's hand-roll the memory pool.