REFLEX is a generic event driven OS for embedded devices.

Most embedded devices are used to control more or less complicated processes in the real world. Therefore the operating systems on those devices do not need to be general purpose systems. Other requirements rule that world, namely a small memory footprint, robustness, real-time capabilities and of course resource consumption.

REFLEX is a generic event driven OS for embedded devices. Event handlers and control functions are all represented as passive objects that are scheduled according to a configurable scheduling strategy. All sensors, control functions and actuators of a typical embedded control system are represented by objects that can communicate with each other by means of events.

Synchronization and scheduling of events is based on an event flow model that is in principle very similar to the  data flow paradigm. The implementation of control systems that are given as state machines or SDL-graphs is therefore particularly easy. Consequently, we are working towards a high-level tool chain that links typical modeling tools to a REFLEX runtime platform.

REFLEX has a small memory footprint (only a few KB of RAM for complete control applications) and is entirely implemented in standard C++. RFLEX has been ported so far to several CPU types including Motorola HCS12, Atmel ATmega128, Hitachi H8/300 and Texas Instruments MSP430.

REFLEX will serve as the basic OS in the Cocos project.

The project website is located at .


These contents are currently under construction. A complete list of all publications can be found in the publication area.

This website uses cookies. Those have two functions: On the one hand they are providing basic functionality for this website. On the other hand they allow us to improve our content for you by saving and analyzing anonymized user data. You can redraw your consent to using these cookies at any time. Find more information regarding cookies on our Data Protection Declaration and regarding us on the Imprint.


These cookies are needed for a smooth operation of our website.


Name Purpose Lifetime Type Provider
_pk_id Used to store a few details about the user such as the unique visitor ID. 13 months HTML Matomo
_pk_ref Used to store the attribution information, the referrer initially used to visit the website. 6 months HTML Matomo
_pk_ses Short lived cookie used to temporarily store data for the visit. 30 minutes HTML Matomo