Catalog ECU Software en

Product Catalog
ECU Sof tware
ENGLISH
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 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 1992 1994 1996 1997 1998 1999 2001 2002 Founding of Vector Informatik GmbH Sale of the first CANalyzer license Vector has more than 25 employees Sale of the first CANoe and CANape license Founding of Vector CANtech, Detroit/USA Founding of Vector Japan, Tokyo/Japan, Vector Informatik is DIN EN ISO 9001:1994 certified Vector has more than 100 employees worldwide Move to the new company building in Stuttgart, Founding of Vector Consulting Vector Informatik is DIN EN ISO 9001:2000 certified, Founding of Vector France, Paris/France, Founding of VecScan, Gteborg/Sweden, Vector has more than 250 employees worldwide Vector has more than 400 employees worldwide Move to the second company building in Stuttgart, Founding of customer care center north in Braunschweig and customer care center south in Munich/Germany Vector has more than 500 employees worldwide Founding of office in Regensburg/Germany Vector has more than 600 employees worldwide Vector has more than 700 employees worldwide Start of construction for the third company building in Stuttgart/Germany Founding of Vector Korea, Seoul/Rep. of Korea Vector has more than 800 employees worldwide Move to the third company building in Stuttgart Founding of Vector Great Britain, Birmingham Founding of Vector Informatik India, Pune Opening of Representative Office Shanghai, China aquintos becomes part of the Vector Group High Customer Satisfaction The delivery quality and delivery time as well as consulting competence from Sales, Support, and Consulting are not just maintained on a high level, but are constantly being improved. The success: our customers judge us on a scale of 1 to 5 (where 1 is the best grade and 5 the worst) with an average grade of 1.6. Excellent Working Atmosphere 70 % of our highly-qualified employees work in the development environment. Teamwork in modern structures ensures a working atmosphere that in the past few years has been judged very good according to internal surveys. Trainees, interns, and graduating students also profit from the many opportunities to work actively with the newest technologies. Employee turnover at Vector, which has been extremely low for many years, confirms how each person at Vector understands his or her work: as mental work with a fun factor. On Location Worldwide For Vector, partnership with its customers means understanding their requirements. In order to be responsive to our partners quickly and to be able to act purposefully, we are present worldwide. For optimal support on location, the Vector Group has established, in addition to its own locations, a globe-spanning network of distributors.
2003 2004
2005 2006 2007
2008 2009
2010
VECTOR XXXXXXXXXXXX THE COMPANY
1/1
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) and communication modules for e.g. CAN, LIN, FlexRay and Ethernet. Software for memory management and for reprogramming of
ECUs. Basic software for AUTOSAR. Development services for software components.
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: catalog@vector.com Development of Distributed Systems Tools and Services to design and develop a network of ECUs. Tools to simulate, analyze and test the communication of the network. ECU Testing Tools and services that allow the test of ECUs in all development phases, check the functionality of prototypes or execute regression and conformity tests. ECU Calibration Tools to access the ECU at run-time. This allows acquiring and modifying measurement data and parameters, so the ECU algorithms can be modified and optimized. Process Management Tools and Services to support the process management required to develop complex vehicle electronics. This includes qualification of human resources, coaching, and supplying special tools that allow the management of complex data, workflows and projects. Vehicle Diagnostics Tools to describe, implement and test the diagnostic functionalities that are required to run diagnostic services on an ECU. Diagnostic functionalities are set up during the ECU development, stored in a consistent database and used during the ECUs lifecycle.
Bus Systems, Embedded Network Protocols, Standards and appropriate Vector Products
1/2
Bus System CAN Description CAN (Controller Area Network) was developed by the Robert Bosch GmbH in the early eighties and was internationally standardized (ISO 11898) in 1994. CAN was specifically developed for the serial data exchange between electronic control units in automobiles but is also used for the realization of industrial microcontroller networks. LIN (Local Interconnect Network) has been developed especially for the cost-efficient communication of intelligent sensors and actuators in automobiles. LIN bus system characteristics: > master/slave architecture > time-controlled data transmission > single-wire data transmission max. 20 kBaud > synchronization mechanism integrated in the protocol (no expensive quartz needed) Application Area Automotive engineering, automation engineering Appropriate Vector Product All Vector Products Page
LIN
Automotive engineering (body electronics bus e.g. networking within a seat)
CANalyzer.LIN/CANoe.LIN CANalyzer/CANoe Option SCOPE CANape CANbedded LIN Communication Embedded Gateway Flash Bootloader CANister CANlog 3/4 GL1000, GL3000/4000/4200 MICROSAR LIN Multilog Network Designer LIN VN8900 XL-Interface-Family
3/8 3/12 5/2
2/18
MOST
MOST (Media Oriented Systems Transport) has been developed especially for the transmission of multimedia data in automobiles. MOST bus system characteristics: > optical data transmission up to 25 Mbit/s > ring structure of the bus system > usage of the standardized XML Function Catalog > plug&play capability FlexRay has been designed as a bus system for all securityrelevant applications as well as for transmission of large amount of data in automobiles. FlexRay bus system characteristics: > data transmission up to 10 Mbit/s > redundant implementation of all networks > deterministic transmission behavior As an exchange format for tools for the configuration of bus communication (design, parameterization) with FlexRay, the XML based FIBEX format (Field bus Exchange) is predominantly used.
Automotive engineering (multimedia applications; networking of infotainment devices e.g. tuner, DVD changer, etc.) Automotive engineering (e.g. securityrelevant applications, brake-by-wire, highspeed backbone for other bus systems)
CANalyzer.MOST CANoe.MOST 5/2 Flash Bootloader 2/22 MICROSAR MOST Multilog VN2610 USB-Interface for MOST
FlexRay
CANalyzer.FlexRay CANape CANoe.FlexRay Flash Bootloader FlexCard Cyclone II SE/E-Ray FRstress MICROSAR FR Multilog Network Designer FlexRay VN3300, VN3600 and VN7600 FlexRay-Interfaces Appropriate Vector Product AUTOSAR Evaluation Bundle AUTOSAR Services AUTOSAR Basic Software Modules AUTOSAR Tools MICROSAR DIAG CANalyzer.CANaero CANoe.CANaero
5/2 2/16
Protocol resp. Description Exchange Format AUTOSAR The goal of the development partnership, founded by leading automotive OEMs and suppliers, is the definition of an open reference architecture for ECU-specific software.
Application Area Automotive ECUs, basic software
Page 2/2 2/54 2/6 2/44 2/28
ARINC 8xx CANaerospace
ARINC 810 and 812 specify communication between modules in the on-board galley (Galley Master, Galley 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).
Avionics and space technology
BUS SYSTEMS, EMBEDDED NETWORK PROTOCOLS, STANDARDS AND APPROPRIATE VECTOR PRODUCTS
Protocol resp. Description Exchange Format J1939/ ISO11783 J1939 is a communication protocol based on CAN for realtime data exchange between electronic control units (ECUs) in the area of commercial vehicles. It describes the information exchanged between the ECUs in such a system. ISO11783 is a further development for agricultural engineering. NMEA 2000 is a communication protocol based on J1939 from the National Marine Electronics Association (NMEA) for the realtime data exchange between electronic control units in maritime electronics. SAE J1708 defines a serial, bidirectional network for use in the commercial vehicle industry. The SAE J1587 Standard regulates communication and standardized data exchange between different ECU based on SAE J1708 networks. The CANopen profile family specifies standardized communication mechanisms and device functionalities. CANopen is maintained by CAN in Automation (CiA), and can be implemented free of license.
Application Area Commercial vehicle engineering, railway engineering, agricultural engineering Marine engineering
Appropriate Vector Product CANoe.J1939 CANalyzer.J1939 CANoe.ISO11783 CANbedded J1939 CANape CANoe.J1939 CANalyzer.J1939 CANbedded J1939 CANoe/CANalyzer.J1587
Page
3/6
NMEA 2000
1/3
3/6
J1587/ J1708
Commercial vehicles engineering
CANopen
Automation engineering, CAN embedded
CANoe.CANopen CANalyzer.CANopen CANerator CANopen ProCANopen CANeds CANopen Master Source Code CANopen Slave Source Code PassThru XL Library
3/28 3/20 3/24
J2534
The SAE J2534 standard defines the re-programming of ECUs via a PassThru interface. The purpose of this standard is to provide a unified communication capability via a standardized PC interface basically intended for flashing but also for diagnostics and other purposes. Ethernet-based networks and the protocols built upon them are used in IT networks for decades. In the meantime they continue to grow in importance in the embedded environment. The main focus is on transmission of periodic signals and real-time capability. XCP is an improved and generalized version of the CAN Calibration Protocol V2.1. (CCP). XCP can be used also in nonCAN networks (e.g. FlexRay, SPI, SCI). The main benefit of XCP is the independence concerning the transport layer. Keyword Protocol 2000 (KWP2000; ISO 14230) and Unified Diagnostic Services (UDS; ISO 14229) are standardized diagnostic protocols for electronic control units. The physical access to the ECU is possible via a serial connection (K-line KWP-on-K-Line) or via CAN (KWP-on-CAN, UDS-on-CAN). The ODX format (Open Diagnostic Data Exchange) is based on the ASAM-MCD-2D-Basic working draft. Manufacturers of vehicles, electronic control units, and testers can write and exchange electronic control unit data in the uniform ODX format, which covers all manufacturers.
Vehicle ECUs, Diagnostics, PassThru re-programming
Ethernet/IP
Car2x, vehicles engineering, automation engineering, factory automation Automotive engineering, development of electronic control units, measurement and calibration Diagnostics of vehicle electronic control units, measurement and calibration
CANoe.IP CANalyzer.IP MICROSAR IP
2/20
XCP/CCP
CANape XCP software component CANoe Option XCP GL1000, GL3000/4000/4200 CANape CANdelaStudio CANdesc CANoe CANoe.DiVa vFlash Indigo CANdelaStudio CANdelaFlash ODX Studio CANape CANoe CANoe.DiVa vFlash Indigo RP1210 API
3/30
KWP2000/ UDS
3/14 5/12
ODX
Diagnostics of vehicle electronic control units
5/10
5/12
RP1210
The RP1210 specification defines an open interface (API) between Windows-based applications and in-vehicle communication networks. This interface offers functionality for bus systems such as CAN and J1708 as well as for higher layer protocols such as J1939 and J1587.
Commercial vehicles engineering, engine control
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: catalog@vector.com
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 of Distributed Systems ECU Software Components Process Management
Vector Product ASAP2 Editor ASAP2 Lib ASAP2 Tool-Set AUTOSAR Basic Software (MICROSAR) CANalyzer CANape Option Adv. Multimedia Option GPS Option Simulink XCP Server CANbedded CANbedded Gateway CANbedded J1939 CANbedded LIN CANdb++ Admin.J1939 CANdbLib CANdelaStudio CANdelaFlash CANdesc CANdito CANeds CANerator CANopen CANextender CANgraph CANister CANlog 3 and 4 CANoe CANoe.DiVa CANopen Master Source Code CANopen Slave Source Code CANscope CANstressD/DR
ECU Testing
Diagnostics
ECU Calibration ++ ++ ++
Page

++
2/2
++ + + + + + ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ ++ + ++ ++ ++ + ++ ++ + ++ + + ++ ++ ++ ++ ++ ++ ++ +

3/2 3/12 3/6 3/8

5/10 3/14

3/28

3/20 3/24
APPLICATION AREAS OF THE VECTOR PRODUCTS
Vector Product COMPASS DaVinci Component Tester Configurator Pro Configurator Kit Developer eASEE.cdm eASEE.rqm eASEE.pm eASEE.chm eASEE.sdm EEPROM Emulations Modul Flash Bootloader FlexCard Cyclone II FRstress GL1000, GL3000/ 4000/4200 High Resolution Timer Indigo Multilog Network Designer CAN/LIN/FlexRay ODX Studio osCAN PassThru XL Library ProCANopen RP1210 API Test Automation Editor Timing Analyzer vFlash VN2610 USB Interface for MOST VN3300, VN3600, VN7600 Interfaces for FlexRay VN8900 VT System VX1000 XL-InterfaceFamily (e.g. CANcardXL, CANcaseXL, )
Development of Distributed Systems
ECU Testing
Diagnostics
SteuergerteECU Calibration Kalibrierung
SteuergerteECU Software SoftwareComponents Komponenten
ProzessProcess management Management ++
Seite Page
2/46 2/50 2/52 2/44
++ ++ ++ ++ + ++ ++ ++ ++ ++ ++ + ++ ++ ++ ++ + ++ ++ ++ ++ ++ ++ + ++ + ++ ++ ++ ++ ++ ++ ++ + ++ ++ ++ ++
1/5

5/6 5/2

4/4

4/2

4/6 5/12
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: catalog@vector.com
Use of Standardized Basic Software for ECUs

Supported Hardware Platforms and Vehicle Manufacturer (OEMs)
1/6
Overview of advantages > Support of the standards AUTOSAR, ISO, HIS, IEC, OSEK, SAE, etc. > Available in numerous OEM-specific variants > Proven algorithms used in production development at all OEMs > Support of many different hardware platforms via a standardized API > Customization of basic software for your use case > Simple, tool-supported configuration You can get mature standardized basic software from Vector for ECU communication, diagnostics, real-time operating systems, flashing, EEPROM programming and control of IO drivers. This solution lets you port your application conveniently and quickly onto different hardware platforms and for different OEMs. 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.
Application Areas You can obtain basic software from Vector for the following use areas: > Hardware drivers for CAN, LIN, FlexRay, Ethernet, Flash, EEPROM, Timer, ADC, PWM, etc. > Communication software for CAN, LIN, FlexRay, Ethernet and MOST > Gateway solutions for CAN, LIN, FlexRay, Ethernet and MOST > Administration of nonvolatile data (EEPROM, Flash) > Diagnostics with error memory module > Watchdog > Flash Bootloader > Operating system > Calibration protocols XCP and CCP > Higher protocols: J1939, CANopen, etc. Hardware For the latest list of supported hardware platforms for automotive software please visit our e-catalog: www.vector.com/ecat_es The list for CANopen can be found on the product pages for the Master and Slave source code: www.canopen-solutions.com
ECU 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
OEMs and brands from A-Z (1) > Alfa Romeo, Aston Martin, Audi > BAIC, Bentley, BMW, Brilliance, Bugatti, Buick > Cadillac, Chery, Chevrolet, Chrysler, Citroen, Claas > DAF, Dongfeng, Daimler, Daimler Commercial Vehicles > FAW, FAW-VW, FCC, Ferrari, Fiat, Fisker, Ford > GAC, Geely, GMC, GM-Daewoo > Holden, Honda, Hummer, Hyundai (HMC) > Isuzu > Jaguar > Kia > Lamborghini, Lancia, Land Rover, Lincoln > MAN Commercial Vehicles, Maybach, Mazda, Mercedes, Mercury, Mini, Mitsubishi > NAC, Nanjing MG, Nissan > Opel > Peugeot, Pontiac, Porsche, PSA > Renault > Saab, SAIC, Saturn, Scania, Seat, Skoda, Smart, Suzuki, SsangYong > TATA > Vauxhall, Volkswagen, Volvo, Volvo AB, VW Commercial Vehicles
If your OEM is not included in the list, please contact your Vector Sales representative. Vector can develop basic software for other automotive OEMs and brands upon request. An independent variant of the basic software is available for non-OEM-specific communication.
1/7
(1)
Revision level: January 2011
Technical Consulting/Engineering Services

Individual support in the development of ECU software and vehicle networks
1/8
Overview of Advantages > Tailored support > Quick implementation of your application > Sustained build-up of know-how For over 15 years, Vector has been creating software components as well as professional tools, and has been successfully supporting customers worldwide in developing ECU software and networking ECUs. Our experts bring success to your project with individually tailored technical consulting and engineering services. Starting with your aspired goals, our engineers work together with you to plan and implement an individual package of services. In every phase of development, our consultation and support is entirely based on your needs. Projects are handled in close coordination with your project team and based on a process that is optimally aligned to your needs. This lets you attain maximum relief of work load and ideal transparency. Application Areas > ECU Software Development > Vehicle Networks Design
ECU Software In developing your ECU software with our embedded standard software, such as CANbedded or MICROSAR, we can provide the following support: > Product-related Software Engineering Services In conjunction with Vector embedded software products, which you use in your development, we can offer you professional support with training, support, review, installation and coaching, which we would also be glad to provide at your business site. > Technical consulting In taking on your technical challenges, our expert team provides you with technical consulting or individual concept development. Our technical consulting, e.g. in the framework of joint workshops, helps you in tasks such as these: > Introducing a new operating system > Optimizing an existing software architecture > Porting your application software to a multi-processor ECU > Layout of safety-related mixed SIL systems > Migration of ECUs to FlexRay or AUTOSAR > 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
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 Integration Package (EIP) via the development of system functions and software integration to the take-over of overall responsibility for all application software. For a detailed description of our service line-up in the area of ECU software, please refer to the datasheets on AUTOSAR Services and Software Development Services. 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
> Engineering Services Beyond technical consulting, we would also be glad to handle all of the project related development tasks such as: > Specification of CAN, LIN and FlexRay based vehicle networks > Specification of individual communication protocols > Creating and maintaining communication relationships between the ECUs > Specifications of gateway components
1/9
Services for Vehicle Networks
Software Engineering Services

Professional Support for your ECU software
1/10
Overview of Advantages > Take advantage of our expertise in embedded standard software for your project > Quick implementation of the communication, diagnostics and flash download for initial sample submission to the OEM > Tailored support from entry-level to the take-over of entire software projects For over 15 years, Vector has been developing software components and professional tools and has been successfully supporting customers worldwide in the development of ECU software. Vector is the market leader in OEM-specific standard software, e.g. for communication, diagnostics, operating systems, flash download and low level drivers. Many OEMs and their suppliers are already benefiting from our know-how. Our experts bring success to your project too with individually tailored software engineering services. Application Areas > Extended Integration Package (EIP): Extended integration of the 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
Extended Integration Package (EIP) The Extended Integration Package is a predefined project scope for integration of OEM-specific standard software on your ECU. It offers an efficient entry into your project and enables early and successful execution of initial network testing at the OEM. It includes: > Installation of the basic software on your ECU hardware with the help of a sample application > Specification-conformant configuration of the standard software and the OEM-specific system modules > Test execution with the OEM-specific tool chain > Test reports on fulfillment of OEM specification requirements The following functions are started up with the EIP: > Communication on the vehicle bus, including control of the start and stop states as well as sleep and wake-up > Basic diagnostic functionality including implementation of error memory entries concerning communication errors (e.g. timeout, bus-off) > Flash download using an EEPROM emulation in RAM memory
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 Perhaps you want to focus more on your application development and are seeking a partner to assume responsibility for implementing a portion of your software project. We can offer you project support tailored to your individual needs. The project is executed in close cooperation with your project team and is based on a process that is optimally aligned to your needs: from prototype to serial production. If you need safety-related software, the development can be performed according to ISO DIS 26262. Model-based software development can also be performed. Using our support, you get maximum work load relief and ideal transparency on the current status of the project. We integrate the standard software on your ECU hardware under consideration of your design and OEM requirements. In addition, we link it completely to your software application. We would be 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
> Development of the entire diagnostic software component (SWC) > Development of sensor and actuator software components > Integration of the flash bootloader, even for multi-processor systems In addition, project services include: > Creating documentation such as requirements specification, design documentation, MISRA reports, test specifications > Project control by project and release planning, project report, status reports, quality gates and production release by Vector Complete Application Software Perhaps you do not wish to develop your application software yourself and are seeking a partner that can handle its implementation for you? We would be glad to assume responsibility for executing an entire ECU software project.
1/11
Vector can develop individual system functions or the entire application software
Solutions for AUTOSAR
2/0
The core idea of AUTOSAR is to master the growing complexity of software in modern vehicles by standardization. The development partnership founded by leading automotive OEMs and suppliers set the goal of defining an open reference architecture for ECU software. Many advantages are realized by standardization and using clearly specified interfaces between the basic software modules to the functional software : e.g. re-usability of the same software for different microcontrollers and functions with a simultaneous increase in quality. Vector, your Trusted Partner for AUTOSAR Projects As one of the first premium members of the AUTOSAR Consortium, Vector has been actively involved in the development of new technology for a long time. This active participation was recognized by the AUTOSAR Consortium in awarding Vector the first AUTOSAR Premium Member Award in 2007. Vectors experience with AUTOSAR is also reflected in AUTOSAR tools and the basic software, which is already being used in numerous production projects. Overview of the Vector AUTOSAR Solution Vector supports you in all development phases of projects with tailor-made AUTOSAR solutions for design, development and implementation:
DaVinci The AUTOSAR Tools from Vector > DaVinci Developer is the optimal tool for graphic-based definition of AUTOSAR software components and for configuration and generation of the MICROSAR RTE. > DaVinci Component Tester lets you conveniently test AUTOSAR software components on a PC. > DaVinci Configurator Pro is used to create a consistent configuration of the MICROSAR basic software from Vector and of basic software from third-party suppliers. The proven GENy tool is used for the communication modules. > DaVinci Configurator Kit optimally supports you in integrating modules you have developed (e.g. complex device drivers) in DaVinci Configurator Pro. MICROSAR The AUTOSAR Basic Software Modules from Vector With MICROSAR, Vector offers AUTOSAR-conformant software modules for efficient development of production-mature ECUs. They are based on AUTOSAR Release 3.x and cover all aspects of the AUTOSAR standard. Practice-based extensions and features implemented in anticipation of AUTOSAR Release 4.0 complete this solution, e.g. with support of Ethernet, encrypted communication, FlexRay IsoTp, XCP and J1939. In partnership with TTTech Automotive, Vector can already offer you software modules for end-to-end communication validation of ISO DIS 26262 Integrity Level D per AUTOSAR 4.0.
AUTOSAR
When choosing the AUTOSAR solution from Vector: > You benefit from a seamless tool chain: From the design of your system to the development of your functional software and integration of the software in your ECU. > With MICROSAR you get a complete set of basic software from a single source, which you can use individually or in conjunction with third-party components. > Vector, together with its partner TTTech Automotive, offers you a reliable solution for safety-relevant ECUs per ISO DIS 26262. > You do not need to migrate to AUTOSAR all at once. Vector can show you solutions for stepwise migration without loss of quality. > You are choosing a future-oriented solution with a reliable partner. Further Tools Take advantage of the comprehensive Vector tool chain to develop your AUTOSAR ECUs and systems. > The eASEE Automotive Solution lets you specify and manage in-vehicle electronic systems. This ranges from defining requirements to designing distributed functions and defining components such as sensors, actuators and ECUs. Data communication in the networks can also be defined with eASEE. > Network Designer is used to design a vehicles networking architecture and data communication for the networks.
> CANdela Studio lets you specify the diagnostic functionality of your ECUs. Vector can offer you a complete solution for your projects together with numerous other tools for ECU testing as well as measurement and calibration. The Easy Way to Get Started with AUTOSAR Besides training courses on fundamentals and on specific products, Vector also offers on-site support in project implementation and in introducing the AUTOSAR software. The AUTOSAR Evaluation Bundle from Vector gives you a solution for prototype development of AUTOSAR systems. It offers a structured approach for training in the AUTOSAR methodology and gives you an opportunity to evaluate the functionality and performance of the AUTOSAR software. Support for Your Projects Vector accompanies you from the early evaluation phase to production projects. Together with you, we can develop a comprehensive solution for your ECU. In the process, it does not matter whether you are using Vector products, your own in-house developments or third-party components. We support your projects with experience and integration know-how.
2/1
>> CONTENTS
AUTOSAR Evaluation Bundle MICROSAR MICROSAR OS MICROSAR COM MICROSAR CAN MICROSAR FR MICROSAR LIN MICROSAR IP MICROSAR MOST MICROSAR MEM MICROSAR SYS MICROSAR DIAG MICROSAR CAL MICROSAR EXT 2/2 2/6 2/10 2/12 2/14 2/16 2/18 2/20 2/22 2/24 2/26 2/28 2/32 2/34 MICROSAR IO MICROSAR RTE MICROSAR Safe Identity Manager for AUTOSAR DaVinci Developer DaVinci Component Tester DaVinci Configurator Pro DaVinci Configurator Kit AUTOSAR Services 2/36 2/38 2/40 2/42 2/44 2/46 2/50 2/52 2/54
EMBEDDED SOFTWARE
AUTOSAR Evaluation Bundle

