MICROSAR - The Smart Implementation of the AUTOSAR Classic Standard

MICROSAR is the embedded software for your AUTOSAR Classic ECUs. It consists of the runtime environment MICROSAR.RTE and MICROSAR basic software modules (BSW). They cover the entire AUTOSAR Classic standard and contain a lot of useful extensions.

The uniform and intuitive user interface of DaVinci Configurator Pro is used to configure the MICROSAR modules. This tool includes helpful features like automatic derivation of parameters and extensive validation functions.

Supports many different data formats such as AUTOSAR-XML, DBC, LDF, FIBEX, CDD, ODX

Mature, long-term and reliable solution from an AUTOSAR Premium Member

Detailed documentation is included in the software delivery

Gallery

Video: Variant Handling Using the Vector AUTOSAR Solution

Video: The Application Area of DaVinci Configurator Pro

MICROSAR Basic Software Modules

Application Areas

Solutions for All AUTOSAR ECU Projects

The basic software modules of the MICROSAR packages assure basic functionality of the ECU. They contain the implementations of AUTOSAR standard services you will need for your functional software. You are able to develop your functional software platform independently, because the AUTOSAR architecture follows a consistent strategy of hardware abstraction.

You can configure all necessary MICROSAR BSW modules based on your project requirements, and after generation you can integrate them with the functional software. This produces a complete set of ECU software. If the functional software consists of AUTOSAR-conformant SWCs, you will need a runtime environment (RTE). The MICROSAR.RTE implements communication between the SWCs and their access to data and services from the BSW modules. Along with managing the entire flow of events and information, the MICROSAR.RTE also assures consistency in the exchange of information and coordinates accesses across core or memory protection boundaries.

Functions

Numerous extensions make MICROSAR the ideal solution for all ECU projects. A detailed description is provided in the comprehensive MICROSAR Product Information.

For a short description of the different MICROSAR clusters please refer to the following tabs.

MICROSAR.OS

The Real-Time Operating System for the AUTOSAR Standard

MICROSAR.OS is a preemptive real-time multitasking operating system with optimized properties for use on microcontrollers. Vector’s many years of experience in developing operating systems and drivers for microcontrollers are bundled into this small, robust operating system core.

MICROSAR-OS is based on the AUTOSAR OS specification, an extension of the practice-proven OSEK/VDX-OS operating system standard. This standard was extended to include functions for time monitoring and memory protection. The implemented high resolution timer mechanism for example offers time resolutions of less than 1ms without increasing the interrupt load. Depending on the controller, this may enable resolutions into the microseconds range. MICROSAR.OS is fully conformant to the AUTOSAR OS specification and supports all scalability classes.

Afficher plus

MICROSAR.COM

AUTOSAR Basic Software Modules for Communication

The basic software modules (BSW) of MICROSAR.COM include AUTOSAR services for ECU communication. These services can support any number of communication channels. They are bus-independent and are needed in every communication stack. Per AUTOSAR architecture, they handle control and full integration in the ECU software of bus-specific communication modules for CAN, CAN-FD, J1939, FR, LIN and ETH.

Afficher plus

MICROSAR.CAN

AUTOSAR Basic Software Modules for CAN Communication

MICROSAR.CAN is used to handle communication in CAN networks. It is also well-suited as a foundation for calibration with XCP, gateways or re-programming. You can also extend MICROSAR.CAN with the optional J1939TP package to enable operation of an AUTOSAR ECU in a J1939 network. Support of CAN-FD up to 64 byte data with enhanced bandwidth. Available for many CAN-FD controllers.

Afficher plus

MICROSAR.FR

AUTOSAR Basic Software Modules for FlexRay Communication

MICROSAR.FR is used to handle communication in FlexRay networks including partial networking. Furthermore, it is ideal as a foundation for calibration with XCP, gateways or flashing.

Afficher plus

MICROSAR.LIN

AUTOSAR Basic Software Modules for LIN Communication

