Applications › Battery-powered & consumer devices
In appliances, wearables and sensors, cost and battery life decide the design. A lean scheduler lets you choose a smaller MCU, clock it lower and keep it asleep longer.
In volume products a smaller MCU is a direct bill-of-materials saving.
Periodic tick interrupts wake the MCU even when nothing is ready to run.
Buttons, sensors, display and radio each need their own timing, without a heavyweight RTOS.
Timer-based wakeups instead of periodic ticks maximize sleep time.
About 12% more application CPU time than FreeRTOS in our benchmark, which can let you run at a lower clock frequency.
Arm Cortex-M from ARMv6-M, and RISC-V RV32I and RV32E, including very small RAM devices.
BlockMemoryPool and BytePool, no heap, no fragmentation. In the 4-task benchmark STK used 6.7 KB of RAM against 8.8 KB for FreeRTOS.
FreeRTOS, CMSIS-RTOS2 and POSIX Threads compatibility layers help move existing code.
TinyUSB and lwIP ports; I2S/TDM audio and DMA integration are available as services.
Start in tickless mode so idle gaps put the MCU to sleep.
Size stacks and memory pools statically so total RAM is known at build time.
Keep tasks simple: the default soft real-time mode suits most appliance logic, and optional time-slicing is available where you need it.
To reuse existing code, begin with the FreeRTOS or CMSIS-RTOS2 compatibility layer and migrate gradually.
For balance: STK's flash use in the benchmark was higher than FreeRTOS (for example 14.9 KB against 12.6 KB at -Os), while RAM use was lower. Measure on your own target before choosing.
Porting, real-time tuning, certification support and commercial components are available. See services.