The complete package for the evaluation of AUTOSAR basic software and tools
Overview of advantages > Production-quality tools and basic software per AUTOSAR Release 3.x, to implement a complete set of ECU software > Enables realistic evaluation of execution time and memory requirements for your ECU project > Conveniently test your software components on a PC on the Virtual Function Bus level > Available for many different micro-controllers and the PC as runtime platform > Quick way to train in AUTOSAR with a detailed sample project > Support of both AUTOSAR-conformant files and conventional description files The AUTOSAR Evaluation Bundle is a comprehensive package of AUTOSAR basic software and design and configuration tools from Vector. This package lets you develop entire ECU software with an AUTOSAR-conformant software architecture. You get an in-depth look into the AUTOSAR world from the design and configuration process to implementation of the actual basic software. Application Areas The AUTOSAR Evaluation Bundle supports both the automotive OEM in evaluating AUTOSAR processes and methods and suppliers in creating their first AUTOSAR-conformant ECU software. Since the tools and basic software are at a level of production
maturity, you can reliably use the Vector solution to evaluate AUTOSAR with regard to: > Efficiency of the basic software > Integration of the tools in your development environment > Potential uses of AUTOSAR concepts in your application area The AUTOSAR Evaluation Bundle also provides an optimal foundation for initial developments of AUTOSAR-conformant software components for service providers who focus on the application level. If your focus is on evaluation of the AUTOSAR method and tools, you can obtain the AUTOSAR Evaluation Bundle with MICROSAR CANoe Emulation as well. In this case, you would use the PC with the CANoe test and development tool from Vector as the runtime platform and can work without startup of real hardware. Nonetheless, you work with the same methods, tools and basic software as in the development of a real ECU. Functions The AUTOSAR Evaluation Bundle contains all tools and software from Vector for creating a complete set of AUTOSAR ECU software, which consists of software components (SWCs), Runtime Environment (RTE) and basic software (BSW). The DaVinci tools are tailored to AUTOSAR and simplify your work in designing complex AUTOSAR applications. As input for configuring the MICROSAR software, you would use an ECU Extract of System Description
AUTOSAR Tools
AUTOSAR Basic Software
Additional Tools
V2.4 2011-05
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
(AUTOSAR XML) or as an alternative a conventional network description file (DBC, FIBEX, LDF). > The DaVinci Developer tool gives you an easy way to generate AUTOSAR-conformant ECU applications. Using the graphic editor, you can describe your AUTOSAR software components quickly and clearly and define their interfaces. The SWCs serve as a basis for the RTE configuration process, which you also perform with DaVinci Developer. > The DaVinci Component Tester is used to conveniently test on a PC - implementation of the SWCs. Based on SWC description files, you can emulate a complete Virtual Function Bus (VFB). > The DaVinci Configurator Pro tool is used to configure the basic software modules. You can use the convenient and intuitive user interface to adapt parameter values for your ECU project. The GENy tool offers special support in configuring the communication basic software. > The CANdelaStudio tool is used to define diagnostic data for your networks and ECUs. You can export this data via standard formats, and use the data in automatic configuration of the MICROSAR diagnostic basic software. The MICROSAR basic software modules contained in the AUTOSAR Evaluation Bundle implement all functions of AUTOSAR Release 3.x and many extensions, efficiently and flexibly. The modules are bundled in these functionally interrelated MICROSAR products: MICROSAR RTE > Contains the AUTOSAR RTE (Runtime Environment)
MICROSAR OS Contains the AUTOSAR basic software module Operating System (OS) > Implementation of Scalability Class SC1 (SC2-SC4 available as option if supported by processor) > Fully compatible with OSEK OS > Supports Schedule Tables MICROSAR SYS Contains the AUTOSAR basic software modules > Communication Manager (COMM) > Cyclic Redundancy Check Routines (CRC) > ECU Manager (ECUM) > Development Error Tracer (DET) > Watchdog Manager (WDGM) > Watchdog Interface (WDGIF) > Scheduler Module (SCHM) > Basic Software Mode Manager (BswM, available as option) MICROSAR DIAG Contains the AUTOSAR basic software modules > Diagnostic Event Manager (DEM) > Diagnostic Communication Manager (DCM) > Function Inhibition Manager (FIM) MICROSAR MEM Contains the AUTOSAR basic software modules > NVRAM Manager (NVM)
Designing software components with DaVinci Developer
Configuration of the Basic Software with DaVinci Configurator
EMBEDDED SOFTWARE
> Memory Abstraction Interface (MEMIF) > EEPROM Abstraction (EA) > Flash EEPROM Emulation (FEE) MICROSAR CAN Contains the AUTOSAR basic software modules > CAN Interface (CANIF) > CAN Transport Protocol (CANTP) > CAN Network Management (CANNM) > CAN State Manager (CANSM) MICROSAR J1939TP (available as option) Contains the transport protocols > BAM - Broadcast Announce Message > CMDT - Connection Mode Data Transfer MICROSAR FR (available as option) Contains the AUTOSAR basic software modules > FlexRay Interface (FRIF) > FlexRay Transport Protocol (FRTP) > FlexRay Network Management (FRNM) > FlexRay State Manager (FRSM) MICROSAR LIN (available as option) Contains the AUTOSAR basic software modules > LIN Interface (LINIF) > LIN Transport Protocol (LINTP, contained in LINIF)
> LIN State Manager (LINSM) MICROSAR COM Contains the AUTOSAR basic software modules > Communication (COM) > Network Management Interface (NM) > PDU Router (PDUR) > I-PDU Multiplexer (IPDUM) available as option MICROSAR IO Contains the AUTOSAR basic software modules > IO Hardware Abstraction (IOHW) MICROSAR CAL Contains the AUTOSAR basic software modules > General Purpose Timer Driver (GPTDRV) > Watchdog Driver (WDGDRV) > Microcontroller Unit Driver (MCUDRV) > EEPROM Driver (EEPDRV) > Flash Driver (FLSDRV) > CAN Driver (CANDRV) > LIN Driver (LINDRV, available as option) > FlexRay Driver (FRDRV, available as option) > SPI Driver (SPIDRV) > Input Capture Unit Driver (ICUDRV) > Pulse Width Modulation Driver (PWMDRV) > A/D Conversion Driver (ADCDRV)
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.
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
> PORT Driver (PORTDRV) > Digital IO Driver (DIODRV) MICROSAR EXT Contains the AUTOSAR basic software modules > CAN Transceiver Driver (CANTRCV) > FlexRay Transceiver Driver (FRTRCV) > LIN Transceiver Driver (LINTRCV) MICROSAR Safe (optional) Complete solution for safety relevant functional software according to ISO DIS 26262. Additional Included Features > Sample application in source code, and a detailed guide on its use > AUTOSAR Training at Vector (4 days) Further Options The AUTOSAR Evaluation Bundles CAN, LIN and FlexRay may be used with one another in any combination. Upon request, Vector can support you with extensive MICROSAR Coaching at initial startup and during integration of the MICROSAR basic software in your application. Vector can also provide coaching at your business site.
Available Hardware Platforms The AUTOSAR Evaluation Bundle is available for the most commonly used 16-bit and 32-bit hardware platforms. Due to the hardware dependency of the MICROSAR CAL modules and the MICROSAR OS, binding statements cannot be made without specific processor device numbers. The Vector Sales Team would be glad to provide this information. MICROSAR CANoe Emulation As an alternative, Vector also offers the AUTOSAR Evaluation Bundle for CANoe as a PC runtime platform. In this case, emulations of the MICROSAR CAL modules and the MICROSAR OS are included. The flash memory of the AUTOSAR ECU is also emulated. The EEPDRV is not needed in this case, and so it is not provided.
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 device 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
EMBEDDED SOFTWARE
MICROSAR
The Vector Solution for AUTOSAR ECU Software
Overview of Advantages > All AUTOSAR basic software from a single source > Many innovative extensions perfectly tuned to one another > Reliable foundation for your AUTOSAR ECU software > Already in production use at leading OEMs and TIER1 suppliers > Simplifies development of platform-independent functional software > Available for many hardware platforms and automotive OEMs > Mature and long-term solution from an AUTOSAR Premium Member MICROSAR is the AUTOSAR solution for your ECU software. MICROSAR consists of the MICROSAR RTE and MICROSAR basic software modules (BSW), which cover all aspects of the AUTOSAR standard and many extensions. Each AUTOSAR BSW module is assigned to a MICROSAR package. For detailed descriptions of individual packages and the MICROSAR RTE, please refer to the separate datasheets. Vector combines the BSW modules needed in individual software integration packages. Application Areas The BSW modules of the MICROSAR packages assure basic functionality of the ECU. They contain the implementations of AUTOSAR standard services you will need for your functional software. You are able to develop your functional software platform independ-
ently, because the AUTOSAR architecture follows a consistent strategy of hardware abstraction. Modules from the MICROSAR OS and MICROSAR CAL packages are hardware-dependent. Vector offers these modules for a large number of different hardware platforms and compilers, e.g. to enable quick change-out of the controller device. The operating system MICROSAR OS is available for single core and multi coreprocessors. Based on its ongoing contacts with OEMs, Vector is able to offer a number of OEM-specific BSW modules such as the diagnostic modules. You can configure all necessary MICROSAR BSW modules based on your projects requirements, and after generation you can integrate them with the functional software. This produces a complete set of ECU software. If the functional software consists of AUTOSAR-conformant SWCs, you will need a run-time environment (RTE). The MICROSAR RTE handles communication between the SWCs and their access to data and services from the BSW modules. Along with managing the entire flow of information, the MICROSAR RTE also assures consistency in the exchange of information. Properties Development of the MICROSAR basic software modules is founded on the Vector development process for standard modules, which is
V2.3 2011-06
The MICROSAR packages contain all modules of the AUTOSAR standard
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
based on SPICE. All MICROSAR packages offer the following features: > Efficient memory utilization and short execution times > Available for production use > Conformant to AUTOSAR Release 3.x > Assistants and timely checks support you in achieving consistent configuration of your basic software > Scalable, adaptable to your specific application > Optimally integrated into your development process > AUTOSAR Monitoring for testing and analysis of ECUs > User-selectable configuration point (pre-compile, link-time or post-build) > Communication stack is versatile in its use > Supports multiple ECUs > Optional delivery as source code > Together with MICROSAR Safe: well-suited for safety-relevant functions (ISO DIS 26262) Production Use The MICROSAR BSW modules are already being used in production projects. MICROSAR lets you benefit from Vectors many years of experience in implementing embedded standard software. Before delivery, all MICROSAR Software modules undergo systematic integration tests for the specific conditions of your application (hardware platform, compiler, processor device, OEM, with/without RTE, etc.). Upon request, these tests may be
extended to cover software modules from third-party producers (e.g. MCAL drivers). AUTOSAR Release 3.x and Extensions All MICROSAR basic software modules fundamentally conform to AUTOSAR Release 3.x. In addition, it is possible to integrate MCAL drivers of different AUTOSAR Releases. The packets MICROSAR OS Multi-Core, MICROSAR J1939 and XCP as well as the modules from MICROSAR IP already contain important functionality from Release 4.0. Moreover, the MICROSAR MOST package lets you connect any AUTOSAR ECU to a MOST ring. All of these extensions are compatible with the rest of the MICROSAR basic software modules of Release 3.x. Consistent and Simple Configuration With AUTOSAR, the work of manually developing or adapting the basic functionality of ECU software is replaced by configuration of the BSW modules. The intuitive, user-friendly and well coordinated AUTOSAR tools from Vector (DaVinci) support the user in this process. Multi User Support of the DaVinci tools enables simultaneous work on a project by multiple users. The DaVinci tools require an ECU Extract of System Description file as input. It is also possible to produce a configuration based on commonly used network description files (DBC, FIBEX, LDF, etc.). Early in the configuration process, all DaVinci tools check the validity of individual parameters, complex parameter groups and
DaVinci tools are used to consistently configure the MICROSAR RTE and MICROSAR BSW modules
EMBEDDED SOFTWARE
their interrelationships. In case of invalid configurations, the tools make recommendations for corrections, if possible. This extension of the AUTOSAR method simplifies integration of the basic software in your ECU and reduces integration time. For more details on DaVinci tools from Vector, please refer to the relevant datasheets. > You can configure the MICROSAR BSW modules with DaVinci Configurator Pro. Vector recommends the proven GENy configuration tool for configuring the communication-related MICROSAR modules. GENy is supplied with DaVinci Configurator Pro. GENy enables cross-module configuration of specific parameters and parameter groups. This saves you time compared to step-wise configuration of individual BSW modules; it also ensures a compatible configuration of interdependent modules. > The MICROSAR RTE is configured with DaVinci Developer, the design tool for SWCs. Scalability In addition to fulfilling AUTOSAR requirements, the MICROSAR BSW modules also provide a number of functional extensions. The extended configuration options let you deactivate unnecessary functions to optimize the MICROSAR code for your application. This scalability makes the MICROSAR modules the optimal solution for both small and challenging applications. MICROSAR is already being implemented in a wide range of ECUs, such as steering angle sensors, door ECUs, engine ECUs, central gateways, etc. MICROSAR may also be used with other operating systems such as Linux or QNX.
Flexible Development Process With the DaVinci tools it is possible to execute a top-down configuration or a bottom-up configuration to integrate the MICROSAR products in your development process. A combination of the two approaches offers optimal results. Bottom-up is especially well-suited to MICROSAR DIAG and MICROSAR IO, while topdown is ideal for the other MICROSAR BSW modules. In the bottom-up approach, the configuration of the interfaces of the functional software is done by using the basic software. This involves using DaVinci Developer to automatically generate SWC service ports (including runnables) based on BSW service ports. This approach gives you quick training in AUTOSAR, and you can create your first functionally-capable ECU in a short period of time. In the top-down approach, DaVinci Developer is used to connect the ports of the SWCs via service mapping to the ports of the BSW modules in part automatically. This reduces configuration effort significantly. AUTOSAR Monitoring AUTOSAR Monitoring simplifies testing and analysis of ECUs with such tools as CANape or CANoe. The MICROSAR A2L Generator generates an A2L file for this purpose. This contains the description of important RTE-internal variables such as Send/Receive ports, internal states of the MICROSAR BSW modules and of COM signals. In testing, you read them out at runtime with XCP.
You use DaVinci Configurator Pro to configure the BSW modules
You use DaVinci Developer to create the MICROSAR RTE for your application
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
User-Selectable Configuration Point The configuration point of all MICROSAR basic software modules is user-selectable. Per AUTOSAR Configuration Conformance Classes CCC1 to CCC3, you can select the configuration point for each BSW module; choices are: pre-compile, link-time or post-build. GENy offers optimal process support for the post-build configured communications-related MICROSAR modules. Post-build lets you replace certain parameter values from the communication matrix without compiling in the ECU. GENy has a special graphic mode that is exclusively used to edit post-build parameters. Afterwards, GENy generates platform-specific HEX files, which can be flashed directly to the ECU. The MICROSAR BSW modules check for compatibility of the replaced configuration at runtime. ECU Variants To save on logistical costs in AUTOSAR ECUs, the MICROSAR modules can be delivered with the optional Identity Manager. This option lets you develop physical multiple-ECUs within a car line or multi-configuration of ECUs that are used in different car lines. For more information, see the datasheet on the AUTOSAR Identity Manager. Safety according to ISO DIS 26262 For use of the MICROSAR BSW in safety-related functions, Vector together with TTTech Automotive offers a complete solution for
your AUTOSAR ECU. For more information, please refer to the MICROSAR Safe datasheet. Optional Delivery of Source Code 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. Other Services > Consulting on system design > Extension of standard BSW modules per customer wishes > Development of customer-specific software components (SWC) > Support in adapting existing functional software > Complete software integration in your ECU including thirdparty software > Migration of existing software to AUTOSAR > Hotline, special workshops and training courses on the topic of embedded software and AUTOSAR
List of available MICROSAR Packages > MICROSAR OS AUTOSAR operating system > MICROSAR SYS Basic ECU functions > MICROSAR DIAG Diagnostics > MICROSAR MEM Memory Management > MICROSAR COM Network independent communication > MICROSAR CAN Communication via CAN > MICROSAR LIN Communication via LIN > MICROSAR FR Communication via FlexRay > MICROSAR IP Communication via Ethernet > MICROSAR MOST Communication via MOST
> MICROSAR CAL
AUTOSAR conform controlling of the microcontroller peripherals > MICROSAR IO Direct connection of the microcontroller peripherals to the application > MICROSAR EXT Controlling external hardware > XCP Measurement and calibration of an AUTOSAR-ECU using XCP incl. transport layer for Ethernet, FlexRay und CAN > MICROSAR J1939TP Operation of an AUTOSAR ECU in J1939 networks (BAM, CMDT) > MICROSAR Safe Solution for safety-relevant application software according to ISO DIS 26262
MICROSAR OS
The Real-Time Operating System for the AUTOSAR Standard
2/10
Overview of Advantages > Small, quick and resource-economizing operating system > Short boot times > MICROSAR OS provides an ideal runtime environment for embedded software and forms the basis for migration to AUTOSAR-conformant applications > Supplied as source code > Numerous auxiliary functions simplify software development > Quality process per SPICE Level 3 > Graphic configuration tool for easy configuration of the operating system > TimingAnalyzer for runtime analysis of MICROSAR OS applications > Available for many 8, 16, 32 and 64 bit microcontrollers > Available as multi-core operating system, too MICROSAR OS is a pre-emptive real-time multitasking operating system with optimized properties for use on microcontrollers. Vectors many years of experience in developing operating systems and drivers for microcontrollers are bundled into this small, robust operating system core. Properties MICROSAR-OS is based on the AUTOSAR OS specification, an extension of the practice-proven OSEK/VDX-OS operating system
standard. This standard was extended to include functions for time monitoring and memory protection as well as functionalities that support distributed applications in networks. MICROSAR OS is fully conformant to the AUTOSAR OS specification and supports all scalability classes: SC1: Real-time operating system implemented per the OSEK/VDXOS standard and extended to include schedule tables SC2: Real-time operating system with time synchronization and monitoring of the time behavior of individual tasks and interrupt service routines SC3: Real-time operating system with memory protection mechanisms on microcontrollers with suitable hardware support SC4: Combines scalability classes SC2 and SC3 Multi-core: Operating system for multi-core processors. Scalability classes SC1 through SC4 are supported. Functions > Synchronization with the global system time Schedule tables can be synchronized with the global system time, e.g. the time transmitted over the FlexRay bus. This makes synchronized and simultaneous execution of tasks possible in a distributed system. > Memory protection (SC3, SC4) Memory protection protects memory areas so that applications can be reliably integrated. It ensures that the data of other applications are not destroyed.
MICROSAR OS Modul
AUTOSAR
Training In the framework of our training program we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. For more information on individual training events and dates please visit: www.vector-academy.com
Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www.microsar.com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact
> Timing Protection (SC2, SC4) Timing protection ensures that assumptions made in the early design phase related to execution times are preserved during runtime as well. When protection encounters a defective application section, this does not have any negative effects on other running applications. > Execution time measurements (SC2, SC4) You can use functions of scalability classes 2 and 4 to measure the execution times and interrupt disable times of applications. These measured data can later be used as practice-based values in designing and integrating future applications. > TimingAnalyzer Design Assistance TimingAnalyzer design assistance computes the task execution schedule, checks for conformance to execution time restrictions and represents the schedule tables in a well-organized graphic display. Analysis is performed for every task and every interrupt with the following information: Priority, period, execution time and end time. The graphic user interface visualizes system behavior clearly and concisely.
Optional Extensions > High Resolution Timer If resolutions finer than 1ms are needed for the timers, the mechanisms of the High Resolution Timer are advisable, which implement this precision without simultaneously increasing interrupt load. Depending on the controller, this may enable resolutions into the microseconds range. > High Resolution Synchronization for Schedule Tables In some applications, it is necessary to synchronize and trigger schedule tables with very high precision using internal or external signal sources. The High Resolution Synchronization option gives you resolutions in the microsecond range without increasing interrupt load. Scope of Delivery > Operating system core as source code > Graphic configuration and generation tool for Windows XP/Vista/Windows 7 > Command line based generator > BSW modules description > Description files for DaVinci Configurator Pro > Documentation > TimingAnalyzer
2/11
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
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.
EMBEDDED SOFTWARE
MICROSAR OS Multi-Core
AUTOSAR operating system for multi-core processors
Overview of Advantages > Supports symmetrical and asymmetrical multi-core processors > Fast and stable kernel > Easy migration of OSEK/VDX-based projects due to compatible API > Memory protection and timing protection available Application Areas You use MICROSAR OS Multi-Core whenever developing a multicore system according to the AUTOSAR specification. Typical requirements of a multi-core system are: > Greater computing performance at the same oscillator frequency > A safety concept based on separate processing of application components > A safety concept based on redundancy, i.e. parallel processing of the same algorithms > Reduced power consumption by reducing the oscillator frequency Multi-core processors satisfy these requirements without requiring any additional space on the PC-board. Functions The functions and interfaces correspond to the functions of MICROSAR-OS. In addition, the Multi-Core variant offers various
mechanisms for coordinating and synchronizing tasks running on different cores. > Inter-Core Coordination Processes on different cores are synchronized by task activations, setting of events, starting and stopping of alarms or Schedule Tables. > Shared Resource Access Access to shared resources is synchronized by Spinlocks. > Inter-Core Communication The operating system provides an efficient interface for consistent data exchange between two cores in the form of the Inter-OS Application Communicator (IOC). Optional Extensions > Memory protection (SC3, SC4) Memory protection ensures that the data of different applications do not corrupt one another. This makes integration of applications simpler and more reliable. > Timing protection (SC2, SC4) Timing protection ensures that a defective application section will not impair other processes that are running.
V2.0 2011-03
Architecture model of a multi-core application with MICROSAR OS Multi-Core and MICROSAR Basic Software
EMBEDDED SOFTWARE
MICROSAR COM
AUTOSAR Basic Software Modules for Communication
2/12
Overview of Advantages > Code and execution time optimized by application-specific configuration > Very efficient signal access via function macros > Contains important functionality of AUTOSAR Release 4.0 and many other useful extensions > Extended support for NM coordinators > NM module: OSEK NM compatibility is configurable > Supports simultaneous operation of AUTOSAR NM and OSEK NM in NM migration projects The basic software modules (BSW) of MICROSAR COM include AUTOSAR services for ECU communication. These services can support any number of communication channels. They are bus-independent and are needed in every communication stack. Per AUTOSAR architecture, they handle control and full integration in the ECU software of bus-specific communication modules from MICROSAR CAN, MICROSAR FR, MICROSAR LIN, MICROSAR IP and MICROSAR MOST. Application Areas MICROSAR COM lets users develop their functional software by a fully bus-independent approach. All necessary tasks for transmitting messages and for cross-bus network management activities are handled by the configurable BSW modules COM, NM, PDUR and IPDUM from MICROSAR COM.
For a gateway ECU, you do not need any additional software. The COM and PDUR BSW modules from MICROSAR COM enable routing of signals and TP or application messages. Functions The BSW modules from MICROSAR COM contain functions defined in AUTOSAR Release 3.x: > Services of the COM module organize transmission of messages according to their send type (cyclic, event-triggered, etc.). A key task is to implement bus-independent signals of the functional software in PDUs. > The PDU Router (PDUR) distributes the PDUs to the bus-specific AUTOSAR communication modules, so that they can transmit the information. In the opposite direction, the PDUR receives the PDUs and routes them to the relevant services of the NM, COM or DCM modules or to other networks (gateway). > The Generic Network Management Interface (NM) bundles inter-bus network management activities of all of the ECUs communication channels. As NM coordinator, it synchronizes wake-up and sleep of the communication channels. > Optionally, a user may use an I-PDU Multiplexer (IPDUM) in the communication stack of the ECU software. IPDUM supports multiple usage of fixed I-PDUs with variable data contents.
MICROSAR COM Modules
AUTOSAR
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 please visit: www.vector-academy.com
The following functions are optionally available: > COM: TX deadline monitoring > PDUR: TP layer fan-out and zero cost operation > PDUR: Transmit cancellation and change parameter request Furthermore, the BSW modules from MICROSAR COM contain the following functionalities. Some of them are part of AUTOSAR Release 4.0 (ASR 4.0): > COM: Indication and timeout flags for signals and signal groups > COM: Signal conversion. This conversion may be configured with an A2L ASAP2 database. > COM: Invalidity declaration of TX signals in case of RX signal timeout > COM: Deactivation of the TX confirmation interrupt > COM: Pre-compile optimizations such as function macros for very efficient signal access > COM, PDUR: Transport of long I-PDUs and signals via CANTP and via J1939 as specified in ASR 4.0. Other TPs are available upon request. > COM: Extension by signal callout functions, e.g. to integrate gateways as complex device drivers. > PDUR: Generic interface for integrating a TP and bus communication as complex device driver > PDUR: Intra-ECU communications for TP connections > PDUR: Optimized routing per ASR 4.0 (e.g. with Burst Transmission) together with CANTP or optimized routing as extension to ASR 3.0 together with CANTP and FRISOTP
> NM: Synchronous sleep and wake-up of multiple networks via different NM coordinators > NM: Backup coordinator > NM: Pre-compile optimizations such as function macros > NM: Support of OSEK NM (configurable) > NM: Mixed operation of OSEK and AUTOSAR-NM on one channel Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/XP/Vista/ Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR solution from Vector 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.
2/13
Configuring the COM module with GENy
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, CANTP, CANSM and CANXCP. Application Areas MICROSAR CAN is used to handle communication in CAN networks. It is also well-suited as a foundation for calibration with XCP, gateways or flashing. You can also combine MICROSAR CAN with the separately available MICROSAR J1939TP package to enable operation of an AUTOSAR ECU in a J1939 network. The BAM and CMDT transport protocols are available for this. Overview of Advantages > Code and execution time are optimized based on needspecific configuration > Inter-module configuration of all communication-specific software modules > Fast wakeup handling at ECU startup > Includes high-performance gateway functionality > CANTP: ISO 15765-2 compatibility is configurable > CANNM: OSEK NM compatibility is configurable > Optionally available: J1939 Transport Layer, BAM and CMDT
2/14
Functions The BSW modules in MICROSAR CAN contain functions defined in AUTOSAR Release 3.x. The following functions are available as options for the CANIF module: > Support of an external CAN controller > Increased number of Full CAN objects by combining multiple CAN controllers on one physical CAN bus (Common CAN) > Individual polling of messages in Full CAN objects > Support of multiple Basic CAN objects to further optimize acceptance filters > Rx queue for short interrupt execution times In addition, BSW modules from MICROSAR CAN or MICROSAR J1939TP contain the following extensions. Some of them are from AUTOSAR Release 4.0 (ASR 4.0): > CANIF: Double hash search algorithm for filtering the Rx messages > CANNM: Pre-compile optimizations, e.g. for single-channel systems > CANSM: Optimization of the wakeup process by wakeup detection at ECU startup > CANSM: Support of ECU Passive Mode > CANSM: Extended Callback Interface for the error states BusOff Begin and BusOff End
MICROSAR CAN modules
AUTOSAR
> CANSM: Checks whether states were successfully set in the CAN driver (CANDRV) or CAN transceiver driver (CANTRCV). In case of error, an automatic repetition is executed. > CANTP: Supports full duplex communication > CANTP: Supports mixed addressing (11 bit CAN ID); typically for CAN/LIN gateway applications > CANTP: Optimized routing per ASR 4.0 (e.g. with Burst Transmission) together with the PDUR from MICORSAR COM. > CANTP: ISO 15765-2 compatibility is configurable > CANTP: Sets BlockSize and STmin at runtime > BAM and CMDT: Transport protocols for J1939 networks available as option Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector 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. 2/15 Other MICROSAR Products for a Complete CAN Communication Stack Based on the AUTOSAR architecture, a complete communication stack for CAN can be formed using MICROSAR CAN together with the BSW modules from the separately available MICROSAR COM, MICROSAR CAL and MICROSAR EXT packages. To interface MICROSAR CAN to the application and the hardware, you will still need the following BSW modules: > Hardware-specific CAN driver (CANDRV) from MICROSAR CAL > Hardware-specific transceiver control (CANTRCV) from MICROSAR EXT > General communication modules (COM, NM, PDUR, IPDUM) from MICROSAR COM Modules in MICROSAR CAL and MICROSAR EXT are available for many microcontrollers and transceivers. Other relevant MICROSAR Products for CAN > DCM and DEM from MICROSAR DIAG > DET, ECUM and COMM from MICROSAR SYS > XCP
Vector offers a comprehensive range of products and services for your CAN projects
EMBEDDED SOFTWARE
MICROSAR FR
AUTOSAR Basic Software Modules for FlexRay Communication
Vector offers you MICROSAR FR, an AUTOSAR-conformant package for FlexRay communication. It contains the following BSW modules defined in the AUTOSAR architecture: FRIF, FRNM, FRTP or FRISOTP, FRSM and FRXCP. Application Areas MICROSAR FR is used to handle communication in FlexRay networks. Furthermore, it is ideal as a foundation for calibration with XCP, gateways or flashing. Overview of Advantages > Small code size and short execution times due to optimized administration of job lists of the FlexRay interfaces > Either the FRTP (AUTOSAR) or FRISOTP (ISO 10681) transport protocol may be used > Support of ECU passive mode in the FlexRay State Manager > Early detection of synchronization losses Functions The BSW modules in MICROSAR FR contain functions defined in AUTOSAR Release 3.x. In anticipation of AUTOSAR Release 4.0 (ASR 4.0), MICROSAR FR also includes the BSW module FRISOTP, conformant to ISO 10681. It is compatible with the rest of the MICROSAR BSW modules, and upon request it can replace FRTP in your FlexRay communication stack. The following functions are available as an option:
> FRISOTP: Unknown Message Length Transmission > FRIF: Dual Channel Redundancy for redundant transmission of frames as well as PDU-specific voting functions for the SWCs In addition, the BSW modules from MICROSAR FR contain the following services. Some of them are part of ASR 4.0: > FRDRV: Optimized wakeup during operation (WUDOP) > FRDRV & FRIF: Support of the following ASR 4.0 APIs: GetChannelStatus, GetClockCorrection, CancelTransmit, GetSyncFrameList, ReadCCConfig and LpdU reconfiguration > FRDRV & FRIF: FIFO support > FRIF: Automatic repetition of job list execution in case of errors or loss of bus synchronization > FRISOTP: Optimized TP routing for gateway operation (ASR 4.0) > FRNM: Pre-compile optimizations, e.g. for single-channel systems, Direct sending of NM user data from the COM module > FRNM and FRSM: Detection and recovery from synchronization losses (Long/Short Term Sync) (ASR 4.0) > FRSM: Support of ECU Passive Mode (ASR 4.0), immediate startup after passive wakeup (ASR 4.0), extended error handling by State Change Notification, configurable time delay for FlexRay startup at passive wakeup as well as configurable number of wakeup patterns (ASR 4.0) Operating System FlexRay basic software modules can be used entirely without an operating system. However, it makes sense to use an AUTOSAR OS
V2.5 2011-02
EMBEDDED SOFTWARE
Training In the framework of our training program, we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. For more information on individual training events and dates please visit: www.vector-academy.com
Contact and Availability You can 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 versions as well as customized support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact
or a conventional OSEK-OS (e.g. Vector osCAN). Ideally suited for FlexRay applications is MICROSAR OS from Vector. Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/ XP/Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector 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 FlexRay Communication Stack Based on the AUTOSAR architecture, a complete communication stack for FlexRay can be made with MICROSAR FR together with the BSW modules from the separately available MICROSAR COM, MICROSAR CAL, MICROSAR SYS and MICROSAR EXT packages. You
will also need the following BSW modules to interface MICROSAR FR to the application and hardware: > Hardware-specific FlexRay driver (FRDRV) from MICROSAR CAL > Hardware-specific transceiver control (FRTRCV) from MICROSAR EXT > General communication modules (COM, NM, PDUR, IPDUM) from MICROSAR COM The modules in MICROSAR CAL and MICROSAR EXT are available for many different microcontrollers and transceivers. Other MICROSAR Products for FlexRay > DCM and DEM from MICROSAR DIAG > DET, ECUM and COMM from MICROSAR SYS > XCP Additional Services > Consultation in system design > Integration of basic software in existing ECUs > Extension of standard modules per customer requirements > Development of customer specific AUTOSAR software components (SWC) > Hotline, special workshops and training events on the topic of embedded software and AUTOSAR
Vector offers a comprehensive portfolio of products and services for your FlexRay projects
MICROSAR LIN
AUTOSAR Basic Software Modules for LIN Communication
MICROSAR LIN contains the BSW modules defined in the AUTOSAR architecture for LIN communication: LINIF, LINTP, LINSM. Per AUTOSAR, LINTP is a component of LINIF. Application Areas MICROSAR LIN is used to handle communication tasks for a LIN Master in a LIN network. In addition, it may be used as a foundation for gateways or flashing. Overview of Advantages > Core component of the complete LIN communication stack for AUTOSAR ECUs > Optimized routing of diagnostic requests to LIN Slaves > Quick start of the LIN channel > Reliable switching of schedule tables possible > Based on Vectors many years of experience with production software for LIN
2/18
> LINIF: Configurable wakeup delay > LINIF/LINSM: Production/Development Error Reporting (DEM/DET) has been extended by additional and more precise events > LINIF and LINTP: Separately configurable memory mapping of configuration data for LINIF and LINTP. This is especially appealing for controllers with segmented memory. The MICROSAR LIN product includes two separate generators for LINIF and LINTP for this purpose. > LINTP: Extends gateway functionality for precise switchover of the schedule tables for diagnostic requests and responses > LINSM: Extended interface for monitoring the LINSM submodes for controlled switchover of the LIN schedule tables > LINSM: Optimized startup behavior by automatic selection of a schedule table (configurable) Configuration With GENy support, the user can acquire information on the connected LIN1.3 and LIN2.x Slaves. This information is saved in the ECU Configuration Description and is considered when configuring the master. This lets the master evaluate the response error bits sent by the slaves and then initiate the associated DEM events.
Functions The BSW modules in MICROSAR LIN contain functions defined in AUTOSAR Release 3.x. In addition, BSW modules from MICROSAR LIN contain the following services. Some of them are specified in AUTOSAR Release 4.0 (ASR 4.0):
MICROSAR LIN modules
AUTOSAR
Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector 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.
> Hardware-specific LIN driver (LINDRV) from MICROSAR CAL > Hardware-specific transceiver control (LINTRCV) from MICROSAR EXT > General communication modules (COM, PDUR) from MICROSAR COM The modules in MICROSAR CAL and MICROSAR EXT are available for many different microcontrollers and transceivers. Other Relevant MICROSAR Products for LIN > DET, ECUM and COMM from MICROSAR SYS
2/19
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 application and hardware, you will still need the following BSW modules:
Vector offers you a comprehensive range of products and services for your LIN projects
MICROSAR IP
AUTOSAR Basic Software Modules for Communication over Internet Protocol via Ethernet
2/20
The Internet Protocol (IPv4) based on TCP/IP via Ethernet represents a very widely used standard for transporting data at high rates. Standardization of this Internet technology for use in automotive projects is part of AUTOSAR Release 4.0. In its MICROSAR IP, Vector is providing this as a supplement to AUTOSAR 3.x. The package contains BSW modules for Ethernet communication defined in the AUTOSAR architecture: ETHXCP, SOAD, ETHSM, ETHIF. In addition, it contains the base package for IPv4: IPBASE. Application Areas With MICROSAR IP in the ECU and a conventional PC as a communication partner, you can do the following with no extra hardware other than an Ethernet cable: > Quickly flash large quantities of data, > Simultaneously and efficiently measure and calibrate many parameters with XCP on Ethernet, > Perform vehicle diagnostics per ISO 13400-2 (DoIP) over IP, > Conveniently access vehicle data, > In future: Intelligent charging of batteries (Smart Charging according to ISO/IEC 15118 The superior data throughput of Ethernet enables enormous reductions in overall flash and diagnostic times. However, it 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 other MICROSAR packages.
Overview of Advantages > Supports Internet Protocol IPv4 > Compatible with AUTOSAR Release 3.0 > Contains both UDP and TCP protocols > Configurable number of sockets > Execution time advantages due to reduced number of copying operations > Supports Diagnostics over IP (DoIp) per ISO 13400-2 > Data is exchanged up to 200 times faster than over a conventional High-Speed CAN interface Functions The BSW modules in MICROSAR IP contain functions defined in AUTOSAR Release 4.0. In addition, MICROSAR IP contains AUTOSAR 3.x compatible interfaces which assure compatibility to the rest of the MICROSAR BSW modules. > ETHIF: The AUTOSAR Ethernet Interface enables hardwareindependent control of the various Ethernet drivers. > ETHSM: The AUTOSAR Ethernet State Manager handles activation/deactivation of the microcontroller and transceiver. > ETHXCP: Ethernet-specific transport layer for XCP (Universal Calibration Protocol) per the ASAM standard > IPBASE: The basic package for IP contains all necessary modules from the RFC standard: Socket, UDP, ICMP, ARP and IPv4. The modules DHCP and TCP are available as an option. Modules from IPBASE assure basic functionality of the TCP/IP protocols
MICROSAR IP modules
AUTOSAR
Training In the framework of our training program, we can offer various training courses and workshops on MICROSAR at our classrooms or at your business site. For more information on individual training events and dates please visit: www.vector-academy.com
Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules, go to: www.microsar.com/availability/ We would be glad to provide you with information on OEMspecific versions and customized support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact
per AUTOSAR requirements. The IPBASE modules are optimized to minimize the number of copying operations. This property offers tremendous execution time savings in gateway routing, in flash routines, XCP and diagnostic applications. > SOAD: The Socket Adapter implements the communication via PDUs defined in AUTOSAR as socket-oriented communication (TCP/IP). SOAD also contains the diagnostic functionality defined in ISO 13400-2 (DoIP). Configuration MICROSAR IP is configured with the familiar configuration tool GENy. IP-specific configuration parameters are saved as an extension in the ECU Configuration Description. Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW module description > DLLs for configuration with GENy > Documentation
The complete AUTOSAR Solution from Vector 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 Relevant MICROSAR Products Based on the AUTOSAR architecture, a complete communication stack for Ethernet is formed with MICROSAR IP together with the BSW modules from the separately available MICROSAR COM, MICROSAR CAL and MICROSAR EXT packages. You will also need the following BSW modules to interface MICROSAR IP to the application and hardware: > Hardware-specific Ethernet driver (ETHDRV from MICROSAR CAL) > Hardware-specific transceiver control (ETHTRCV from MICROSAR EXT) > General communication module (PDUR) from MICROSAR COM Modules in MICROSAR CAL and MICROSAR EXT are available for many different microcontrollers and transceivers. Other Relevant Products for Ethernet > DCM and DEM from MICROSAR DIAG > DET, ECUM and COMM from MICROSAR SYS > XCP
2/21
Vector offers you a comprehensive portfolio of products and services for your IP projects
MICROSAR MOST
AUTOSAR compatible Basic Software Modules for MOST Communication
Previously, MOST (Media Oriented Systems Transport) was not part of the AUTOSAR standard. Vector now offers MICROSAR MOST, an AUTOSAR-compatible embedded software solution for your MOST application. It contains the BSW modules MOSTIF and DISP. 2/22 Application Areas MICROSAR MOST lets you connect AUTOSAR ECUs to a MOST ring to exchange data on the control and asynchronous channel. In addition, MICROSAR MOST contains all of the services required to implement gateway functionality to CAN, LIN, FlexRay and Ethernet buses. BSW modules from MICROSAR MOST are interfaced to the application software in a way similar to CAN, LIN or FlexRay, and the product is fully compatible with the AUTOSAR architecture. MICROSAR MOST is interfaced to the MOST bus via a Network Services Library and a low level driver (MOSTDRV). Overview of Advantages > Extends AUTOSAR features to include MOST communication > Flexibly routes messages and signals between MOST buses and any desired networks > Provides seamless interface to a Network Services Library for MOST > Supports MOST 150
Functions The MOST-specific BSW module MOSTIF and the Dispatcher (DISP) template are Vector-specific extensions of the AUTOSAR standard: > MOSTIF: MOST Interface for hardware-independent conversion of the PDUs to be transmitted to MOST frames. MOSTIF is compatible with the BSW modules of AUTOSAR Release 3.x. > DISP: The Dispatcher is a template for interfacing the MOSTIF module to a Network Services Library for MOST. The BSW modules from MICROSAR MOST are offering the following services: > Support of signal, message and TP routing > Sending signals on MOST via Notification Services > Support of MOST protocols MHP and AMS Operating System MOST basic software modules can be used entirely without an operating system. However, it is advisable to use an AUTOSAR OS or a conventional OSEK-OS (e.g. Vector osCAN). The MICROSAR OS from Vector is ideally suited for MOST applications. Configuration MICROSAR MOST is configured with the familiar GENy configuration tool. MOST specific configuration parameters are saved as an extension in the ECU Configuration Description.
MICROSAR MOST modules
AUTOSAR
For gateways, in particular, Vector offers customized solutions that take into account the special aspects of OEM-specific data formats in configuration. Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW module description > DLLs for configuration with GENy > Documentation The complete AUTOSAR Solution from Vector 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.
To interface this communication stack to a MOST bus, a Network Services Library and a low level driver (MOSTDRV) are also necessary. These two components are not included with the MICROSAR MOST product. Low-Level Driver In the framework of project work, Vector would be glad to create a Low-Level Driver for interfacing the Network Services Library for MOST to your specific hardware. 2/23
Other Relevant MICROSAR Products for MOST > DCM and DEM from MICROSAR DIAG > DET, ECUM and COMM from MICROSAR SYS
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
MICROSAR MEM
AUTOSAR Basic Software Modules for Memory Management
2/24
Overview of Advantages > Exceptionally secure data transactions > Efficient data accesses > Efficient and robust management of nonvolatile memories > Redundant storage of management data increases reliability of FEE and EA modules > Inter-module configuration of the entire memory stack > Platform-optimized memory stack solution from a single source The MICROSAR MEM package contains all of the AUTOSAR modules for memory management: NVM, MEMIF, EA and FEE. They support management, checking and restoring of data from nonvolatile memories (Flash or EEPROM). The Basic Software Modules (BSW) from MICROSAR MEM are fast, reliable and robust. Application Areas MICROSAR MEM lets you develop your functional software platform-independently. MICROSAR MEM contains AUTOSAR services for reading, writing and erasing persistent application data in flash and/or EEPROM memories. This gives the functional software hardware-independent access to memory. The application does not need to know the specific type of memory that exists on the platform or whether this memory is internal to the controller or externally connected to it.
Functions The BSW modules in MICROSAR MEM contain functions defined in AUTOSAR Release 3.x. In each memory stack, you will need the BSW modules NVM and MEMIF from MICROSAR MEM. They handle block-oriented and technology-independent access to the memory areas without requiring prior knowledge of memory attributes. Your memory stack will need additional BSW modules, depending on the use case: > When using flash memory: Flash EEPROM Emulation (FEE) from MICROSAR MEM and a flash driver (FLSDRV) from MICROSAR CAL that is suitable for your hardware. To manage the data, the FEE module needs at least two flash sectors. > When using an EEPROM: EEPROM Abstraction (EA) from MICROSAR MEM and an EEPROM driver (EEPDRV) from MICROSAR CAL that is suitable for your hardware. It is possible to use multiple flash or EEPROM chips in one ECU. This involves using multiple FEE or IO modules in the ECU software. For special requirements, Vector offers platform-optimized solutions, e.g. for using the EA BSW module in data flashing or optimizing the FEE module for specific hardware. The following functions are optionally available: > NVM: Block type DATASET_ROM with multiple ROM blocks > NVM: Data protection with CRC8
MICROSAR MEM modules
AUTOSAR
Training In the framework of our training program we offer various training courses and workshops on MICROSAR at our classrooms or at your business site. For more information on individual training events and dates please visit: www.vector-academy.com
Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www.microsar.com/availability/ We would be glad to provide you with information on OEMspecific versions and individual support of your AUTOSAR projects. Find your contact person at: www.vector.com/contact
In addition, MICROSAR MEM contains the following extensions; some are from AUTOSAR Release 4.0 (ASR 4.0): > Fixed, predefined maximum execution times for all MICROSAR MEM functions. This enables system optimizations to shorten access times. > NVM: Allocates RAM for CRC memory storage > NVM: Dedicated interface for the DCM diagnostic module for direct read-out and manipulation of data blocks (ASR4.0) > NVM and EA: Additional configurable transaction security, which is a standard feature of the FEE module > FEE: High-performance administration of stored memory data > FEE: Common usage of FEE module by Flash Bootloader (FBL) and application possible also with common memory blocks. An update of the ECU software can be done without adjustment of the FBL. > FEE: Update support for adjustment of non volatile memory after ECU re-programming. This is done with a new configuration table (content and size). > FEE/EA: Redundant storage of management data for increased reliability. > FEE: Flexible placement of the FEE sectors in the DataFlash Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7)
> BSW modules description > Description files for DaVinci Configurator Pro > Documentation The complete AUTOSAR Solution from Vector Vector offers a fully tuned AUTOSAR solution for developing AUTOSAR ECUs with its DaVinci and MICROSAR products. 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.
2/25
Other MICROSAR Products relevant for a Memory Stack Based on the AUTOSAR architecture, a complete memory stack can be formed with memory services from MICROSAR MEM together with other platform-specific BSW modules from the separately available MICROSAR CAL and MICROSAR EXT packages. > FLSDRV and/or EEPDRV from MICROSAR CAL > DRVEXT from MICROSAR EXT for external memory chips In addition, it is easy to integrate MCAL drivers from semiconductor manufacturers in any MICROSAR memory stack. You can protect your memory data with the checksum module (CRC) at your desired security level. To do this, you will need the LIBS module (CRC) from MICROSAR SYS.
Configuration Dialog for the Non volatile RAM Manager
EMBEDDED SOFTWARE
MICROSAR SYS
System-related Basic Software Modules for AUTOSAR
Overview of Advantages: > The ECUM module is included as either a resource-saving PreCompile variant or as a flexible Post-Build variant > Supports activation/deactivation of PDUs for diagnostics (Service Communication Control) > Cross-module configuration of modules from MICROSAR SYS and MICROSAR CAL The MICROSAR SYS package contains AUTOSAR modules that offer system services: COMM, LIBS, DET, ECUM, SCHM, WDGM and WDGIF. They assure start-up and operation of the ECU, and are an important part of each AUTOSAR ECU. System services for diagnostics and the operating system can be obtained in the MICROSAR DIAG and MICROSAR OS packages. Application Areas Services from the MICROSAR SYS basic software modules (BSW) cover an important aspect of the basic functionality of your AUTOSAR ECU. They are called by the functional software (via the RTE) and the rest of the BSW modules. System services include power management, control of all communication channels, scheduling of all BSW modules and monitoring of individual software components (SWC) of the functional software.
The package is platform-independent. To operate MICROSAR SYS on your hardware, you combine it with hardware-dependent drivers from the MICROSAR CAL package per the AUTOSAR architecture. Functions The BSW modules in MICROSAR SYS contain functions defined in AUTOSAR Release 3.x: > BswM: The Basic Software Mode Manager manages specific mode change requests from the BSW modules and executes them based on AUTOSAR 3.2 standardized action lists. For example, the BswM module is responsible for activating and deactivating PDU groups and NM-PDUs for diagnostics (Service Communication Control). > COMM: The communication manager checks the states of all communication channels connected to the ECU. It can keep the ECU awake and ready for communication as necessary. It also coordinates access to the communication channels by all SWCs. Optionally, COMM supports the bus type Internal. > DET: The Development Error Tracer collects the so-called development errors of the SWCs and BSW modules. In case of error, the affected BSW module or SWCs report the faulty function and error type. Optionally, DET supports the Service Ports. > ECUM: The ECU State Manager executes the individually configurable initialization and de-initialization of all basic software modules, including the RTE and OS. It puts the ECUs in different operating modes at the request of the SWCs.
V2.6 2011-06
MICROSAR SYS modules
EMBEDDED SOFTWARE
> LIBS: The LIBS package contains the Cyclic Redundancy Check Library (CRC), Crypto Abstraction Library (CAL), Crypto Primitive Library (CPL) and E2ELIB for protection of safety-relevant communication data. These libraries make various services available to the basic software modules and the functional software. The CRC services, for example, are especially important to BSW modules from the memory stack. > RAMTST: The hardware-independent module RAM Test enables synchronous or asynchronous checking of the physical functional integrity of the RAM memory. At configuration time, you choose between destructive and non-destructive algorithms (Checkerboard, March, Galpat, etc.) and determine the memory area to be tested. > SCHM: The Schedule Manager/BSW Scheduler coordinates execution of the BSW modules. In configuring the SchM you define individual tasks and the cycle times of individual BSW module. You also define the exclusive areas settings for each module centrally. > WDGM and WDGIF: The Watchdog Manager monitors the functional software for proper operation. If the Watchdog time expires, it triggers an ECU reset. In addition, the following extensions are included. Some of them are part of AUTOSAR Release 4.0 (ASR 4.0): > COMM: Compatibility with OSEK NM, Link-time implementation
> ECUM: Supports validation of the reason for wake-up in Power SetUp and Run modes. ECUM is available as a pre-compile or post-build implementation variant > WDGM, WDGIF: Precise supervision of defined time windows for the watchdog (even for high resolution window watchdogs) Configuration The ECUM module can be configured with either GENy or DaVinci Configurator Pro. Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows XP/Vista/Windows 7) > BSW modules description > Description files for DaVinci Configurator Pro > Documentation The complete AUTOSAR Solution from Vector 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.
Configuring the SYS module with DaVinci Configurator Pro

