Vector Catalog ECU Software EN

Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1

Product Catalog

ECU Software ENGLISH Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite a

Date: March 2011 · Responsible for the contents: Vector Informatik GmbH, Stuttgart, Germany All mentioned product names are either registered or unregistered trademarks of their respective owners. The constant worldwide availability of all products or services is not warranted. No information contained in this catalog may be reproduced without expressed permission, in writing, from Vector Informatik GmbH. Errors and omissions excepted. Illustration & Design: SATZTEAM Fotosatz & Neue Medien GmbH, Eberdingen, Germany Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite b Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/a

Vector – the Company

1/0 Vector provides OEMs and suppliers of automotive and related industries a professional and open development platform of tools, software components and services for creating embedded systems.

Customers worldwide place their trust in the solutions and products of the independent and self-contained Vector Group.

Reliable Partner with Quality For many years, our customers have realized what they have in Vector: a reliable and competent partner for efficient solutions in electronic networking.

This reliability is based upon the factors below: > Global unique processes and standards > All Vector subsidiaries are certified according to ISO 9001:2000 > SPICE level 3 (HIS scope) reached in the area of ECU software > CMMI maturity level 2 reached in the area of software services

Milestones / Key Data 1988 Founding of Vector Informatik GmbH High Customer Satisfaction 1992 Sale of the first CANalyzer license The delivery quality and delivery time as well as consulting compe- 1994 Vector has more than 25 employees tence from Sales, Support, and Consulting are not just maintained 1996 Sale of the first CANoe and CANape license on a high level, but are constantly being improved. 1997 Founding of Vector CANtech, Detroit/USA The success: our customers judge us on a scale of 1 to 5 (where 1 is 1998 Founding of Vector Japan, Tokyo/Japan, the best grade and 5 the worst) with an average grade of 1.6. Vector Informatik is DIN EN ISO 9001:1994 certified 1999 Vector has more than 100 employees worldwide Excellent Working Atmosphere 2001 Move to the new company building in Stuttgart, 70 % of our highly-qualified employees work in the development Founding of Vector Consulting environment. Teamwork in modern structures ensures a working 2002 Vector Informatik is DIN EN ISO 9001:2000 certified, atmosphere that in the past few years has been judged “very good” Founding of Vector France, Paris/France, Founding of VecScan, Göteborg/Sweden, according to internal surveys. Trainees, interns, and graduating Vector has more than 250 employees worldwide students also profit from the many opportunities to work actively 2003 Vector has more than 400 employees worldwide with the newest technologies. Employee turnover at Vector, which 2004 Move to the second company building in Stuttgart, has been extremely low for many years, confirms how each person Founding of customer care center north in Braunschweig at Vector understands his or her work: as mental work with a “fun” and customer care center south in Munich/Germany factor. 2005 Vector has more than 500 employees worldwide 2006 Founding of office in Regensburg/Germany On Location Worldwide Vector has more than 600 employees worldwide For Vector, partnership with its customers means understanding their 2007 Vector has more than 700 employees worldwide requirements. In order to be responsive to our partners quickly and to Start of construction for the third company building be able to act purposefully, we are present worldwide. For optimal in Stuttgart/Germany support on location, the Vector Group has established, in addition to Founding of Vector Korea, Seoul/Rep. of Korea its own locations, a globe-spanning network of distributors. 2008 Vector has more than 800 employees worldwide Move to the third company building in Stuttgart 2009 Founding of Vector Great Britain, Birmingham Founding of Vector Informatik India, Pune Opening of Representative Office Shanghai, China 2010 aquintos becomes part of the Vector Group Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/1

VECTOR –XXXXXXXXXXXX THE COMPANY

1/1

This catalog provides you an overview of Vector products and Services of the application area ECU Software:

ECU Software Embedded software like real time operating systems (RTOS) ECUs. Basic software for AUTOSAR. Development services for soft- and communication modules for e.g. CAN, LIN, FlexRay and Ether- ware components. net. Software for memory management and for reprogramming of

Please request other catalogs in the application areas Development of Distributed Systems, ECU Testing, ECU Calibration, Process Management, Vehicle Diagnostics, or request further information about the Vector Solutions for various tasks in automotive networking: Internet: www.vector.com/catalog/ • E-mail: [email protected]

Development of Distributed Systems Process Management Tools and Services to design and develop a network of ECUs. Tools and Services to support the process management Tools to simulate, analyze and test the communication of the net- required to develop complex vehicle electronics. This includes work. qualification of human resources, coaching, and supplying special tools that allow the management of complex data, workflows and ECU Testing projects. Tools and services that allow the test of ECUs in all development phases, check the functionality of prototypes or execute Vehicle Diagnostics regression and conformity tests. Tools to describe, implement and test the diagnostic functionalities that are required to run diagnostic services on an ECU. ECU Calibration Diagnostic functionalities are set up during the ECU development, Tools to access the ECU at run-time. This allows acquiring stored in a consistent database and used during the ECU‘s and modifying measurement data and parameters, so the ECU lifecycle. algorithms can be modified and optimized. Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/2

Bus Systems, Embedded Network Protocols, Standards and appropriate Vector Products

1/2 Bus System Description Application Area Appropriate Vector Product Page CAN CAN (Controller Area Network) was developed by the Automotive engineer- All Vector Products Robert Bosch GmbH in the early eighties and was interna- ing, automation tionally standardized (ISO 11898) in 1994. CAN was specif- engineering ically developed for the serial data exchange between electronic control units in automobiles but is also used for the realization of industrial microcontroller networks. LIN LIN (Local Interconnect Network) has been developed Automotive engineer- CANalyzer.LIN/CANoe.LIN ● especially for the cost-efficient communication of ing (body electronics CANalyzer/CANoe Option SCOPE ● intelligent sensors and actuators in automobiles. bus e.g. networking CANape ● LIN bus system characteristics: within a seat) CANbedded LIN Communication 3/8 > master/slave architecture Embedded Gateway 3/12 > time-controlled data transmission Flash Bootloader 5/2 > single-wire data transmission max. CANister ● 20 kBaud CANlog 3/4 ● > synchronization mechanism integrated in the GL1000, GL3000/4000/4200 ● protocol (no expensive quartz needed) MICROSAR LIN 2/18 Multilog ● Network Designer LIN ● VN8900 ● XL-Interface-Family ● MOST MOST (Media Oriented Systems Transport) has been devel- Automotive engineer- CANalyzer.MOST ● oped especially for the transmission of multimedia data in ing (multimedia CANoe.MOST ● automobiles. applications; net- Flash Bootloader 5/2 MOST bus system characteristics: working of infotain- MICROSAR MOST 2/22 > optical data transmission up to 25 Mbit/s ment devices e.g. Multilog ● > ring structure of the bus system tuner, DVD changer, VN2610 – USB-Interface for MOST ● > usage of the standardized XML Function Catalog etc.) > plug&play capability FlexRay FlexRay has been designed as a bus system for all security- Automotive engineer- CANalyzer.FlexRay ● relevant applications as well as for transmission of large ing (e.g. security- CANape ● amount of data in automobiles. relevant applications, CANoe.FlexRay ● FlexRay bus system characteristics: brake-by-wire, high- Flash Bootloader 5/2 > data transmission up to 10 Mbit/s speed backbone for FlexCard Cyclone II SE/E-Ray ● > redundant implementation of all networks other bus systems) FRstress ● > deterministic transmission behavior MICROSAR FR 2/16 As an exchange format for tools for the configuration of Multilog ● bus communication (design, parameterization) with Network Designer FlexRay ● FlexRay, the XML based FIBEX format (Field bus Exchange) VN3300, VN3600 and VN7600 is predominantly used. FlexRay-Interfaces ●

Protocol resp. Description Application Area Appropriate Vector Product Page Exchange Format AUTOSAR The goal of the development partnership, founded by Automotive ECUs, AUTOSAR Evaluation Bundle 2/2 leading automotive OEMs and suppliers, is the definition of basic software AUTOSAR Services 2/54 an open reference architecture for ECU-specific software. AUTOSAR Basic Software Modules 2/6 AUTOSAR Tools 2/44 MICROSAR DIAG 2/28

ARINC 8xx ARINC 810 and 812 specify communication between Avionics and space CANalyzer.CANaero ● CANaerospace modules in the on-board galley (Galley Master, Galley technology CANoe.CANaero ● Inserts). The focus here is on power management. ARINC 825 specifies both the fundamental communication within CAN-based subsystems and between CAN subsystems, which for example are interconnected by AFDX. ARINC 826 specifies Software Data Load over CAN. Key protocol applications of CANaerospace are in engineering simulators, simulation cockpits and especially on drones (UAVs). Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/3

BUS SYSTEMS, EMBEDDED NETWORK PROTOCOLS, STANDARDS AND APPROPRIATE VECTOR PRODUCTS

Protocol resp. Description Application Area Appropriate Vector Product Page Exchange Format J1939/ J1939 is a communication protocol based on CAN for real- Commercial vehicle CANoe.J1939 ● ISO11783 time data exchange between electronic control units engineering, CANalyzer.J1939 ● (ECUs) in the area of commercial vehicles. railway engineering, CANoe.ISO11783 ● It describes the information exchanged between the ECUs agricultural CANbedded J1939 3/6 in such a system. ISO11783 is a further development for engineering CANape ● agricultural engineering. 1/3 NMEA 2000 NMEA 2000® is a communication protocol based on J1939 Marine engineering CANoe.J1939 ● from the National Marine Electronics Association (NMEA) CANalyzer.J1939 ● for the realtime data exchange between electronic control CANbedded J1939 3/6 units in maritime electronics. J1587/ SAE J1708 defines a serial, bidirectional network for use in Commercial vehicles CANoe/CANalyzer.J1587 ● J1708 the commercial vehicle industry. The SAE J1587 Standard engineering regulates communication and standardized data exchange between different ECU based on SAE J1708 networks. CANopen The CANopen profile family specifies standardized commu- Automation CANoe.CANopen ● nication mechanisms and device functionalities. engineering, CANalyzer.CANopen ● CANopen is maintained by “CAN in Automation” (CiA), and CAN embedded CANerator CANopen 3/28 can be implemented free of license. ProCANopen ● CANeds ● CANopen Master Source Code 3/20 CANopen Slave Source Code 3/24 J2534 The SAE J2534 standard defines the re-programming of Vehicle ECUs, PassThru XL Library ● ECUs via a PassThru interface. The purpose of this standard Diagnostics, PassThru is to provide a unified communication capability via a re-programming standardized PC interface basically intended for flashing but also for diagnostics and other purposes. Ethernet/IP Ethernet-based networks and the protocols built upon Car2x, vehicles engi- CANoe.IP ● them are used in IT networks for decades. In the meantime neering, automation CANalyzer.IP ● they continue to grow in importance in the embedded engineering, factory MICROSAR IP 2/20 environment. The main focus is on transmission of periodic automation signals and real-time capability. XCP/CCP XCP is an improved and generalized version of the CAN Cali- Automotive engineer- CANape ● bration Protocol V2.1. (CCP). XCP can be used also in non- ing, development of XCP software component 3/30 CAN networks (e.g. FlexRay, SPI, SCI). The main benefit of electronic control CANoe Option XCP ● XCP is the independence concerning the transport layer. units, measurement GL1000, GL3000/4000/4200 ● and calibration KWP2000/ Keyword Protocol 2000 (KWP2000; ISO 14230) and “Unified Diagnostics of vehicle CANape ● UDS Diagnostic Services” (UDS; ISO 14229) are standardized electronic control CANdelaStudio ● diagnostic protocols for electronic control units. units, measurement CANdesc 3/14 The physical access to the ECU is possible via a serial con- and calibration CANoe ● nection (“K-line” KWP-on-K-Line) or via CAN (KWP-on-CAN, CANoe.DiVa ● UDS-on-CAN). vFlash 5/12 Indigo ● ODX The ODX format (Open Diagnostic Data Exchange) is based Diagnostics of vehicle CANdelaStudio ● on the ASAM-MCD-2D-Basic working draft. Manufacturers electronic control CANdelaFlash 5/10 of vehicles, electronic control units, and testers can write units ODX Studio ● and exchange electronic control unit data in the uniform CANape ● ODX format, which covers all manufacturers. CANoe ● CANoe.DiVa ● vFlash 5/12 Indigo ● RP1210 The RP1210 specification defines an open interface (API) Commercial vehicles RP1210 API ● between Windows-based applications and in-vehicle com- engineering, engine munication networks. This interface offers functionality control for bus systems – such as CAN and J1708 – as well as for higher layer protocols such as J1939 and J1587. ◆ X/XX = Product information included in this catalog ● = Product information included in other application area catalogs or on the internet. Please request further catalogs about the application areas Development of Distributed Systems, ECU Testing, ECU Calibration, Process Management or Vehicle Diagnostics at: Internet: www.vector.com/catalog/ • E-mail: [email protected] Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/4

Application Areas of the Vector Products

1/4 The following matrix gives you an overview which Vector products support you in your specific application area. ++ = main application area; + = additional application area

Development ECU Software Process Vector Product of Distributed ECU Testing Diagnostics ECU Calibration Page Components Management Systems ASAP2 Editor ++ ● ASAP2 Lib ++ ● ASAP2 Tool-Set ++ ● AUTOSAR Basic Software ++ 2/2 (MICROSAR) CANalyzer ++ ● CANape + + ++ ● Option Adv. ● Multimedia +++ Option GPS + ++ ● Option Simulink + ++ ● XCP Server CANbedded ++ 3/2 CANbedded Gateway ++ 3/12 CANbedded J1939 ++ 3/6 CANbedded LIN ++ 3/8 CANdb++ Admin.J1939 ++ ● CANdbLib ++ ● CANdelaStudio ++ ● CANdelaFlash ++ 5/10 CANdesc ++ + 3/14 CANdito + ++ ● CANeds ++ ● CANerator ++ CANopen 3/28 CANextender ++ ● CANgraph + ++ ● CANister ++ ● CANlog 3 and 4 ++ ● CANoe + ++ + ● CANoe.DiVa + ++ ● CANopen Master ++ Source Code 3/20 CANopen Slave ++ Source Code 3/24 CANscope ++ ● CANstressD/DR ++ ● Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/5

APPLICATION AREAS OF THE VECTOR PRODUCTS

Development Steuergeräte- Steuergeräte- ECU Software Prozess-Process Vector Product of Distributed ECU Testing Diagnostics ECU Calibration Software- SeitePage Kalibrierung Components managementManagement Systems Komponenten COMPASS ++ ● DaVinci Component Tester ++ 2/46 Configurator Pro ++ 2/50 Configurator Kit ++ 2/52 Developer ++ 2/44 1/5 eASEE.cdm + ++ ● eASEE.rqm ++ ● eASEE.pm ++ ● eASEE.chm ++ ● eASEE.sdm ++ ● EEPROM ++ Emulations Modul 5/6 Flash Bootloader + ++ 5/2 FlexCard Cyclone II ++ ● FRstress ++ ● GL1000, GL3000/ ++ ● 4000/4200 High Resolution ++ Timer 4/4 Indigo + ++ ● Multilog ++ ● Network Designer ++ ● CAN/LIN/FlexRay ODX Studio ++ ● osCAN ++ 4/2 PassThru XL Library ++ ● ProCANopen ++ ● RP1210 API + ++ ● Test Automation ++ ● Editor Timing Analyzer + ++ 4/6 vFlash ++ 5/12 VN2610 USB Inter- ++ ● face for MOST VN3300, VN3600, VN7600 Interfaces ++ ● for FlexRay VN8900 ++ ● VT System ++ ● VX1000 ++ ● XL-Interface- Family ++ + ● (e.g. CANcardXL, CANcaseXL, …)

X/XX = Product information included in this catalog ● = Product information included in other application area catalogs or on the internet. Please request further catalogs about the application areas Development of Distributed Systems, ECU Testing, ECU Calibration, Process Management or Vehicle Diagnostics at: Internet: www.vector.com/catalog/ • E-mail: [email protected] EMBEDDED SOFTWARE

Use of Standardized Basic Software for ECUs

Supported Hardware Platforms and Vehicle Manufacturer (OEMs)

Overview of advantages Application Areas > Support of the standards AUTOSAR, ISO, HIS, IEC, OSEK, SAE, etc. You can obtain basic software from Vector for the following use > Available in numerous OEM-specific variants areas: > > Proven algorithms used in production development at all OEMs Hardware drivers for CAN, LIN, FlexRay, Ethernet, Flash, > Support of many different hardware platforms via a standardized EEPROM, Timer, ADC, PWM, etc. > API Communication software for CAN, LIN, FlexRay, Ethernet and > Customization of basic software for your use case MOST > > Simple, tool-supported configuration Gateway solutions for CAN, LIN, FlexRay, Ethernet and MOST > Administration of nonvolatile data (EEPROM, Flash) > Diagnostics with error memory module You can get mature standardized basic software from Vector for > Watchdog ECU communication, diagnostics, real-time operating systems, > Flash Bootloader flashing, EEPROM programming and control of IO drivers. This > Operating system solution lets you port your application conveniently and quickly > Calibration protocols XCP and CCP onto different hardware platforms and for different OEMs. > Higher protocols: J1939, CANopen, etc.

You get a software package specially tailored to your project. It is assembled according to the following criteria: > Basic software that is needed (depends on functionality) > Bus system > Hardware > Vehicle manufacturer or platform Before delivery, a test is performed based on your specified hardware and compiler combination. If necessary, Vector can also integrate drivers, e.g. drivers supplied by semi-conductor manufacturers. V2.3 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training In the framework of our training program, we can offer you OEM- specific training courses and workshops for our software components and Flash Bootloader in our classrooms as well as at your business site. For more information on individual training events and dates please visit: www.vector-academy.com

Hardware Embedded software from Vector is available in optimized versions for a large number of specific hardware platforms. For the latest lists, see the e-catalog: > AUTOSAR basic software (MICROSAR) www.vector.com/ds_microsar.availability_en > CANbedded communication components www.vector.com/ds_canbedded.availability_en > osCAN operating system www.vector.com/ds_oscan.availability_en > Flash Bootloader www.vector.com/ds_flashbootloader.availability_en

For CANopen, the list can be found on the product pages for the CANopen Source Code: www.vector.com/sourcecode

OEMs and brands from A-Z Embedded software from Vector supports the specifications of nearly all OEMs. For the latest list, go to: www.vector.com/ds_pes.supported.oems_en

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Supported OEMs

For OEM-specific Basic Software

Vector offers embedded software for a large number of OEMs. Addi- OEM Commu- Diagnostic Flash tionally, a version without vendor-specific characteristics is avail- nication Software Bootloader able. G Depending on the OEM the software is available for conventional GAC X X X (CANbedded) and/or AUTOSAR-conformant ECUs. The diagnostic software and the Flash Bootloader contain OEM-specific diagnostic Geely X X services, fault memory or flash processes. Depending on the OEM GM X X X the scope of the available diagnostic solution differs, e.g. UDS or Great Wall X X KWP2000 is used as diagnostic protocol. Motors Please contact Vector. We will help you to find the optimal solution H for you requirements. Honda X X X OEM Commu- Diagnostic Flash HMC X X X nication Software Bootloader I B Isuzu X X BAIC X X X Iveco X X Brilliance X J BMW X X X JAC Motors X X BYD X Jaguar / X X X C Landrover CHANA X X X K Chery X X KMC X X X Chrysler X X X M Claas X X X MAN X X X D Mazda X X X DAF X X X Mitsubishi X X X Daimler X X X N Dongfeng X X X NAC X X X

F Nissan X X X FAW X X P FCC X X X Porsche X X X FIAT X X X PSA X X X Fisker X X X Q Ford X X X Qoros X X X Foton X R Renault X X X

V2.7 2012-03

More Information: www.vector.com/contact EMBEDDED SOFTWARE

OEM Commu- Diagnostic Flash nication Software Bootloader S SAIC X X X SsangYong X X X Subaru X Suzuki X X

T Toyota X X X

V Volvo AB X X X VCC X X X VW/Audi X X X

OEM X X X independent

Vector is pleased to support further OEMs on request.

Vector Informatik GmbH > Ingersheimer Str. 24 > 70499 Stuttgart > Tel. +49 711 80670-0 > Fax +49 711 80670-111 > www.vector.com Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/8

Technical Consulting/Engineering Services

Individual support in the development of ECU software and vehicle networks

1/8 ECU Software Overview of Advantages In developing your ECU software with our embedded standard > Tailored support software, such as CANbedded or MICROSAR, we can provide the > Quick implementation of your application following support: > Sustained build-up of know-how > Product-related Software Engineering Services For over 15 years, Vector has been creating software components In conjunction with Vector embedded software products, which as well as professional tools, and has been successfully support- you use in your development, we can offer you professional sup- ing customers worldwide in developing ECU software and net- port with training, support, review, installation and coaching, working ECUs. Our experts bring success to your project with which we would also be glad to provide at your business site. individually tailored technical consulting and engineering services. > Technical consulting Starting with your aspired goals, our engineers work together In taking on your technical challenges, our expert team provides with you to plan and implement an individual package of services. you with technical consulting or individual concept development. In every phase of development, our consultation and support is Our technical consulting, e.g. in the framework of joint work- entirely based on your needs. Projects are handled in close coordi- shops, helps you in tasks such as these: nation with your project team and based on a process that is opti- > Introducing a new operating system mally aligned to your needs. This lets you attain maximum relief of > Optimizing an existing software architecture work load and ideal transparency. > Porting your application software to a multi-processor ECU > Layout of safety-related “mixed SIL” systems Application Areas > Migration of ECUs to FlexRay or AUTOSAR > ECU Software Development > Vehicle Networks Design > Engineering Services Our engineers would be glad to take on the specification and development of your ECU software, even with safety-related content according to ISO DIS 26262. Model-based software development can also be provided.

Services for the development of ECU software Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/9

ECU SOFTWARE

Contact We would be glad to support you on your projects. Please feel free to contact us at: www.vector.com/contact

Our services line-up ranges from a standard “Extended Integra- > Engineering Services 1/9 tion Package (EIP)” via the development of system functions and Beyond technical consulting, we would also be glad to handle all software integration to the take-over of overall responsibility for of the project related development tasks such as: all application software. > Specification of CAN, LIN and FlexRay based vehicle networks > Specification of individual communication protocols For a detailed description of our service line-up in the area of ECU > Creating and maintaining communication relationships software, please refer to the datasheets on AUTOSAR Services and between the ECUs Software Development Services. > Specifications of gateway components ◆

Vehicle Networks In the development of vehicle networks, you can obtain the following support from Vector:

> Technical Consulting Technical consulting focuses on sustainable transfer of the necessary technological information. Close cooperation with our experts guarantees intensive knowledge transfer to your professional team. During individual workshops, we conceptualize solutions together with you for: > Distribution of vehicle functions > Creating and extending network architectures > Optimizing your system layout > Definition of routing concepts for gateways

Services for Vehicle Networks Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/10

Software Engineering Services

Professional Support for your ECU software

1/10 Extended Integration Package (EIP) Overview of Advantages The Extended Integration Package is a predefined project scope > Take advantage of our expertise in embedded standard for integration of OEM-specific standard software on your ECU. It software for your project offers an efficient entry into your project and enables early and > Quick implementation of the communication, diagnostics successful execution of initial network testing at the OEM. It and flash download for initial sample submission to the OEM includes: > Tailored support from entry-level to the take-over of entire > Installation of the basic software on your ECU hardware with software projects the help of a sample application > Specification-conformant configuration of the standard For over 15 years, Vector has been developing software compo- software and the OEM-specific system modules nents and professional tools and has been successfully supporting > Test execution with the OEM-specific tool chain customers worldwide in the development of ECU software. Vector > Test reports on fulfillment of OEM specification requirements is the market leader in OEM-specific standard software, e.g. for communication, diagnostics, operating systems, flash download The following functions are started up with the EIP: and low level drivers. Many OEMs and their suppliers are already > Communication on the vehicle bus, including control of the benefiting from our know-how. Our experts bring success to your start and stop states as well as sleep and wake-up project too with individually tailored software engineering services. > Basic diagnostic functionality including implementation of error memory entries concerning communication errors Application Areas (e.g. timeout, bus-off) > Extended Integration Package (EIP): Extended integration of the > Flash download using an EEPROM emulation in RAM memory standard software on your ECU as quick entry-level assistance in an initial sample submition for network testing at the OEM > System Functions and Software Integration: Full integration of the standard software with your application and development of additional system functions > Complete Application Software: Full development of your ECU applications Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 1/11

ECU SOFTWARE

Contact We would be glad to support you in your projects. Please find your personal contact at: www.vector.com/contact

System Functions and Software Integration > Development of the entire diagnostic software component 1/11 Perhaps you want to focus more on your application development (SWC) and are seeking a partner to assume responsibility for implement- > Development of sensor and actuator software components ing a portion of your software project. > Integration of the flash bootloader, even for multi-processor We can offer you project support tailored to your individual systems needs. The project is executed in close cooperation with your project team and is based on a process that is optimally aligned to In addition, project services include: your needs: from prototype to serial production. If you need safe- > Creating documentation such as requirements specification, ty-related software, the development can be performed according design documentation, MISRA reports, test specifications to ISO DIS 26262. Model-based software development can also be > Project control by project and release planning, project report, performed. status reports, quality gates and production release by Vector Using our support, you get maximum work load relief and ideal transparency on the current status of the project. Complete Application Software Perhaps you do not wish to develop your application software We integrate the standard software on your ECU hardware under yourself and are seeking a partner that can handle its implemen- consideration of your design and OEM requirements. In addition, tation for you? We would be glad to assume responsibility for exe- we link it completely to your software application. We would be cuting an entire ECU software project. ◆ glad to develop additional system functions for you, ranging from requirements analysis to verification.

Typical project contents: > Specification-conformant configuration and integration of the standard software on your ECU hardware > Development of specific auxiliary functions, e.g. for controlling the communication buses and error behavior, development of special routings or signal conversions for the communication channel used

Vector can develop individual system functions or the entire application software EMBEDDED SOFTWARE

Solutions for AUTOSAR

The core idea of AUTOSAR is to master the growing complexity of DaVinci – The AUTOSAR Tools from Vector software in modern vehicles by standardization. The development > DaVinci Developer is the optimal tool for graphic-based defini- partnership founded by leading automotive OEMs and suppliers set tion of AUTOSAR software components. the goal of defining an open reference architecture for ECU soft- > DaVinci Component Tester lets you conveniently test AUTOSAR ware. Many advantages are realized by standardization and using software components on a PC. clearly specified interfaces between the basic software modules to > DaVinci Configurator Pro is used to configure the MICROSAR the functional software: e.g. re-usability of the same software for basic software and the RTE from Vector, the basic software from different microcontrollers and functions with a simultaneous third-party suppliers or for modules you developed in-house increase in quality. (e.g. complex drivers).

Vector, your Trusted Partner for AUTOSAR Projects MICROSAR – The AUTOSAR Basic Software Modules from Vector As one of the first premium members of the AUTOSAR Consortium, To make it possible for you to efficiently develop production- Vector has been actively involved in the development of new tech- mature ECUs according to AUTOSAR, you get MICROSAR from Vector nology for a long time. This active participation was recognized by – software modules that are AUTOSAR-conformant for AUTOSAR 3 the AUTOSAR Consortium in awarding Vector the first AUTOSAR (ASR 3) and from Q3/2012 also for AUTOSAR 4.0 (ASR 4.0). They Premium Member Award in 2007. Vector‘s experience with cover the entire AUTOSAR standard and also contain numerous AUTOSAR is also reflected in AUTOSAR tools and the basic software, practical extensions. which is already being used in numerous production projects. For ECUs with safety-relevant functions, we recommend to use Overview of the Vector AUTOSAR Solution MICROSAR Safe – the MICROSAR solution for ECUs up to ASIL D per Vector supports you in all development phases of projects with ISO 26262. MICROSAR Safe is available for ASR 4.0 and ASR 3. tailor-made AUTOSAR solutions for design, development and implementation:

V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

> When choosing the AUTOSAR solution from Vector: CANdela Studio let’s you specify the diagnostic functionality. > You benefit from a seamless tool chain: From the design of your system to the development of your functional software and inte- Vector can offer you a complete solution for your projects together gration of the software in your ECU. with numerous other tools for ECU testing as well as measurement > You get, with MICROSAR, a comprehensive package of basic and calibration. software for AUTOSAR 3 or AUTOSAR 4.0 from a single source. You can also use just individual modules or the MICROSAR mod- The Easy Way to Get Started with AUTOSAR ules in conjunction with third-party components. Besides training courses on fundamentals and on specific prod- > Vector offers you, in conjunction with its partner TTTech Auto- ucts, Vector also offers on-site support in project implementation motive, a reliable solution for safety-relevant ECUs per ISO and in introducing the AUTOSAR software. 26262 - both for AUTOSAR 3 and for AUTOSAR 4.0. The AUTOSAR Evaluation Bundle from Vector gives you a solution > You do not need to migrate to AUTOSAR all at once. Vector can show for evaluating the Vector AUTOSAR solution. It offers a structured you solutions for stepwise migration without loss of quality. approach for training in the AUTOSAR methodology and gives you > You are choosing a future-oriented solution with a reliable partner. an opportunity to evaluate the functionality and performance of the AUTOSAR software.

