OSEK

Source: Wikipedia, the free encyclopedia.

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.

OSEK was founded in 1993 by a German automotive company consortium (

Siemens AG).[7]

Standards

OSEK is an

automobile industry.[8][9][10] Some parts of OSEK are standardized in ISO 17356.[11][12]

  • 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)

before ISO

OSEK VDX Portal[13]

  • OSEK/VDX Operating system(OS) : "event-triggered" Real-time kernel
  • OSEK/VDX Communication(COM) : Application level communication protocol
  • OSEK/VDX Newark Management(NM) : Network management
  • OSEK/VDX OSEK Implementation Language(OIL) : Offline application description and configuration language
  • OSEK/VDX OSEK RTI(ORTI) : Debugging interface
  • OSEK/VDX Binding Specification: Binding document
  • MODISTARC
    • OSEK/VDX Conformance Testing Methodology
    • OSEK/VDX Operating System Test Plan
    • OSEK/VDX Operating System Test Procedure
    • OSEK/VDX Communication Test Plan
    • OSEK/VDX Communication Test Procedure
    • OSEK/VDX Communication Test Suites
    • OSEK/VDX Network Management Test Plan
    • OSEK/VDX Network Management Test Procedure
    • OSEK/VDX direct Network Management Test Suites
    • OSEK/VDX indirect Network Management Test Suites

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

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:[14][15][16]

  • 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)

State of the art

AUTOSAR

Currently the AUTOSAR consortium reuses the OSEK specifications as part of the Classic Platform.[17]

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.[18] OSEKtime specifies a standard for optional time-triggered real-time operating systems.[19] 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[20] or in relation to the compatibility between OSEK and AUTOSAR.[21]

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.[22][23]

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)[24]
  • EB tresos Safety OS[25]
  • EB tresos AutoCore OS
 Proprietary Infineon AURIX TC38XQ, etc. Former product names: ProOSEK and ProOSEK/time by 3SOFT (3SOFT was purchased by Elektrobit)
ERIKA Enterprise[26]
  • ERIKA v2[27]
  • ERIKA v3
GPL or GPL linking exception or Commercial[28]
 ARM Cortex, Intel x86, Infineon AURIX, etc.[29] Officially certified on ARM Cortex-M4 and Infineon TriCore AURIX
Robert Bosch GmbH)[30]
  • RTA-OS
  • RTA-OSEK
 Proprietary Various architectures
NXP Semiconductors (former Freescale)
  • AUTOSAR 3.0, 4.0, 4.2, 4.3
 Proprietary PowerPC 5xxx (e. g. e200), S12/S32, etc.[31] Former product names: OSEKturbo
Siemens (through acquisition of Mentor Graphics's Automotive arm)
  • Capital VSTAR OS[32]
 Proprietary Various architectures
Vector Informatik
  • MICROSAR.OS[33]
  • MICROSAR Safe
 Proprietary Various architectures Supporting 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

  • Berkely EE249 on OSEK (Presentation in PDF formatting)
  • Christian Michel Sendis. OSEK/RTOS & OSEKturbo Introduction (PDF, March 2009, NXP Semiconductors)
  • Lemieux, Joseph (2001). Programming in the OSEK/VDX environment. Lawrence, Kan.: CMP Books.
    OCLC 171039798
    .

See also

References

  1. ISSN 0280-5316
    .
  2. doi:10.4271/2000-01-1243
    .
  3. CiteSeerX 10.1.1.67.6507
    .
  4. ^ "OSEK". PiEmbSysTech. Retrieved 2021-03-08.
  5. doi:10.1049/ic:19981073
    .
  6. OCLC 906179237.{{cite book}}: CS1 maint: location missing publisher (link) CS1 maint: others (link
    )
  7. ^ "OSEK VDX Portal - Trademark Information". 2011-08-25. Archived from the original on 2011-08-25. Retrieved 2021-03-08.
  8. ^ OSEK/VDX Operating System Specification 2.2.3 https://www.irisa.fr/alf/downloads/puaut/TPNXT/images/os223.pdf
  9. doi:10.1049/ic:19981074
    .
  10. OCLC 759826017.{{cite book}}: CS1 maint: multiple names: authors list (link) CS1 maint: numeric names: authors list (link
    )
  11. ^ "openOSEK : ISO17356 Standards Overview". openosek.org. Retrieved 2021-03-08.
  12. ^ "ISO 17356-2:2005". ISO. Retrieved 2021-03-08.
  13. ^ "OSEK VDX Portal - Deprecated Specification". portal.osek-vdx.org. Archived from the original on 24 August 2011. Retrieved 12 January 2022.
  14. ^ "OSEK – PiEmbSysTech". Retrieved 2021-04-05.
  15. S2CID 17396815
    .
  16. S2CID 3709038
    .
  17. ^ "Classic Platform". www.autosar.org. Retrieved 2021-03-08.
  18. S2CID 12499184
    .
  19. doi:10.4271/2000-01-1051.{{cite book}}: CS1 maint: location missing publisher (link
    )
  20. S2CID 17490657
    .
  21. ISBN 978-3-642-33829-8
    .
  22. doi:10.1184/R1/6582899.V1. {{cite journal}}: Cite journal requires |journal= (help
    )
  23. ^ "Real-Time Application Development with OSEK: A Review of the OSEK Standards". resources.sei.cmu.edu. 31 October 2003. Retrieved 2021-10-05.
  24. ^ "EB tresos BSW". Elektrobit. Retrieved 2021-10-05.
  25. ^ "EB tresos operating systems". Elektrobit. Retrieved 2021-10-07.
  26. ^ "Erika Enterprise RTOS v3". Erika3. 2021-07-29. Retrieved 2021-10-05.
  27. ^ "v2 vs v3". Erika3. 2021-07-29. Retrieved 2021-10-07.
  28. ^ "Licensing". Erika3. 2021-07-29. Retrieved 2021-10-07.
  29. ^ "Supported architectures". Erika3. 2021-07-29. Retrieved 2021-10-07.
  30. ^ "RTA-OS". www.etas.com. Retrieved 2021-10-05.
  31. ^ "AUTOSAR Software Architecture | NXP Semiconductors". www.nxp.com. Retrieved 2021-10-07.
  32. ^ "Streamlined ECU software development". Siemens Digital Industries Software. Retrieved 2021-10-07.
  33. ^ "MICROSAR | Vector". www.vector.com. Retrieved 2021-10-07.
  34. ^ "AUTOSAR tools and software for the automotive industry - ARCCORE". www.arccore.com. Retrieved 2021-10-05.
  35. ^ "Proyecto CIAA". www.proyecto-ciaa.com.ar. Retrieved 2021-10-05.
  36. ^ "nxtOSEK/JSP: ANSI C/C++ with OSEK/μITRON RTOS for LEGO MINDSTORMS NXT". lejos-osek.sf.net. Retrieved 2021-10-05.
  37. ^ "TOPPERS Project／ATK1". www.toppers.jp. Retrieved 2021-10-05.
  38. ^ "TOPPERS Project／ATK2". www.toppers.jp. Retrieved 2021-10-07.
  39. ^ "Free OSEK real-time kernel for dsPIC | Microchip". www.microchip.com. Retrieved 2021-10-05.
  40. ^ "COMASSO". www.comasso.org. Retrieved 2021-10-05.

External links

Retrieved from "https://en.wikipedia.org/w/index.php?title=OSEK&oldid=1189878642"
This page is based on the copyrighted Wikipedia article: OSEK. Articles is available under the CC BY-SA 3.0 license; additional terms may apply.Privacy Policy