MICROSAR.LIN handles communication tasks for a LIN Master in a LIN network. In addition, it may be used as a foundation for gateways or re-programming.

Afficher plus

MICROSAR.ETH

AUTOSAR Basic Software Modules for Ethernet-Based Communication

The Internet Protocol and the higher level Transport Protocols UDP and TCP are very widely used standards for high speed data exchange over ethernet. The MICROSAR.ETH (ethernet) package contains the AUTOSAR BSW modules including a TCP/IP stack developed to an automotive standard for ethernet-based communication between ECUs. AUTOSAR 4.0 is the first version to specify ethernet as a network technology. In AUTOSAR 4.1, the specifications were substantially modified and extended. Further extensions, e.g. ethernet switch configuration and time synchronization between ECUs, are specified in AUTOSAR 4.2. The BSW modules of MICROSAR.ETH are available according to AUTOSAR 4.x and as a supplement to AUTOSAR 3.x.

Afficher plus

MICROSAR.CHARGE

Basic Software Modules for Communicating with External Infrastructure

Ethernet and the higher-level TCP/IP stack provide the basic technology needed to communicate with vehicle-external charging infrastructure. MICROSAR.CHARGE lets you perform intelligent charging of electric and hybrid vehicles at a suitable charging station. Supported are the standards

ISO 15118 and

DIN SPEC 70121

SAE J2847/2

You can use the modules of the MICROSAR.CHARGE package to also have your ECU communicate with a server via commonly used Internet protocols. If necessary, the communication may also be encrypted.

MICROSAR.CHARGE also supports the standards GB/T 27930 and CHAdeMO for China and Japan. These specify the DC charging and are based on communication via CAN.

Afficher plus

MICROSAR.AVB

Basic Software Modules for Audio/Video Communication via Ethernet

MICROSAR.AVB (Audio/Video Bridging) over Ethernet enables quick and reliable transport of audio/video data. The MICROSAR.AVB package contains various BSW modules which are overlaid on the Ethernet interface, e.g. from MICROSAR.ETH. The solution based on AUTOSAR 4.x supports vAVTP (Audio/Video Transport Protocol), vRTP (Transport Protocol for Real-Time Applications), vSRP (Stream Reservation Protocol), ETHTSYN (Time Synchronisation over Ethernet) and on request also BMCA (Best Master Clock Algorithm). This makes it possible to implement AVB end points as well as bridge functionality.

Afficher plus

MICROSAR.MEM

AUTOSAR Basic Software Modules for Memory Management

MICROSAR.MEM contains AUTOSAR services for reading, writing and erasing persistent application data in flash and/or EEPROM memories. This gives the functional software hardware-independent access to memory. The application does not need to know the specific type of memory that exists on the platform or whether this memory is internal to the controller or externally connected to it.

Afficher plus

MICROSAR.SYS

System-related Basic Software Modules for AUTOSAR

The system services in the MICROSAR.SYS basic software modules (BSW) cover an important part of your AUTOSAR ECU's basic functionality. They are called by the functional software (via the RTE) and the remaining BSW modules. The modules of MICROSAR.SYS offer all key functions for state handling of the ECU.

System services include power and mode management, control of all communication channels and partial networks, monitoring of individual software components (SWC) of the functional software and within AUTOSAR 3.x scheduling of all BSW modules.

Afficher plus

MICROSAR.DIAG

AUTOSAR-compatible diagnostic protocol implementation

MICROSAR.DIAG is the scalable and highly optimized implementation of the diagnostic protocols for enhanced diagnostics (UDS) and the various legislated diagnostic (OBD) according to the AUTOSAR standard. For enhanced diagnostics, Vector offers an UDS implementation based on ISO 14229 with OEM specific extensions to adapt the AUTOSAR standard to OEM individual diagnostic requirements. For ECUs without a special diagnostic specification, an OEM-independent bundle of MICROSAR.DIAG is available.