Further Tools Support for Your Projects Take advantage of the comprehensive Vector tool chain to develop Vector accompanies you from the early evaluation phase to pro- your AUTOSAR ECUs and systems. duction projects. Together with you, we can develop a comprehen- > PREEvision lets you specify and manage in-vehicle electronic sive solution for your ECU. In the process, it does not matter systems. This ranges from defining requirements to designing whether you are using Vector products, your own in-house devel- distributed functions and defining components such as sensors, opments or third-party components. We support your projects with actuators and ECUs. Data communication in the networks can experience and integration know-how. also be defined with PREEvision. > Network Designer is used to design a vehicle’s networking architecture and data communication for the networks.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

AUTOSAR Evaluation Bundle

The complete package for the evaluation of AUTOSAR basic software and tools

Overview of advantages Application Areas > Tools and basic software in production quality according to The AUTOSAR Evaluation Bundle supports both the automotive − AUTOSAR 3 or 4.0 (from Q3/2012), lets users evaluate the Vector OEM in evaluating AUTOSAR processes and methods – and sup- solution for AUTOSAR pliers in creating a first AUTOSAR-conformant ECU software. Since > Enables realistic evaluation of execution time and memory require- the tools and basic software are at a level of production maturity, ments for your ECU project you can reliably use the Vector solution to evaluate AUTOSAR with > Conveniently test your software components on a PC on the regard to: > Virtual Function Bus level Efficiency of the basic software > > Available for many different micro-controllers and the PC as runtime Integration of the tools in your development environment > platform Potential uses of AUTOSAR concepts in your application area > Quick way to train in AUTOSAR with a detailed sample project > Support of both AUTOSAR-conformant files and conventional The AUTOSAR Evaluation Bundle also provides an optimal founda- description files tion for initial developments of AUTOSAR-conformant software components (SWCs) for service providers who focus on the application level. The AUTOSAR Evaluation Bundle is a comprehensive package of OEM independent AUTOSAR basic software and design and config- If you do not have any specific hardware available and only wish to uration tools from Vector. This package lets you develop your first evaluate the AUTOSAR method and tools, you can also obtain the ECU software with an AUTOSAR-conformant software architecture. AUTOSAR Evaluation Bundle with the MICROSAR CANoe Emulation. You get an in-depth look into the AUTOSAR world – from the In this case, you use the PC as a runtime platform with the CANoe design and configuration process to implementation of the actual testing and development tool from Vector (not included with basic software. You can obtain OEM-specific BSW modules, e.g. for bundle) and can omit startup with real hardware. However, you diagnostics, in our MICROSAR Prototype SIP (see page 4 of this work with the same methods, tools and basic software as in the datasheet). development of a real ECU.

AUTOSAR Tools AUTOSAR Basic Software

Additional Tools V2.6 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training In the framework of our training program, we can offer various training events and workshops for MICROSAR in our classrooms as well as at your business site. For more information on individual training events and dates on the Internet please visit: www.vector-academy.com

Functions formats, and use the data in automatic configuration of the The AUTOSAR Evaluation Bundle contains all tools and software MICROSAR diagnostic basic software. from Vector for creating a complete set of AUTOSAR ECU software, which consists of software components (SWCs), Runtime Environ- The AUTOSAR Evaluation Pack is available for AUTOSAR 3 (ASR 3) ment (RTE) and basic software (BSW). The DaVinci tools are tai- and 4.0 (ASR 4.0). The included MICROSAR basic software modules lored to AUTOSAR and simplify your work in designing complex efficiently and flexibly implement all functions of the related AUTOSAR applications. As input for configuring the MICROSAR AUTOSAR Releases. They also contain many extensions that go software, you would use an ”ECU Extract of System Description“ beyond the standard. (AUTOSAR XML) or as an alternative a conventional network The following list gives you an overview of the individual description file (DBC, FIBEX, LDF). MICROSAR bundles contained in the AUTOSAR Evaluation bundle. > The DaVinci Developer tool gives you an easy way to generate For a complete description of the individual bundles, please refer AUTOSAR-conformant ECU applications. Using the graphic edi- to the separate datasheets in this catalog. tor, you can describe your AUTOSAR software components quickly and clearly and define their interfaces. The SWCs serve as MICROSAR RTE a basis for the RTE configuration process, which you also per- > Contains the AUTOSAR RTE (Runtime Environment) form with DaVinci Developer. > The DaVinci Component Tester is used to conveniently test – on MICROSAR OS a PC - implementation of the SWCs. Based on SWC description Contains the AUTOSAR basic software module Operating System files, the DaVinci Component Tester emulates the Virtual Func- (OS) tion Bus (VFB) and lets you conduct unit testing of SWCs. > Implementation of “Scalability Class” SC1 (SC2-SC4 available as > The DaVinci Configurator Pro tool is used to configure the basic option if supported by processor) software modules and the RTE. You can use the convenient and > Fully compatible with OSEK OS intuitive user interface to adapt parameter values for your ECU > Supports Schedule Tables project. The GENy tool offers special support in configuring the communication basic software. MICROSAR SYS > The CANdelaStudio tool is used to define diagnostic data for Contains system-related AUTOSAR basic software modules. The your networks and ECUs. You can export this data via standard following BSW modules are available as options:

Designing software components with DaVinci Developer Configuration of the Basic Software and the RTE with DaVinci Configurator Pro

More Information: www.vector.com/contact EMBEDDED SOFTWARE

> MICROSAR CSM (Crypto Service Manager) for ASR 4.0 FRISOTP can be replaced by FRTP, and XCP can also be supplied for > MICROSAR STBM (Synchronized Time-Base Manager) for ASR 4.0 measuring and calibrating via FlexRay. > Driver for controlling external memory chips (see MICROSAR MICROSAR LIN (available as option) EXT) Contains all AUTOSAR basic software modules for LIN communication. MICROSAR DIAG Contains all basic software modules for AUTOSAR-compatible MICROSAR IP (optional) implementation of the UDS protocol Contains all AUTOSAR basic software modules for communication via the internet protocol based on Ethernet. Upon request, XCP MICROSAR MEM can also be supplied for measuring and calibrating via Ethernet. Contains the AUTOSAR basic software modules for memory management – either with MICROSAR EA for internal EEPROMs or MICROSAR COM MICROSAR FEE for internal flash memory. Optionally, drivers for Contains all AUTOSAR basic software modules for bus system inde- controlling external memory chips are available in MICROSAR EXT. pendent communiation.

MICROSAR CAN MICROSAR IO Contains the AUTOSAR basic software modules for CAN commu- Contains the AUTOSAR basic software modules for input/output nication. The following BSW modules are available in MICROSAR hardware abstraction. CAN as options: > XCP for measuring and calibrating via CAN MICROSAR CAL > Transport protocols BAM (Broadcast Announce Message) and Contains AUTOSAR drivers for controlling the microcontroller CMDT (Connection Mode Data Transfer) for J1939 networks (also periphery, including bus-specific drivers for CAN/LIN/IP and for ASR3) FlexRay. Also available as options are the following BSW modules: > IICDRV (driver for interfacing to external peripheral chips via the MICROSAR FR (available as option) Inter-Integrated Circuit Bus I2C) Contains the AUTOSAR basic software modules for FlexRay com- > FLASHTST, RAMTST, CORETST munication with FRISOTP as the transport protocol. Upon request,

Special functions DaVinci Developer has an import/export interface for AUTOSAR XML files. This interface lets you exchange design and configuration data. For example, you might use it to integrate AUTOSAR software components in an ECU you have developed in a model-based approach using tools like MATLAB® Simulink®.

All MICROSAR products conform to: > “Implementation Conformance Class” ICC3, and > “Configuration Conformance Class” CCC 2.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www.microsar.com/availability/ We can also tell you about OEM-specific versions and custom support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact

MICROSAR EXT (optional) Available Hardware Platforms Contains the AUTOSAR basic software modules for controlling The AUTOSAR Evaluation Bundle is available for the most com- external chips. monly used 16-bit and 32-bit hardware platforms. Due to the hardware dependency of the MICROSAR CAL modules and the MICROSAR Safe (optional) MICROSAR OS, binding statements cannot be made without specific Complete solution for safety relevant functional software accord- processor device numbers. The Vector Sales Team would be glad to ing to ISO 26262. provide this information.

Additional Included Features MICROSAR CANoe Emulation > Sample application in source code, and a detailed guide on its As an alternative, Vector also offers the AUTOSAR Evaluation Bun- use dle for CANoe as a PC runtime platform. In this case, emulations of > AUTOSAR Training at Vector (4 days) the MICROSAR CAL modules and the MICROSAR OS are included. The flash memory of the AUTOSAR ECU is also emulated. The Further Options EEPDRV is not needed in this case, and so it is not provided. The AUTOSAR Evaluation Bundles CAN, LIN, IP and FlexRay may be used with one another in any combination. MICROSAR Prototypen SIP If you need software for the prototype phase of a specific OEM Upon request, Vector can support you with extensive MICROSAR project that goes beyond pure evaluation purposes, we recommend Coaching at initial startup and during integration of the MICROSAR that you obtain our MICROSAR Prototype SIP (Software Integration basic software in your application. Vector can also provide coach- Package). Please contact us for further information. ing at your business site.

Special functions of the MICROSAR CANoe emulation In conjunction with CANoe, the emulation comprises the following functions: > Access to the CAN, LIN or FlexRay bus systems > Simulation of I/O ports via CANoe panels > Connection of real sensors and actuators > Easy debugging of the application by stopping the global time of the entire emulation when a breakpoint is reached > Interactive and automated tests of the AUTOSAR ECU software and execution of remaining bus simulations > Your own custom extensions are possible, e.g. to emulate complex drivers

System requirements for the MICROSAR CANoe emulation > CANoe 7.0 SP5 or higher > Microsoft Visual Studio 7.1, 8.0 or 9.0

Functional principle: CANoe as target platform

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR

The Vector Solution for AUTOSAR ECU Software

Overview of Advantages ently, because the AUTOSAR architecture follows a consistent > The entire AUTOSAR basic software for Release 3 and 4.0 (from strategy of hardware abstraction. Q3/2012) from a single source > Many innovative extensions perfectly tuned to one another Modules from the MICROSAR OS and MICROSAR CAL packages are > Already in production use at leading OEMs and TIER1 suppliers hardware-dependent. Vector offers these modules for a large > Simplifies development of platform-independent functional - number of different hardware platforms and compilers, e.g. to software enable quick change-out of the controller device. The operating > Available for many hardware platforms and automotive OEMs system MICROSAR OS is available for single core and multi core- > Mature, long-term and reliable solution from an AUTOSAR processors. Based on its ongoing contacts with OEMs, Vector is Premium Member able to offer a number of OEM-specific BSW modules such as the diagnostic modules.

MICROSAR is the AUTOSAR solution for your ECU software. You can configure all necessary MICROSAR BSW modules based on MICROSAR consists of the MICROSAR RTE and MICROSAR basic your project’s requirements, and after generation you can inte- software modules (BSW), which cover all aspects of the AUTOSAR grate them with the functional software. This produces a complete standard and many extensions. Each AUTOSAR BSW module is set of ECU software. If the functional software consists of assigned to a MICROSAR package. For detailed descriptions of AUTOSAR-conformant SWCs, you will need a run-time environment individual packages and the MICROSAR RTE, please refer to the (RTE). The MICROSAR RTE handles communication between the separate datasheets. Vector combines the BSW modules needed in SWCs and their access to data and services from the BSW modules. individual “software integration packages”. Along with managing the entire flow of information, the MICROSAR RTE also assures consistency in the exchange of information. Application Areas The BSW modules of the MICROSAR packages assure basic func- Properties tionality of the ECU. They contain the implementations of AUTOSAR Development of the MICROSAR basic software modules is founded standard services you will need for your functional software. You on the Vector development process for standard modules, which is are able to develop your functional software platform independ-

The MICROSAR packages contain all modules of the AUTOSAR 4.0 standard V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Contact and Availability MICROSAR BSW modules are available for many currently used microcontrollers as well as in OEM-specific versions. For more information, go to: www.microsar.com/availability/ or contact us. Find your contact person at: www.vector.com/contact

based on SPICE. All MICROSAR packages offer the following fea- extended to cover software modules from third-party producers tures: (e.g. MCAL drivers). > Efficient memory utilization and short execution times > Available for production use Support of AUTOSAR 3 and 4.0 > Available for AUTOSAR 3 and 4.0 (from Q3/2012) Regardless of whether you use AUTOSAR 3 (ASR 3) or 4.0 (ASR 4.0 - > Assistants and timely checks support you in achieving consistent from Q3 2012), from Vector you get the entire basic software from configuration of your basic software a single source. In migration of your projects, you benefit from the > Scalable, adaptable to your specific application uniform development environment for both ASR3 and ASR4.0: > Optimally integrated into your development process > The configuration tools DaVinci Developer and DaVinci > AUTOSAR Monitoring for testing and analysis of ECUs Configurator Pro are designed for both releases. This lets you > User-selectable configuration point (pre-compile, link-time or avoid a change in tools. post-build) > MCAL drivers from different AUTOSAR releases can be combined > Communication stack is versatile in its use with MICROSAR. > Supports multiple ECUs In addition, we support you in adapting your functional software > Optional delivery as source code to the modified interfaces of the ASR4.0 standard. > Together with MICROSAR Safe: well-suited for safety-relevant Another advantage of MICROSAR lies in its many extensions in the functions (ISO 26262) BSW modules for ASR 3, which actually were not specified until ASR 4.0. Some examples are the multi-core operating system, as well as Production Use support for J1939, XCP and Ethernet/IP, which are already availa- The MICROSAR BSW modules are already being used in production ble for ASR 3. The MICROSAR MOST bundle is a supplement to the projects. MICROSAR lets you benefit from Vector’s many years of standard created by Vector and is compatible with ASR 3 and ASR experience in implementing embedded standard software. Before 4.0. delivery, all MICROSAR Software modules undergo systematic integration tests for the specific conditions of your application Consistent and Simple Configuration (hardware platform, compiler, processor device, OEM, With AUTOSAR, the work of manually developing or adapting the with/without RTE, etc.). Upon request, these tests may be basic functionality of ECU software is replaced by configuration of

DaVinci tools are used to consistently configure the MICROSAR RTE and MICROSAR BSW modules

More Information: www.vector.com/contact EMBEDDED SOFTWARE

the BSW modules. The intuitive, user-friendly and well coordinated functions to optimize the MICROSAR code for your application. This AUTOSAR tools from Vector (DaVinci) support the user in this scalability makes the MICROSAR modules the optimal solution for process. Multi User Support of the DaVinci tools enables simulta- both small and challenging applications. MICROSAR is already neous work on a project by multiple users. The DaVinci tools being implemented in a wide range of ECUs, such as steering angle require an “ECU Extract of System Description” file as input. It is sensors, door ECUs, engine ECUs, central gateways, etc. MICROSAR also possible to produce a configuration based on commonly used may also be used with other operating systems such as Linux or network description files (DBC, FIBEX, LDF, etc.). QNX. Early in the configuration process, all DaVinci tools check the validity of individual parameters, complex parameter groups and AUTOSAR Monitoring their interrelationships. In case of invalid configurations, the tools AUTOSAR Monitoring simplifies testing and analysis of ECUs with make recommendations for corrections, if possible. This extension such tools as CANape or CANoe. The MICROSAR A2L Generator of the AUTOSAR method simplifies integration of the basic soft- generates an A2L file for this purpose. This contains the descrip- ware in your ECU and reduces integration time. tion of important RTE-internal variables such as Send/Receive The DaVinci tools optimally assist you in configuring the RTE and ports, internal states of the MICROSAR BSW modules and of COM the BSW modules. In a bottom-up process, for example, the SWC signals. In testing, you read them out at runtime with XCP. service ports (including runnables) are automatically generated to match the BSW configuration. This automation relieves you of User-Selectable Configuration Point tasks that recur frequently and are prone to errors when performed The configuration point of all MICROSAR basic software modules is manually. This saves you time and costs. user-selectable. You can select the configuration point for each For more details on DaVinci tools from Vector, please refer to the BSW module; choices are: pre-compile, link-time or post-build. relevant datasheets. ECU Variants Scalability To save on logistical costs in AUTOSAR ECUs, the MICROSAR mod- In addition to fulfilling AUTOSAR requirements, the MICROSAR BSW ules can be delivered with the optional Identity Manager. This modules also provide a number of functional extensions. The option lets you develop physical multiple-ECUs within a car line or extended configuration options let you deactivate unnecessary multi-configuration of ECUs that are used in different car lines. For

You use DaVinci Configurator Pro to configure the BSW You use DaVinci developer to define the functional modules and the RTE. software (SWCs)

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Contact and Availability MICROSAR BSW modules are available for a large number of commonly used microcontrollers and in OEM-specific variants. You can obtain more information at www.microsar.com/availability/ or upon request. Please find your contact person at: www.vector.com/contact

more information, see the datasheet on the AUTOSAR Identity Additional Services Manager. > Consulting on system design > Extension of standard BSW modules per customer wishes Functional Safety according to ISO 26262: MICROSAR Safe > Development of customer-specific software components (SWC) For use of the MICROSAR BSW in safety-related functions, Vector – > Support in adapting existing functional software together with TTTech Automotive – offers a complete solution for > Complete software integration in your ECU – including third- your AUTOSAR ECU. For more information, please refer to the party software MICROSAR Safe datasheet. > Migration of existing software to AUTOSAR > Hotline, special workshops and training courses on the topic of Optional Delivery of Source Code embedded software and AUTOSAR The MICROSAR modules are also available as source code, upon request. The source code lets you make pre-compile optimizations and simplifies testing.

License and Maintenance Vector offers you flexible licensing – individually tailored to your requirements. In the framework of a maintenance contract, you get software updates that keep you current to the latest level of development.

List of available MICROSAR Packages > MICROSAR AMD – Monitoring and Debugging > MICROSAR MEM – Memory Management > MICROSAR CAL – AUTOSAR conform controlling of the > MICROSAR MOST – Communication via MOST microcontroller peripherals > MICROSAR OS – AUTOSAR operating system > MICROSAR CAN – Communication via CAN > MICROSAR RTE – Runtime environment for SWCs > MICROSAR COM – Network independent communication > MICROSAR Safe – Solution for safety-relevant application > MICROSAR EXT – Controlling external hardware software according to ISO 26262 > MICROSAR FR – Communication via FlexRay > MICROSAR SYS – Basic ECU functions > MICROSAR DIAG – Diagnostics > XCP – Measurement and calibration of an > MICROSAR IO – Direct connection of the microcontroller AUTOSAR-ECU using XCP incl. transport peripherals to the application layer for Ethernet, FlexRay und CAN > MICROSAR IP – Communication via Ethernet > MICROSAR LIBS – AUTOSAR Libraries > MICROSAR LIN – Communication via LIN

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR OS

The Real-Time Operating System for the AUTOSAR Standard

Overview of Advantages monitoring and memory protection as well as functionalities that > Small, quick and resource-economizing operating system support distributed applications in networks. > Short boot times > MICROSAR OS is available for AUTOSAR 3 and 4.0 (from Q3/2012) MICROSAR OS is fully conformant to the AUTOSAR OS specification > Available as multi core operating system, too and supports all scalability classes: > Optional: Safe context switching per ISO26262 / ASIL-D SC1: Real-time operating system implemented per the OSEK/VDX- > MICROSAR OS provides an ideal runtime environment for embedded OS standard and extended to include schedule tables software and forms the basis for migration to AUTOSAR-conformant SC2: Real-time operating system with time synchronization and applications monitoring of the time behavior of individual tasks and interrupt > Supplied as source code service routines > Numerous auxiliary functions simplify software development SC3: Real-time operating system with memory protection mecha- > Quality process per SPICE Level 3 nisms on microcontrollers with suitable hardware support > Graphic configuration tool for easy configuration SC4: Combines scalability classes SC2 and SC3 > TimingAnalyzer for analyzing the schedulability > Available for many 8, 16, 32 and 64 bit microcontrollers Optional Extensions > Synchronization with the global system time Schedule tables can be synchronized with the global system time, MICROSAR OS is a pre-emptive real-time multitasking operating e.g. the time transmitted over the FlexRay bus. This makes syn- system with optimized properties for use on microcontrollers. chronized and simultaneous execution of tasks possible in a dis- Vector’s many years of experience in developing operating systems tributed system. and drivers for microcontrollers are bundled into this small, robust operating system core. > Memory protection (SC3, SC4) Memory protection assures that application components do not Properties mutually destroy data. This makes the integration of applications MICROSAR-OS is based on the AUTOSAR OS specification, an exten- easier and more reliable. sion of the practice-proven OSEK/ VDX-OS operating system standard. This standard was extended to include functions for time

MICROSAR OS Modul according to AUTOSAR 4.0 V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program we can offer various For information on the availability of hardware-specific MICROSAR training courses and workshops on MICROSAR at our classrooms or at BSW modules go to: www.microsar.com/availability/ your business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates please versions and individual support for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

> Timing Protection (SC2, SC4) Operating system for applications according to ISO 26262 Timing protection ensures that assumptions made in the early For safety-relevant applications according to ISO 26262, you can design phase related to execution times are preserved during obtain from Vector the operating system variant MICROSAR OS runtime as well. As a result, a defective application section cannot SafeContext that was developed according to ASIL D. It is based on impair the execution times of other running processes. the AUTOSAR scalability classes SC3 and SC4 and is responsible for memory protection and safe context switching. To preserve “free- > Execution time measurements (SC2, SC4) dom from interference” with regard to memory protection, you You can use functions of scalability classes 2 and 4 to measure the need a suitable processor, e.g. with a Memory Protection Unit execution times and interrupt disable times of applications. These (MPU). measured data can later be used as practice-based values in designing and integrating future applications. You can use MICROSAR OS SafeContext to use safety-relevant application components together with standard components on > High Resolution Timer the same CPU. The high resolution timer mechanism offers time resolutions of less than 1ms without increasing interrupt load. Depending on the Components supplied with MICROSAR OS SafeContext: controller, this may enable resolutions into the microseconds > Operating system range. > Configuration and generation tool > Read-back tool – developed per ASIL and certified > High Resolution Synchronization for Schedule Tables > Safety Manual In some applications, it is necessary to synchronize and trigger For more details on the Vector solution for safety, please refer to schedule tables with very high precision using internal or external the separate datasheet for MICROSAR Safe. signal sources. The “High Resolution Synchronization” option gives you resolutions in the microsecond range without increasing interrupt load.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Multi-Core operating system > Shared Resource Access MICROSAR OS Multi-Core is an advanced development of the If different cores should access commonly used resources, the proven real-time operating system MICROSAR OS from Vector. You operating system provides a coordination mechanism known as can use it wherever a multi-core system is to be developed Spinlocks. according to the AUTOSAR specification. MICROSAR OS Multi-Core is based on AUTOSAR specification 4.0, but it can also be used in > Inter-Core Communication AUTOSAR 3 projects. For consistent data exchange between two cores, the operating system provides an efficient interface in the form of the Inter-OS Functions of the Multi-Core operating system Application Communicator (IOC). The multi-core operating system enables parallel and independent operation of multiple processor cores, each with a separate Development Tools instance of the AUTOSAR operating system. Thereby, its configura- > Graphic configuration tool tion and system services match those of the single-core operating The Configuration of the operating system can be done using the system. The extensions SC2 to SC4 and High Resolution Timing are supplied configuration tool. For convenient configuration, we re- available. In addition, MICROSAR OS Multi-Core offers mechanisms commend an upgrade from the supplied DaVinci Configurator Base for coordinating and synchronizing tasks that run on different to DaVinci Configurator Pro that also includes a consistency check. cores. > TimingAnalyzer Design Assistance > Synchronized Start-Up The TimingAnalyzer computes the task execution schedule, checks The operating system assures that all cores are started up and for conformance to execution time restrictions and represents the initialized before the associated application is started. schedule tables in a well-organized graphic display. Analysis is performed for every task and every interrupt with the following > Inter-Core Coordination information: Priority, period, execution time and end time. The Processes on different cores are synchronized by task activations, graphic user interface visualizes system behavior clearly and setting of events, starting and stopping of alarms or Schedule- concisely. Tables.

The complete AUTOSAR solution from Vector The Vector AUTOSAR solution consists of the DaVinci tools, the MICROSAR BSW and the MICROSAR RTE. You will find information on general properties of the BSW modules from the MICROSAR packages as well as details on functional features of the individual DaVinci Tools in the particular datasheets.

MICROSAR-OS conforms to AUTOSAR Specification 3.x

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Scope of Delivery > Operating system core as source code > Graphic configuration and generation tool for Windows XP/ Windows 7 > DaVinci Configurator Base as basic editor > Command line based generator > BSW modules description > Documentation > TimingAnalyzer

Additional Services Vector offers you worldwide support related to AUTOSAR: > Training events > Design consulting > Customer-specific implementations > Hotline > Software maintenance The extent and form of all services are tailored to your wishes.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR COM

AUTOSAR Basic Software Modules for Communication

Overview of Advantages For a gateway ECU, you do not need any additional software. The > Code and execution time optimized by application-specific COM and PDUR BSW modules from MICROSAR COM enable routing configuration of signals and TP or application messages. > Very efficient signal access via function macros > Available for AUTOSAR 3 and 4.0 (from Q3/2012) Functions > Contains many useful extensions The BSW modules from MICROSAR COM contain functions defined > Extended support for NM coordinators in AUTOSAR Release 3 (ASR 3) and 4.0 (ASR 4.0): > > NM module: OSEK NM compatibility is configurable Services of the COM module organize transmission of messages > Supports simultaneous operation of AUTOSAR NM and OSEK NM according to their send type (cyclic, event-triggered, etc.). A key in NM migration projects task is to implement bus-independent signals of the functional software in PDUs. > The PDU Router (PDUR) provides to the modules COM, DCM and The basic software modules (BSW) of MICROSAR COM include to the complex drivers an interface to the communication mod- AUTOSAR services for ECU communication. These services can ules (interface, transport protocol and network management) of support any number of communication channels. They are bus- the bus systems. This interface serves to transmit and receive independent and are needed in every communication stack. Per data via PDUs. The PDUR also implements a gateway between the AUTOSAR architecture, they handle control and full integration in communication modules of the various bus systems. the ECU software of bus-specific communication modules from > The Generic Network Management Interface (NM) bundles inter- MICROSAR CAN, MICROSAR FR, MICROSAR LIN, MICROSAR IP and bus network management activities of all of the ECU’s communi- MICROSAR MOST. cation channels. As NM coordinator, it synchronizes wake-up and sleep of the communication channels. Application Areas > The optional I-PDU Multiplexer (IPDUM) supports multiple usage MICROSAR COM lets users develop their functional software by a of fixed I-PDUs with different data contents. fully bus-independent approach. All necessary tasks for transmitting messages and for cross-bus network management activities The following functions are optionally available: are handled by the configurable BSW modules COM, NM, PDUR and > COM: TX deadline monitoring IPDUM from MICROSAR COM. COM: PDU Replication (for ASR 4.0)

MICROSAR COM Modules according to AUTOSAR 4.0 V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program, we can offer various You will find information on the availability of hardware-specific training events and workshops for MICROSAR in our classrooms as MICROSAR BSW modules at: www.microsar.com/availability/ well as at your business site. We can also tell you about OEM-specific versions and custom support For more information on individual training events and dates please for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

> COM: Dynamic signal length (for ASR 4.0) Configuration > PDUR: TP layer fan-out and zero cost operation For convenient configuration we recommend an upgrade from the > PDUR: Transmit cancellation and change parameter request supplied DaVinci Configurator Base to DaVinci Configurator Pro. For more details, see the separate datasheet. Beyond the AUTOSAR standard, MICROSAR COM also contains the It is easy to link the COM modules PDUR, FRIF and CANIF to your following important services: complex drivers by configuration with DaVinci Configurator Pro. > COM: Indication and timeout flags for signals and signal groups > COM: Invalidity declaration of TX signals in case of RX signal Scope of Delivery timeout > Software modules as library with C header files, optionally as > COM: Deactivation of the TX confirmation interrupt source code > COM: Pre-compile optimizations such as function macros for very > Command line based generator (for Windows XP/ Windows 7) efficient signal access > BSW modules description > COM, PDUR: Transport of long I-PDUs and signals via CANTP and > DaVinci Configurator Base as basic editor via J1939TP (for ASR 3). Other TPs are available upon request. > Documentation > COM: SWC/CDD signal callout functions, e.g. to integrate gateways as complex drivers. The complete AUTOSAR solution from Vector > PDUR: Generic interface for integrating a TP and bus The AUTOSAR solution from Vector consists of the DaVinci tools, communication as complex driver MICROSAR-basic software and the MICROSAR RTE. > PDUR: Optimized CANTP- and FRISOTP-routing to avoid bursts You will find information on properties of BSW modules from the (for ASR 3) MICROSAR packages and detailed descriptions of functional features > PDUR: TP-Routing in accordance with ASR 4.0 (for ASR 3) of individual DaVinci Tools in the relevant datasheets. > NM: Synchronous sleep and wake-up of multiple networks via different NM coordinators (for ASR 3) > NM: Backup coordinator (for ASR 3) > NM: Pre-compile optimizations such as use of function macros > NM: Support of OSEK NM (configurable) > NM: Mixed operation of OSEK and AUTOSAR-NM on one channel

Configuration of the communication modules with DaVinci Configurator Pro

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR CAN

AUTOSAR Basic Software Modules for CAN Communication

