OSEK explained

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] 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.

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.[4] [5] 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).[6]

Standards

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

before ISO

OSEK VDX Portal[12]

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-OS scheduling can be configured as:[13] [14]

State of the art

AUTOSAR

Currently 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.

Research

There is also a limited amount of active research, e. g. in the area of systems engineering and OSEK / VDX RTOS[18] or in relation to the compatibility between OSEK and AUTOSAR.[19]

Quality

In a 48-page report from 2003 by the Software Engineering Institute (SEI) at Carnegie Mellon University (CMU), the specifications were examined and possible weaknesses in the areas of alarm and event mechanisms were identified with possible solutions. The potential of OSEK was also mentioned.[20] [21]

Implementations

Note: A limited number of implementations and vendors exist. Most products are only commercially sold and licensed, others are freely available with open-source license for a limited number of controllers. See also: Comparison of real-time operating systems.

Table of OSEK / AUTOSAR implementations!Vendor!Products!License!Targets!Other information
Elektrobit Automotive GmbH (part of Continental AG)[22]
  • EB tresos Safety OS[23]
  • EB tresos AutoCore OS
Infineon AURIX TC38XQ, etc.Former product names: ProOSEK and ProOSEK/time by 3SOFT (3SOFT was purchased by Elektrobit)
ERIKA Enterprise[24]
  • ERIKA v2[25]
  • ERIKA v3
[26] ARM Cortex, Intel x86, Infineon AURIX, etc.[27] Officially certified on ARM Cortex-M4 and Infineon TriCore AURIX
ETAS Group (part of Robert Bosch GmbH)[28]
  • RTA-OS
  • RTA-OSEK
Various architectures
NXP Semiconductors (former Freescale)
  • AUTOSAR 3.0, 4.0, 4.2, 4.3