The diagnostic configuration workflow is optimized to the individual OEM specific workflows and supports various data formats e.g. CANdelaStudio documents, AUTOSAR Diagnostic Extract Template or ODX. Support for legislated OBD is an optional functionality of MICROSAR.DIAG. Common legislated emission diagnostic requirements of today and tomorrow are supported:

OBD-II according to SAE J1979 and CARB CCR1968.2

WWH-OBD based on EURO VI with ISO 27145

China 6 (Light Duty and Heavy Duty)

OBDonUDS based on SAE J1979-2 is planned, please ask us for further detail

If your ECU requires variants in the diagnostic configuration, MICROSAR.DIAG offers a high-performance solution for this. You can define up to 31 different parameterizations and store them in the ECU, in a resource-optimized way. This avoids redundancies in the ECU software, because identical interfaces to the same data, services and DTCs are combined in the generated diagnostic code. The diagnostic configuration workflow creates your diagnostic variants based on the provided input data.

Case Study vDes

Distribution of monitor functions for diagnostics on multiple controllers can be a challenging task. In our case study, we show you how the MICROSAR.DIAG module vDes can efficiently synchronize multiple fault memories across microcontroller boundaries.

MICROSAR.MCAL

AUTOSAR Driver for Control of Microcontroller Peripherals

MICROSAR.MCAL is a turnkey solution for driving your microcontroller peripherals. When switching to different hardware, it is not necessary to make changes to the functional software. You will only need to replace MICROSAR.MCAL to integrate the appropriate new drivers.

The MICROSAR.MCAL drivers perfectly fit to the overall MICROSAR bundle. Depending on the requirements of your application, you may use additional bundles (e.g. MICROSAR.CAN, MICROSAR.MEM, etc.) and thereby obtain a complete communications stack or memory management as an example.

Afficher plus

MICROSAR.EXT

AUTOSAR drivers for control of external devices

MICROSAR.EXT gives you a turnkey solution for driving your external peripheral devices. So, it is not necessary to modify the functional software when switching out external hardware. All you need to do is switch out the relevant drivers from MICROSAR.EXT. Depending on the requirements of your application, you can add other packages (e.g. MICROSAR.CAN, MICROSAR.MEM,etc.) for a complete communication stack or memory management per AUTOSAR specification.

Integration of External Functions of a Microcontroller with vSBC Driver for System Basis Chips

Read or Case Study to see why vSBC from Vector is the suitable driver for integrating external functions into an AUTOSAR project.

MICROSAR.IO

AUTOSAR Input-Output Hardware Abstraction

The cluster IO establishes a connection between the application (e.g. the SWCs) and the MCAL modules. This gives the application or SWC access to I/O ports, for example to read sensor data or steer actors.

Afficher plus

MICROSAR.RTE

The Optimized Run-Time Environment for Software Components per the AUTOSAR Standard

MICROSAR.RTE (Run Time Environment) is the scalable and highly optimized AUTOSAR run-time environment from Vector. The RTE is a module introduced by AUTOSAR that manages communication between the software components (SWCs). It assures consistency of the overall information flow and represents the interface between the functional software, basic software (BSW) and complex drivers (CDD).

When the functional software of an ECU is implemented by AUTOSAR-conformant SWCs, the user needs the RTE as a runtime environment. This modular layout of the ECU software offers the user maximum flexibility: SWCs that have been manually developed or designed by model-based tools can be re-used in multiple ECU projects. The RTE only needs to be reconfigured and regenerated for the specific ECU and, if applicable, the BSW modules. It is also possible to use a SWC in multiple instances on one ECU.

Afficher plus

MICROSAR.AMD

AUTOSAR Monitoring and Debugging

The MICROSAR.AMD package efficiently supports you in testing your AUTOSAR ECU software. The basic software modules from MICROSAR.AMD have access to all important internal variables, states and error messages of your MICROSAR basic software. The XCP protocol (Universal Calibration Protocol) – familiar from the measurement and calibration field – is best suited for transferring ECU-internal parameters. Therefore, Vector decided to develop MICROSAR.AMD based on XCP.

