Why Switch to an OSEK RTOS and How to Address the Associated Challenges 2005-01-0312
Most automotive software systems are still built today using a cyclical scheduler that runs tasks at fixed time intervals. This approach provides excellent insight into and control of the real-time behavior of a system, as tasks repeatedly run one at a time and in the same order.
Given that so many operating systems are using an approach that provides the necessary real-time control and transparency, why change to an OSEK operating system? In other words, what value does an OSEK operating system deliver compared to one that uses the traditional approach to task scheduling?
In this paper, we answer precisely that question. An OSEK OS can offer significant efficiency advantages that ultimately save cost in development and production. However, an organization faces certain challenges when it decides to replace its traditional OS with an OSEK OS. We identify and discuss these challenges.