PowerPC 5xxx (e. g. e200), S12/S32, etc.[29] Former product names: OSEKturbo
Siemens (through acquisition of Mentor Graphics's Automotive arm)
  • Capital VSTAR OS[30]
Various architectures
Vector Informatik
  • MICROSAR.OS[31]
  • MICROSAR Safe
Various architecturesSupporting software: DaVinci Configurator Pro

Open-source derivates

Note: Open-source developments are often very limited in scope (targets, conformance classes, characteristics) and are not verified against the specifications unless told otherwise.

Defunct, not active, unknown status

Further reading

See also

External links

Notes and References

  1. Evertsson. Pontus. 2004. Investigation of Real-Time Operating Systems: OSEK/VDX and Rubus. MSC Theses. 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. 1. Warrendale, PA. SAE International. 10.4271/2000-01-1243.
  3. Book: Waszniowski. Libor. Analysis of Osek/Vdx Based Automotive Applications. Hanzalek. Zdenek. 10.1.1.67.6507.
  4. Book: John, D.. IEE Seminar OSEK/VDX Open Systems in Automotive Networks . OSEK/VDX history and structure . November 1998 . https://ieeexplore.ieee.org/document/744162 . 1998. 2/1–214. 10.1049/ic:19981073.
  5. Book: Handbuch Fahrerassistenzsysteme Grundlagen, Komponenten und Systeme für aktive Sicherheit und Komfort. 2015. Hermann Winner, Stephan Hakuli, Felix Lotz, Christina Singer. 978-3-658-05734-3. 3., überarb. u. erg. Aufl. 2015. Wiesbaden. 115 ff. 906179237.
  6. Web site: 2011-08-25. OSEK VDX Portal - Trademark Information. 2021-03-08. https://web.archive.org/web/20110825000901/http://portal.osek-vdx.org/index.php?option=com_content&task=view&id=6&Itemid=9. 2011-08-25.
  7. OSEK/VDX Operating System Specification 2.2.3 https://www.irisa.fr/alf/downloads/puaut/TPNXT/images/os223.pdf
  8. Book: Roy, L.. IEE Seminar OSEK/VDX Open Systems in Automotive Networks . ISO and OSEK harmonisation efforts . November 1998 . 1998 . https://ieeexplore.ieee.org/document/744163 . 3/1–3/3. 10.1049/ic:19981074.
  9. Book: Herausgeber, Winner, Hermann 1955- Herausgeber Hakuli, Stephan Herausgeber Wolf, Gabriele. Handbuch Fahrerassistenzsysteme Grundlagen, Komponenten und Systeme für aktive Sicherheit und Komfort ; mit 45 Tabellen. 7 October 2011. Vieweg+Teubner Verlag . 978-3-8348-1457-9. 759826017.
  10. Web site: openOSEK : ISO17356 Standards Overview. 2021-03-08. openosek.org.
  11. Web site: ISO 17356-2:2005. 2021-03-08. ISO. en.
  12. Web site: OSEK VDX Portal - Deprecated Specification . portal.osek-vdx.org . 12 January 2022 . https://web.archive.org/web/20110824235904/http://portal.osek-vdx.org/index.php?option=com_content&task=view&id=11&Itemid=14 . 24 August 2011 . dead.
  13. Book: Hong. J.. Kum. D.. Jin. S.. 2012 9th International Conference on Ubiquitous Robots and Ambient Intelligence (URAI) . Analysis of the scheduler development techniques for the optimization of the OSEK OS . November 2011. https://ieeexplore.ieee.org/document/6463096. 614–615. 10.1109/URAI.2012.6463096. 978-1-4673-3112-8. 17396815.
  14. Book: Chung. Y.. Kim. D.. Choi. Y.. 2017 24th Asia-Pacific Software Engineering Conference (APSEC) . Modeling OSEK/VDX OS Requirements in C . December 2017. https://ieeexplore.ieee.org/document/8305962. 398–407. 10.1109/APSEC.2017.46. 978-1-5386-3681-7. 3709038.
  15. Web site: Classic Platform. 2021-03-08. www.autosar.org. en.
  16. Book: Hofer. Wanja. Danner. Daniel. Muller. Rainer. Scheler. Fabian. Schroder-Preikschat. Wolfgang. Lohmann. Daniel. 2012 IEEE 33rd Real-Time Systems Symposium . Sloth on Time: Efficient Hardware-Based Scheduling for Time-Triggered RTOS . December 2012. https://ieeexplore.ieee.org/document/6424807. San Juan, PR, USA. IEEE. 237–247. 10.1109/RTSS.2012.75. 978-1-4673-3098-5. 12499184.
  17. Book: Poledna. Stefan. Glück. Martin. Tanzer. Christian. Boutin. Samuel. Dilger. Elmar. Führer. Thomas. Ebner. Christian. Fuchs. Emmerich. Belschner. Ralf. Hedenetz. Bernd. Holzmann. Bettina. SAE Technical Paper Series. 2000-03-06. OSEKtime: A Dependable Real-Time Fault-Tolerant Operating System and Communication Layer as an Enabling Technology for By-Wire Applications. 1. https://www.sae.org/publications/technical-papers/content/2000-01-1051/. English. Warrendale, PA. 10.4271/2000-01-1051.
  18. Macher. Georg. Atas. Muesluem. Armengaud. Eric. Kreiner. Christian. 2015-01-22. Automotive real-time operating systems: a model-based configuration approach. ACM SIGBED Review. en. 11. 4. 67–72. 10.1145/2724942.2724953. 17490657. 1551-3688.
  19. Book: Lee. Y. H.. Kim. Jin Ho. Jeon. Jae Wook. Proceedings of the FISITA 2012 World Automotive Congress . Applying AUTOSAR Network Management in OSEK/VDX for Compatibility of AUTOSAR and OSEK/VDX . 2013. https://link.springer.com/chapter/10.1007%2F978-3-642-33829-8_65. Lecture Notes in Electrical Engineering. 194. en. Berlin, Heidelberg. Springer. 693–704. 10.1007/978-3-642-33829-8_65. 978-3-642-33829-8.
  20. Feiler. Peter H.. 2018. Real-Time Application Development with OSEK: A Review of the OSEK Standards. 168866 Bytes. 10.1184/R1/6582899.V1.
  21. Web site: Real-Time Application Development with OSEK: A Review of the OSEK Standards. 2021-10-05. resources.sei.cmu.edu. 31 October 2003 . en.
  22. Web site: EB tresos BSW. 2021-10-05. Elektrobit. en-US.
  23. Web site: EB tresos operating systems. 2021-10-07. Elektrobit. en-US.
  24. Web site: 2021-07-29. Erika Enterprise RTOS v3. 2021-10-05. Erika3. en-US.
  25. Web site: 2021-07-29. v2 vs v3. 2021-10-07. Erika3. en-US.
  26. Web site: 2021-07-29. Licensing. 2021-10-07. Erika3. en-US.
  27. Web site: 2021-07-29. Supported architectures. 2021-10-07. Erika3. en-US.
  28. Web site: RTA-OS. 2021-10-05. www.etas.com. en.
  29. Web site: AUTOSAR Software Architecture NXP Semiconductors. 2021-10-07. www.nxp.com.
  30. Web site: Streamlined ECU software development. 2021-10-07. Siemens Digital Industries Software.
  31. Web site: MICROSAR Vector. 2021-10-07. www.vector.com. en.
  32. Web site: AUTOSAR tools and software for the automotive industry - ARCCORE. 2021-10-05. www.arccore.com.
  33. Web site: Proyecto CIAA. 2021-10-05. www.proyecto-ciaa.com.ar.
  34. Web site: nxtOSEK/JSP: ANSI C/C++ with OSEK/μITRON RTOS for LEGO MINDSTORMS NXT. 2021-10-05. lejos-osek.sf.net.
  35. Web site: TOPPERS Project/ATK1. 2021-10-05. www.toppers.jp.
  36. Web site: TOPPERS Project/ATK2. 2021-10-07. www.toppers.jp.
  37. Web site: Free OSEK real-time kernel for dsPIC Microchip. 2021-10-05. www.microchip.com.
  38. Web site: COMASSO. 2021-10-05. www.comasso.org.