CMRX is a real-time microkernel OS that provides automatic, hardware-enforced memory protection for ARM Cortex-M microcontrollers. No manual configuration. No months of MPU work. Deploy in days and cut long-term maintenance costs.
Every connected device without memory protection is a liability. A regulatory risk. A potential breach vector. And a growing maintenance burden.
Third-party drivers and stacks (WiFi, USB, Bluetooth) can contain bugs. Without isolation, a buffer overflow in any component can corrupt your entire system.
Configuring ARM MPU regions manually takes months of specialized work. Most teams skip it or get it wrong. Human error in MPU setup is a documented compliance gap.
Even a “simple” IoT sensor becomes an attack vector once it’s on a network. Attackers chain vulnerabilities across connected devices to reach high-value targets.
The CRA requires manufacturers of products with digital elements to implement cybersecurity measures throughout the product lifecycle. This includes embedded devices.
Memory protection is not explicitly mandated, but it’s a fundamental cybersecurity measure that auditors and regulators will expect. Devices without it face compliance risks.
Manual MPU configuration takes months and is error-prone. CMRX makes memory protection automatic — deployable in days, auditable by design. That means lower maintenance costs and fewer field incidents over the product lifecycle.
Automatic, hardware-enforced memory protection for ARM Cortex-M. No configuration. No specialized MPU expertise required. Deploys in days — saving months of engineering cost.
The conventional approach to memory protection on microcontrollers creates more problems than it solves.
| CMRX | FreeRTOS | Zephyr | QNX | |
|---|---|---|---|---|
| Memory protection | Always-on, automatic | Manual, painful | Optional add-on | Yes (requires MMU) |
| Architecture | Microkernel | Monolithic | Monolithic | Microkernel |
| Driver isolation | Full (userspace) | None (kernel-resident) | None | Full |
| Minimum hardware | Cortex-M0+ (MPU) | Cortex-M0 | Cortex-M0 | Cortex-A (MMU req.) |
| RAM requirement | 1kB+ | 1kB+ | 4kB+ | MB range |
| License | MIT | MIT | Apache 2.0 | Proprietary |
| Maintenance cost | Low (bugs contained) | High (cascading bugs) | Medium | Low (but expensive) |
| Off-target testing | Built-in | No | Limited | Separate tools |
Your connected sensor, gateway, or actuator needs memory protection before December 2027. CMRX makes it automatic on the hardware you already use — cutting months of setup and ongoing maintenance.
Your clients are asking about CRA compliance. CMRX lets you deliver memory-isolated firmware without months of MPU configuration per project. Lower your costs, increase your margin.
Mixed-criticality systems need spatial isolation. CMRX provides hardware-enforced process separation that supports ISO 26262 / IEC 62443 arguments — with dramatically lower total cost of ownership.
Pick your platform. Clone the repo. Build and flash. Memory protection is on from the first boot.
Start building secure embedded firmware today. Zero configuration. Zero license fees. Hardware-enforced memory protection from the first boot.
Or email directly: info@cmrxrtos.org