MICROSAR ProductInformation en
MICROSAR ProductInformation en
MICROSAR ProductInformation en
Product Information
MICROSAR
Table of Contents
MICROSAR.OS The Real-Time Operating System for the AUTOSAR Standard .............................................................. 8
MICROSAR V2G Basic Software Modules for Communicating with External Infrastructure ...................................... 31
10
MICROSAR AVB Basic Software Modules for Audio/Video Communication via Ethernet ........................................... 34
11
12
13
14
15
16
17
MICROSAR.RTE - The optimized Run-time Environment for Software Components per the AUTOSAR Standard ...... 58
18
19
MICROSAR Safe Functional Safety according to ISO 26262 up to ASIL D for ECU software ..................................... 65
20
21
22
23
MICROSAR J1939 AUTOSAR Basic Software Modules Specially Designed for Heavy-Duty Vehicles......................... 77
24
25
26
AUTOSAR Evaluation Bundle The complete package for the evaluation of AUTOSAR basic software and tools...... 87
27
V2.2 09/2016
Please consider the environment before printing this document.
MICROSAR
MICROSAR is the AUTOSAR solution from Vector for your ECU software. MICROSAR consists of the MICROSAR.RTE and
MICROSAR basic software modules (BSW), which cover all aspects of the AUTOSAR standard and many extensions. Each
AUTOSAR BSW module is assigned to a MICROSAR package. For detailed descriptions of individual packages and the
MICROSAR.RTE, please refer to the following chapters. Vector combines and releases the BSW modules needed in individual
software integration packages (SIP).
1.1
Figure 1: The MICROSAR packages contain all modules of the AUTOSAR 4.2 standard
Content
MICROSAR AMD
MICROSAR AVB
MICROSAR MCAL
MICROSAR CAN
MICROSAR COM
MICROSAR EXT
MICROSAR FR
MICROSAR DIAG
MICROSAR.IO
MICROSAR ETH
MICROSAR.LIBS
AUTOSAR Libraries
MICROSAR.LIN
MICROSAR.MEM
MICROSAR
Package
Content
MICROSAR.OS
MICROSAR.RTE
Optimized run-time environment for software components according to the AUTOSAR standard
MICROSAR Safe
MICROSAR.SYS
MICROSAR V2G
MICROSAR XCP
Measurement and calibration of an AUTOSAR-ECU using XCP incl. transport layer for Ethernet, FlexRay und CAN
1.2
Application Areas
The BSW 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.
Modules from the MICROSAR.OS and MICROSAR.MCAL packages are hardware-dependent. Vector offers these modules for
a large number of different hardware platforms and compilers, e.g. to enable quick change-out of the controller device. The
operating system MICROSAR.OS is available for single core and multi core-processors. Based on its ongoing contacts with
OEMs, Vector is able to offer a number of OEM-specific BSW modules and extensions such as the diagnostic modules.
You can configure all necessary MICROSAR BSW modules based on your projects 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 run-time 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.
ECU projects without SWC architecture (and therefore also without RTE) are optionally supported by the Vector BRE (Basic
Runtime Environment). BRE simplifies the BSW integration by providing configurable BSW scheduling, critical section
management and creation of type definitions for service layer BSW modules which normally would be created by the RTE.
Hereby the BRE speeds up and simplifies building up AUTOSAR 4 based projects which do not have a RTE.
1.3
Properties
Development of the MICROSAR basic software modules is founded on the SPICE-based Vector development process for
standard modules, which is based on SPICE. All MICROSAR packages offer the following features:
> Efficient memory utilization and short execution times
> Available for production use
> Available for AUTOSAR 4.x and 3.x
> Assistants and timely checks support you in achieving consistent configuration of your basic software
> Highly scalable, adaptable to your specific application
> Optimally integrated into your development process
> AUTOSAR Monitoring for testing and analysis of ECUs
> User-selectable configuration point (pre-compile, link-time or post-build)
> Supports multiple ECUs
> Optional delivery as source code
> Together with MICROSAR Safe: well-suited for safety-relevant functions (ISO 26262)
1.4
Production Use
The MICROSAR BSW modules are already being used in production projects. MICROSAR lets you benefit from Vectors many
years of experience in implementing embedded standard software. Before delivery, all MICROSAR Software modules
undergo systematic integration tests for the specific conditions of your application (hardware platform, compiler, processor
MICROSAR
device, OEM, with/without RTE, etc.). Upon request, these tests may be extended to cover software modules from thirdparty producers (e.g. MCAL drivers).
1.5
Regardless of whether you use AUTOSAR 4.x or 3.x, from Vector you get the entire basic software from a single source. In
migration of your projects, you benefit from the uniform development workflow for both AUTOSAR 4.x and 3.x:
> The configuration tools DaVinci Developer and DaVinci Configurator Pro are designed for both releases. This lets you
avoid a change in tools.
> MCAL drivers from different AUTOSAR releases can be combined with MICROSAR.
In the case of a migration from AUTOSAR 3 to 4, we can support you in adapting your application software to the interfaces
that were changed in the AUTOSAR 4.x standard.
Another advantage of MICROSAR lies in its many extensions in the BSW modules for AUTOSAR 3.x, which are specified in
AUTOSAR 4.x. Some examples are the multi-core operating system, as well as support for J1939, XCP and Ethernet/IP,
which are already available for AUTOSAR 3.x. The MICROSAR.MOST bundle is a Vector supplement to the standard and is
compatible with AUTOSAR 4.x and AUTOSAR 3.x.
1.6
With AUTOSAR, the work of manually developing or adapting the basic functionality of ECU software is replaced by
configuration of the BSW modules. The intuitive, user-friendly and well-coordinated AUTOSAR tools from Vector (DaVinci)
support the user in this process. Multi User Support of the DaVinci tools enables simultaneous work on a project by multiple
users. The DaVinci tools require an ECU Extract of System Description file as input. It is also possible to produce a
configuration based on commonly used network description files (DBC, FIBEX, LDF, etc.).
Early in the configuration process, all DaVinci tools check the validity of individual parameters, complex parameter groups
and their interrelationships. In case of invalid configurations, the tools make recommendations for corrections, if possible.
This extension of the AUTOSAR method simplifies integration of the basic software in your ECU and reduces integration
time.
The DaVinci tools optimally assist you in configuring the RTE and the BSW modules. In a bottom-up process, for example, the
SWC service ports (including runnables) are automatically generated to match the BSW configuration. This automation
relieves you of tasks that recur frequently and are prone to errors when performed manually. This saves you time and costs.
Figure 2: You use DaVinci Configurator Pro to configure the BSW modules and the RTE.
MICROSAR
Figure 3: You use DaVinci Developer to define the functional software (SWCs).
For more details on DaVinci tools from Vector, please refer to the relevant datasheets.
1.7
Scalability
In addition to fulfilling AUTOSAR requirements, the MICROSAR BSW modules also provide a number of functional
extensions. The extended configuration options let you deactivate unnecessary functions to optimize the MICROSAR code for
your application. This scalability makes the MICROSAR modules the optimal solution for both small and challenging
applications. MICROSAR is already being implemented in a wide range of ECUs, such as steering angle sensors, door ECUs,
engine ECUs, central gateways, etc. MICROSAR may also be used with other operating systems such as Linux or QNX.
1.8
The AMD package simplifies testing and analysis of BSW and application functions by transferring important status
information and results to tools such as CANape or CANoe.AMD. In addition, AMD offers the option of executing run-time
measurements at the BSW and application functions. For more information, please refer to the section on MICROSAR AMD.
1.9
The configuration point of all MICROSAR basic software modules is user-selectable. You can select the configuration point
for each BSW module; choices are: pre-compile, link-time or post-build.
1.10 ECU Variants and Reloading the BSW Configuration
To save on logistical costs in AUTOSAR ECUs, the MICROSAR modules are available with the Identity Manager option. This
option can be used to store multiple configurations (e.g. left or right door) in one ECU. This lets you install an identical ECU
for multiple functionalities within a model series or in different model series.
The BSW option "Post-Build Loadable" lets users modify many parameters of the BSW configuration at a later time without
having to recompile the ECU software. For example, routing tables and send types can be modified and extended without
the ECU's build environment and without requiring that the supplier be contracted for a new ECU variant.
For more information, please refer to the section "MICROSAR Variant Handling".
1.11 Functional Safety according to ISO 26262: MICROSAR Safe
For use of the MICROSAR BSW in safety-related functions, Vector together with TTTech Automotive offers a complete
solution for your AUTOSAR ECU. For more information, please refer to the chapter on MICROSAR Safe.
MICROSAR
MICROSAR
MICROSAR.OS is a pre-emptive real-time multitasking operating system with optimized properties for use on
microcontrollers. Vectors many years of experience in developing operating systems and drivers for microcontrollers are
bundled into this small, robust operating system core.
2.1
Overview of Advantages
> Small, quick, resource-economizing operating system and with short boot times
> MICROSAR.OS is available for AUTOSAR 4.x and 3.x
> Optional: Available as multi core operating system
> Optional: Safe context switching per ISO26262 / ASIL D
> Quality process per SPICE Level 3
> Graphic configuration tool for easy configuration
> Available for many 8, 16, 32 and 64 bit microcontrollers
2.2
Properties
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:
> SC1: Real-time operating system implemented per the OSEK/VDX-OS standard and extended to include schedule tables
> SC2: Real-time operating system with time synchronization and monitoring of the time behavior of individual tasks and
interrupt service routines
MICROSAR
> SC3: Real-time operating system with memory protection mechanisms on microcontrollers with suitable hardware
support
> SC4: Combines scalability classes SC2 and SC3
2.3
Optional Extensions
For safety-relevant applications per ISO 26262, you can obtain Vectors operating system variant MICROSAR.OS
SafeContext that was developed according to ASIL D. It is based on the AUTOSAR scalability classes SC3 and SC4 and is
responsible for memory protection and safe context switching. To preserve freedom from interference with regard to
memory protection, you need a suitable processor, e.g. with a Memory Protection Unit (MPU).
You can use MICROSAR.OS SafeContext to use safety-relevant application components together with standard components
on the same CPU.
Scope of delivery for MICROSAR.OS SafeContext:
> Operating system core as source code
> Graphic configuration tool for Windows 7 / Windows XP
> Command line based generator
> BSW Module Description
> Description files for DaVinci Configurator Pro o
> Documentation
> Read-back tool
> Safety Manual
For more details on the Vector solution for safety, please refer to the separate chapter about MICROSAR Safe.
2.5
MICROSAR.OS Multi-core is an advanced development of the proven real-time operating system MICROSAR.OS from
Vector. You can use it wherever a multi-core system is to be developed according to the AUTOSAR specification.
MICROSAR.OS Multi-core is based on AUTOSAR specification 4.x, but it can also be used in AUTOSAR 3.x projects.
MICROSAR
Synchronized Start-Up
The operating system assures that all cores are started up and initialized before the associated application is started.
2.5.1.2
Inter-Core Coordination
Processes on different cores are synchronized by task activations, setting of events, starting and stopping of alarms or
ScheduleTables.
2.5.1.3
If different cores should access commonly used resources, the operating system provides a coordination mechanism known
as Spinlocks.
2.5.1.4
Inter-Core Communication
For consistent data exchange between two cores, the operating system provides an efficient interface in the form of the
Inter-OS Application Communicator (IOC).
2.6
For a comfortable configuration we recommend the DaVinci Configurator Pro. It contains consistency checks and the call of
the generator. The generator is implemented as a command-line tool to enable its integration in an automated development
environment.
2.7
Scope of Delivery
10
MICROSAR
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.
3.1
Overview of Advantages
Application Areas
MICROSAR.COM lets users develop their functional software by a fully bus-independent approach. All necessary tasks for
transmit-ting messages and for cross-bus network management activities are handled by the configurable BSW modules
COM, NM, PDUR and IPDUM from MICROSAR.COM.
For a gateway ECU, you do not need any additional software. The COM and PDUR BSW modules from MICROSAR.COM
enable routing of signals and TP or application messages.
11
MICROSAR
3.3
Functions
The BSW modules from MICROSAR.COM contain functions defined in AUTOSAR 4.x:
> Services of the COM module organize transmission of messages according to their send type (cyclic, event-triggered,
etc.). A key task is to implement bus-independent signals of the functional software in PDUs.
> The PDU Router (PDUR) provides the modules COM, DCM and the complex drivers with an interface to the
communication modules (interface, transport protocol and network management) of the different bus systems. This
interface serves to transmit and receive data via PDUs. The PDUR also implements a gateway between the
communication modules of the various bus systems. The MICROSAR module CDD allows TP- and IF-PDUs to be
integrated into the COM stack:
> above or below the PDU router
> above the communication interfaces
> The Network Management Interface (NM) bundles inter-bus network management activities of all of the ECUs
communication channels. As NM coordinator, it synchronizes wake-up and sleep of the communication channels.
> The optional I-PDU Multiplexer (IPDUM) module supports multiple usage of frames with different data contents, via a
static configuration for the classic bus systems or alternatively via dynamic data content mapping for CAN-FD.
> Transformer: Allows efficient transmission of complex data structures and big PDUs over the network.
> COMXF: Allows efficient signal groups with many group signals. The placement is derived from the system extract.
> SOMEIPXF: Provides a serialization strategy for various data types. LDCOM can be used here for a highly efficient
transmission.
> E2EXF: Enables end-to-end protection for network communication that is managed using the AUTOSAR transformer
concept (i.e. serialization through COMXF or SOMEIPXF).
> SecOC: For details to the Secured OnBoard Communication (SecOC), please refer to the chapter "MICROSAR Security".
Beyond the AUTOSAR standard, MICROSAR.COM also contains the following important services:
> COM: Invalidity declaration of TX signals in case of RX signal timeout
> COM: Optimizations for mainfunction run-time reduction (Rx-sided: caching of received events, Tx-sided: configuration
of multiple time domains.)
> COM: Deferred Event Caching of Rx IPDUs. This is an optimization of the Rx mainfunction run-time via an event
triggered processing of Rx PDUs. The optimization allows to waive cyclic polling of all PDUs in the mainfunction Rx.
> COM, PDUR & IPDUM : Pre-compile and post-build loadable optimizations such as finding and removing redundant data
> NM: Synchronous sleep and wake-up of multiple networks via different NM coordinators
> NM: Backup coordinator
The following functions are optionally available:
> COM: PDU Replication (for AUTOSAR 4.x)
> COM: The COM module can be supplied with gateway functionality. Routing is possible for signals and signal groups.
Routing in COM is possible via a configuration description without existance of a real signal or signal group.
> NM: Support of OSEK NM (configurable)
> NM: Mixed operation of OSEK and AUTOSAR-NM on one channel
> PDUR: Support for
> TP and message routing
> routing via meta data in case of range routing
> routing of variable adresses ("dynamic gateway")
> Routing of dynamic PDU lengths
12
MICROSAR
> Post-build loadable and Post-build selectable: For details, please refer to the section "MICROSAR Variant Handling".
> Gateway Mirroring: allows mirroring internal busses to the diagnostic access which enables to read normally inaccessible
messages on the bus and to identify problems. In the base version, this function allows to mirror one internal CAN or LIN
channel to diagnostic CAN. With the optional enhancements, it is possible to
> mirror multiple CAN, LIN, FR and ETH channels to diagnostic ETH
> mirror CAN, LIN or FR channels to diagnostic CAN or FR
> High End Features: this option activates the following functions for COM modules:
> description based routing: this additional routing option allows to route PDU segments (defined by their start bit and
length) including class of emission management (periodic, event triggered, on changes). This creates a performant
alternative to signal based routing and to cycle-retarding PDU routing. This function requires the above mentioned
gateway option.
3.4
Configuration
For convenient configuration we recommend our DaVinci Configurator Pro. For more details, see the separate datasheet.
Using DaVinci Configurator Pro, you can easily link the MICROSAR.COM module PDUR and the modules CANIF, LINIF, FRIF
and ETHIF (SOAD) to your complex drivers by configuration.
13
MICROSAR
Gateway ECUs are central node points in the often heterogeneous network architecture of a vehicle. In this role, a gateway
interconnects the various networks to enable data transfer between distributed ECUs also across different network types.
The performance indicators of a gateway range between the contradictory priorities of high data throughput and low
resource load (especially RAM and CPU utilization) and low latency times in transmission.
Vector offers optimized modules for gateways, which enable routing to different protocol levels and between different bus
systems (CAN, LIN, FlexRay, Ethernet). Building upon these basic functions, the MICROSAR Gateway offers a number of
special functions, such as mirroring of sub-networks and a modular plug-in concept for extending existing functionality. The
MICROSAR Gateway offers the necessary flexibility to cover specific application cases, because of its three-stage concept of
basic functionality, special functions and extendibility.
To enable optimal gateway performance, certain aspects of the MICROSAR Gateway follow an independent architecture.
They meet the requirements of AUTOSAR Architecture Conformity Class 2 (ICC2), so AUTOSAR software components can
be incorporated.
4.1
> Routing on different protocol levels (PDU, high-level TP, PDU section, signal)
> Routing between different network types (CAN, LIN, FlexRay, Ethernet)
> Flexible configuration of buffer concepts (Rx FIFO queue, Tx FIFO queue, priority-based queue)
> Flexible configuration of processing concepts (interrupt, task)
> Post-build approach to flexible post-loading of routing relationships
> Mirroring of sub-networks to diagnostic access (CAN and Ethernet)
> Extended support for NM coordinators
> Toolchain for automatic processing of input data (.dbc, .ldf, .fibex, .arxml and proprietary formats)
> Defined interfaces for extending the toolchain (scripting, extensions) and the basic software (CDD support)
> Optional project-related support of gateway projects by Vector in close cooperation with Tier1
4.2
Application Areas
MICROSAR Gateway offers users the basic software they need to route data on the optimal protocol level between CAN,
LIN, FlexRay and Ethernet networks. This flexible approach enables use of the MICROSAR Gateway in developing:
14
MICROSAR
Functions
15
MICROSAR
Configuration
Gateway configurations are often very extensive. This makes it all the more important to be able to automatically
parameterize the basic software according to the input data provided by the OEM. The DaVinci Configurator Pro
configuration tool from Vector supports automatic parameterization by various methods:
> Configuration via an AUTOSAR System Extract (.arxml): The data format defined by AUTOSAR permits explicit
specification of routing information. This information is read in by DaVinci Configurator Pro and is transformed into a
software configuration.
> Configuration via extended network files: The proprietary network files (.dbc / .ldf / .fibex) generally do not offer any
ability to specify routing information natively. However, DaVinci Configurator Pro interprets various supplemental
attributes and can evaluate rules (e.g. an existing identical naming of signals), in order to derive routing information.
> Configuration via proprietary data (e.g. .xls): The Vector toolchain also offers the option of defining routing information
via a separate additional file. This file makes it possible to define relationships between messages and signals from the
network files in a Vector-specified XML format (Vector System Description Extension, VSDE), thereby specifying routing
relationships. A VSDE file is especially well-suited for integrating proprietary routing configurations into the toolchain.
This requires implementation of a conversion routine, which transfers the proprietary file into a VSDE file.
> Scripting: The methods described above may also be combined with a scripting solution. Using DaVinci Configurator Pro
Option WF (Workflow), you can create scripts specifically for your project, which you can use to supplement routing
information in programming.
The software configuration generated by these methods is not restricted to a one-time process. If the network description in
the input files should change, the software configuration can be automatically updated.
16
MICROSAR
Figure 9: Options for automatic configuration of the BSW for the gateway with DaVinci Configurator Pro
In addition to automatic derivation of the configuration, all parameters can also be processed manually in DaVinci
Configurator Pro. For more details on this, please refer to the separate product information at
http://vector.com/vi_davinci_configurator_pro_de.html.
4.5
Project Support
Requirements placed on gateway ECUs are especially frequently both OEM-specific and application-specific, and therefore a
standard product generally cannot satisfy them fully. Nonetheless, Vector offers a two-stage approach for efficiently
addressing these requirements in your project:
> First, MICROSAR Gateway supports many extension options in the form of a plug-in architecture that lets you integrate
software you have developed yourself or procured from third-party suppliers.
> As an option that builds upon these interfaces, we can also offer the service of working together with you to handle
project requirements. This enables much more flexible implementation of customer requirements than by a product
approach which is characterized by release cycles: Within a joint project, we are then glad to also implement the product
extensions needed to satisfy customer requirements.
17
MICROSAR
The MICROSAR.CAN package contains the BSW modules defined in the AUTOSAR architecture for CAN communication:
CANIF, CANNM, CANTP, CANSM and optional modules for J1939 and XCP.
5.1
Overview of Advantages
Application Areas
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 net-work. The BAM and CMDT transport protocols are available for this.
5.3
Functions
The BSW modules in MICROSAR.CAN contain functions defined in AUTOSAR 4.x. Beyond the standard itself,
MICROSAR.CAN offers the following important services:
18
MICROSAR
> CANIF: Double hash search algorithm for efficient filtering the Rx messages
> CANNM, CANTP: Pre-compile optimizations, e.g. for single-channel systems
> CANSM: Support of ECU Passive Mode
> CANTP: Supports mixed addressing (11 bit CAN ID); typically for CAN/LIN gateway applications
> CANTP: Optimized routing (e.g. with Burst Transmission) together with the PDUR from MICORSAR COM
> CANTP: ISO 15765-2 compatibility is configurable
> CANTSYN: Time Synchronization over CAN (CANTSYN) implements the Generalized Precision Time Protocol (gPTP)
according to IEEE 802.1AS. This permits clock synchronization between CAN ECUs. The Synchronized Time Base
Manager (STBM) BSW module from MICROSAR.SYS is available as a higher-level time coordinator.
The following functionalities are available as options:
> J1939: Network Manager J1939NM, Request Manager J1939RM, diagnostic module J1939DCM and in J1939TP the
transport protocols BAM and CMDT for J1939 networks
> CAN driver: Increase the number of Full-CAN objects by combining multiple CAN controllers on one physical CAN bus
(Common CAN)
> For CANIF: support of an external CAN controller
> Post-build loadable and Post-build selectable: For details, please refer to the section "MICROSAR Variant Handling".
5.4
Configuration
For convenient configuration, we recommend to use DaVinci Configurator Pro. For more details, please refer to the separate
product information.
5.5
Based on the AUTOSAR architecture, a complete communication stack for CAN can be formed using MICROSAR.CAN
together with the BSW modules from the separately available MICROSAR.COM, MICROSAR.MCAL and MICROSAR.EXT
packages. To interface MICROSAR.CAN to the application and the hardware, you will still need the following BSW modules:
> Hardware-specific CAN driver (CANDRV) from MICROSAR.MCAL
> Hardware-specific transceiver control (CANTRCV) from MICROSAR.EXT, also for partial networking
> General communication modules (COM, NM, PDUR, IPDUM) from MICROSAR.COM
Modules in MICROSAR.MCAL and MICROSAR.EXT are available for many microcontrollers and transceivers.
5.6
19
MICROSAR
5.7
Figure 12: Vector offers a comprehensive range of products and services for your CAN projects
20
MICROSAR
Vector offers you MICROSAR.FR, an AUTOSAR-conformant package for FlexRay communication. It contains the following
BSW modules defined in the AUTOSAR architecture: FRIF, FRNM, FRSM and a choice between FRTP and FRISOTP.
MICROSAR.FR can be extended with XCP as an option.
6.1
Overview of Advantages
Application Areas
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.
6.3
Functions
The BSW modules in MICROSAR.FR contain functions defined in AUTOSAR 4.x, where FRISOTP is a supplement to AUTOSAR
3.x. MICROSAR.FR contains the following important services that go beyond the standard:
> FRDRV: Optimized wakeup during operation (WUDOP)
> FRDRV & FRIF: Support of the following APIs: CancelTransmit and L-PdU reconfiguration
> FRIF: Dual channel redundancy for redundant transmission of frames and PDU-specific voting function for the SWCs
21
MICROSAR
> FRDRV, FRIF, FRNM, FRTP: Pre-compile optimizations, e.g. for single-channel systems
> FRSM: Support of ECU Passive Mode, immediate startup after passive wakeup, extended error handling by State
Change Notification, configurable time delay for FlexRay startup at passive wakeup as well as configurable number of
wakeup patterns.
> FRTSYN: Time Synchronization over FlexRay (FRTSYN) implements the Generalized Precision Time Protocol (gPTP)
according to IEEE 802.1AS. This permits clock synchronization between FR ECUs. The Synchronized Time Base Manager
(STBM) BSW module from MICROSAR.SYS is available as a higher-level time coordinator.
The following functionalities are available as options:
> Post-build loadable and Post-build selectable: For details, please refer to the section "MICROSAR Variant Handling".
6.4
Operating System
FlexRay basic software modules can be used entirely without an operating system. However, it makes sense to use an
AUTOSAR OS or a conventional OSEK-OS (e.g. Vector osCAN). Ideally suited for FlexRay applications is MICROSAR.OS from
Vector.
6.5
Configuration
For convenient configuration we recommend the DaVinci Configurator Pro. For more details, please refer to the separate
product information.
6.6
Based on the AUTOSAR architecture, a complete communication stack for FlexRay can be made with MICROSAR.FR
together with the BSW modules from the separately available MICROSAR.COM, MICROSAR.MCAL, MICROSAR.SYS and
MICROSAR.EXT packages. You will also need the following BSW modules to interface MICROSAR.FR to the application and
hardware:
> Hardware-specific FlexRay driver (FRDRV) from MICROSAR.MCAL
> Hardware-specific transceiver control (FRTRCV) from MICROSAR.EXT
> General communication modules (COM, NM, PDUR, IPDUM) from MICROSAR.COM
The modules in MICROSAR.MCAL and MICROSAR.EXT are available for many different microcontrollers and transceivers.
6.7
22
MICROSAR
6.8
Figure 14: Vector offers a comprehensive portfolio of products and services for your FlexRay projects
23
MICROSAR
MICROSAR.LIN contains the BSW modules defined in the AUTOSAR architecture for LIN communication: LINIF, LINSM and
LINNM. According to AUTOSAR, LINTP is a part of LINIF. The LIN transport protocol is offered as an option, because not
every LIN communication stack requires a transport protocol. XCP for the MICROSAR.LIN Master is also available as an
ASAM extension.
7.1
Overview of Advantages
Application Areas
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.
7.3
Functions
The BSW modules from MICROSAR.LIN contain functions defined in AUTOSAR 4.x.
Beyond the standard, MICROSAR.LIN includes the following important services:
24
MICROSAR
Configuration
For convenient configuration, we recommend the DaVinci Configurator Pro. For more details, please refer to the separate
product information.
7.5
Based on the AUTOSAR architecture, a complete communication stack for LIN is formed by MICROSAR.LIN together with
the BSW modules from the separately available MICROSAR.COM, MICROSAR.MCAL and MICROSAR.EXT packages. To
interface MICROSAR.LIN to the application and hardware, you will still need the following BSW modules:
> Hardware-specific LIN driver (LINDRV) from MICROSAR.MCAL
> Hardware-specific transceiver control (LINTRCV) from MICROSAR.EXT
> General communication modules and gateway functions (COM, PDUR) from MICROSAR.COM
The modules in MICROSAR.MCAL and MICROSAR.EXT are available for many different microcontrollers and transceivers.
7.6
25
MICROSAR
7.7
Figure 16: Vector offers you a comprehensive range of products and services for your LIN projects
26
MICROSAR
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 and 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.
8.1
> BSW modules are available for AUTOSAR 4.1, 4.0 and as a supplement to AUTOSAR 3.x.
> TCP/IP stack developed to an automotive standard and tested by the Fraunhofer ESK organization
> No Open Source Software
> Seamless integration, e.g. of Vehicle-to-Grid communication (MICROSAR V2G) and Audio/Video Bridging (MICROSAR
AVB), in the AUTOSAR Ethernet- and TCP/IP stack
> Simple integration of customer-specific functions/modules on all levels
8.2
Application Areas
With MICROSAR.ETH in the ECU (Server) and a conventional PC or diagnostic tester as Client, you can
> diagnose the vehicle in accordance with ISO 13400-2 (DoIP) and
> reprogram ECUs quickly and in parallel.
The larger data throughput of Ethernet shortens total software download and diagnostic times considerably. An existing
gateway in the vehicle can be used to route diagnostic requests to internal vehicle networks. For instance, this gives you the
ability to reprogram multiple CAN ECUs in parallel over DoIP. In combination with other MICROSAR packages,
27
MICROSAR
MICROSAR.ETH implements the required gateway functionality. If MICROSAR.ETH is being used in the flash bootloader
(FBL), an ECU that is connected to the Ethernet network (e.g. the gateway itself) can be reprogrammed directly over DoIP.
MICROSAR XCP on Ethernet is available to you for measuring and calibrating Ethernet ECUs, which gives you the benefit of
larger bandwidth. XCP routing extends a gateway by adding the ability to calibrate also CAN and FlexRay ECUs over XCP via
the Ethernet (vehicle) port.
Along with the application areas of diagnostics, measurement and calibration, in which Ethernet-based communication
occurs between the external infrastructure and the vehicle, MICROSAR.ETH also offers the ability to efficiently use vehicleinternal Ethernet networks. Using "scalable service oriented middleware over IP" (SOME/IP) you can transmit data serviceoriented, for instance. This might involve use of the Service Discovery BSW module (SD) for the administration of services
which was introduced in AUTOSAR 4.1.1. Apart from the service orientation, SOME/IP also offers a dynamic data
serialization. Its' implementation is available as an RTE transformer. You will find more information on the SOME/IP
transformer in the chapters on MICROSAR.RTE and MICROSAR.COM.
Of course, you can also transmit data on Ethernet in a signal- and PDU-based way.
Parts of MICROSAR.ETH also serve as the basis for Vehicle-to-Grid communication and audio/video bridging. You will find
more details on these application areas in the sections on MICROSAR V2G and MICROSAR AVB.
8.3
Functions
The following BSW modules from MICROSAR.ETH contain the functions defined in AUTOSAR 4.1. For use in an AUTOSAR 4.0
or AUTOSAR 3.x software stack, they have suitable compatible interfaces:
> ETHIF: The Ethernet Interface enables hardware-independent access to the Ethernet driver (ETHDRV) and Ethernet
transceiver driver (ETHTRCV). Starting with AUTOSAR 4.1, this module is also responsible for VLAN handling. Hardwareindependent control of Ethernet switch drivers (ETHSWTDRV and ETHSWTDRV EXT) has been part of ETHIF since
AUTOSAR 4.2.
> ETHSM: To start up or shut down communication in Ethernet clusters, the Ethernet State Manager (ETHSM) provides
an abstract interface to the Communication Manager (COMM). The ETHSM accesses the Ethernet hardware over the
ETHIF.
> ETHTSYN: Time Synchronization over Ethernet (ETHTSYN) implements the Generalized Precision Time Protocol (gPTP)
according to IEEE 802.1AS. This permits clock synchronization between Ethernet ECUs.
> ETM: The Ethernet Testability Module (ETM) implements a standardized counterpart for protocol conformity tests. The
module enables an externally connected test environment to trigger defined actions, e.g. sending UDP packages or
creating a TCP-connection. The ETM module is specified in AUTOSAR 4.3 and currently available as an extension.
> TCPIP: This module contains all protocols for UDP- and TCP-based communication. It supports IPv4 and IPv6 and
parallel operation of IPv4 and IPv6 in one ECU. It contains the following protocols:
> IPv4, ICMPv4, ARP and DHCPv4 (client)
> IPv6, ICMPv6, NDP and DHCPv6 (client)
> UDP and TCP
Circumstantially for some use cases, e.g. for communication with external infrastructure outside the car, additional
functions for a TCP/IP stack may be necessary. In MICROSAR.ETH two extensions are available which cover the
following IETF RFCs:
> IPv6 Extensions
> RFC3810 Multicast Listener Discovery Version 2 (MLDv2) for IPv6 (RFCs 2710, 2711, 3590)
> RFC4941 Privacy Extensions for Stateless Address Autoconfiguration in IPv6
> TCP Extensions
> RFC1323 TCP Extensions for High Performance (RTTM Round-Trip Time Measurement)
> RFC2018 TCP Selective Acknowledgment Options
> RFC5482 TCP User Timeout Option
> RFC5681 TCP Congestion Control (RFCs 6298, 6582)
28
MICROSAR
In conjunction with Ethernet switch support in AUTOSAR 4.2, the TCPIP module was supplemented with a DHCPv4
server which assigns IP addresses based on the switch port. This DHCPv4 server is also available as a TCP/IP Add-On.
> SOAD: The Socket Adapter (SOAD) converts the communication over PDUs defined in AUTOSAR into socket-oriented
communication. In AUTOSAR 4.0, the SOAD also contains the diagnostic functionality (DoIP) defined in ISO 13400-2. In
AUTOSAR 4.1, this plug-in is made separate and is specified as an independent module (DOIP). Moreover, extensions for
XCP routing are implemented in the SOAD.
> The option "SOAD (BSD)" enables the SOAD and the overlying modules to be used in a non-AUTOSAR environment, e.g.
LINUX.
> DOIP: Effective with AUTOSAR 4.1.1, the Diagnostics over IP (DOIP) module contains the diagnostic functionality by the
same name according to ISO 13400-2. Up to and including AUTOSAR 4.0.3, this functionality is part of the Socket
Adapter (SOAD).
> SD: Service Discovery (SD) is specified for the first time in AUTOSAR 4.1.1. An ECU informs its communication partners
about the availability of its services with the protocol implemented in this module. In addition, ECUs can register to
receive automatic notifications, e.g. in the event of a signal update.
> UDPNM: You can implement synchronous going to sleep of Ethernet ECUs by network management over UDP
(UDPNM).
> TLS: This module contains a Transport Layer Security Client. TCP-based communication is encrypted with TLS. You can
select the encryption algorithm to be used.
Options:
> Post-build loadable: This feature is available for the modules SOAD and SD.
8.4
Configuration
We recommend our DaVinci Configurator Pro for a convenient configuration. You will find more details in the separate
product information.
Ethernet- and TCP/IP-specific configuration parameters are saved as an extension in the "ECU Configuration Description
(ECUC)" for AUTOSAR 3.x. This also applies to non-specified configuration parameters within AUTOSAR 4.x.
8.5
Based on the AUTOSAR architecture, MICROSAR.ETH, together with the BSW modules from the MICROSAR.MCAL and
MICROSAR.EXT that are available separately, forms a complete communications stack for Ethernet and TCP/IP.
> You will still need the following BSW modules to interface MICROSAR.ETH to the hardware:
> Hardware-specific Ethernet driver (ETHDRV from MICROSAR.MCAL)
> Hardware-specific transceiver driver (ETHTRCV from MICROSAR.EXT)
> Optional: Hardware-specific Ethernet-Switch driver (ETHSWTDRV from MICROSAR.MCAL and ETHSWTDRV EXT
from MICROSAR.EXT)
> The modules in MICROSAR.MCAL and MICROSAR.EXT are available for many microcontrollers and transceivers.
> If PDUs should be passed to other software modules of the AUTOSAR stack, you will in most use cases also require the
PDU Router (PDUR) module from the MICROSAR.COM package.
> The modules of the MICROSAR.SYS package can be used to control the Ethernet stack and TCP/IP stack:
> COMM: Central coordination point for starting up and shutting down the communication stack
> NM: Central coordination point for network management
> BSWM: Mode management module, used for service discovery
> STBM: Higher-level time coordinator used for time synchronization between different networks and bus systems.
> DET: Detects and evaluates errors during the development period
> DEM: You can use the DEM module from the MICROSAR.DIAG package to manage the detected system events (errors
and environmental data).
29
MICROSAR
> MICROSAR XCP enables measuring and calibrating according to ASAM XCP. The module was especially optimized for
use together with CANoe.XCP and CANoe.AMD as well as CANape. For Ethernet ECUs, MICROSAR XCP contains the
related transport layer ETHXCP.
> VX1000If: For safety reasons, very often it is not allowed to keep the measurement and calibration interfaces active in
serial production projects. The module VX1000If allows to keep the VX1000 measurement and calibration hardware
driver in the BSW also in serial production, but in a deactivated mode. Through an API the VX1000 driver can be released
again for check and development purposes. Delivery of the module must take place within a MICROSAR SIP to receive
approval for this use case in serial production. The activation of the VX1000 driver within a serial production project at
runtime however is also not allowed when using the module VX1000If.
> The Vehicle-to-Grid application cases are covered by the modules of the MICROSAR V2G package. Also building upon
MICROSAR.ETH are the modules from MICROSAR AVB that are available for audio/video bridging.
8.6
With the CANoe option ".Ethernet" you can conveniently extend your existing CANoe installation to include the ability to
analyze and simulate Ethernet-based communication.
The VN5610 network interface is recommended as the hardware interface, especially when BroadR-Reach is used as the
physical layer. Along with two Ethernet channels (individually configurable for BroadR-Reach or 100BASE-TX), it also offers
two High-Speed CAN channels.
8.7
Figure 18: Vector offers you a comprehensive range of products and services for your Ethernet projects
30
MICROSAR
MICROSAR V2G 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
infrastructure.
The MICROSAR V2G (Vehicle-to-Grid) package contains BSW modules for intelligent charging of electric and hybrid vehicles
and for communication with the infrastructure over Internet technologies such as HTTP. All of the modules from this package
are not specified in AUTOSAR. However, they are integrated in the Vector AUTOSAR solution. The extensions are offered for
both AUTOSAR 4.x and AUTOSAR 3.x. Required as a basis for MICROSAR V2G are modules from them MICROSAR.ETH
package. You will find details on this in section 9.5.
Figure 19: The MICROSAR V2G BSW modules according to AUTOSAR 4.2
9.1
Application Areas
MICROSAR V2G lets you perform intelligent charging of electric and hybrid vehicles at a suitable charging station. Supported
are the standards
> ISO 15118 and
> DIN 70121
with their options of charging by AC or DC current.
You can use the modules of the MICROSAR V2G package to also have your ECU communicate with a server via commonly
used Internet protocols.
If necessary, the communication may also be encrypted.
31
MICROSAR
9.3
Functions
Configuration
The modules of the MICROSAR V2G package are configured with DaVinci Configurator. You will find more details in the
separate product information.
The specific configuration parameters are saved as an extension in the "ECU Configuration Description".
9.5
MICROSAR V2G builds upon the MICROSAR.ETH package and requires the Ethernet stack and TCP/IP stack as a basis for
communication. It comprises the following modules:
> Ethernet Interface (ETHIF) for abstracting the underlying hardware
> Ethernet State Manager (ETHSM) for switching Ethernet-based communication on and off
> The TCP/IP stack (TCPIP) with the related IP Version (IPv4 and/or IPv6)
Also needed are an Ethernet driver (ETHDRV) from MICROSAR.MCAL and an Ethernet transceiver driver (ETHTRCV) from
MICROSAR.EXT. Special drivers and transceiver drivers for Powerline Communication (PLC) are available for Smart Charge
Communication here.
If the control of Smart Charge Communication is implemented via an AUTOSAR software component, we recommend the
use of MICROSAR.RTE.
The module DET from MICROSAR.SYS is available for detecting and evaluating errors during the development period.
The module DEM from the MICROSAR.DIAG package can be used to manage detected system events (errors and
environment data).
9.6
You can conveniently extend your existing CANoe installation to include the ability to analyze and simulate Ethernet-based
communication with the related CANoe Option for Ethernet. The Smart-Charge-Communication Add-On, which is available
free-of-charge, also lets you analyze SCC data traffic in CANoe. This lets you set up complex vehicle and charging station
simulations based on the DIN standard.
Vector offers a plug-in card for Powerline Communication for the VT system.
32
MICROSAR
9.7
Figure 20: Vector offers you a comprehensive range of products and services for your Ethernet/V2G projects
33
MICROSAR
10 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 AVTP (Audio/Video Transport Protocol), RTP (Transport
Protocol for Real-Time Applications), SRP (Stream Reservation Protocol), PTP (Precision Time Protocol) and on request also
BMCA (Best Master Clock Algorithm). This makes it possible to implement AVB end points as well as bridge functionality.
Figure 21: Figure 1: The MICROSAR AVB BSW modules according to AUTOSAR 4.2
34
MICROSAR
35
MICROSAR
The modules in MICROSAR.MCAL and MICROSAR.EXT are already available for many microcontrollers and transceivers, and
they will be also developed for new microcontrollers and transceivers as necessary.
10.6 Additional Relevant MICROSAR Modules for Ethernet
> TCPIP, SOAD, DOIP, SOME/IP from MICROSAR.ETH
> DCM and DEM from MICROSAR.DIAG
> DET, ECUM, COMM and NM, from MICROSAR.SYS
> MICROSAR XCP
10.7 Other Relevant Products for Ethernet
The CANoe option ".Ethernet" lets you conveniently extend your existing CANoe installation to include the ability to analyze
and simulate Ethernet- and AVB-based communication.
The VN5610 network interface is recommended, especially when BroadR-Reach is used as the physical layer. Along with two
Ethernet channels (individually configurable for BroadR-Reach or 100BASE-TX), it also offers two High-Speed CAN
channels.
10.8 The Vector Toolchain for Developing Ethernet/AVB ECUs
Figure 22: Vector offers you a comprehensive range of products and services for your Ethernet/AVB projects
36
MICROSAR
37
MICROSAR
> When a flash memory is used: Flash EEPROM Emulation (FEE) e.g. from MICROSAR.MEM and a flash driver (FLSDRV)
that is suitable for your hardware included in the service of our MCAL Integration Package, or for external memory the
module DRVEXT from MICROSAR.EXT. To manage the data, the FEE module needs at least two physical flash sectors.
> When using an EEPROM: EEPROM Abstraction (EA) from MICROSAR.MEM and an EEPROM driver (EEPDRV), for
example the module DRVEXT from MICROSAR.EXT for external memory.
It is possible to mix multiple flash and EEPROM chips in one ECU.
For special requirements, Vector offers platform-optimized solutions, e.g. for using the BSW module EA in data flashing or
optimizing the FEE module for specific hardware.
Beyond the standard, MICROSAR.MEM contains the following important services:
> Fixed, predefined maximum execution times for all MICROSAR.MEM functions. This enables system optimizations to
shorten access times.
> NVM: Allocates RAM for CRC memory storage
> NVM: Dedicated interface for the DCM diagnostic module for direct read-out and modification of data blocks
> NVM and EA: Additional configurable transaction security, which is a standard feature of the FEE module
> FEE: High-performance administration of stored memory data
> FEE: Common usage of FEE module by Flash Bootloader (FBL) and application possible - also with common memory
blocks. An update of the ECU software can be done without adjustment of the FBL.
> FEE/EA: Redundant storage of management data for increased reliability of data access
> FEE: Flexible placement of the FEE sectors in the DataFlash
> FEE: Services for handling of undervoltage situations
> FEE: Frequently used data is isolated from extremely important data by introducing partitions. This further increases
data availability in fault situations (e.g. reset while writing or erasing data).
The following function is optional:
> NVM: Block type DATASET_ROM with multiple ROM blocks
> FEE: Update support for adjustment of non-volatile memory after ECU re-programming. This is done with a new
configuration table (content and size).
> FEE: The variant "Small sector FEE" is recommended in case a Flash Memory with a numerous amount but small sized
sectors is used. It offers two main benefits:
> less management data needs to be stored, offering more space for user data
> a faster evaluation of the valid data set version, which makes power-up faster, as well as data storage
11.4 Configuration
We recommend DaVinci Configurator Pro for a convenient configuration. This contains certain functions that make work
simpler, such as optimization assistance, visual representation of flash utilization, etc. See the separate product information
for more details.
38
MICROSAR
Figure 24: Configuration of the MICROSAR.MEM modules with DaVinci Configurator Pro
39
MICROSAR
40
MICROSAR
> COMM: The Communication Manager monitors the state changes of the communication channels connected to the
ECU and of the sub-networks configured in the ECU. It can keep the ECU awake and ready for communication as
necessary. Furthermore, it coordinates access of all SWCs to the communication channels and sub-networks. Optionally,
COMM supports the bus type Internal.
> BSWM and COMM: Support of partial networking
> DET: The Development Error Tracer collects the development errors of the SWCs and BSW modules. Optionally, DET
supports the Service Ports.
> ECUM: The ECU State Manager is responsible for Startup, Shutdown and WakeUp. In AUTOSAR 3.x, there are other
fixed defined operating states that are managed by the ECUM. In AUTOSAR 4.x, these operating states are flexibly
defined by the user in the BSWM. This makes it possible to implement individual energy-saving states or different
power-up behaviors.
> SCHM: The Schedule Manager/BSW Scheduler coordinates execution of the BSW modules. In configuring you define
tasks and the cycle times of the BSW modules. You also define the exclusive areas settings for each module centrally.
For AUTOSAR 3.x, SCHM is part of MICROSAR.SYS. In AUTOSAR 4.x, the MICROSAR.RTE assumes the functionality of
the SCHM.
> WDGM and WDGIF: The Watchdog Manager monitors the correct operation of the functional software with the
modules WDGIF and WDGDRV (MICROSAR.MCAL).
MICROSAR.SYS contains the following important services that extend beyond those of the AUTOSAR standard:
> COMM: Compatibility with OSEK NM (for AUTOSAR 3.x)
> WDGM, WDGIF: Precise supervision of defined time windows for the watchdog (even for high resolution window
watchdogs)
> ECUM: The ECUM module is implemented according to the AUTOSAR ECUM Flex specification, so it offers a high level of
configuration options that can also support complex state transitions. When ECUs are being developed that have
reduced requirements for state management, the ECUM module can optionally also behave compatibly with the
AUTOSAR ECUM Fixed Specification. In this case, the ECUM module offers the following functionalities:
> ECUM Run Request Protocol
> ECUM State Management
> ECUM Fixed Compatible Service SWC interfaces
The following BSW modules are available as options:
> CSM: The Crypto Service Manager gives the SWCs and the BSW modules uniform access to cryptographic functions
such as AES 128 encryption (Advanced Encryption Standard).
> STBM: The Synchronized Time-Base Manager enables precise time synchronization between different parts of the ECU
software. It does this by making one or more common time bases available to the BSW modules and the SWCs. The
relevant Tsyn modules for the CAN, FR and ETH bus systems are available to serve as a communication service for
vehicle-wide time synchronization of ECUs.
> WDGM: Program flow and deadline monitoring to observe the SWCs.
> Post-build loadable and Post-build selectable: For details, please refer to the section "MICROSAR Variant Handling".
12.4 The Basis Software Manager (BSWM)
The BSWM is a central part of the mode management and is implemented according to the AUTOSAR 4 standard. However,
numerous helpful features beyond the standard offer extended comfort while configuring your ECU software.
To react on mode changes in other BSW modules or to request such mode changes, the BSWM module in AUTOSAR 4 allows
free configuration of arbitrage rules, logical expressions and actions.
Due to the given AUTOSAR configuration structure, this may become very complex within short time because of the fact
that even simple configurations request numerous intertwining steps:
41
MICROSAR
Figure 26: pre-configured state machine / auto-configuration of the BSWM with DaVinci Configurator Pro. Also visible: the auto-configuration for
module initialization and communication control and the area for your project related configuration of the BSWM (Custom Configuration).
Though this is not a static configuration, rather all necessary parameters are considered. If parameters are changed, e.g. if a
new PDU group is created, the tool will recognize this immediately and will inform the user about a necessary reconfiguration.
The built-in assistants of DaVinci Configurator Pro also support free configuration tasks such as creating rules or action lists.
They guide you through the configuration, offer know-how on possible and necessary parameters and they identify mistakes
and offers possible corrections. However, they also accept settings which you intentionally want to set differently.
The MICROSAR BSWM provides a lot more than specified by AUTOSAR. As an example, it is also possible to switch on and
off the analysis of rules at runtime. You can realize a timer whose expiration can be analyzed by the BSWM. The timer can be
started and stopped by actions. If not all SWCs which you have to connect are available yet, the BSWM itself can create all
necessary mode declarations and hereby allow you to perform a bottom-up configuration.
12.5 Watchdog for ISO 26262 applications
All watchdog modules are also available as SEooCs (Safety Element out of Context) for safety-relevant functions up to ISO
26262 / ASIL D. They are well suited for validation of run-time monitoring of tasks as well as flow control for the SWCs. For
more details, please refer to the chapter about MICROSAR Safe.
42
MICROSAR
12.6 Configuration
For convenient configuration, we recommend the DaVinci Configurator Pro. For more details, please refer to the separate
Product Information.
Figure 27: Configuring the COMM module with DaVinci Configurator Pro
43
MICROSAR
44
MICROSAR
MICROSAR DIAG can be used for legal requirements of today and tomorrow, such as EURO VI. Support of OBDII (ISO
15031/ SAE J1979) and WWH-OBD (ISO27145) is available as an option.
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.
13.3 Functions
The BSW modules in MICROSAR.DIAG contain the functions for the three BSW modules DCM, DEM and FIM that are
defined in AUTOSAR 4.x and 3.x:
13.3.1 Diagnostic Event Manager (DEM) Functions
The OEM-specific DEM module contains the implementation of the respective OEM requirements concerning the fault
memory of an ECU. The OEM-independent variant is available for AUTOSAR 4.x as well as 3.x. It supports the following functions as standard features:
> Management of all DTC status bits according to the UDS standard
> Definition of individual snapshots and extended records
> Predefined extended records (e.g. OccurenceCounter)
> Counter and time-based error de-bounce algorithms
> Suppression of low-priority errors when memory is full
> Flexible unlearning (aging) of errors
> Variants handling for diagnostic configuration
> Link time configuration
> Compressed Configuration Data to optimize code size
> Support of combined errors
> Suitable for "mixed AUTOSAR" projects
The following functions are available as options:
> OBDII (ISO 15031 / SAE J1979)
> WWH-OBD (ISO27145)
> Post-build loadable and Post-build selectable: For details, please refer to the section "MICROSAR Variant Handling".
The DEM base functionality differs only a little between AUTOSAR 4.x and 3.x, except for the interface definitions. That is
why Vector offers a migration solution that you can use to easily migrate your AUTOSAR 3.x compatible SWCs to an
AUTOSAR 4.x project.
13.3.2 Diagnostic Communication Manager (DCM) Functions
The DCM implements UDS and OBDII services in the ECU.
The OEM-independent variant of the DCM is available for both AUTOSAR 4.x and 3.x. For a complete list of supported
services, please refer to the table at the end of this chapter about MICROSAR.DIAG.
The DCM modules for specific OEMs implement the specifications of the particular OEM. Therefore, the lists of supported
services vary, e.g. in supplemental support of ResponseOnEvent or LinkControl. We would be glad to provide you with
detailed information on this. In addition, the DCM contains the following extensions as standard features:
> Variant handling for diagnostic configurations
> Easy integration of the Vector Flash Bootloader
> Generation of an application code template for the ECU software (AUTOSAR 3.x)
> J1939DCM: DCM module specially designed for heavy-duty vehicles
45
MICROSAR
Figure 29: Parameterization of the MICROSAR.DIAG modules is done with CANdela Studio.
46
MICROSAR
Figure 30: Parameterization of MICROSAR.DIAG is done by CANdela Studio and DaVinci Configurator Pro
Service ID
(hex)
AUTOSAR 4.x:
The SWC has to
AUTOSAR 3.x:
The SWC has to
10
ECUReset
11
- (handled in DCM/BSWM)
- (handled in DCM/BSWM)
SecurityAccess
27
CommunicationControl
28
- (handled in DCM/BSWM)
- (handled in DCM/BSWM)
TesterPresent
3E
47
MICROSAR
Service ID
(hex)
AUTOSAR 4.x:
The SWC has to
85
AUTOSAR 3.x:
The SWC has to
- (handled in DEM module)
22
ReadMemoryByAddress
23
via callout
via callout
ReadDataByPeriodic Identifier
2A
DynamicallyDefineData Identifier
2C
WriteDataByIdentifier
2E
WriteMemoryByAddress
3D
via callout
via callout
19
ClearDiagnosticInformation
14
2F
31
The module DCM from MICROSAR.DIAG optionally supports the following OBD II Diagnose Services:
Diagnostic Service Name
(ISO 15031-5)
Service
ID
(hex)
01
handle data acquisition for each PID other than the "supported ID"
and DEM ones
02
03
04
06
07
08
09
0A
Figure 32: OBD2 UDS diagnostic services for the module DCM
48
MICROSAR
49
MICROSAR
14.3 Functions
The MICROSAR.MCAL package contains the driver modules CAN, ETH, FR, LIN, and IIC, and in the version for AUTOSAR 4.x
the RamTst test module. The modules conform to AUTOSAR 4.x and are available for many different available
microcontrollers. With AUTOSAR 4.2, the ethernet switch driver is included in the delivery.
In addition, MICROSAR.MCAL contains the following extensions:
> CANDRV: Notification (Callback) on message reception and after successfully sending a message. This allows to automatically execute application-specific code.
> FRDRV: Supports self-diagnostics. When the FlexRay controller detects an error, it notifies the application so that it can
call up the error status.
The following functionalities or modules are available as options:
> CANDRV: Option HighEnd offers extended filter options for Multiple Basic CAN objects, RX queue to shorten the
interrupt time during reception, individual polling of mailboxes to assure data consistency and reduction of interrupt
load.
> IICDRV: The IICDRV contains drivers for interfacing to external peripheral chips via the Inter-Integrated Circuit Bus (I2C)
(AUTOSAR extension).
> Post-build loadable / Post-build selectable: these features are available as options for several determined MCALs.
14.4 Configuration
For convenient configuration, we recommend the DaVinci Configurator Pro. For more details please refer to the separate
product information.
Figure 34: Configuration with the DaVinci Configurator: Clock settings based on example of Freescale MPC560xB (Bolero)
50
MICROSAR
integrate it- and create supplemental packages which allow to embed the 3rd party Software into the Vector embedded
software and the Vector tool chain.
Before delivery of the stack, the MCAL by default is removed again so that at customer side the desired packages have to be
supplemented. A script is provided with the delivery which to a large extend automates the merge of all packages and applies
indispensable changes to the packages of the semiconductor vendor. This allows an independent update of the MCAL by the
customer at any point in time.
In case of an update of the used MCAL you can of course request the service of our MCAL integration package again.
This service portfolio for the provided MCAL makes on-site setup of the MCAL easy to a large extend, so that your team can
focus on the development of your application.
The MCAL Integration Package contains the following services:
51
MICROSAR
52
MICROSAR
53
MICROSAR
15.3 Functions
The BSW modules in MICROSAR.EXT contain functions defined in AUTOSAR 4.x plus the following extended functions:
> Bus error detection on FlexRay
> LIN transceiver drivers (also for AUTOSAR 3.x)
> Ethernet transceiver drivers, also for Powerline Communication (PLC) and Wireless LAN (WLAN) (AUTOSAR 4.x and
3.x)
> Ethernet Switch driver
The MICROSAR SBC driver is available as an option. It supports different peripheral devices such as transceivers and
watchdogs depending on the specific hardware used. It makes it easy to link external peripherals to the MICROSAR software.
Please inquire about the exact functional scope of the SBC driver in reference to the hardware you are using. Optionally, the
SBC driver can also be offered within the solution SafeBSW and is available from ASIL A to ASIL D.
A generic SBC driver is also available which gives you access to the SBC registers to implement control functions for the SBC
hardware.
15.4 Configuration
For convenient configuration we recommend our DaVinci Configurator Pro. For more details, see the separate product
information.
54
MICROSAR
55
MICROSAR
Figure 40: Configuration of the DIOHWAB module with DaVinci Configurator Pro
16.3.2 IOHWAB
Using DaVinci Developer, you can create an IOHWAB SWC description and implement it into the SWC design afterwards
with only little effort. Beyond this, the MICROSAR.RTE or the DaVinci Developer Option .CPG both offer the possibility to
directly create a code template for your individual IOHWAB implementation from this IOHWAB SWC description. The code
template is enhanced by ECU specific algorithms (debouncer, signal filters, etc.) by the development engineer and connected
to the MCAL API's.
56
MICROSAR
57
MICROSAR
17 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).
58
MICROSAR
> Contract Phase Generation for developing individual SWCs in an early phase. In this case, the generator just creates a
header file for each SWC instead of the entire RTE. This makes it possible to compile the SWCs individually, e.g. to
transfer them to a development partner as object code.
> RTE generation for the entire ECU software. The code generated in this mode is highly efficient and requires only little
memory space. It is optimized for the entire ECU configuration and makes few demands on system resources due to
short execution times and minimal interrupt disable times. One way this is achieved is by using intelligent
synchronization mechanisms that are tuned to the properties of the hardware used.
17.3 Functions
MICROSAR.RTE is compatible with AUTOSAR 4.x and 3.x. Specifically, MICROSAR.RTE contains the following functionality:
> Sender/Receiver and Client/Server communication
> Mode management
> InterRunnable variables as well as Exclusive Areas.
> Access to Nv block software components via sender/receiver ports
> Trigger for runnables
> Online and offline calibration of SWCs are supported as well as measurement of S/R ports, InterRunnable variables and
Per-Instance memory using the XCP protocol.
> Multiple instancing of SWCs and per-instance memory.
> Schedule Manager/BSW Scheduler (SCHM): Since AUTOSAR 4.0, the RTE has assumed the functionality of the SCHM
module. This was previously contained in MICROSAR.SYS. For more information on the SCHM module, please refer to
the chapter about MICROSAR.SYS.
> Support of the transformer interfaces for COMXF, SOMEIPXF and E2EXF. For details please refer to the chapter
MICROSAR.COM.
> External Client/Server communication (Inter-ECU) through the optional SOMEIPXF.
Beyond the standard, MICROSAR.RTE for AUTOSAR 3 includes the following important services:
> Generation of code templates for SWCs based on the SWC Description. These templates contain all APIs of the RTE.
> Use of memory protection mechanisms as specified in the AUTOSAR operating system. This support is especially
optimized when MICROSAR.OS is used.
> Configuration of initialization runnables for the AUTOSAR concept of Mode-Dependent Runnables.
> Generation of an HTML report showing RTE properties. It contains information such as the calculated RTE resource load
(RAM + constants).
> Generation of an A2L file for simple linkage to existing calibration and diagnostic standards.
The following functionalities are available as options:
> MPU support for memory protection
> Multi-core support
> Post-build selectable: within the MICROSAR product family, this feature is available in the module "Identity Manager".
For details please refer to the section "MICROSAR Variant Handling".
Optional features available upon request:
> Support of internal, external and background runnable triggers (for AUTOSAR 4.x)
> Scaling of ports and signals (for AUTOSAR 4.x)
> Range checks (for AUTOSAR 4.x)
59
MICROSAR
Figure 42: MICROSAR.RTE enables generation of code templates for the SWCs
60
MICROSAR
61
MICROSAR
Figure 44: MICROSAR AMD enables easy access to internal ECU information in interplay with CANoe.AMD
18.3 Functions
The functionality of the DBG (Debugging) and DLT (Diagnostic Log and Trace) modules is specified in AUTOSAR 4.x.
Nonetheless, it is already available from Vector for AUTOSAR 3. In addition to the AUTOSAR standard, MICROSAR AMD
offers the ability to determine CPU load and any execution times.
For display and analysis, the values read out with MICROSAR AMD are transmitted to an XCP Master via the XCP Slave.
You can use one of the following Vector tools as the XCP Master on the PC side:
> CANape together with MICROSAR modules DLT und DBG
> CANoe.AMD from Version 8.1 together with MICROSAR modules DLT, DBG and RTM.
With these tools and a description of the measurement objects in the form of an ASAM A2L file, you can select internal ECU
data and analyze its flows. CANape was extended for AMD with the Digital Window and the Status signal display.
CANoe.AMD was extended with the special State Tracker window. This lets you display separate states and binary signals
in a well-organized layout in one window.
Figure 45: Evaluating status changes with the State Tracker Window in CANoe.AMD
62
MICROSAR
63
MICROSAR
18.4 Configuration
For user-friendly configuration, we recommend DaVinci Configurator Pro. You will find more details on this in the separate
product information.
18.5 Scope of Delivery
MICROSAR AMD consists of the following components
> Software modules as source code
> A2L Generator (for Windows XP/Windows 7)
> BSW Module Description files
> Documentation
18.6 Other relevant products
Prerequisites for using MICROSAR AMD are the following Vector software modules:
> the simultaneous use of MICROSAR XCP for CAN, FlexRay or Ethernet, or
> VX1000 systems from Vector. These are advisable for maximum data throughput with minimal effects on execution
time. You will find details on this at our product website: www.vector.com/vx. For safety reasons, very often it is not
allowed to keep the measurement and calibration interfaces active in serial production projects. The module VX1000If
allows keeping the VX1000 measurement and calibration hardware driver in the BSW also in serial production, but in a
deactivated mode. Through an API the VX1000 driver can be released again for check and development purposes.
Delivery of the module must take place within a MICROSAR SIP to receive approval for this use case in serial production.
The activation of the VX1000 driver within a serial production project at runtime however is also not allowed when using
the module VX1000If.
64
MICROSAR
19 MICROSAR Safe Functional Safety according to ISO 26262 up to ASIL D for ECU software
The ISO 26262 safety standard defines criteria by which safety-related ECUs shall be developed in the automotive field.
MICROSAR Safe from Vector gives you a solution for implementing safety-related functionality up to the highest safety level
(ASIL D) in an AUTOSAR project.
AUTOSAR basic software developed according to ISO 26262 can help to reduce the number of partitions in the system and
hereby can contribute to a higher performance. Many of our MICROSAR BSW modules are developed with the methods of
ISO 262162/ASIL D and subsequently are able to co-exist with safety relevant SWCs without partitioning. Beyond this,
further safety requirements can be implemented into the BSW if necessary.
Figure 47: MICROSAR Safe Module according to AUTOSAR 4.2. Additionally to the above indicated, further modules are available as ASIL software,
such as OESK NM or OEM specific software components.
65
MICROSAR
MICROSAR Safe enables "freedom from interference" in executing safe software parts with different ASIL and non-safe
software parts (QM software) on the same ECU (Mixed-ASIL systems). MICROSAR Safe is the result of many years of
experience in the field of functional safety.
19.3 Functions
For projects according to the AUTOSAR 4 standard, MICROSAR Safe contains safe basic software with its core products
SafeOS, SafeE2E and SafeWatchdog. They comply with the AUTOSAR specification and are compatible with all of the
remaining MICROSAR modules which optionally can be provided in the context of SafeBSW as well. Beyond this, MICROSAR
Safe also provides a SafeRTE.
The combination of SafeOS, SafeE2E and SafeWDG is the minimum expansion stage which is necessary for mixed-ASIL
systems (ECUs which contain both ASIL functions and functions without safety relevance). An extension of this mandatory
package is possible according to your specific requirements - up to a full BSW stack according to ASIL D.
Figure 48: MICROSAR Safe with SafeRTE and SafeBSW according to AUTOSAR 4.2
66
MICROSAR
The SafeWDG package implements the interface to an internal or external hardware watchdog with the help of the modules
WDGIF, WDGDRV resp. WDGDRVEXT and -on demand- can support external system basis chips (SBC) as well.
19.3.4 SafeRTE safe ECU-internal communication
MICROSAR.RTE supports partitioning of memory sections via the operating system's option "SafeOS". According to ISO
26262, a qualification of the RTE is necessary to establish a safe communication between applications within an ECU. The
static analysis tool "RTE Analyzer" is available as option for this purpose.
19.3.5 Validation of the hardware
The modules of MICROSAR Safe assume a safe hardware within the customer project. If this requirement is not fulfilled by
the hardware, you may also accomplish this by suitable software test functions. This requires that you consider the project
specific safety goals.
SafeOS already offers auxiliary functions in reference to the MPU. Other functions for validating the RAM, Flash, MPU, IO,
etc. can be provided by Vector in the context of project work.
19.4 Configuration
We recommend that you use the DaVinci Configurator Pro tool to configure the BSW modules of MICROSAR Safe.
19.5 Scope of Delivery
MICROSAR Safe is developed according to the AUTOSAR 4 standard. In addition to the BSW modules every delivery of
MICROSAR Safe also comes with the required safety manuals for the modules developped according to ASIL. The delivered
software package altogether is one single SEooC for which Vector will provide a corresponding project specific Safety Case
document.
MICROSAR Safe is also available for AUTOSAR 3 projects, enabling you to realize Mixed-ASIL projects according to this
standard. The aspect "freedom from interference" in this case is supported by the functionalities MPU support including safe
context switch, runtime measurement and safe external communication. MICROSAR Safe for AUTOSAR 3 contains SafeOS,
SafeE2E and SafeWDG, plus SafeCRC.
19.6 Implementation
Safety-relevant functions are supported by the above mentioned core products from MICROSAR Safe. They conform to the
AUTOSAR specification, are developed according to ISO 26262/ ASIL D and in detail contain the following features:
package
SafeOS
content
> Memory protection and safe context switching (option for MICROSAR.OS)
> Timing Protection (Option for MICROSAR.OS)
SafeE2E
SafeWDG
67
MICROSAR
Figure 49: Security modules according to AUTOSAR 4.2: Via CSM it is possible to use a hardware which conforms to the Standard Secure Hardware
Extension (SHE).
68
MICROSAR
Hash functions
Checksum
Random numbers
Data Stream
ECB Mode
CBC Mode
CAL
Algorithms
Hash
Yes
Yes
Yes
Yes
Checksum
Yes
Yes
Yes
CRC-16, CRC-32
RandomGenerate
No
Yes
Yes
FIPS-186
RandomSeed
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
MacGenerate
Message Authentication Code
CSM
MacVerify
SymBlockEncrypt
SymBlockDecrypt
SymEncrypt
SymDecrypt
Yes
Yes
Yes
HMAC-RIPEMD-160,
HMAC-SHA-1,
HMAC-SHA-256
AES, DES,
Triple DES, RC2
AES, DES,
Triple DES, RC2
69
MICROSAR
Service
Key generation
Key management
Asymmetrical encryption
Signature
Key exchange
Key Extraction
Wrapping asymmetric private Key
using public Key
Compression
Data Stream
CSM
CAL
KeyDerive
Yes
Yes
Yes
SymKeyGenerate
No
Yes
No
KeyDeriveSymKey
No
Yes
No
SymKeyUpdate
Yes
Yes
No
SymKeyExtract
Yes
Yes
Yes
SymKeyWrapSym
Yes
Yes
Yes
AsymPrivateKeyWrapSym
Yes
Yes
Yes
AsymEncrypt
Yes
Yes
Yes
AsymDecrypt
Yes
Yes
Yes
SignatureGenerate
Yes
Yes
Yes
SignatureVerify
Yes
Yes
Yes
KeyExchanageCalcPubVal
No
Yes
Yes
KeyExchangeCalcSecret
Yes
Yes
Yes
KeyExchangeCalcSymKey
Yes
Yes
No
SymKeyWrapAsym
Yes
Yes
Yes
AsymPrivateKeyUpdate
Yes
Yes
No
AsymPublicKeyUpdate
Yes
Yes
No
AsymPublicKeyExtract
Yes
Yes
Yes
AsymPrivateKeyExtract
Yes
Yes
Yes
AsymPrivateKeyWrapAsym
Yes
Yes
Yes
Compress
Yes
Yes
Yes
Decompress
Yes
Yes
Yes
Algorithms
PKCS #5 V2.0
X9.63
EDHC
20.4 Configuration
We recommend that you use the DaVinci Configurator Pro configuration tool for easier configuration of the modules of
MICROSAR Security. For more details, please see the separate product information.
20.5 Implementation
> Either the Crypto Abstraction Library or the Crypto Service Manager is offered according to specific needs
> The necessary security algorithms are available as a software implementation in both CPL and CRY
> Upon request, internal or external security hardware, e.g. per HIS-SHE, can be supported
70
MICROSAR
71
MICROSAR
Figure 52: Mapping SWCs, tasks and OS instances to the processor cores - schematic diagram
We recommend the use of DaVinci Configurator Pro to make it easy to configure your ECU. You will find more details on this
process in the separate product information.
72
MICROSAR
73
MICROSAR
74
MICROSAR
75
MICROSAR
Figure 55: One ECU performs different functions with use of the Identity Manager
76
MICROSAR
23 MICROSAR J1939 AUTOSAR Basic Software Modules Specially Designed for Heavy-Duty Vehicles
In this section, we introduce the BSW modules defined in the AUTOSAR architecture for communication in J1939 networks:
The network manager J1939NM, the request manager J1939RM, the transport protocol J1939TP and the diagnostic module
J1939DCM. These modules are part of MICROSAR.CAN and MICROSAR.DIAG.
77
MICROSAR
>
Post-build loadable and post-build selectable: For details, please refer to the section "MICROSAR Variant Handling".
23.4 Configuration
We recommend our DaVinci Configurator Pro for convenient configuration. You will find more details in the separate product
information.
23.5 Other Relevant MICROSAR Products for J1939
> DEM from MICROSAR.DIAG
> DET, BSWM, ECUM and COMM from MICROSAR.SYS
> MICROSAR XCP enables measuring and calibrating according to ASAM XCP. The module was optimized, especially with
regard to its use in conjunction with CANoe.XCP, CANoe.AMD and CANape. MICROSAR XCP contains the related
transport layer CANXCP for CAN ECUs.
> Beyond the AUTOSAR standard, MICROSAR XCP supports generic readout of measuring objects. As a result, no
addresses must be defined and updated in the a2l file. Data from any version or variant can be extracted with an a2l file
independent from the MCU build. The generic readout feature requires usage of CANoe.AMD or CANape as XCP tool.
> For safety reasons, very often it is not allowed to keep the measurement and calibration interfaces active in serial
production projects. The module VX1000If allows keeping the VX1000 measurement and calibration hardware driver in
the BSW also in serial production, but in a deactivated mode. Through an API the VX1000 driver can be released again
for check and development purposes. Delivery of the module must take place within a MICROSAR SIP to receive
approval for this use case in serial production. The activation of the VX1000 driver within a serial production project at
runtime however is also not allowed when using the module VX1000If.
78
MICROSAR
vVIRTUALtarget (VTT) offers the right solution for this situation. It is a runtime environment in which ECU software can be
executed without requiring access to a real ECU. This environment enables decoupling of test execution from the real
hardware and from the existence of the basic software. This, in turn, leads to substantial time advantages. The same
configuration can be used for both the target hardware and the environment of vVIRTUALtarget:
After development of the SWCs and their system integration, the ECU software and its parameterization are at an
advanced stage. Along with developing the application, another focus is on configuring the basic software. Here,
vVIRTUALtarget enables testing that is independent of the target platform.
79
MICROSAR
80
MICROSAR
application. Debugging can be performed afterwards. Our solution vVIRTUALtarget is developed for Microsoft Visual Studio
2013 (Express & Professional).
Two options are available for debugging: One option is to debug directly in the runtime environment of vVIRTUALtarget.
Another approach is to use CANoe as the runtime and debugging environment. This lets you stimulate and visualize the buses
and I/O interfaces of the generated SUT DLL.
24.3.2 vVIRTUALtarget in conjunction with MICROSAR.MCAL and MICROSAR.OS
The BSW modules MICROSAR.MCAL and MICROSAR.OS were ported for the use of vVIRTUALtarget. The MCAL interfaces
and behavior conform to AUTOSAR 4 specifications here. The MICROSAR.OS that is available for vVIRTUALtarget
implements the SC1 Scalability Class without multi-core extensions.
The rest of the BSW modules do not require that any modifications be executed in the vVIRTUALtarget environment. The
BSW modules are the same as those used in the real ECU.
24.4 Workflow
The workflow for configuring the BSW modules in the vVIRTUALtarget area does not differ from the approach taken with
the real hardware platform. The only exception is that the MCAL modules specific to the vVIRTUALtarget may need special
settings, if they cannot be automatically derived by the DaVinci Configurator Pro configuration tool.
81
MICROSAR
24.5 Configuration
For convenient configuration, we recommend our DaVinci Configurator Pro. You will find more details in the separate
product information. The vVIRTUALtarget runtime environment is configured via the Option.VTT, which is available for
DaVinci Configurator Pro.
24.6 Product Components
The modules of vVIRTUALtarget are supplied as a Software Integration Package (SIP). The customer may choose to have the
SIP supplied just for the vVIRTUALtarget platform (just vVIRTUALtarget MCAL), or a dual-target SIP can be supplied
together with drivers for a customer-defined real hardware platform (real MCAL & vVIRTUALtarget MCAL).
24.7 System Requirements
Our product vVIRTUALtarget is a 64 bit application and therefore requires a 64 bit system.
24.8 Further relevant MICROSAR Products for VTT
The "AUTOSAR Evaluation Bundle VTT" is available to get to know virtual integration and for testing its functionalities. For
further information, please see chapter "AUTOSAR Evaluation Bundle".
82
MICROSAR
83
MICROSAR
Figure 62: MICROSAR Software Integration Package and its optional supplemental services
84
MICROSAR
To find out which options are available for your automotive OEM, please refer to the OEM-specific product information sheet
that is automatically provided to you with our quotation.
25.2 Extended Integration Package (EIP)
Building upon the MICROSAR.SIP, in conjunction with extended SIP extensions (see above), 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.
Vector employees handle preparations that are normally conducted on-site at the customer. We perform this service at a
fixed price and in the framework of task planning that is detailed in an agreement with you. We can:
> Place a start application in your ECU with a specification-conformant configuration and using the databases
(communication and diagnostics) that are relevant to the project
> Perform other project management jobs such as coordination via regular consultation meetings and project reporting
> Create release planning tailored to your needs
> Perform on-site startup together with you at the end of the EIP service package
> Execute test cases related to the BSW that are required by the OEM
The results of these prepared activities are then also part of the delivery:
> Your basic software package including configured start application
> Release notes
> Write-up of related test reports
Figure 63: The Extended Integration Package and its interaction with the SIP options
85
MICROSAR
86
MICROSAR
26 AUTOSAR Evaluation Bundle The complete package for the evaluation of AUTOSAR basic software
and tools
The AUTOSAR Evaluation Bundle is a comprehensive package of OEM independent AUTOSAR basic software (MICROSAR)
and the tools DaVinci Developer and DaVinci Configurator Pro. This package lets you develop your first ECU software with
AUTOSAR-conformant software architecture. You get an in-depth look into the AUTOSAR world from the design and
configuration process to implementation of the actual basic software. You can obtain OEM-specific BSW modules, e.g. for
diagnostics, in our MICROSAR Prototype SIP (see end of this chapter).
26.1 Overview of advantages
> Tools and basic software in production quality according to AUTOSAR 4.x or 3.x to evaluate the Vector solution for
AUTOSAR
> Enables realistic evaluation of execution time and memory requirements for your ECU project
> Available for many different microcontrollers
> Quick way to train in AUTOSAR with a detailed sample project
> Support of both AUTOSAR-conformant files and conventional description files
26.2 Application Areas
The AUTOSAR Evaluation Bundle supports both the automotive OEM in evaluating AUTOSAR processes and methods
and suppliers in creating a first AUTOSAR-conformant ECU software. Since the tools and basic software are at a level of
production maturity, you can reliably use the Vector solution to evaluate AUTOSAR with regard to:
> Efficiency of the basic software
> Integration of the tools in your development environment
> Potential uses of AUTOSAR concepts in your application area
The AUTOSAR Evaluation Bundle also provides an optimal foundation for initial developments of AUTOSAR-conformant
software components (SWCs) for service providers who focus on the application level.
26.3 Functions
The AUTOSAR Evaluation Bundle contains the tools and embedded software from Vector for creating a complete set of
AUTOSAR ECU software, which consists of software components (SWCs), Run-time Environment (RTE) and basic software
(BSW). The DaVinci tools are tailored to AUTOSAR and simplify your work in designing complex AUTOSAR applications. As
input for configuring the MICROSAR software, you would use an "ECU Extract of System Description" (AUTOSAR XML) or
as an alternative a conventional network description file (DBC, FIBEX, LDF).
> The DaVinci Developer tool gives you an easy way to generate AUTOSAR-conformant ECU applications. Using the
graphic editor, you can describe your AUTOSAR software components quickly and clearly and define their interfaces. The
SWCs serve as a basis for the RTE configuration process, which you also perform with DaVinci Developer.
> The DaVinci Configurator Pro tool is used to configure the basic software modules and the RTE. You can use the
convenient and intuitive user interface to adapt parameter values for your ECU project.
> The CANdelaStudio tool from Vector is also available. It lets you define diagnostic data for your networks and ECUs. You
can export this data via standard formats, and use the data in automatic configuration of the MICROSAR diagnostic
basic software.
87
MICROSAR
Figure 65: Configuration of the Basic Software and the RTE with DaVinci Configurator Pro
The AUTOSAR Evaluation Bundle is available for AUTOSAR 4.x and 3.x. The included MICROSAR basic software modules
efficiently and flexibly implement all functions of the related AUTOSAR Releases. They also contain many extensions that go
beyond the standard.
26.4 Included BSW Packages
The following table gives you an overview of the individual MICROSAR bundles contained in the AUTOSAR Evaluation bundle.
For a complete description of the individual bundles, please refer to the separate chapters in this document.
In EVAL bundle
MICROSAR.OS
Available options
> Implementation of the "Scalability Class" SC1 is standard
> SC2-SC4 are available as options, provided that they are supported by the processor
> Multi-core is available as option
MICROSAR.COM
MICROSAR.CAN
MICROSAR.LIN
MICROSAR.FR
MICROSAR.ETH
88
MICROSAR
In EVAL bundle
MICROSAR.MEM
Available options
> EA module for internal EEPROMs
> FEE module for internal flash memory
> Driver for driving external memory chips in MICROSAR.EXT
MICROSAR.SYS
MICROSAR.DIAG
MICROSAR.MCAL
> IICDRV (driver for interfacing to external peripheral chips via the Inter-Integrated Circuit Bus "I2C")
In addition, the following options can be ordered with the evaluation bundle:
Module
Decription
MICROSAR.EXT
MICROSAR. VTT
MICROSAR Safe
> Complete solution for safety-related functional software according to ISO 26262
89
MICROSAR
90
MICROSAR
27 Additional Information
For further information on our products and our configuration tool DaVinci Configurator Pro, please see our internet site:
http://vector.com/vi_embedded_software_en.html.
91
More Information
www.vector.com