MICROSAR Product Information English - Vector

1 MICROSAR Classic Product Information MICROSAR Classic 2 Table of Contents 1 MICROSAR Classic .. 3 MICROSAR Classic SIP .. 3 MICROSAR Classic autosar Evaluation Bundle .. 5 MICROSAR Classic Safe .. 6 MICROSAR Classic Security .. 7 MICROSAR Classic MCAL Integration Package .. 8 MICROSAR Classic IPC .. 9 MICROSAR Classic Multi-Core .. 10 MICROSAR Classic HSM .. 10 MICROSAR Classic Gateway .. 12 MICROSAR Classic POSIX .. 14 MICROSAR Classic J1939 .. 15 MICROSAR Classic vVIRTUAL target .. 16 MICROSAR Classic Variant Handling .. 16 2 Modules and Add-Ons .. 18 MICROSAR Classic OS .. 19 MICROSAR Classic COM.

2 20 MICROSAR Classic CAN .. 21 MICROSAR Classic FR .. 23 MICROSAR Classic LIN .. 24 MICROSAR Classic ETH .. 25 MICROSAR Classic IPC .. 28 MICROSAR Classic CHARGE .. 29 MICROSAR Classic AVB .. 30 MICROSAR Classic MEM .. 31 MICROSAR Classic SYS .. 32 MICROSAR Classic DIAG .. 34 MICROSAR Classic MCAL .. 36 MICROSAR Classic EXT .. 37 MICROSAR Classic AMD .. 38 MICROSAR Classic IO .. 39 MICROSAR Classic RTE .. 40 MICROSAR Classic OTA .. 42 MICROSAR Classic CRYPTO .. 42 3 Configuration and Toolchain .. 44 4 Further Information .. 45 Contact, Availability and Training .. 45 06/2022 Please consider the environment before printing this document.

3 MICROSAR Classic 3 1 MICROSAR Classic The complete Vector Solution for autosar ECU Software MICROSAR Classic by Vector is the perfect autosar solution for ECU software and consists of Basic Software (BSW), RTE and tooling (DaVinci Tools, PREE vision and TA Tool Suite), covering all aspects of the autosar standard and beyond. MICROSAR Classic is used in countless production projects and offers high value through many years of experience in the implementation of embedded software. All deliveries go through systematic integration tests in advance for the specific conditions of the required application, hardware platform, compiler, CPU device, OEM, with or without RTE, which can be extended to third party software modules ( MCAL drivers) on request.

4 Each BSW module is assigned to clusters and combined in individual Software Integration Package (SIP) for many use-cases. In addition to the autosar requirements, MICROSAR Classic offers a number of functional enhancements. For example, unneeded functions within BSW modules can be deactivated for code optimization, therefor modules can be used for both small and sophisticated applications, from steering angle sensors and door control units to engine control units and central gateways. MICROSAR Classic can also be used with other operating systems such as Linux or QNX and offers flexible licensing and maintenance contracts tailored to individual requirements, which keep the software up-to-date through updates.

5 Vector supports the migration from autosar 3 to 4 with a uniform work flow by customizing the existing application software to the interfaces changed in the autosar 4 standard. In addition, many extensions from autosar 4 have been integrated into existing BSW modules for autosar 3, such as multi-core OS, J1939, XCP, Ethernet/IP or the complete MOST bundle. MCAL drivers from different autosar releases can be combined with MICROSAR Classic. The configuration tools DaVinci Developer Classic and DaVinci Configurator Classic are designed for both releases. All MICROSAR Classic products are compliant with ICC3 (Implementation Conformance Class) and CCC2 (Configuration Conformance Class).

6 As additional services, Vector offers system design consulting, extension of MICROSAR Classic BSW modules according to customer requirements and development of customer-specific software components (SWC), as well as support in customizing existing functional software. In addition, complete software integration into the ECU, including third party software, or migration of existing software into an autosar -based concept can be performed by Vector . A hotline, special workshops and training courses on embedded software and autosar complete the full range of services. MICROSAR Classic SIP Software Integration Package A Quick Start to Your autosar Project The Software Integration Package (SIP) is an integral part of every MICROSAR Classic delivery and with a variable, context-dependent scope of services for every type of project (series, update, beta, prototype).

7 It offers a decisive advantage in the development of ECU software and optimizes the usability of the delivery even with slightly changed boundary conditions. Using a questionnaire, Vector catalogs the requirements in advance in as much detail as possible, on the basis of which the SIP is then built individually. With SIP Maintenance, active error tracking is offered from the first delivery of the Product , providing Information on known errors and corrective measures. In addition, SIP Maintenance includes one SIP update delivery per calendar year (with extended maintenance, two SIP update deliveries per year).

8 With the update SIP we actively help you with the introduction of a new SIP. MICROSAR Classic 4 > Check OEM-specific aspects of the BSW including SWCs and the associated tool chain ( support of OEM data formats for communication and diagnostics) and ensure conformance to OEM specifications > Checking the project-specific combination of BSW components and features for a defined ECU use case > Checking the package under abstract boundary conditions (configurations and initiate database change frequently) with the goal of implementing the broadest possible package (realization of additional variants to the initial configuration and database)

9 > Configuration management tailored to the delivery with assurance of optional subsequent delivery for 10 years > Regular issue reporting Runtime Integration Service The extension "Runtime Integration Service" (RIS) is an additional service to the MICROSAR Classic SIP if it is technically possible for the customer project. It includes a Demo Application based on the ECU specific input data for communication ( ECU extract) and diagnostics ( ECUC). This Demo Application demonstrates basic SIP functionality based on the ordered modules. Examples > Communication: The Start Application included SWCs demonstrate the reception and transmission of one signal on runnable level.

10 The BSW is configured in a way that the system gets initialized and communicates on all communication busses defined in the input data. > Diagnostics: The Start Application included SWCs will be extended by a sample implementation of an RDBI/WDBI service on runnable level. Moreover, it offers the possibility to trigger a DTC. > Memory: The Start Application included SWCs will be extended by a sample implementation to store data to an NV-Block. > POSIX Integration: As an additional service, we optimally tune the POSIX integration to the customer's hardware. For this, the POSIX operating system must support POSIX threads (pthreads) and the POSIX standard IEEE Std Prerequisite for the execution of these tasks is that the required MICROSAR Classic modules are part of the SIP delivery.