EMBEDDED SOFTWARE
MICROSAR DIAG
AUTOSAR Basic Software Modules for the UDS Protocol
Summary of Advantages > Customized solutions available for many automotive OEMs > Vectors numerous years of experience in the diagnostics field > Contains all necessary extensions for use in production > Supports OBDII for DCM per AUTOSAR 3.1 > Also supports WWH-OBD (Euro VI) > Variants handling already included for diagnostic configuration > Configurable via ODX format with CANdelaStudio > Application code templates are generated for the ECU software MICROSAR DIAG contains the AUTOSAR-compatible implementation of UDS protocol ISO 14229-1:2006 and is ideal as diagnostic software for your vehicle project. MICROSAR DIAG performs a number of tasks. Offering: > OEM-specific implementation of the diagnostic protocol for communication between tester and ECU > Fault memory and management > Disabling of certain functionalities based on active fault entries Combined with CANdelaStudio the widely used specification tool for creating diagnostic data you get a complete diagnostic solution from a single source. Application Areas Diagnostics are not completely specified in AUTOSAR. Beyond the standard each OEM has its own specifications. For this reason Vector offers MICROSAR DIAG with OEM specific extensions. It is
suited for the series use and is available already for many OEMs. For ECUs without diagnostics specification an OEM independent package of MICROSAR DIAG is available. MICORSAR DIAG can be used for current and future legal requirements such as EURO VI. The support of OBDII (ISO 15031/ SAE J1979) as well as WWH-OBD (ISO27145) is available as an option. If your ECU requires diagnostic configuration variants, MICROSAR DIAG offers a powerful solution. With GENy you can define up to 31 different parameter sets and save them resource-optimized in the ECU. This avoids redundancies in the ECU software, because identical interfaces to the same data, services or DTCs are combined in the generated diagnostic code. Functions MICROSAR DIAG contains the three BSW modules DCM, DEM and FIM from the AUTOSAR architecture. Their functions are described in the following sections. Diagnostic Event Manager (DEM) Functions According to AUTOSAR, it is the OEM who specifies diagnostic functionality. Only interfaces are defined for the DEM module, so that users can develop their own functional software (SWCs) independent of the use case. Vector can offer you DEM variants that have been modified for many different OEMs. These variants cover the requirements of the
V2.5 2011-08
MICROSAR DIAG modules
EMBEDDED SOFTWARE
Training In the framework of our training program, we offer various training courses and workshops on MICROSAR at our classrooms or at your business site. For more information on individual training events and dates please visit: www.vector-academy.com
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
specific carmakers. A generic OEM-independent variant is also available. This version supports the following functions as standard features: > Administration of all DTC status bits per the UDS standard > Definition of individual snapshot records and extended records > Pre-defined extended records (e.g. OccurenceCounter) > Counter and time-based error debounce algorithms > Suppression of low-priority errors when memory is full > Flexible unlearning (aging) of errors > Variants handling for diagnostic configuration > Link-time configuration > Compressed configuration data to optimize code size The following AUTOSAR functions are optionally available: > Support of combined errors > Implementation of additional error debounce algorithms (e.g. frequency-based) > WWH-OBD (ISO27145) > Post-build configurability Diagnostic Communication Manager (DCM) Functions The DCM contains functions defined in AUTOSAR Release 3.0. At the end of this datasheet you find a table with an overview of all supported UDS and OBDII services, as well as the necessary tasks of the application software. The following functions are optionally available:
> > > >
Support of OBDII (ISO15031-5) per AUTOSAR 3.1 WWH-OBD (ISO27145) Post-build configuration Support of multiple diagnostic protocols per AUTOSAR
In addition, the DCM contains the following extensions to AUTOSAR as standard features: > Inclusion of the most important UDS Services not contained in AUTOSAR 3.0 > OEM-specific extensions (e.g. RoutineControl Service, ECUPassiveMode) > Variants handling for diagnostic configurations > Link-time configuration > Multiple client support > Seamless interaction with the Vector Flash Bootloader > Generation of an application code template for the ECU software Function Inhibition Manager (FIM) Functions All functions of AUTOSAR Release 3.x are standard features of the MICROSAR FIM. The following functions are optionally available: > Post-build configuration > Periodic or event-based evaluation of FIM status to prevent bursts in processor loading > Export of an ASAP2 file for read-out of momentary status information over XCP
Configuration of the UDS or OBDII services from the DCM module with GENy
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 You can adapt BSW modules from MICROSAR DIAG to meet the needs of your application by modifying the configuration. Since diagnostic-specific parameterization of the DCM is limited using the standard AUTOSAR 3.0 exchange file ECU Configuration Description, the MICROSAR DCM modules are parameterized by a CDD file. You can create them quickly and easily or import them from the most commonly used ODX dialects with the proven diagnostic authoring tool CANdelaStudio. The DEM may be configured via either a CDD file or an ECU Configuration Description. Scope of Delivery > Software modules as a library with C header files, optionally as source code > Command line based generator (for Windows XP/Vista/ Windows 7) > BSW module description > DLLs for configuration with GENy > Documentation > Converters for CANdela diagnostic descriptions
The complete AUTOSAR Solution from Vector 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 Relevant Vector Products You can combine MICROSAR DIAG with the following MICROSAR products to fulfill relevant ISO standards: > MICROSAR CAN (ISO 15765-3 or ISO/DIS 14229-3) > MICROSAR FR (ISO/DIS 14229-4) > MICROSAR IP (ISO/DIS 14229-5) To parameterize MICROSAR DIAG you will need CANdelaStudio. For more information on this, see the separate datasheet in Vectors diagnostics catalog.
MICROSAR DIAG is parameterized with CANdelaStudio and GENy

