What is OSEK
A specification for an RTOS
•With standard software interfaces (OS API)
•Including intertask & interprocessor communication (COM)
•Including network management (NM)
•Including the language used to statically declare OS elements used in an application – OSEK Implementation Language (OIL)
OSEK Components
OS
•base routines
•resource management
•event mechanisms
COM
•communication between tasks and applications
•hiding of physical network
NM
•network startup and shutdown
•monitoring of network nodes
OIL
•language used to statically define the OS elements used in an application
OSEK-OS Philosophy
Support for event-driven control systems
Software supplied by various manufacturers
Need to support different control units
•Hardware independent
•Flexible configuration
Maximum production performance
•No memory management etc.
Reliable
•Static
OSEK OS characteristics
The OSEK Operating System:
•is a static OS
•specifies different kinds of scalability
•has only one small interface (API)
•has no memory management (malloc(), etc.)
•defines no I/O model
OSEK OS Overview
OSEK provides a simple API
•34 functions described
Data types are specified for platform independence
The developer can select from a choice of scheduling policies
The following elements are implemented:
•Tasks
•Interrupts
•Events
•Counters
•Alarms
•Resources
•Hooks
Advantages of OSEK
Reduced cost and development time
Enhanced software quality & re-use
Provides standardized interfaces( For processors with different architectures )
Utilization of existing resources
Cost-effective development tools
Ultimately allows the developer to concentrate on application development - the value component
