ZenOS 1.1.0 · STM32 · ARM Cortex-M · Real-time

STM32 RTOS with ZenOS

A practical visual overview of the ZenOS 1.1.0 kernel architecture for STM32 firmware: configurable priority scheduling, task resources, timing, IPC, diagnostics and safety mechanisms.

⚡

16 priorities by default

The default configuration provides 16 priority slots and supports a configurable range of 2–256. Priority 0 is reserved for idle, while higher numeric values represent higher application priority.

🧱

Static resources

Task stacks and task control resources are statically allocated; task creation does not require a general-purpose heap for task stacks.

🔗

Bounded IPC

Events, mutexes, queues and semaphores support common task coordination patterns. Mutexes use IPC priority-ceiling behavior.

STM32 firmware flow

From hardware events to application tasks

IRQ / DMAdata arrives
→
IPCnotify / queue
→
Taskprocess / control

Why an RTOS?

Separate communications, sensors, control, telemetry, UI and diagnostics into independently scheduled activities instead of one large main loop.

Timing & diagnostics

The default kernel tick period is 100 µs, configurable within the supported 100–1000 µs range. CPU, stack, deadline, error and watchdog-related monitoring are configurable.

Safety configuration

Depending on target and configuration, mechanisms include watchdog support, MPU integration where supported, CRC checks, bounded RAM integrity testing and integrity monitoring. These are not certification evidence.