The MICROSAR CAN package contains the BSW modules defined in the AUTOSAR architecture for CAN communication: CANIF, CANNM, Functions CANTP, CANSM and optional J1939TP and XCP. The BSW modules in MICROSAR CAN contain functions defined in AUTOSAR 3 (ASR 3) and 4.0 (ASR 4.0). Application Areas The following functions are available as options for the CANIF MICROSAR CAN is used to handle communication in CAN networks. module: It is also well-suited as a foundation for calibration with XCP, > Support of an external CAN controller gateways or flashing. > Increased number of Full CAN objects by combining multiple CAN You can also extend MICROSAR CAN with the option J1939TP pack- controllers on one physical CAN bus (Common CAN) age to enable operation of an AUTOSAR ECU in a J1939 network. The BAM and CMDT transport protocols are available for this. Beyond the standard itself, MICROSAR CAN offers the following important services: > Overview of Advantages CANIF: Double hash search algorithm for filtering the Rx mes- > Available for AUTOSAR 3 and 4.0 (from Q3/2012) sages > > Contains numerous useful extensions CANNM, CANTP: Pre-compile optimizations, e.g. for single- > Code and execution time are optimized based on need-specific channel systems > configuration CANSM: Optimization of the wakeup process by wakeup detec- > Inter-module configuration of all communication-specific soft- tion at ECU startup (for ASR 3) > ware modules CANSM: Support of ECU Passive Mode > > Fast wakeup handling at ECU startup CANSM: Extended Callback Interface for the error states “BusOff > Includes high-performance gateway functionality Begin” and “BusOff End” (for ASR 3) > > CANTP: ISO 15765-2 compatibility is configurable CANSM: Checks whether states were successfully set in the CAN > CANNM: OSEK NM compatibility is configurable driver (CANDRV) or CAN transceiver driver (CANTRCV). In case of > J1939 Transport Layer, BAM and CMDT, also for AUTOSAR 3 error, an automatic repetition is executed. (for ASR 3) > CANTP: Supports full duplex communication (for ASR 3)

MICROSAR CAN modules according to AUTOSAR 4.0 V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

> CANTP: Supports mixed addressing (11 bit CAN ID); typically for CAN/LIN gateway applications (also for ASR 3) Other MICROSAR Products for a Complete CAN Communication > CANTP: Optimized routing per ASR 4.0 (e.g. with Burst Trans- Stack mission) together with the PDUR from MICORSAR COM (also for Based on the AUTOSAR architecture, a complete communication ASR 3) stack for CAN can be formed using MICROSAR CAN together with > CANTP: ISO 15765-2 compatibility is configurable the BSW modules from the separately available MICROSAR COM, > CANTP: Sets BlockSize and STmin at runtime MICROSAR CAL and MICROSAR EXT packages. To interface MICROSAR CAN to the application and the hardware, you will still The following functionalities are available as options: need the following BSW modules: > J1939: Transport protokcols BAM and CMDT for J1939 networks > Hardware-specific CAN driver (CANDRV) from MICROSAR CAL (also for ASR3) > Hardware-specific transceiver control (CANTRCV) from > XCP: Transport protocol CANXCP und XCP Professional (see sepa- MICROSAR EXT rate datasheet) for measuring and calibrating over CAN > General communication modules (COM, NM, PDUR, IPDUM) from MICROSAR COM Configuration Modules in MICROSAR CAL and MICROSAR EXT are available for For convenient configuration, we recommend an upgrade from the many microcontrollers and transceivers. supplied DaVinci Configurator Base to DaVinci Configurator Pro. For more details, please refer to the separate datasheet. Other relevant MICROSAR Products for CAN > DCM and DEM from MICROSAR DIAG Scope of Delivery > DET, ECUM and COMM from MICROSAR SYS > Software modules as library with C header files, optionally as > XCP source code > Command line based generator (for Windows XP/ Windows 7) > BSW modules description > DaVinci Configurator Base as basic editor > Documentation

Vector offers a comprehensive range of products and services for your CAN projects

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR FR

AUTOSAR Basic Software Modules for FlexRay Communication

Vector offers you MICROSAR FR, an AUTOSAR-conformant package The following functions are available as options: for FlexRay communication. It contains the following BSW modules > FRISOTP: Optimized TP routing for gateways (for ASR4.0) defined in the AUTOSAR architecture: FRIF, FRNM, FRSM and selec- > XCP: Transport protocols FRXCP and XCP Professional (see sepa- tively FRTP or FRISOTP. MICROSAR FR can be extended with XCP as rate datasheet) for measuring and calibrating over FlexRay an option. MICROSAR FR contains the following important services that go Application Areas beyond the standard: MICROSAR FR is used to handle communication in FlexRay net- > FRDRV: Optimized wakeup during operation (WUDOP) works. Furthermore, it is ideal as a foundation for calibration with > FRDRV & FRIF: Support of the following APIs: CancelTransmit and XCP, gateways or flashing. LpdU reconfiguration (also for ASR 3) > FRIF: Dual channel redundancy for redundant transmission of Overview of Advantages frames and PDU-specific voting function for the SWCs > > Available for AUTOSAR 3 and 4.0 (from Q3/2012) FRISOTP: Optimized TP routing for gateway operation (for ASR 3) > > Contains many useful extensions FRNM: Pre-compile optimizations, e.g. for single-channel > Small code size and short execution times due to optimized admini- systems > stration of job lists of the FlexRay interfaces FRSM: Support of ECU Passive Mode, immediate startup after > Either the FRTP (AUTOSAR) or FRISOTP (ISO 10681) transport proto- passive wakeup, extended error handling by State Change Noti- col may be used, also for AUTOSAR 3 fication, configurable time delay for FlexRay startup at passive > Support of ECU passive mode in the FlexRay State Manager wakeup as well as configurable number of wakeup patterns (also > Early detection of synchronization losses for ASR 3)

Operating System Functions FlexRay basic software modules can be used entirely without an The BSW modules in MICROSAR FR contain functions defined in operating system. However, it makes sense to use an AUTOSAR OS AUTOSAR 3 (ASR 3) and 4.0 (ASR 4.0), where FRISOTP is a supple- or a conventional OSEK-OS (e.g. Vector osCAN). Ideally suited for ment to ASR 3. FlexRay applications is MICROSAR OS from Vector.

MICROSAR FlexRay Moduls according to AUTOSAR 4.0 V2.6 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program, we can offer various training You can find information on the availability of hardware-specific courses and workshops on MICROSAR at our classrooms or at your MICROSAR BSW modules at: www.microsar.com/availability/ business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates please versions as well as customized support for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

Configuration MICROSAR CAL, MICROSAR SYS and MICROSAR EXT packages. You For convenient configuration we recommend an upgrade from the will also need the following BSW modules to interface MICROSAR supplied DaVinci Configurator Base to DaVinci Configurator Pro. FR to the application and hardware: For more details, please refer to the separate datasheet. > Hardware-specific FlexRay driver (FRDRV) from MICROSAR CAL > Hardware-specific transceiver control (FRTRCV) from MICROSAR Scope of Delivery EXT > Software modules as library with C header files, optionally as > General communication modules (COM, NM, PDUR, IPDUM) from source code MICROSAR COM > Command line based generator (for Windows XP/ Windows 7) The modules in MICROSAR CAL and MICROSAR EXT are available for > BSW modules description many different microcontrollers and transceivers. > DaVinci Configurator Base as basic editor > Documentation Other MICROSAR Products for FlexRay > DCM and DEM from MICROSAR DIAG > The complete AUTOSAR Solution from Vector DET, ECUM and COMM from MICROSAR SYS > The AUTOSAR solution from Vector consists of the DaVinci tools, XCP MICROSAR basic software and the MICROSAR RTE. You will find information on properties of BSW modules from the Additional Services > MICROSAR packages and detailed descriptions of functional features Consultation in system design > of individual DaVinci Tools in the relevant datasheets. Integration of basic software in existing ECUs > Extension of standard modules per customer requirements > Development of customer specific AUTOSAR software compo- Other MICROSAR Products for a complete FlexRay Communica- nents (SWC) tion Stack > Hotline, special workshops and training events on the topic of Based on the AUTOSAR architecture, a complete communication embedded software and AUTOSAR stack for FlexRay can be made with MICROSAR FR together with the BSW modules from the separately available MICROSAR COM,

Vector offers a comprehensive portfolio of products and services for your FlexRay projects

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR LIN

AUTOSAR Basic Software Modules for LIN Communication

MICROSAR LIN contains the BSW modules defined in the AUTOSAR Beyond the standard, MICROSAR LIN includes the following architecture for LIN communication: LINIF, LINSM and LINNM (for important services: AUTOSAR 4.0). According to AUTOSAR, LINTP is a part of LINIF. The > LINIF: Configurable wakeup delay LIN transport protocol is offered as an option, because not every LIN > LINIF and LINTP: Separately configurable memory mapping of communication stack requires a transport protocol. configuration data for LINIF and LINTP. This is especially ap- pealing for controllers with segmented memory. The MICROSAR Application Areas LIN product includes two separate generators for LINIF and MICROSAR LIN handles communication tasks for a LIN Master in a LINTP for this purpose. LIN network. In addition, it may be used as a foundation for gate- > LINIF/LINSM: Notification of Schedule Table End ways or flashing. > LINTP (optional): Extends gateway functionality for precise switchover of the schedule tables for diagnostic requests and Overview of Advantages responses > > Available for AUTOSAR 3 and 4.0 (from Q3/2012) LINSM: Extended interface for monitoring the LINSM sub-modes > Contains numerous useful extensions for controlled switchover of the LIN schedule tables (for ASR 3) > > Minimized scheduling jitter for multi-channel master LINSM: Optimized startup behavior by automatic selection of a > Optimized routing of diagnostic requests to LIN Slaves schedule table (configurable) (for ASR 3) > Quick start of the LIN channel > Reliable switching of schedule tables possible Configuration > Based on Vector’s many years of experience with production soft- For convenient configuration, we recommend an upgrade from the ware for LIN supplied DaVinci Configurator Base to DaVinci Configurator Pro. For more details, please refer to the separate datasheet. With DaVinci Configurator Pro support, you can acquire infor- Functions mation on the connected LIN1.3 and LIN2.x Slaves. This informa- The BSW modules from MICROSAR LIN contain functions defined in tion is saved in the ECU Configuration Description and is consid- AUTOSAR 3 (ASR 3) and 4.0 (ASR 4.0), where the LINTP module is ered when configuring the master. This lets the master evaluate available as an option.

MICROSAR LIN modules according to

V2.4 2012-02 AUTOSAR 4.0

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program we can offer various training For information on the availability of hardware-specific MICROSAR courses and workshops on MICROSAR at our classrooms or at your BSW modules go to: www.microsar.com/availability/ business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates please versions and individual support for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

the response error bits sent by the slaves and then initiate the application and hardware, you will still need the following BSW associated DEM events. modules: > Hardware-specific LIN driver (LINDRV) from MICROSAR CAL Scope of Delivery > Hardware-specific transceiver control (LINTRCV) from MICROSAR > Software modules as library with C header files, optionally as EXT source code > General communication modules (COM, PDUR) from MICROSAR > Command line based generator (for Windows XP/ Windows 7) COM > BSW modules description The modules in MICROSAR CAL and MICROSAR EXT are available for > DaVinci Configurator Base as basic editor many different microcontrollers and transceivers. > Documentation Other Relevant MICROSAR Products for LIN The complete AUTOSAR Solution from Vector > DET, ECUM and COMM from MICROSAR SYS The AUTOSAR solution from Vector consists of the DaVinci tools, MICROSAR-basic software and the MICROSAR RTE. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets.

Other MICROSAR Products for a Complete LIN Communication Stack 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 CAL and MICROSAR EXT packages. To interface MICROSAR LIN to the

Vector offers you a comprehensive range of products and services for your LIN projects

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR IP

AUTOSAR Basic Software Modules for Communication over Internet Protocol via Ethernet

> Overview of Advantages Simultaneously and efficiently measure and calibrate many > Supports Internet Protocols IPv4 and IPv6 parameters with XCP on Ethernet, > > Available for AUTOSAR 3 and 4.0 (from Q3/2012) Perform vehicle diagnostics per ISO 13400-2 (DoIP) over IP, > > Contains both UDP and TCP protocols Intelligent charging of batteries (Smart Charging according to > Configurable number of sockets ISO/IEC 15118). > Reduced number of copying operations > Supports Diagnostics over IP (DoIp) per ISO 13400-2 The superior data throughput of Ethernet enables enormous > Data is exchanged up to 200 times faster than over a conventional reductions in overall flash and diagnostic times. However, it High-Speed CAN interface requires a gateway in the vehicle, which interconnects the various in-vehicle networks to the external Ethernet. MICROSAR IP implements the necessary gateway functionality in combination with The Internet protocols IPv4 and IPv6 based on TCP/IP over Ether- other MICROSAR packages. net are two very widely used standards for transmitting data at high speed. Functions The MICROSAR IP bundle contains AUTOSAR BSW modules and the The following BSW modules from MICROSAR IP contain the func- modules from the RFC standard for Ethernet communication of tions defined in AUTOSAR 4.0 (ASR 4.0). They enable socket-based ECUs. Standardization of the Internet technology for use in auto- communication with the ECU. MICROSAR IP has an ASR 3-compati- motive projects is part of AUTOSAR 4.0. However, MICROSAR IP is ble interface for use in an AUTOSAR 3 (ASR 3) ECU. also available as a supplement to AUTOSAR 3. MICROSAR IP can be With MICROSAR IP it is possible to use IPv4 and IPv6 simultane- extended with XCP as an option. ously at runtime. > IPBASE: The basic package for IP contains the modules Socket & Application Areas UDP according to RFC (Requests for Comments). In addition, you With MICROSAR IP in the ECU and a conventional PC as a communi- will need one of the following options: cation partner, you can do the following with no extra hardware > IPBASE IPv4: IPv4, DHCPv4, ICMPv4, ARP and TCP other than an Ethernet cable: > IPBASE IPv6: IPv6, DHCPv6, ICMPv6, TCP and NDP > Quickly flash large quantities of data,

MICROSAR IP modules according to AUTOSAR 4.0 V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program, we can offer various For information on the availability of hardware-specific MICROSAR BSW training courses and workshops on MICROSAR at our classrooms or at modules, go to: www.microsar.com/availability/ your business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates please versions and customized support for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

The modules from IPBASE assure basic functionality of the Scope of Delivery TCP/IP protocols according to AUTOSAR requirements. The mod- > Software modules as library with C header files, optionally as ules are optimized to minimize the number of copying opera- source code tions. This property offers excellent savings in execution time > Command line based generator (for Windows XP/ Windows 7) for gateway routing, flash sequences and in XCP and diagnostic > BSW module description applications. > DaVinci Configurator Base as basic editor > ETHIF: The AUTOSAR Ethernet Interface enables hardware-inde- > Documentation pendent control of the Ethernet drivers. > ETHSM: The AUTOSAR Ethernet State Manager handles activa- Other Relevant MICROSAR Products tion/deactivation of the microcontroller and transceiver. Based on the AUTOSAR architecture, a complete communication > SOAD: The Socket Adapter implements the communication via stack for Ethernet is formed with MICROSAR IP together with the PDUs defined in AUTOSAR as socket-oriented communication BSW modules from the separately available MICROSAR COM, (TCP/IP). SOAD also contains the diagnostic functionality MICROSAR CAL and MICROSAR EXT packages. You will also need the defined in ISO 13400-2 (DoIP). following BSW modules to interface MICROSAR IP to the applica- > ETHXCP: You can use the Ethernet transport layer ETHXCP and tion and hardware: the XCP Professional module (see separate datasheet) to meas- > HW-specific Ethernet driver (ETHDRV from MICROSAR CAL) ure and calibrate over Ethernet according to the ASAM standard. > HW-specific transceiver control (ETHTRCV from MICROSAR EXT) > UDPNM: UDP network management is responsible for synchro- > General communication module (PDUR) from MICROSAR COM nous wake-up and go-to-sleep transitions of the IP ECUs. Modules in MICROSAR CAL and MICROSAR EXT are available for many different microcontrollers and transceivers. Configuration For convenient configuration, we recommend an upgrade from the Other Relevant Products for Ethernet supplied DaVinci Configurator Base to DaVinci Configurator Pro. > DCM and DEM from MICROSAR DIAG For more details, please refer to the separate datasheet. > DET, ECUM and COMM from MICROSAR SYS IP-specific configuration parameters for ASR 3 are saved as an > XCP extension in the “ECU Configuration Description.”

Vector offers you a comprehensive portfolio of products and services for your IP projects

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR MOST

AUTOSAR compatible Basic Software Modules for MOST Communication

Previously, MOST (Media Oriented Systems Transport) was not part Functions of the AUTOSAR standard. Vector now offers MICROSAR MOST, an The MOST-specific BSW module MOSTIF and the Dispatcher (DISP) AUTOSAR-compatible embedded software solution for your MOST template are Vector-specific extensions of the AUTOSAR standard: application. It contains the BSW modules MOSTIF and DISP. > MOSTIF: MOST Interface for hardware-independent conversion of the PDUs to be transmitted to MOST frames. MOSTIF is compati- Application Areas ble with the BSW modules of AUTOSAR 3 and 4.0. MICROSAR MOST lets you connect AUTOSAR ECUs to a MOST ring to > DISP: The Dispatcher is a template for interfacing the MOSTIF exchange data on the control and asynchronous channel. In addi- module to a Network Services Library for MOST. tion, MICROSAR MOST contains all of the services required to implement gateway functionality to CAN, LIN, FlexRay and Ether- The BSW modules from MICROSAR MOST are offering the following net buses. services: BSW modules from MICROSAR MOST are interfaced to the applica- > Support of signal, message and TP routing tion software in a way similar to CAN, LIN or FlexRay, and the > Sending signals on MOST via Notification Services product is fully compatible with the AUTOSAR architecture. > Support of MOST protocols MHP and AMS MICROSAR MOST is interfaced to the MOST bus via a Network Services Library and a low level driver (MOSTDRV). Operating System MOST basic software modules can be used entirely without an Overview of Advantages operating system. However, it is advisable to use an AUTOSAR OS > Extends AUTOSAR features to include MOST communication or a conventional OSEK-OS (e.g. Vector osCAN). The MICROSAR OS > Available for AUTOSAR 3 and 4.0 (from Q3/2012) from Vector is ideally suited for MOST applications. > Flexibly routes messages and signals between MOST buses and any desired networks Configuration > Provides seamless interface to a Network Services Library for MOST For convenient configuration, we recommend an upgrade from the > Supports MOST 150 supplied DaVinci Configurator Base to DaVinci Configurator Pro. For more details, please refer to the separate datasheet.

MICROSAR MOST modules according to AUTOSAR 4.0 V2.12 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

For gateways, in particular, Vector offers customized solutions that To interface this communication stack to a MOST bus, a Network take into account the special aspects of OEM-specific data formats Services Library and a low level driver (MOSTDRV) are also neces- in configuration. sary. These two components are not included with the MICROSAR MOST product. Scope of Delivery > Software modules as library with C header files, optionally as Low-Level Driver source code In the framework of project work, Vector would be glad to create a > Command line based generator (for Windows XP/ Windows 7) Low-Level Driver for interfacing the Network Services Library for MOST > BSW module description to your specific hardware. > DaVinci Configurator Base as basic editor > Documentation Other Relevant MICROSAR Products for MOST > DCM and DEM from MICROSAR DIAG The complete AUTOSAR Solution from Vector > DET, ECUM and COMM from MICROSAR SYS The AUTOSAR solution from Vector consists of the DaVinci tools, MICROSAR-basic software and the MICROSAR RTE. You will find information on properties of BSW modules from the MICROSAR packages and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets.

Other MICROSAR Products for a complete MOST Communication Stack MICROSAR MOST, together with the general communication modules COM and PDUR from the MICROSAR COM packet, combine to form a communication stack for MOST.

Vector offers a comprehensive range of products and services for MOST projects

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR MEM

AUTOSAR Basic Software Modules for Memory Management

Overview of Advantages Functions > Exceptionally secure data transactions The BSW modules in MICROSAR MEM contain functions defined in > Efficient data accesses AUTOSAR 3 (ASR 3) and 4.0 (ASR 4.0). In each memory stack, you > Efficient and robust management of nonvolatile memories will need the BSW modules NVM and MEMIF from MICROSAR MEM. > Redundant storage of management data increases reliability of data They handle block-oriented and technology-independent access to − access the memory areas without requiring prior knowledge of memory > Inter-module configuration of the entire memory stack attributes. Your memory stack will need additional BSW modules, > Platform-optimized memory stack solution from a single source depending on the use case: > > Available for AUTOSAR 3 and 4.0 (ab Q3/2012) When a flash memory is used: Flash EEPROM Emulation (FEE) from MICROSAR MEM and a flash driver (FLSDRV) from MICROSAR CAL that is suitable for your hardware, or for external memory The MICROSAR MEM package contains all of the AUTOSAR modules the module DRVEXT from MICROSAR EXT. To manage the data, for memory management: NVM, MEMIF, EA and FEE. They support the FEE module needs at least two flash sectors. management, checking and restoring of data from nonvolatile > When using an EEPROM: EEPROM Abstraction (EA) from memories (Flash or EEPROM). The Basic Software Modules (BSW) MICROSAR MEM and a EEPROM driver (EEPDRV) from MICROSAR from MICROSAR MEM are fast, reliable and robust. CAL that is suitable for your hardware, or for external memory the module DRVEXT from MICROSAR EXT. Application Areas MICROSAR MEM contains AUTOSAR services for reading, writing It is possible to use multiple flash or EEPROM chips in one ECU. This and erasing persistent application data in flash and/or EEPROM involves using multiple FEE or IO modules in the ECU software. memories. This gives the functional software hardware-independ- For special requirements, Vector offers platform-optimized solu- ent access to memory. The application does not need to know the tions, e.g. for using the EA BSW module in data flashing or opti- specific type of memory that exists on the platform or whether this mizing the FEE module for specific hardware. memory is internal to the controller or externally connected to it. The following function is optionally available: > NVM: Block type “DATASET_ROM” with multiple ROM blocks

MICROSAR MEM modules according to AUTOSAR 4.0 V2.5 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program we offer various training For information on the availability of hardware-specific MICROSAR BSW courses and workshops on MICROSAR at our classrooms or at your modules go to: www.microsar.com/availability/ business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates please versions and individual support of your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

Beyond the standard, MICROSAR MEM contains the following Scope of Delivery important services: > Software modules as library with C header files, optionally as > Fixed, predefined maximum execution times for all MICROSAR source code MEM functions. This enables system optimizations to shorten > Command line based generator (for Windows XP/ Windows 7) access times. (for ASR 3) > BSW modules description > NVM: Allocates RAM for CRC memory storage (for ASR 3) > DaVinci Configurator Base as basic editor > NVM: Dedicated interface for the DCM diagnostic module for > Documentation direct read-out and manipulation of data blocks > NVM and EA: Additional configurable transaction security, which Other MICROSAR Products relevant for a Memory Stack is a standard feature of the FEE module Based on the AUTOSAR architecture, a complete memory stack can > FEE: High-performance administration of stored memory data be formed with memory services from MICROSAR MEM together > FEE: Common usage of FEE module by Flash Bootloader (FBL) with other platform-specific BSW modules from the separately and application possible - also with common memory blocks. An available MICROSAR CAL and MICROSAR EXT packages. update of the ECU software can be done without adjustment of > FLSDRV and/or EEPDRV from MICROSAR CAL the FBL. > DRVEXT from MICROSAR EXT for external memory chips > FEE: Update support for adjustment of non volatile memory after In addition, it is easy to integrate MCAL drivers from semiconduc- ECU re-programming. This is done with a new configuration tor manufacturers in the MICROSAR memory stack. table (content and size). > FEE/EA: Redundant storage of management data for increased Depending on the desired safety level, you can verify your memory reliability of data access data with the checksum module (CRC) from the MICROSAR LIBS > FEE: Flexible placement of the FEE sectors in the DataFlash bundle. For more information, please refer to the separate > FEE: Services for handling of undervoltage situations MICROSAR SYS datasheet.

Configuration of the MICROSAR MEM modules with DaVinci Configurator Pro

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR SYS

System-related Basic Software Modules for AUTOSAR

Overview of Advantages: Functions > Available for AUTOSAR 3 and 4.0 (from Q3/2012) The BSW modules in MICROSAR SYS contain functions defined in > The ECUM module is included as either a resource-saving Pre-Com- AUTOSAR 3 (ASR 3) and 4.0 (ASR 4.0): > pile variant or as a flexible Post-Build variant BSWM: The Basic Software Mode Manager manages mode change > Supports activation/deactivation of PDUs for diagnostics (Service requests from the BSW modules and SWCs and executes them Communication Control) according to the standardized action lists. For example, the > Cross-module configuration of modules from MICROSAR SYS and BSWM module is responsible for activating and deactivating PDU MICROSAR CAL groups and NM-PDUs for diagnostics. > COMM: The “Communication Manager“ monitors the state changes of the communication channels connected to the ECU The MICROSAR SYS package contains the AUTOSAR modules and of the sub-networks configured in the ECU. It can keep the providing system services. They assure start-up and operation of ECU awake and ready for communication as necessary. Further- the ECU, and are an important part of each AUTOSAR ECU. System more, it coordinates access of all SWCs to the communication services for diagnostics and the operating system can be obtained channels and sub-networks. Optionally, COMM supports the bus in the MICROSAR DIAG and MICROSAR OS packages. type ”Internal”. > DET: The Development Error Tracer collects the development Application Areas errors of the SWCs and BSW modules. Optionally, DET supports Services from the MICROSAR SYS basic software modules (BSW) the Service Ports. cover an important aspect of the basic functionality of your > ECUM: The ECU State Manager is responsible for Startup, Shut- AUTOSAR ECU. They are called by the functional software (via the down and WakeUp. In ASR3, there are other fixed defined oper- RTE) and the rest of the BSW modules. System services include ating states that are managed by the ECUM. In ASR 4, these power and mode management, control of all communication operating states are flexibly defined by the user in the BSWM. channels, scheduling of all BSW modules and monitoring of indi- This makes it possible to implement individual energy-saving vidual software components (SWC) of the functional software. states or different power-up behaviors. > LIBS: The LIBS package contains the Cyclic Redundancy Check Library (CRC), Crypto Abstraction Library (CAL) and the E2ELIB.

MICROSAR SYS modules according to AUTOSAR 4.0 V2.7 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program, we can offer various You will find information on the availability of hardware-specific training events and workshops for MICROSAR in our classrooms as well MICROSAR BSW modules at: www.microsar.com/availability/ as at your business site. We can also tell you about OEM-specific versions and custom support For more information on individual training events and dates please for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

For ASR 3, LIBS is part of MICROSAR SYS. For ASR 4.0, MICROSAR > STBM (for ASR4): The Synchronized Time-Base Manager enables LIBS is available as a separate bundle. precise synchronization between different parts of the ECU soft- > SCHM: The Schedule Manager/BSW Scheduler coordinates ware. It makes one or more common time bases available to the execution of the BSW modules. In configuring you define BSW modules and the SWCs. individual tasks and the cycle times of individual BSW module. You also define the exclusive areas settings for each module Watchdog for ISO 26262 applications centrally. For ASR 3, SCHM is part of MICROSAR SYS. In ASR 4, All watchdog modules are also available as SEooCs (Safety Element the MICROSAR RTE assumes the functionality of the SCHM. out of Context) for safety-relevant functions up to ISO 26262 / > WDGM and WDGIF: The Watchdog Manager monitors for correct ASIL D. They are well suited for validation of runtime monitoring of operation of the functional software with the modules WDGIF tasks as well as flow control for the SWCs. For more details, please and WDGDRV (MICROSAR CAL). refer to the MICROSAR Safe datasheet.

In addition, the following extensions are included: Configuration > COMM: Compatibility with OSEK NM, Link-time implementation For convenient configuration, we recommend an upgrade from the (for ASR 3) supplied DaVinci Configurator Base to DaVinci Configurator Pro. > ECUM: ECUM is available as a pre-compile or post-build imple- For more details, please refer to the separate datasheet. mentation variant (for ASR 3) > WDGM, WDGIF: Precise supervision of defined time windows for Scope of Delivery the watchdog (even for high resolution window watchdogs) > Software modules as library with C header files, optionally as (also for ASR 3) source code > Command line based generator (for Windows XP/ Windows 7) The following BSW modules are available as options: > BSW modules description > WDGM: Program Flow Monitoring for monitoring the SWCs > DaVinci Configurator Base as basic editor > CSM (for ASR 4.0): The Crypto Service Manager gives the SWCs > Documentation and the BSW modules uniform access to cryptographic functions such as AES 128 encryption (Advanced Encryption Standard).

Configuring the COMM module with DaVinci Configurator Base

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR DIAG

AUTOSAR-compatible implementation of the UDS protocol

