The document discusses the OSEK/VDX standard which defines interfaces and protocols for automotive embedded systems to enable portability, reusability, and extensibility of software. It provides an overview of the OSEK/VDX operating system including the task concept, scheduler, events, alarms, resources, and interrupt processing. The OSEK/VDX standard aims to improve quality and reduce costs for automotive embedded control software.

1. ©
OSEK / VDX

2. ©
OSEK / VDX > Agenda
OSEK/VDX Standard - Overview
OSEK/VDX Operating System – Overview (Task Concept, Scheduler, Events)

3. ©
OSEK/VDX > What is OSEK/VDX?
• Joint project of the European automotive industry
 Target: Define an industry standard for an open-ended
architecture for distributed control units in vehicles.
• Founded 1993
 OSEK: Offene Systeme und deren Schnittstellen für die
Elektronik im Kraftfahrzeug (“Open Systems and the
Corresponding Interfaces for Automotive Electronics”)
 VDX: Vehicle Distributed eXecutive
 Joined OSEK in 1994  OSEK/VDX

4. ©
OSEK/VDX > OSEK Specifications
OSEK OS
– serves as a basis for the controlled real-time execution of concurrent applications
OSEK OIL
– OIL provides a possibility to configure an OSEK/VDX application inside a particular CPU
OSEK COM / NM
– provides interfaces and protocols for the transfer of data within vehicle networks

5. ©
OSEK/VDX > Goals & Motivations
• Definition of standardized interfaces & protocols (HW & Network independent)
 Portability, Reusability & Extendibility of SW (through different HW platforms
& different applications)
 Possible "co-habitation" of software from different suppliers
 Independence regarding a particular implementation
• Definition of configurable & scalable functionalities
 Optimal adjustment of the architecture to a particular context (i.e. same
OSEK/VDX interfaces, but different implementations, depending on the hardware
architecture and the performance required)
 Quality improvement
 Savings in costs and development time

6. ©
OSEK/VDX > Automotive Embedded Control Software >
OSEK/VDX Architecture
Electronic Control Unit
Embedded Control Software
OSEK/VDX OS
IO
SW
OSEK/VDX COM
System Bus (e.g.
CAN)
Actuators
Sensors
OSEK/VD
X
NM
Function D
Function C
Function B
Function A

7. ©
OSEK/VDX > OSEK COM Architecture

8. ©
OSEK/VDX > Goals & Motivations > Reusability
OSEK/VDX COM
OSEK/VDX
NM
OSEK/VDX OS
OIL
HW Platform A
Application
Bus protocol x
OSEK/VDX COM
OSEK/VDX
NM
OSEK/VDX OS
OIL
HW Platform B
Bus protocol y
Application

9. ©
OSEK/VDX > Goals & Motivations > Distributed functions
OSEK/VDX COM
OSEK
/
VDX
NM
OSEK/VDX OS
HW Platform
A
B
C
OSEK/VDX COM
OSEK
/
VDX
NM
OSEK/VDX OS
HW Platform
OSEK/VDX COM
OSEK/VDX OS
HW Platform
OSEK/VDX COM
OSEK
/
VDX
NM
OSEK/VDX OS
HW Platform
OSEK
/
VDX
NM
B
C
A

10. ©
COUNTER
OSEK/VDX Operating System > Overview
ALARM
EVENT
HOOK
RESOURCE
TASK
ISR
MESSAGE
- Single processor operating system
 Implementations available for
8/16/32 bit µC
- Minimum ROM, RAM and CPU time
consumption
 Statically defined resources (tasks,
events, alarms, ...)
 Different levels of functionality
(conformance classes)
- Standardized operating system
behavior and interfaces for the
application
 Services defined according to the
ISO/ANSI-C syntax
 Independent from a specific µC

11. ©
OSEK/VDX Operating System > Conformance Classes
Four conformance classes in the one standard
– provides convenient groups of features to ease understanding
– enables partial implementations
– scalability
BCC: Basic tasks
ECC: Extended tasks
Level 1: One task per priority,
one activation per task
Level 2: More than one task
per priority and more than
one activation per task
Overheads
Features
BCC1
BCC2
ECC1
ECC2

12. ©
OSEK/VDX Operating System > Task management
Basic tasks only release the processor if
– they terminate, the OSEK OS switches to a higher priority task (preemption) or an
interrupt occurs
Extended tasks
– can also wait on events (WaitEvent API call)
Running
Ready
SuspendedWaiting
Wait
Release
Preempt
Start
Activate
Terminate

13. ©
OSEK/VDX Operating System > Scheduler
Scheduler
•The scheduler decides on the basis of the task priority which is the next
of the ready tasks to be transferred into the running state.
• A preempted task is considered to be the first (oldest) task in the ready list of
its current priority.
• A task being released from the waiting state is treated like the last (newest) task
in the ready queue of its priority.

14. ©
OSEK/VDX Operating System > Scheduler
The fundamental steps to determine the next task to be processed are:
• The scheduler searches for all tasks in the ready/running state.
• From the set of tasks in the ready/running state, the scheduler determines the set of
tasks with the highest priority.
• Within the set of tasks in the ready/running state and of highest priority, the scheduler
finds the oldest task.

15. ©
OSEK/VDX Operating System > Preemptive & Non-
Preemptive Scheduling
Preemptive Scheduling
Non- Preemptive Scheduling

16. ©
OSEK/VDX Operating System > Interrupt Processing
Two interrupt service routine categories
– Category 1:
• ISR does not use OS services
• ISR executes above the priority level of the scheduler
• No additional interrupt latency due to the OS
– Category 2:
• ISR can use OS services, e.g. activate tasks, etc.
• ISR executes under the control of the scheduler
• OS imposes some additional latency to set up the ISR
environment

17. ©
OSEK/VDX Operating System > Resource management
S1 ceiling = high
OSEK requires the use of the priority ceiling protocol for resource management:
– Priority inversion minimised
– Deadlock cannot occur
– Access to resource never results in a waiting state
– Can be analysed to enable real-time performance to be guaranteed

18. ©
OSEK/VDX Operating System > Priority Inversion

19. ©
OSEK/VDX Operating System > Deadlock

20. ©
OSEK/VDX Operating System > Solution for Priority
Inversion & Deadlock
1. Task T0 has the highest, and task T4 the lowest priority.
2. Task T1 and task T4 access the same standard resource.
3. Task T4 get the resource and raise its priority to the ceiling priority.
4. Task T0 preempts task T4 because its has a higher priority. When task T0 finishes, task T4 continues to
run and release the standard resource.
5. Task T1 which is ready to run get the resource and preempts task T4. Task T4 is put into ready state.
6. Task T1 finishes and release resource. Since task T2 and T3 are ready, task T4 must wait for task T2 and
T3 to complete before it can continues its tasks.

21. ©
OSEK/VDX Operating System > Alarms
Provides support for processing recurring events
– The recurring events (sources) are registered by implementation specific counters
– Based on the counters the OSEK OS provides alarm mechanisms to the application
developer
Counters provide a counter value measured in ‘ticks’
Alarms expire when a predefined counter value is reached, it can then:
– Activate a task
– Set an event

22. ©
OSEK/VDX Operating System > Hook Routines
StartupHook
• Called at OS startup, interrupt disabled
• Can be used for initialization purpose
ShutdownHook
• Called at OS shutdown, interrupt disabled
• Can be used for epilogue purpose
PreTaskHook
• Called when a task enters the running state of a task
• Not to be used due to CPU time consumption
PostTaskHook
• Called when a task exits the running state of a task
• Not to be used due to CPU time consumption