EMBEDDED SOFTWARE
The module DCM from MICROSAR DIAG supports by default: UDS diagnostic services
Diagnostic Service Name Service AUTOSAR The SCW has to (ISO 14229-1) ID Extension Diagnostic and Communication Management Functional Unit grant service DiagnosticSessionControl 10 execution grant service ECUReset 11 X execution calculate SecurityAccess 27 seed/key for each security level grant service CommunicationControl 28 X execution TesterPresent 3E - (is handled in DEM ControlDTCSetting 85 module) Data Transmission Functional Unit handle data ReadDataByIdentifier (RDBI) 22 acquisition for each DataId ReadMemoryByAddress 23 X - (internal, but data ReadDataByPeriodicIdentifier 2A acquisition is done through RDBI) - (internal, but data DynamicallyDefineDataIdentifier 2C acquisition is done through RDBI) handle data WriteDataByIdentifier 2E access for each DataId WriteMemoryByAddress 3D X Stored Data Transmission Functional Unit ReadDTCInformation ClearDiagnosticInformation 19 14 - (is handled in DEM module) - (is handled in DEM module)
Optionally: OBD II diagnostic services according to AUTOSAR 3.1

Diagnostic Service Name Service The SCW has to (ISO 15031-5) ID Diagnostic Service Definition for CAN handle data acquisition for Request Current Powertrain 01 each PID other than the Diagnostic Data "supported ID" and DEM ones Request Powertrain Freeze Frame 02 - (is handled in DEM module) Data Request Emission-Related 03 - (is handled in DEM module) Diagnostic Trouble Codes Clear/Reset Emission-Related 04 - (is handled in DEM module) Diagnostic Information Request On-Board Monitoring Test handle data acquisition for 06 Results for Specific Monitored each TestId of a MonitorId Systems Request Emission-Related Diagnostic Trouble Codes Detected 07 - (is handled in DEM module) During Current or Last Completed Driving Cycle Request Control of On-Board 08 process each TestId System, Test or Component handle data acquisition for each InfoType ID other than Request Vehicle Information 09 the "supported ID" and DEM ones Request Emission-Related 0A - (is handled in DEM module) Diagnostic Trouble Codes with Permanent Status
Input/Output Control Functional Unit InputOutputControlByIdentifier control I/O for each DataId Remote Activation Of Routine Functional Unit start (stop/request 31 result) for each RoutineId 2F
RoutineControl
EMBEDDED SOFTWARE
MICROSAR CAL
AUTOSAR Driver for Control of Microcontroller Peripherals
Overview of advantages > Optimal support of microcontroller peripherals > Simplified configuration by considering cross-module parameter dependencies in the configurator > Development accelerated by plausibility and completeness tests in the configurator > Resource-saving, since functionalities can be deactivated > Reduced hardware requirements due to optimal utilization of hardware buffers > Gateway developments are supported by efficient auxiliary functions The MICROSAR CAL package contains the drivers for controlling the microcontrollers peripherals. These drivers are fully compatible with the AUTOSAR specifications of the Microcontroller Abstraction Layer. Each MICROSAR CAL driver is optimized controllerspecifically. Application Areas MICROSAR CAL gives you a turn-key solution for driving your microcontroller peripherals. So, it is not necessary to make changes to the functional software when switching to different hardware. All you need to do is switch out MICROSAR CAL to integrate the appropriate drivers.
The MICROSAR CAL drivers work together optimally with the rest of the MICROSAR packages. You just add other packages (e.g. MICROSAR CAN, MICROSAR MEM, etc.) depending on the requirements of your application. For example, you could do this to obtain a complete communication stack or memory management per AUTOSAR specification. Functions The MICROSAR CAL package contains the driver modules Adc, Can, Fr, Lin, Dio, Eep, Fls, Gpt, Icu, Mcu, Port, Pwm, Spi and Wdg. They conform to AUTOSAR Release 3.x and are available for many commonly used microcontrollers. In addition, MICROSAR CAL contains the following extensions. Some are from AUTOSAR Release 4.0 (ASR 4.0): > Ethernet driver (ETHDRV) (ASR 4.0) > IICDRV: Drivers for interfacing to external peripheral chips via the Inter-Integrated Circuit Bus (I2C) > Implementation of Interrupt Service Routines as CAT1, CAT2 or void-void function (configurable) > Flexible integration of error handling with user-configurable interface names such as Det, Dem, etc. > CANDRV: Notification (Callback) on message reception and after successfully sending a message. This makes it possible to automatically execute application-specific code.
MICROSAR CAL modules

V2.4 2011-06
EMBEDDED SOFTWARE
Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www.microsar.com/availability/ We would be glad to provide you with information on OEM-specific versions and individual support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact
> DIODRV: User-configurable locating of the pins within a ChannelGroup > ICUDRV: Notification of timer overrun and in signal measurement mode > MCUDRV: Reset mechanisms are user-configurable for the function Mcu_PerformReset(). The following functionalities are available options: > FRDRV: Bus self-diagnostics. If the FlexRay controller detects an error, it sets a status bit that is polled by the FlexRay driver (FRDRV). > FRDRV: The FlexRay configuration can be read out by a diagnostic command. > CANDRV: Extended filter options for multiple basic CAN objects > CANDRV: Rx queue for reducing interrupt execution time while receiving messages Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows XP/Vista/Windows 7) > BSW module description > DLLs for configuration with GENy > Description files for DaVinci Configurator Pro > 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 the particular datasheets. Additional Services > Integration of drivers by third-party producers, e.g. semiconductor manufacturers, in DaVinci Configurator Pro. This lets the user configure the entire ECU software with a single tool, seamlessly and quickly. > In the framework of project work, Vector would be glad to create a low-level MOST driver for your specific hardware to interface it to the Network Services Library.
Configuration of the ADCDRV with DaVinci Configurator Pro

MICROSAR EXT
AUTOSAR drivers for control of external devices
2/34
Overview of Advantages > Optimal control of your external transceiver and memory devices > Additional support for LIN and Ethernet transceivers > Simplified configuration by considering parameter dependencies with other modules > Development accelerated by plausibility and completeness checks in the Configurator MICROSAR EXT contains communication-related AUTOSAR transceiver drivers for CAN (CANTRCV), FlexRay (FRTRCV), LIN (LINTRCV), Ethernet (ETHTRCV) and drivers for other external devices such EEPROM, flash memory and watchdog (DRVEXT). Functions contained in the drivers were specified by AUTOSAR in the ECU Abstraction Layer and they conform to AUTOSAR Release 3.x. They have each been optimized for a specific device and are available for many commonly used devices. Application Areas MICROSAR EXT gives you a turn-key solution for driving your external peripheral devices. So, it is not necessary to modify the functional software when switching out external hardware. All you need to do is switch out the relevant drivers from MICROSAR EXT.
Depending on the requirements of your application, you can add other packages (e.g. MICROSAR CAN, MICROSAR MEM, etc.) for a complete communication stack or memory management per AUTOSAR specification. Functions The BSW modules in MICROSAR EXT contain functions defined in AUTOSAR Release 3.x plus the following extended functions: > Bus error detection on FlexRay > Active star handling on FlexRay > LIN transceiver drivers > Ethernet transceiver drivers (per AUTOSAR Release 4.0) Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > DLLs for configuration with GENy > Documentation
MICROSAR EXT modules
AUTOSAR
# 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 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.
2/35
Configuration of MICROSAR EXT with DaVinci Configurator Pro
EMBEDDED SOFTWARE
MICROSAR IO
AUTOSAR Input-Output Hardware Abstraction
Overview of Advantages > Quick implementation of user-specific code for acquiring and providing ECU signals > Generation of complete DIO accesses > Provision of code templates with all necessary interface definitions > Support of actuator tests via diagnostics AUTOSAR has defined hardware-independent Set/Get and Diag operations in the IO Hardware Abstraction for setting, reading out and manipulating physical I/O signals (digital or analog) from your ECUs periphery. Vector offers them in the MICROSAR IO package. In addition to functions specified by AUTOSAR, you can use MICROSAR IO to create your own signal definitions, making it easy to implement application-specific signal processing. Application Areas MICROSAR IO provides a convenient foundation for developing your IO Hardware Abstraction. In combination with the suitable drivers for microcontroller peripherals from MICROSAR CAL, you get a complete I/O stack for the ECU software. It interconnects the functional software to physical IO signals of sensors and actuators, which makes the application software hardware-independent. In configuring MICROSAR IO, you define each individual signal as either a user defined signal or a DIO port signal. MICROSAR IO provides all of the necessary Client/Server interfaces and code
templates needed to give the functional software access to the I/O signals via the RTE. They let the user condition and filter the signals. No special extension to the MICROSAR IO code is needed for direct access to DIO signals. Functions BSW modules in MICROSAR IO contain functions defined in AUTOSAR Release 3.x. In addition, you can use MICROSAR IO to: > Define user defined ports for acquiring ECU-specific user defined signals. > Process user defined signals from the user defined ports. Upon request, DaVinci Configurator Pro can generate code templates, in which users can directly program their extensions. > Execute functions for the DCM actuator test via the standard interface. This function already conforms to AUTOSAR Release 4.0. Configuration MICROSAR IO is configured with DaVinci Configurator Pro. The configuration and generation tool checks for plausibility of the configuration parameters for MICROSAR CAL and MICROSAR IO. The following bottom up approach is recommended: > Configure the CAL driver > Configure MICROSAR IO > Generate SWC description for modeling of MICROSAR IO
V2.3 2011-06
MICROSAR IO modules
EMBEDDED SOFTWARE
Training In the framework of our training program we can offer you various training courses and workshops on MICROSAR at our classrooms or at your business site. For more information on individual training events and dates please visit: www.vector-academy.com
Contact and Availability For information on the availability of hardware-specific MICROSAR BSW modules go to: www.microsar.com/availability/ We would be glad to provide you with information on OEM-specific versions and individual support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact
This SWC description later flows into modeling of the entire ECU software, which could be created with DaVinci Developer, for example. Here, the Vector design and configuration tool ensures that ECU signals defined in MICROSAR IO are integrated in the overall data flow of the ECU software. This modeling is the foundation for later generation of the RTE. Scope of Delivery > Software modules as library with C header files, optionally as source code > Command line based generator (for Windows XP/Vista/Windows 7) > BSW modules description > Description files for DaVinci Configurator Pro > 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. Additional Services Vector would be glad to support you in the development of the IO Hardware Abstraction Layer of your special ECU in the framework of project work. You benefit from Vectors detailed knowledge of the AUTOSAR specification and methodology as well as its extensive experience in integration of ECU software.
Konfiguration des Moduls IO mit DaVinci Configurator Pro

MICROSAR RTE
The optimized Run-time Environment for Software Components per the AUTOSAR Standard
2/38
Overview of Advantages > Easy to configure and scalable > In-depth consistency check of the configuration > Highly optimized code with intelligent synchronization mechanisms > Quick entry into working with AUTOSAR, e.g. based on generated code templates for the software components (SWCs) > Well-suited for migration projects > Simplified testing of the application by XCP access to S/R ports, InterRunnable variables and Per-Instance memory MICROSAR RTE (Run Time Environment) is the scalable and highly optimized AUTOSAR runtime environment from Vector. The RTE is a module introduced by AUTOSAR that manages communication between the software components (SWCs). It assures consistency of the overall information flow and represents the interface between the functional software, basic software (BSW) and complex device drivers (CDD). The SWCs, RTE, CDD and BSW modules together form the overall AUTOSAR ECU software. Application Areas When the functional software of an ECU is implemented by AUTOSAR-conformant SWCs, the user needs the RTE as a runtime environment. This modular layout of the ECU software offers the user maximum flexibility: SWCs that have been manually devel-
oped or designed by model-based tools can be re-used in multiple ECU projects. The RTE only needs to be reconfigured and regenerated for the specific ECU and, if applicable, the BSW modules. It is also possible to use a SWC in multiple instances on one ECU. In generating the MICROSAR RTE, the user can choose between two modes: > Contract Phase Generation for developing individual SWCs in an early phase. In this case, the generator just creates a header file for each SWC instead of the entire RTE. This makes it possible to compile the SWCs individually, e.g. to transfer them to a development partner as object code. > RTE generation for the entire ECU software. The code generated in this mode is highly efficient and requires only little memory space. It is optimized for the entire ECU configuration and makes few demands on system resources due to short execution times and minimal interrupt disable times. One way this is achieved is by using intelligent synchronization mechanisms that are tuned to the properties of the hardware used. Functions The MICROSAR RTE contains functions defined in AUTOSAR Releases 3.x: > Sender/Receiver and Client/Server communication > Mode management > InterRunnable variables as well as Exclusive Areas > Trigger for runnables
MICROSAR RTE module
AUTOSAR
> Online and offline calibration of SWCs are supported as well as measurement of S/R ports, InterRunnable variables and Per-Instance memory using the XCP protocol. > Multiple instancing of SWCs and per-instance memory Moreover, the MICROSAR RTE offers: > Generation of code templates for SWCs based on the XML file SWC Description. These templates contain all APIs of the RTE. Users fill these templates with their own application code. > Use of memory protection mechanisms as specified in the AUTOSAR operating system. This support is especially optimized when MICROSAR OS is used. > Configuration of initialization runnables for the AUTOSAR concept of Mode-Dependent Runnables > Generation of an A2L file for simple linkage to existing calibration and diagnostic standards > Generation of an HTML report showing RTE properties. It contains information such as the calculated RTE resource load (RAM + constants). The following AUTOSAR 3.x functions are optionally available: > External Client/Server communication (Inter-ECU) > Full support for measurement and calibration > Rx data filter for functional software
Configuration You can configure the MICROSAR RTE with DaVinci Developer. As an extension to the AUTOSAR method, it contains validation rules that ensure the consistency of the RTEs configuration parameters. The subsequent generation of the RTE is performed directly from DaVinci Developer or with a separate generator. Automated generation of the RTE using the command line method is also possible. Scope of Delivery > Command line based generator (for Windows NT/2000/XP/ Vista/Windows 7) > BSW modules description > 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 details on functional features of the DaVinci Tools in separate datasheets.
2/39
Other Relevant MICROSAR Products: The RTE requires the presence of an operating system such as MICROSAR OS or osCAN.
MICROSAR RTE enables generation of code templates for the SWCs
EMBEDDED SOFTWARE
MICROSAR Safe
Safety according to ISO DIS 26262 for ECUs with AUTOSAR software
Overview of advantages > Solution for all Automotive Safety Integrity Levels (ASIL) through ASIL D > Savings in qualification costs > Support of different ASILs on one controller Application areas For using MICROSAR basic software in ECUs with safety-relevant functions, you will receive MICROSAR Safe from Vector. This solution is the result of collaborative work with TTTech, our partner with many years of experience in the field of functional safety. It lets you develop AUTOSAR-based applications using software components (SWCs) for ECUs up to ASIL D per ISO DIS 26262. The modules from MICROSAR Safe are SEooCs (Safety Elements out of Context), which are developed according to ISO DIS 26262 / ASIL D. Their use helps you to drastically reduce effort for qualifying your safety-relevant functions. Functions The SafeCom, SafeExecution and SafeSelfTest bundles from MICROSAR Safe contain the following specific functionalities. They were implemented according to the AUTOSAR specification and are compatible with the remaining MICROSAR modules:
SafeExecution: > Runtime monitoring of tasks > Flow control of safety-relevant SWCs > Memory protection and safe context switching SafeCom: > Safe intra-ECU and inter-ECU communication SafeSelfTest: > Periodic hardware checking The use of Runtime Monitoring, Flow Control, Memory Protection and Safe Context Switching makes it possible to let safety-relevant and non-safety relevant SWCs run next to one another on the same ECU without interference. This means that software parts whose correct execution cannot be verified cannot disturb safety-relevant functions unnoticed. Runtime Monitoring Runtime monitoring assures that tasks have sufficient computing time for their execution. Runtime monitoring is provided by MICROSAR OS SC2/SC4 and is validated to ISO DIS 26262 by the modules WDGM, WDGIF and WDGDRV from SafeExecution.
V2.2 2011-10
MICROSAR Safe
EMBEDDED SOFTWARE
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 the properties of the BSW modules and a detailed description of the functional features of the individual DaVinci Tools in individual datasheets.
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 as well as individual support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact
Program Flow Monitoring Correct execution of safety-relevant SWCs is assured by the modules WDGM, WDGIF and WDGDRV. This involves using what are referred to as checkpoints in the software components. Memory Protection and Safe Context Switching The MICROSAR operating systems option SafeContext, which was developed to ASIL D, assures memory protection for ECUs with safety-relevant applications on suitable microprocessors (e.g. with MPU, the Memory Protection Unit). The option SafeContext is available for MICROSAR OS (SC3/SC4) and it is used to separate the various software components from one another during task changes and interrupts. SafeContext prevents unauthorized writing by one software component to the memory of another software component that could corrupt the data. Safe Intra-ECU and Inter-ECU communication Data that is exchanged between safety-relevant applications must be checked for correct transmission. A checksum protects the data contents and the correct sequence of data is monitored by a message counter. If one of these checks fails, the application is informed, and it can react accordingly. This detects errors such as masquerading, failure or reversed data.
Hardware checking You can perform cyclic tests for error-free functionality of the ECUs various hardware components during operation using generic test functions of the SafeSelfTest package. The precise scope of monitoring that is necessary is project-specific. We would be glad to consult with you in selecting specific monitoring mechanisms for your project. RTE for safety-relevant functions The MICROSAR RTE supports partitioning of memory areas via the operating system option SafeContext. This enables a Decomposition in the sense of ISO DIS 26262. Configuration The safety elements of MICROSAR Safe are configured with the DaVinci tools. Product components > Software modules as library with C header files, optionally as source code > Instruction line based generator (for Windows XP/Vista/ Windows 7) > BSW module description files > Description files for DaVinci Configurator Pro > Documentation with Safety Manual
Implementation Safety-relevant functions are implemented by the Safety Elements out of Context (SEooC) from MICROSAR Safe. They detect and handle potential errors in non-safety software layers. The SEooCs conform to ISO 26262 ASIL D and are developed according to the AUTOSAR specification. MICROSAR Safe contains the following SEooCs: SafeCom: > E2ELIB: End-to-end library > Protection Wrapper: End-to-end protection Wrapper
SafeExecution: > SafeContext: Memory Protection and Safe Context Switching (option for MICROSAR OS) > WDGM: Watchdog Manager > WDGIF: Watchdog Interface > WDGDRV: Driver for internal watchdog devices > WDGEXT: Driver for external watchdog devices SafeSelfTest: > RAMTST: Tests for RAM memory > FLASHTST: Tests for flash memory > CORETST: Tests for the microcontroller core > IOTST: Tests for inputs and outputs
Identity Manager for AUTOSAR

Solution for Multiple ECUs
Overview of Advantages > Efficient handling of ECU variants > Less administration effort > Reduced inventory costs 2/42 In the modern automobile, there is an increase in the number of ECUs that can be installed in different variants; they are known as multiple ECUs. Your advantage is the use of a single hardware for the different application areas. This reduces hardware costs and effort in inventory management. On the other hand, it results in increased effort in software development and the management of software variants for production and service areas. Based on its many years of cooperation with automotive OEMs and suppliers, Vector is familiar with typical applications for ECU variants and can provide practice-oriented solutions for multiple ECUs based on AUTOSAR Release 3.x. Physical Multiple ECU One speaks of Physical Multiple ECUs, when multiple ECUs in a vehicle perform nearly identical functions at different locations. Door ECUs are a typical example of this. The individual ECUs only differ in their Rx and Tx PDUs or in their diagnostics and address in the network. In this case, a single ECU is developed and produced.
Identity An ECU is identified by its Identity. The Identity establishes which variant of the ECU should be activated (e.g. which door side). So, an 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 initialized. Via the so-called Identity (see box), each ECU knows during startup which one it is and where it is installed, and therefore also which functions it needs to fulfill. The buffer for the Rx and Tx PDUs can be completly overlaid if their layout is identical. The application accesses signals and data elements independent of its identity. No differentiation is necessary in the code. Multiple Configuration With the multiple configuration, it is possible to use an ECU in different car lines, and therefore in completely different communication networks. A typical application here would be for what are known as carry-over ECUs. These ECUs contain the software for all of the car lines in which they are used. In this case, the ECU Extracts upon which the configuration of the AUTOSAR ECU software is based may differ very significantly for the different variants, 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
AUTOSAR
The complete AUTOSAR solution from Vector 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 package and detailed descriptions of functional features of individual DaVinci Tools in the relevant datasheets.
Contact and Availability You will find information on the availability of hardwarespecific MICROSAR BSW modules at: www.microsar.com/availability We can also tell you about OEM-specific versions and customer support for your AUTOSAR projects. Find your contact person at: www.vector.com/contact
For both solutions, PDUs may be overlaid if only a few signals are identical in the PDUs. The RTE implements this by the so-called fan-in or fan-out mechanism. Integrating both Solutions in the AUTOSAR Concept According to AUTOSAR, an ECU is described by an ECU Extract of System Description. To describe two or more ECU variants, two or more ECU Extracts are needed. For the RTE, these files are merged into one file with DaVinci Developer. Afterwards, DaVinci Developer generates a higher-order ECU Configuration Description (ECUC) for the basic software. Both files contain a superset of the relevant ECU-specific information. Proven Configuration Process The configuration tools DaVinci Developer and GENy read in the merged files (ECU Extract and ECUC). In these two tools, the user finds a superset of the ECU interfaces to be implemented and configures the multiple ECU like a normal 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. The user configures the optimal superset of all diagnostic services as usual in GENy.
Saving Resources Since Physical Multiple ECUs are identical in much of their content, for optimization no separate set of configuration parameters is created for some BSW modules but only a common set is created for all instances. This applies to such elements as identical messages, diagnostic services, etc. In multiple configurations, ECU resource savings are realized. Although the ECU must be large enough to offer space for both applications, only one hardware component is needed. Scope of Delivery The scope of delivery of the Identity Manager includes: > License for enabling in the configuration tool > BSW modules with Identity Manager functionality
2/43
Configuration process of multiple ECUs
EMBEDDED SOFTWARE
Wide Availability of MICROSAR

Supported Microcontrollers and Compilers for the hardware-specific AUTOSAR BSW Modules
Controller
Compiler
MICROSAR OS [1]
MICROSAR CAL [2, 3] CAN FlexRay LIN IP/Ethernet