Overview of advantages with OEM-specific extensions. It is well-suited for production use > OEM-independent solution for AUTOSAR 3 and 4.0 (from and is already available to many OEMs. For ECUs without a special Q3/2012) diagnostic specification, an OEM-independent bundle of MICROSAR > Customized solutions available for many automotive OEMs DIAG is available. > Vector’s numerous years of experience in the diagnostics field > Supports OBDII and WWH-OBD (Euro VI) MICORSAR DIAG can be used for legal requirements of today and > Variants handling already included for diagnostic configuration tomorrow, such as EURO VI. Support of OBDII (ISO 15031/ SAE > Configurable with the CANdela-and ODX format J1979) and WWH-OBD (ISO27145) is available as an option. > Generation of optimized application code templates If your ECU requires variants in the diagnostic configuration, MICROSAR DIAG offers a high-performance solution for this. You MICROSAR DIAG contains the BSW modules for implementing the can define up to 31 different parameterizations and store them in UDS protocol ISO 14229-1:2006 (resp. ISO/DIS 14229-1:2011) the ECU, in a resource-optimized way. This avoids redundancies in according to AUTOSAR, making it the diagnostic software for your the ECU software, because identical interfaces to the same data, vehicle project. MICROSAR DIAG handles a number of tasks: services and DTCs are combined in the generated diagnostic code. > OEM-specific implementation of fault memory and its management Functions > OEM-specific implementation of the diagnostic protocol for The BSW modules in MICROSAR DIAG contain the functions for the communication between the diagnostic tester and the ECU three BSW modules DCM, DEM and FIM that are defined in AUTOSAR > Deactivation of certain functionalities due to active error entries 3 (ASR 3) and 4.0 (ASR 4.0): Combined with CANdelaStudio, the widely used specification tool for creating diagnostic data, you get a complete diagnostic solu- Diagnostic Event Manager (DEM) Functions tion from a single source. The OEM-specific DEM module contains the implementation of the respective OEM requirements concerning the fault memory of an Application Areas ECU. The OEM-independent variant is available for ASR 3 as well as Beyond the AUTOSAR standard, every OEM has its own require- ASR 4.0. It supports the following functions as standard features: ments for diagnostics. That is why Vector offers MICROSAR DIAG

MICROSAR DIAG modules according to AUTOSAR 4.0 V2.6 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Contact and Availability You will find information on the availability of hardware-specific MICROSAR BSW modules at: www.microsar.com/availability/ We would be glad to provide you with information on OEM-specific variants and individual support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact

> Management of all DTC status bits according to the UDS standard sender/receiver communication, read or write in the NvM and > Definition of individual snapshots and extended records adapt IoHwAb signals. > Predefined extended records (e.g. OccurenceCounter) > High-performance mode control, which enables execution of > Counter and time-based error de-bounce algorithms diagnostic services via mode dependencies, for example. > Suppression of low-priority errors when memory is full > Flexible unlearning (aging) of errors The OEM-independent variant of the DCM is available for both ASR > Variants handling for diagnostic configuration 3 and ASR 4.0. For a complete list of supported services, please > Link time configuration refer to the table at the end of this datasheet. > Compressed Configuration Data to optimize code size The DCM modules for specific OEMs implement the specifications of the particular OEM. Therefore, the lists of supported services vary, The following AUTOSAR functions are available as options: e.g. in supplemental support of ResponseOnEvent or LinkControl. > Support of combined errors We would be glad to provide you with detailed information on this. > OBDII (ISO 15031 / SAE J1979) > WWH-OBD (ISO27145) The following functions are available as options: > Support of OBDII (ISO15031-5) The DEM base functionality differs a little between ASR 3 and ASR > WWH-OBD (ISO27145) 4.0, except for the interface definitions. That is why Vector offers a migration solution that you can use to easily migrate your ASR 3 In addition, the DCM contains the following extensions as standard compatible SWCs to an ASR 4.0 project. features: > Variant handling for diagnostic configurations Diagnostic Communication Manager (DCM) Functions > Multiple Client support The DCM implements UDS and OBDII services in the ECU. The ASR > Seamless collaboration with the Vector Flash Bootloader 4.0 version of the DCMs offers several extensions compared to the > Generation of an application code template for the ECU software ASR 3 version. The most important of them are: > Functional Diagnostics. This lets the DCM perform such tasks as Function Inhibition Manager (FIM) Functions directly accessing individual signals of ECU-internal MICORSAR FIM contains the functional features of ASR 3 and ASR 4.0 as standard.

Parameterization of the MICROSAR DIAG modules is done with Candelastudio.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Services for Diagnostic Applications: > Customer-specific extensions of MICROSAR DIAG > Creation of a customer-specific diagnostic application > Integration of diagnostics in your ECU software

Configuration and Parameterization The complete AUTOSAR Solution from Vector You adapt the BSW modules from MICROSAR DIAG to your applica- The AUTOSAR solution from Vector consists of the DaVinci tools, tion’s needs comfortably by configuration with DaVinci Configu- MICROSAR-basic software and the MICROSAR RTE. rator Pro. This may be done either with the help of a CANdela or You will find information on properties of BSW modules from the ODX file or by an “ECU Configuration Description”. MICROSAR packages and detailed descriptions of functional features For ASR3, diagnostic-specific parameterization of the DCM is of individual DaVinci Tools in the relevant datasheets. performed exclusively via a CANdela file. You can create it quickly and simply or import it from most commonly used ODX dialects with the proven “diagnostic authoring tool” CANdelaStudio. Other Relevant Vector Products To fulfill specific ISO standards, you can combine MICROSAR DIAG Scope of Delivery with the following MICROSAR products: > Software modules as a library with C header files, optionally as > MICROSAR CAN (ISO 15765-3 oder ISO/DIS 14229-3) source code > MICROSAR FR (ISO/DIS 14229-4) > Command line based generator (for Windows XP/Windows 7) > MICROSAR IP (ISO/DIS 14229-5) > BSW module description You can use CANdelaStudio to parameterize the CANdela or ODX file > Documentation for configuration of MICROSAR DIAG. For more information, please > Converters for CANdela diagnostic descriptions refer to the separate datasheet in Vector’s diagnostics catalog.

Parameterization of MICROSAR DIAG is done by CANdelaStudio and DaVinci Configurator Pro

More Information: www.vector.com/contact EMBEDDED SOFTWARE

The module DCM from MICROSAR DIAG supports … … optional: OBD II Diagnose Services

… by default: UDS diagnostic services

Diagnostic Service Name Service ID ASR 3: The SWC ASR 4.0: The SWC Diagnostic Service Name Service The SWC has to … (ISO 14229-1) (hex) has to … has to … (ISO 15031-5) ID Diagnostic and Communication Management Functional Unit Diagnostic Service Definition for CAN DiagnosticSessionControl 10 … grant service - (handled in DEM Request Current Powertrain … handle data acquisition for 01 execution configuration) Diagnostic Data each PID other than the ECUReset 11 … grant service - (handled in DEM "supported ID" and DEM ones execution configuration) Request Powertrain Freeze Frame 02 - (handled in DEM module) … calculate … calculate Data SecurityAccess 27 seed/key for each seed/key for each Request Emission-Related 03 - (handled in DEM module) security level security level Diagnostic Trouble Codes CommunicationControl 28 … grant service - (handled in DEM Clear/Reset Emission-Related 04 - (handled in DEM module) execution configuration) Diagnostic Information

TesterPresent 3E - - Request On-Board Monitoring Test … handle data acquisition for 06 ControlDTCSetting 85 - (handled in DEM - (handled in DEM Results for Specific Monitored each TestId of a MonitorId module) module) Systems Request Emission-Related Data Transmission Functional Unit … handle data … handle data Diagnostic Trouble Codes Detected 07 - (handled in DEM module) ReadDataByIdentifier 22 acquisition for acquisition for During Current or Last Completed Driving Cycle each DataId each DataElement ReadMemoryByAddress 23 via callout via callout Request Control of On-Board 08 … process each TestId System, Test or Component ReadDataByPeriodic 2A - - … handle data acquisition for Identifier Request Vehicle Information 09 each InfoType ID other than DynamicallyDefineData 2C - - the "supported ID" and DEM Identifier ones …handle data …handle data Request Emission-Related WriteDataByIdentifier 2E access for each access for each Diagnostic Trouble Codes with 0A - (handled in DEM module) DataId DataElement Permanent Status WriteMemoryByAddress 3D via callout via callout Stored Data Transmission Functional Unit

ReadDTCInformation 19 - (handled in DEM - (handled in DEM module) module) ClearDiagnosticInformation 14 - (handled in DEM - (handled in DEM module) module) Input/Output Control Functional Unit InputOutputControlBy 2F … control I/O for … control I/O for Identifier each DataId each DataElement Remote Activation Of Routine Functional Unit … start … start RoutineControl 31 (stop/request (stop/request result) for each result) for each RoutineId RoutineId

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR CAL

AUTOSAR Driver for Control of Microcontroller Peripherals

Overview of advantages The MICROSAR CAL drivers work optimally together with the rest of > Optimal support of microcontroller peripherals the MICROSAR bundles. Depending on the requirements of your > Simplified configuration by considering cross-module parameter application, you may use additional bundles (e.g. MICROSAR CAN, dependencies in the configurator MICROSAR MEM, etc.) and thereby obtain a complete communica- > Development accelerated by plausibility and completeness tests in tions stack, for example, or memory management. the configurator > Resource-saving, since functionalities can be deactivated Functions > Reduced hardware requirements due to optimal utilization of hard- The MICROSAR CAL package contains the driver modules Adc, Can, ware buffers Eth, Fr, Lin, Dio, Eep, Fls, Gpt, Icu, Mcu, Port, Pwm, Spi and Wdg as > Gateway developments are supported by efficient auxiliary func- well as the test modules CoreTst, FlsTst und RamTst in the version tions for AUTOSAR 4.0. The modules conform to AUTOSAR 3 and 4.0 and > Available for AUTOSAR 3 and 4.0 (from Q3/2012) are available for many commonly used microcontrollers.

In addition, MICROSAR CAL contains the following extensions: The MICROSAR CAL package contains the drivers for controlling the > Implementation of Interrupt Service Routines as CAT1, CAT2 or microcontroller’s peripherals. These drivers are fully compatible void-void function (configurable) (for AUTOSAR 3) with the AUTOSAR specifications of the “Microcontroller Abstrac- > CANDRV: Notification (Callback) on message reception and after tion Layer”. Each MICROSAR CAL driver is optimized controller- successfully sending a message. This makes it possible to auto- specifically. matically execute application-specific code. > DIODRV: User-configurable locating of the pins within a Chan- Application Areas nelGroup MICROSAR CAL gives you a turn-key solution for driving your > FRDRV: Supports self-diagnostics. When the FlexRay controller microcontroller peripherals. So, it is not necessary to make detects an error, it notifies the application, so that it can call up changes to the functional software when switching to different the error status. hardware. All you need to do is switch out MICROSAR CAL to inte- > ICUDRV: Notification of timer overrun and in signal measure- grate the appropriate drivers. ment mode

MICROSAR CAL Modules according to AUTOSAR 4.0 V2.5 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program we can offer various For information on the availability of hardware-specific MICROSAR training courses and workshops on MICROSAR at our classrooms or at BSW modules go to: www.microsar.com/availability/ your business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates please versions and individual support for your AUTOSAR projects. Find your visit: www.vector-academy.com contact person at: www.vector.com/contact

> MCUDRV: Reset mechanisms are user-configurable for the func- Scope of Delivery tion Mcu_PerformReset(). > Software modules as library with C header files, optionally as source code The following functionalities or modules are available options: > Command line based generator (for Windows XP/ Windows 7) > CANDRV: Option “HighEnd” offers extended filter options for > BSW module description Multiple Basic CAN objects, RX queue to shorten the interrupt > DaVinci Configurator Base as a basic editor time during receiving, individual polling of mailboxes to assure > Documentation data consistency and reduction of interrupt load. > FLSTST: The Flash Test checks internal and external memory cells The complete AUTOSAR solution from Vector that actually cannot be modified. This is especially important for The AUTOSAR solution from Vector consists of the DaVinci tools, safety-relevant applications. MICROSAR basic software and MICROSAR RTE. > CORETST: The Core Test controls the test possibilities contained You will find information on properties of BSW modules from the in the microcontroller core and offers a framework for imple- MICROSAR packages as well as detailed descriptions of functional menting further tests. Especially for safety-relevant applica- features of the DaVinci Tools in the particular datasheets. tions, CORETST tests critical units such as the ALU and the registers. > IICDRV: The IICDRV contains drivers for interfacing to external Additional Services peripheral chips via the Inter-Integrated Circuit Bus (I2C) > Integration of drivers by third-party producers, e.g. semicon- (Vector extension). ductor manufacturers, in DaVinci Configurator Pro. This lets you configure the entire ECU software with a single tool, seamlessly Configuration and quickly. For convenient configuration, we recommend an upgrade of the > In the framework of project work, Vector would be glad to create supplied DaVinci Configurator Base to DaVinci Configurator Pro. a low-level MOST driver for your specific hardware to interface it For more details see the separate datasheet. to the Network Services Library.

Configuration of the ADCDRV with DaVinci Configurator Base

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR EXT

AUTOSAR drivers for control of external devices

Overview of Advantages complete communication stack or memory management per > Optimal control of your external transceiver and memory devices AUTOSAR specification. > Available for AUTOSAR 3 and 4.0 (from Q3/2012) > Additional support for LIN and Ethernet transceivers Functions > Simplified configuration by considering parameter dependencies The BSW modules in MICROSAR EXT contain functions defined in with other modules AUTOSAR 3 (ASR 3) and 4.0 (ASR 4.0) plus the following extended > Development accelerated by plausibility and completeness checks functions: > in the Configurator Bus error detection on FlexRay > LIN transceiver drivers (also for ASR 3) > Ethernet transceiver drivers (also for ASR 3) MICROSAR EXT contains communication-related AUTOSAR transceiver drivers for CAN (CANTRCV), FlexRay (FRTRCV), LIN (LINTRCV), Scope of Delivery Ethernet (ETHTRCV) and drivers for other external devices such > Software modules as library with C header files, optionally as EEPROM, flash memory and watchdog (DRVEXT). Functions con- source code tained in the drivers were specified by AUTOSAR in the “ECU > Command line based generator (for Windows XP/ Windows 7) Abstraction Layer” and they conform to AUTOSAR 3 and 4.0. They > BSW modules description have each been optimized for a specific device and are available for > DaVinci Configurator Base as basic editor many commonly used devices. > Documentation

Application Areas MICROSAR EXT gives you a turn-key solution for driving your exter- The complete AUTOSAR Solution from Vector nal peripheral devices. So, it is not necessary to modify the func- The AUTOSAR solution from Vector consists of the DaVinci tools, tional software when switching out external hardware. All you MICROSAR basic software and MICROSAR RTE. need to do is switch out the relevant drivers from MICROSAR EXT. You will find information on properties of BSW modules from the Depending on the requirements of your application, you can add MICROSAR packages as well as detailed descriptions of functional other packages (e.g. MICROSAR CAN, MICROSAR MEM, etc.) for a features of the DaVinci Tools in separate datasheets.

MICROSAR EXT modules according to AUTOSAR 4.0 V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program we can offer various training For information on the availability of hardware-specific MICROSAR courses and workshops on MICROSAR at our classrooms or at your BSW modules go to: www.microsar.com/availability/ business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates Please versions and individual support for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

Other Relevant MICROSAR Products The external devices are physically driven via SPI, DIO or a port. You will need the relevant drivers for this (SPIDRV, DIODRV or PORTDRV) from MICROSAR CAL.

Additional Services Vector can offer services for integrating the configuration of your drivers or drivers by third-party producers, such as semi-conductor manufacturers in DaVinci Configurator Pro. This lets you configure the entire ECU software with a single tool, seamlessly and quickly.

Configuration of MICROSAR EXT with DaVinci Configurator Base

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR IO

AUTOSAR Input-Output Hardware Abstraction

Overview of Advantages In configuring MICROSAR IO, you define each individual signal as > Quick implementation of user-specific code for acquiring and either a user defined signal or a DIO port signal. MICROSAR IO providing ECU signals provides all of the necessary Client/Server interfaces and code > Generation of complete DIO accesses templates needed to give the functional software access to the I/O > Provision of code templates with all necessary interface definitions signals via the RTE. They let the user condition and filter the sig- > Support of “actuator tests” via diagnostics nals. No special extension to the MICROSAR IO code is needed for > Available for AUTOSAR 3 and 4.0 (from Q3/2012) direct access to DIO signals.

Functions AUTOSAR has defined hardware-independent Set/Get and Diag The BSW modules in MICROSAR IO contain the functions defined in operations in the “IO Hardware Abstraction” for setting, reading AUTOSAR 3 and 4.0. In addition the modules of MICROSAR IO out and manipulating physical I/O signals (digital or analog) from include the following important functionalities: your ECU’s periphery. Vector offers them in the MICROSAR IO pack- > Definition of user defined ports for acquiring ECU-specific user age. In addition to functions specified by AUTOSAR, you can use defined signals. MICROSAR IO to create your own signal definitions, making it easy > Processing of user defined signals from the user defined ports. to implement application-specific signal processing. Upon request, DaVinci Configurator Pro can generate code templates, in which users can directly program their extensions. Application Areas > Execution of functions for the DCM actuator test via the standard MICROSAR IO provides a convenient foundation for developing interface. your “IO Hardware Abstraction”. In combination with the suitable drivers for microcontroller peripherals from MICROSAR CAL, you Configuration get a complete I/O stack for the ECU software. It interconnects the For convenient configuration we recommend an upgrade from the functional software to physical IO signals of sensors and actuators, supplied DaVinci Configurator Base to DaVinci Configurator Pro. which makes the application software hardware-independent. DaVinci Configurator Pro checks for plausibility of the configuration parameters for MICROSAR CAL and MICROSAR IO. The following “bottom up” approach is recommended:

MICROSAR IO modules according to AUTOSAR 4.0 V2.4 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Contact and Availability In the framework of our training program we can offer you various For information on the availability of hardware-specific MICROSAR training courses and workshops on MICROSAR at our classrooms or at BSW modules go to: www.microsar.com/availability/ your business site. We would be glad to provide you with information on OEM-specific For more information on individual training events and dates please versions and individual support for your AUTOSAR projects. visit: www.vector-academy.com Find your contact person at: www.vector.com/contact

> Configure the CAL driver Additional Services > Configure MICROSAR IO Vector would be glad to support you in the development of the “IO > Generate the SWC description belonging to MICROSAR IO Hardware Abstraction Layer” of your special ECU in the framework of project work. You benefit from Vector‘s detailed knowledge of Scope of Delivery the AUTOSAR specification and methodology as well as its exten- > Software modules as library with C header files, optionally as sive experience in integration of ECU software. source code > Command line based generator (for Windows XP/ Windows 7) > BSW modules description > DaVinci Configurator Base as basic editor > Documentation

The complete AUTOSAR Solution from Vector The AUTOSAR solution from Vector consists of the DaVinci tools, MICROSAR basic software and MICROSAR RTE. You will find information on properties of BSW modules from the MICROSAR packages as well as detailed descriptions of functional features of the DaVinci Tools in separate datasheets.

Other Relevant MICROSAR Products If I/O signals are accessed via an external device, your I/O Stack will need an additional suitable driver from MICROSAR EXT.

Configuration of the IO module using DaVinci Configurator Base

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR RTE

The optimized Run-time Environment for Software Components per the AUTOSAR Standard

Overview of Advantages or designed by model-based tools can be re-used in multiple ECU > Easy to configure and scalable projects. The RTE only needs to be reconfigured and regenerated > Available for AUTOSAR 3 and 4.0 (from Q3/2012) for the specific ECU and, if applicable, the BSW modules. It is also > In-depth consistency check of the configuration possible to use a SWC in multiple instances on one ECU. > Highly optimized code with intelligent synchronization mechanisms In generating the MICROSAR RTE, the user can choose between two > Quick entry into working with AUTOSAR, e.g. based on gener- modes: > ated code templates for the software components (SWCs) Contract Phase Generation for developing individual SWCs in an > Well-suited for migration projects early phase. In this case, the generator just creates a header file > Simplified testing of the application by XCP access to S/R ports, for each SWC instead of the entire RTE. This makes it possible to InterRunnable variables and Per-Instance memory 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 MICROSAR RTE (Run Time Environment) is the scalable and highly in this mode is highly efficient and requires only little memory optimized AUTOSAR runtime environment from Vector. The RTE is a space. It is optimized for the entire ECU configuration and module introduced by AUTOSAR that manages communication makes few demands on system resources due to short execution between the software components (SWCs). It assures consistency times and minimal interrupt disable times. One way this is of the overall information flow and represents the interface achieved is by using intelligent synchronization mechanisms between the functional software, basic software (BSW) and com- that are tuned to the properties of the hardware used. plex device drivers (CDD). Functions Application Areas MICROSAR RTE is compatible with AUTOSAR 4.0 (ASR 4.0) and 3 (ASR When the functional software of an ECU is implemented by 3). Specifically, MICROSAR RTE contains the following functionality: AUTOSAR-conformant SWCs, the user needs the RTE as a runtime > Sender/Receiver and Client/Server communication environment. This modular layout of the ECU software offers the > Mode management user maximum flexibility: SWCs that have been manually developed > InterRunnable variables as well as Exclusive Areas

MICROSAR RTE module according to AUTOSAR 4.0 V2.2 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

> Trigger for runnables The following functionalities are available as options: > Online and offline calibration of SWCs are supported as well as > External Client/Server communication (Inter-ECU) measurement of S/R ports, InterRunnable variables and Per- > Support of internal, external and background runnable triggers Instance memory using the XCP protocol (for ASR 4.0) > Multiple instancing of SWCs and per-instance memory > Multi-core support (for ASR 4.0) > Schedule Manager/BSW Scheduler (SCHM): Since ASR 4.0, the > Scaling of ports and signals (for ASR 4.0) RTE has assumed the functionality of the SCHM module. This was > Generating NvRAM software components (for ASR 4.0) previously contained in MICROSAR SYS. For more information on > Range checks (for ASR 4.0) the SCHM module, please refer to the “MICROSAR SYS” > SCHM: For applications without an RTE, the SCHM module is datasheet. available as an independent ASR 4.0 compatible module.

Beyond the standard, MICROSAR RTE for ASR 3 includes the fol- Configuration lowing important services: For configuration of the RTE, you will need either DaVinci Configu- > Generation of code templates for SWCs based on the “SWC rator Pro with Option .RTE or DaVinci Developer. For more details, Description“. These templates contain all APIs of the RTE. please refer to separate datasheets. > Use of memory protection mechanisms as specified in the AUTOSAR operating system. This support is especially optimized Scope of Delivery when MICROSAR OS is used. > Command line based generator (for Windows XP/ Windows 7) > Configuration of initialization runnables for the AUTOSAR con- > BSW modules description cept of “Mode-Dependent Runnables” > Documentation and sample programs with makefiles > Generation of an HTML report showing RTE properties. It contains information such as the calculated RTE resource load (RAM Other Relevant MICROSAR Products: + constants). The RTE requires the presence of an operating system such as > Generation of an A2L file for simple linkage to existing calibra- MICROSAR OS or osCAN. tion and diagnostic standards

MICROSAR RTE enables generation of code templates for the SWCs

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR AMD

AUTOSAR monitoring and debugging via CAN, FlexRay or Ethernet

Overview of advantages The functionality of the modules is actually specified in AUTOSAR > Simplified testing of ECUs by acquiring internal ECU data – already 4.0, but it is already available from Vector for the MICROSAR 3.x implemented for AUTOSAR Release 3.x solution. > Easy measurement of start up and go-to-sleep behavior You can use one of the following Vector tools as the XCP Master on > Automatic generation of required A2L file the PC side: > CANape > CANoe.AMD Application areas With these tools and a description of the measurement objects in The MICROSAR AMD package efficiently supports you in testing the form of an A2L file in ASAM format, you can select internal ECU your AUTOSAR ECU software. The basic software modules from data and analyze its flows. CANape was extended for AMD with the MICROSAR AMD have access to all important AUTOSAR-specific “Digital Window” and the “Status” signal display. CANoe.AMD was internal variables, states and error messages. extended with the special “State Tracker” window. This lets you The XCP protocol (Universal Calibration Protocol) – familiar from display discrete states and binary signals in a well-organized the measurement and calibration field – is excellently suited for layout in one window. transferring ECU-internal parameters. Therefore, Vector decided to develop MICROSAR AMD based on XCP. The values read out with Acquiring internal variables from AUTOSAR BSW modules MICROSAR AMD are transferred to a Master over XCP for display and In the case of ECU tests, the engineer can use the DBG BSW module analysis. from MICROSAR AMD to determine which external and internal factors caused a state change of the BSW modules. The DBG mod- Functions ule sends the needed internal variables of the MICROSAR BSW An XCP slave is expanded in the ECU with the basic software mod- modules to the Master via XCP. ules (BSW) from MICROSAR AMD: > DBG (Debugging) Acquiring internal variables from the MICROSAR RTE > DLT (Diagnostic Log and Trace) When using a MICROSAR RTE as a runtime environment in your ECU software, it is possible to monitor the data flow between SWCs over

MICROSAR AMD modules according to AUTOSAR 4.0 V2.0 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Contact and Availability Training You will find information on the availability of hardware-specific In the framework of our training program, we can offer various MICROSAR BSW modules at: www.microsar.com/availability/ training events and workshops for MICROSAR in our classrooms as We can also tell you about OEM-specific versions and custom support well as at your business site. for your AUTOSAR projects. For more information on individual training events and dates, Find your contact person at: www.vector.com/contact please go to: www.vector-academy.com

XCP. After activating the “Measurement Support” option in the RTE Scope of Delivery configuration, the following RTE-internal objects are acquired: > Software modules as source code > Inter-runnable variables > Command line based A2L Generator (for Windows XP/Windows 7) > Sender/receiver ports > BSW Module Description files > Mode ports > Documentation > Per-instance memory This is how you monitor the intra- and inter-ECU communication Other relevant products and measure or stimulate not connected sender/receiver ports. The following Vector software modules are prerequisites for using MICROSAR AMD: Acquiring internal error messages and warnings > XCP Professional driver During runtime, the DLT BSW module from MICROSAR AMD acquires > XCP Option for the MICROSAR Communication Stack (CAN, and transmits, via XCP, all occurring error messages and warnings FlexRay or Ethernet) that the BSW reports to the DET and DEM modules. The VX1000 System from Vector is available for maximum data throughput with minimal effects on the ECU’s execution time. The Generating the A2L file for the XCP Master system forms the interface between the ECU and a measurement Based on the configuration data from the ECU configuration file tool like CANape or CANoe. Data access is performed via the micro- (ECUC), you generate the A2L description file (Master.a2l) for the controller-specific data trace and debug interfaces rather than XCP Master with the DaVinci tools. The A2L file contains the using communication buses. description of the MICROSAR-internal variables. If symbolic names exist for values of measurable objects, they are also stored for later visualization. It is also possible to incorporate other application- specific or 3rd-Party A2L fragments into the Master A2L file. Before starting the measurement, a Map Reader is used to update the Master A2L file with the actual addresses of the variables. The Map Reader is supplied as part of CANape and CANoe.AMD..

Evaluating status changes with the State Tracker Window in CANoe.AMD

Generation of an A2L file for the XCP-Master

More Information: www.vector.com/contact EMBEDDED SOFTWARE

MICROSAR Safe

Safety according to ISO 26262 up to ASIL D for ECUs with AUTOSAR software

Overview of advantages SafeExecution: > > Solution for all Automotive Safety Integrity Levels (ASIL) through Runtime monitoring of tasks > ASIL D Flow control of safety-relevant SWCs > > Reducing qualification costs Memory protection and safe context switching > Support of different ASILs on one controller SafeCom: > Safe intra-ECU and inter-ECU communication Application areas For using MICROSAR basic software in ECUs with safety-relevant SafeSelfTest: functions, you will receive MICROSAR Safe from Vector. This solution > Periodic hardware checking is the result of collaborative work with TTTech, our partner with many years of experience in the field of functional safety. It lets you The use of Runtime Monitoring, Flow Control, Memory Protection develop AUTOSAR-based applications using software components and Safe Context Switching makes it possible to let safety-relevant (SWCs) for ECUs up to ASIL D per ISO 26262. and non-safety relevant SWCs run next to one another on the same The modules from MICROSAR Safe are SEooCs (Safety Elements out ECU without interference. This means that software parts whose of Context), which are developed according to ISO 26262 / ASIL D. correct execution cannot be verified cannot disturb safety-relevant Their use helps you to drastically reduce effort for qualifying your functions unnoticed. safety-relevant functions. Runtime Monitoring Functions Runtime monitoring assures that tasks have sufficient computing The SafeCom, SafeExecution and SafeSelfTest bundles from time for their execution. Runtime monitoring is provided by MICROSAR Safe were implemented according to the AUTOSAR MICROSAR OS SC2/SC4 and is validated to ISO 26262 by the mod- specification, are compatible with the remaining MICROSAR modules WDGM, WDGIF and WDGDRV from SafeExecution. ules and contain the following specific functionalities:

MICROSAR Safe V2.3 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

The complete AUTOSAR solution from Vector Contact and Availability The AUTOSAR solution from Vector consists of the DaVinci tools, You will find information on the availability of hardware-specific MICROSAR basic software and MICROSAR RTE. MICROSAR BSW modules at: www.microsar.com/availability/ You will find information on the properties of the BSW modules and a We would be glad to provide you with information on OEM-specific variants detailed description of the functional features of the individual as well as individual support for your AUTOSAR projects. DaVinci Tools in individual datasheets. Find your contact person at: www.vector.com/contact

