μVOS: Real-Time Operating System for Embedded Actuators and Sensors
Overview
μVOS is a real-time operating system purpose-built for embedded controllers in automotive and industrial applications. Designed for ultra-low memory environments, μVOS enables responsive, reliable execution of sensor and actuator logic on microcontrollers with as little as 2KB of RAM. It leverages an OSEK-compliant architecture extended with key elements from the AUTOSAR standard, while offering a lock-free kernel to minimize interrupt latency and context switch overhead.
The system is ideally suited for time-sensitive, safety-critical applications such as motion control, communication gateways, and self-calibrating smart sensors. Its integrated code generation toolchain allows developers to deploy configuration-driven systems with minimal manual coding effort.
Core Features
- Lock-free, asynchronous scheduling model
- Fast interrupt response (≤20 clock cycles on 8-bit AVR)
- Scalable task and ISR model with no built-in limits
- Predictable execution behavior for safety-critical use
- Minimal RAM footprint (<2KB typical)
- Designed for 8-bit, 16-bit, and low-end 32-bit MCUs
- Efficient task dispatch with performance comparable to direct function calls
- Extended OIL configuration model
- Code generation toolchain for application scaffolding
- Support for static and dynamic task mapping
- LIN and CAN communication stack support
- Optional AUTOSAR Network Management integration
- Suitable for multi-node distributed applications
Layered Architecture
μVOS follows a modular layered model, aligned with automotive standards.
Application Layer
For application logic not bound by hard real-time constraints – e.g., diagnostics, state monitoring, etc.
Complex Drivers
High-speed control loops, such as current regulation or motor drivers, implemented directly over ISR or task abstraction.
Virtual Bus
Middleware layer that automatically routes signals and events across components and buses (CAN/LIN).
Service Layer
Cross-cutting services, including:
- Scheduler
- Diagnostic Manager
- Watchdog Manager
- ECU State Manager
- Time Services
- Utility Libraries (CRC, fixed-point math, LUTs)
ECU & MCU Abstraction Layers
Abstract hardware differences and allow for:
- EEPROM/Flash emulation
- On-board device integration
- Communication controller abstraction (LIN/CAN/SPI)
- I/O abstraction and virtualization
Toolchain & Development Process
- Runtime services
- OS configuration
- Communication layers
- A2L/FIBEX system descriptors
Proven Use Cases
- Electric motor controllers with field-oriented control
- HVAC and expansion valve control units
- Smart actuators with distributed calibration logic
- Communication gateways for automotive LIN/CAN networks
Why Choose μVOS?
Capability |
Description |
|---|---|
| Ultra-Low Footprint | Runs on devices with less than 2KB of RAM |
| Lock-Free Kernel | Deterministic execution without global IRQ locks |
| Code Generation | Configuration-driven development using extended OIL |
| Real-Time Performance | Context switching in fewer than 20 clock cycles |
| Protocol Support | Native support for LIN and CAN communications |
Tell Us About Your Project
"*" indicates required fields
