Embedded operating system

An embedded operating system is a specialized OS that runs on dedicated hardware, often with real-time constraints. Unlike desktop OSes, it is optimized for a single function or a narrow set of functions, such as controlling an engine, a medical device, or a network router. Key characteristics include deterministic scheduling, minimal resource usage, and the ability to operate without user intervention. Many embedded OSes are real-time operating systems (RTOS), which guarantee task completion within specified deadlines. They often use a microkernel architecture to reduce overhead and increase reliability. Examples include FreeRTOS, VxWorks, and QNX. The OS interacts directly with hardware through device drivers and provides APIs for application development, but typically lacks a full graphical user interface.

The evolution of embedded operating systems began in the 1970s with simple kernels for aerospace and industrial control, such as the Apollo Guidance Computer's executive software. In the 1980s, commercial RTOSes like VxWorks and pSOS emerged, serving the growing telecommunications and defense sectors. The 1990s saw the rise of open-source options like Linux and eCos, which offered flexibility and cost savings. The proliferation of smartphones and IoT devices in the 2000s and 2010s drove the adoption of Android (based on Linux) and lightweight OSes like Contiki and RIOT for constrained devices. Today, embedded OSes are integral to automotive systems, medical implants, and industrial automation, with a trend toward virtualization and mixed-criticality support.

Embedded operating systems vary widely in architecture and capability. At one end are bare-metal kernels and tiny RTOSes like FreeRTOS and Zephyr, which provide basic task scheduling and inter-process communication in a few kilobytes of memory. At the other end are full-featured OSes like Embedded Linux and Windows IoT, which offer rich APIs, networking, and file systems but require more resources. Some systems use a hypervisor to run multiple OSes on a single processor, enabling mixed-criticality workloads. Another distinction is between event-driven and time-triggered designs, affecting predictability. The choice of OS depends on factors such as power consumption, memory footprint, real-time guarantees, and certification requirements, especially in safety-critical domains like avionics (DO-178C) and automotive (ISO 26262).

Beyond mainstream RTOSes, there are niche embedded OSes with unique features. For instance, the ERIKA Enterprise is an open-source RTOS compliant with the OSEK/VDX standard for automotive. seL4 is a formally verified microkernel, proving security and correctness mathematically. Fuchsia, developed by Google, uses a microkernel called Zircon and is designed for embedded and IoT devices. In the space sector, RTEMS (Real-Time Executive for Multiprocessor Systems) has been used in satellites and space probes. Also notable is Contiki, which introduced the concept of protothreads for memory-constrained sensor networks. These systems often have dedicated communities and are used in research and specialized industries, highlighting the diversity of embedded OS design.

RTOS

Real-Time Operating System; an OS that guarantees task completion within specified time constraints.

Microkernel

A minimal kernel that provides only essential services, with other services running in user space.

SoC

System-on-a-Chip; an integrated circuit that contains all components of a computer or other system.

Hypervisor

Software that creates and runs virtual machines, allowing multiple OSes to share hardware.

Mixed-criticality

A system where tasks of different safety criticality levels run on the same hardware.