Program Flow Monitoring Hardware checking Correct execution of safety-relevant SWCs is assured by the mod- You can perform cyclic tests for error-free functionality of the ules WDGM, WDGIF and WDGDRV. This involves using what are ECU’s various hardware components during operation using referred to as checkpoints in the software components. generic test functions of the SafeSelfTest package. The precise scope of monitoring that is necessary is project-specific. We would Memory Protection and Safe Context Switching be glad to consult with you in selecting specific monitoring mech- The MICROSAR operating system’s option SafeContext, which was anisms for your project. developed to ASIL D, assures memory protection for ECUs with safety-relevant applications on suitable microprocessors (e.g. with RTE for safety-relevant functions MPU, the Memory Protection Unit). The option SafeContext is The MICROSAR RTE supports partitioning of memory areas via the available for MICROSAR OS (SC3/SC4) and it is used to separate the operating system option SafeContext. This enables a “Decomposi- various software components from one another during task tion” in the sense of ISO 26262. changes and interrupts. SafeContext prevents unauthorized writing by one software component to the memory of another software Configuration component that could corrupt the data. The safety elements of MICROSAR Safe are configured with the DaVinci tools. Safe Intra-ECU and Inter-ECU communication Data that is exchanged between safety-relevant applications must Product components be checked for correct transmission. A checksum protects the data > Software modules as library with C header files, optionally as contents and the correct sequence of data is monitored by a mes- source code sage counter. If one of these checks fails, the application is > Instruction line based generator (for Windows XP/ Windows 7) informed, and it can react accordingly. This detects errors such as > BSW module description files masquerading, failure or reversed data. > Description files for DaVinci Configurator Pro > Documentation with Safety Manual

Implementation SafeExecution: Safety-relevant functions are implemented by the Safety Elements out > SafeContext: Memory Protection and Safe Context Switching (option of Context (SEooC) from MICROSAR Safe. They detect and handle for MICROSAR OS) potential errors in non-safety software layers. The SEooCs conform to > WDGM: Watchdog Manager ISO 26262 ASIL D and are developed according to the AUTOSAR > WDGIF: Watchdog Interface specification. > WDGDRV: Driver for internal watchdog devices > WDGEXT: Driver for external watchdog devices MICROSAR Safe contains the following SEooCs: SafeSelfTest: SafeCom: > RAMTST: Tests for RAM memory > E2ELIB: End-to-end library > FLASHTST: Tests for flash memory > Protection Wrapper: End-to-end protection Wrapper > CORETST: Tests for the microcontroller core > IOTST: Tests for inputs and outputs

More Information: www.vector.com/contact EMBEDDED SOFTWARE PRODUCT LINE

Identity Manager for AUTOSAR

Solution for Multiple ECUs

Overview of Advantages Identity > Efficient handling of ECU variants An ECU is identified by its Identity. The Identity establishes which > Less administration effort variant of the ECU should be activated (e.g. which door side). So, an > Reduced inventory costs Identity is really the configuration of an ECU that is active at runtime and is based on a description file. The Identity is set when the ECU is In the automobile, there is an increase in the number of ECUs that initialized. can be installed in different variants; they are known as multiple ECUs. Your advantage is the use of a single hardware for the differ- Via the so-called Identity (see box), each ECU knows during start- ent application areas. This reduces hardware costs and effort in up which one it is and where it is installed, and therefore also inventory management. On the other hand, it results in increased which functions it needs to fulfill. The buffer for the Rx and Tx effort in software development and the management of software PDUs can be completly overlaid if their layout is identical. The variants for production and service areas. application accesses signals and data elements independent of its Based on its many years of cooperation with automotive OEMs and identity. No differentiation is necessary in the code. suppliers, Vector is familiar with typical applications for ECU variants and can provide practice-oriented solutions for multiple ECUs Multiple Configuration based on AUTOSAR. With the multiple configuration, it is possible to use an ECU in different car lines, and therefore in completely different communi- Physical Multiple ECU cation networks. A typical application here would be for what are One speaks of Physical Multiple ECUs, when multiple ECUs in a known as carry-over ECUs. These ECUs contain the software for all vehicle perform nearly identical functions at different locations. of the car lines in which they are used. In this case, the ECU Door ECUs are a typical example of this. The individual ECUs only Extracts upon which the configuration of the AUTOSAR ECU soft- differ in their Rx and Tx PDUs or in their diagnostics and address in ware is based may differ very significantly for the different vari- the network. In this case, a single ECU is developed and produced. ants, they may exhibit a completely different signal layout or support a different number of buses. Here too, the identity of the ECU is determined when it is started.

Physical Multiple ECU and multiple configuration V2.3 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE PRODUCT LINE

The complete AUTOSAR Solution from Vector Contact and Availability The AUTOSAR solution from Vector consists of the DaVinci tools, You will find information on the availability of hardware-specific MICROSAR Basic Software and the MICROSAR RTE. MICROSAR BSW modules at: www.microsar.com/availability/ You will find information on properties of BSW modules from the We can also tell you about OEM-specific versions and custom support MICROSAR packages and detailed descriptions of functional features for your AUTOSAR projects. of individual DaVinci Tools in the relevant datasheets. Find your contact person at: www.vector.com/contact

For both solutions, PDUs may be overlaid if only a few signals are The user configures the optimal superset of all diagnostic services identical in the PDUs. The RTE implements this by the so-called as usual in GENy/DaVinci Configurator Pro*. fan-in or fan-out mechanism. Saving Resources Since Physical Multiple ECUs are identical in much of their content, Integrating both Solutions in the AUTOSAR Concept for optimization no separate set of configuration parameters is According to AUTOSAR, an ECU is described by an ECU Extract of created for some BSW modules but only a common set is created System Description. To describe two or more ECU variants, two or for all instances. This applies to such elements as identical mes- more ECU Extracts are needed. For the RTE, these files are merged sages, diagnostic services, etc. into one file with DaVinci Developer/DaVinci Configurator Pro*. In multiple configurations, ECU resource savings are realized. Afterwards you generate a higher-order ECU Configuration Although the ECU must be large enough to offer space for both Description (ECUC) for the basic software. Both files contain a applications, only one hardware component is needed. superset of the relevant ECU-specific information. Scope of Delivery Proven Configuration Process The scope of delivery of the Identity Manager includes: The configuration tools DaVinci Developer and GENy/DaVinci > License for enabling in the configuration tool Configurator Pro* read in the merged files (ECU Extract and ECUC). > BSW modules with Identity Manager functionality In these two tools, the user finds a superset of the ECU interfaces to be implemented and configures the multiple ECU like a normal *Regarding availability, please contact Vector. ECU. The Project Assistant that is contained in the tools supports the user here.

Diagnostics To describe the diagnostics of an ECU, one diagnostic description file (CDD) is needed per ECU. Exactly as in communication, identical diagnostic services are overlaid, and so they exist just once.

Configuration process of multiple ECUs

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Wide Availability of MICROSAR

Supported Microcontrollers and Compilers for the hardware-specific AUTOSAR BSW Modules

Controller Compiler MICROSAR OS MICROSAR CAL [2, 3] [1] CAN FlexRay LIN IP/Ethernet Further MCAL Driver Altera NIOS II GNU, Tasking X

ARM Cortex M ARM X

Atmel AT91 GNU X AVR32 IAR X X X

Freescale i.MX25, i.MX35 GNU X MAC7100 ARM, IAR X X S12X Cosmic, Metrowerks X X X X X MPC55xx Green Hills, X X X X [4] X Metrowerks, Wind River MPC56xx Green Hills, X X X X X X (QORIVVA/ Metrowerks, Wind 5xxx/Automotive) River Fujitsu 16FX Fujitsu X X FCR4 Green Hills X X X FR60 Fujitsu X X X FR81 Fujitsu X X X MB86 GNU, Green Hills X X MB9E/DF126 Green Hills X (Cortex-R4) Infineon TriCore GNU, Green Hills, X X X X X Tasking XC2000 Tasking VX X X X X Microchip PIC24 Microchip X dsPIC33E, dsPic33F Microchip X X NXP LPC17xx Keil/ARM X X X V2.5 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Availability and Contact The MICROSAR software modules are hardware independent to a large extent. Only the modules listed in the table below must be tailored for each hardware platform. Please send a request to Vector for the combination of derivative and compiler you require. Please collect this information as early as possible, so that Vector can supply your software for the project start. Find your contact person at: www.vector.com/contact

Controller Compiler MICROSAR OS MICROSAR CAL [2, 3] [1] CAN FlexRay LIN IP/Ethernet Further MCAL Driver Renesas Electronics (NEC/Renesas) 78K0R IAR X X V85x Green Hills, IAR, X X X X X X Renesas M16C Renesas X M32C Renesas, IAR X X M32R Renesas X X R32C Renesas, IAR X X X X R8C IAR X SH2 Renesas, Green Hills X X X X SH4 Renesas X STMicroelectronics SPC56xx Green Hills, X X X X X X Metrowerks, Wind River STR9 GNU X Texas Instruments TMS320 Texas Instruments X TMS470 Texas Instruments X X TMS570 Texas Instruments X X X X X Vector CANoe osCAN Microsoft VisualC X X X X X X Emulation

[1] = As alternative to MICROSAR OS you can use an osCAN operating system in AUTOSAR systems. [2] = Some of the MCAL drivers are created by hardware manufacturers and correspond partly to AUTOSAR release 2.1, 3.0, 3.1 or 4.0. [3] = On request Vector can develop further MCAL drivers or merge the configuration of your MCAL drivers into the configuration tool DaVinci Configurator Pro. [4] = Currently in development

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 2/44

DaVinci Developer

Designing AUTOSAR Software Components and Configuring the MICROSAR RTE

Functions Overview of advantages DaVinci Developer offers extensive functions for defining and > Convenient graphical definition of software components integrating AUTOSAR SWCs: > Clear representation of complex systems > Graphical definition of SWCs with extensive layout functions > Special functions simplify data exchange between OEM and > Definition of port interfaces and data types ECU developer 2/44 > Definition of port prototypes with service needs and communi- > Easy connection to configuration management tools cation specification, e.g. initial values and timeouts > Consistent configuration of the MICROSAR RTE > Definition of runnable entities with activation events and port access DaVinci Developer is the professional tool for designing AUTOSAR > Support for all types of AUTOSAR SWCs and application compo- software components (SWCs) and for configuring the MICROSAR nents, compositions, calibration and service components RTE. Convenient graphical editors let you design the structure and > Import and export of AUTOSAR XML formats (System Descrip- interfaces of the functional software for your ECU quickly and tion Template, Software Component Template) clearly, and they facilitate smooth integration of the functional > Support for various AUTOSAR XML versions in parallel. software with the ECU‘s basic software. > Signal import from commonly used network description formats (DBC, FIBEX, LDF) Application Areas > Data mapping of port data to network signals DaVinci Developer supports ECU developers in developing > Consistency check of the SWC definition and the RTE AUTOSAR-conformant ECUs. You can use DaVinci Developer as an configuration architecture tool to define application software architectures. > Interface to model-based development tools via AUTOSAR-SWC DaVinci Developer is also well-suited as an integration tool you description files can use to consistently integrate existing AUTOSAR SWCs in an ECU. This means that DaVinci Developer is a flexible tool that can be used in different OEM projects. Finally, DaVinci Developer lets you consistently configure the MICROSAR RTE based on previously defined AUTOSAR SWCs.

DaVinci Developer – Design tool for AUTOSAR-conformant ECUs Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 2/45

AUTOSAR

The complete AUTOSAR solution from Vector Training Events Vector‘s DaVinci and MICROSAR products offer a fully tuned In the framework of our training program, we offer various solution for developing AUTOSAR ECUs. AUTOSAR training courses and workshops at our classrooms, Separate datasheets describe general properties of the BSW as online Webinars or at your company site. modules from the MICROSAR packets and detailed functional For more information on individual training events and the features of the individual DaVinci Tools. schedule on the Internet go to: www.vector-academy.com

Workflows and AUTOSAR Methods DaVinci Developer works seamlessly with DaVinci Configurator Pro DaVinci Developer can be flexibly used in a distributed develop- to create a consistent overall configuration. For example, the ment process based on the AUTOSAR method. For this purpose, service components and IO hardware abstraction components the tool offers extensive functionality for data exchange between generated by DaVinci Configurator Pro can be conveniently OEM and ECU developer: imported and linked to the application SWCs. DaVinci Developer > Import/Update function to support an iterative development offers special support by automatically creating suitable service 2/45 process port prototypes and server runnables for the application SWCs. > Diff and Merge functions with configurable presettings for indi- Finally, the RTE configuration is saved AUTOSAR-conformantly in vidual objects. This makes it possible to extend OEM-generated an ECU configuration file. SWCs by adding port prototypes and runnable entities. > Library concept for reusing components or interfaces in Scope of Delivery multiple ECU projects > DaVinci Developer > Connection to configuration management systems with fine- > Utility tools for automating work steps granulation versioning of individual objects, e.g. SWCs > Demo data > Documentation Configuration of the MICROSAR RTE DaVinci Developer is used to configure the MICROSAR RTE; it sup- System Requirements ports work steps such as: Component Recommended Minimum > Assigning runnable entities to operating system tasks. This Processor Pentium 4/2.6 GHz Pentium III/1 GHz work is simplified by special views on the runnable entities, Memory (RAM) 2 GB 1 GB such as the trigger-oriented or component-oriented view. Screen resolution 1280 x 1024 1024 x 768 > Configuring optimization options > Consistency checking of the RTE configuration with detailed Operating system Windows XP SP2 or SP3 Windows 7 (32- or 64-Bit) error reports and tips on correcting inconsistencies ◆

Special functions > Configuration of multipurpose ECUs > Project assistant for conveniently creating and updating ECU projects > User-specific extension of the data model by generic attributes TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS

DaVinci Component Tester

Testing AUTOSAR Application Software on the PC

Overview of advantages DaVinci Component Tester is a universal run-time platform for > User-friendly testing of AUTOSAR software components (SWC) on a testing SWCs in all development phases of ECU applications. PC > Wide variety of use cases; from tests supporting the ECU developer Application Areas to acceptance tests at the automotive OEM DaVinci Component Tester supports the following application > Suitable for all application SWCs, e.g. state machines or control areas: > systems Rapid Prototyping > Testing of SWCs developed manually or by model-based methods While developing ECU applications, you can use the DaVinci > Unlimited support of all SWC interfaces per AUTOSAR Release 3.0 Component Tester as a convenient run-time platform for SWCs. and 3.1 By integrating DaVinci Component Tester in the development > Quick setup of tests without time-consuming configuration environment, you can execute and debug the SWCs right on your > Simplified test cases by emulating AUTOSAR Standard Services development PC. Also, in conjunction with a development and > Interfaces to standard test tools: CANoe from Vector and NUnit test tool such as CANoe you can control the SWCs interactively, > Interfaces to development environments such as Microsoft e.g. via user interfaces, and analyze their behavior. > Developer Studio or Eclipse via open interfaces Unit Test of software components Use DaVinci Component Tester for testing the functionality and AUTOSAR-conformity of your SWCs. Together with a unit test tool Thanks to AUTOSAR, an ECU’s application software can be devel- such as NUnit, this will increase the quality of your SWCs by oped as hardware-independent software components (SWCs) testing during development. An example is automated regres- based on a Virtual Functional Bus (VFB). DaVinci Component Tester sion tests. is a high-performance VFB emulator that enables execution and > Integration tests of software components testing of such SWCs on a PC. It is very easy to configure the DaVinci Component Tester supports integrating complex systems DaVinci Component Tester, by using just the SWC description file consisting of multiple SWCs. When used together with a test tool without modification of the SWCs. The original source code is like CANoe, this lets you verify system functionality early on. executed directly.

Testing atomic AUTOSAR software components with Testing a composition of multiple software components with DaVinci Component Tester DaVinci Component Tester V2.4 2011-07

More Information: www.vector.com/contact TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS

Functions Operating Modes The core of DaVinci Component Tester is an emulator that executes DaVinci Component Tester offers two operating modes, which the SWCs on a PC. This does not require an AUTOSAR RTE (Runtime depend on its intended use. They affect execution of the SWC’s Environment) or basic software. The finely tuned emulator simu- runnable entities: lates the AUTOSAR-ECU environment for the SWC under test with > Programmed execution mode realistic behavior. The emulation covers full RTE functionality and You can implement execution of the runnable entities in an lets you test any AUTOSAR Release 3.0 and 3.1 SWCs using explicit test case. This execution mode is used in unit tests with functions such as: focus on detailed inspection of the implementation. > Setting data elements of receiver ports > Automatic execution mode > Reading data elements from sender ports DaVinci Component Tester executes the runnable entities inde- > Calling up server ports pendently according to the trigger specification, e.g. periodi- > Controlling mode ports cally every 10 ms. Therefore DaVinci Component Tester synchro- > Setting calibration data nizes itself to the time base of your test tool. This execution > Executing runnables with non-blocking API calls (Category I) mode is used for integration testing of complex SWCs or in > Executing runnables with blocking API accesses (Category II) experimental startup of a SWC during development (Rapid > Handling internal communication between multiple SWCs Prototyping). > Simulating errors such as timeout or empty queue All you need to configure the test setup or experiments is the SWC description (AUTOSAR XML file). Based on the SWC Description, DaVinci Component Tester provides a structured API that can be used by an external tool to access the SWC. The external test tool handles control of the test, e.g. by programming test cases, and evaluation of the test.

More Information: www.vector.com/contact TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS

> Special functions EcuM (ECU Manager) > > Instruction line support for automated tests DEM (Diagnostic Event Manager) > > Checking API consistency of the SWC Description and SWC FiM (Function Inhibition Manager) > implementation file NvM (Non-Volatile Memory Manager) > > Programming callbacks in the test environment for specific reaction ComM (Communication Manager) > to an API call of the SWC under test WdgM (Watchdog Manager) > Generating the header file of SWCs (Contract Phase Generator) for compiling the SWC implementation with the Microsoft Compiler Interface to CANoe You can use DaVinci Component Tester in combination with CANoe to execute integration tests of SWCs. While CANoe controls the test Service Emulator flow, DaVinci Component Tester automatically handles execution DaVinci Component Tester contains an emulator for the standard of the runnable entities. Therefore DaVinci Component Tester services of an AUTOSAR ECU. This emulator simulates the behavior synchronizes itself to the simulation time of CANoe. of the services in an abstracted form. You describe the test environment in CANoe, e.g. with the help of When a test or experiment is set up, the SWC’s service ports are the Test Feature Set. All other CANoe functions are available as automatically connected to the service emulator. There is no need well; such as panels, analysis windows and integration of MATLAB to explicitly consider the service ports in the test environment, models for an environment simulation. allowing you to focus entirely on the SWC’s application ports. This reduces the complexity of the test environments considerably. The service emulator may be accessed at any time. For example, you can preset a block with a certain value that is read out by the SWC from nonvolatile memory, or you can check the value changed by the SWC. Similarly, users can control or monitor the current state of the ECU Manager from a test case. The service emulator supports AUTOSAR standard services of the following basic software modules:

Functional principle: Interfacing DaVinci Component Tester to CANoe

More Information: www.vector.com/contact TOOLS FOR NETWORKS AND DISTRIBUTED SYSTEMS

Interface to NUnit mentation compiled by the Microsoft Compiler and the SWC You can execute unit tests of SWCs in conjunction with the open Description (AUTOSAR XML). source tool NUnit. This is done by implementing the test cases in > Contract Phase Generator: any desired .NET language such as C#. The test cases typically show Instruction line tool for generating the SWC’s header file the following pattern: Set input vector, execute runnables, read > Emulator (including Service Emulator): output vector and check it. NUnit handles test execution and .NET DLL for executing SUT executables reporting. > NUnit Adapter: Microsoft Visual Studio is used to program the test cases. In Interfaces the emulator to NUnit. Interfacing is via a .NET implementing the test cases, you are supported by programming Assembly with a structured API for access to the SWC. assistance integrated in the development environment (Intelli- > CANoe Adapter: Sense). For example, a user could easily program access to a Interfaces the emulator to CANoe. Interfacing is via a .NET Node, receiver port by listing all of the SWC’s receiver ports and selecting which you integrate in your CANoe configuration. The SWC’s the desired port from the list. input and output data elements are mapped via CANoe system variables. > Integration in your test environment Sample projects > Due to its open interfaces, DaVinci Component Tester can be inte- Manual as PDF document grated in your development environment or test tool chain, making it AUTOSAR-capable. Vector offers support in integration of DaVinci System Requirements > Component Tester. MS Visual Studio 2005 or 2008 (Express, Standard or Profes- sional Edition). The Professional Edition is required for debugging in combination with NUnit. Scope of Delivery > Windows XP or Windows 7 (32- or 64-Bit) DaVinci Component Tester consists of the following components: > CANoe 7.1 or higher > SUT Executable Generator: > Alternative: NUnit 2.4.7 or higher (available at: Instruction line tool for preparing the SCW under test as an http://www.nunit.org) executable system under test (SUT). Inputs are the SCW imple-

Functional principle: Interfacing DaVinci Component Tester to NUnit

More Information: www.vector.com/contact EMBEDDED SOFTWARE

DaVinci Configurator Pro

Configuration of AUTOSAR Basic Software

Overview of advantages Application Areas > Convenient configuration of MICROSAR basic software DaVinci Configurator Pro supports the ECU developer in configur- > Easy integration of your own basic software ing, validating and generating the BSW modules from Vector > Workflow support for typical OEM and TIER1 project situations (MICROSAR), third-party producers (e.g. MCALs from semiconduc- tor manufacturers) as well as BSW modules developed in-house at your company. DaVinci Configurator Pro is the tool of choice for AUTOSAR-conformant configuration of ECU basic software (BSW). It is ideal for Functions configuring the MICROSAR BSW modules and the MICROSAR RTE as DaVinci Configurator Pro simplifies the development of AUTOSAR well as your own BSW. ECUs by providing the following core functions: > Creating configuration files Properties and Advantages > Validating the configuration DaVinci Configurator Pro was designed as an open tool for config- > Calling BSW code generators uring and generating BSW modules, and it is additionally charac- terized by the following features: Configuring basic software and the RTE > Convenient user interfaces for all domains of the basic software DaVinci Configurator Pro offers convenient user interfaces for all > Supports all available AUTOSAR releases (3.x and 4.0 (from Q3 individual areas of the basic software, from communication to 2012)), even mixed within the same project memory services to the runtime environment. For each area, rele- > Project-oriented work method by simple activation/deactivation vant editors display configuration parameters in an optimized of individual BSW modules layout. The parameters are grouped according to their function, – > Supports commonly used network description formats (DBC, even across module boundaries. Some editors also contain graphic FIBEX, LDF) and the AUTOSAR “ECU Extract of System Descrip- views, e.g. to represent the relationship of communication data tion” (PDUs) in the ECU or to show the overhead analysis of the memory > Project Assistant makes it easy to create and update ECU projects blocks. > Seamless interaction with DaVinci Developer and other develop- The comfort editors of DaVinci Configurator Pro also simplify the ment tools for software components (SWCs) process of maintaining consistency conditions: if there is a depen-

Configuration of BSW modules with V2.5 2012-02 DaVinci Configurator Pro

More Information: www.vector.com/contact EMBEDDED SOFTWARE

dency between parameters, the parameter values are automatically Validation adjusted whenever a change is made. The consistency of configuration parameters is assured by an Special assistants are included for complex configuration tasks, extensive set of module-specific and cross-module validation e.g. for automatically linking SWCs (see Option .RTE). rules. If a configuration is faulty, DaVinci Configurator Pro displays validation error messages clearly and offers you recommendations Along with “convenience” editors, DaVinci Configuration Pro also for a solution. contains basic editors that offer a view of the configuration para- Validation is automatically executed before code generation. In meters based on their module definition file (BSWMD). This is a addition, live validation of your inputs is performed. This lets you generic view that follows the AUTOSAR concept of the Generic detect a faulty configuration early on, so that you can quickly Configuration Editor (GCE). While an ECU configuration is being correct it. created, you can switch between the comfort view and the basic view at any time. Generation DaVinci Configurator Pro serves as a central tool for calling the In both types of editors, you can make use of general functions BSW module generators. Besides generators for the MICROSAR such as: modules, you can also configure any other generation steps. For > Show a parameter’s definition example, you might do this to integrate external code generators > Show help texts for a specific parameter for your own BSW modules. You can configure such a generation > Search function and bookmarks* step by defining the command line call of the external code generator. As an option, DaVinci Configurator Pro performs a Integrating your own basic software schema conversion of the configuration file or any transformation DaVinci Configurator Pro is very well suited as a central configura- you might wish to define. This also lets you integrate code gener- tion tool for the entire ECU. You can jointly configure the ators that require a specific AUTOSAR format, for example, or MICROSAR modules and your own BSWs by adding their BSWMD whose parameters deviate from the AUTOSAR standard. files to the project. After that, you can configure your modules with a basic editor, which is ideally integrated in the user interface of DaVinci Configurator Pro.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Workflows and AUTOSAR methods Technology DaVinci Configurator Pro lets users configure the basic software in DaVinci Configurator Pro was developed based on the Eclipse plat- a process-assured way that is tuned to typical project situations in form, and it utilizes state-of-the-art methods for efficiently pro- the interactions of OEM and TIER1: cessing large amounts of data. > Automatic derivation of parameter values from the system description Variants and options > Blocking of changes to derived or preconfigured parameters The following tool versions are available: > Automatic update after changes to the system description > DaVinci Configurator Pro > Controlled overwriting of single derived parameters, e.g. to Full version with all functions for BSW configuration of AUTOSAR correct errors in the system description ECUs (except RTE) > Easy setup of a project with the integrated DaVinci Project Assis- > DaVinci Configurator Base tant and a Startup Guide automatically adapted to the project Base version with reduced set of functional features. Contains > Automation interface for remote controlled generation of base editors for creating module configurations. configurations and for calling tool functions > Creating reports of the ECU configuration* The following options are available for DaVinci Configurator Pro: > Option .RTE: Enables configuration of the MICROSAR RTE. The Multi-user support option contains specific editors for integrating SWCs. You can DaVinci Configurator Pro simplifies teamwork on the same ECU add SWCs to the project and link them to other SWCs or the net- project. Parallel editing of the configuration is simplified by spe- work signals. It also contains special assistants, e.g. to auto- cific functions: matically link SWCs or to simplify task assignments of SWCs. > Fine-grained storage of the ECU configuration files (ECU Split If you have a DaVinci Developer license, this option is already Files) included. > Prevention of changes to write-protected module configurations > Option .WF* (Workflow): Enables customization of the pro- > Import of module configurations from other projects* cessing of input data, e.g. system descriptions. In addition, this > Integrated Diff/Merge function (see Option .WF)* option enables project-specific preconfiguration of modules, > Separate Diff tool for comparing any AUTOSAR files e.g. to automatically consider your company standards. Also included is the integrated Diff/Merge function, with which you

DaVinci Configurator Pro makes it easy for you to configure, validate and generate AUTOSAR BSW modules.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Contact Vector supports you in your projects with standard software and customized services, such as hotline, special workshops and training events on embedded software and AUTOSAR. For more information, go to: www.microsar.com or contact Vector. Find your local contact person: www.vector.com/contact

can show differences between ECU configurations directly in the convenience and basic editors. Merging of ECU configurations is also possible here, and it is automatically controlled by analysis of a common previous version of the ECU configuration (3-way merge). > Option .MD* (Module Development): Contains the Eparm tool that makes it easy to create BSWMD files with module, container and parameter definitions and is used to create pre-configurations.

System requirements Component Recommended Minimum Processor Pentium 4/2.6 GHz Pentium III/1 GHz Memory (RAM) 2 GB 1 GB Screen resolution 1280 × 1024 1024 × 768 Operating system Windows XP SP2 or SP3 Windows 7 (32 or 64 bit)

Additional services > Creation of project-specific workflows > Development of specific configuration interfaces and validation rules for your own basic software > Hotline, special workshops and training events on the topic of embedded software and AUTOSAR

* Please contact Vector regarding availability.

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 2/54

AUTOSAR Services

Proficient support for your AUTOSAR projects

First, we work together with you to setup the MICROSAR basic Overview of advantages software (BSW) and RTE on your ECU hardware using the related > Builds up knowledge efficiently and effectively configuration tools. For this purpose we use a sample application. > Tailored support This quickly gives you a runnable system, letting you focus on > Quick implementation of your application your application. This support is typically performed at your busi- 2/54 ness site. With our AUTOSAR Software Engineering Services, we support you in every phase of your ECU development. Starting with our ex- Afterwards, hotline support is available to you by telephone or tensive AUTOSAR experience and your aspired project goals, we email, which ensures continuous support in case you have ques- jointly carry out a customized action package for you, in which tions about how to use our products. you realize sustained benefits from our AUTOSAR competence. MICROSAR Reviews AUTOSAR Training You have been using our AUTOSAR Embedded Software for a lon- Vector AUTOSAR training courses provide you with an ideal entry ger period of time, and you are approaching an important project into ECU development with AUTOSAR. Intensive exercises ensure its milestone. relevance to practice. For the list of Vector in-house training courses Based on prepared checklists, we conduct an integration and con- on the Internet, go to: www.vector.com/AUTOSAR-Training. We figuration review related to the concrete useage of the MICROSAR would also be glad to conduct these training courses at your busi- stack. In this process, we evaluate the completeness, correctness ness site. It is possible to adapt the training content to your indi- and consistency of the selected settings and the required integra- vidual needs. tion code. In particular, OEM-specific aspects are also considered, such as provided software components. MICROSAR Installation and Support You have already gained familiarity with the topic of AUTOSAR and are now using the AUTOSAR Embedded Software (MICROSAR) from Vector in a specific project. Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 2/55

AUTOSAR

For more information On our “AUTOSAR Services” please contact us. Please find your contact person at: www.vector.com/contact

