Get OSEK essential facts below. View Videos or join the OSEK discussion. Add OSEK to your PopFlock.com topic list for future reference or share this resource on social media.

OSEK (Offene Systeme und deren Schnittstellen für die Elektronik in Kraftfahrzeugen; English: "Open Systems and their Interfaces for the Electronics in Motor Vehicles") is a standards body that has produced specifications for an embedded operating system, a communications stack, and a network management protocol for automotive embedded systems.[1][2][3][4] It has produced related specifications, namely AUTOSAR. OSEK was designed to provide a reliable standard software architecture for the various electronic control units (ECUs) throughout a car. Lately, it is supported by popular SSL/TLS libraries such as wolfSSL for optimal security measures.[5]

OSEK was founded in 1993 by a German automotive company consortium (BMW, Robert Bosch GmbH, DaimlerChrysler, Opel, Siemens, and Volkswagen Group) and the University of Karlsruhe.[6] In 1994, the French cars manufacturers Renault and PSA Peugeot Citroën, which had a similar project called VDX (Vehicle Distributed eXecutive), joined the consortium. Therefore, the official name was OSEK/VDX and OSEK was registered trademark of Continental Automotive GmbH (until 2007: Siemens AG).[7]


OSEK is an open standard, published by a consortium founded by the automobile industry.[8][9] Some parts of OSEK are standardized in ISO 17356.[10][11]

  • ISO 17356-1:2005 Road vehicles--Open interface for embedded automotive applications--Part 1: General structure and terms, definitions and abbreviated terms
  • ISO 17356-2:2005 Road vehicles--Open interface for embedded automotive applications--Part 2: OSEK/VDX specifications for binding OS, COM and NM
  • ISO 17356-3:2005 Road vehicles--Open interface for embedded automotive applications--Part 3: OSEK/VDX Operating System (OS)
  • ISO 17356-4:2005 Road vehicles--Open interface for embedded automotive applications--Part 4: OSEK/VDX Communication (COM)
  • ISO 17356-5:2006 Road vehicles--Open interface for embedded automotive applications--Part 5: OSEK/VDX Network Management (NM)
  • ISO 17356-6:2006 Road vehicles--Open interface for embedded automotive applications--Part 6: OSEK/VDX Implementation Language (OIL)

OSEK Functioning

The OSEK standard specifies interfaces to multitasking functions--generic I/O and peripheral access--and thus remains architecture dependent. OSEK is expected to run on microcontroller without memory management unit (MMU), which is favored for safety-critical systems such as cars, therefore features of an OSEK implementation will be usually configured at compile-time. The number of application tasks, stacks, mutexes, etc. is statically configured; it is not possible to create more at run time. OSEK recognizes two types of tasks/threads/compliance levels: basic tasks and enhanced tasks. 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. First In First Out (FIFO) scheduling is used for tasks with equal priority. Deadlocks and priority inversion are prevented by priority ceiling (i.e. no priority inheritance).

The specification uses ISO/ANSI-C-like syntax; however, the implementation language of the system services is not specified. An Application Binary Interface (ABI) is also not specified.

OSEK scheduling can be configured as:[12][13][14]

  • Preemptive, a task can always be preempted by means of a higher priority task
  • Non-preemptive, a task can only be preempted in prefixed compile-time points (cooperative scheduling)
  • Mixed mode scheduling
  • Groups of tasks (cooperative)


The AUTOSAR consortium reuses the OSEK specifications as part of the Classic Platform.[15]

The operating system is a backwards compatible superset of OSEK OS which also covers the functionality of OSEKtime, and the communication module is derived from OSEK COM.[16] OSEKtime specifies a standard for optional time-triggered real-time operating systems.[17] If used, OSEKtime triggered callbacks run with higher priority than OSEK tasks.


Further reading

