Top Qs
Timeline
Chat
Perspective

OSEK

Specifications for embedded operating systems within automotives From Wikipedia, the free encyclopedia

Remove ads

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]

Remove ads

Standards

Summarize
Perspective

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]

  • 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[12]

  • 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
Remove ads

OSEK Functioning

Summarize
Perspective

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]

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

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

Summarize
Perspective

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.

More information Vendor, Products ...

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

Remove ads

Further reading

  • Berkely EE249 on OSEK (Presentation in PDF formatting)
  • Christian Michel Sendis. OSEK/RTOS & OSEKturbo Introduction Archived 2021-05-18 at the Wayback Machine (PDF, March 2009, NXP Semiconductors)
  • Lemieux, Joseph (2001). Programming in the OSEK/VDX environment. Lawrence, Kan.: CMP Books. ISBN 978-0-08-052218-0. OCLC 171039798.

See also

References

External links

Loading related searches...

Wikiwand - on

Seamless Wikipedia browsing. On steroids.

Remove ads
Remove ads