Further MCAL Driver
Altera NIOS II ARM Cortex M Atmel AVR32 Freescale i.MX25, i.MX35 MAC7100 S12X MPC55xx GNU ARM, IAR Cosmic, Metrowerks Green Hills, Metrowerks, Wind River Green Hills, Metrowerks, Wind River X X X X X X X X X X [4] X X X IAR X X X ARM X GNU, Tasking X
MPC56xx (QORIVVA/ 5xxx/Automotive) Fujitsu 16FX FCR4 FR60 FR81 MB86 MB9E/DF126 (Cortex-R4) Infineon TriCore XC2000 Microchip PIC24 dsPIC33E, dsPic33F NXP LPC1768
V2.4 2011-10
Fujitsu Green Hills Fujitsu Fujitsu GNU, Green Hills Green Hills
X X X X X
X X X X
GNU, Green Hills, Tasking Tasking VX
X X
X X
X X
Microchip Microchip
X X X
Keil
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 [1]
MICROSAR CAL [2, 3] CAN FlexRay LIN IP/Ethernet

Further MCAL Driver
Renesas Electronics (NEC/Renesas) 78K0R V85x M32C M32R R32C R8C SH2 STMicroelectronics SPC56xx Green Hills, Metrowerks, Wind River GNU X X X X X X IAR Green Hills, IAR, Renesas Renesas, IAR Renesas Renesas, IAR IAR Renesas, Green Hills X X X X X X X X X X X X X X X X X X X X
STR9 Texas Instruments TMS320 TMS470 TMS570 Vector CANoe osCAN Emulation
Texas Instruments Texas Instruments Texas Instruments X
X X X X X X X
Microsoft VisualC
[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
DaVinci Developer
Designing AUTOSAR Software Components and Configuring the MICROSAR RTE
2/44
Overview of advantages > Convenient graphical definition of software components > Clear representation of complex systems > Special functions simplify data exchange between OEM and ECU developer > Easy connection to configuration management tools > Consistent configuration of the MICROSAR RTE DaVinci Developer is the professional tool for designing AUTOSAR software components (SWCs) and for configuring the MICROSAR RTE. Convenient graphical editors let you design the structure and interfaces of the functional software for your ECU quickly and clearly, and they facilitate smooth integration of the functional software with the ECUs basic software. Application Areas DaVinci Developer supports ECU developers in developing AUTOSAR-conformant ECUs. You can use DaVinci Developer as an architecture tool to define application software architectures. DaVinci Developer is also well-suited as an integration tool you 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.
Functions DaVinci Developer offers extensive functions for defining and integrating AUTOSAR SWCs: > Graphical definition of SWCs with extensive layout functions > Definition of port interfaces and data types > Definition of port prototypes with service needs and communication specification, e.g. initial values and timeouts > Definition of runnable entities with activation events and port access > Support for all types of AUTOSAR SWCs and application components, compositions, calibration and service components > Import and export of AUTOSAR XML formats (System Description Template, Software Component Template) > Support for various AUTOSAR XML versions in parallel. > Signal import from commonly used network description formats (DBC, FIBEX, LDF) > Data mapping of port data to network signals > Consistency check of the SWC definition and the RTE configuration > Interface to model-based development tools via AUTOSAR-SWC description files
DaVinci Developer Design tool for AUTOSAR-conformant ECUs
AUTOSAR
The complete AUTOSAR solution from Vector Vectors DaVinci and MICROSAR products offer a fully tuned solution for developing AUTOSAR ECUs. Separate datasheets describe general properties of the BSW modules from the MICROSAR packets and detailed functional features of the individual DaVinci Tools.
Training Events In the framework of our training program, we offer various AUTOSAR training courses and workshops at our classrooms, as online Webinars or at your company site. For more information on individual training events and the schedule on the Internet go to: www.vector-academy.com
Workflows and AUTOSAR Methods DaVinci Developer can be flexibly used in a distributed development process based on the AUTOSAR method. For this purpose, the tool offers extensive functionality for data exchange between OEM and ECU developer: > Import/Update function to support an iterative development process > Diff and Merge functions with configurable presettings for individual objects. This makes it possible to extend OEM-generated SWCs by adding port prototypes and runnable entities. > Library concept for reusing components or interfaces in multiple ECU projects > Connection to configuration management systems with finegranulation versioning of individual objects, e.g. SWCs Configuration of the MICROSAR RTE DaVinci Developer is used to configure the MICROSAR RTE; it supports work steps such as: > Assigning runnable entities to operating system tasks. This work is simplified by special views on the runnable entities, such as the trigger-oriented or component-oriented view. > Configuring optimization options > Consistency checking of the RTE configuration with detailed error reports and tips on correcting inconsistencies
DaVinci Developer works seamlessly with DaVinci Configurator Pro to create a consistent overall configuration. For example, the service components and IO hardware abstraction components generated by DaVinci Configurator Pro can be conveniently imported and linked to the application SWCs. DaVinci Developer offers special support by automatically creating suitable service port prototypes and server runnables for the application SWCs. Finally, the RTE configuration is saved AUTOSAR-conformantly in an ECU configuration file. Scope of Delivery > DaVinci Developer > Utility tools for automating work steps > Demo data > Documentation System Requirements
Component Processor Memory (RAM) Screen resolution Operating system Recommended Pentium 4/2.6 GHz 2 GB 1280 x 1024 Minimum Pentium III/1 GHz 1 GB 1024 x 768
2/45
Windows XP SP2 or SP3 Windows 7 (32- or 64-Bit)
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 1.0

Testing AUTOSAR Application Software on the PC
Overview of advantages > User-friendly testing of AUTOSAR software components (SWC) on a PC > Wide variety of use cases; from tests supporting the ECU developer to acceptance tests at the automotive OEM > Suitable for all application SWCs, e.g. state machines or control systems > Testing of SWCs developed manually or by model-based methods > Unlimited support of all SWC interfaces per AUTOSAR Release 3.0 and 3.1 > Quick setup of tests without time-consuming configuration > Simplified test cases by emulating AUTOSAR Standard Services > Interfaces to standard test tools: CANoe from Vector and NUnit > Interfaces to development environments such as Microsoft Developer Studio or Eclipse via open interfaces Thanks to AUTOSAR, an ECUs application software can be developed as hardware-independent software components (SWCs) based on a Virtual Functional Bus (VFB). DaVinci Component Tester is a high-performance VFB emulator that enables execution and testing of such SWCs on a PC. It is very easy to configure the DaVinci Component Tester, by using just the SWC description file without modification of the SWCs. The original source code is executed directly.
DaVinci Component Tester is a universal run-time platform for testing SWCs in all development phases of ECU applications. Application Areas DaVinci Component Tester supports the following application areas: > Rapid Prototyping While developing ECU applications, you can use the DaVinci Component Tester as a convenient run-time platform for SWCs. By integrating DaVinci Component Tester in the development environment, you can execute and debug the SWCs right on your development PC. Also, in conjunction with a development and test tool such as CANoe you can control the SWCs interactively, e.g. via user interfaces, and analyze their behavior. > 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 such as NUnit, this will increase the quality of your SWCs by testing during development. An example is automated regression tests. > Integration tests of software components DaVinci Component Tester supports integrating complex systems consisting of multiple SWCs. When used together with a test tool like CANoe, this lets you verify system functionality early on.
V2.4 2011-07
Testing atomic AUTOSAR software components with DaVinci Component Tester
Testing a composition of multiple software components with DaVinci Component Tester
Functions The core of DaVinci Component Tester is an emulator that executes the SWCs on a PC. This does not require an AUTOSAR RTE (Runtime Environment) or basic software. The finely tuned emulator simulates the AUTOSAR-ECU environment for the SWC under test with realistic behavior. The emulation covers full RTE functionality and lets you test any AUTOSAR Release 3.0 and 3.1 SWCs using functions such as: > Setting data elements of receiver ports > Reading data elements from sender ports > Calling up server ports > Controlling mode ports > Setting calibration data > Executing runnables with non-blocking API calls (Category I) > Executing runnables with blocking API accesses (Category II) > Handling internal communication between multiple SWCs > 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.
Operating Modes DaVinci Component Tester offers two operating modes, which depend on its intended use. They affect execution of the SWCs runnable entities: > Programmed execution mode You can implement execution of the runnable entities in an explicit test case. This execution mode is used in unit tests with focus on detailed inspection of the implementation. > Automatic execution mode DaVinci Component Tester executes the runnable entities independently according to the trigger specification, e.g. periodically every 10 ms. Therefore DaVinci Component Tester synchronizes itself to the time base of your test tool. This execution mode is used for integration testing of complex SWCs or in experimental startup of a SWC during development (Rapid Prototyping).
Special functions > Instruction line support for automated tests > Checking API consistency of the SWC Description and SWC implementation file > Programming callbacks in the test environment for specific reaction to an API call of the SWC under test > Generating the header file of SWCs (Contract Phase Generator) for compiling the SWC implementation with the Microsoft Compiler Service Emulator DaVinci Component Tester contains an emulator for the standard services of an AUTOSAR ECU. This emulator simulates the behavior of the services in an abstracted form. When a test or experiment is set up, the SWCs service ports are automatically connected to the service emulator. There is no need to explicitly consider the service ports in the test environment, allowing you to focus entirely on the SWCs 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:
> > > > > >
EcuM (ECU Manager) DEM (Diagnostic Event Manager) FiM (Function Inhibition Manager) NvM (Non-Volatile Memory Manager) ComM (Communication Manager) WdgM (Watchdog Manager)
Interface to CANoe You can use DaVinci Component Tester in combination with CANoe to execute integration tests of SWCs. While CANoe controls the test flow, DaVinci Component Tester automatically handles execution of the runnable entities. Therefore DaVinci Component Tester synchronizes itself to the simulation time of CANoe. You describe the test environment in CANoe, e.g. with the help of the Test Feature Set. All other CANoe functions are available as well; such as panels, analysis windows and integration of MATLAB models for an environment simulation.
Functional principle: Interfacing DaVinci Component Tester to CANoe
Interface to NUnit You can execute unit tests of SWCs in conjunction with the open source tool NUnit. This is done by implementing the test cases in any desired .NET language such as C#. The test cases typically show the following pattern: Set input vector, execute runnables, read output vector and check it. NUnit handles test execution and reporting. Microsoft Visual Studio is used to program the test cases. In implementing the test cases, you are supported by programming assistance integrated in the development environment (IntelliSense). For example, a user could easily program access to a receiver port by listing all of the SWCs receiver ports and selecting the desired port from the list. Integration in your test environment Due to its open interfaces, DaVinci Component Tester can be integrated in your development environment or test tool chain, making it AUTOSAR-capable. Vector offers support in integration of DaVinci Component Tester. Scope of Delivery DaVinci Component Tester consists of the following components: > SUT Executable Generator: Instruction line tool for preparing the SCW under test as an executable system under test (SUT). Inputs are the SCW imple-
> > >
>
> >
mentation compiled by the Microsoft Compiler and the SWC Description (AUTOSAR XML). Contract Phase Generator: Instruction line tool for generating the SWCs header file Emulator (including Service Emulator): .NET DLL for executing SUT executables NUnit Adapter: Interfaces the emulator to NUnit. Interfacing is via a .NET Assembly with a structured API for access to the SWC. CANoe Adapter: Interfaces the emulator to CANoe. Interfacing is via a .NET Node, which you integrate in your CANoe configuration. The SWCs input and output data elements are mapped via CANoe system variables. Sample projects Manual as PDF document
System Requirements > MS Visual Studio 2005 or 2008 (Express, Standard or Professional Edition). The Professional Edition is required for debugging in combination with NUnit. > Windows XP or Windows 7 (32- or 64-Bit) > CANoe 7.1 or higher > Alternative: NUnit 2.4.7 or higher (available at: http://www.nunit.org)
Functional principle: Interfacing DaVinci Component Tester to NUnit

DaVinci Configurator Pro

Configuration of AUTOSAR Basic Software
Vectors DaVinci Configurator Pro is the professional tool for configuring the Basic Software (BSW) modules of an AUTOSAR ECU according to the AUTOSAR standard. Properties and Advantages DaVinci Configurator Pro was created as an open tool for configuring and generating BSW modules. It is a practical, intuitive and user-friendly implementation of the AUTOSAR method. In addition, its multi-stage and rule-based validation process assures consistency of all configuration parameters between modules. For user-friendly configuration of the BSW modules, DaVinci Configurator Pro uses so-called DaVinci description files which are included in the scope of delivery of Vector AUTOSAR BSW modules (MICROSAR). The DaVinci Configurator Kit from Vector, available as a separate product, makes it easy to create these DaVinci description files on your own. As an alternative, if only an AUTOSAR BSWMD file exists, DaVinci Configurator Pro offers the Generic Configuration Editor (GCE) mode for modules. This makes it an ideal central configuration tool. DaVinci Configurator Pro is also characterized by the following properties: > Support of all available AUTOSAR releases (2.1, 3.0 and 3.1), also in mixed forms within a project > Project-oriented working mode by simple activation or deactivation of individual BSW modules
2/50
> Support of commonly used network description formats (DBC, FIBEX, LDF) and/or the AUTOSAR ECU Extract of System Description > Flexible generation options for optimal integration in existing development processes > Project assistant for easily creating and updating ECU projects Application Areas DaVinci Configurator Pro supports users in configuring, validating and generating BSW modules from Vector (MICROSAR), third party producers (e.g. MCALs from semiconductor manufacturers) and user-developed BSW modules. Functions DaVinci Configurator Pro offers users two different configuration modes: Comfort Mode and GCE Mode. The Comfort Mode supports you extensively in configuring the BSW modules. Using the DaVinci description files you can: > Edit configuration parameters over a user-oriented interface, e.g. to show complex configuration relationships in simplified form > Validate parameters across modules > Define the value range of input values > Display configurations in GCE or Comfort Mode > Show the syntax of internal module APIs and callouts > Display implementation-specific help texts
Configuring BSW modules with DaVinci Configurator Pro
AUTOSAR
Useful auxiliary tools included in the scope of delivery: > DaVinci Initial ECUC Generator for the initial generation of an ECU Configuration Description (ECUC) file from an ECU Extract of System Description > DaVinci ECUC Updater for updating an existing ECUC file after a change has been made to the ECU Extract of System Description > DaVinci Difference Analyzer for comparing AUTOSAR files
Services Vector can support you with standard software for your projects, as well as with customized services such as a hotline, special workshops and training on the topic of embedded software and AUTOSAR. For more information go to www.microsar.com or contact us directly.
Beyond the functional features defined in AUTOSAR, the GCE Mode of DaVinci Configurator Pro offers the following supplemental functions: > Clearly organized display of all software modules based on the AUTOSAR architecture > Copying of configurations of individual BSW modules from other projects > Efficient searching and modification of AUTOSAR containers, parameters and references over the entire project > Easy integration of external code generators > Flexible definition of target directories > Add module-specific documents for quick access > Logging of configuration settings and listing of important alerts The GENy tool is included in the scope of delivery and is used for time-saving configuration of communication-related MICROSAR BSW modules from the SYS, COM, CAN, LIN, FR, MOST and IP packets as well as diagnostic modules from DIAG. GENy offers a userfriendly interface specifically optimized for these configuration parameters, and it can be directly opened from within DaVinci Configurator Pro.
Scope of Delivery > Windows-based configurators: DaVinci Configurator Pro and GENy > DaVinci Initial ECUC Generator, DaVinci ECUC Updater, DaVinci ECUC Difference Analyser 2/51 System Requirements
Additional Services > Creating DaVinci description files for convenient and userdefinable configuration, validation and generation of any desired modules with DaVinci Configurator Pro > Hotline, special workshops and training events on the topic of embedded software and AUTOSAR
DaVinci Configurator Pro supports you in conveniently configuring, validating and generating AUTOSAR BSW modules.
DaVinci Configurator Kit

Creating configuration interfaces and generators for user-developed software modules
2/52
The AUTOSAR architecture currently defines approx. 50 configurable standard Basic Software (BSW) modules. Each module is configured to the needs of an individual ECU. DaVinci Configurator Pro is the AUTOSAR configuration tool from Vector that is used to configure all BSW modules. You can extend DaVinci Configurator Pro (see separate datasheet) with the DaVinci Configurator Kit, so that you can configure and generate in a time-saving and user friendly way your own inhouse embedded software modules. This lets you concentrate fully on the development of your embedded software module, and you will not need any additional configuration tool. You can also use the DaVinci Configurator Kit to extend any desired software module to prepare it for integration in an AUTOSAR ECU. Conformance to the AUTOSAR standard is assured by Vectors many years of experience with AUTOSAR. Properties and Advantages The DaVinci Configurator Kit supports the embedded module developer in designing individual configuration interfaces for user-developed software modules and creating flexible code generators. As a supplement to the AUTOSAR method, the DaVinci configuration tools from Vector also offer a validation feature. Before code generation it ensures that individually configured parameters as well as complex parameter groups are consistent with one another. For user-created software modules, you can also use the DaVinci Configurator Kit to define the validation rules.
Application Areas The DaVinci Configurator Kit supports developers of AUTOSAR basic software modules, complex device drivers and user-developed software modules. Developers benefit from the simplified process of creating configuration interfaces, validation rules and generators without requiring knowledge of tool programming. With just minimal effort it is possible to configure and integrate complex device drivers in an existing AUTOSAR SW architecture. Functions: The Vector DaVinci Configurator Kit lets you: > Generate the AUTOSAR-conformant BSW Module Description > Conveniently create configuration interfaces, validation rules and generation processes for DaVinci Configurator Pro > Define range and default values for configuration parameters > Conveniently define your own configuration parameters > Describe dependencies between different configuration parameters within a module or across modules > Create your own code generators > Easily define individual project reports that document the parameter configuration in DaVinci Configurator Pro > Extend the DaVinci Configurator Pro functionality by integrating your own C++ based DLLs > Protect your own know-how by encrypting DaVinci description files
DaVinci Configurator Kit supports you in integrating your software module in DaVinci Configurator Pro
AUTOSAR
Services Vector can support you with standard software for your projects, as well as with customized services such as a hotline, special workshops and training on the topic of embedded software and AUTOSAR. For more information go to www.microsar.com or contact us directly.
System Requirements The following development tools are included with the DaVinci Configurator Kit: > Eparm to define and pre-configure individual parameters for a module > Clix to flexibly lay out user interfaces for displaying and editing the module configuration in DaVinci Configurator Pro > Erule to create complex rules for data checking and file generation > Cryps to encrypt DaVinci description files created with Eparm, Clix and Erule > Elic to incorporate user-developed modules in existing DaVinci Configurator Pro licenses Scope of Delivery > DaVinci Configurator Pro (developer license) > Tools for generating the DaVinci description files > Extensive technical documentation of interfaces, as well as numerous application examples > Command line based code generator > 3 days of training > 20 hours of hotline support
2/53
Additional Services > Designing convenient configuration interfaces and supplemental validation rules for software modules of third party producers, such as MCAL drivers or IO hardware abstraction > Completely creating complex device drivers > Extensions of AUTOSAR standard BSW modules > Developing customer-specific AUTOSAR software components (SWCs) > Working out individual strategies for migration of your existing systems to AUTOSAR > Hotline, special workshops and training events on the topic of embedded software and AUTOSAR
Defining a modules configuration parameters with the Eparm tool from the DaVinci Configurator Kit.
AUTOSAR Services
Proficient support for your AUTOSAR projects
Overview of advantages > Builds up knowledge efficiently and effectively > Tailored support > Quick implementation of your application 2/54 With our AUTOSAR Software Engineering Services, we support you in every phase of your ECU development. Starting with our extensive AUTOSAR experience and your aspired project goals, we jointly carry out a customized action package for you, in which you realize sustained benefits from our AUTOSAR competence. AUTOSAR Training Vector AUTOSAR training courses provide you with an ideal entry into ECU development with AUTOSAR. Intensive exercises ensure its relevance to practice. For the list of Vector in-house training courses on the Internet, go to: www.vector.com/AUTOSAR-Training. We would also be glad to conduct these training courses at your business site. It is possible to adapt the training content to your individual needs. 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.
First, we work together with you to setup the MICROSAR basic software (BSW) and RTE on your ECU hardware using the related configuration tools. For this purpose we use a sample application. This quickly gives you a runnable system, letting you focus on your application. This support is typically performed at your business site. Afterwards, hotline support is available to you by telephone or email, which ensures continuous support in case you have questions about how to use our products. MICROSAR Reviews You have been using our AUTOSAR Embedded Software for a longer period of time, and you are approaching an important project milestone. Based on prepared checklists, we conduct an integration and configuration review related to the concrete useage of the MICROSAR stack. In this process, we evaluate the completeness, correctness and consistency of the selected settings and the required integration code. In particular, OEM-specific aspects are also considered, such as provided software components.
AUTOSAR
For more information On our AUTOSAR Services please contact us. Please find your contact person at: www.vector.com/contact
MICROSAR Coaching In MICROSAR Coaching, installation of the MICROSAR software is performed with your concrete application, which takes your specific requirements into consideration. We focus on addressing your individual needs here. For example, we can support you in: > Initializing the hardware, including CPU clock and PLL > Integrating the MICROSAR components in the project structure > Individual configuration of the operating system > Starting and stopping the bus communication depending on the network state > Providing the necessary I/O signal interfaces, including signal processing via the RTE > ECU and mode management in power up and shut down > Integration of diagnostics, error memory and memory management in your ECU software > Linking of the applications to watchdog management > Integration of further standard software from the OEM The included Premium Support contains on-site support in addition to the telephone and email Hotline. Based on the specific objectives that were agreed on, we ensure individual support of your project.
AUTOSAR Consulting In the framework of AUTOSAR consulting, together with you we can work out individual, technical solutions to various technical questions related to AUTOSAR: > Definition of an AUTOSAR-conformant software architecture > Optimal use of the AUTOSAR tool chain > Migration of existing software to the AUTOSAR architecture > Conceptualization of gateway functions > Structuring of MATLAB/Simulink models to be linked as software components via the RTE > Interfacing external peripheral components > Hardware-dependent Sleep and Wakeup concepts under consideration of individual quiescent current requirements > Consideration of requirements related to Functional Safety (ISO DIS 26262) We typically perform these consulting activities as customized workshops. This ensures that the worked-out solutions optimally fit into your ECU project. Software Development 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.
2/55
Solutions with CANbedded
The software implemented in automotive ECUs can be either infrastructure software or application software. The latter implements the desired functionality, while the infrastructure software includes the operating system, communication software and fundamental input and output services. The use of uniform communication protocols is absolutely necessary when setting up networks in a vehicle. The use of standardized software components ensures easy portability and reliable integration of ECUs in the vehicles network for the automotive OEM and its suppliers. In addition, the software components lead to a substantial reduction in development costs. CANbedded Vector develops high-quality and innovative software components for use in the automotive industry. One focus of the product line is on ECU communication, an area in which Vector has well-founded knowledge. The necessary hardware drivers are also important here. CANbedded products from Vector are available for systems without AUTOSAR. You can obtain them for the CAN and LIN networks as well as for the J1939 protocol. In addition, Vector can offer 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 Vectors 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.
CANopen For CANopen communication, Vector offers source code for master and slave ECUs. The source code contains all functions and services required for the CANopen protocol, which are standardized by CiA. Detailed information on this can be found beginning on page 3/20. Uniform solution Network communication is described in a database. It is used to configure the software components and serves as a foundation for Vector development and test tools. This gives software developers a universal and uniform solution, from simulation and design to testing and validation. Further information on tools for development and testing of automotive networks can be found in the combined product catalog Development of distributed systems and ECU testing. Communication Software for AUTOSAR Systems Vector also provides AUTOSAR-based communications software. This software is available for the CAN, LIN, FlexRay, MOST and Ethernet/IP bus systems. Further information and a description of the available software modules can be found in the AUTOSAR section beginning on page 2/0.
3/0
COMMUNICATION SOFTWARE
3/1
>> CONTENTS
CANbedded CANbedded J1939 CANbedded LIN Communication CANbedded Gateway CANdesc and CANbedded DEM Identity Manager GENy CANopen Master Source Code CANopen Slave Source Code Feature Matrix CANopen Source Codes CANerator CANopen XCP Professional 3/2 3/6 3/8 3/12 3/14 3/16 3/18 3/20 3/24 3/26 3/28 3/30
CANbedded
Basic software for CAN communication
Vector CANbedded basic software lets ECUs exchange information over the CAN bus. As a part of the ECU software, it handles communication-related tasks as specified by the OEM. With CANbedded, your ECU is able to efficiently communicate with other ECUs in the vehicle and with an external service tester. CANbedded is available in variants for most OEMs and for a large number of microcontrollers. CANbedded consists of the configurable software components CAN driver, Interaction Layer, Network Management, Transport Protocol and Communication Control Layer, which you can combine as necessary to form a communication stack. This provides you with a reliable foundation for your ECU. Overview of Advantages: > Reliable and tested through many years of development > Generated source code that is scalable and applicationspecific > Low memory requirement and fast runtimes > Supports over 80 different hardware platforms > Available in platform-specific and OEM-specific variants > Clearly defined and uniform interfaces > Easy to port to other platforms and OEMs > Easy to integrate in your ECU software
Application Areas CANbedded lets users focus their efforts completely on their functional software, because the CANbedded stack handles OEM-conformant sending and receiving of messages over CAN. Vector offers OEM-specific CANbedded variants for most OEMs. The CAN driver (the only hardware-specific component) is available in an optimized version for many different hardware platforms (8 to 64 bit controllers). The use of CANbedded in all of a networks ECUs assures compatibility of all communication stacks. This reduces development costs and test effort. A single-channel variant of CANbedded has been optimized for use in ECUs connected to a single CAN bus. A multichannel variant is also available for communication over multiple CAN channels. You can extend the CANbedded stack with additional basic software from Vector for your specific application: > CANbedded Gateway > Diagnostics: CANdesc > Commercial vehicles: CANbedded J1939 > Measurement and calibration: CCP or XCP For information on these extensions, please refer to the specific datasheets on the following pages.
3/2
Overview of the CANbedded software components
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 CANbedded provides simple interfaces (APIs) that are identical for all applications. If possible, the API is standardized over all OEM and hardware variants. This lets the user quickly and conveniently integrate CANbedded in the ECU software. The CANbedded components route asynchronous events such as receiving of CAN messages, bus wake-up or different error states (Assertions) to the application by means of configurable callback functions. You can configure the precise set of generated APIs and callbacks to optimally adapt them to the needs of your specific application. The Vector tool chain optimally supports you here. CANbedded consists of the software components described in the sections that follow. Vector would be glad to assist you in selecting the components you need. CAN Driver The CAN driver provides an interface for higher software layers that is as hardware independent as possible. This enables platform-independent use or re-use of the higher software layers. All necessary settings such as parameters for the hardware acceptance filter or Bus Timing Register are made at configuration time. The configuration tool GENy from Vector offers preselections for configuring these filters and registers.
The following basic functions are provided by the CAN driver: > Initialization of the CAN controller > Sending of CAN messages > Receiving of CAN messages > Overrun and error handling > Notification via wake-up events Interaction Layer (IL) The IL operates signal-oriented and is responsible for: > Sending messages depending on the send types of the signals they contain (Cyclic, OnEvent, IfActive, etc.), > Timeout monitoring of Rx messages and signals, > Notification of sending and receiving of signals. The IL is available in OEM-specific variants. Network Management (NM) The main task of Network Management is to manage the sleep and wake-up states of a networks ECUs. This functionality is handled by the NM CANbedded software component, which is available in different variants. Depending on OEM requirements, either OSEK NM, AUTOSAR NM or another OEM-specific NM algorithm is used. Transport Protocol (TP) By default, the CANbedded Transport Protocol conforms to ISO 15765-2. OEM-specific TP variants are also available, e.g. VWTP or MCNet. The ISO 15765-2 conformant variant is available in either
3/3
Configuration and parameterization with the GENy configuration tool
the 1999 variant or the 2004 variant and with different addressing methods (Normal, Extended, Normal fixed, Mixed). Communication Control Layer (CCL) The CCL simplifies integration of the CANbedded software components in your ECU software, such as CAN driver, IL, TP, NM, and other CANbedded options CANbedded Gateway, CANbedded J1939 and CANdesc. It manages defined system states (PowerOn, StartUp, ShutDown, Stop/Sleep, Normal) as well as communication states (Net request, Net release). It can coordinate state transitions (WakeUp and GotoSleep) according to the requests. The CCL offers the following functions: > Initializing the CANbedded software components > Calling periodic functions of the CANbedded software components such as Timer Tasks or State Tasks. > Controlling the bus transceiver Special CCL Functions > The CCL already contains OEM-specific communication requirements such as Wakeup Prevention and Minimum Communication Activity. > The CCL supports what are known as multipurpose ECUs (for details, see datasheet on the Identity Manager.)
Configuration You configure CANbedded with the PC-based configuration tool GENy. GENy utilizes information from the communication database (e.g. the DBC file from the OEM) as well as manual settings. GENy generates parameterization files based on the configuration. They contain the parameters and function calls of the CANbedded software components that are used. For example, the initialization sequence for software components is defined in the CCL configuration. Scope of Delivery You get the CANbedded components as C source code. In special cases, e.g. for time-critical applications on small microprocessors, certain portions of code may be programmed in Assembler. The scope of delivery of CANbedded includes: > GENy configuration tool as executable Windows program > C header and source files > Documentation and sample programs with makefiles
3/4
The CCL coordinates the state transition Wakeup
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
Additional basic software from Vector that is relevant to CANbedded: > CANbedded J1939 > CANbedded Gateway > CANdesc for diagnostics > Measurement and calibration with XCP/CCP > CANbedded LIN > CANopen Master and CANopen Slave You will find details on these products in specific datasheets on the following pages. 3/5 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.
Vector offers a comprehensive range of products and services for your CAN projects
CANbedded J1939
Embedded Software Components for J1939 Applications
Overview of Advantages > Convenient configuration via GUI > Code efficiency due to broad configurability of the software > Good portability due to hardware-independent API > Easy to integrate other standard components (e.g. transport protocol, diagnostics, etc.) The CANbedded J1939 package contains software components for SAE J1939-based applications. These components provide functions for basic communication between ECUs, as they are needed in heavy-duty vehicles. CANbedded J1939 is based on software components of the CANbedded product line; for details please refer to the CANbedded datasheet. Vector CANbedded J1939 software components are available as source code. Application Areas > Powertrain and chassis ECUs in heavy-duty vehicles > FMS (Fleet Management System) > Terminals and agricultural implements Functions The following J1939 software components are available: > J1939 Base Module: Contains queues for sending and receiving J1939 messages (PGNs), static address claiming (J1939-NM) and an interface to OSEK/VDX-OS
3/6
> J1939 Module Virtual ECUs: Multiple instancing of the software on a CAN channel for implementing multiple independent J1939 nodes on one ECU > J1939 Transport protocol BAM > J1939 Transport protocol CMDT > J1939 Dynamic Interaction Layer: Standard access to the signals of PGNs with variable CAN identifiers (node address, priority) via macros. Some applications use multiple CAN buses. In this case, the CAN driver and the J1939 components provide a multi-channel interface. Supported Standards J1939 software components are based on the following international standards: > ISO: International Organization for Standardization > SAE: US Society of Automotive Engineers Many different projects with international automotive OEMs have confirmed that the Vector software components conform to these standards.
J1939 software architecture
Solutions for ISO11783 and NMEA2000 We offer a CANbedded J1939 extension for ISO11783 (ISOBUS) and NMEA2000. It contains the following functionalities: > Dynamic address claiming (J1939-NM) > ETP transport protocol and FastPacket > Working sets
Training We offer various courses and workshops for CANbedded J1939 in our classrooms as well as at our customers sites. For further information on individual classes and dates please visit: www.vector-academy.com
Properties of the J1939 Software Components > Configurable standard components > C source code is provided for easy handling during integration > Low ROM and RAM memory requirements due to excellent scalability > Runtime efficiency > Generation of parameter settings and configurations > Easy to integrate in application software > Components are compatible with the SAE J1939 standard Configuration The PC-based GENy software tool is used to configure and generate the CANbedded J1939 software components. Scope of Delivery The CANbedded J1939 product includes: > GENy for configuring the software components > C source code > C header files > Documentation, user manual, Readme > Sample programs
Optional Services Vector can perform project work for you covering these aspects: > Adaptation of software components to other target platforms > Extensions for ISOBUS and NMEA2000 > Extension of standard components to add your specific functions > Flash programming This is supplemented by telephone and e-mail hotlines, special workshops focusing on OEM-specific aspects and consultation on software integration tailored to your needs. This reduces your development time and development costs. Supported Hardware Platforms CANbedded J1939 is available for many different controllers and compilers. You will find a current listing on the Internet at: www.canbedded.com/j1939
3/7
Configuring the J1939 system with a convenient user interface
EMBEDDED SOFTWARE
CANbedded LIN Communication

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

EMBEDDED SOFTWARE
Training As part of our training program, we offer a range of classes and workshops on CANbedded LIN Communication. For more information and the dates of our training courses, please visit: www.vector-acadamy.com
Availability Our LIN software components for motor vehicle ECUs are available for a large number of commonly used microcontrollers. For further information please visit: http://www.vector.com/vi_canbedded_lin_en.html
> Receiving of LIN messages (notification by flags and callback functions) > Sleep and wakeup handling > Protocol error handling > Timeout monitoring of messages > Checking of runtime behavior during the development phase (debugging) Application Areas LIN was developed to round out a collection of automotive protocol standards, but it has been adopted in other areas such as automation engineering as well. The focus is on cost-effective communication networks for ECU subsystems with low data rates. LIN therefore supplements existing bus protocols. Hardware Interfaces Two software components are needed for LIN communication. One component is a hardware-dependent low-level SIO driver, whose task is to implement abstraction of access to the serial interface. The second component, the LIN driver, is overlaid on this and provides an API to higher-level components. This API satisfies all of the requirements of the current LIN standard. The driver is a standardized and easy-to-configure software component 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.
This makes it easy to implement CAN-LIN gateways, which are usually implemented as master network nodes. LIN Master Transport Layer Since the master ECU usually has an auxiliary CAN channel, over which diagnostics are performed from a tester, the main task of the LIN master is to pass the received tester requests to the relevant LIN slaves. The LIN Diagnostic Transport Layer (DTL) is used for this; it offers two API types according to the LIN 2.0/2.1 and 2.2 specifications: > DTL Raw is used if the data already exist in segmented form (routing of CAN TP messages on LIN). > DTL Cooked accepts assembled data and segments them according to LIN bus requirements (Diagnostic Service Data Units). LIN Slave Diagnostics LINdiag is a very compact implementation of UDS 14229.3 diagnostics for LIN slave ECUs. It receives requests, routes them to the appropriate service and constructs the response in interaction with the application. This involves internal management of a diagnostic buffer to monitor for data consistency and overruns. To send and receive requests and responses LINdiag needs the LIN Transport Protocol, which is included in the delivery.
Overview of Design, Configuration and Integration Processes

EMBEDDED SOFTWARE
Further Options > Optional for slave ECUs: Diagnostic software components with associated transport protocol > Optional for master ECUs: Transport protocol with raw or cooked API > Gateway: CAN-LIN and LIN-LIN routing for master ECUs > SAE J2602: As a supplemental option, support of the SAE J2602 Recommended Practice specification is available for LIN drivers. > Flashing of LIN slaves Scope of Delivery The following items are supplied with the product: > Configuration tool (executable Windows program) > C sources for LIN driver and optional software components > Sample programs > Documentation and operating instructions
Licenses When the same hardware interface and same compiler are used the acquired licenses can be used for all devices of a processor type and any desired projects. Supplemental Services Vector also offers related project services such as: > LIN driver expansions > Support of other target hardware > Development of higher OEM-specific protocol layers, e.g. diagnostic protocol Services also include telephone and e-mail hotlines, special workshops with OEM-specific focus and individualized consultation on software integration with the goal of reducing development time and costs.
EMBEDDED SOFTWARE
CANbedded Gateway
Standard Embedded Software Components for CAN and LIN Routing
Overview of advantages > Selectable coupling of CAN and/or LIN networks with userdefinable routing relationships > Mature standard software component > Solid, lean and efficient foundation for your gateway ECU > Available for a large number of OEMs To exchange data between different networks, a gateway ECU is needed that only transports to the other network those messages or signals that are actually needed. Application Areas CANbedded Gateway is a mature standard software component for gateway ECUs between different CAN or LIN networks. CANbedded Gateway lets users define routing relationships simply and quickly. Both 1:1 and 1:N routings are supported in any direction. The CANbedded Gateway utilizes bus-specific standard components of CANbedded, and so it is hardware independent. It covers the specific requirements of many different OEMs. Functions The CANbedded Gateway contains complex mechanisms for receiving all messages and signals and then sending them to another network under consideration of filter and conversion rules. Users can select from:
> Signal routing > Message routing (with/without data queue) > TP (Transport Protocol) routing Signal Routing Routing of signals makes it possible to exchange dedicated information (e.g. momentary vehicle speed) between the networks. The send cycle times, send types and signal positions within messages all defined in the communication database may differ between the source and target networks. The values of the signals to be transmitted are not changed in the process. In case of an Rx timeout, the CANbedded Gateway implements a substitute value strategy. The signal to be transmitted is written and routed with a predefined signal value (default value or special substitute value). If routing relationships occur that cannot be resolved, e.g. if the signals of a routing relationship have different sizes, the application can use C callback functions to flexibly adapt signal contents before routing (e.g. by scaling signal values). Message Routing In routing of messages, the entire message is routed in either the interrupt or task context. This routing type is faster and more efficient than signal routing, but it cannot be applied in all routing relationships. In message routing, the messages may differ in their message-ID, send cycle and send type.
3/12
Gateway between CAN and LIN buses
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. If data is transmitted less frequently than the data is processed by the associated Rx event, the CANbedded Gateway sends the data of the last Rx event. Neither the signal layout within the message nor the signal values are changed here. The user can control gateway activities by configuring conditional routing. This saves on bandwidth during critical phases, such as during software flashing or diagnostic sessions. This is done by defining routing groups and assigning routing relationships to one or more routing groups. At runtime, the application can enable or disable routing of individual groups with the help of an API. TP Routing The TP Gateway is responsible for routing the transport protocol 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.
Configuration The CANbedded Gateway is configured with GENy, the configuration and code generator tool from Vector. The configuration process is based on a DBC or LDF/NCF description file. Routing relationships are defined either: > Automatically by OEM-specific algorithms based on clear rules > Manually by targeted selection of the signals and messages to be implemented Scope of Delivery > Configuration tool as executable Windows program > C source code > C header files > Documentation
3/13
Layer model of the CANbedded Gateway
EMBEDDED SOFTWARE
CANbedded Safe
Safety according to ISO DIS 26262 for ECUs with CANbedded software
Overview of advantages > Solution for all Automotive Safety Integrity Levels (ASIL) through ASIL D > Savings in qualification costs > Support of different ASILs on one controller Application areas You will receive CANbedded Safe from Vector for using CANbedded software in ECUs with safety-relevant functions. This solution is the result of collaborative work with TTTech, our partner with many years of experience in the field of functional safety. CANbedded Safe lets you develop OEM-specific applications for ECUs up to ASIL D per ISO DIS 26262. The modules from CANbedded Safe are SEooCs (Safety Elements out of Context), which are developed according to ISO DIS 26262 / ASIL D. Their use helps you to drastically reduce effort for qualifying your safety-relevant functions. Functions The SafeCom, SafeExecution and SafeSelfTest bundles from CANbedded Safe were implemented according to the AUTOSAR specification and are compatible with the CANbedded components. They contain the following specific functionalities:
SafeExecution: > Runtime monitoring of tasks > Flow control of safety-relevant functions > Memory protection and safe context switching SafeCom: > Safe intra-ECU and inter-ECU communication SafeSelfTest: > Periodic hardware checking The use of Runtime Monitoring, Flow Control, Memory Protection and Safe Context Switching makes it possible to let safety-relevant and non-safety relevant parts of your application software run next to one another on the same ECU without interference. This means that software parts whose correct execution cannot be verified cannot disturb safety-relevant functions unnoticed. Runtime Monitoring Runtime monitoring assures that tasks have sufficient computing time for their execution. Runtime monitoring is provided by MICROSAR OS SC2/SC4 and is validated to ISO DIS 26262 by the modules WDGM, WDGIF and WDGDRV from SafeExecution.
V2.0 2011-12
CANbedded Safe
EMBEDDED SOFTWARE
Training In the framework of our training program, we offer various training courses and workshops on CANbedded at our classrooms as well as at your business site. For more information on individual training events and a schedule, please go to: www.vector-academy.com
Contact and Availability The drivers of CANbedded and the MICROSAR OS module are hardwarespecific. Please contact Vector to find out whether the hardware you are using is already supported. We would be glad to provide you with information on OEM-specific variants as well as offer you customized support for your projects. Please find your contact person: www.vector.com/contact
Program Flow Monitoring Correct execution of safety-relevant application software is assured by the modules WDGM, WDGIF and WDGDRV. This involves using what are referred to as checkpoints in the safety-relevant application software. Memory Protection and Safe Context Switching The MICROSAR operating systems option SafeContext, which was developed to ASIL D, assures memory protection for ECUs with safety-relevant applications on suitable microprocessors (e.g. with MPU, the Memory Protection Unit). The option SafeContext is available for MICROSAR OS (SC3/SC4) and it is used to separate the various software parts from one another during task changes and interrupts. SafeContext prevents unauthorized writing by one software part to the memory of another that could corrupt the data. Safe Intra-ECU and Inter-ECU communication Data that is exchanged between safety-relevant applications must be checked for correct transmission. A checksum protects the data contents and the correct sequence of data is monitored by a message counter. If one of these checks fails, the application is informed, and it can react accordingly. This detects errors such as masquerading, failure or reversed data.
Hardware checking You can perform cyclic tests for error-free functionality of the ECUs various hardware components during operation using generic test functions of the SafeSelfTest package. The precise scope of monitoring that is necessary is project-specific. Vector would be glad to consult with you in selecting specific monitoring mechanisms for your project. Configuration The safety elements of CANbedded Safe are configured with the DaVinci tools. Product components > Software modules as library with C header files, optionally as source code > Instruction line based generator (for Windows XP/Vista/ Windows 7) > BSW module description files > Description files for DaVinci Configurator Pro > Documentation with Safety Manual
Implementation Safety-relevant functions are implemented by the Safety Elements out of Context (SEooC) from CANbedded Safe. They detect and handle potential errors in non-safety software layers. The SEooCs conform to ISO 26262 ASIL D and are developed according to the AUTOSAR specification. CANbedded Safe contains the following SEooCs: SafeCom: > E2ELIB: End-to-end library > Protection Wrapper: End-to-end protection Wrapper
SafeExecution: > SafeContext: Memory Protection and Safe Context Switching (option for MICROSAR OS) > WDGM: Watchdog Manager > WDGIF: Watchdog Interface > WDGDRV: Driver for internal watchdog devices > WDGEXT: Driver for external watchdog devices SafeSelfTest: > RAMTST: Tests for RAM memory > FLASHTST: Tests for flash memory > CORETST: Tests for the microcontroller core > IOTST: Tests for inputs and outputs
EMBEDDED SOFTWARE
Wide Availability of CANbedded

Supported Microcontrollers and Compilers
Controller Altera NIOS II with Bosch D-CAN controller Analog Devices Aduc703x AduCM330 Blackfin BF5xx Atmel AT90CANXX ATmega (X8, X4P, XC1, XM1) ATtinyX7 AVR32 T89C51CC00x Cypress PSoC3 Europe Technologies easyCAN Freescale 68HC08 DSP56F80x DSP56F83x HC12, HCS12, MC9S12, S12, MCS12 HCS12x, MC9S12x, S12x, MCS12x MAC 7100, MAC 7200 MC68k MCF52xx MCS08 MPC5xx Cosmic, Metrowerks Metrowerks Metrowerks Cosmic, IAR, Metrowerks Cosmic, IAR, Metrowerks ARM, IAR Microtec, Tasking DIABDATA Wind River Cosmic, Metrowerks DIABDATA Wind River, Green Hills, Metrowerks X/X X X X X X X X/X X X X X X X ARM X Keil X/HPInfotech, IAR HPInfotech, IAR IAR IAR Keil X X/X X X X X X ARM, IAR IAR VisualDSP++ X X X X Fujitsu 8L, 8FX 16FX, 16LX FR30, FR50 FR60 FR81 MB86R0x Infineon C16x C5x5 TriCore XC16x XC2000 XC800 Microchip dsPic33F PIC18 PIC24 Micronas CDC32xxG CEVF National CR16 NXP LPC2000 Green Hills X National, IAR X X Green Hills IAR X X/Microchip Microchip Microchip X X/X X X Keil, Tasking Keil GNU, Green Hills, Tasking Keil, Tasking Tasking Keil X X/X X X X/X X X Fujitsu Fujitsu Fujitsu Fujitsu Fujitsu GNU, QCC X X X [1] X X X X X MPC55xx, MPC56xx GNU X MPC5200 Compiler
CANbedded/ CANbedded J1939 CANbedded LIN
Controller
Compiler DIABDATA Wind River, Metrowerks, QCC DIABDATA Wind River, GNU, GAIO, Green Hills, Metrowerks
CANbedded/ CANbedded J1939
CANbedded LIN
V2.4 2011-12
EMBEDDED SOFTWARE
Controller SAF7780 SJA20xx OKI AVC-Core ML76Q25xx Panasonic MN101E MN103S
Compiler Green Hills Green Hills
CANbedded LIN
Controller ST7
Compiler Cosmic, Hiware GNU GNU, Keil, Tasking ARM, Green Hills ARM, Green Hills ARM Cosmic
CANbedded LIN
X X X
X/X/X X X X X/-
X X X X
ST9 ST10
ARM IAR
X X
ST30 STA20
Panasonic Panasonic
X/X
STM32 STM8A Telechips X X X
Renesas Electronics (NEC/Renesas) 78k0 78K0R 78K0S H8 tiny H8S, H8SX M16C M32C M32R R8C R32C SH2, SH2-A Renesas (NEC), IAR Renesas (NEC), IAR IAR Renesas Renesas, IAR Renesas, IAR Renesas, IAR Renesas, GAIO Renesas, IAR Renesas, IAR Renesas, Green Hills, GAIO, IAR Renesas, Green Hills, QCC Renesas (NEC), Green Hills, IAR Keil X X X X X X X X X X X X X X/X
TCC800 Texas Instruments TMS320 TMS470
ARM
Texas Instruments, QCC Texas Instruments, ARM, Green Hills Texas Instruments, ARM Toshiba Toshiba ARM Green Hills GNU, Green Hills GNU
X X X
TMS570 Toshiba TLCS870 TLCS900 Tx03 TX39 TX49
X X X X X
SH4 V85x
X X X
Xilinx Microblaze Vector CANoe osCAN Emulation Microsoft VisualC X X X
Silicon Labs C8051F5XX STmicroelectronics SPC56xx DIABDATA Wind River, GNU, GAIO, Green Hills, Metrowerks X X X
[1] = Currently in development
CANdesc and CANbedded DEM

Software components for diagnostics
3/14
Overview of Advantages > OEM-independent implementation of your application software > Quick, simple and uniform interface to the OEM-specific diagnostic protocol in the desired version > Available for many bus systems > Together with CANdelaStudio CANdesc gives you a comprehensive diagnostic solution from specification to embedded software > Multiple diagnostic configurations with up to 31 different parameter sets > Guaranteed consistency between diagnostic specification and generated code The diagnostic software component CANdesc (desc = diagnostic embedded software component) is the uniform implementation of the diagnostic protocol for different automotive OEMs. CANdesc is generated according to the configuration based on the diagnostic specification (CDD file). To implement the error memory, you can extend CANdesc with the CANbedded DEM component, which gives you a fully OEM-specific diagnostic solution for your ECU. Application Areas > ECUs for passenger and commercial vehicles > ECUs in CAN, MOST, FlexRay and other communication systems
CANdesc and CANbedded DEM can easily be incorporated into a CANbedded communication stack from Vector. However, you can also use the two software components in your communication stack. Functions CANdesc and CANbedded DEM are conformant to the OEM-specific diagnostic specification and are available for a number of different OEMs. They contain the following functionality: CANdesc: > Provides a signal-based interface as a uniform interface to the application. This simplifies interfacing of diagnostics to your ECU software. > Full implementation of diagnostic services $28 (CommunicationControl), $2A (ReadDataByPeriodicIdentifier) and $2C (DynamicallyDefineDataIdentifier) > Validation of diagnostic requests in reference to Service Id, Session, Sub-Service Id, Format, Session and Security of a sub-service > State control (depends on the CANdela database, e.g. Session or Security) > Assurance of data consistency in parallel diagnostic requests from the same tester or multiple testers > Generation of a template including the necessary function stubs that lets you realize your own diagnostic implementation quickly and easily.
Complete generation of the ECUs diagnostic software
Example of Code Sizes Microprocessor: Motorola HC12, MC9S12P128 Compiler: Cosmic 4.7 13 Diagnostic services and 40 subfunctions are implemented Code size: approx. 6 kBytes Tables and constants: approx. 700 bytes RAM: approx. 90 bytes plus bytes for the diagnostic buffer
Extended setup with services 0x2A and 0x2C: The code size is increased to approx. 14 kBytes. The RAM size depends on the size of the scheduling table and the number of dynamically defined data identifiers.
> Optional: Implementation of the Diagnostic Adaptation Protocol (DAP) for MOST ECUs CANbedded DEM As soon as the application software detects errors, it must initiate saving of the related Diagnostic Trouble Codes (DTC). The CANbedded DEM component from Vector can be used for this task. For each error (DTC), the software component stores the following information in error memory: > DTC status byte > Environment data > Cycle counters > Fault detection counter > Aging counter When CANbedded DEM is combined with the diagnostic software component CANdesc, you get a complete implementation of the following error memory related UDS services: > $14 Clear diagnostic information > $19 Read DTC information > $85 Control DTC setting Configuration You configure CANdesc and CANbedded DEM with the GENy tool and a CANdela file (CDD). To create this file you will need the tool CANdelaStudio Version 6.5 or higher.
The use of CANdelaStudio offers CANdesc users significant advantages. For more details, please refer to the CANdelaStudio datasheet in the diagnostics catalog. Handling of Variants If your ECU requires diagnostic configuration variants, CANdesc and CANbedded DEM offer a powerful solution for this. With GENy you can define up to 31 different parameter sets and store them in the ECU in a resource optimizing way. This avoids redundancies in the ECU software, because identical interfaces to the same data, services or DTCs are merged in the generated diagnostic code. Scope of Delivery > GENy configuration tool as executable Windows program (for Windows NT/2000/XP/Vista/Windows 7) > Documentation/users manual/Readme > C source code for CANbedded DEM Additional Services Vector offers project services related to diagnostics: > Adapting the application to CANdesc > Implementing error memory strategies > Process consultation in the area of diagnostics > Testing diagnostic implementations for ECUs.
3/15
Diagnostic software (CANdesc and CANbedded DEM) in the diagnostic development process
EMBEDDED SOFTWARE
Supported OEMs
For OEM-specific Basic Software
Vector offers embedded software for a large number of OEMs. Additionally, a version without vendor-specific characteristics is available. Depending on the OEM the software is available for conventional (CANbedded) and/or AUTOSAR-conformant ECUs. The diagnostic software and the Flash Bootloader contain OEM-specific diagnostic services, fault memory or flash processes. Depending on the OEM the scope of the available diagnostic solution differs, e.g. UDS or KWP2000 is used as diagnostic protocol. Please contact Vector. We will help you to find the optimal solution for you requirements. OEM B BAIC Brilliance BMW BYD C CHANA Chery Chery Quantum Chrysler Claas D DAF Daimler Dongfeng F FAW FCC FIAT Fisker Ford
V2.5 2011-12
OEM G GAC Geely GM Great Wall Motors H Honda HMC I Isuzu Iveco J JAC Motors Jaguar / Landrover
Communication X X X X
Diagnostic Software X X X X
Flash Bootloader X
X X
X X X
Communication X X X X
Diagnostic Software X
Flash Bootloader X
X X
X X
X X
X X X
X X X X X
X X X X X
M MAN X X X X X X X X X
X X X
Mazda Mitsubishi N NAC Nissan P Porsche PSA R Renault S SAIC SsangYong Subaru Suzuki
X X
X X
X X
X X X
X X X
X X X
X X
X X
X X
X X X X X X
X X X X X
X X X X X
X X X X
X X
X X
Foton
EMBEDDED SOFTWARE
OEM T Toyota V Volvo AB VW/Audi
Communication X
Diagnostic Software X
Flash Bootloader X
X X
X X
X X
OEM 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
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 them and also results in growing costs. Cost savings are realized by reducing administrative effort. This can only be achieved with the assistance of intelligent solutions that can manage the many different variants. Based on our many years of working together with automotive OEMs and suppliers, Vector knows these continually recurring use cases well and has developed optimized solutions especially for them. Use cases Practice shows that it is primarily the following three use cases that recur frequently: > Physical multiple ECU > Virtual multiple ECU > Multiple configurations ECU The solution approaches presented below lead to substantial simplification, reduce administrative effort and thereby reduce costs. Identity An identity identifies an ECU. It determines which variant of the ECU should be activated (e.g. which door side). So, an identity is the configuration of an ECU that is active at run time, based on a description file. An ECUs identity is set when the ECU is initialized. A typical case of physical multiple ECUs are the ECUs for the driver and passenger side doors. These ECUs have nearly identical functions. However, there are differences in the receive and send messages, diagnostics and Network Management address. The steps: Develop an ECU that will later be used for both door sides. Load the database that covers the ECUs in the GENy configuration tool and select both ECUs simultaneously. Configure the Identity Manager as a physical multiple ECU and assign a separate identity to each of the nodes (Left ECU, Right ECU). There are essentially two different ways to proceed in coding: If the message layout is identical between the identities, utilize the manual buffer overlay in GENy. This means that the same signal APIs can be used regardless of the currently active identity. So, only one application needs to be developed, but the ECU acts differently to the outside world depending on the identity which is initialized. The differences are automatically read out from the DBC file. In the second case, buffer overlaying is not needed. Instead, differentiate between the left and right sides using generated macros in the code. It is also easy to implement crossovers of receive and send messages between the two door ECUs while optimizing resources. 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 ECUs identity.
3/16
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. The different communication nodes are derived from one database. In the configuration tool GENy, you only need to select those nodes that will be implemented and then configure a virtual multiple ECU in the Identity Manager. All nodes are assigned to one identity. The identity operates from a node superset and all necessary information on the nodes.
A typical application involving multiple configurations is the development of ECUs for both a current car line and a new car line. These ECUs are also referred to as carry over ECUs. Changes made within the associated database are often very extensive. It is possible to use a completely different signal layout or use different messages for different model series. The new configuration could even support a different number of CAN buses. 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 ECUs identity is determined by a function call at the start.
GENy
PC-Tool for Configuring Embedded Software Components
GENy is the convenient configuration tool for software components from Vector. It was created for development processes of the future. It is used to configure CANbedded components, AUTOSAR communication modules and the Flash Bootloader for use in production ECUs. Features and Advantages GENy is a developmental offshoot of the previous configuration tools CANgen and DBKOMgen. The GENy architecture was completely redesigned based on experience with those two tools. 3/18 The following properties characterize the design: > Thoroughly modular structure due to its static framework, stand-alone graphic user interface (GUI) and dynamically reloadable components > Reloadable hierarchies make it well suited for any configuration task (CANbedded, LIN, FlexRay) > A cleverly designed framework mechanism interprets and manages dependencies in configuring components > XML is used throughout as the file format, both for the component descriptions (Attributes) and data saving > Open interfaces offer simple expandability
This makes GENy a scalable and fully generic configuration editor/generator that permits consistent configuration from a single integration environment, even in complex heterogeneous systems. Vectors many years of experience in the area of ECU development ensures optimal workflows between OEM and suppliers without altering their tasks or roles. GENy is a collection of components (not a rigid program block); therefore it can also be expanded very easily by adding auxiliary components. GENys graphic interface makes it very easy to use and intuitive. GENy always appears with the same look and feel independent of the components to be configured. The configuration data is shown and processed in a hierarchical tree structure. This makes navigation user friendly, and the user gets a clear view of all options. The Configuration View can be modified manually or via an external XML file. The latter is essential for an OEM-specific appearance of GENys GUI and guarantees that parameters will have functionally 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
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 indicates potential errors (e.g. mistakes in configuring) and other important information. This is done to avoid tedious debugging efforts. 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 Functions GENy is the tool for configuring any software component. Configuration 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)
Application Areas The GENy configuration tool is always used in conjunction with other Vector software components for communication and diagnostics. GENy fulfills AUTOSAR Consortium requirements.
3/19
GENy Navigation View
TOOLS & COMPONENTS FOR OPEN NETWORKING
CANopen Source Code

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

The CANopen Source Code by Vector is available for many popular microcontrollers. For current information, please visit our website: www.vector.com/sourcecode
NMT Slave The code supports both guarding and heartbeat. It is possible to react to heartbeat messages of other nodes (heartbeat consumer). This makes it possible to set up highly efficient monitoring mechanisms in a network. User-specific emergency messages can also be generated. The code supports an interface for non-volatile storage of parameters. Here it is assumed that the memory is available via a file system or as flash. Mini-Master The full functionality of a CANopen manager is not required for many embedded networks. Often, by limiting functionality, emphasis can be placed on requiring very few resources and the simplest possible use. This is the purpose of the add-on Mini-Master. It contains: NMT Master control of the status machine of the NMT slaves to start the network, for example. Monitoring of nodes by means of node guarding. SDO Client the user can thus also initiate an SDO transfer. This makes it possible to adjust settings in the object directories of other nodes and to call up data that is not available through PDO (e.g. for diagnostic purposes). SYNC Producer This module can be used to periodically send the SYNC message. LSS (Layer Setting Services) Among other things, CANopen devices require a setting of baud rate and node number. Devices without access possibilities via switches (e.g. watertight sensors) require a setting of these values via the CAN bus itself. CANopen specifies the LSS (CiA 305) for this. The necessary services are provided in the form of source code modules by the LSS Slave and LSS Master add-on modules.
Adaptation of the Code Before the code is translated, the user can specify the qualities to be supported allowing the code to be used even on systems with very limited resources. The adaptation occurs via the #define instructions that are set in a configuration file. By using the CANerator tools (sold separately), this adaptation is simplified significantly. Local Object Directory 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. Such an object directory contains the object's attributes and a pointer to the actual memory location. For each object it is possible to initiate callback functions with user-defined functionality when reading or writing. Thus, for example, an area test can be implemented when writing an object. With the aid of the CANopen CANerator, this object directory can be created automatically. For additional functional details, please refer to the CANopen CANerator product information. Adaptation to a Target Hardware To use the CANopen Source Code on a microcontroller platform, first an adaptation is always necessary to abstract the CAN controller and the specific timer and interrupt system. Of course, the relevant compiler is also considered here. Vector offers prepared adaptations for many platform combinations. Support during Integration We can also support you during the integration of the CANopen Source Code into your environment. Our support services range from custom-tailored training solutions to workshops to project work.
Feature Matrix CANopen Source Code
CANopen Source Code1 Feature Local object dictionary with mandatory entries: 1000, 1001, 1018 Object dictionary: pre-build configuration Maximum number of parallel SDO Servers SDO server protocols2 Maximum number of parallel SDO Clients SDO client protocols2 NMT slave state machine Node guarding Life guarding NMT master (NMT0 message) Heartbeat producer Heartbeat consumer Store/restore (objects 1010/1011) Error behavior (1029) EMCY producer EMCY consumer (object 1028 not supported) Number of PDOs (adjustable) PDO variable communication parameters PDO variable mapping PDO granularity (minimum size of mapped objects) 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 LSS Slave
Legend:
CANopen Source Code1 Add-On Package Mini-Master LSS Slave LSS Master 1 [e], [s], [b]
16 [e], [s], [b] (max. 1261) 0 n1 8 bit (byte boundary)
V1.1 2011-03
= available = not available

1 2
= =
The overall number of messages handled by the slave source code is restricted to 255. [e] expedited [s] segmented [b] block
CANerator CANopen
Generation and Configuration of Source Code
CANerator CANopen is a tool for managing source code configuration settings and for creating and generating object directories automatically. Features and Advantages The CANopen communication profile distinguishes itself through its broad scalability for use in embedded networks. It offers many opportunities for representing necessary device functionality and at the same time accommodating the small resources of a microcontroller. Vectors CANopen Master and Slave Source Code therefore offers a multitude of setting possibilities. The price for this flexibility is the increased complexity of the development process. In addition, there is the requirement for reusability and more flexible adaptability of software for entire spectrums of various devices from a manufacturer. In addition to the actual configuration of the source code, the developer of CANopen devices must also create an object directory. This forms the interface between application and CANopen communication and serves to describe the device characteristics. With CANerator CANopen, the software developer has available a tool that supports him comfortably in his tasks and significantly speeds up the development process.
Application Areas CANerator CANopen is intended for use together with CANopen Master and Slave Source Code from Vector. Functions CANerator CANopen makes available the following functions: > Configuration of the source code with the aid of a clear display of all #define instructions > Creation and automatic generation of the object directory as source code > Automatic creation of EDS files > Simple management of projects These functions will be described in detail below. Source Code Configurator CANerator CANopen displays all relevant settings of the source code (#defines) in a tree view. An instrumentation of the source code allows the display of only the relevant #define instructions and structures them in problemrelated groups. 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.
3/28
Creating the EDS File with the Aid of CANeds
Generation of Object Directory Thanks to complete integration of CANeds, all capabilities of this tool are available. These are described in detail in the CANeds product information. With the aid of CANeds, all standard objects of the object directory can be created with drag and drop. In addition, it is possible to define manufacturer-specific objects. The objects are already provided with default values that can be modified if necessary. After the developer has specified the objects, CANerator CANopen displays the structure of the object directory in a hierarchical tree structure. Then variables in the program are assigned to objects. These are ultimately the interface between the protocol-specific part of the software and the application. In addition to the symbolic specification of variable names, the CANerator also supports 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.
Project Management CANerator CANopen allows the easy and comfortable management of profiles. When a set of settings has been created, it is stored under its own name. Different profiles of this type can be used in one and the same project for generation. Therefore it is possible, for example, to provide a project with or without debugging information and to change between the profiles with the touch of a button. Another application is the creation of profiles for various device types on the basis of a source code. This simplifies the single source principle. As project documentation, an HTML page is generated, which in addition to general project information contains a list of all objects with their attribute values as well as a list of all settings.
3/29
CANerator CANopen in Configuration Mode: All #define Settings can be Edited Clearly.
XCP Professional
Measuring and Calibrating via CAN, FlexRay and Ethernet
Overview of advantages > Can be activated/deactivated in production operation > Easy to configure with PC-based tool > Low memory requirement and short execution times based on scaling of the software component to your requirements > Transport layers available for CAN, FlexRay and Ethernet > Compatible with MICROSAR BSW modules (AUTOSAR) Application Areas Automotive in-vehicle ECUs are measured and calibrated with the XCP Protocol (Universal Calibration Protocol) the successor to CCP (CAN Calibration Protocol). XCP was standardized by ASAM (Association for Standardization of Automation and Measuring Systems), a process in which Vector played a leading role. By clearly differentiating the Protocol Layer and Transport Layer, XCP is able to support many different bus systems: CAN, FlexRay and Ethernet. On the PC side, the CANape tool is used as the XCP master. Its counterpart in the ECU is the XCP slave. This is implemented by the XCP Professional software component. It not only contains all ASAM functional content, but useful extensions as well. You can use XCP Professional together either with a conventional communication stack or in AUTOSAR systems. In either case, it is unnecessary to modify the XCP software. If a software stack by a third-party producer is used, small modifications to the XCP Transport Layer (TL) may be necessary. Vector would be glad to assist you in this area.
3/30
Functions XCP Professional contains all necessary functions for communicating with the XCP Master, such as: > Synchronous data acquisition based on DAQ lists > Read and write accesses > Initialization and switchover of the memory area for calibration data > Support of time stamps > Protection against unauthorized writing and reading in memory > Shutoff of XCP in production operation by a single function call > Access protection by Seed & Key support > Synchronous data stimulation (STIM) and Resume mode > Flash and EEPROM programming > Communication mode: Block transfer > Transmission of service request packets > Support of AUTOSAR CRC modules > Bit modification and short download > Configuration by GENy > Generation of an a2l file based on the ECU configuration Synchronous Data Stimulation (STIM) To optimize algorithms and parameters, you can use XCP over the bus system to read a measured signal from the ECU (DAQ) and modify it with a simulation model (e.g. MATLAB). The re-computed value is then written back to the ECU (STIM). Reading and writing are performed synchronously in a predefined time interval (Bypassing).
XCP Professional is available for CAN, FlexRay and Ethernet
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
Resume Mode The Resume mode permits cold-start measurements, e.g. to check ECU behavior in the wakeup phase. This involves activating the XCP stored in the flash memory immediately after a cold-start even before the application starts. Sending of the measured values begins automatically, and they can be logged for later evaluation. Flash and EEPROM Programming The Vector XCP component is not only able to store measured values in RAM, but also in flash or EEPROM memory. To do this, XCP executes callback functions in which the application could activate the flash algorithms, for example. This gives you the option of individually adapting the algorithms to the flash or EEPROM memory being used. 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.
Transmission of Service Request Packets Service request packets let you transmit lines of text. They are stored in program code, and when the program section is executed they are sent to the XCP master where they are displayed. This function is very useful primarily during system development and in debugging. Configuration XCP Professional is configured with the PC-based GENy configuration tool. Compiler switches may be used to deactivate unneeded functions, and this reduces memory loading. When XCP transmission is started, the list of supported functions is communicated to the XCP master via the XCP plug-and-play mechanism.
3/31
CANape as XCP Master CANape, the all-round tool for measurement, calibration and diagnostics of ECUs, is the XCP master, while the ECU acts as the XCP slave. The XCP slave allows CANape to access the measured signals and calibration parameters in the ECU with the help of an ECU description file. Values can be displayed or edited in physical units. The key properties of CANape related to measurement and calibration are: > Time-synchronous real-time acquisition and visualization of internal ECU signals with XCP/CCP, of signals from CAN, LIN and FlexRay buses and from external measurement equipment
> Online calibration via XCP/CCP, real-time stimulation via XCP and offline calibration > Flash programming of the ECU via XCP/CCP or the diagnostic protocol > Rapid prototyping for functional development by bypassing a MATLAB/Simulink model with the help of CANape Additional information can be found in the ECU Calibration product catalog.
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 worlds 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 Vectors MICROSAR OS is an AUTOSAR-conformant operating system. The operating system core conforms to the practicle-proven OSEK/VDX standard. In addition, MICROSAR OS may include the optional extensions 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 Vectors classrooms or on site. Vector assists the ECU development process with on-site startups, code reviews and other development supporting software tools.
4/0
OPERATING SYSTEMS
4/1
>> CONTENTS
osCAN High Resolution Timer TimingAnalyzer 4/2 4/4 4/6
osCAN
The real-time operating system based on the OSEK/VDX standard
Overview of advantages > Small, fast and resource-saving operating system core > Short boot times > Stack monitoring at runtime (deactivatable) > Internal fault trace (deactivatable) > Component management for integration of sub-projects > Supplied as source code > Quality process fulfills SPICE Level 3 > Graphic configuration tool for easy configuration of the operating system > Simplified execution time analysis of osCAN applications by supplied TimingAnalyzer > Available for many 8, 16, 32 and 64 bit microcontrollers osCAN is a preemptive real-time multitasking operating system with properties optimized for use on microcontrollers. Vectors many years of experience in developing operating systems and drivers has made osCAN a small and robust operating system core. It is certified to OSEK/VDX specification 2.2. This open standard of the automotive industry provides a foundation for long-term stability and availability.
Application Areas Due to its static operating system architecture, osCAN is small and fast, and its use is beneficial wherever resources such as memory and processing time are in short supply. osCAN is especially ideal when extremely short boot times are necessary. Functions As a fully preemptive multitasking operating system, osCAN offers priority-driven task management and a wide variety of synchronization mechanisms. It can generate cyclic and singular time intervals as well as behave in an event-driven way. Its flexible interrupt strategy makes it possible to use system services even within interrupt service routines. In addition to functions defined in the standard, osCAN offers: > Monitoring of stack utilization at runtime > Internal tracing of system calls > Extended error checking at runtime > Clear and concise documentation of the configuration in HTML With the optional High Resolution Timer, you can implement resolutions higher than 1ms for the timers, without simultaneously increasing interrupt load. Depending on the controller, resolutions in the microseconds range are possible.
4/2
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
Complete solution from Vector Vector provides you a completely tuned solution for developing ECUs. Along with the operating system, you get protocols and drivers for CAN, LIN or FlexRay. For more detailed information, please refer to the relevant datasheets. Configuration An easy-to-use graphic configuration tool lets you define all operating system resources before compiling. To assure portability, the configuration is saved in the standardized OIL format (OSEK Implementation Language). The configuration tool offers component management, which lets you implement sub-applications simultaneously in parallel processes. Next, the sub-applications are integrate into a total application. This enables short development times and spatially separate developments. Properties: > Easy to operate graphic user interface > Automatic checking for completeness and consistency > Convenient system scaling > Component management > ORTI support
Supporting Tools The TimingAnalyzer design assistant simulates and computes task execution times for you. The analysis is performed for each task and each interrupt with the following parameters: Priority, period, execution time and deadline. The graphic user interface offers clear and concise visualization of system behavior. With the help of the CANoe osCAN Library, your application can be compiled into a DLL and integrated in a network simulation under CANoe. This allows the application to be tested even before the availability of first hardware prototypes. Many emulators already offer the option of observing application behavior on the operating system services level (OSEK Awareness). osCAN supports the ORTI interface required for this. Some UML and SDL modeling tools give you the option of configuring models for use with an OSEK/VDX operating system. This is possible, for example, with: > MATLAB/Simulink from Mathworks > TargetLink from dSPACE Related Vector products: > CANoe osCAN Library > TimingAnalyzer > High Resolution Timer
4/3
Scope of Delivery > Operating system core as source code > Graphic configuration tool (OIL) for Windows NT/2000/XP/ Vista/Windows 7 > Instruction line based generator > Documentation > Sample programs > TimingAnalyzer osCAN conforms to OSEK/VDX specifications > OSEK/VDX-OS 2.2 > OSEK/VDX-OIL 2.3 > OSEK/VDX-COM 2.2.2 > All conformity classes (BCC1, BCC2, ECC1, ECC2, CCCA, CCCB) > Size: 110 kB ROM, depending on platform and configuration
Availability The real-time operating system osCAN from Vector is available for many commonly used 8, 16 and 32 bit microcontrollers. For more information on the Internet go to: www.vector.com/oscan Additional Services Vector offers you worldwide support related to OSEK/VDX: > Training courses > Design consultation > Customer-specific implementations > Hotline > Software maintenance The scope and form of all services are aligned to your wishes and needs.
High Resolution Timer

Improve performance with high-precision timers for operating systems
An important property of operating systems is the precision of alarms; this in turn affects the resulting interrupt load. The alarm mechanism of an OSEK/VDX or AUTOSAR operating system is based on counters which are incremented by either software or hardware timers. When a counter reaches a preset alarm value, a predefined action is executed. The typical time resolution of such timers is 1 ms. If timer resolutions with a higher precision than 1 ms are required, the High Resolution Timer mechanism can achieve these enhanced precisions without simultaneously increasing interrupt load. Resolutions in the microsecond range are possible depending on the controller used. Features and advantages The High Resolution Timer for the osCAN and MICROSAR OS operating systems permits high-precision alarms with low system interrupt load (depending on hardware). An interrupt is only triggered when an alarm actually becomes due. 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.
Application areas The High Resolution Timer is designed for applications requiring high-precision timers but in which additional interrupt loads are unacceptable. Hardware requirements The High Resolution Timer can be used on all microcontrollers which have a free-running timer. The timer must also be able to trigger an interrupt when its value matches a user-definable compare value (compare-match). The clock speed at which the hardware timer is operated should be adjustable so that the desired level of accuracy is achieved. Configuration The High Resolution Timer is configured using the configuration tool for the Vector operating systems. This tool is used to adjust the prescalers according to the clock frequency of the microcontroller.
4/4
Alarms and Tasks
OPERATING SYSTEMS
4/5
TimingAnalyzer
Schedulability analysis/Trace visualization
The foundation for designing real-time systems is an analysis of the schedulability of tasks (schedulability analysis). Systems that employ a real-time operating system, such as the OSEK/VDX operating system or AUTOSAR OS, consist of tasks and interrupt service routines (ISR). Schedulability analysis shows whether a task or ISR could miss its deadline when all circumstances are taken into considerations. Properties and Advantages The TimingAnalyzer simulates scheduling tables and computes schedulability. The analysis is performed for each task and ISR with the information: priority, period, execution time and deadline. Various algorithms from scheduling theory may be selected. In the default setting, the best algorithm is selected for a given data record. 4/6 By using the TimingAnalyzer you can avoid the difficult and timeconsuming work involved in determining worst case timing situations, which is usually done by testing. The TimingAnalyzer is a tool for integrating familiar software components into a runnable system. The time savings in terms of program creation and the 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.
A graphic diagram offers an intuitive overview of the timing. It gives the application engineer a better understanding of program processing in the ECU. It also considerably reduces the risk of creating unreliable systems. Functions In the analysis, the TimingAnalyzer studies the timing of both tasks and ISRs. A special algorithm considers mutual interactions resulting from use of the resource operating system service. In the TimingAnalyzer you can input the time with which a task or ISR occupies the specific OSEK resource. The graphic representation simulates a possible task switching sequence. The simulated schedule can be examined by zooming in and measuring time intervals. Bitmaps of the graphic diagram can be saved for documentation purposes. Special functions > Schedulability analysis > Graphic simulation of schedules > Import and display of emulator traces
Analysis example in the TimingAnalyzer
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 attention 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

Controller Altera Excalibur NIOS II ARM ARM7-TDMI Cortex M Atmel AT91 AVR32 Freescale 68HC08 68HC12, S12 MAC71xx Mcore MPC55x, MPC56x MPC55xx, MPC56xx S12X Fujitsu 16FX 16LX FCR4 FR30, FR50, FR60 MB86 Infineon C167 Tricore XC16x XC2000 Intel PXA27x
V2.3 2011-12
Compiler
Controller Microchip
Compiler
Green Hills GNU, TaskingVX
dsPIC30 PIC18 PIC24
Microchip Microchip Microchip
Green Hills ARM
NXP LPC2XXX SAF7780 Green Hills ARM, Green Hills Green Hills
Green Hills IAR
SJA20xx OKI ML67
Green Hills, IAR OKI
Cosmic Cosmic, IAR, Metrowerks Green Hills DIABDATA Wind River DIABDATA Wind River, Green Hills, Metrowerks DIABDATA Wind River, Green Hills, Metrowerks Cosmic, Metrowerks
ML665S
Renesas Electronics (NEC/Renesas) 78kO H8 tiny H8S H8SX M16C M32C M32R IAR Renesas Renesas Renesas Renesas, IAR, Tasking GAIO, IAR, Renesas Renesas, GAIO Renesas, IAR IAR IAR, Renesas, GAIO, Green Hills Green Hills, IAR
Fujitsu Fujitsu Green Hills Fujitsu Green Hills
R32C R8C SH2 V850 STmicroelectronics SPC56xx
Keil, Tasking, TaskingVX GNU , Tasking Keil, Tasking, TaskingVX TaskingVX
DIABDATA Wind River, Green Hills, Metrowerks Keil, Tasking GNU
ST10 STR9 Texas Instruments MSP 430 TMS 320 TMS 470 TMS 570
IAR Texas Instruments Texas Instruments, Green Hills Texas Instruments
Green Hills
EMBEDDED SOFTWARE
Controller Toshiba TLCS-900 TX19, TX39, TX49 TX19A Vector CANoe osCAN Emulation
Compiler
Toshiba Green Hills Toshiba
Microsoft VisualC
Flash Memory Programming
Today, systems for downloading software to ECUs are used in all phases of ECU development. Vector offers a number of software solutions to meet various requirements: > Flash Bootloader for CAN, LIN, FlexRay, MOST and Ethernet > Flashing via CCP/XCP > Option for the Flash Bootloader: Security component > Option for the Flash Bootloader: Data compression > PC-based flash tool Flash Bootloader The Flash Bootloader lets you program ECUs with new software within an in-vehicle network. In particular, when the ECU is mounted at a hard to access location in the vehicle, the Flash Bootloader offers the advantage of updating ECU software without needing to remove the ECU. This results in the following capabilities: > Reprogramming during the development phase > End-of-line programming > Software updating in the Service area (After Sales) Reprogramming is performed via CAN, FlexRay, MOST or Ethernet utilizing a diagnostic protocol (UDS or KWP2000). A special LIN Flash Bootloader is available for LIN Slave ECUs. Programming via XCP/CCP The use of XCP or CCP is an alternative to reprogramming with the Flash Bootloader. This variant is primarily used to optimize ECU parameters. Since XCP/CCP programming is generally used in the 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 flexibility to set the security level required by the automotive OEM.
Data compression Automotive electronics is continuously becoming more complex, and so it requires more extensive software. Suitable data compression methods can be used to transport the increasing amounts of data more quickly on data buses; they reduce transmission times drastically. Vector offers optimized solutions for the Flash Bootloader and flash tools. Flash tools Different data and diagnostic formats are used by different automotive OEMs for programming ECUs. Meanwhile, ODX and ODX-F have become established at some automotive OEMs as a standard data format for ECU programming. To master the many different data and diagnostic exchange formats, Vector offers authoring and flash tools for specific use cases in its CANdelaFlash and CANditoFlash products. Flashing CANopen ECUs Vector also offers Flash Bootloaders for the special requirements involved in flashing CANopen ECUs. Vector can adapt them to your platform in the context of project work. EEPROM Emulation Module (EepM) The EEPROM Emulation Module (EepM) lets you efficiently store nonvolatile data of any desired length in program or data flash memory. The module is called directly by the application. To save on resources, the module can be used by either the application or the Flash Bootloader.
5/0
FLASHING
5/1
>> CONTENTS
Flash Bootloader Option Security (Crypto) Data Compression Option EEPROM Emulations Modul (EepM) Flashen with CCP and XCP CANdelaFlash vFlash 5/2 5/4 5/5 5/6 5/8 5/10 5/12
Flash Bootloader
ECU reprogramming via CAN, LIN, FlexRay, MOST and Ethernet
Overview of Advantages > Efficient and reliable reprogramming of ECUs; without having to remove the ECU > Low memory requirement in the ECU > Available for most OEMs and many microcontroller platforms > Security and data compression options available > Proven flash solution based on over 10-years of use in numerous development and production projects Application Areas The Vector Flash Bootloader is a universal and compact solution for quick, efficient and reliable reprogramming of ECUs during development, while in production or while in service. It is available for CAN, LIN, FlexRay, MOST and Ethernet bus systems, and conforms to specifications of automotive OEMs. The Flash Bootloader is continually coordinated with the OEMs. The Flash Bootloader consists of these components: > Bootloader including OEM Download Manager and communication stack > Flash driver (HIS device driver) Reprogramming is executed with a flash tool such as vFlash from Vector. Scripts needed for the Vector flash tools are supplied with the Flash Bootloader.
The Flash Bootloader permits reprogramming on single or multiprocessor platforms. It includes a Multiple Memory Manager for programming different memory types connected either internally or externally. Due to its low memory requirement, the Bootloader is also well suited for microcontroller platforms that have limited resources. Functions The flash download is executed according to OEM requirements using either the KWP2000 or UDS diagnostic protocol. The Bootloader contains the communication stack needed for the specific bus system. > The flash procedure with the OEM Download Manager In the ECU, the Bootloader is stored in a protected ECU memory area. After a reset, it is started as the first software instance in the boot phase. It then checks whether a flash request or valid application software exists. If the ECU is to be reprogrammed, the Bootloader starts reprogramming via the OEM Download Manager. After verifying access authorization, the OEM Download Manager loads the flash driver from the bus system to the ECUs RAM memory if needed. Then it erases the old ECU software and reprograms the flash memory with the new data it receives over the bus system. If the flash procedure is interrupted, it can be repeated at any time.
5/2
Flashing over CAN, LIN, FlexRay, MOST and Ethernet
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: embedded@de.vector.com Telephone: +49 711 80670-400
> Bus-specific communication stack The Bootloader communicates with the flash tool via the busspecific communication stack. For the CAN bus, a specially optimized CAN driver with Transport Protocol (ISO-15765) is used to economize on valuable resources; this also applies to LIN as well. AUTOSAR communication modules from Vector are used for FlexRay and Ethernet/DoIP. A Network Services Library for MOST is used to flash over MOST. > Flash driver The Flash Bootloader includes a flash driver that matches the hardware platform. It contains system-based routines for reliably erasing and programming nonvolatile memory chips. All Vector flash drivers have low memory requirements, and they conform to the HIS standard Functional Specification of a Flash Driver, Version 1.3. Options > Security: For ECUs with sensitive vehicle data that needs to be protected from unauthorized manipulation > Data compression: For quick re-programming of ECUs For detailed information on these options, please refer to the relevant datasheet on the following pages.
Configuration You configure the Bootloader with the GENy configuration tool, adapting it to the specific requirements of your application. Further modifications and extensions are possible using callback functions in the Bootloader Application Layer. Scope of Delivery > Bootloader as configurable C source code > Flash driver for your specific hardware platform > GENy configuration tool > Flash scripts for controlling the download process > Documentation Flash Tools To reprogram one or more ECUs, you can obtain the userfriendly vFlash tool from Vector. Its flexible approach lets it support various flash specifications for a wide variety of automotive OEMs without requiring modifications by the end user. For more information, please refer to the datasheet in the Diagnostics catalog. 5/3
Configuring flash blocks with GENy
Flash Bootloader: Option Security (Crypto)

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

Fast Flash Programming
Overview of Advantages > Reduced download times in flashing > Efficient decompression module for the ECU > Offers support in data compression > Bus system independent With the Vector Flash Bootloader you can program ECUs via a bus system without having to remove the ECU. Compression and subsequent decompression of the flash data is recommended to reduce download time. Application Areas Some automotive OEMs specify the use of data compression in their flash procedures to accelerate the flash procedure at a constant baudrate. Compression of the flash data saves time even for small quantities of data. Savings are maximized when flashing large quantities of data (e.g. in the Infotainment area). Compression also offers many benefits when short cycle times are specified, as in end-of-line programming. The data compression option of the Vector Flash Bootloader lets 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 Bootloaders decompression module is very efficient in terms of execution time and memory. It is available on all microcontrollers for which a Bootloader is available.
Functions The compression method used in this module enables a compression rate of 4060%, where the rate actually attained depends on the flash data itself. Compression is performed with the supplied tool HexView. If compressed flash data needs to be transmitted, the flash tool must communicate this via diagnostics to the Bootloader in the ECU, afterwards the flash tool transmits the compressed data. After receiving the flash data, the Bootloaders OEM Download Manager calls the decompression function, and then it programs the decompressed data in flash memory via the Multiple Memory Manager. Scope of Delivery > Configurable C source code; integrated in Bootloader > Tool HexView for compression of the flash data > Documentation 5/5
Compression and decompression of flash data
EEPROM Emulation Module (EepM)

EEPROM Emulation in Flash Memory
In recent years, flash memory has become more cost-effective and faster than conventional EEPROMs. New microcontrollers are often offered without EEPROM memory and just have a larger internal flash memory. Since writing to flash memory, unlike EEPROMs, is not by the byte but by the page, it is only possible to achieve optimized utilization of the flash memory with the help of an EEPROM emulation. Overview of Advantages > Usable for external and internal flash > Usable for data and program flash > Conserves resources and optimizes flash lifetime > Possible to use EEPROM emulation module together with the Vector Flash Bootloader
access the stored data by identifiers that are predefined or flexibly defined at runtime. Special Functions The EEPROM Emulation module is configurable and so it can be adapted to the requirements of the application. It enables: > Simultaneous emulation of multiple EEPROMs > Integration of different flash hardware
5/6
Application Areas Flash memory cannot be erased or written in the same way as conventional EEPROMs. EEPROM emulation in flash memory makes it possible for an application to store changed nonvolatile data in a flash memory, just as in a conventional EEPROM. Functions The Vector EEPROM Emulation Module (EepM) manages predefined flash areas by taking all hardware-specific constraints into consideration. Reading and writing of changeable nonvolatile data via the EepM is fully transparent to the application. It is easy to
Differences between EEPROMs and Flash Memory Flash memories cannot be written byte-by-byte. Their smallest writing unit, known as a page, extends over a number of bytes. A 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 sector lengths may also vary within a flash memory. Efficient Structuring of Nonvolatile Data Essentially, the use of a flash memory requires that the data to be stored is defined in so-called records. They are addressable by unique identifiers, and besides the stored data they also contain management information. This information assures quick and reliable read access to valid data. The application either defines the length of a record either statically during software configuration or dynamically at runtime, depending on the configuration.
Software architecture of the EepM
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 Internet at: http://www.vector.com/vi_eepm_availability_en or upon request E-mail: embedded@vector-informatik.com Telephone: +49 711 80670 400.
Reliable Access In addition to the nonvolatile data, control information is stored in a record and includes a Cyclic Redundancy Checksum (CRC). This information assures that the data remains consistent with each access. If the application calls up nonexistent data, the EepM generates an error message. Optimizing Resources and Lifespan During configuration the reserved flash area is partitioned into two blocks. The EepM sequentially writes new or updated records into the currently active block. When this block is full, the EepM completely erases the inactive block fully before it copies the still valid records of the active block into it. After an integrity check, the inactive block becomes the active block. This alternating and 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 Bootloader is integrated into the ECU, the context pointers make it possible to use the EEPROM Emulation module from the Flash 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.
Configuration The EepM is configured via a header file. Scope of Delivery > C header files and source code > Makefiles and sample programs > Documentation/operating instructions/Readme file Optional Services > Consultation in system design and integration in the ECU > We supply HIS flash drivers > We will extend standard modules according to your needs > Hotline, special workshops and training courses on the topic of embedded software
5/7
Resource optimization by use of EepM from the Vector Flash Bootloader
Flashing with CCP and XCP

Using the CCP/XCP protocol for flash programming
Advantages > Calibration and reprogramming with the same software component > Use CANape as a flash tool > Reset-safe solutions are available The CAN Calibration Protocol (CCP) and its successor, the Universal Measurement and Calibration Protocol (XCP) are ASAM Standards that are used to measure and calibrate internal ECU parameters. XCP offers several different physical interfaces such as CAN, FlexRay, Ethernet, USB and SPI/SCI. The calibration tool CANape from Vector supports all of these interfaces. Application areas Flashing via CCP and XCP is primarily used to update calibration 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 ECUs 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 containing 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.
Less widely used but technically feasible is the option of replacing the entire application by flashing via CCP and XCP. Failsafe reprogramming Unfortunately, the use of a flash kernel has one disadvantage: If the data transfer is interrupted during programming, this might lead to a catastrophic failure of the ECU. This can be remedied by using a CCP or XCP bootloader (see illustration, right). It is permanently stored in a protected memory area. The bootloader is always called after the start, and it checks the application. The application is not started unless it is valid and complete. A flash abort always causes the bootloader to assume control, and the flash process can be resumed at any time. Tool support The flash download is executed by CANape.
5/8
Flashing via XCP using a flash kernel
Flashing via an XCP bootloader
FLASHING
5/9
EMBEDDED SOFTWARE
Wide Availability of Flash Bootloader and EepM

Controller AnalogDevices BlackFin Atmel AVR AVR32 Freescale DSP56F83xx HC08, MCS08 HC12, Star12, Star12x, MCS12xE i.MX25 MAC71xx, MAC72xx MPC 55x, 56x, 5200 MPC 55xx, 56xx Fujitsu 16FX 16LX FR60 Jade Infineon C16x (external AMD-Flash) Tricore XC16x XC2000 Microchip dsPIC24 dsPIC33 PIC18 National CR16
V2.1 2010-10
Compiler
Available for [1]
Controller
Compiler
Available for [1]
Renesas Electronics (NEC/Renesas) VisualDSP CAN 78k0 78K0R IAR IAR CAN, LIN CAN H8S M16C M32C Metrowerks Cosmic, Metrowerks (Hiware) Cosmic, IAR, Metrowerks (Hiware) GNU ARM, IAR DIABDATA Wind River, Metrowerks DIABDATA Wind River CAN CAN, LIN CAN CAN CAN CAN CAN, FlexRay M32R R32C R8C SH2 V85x STmicroelectronics ST9 ST10 STM8a Fujitsu Fujitsu Fujitsu GNU CAN CAN CAN CAN Texas Instruments TI OMAP 59xx TMS320 TMS470 TMS570 Tasking GNU, Tasking Keil, Tasking Tasking CAN CAN, FlexRay CAN CAN Toshiba TLCS900 TX19 TX49 Toshiba Green Hills Green Hills CAN CAN CAN Texas Instruments Texas Instruments Texas Instruments, ARM Texas Instruments, ARM CAN CAN CAN CAN, FlexRay GNU Tasking Cosmic CAN CAN CAN IAR IAR Renesas Renesas, IAR Renesas, IAR Renesas IAR Renesas, IAR Renesas Renesas (NEC), Green Hills, IAR CAN, LIN CAN CAN CAN CAN CAN CAN CAN CAN CAN, LIN, FlexRay
Microchip C30 Microchip C30 Microchip, Hi-Tech
CAN CAN CAN, LIN
[1] Please contact Vector (embedded@vector.com) if your controller is not on the list or if you need additional support for a not listed bus system. In general CAN, LIN, FlexRay, Ethernet and MOST can be supported. The Flash Bootloader is available for a great variety of OEM-specific flash processes. Please find the list of supported OEMs in the separate datasheet.
IAR
CAN
EMBEDDED SOFTWARE
CANdelaFlash 2.0
Management of Flash Data and Generation of ODX Flash Containers for an Assured Process
Properties Overview > Import and Export of ODX Flash Containers > Modularization of flash data > Management of software revision levels and part numbers > Administration of data for Flash ROMs > Reuse of diagnostic descriptions from CANdelaStudio > Can be used by both vehicle manufacturers and suppliers > Comfortable user interface Application Areas Today the development process for an ECU is very complex. While previously just a few ECUs were flashable in the vehicle, in future all ECUs will have a flash capability. The large number of ECUs that are networked together in the vehicle, and their growing complexity and amount of programmable data will require management of the flash data for an assured process. In the future the flashing of ECU sub-functionalities will also come to the forefront. CANdelaFlash is a software tool designed to manage these requirements. CANdelaFlash should be used wherever process-assured flashing of ECU functionalities (full or partial) is required. It can be implemented in both ECU development at a supplier and in test vehicle or preproduction development at the vehicle OEM.
Functions CANdelaFlash supports the import and export to the standardized ODX format completely. ODX Flash Containers can thereby be prepared at an early stage in the development process. These ODX Flash Containers have become a standard for modern flash tools used in development and production. CANdelaFlash fits seamlessly into existing tool chains. In particular it supports the development process with other Vector products such as CANdelaStudio. Another advantage of CANdelaFlash is that it supports modularization of flash data, e.g. post-flashing of individual ECU functionalities (gear shift programs, idle-speed control, country variants, etc.). CANdelaFlash offers a simple and easy-to-use interface. For example, the organization of a CANdelaFlash document is shown in a tree view, and most entries are made via easy-to-use tables with intuitive input masks. Functions at a Glance: > Assignment of software revision levels and part numbers > Assignment of the various software revision levels to specific ECUs in the vehicle > Identification of valid target ECUs. Checking whether the session is valid for the ECU that has to be programmed. > User-friendly acquisition and management of binary and hexadecimal data for Flash ROMs (e.g. import of source files in Intel Hex and Motorola S-Record formats)
5/10
New Functions of Version 2.0 Data Extraction Plugin Interface > Interface for automatic extraction of data out of hex files at import time or interactively using the menu via OEM specific plug-in Base Session > Optional definition of session defaults for a project Session Wizard > Simple creation of flash sessions through configurable Session Wizard > Mask out unused or read only elements in the user interface
Process-assured generation of ODX Flash Container
FLASHING
> Use of templates for new CANdelaFlash documents > Creation and editing of sessions and data blocks > User-friendly editing of the segments of a data block including extensive consistency checks > Grouping of sessions into so-called Flash Classes > Cut, copy, and paste functions for objects of the CANdelaFlash document > Searching of the CANdelaFlash database for objects by their names > Import and Export of the CANdelaFlash document into ODX 2.0 and ODX 2.1 data format > Import/export of embedded flash data from/to ODX > Creation and editing by authors, revision entries, and brief descriptions > Interfacing to external tools by user-defined actions > Plug-In interface for linking customer-specific security DLLs for CRC and signature calculation > Support of customized user settings > Reuse of diagnostic data (from CANdelaStudio) > Detailed recording of program sequences (Output Window) > Read and write of PDX archives (Packaged ODX) > Expanded format checking in attribute masks via specification of regular expressions in the template
Structure of the CANdelaFlash Data The management and the acquisition of flash data are done comfortably via the user interface in the following structure: > Flash description: Reference to multiple ECUs (CANdelaStudio ECU-specific descriptions; *.cdd files) > Base Session: Optional definition of session defaults for a project > Sessions: Session with list of data blocks. This is a list of jobs for upload/ download (initial programming, reprogramming, partial reprogramming). The data blocks reference the flash data (reusable in different sessions) and they specify the segments of flash data for upload/download. > Memory layouts: Description of the memory layouts of several ECUs > Flash classes: User-defined organization of sessions in any desired number of flash classes > Flash data: Database of reusable flash data
5/11
Flash data management with CANdela Flash: Structure of the CANdelaFlash data
vFlash 1.1
(Re-)Programming easily and quickly over CAN or Ethernet (DoIP)
Overview of Advantages > Extremely easy to reprogram ECUs over CAN or Ethernet (DoIP) > Preconfigured flash projects can be exchanged readily all relevant data is packed in one file > Flash projects are easy to create using templates > Supports different protocols and flash sequences (based on the specifications of many different automotive OEMs) > Direct native programming of data in Intel hex, Motorola-S and binary format > Flash programming based on ODX-F > Flashing of compressed data > Supports interactive flashing (GUI) as well as batch processing (C API) > Interacts perfectly with Vector Flash Bootloader vFlash is a very easy-to-use tool for programming one or more ECUs. Because of its flexible approach, it can support the different flash specifications of a wide variety of automotive OEMs without requiring modifications by the end user. Application Areas vFlash is designed for all users at automotive OEMs and suppliers whose tasks include (re-)programming of ECUs. It supports ECU programming over CAN and over Ethernet (DoIP), either individually or in an ECU network group. vFlash lets users flash in the
laboratory, at programming stations, at a laboratory vehicle or in the vehicle. vFlash is very simple and does not require any expert knowledge to use the user interface is tailored for flashing tasks. vFlash may be used either interactively or by remote control. In the interactive mode, the user loads a project and starts programming by the push of a button. In remote control mode, vFlash can be executed from the command line or controlled via a C programming interface. vFlash is designed to process very large quantities of data. You can transmit 4 GB or more or segments of very large binary data sets quite easily. Last but not least, the vFlash tools very fast transmission rate significantly reduces flash times in the case of large amounts of data. Functions vFlash utilizes flash projects to save and exchange the configuration to program individual ECUs. Flash projects contain all relevant settings and reference the data files to be programmed. If the focus is on flexibility in changing the flash data, the referenced data files can simply be exchanged in background, e.g. as part of an automated software build process. In this case, the flash project remains unchanged. If the focus is on a process-safe exchanging of flash configurations, the flash projects may be exchanged in the Pack&Go format. In this case, all relevant settings together with the data files are packed in an archive file.
5/12
Flash process with vFlash
FLASHING
The user creates flash projects based on flash templates. A flash template defines the diagnostic services and presettings that are relevant to the flash process for a group of ECUs of a specific automotive OEM (e.g. for a vehicle platform). In practice, the flash specifications of automotive OEMs differ enormously, not least of all due to the differences in diagnostic protocols and in-house flash standards. The advantage of flash templates concept is that the differences described above remain largely hidden from the user. The reference flash process from Vector is also available as source code (C#). This lets end users modify the flash sequence themselves 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
OEM-specific flash templates Vector offers prepared flash templates for a number of different automotive OEMs. Please contact us at: www.vector.com/contact System Requirements
Windows XP (32-bit) Processor RAM PC with min. 1.6 GHz 1 GB Windows Vista (32 bit) Windows 7 (32/64 bit) PC with min. 1.6 GHz 2 GB
5/13 Supported Hardware > XL interface product family (e.g. CANcardXL, CANcardXLe, CANcaseXL)
vFlash User Interface
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.
6/0
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: academy@de.vector.com Vector Consulting Services: info@vector-consulting.de Vector CANtech: academy@us.vector.com Vector Scandinavia: academy@se.vector.com Vector France: academy@fr.vector.com Vector Japan: academy@jp.vector.com Vector Great Britain: academy@uk.vector.com Vector Korea: academy@kr.vector.com 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.
TRAINING
6/1
Germany
6/8
DIRECTIONS TO VECTOR
USA and Great Britain

Subsidiaries: Vector CANtech Inc., Vector GB Limited
6/9
France and Sweden

Subsidiaries: Vector France S.A.S., VecScan AB
6/10
Japan and Korea

Subsidiaries: Vector Japan Co., Ltd., Vector Korea IT Inc.
6/11
India and China

Subsidiaries: Vector Informatik India Pvt. Ltd., Vector Informatik China
6/12
6/13
Your contact
Germany and all countries not named below Vector Informatik GmbH Vector Consulting Services GmbH Ingersheimer Str. 24 70499 Stuttgart GERMANY Tel.: +49 711 80670-0 Fax: +49 711 80670-111 France, Belgium, Luxembourg Vector France 168, Boulevard Camlinat 92240 Malakoff FRANCE Tel.: +33 1 4231 4000 Fax: +33 1 4231 4009 USA, Canada, Mexico Vector CANtech, Inc. Suite 550 39500 orchard Hill Place Novi, MI 48375 USA Tel.: +1 248 449 9290 Fax: +1 248 449 9704
Japan Vector Japan Co., Ltd. Seafort Square Center Bld. 18F 2-3-12 Higashi-shinagawa, Shinagawa-ku Tokyo 140-0002 JAPAN Tel.: +81 3 5769 7800 Fax: +81 3 5769 6975 Korea Vector Korea IT Inc. 1406 Mario Tower 222-12 Guro-dong, Guro-gu Seoul 152-848 REPUBLIC oF KoREA Tel.: +82 2 8070 600 Fax: +82 2 8070 601 India Vector Informatik India Prv. Ltd. 4/1/1/1, 3rd floor, Sutar Icon Sus Road Pashan Pune 411021 INDIA Tel.: +91 20 2587 2023 Fax: +91 20 2587 2025
Sweden, Denmark, Norway, Finland, Iceland VecScan AB Theres Svenssons Gata 9 41755 Gteborg SWEDEN Tel.: +46 31 764 7600 Fax: +46 31 764 7619 United Kingdom & Ireland Vector GB Limited Rhodium, Central Boulevard Blythe Valley Park Solihull, Birmingham West Midlands, B90 8AS UNITED KINGDoM Tel.: +44 121 50681-50 Fax: +44 121 50681-69 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

Catalog ECU Software en

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Catalog ECU Software en

Uploaded by

Copyright:

Available Formats

Product Catalog

ECU Sof tware

Vector the Company

Milestones / Key Data

2005 2006 2007

VECTOR XXXXXXXXXXXX THE COMPANY

Automotive engineering (body electronics bus e.g. networking within a seat)

3/8 3/12 5/2

Application Area Automotive ECUs, basic software

Page 2/2 2/54 2/6 2/44 2/28

ARINC 8xx CANaerospace

Avionics and space technology

Commercial vehicles engineering

Automation engineering, CAN embedded

3/28 3/20 3/24

Vehicle ECUs, Diagnostics, PassThru re-programming

CANoe.IP CANalyzer.IP MICROSAR IP

Diagnostics of vehicle electronic control units

Commercial vehicles engineering, engine control

Application Areas of the Vector Products

APPLICATION AREAS OF THE VECTOR PRODUCTS

Development of Distributed Systems

SteuergerteECU Calibration Kalibrierung

SteuergerteECU Software SoftwareComponents Komponenten

ProzessProcess management Management ++

2/46 2/50 2/52 2/44

Use of Standardized Basic Software for ECUs

Revision level: January 2011

Technical Consulting/Engineering Services

Services for the development of ECU software

Services for Vehicle Networks

Software Engineering Services

Solutions for AUTOSAR

AUTOSAR Evaluation Bundle

AUTOSAR Basic Software

More Information: www.vector.com/contact

Designing software components with DaVinci Developer

Configuration of the Basic Software with DaVinci Configurator

More Information: www.vector.com/contact

More Information: www.vector.com/contact

The MICROSAR packages contain all modules of the AUTOSAR standard

More Information: www.vector.com/contact

More Information: www.vector.com/contact

You use DaVinci Configurator Pro to configure the BSW modules

More Information: www.vector.com/contact

> MICROSAR CAL

More Information: www.vector.com/contact

More Information: www.vector.com/contact

MICROSAR COM Modules

Configuring the COM module with GENy

MICROSAR CAN modules

More Information: www.vector.com/contact

MICROSAR LIN modules

MICROSAR MOST modules

MICROSAR MEM modules

Configuration Dialog for the Non volatile RAM Manager

MICROSAR SYS modules

More Information: www.vector.com/contact

Configuring the SYS module with DaVinci Configurator Pro

MICROSAR DIAG modules

More Information: www.vector.com/contact

> > > >

More Information: www.vector.com/contact