Afficher plus

MICROSAR.XCP

Measurement and Calibration

MICROSAR.XCP enables measuring and calibrating according to ASAM XCP. It allows address-based read and write access to ECU memory. The module was especially optimized for use together with CANoe.XCP and CANoe.AMD as well as CANape. It is available for many topologies: CAN, CAN-FD, FR, ETH, LIN, J1939.

Afficher plus

MICROSAR.HSM

Firmware for Hardware Security Modules

With vHSM you get efficient and secure firmware for Hardware Security Modules (HSM) which are integrated in microcontrollers and contain a secure core. vHSM provides cryptographic services and accesses the available hardware resources for this purpose. The vHSM firmware enhances the ECU's cybersecurity by implementing features such as basic cryptographic basic functions, secure storage of keys and secure boot mechanisms.

vHSM is available for many Hardware Security Modules from different semiconductor manufacturers. The PC-based DaVinci Configurator Pro configuration tool lets you configure vHSM to meet the requirements of your project. Due to the modular layout of the vHSM firmware, it can be adapted to the specific memory and execution time requirements of your special use case. Furthermore, various add-ons and user-specific services may be added.

While the AUTOSAR environment – which typically utilizes the cryptographic services of the HSM – is executed on the host core, vHSM is used on the secure core. The AUTOSAR environment utilizes the functions provided by vHSM via the Crypto(vHSM) driver.

Components of the comprehensive vHSM solution:

vHSM: The actual firmware, which is executed on the secure core of the HSM. It consists of several modules.

Crypto(vHSM): MCAL driver for the AUTOSAR stack and the Flash Bootloader as an interface to the vHSM firmware

AUTOSAR Basic Software for Safety-Related Functions

MICROSAR Safe helps you to integrate safety-related functions into your ECU. It lets you develop AUTOSAR-based applications for ECUs up to ASIL D according to ISO 26262.

The modules of MICROSAR Safe are developed as SEooCs (Safety Elements out of Context) according to ISO 26262 / ASIL D. MICROSAR Safe is the result of many years of experience in the field of functional safety. It is independently certified by exida for use in systems up to ASIL D.

Functions

Spacial and temporal separation of software applications

Program flow monitoring of safety-relevant software components

Protection of inter-ECU communication

Advantages

Solution for all Automotive Safety Integrity Levels (ASILs) up to ASIL D

Reduces qualification costs through highly automated verification

Supports different ASILs on one controller

Efficient partitioning concepts with the complete basis software available in ASIL D

Consulting for Functional Safety and ISO 26262:

Do you have questions related to the development process and safety strategies for using safety-related SWCs? We would be glad to consult with you in colaboration with Vector Consulting.

Afficher plus

Access Security for AUTOSAR ECUs

The growth in the amount of safety-related information and personal data in the automobile is making protection against intentional data manipulation and data theft increasingly more important. Security mechanisms shall be used to protect the integrity, authenticity and confidentiality of information. In this area, Vector can offer you components specified in AUTOSAR and beyond the standard.

Overview of Advantages of MICROSAR Security

Standard-conformant implementation of security functions from a single source

Established cryptographic algorithms

Protection against unauthorized modification of critical data

Protection of confidential data

Protection against replay attacks

Authentication of communication Tx points

Protection against unauhtorized injection of data

Functions

Crypto Service Manager (Csm)

The Cryptographic Service Manager provides access to standardized cryptographic primitives and secure key- and certificate storage.

Crypto Interface (CryIf)

The Crypto Interface (CryIf) module makes it possible to use Csm hardware-based and software-based crypto solutions. The necessary allocation scheme is managed by the Crypto Interface.

Crypto (SW)