MICROSAR Coaching AUTOSAR Consulting In MICROSAR Coaching, installation of the MICROSAR software is In the framework of AUTOSAR consulting, together with you we performed with your concrete application, which takes your spe- can work out individual, technical solutions to various technical cific requirements into consideration. We focus on addressing questions related to AUTOSAR: your individual needs here. For example, we can support you in: > Definition of an AUTOSAR-conformant software architecture > Initializing the hardware, including CPU clock and PLL > Optimal use of the AUTOSAR tool chain 2/55 > Integrating the MICROSAR components in the project structure > Migration of existing software to the AUTOSAR architecture > Individual configuration of the operating system > Conceptualization of gateway functions > Starting and stopping the bus communication depending on > Structuring of MATLAB/Simulink models to be linked as soft- the network state ware components via the RTE > Providing the necessary I/O signal interfaces, including signal > Interfacing external peripheral components processing via the RTE > Hardware-dependent Sleep and Wakeup concepts under > ECU and mode management in power up and shut down consideration of individual quiescent current requirements > Integration of diagnostics, error memory and memory > Consideration of requirements related to Functional Safety management in your ECU software (ISO DIS 26262) > Linking of the applications to watchdog management > Integration of further standard software from the OEM We typically perform these consulting activities as customized workshops. This ensures that the worked-out solutions optimally The included Premium Support contains on-site support in addi- fit into your ECU project. tion to the telephone and email Hotline. Based on the specific objectives that were agreed on, we ensure individual support of Software Development your project. Moreover, we would also be glad to handle the entire development of your ECU software. For more detailed information on our engineering services, please refer to the “Software Engineering Services” datasheet. ◆ EMBEDDED SOFTWARE

Solutions with CANbedded

The software implemented in automotive ECUs can be either infra- CANopen structure software or application software. The latter implements For CANopen communication, Vector offers source code for master the desired functionality, while the infrastructure software and slave ECUs. The source code contains all functions and services includes the operating system, communication software and fun- required for the CANopen protocol, which are standardized by CiA. damental input and output services. Detailed information on this can be found beginning on page 3/22.

The use of uniform communication protocols is absolutely neces- Uniform solution sary when setting up networks in a vehicle. The use of standardized Network communication is described in a database. It is used to software components ensures easy portability and reliable inte- configure the software components and serves as a foundation for gration of ECUs in the vehicle’s network for the automotive OEM Vector development and test tools. This gives software developers and its suppliers. In addition, the software components lead to a a universal and uniform solution, from simulation and design to substantial reduction in development costs. testing and validation. Further information on tools for development and testing of auto- CANbedded motive networks can be found in the combined product catalog Vector develops high-quality and innovative software components “Development of distributed systems” and “ECU testing”. for use in the automotive industry. One focus of the product line is on ECU communication, an area in which Vector has well-founded Communication Software for AUTOSAR Systems knowledge. The necessary hardware drivers are also important Vector also provides AUTOSAR-based communications software. here. This software is available for the CAN, LIN, FlexRay, MOST and CANbedded products from Vector are available for systems without Ethernet/IP bus systems. Further information and a description of AUTOSAR. You can obtain them for the CAN and LIN networks as the available software modules can be found in the AUTOSAR well as for the J1939 protocol. In addition, Vector can offer section beginning on page 2/0. individual solutions for further simplification of the application, e.g. solutions for gateways or state management.

Advantages of CANbedded > Many years of experience: Vector has been developing basic software for CAN communication in automotive applications since 1992. > High level of maturity: It would be hard to find a vehicle with a CAN bus today that did not have a CANbedded stack. > Broad range of applications: Applicable for various use cases - from powertrain via body bus to infotainment > Support of many automotive manufacturers: Available in many OEM-specific variants.

Your partner right from the start Vector offers comprehensive support, from the start of a project to its successful completion. Training sessions and courses provide basic information and in-depth knowledge on working with the software – conducted in Vector’s classrooms or right at your company. Vector can assist you through the ECU development process with on-site startups, code reviews, project-specific services and other development-supporting software tools. V2.3 2012-01 V2.3 2012-01

More Information: www.vector.com/contact EMBEDDED SOFTWARE

CANbedded

Basic software for CAN communication

Vector CANbedded basic software lets ECUs exchange information Application Areas over the CAN bus. As a part of the ECU software, it handles commu- CANbedded lets users focus their efforts completely on their func- nication-related tasks as specified by the OEM. With CANbedded, tional software, because the CANbedded stack handles OEM-con- your ECU is able to efficiently communicate with other ECUs in the formant sending and receiving of messages over CAN. Vector offers vehicle and with an external service tester. CANbedded is available OEM-specific CANbedded variants for most OEMs. The CAN driver in variants for most OEMs and for a large number of microcontrol- (the only hardware-specific component) is available in an opti- lers. mized version for many different hardware platforms (8 to 64 bit controllers). CANbedded consists of the configurable software components CAN driver, Interaction Layer, Network Management, Transport Proto- The use of CANbedded in all of a networks ECUs assures compatibil- col and Communication Control Layer, which you can combine as ity of all communication stacks. This reduces development costs necessary to form a communication stack. This provides you with a and test effort. reliable foundation for your ECU. A single-channel variant of CANbedded has been optimized for use Overview of Advantages: in ECUs connected to a single CAN bus. A multichannel variant is > Reliable and tested through many years of development also available for communication over multiple CAN channels. > Generated source code that is scalable and application-specific > Low memory requirement and fast runtimes You can extend the CANbedded stack with additional basic soft- > Supports over 80 different hardware platforms ware from Vector for your specific application: > > Available in platform-specific and OEM-specific variants CANbedded Gateway > > Clearly defined and uniform interfaces Diagnostics: CANdesc > > Easy to port to other platforms and OEMs Commercial vehicles: CANbedded J1939 > > Easy to integrate in your ECU software Measurement and calibration: CCP or XCP For information on these extensions, please refer to the specific datasheets on the following pages.

V2.4 2012-01 Overview of the CANbedded software components

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Contact and Availability CANbedded basic software is available for many commonly used microcontrollers and in OEM-specific variants. For more information go to: www.vector.com/cve/ Or find your personal contact at: www.vector.com/contact

Functions The following basic functions are provided by the CAN driver: CANbedded provides simple interfaces (APIs) that are identical for > Initialization of the CAN controller all applications. If possible, the API is standardized over all OEM > Sending of CAN messages and hardware variants. This let’s the user quickly and conveniently > Receiving of CAN messages integrate CANbedded in the ECU software. The CANbedded compo- > Overrun and error handling nents route asynchronous events such as receiving of CAN > Notification via wake-up events messages, bus wake-up or different error states (Assertions) to the application by means of configurable callback functions. Interaction Layer (IL) The IL operates signal-oriented and is responsible for: You can configure the precise set of generated APIs and callbacks > Sending messages depending on the send types of the signals to optimally adapt them to the needs of your specific application. they contain (Cyclic, OnEvent, IfActive, etc.), The Vector tool chain optimally supports you here. > Timeout monitoring of Rx messages and signals, > Notification of sending and receiving of signals. CANbedded consists of the software components described in the The IL is available in OEM-specific variants. sections that follow. Vector would be glad to assist you in selecting the components you need. Network Management (NM) The main task of Network Management is to manage the sleep and CAN Driver wake-up states of a network’s ECUs. This functionality is handled The CAN driver provides an interface for higher software layers that by the NM CANbedded software component, which is available in is as hardware independent as possible. This enables platform- different variants. Depending on OEM requirements, either OSEK independent use or re-use of the higher software layers. NM, AUTOSAR NM or another OEM-specific NM algorithm is used.

All necessary settings such as parameters for the hardware accep- Transport Protocol (TP) tance filter or Bus Timing Register are made at configuration time. By default, the CANbedded Transport Protocol conforms to ISO The configuration tool GENy from Vector offers preselections for 15765-2. OEM-specific TP variants are also available, e.g. VWTP or configuring these filters and registers. MCNet. The ISO 15765-2 conformant variant is available in either

Configuration and parameterization with the GENy configuration tool

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training In the framework of our training program, we offer various courses and workshops on CANbedded in our classrooms or at your business site. For more information on individual training events and a schedule go to: www.vector-academy.com

the 1999 variant or the 2004 variant and with different addressing Configuration methods (Normal, Extended, Normal fixed, Mixed). You configure CANbedded with the PC-based configuration tool GENy. GENy utilizes information from the communication database Communication Control Layer (CCL) (e.g. the DBC file from the OEM) as well as manual settings. GENy The CCL simplifies integration of the CANbedded software com- generates parameterization files based on the configuration. They ponents in your ECU software, such as CAN driver, IL, TP, NM, and contain the parameters and function calls of the CANbedded soft- other CANbedded options CANbedded Gateway, CANbedded J1939 ware components that are used. For example, the initialization and CANdesc. It manages defined system states (PowerOn, sequence for software components is defined in the CCL confi- StartUp, ShutDown, Stop/Sleep, Normal) as well as communica- guration. tion states (Net request, Net release). It can coordinate state transitions (WakeUp and GotoSleep) according to the requests. Scope of Delivery The CCL offers the following functions: You get the CANbedded components as C source code. In special cases, e.g. for time-critical applications on small microprocessors, > Initializing the CANbedded software components certain portions of code may be programmed in Assembler. > Calling periodic functions of the CANbedded software components such as Timer Tasks or State Tasks. The scope of delivery of CANbedded includes: > Controlling the bus transceiver > GENy configuration tool as executable Windows program > C header and source files > Special CCL Functions Documentation and sample programs with makefiles > The CCL already contains OEM-specific communication requirements such as Wakeup Prevention and Minimum Communication Activity. Additional basic software from Vector that is relevant to > The CCL supports what are known as multipurpose ECUs (for details, CANbedded: > see datasheet on the Identity Manager.) CANbedded J1939 > CANbedded Gateway > CANdesc for diagnostics > Measurement and calibration with XCP/CCP

The CCL coordinates the state transition „Wakeup“

More Information: www.vector.com/contact EMBEDDED SOFTWARE

> CANbedded LIN > CANopen Master and CANopen Slave You will find details on these products in specific datasheets on the following pages.

Additional Services You can have Vector perform project work on the following aspects: > Adaptation of the CANbedded software components to special target platforms > Extension of the CANbedded software components > Creation of software components for other bus systems such as FlexRay, Ethernet or MOST based on AUTOSAR

This list is supplemented with telephone and e-mail hotlines, special workshops that address OEM-specific issues and individual consultation on software integration. This support lets you reduce the development time and costs for your ECU.

The Vector products for your CAN projects

More Information: www.vector.com/contact EMBEDDED SOFTWARE

CANbedded J1939

Embedded software components for J1939 applications

> Overview of advantages J1939 Base Module: Contains queues for sending and receiving > Convenient configuration via GUI J1939 messages (PGNs), static address claiming (J1939 NM) and > Code and runtime efficiency due to wide-ranging configurability an interface to OSEK/VDX-OS. Optionally, the J1939 Base Mod- > Good portability by hardware-independent API ule offers the ability to implement multiple ECUs with different > Easy to integrate in your application software, since it is delivered ECU addresses on a single hardware unit (virtual ECU). > as source code CAN Driver: The CAN driver handles sending and receiving of > Easy integration of other standard components (e.g. transport J1939 messages. It is hardware-dependent and is available for protocol, diagnostics, etc.) many currently used microcontrollers (for more details, see the CANbedded datasheet).

The CANbedded J1939 bundle contains standard software compo- As options, you can extend the communication stack with the nents for your SAE J1939-based applications. CANbedded J1939 following modules: provides functions for fundamental communication between ECUs > J1939 Dynamic Interaction Layer: Standard access to the signals in heavy-duty vehicles and agricultural machines. The software and parameters of PGNs with variable CAN identifiers (node components are available as optimized single or multi-channel address, priority) variants. You can extend CANbedded J1939 with various software > J1939 TP BAM: Transport protocol for broadcast messages per components of the CANbedded product line from Vector. J1939-21 > J1939 TP CMDT: Transport protocol for point-to-point transmis- Application areas sion per J1939-21 > ECUs of the drivetrain and chassis of heavy-duty vehicles > J1939 Dynamic NM: Support for dynamic address assignment per > FMS (Fleet Management System) J1939-81 > Terminals and implements for agricultural machines > J1939 Router: Routing of J1939 messages to other J1939 buses using configurable filter rules

Functions CANbedded J1939 contains a J1939 communication stack with the following software components:

CANbedded J1939 software architecture V2.5 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Schulungen Supported hardware platforms Im Rahmen unseres Schulungsangebotes bieten wir for CANbedded CANbedded J1939 is available for many different controllers and J1939 and ISO11783 verschiedene Schulungen and Workshops in compilers. You will find a current list online at: unseren Seminarräumen sowie vor Ort bei Ihnen an. www.vector.com/ds_canbedded.availability_en Mehr Informationen zu den einzelnen Schulungen and die Termine finden Sie im Internet unter: www.vector-academy.com

Configuration Additional services You can conveniently configure and generate CANbedded J1939 Vector can perform project work for you in the following areas: standard software components with the Vector PC-based software > Modification of software components for other target platforms tool GENy. > Extensions of CANbedded J1939 for ISOBUS (ISO11783) and NMEA2000 with dynamic address claiming (J1939 Dynamic NM), Product components ETP and FastPacket transport protocols and working sets The CANbedded J1939 product contains the following: > Extension of standard components by adding customer-specific > GENy for configuring and generating software components functions > Software components as C source code > Flash programming > Documentation > Sample programs Our service offer is supplemented by telephone and e-mail hotlines, special workshops that focus on OEM-specific aspects and Other relevant products customized consultation for software integration. This reduces > CANdesc: Embedded software component for OEM-specific diag- your development time and costs. nostics over KWP or UDS (for more details, see the CANdesc datasheet). > Transport protocol (TP): Software component for transmitting data > 8 bytes according to ISO 15765-2. In addition, OEM-specific variants are available (for more details, see the CANbedded datasheet). > osCAN: Preemptive real-time operating system per the OSEK/ VDX standard with a small, robust operating system core.

Configuration of J1939 software component is performed with GENy

More Information: www.vector.com/contact EMBEDDED SOFTWARE

CANbedded LIN Communication

Embedded Software Components for Local Interconnect Network

LIN (Local Interconnect Network) is a cost-effective, serial communica- Modifications and settings in detail: tion system for distributed electronic control units in the motor vehicle. > Adaptation of ECU-specific parameters to the network design The LIN protocol is specified by the LIN Consortium, of which Vector is an > Configuration of the LIN driver to the properties of the specific ECU Associate Member. e.g. oscillator frequency, UART, etc. > Configuration of diagnostic services for LIN Slave ECUs Features and Advantages > Definition of message and signal callbacks Increasing software complexity makes it advantageous to implement standardized software components. Vector’s expertise acquired in devel- The object codes of the LIN software components are compiled and oping and working with other protocols has been utilized throughout the linked with the application. Vector’s LIN simulation and analysis tools development of LIN software components: (e.g. CANoe.LIN and CANalyzer.LIN) are available for integration, analy- > Standard software components based on a portion of the generated sis and for test purposes. For physical bus access one of Vector’s XLI- code are scalable for application-specific requirements Interface products can be purchased; these products serve as universal, > Automatic generation of parameter settings and configurations serial bus interfaces for the LIN bus. > Runtime efficiency Timing control of the LIN software components is achieved by having > Low demand for ROM and RAM memory tasks called periodically by the application or an operating system. > Simple interfacing to the application software Therefore the LIN driver does not require any auxiliary timers. > Compatibility with other Vector products including analysis, simulation, and calibration tools Functions > Support of LIN 1.2/1.3/2.0/2.1 and 2.2 The fundamental objective of the implementation is to provide an inter- > Support of multi-channel LIN configurations face that is easy to use and satisfies all applications. The standardized interface offers these features: LIN networks are described in the LDF (LIN Description File) format > Initialization of the LIN hardware according to the “LIN Configuration Language Specification”. This > User-configurable baudrate (Recommended: 2400, 9600, and 19200 includes all of the information needed to define signals, messages, baud Baud) rate and schedule tables. A configuration tool is used to adapt all LIN > Sending of LIN messages (confirmation by flags and callback func- software components to ECU-specific requirements. The tool imports tions) either LDFs or NCF files (Node Capability File) for parameterization.

Overview of the software components V2.3 2011-12 of CANbedded LIN Communication

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training Availability

As part of our training program, we offer a range of classes and Our LIN software components for motor vehicle ECUs are available workshops on CANbedded LIN Communication. for a large number of commonly used microcontrollers. For more information and the dates of our training courses, please For further information please visit: visit: www.vector-acadamy.com http://www.vector.com/vi_canbedded_lin_en.html

> Receiving of LIN messages (notification by flags and callback func- This makes it easy to implement CAN-LIN gateways, which are usually tions) implemented as master network nodes. > Sleep and wakeup handling > Protocol error handling LIN Master Transport Layer > Timeout monitoring of messages Since the master ECU usually has an auxiliary CAN channel, over > Checking of runtime behavior during the development phase (debug- which diagnostics are performed from a tester, the main task of the ging) LIN master is to pass the received tester requests to the relevant LIN slaves. The LIN Diagnostic Transport Layer (DTL) is used for Application Areas this; it offers two API types according to the LIN 2.0/2.1 and 2.2 LIN was developed to round out a collection of automotive protocol specifications: standards, but it has been adopted in other areas such as automation > DTL Raw is used if the data already exist in segmented form engineering as well. The focus is on cost-effective communication net- (routing of CAN TP messages on LIN). works for ECU subsystems with low data rates. > DTL Cooked accepts assembled data and segments them accord- LIN therefore supplements existing bus protocols. ing to LIN bus requirements (Diagnostic Service Data Units).

Hardware Interfaces LIN Slave Diagnostics Two software components are needed for LIN communication. One LINdiag is a very compact implementation of UDS 14229.3 diag- component is a hardware-dependent low-level SIO driver, whose task is nostics for LIN slave ECUs. It receives requests, routes them to the to implement abstraction of access to the serial interface. The second appropriate service and constructs the response in interaction with component, the LIN driver, is overlaid on this and provides an API to the application. This involves internal management of a diagnostic higher-level components. This API satisfies all of the requirements of the buffer to monitor for data consistency and overruns. To send and current LIN standard. receive requests and responses LINdiag needs the LIN Transport The driver is a standardized and easy-to-configure software component Protocol, which is included in the delivery. for communication between master and slave network nodes. The LIN driver is one of the CANbedded components from Vector; it assures consistent integration with CAN components.

Overview of Design, Configuration and Integration Processes

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Further Options Licenses > Optional for slave ECUs: Diagnostic software components with When the same hardware interface and same compiler are used the associated transport protocol acquired licenses can be used for all devices of a processor type > Optional for master ECUs: Transport protocol with raw or cooked API and any desired projects. > Gateway: CAN-LIN and LIN-LIN routing for master ECUs > SAE J2602: As a supplemental option, support of the SAE J2602 Supplemental Services “Recommended Practice” specification is available for LIN Vector also offers related project services such as: drivers. > LIN driver expansions > Flashing of LIN slaves > Support of other target hardware > Development of higher OEM-specific protocol layers, e.g. diagnostic Scope of Delivery protocol The following items are supplied with the product: Services also include telephone and e-mail hotlines, special workshops > Configuration tool (executable Windows program) with OEM-specific focus and individualized consultation on software > C sources for LIN driver and optional software components integration with the goal of reducing development time and costs. > Sample programs > Documentation and operating instructions

More Information: www.vector.com/contact EMBEDDED SOFTWARE

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/12

CANbedded Gateway

Standard Embedded Software Components for CAN and LIN Routing

> Signal routing Overview of advantages > Message routing (with/without data queue) > Selectable coupling of CAN and/or LIN networks with user- > TP (Transport Protocol) routing definable routing relationships > Mature standard software component Signal Routing > Solid, lean and efficient foundation for your gateway ECU Routing of signals makes it possible to exchange dedicated infor- > Available for a large number of OEMs mation (e.g. momentary vehicle speed) between the networks. The send cycle times, send types and signal positions within mes- To exchange data between different networks, a gateway ECU is sages – all defined in the communication database – may differ needed that only transports to the other network those messages between the source and target networks. The values of the signals 3/12 or signals that are actually needed. to be transmitted are not changed in the process. In case of an Rx timeout, the CANbedded Gateway implements a substitute value Application Areas strategy. The signal to be transmitted is written and routed with a CANbedded Gateway is a mature standard software component for predefined signal value (default value or special substitute gateway ECUs between different CAN or LIN networks. CANbedded value). If routing relationships occur that cannot be resolved, Gateway lets users define routing relationships simply and quick- e.g. if the signals of a routing relationship have different sizes, ly. Both 1:1 and 1:N routings are supported in any direction. The the application can use C callback functions to flexibly adapt sig- CANbedded Gateway utilizes bus-specific standard components of nal contents before routing (e.g. by scaling signal values). CANbedded, and so it is hardware independent. It covers the specific requirements of many different OEMs. Message Routing In routing of messages, the entire message is routed in either the Functions interrupt or task context. This routing type is faster and more The CANbedded Gateway contains complex mechanisms for receiv- efficient than signal routing, but it cannot be applied in all routing all messages and signals and then sending them to another ing relationships. In message routing, the messages may differ in network under consideration of filter and conversion rules. Users their message-ID, send cycle and send type. can select from:

Gateway between CAN and LIN buses Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/13

COMMUNICATION SOFTWARE

Training In the framework of our training program, we can offer you various training events and workshops on our software components in our classrooms as well as at your business site. For more information on individual training events and dates please visit: www.vector-academy.com

By default, message routing always utilizes the most recent data. Configuration If data is transmitted less frequently than the data is processed by The CANbedded Gateway is configured with GENy, the configura- the associated Rx event, the CANbedded Gateway sends the data tion and code generator tool from Vector. The configuration pro- of the last Rx event. Neither the signal layout within the message cess is based on a DBC or LDF/NCF description file. Routing rela- nor the signal values are changed here. tionships are defined either: The user can control gateway activities by configuring “condition- > Automatically by OEM-specific algorithms based on clear rules al routing”. This saves on bandwidth during critical phases, such > Manually by targeted selection of the signals and messages to as during software flashing or diagnostic sessions. This is done by be implemented defining routing groups and assigning routing relationships to one or more routing groups. At runtime, the application can ena- Scope of Delivery ble or disable routing of individual groups with the help of an API. > Configuration tool as executable Windows program 3/13 > C source code TP Routing > C header files The TP Gateway is responsible for routing the transport protocol > Documentation ◆ data. Diagnostic requests from CAN to LIN and the associated responses from LIN to CAN might be transmitted, for example. Using the ISO transport protocol component from CANbedded, it is possible to support different protocol addressing modes on the CAN bus.

Other Relevant CANbedded Products Preconditions for use of the CANbedded Gateway are the presence of the Vector Interaction Layer (when signal routing is used) and the relevant Vector CAN or LIN drivers. TP routing requires the ISO Transport Protocol for CAN or the DTL (Diagnostic Transport Layer) for LIN.

Layer model of the CANbedded Gateway Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/14

CANdesc and CANbedded DEM

Software components for diagnostics

CANdesc and CANbedded DEM can easily be incorporated into a Overview of Advantages CANbedded communication stack from Vector. However, you can > OEM-independent implementation of your application also use the two software components in your communication software stack. > Quick, simple and uniform interface to the OEM-specific diagnostic protocol in the desired version Functions > Available for many bus systems CANdesc and CANbedded DEM are conformant to the OEM-specific > Together with CANdelaStudio CANdesc gives you a diagnostic specification and are available for a number of differ- comprehensive diagnostic solution from specification to ent OEMs. They contain the following functionality: embedded software > Multiple diagnostic configurations with up to 31 different 3/14 CANdesc: parameter sets > Provides a signal-based interface as a uniform interface to the > Guaranteed consistency between diagnostic specification application. This simplifies interfacing of diagnostics to your and generated code ECU software. > Full implementation of diagnostic services $28 (Communica- The diagnostic software component CANdesc (desc = diagnostic tionControl), $2A (ReadDataByPeriodicIdentifier) and $2C embedded software component) is the uniform implementation of (DynamicallyDefineDataIdentifier) the diagnostic protocol for different automotive OEMs. CANdesc is > Validation of diagnostic requests in reference to Service Id, generated according to the configuration based on the diagnostic Session, Sub-Service Id, Format, Session and Security of a specification (CDD file). To implement the error memory, you can sub-service extend CANdesc with the CANbedded DEM component, which gives > State control (depends on the CANdela database, e.g. Session you a fully OEM-specific diagnostic solution for your ECU. or Security) > Assurance of data consistency in parallel diagnostic requests Application Areas from the same tester or multiple testers > ECUs for passenger and commercial vehicles > Generation of a template including the necessary function > ECUs in CAN, MOST, FlexRay and other communication systems stubs that lets you realize your own diagnostic implementation quickly and easily.

Complete generation of the ECU’s diagnostic software Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/15

COMMUNICATION SOFTWARE

Example of Code Sizes Microprocessor: Motorola HC12, MC9S12P128 Extended setup with services 0x2A and 0x2C: Compiler: Cosmic 4.7 13 Diagnostic services and 40 subfunctions are implemented The code size is increased to approx. 14 kBytes. The RAM size depends on the size of the scheduling table and Code size: approx. 6 kBytes the number of dynamically defined data identifiers. Tables and constants: approx. 700 bytes RAM: approx. 90 bytes plus bytes for the diagnostic buffer

> Optional: Implementation of the Diagnostic Adaptation The use of CANdelaStudio offers CANdesc users significant advan- Protocol (DAP) for MOST ECUs tages. For more details, please refer to the CANdelaStudio datasheet in the diagnostics catalog. CANbedded DEM As soon as the application software detects errors, it must initiate Handling of Variants saving of the related Diagnostic Trouble Codes (DTC). The CANbedded If your ECU requires diagnostic configuration variants, CANdesc DEM component from Vector can be used for this task. For each and CANbedded DEM offer a powerful solution for this. With GENy error (DTC), the software component stores the following infor- you can define up to 31 different parameter sets and store them mation in error memory: in the ECU in a resource optimizing way. This avoids redundancies > DTC status byte in the ECU software, because identical interfaces to the same > Environment data data, services or DTCs are merged in the generated diagnostic 3/15 > Cycle counters code. > Fault detection counter > Aging counter Scope of Delivery > GENy configuration tool as executable Windows program When CANbedded DEM is combined with the diagnostic software (for Windows NT/2000/XP/Vista/Windows 7) component CANdesc, you get a complete implementation of the > Documentation/user’s manual/Readme following error memory related UDS services: > C source code for CANbedded DEM > $14 Clear diagnostic information > $19 Read DTC information Additional Services > $85 Control DTC setting Vector offers project services related to diagnostics: > Adapting the application to CANdesc Configuration > Implementing error memory strategies You configure CANdesc and CANbedded DEM with the GENy tool > Process consultation in the area of diagnostics and a CANdela file (CDD). To create this file you will need the tool > Testing diagnostic implementations for ECUs. ◆ CANdelaStudio Version 6.5 or higher.

Diagnostic software (CANdesc and CANbedded DEM) in the diagnostic development process EMBEDDED SOFTWARE

XCP Professional

Measuring, Calibrating, and Testing via CAN, FlexRay and Ethernet

Overview of advantages port Layer (TL) may be necessary. Vector would be glad to assist > Can be activated/deactivated in production operation you in this area. > Easy to configure with PC-based tool > Low memory requirement and short execution times based on Functions scaling of the software component to your requirements XCP Professional contains all necessary functions for communicat- > Transport layers available for CAN, FlexRay and Ethernet ing with the XCP Master, such as: > > Compatible with MICROSAR BSW modules (AUTOSAR) Synchronous data acquisition based on DAQ lists > Read and write accesses to memory addresses > Initialization and switchover of the memory area for calibration Application Areas data Automotive in-vehicle ECUs are measured, calibrated, and tested > Support of time stamps with the XCP Protocol (Universal Calibration Protocol) – the suc- > Protection against unauthorized writing and reading in memory cessor to CCP (CAN Calibration Protocol). XCP was standardized by > Shutoff of XCP in production operation by a single function call ASAM (Association for Standardization of Automation and Measu- > Access protection by Seed & Key support ring Systems), a process in which Vector played a leading role. By > Synchronous data stimulation (STIM) and Resume mode clearly differentiating the Protocol Layer and Transport Layer, XCP > Flash and EEPROM programming is able to support many different bus systems: CAN, FlexRay and > Communication mode: Block transfer Ethernet. > Transmission of service request packets On the PC side, the CANape or CANoe tool is used as the XCP mas- > Bit modification and short download ter. Its counterpart in the ECU is the XCP slave. This is implemented > Generation of an A2L file based on the ECU configuration by the XCP Professional software component. It not only contains all ASAM functional content, but useful extensions as well. Synchronous Data Stimulation (STIM) You can use XCP Professional together either with a conventional To optimize algorithms and parameters, you can use XCP over the communication stack or in AUTOSAR systems. In either case, it is bus system to read a measured signal from the ECU (DAQ) and unnecessary to modify the XCP software. If a software stack by a modify it with a simulation model (e.g. MATLAB). The re-computed third-party producer is used, small modifications to the XCP Trans- value is then written back to the ECU (STIM). Reading and writing

XCP Professional is available for CAN, FlexRay and Ethernet V2.3 2011-12

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Training In the framework of our training program, we can offer you various training events and workshops for XCP in our classrooms or at your business site. For more information on individual training events and dates on the Internet go to: www.vector-academy.com

