ChibiOS/RT is the real-time kernel of the ChibiOS embedded platform, engineered for predictability, efficiency, fine‑grained timing control, and real SMP support for next-generation MCUs and MPUs.
It combines a fully static architecture, true tickless operation, µs‑class system time, and a fully preemptive scheduler with very low context switch and thread flyback latencies, delivering a small, fast, and highly deterministic RTOS suitable for both open source and commercial products.
ChibiOS/RT is designed around a fully static kernel.
This approach is particularly well suited for safety‑relevant, resource‑constrained, and long‑lived embedded systems.
ChibiOS/RT implements a fully preemptive scheduler optimized for extremely low latency:
This makes ChibiOS/RT particularly suitable for real‑time control, motor drives, and drone/UAV flight stacks, where worst‑case latency is critical.
ChibiOS/RT implements real tickless scheduling:
A traditional fixed tick can still be enabled when needed, but the core design is event‑driven and tickless.
System time in ChibiOS/RT is derived from high‑resolution timers, enabling microsecond‑class (µs) delays and timing:
ChibiOS/RT provides true symmetric multiprocessing (SMP) capabilities:
This enables better scalability and performance when moving from single‑core to multi‑core platforms.
ChibiOS/RT is used in a wide range of real‑time embedded systems where deterministic timing, low latency, and tight resource budgets are essential:
| Use case | Typical roles for ChibiOS/RT |
|---|---|
| Drones and UAVs | Flight control, stabilization loops, sensor fusion, navigation, and payload control with hard real‑time constraints |
| Robotics and autonomous systems | Motion control, kinematics, sensor processing, and coordination of multiple actuators and sensors |
| Motor control and drives | FOC (Field‑Oriented Control), BLDC/PMSM drives, servo control, and high‑frequency control loops |
| Audio and signal processing | Low‑latency audio pipelines, DSP‑style tasks, and precise scheduling of sample processing |
| Power management / low‑power systems | Battery‑powered devices, low‑power modes, and applications where tickless operation reduces energy consumption |
| Industrial and instrumentation | PLC‑like control, data acquisition, instrumentation front‑ends, and tightly timed I/O handling |
| Connectivity and communication | Protocol handling, time‑critical communication windows, and synchronized data transfers |
(Real deployments range from hobby projects to professional and industrial products, often on STM32 and other popular MCU families.)
| Aspect / Feature | ChibiOS/RT focus and design choices | Common alternatives (typical RTOS designs) |
|---|---|---|
| Architecture & determinism | Monolithic, fully preemptive RTOS with strong focus on predictable, analyzable timing | Monolithic or modular kernels; determinism depends on configuration and enabled subsystems |
| Scheduling latency | Optimized for very low context switch times and short thread flyback latencies | Context switch and wakeup times vary widely by implementation and configuration |
| Memory model | Fully static kernel, no dynamic allocation required in the core | Many RTOS kernels allow or expect dynamic allocation for some OS objects |
| Tick model | True tickless, event-driven scheduling (fixed tick optional) | Commonly based on a periodic system tick; often provide tickless idle or tick suppression |
| System time resolution | High‑resolution, µs‑class system time and delays | Often optimized around millisecond‑level ticks; higher resolution may require extra configuration or code |
| SMP capabilities | Real SMP support for single‑image, multi‑core MCUs/MPUs | SMP support varies; many RTOSes focus on single core, some offer SMP on selected architectures |
| Footprint (kernel only) | Very small footprint, tuned for MCU‑class, resource‑constrained systems | Footprint ranges from very small kernels to larger, feature‑rich platforms |
| HAL / drivers | Integrated HAL with broad MCU coverage (e.g., STM32 and others) | Some RTOSes focus mainly on the kernel and rely on external or vendor‑specific HALs; others provide a large, unified driver model |
| Licensing & commercial use | Open Source (GPLv3, Apache‑2.0) plus commercial licensing options for proprietary and safety‑related projects | Typically permissive or copyleft open source licenses; commercial support options vary by vendor or service provider |
This table is intended as a high‑level, technical overview of common RTOS design choices. Actual capabilities and configurations depend on the specific RTOS, version, port, and project settings.
Explore the features set.