Osek Operating System Analysis

I. Introduction:
OSEK is basically a German Term which stands for “Open systems and the corresponding interfaces for the Automotive Electronics in Motor Vehicle Distributed” [1]. This source is available for everyone and produced specification for three main components which are Operating System (OS), Network Management (NM) and Communication for Automotive embedded systems to increase and improve the Software Portability and Reusability. This document only focuses on the OSEK operating system.
Today automotive vehicles have very strict real time requirements and to manage the complexity of electronic control units is very difficult as compared to previous 20 years ago that’s why we are using OSEK Operating system to achieve mandatory functionality
OSEK Operating System

1. Processing Levels:
OSEK operating system used for Real time executions of processes which are running in parallel and we want to control them. OSEK operating system allows a set of interfaces for the user. Entities used these interfaces for competing the Central Process Unit. There are two main types of entities which are given below:
• Interrupts Service Routine (ISR) Which is handled by Operating System
• Tasks (1st Basic Tasks & 2nd Extended Tasks)
Operating system services handled the hardware resources of the control unit. Unique interfaces or application program are used to summon these Operating system services.
OSEK explains three main processing levels:
• Interrupt level
• Logic level by scheduler
• Task Level
User assigned the priorities to schedule the tasks in the Task Level. The runtime context is active at the start of execution time and then enable again when the running task is complete.

Figure 1: Processing Level of the OSEK Operating System [1] Following are the
There are two types of alarms single alarm or cyclic alarm. It doesn’t provide any standardized API. First we defined the counter value for the event or call back routine, when the counter reached to that value alarm will become expire and do that event which have to be done.

6. Conclusion:
OSEK OS is a firm real-time operating system with flexible abilities. It provides scheduler which organizes the tasks and interrupts in a better way. To avoid the deadlock and priority inversion, it made critical section. It gives the opportunity for triggering the task with respect to specific time. It also supports debugging. Cost is very important now days so it is used to reduce the cost of new hardware and also have the ability of the code reuse. Vastly used in Safety critical domain because of the stringent timing requirement. The maintenance is very cheap and has shorter development time.
It does not provide any graphics and file systems. It is used only for single core processors; it doesn’t support multi core processors, still working on it. It doesn’t contain any memory protection. OSEK don’t have any capability to produce any new