The Crypto (SW) module provides implementations for cryptographic algorithms and functions in software which are supplied via the Csm. All computations are executed in software, and no special hardware is required to execute cryptographic operations.

The OEM-specific vSecMod includes the Freshness Value Manager (vFVM) and the Key Management (vKeyM) with the following functionalities:

vFVM: Provides a freshness value to SecOC component to prevent replay attacks. This module is used by (and therefore requires) the Secure Onboard Communication (SecOC)

vKeyM: Handles key exchange and key updates

Crypto (HW)

The Crypto (HW) module acts as the driver for accessing security algorithms and functions, which are provided via a Hardware Trust Anchor (HTA). Different HTA types are available such as Secure Hardware Extensions (SHE) and Hardware Security Modules (HSM). Vector offers the following options for the Crypto (HW) module according to the hardware platform and the derivative used:

Integration of a Crypto (HW) developed by Vector

Integration of a 3rd party Crypto (HW) developed at the semiconductor manufacturer

Secure OnBoard Communication (SecOC)

The SecOC module, also called Authenticated Messaging, is used to authenticate the communication between two ECU's. This validation prevents a third party from intervening or pretending to be the correct communication partner. This prevents manipulative interventions. The SecOC interacts with the PDU router.

Ethernet Firewall (vEthFw)

The Ethernet Firewall (vEthFw) provides the implementation of a firewall for Ethernet communication. Its main task is to block undesirable incoming or outgoing data traffic to enhance the security of the overall network.

Vector Internet Security (vIpSec)

The add-on vIpSec allows to establish an IPsec communication according to IETF RfC 4301. The functionality is restricted to transport mode and the usage of Authentication Header only according to RfC 4302.

Vector Transport Layer Security (vTls (Client))

This module contains a Transport Layer Security Client. TCP-based communication is encrypted with vTls. You can select the encryption algorithm to be used.

Afficher plus

Vector offers options for handling ECU variants. These support both car manufacturers and suppliers in realizing cost savings and to gain flexibility during ECU production:

Post-Build Selectable (Identity Manager) reduces the number of required ECUs because

the same ECU type can take over similar tasks at different positions in the vehicle via the given identity (example: door ECU left / right).

the same ECU type can be used in multiple vehicle lines as the ECU contains the communication descriptions of all vehicle lines and will support the correct one in each vehicle line after initialization.

Post-Build Loadable allows changing BSW parameters of communication and diagnostics interfaces also after the ECU has been manufactured. As it does not require the application, compiler, etc. for the post-build update, it can be done easily and cost efficient by the car manufacturer himself. The Post-Build Loadable option is available for the AUTOSAR basic software MICROSAR.

Afficher plus

MICROSAR POSIX

Connecting AUTOSAR Classic to POSIX Operating Systems

Driver assistance systems and infotainment are leading to increasingly more intensive intermeshing of established static ECU solutions with new dynamic services. That is why POSIX-based systems are being used more frequently in combination with classic AUTOSAR technology in ECU projects. The newly defined AUTOSAR Adaptive standard underscores this trend. Therefore, MICROSAR offers solutions for using classic automotive functions under a POSIX operating system as well, or for exchanging data between a POSIX domain and an AUTOSAR domain.

Overview of Advantages

MICROSAR basic software is operated as a process in third-party operating systems such as Linux, QNX, INTEGRITY and PikeOS

Thus, established modules from AUTOSAR Classic may be re-used in a non-AUTOSAR environment

Technical Article

AUTOSAR Classic and POSIX-Compliant OS – Is That Gonna Work?

POSIX-compliant operating systems enable dynamic in-vehicle software applications. However, they lack automotive functions such as diagnostics and network management. For new developments, AUTOSAR Adaptive supports these tasks. But can the use of a POSIX-OS succeed if the vehicle platform is still based on AUTOSAR Classic?