are performed synchronously in a predefined time interval Transmission of Service Request Packets (Bypassing). Service request packets let you transmit lines of text. They are stored in program code, and when the program section is executed Resume Mode they are sent to the XCP master where they are displayed. This The Resume mode permits cold-start measurements, e.g. to check function is very useful primarily during system development and in ECU behavior in the wakeup phase. This involves activating the XCP debugging. stored in the flash memory immediately after a cold-start – even before the application starts. Sending of the measured values Configuration begins automatically, and they can be logged for later evaluation. XCP Professional is configured with the PC-based GENy configuration tool. Compiler switches may be used to deactivate unneeded Flash and EEPROM Programming functions, and this reduces memory loading. When XCP transmis- The Vector XCP component is not only able to store measured sion is started, the list of supported functions is communicated to values in RAM, but also in flash or EEPROM memory. To do this, XCP the XCP master via the XCP plug-and-play mechanism. executes callback functions in which the application could activate the flash algorithms, for example. This gives you the option of XCP-Master individually adapting the algorithms to the flash or EEPROM mem- The XCP Master, using an ECU description file in ASAM format (A2L), ory being used. has access to measurement signals and calibration parameters in the ECU through the XCP Slave. Communication Mode: Block Transfer Block Transfer lets you transfer large quantities of data. This functionality is comparable to that of a transport protocol. The sender segments the data, and the receiver re-assembles them in the correct sequence.

CANape as XCP Master CANoe.XCP or CANoe.AMD as XCP-Master CANape is the all-round tool from Vector for measurement, calibration CANoe is Vector tool for the development of both complete ECU and diagnostics of ECUs. The key properties of CANape related to networks and individual ECUs. CANoe is made an XCP Master with the measurement and calibration are: XCP and AMD options.. > Time-synchronous real-time acquisition and visualization of internal ECU signals with XCP/CCP, of signals from CAN, LIN, CANoe.XCP provides you a reading or writingaccess to ECU memory Ethernet and FlexRay buses and from external measurement location via the ASAM-standardized XCP or CCP protocol. equipment Especially for AUTOSAR, CANoe.AMD (AUTOSAR Measurement and > Online calibration via XCP/CCP, real-time stimulation via XCP and Debugging) contains the “State Tracker” window that displays discrete offline calibration states and binary signals in a user-friendly way. This permits you to > Flash programming of the ECU via XCP/CCP or the diagnostic analyze critical flow sequences. protocol > Rapid prototyping for functional development by bypassing a For more information, please refer to the “ECU Testing” product MATLAB/Simulink model with the help of CANape catalog.

Additional information can be found in the “ECU Calibration” product catalog.

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/16

Identity Manager

Solution for Multiple ECUs

Physical multiple ECU Advantages > More efficient handling of variants > Less administrative effort > Reduced warehouse costs

When tracking the development of ECUs in automobiles, one trend is clearly evident – ECUs are becoming increasingly more powerful. At the same time, the number of variants is growing drastically, which is reflected in the growing effort required to manage 3/16 them and also results in growing costs. A typical case of physical multiple ECUs are the ECUs for the driver Cost savings are realized by reducing administrative effort. This and passenger side doors. These ECUs have nearly identical func- can only be achieved with the assistance of intelligent solutions tions. However, there are differences in the receive and send mes- that can manage the many different variants. sages, diagnostics and Network Management address.

Based on our many years of working together with automotive The steps: Develop an ECU that will later be used for both door OEMs and suppliers, Vector knows these continually recurring use sides. Load the database that covers the ECUs in the GENy config- cases well and has developed optimized solutions especially for uration tool and select both ECUs simultaneously. Configure the them. Identity Manager as a physical multiple ECU and assign a separate identity to each of the nodes (Left ECU, Right ECU). Use cases Practice shows that it is primarily the following three use cases There are essentially two different ways to proceed in coding: If that recur frequently: the message layout is identical between the identities, utilize the manual buffer overlay in GENy. This means that the same signal > Physical multiple ECU APIs can be used regardless of the currently active identity. So, > Virtual multiple ECU only one application needs to be developed, but the ECU acts dif- > Multiple configurations ECU ferently to the outside world depending on the identity which is initialized. The differences are automatically read out from the The solution approaches presented below lead to substantial sim- DBC file. plification, reduce administrative effort and thereby reduce costs. In the second case, buffer overlaying is not needed. Instead, dif- Identity ferentiate between the left and right sides using generated mac- An identity identifies an ECU. It determines which variant of ros in the code. It is also easy to implement crossovers of receive the ECU should be activated (e.g. which door side). So, an and send messages between the two door ECUs while optimizing identity is the configuration of an ECU that is active at run resources. time, based on a description file. An ECU’s identity is set when the ECU is initialized. This software is loaded in the left and right ECUs. The decision on whether the software is to be installed in the left or right door ECU is made with each new initialization. A simple function call establishes the ECU’s identity. Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/17

COMMUNICATION SOFTWARE

Virtual multiple ECU Multiple configurations

3/17 Higher-performance control modules also contain more memory space. This makes it possible to represent multiple ECUs (e.g. gateway and radio) in one CPU, saving on additional hardware. These are referred to as virtual multiple ECUs. A typical application involving multiple configurations is the development of ECUs for both a current car line and a new car line. The different communication nodes are derived from one data- These ECUs are also referred to as carry over ECUs. Changes made base. In the configuration tool GENy, you only need to select tho- within the associated database are often very extensive. It is pos- se nodes that will be implemented and then configure a virtual sible to use a completely different signal layout or use different multiple ECU in the Identity Manager. All nodes are assigned to messages for different model series. The new configuration could one identity. The identity operates from a node superset and all even support a different number of CAN buses. necessary information on the nodes. First, develop the software for both car lines. In doing so, treat each car line as though it were assigned to one (or more) dedicated CAN channel(s) with an associated database (DBC file). These configured, logical CAN channels are then mapped to physical CAN Controllers. Just as with the physical multiple ECU, the ECU’s identity is determined by a function call at the start. ◆ EMBEDDED SOFTWARE

Wide Availability of CANbedded

Supported Microcontrollers and Compilers

Controller Compiler CANbedded/ CANbedded Controller Compiler CANbedded/ CANbedded CANbedded LIN CANbedded LIN J1939 J1939 Altera DIABDATA Wind River, MPC5xx X X NIOS II with Bosch GNU X Green Hills, D-CAN controller Metrowerks Analog Devices DIABDATA Wind River, MPC5200 X Aduc703x ARM, IAR X Metrowerks, QCC AduCM330 IAR X DIABDATA Blackfin BF5xx VisualDSP++ X X Wind River, MPC55xx, MPC56xx GNU, GAIO, X X Atmel Green Hills, Metrowerks AT90CANXX HPInfotech, X X IAR Fujitsu ATmega (X8, X4P, HPInfotech, X X 8L, 8FX Fujitsu X XC1, XM1) IAR 16FX, 16LX Fujitsu X X ATtinyX7 IAR X FM3 Keil X AVR32 IAR X X FR30, FR50 Fujitsu X T89C51CC00x Keil X/- FR60 Fujitsu X X Cypress FR81 Fujitsu [1] X PSoC3 Keil X/- MB86R0x GNU, QCC X Europe Technologies Infineon easyCAN ARM X C16x Keil, Tasking X X Freescale C5x5 Keil X/- Cosmic, 68HC08 X/- X Metrowerks TriCore GNU, Green X X DSP56F80x Metrowerks X Hills, Tasking XC16x Keil, Tasking X DSP56F83x Metrowerks X HC12, HCS12, XC2000 Tasking X X Cosmic, IAR, MC9S12, S12, X X Metrowerks XC800 Keil X/- MCS12 HCS12x, MC9S12x, Cosmic, IAR, Microchip X X S12x, MCS12x Metrowerks GNU, Green dsPic33F Microchip X X IMX X Hills, QCC PIC18 Microchip X/- X MAC 7100, ARM, IAR X X MAC 7200 PIC24 Microchip X Microtec, MC68k X Tasking Micronas DIABDATA MCF52xx X CDC32xxG Green Hills X Wind River Cosmic, CEVF IAR X/- MCS08 X/- X Metrowerks National CR16 National, IAR X X V2.5 2012-02

More Information: www.vector.com/contact EMBEDDED SOFTWARE

Controller Compiler CANbedded/ CANbedded Controller Compiler CANbedded/ CANbedded CANbedded LIN CANbedded LIN J1939 J1939 NXP STmicroelectronics LPC1700, LCP2000 Green Hills, X SPC56xx DIABDATA X X Keil Wind River, SAF7780 Green Hills X GNU, GAIO, Green Hills, SJA20xx Green Hills X X Metrowerks OKI ST7 Cosmic, Hiware X/- X AVC-Core ARM X ST9 GNU X/- X ML76Q25xx IAR X ST10 GNU, Keil, X X Tasking Panasonic ST30 ARM, Green X X MN101E Panasonic X/- Hills STA20 ARM, Green X MN103S Panasonic X Hills Renesas Electronics (NEC/Renesas) STM32 ARM X 78k0 Renesas X/- X STM8A Cosmic X/- X (NEC), IAR Telechips 78K0R Renesas X X (NEC), IAR TCC800 ARM X 78K0S IAR X Texas Instruments H8 tiny Renesas X TMS320 Texas Instru- X H8S, H8SX Renesas, IAR X X ments, QCC TMS470 Texas Instru- X X M16C Renesas, IAR X X ments, ARM, M32C Renesas, IAR X Green Hills TMS570 Texas Instru- X X M32R Renesas, X ments, ARM GAIO Toshiba R8C Renesas, IAR X X TLCS870 Toshiba X R32C Renesas, IAR X X TLCS900 Toshiba X RL78 Renesas [1] Tx03 ARM X SH2, SH2-A Renesas, X X Green Hills, TX39 Green Hills X GAIO, IAR TX49 GNU, Green X SH4 Renesas, Green X Hills Hills, QCC Xilinx V85x Renesas X X (NEC), Green Microblaze GNU X Hills, IAR Vector Silicon Labs CANoe osCAN Microsoft X X C8051F5XX Keil [1]/- X Emulation VisualC [1] = Currently in development

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/18

GENy

PC-Tool for Configuring Embedded Software Components

GENy is the convenient configuration tool for software compo- This makes GENy a scalable and fully generic configuration edi- nents from Vector. It was created for development processes of tor/generator that permits consistent configuration from a single the future. It is used to configure CANbedded components, integration environment, even in complex heterogeneous AUTOSAR communication modules and the Flash Bootloader for systems. Vector’s many years of experience in the area of ECU use in production ECUs. development ensures optimal workflows between OEM and suppliers without altering their tasks or roles. Features and Advantages GENy is a developmental offshoot of the previous configuration GENy is a collection of components (not a rigid program block); tools CANgen and DBKOMgen. The GENy architecture was com- therefore it can also be expanded very easily by adding auxiliary pletely redesigned based on experience with those two tools. components. 3/18 The following properties characterize the design: GENy’s graphic interface makes it very easy to use and intuitive. > Thoroughly modular structure due to its static framework, GENy always appears with the same “look and feel” independent stand-alone graphic user interface (GUI) and dynamically of the components to be configured. The configuration data is reloadable components shown and processed in a hierarchical tree structure. This makes > Reloadable hierarchies make it well suited for any configuration navigation user friendly, and the user gets a clear view of all task (CANbedded, LIN, FlexRay) options. > A cleverly designed framework mechanism interprets and manages dependencies in configuring components The Configuration View can be modified manually or via an exter- > XML is used throughout as the file format, both for the compo- nal XML file. The latter is essential for an OEM-specific appearance nent descriptions (Attributes) and data saving of GENy’s GUI and guarantees that parameters will have functio- > Open interfaces offer simple expandability nally relevant preset values.

Tool tips and the online help function help to save time and immediately gives you the information needed about possible component settings. Plausibility checks prevent invalid settings and thereby prevent errors.

GENy Program Window Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/19

COMMUNICATION SOFTWARE

Training As part of our CANbedded training program the configuration tool GENy is also explained. For more information on individual training events and schedules please visit: www.vector-academy.com

The generation process is logged in the Message Window, and this Application Areas indicates potential errors (e.g. mistakes in configuring) and The GENy configuration tool is always used in conjunction with other important information. This is done to avoid tedious debug- other Vector software components for communication and diag- ging efforts. nostics. GENy fulfills AUTOSAR Consortium requirements. ◆

Characteristics: > Configuration templates for different application types > System-wide parameters only need to be configured once > There is only one XML-based configuration file > Expandable due to open interfaces > For the Windows operating systems 2000, XP and Vista 3/19

Functions GENy is the tool for configuring any software component. Config- uration and parameter files can be generated to integrate them in the application project. Functional capabilities of GENy include the configuration of: > Embedded software components for CAN, LIN, and FlexRay > Flash Bootloaders > AUTOSAR BSW (communication modules)

GENy reads the following input files: > CAN database files (DBC) > LIN files (LDF) > FlexRay files (Fibex) > CANdela database (CDD) > AUTOSAR “ECU Configuration Description” (EDUC)

GENy Navigation View TOOLS & COMPONENTS FOR OPEN NETWORKING

CANopen Source Code

Embedded Software for CANopen

The CANopen Source Code contains CANopen services required for  NMT Slave (supports “Life Guarding”) an implementation. It thus offers the user the communication  Simple adjustment to various requirements functionality required for internal device development.  Broad spectrum of supported hardware platforms  Source code configuration and automatic generation of the Application Area object directory via CANerator CANopen The code can be used everywhere customers would like to equip For special application areas there are expansion modules available their devices with CANopen functionality, especially in systems for the CANopen Source Code, which can be ordered separately: where resources are at a premium.  Mini-Master  LSS Master Features and Advantages  LSS Slave Significant time savings can be achieved during product development by using the CANopen Source Code. The user can concentrate SDO Server on the integration of the application; the implementation of the The SDO Server offers an object directory and supports all defined CANopen protocol is simplified significantly. The code corresponds SDO transfer mechanisms such as expedited transfer, segmented to the most recent version of the CANopen DS-301 communication transfer, and block transfer for up to two parallel SDO servers. profile enabling a secure and CANopen-conforming implementation of the project. PDO Handling To simplify connection of internal application data to the object For the PDOs, the initial configuration is specified via static struc- directory, there are exemplary entries already in the object directo- tures that the user can adjust to his circumstances. The code sup- ry. Using these specifications, it is easy to create your own entries. ports variable mapping up to a granularity of 1 byte. All PDOs are also configurable via the object directory. On receipt of a PDO a Functions callback is initiated in which the user can place additional han- The CANopen Source Code offers the following functions: dling code. The user can create up to 200 PDOs and then transmit  SDO Server these event-based through changed data contents, synchronously  PDO/SYNC Handling through the reception of a SYNC message or time-triggered.  Heartbeat Producer/Consumer

V2.120011-3

Modules of the CANopen Source Code

More Information: www.vector.com/contact TOOLS & COMPONENTS FOR OPEN NETWORKING

The CANopen Source Code by Vector is available for many popu- lar microcontrollers. For current information, please visit our website: www.vector.com/sourcecode

NMT Slave Adaptation of the Code The code supports both guarding and heartbeat. It is possible to Before the code is translated, the user can specify the qualities to react to heartbeat messages of other nodes (heartbeat consumer). be supported allowing the code to be used even on systems with This makes it possible to set up highly efficient monitoring mecha- very limited resources. The adaptation occurs via the #define instruc- nisms in a network. User-specific emergency messages can also be tions that are set in a configuration file. By using the CANerator tools generated. (sold separately), this adaptation is simplified significantly. The code supports an interface for non-volatile storage of parameters. Here it is assumed that the memory is available via a file Local Object Directory system or as flash. The object directory of the source code can easily be expanded by the user. For this, appropriate entries must be added to the C files. Mini-Master Such an object directory contains the object's attributes and a The full functionality of a CANopen manager is not required for pointer to the actual memory location. For each object it is possi- many embedded networks. Often, by limiting functionality, em- ble to initiate callback functions with user-defined functionality phasis can be placed on requiring very few resources and the sim- when reading or writing. Thus, for example, an area test can be plest possible use. implemented when writing an object. With the aid of the CANopen This is the purpose of the add-on Mini-Master. It contains: CANerator, this object directory can be created automatically. For  NMT Master – control of the status machine of the NMT slaves to additional functional details, please refer to the CANopen CANerator start the network, for example. Monitoring of nodes by means of product information. node guarding.  SDO Client – the user can thus also initiate an SDO transfer. This Adaptation to a Target Hardware makes it possible to adjust settings in the object directories of To use the CANopen Source Code on a microcontroller platform, other nodes and to call up data that is not available through PDO first an adaptation is always necessary to abstract the CAN control- (e.g. for diagnostic purposes). ler and the specific timer and interrupt system. Of course, the  SYNC Producer – This module can be used to periodically send relevant compiler is also considered here. Vector offers prepared the SYNC message. adaptations for many platform combinations.

LSS (Layer Setting Services) Support during Integration Among other things, CANopen devices require a setting of baud We can also support you during the integration of the CANopen rate and node number. Devices without access possibilities via Source Code into your environment. Our support services range switches (e.g. watertight sensors) require a setting of these values from custom-tailored training solutions to workshops to project via the CAN bus itself. CANopen specifies the LSS (CiA 305) for this. work. The necessary services are provided in the form of source code modules by the LSS Slave and LSS Master add-on modules.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

More Information: www.vector.com/contact TOOLS & COMPONENTS FOR OPEN NETWORKING

Feature Matrix CANopen Source Code

CANopen Source Code1 CANopen Source Code1 Add-On Package Feature Mini-Master LSS Slave LSS Master Local object dictionary with mandatory entries:  – – – 1000, 1001, 1018 Object dictionary: pre-build configuration  – – – Maximum number of parallel SDO Servers 16 – – – SDO server protocols2 [e], [s], [b] – – – Maximum number of parallel SDO Clients – 1 – – SDO client protocols2 – [e], [s], [b] – – NMT slave state machine  – – – Node guarding –  – – Life guarding  – – – NMT master (NMT0 message) –  – – Heartbeat producer  – – – Heartbeat consumer  (max. 1261) – – – Store/restore (objects 1010/1011)  – – – Error behavior (1029)  – – – EMCY producer  – – – EMCY consumer (object 1028 not supported)  – – – Number of PDOs (adjustable) 0 – n1 –– – PDO variable communication parameters  – – – PDO variable mapping  – – – PDO granularity (minimum size of mapped objects) 8 bit (byte boundary) – – – TPDO inhibit & event time  – – – RPDO event time (time-out monitoring)  – – – PDO SYNC handling  – – – Multiplexed PDO  – – – SYNC producer –  – – RTR for Guarding & TPDO   – – Self-starting device  – – – LSS Master – – – 

V1.1 2011-03 LSS Slave – –  –

Legend:  = available – = not available 1 = The overall number of messages handled by the slave source code is restricted to 255. 2 = [e] – expedited [s] – segmented [b] – block

More Information: www.vector.com/contact TOOLS & COMPONENTS FOR OPEN NETWORKING

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/28

CANerator CANopen

Generation and Configuration of Source Code

CANerator CANopen is a tool for managing source code configura- Application Areas tion settings and for creating and generating object directories CANerator CANopen is intended for use together with CANopen automatically. Master and Slave Source Code from Vector.

Features and Advantages Functions The CANopen communication profile distinguishes itself through CANerator CANopen makes available the following functions: its broad scalability for use in embedded networks. It offers many > Configuration of the source code with the aid of a clear display opportunities for representing necessary device functionality and of all #define instructions at the same time accommodating the small resources of a micro- > Creation and automatic generation of the object directory as controller. Vector’s CANopen Master and Slave Source Code there- source code 3/28 fore offers a multitude of setting possibilities. > Automatic creation of EDS files The price for this flexibility is the increased complexity of the > Simple management of projects development process. In addition, there is the requirement for reusability and more flexible adaptability of software for entire These functions will be described in detail below. spectrums of various devices from a manufacturer. In addition to the actual configuration of the source code, the Source Code Configurator developer of CANopen devices must also create an object direct- CANerator CANopen displays all relevant settings of the source ory. This forms the interface between application and CANopen code (#defines) in a tree view. communication and serves to describe the device characteristics. An instrumentation of the source code allows the display of only With CANerator CANopen, the software developer has available a the relevant #define instructions and structures them in problem- tool that supports him comfortably in his tasks and significantly related groups. speeds up the development process. In addition, comments are assigned to the settings that explain their purpose and value range. Different data types are thus assigned various masks with type-sensitive validators.

Creating the EDS File with the Aid of CANeds Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 3/29

COMMUNICATION SOFTWARE

Generation of Object Directory Project Management Thanks to complete integration of CANeds, all capabilities of this CANerator CANopen allows the easy and comfortable management tool are available. These are described in detail in the CANeds of profiles. When a set of settings has been created, it is stored product information. With the aid of CANeds, all standard objects under its own name. Different profiles of this type can be used in of the object directory can be created with drag and drop. In addi- one and the same project for generation. Therefore it is possible, tion, it is possible to define manufacturer-specific objects. The for example, to provide a project with or without debugging infor- objects are already provided with default values that can be modi- mation and to change between the profiles with the touch of a fied if necessary. button. After the developer has specified the objects, CANerator CANopen Another application is the creation of profiles for various device displays the structure of the object directory in a hierarchical tree types on the basis of a source code. This simplifies the single structure. Then variables in the program are assigned to objects. source principle. 3/29 These are ultimately the interface between the protocol-specific As project documentation, an HTML page is generated, which in part of the software and the application. In addition to the sym- addition to general project information contains a list of all ob- bolic specification of variable names, the CANerator also sup- jects with their attribute values as well as a list of all settings. ◆ ports the specification of physical addresses in order to enable direct access to hardware ports. After the object directory has been created, the corresponding portions of the source code are created automatically.

Electronic Data Sheet (EDS) Virtually as a byproduct, the Electronic Data Sheet is generated. This can be processed further and tested with the functions of CANeds.

CANerator CANopen in Configuration Mode: All #define Settings can be Edited Clearly. EMBEDDED SOFTWARE

Operating Systems

The complexity of software applications is continually growing. The related development tasks can only be mastered by modularly structured programming.

Operating system conforming to the OSEK/VDX standard The use of an operating system helps implement complex flow, control and regulation tasks. An operating system based on the OSEK/VDX specification provides even better extendibility, portability and reusability for your application software.

As supplier of the world’s first certified OSEK/VDX-conformant operating system osCAN, Vector has many years of experience in implementation. A solution can be found for nearly any application, since Vector can offer a selection of over 30 different microcontroller platforms and universal tool-supported configurations of the operating system.

Operating system conforming to the AUTOSAR standard Vector’s MICROSAR OS is an AUTOSAR-conformant operating system. The operating system core conforms to the practice- proven OSEK/VDX standard. In addition, MICROSAR OS may include the optional executions time monitoring and/or memory protection. You will find detailed information on page 2/10. MICROSAR OS is also available as a multi-core operating system for multi-core processors.

Your partner right from the start Vector offers comprehensive support, from the beginning of a project until its successful completion. Training sessions and workshops provide basic information as well as in-depth knowledge for working with the software, conducted in Vector’s classrooms or on site. Vector assists the ECU development process with on-site startups, code reviews and other development supporting software tools.

V2.4 2012-01 V2.4 2012-01

More Information: www.vector.com/contact EMBEDDED SOFTWARE

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 4/2

osCAN

The real-time operating system based on the OSEK/VDX standard

Application Areas Overview of advantages Due to its static operating system architecture, osCAN is small and > Small, fast and resource-saving operating system core fast, and its use is beneficial wherever resources such as memory > Short boot times and processing time are in short supply. osCAN is especially ideal > Stack monitoring at runtime (deactivatable) when extremely short boot times are necessary. > Internal fault trace (deactivatable) > Component management for integration of sub-projects Functions > Supplied as source code As a fully preemptive multitasking operating system, osCAN offers > Quality process fulfills SPICE Level 3 priority-driven task management and a wide variety of synchro- > Graphic configuration tool for easy configuration of the nization mechanisms. It can generate cyclic and singular time operating system intervals as well as behave in an event-driven way. Its flexible > Simplified execution time analysis of osCAN applications by interrupt strategy makes it possible to use system services even supplied TimingAnalyzer within interrupt service routines. > Available for many 8, 16, 32 and 64 bit microcontrollers In addition to functions defined in the standard, osCAN offers: > Monitoring of stack utilization at runtime osCAN is a preemptive real-time multitasking operating system > Internal tracing of system calls 4/2 with properties optimized for use on microcontrollers. Vector’s > Extended error checking at runtime many years of experience in developing operating systems and > Clear and concise documentation of the configuration in HTML drivers has made osCAN a small and robust operating system core. With the optional High Resolution Timer, you can implement reso- It is certified to OSEK/VDX specification 2.2. This open standard lutions higher than 1ms for the timers, without simultaneously of the automotive industry provides a foundation for long-term increasing interrupt load. Depending on the controller, resolu- stability and availability. tions in the microseconds range are possible. Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 4/3

OPERATING SYSTEMS

Training In the framework of our training program, we offer various training events and workshops for osCAN in our classrooms as well as at the business sites of our customers. For more information on individual training events and dates please visit: www.vector-academy.com

Supporting Tools Complete solution from Vector The TimingAnalyzer design assistant simulates and computes Vector provides you a completely tuned solution for devel- task execution times for you. The analysis is performed for each oping ECUs. Along with the operating system, you get proto- task and each interrupt with the following parameters: Priority, cols and drivers for CAN, LIN or FlexRay. For more detailed period, execution time and deadline. The graphic user interface information, please refer to the relevant datasheets. offers clear and concise visualization of system behavior.

With the help of the CANoe osCAN Library, your application can Configuration be compiled into a DLL and integrated in a network simulation An easy-to-use graphic configuration tool lets you define all oper- under CANoe. This allows the application to be tested even before ating system resources before compiling. To assure portability, the availability of first hardware prototypes. the configuration is saved in the standardized OIL format (OSEK Implementation Language). Many emulators already offer the option of observing application The configuration tool offers component management, which lets behavior on the operating system services level (OSEK Aware- you implement sub-applications simultaneously in parallel pro- ness). osCAN supports the ORTI interface required for this. cesses. Next, the sub-applications are integrate into a total appli- Some UML and SDL modeling tools give you the option of configu- cation. This enables short development times and spatially sepa- ring models for use with an OSEK/VDX operating system. This is 4/3 rate developments. possible, for example, with: > MATLAB/Simulink from Mathworks Properties: > TargetLink from dSPACE > Easy to operate graphic user interface > Automatic checking for completeness and consistency > Convenient system scaling Related Vector products: > Component management > CANoe osCAN Library > ORTI support > TimingAnalyzer > High Resolution Timer

◆

Scope of Delivery Availability > Operating system core as source code The real-time operating system osCAN from Vector is availa- > Graphic configuration tool (OIL) for Windows NT/2000/XP/ ble for many commonly used 8, 16 and 32 bit microcontrol- Vista/Windows 7 lers. For more information on the Internet go to: > Instruction line based generator www.vector.com/oscan > Documentation > Sample programs Additional Services > TimingAnalyzer Vector offers you worldwide support related to OSEK/VDX: > Training courses osCAN conforms to OSEK/VDX specifications > Design consultation > OSEK/VDX-OS 2.2 > Customer-specific implementations > OSEK/VDX-OIL 2.3 > Hotline > OSEK/VDX-COM 2.2.2 > Software maintenance > All conformity classes (BCC1, BCC2, ECC1, ECC2, CCCA, The scope and form of all services are aligned to your wishes CCCB) and needs. > Size: 1–10 kB ROM, depending on platform and configuration Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 4/4

High Resolution Timer

Improve performance with high-precision timers for operating systems

An important property of operating systems is the precision of Application areas alarms; this in turn affects the resulting interrupt load. The alarm The High Resolution Timer is designed for applications mechanism of an OSEK/VDX or AUTOSAR operating system is based requiring high-precision timers but in which additional interrupt on counters which are incremented by either software or hard- loads are unacceptable. ware timers. When a counter reaches a preset alarm value, a predefined action is executed. The typical time resolution of such Hardware requirements timers is 1 ms. The High Resolution Timer can be used on all microcontrollers If timer resolutions with a higher precision than 1 ms are required, which have a free-running timer. The timer must also be able to the High Resolution Timer mechanism can achieve these enhan- trigger an interrupt when its value matches a user-definable com- ced precisions without simultaneously increasing interrupt load. pare value (compare-match). The clock speed at which the hard- Resolutions in the microsecond range are possible depending on ware timer is operated should be adjustable so that the desired the controller used. level of accuracy is achieved.

Features and advantages Configuration The High Resolution Timer for the osCAN and MICROSAR OS oper- The High Resolution Timer is configured using the configuration ating systems permits high-precision alarms with low system tool for the Vector operating systems. This tool is used to adjust 4/4 interrupt load (depending on hardware). An interrupt is only the prescalers according to the clock frequency of the microcon- triggered when an alarm actually becomes due. troller. ◆ The precision of the alarm time depends only on the resolution and clock frequency of the hardware timer. It may range from 100 ns to 100 μs depending on the microcontroller.

Functions “Collective” processing of several consecutive alarms can be controlled by defining a minimum interval between timer interrupts. This reduces interrupt load, especially when several alarms with similar intervals expire almost simultaneously.

Alarms and Tasks Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 4/5

OPERATING SYSTEMS

4/5 Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 4/6

TimingAnalyzer

Schedulability analysis/Trace visualization

