|Published (Last):||27 March 2014|
|PDF File Size:||19.67 Mb|
|ePub File Size:||14.90 Mb|
|Price:||Free* [*Free Regsitration Required]|
Standard[ edit ] OSEK is an open standard , published by a consortium founded by the automobile industry. OSEK systems are expected to run on chips without memory protection.
Features of an OSEK implementation can be usually configured at compile-time. The number of application tasks, stacks, mutexes , etc. Basic tasks never block; they "run to completion" coroutine. Enhanced tasks can sleep and block on event objects. The events can be triggered by other tasks basic and enhanced or interrupt routines. Only static priorities are allowed for tasks. Deadlocks and priority inversion are prevented by priority ceiling i. Comment - Two of the above claims are contradictory: 1.
It uses priority ceiling , which states: "The protocol works by temporarily raising the priorities of tasks in certain situations, thus it requires a scheduler that supports dynamic priority scheduling.
According to the German version of this entry, namely OSEK-OS , The scheduling can be configured in two different ways: In preemptive scheduling, a task can always be preempted by means of a higher priority task.
In non-preemptive scheduling, a task can only be preempted in prefixed compile-time points cooperative scheduling. A mixed mode is also possible. OSEKtime specifies a standard for optional time-triggered real-time operating systems.