Features Documentation Examples Repository Blog Contact

ESE Kongress 2025 Talk

September 10, 2025

This december the ESE Kongress will take place in Sindelfingen. We are pleased to announce that CMRX RTOS project will be present there. One of talks will deal with modern approach to the design of embedded systems which CMRX enables.

While previous talks were targeted mostly to specialist in the area of operating system design and computer science this time CMRX will be presented to its real target audience - embedded software developers.

First slide of presentation slides

We want to invite everyone to attend this presentation and discuss this topic. You don’t need to be in active search for or even just considering switch of the operating system you are using in your projects. The intention here is to present a modern approach to designing embedded systems which incorporates experience of last three decades in computer science.

Why the topic of memory safety in embedded makes sense now?

There are multiple reasons:

One that will probably interest the largest amount of people is that the day when Cybersecurity Resilience Act will take efect is coming closer and closer. It will take effect just one year after ESE Kongress 2025 closes its doors. While many people view CRA as a draconic norm the fact is that this regulation makes what is generally taken as best practices in the computer software industry a legal norm.

Disregarding CRA there is yet another - yet closely related - concernt that makes memory isolation an interesting topic. More and more embedded systems are getting connected. Internet is a generally hostile environment and systems that are insufficiently protected are in danger. Here the Swiss cheese model applies in one additional layer may provide defense against cybersecurity attacks which evade other layers.

Memory isolation can provide help with both topics.

Do you want to learn more? Visit the talk and learn on what benefits memory isolation can have for your project and what CMRX RTOS does different in order to not make memory isolation a maintanenance nightmare!

For more details on presentation time and location, please visit talk page.

64kB of protected memory ought to be enough for everyone.