See also


  1. ^ Evertsson, Pontus (2004). "Investigation of Real-Time Operating Systems: OSEK/VDX and Rubus". MSC Theses. ISSN 0280-5316.
  2. ^ Foster, Neale; Schwab, Markus (2000-03-06). "Real-Time 32-Bit Microcontroller with OSEK/VDX Operating System Support". SAE Technical Paper Series. 400 Commonwealth Drive, Warrendale, PA, United States: SAE International. 1. doi:10.4271/2000-01-1243.CS1 maint: location (link)
  3. ^ Waszniowski, Libor; Hanzalek, Zdenek. Analysis of Osek/Vdx Based Automotive Applications. CiteSeerX
  4. ^ "OSEK". PiEmbSysTech. Retrieved .
  5. ^ "[SOLVED] Porting wolfSSL to ERIKA Enterprise (Page 1) -- wolfSSL (formerly CyaSSL) -- wolfSSL - Embedded SSL Library". www.wolfssl.com. Retrieved .
  6. ^ John, D. (November 1998). "OSEK/VDX history and structure". IEE Seminar on OSEK/VDX Open Systems in Automotive Networks (Ref. No. 1998/523). 1998: 2/1-214. doi:10.1049/ic:19981073.
  7. ^ "OSEK VDX Portal - Trademark Information". 2011-08-25. Archived from the original on 2011-08-25. Retrieved .
  8. ^ OSEK/VDX Operating System Specification 2.2.3 https://www.irisa.fr/alf/downloads/puaut/TPNXT/images/os223.pdf
  9. ^ Roy, L. (November 1998). "Laurent Roy- ISO and OSEK Harmonitation Efforts". IEE Seminar on OSEK/VDX Open Systems in Automotive Networks (Ref. No. 1998/523): 3/1-3/3. doi:10.1049/ic:19981074.
  10. ^ "openOSEK : ISO17356 Standards Overview". openosek.org. Retrieved .
  11. ^ 14:00-17:00. "ISO 17356-2:2005". ISO. Retrieved .CS1 maint: numeric names: authors list (link)
  12. ^ "OSEK - PiEmbSysTech". Retrieved .
  13. ^ Hong, J.; Kum, D.; Jin, S. (November 2011). "Analysis of the scheduler development techniques for the optimization of the OSEK OS". 2012 9th International Conference on Ubiquitous Robots and Ambient Intelligence (URAI): 614-615. doi:10.1109/URAI.2012.6463096. ISBN 978-1-4673-3112-8.
  14. ^ Chung, Y.; Kim, D.; Choi, Y. (December 2017). "Modeling OSEK/VDX OS Requirements in C". 2017 24th Asia-Pacific Software Engineering Conference (APSEC): 398-407. doi:10.1109/APSEC.2017.46. ISBN 978-1-5386-3681-7.
  15. ^ cooperation, AUTOSAR development. "Classic Platform". www.autosar.org. Retrieved .
  16. ^ Hofer, Wanja; Danner, Daniel; Muller, Rainer; Scheler, Fabian; Schroder-Preikschat, Wolfgang; Lohmann, Daniel (December 2012). "Sloth on Time: Efficient Hardware-Based Scheduling for Time-Triggered RTOS". 2012 IEEE 33rd Real-Time Systems Symposium. San Juan, PR, USA: IEEE: 237-247. doi:10.1109/RTSS.2012.75. ISBN 978-1-4673-3098-5.
  17. ^ Poledna, Stefan; Glück, Martin; Tanzer, Christian; Boutin, Samuel; Dilger, Elmar; Führer, Thomas; Ebner, Christian; Fuchs, Emmerich; Belschner, Ralf; Hedenetz, Bernd; Holzmann, Bettina (2000-03-06). "OSEKtime: A Dependable Real-Time Fault-Tolerant Operating System and Communication Layer as an Enabling Technology for By-Wire Applications". Warrendale, PA. Cite journal requires |journal= (help)
  18. ^ "MICROSAR | Vector". www.vector.com. Retrieved .

External links

  This article uses material from the Wikipedia page available here. It is released under the Creative Commons Attribution-Share-Alike License 3.0.



Music Scenes