H-RTOS: ARINC 653 RTOS
A partitioned real-time operating system for 64-bit Arm Integrated Modular Avionics (IMA) platforms, integrated with the H-series hardware
ARINC 653 is the avionics standard for partitioned real-time operating systems. Software applications of different criticality share one computer, each in its own partition with guaranteed memory and processor time. The Hover Real-Time Operating System (H-RTOS) implements the standard for the H-series IMA computers, developed to DO-178C Level A as part of the H-series TSO-C153a IMA platform.
Part of the platform, not ported to it
An ARINC 653 operating system is usually licensed on its own, then ported to a target and integrated with it. H-RTOS is part of the H-series IMA platform: hardware, software, and tools share a single TSO-C153a baseline and one set of certification data, so applicants start from an integrated and verified foundation, with DO-297 Task 1 module acceptance credit for the IMA platform.
Robust spatial and temporal partitioning
Each partition has its own memory, enforced by the processor's Memory Management Unit (MMU). Partitions execute unprivileged and the kernel privileged, so an access outside a partition's memory is blocked and raised as an error. Processor time is allocated by a fixed, repeating schedule, so a fault or overrun in one partition cannot affect the processor time allocated to another. Access to non-volatile storage is bounds-checked per partition.
Multi-core, by design
Higher-criticality software executes in single-core windows, where its worst-case execution time is bounded and verifiable, and lower-criticality software executes on both cores in multi-core windows. Multi-core interference therefore does not affect the higher-criticality software, while the platform still delivers the throughput of both cores.
APEX services
H-RTOS implements the standard ARINC 653 Application Executive (APEX) interface: partition and process management, time management, error handling and health monitoring, sampling and queuing ports, buffers, blackboards, events, semaphores, and mutexes. Additional services support logging and database storage on NOR, NAND, and NVMe flash.
Health monitoring
Health monitor tables are configured at module, partition, and process level, so each error is handled at the level configured for it, from restarting a process to restarting a partition or the module.
Networking and drivers included
H-RTOS includes a network stack with UDP, TCP, TFTP, and Precision Time Protocol (PTP), and drivers for digital, analog, and serial I/O, including ARINC 429 and CAN. Software applications access every H-series interface from project inception, with no board support package to develop or certify.
Integrated development environment
Partitions, memory, schedules, health monitoring, and communication channels are configured in the Hover Software Development Kit (H-SDK) configuration tool in VS Code. Software applications are developed and tested in an emulator with simulated ARINC 429, CAN, Ethernet, and discrete interfaces before they reach the target, then debugged on the target from the same editor and loaded with the H-DL ARINC 615A data loader. Code generated by tools such as Ansys SCADE or MathWorks MATLAB/Simulink is compiled and hosted in partitions in the same way as hand-written code.
Where it is used
- Flight control and autoflight computers
- Detect and Avoid and mission computers
- Data concentrators and battery or fuel cell management
- Software applications of different criticality sharing one IMA platform
Operating system
- Standard
- ARINC 653 Part 1 (APEX)
- Partitioning
- Spatial (MMU) and temporal (fixed schedule)
- Multi-core
- Single-core and multi-core windows
- Health monitoring
- Module, partition, and process level
- Design assurance
- DO-178C Level A