This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Why Switch to an OSEK RTOS and How to Address the Associated Challenges
Technical Paper
2005-01-0312
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
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.
Recommended Content
| Technical Paper | Why You Should Use Web Based Learning for CAD Training in Your Organization |
| Aerospace Standard | Maintainability Program Standard Implementation Guide |
| Aerospace Standard | Reliability Program Handbook |
Authors
Citation
Rolina, T. and Tracey, N., "Why Switch to an OSEK RTOS and How to Address the Associated Challenges," SAE Technical Paper 2005-01-0312, 2005, https://doi.org/10.4271/2005-01-0312.Also In
Automotive Electronics on CD-ROM from the SAE 2005 World Congress
Number: SP-1980CD; Published: 2005-04-11
Number: SP-1980CD; Published: 2005-04-11
References
- “Software as assets” fall 2004 Embedded computing design http://www.embeddedcomputing.com/articles/mellor/
- Deadline Monotonic Analysis http://www.embedded.com/2000/0006/0006feat1.htm
- OSEK-VDX http://www.osek-vdx.org