MICROSAR Gateway offers optimized AUTOSAR-based modules for gateways which enable routing on different protocol levels and between different bus systems (CAN, LIN, FlexRay, Ethernet). Building upon these basic functions, MICROSAR Gateway offers a number of special functions, such as mirroring of sub-networks and a modular plug-in concept for extending the existing functionality.

This flexible approach enables use of the MICROSAR Gateway in developing

MICROSAR Multi-Core

Die AUTOSAR-Lösung für Mehrkern-Prozessoren

The introduction of multi-core processors has also changed the design of the downstream AUTOSAR software. Individual AUTOSAR applications can now be distributed to different processor cores and thus be executed simultaneously. Crucial to success is to find the appropriate distribution for the intended application use case. For achieving this, internal ECU communication must be offered with minimal synchronization losses.

MICROSAR Multi-core is perfectly integrated with the TA Tool Suite which offers automated application distribution optimization. In addition, MICROSAR embedded code is designed to efficiently provide basic software services and intra-application communication. This provides optimal support for a large number of applications.

Afficher plus

MICROSAR vVIRTUALtarget basic

Virtual Integration

The process for developing an ECU typically begins with creating the individual software modules (SWC). However, because of the continued trend towards shorter project time, there is generally insufficient time to sequentially create all the necessary SWCs first, then test their interaction with one another and finally test their interplay with the basic software on the target hardware. An integrated test of the SWC together with basic software is essential for early assessment and fast iteration.

Numerous projects today are characterized by the need to start test runs in a very early project phase - sometimes in a phase in which the target hardware has not yet been fully defined. vVIRTUALtarget offers the optimal solution for this situation. It is an emulated runtime environment in which ECU software can be executed without requiring access to real hardware, which decouples test execution from hardware platform. This, in turn, leads to substantial time advantages. Furthermore, the same basic software configuration can be used for both the target hardware and the environment of vVIRTUALtarget.

A CANoe license is required to simulate and measure communication and I/O interfaces.

MICROSAR J1939

The application area of the J1939 modules is in handling communication in heavy-duty vehicles over CAN networks with the special features defined in the SAE J1939 standard. They are implemented in J1939-specific BSW modules and are supported by extensions in neighboring modules. In addition, MICROSAR.CAN can also be used to implement ISOBUS ECUs (according to ISO 11783) in agricultural vehicles and implements. For that purpose, J1939Nm and CanIf were extended by functionalities for fully dynamic address arbitration and address tracking, and the ETP and FastPacket transport protocols were also implemented in the J1939Tp. Also, maritime use cases according to NMEA2000 can be supported by FastPacket and fully dynamic address arbitration.

The BSW modules for J1939 contain the functions defined in AUTOSAR 4.x, specifically:

The Quick Start to Your AUTOSAR Project

MICROSAR.SIP and MICROSAR.EIP

The Software Integration Package (SIP) and the Extended Integration Package (EIP) from Vector give you a decisive advantage in developing your ECU software: we test your software package before delivery, and you can put the entire package into operation within just a few days. Via a questionnaire, we catalog your requirements in as much detail as possible in advance of delivery. Afterwards we custom-build your Software Integration Package as individually as possible on this basis.

MICROSAR.SIP is a standard delivery item, and it focuses on the broadest possible range of use for your stack. It optimizes the usability of our delivery to you, even when constraints are altered slightly.

MICROSAR.EIP assists in followup activities after an initial delivery. It offers crucial support in achieving a quick and comprehensive startup. The goal here is to pass the first bench test at the OEM.

Training

AUTOSAR Workshop | 1-5 days

Do you want to know more about the basics of AUTOSAR and the AUTOSAR basic software and tools? Vector offers a 1-5-day modular AUTOSAR workshop. This deals with AUTOSAR 4 and AUTOSAR 3 alternately. According to the booked module...

You get to know the AUTOSAR methodology

You gain insights in all major subject areas of the ECU development

You get to know the specifics of some vehicle manufacturers

MICROSAR safe is presented - the Vector solution for safety-related ECUs according to ISO 26262.