What is the difference between OSEK and autosar?

The main difference of the two NMs is the different means of message timeout. OSEK NM interprets message timeout as a device error, but AUTOSAR NM interprets message timeout as requesting Bus Sleep Mode.


RTA-OS and RTA-OSEK are commercial implementations by ETAS of an OSEK RTOS with support for a broad range of micro-controllers, including Linux and Windows PC (Unknown license).

Is autosar an OS?

To support dynamic deployment of customer applications and to provide an environment for applications that require high-end computing power AUTOSAR is currently standardizing the AUTOSAR Adaptive Platform. Its core is an operating system based on the POSIX standard.

What is OS application in autosar?

OSEK OS is an event-triggered operating system. Event triggering gives freedom for the selection of the events to drive scheduling at run-time, for example angular rotation, local time source, global time source, error occurrence etc. For these reasons the core functionality of the AUTOSAR OS was derived from OSEK OS.

What does OSEK stand for?

OSEK is an abbreviation for a German term that translates to “open systems and the corresponding interfaces for automotive electronics.” OSEK OS is the operating system specification and OSEK COM is the communication specification.

What is OSEK NM?

The open system and corresponding interfaces for automotive electronics/vehicle distributed executive (OSEK/VDX) set a goal of being the industry standard for real-time operating systems used in vehicle systems. OSEK/VDX includes a reliable network management algorithm, OSEK network management (OSEK NM).


A standardized interface is an interface which is predefined by the AUTOSAR standard as an API in the C language. It is used between BSW modules in an ECU, between the RTE and the operating system or between the RTE and the BSW module Com.

CAN transceiver AUTOSAR?

The CAN Transceiver Driver module is responsible for handling the CAN transceiver hardware chips on an ECU. The CAN Transceiver is a hardware device, which adapts the signal levels that are used on the CAN bus to the logical (digital) signal levels recognised by a microcon- troller.

What is RTE autosar?

The AUTOSAR Runtime Environment (RTE) is the central connecting element in an AUTOSAR ECU architecture. It realizes the interfaces as provided by the VFB ( it actually allocates the memory, specifies the ports etc) in order to enable interaction between the software components.

Which layer does autosar operating system belongs to?

The RTE is a layer providing communication services to the application software (AUTOSAR Software Components and/or AUTOSAR Sensor/Actuator components).

How does OSEK OS support concepts in AUTOSAR?

In particular OSEK OS provides the following features to support concepts in AUTOSAR: OSEK OS provides many features in addition to these. Readers should consult the OSEK specification for details. OsApplication are used, all OsTasks, OsIsrs, OsCounters, OsAlarms and OsScheduleTables must belong to an OsApplication.

What does Osek stand for in automotive category?

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.

Which is a backwards compatible version of Osek?

The AUTOSAR consortium reuses the OSEK specifications as part of the Classic Platform. 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. OSEKtime specifies a standard for optional time-triggered real-time operating systems.

Which is the specification of the operating system AUTOSAR?

Specification of Operating System AUTOSAR Release 4.2.2 1 of 247 Document ID 034: AUTOSAR_SWS_OS – AUTOSAR confidential – Document Change History Release Changed by Change Description