In Part 3, we gave MicrOS logging compile-time filtering and per-module verbosity control. That already makes it a powerful tool for day-to-day development. But what if we want to push further? In this final part of the series, I’ll explore…
In Part 2, we added colors, severity tags, and file/line information to MicrOS logs. Now we’re going to take it further: instead of just printing everything, we’ll give developers fine-grained control over what gets logged. This is crucial in embedded…
In Part 1 of this series, I explained why logging matters for MicrOS and how we started with a simple design: log levels, a global ceiling, and per-module registration. That gave us the skeleton of a logging system — but…
When working with microcontrollers, debugging can feel like peering through a keyhole. Unlike desktop development, there’s no rich OS to lean on, no debugger always attached, and no full-featured console to tell you what went wrong. If your system crashes,…
In the last article, we looked at how PendSV swaps thread contexts using prebuilt stack frames. Now it’s time to give our kernel a proper yield mechanism — so threads can give up the CPU voluntarily, or automatically via a…
One of the most magical parts of an RTOS is when the CPU suddenly stops running one function and starts running another — as if by sleight of hand. In MicrOS, this magic is powered by the PendSV exception and…
With the LM3S8965EVB QEMU target, MicrOS has taken its first big step into becoming a real operating system:we now support context switching and a simple task API. In this post, I’ll explain what a context switch is, why it matters,…
For the last couple of days I’ve been battling with my custom embedded operating system — MicrOS (slogan: “simple, open, embedded”). The goal was straightforward: get a bare-metal “Hello, world” sample running under emulation, before moving to real hardware. The…