The foundation for designing real-time systems is an analysis of A graphic diagram offers an intuitive overview of the timing. It the schedulability of tasks (schedulability analysis). Systems that gives the application engineer a better understanding of program employ a real-time operating system, such as the OSEK/VDX oper- processing in the ECU. It also considerably reduces the risk of ating system or AUTOSAR OS, consist of tasks and interrupt service creating unreliable systems. routines (ISR). Schedulability analysis shows whether a task or ISR could miss its deadline when all circumstances are taken into Functions considerations. In the analysis, the TimingAnalyzer studies the timing of both tasks and ISRs. A special algorithm considers mutual interactions Properties and Advantages resulting from use of the “resource” operating system service. In The TimingAnalyzer simulates scheduling tables and computes the TimingAnalyzer you can input the time with which a task or schedulability. The analysis is performed for each task and ISR ISR occupies the specific OSEK resource. with the information: priority, period, execution time and deadline. Various algorithms from scheduling theory may be selected. The graphic representation simulates a possible task switching In the default setting, the best algorithm is selected for a given sequence. The simulated schedule can be examined by zooming in data record. and measuring time intervals. Bitmaps of the graphic diagram can be saved for documentation purposes. 4/6 By using the TimingAnalyzer you can avoid the difficult and time- consuming work involved in determining worst case timing situa- Special functions tions, which is usually done by testing. The TimingAnalyzer is a > Schedulability analysis tool for integrating familiar software components into a runnable > Graphic simulation of schedules system. The time savings in terms of program creation and the > Import and display of emulator traces test phase translate into cost savings as well. Processor use is computed and output as a percentage. Processor use is optimized by modifying calibration parameters, leading to an efficient design that conserves on hardware resources.

Analysis example in the TimingAnalyzer Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 4/7

OPERATING SYSTEMS

Data Import Besides manual data input, the data may also be read-in from the configuration file of the operating system. This simplifies handling, since data input and calling of the TimingAnalyzer are performed directly in the configuration tool.

Application Areas The TimingAnalyzer is an efficient tool for all development departments that use real-time operating systems. Special atten- tion was given to supporting OSEK/VDX and AUTOSAR real-time operating systems and their applications.

Availability The TimingAnalyzer is available in combination with the OSEK/VDX-conformant operating system osCAN as well as the AUTOSAR-conformant MICROSAR OS. 4/7

Scope of Delivery > Graphic analysis tool for Windows NT/2000/XP/ Vista/Windows 7 > Documentation in electronic form > Sample files ◆ EMBEDDED SOFTWARE

Wide Availability of osCAN

Supported Microcontrollers and Compilers

Controller Compiler Controller Compiler Altera NXP Excalibur Green Hills LPC2XXX Green Hills NIOS II GNU, TaskingVX SAF7780 ARM, Green Hills ARM SJA20xx Green Hills ARM7-TDMI Green Hills OKI Cortex M ARM ML67 Green Hills Atmel ML665S OKI AT91 Green Hills Renesas Electronics (NEC/Renesas) AVR32 IAR 78kO IAR Freescale H8 tiny Renesas 68HC08 Cosmic H8S Renesas 68HC12, S12 Cosmic, IAR, Metrowerks H8SX Renesas MPC55xx, MPC56xx DIABDATA Wind River, M16C IAR, Renesas, Tasking Green Hills, Metrowerks M32C GAIO, IAR, Renesas S12X Cosmic, Metrowerks M32R GAIO, Renesas Fujitsu R32C IAR, Renesas 16FX Fujitsu R8C IAR 16LX Fujitsu SH2 GAIO, Green Hills , Renesas FCR4 Green Hills V850 Green Hills, IAR FR30, FR50, FR60 Fujitsu STmicroelectronics MB86 Green Hills SPC56xx DIABDATA Wind River, Infineon Green Hills, Metrowerks Tricore GNU , Tasking ST10 Keil, Tasking XC16x Keil, Tasking, TaskingVX Texas Instruments XC2000 TaskingVX TMS 320 Texas Instruments Intel TMS 470 Texas Instruments, Green Hills PXA27x Green Hills TMS 570 Texas Instruments Microchip Toshiba dsPIC30 Microchip TLCS-900 Toshiba PIC18 Microchip TX19, TX39, TX49 Green Hills PIC24 Microchip TX19A Toshiba Vector

V2.4 2012-02 CANoe osCAN Emulation Microsoft VisualC

More Information: www.vector.com/contact EMBEDDED SOFTWARE EMBEDDED SOFTWARE

Flash Memory Programming

Today, systems for downloading software to ECUs are used in all Data compression phases of ECU development. Vector offers a number of software Automotive electronics is continuously becoming more complex, solutions to meet various requirements: and so it requires more extensive software. Suitable data > Flash Bootloader for CAN, LIN, FlexRay, MOST and Ethernet compression methods can be used to transport the increasing > Flashing via CCP/XCP amounts of data more quickly on data buses; they reduce > Option for the Flash Bootloader: Security component transmission times drastically. Vector offers optimized solutions > Option for the Flash Bootloader: Data compression for the Flash Bootloader and flash tools. > PC-based flash tool Flash tools Flash Bootloader Different data and diagnostic formats are used by different The Flash Bootloader lets you program ECUs with new software automotive OEMs for programming ECUs. Meanwhile, ODX and within an in-vehicle network. In particular, when the ECU is ODX-F have become established at some automotive OEMs as a mounted at a hard to access location in the vehicle, the Flash standard data format for ECU programming. Bootloader offers the advantage of updating ECU software without To master the many different data and diagnostic exchange for- needing to remove the ECU. This results in the following mats, Vector offers authoring and flash tools for specific use cases capabilities: in its CANdelaFlash and CANditoFlash products. > Reprogramming during the development phase > End-of-line programming Flashing CANopen ECUs > Software updating in the Service area (After Sales) Vector also offers Flash Bootloaders for the special requirements involved in flashing CANopen ECUs. Vector can adapt them to your Reprogramming is performed via CAN, FlexRay, MOST or Ethernet platform in the context of project work. utilizing a diagnostic protocol (UDS or KWP2000). A special LIN Flash Bootloader is available for LIN Slave ECUs. EEPROM Emulation Module (EepM) The EEPROM Emulation Module (EepM) lets you efficiently store Programming via XCP/CCP nonvolatile data of any desired length in program or data flash The use of XCP or CCP is an alternative to reprogramming with the memory. The module is called directly by the application. To save Flash Bootloader. This variant is primarily used to optimize ECU on resources, the module can be used by either the application or parameters. Since XCP/CCP programming is generally used in the the Flash Bootloader. development phase, unlike the Flash Bootloader, security aspects play a subordinate role here.

Security component ECUs can only be reprogrammed if the ECU has been unlocked beforehand with the help of a request/response (Seed/Key) method. As soon as the ECU is unlocked, it can also be reprogrammed with ECU software, even if it does not originate from the automotive OEM. Since the Request/Response method provides inadequate protection from a technical security perspective, special cryptographic methods are used in security-critical ECUs. Security requirements related to software manipulation pose the greatest challenge to the software. This optional extension of the Flash Bootloader that adds a security component provides maximum security and the

V2.3 2012-01 V2.3 2012-01 flexibility to set the security level required by the automotive OEM.

More Information: www.vector.com/contact EMBEDDED SOFTWARE

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 5/2

Flash Bootloader

ECU reprogramming via CAN, LIN, FlexRay, MOST and Ethernet

The Flash Bootloader permits reprogramming on single or multi- Overview of Advantages processor platforms. It includes a Multiple Memory Manager for > Efficient and reliable reprogramming of ECUs; without programming different memory types connected either internally having to remove the ECU or externally. Due to its low memory requirement, the Bootloader > Low memory requirement in the ECU is also well suited for microcontroller platforms that have limited > Available for most OEMs and many microcontroller resources. platforms > Security and data compression options available Functions > Proven flash solution based on over 10-years of use in The flash download is executed according to OEM requirements numerous development and production projects using either the KWP2000 or UDS diagnostic protocol. The Boot- loader contains the communication stack needed for the specific Application Areas bus system. The Vector Flash Bootloader is a universal and compact solution for quick, efficient and reliable reprogramming of ECUs during devel- > The flash procedure with the OEM Download Manager opment, while in production or while in service. It is available for In the ECU, the Bootloader is stored in a protected ECU memory CAN, LIN, FlexRay, MOST and Ethernet bus systems, and conforms area. After a reset, it is started as the first software instance in to specifications of automotive OEMs. The Flash Bootloader is the boot phase. It then checks whether a flash request or valid continually coordinated with the OEMs. application software exists. If the ECU is to be reprogrammed, the The Flash Bootloader consists of these components: Bootloader starts reprogramming via the OEM Download Manager. > Bootloader including OEM Download Manager and After verifying access authorization, the OEM Download Manager communication stack loads the flash driver from the bus system to the ECU’s RAM mem- 5/2 > Flash driver (HIS device driver) ory if needed. Then it erases the old ECU software and reprograms Reprogramming is executed with a flash tool such as vFlash from the flash memory with the new data it receives over the bus sys- Vector. Scripts needed for the Vector flash tools are supplied with tem. If the flash procedure is interrupted, it can be repeated at the Flash Bootloader. any time.

Flashing over CAN, LIN, FlexRay, MOST and Ethernet Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 5/3

FLASHING

Contact and Availability The Flash Bootloader is available for many commonly used microcontrollers and in OEM-specific variants. For more information go to: www.vector.com/fvd/ or contact us at: E-mail: [email protected] Telephone: +49 711 80670-400

> Bus-specific communication stack Configuration The Bootloader communicates with the flash tool via the bus- You configure the Bootloader with the GENy configuration tool, specific communication stack. For the CAN bus, a specially opti- adapting it to the specific requirements of your application. Fur- mized CAN driver with Transport Protocol (ISO-15765) is used to ther modifications and extensions are possible using callback economize on valuable resources; this also applies to LIN as well. functions in the Bootloader Application Layer. AUTOSAR communication modules from Vector are used for FlexRay and Ethernet/DoIP. A Network Services Library for MOST is used to Scope of Delivery flash over MOST. > Bootloader as configurable C source code > Flash driver for your specific hardware platform > Flash driver > GENy configuration tool The Flash Bootloader includes a flash driver that matches the > Flash scripts for controlling the download process hardware platform. It contains system-based routines for reliably > Documentation erasing and programming nonvolatile memory chips. All Vector flash drivers have low memory requirements, and they conform Flash Tools to the HIS standard “Functional Specification of a Flash Driver, To reprogram one or more ECUs, you can obtain the user- Version 1.3.” friendly vFlash tool from Vector. Its flexible approach lets it support various flash specifications for a wide variety of Options automotive OEMs without requiring modifications by the end > Security: For ECUs with sensitive vehicle data that needs to be user. For more information, please refer to the datasheet in protected from unauthorized manipulation the Diagnostics catalog. > Data compression: For quick re-programming of ECUs 5/3 For detailed information on these options, please refer to the ◆ relevant datasheet on the following pages.

Configuring flash blocks with GENy Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 5/4

Flash Bootloader: Option “Security (Crypto)”

Data encryption, validation and authentication during flash programming

Functions Overview of Advantages Option Security for the Vector Flash Bootloader meets the require- > Protection against unauthorized ECU access ments of HIS “Security Module Specification, Version 1.1.” The > Secure downloads following modules are available: > Efficient program execution monitoring by signature > Symmetrical data encryption based on the Advanced checking Encryption Standard (AES), class AAA > Computation of Hash codes with Hash function SHA-1 The Vector Flash Bootloader lets you program ECUs over a bus sys- (alternatively: RIPEMD-160, SHA-256, MD5). tem without having to remove the ECU. To prevent unauthorized > Validation and authentication of the download process by access during this process, the Flash Bootloader may use simple signatures per security classes C and CCC. or OEM-specific Seed/Key methods. This is sufficient for most Class C: The signature is generated in the flash tool by the H-MAC ECUs today. However, in the case of ECUs containing sensitive method with a confidential, symmetrical key, and it is verified in vehicle data such as an engine immobilizer function or odometer, the ECU. the Option Security (Crypto) modules are needed to implement Class CCC: The signature is generated externally by the RSA meth- extended security measures. The Hersteller Initiative Software od with a confidential private key. In the ECU, the signature is (HIS; “Manufacturers Software Initiative”) has specified crypto- opened with a public key and is verified. graphic routines with standardized interfaces in scalable security During ECU development, it is convenient to use the supplied classes for this purpose. HexView tool for signature computation. In production usage, the CANdelaFlash tool would be used to generate the entire ODX-F Application Areas container. Option Security for the Vector Flash Bootloader lets you efficient- 5/4 ly prevent flashing and unauthorized execution of protected soft- Scope of Delivery ware in the ECU. The option contains secure, qualitatively high- > Configurable C source code; integrated in the Bootloader end cryptographic functions from the company Cryptovision. > Tool HexView for efficient computation of the signatures Upon request, you can also obtain extended Seed/Key methods > Documentation for ECU access protection. ◆

Generating, transmitting and verifying a digital signature Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 5/5

FLASHING

Flash Bootloader: Data Compression Option

Fast Flash Programming

Functions Overview of Advantages The compression method used in this module enables a compres- > Reduced download times in flashing sion rate of 40–60%, where the rate actually attained depends on > Efficient decompression module for the ECU the flash data itself. Compression is performed with the supplied > Offers support in data compression tool HexView. > Bus system independent If compressed flash data needs to be transmitted, the flash tool must communicate this via diagnostics to the Bootloader in the With the Vector Flash Bootloader you can program ECUs via a bus ECU, afterwards the flash tool transmits the compressed data. system without having to remove the ECU. Compression and sub- After receiving the flash data, the Bootloader’s OEM Download sequent decompression of the flash data is recommended to Manager calls the decompression function, and then it programs reduce download time. the decompressed data in flash memory via the Multiple Memory Manager. Application Areas Some automotive OEMs specify the use of data compression in Scope of Delivery their flash procedures to accelerate the flash procedure at a con- > Configurable C source code; integrated in Bootloader stant baudrate. Compression of the flash data saves time even for > Tool HexView for compression of the flash data small quantities of data. Savings are maximized when flashing > Documentation large quantities of data (e.g. in the Infotainment area). Compres- sion also offers many benefits when short cycle times are speci- ◆ fied, as in end-of-line programming. The data compression option of the Vector Flash Bootloader lets 5/5 you efficiently compress all of your flash data. It utilizes an optimized LZ77 method and is especially well suited for use in automotive ECUs. Implementation in the Bootloader’s decompression module is very efficient in terms of execution time and memory. It is available on all microcontrollers for which a Bootloader is available.

Compression and decompression of flash data Vector Katalog ECU Software EN 09.02.2011 13:41 Uhr Seite 5/6

EEPROM Emulation Module (EepM)

EEPROM Emulation in Flash Memory

In recent years, flash memory has become more cost-effective access the stored data by identifiers that are predefined or flexi- and faster than conventional EEPROMs. New microcontrollers are bly defined at runtime. often offered without EEPROM memory and just have a larger internal flash memory. Since writing to flash memory, unlike Special Functions EEPROMs, is not by the byte but by the page, it is only possible to The EEPROM Emulation module is configurable and so it can be achieve optimized utilization of the flash memory with the help of adapted to the requirements of the application. It enables: an EEPROM emulation. > Simultaneous emulation of multiple EEPROMs > Integration of different flash hardware Overview of Advantages > Usable for external and internal flash > Usable for data and program flash Differences between EEPROMs and Flash Memory > Conserves resources and optimizes flash lifetime Flash memories cannot be written byte-by-byte. Their smallest > Possible to use EEPROM emulation module together with writing unit, known as a page, extends over a number of bytes. A the Vector Flash Bootloader page cannot be overwritten directly. First, it must be erased together with all of the pages of a sector (smallest erasing unit). The page length and sector length are hardware-dependent, and Application Areas sector lengths may also vary within a flash memory. Flash memory cannot be erased or written in the same way as conventional EEPROMs. EEPROM emulation in flash memory makes it Efficient Structuring of Nonvolatile Data possible for an application to store changed nonvolatile data in a Essentially, the use of a flash memory requires that the data to be flash memory, just as in a conventional EEPROM. stored is defined in so-called records. They are addressable by 5/6 unique identifiers, and besides the stored data they also contain Functions management information. This information assures quick and reli- The Vector EEPROM Emulation Module (EepM) manages predefined able read access to valid data. The application either defines the flash areas by taking all hardware-specific constraints into con- length of a record either statically during software configuration sideration. Reading and writing of changeable nonvolatile data or dynamically at runtime, depending on the configuration. via the EepM is fully transparent to the application. It is easy to

Software architecture of the EepM Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 5/7

FLASHING

Contact and Availability Vector offers EEPROM Emulation Modules for a number of hardware platforms with different internal or external flash memories. You will find additional information on the Inter- net at: http://www.vector.com/vi_eepm_availability_en or upon request E-mail: [email protected] Telephone: +49 711 80670 400.

Reliable Access Configuration In addition to the nonvolatile data, control information is stored The EepM is configured via a header file. in a record and includes a Cyclic Redundancy Checksum (CRC). This information assures that the data remains consistent with each Scope of Delivery access. If the application calls up nonexistent data, the EepM > C header files and source code generates an error message. > Makefiles and sample programs > Documentation/operating instructions/Readme file Optimizing Resources and Lifespan During configuration the reserved flash area is partitioned into Optional Services two blocks. The EepM sequentially writes new or updated records > Consultation in system design and integration in the ECU into the currently active block. When this block is full, the EepM > We supply HIS flash drivers completely erases the inactive block fully before it copies the still > We will extend standard modules according to your needs valid records of the active block into it. After an integrity check, > Hotline, special workshops and training courses on the topic of the inactive block becomes the active block. This alternating and embedded software ◆ consistent use of two blocks optimizes the lifespan of the flash memory.

The EepM can emulate multiple EEPROMs within a flash simultaneously using predefined context pointers. If a Vector Flash Boot- loader is integrated into the ECU, the context pointers make it possible to use the EEPROM Emulation module from the Flash 5/7 Bootloader.

Since all interrupts are blocked during access to flash memory, EEPROM management tasks should be performed at a non-critical time for the application. We would be glad to offer you consultation in system design.

Resource optimization by use of EepM from the Vector Flash Bootloader Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 5/8

Flashing with CCP and XCP

Using the CCP/XCP protocol for flash programming

Less widely used but technically feasible is the option of replacing Advantages the entire application by flashing via CCP and XCP. > Calibration and reprogramming with the same software component Failsafe reprogramming > Use CANape as a flash tool Unfortunately, the use of a flash kernel has one disadvantage: If > Reset-safe solutions are available the data transfer is interrupted during programming, this might lead to a catastrophic failure of the ECU. This can be remedied by The CAN Calibration Protocol (CCP) – and its successor, the Univer- using a CCP or XCP bootloader (see illustration, right). It is perma- sal Measurement and Calibration Protocol (XCP) – are ASAM nently stored in a protected memory area. The bootloader is Standards that are used to measure and calibrate internal ECU always called after the start, and it checks the application. The parameters. XCP offers several different physical interfaces such application is not started unless it is valid and complete. A flash as CAN, FlexRay, Ethernet, USB and SPI/SCI. The calibration tool abort always causes the bootloader to assume control, and the CANape from Vector supports all of these interfaces. flash process can be resumed at any time.

Application areas Tool support Flashing via CCP and XCP is primarily used to update calibration The flash download is executed by CANape. ◆ data and parameter data in the calibration process. After a change has been made to the data in the calibration tool, the new data is written to the ECU’s flash memory via the bus system. First, a flash kernel (see illustration, left) is transferred to the ECU, is written into RAM and is started by the application. Besides con- 5/8 taining the CCP and XCP protocols for communication, it also contains routines for erasing and programming flash memory. The subsequent download of ECU data is handled by the kernel, and the data is transferred to the flash chip. This achieves an especially space-saving solution.

Flashing via XCP using a flash kernel Flashing via an XCP bootloader Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 5/9

FLASHING

5/9 EMBEDDED SOFTWARE

Wide Availability of Flash Bootloader and EepM

Supported Microcontrollers and Compilers

Controller Compiler Available for [1] Controller Compiler Available for [1]

AnalogDevices H8S Renesas CAN BlackFin VisualDSP CAN M16C Renesas, IAR CAN Atmel M32C Renesas, IAR CAN AVR IAR CAN, LIN M32R Renesas CAN AVR32 IAR CAN R32C Renesas, IAR CAN Freescale R8C Renesas, IAR CAN DSP56F83xx Metrowerks CAN SH2, SH2-A Renesas CAN Cosmic, Metrowerks Renesas (NEC), HC08, MCS08 CAN, LIN V85x CAN, LIN, FlexRay (Hiware) Green Hills, IAR HC12, Star12, Cosmic, IAR, Metro- CAN STmicroelectronics Star12x, MCS12xE werks (Hiware) ST9 GNU CAN i.MX25 GNU CAN ST10 Tasking CAN MAC71xx, MAC72xx ARM, IAR CAN STM8a Cosmic CAN DIABDATA Wind MPC 55x, 56x, 5200 CAN River, Metrowerks STM32 CAN CAN DIABDATA Wind CAN, FlexRay, Texas Instruments MPC 55xx, 56xx River, Green Hills, Ethernet Metrowerks TI OMAP 59xx Texas Instruments CAN Fujitsu TMS320 Texas Instruments CAN 16FX Fujitsu CAN Texas Instruments, TMS470 CAN ARM 16LX Fujitsu CAN Texas Instruments, TMS570 CAN, FlexRay FR60 Fujitsu CAN ARM Jade GNU CAN Toshiba Infineon TLCS900 Toshiba CAN C16x (external Tasking CAN TX19 Green Hills CAN Flash) TX49 Green Hills CAN Tricore GNU, Tasking CAN, FlexRay

XC16x Keil, Tasking CAN [1] Please contact Vector ([email protected]) if your XC2000 Tasking, Keil CAN controller is not on the list or if you need additional support for a NXP not listed bus system. In general CAN, LIN, FlexRay, Ethernet and MOST can be supported. LPC 17xx GNU, Keil CAN

GNU, Keil, Green LPC 21xx CAN Hills The Flash Bootloader is available for a great variety of OEM-specific flash processes. Please find the list of supported OEMs in the separate Renesas Electronics (NEC/Renesas) datasheet. 78k0 IAR CAN, LIN 78K0R IAR CAN V2.2 2012-03

More Information: www.vector.com/contact EMBEDDED SOFTWARE

More Information: www.vector.com/contact Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 5/12

vFlash 1.1

(Re-)Programming easily and quickly – over CAN or Ethernet (DoIP)

laboratory, at programming stations, at a laboratory vehicle or in Overview of Advantages the vehicle. > Extremely easy to reprogram ECUs over CAN or Ethernet vFlash is very simple and does not require any expert knowledge (DoIP) to use – the user interface is tailored for flashing tasks. vFlash > Preconfigured flash projects can be exchanged readily – all may be used either interactively or by remote control. In the relevant data is packed in one file interactive mode, the user loads a project and starts program- > Flash projects are easy to create using templates ming by the push of a button. In remote control mode, vFlash can > Supports different protocols and flash sequences (based on be executed from the command line or controlled via a C pro- the specifications of many different automotive OEMs) gramming interface. > Direct “native” programming of data in Intel hex, Motorola-S vFlash is designed to process very large quantities of data. You and binary format can transmit 4 GB or more – or segments of very large binary data > Flash programming based on ODX-F sets – quite easily. Last but not least, the vFlash tool’s very fast > Flashing of compressed data transmission rate significantly reduces flash times in the case of > Supports interactive flashing (GUI) as well as batch large amounts of data. processing (C API) > Interacts perfectly with Vector Flash Bootloader Functions vFlash utilizes flash projects to save and exchange the configura- vFlash is a very easy-to-use tool for programming one or more tion to program individual ECUs. Flash projects contain all rele- ECUs. Because of its flexible approach, it can support the differ- vant settings and reference the data files to be programmed. ent flash specifications of a wide variety of automotive OEMs If the focus is on flexibility in changing the flash data, the without requiring modifications by the end user. referenced data files can simply be exchanged in background, e.g. 5/12 as part of an automated software build process. In this case, the Application Areas flash project remains unchanged. vFlash is designed for all users at automotive OEMs and suppliers If the focus is on a process-safe exchanging of flash configura- whose tasks include (re-)programming of ECUs. It supports ECU tions, the flash projects may be exchanged in the Pack&Go for- programming over CAN and over Ethernet (DoIP), either indi- mat. In this case, all relevant settings together with the data files vidually or in an ECU network group. vFlash lets users flash in the are packed in an archive file.

Flash process with vFlash Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 5/13

FLASHING

The user creates flash projects based on flash templates. A flash template defines the diagnostic services and presettings that are OEM-specific flash templates relevant to the flash process for a group of ECUs of a specific auto- Vector offers prepared flash templates for a number of differ- motive OEM (e.g. for a vehicle platform). In practice, the flash ent automotive OEMs. specifications of automotive OEMs differ enormously, not least of Please contact us at: www.vector.com/contact all due to the differences in diagnostic protocols and in-house flash standards. The advantage of flash templates concept is that System Requirements the differences described above remain largely hidden from the Windows XP (32-bit) Windows Vista (32 bit) user. Windows 7 (32/64 bit) Processor PC with min. 1.6 GHz PC with min. 1.6 GHz The reference flash process from Vector is also available as source RAM 1 GB 2 GB code (C#). This lets end users modify the flash sequence them- ◆ selves as necessary. All that is needed for this is Microsoft Visual Studio for C#; the Express Edition can be obtained from Microsoft free-of-charge.

Transfer rate Programming of 100 kByte data in 6.3 s (16.3 kByte/s) into an idealized reference ECU over CAN at 500 kBit/s with STmin = 0, BS = 0 5/13

Supported Hardware > XL interface product family (e.g. CANcardXL, CANcardXLe, CANcaseXL)

vFlash User Interface Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/a

VectorAcademy

Seminar or Workshop? Vector offers seminars and workshops on Vector software tools as well as the latest bus technologies and protocols at Vector Group locations worldwide. VectorAcademy seminars serve to communicate theoretical basics, while workshops distinguish themselves through their applicability, practical examples, and exercises.

Modularity Trainings are partly constructed of several independent, one-day modules designed to follow one another. Beginners and advanced users can adjust their individual training program to suit their own needs.

You will find the latest information on current dates, additions to the training offerings, and information about registration of the Vector Group at www.vector-academy.com.

Customer-Specific Trainings Additionally, we offer customized training courses, where we combine or expand the contents according to your needs. If desired we can also conduct all training courses at your company site. We would be glad to provide you with a quotation based on your specific needs. Please contact our training consultants: Vector Informatik: [email protected] 6/0 Vector Consulting Services: [email protected] Vector CANtech: [email protected] Vector Scandinavia: [email protected] Vector France: [email protected] Vector Japan: [email protected] Vector Great Britain: [email protected] Vector Korea: [email protected]

The Training Team Our training team consists of experienced engineers, who enjoy sharing their experience and knowledge base. A continuous flow of information between trainers and development departments ensures that the training courses we offer reflect current trends and developments.

Premises We conduct our trainings in generously appointed and modern classrooms, equipped with state-of-the-art training technology and powerful workstations, running the latest development, analysis, measurement, and diagnostics software. Excercise hardware and demonstration objects complete the working environment. Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/1

TRAINING

6/1 Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/8

Germany

6/8 Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/9

DIRECTIONS TO VECTOR

USA and Great Britain

Subsidiaries: Vector CANtech Inc., Vector GB Limited

6/9 Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/10

France and Sweden

Subsidiaries: Vector France S.A.S., VecScan AB

6/10 Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/11

DIRECTIONS TO VECTOR

Japan and Korea

Subsidiaries: Vector Japan Co., Ltd., Vector Korea IT Inc.

6/11 Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/12

India and China

Subsidiaries: Vector Informatik India Pvt. Ltd., Vector Informatik China

6/12 Vector Katalog ECU Software EN 09.02.2011 13:42 Uhr Seite 6/13

DIRECTIONS TO VECTOR

6/13 Your contact

Germany and all countries USA, Canada, Mexico not named below Vector CANtech, Inc. Vector Informatik GmbH Suite 550 Vector Consulting Services GmbH 39500 Orchard Hill Place Ingersheimer Str. 24 Novi, MI 48375 70499 Stuttgart USA GERMANY Tel.: +1 248 449 9290 Tel.: +49 711 80670-0 Fax: +1 248 449 9704 Fax: +49 711 80670-111

France, Belgium, Luxembourg Japan Vector France Vector Japan Co., Ltd. 168, Boulevard Camélinat Seafort Square Center Bld. 18F 92240 Malakoff 2-3-12 Higashi-shinagawa, FRANCE Shinagawa-ku Tel.: +33 1 4231 4000 Tokyo 140-0002 Fax: +33 1 4231 4009 JAPAN Tel.: +81 3 5769 7800 Fax: +81 3 5769 6975

Sweden, Denmark, Norway, Korea Finland, Iceland Vector Korea IT Inc. VecScan AB 1406 Mario Tower Theres Svenssons Gata 9 222-12 Guro-dong, Guro-gu 41755 Göteborg Seoul 152-848 SWEDEN REPUBLIC OF KOREA Tel.: +46 31 764 7600 Tel.: +82 2 8070 600 Fax: +46 31 764 7619 Fax: +82 2 8070 601

United Kingdom & Ireland India Vector GB Limited Vector Informatik India Prv. Ltd. Rhodium, Central Boulevard 4/1/1/1, 3rd floor, Sutar Icon Blythe Valley Park Sus Road Solihull, Birmingham Pashan West Midlands, B90 8AS Pune 411021 United Kingdom India Tel.: +44 121 50681-50 Tel.: +91 20 2587 2023 Fax: +44 121 50681-69 Fax: +91 20 2587 2025

China Vector Informatik GmbH Shanghai Representative Office Unit 1701, Sunyoung Center No. 398 Jiangsu Road Changning District Shanghai 200050 P.R. CHINA Tel.: +86 21 6432 53530 Fax: +86 21 6432 5308

F www.vector.com F Get Price Quote