Catalog ECU Software en

Product Catalog

ECU Sof tware

ENGL

ISH

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

Date: March 2011 · Responsible for the contents: Vector Informatik GmbH, Stuttgart, Germany

All mentioned product names are either registered or unregistered trademarks of their respective owners. The constant worldwide availability of all products or services is not warranted.

No information contained in this catalog may be reproduced without expressed permission, in writing, from Vector Informatik GmbH.

Errors and omissions excepted.

Illustration & Design: SATZTEAM Fotosatz & Neue Medien GmbH, Eberdingen, Germany

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

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

1/0

Vector – the Company

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 QualityFor 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

High Customer SatisfactionThe delivery quality and delivery time as well as consulting compe-

tence 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 Atmosphere70 % 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 WorldwideFor 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.

Milestones / Key Data1988 Founding of Vector Informatik GmbH

1992 Sale of the first CANalyzer license

1994 Vector has more than 25 employees

1996 Sale of the first CANoe and CANape license

1997 Founding of Vector CANtech, Detroit/USA

1998 Founding of Vector Japan, Tokyo/Japan,Vector Informatik is DIN EN ISO 9001:1994 certified

1999 Vector has more than 100 employees worldwide

2001 Move to the new company building in Stuttgart,Founding of Vector Consulting

2002 Vector Informatik is DIN EN ISO 9001:2000 certified,Founding of Vector France, Paris/France,Founding of VecScan, Göteborg/Sweden,Vector has more than 250 employees worldwide


2004 Move to the second company building in Stuttgart,Founding of customer care center north in Braunschweigand customer care center south in Munich/Germany


2006 Founding of office in Regensburg/GermanyVector has more than 600 employees worldwide

2007 Vector has more than 700 employees worldwideStart of construction for the third company building in Stuttgart/GermanyFounding of Vector Korea, Seoul/Rep. of Korea

2008 Vector has more than 800 employees worldwideMove to the third company building in Stuttgart

2009 Founding of Vector Great Britain, BirminghamFounding of Vector Informatik India, PuneOpening of Representative Office Shanghai, China

2010 aquintos becomes part of the Vector Group

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

1/1

XXXXXXXXXXXXVECTOR – THE COMPANY

1/1

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

Process ManagementTools 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 func-

tionalities 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 ECU‘s

lifecycle.

Development of Distributed SystemsTools and Services to design and develop a network of ECUs.

Tools to simulate, analyze and test the communication of the net-

work.

ECU TestingTools and services that allow the test of ECUs in all develop-

ment phases, check the functionality of prototypes or execute

regression and conformity tests.

ECU CalibrationTools 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.

Please request other catalogs in the application areas Development of Distributed Systems, ECU Testing, ECU Calibration, Process Management, Vehicle Diagnostics, or request further information about the Vector Solutions for various tasks in automotive

networking: Internet: www.vector.com/catalog/ • E-mail: [email protected]

ECUs. Basic software for AUTOSAR. Development services for soft-

ware components.

ECU SoftwareEmbedded software like real time operating systems (RTOS)

and communication modules for e.g. CAN, LIN, FlexRay and Ether-

net. Software for memory management and for reprogramming of

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

1/2

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

Bus System Description Application Area Appropriate Vector Product Page

CAN (Controller Area Network) was developed by the Robert Bosch GmbH in the early eighties and was interna-tionally standardized (ISO 11898) in 1994. CAN was specif-ically developed for the serial data exchange betweenelectronic control units in automobiles but is also used forthe realization of industrial microcontroller networks.

LIN (Local Interconnect Network) has been developed especially for the cost-efficient communication ofintelligent 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)

MOST (Media Oriented Systems Transport) has been devel-oped especially for the transmission of multimedia data inautomobiles.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 security-relevant applications as well as for transmission of largeamount of data in automobiles. FlexRay bus system characteristics:> data transmission up to 10 Mbit/s> redundant implementation of all networks> deterministic transmission behaviorAs an exchange format for tools for the configuration ofbus communication (design, parameterization) with FlexRay, the XML based FIBEX format (Field bus Exchange)is predominantly used.

Automotive engineer-ing, automation engineering

Automotive engineer-ing (body electronicsbus e.g. networkingwithin a seat)

Automotive engineer-ing (multimedia applications; net-working of infotain-ment devices e.g.tuner, DVD changer,etc.)

Automotive engineer-ing (e.g. security-relevant applications,brake-by-wire, high-speed backbone forother bus systems)

All Vector Products

CANalyzer.LIN/CANoe.LINCANalyzer/CANoe Option SCOPECANapeCANbedded LIN CommunicationEmbedded GatewayFlash BootloaderCANisterCANlog 3/4GL1000, GL3000/4000/4200MICROSAR LINMultilogNetwork Designer LINVN8900XL-Interface-Family

CANalyzer.MOSTCANoe.MOSTFlash BootloaderMICROSAR MOSTMultilogVN2610 – USB-Interface for MOST

CANalyzer.FlexRay CANapeCANoe.FlexRay Flash Bootloader FlexCard Cyclone II SE/E-RayFRstressMICROSAR FRMultilogNetwork Designer FlexRay VN3300, VN3600 and VN7600

FlexRay-Interfaces

●●●

3/83/125/2●●●

2/18●●●●

●●

5/22/22●●

●●●

5/2●●

2/16●●

●

CAN

LIN

MOST

FlexRay

The goal of the development partnership, founded by leading automotive OEMs and suppliers, is the definition ofan open reference architecture for ECU-specific software.

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 communicationwithin CAN-based subsystems and between CAN subsystems,which for example are interconnected by AFDX. ARINC 826specifies Software Data Load over CAN. Key protocol applications of CANaerospace are in engineering simulators,simulation cockpits and especially on drones (UAVs).

Automotive ECUs, basic software

Avionics and space technology

AUTOSAR Evaluation BundleAUTOSAR ServicesAUTOSAR Basic Software ModulesAUTOSAR ToolsMICROSAR DIAG

CANalyzer.CANaeroCANoe.CANaero

AUTOSAR

ARINC 8xxCANaerospace

Protocol resp. Description Application Area Appropriate Vector Product PageExchange Format

2/22/542/62/442/28

●●


1/3

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

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

J1939 is a communication protocol based on CAN for real-time data exchange between electronic control units(ECUs) in the area of commercial vehicles. It describes the information exchanged between the ECUsin such a system. ISO11783 is a further development foragricultural engineering.

NMEA 2000® is a communication protocol based on J1939from the National Marine Electronics Association (NMEA)for the realtime data exchange between electronic controlunits in maritime electronics.

SAE J1708 defines a serial, bidirectional network for use inthe commercial vehicle industry. The SAE J1587 Standardregulates communication and standardized data exchangebetween different ECU based on SAE J1708 networks.

The CANopen profile family specifies standardized commu-nication mechanisms and device functionalities.CANopen is maintained by “CAN in Automation” (CiA), andcan be implemented free of license.

The SAE J2534 standard defines the re-programming ofECUs via a PassThru interface. The purpose of this standardis to provide a unified communication capability via astandardized PC interface basically intended for flashingbut also for diagnostics and other purposes.

Ethernet-based networks and the protocols built uponthem are used in IT networks for decades. In the meantimethey continue to grow in importance in the embeddedenvironment. The main focus is on transmission of periodicsignals and real-time capability.

XCP is an improved and generalized version of the CAN Cali-bration Protocol V2.1. (CCP). XCP can be used also in non-CAN networks (e.g. FlexRay, SPI, SCI). The main benefit ofXCP is the independence concerning the transport layer.

Keyword Protocol 2000 (KWP2000; ISO 14230) and “UnifiedDiagnostic Services” (UDS; ISO 14229) are standardized diagnostic protocols for electronic control units. The physical access to the ECU is possible via a serial con-nection (“K-line” KWP-on-K-Line) or via CAN (KWP-on-CAN,UDS-on-CAN).

The ODX format (Open Diagnostic Data Exchange) is basedon the ASAM-MCD-2D-Basic working draft. Manufacturersof vehicles, electronic control units, and testers can writeand exchange electronic control unit data in the uniformODX format, which covers all manufacturers.

The RP1210 specification defines an open interface (API)between Windows-based applications and in-vehicle com-munication networks. This interface offers functionalityfor bus systems – such as CAN and J1708 – as well as for higher layer protocols such as J1939 and J1587.

Commercial vehicle engineering, railway engineering, agricultural engineering

Marine engineering

Commercial vehicles engineering

Automation engineering,CAN embedded

Vehicle ECUs, Diagnostics, PassThrure-programming

Car2x, vehicles engi-neering, automationengineering, factoryautomation

Automotive engineer-ing, development ofelectronic controlunits, measurementand calibration

Diagnostics of vehicleelectronic controlunits, measurementand calibration

Diagnostics of vehicleelectronic controlunits

Commercial vehiclesengineering, enginecontrol

CANoe.J1939CANalyzer.J1939CANoe.ISO11783CANbedded J1939CANape

CANoe.J1939CANalyzer.J1939CANbedded J1939

CANoe/CANalyzer.J1587

CANoe.CANopenCANalyzer.CANopenCANerator CANopenProCANopenCANedsCANopen Master Source CodeCANopen Slave Source Code

PassThru XL Library

CANoe.IPCANalyzer.IPMICROSAR IP

CANapeXCP software componentCANoe Option XCPGL1000, GL3000/4000/4200

CANapeCANdelaStudioCANdescCANoeCANoe.DiVavFlashIndigo

CANdelaStudioCANdelaFlashODX StudioCANapeCANoeCANoe.DiVavFlashIndigo

RP1210 API

●●●

3/6●

●●

3/6

●

●●

3/28●●

3/203/24

●

●●

2/20

●3/30●●

●●

3/14●●

5/12●

●5/10●●●●

5/12●

●

◆

J1939/ISO11783

NMEA 2000

J1587/J1708

CANopen

J2534

Ethernet/IP

XCP/CCP

KWP2000/UDS

ODX

RP1210

Protocol resp. Description Application Area Appropriate Vector Product PageExchange Format


1/4

Application Areas of the Vector Products

The following matrix gives you an overview which Vector products support you in your specific application area.

++ = main application area; + = additional application area

ASAP2 Editor ++ ●

ASAP2 Lib ++ ●

ASAP2 Tool-Set ++ ●

AUTOSAR Basic Software ++ 2/2(MICROSAR)

CANalyzer ++ ●

CANape + + ++ ●

Option Adv.+ ++ ●Multimedia

Option GPS + ++ ●

Option Simulink + ++ ●XCP Server

CANbedded ++ 3/2

CANbedded Gateway ++ 3/12

CANbedded J1939 ++ 3/6

CANbedded LIN ++ 3/8

CANdb++ Admin.J1939 ++ ●

CANdbLib ++ ●

CANdelaStudio ++ ●

CANdelaFlash ++ 5/10

CANdesc ++ + 3/14

CANdito + ++ ●

CANeds ++ ●

CANerator CANopen ++ 3/28

CANextender ++ ●

CANgraph + ++ ●

CANister ++ ●

CANlog 3 and 4 ++ ●

CANoe + ++ + ●

CANoe.DiVa + ++ ●

CANopen Master Source Code ++ 3/20

CANopen Slave Source Code ++ 3/24

CANscope ++ ●

CANstressD/DR ++ ●

Vector ProductDevelopment of Distributed

SystemsECU Testing Diagnostics ECU Calibration ECU Software

ComponentsProcess

Management Page


APPLICATION AREAS OF THE VECTOR PRODUCTS

1/5

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

Steuergeräte-Kalibrierung

Steuergeräte-Software-

Komponenten

Prozess-management Seite

COMPASS ++ ●

DaVinci

Component Tester ++ 2/46

Configurator Pro ++ 2/50

Configurator Kit ++ 2/52

Developer ++ 2/44

eASEE.cdm + ++ ●

eASEE.rqm ++ ●

eASEE.pm ++ ●

eASEE.chm ++ ●

eASEE.sdm ++ ●

EEPROM Emulations Modul ++ 5/6

Flash Bootloader + ++ 5/2

FlexCard Cyclone II ++ ●

FRstress ++ ●

GL1000, GL3000/4000/4200 ++ ●

High Resolution Timer ++ 4/4

Indigo + ++ ●

Multilog ++ ●

Network Designer ++ ●CAN/LIN/FlexRay

ODX Studio ++ ●

osCAN ++ 4/2

PassThru XL Library ++ ●

ProCANopen ++ ●

RP1210 API + ++ ●

Test AutomationEditor ++ ●

Timing Analyzer + ++ 4/6

vFlash ++ 5/12

VN2610 USB Inter- ++ ●face for MOST

VN3300, VN3600,VN7600 Interfaces ++ ●for FlexRay

VN8900 ++ ●

VT System ++ ●

VX1000 ++ ●

XL-Interface- Family(e.g. CANcardXL, ++ + ●

CANcaseXL, …)

Vector ProductDevelopment of Distributed

SystemsECU Testing Diagnostics ECU Calibration ECU Software

ComponentsProcess

Management Page


1/6

Use of Standardized Basic Software for ECUsSupported Hardware Platforms and Vehicle Manufacturer (OEMs)

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 hard-

ware and compiler combination. If necessary, Vector can also

integrate drivers, e.g. drivers supplied by semi-conductor manu-

facturers.

Application AreasYou 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.

HardwareFor the latest list of supported hardware platforms for automotive

software please visit our e-catalog: www.vector.com/ecat_esThe list for CANopen can be found on the product pages for the

Master and Slave source code: www.canopen-solutions.com

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 stand-

ardized API

> Customization of basic software for your use case

> Simple, tool-supported configuration


1/7

ECU SOFTWARE

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

(1) Revision level: January 2011

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 vari-

ant of the basic software is available for non-OEM-specific com-

munication. ◆

Training

In the framework of our training program, we can offer you

OEM-specific training courses and workshops for our soft-

ware 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


1/8

Technical Consulting/Engineering ServicesIndividual support in the development of ECU software and vehicle networks

For over 15 years, Vector has been creating software components

as well as professional tools, and has been successfully support-

ing customers worldwide in developing ECU software and net-

working 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 coordi-

nation with your project team and based on a process that is opti-

mally 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 SoftwareIn 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 sup-

port 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 work-

shops, 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 con-

tent according to ISO DIS 26262. Model-based software develop-

ment can also be provided.

Overview of Advantages

> Tailored support

> Quick implementation of your application

> Sustained build-up of know-how

Services for the development of ECU software


1/9

ECU SOFTWARE

Our services line-up ranges from a standard “Extended Integra-

tion 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 NetworksIn the development of vehicle networks, you can obtain the fol-

lowing support from Vector:

> Technical Consulting

Technical consulting focuses on sustainable transfer of the neces-

sary technological information. Close cooperation with our ex-

perts 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 ◆

Services for Vehicle Networks

Contact

We would be glad to support you on your projects. Please feel

free to contact us at: www.vector.com/contact


1/10

Software Engineering ServicesProfessional Support for your ECU software

For over 15 years, Vector has been developing software compo-

nents 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


> 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


1/11

ECU SOFTWARE

System Functions and Software IntegrationPerhaps you want to focus more on your application development

and are seeking a partner to assume responsibility for implement-

ing 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 pro-

ject team and is based on a process that is optimally aligned to

your needs: from prototype to serial production. If you need safe-

ty-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 SoftwarePerhaps you do not wish to develop your application software

yourself and are seeking a partner that can handle its implemen-

tation for you? We would be glad to assume responsibility for exe-

cuting an entire ECU software project. ◆

Vector can develop individual system functions or the entire application software

Contact

We would be glad to support you in your projects. Please find

your personal contact at:

www.vector.com/contact


2/0

Solutions for AUTOSAR

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 ProjectsAs one of the first premium members of the AUTOSAR Consortium,

Vector has been actively involved in the development of new tech-

nology for a long time. This active participation was recognized by

the AUTOSAR Consortium in awarding Vector the first AUTOSAR

Premium Member Award in 2007. Vector‘s experience with

AUTOSAR is also reflected in AUTOSAR tools and the basic soft-

ware, which is already being used in numerous production pro-

jects.

Overview of the Vector AUTOSAR SolutionVector 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 defini-

tion 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 config-

uration 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 VectorWith 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 anticipa-

tion of AUTOSAR Release 4.0 complete this solution, e.g. with sup-

port 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.

Vector Katalog ECU Software EN 09.02.2011 13:40 Uhr Seite 2/A

2/1

AUTOSAR

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 commu-

nication in the networks can also be defined with eASEE.

> Network Designer is used to design a vehicle’s networking

architecture and data communication for the networks.

> CANdela Studio let’s 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 pro-

ducts, Vector also offers on-site support in project implementa-

tion 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 struc-

tured approach for training in the AUTOSAR methodology and

gives you an opportunity to evaluate the functionality and per-

formance of the AUTOSAR software.

Support for Your ProjectsVector accompanies you from the early evaluation phase to pro-

duction projects. Together with you, we can develop a comprehen-

sive solution for your ECU. In the process, it does not matter

whether you are using Vector products, your own in-house devel-

opments or third-party components. We support your projects

with experience and integration know-how.

>> CONTENTS

AUTOSAR Evaluation Bundle 2/2MICROSAR 2/6MICROSAR OS 2/10MICROSAR COM 2/12MICROSAR CAN 2/14MICROSAR FR 2/16MICROSAR LIN 2/18MICROSAR IP 2/20MICROSAR MOST 2/22MICROSAR MEM 2/24MICROSAR SYS 2/26MICROSAR DIAG 2/28MICROSAR CAL 2/32MICROSAR EXT 2/34

MICROSAR IO 2/36MICROSAR RTE 2/38MICROSAR Safe 2/40Identity Manager for AUTOSAR 2/42DaVinci Developer 2/44DaVinci Component Tester 2/46DaVinci Configurator Pro 2/50DaVinci Configurator Kit 2/52AUTOSAR Services 2/54

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 soft-

ware 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.


EMBEDDED SOFTWARE

More Information: www.vector.com/contact

V2.4

201

1-05


> 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 require-

ments 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 sup-

pliers 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 founda-

tion 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. Nonethe-

less, 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 Environ-

ment (RTE) and basic software (BSW). The DaVinci tools are tai-

lored 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 Basic Software

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

AUTOSAR Tools

Additional Tools

EMBEDDED SOFTWARE


(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 edi-

tor, 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 per-

form 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 communica-

tion 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


> Diagnostic Event Manager (DEM)

> Diagnostic Communication Manager (DCM)

> Function Inhibition Manager (FIM)

MICROSAR MEM


> NVRAM Manager (NVM)

Training

In the framework of our training program, we can offer various

training events and workshops for MICROSAR in our classrooms as


For more information on individual training events and dates on the

Internet please visit: www.vector-academy.com

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


> 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)


> FlexRay Interface (FRIF)

> FlexRay Transport Protocol (FRTP)

> FlexRay Network Management (FRNM)

> FlexRay State Manager (FRSM)

MICROSAR LIN (available as option)


> LIN Interface (LINIF)

> LIN Transport Protocol (LINTP, contained in LINIF)

> LIN State Manager (LINSM)

MICROSAR COM


> Communication (COM)

> Network Management Interface (NM)

> PDU Router (PDUR)

> I-PDU Multiplexer (IPDUM) available as option

MICROSAR IO


> IO Hardware Abstraction (IOHW)

MICROSAR CAL


> 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


> PORT Driver (PORTDRV)

> Digital IO Driver (DIODRV)

MICROSAR EXT


> CAN Transceiver Driver (CANTRCV)

> FlexRay Transceiver Driver (FRTRCV)

> LIN Transceiver Driver (LINTRCV)

MICROSAR Safe (optional)

Complete solution for safety relevant functional software accord-

ing 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 coach-

ing at your business site.

Available Hardware Platforms The AUTOSAR Evaluation Bundle is available for the most com-

monly 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, emula-

tions 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.

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

Functional principle: CANoe as target platform

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

EMBEDDED SOFTWARE


V2.3

201

1-06


> 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 func-

tionality 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 core-

processors. 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 project�s requirements, and after generation you can inte-

grate 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

MICROSAR The Vector Solution for AUTOSAR ECU Software

The MICROSAR packages contain all modules of the AUTOSAR standard

EMBEDDED SOFTWARE


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 Vector�s 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 simulta-

neous 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

Training


training events and workshops for MICROSAR in our classrooms as


For more information on individual training events and dates on the

Internet please visit: www.vector-academy.com

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 soft-

ware 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 configu-

ration 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 con-

figuration 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 espe-

cially well-suited to MICROSAR DIAG and MICROSAR IO, while top-

down 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


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 com-

patibility of the replaced configuration at runtime.

ECU Variants To save on logistical costs in AUTOSAR ECUs, the MICROSAR mod-

ules 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 third-

party 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 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

2/10

MICROSAR OSThe Real-Time Operating System for the AUTOSAR Standard

MICROSAR OS is a pre-emptive real-time multitasking operating

system with optimized properties for use on microcontrollers.

Vector’s many years of experience in developing operating sys-

tems and drivers for microcontrollers are bundled into this small,

robust operating system core.

PropertiesMICROSAR-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/VDX-

OS standard and extended to include schedule tables

SC2: Real-time operating system with time synchronization and

monitoring of the time behavior of individual tasks and interrupt

service routines

SC3: Real-time operating system with memory protection mecha-

nisms 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 syn-

chronized and simultaneous execution of tasks possible in a dis-

tributed system.

> Memory protection (SC3, SC4)

Memory protection protects memory areas so that applications

can be reliably integrated. It ensures that the data of other appli-

cations are not destroyed.

MICROSAR OSModul


> 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 develop-

ment

> 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


2/11

AUTOSAR

> Timing Protection (SC2, SC4)

Timing protection ensures that assumptions made in the early

design phase related to execution times are preserved during run-

time 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 behav-

ior clearly and concisely.

Optional Extensions> High Resolution Timer

If resolutions finer than 1ms are needed for the timers, the mech-

anisms of the High Resolution Timer are advisable, which imple-

ment 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 ◆

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 par-

ticular 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.

Training

In the framework of our training program we can offer vari-

ous training courses and workshops on MICROSAR at our

classrooms or at your business site.



Contact and AvailabilityFor 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 AUTOSARprojects.Find your contact person at: www.vector.com/contact


EMBEDDED SOFTWARE



> 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 multi-

core 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.

MICROSAR OS Multi-Core AUTOSAR operating system for multi-core processors

V2.0

201

1-03

Architecture model of a multi-core application with MICROSAR OS Multi-Core and MICROSAR Basic Software

EMBEDDED SOFTWARE


2/12

MICROSAR COMAUTOSAR Basic Software Modules for Communication

The basic software modules (BSW) of MICROSAR COM include

AUTOSAR services for ECU communication. These services can

support any number of communication channels. They are bus-in-

dependent 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 AreasMICROSAR COM lets users develop their functional software by a

fully bus-independent approach. All necessary tasks for transmit-

ting messages and for cross-bus network management activities

are handled by the configurable BSW modules COM, NM, PDUR and

IPDUM from MICROSAR COM.

For a gateway ECU, you do not need any additional software. The

COM and PDUR BSW modules from MICROSAR COM enable routing

of signals and TP or application messages.

FunctionsThe 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 func-

tional 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 ECU’s

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 COMModules


> 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


2/13

AUTOSAR

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 communi-

cation as complex device driver

> PDUR: Intra-ECU communications for TP connections

> PDUR: Optimized routing per ASR 4.0 (e.g. with Burst Transmis-

sion) 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)


> DLLs for configuration with GENy

> Documentation

◆

Configuring the COM module with GENy

Training

In the framework of our training program, we can offer vari-

ous training events and workshops for MICROSAR in our

classrooms as well as at your business site.




You will find information on the availability of hardware-spe-

cific MICROSAR BSW modules at:

www.microsar.com/availability/ We can also tell you about OEM-specific versions and custom

support for your AUTOSAR projects.



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 func-

tional features of individual DaVinci Tools in the relevant

datasheets.


2/14

MICROSAR CANAUTOSAR 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 AreasMICROSAR 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.

FunctionsThe 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 CANmodules


> Code and execution time are optimized based on need-

specific 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/15

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 Trans-

mission) 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


source code

> Command line based generator (for Windows NT/2000/XP/

Vista/Windows 7)



> Documentation

Other MICROSAR Products for a Complete CAN CommunicationStackBased 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 comprehensiverange of products and services for your CAN projects

Training


ous training events and workshops for MICROSAR in our

classrooms as well as at your business site.




You will find information on the availability of hardware-spe-

cific MICROSAR BSW modules at:

www.microsar.com/availability/ We can also tell you about OEM-specific versions and custom



The complete AUTOSAR Solution from Vector






datasheets.


EMBEDDED SOFTWARE


V2.5

201

1-02

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 net-

works. Furthermore, it is ideal as a foundation for calibration with

XCP, gateways or flashing.


> Small code size and short execution times due to optimized admini-

stration of job lists of the FlexRay interfaces

> Either the FRTP (AUTOSAR) or FRISOTP (ISO 10681) transport proto-

col 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, con-

formant 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 sys-

tems, 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

MICROSAR FR AUTOSAR Basic Software Modules for FlexRay Communication

EMBEDDED SOFTWARE



You can find information on the availability of hardware-specific


We would be glad to provide you with information on OEM-specific

versions as well as customized support for your AUTOSAR projects.


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

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)



> Documentation


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 Communica-tion 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


> 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 compo-

nents (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

2/18

MICROSAR LINAUTOSAR 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 AreasMICROSAR LIN is used to handle communication tasks for a LIN

Master in a LIN network. In addition, it may be used as a founda-

tion for gateways or flashing.

Functions The BSW modules in MICROSAR LIN contain functions defined in

AUTOSAR Release 3.x.

In addition, BSW modules from MICROSAR LIN contain the follow-

ing services. Some of them are specified in AUTOSAR Release 4.0

(ASR 4.0):

> 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 sub-

modes 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 con-

nected LIN1.3 and LIN2.x Slaves. This information is saved in the

ECU Configuration Description and is considered when configur-

ing the master. This lets the master evaluate the response error

bits sent by the slaves and then initiate the associated DEM

events.

MICROSAR LINmodules


> 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 Vector’s many years of experience with produc-

tion software for LIN


2/19

AUTOSAR


source code


Vista/Windows 7)



> Documentation

Other MICROSAR Products for a Complete LIN CommunicationStackBased 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:

> 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


Other Relevant MICROSAR Products for LIN> DET, ECUM and COMM from MICROSAR SYS ◆

Vector offers you a comprehensiverange of products and services foryour LIN projects

Training













datasheets.


2/20

MICROSAR IPAUTOSAR Basic Software Modules for Communication over Internet Protocol via Ethernet

The Internet Protocol (IPv4) based on TCP/IP via Ethernet repre-

sents a very widely used standard for transporting data at high

rates. Standardization of this Internet technology for use in auto-

motive 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 de-

fined in the AUTOSAR architecture: ETHXCP, SOAD, ETHSM, ETHIF.

In addition, it contains the base package for IPv4: IPBASE.

Application AreasWith MICROSAR IP in the ECU and a conventional PC as a commu-

nication 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 imple-

ments the necessary gateway functionality in combination with

other MICROSAR packages.

FunctionsThe 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 hardware-

independent control of the various Ethernet drivers.

> ETHSM: The AUTOSAR Ethernet State Manager handles activa-

tion/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 mod-

ules 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


> 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

MICROSAR IPmodules


2/21

AUTOSAR

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).

ConfigurationMICROSAR IP is configured with the familiar configuration tool

GENy. IP-specific configuration parameters are saved as an exten-

sion in the “ECU Configuration Description”.


source code


Vista/Windows 7)

> BSW module description


> Documentation

Other Relevant MICROSAR ProductsBased 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 applica-

tion 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


Other Relevant Products for Ethernet> DCM and DEM from MICROSAR DIAG


> XCP ◆

Training






Contact and AvailabilityFor 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 customized support for your AUTOSARprojects.Find your contact person at: www.vector.com/contact







datasheets.

Vector offers you a comprehensiveportfolio of products and servicesfor your IP projects


2/22

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.

Application AreasMICROSAR MOST lets you connect AUTOSAR ECUs to a MOST ring to

exchange data on the control and asynchronous channel. In addi-

tion, MICROSAR MOST contains all of the services required to

implement gateway functionality to CAN, LIN, FlexRay and Ether-

net buses.

BSW modules from MICROSAR MOST are interfaced to the applica-

tion 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).

FunctionsThe 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 SystemMOST 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.

ConfigurationMICROSAR MOST is configured with the familiar GENy configura-

tion tool. MOST specific configuration parameters are saved as an

extension in the “ECU Configuration Description”.

MICROSARMOST modules


> 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


2/23

AUTOSAR

For gateways, in particular, Vector offers customized solutions

that take into account the special aspects of OEM-specific data

formats in configuration.


source code


Vista/Windows 7)



> Documentation

Other MICROSAR Products for a complete MOST CommunicationStackMICROSAR MOST, together with the general communication mod-

ules COM and PDUR from the MICROSAR COM packet, combine to

form a communication stack for MOST.

To interface this communication stack to a MOST bus, a Network

Services Library and a low level driver (MOSTDRV) are also neces-

sary. These two components are not included with the MICROSAR

MOST product.

Other Relevant MICROSAR Products for MOST> DCM and DEM from MICROSAR DIAG

> DET, ECUM and COMM from MICROSAR SYS ◆

Vector offers a comprehensiverange of products and servicesfor MOST projects

Training













datasheets.

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/24

MICROSAR MEMAUTOSAR Basic Software Modules for Memory Management

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 AreasMICROSAR MEM lets you develop your functional software plat-

form-independently. MICROSAR MEM contains AUTOSAR services

for reading, writing and erasing persistent application data in

flash and/or EEPROM memories. This gives the functional soft-

ware 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.

FunctionsThe 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 soft-

ware.

For special requirements, Vector offers platform-optimized solu-

tions, e.g. for using the EA BSW module in data flashing or opti-

mizing the FEE module for specific hardware.


> NVM: Block type “DATASET_ROM” with multiple ROM blocks

> NVM: Data protection with CRC8

MICROSAR MEMmodules


> 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


2/25

AUTOSAR

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


source code


Vista/Windows 7)



> Documentation

Other MICROSAR Products relevant for a Memory StackBased 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 semiconduc-

tor 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 theNon volatile RAM Manager

Training

In the framework of our training program we offer various

training courses and workshops on MICROSAR at our class-

rooms or at your business site.



Contact and AvailabilityFor 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 of your AUTOSARprojects.Find your contact person at: www.vector.com/contact


Vector offers a fully tuned AUTOSAR solution for developing

AUTOSAR ECUs with its DaVinci and MICROSAR products.


the MICROSAR packages as well as detailed descriptions of

functional features of the DaVinci Tools in separate data-

sheets.


EMBEDDED SOFTWARE


V2.6

201

1-06

MICROSAR SYS modules

Overview of Advantages:

> The ECUM module is included as either a resource-saving Pre-

Compile 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 impor-

tant 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 soft-

ware components (SWC) of the functional software.

The package is platform-independent. To operate MICROSAR SYS

on your hardware, you combine it with hardware-dependent driv-

ers 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 Communica-

tion 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 func-

tion 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 soft-

ware modules, including the RTE and OS. It puts the ECUs in dif-

ferent operating modes at the request of the SWCs.

MICROSAR SYS System-related Basic Software Modules for AUTOSAR

EMBEDDED SOFTWARE





We can also tell you about OEM-specific versions and custom support

for your AUTOSAR projects.


Training


training events and workshops for MICROSAR in our classrooms as well

as at your business site.



> 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 com-

munication 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 mod-

ules from the memory stack.

> RAMTST: The hardware-independent module RAM Test enables

synchronous or asynchronous checking of the physical func-

tional 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 func-

tional 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.


source code

> Command line based generator (for Windows XP/Vista/Windows 7)



> Documentation



MICROSAR-basic software and the MICROSAR RTE.




Configuring the SYS module with DaVinci Configurator Pro

MICROSAR DIAG modules

EMBEDDED SOFTWARE


V2.5

201

1-08

Summary of Advantages

> Customized solutions available for many automotive OEMs

> Vector�s 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 implementa-

tion of UDS protocol ISO 14229-1:2006 and is ideal as diagnostic

software for your vehicle project. MICROSAR DIAG performs a num-

ber 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 solu-

tion 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 require-

ments 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 identi-

cal 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) inde-

pendent 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

MICROSAR DIAG AUTOSAR Basic Software Modules for the UDS Protocol

EMBEDDED SOFTWARE


specific carmakers. A generic OEM-independent variant is also

available. This version supports the following functions as stan-

dard 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 sup-

ported UDS and OBDII services, as well as the necessary tasks of

the application software.


> 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, ECU-

PassiveMode)

> 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





variants and individual support for your AUTOSAR projects.


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

EMBEDDED 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 �diag-

nostic authoring tool� CANdelaStudio.

The DEM may be configured via either a CDD file or an �ECU Con-

figuration 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)



> Documentation

> Converters for CANdela diagnostic descriptions



MICROSAR-basic software and the MICROSAR RTE.




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 Vector�s

diagnostics catalog.

Services for Diagnostic Applications:

> Customer-specific extensions of MICROSAR DIAG

> Creation of a customer-specific diagnostic application

> Integration of diagnostics in your ECU software

MICROSAR DIAG is parameterized with CANdelaStudio and GENy

EMBEDDED SOFTWARE


The module DCM from MICROSAR DIAG supports �

� by default: UDS diagnostic services

� Optionally: OBD II diagnostic services according to AUTOSAR 3.1

Diagnostic Service Name (ISO 14229-1)

Service ID

AUTOSAR Extension

The SCW has to �

Diagnostic and Communication Management Functional Unit

DiagnosticSessionControl 10 � grant service execution

ECUReset 11 X � grant service execution

SecurityAccess 27 � calculate seed/key for each security level

CommunicationControl 28 X � grant service execution

TesterPresent 3E -

ControlDTCSetting 85 - (is handled in DEM module)

Data Transmission Functional Unit

ReadDataByIdentifier (RDBI) 22 � handle data acquisition for each DataId

ReadMemoryByAddress 23 X -

ReadDataByPeriodicIdentifier 2A - (internal, but data acquisition is done through RDBI)

DynamicallyDefineDataIdentifier 2C - (internal, but data acquisition is done through RDBI)

WriteDataByIdentifier 2E �handle data access for each DataId

WriteMemoryByAddress 3D X -

Stored Data Transmission Functional Unit

ReadDTCInformation 19 - (is handled in DEM module)

ClearDiagnosticInformation 14 - (is handled in DEM module)

Input/Output Control Functional Unit

InputOutputControlByIdentifier 2F � control I/O for each DataId

Remote Activation Of Routine Functional Unit

RoutineControl 31 � start (stop/request result) for each RoutineId

Diagnostic Service Name (ISO 15031-5)

Service ID

The SCW has to �

Diagnostic Service Definition for CAN

Request Current Powertrain Diagnostic Data 01

� handle data acquisition for each PID other than the "supported ID" and DEM ones

Request Powertrain Freeze Frame Data

02 - (is handled in DEM module)

Request Emission-Related Diagnostic Trouble Codes


Clear/Reset Emission-Related Diagnostic Information


Request On-Board Monitoring Test Results for Specific Monitored Systems

06 � handle data acquisition for each TestId of a MonitorId

Request Emission-Related Diagnostic Trouble Codes Detected During Current or Last Completed Driving Cycle


Request Control of On-Board System, Test or Component

08 � process each TestId

Request Vehicle Information 09 � handle data acquisition for each InfoType ID other than the "supported ID" and DEM ones

Request Emission-Related Diagnostic Trouble Codes with Permanent Status

0A - (is handled in DEM module)

EMBEDDED SOFTWARE


V2.4

201

1-06


> 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 hard-

ware buffers

> Gateway developments are supported by efficient auxiliary func-

tions

The MICROSAR CAL package contains the drivers for controlling the

microcontroller�s peripherals. These drivers are fully compatible

with the AUTOSAR specifications of the �Microcontroller Abstrac-

tion Layer�. Each MICROSAR CAL driver is optimized controller-

specifically.

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 inte-

grate 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 require-

ments 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 com-

monly 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 auto-

matically execute application-specific code.

MICROSAR CAL AUTOSAR Driver for Control of Microcontroller Peripherals

MICROSAR CAL modules

EMBEDDED SOFTWARE



For information on the availability of hardware-specific MICROSAR

BSW modules go to: www.microsar.com/availability/


versions and individual support for your AUTOSAR projects. Find your

contact person at: www.vector.com/contact

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.



> DIODRV: User-configurable locating of the pins within a Chan-

nelGroup

> ICUDRV: Notification of timer overrun and in signal measure-

ment mode

> MCUDRV: Reset mechanisms are user-configurable for the func-

tion 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 diag-

nostic command.

> CANDRV: Extended filter options for multiple basic CAN objects

> CANDRV: Rx queue for reducing interrupt execution time while

receiving messages


source code





> Documentation



MICROSAR basic software and MICROSAR RTE.


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. semicon-

ductor manufacturers, in DaVinci Configurator Pro. This lets the

user configure the entire ECU software with a single tool, seam-

lessly 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

2/34

MICROSAR EXTAUTOSAR drivers for control of external devices

MICROSAR EXT contains communication-related AUTOSAR trans-

ceiver drivers for CAN (CANTRCV), FlexRay (FRTRCV), LIN (LINTRCV),

Ethernet (ETHTRCV) and drivers for other external devices such

EEPROM, flash memory and watchdog (DRVEXT). Functions con-

tained 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 avail-

able for many commonly used devices.

Application AreasMICROSAR EXT gives you a turn-key solution for driving your exter-

nal peripheral devices. So, it is not necessary to modify the func-

tional 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.

FunctionsThe 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)


source code


Vista/Windows 7)



> Documentation

MICROSAR EXTmodules


> 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


2/35

AUTOSAR

#

Other Relevant MICROSAR ProductsThe 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 ServicesVector can offer services for integrating the configuration of your

drivers or drivers by third-party producers, such as semi-conduc-

tor manufacturers in DaVinci Configurator Pro. This lets you con-

figure the entire ECU software with a single tool, seamlessly and

quickly. ◆

Configuration of MICROSAR EXT withDaVinci Configurator Pro

Training









tools, MICROSAR basic software and MICROSAR RTE.


the MICROSAR packages as well as detailed descriptions of

functional features of the DaVinci Tools in separate data-

sheets.


EMBEDDED SOFTWARE


V2.3

201

1-06


> 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 ECU�s periphery. Vector offers them in the MICROSAR IO pack-

age. 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 sig-

nals. 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

MICROSAR IO AUTOSAR Input-Output Hardware Abstraction

MICROSAR IO modules

EMBEDDED SOFTWARE



For information on the availability of hardware-specific MICROSAR

BSW modules go to: www.microsar.com/availability/


versions and individual support for your AUTOSAR projects.


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.



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 founda-

tion for later generation of the RTE.


source code




> Documentation



MICROSAR basic software and MICROSAR RTE.


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 Vector�s detailed knowledge of

the AUTOSAR specification and methodology as well as its exten-

sive experience in integration of ECU software.

Konfiguration des Moduls IO mit DaVinci Configurator Pro

2/38

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

MICROSAR RTE (Run Time Environment) is the scalable and highly

optimized AUTOSAR 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 bet-

ween 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 AreasWhen 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 regener-

ated 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 possi-

ble 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 RTEmodule


> 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


2/39

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 RTE’s configuration parame-

ters. 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 pos-

sible.

Scope of Delivery> Command line based generator (for Windows NT/2000/XP/

Vista/Windows 7)


> Documentation

Other Relevant MICROSAR Products:The RTE requires the presence of an operating system such as

MICROSAR OS or osCAN. ◆

MICROSAR RTE enablesgeneration of codetemplates for the SWCs

Training









tools, MICROSAR basic software and MICROSAR RTE.


the MICROSAR packages as well as details on functional fea-

tures of the DaVinci Tools in separate datasheets.


2/40

MICROSAR SafeSafety according to ISO DIS 26262 for ECUs with AUTOSAR Software

Application AreasVector, together with partner TTTech Automotive, is offering a

solution for using standard MICROSAR software modules in ECUs

with safety-related functions. MICROSAR Safe assures the con-

formance of your AUTOSAR-based applications (SWCs) to ISO DIS

26262. For this purpose, TTTech has developed a generic, certified

supplement for ECUs up to ASIL D, which Vector is integrating in

its MICROSAR Basic Software (BSW).

You benefit from using a pre-certified solution because MICROSAR

Safe drastically reduces certification costs for your ECUs, while

simultaneously increasing quality with reusable and proven com-

ponents.

FunctionsThe ISO DIS 26262 certified software modules of MICROSAR Safe

guarantee that safety-related SWCs will have reliable access to

BSW services. They also let you run different SWCs for different

ASILs. Specifically, they contain the following functionality:

> SafeCom: Reliable intra- and inter-ECU communication

> SafeExecution: Runtime monitoring of tasks

> SafeExecution: Memory protection

> SafeExecution: Program Flow Monitoring for safety-related SWCs

> SafeExecution: Assured freedom from interference by non-safety

SWCs to safety-relevant SWCs on the same ECU

> SafeSelfTest: Periodic hardware checking during operation

Reliable Intra- and Inter-ECU CommunicationData that is exchanged between safety-critical applications must

be checked for transmission accuracy. This involves protecting the

data contents by a checksum and monitoring for the correct

sequence of data with a message counter. If one of these tests

fails, the application is informed and can react accordingly. Errors

are detected such as masquerading, incompletion, permutation

etc.

Runtime MonitoringRuntime monitoring ensures that tasks have sufficient computing

time for execution. Conformance of MICROSAR OS’s runtime moni-

toring (Scalability Class 2 or 4) to ISO DIS 26262 is assured by the

SafeWatchdogManager module from the SafeExecution packet.


> Solution for all Automotive Safety Integrity Levels (ASIL)

through ASIL D

> Offers savings in certification costs

> Supports different ASILs on one controller

MICROSAR Safe


2/41

AUTOSAR

Memory ProtectionMemory protection provides separation between the different

software components. It prevents unauthorized writing by one

software component to the memory of another software compo-

nent that would corrupt the data. Conformance of MICROSAR OS’s

memory protection (Scalability Class 3 or 4 on suitable microproces-

sors) to ISO DIS 26262 is assured by the SafeMemoryProtection

module from the SafeExecution packet.

Program Flow MonitoringCorrect execution of safety-related SWCs is assured by program

flow monitoring. This involves having the SafeWatchdogManager

performs monitoring of so-called checkpoints in the software

components. If the flow is correct, the SafeWatchdogManager

sends an alive signal to the watchdog.

Freedom from InterferenceThe measures described above assure correct execution of safety-

related and non-safety-related SWCs running side-by-side on the

same ECU. This prevents software sections whose correct execu-

tion cannot be verified from unnoticed interference with safety-

related functions.

Hardware CheckingGeneric test functions periodically monitor the ECU’s various

hardware parts for error-free functionality.

ConfigurationThe modules of MICROSAR Safe are configured with DaVinci

Configurator Pro, with the exception of the SafeCom module,

which is configured with DaVinci Developer.

Scope of Delivery> Software modules as library with C header files and BSW

module description, optionally as source code

> Instruction line based generator (for Windows NT/2000/

XP/Vista/Windows 7)


> Documentation

Other relevant MICROSAR productsIt is possible to execute consistency checking of the communica-

tion data in ECUs without safety-relevant functions. The LIBS

packet from MICROSAR SYS contains the E2ELIB that is used for

this purpose. ◆

Implementation

Safety-relevant functions are implemented by adding safety

modules from TTTech to Vector’s MICROSAR AUTOSAR solution.

These safety modules detect and handle potential errors in non-

safety-relevant software layers. The safety modules are devel-

oped according to ISO DIS 26262 and certified according to

ASIL D.

The MICROSAR basic software is extended by adding the follow-

ing safety modules from TTTech:

SafeCOM (according to AUTOSAR 4.0):

> E2ELIB: End-to-end library

> Safety Wrapper: End-to-end protection wrapper

SafeExecution:

> SafeMemoryProtection

> SafeWatchdogManager

SafeSelftest:

> RAM Test

> ROM Test

> Core Test

> I/OTest



tools, MICROSAR Basic Software and the MICROSAR RTE.


the MICROSAR package and detailed descriptions of function-

al features of individual DaVinci Tools in the relevant data-

sheets.


For information on the availability of hardware-specific

MICROSAR BSW modules go to:

http://www.vector.com/ds_microsar.availability_enWe would be glad to provide you with information on OEM-spe-

cific versions and individual support for your AUTOSAR projects.



2/42

Identity Manager for AUTOSARSolution for Multiple ECUs

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 vari-

ants and can provide practice-oriented solutions for multiple ECUs

based on AUTOSAR Release 3.x.

Physical Multiple ECUOne 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 pro-

duced.

Via the so-called Identity (see box), each ECU knows during start-

up 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 ConfigurationWith the multiple configuration, it is possible to use an ECU in dif-

ferent car lines, and therefore in completely different communica-

tion 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 soft-

ware is based may differ very significantly for the different vari-

ants, they may exhibit a completely different signal layout or

support a different number of buses. Here too, the identity of the

ECU is determined when it is started.

Physical Multiple ECU and multiple configuration


> Efficient handling of ECU variants

> Less administration effort

> Reduced inventory costs

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.


2/43

AUTOSAR

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 ConceptAccording 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 rele-

vant ECU-specific information.

Proven Configuration ProcessThe 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 con-

figures the multiple ECU like a normal ECU. The Project Assistant

that is contained in the tools supports the user here.

DiagnosticsTo describe the diagnostics of an ECU, one diagnostic description

file (CDD) is needed per ECU. Exactly as in communication, identi-

cal 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 ResourcesSince Physical Multiple ECUs are identical in much of their con-

tent, for optimization no separate set of configuration para-

meters is created for some BSW modules but only a common set is

created for all instances. This applies to such elements as identi-

cal 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 DeliveryThe scope of delivery of the Identity Manager includes:

> License for enabling in the configuration tool

> BSW modules with Identity Manager functionality ◆

Configuration processof multiple ECUs



tools, MICROSAR Basic Software and the MICROSAR RTE.


the MICROSAR package and detailed descriptions of function-

al features of individual DaVinci Tools in the relevant data-

sheets.


You will find information on the availability of hardware-

specific MICROSAR BSW modules at:

www.microsar.com/availabilityWe can also tell you about OEM-specific versions and customer




EMBEDDED SOFTWARE


V2.3

201

1-05

MICROSAR CAL [2, 3] Controller Compiler MICROSAR OS[1] CAN FlexRay LIN IP/Ethernet Further MCAL Driver

Altera

NIOS II GNU, Tasking X

Atmel

AVR32 IAR X X X

Freescale

i.MX25, i.MX35 GNU X

MAC7100 ARM, IAR X X

S12X Cosmic, Metrowerks X X X X X

MPC55xx Green Hills, Metrowerks, Wind River

X X X X [4] X

MPC56xx

(QORIVVA/ 5xxx/Automotive)

Green Hills, Metrowerks, Wind River

X X X X X X

Fujitsu

16FX Fujitsu X

FR60 Fujitsu X X X

FR81 Fujitsu X X

MB86 GNU X X

Infineon

CIC310 (External Controller)

X

TriCore GNU, Green Hills, Tasking

X X X X X

XC2000 Tasking X X X

Microchip

PIC24 Microchip X

dsPic33F Microchip X

Renesas Electronics (NEC/Renesas)

78K0R IAR X X

V85x Green Hills, IAR, Renesas

X X X X X X

M32C Renesas, IAR X X

M32R Renesas X

R32C Renesas, IAR X X X X

Wide Availability of MICROSAR Supported Microcontrollers and Compilers for the hardware-specific AUTOSAR BSW Modules

EMBEDDED SOFTWARE


MICROSAR CAL [2, 3] Controller Compiler MICROSAR OS[1] CAN FlexRay LIN IP/Ethernet Further MCAL Driver

R8C IAR X

SH2 Renesas, Green Hills X X X

STMicroelectronics

SPC56xx Green Hills, Metrowerks, Wind River

X X X X X X

STR9 GNU X

Texas Instruments

TMS320 Texas Instruments X

TMS470 Texas Instruments X X

TMS570 Texas Instruments X X X X X

Vector

CANoe osCAN Emulation

Microsoft VisualC X X X X X X

[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] = 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

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.


2/44

DaVinci Developer Designing AUTOSAR Software Components and Configuring 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 ECU‘s basic software.

Application AreasDaVinci 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.

FunctionsDaVinci 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 communi-

cation 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 compo-

nents, compositions, calibration and service components

> Import and export of AUTOSAR XML formats (System Descrip-

tion 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


> 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 – Design toolfor AUTOSAR-conformant ECUs


2/45

AUTOSAR

Workflows and AUTOSAR MethodsDaVinci Developer can be flexibly used in a distributed develop-

ment 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 indi-

vidual 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 fine-

granulation versioning of individual objects, e.g. SWCs

Configuration of the MICROSAR RTEDaVinci Developer is used to configure the MICROSAR RTE; it sup-

ports 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 Recommended Minimum

Processor Pentium 4/2.6 GHz Pentium III/1 GHz

Memory (RAM) 2 GB 1 GB

Screen resolution 1280 x 1024 1024 x 768

Operating system Windows XP SP2 or SP3Windows 7 (32- or 64-Bit)

◆

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


Vector‘s 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.

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



> 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 ECU�s application software can be devel-

oped 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 regres-

sion 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.

DaVinci Component Tester 1.0 Testing AUTOSAR Application Software on the PC

V2.4

201

1-07

Testing a composition of multiple software components with DaVinci Component Tester

Testing atomic AUTOSAR 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 simu-

lates 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 SWC�s

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 inde-

pendently according to the trigger specification, e.g. periodi-

cally every 10 ms. Therefore DaVinci Component Tester synchro-

nizes 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 SWC�s 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 SWC�s application ports. This

reduces the complexity of the test environments considerably.

The service emulator may be accessed at any time. For example,

you can preset a block with a certain value that is read out by the

SWC from nonvolatile memory, or you can check the value changed

by the SWC. Similarly, users can control or monitor the current

state of the ECU Manager from a test case.

The service emulator supports AUTOSAR standard services of the

following basic software modules:

> 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 (Intelli-

Sense). For example, a user could easily program access to a

receiver port by listing all of the SWC�s 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 inte-

grated 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 SWC�s 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 SWC�s

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 Profes-

sional 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

2/50

DaVinci Configurator ProConfiguration of AUTOSAR Basic Software

Vector’s DaVinci Configurator Pro is the professional tool for con-

figuring the Basic Software (BSW) modules of an AUTOSAR ECU

according to the AUTOSAR standard.

Properties and AdvantagesDaVinci Configurator Pro was created as an open tool for configur-

ing and generating BSW modules. It is a practical, intuitive and

user-friendly implementation of the AUTOSAR method. In addi-

tion, 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 de-

scription 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 deacti-

vation of individual BSW modules

> 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 AreasDaVinci 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.

FunctionsDaVinci 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 withDaVinci Configurator Pro


2/51

AUTOSAR

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 pack-

ets as well as diagnostic modules from DIAG. GENy offers a user-

friendly 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

System Requirements






Additional Services> Creating DaVinci description files for convenient and user-

definable configuration, validation and generation of any

desired modules with DaVinci Configurator Pro


embedded software and AUTOSAR ◆

DaVinci Configurator Pro supports you in conveniently configuring, validating and generating AUTOSAR BSW modules.

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 fileafter 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 pro-jects, as well as with customized services such as a hotline,special workshops and training on the topic of embeddedsoftware and AUTOSAR. For more information go towww.microsar.com or contact us directly.


2/52

DaVinci Configurator KitCreating configuration interfaces and generators for user-developed software modules

The AUTOSAR architecture currently defines approx. 50 configura-

ble standard Basic Software (BSW) modules. Each module is con-

figured 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 in-

house embedded software modules. This lets you concentrate ful-

ly 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 Vector’s

many years of experience with AUTOSAR.

Properties and AdvantagesThe DaVinci Configurator Kit supports the embedded module

developer in designing individual configuration interfaces for

user-developed software modules and creating flexible code gen-

erators.

As a supplement to the AUTOSAR method, the DaVinci configura-

tion 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 anoth-

er. For user-created software modules, you can also use the

DaVinci Configurator Kit to define the validation rules.

Application AreasThe DaVinci Configurator Kit supports developers of AUTOSAR

basic software modules, complex device drivers and user-devel-

oped 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 integrat-

ing your own C++ based DLLs

> Protect your own know-how by encrypting DaVinci description

files

DaVinci ConfiguratorKit supports you inintegrating your software module inDaVinci ConfiguratorPro


AUTOSAR

2/53

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

System Requirements






Additional Services> Designing convenient configuration interfaces and supplemen-

tal 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


embedded software and AUTOSAR ◆

ServicesVector can support you with standard software for your pro-jects, as well as with customized services such as a hotline,special workshops and training on the topic of embeddedsoftware and AUTOSAR. For more information go towww.microsar.com or contact us directly.

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

Defining a module’s configu-ration parameters with theEparm tool from the DaVinciConfigurator Kit.


2/54

AUTOSAR ServicesProficient support for your AUTOSAR projects

With our AUTOSAR Software Engineering Services, we support you

in every phase of your ECU development. Starting with our ex-

tensive 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 TrainingVector 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 busi-

ness site. It is possible to adapt the training content to your indi-

vidual needs.

MICROSAR Installation and SupportYou 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 busi-

ness site.

Afterwards, hotline support is available to you by telephone or

email, which ensures continuous support in case you have ques-

tions about how to use our products.

MICROSAR ReviewsYou have been using our AUTOSAR Embedded Software for a lon-

ger period of time, and you are approaching an important project

milestone.

Based on prepared checklists, we conduct an integration and con-

figuration 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 integra-

tion code. In particular, OEM-specific aspects are also considered,

such as provided software components.


> Builds up knowledge efficiently and effectively

> Tailored support

> Quick implementation of your application


2/55

AUTOSAR

MICROSAR Coaching In MICROSAR Coaching, installation of the MICROSAR software is

performed with your concrete application, which takes your spe-

cific 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 addi-

tion to the telephone and email Hotline. Based on the specific

objectives that were agreed on, we ensure individual support of

your project.

AUTOSAR ConsultingIn 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 soft-

ware 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 DevelopmentMoreover, 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. ◆

For more information

On our “AUTOSAR Services” please contact us. Please find

your contact person at: www.vector.com/contact


3/0

Solutions with CANbedded

The software implemented in automotive ECUs can be either infra-

structure software or application software. The latter implements

the desired functionality, while the infrastructure software in-

cludes the operating system, communication software and funda-

mental input and output services.

The use of uniform communication protocols is absolutely neces-

sary when setting up networks in a vehicle. The use of standard-

ized software components ensures easy portability and reliable

integration of ECUs in the vehicle’s network for the automotive

OEM and its suppliers. In addition, the software components lead

to a substantial reduction in development costs.

CANbeddedVector 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 indi-

vidual 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 startVector offers comprehensive support, from the start of a project

to its successful completion. Training sessions and courses pro-

vide basic information and in-depth knowledge on working with

the software – conducted in Vector’s classrooms or right at your

company. Vector can assist you through the ECU development

process with on-site startups, code reviews, project-specific serv-

ices and other development-supporting software tools.

CANopenFor CANopen communication, Vector offers source code for master

and slave ECUs. The source code contains all functions and serv-

ices required for the CANopen protocol, which are standardized by

CiA. Detailed information on this can be found beginning on page

3/20.

Uniform solutionNetwork 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 devel-

opers a universal and uniform solution, from simulation and

design to testing and validation.

Further information on tools for development and testing of auto-

motive networks can be found in the combined product catalog

“Development of distributed systems” and “ECU testing”.

Communication Software for AUTOSAR SystemsVector 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/1

COMMUNICATION SOFTWARE

>> CONTENTS

CANbedded 3/2CANbedded J1939 3/6CANbedded LIN Communication 3/8CANbedded Gateway 3/12CANdesc and CANbedded DEM 3/14Identity Manager 3/16GENy 3/18CANopen Master Source Code 3/20CANopen Slave Source Code 3/24Feature Matrix CANopen Source Codes 3/26CANerator CANopen 3/28XCP Professional 3/30


3/2

CANbeddedBasic 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 com-

bine as necessary to form a communication stack. This provides

you with a reliable foundation for your ECU.

Application AreasCANbedded lets users focus their efforts completely on their func-

tional software, because the CANbedded stack handles OEM-con-

formant 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 compati-

bility 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 soft-

ware 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.

Overview of Advantages:

> Reliable and tested through many years of development

> Generated source code that is scalable and application-

specific

> 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

Overview of theCANbedded softwarecomponents


3/3


FunctionsCANbedded provides simple interfaces (APIs) that are identical for

all applications. If possible, the API is standardized over all OEM

and hardware variants. This let’s the user quickly and convenient-

ly 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 select-

ing the components you need.

CAN DriverThe CAN driver provides an interface for higher software layers

that is as hardware independent as possible. This enables plat-

form-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 configura-

tion time. The configuration tool GENy from Vector offers prese-

lections 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 network’s 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

Configuration and parameterizationwith the GENy configuration tool


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


3/4

the 1999 variant or the 2004 variant and with different address-

ing methods (Normal, Extended, Normal fixed, Mixed).

Communication Control Layer (CCL)The CCL simplifies integration of the CANbedded software compo-

nents 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

ConfigurationYou configure CANbedded with the PC-based configuration tool

GENy. GENy utilizes information from the communication data-

base (e.g. the DBC file from the OEM) as well as manual settings.

GENy generates parameterization files based on the configura-

tion. 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 DeliveryYou 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

The CCLcoordinates thestate transition“Wakeup”

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.)


3/5


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.

Additional ServicesYou 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, spe-

cial 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 comprehensiverange of products and servicesfor your CAN projects

Training


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


3/6

CANbedded J1939Embedded Software Components for J1939 Applications

The CANbedded J1939 package contains software components for

SAE J1939-based applications. These components provide func-

tions 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 soft-

ware components are available as source code.

Application Areas> Powertrain and chassis ECUs in heavy-duty vehicles

> FMS (Fleet Management System)

> Terminals and agricultural implements

FunctionsThe 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

> 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 inter-

face.


> 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. trans-

port protocol, diagnostics, etc.)

Supported Standards

J1939 software components are based on the following inter-

national 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 con-

form to these standards.

J1939 software architecture


3/7


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

ConfigurationThe PC-based GENy software tool is used to configure and gener-

ate the CANbedded J1939 software components.

Scope of DeliveryThe CANbedded J1939 product includes:

> GENy for configuring the software components

> C source code

> C header files

> Documentation, user manual, Readme

> Sample programs

Optional ServicesVector 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.

◆

Configuring the J1939 system witha convenient user interface

Solutions for ISO11783 and NMEA2000We offer a CANbedded J1939 extension for ISO11783 (ISOBUS) and NMEA2000. It contains the following function-alities:

> 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

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/8

LIN (Local Interconnect Network) is a cost-effective, serial com-

munication system for distributed electronic control units in the

motor vehicle. The LIN protocol is specified by the LIN Consor-

tium, of which Vector is an Associate Member.

Features and AdvantagesIncreasing software complexity makes it advantageous to imple-

ment standardized software components. Vector’s expertise ac-

quired 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 gen-

erated 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 and LIN 2.1

> Support of multi-channel LIN configurations

LIN networks are described in the LDF (LIN Description File) for-

mat according to the “LIN Configuration Language Specification”.

This includes all of the information needed to define signals, mes-

sages, baud rate and schedule tables. A configuration tool is used

to adapt all LIN software components to ECU-specific require-

ments. 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. Vector’s LIN simulation and analysis

tools (e.g. CANoe.LIN and CANalyzer.LIN) are available for inte-

gration, analysis and for test purposes. For physical bus access one

of Vector’s XLI-Interface products can be purchased; these pro-

ducts 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.

FunctionsThe 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)

CANbedded LIN CommunicationEmbedded Software Components for Local Interconnect Network

Overview of the software componentsof CANbedded LIN Communication


3/9


> 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 AreasLIN was developed to round out a collection of automotive proto-

col 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 InterfacesTwo 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 pro-

vides 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 com-

ponent 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 usu-

ally implemented as master network nodes.

LIN Master Transport LayerSince 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 rele-

vant LIN slaves. The LIN Diagnostic Transport Layer (DTL) is used

for this; it offers two API types according to the LIN 2.0 and 2.1

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 accord-

ing to LIN bus requirements (Diagnostic Service Data Units).

LIN Slave DiagnosticsLINdiag is a very compact implementation of UDS 14229.1 diag-

nostics 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 diag-

nostic 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

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 microcontrol-

lers.

For further information please visit:

http://www.vector.com/vi_canbedded_lin_en.html


3/10

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

Product ComponentsThe 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

LicensesWhen 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 ServicesVector 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 work-

shops with OEM-specific focus and individualized consultation on

software integration with the goal of reducing development time

and costs. ◆


3/11



3/12

CANbedded GatewayStandard Embedded Software Components for CAN and LIN Routing

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 AreasCANbedded 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 quick-

ly. 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 spe-

cific requirements of many different OEMs.

Functions The CANbedded Gateway contains complex mechanisms for receiv-

ing 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 RoutingRouting of signals makes it possible to exchange dedicated infor-

mation (e.g. momentary vehicle speed) between the networks.

The send cycle times, send types and signal positions within mes-

sages – 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 sig-

nal contents before routing (e.g. by scaling signal values).

Message RoutingIn 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 rout-

ing relationships. In message routing, the messages may differ in

their message-ID, send cycle and send type.

Gateway between CANand LIN buses


> Selectable coupling of CAN and/or LIN networks with user-

definable routing relationships

> Mature standard software component

> Solid, lean and efficient foundation for your gateway ECU

> Available for a large number of OEMs


3/13


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 “condition-

al 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 ena-

ble or disable routing of individual groups with the help of an API.

TP RoutingThe 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 ProductsPreconditions 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.

ConfigurationThe CANbedded Gateway is configured with GENy, the configura-

tion and code generator tool from Vector. The configuration pro-

cess is based on a DBC or LDF/NCF description file. Routing rela-

tionships 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 ◆

Training


various training events and workshops on our software com-

ponents in our classrooms as well as at your business site.



Layer model of the CANbedded Gateway


EMBEDDED SOFTWARE


V2.3

201

1-05

Controller Compiler CANbedded/ CANbedded

J1939

CANbedded LIN

Altera

NIOS II with Bosch D-CAN controller

GNU X

Analog Devices

Aduc703x ARM, IAR X

Blackfin BF5xx VisualDSP++ X X

Atmel

AT90CANXX HPInfotech, IAR

X X

ATmega (X8, X4P, XC1, XM1)

HPInfotech, IAR

X X

ATtinyX7 IAR X

AVR32 IAR X X

T89C51CC00x Keil X

Cypress

PSoC3 Keil X

Europe Technologies

easyCAN ARM X

Freescale

68HC08 Cosmic, Metrowerks X X

DSP56F80x Metrowerks X

DSP56F83x Metrowerks X

HC12, HCS12, MC9S12, S12, MCS12

Cosmic, IAR, Metrowerks X X

HCS12x, MC9S12x, S12x, MCS12x

Cosmic, IAR, Metrowerks X X

MAC 7100, MAC 7200 ARM, IAR X X

MC68k Microtec, Tasking X

MCF52xx DIABDATA Wind River X

MCS08 Cosmic, Metrowerks X X

MPC5xx

DIABDATA Wind River, Green Hills, Metrowerks

X X


J1939

CANbedded LIN

MPC5200

DIABDATA Wind River, Metrowerks, QCC

X

MPC55xx, MPC56xx

Cosmic, DIABDATA Wind River, GNU, Green Hills, Metro-werks

X X

Fujitsu

8L, 8FX Fujitsu X

16FX, 16LX Fujitsu X X

FR30, FR50 Fujitsu X

FR60 Fujitsu X X

FR81 Fujitsu [1] X

MB86R0x GNU, QCC X

Infineon

C16x Keil, Tasking X X

C5x5 Keil X

TriCore GNU, Green Hills, Tasking

X X

XC16x Keil, Tasking X

XC2000 Tasking X X

XC800 Keil X

Microchip

dsPic33F Microchip X [1]

PIC18 Microchip X X

PIC24 Microchip X

Micronas

CDC32xxG Green Hills X

CEVF IAR X

National

CR16 National, IAR X X

NXP

LPC2000 Green Hills X

SAF7780 Green Hills X

Wide Availability of CANbedded Supported Microcontrollers and Compilers

EMBEDDED SOFTWARE



J1939

CANbedded LIN

SJA20xx Green Hills X X

OKI

AVC-Core ARM X

ML76Q25xx IAR X

Panasonic

MN101E Panasonic X

MN103S Panasonic X


78k0 Renesas (NEC), IAR

X X

78K0R Renesas (NEC), IAR

X X

78K0S IAR X

H8 tiny Renesas X

H8S, H8SX Renesas, IAR X X

M16C Renesas, IAR X X

M32C Renesas, IAR X

M32R Renesas, GAIO

X

R8C Renesas, IAR X X

R32C Renesas, IAR X X

SH2, SH2-A Renesas, Green Hills, GAIO, IAR

X X

SH4 Renesas, Green Hills, QCC

X

V85x Renesas (NEC), Green Hills, IAR

X X

Silicon Labs

C8051F5XX Keil X

STmicroelectronics

SPC56xx Cosmic, DIABDATA Wind River, Green Hills, Metrowerks

X X

ST7 Cosmic, Hiware X X


J1939

CANbedded LIN

ST9 GNU X X

ST10 GNU, Keil, Tasking

X X

ST30 ARM, Green Hills

X X

STA20 ARM, Green Hills

X

STM32 ARM X

STM8A Cosmic X X

Telechips

TCC800 ARM X

Texas Instruments

TMS320 Texas Instru-ments, QCC

X

TMS470 Texas Instru-ments, ARM, Green Hills

X X

TMS570 Texas Instru-ments, ARM

X X

Toshiba

TLCS870 Toshiba X

TLCS900 Toshiba X

Tx03 ARM X

TX39 Green Hills X

TX49 GNU, Green Hills

X

Xilinx

Microblaze GNU X

Vector

CANoe osCAN Emulation

Microsoft VisualC

X X

[1] = Currently in development

3/14

CANdesc and CANbedded DEMSoftware components for diagnostics

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.

FunctionsCANdesc and CANbedded DEM are conformant to the OEM-specific

diagnostic specification and are available for a number of differ-

ent 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 (Communica-

tionControl), $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 ECU’s diagnostic software


> 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


3/15


> 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 infor-

mation 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

ConfigurationYou 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 advan-

tages. For more details, please refer to the CANdelaStudio data-

sheet in the diagnostics catalog.

Handling of VariantsIf 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/user’s manual/Readme

> C source code for CANbedded DEM

Additional ServicesVector 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. ◆

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

Example of Code SizesMicroprocessor: Motorola HC12, MC9S12P128Compiler: Cosmic 4.713 Diagnostic services and 40 subfunctions are implemented

Code size: approx. 6 kBytesTables and constants: approx. 700 bytesRAM: 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 andthe number of dynamically defined data identifiers.


EMBEDDED SOFTWARE


V2.4

201

1-05

Vector offers embedded software for a large number of OEMs. Addi-

tionally, a version without vendor-specific characteristics is avail-

able.

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 Commu-

nication

Diagnostic

Software

Flash

Bootloader

B

BAIC X X X

Brilliance X

BMW X X X

BYD X

C

CHANA X X X

Chery X X

Chery Quantum

X X X

Chrysler X X X

Claas X X X

D

DAF X X X

Daimler X X X

Dongfeng X X X

F

FAW X X X

FCC X X X

FIAT X X X

Fisker X X X

Ford X X X

Foton X

OEM Commu-

nication

Diagnostic

Software

Flash

Bootloader

G

GAC X X X

Geely X X

GM X X X

Great Wall Motors

X X

H

Honda X X

HMC X X X

I

Isuzu X X

J

JAC Motors X X

Jaguar / Landrover

X X X

M

MAN X X X

Mazda X X X

Mitsubishi X X X

N

NAC X X X

Nissan X X X

P

Porsche X X X

PSA X X X

R

Renault X X X

S

SAIC X X X

SsangYong X X X

Subaru X

Suzuki X X

Supported OEMs For OEM-specific Basic Software

EMBEDDED SOFTWARE

Vector Informatik GmbH > Ingersheimer Str. 24 > 70499 Stuttgart > Tel. +49 711 80670-0 > Fax +49 711 80670-111 > www.vector.com

OEM Commu-

nication

Diagnostic

Software

Flash

Bootloader

T

Toyota X X X

V

Volvo AB X X X

VW/Audi X X X

OEM independent

X X X

Vector is pleased to support further OEMs on request.

3/16

Identity ManagerSolution for Multiple ECUs

When tracking the development of ECUs in automobiles, one trend

is clearly evident – ECUs are becoming increasingly more power-

ful. At the same time, the number of variants is growing drastical-

ly, 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 casesPractice 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 sim-

plification, reduce administrative effort and thereby reduce costs.

Physical multiple ECU

A typical case of physical multiple ECUs are the ECUs for the driver

and passenger side doors. These ECUs have nearly identical func-

tions. However, there are differences in the receive and send mes-

sages, 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 config-

uration 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 dif-

ferently 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, dif-

ferentiate between the left and right sides using generated mac-

ros 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 ECU’s identity.

Advantages

> More efficient handling of variants

> Less administrative effort

> Reduced warehouse 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 ECU’s identity is set

when the ECU is initialized.


3/17


Virtual multiple ECU

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 data-

base. In the configuration tool GENy, you only need to select tho-

se 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.

Multiple configurations

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 pos-

sible 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) dedicat-

ed CAN channel(s) with an associated database (DBC file). These

configured, logical CAN channels are then mapped to physical

CAN Controllers. Just as with the physical multiple ECU, the ECU’s

identity is determined by a function call at the start. ◆


3/18

GENyPC-Tool for Configuring Embedded Software Components

GENy is the convenient configuration tool for software compo-

nents 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 AdvantagesGENy is a developmental offshoot of the previous configuration

tools CANgen and DBKOMgen. The GENy architecture was com-

pletely redesigned based on experience with those two tools.

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 compo-

nent descriptions (Attributes) and data saving

> Open interfaces offer simple expandability

This makes GENy a scalable and fully generic configuration edi-

tor/generator that permits consistent configuration from a single

integration environment, even in complex heterogeneous

systems. Vector’s many years of experience in the area of ECU

development ensures optimal workflows between OEM and sup-

pliers 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.

GENy’s 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 exter-

nal XML file. The latter is essential for an OEM-specific appearance

of GENy’s GUI and guarantees that parameters will have functio-

nally relevant preset values.

Tool tips and the online help function help to save time and imme-

diately gives you the information needed about possible compo-

nent settings. Plausibility checks prevent invalid settings and the-

reby prevent errors.

GENy Program Window


3/19


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 debug-

ging 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

FunctionsGENy is the tool for configuring any software component. Config-

uration and parameter files can be generated to integrate them in

the application project.

Functional capabilities of GENy include the configuration of:

> Embedded software components for CAN, LIN, and FlexRay

> Flash Bootloaders

> AUTOSAR BSW (communication modules)

GENy reads the following input files:

> CAN database files (DBC)

> LIN files (LDF)

> FlexRay files (Fibex)

> CANdela database (CDD)

> AUTOSAR “ECU Configuration Description” (EDUC)

Application AreasThe GENy configuration tool is always used in conjunction with

other Vector software components for communication and diag-

nostics. GENy fulfills AUTOSAR Consortium requirements. ◆

GENy Navigation View

Training

As part of our CANbedded training program the configuration

tool GENy is also explained.

For more information on individual training events and sche-

dules please visit: www.vector-academy.com


TOOLS & COMPONENTS FOR OPEN NETWORKING


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 develop-

ment 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 implementa-

tion of the project.

To simplify connection of internal application data to the object

directory, there are exemplary entries already in the object directo-

ry. 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 struc-

tures that the user can adjust to his circumstances. The code sup-

ports variable mapping up to a granularity of 1 byte. All PDOs are

also configurable via the object directory. On receipt of a PDO a

callback is initiated in which the user can place additional han-

dling 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.

CANopen Source Code Embedded Software for CANopen

V2.1

2001

1-3

Modules of the CANopen Source Code



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 mecha-

nisms in a network. User-specific emergency messages can also be

generated.

The code supports an interface for non-volatile storage of parame-

ters. 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, em-

phasis can be placed on requiring very few resources and the sim-

plest 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 instruc-

tions 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 possi-

ble 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 control-

ler 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.

The CANopen Source Code by Vector is available for many popu-

lar microcontrollers. For current information, please visit our

website: www.vector.com/sourcecode



V1.1

201

1-03

Feature

CANopen Source Code1 CANopen Source Code1 Add-On Package Mini-Master LSS Slave LSS Master

Local object dictionary with mandatory entries: 1000, 1001, 1018

– – –

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

LSS Slave – – –

Feature Matrix CANopen Source Code

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

[s] – segmented [b] – block

3/28

Creating the EDS File with the Aid of CANeds

CANerator CANopen Generation and Configuration of Source Code

CANerator CANopen is a tool for managing source code configura-

tion settings and for creating and generating object directories

automatically.

Features and AdvantagesThe 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 micro-

controller. Vector’s CANopen Master and Slave Source Code there-

fore 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 direct-

ory. 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 AreasCANerator CANopen is intended for use together with CANopen

Master and Slave Source Code from Vector.

FunctionsCANerator 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 ConfiguratorCANerator 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 problem-

related 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/29


CANerator CANopen in ConfigurationMode: All #define Settings can be EditedClearly.

Generation of Object DirectoryThanks 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 addi-

tion, it is possible to define manufacturer-specific objects. The

objects are already provided with default values that can be modi-

fied 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 sym-

bolic specification of variable names, the CANerator also sup-

ports the specification of physical addresses in order to enable

direct access to hardware ports. After the object directory has

been created, the corresponding portions of the source code are

created automatically.

Electronic Data Sheet (EDS) Virtually as a byproduct, the Electronic Data Sheet is generated.

This can be processed further and tested with the functions of

CANeds.

Project ManagementCANerator 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 infor-

mation 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 ob-

jects with their attribute values as well as a list of all settings. ◆


3/30

XCP ProfessionalMeasuring and Calibrating via CAN, FlexRay and Ethernet

Application AreasAutomotive 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 (Asso-

ciation for Standardization of Automation and Measuring Systems),

a process in which Vector played a leading role. By clearly differen-

tiating the Protocol Layer and Transport Layer, XCP is able to sup-

port 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.

FunctionsXCP Professional contains all necessary functions for communica-

ting 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-com-

puted value is then written back to the ECU (STIM). Reading and

writing are performed synchronously in a predefined time interval

(Bypassing).


> 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)

XCP Professional is available forCAN, FlexRay and Ethernet


3/31


Resume ModeThe 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 eval-

uation.

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 TransferBlock Transfer lets you transfer large quantities of data. This func-

tionality is comparable to that of a transport protocol. The sender

segments the data, and the receiver re-assembles them in the cor-

rect sequence.

Transmission of Service Request PacketsService request packets let you transmit lines of text. They are

stored in program code, and when the program section is exe-

cuted 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 configura-

tion tool. Compiler switches may be used to deactivate unneeded

functions, and this reduces memory loading. When XCP transmis-

sion is started, the list of supported functions is communicated to

the XCP master via the XCP plug-and-play mechanism. ◆

Training


various training events and workshops for XCP in our class-

rooms or at your business site.


on the Internet go to: www.vector-academy.com

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 cali-

bration 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.


4/0

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 standardThe 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, porta-

bility and reusability for your application software.

As supplier of the world’s first certified OSEK/VDX-conformant

operating system osCAN, Vector has many years of experience in

implementation. A solution can be found for nearly any applica-

tion, since Vector can offer a selection of over 30 different micro-

controller platforms and universal tool-supported configurations

of the operating system.

Operating system conforming to the AUTOSAR standardVector’s MICROSAR OS is an AUTOSAR-conformant operating sys-

tem. 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 startVector 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 knowl-

edge for working with the software, conducted in Vector’s class-

rooms or on site. Vector assists the ECU development process with

on-site startups, code reviews and other development supporting

software tools.


4/1

OPERATING SYSTEMS

>> CONTENTS

osCAN 4/2High Resolution Timer 4/4TimingAnalyzer 4/6


4/2

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

osCAN is a preemptive real-time multitasking operating system

with properties optimized for use on microcontrollers. Vector’s

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 AreasDue 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.

FunctionsAs a fully preemptive multitasking operating system, osCAN offers

priority-driven task management and a wide variety of synchro-

nization 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 reso-

lutions higher than 1ms for the timers, without simultaneously

increasing interrupt load. Depending on the controller, resolu-

tions in the microseconds range are possible.


> 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


4/3

OPERATING SYSTEMS

Configuration An easy-to-use graphic configuration tool lets you define all oper-

ating 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 pro-

cesses. Next, the sub-applications are integrate into a total appli-

cation. This enables short development times and spatially sepa-

rate developments.

Properties:

> Easy to operate graphic user interface

> Automatic checking for completeness and consistency

> Convenient system scaling

> Component management

> ORTI support

Training


training events and workshops for osCAN in our classrooms

as well as at the business sites of our customers.



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: 1–10 kB ROM, depending on platform and

configuration

Availability

The real-time operating system osCAN from Vector is availa-

ble for many commonly used 8, 16 and 32 bit microcontrol-

lers. 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.

Related Vector products:

> CANoe osCAN Library

> TimingAnalyzer

> High Resolution Timer

Complete solution from Vector

Vector provides you a completely tuned solution for devel-

oping ECUs. Along with the operating system, you get proto-

cols and drivers for CAN, LIN or FlexRay. For more detailed

information, please refer to the relevant datasheets.

Supporting ToolsThe 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 Aware-

ness). osCAN supports the ORTI interface required for this.

Some UML and SDL modeling tools give you the option of configu-

ring models for use with an OSEK/VDX operating system. This is

possible, for example, with:

> MATLAB/Simulink from Mathworks

> TargetLink from dSPACE

◆


4/4

High Resolution TimerImprove 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 hard-

ware timers. When a counter reaches a preset alarm value, a pre-

defined 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 enhan-

ced 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 oper-

ating 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 con-

trolled by defining a minimum interval between timer interrupts.

This reduces interrupt load, especially when several alarms with

similar intervals expire almost simultaneously.

Application areasThe High Resolution Timer is designed for applications

requiring high-precision timers but in which additional interrupt

loads are unacceptable.

Hardware requirementsThe 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 com-

pare value (compare-match). The clock speed at which the hard-

ware 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 microcon-

troller. ◆

Alarms and Tasks


4/5

OPERATING SYSTEMS


4/6

TimingAnalyzerSchedulability 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 oper-

ating 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 AdvantagesThe TimingAnalyzer simulates scheduling tables and computes

schedulability. The analysis is performed for each task and ISR

with the information: priority, period, execution time and dead-

line. Various algorithms from scheduling theory may be selected.

In the default setting, the best algorithm is selected for a given

data record.

By using the TimingAnalyzer you can avoid the difficult and time-

consuming work involved in determining worst case timing situa-

tions, 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.

FunctionsIn 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.

Analysis example in the TimingAnalyzer

Special functions

> Schedulability analysis

> Graphic simulation of schedules

> Import and display of emulator traces


4/7

OPERATING SYSTEMS

Data ImportBesides manual data input, the data may also be read-in from the

configuration file of the operating system. This simplifies hand-

ling, since data input and calling of the TimingAnalyzer are per-

formed directly in the configuration tool.

Application AreasThe TimingAnalyzer is an efficient tool for all development

departments that use real-time operating systems. Special atten-

tion was given to supporting OSEK/VDX and AUTOSAR real-time

operating systems and their applications.

Scope of Delivery> Graphic analysis tool for Windows NT/2000/XP/

Vista/Windows 7

> Documentation in electronic form

> Sample files ◆

Availability

The TimingAnalyzer is available in combination with the

OSEK/VDX-conformant operating system osCAN as well as the

AUTOSAR-conformant MICROSAR OS.


EMBEDDED SOFTWARE


V2.2

201

1-02

Controller Compiler

Altera

Excalibur Green Hills

NIOS II GNU, TaskingVX

ARM

ARM7-TDMI Green Hills

Atmel

AT91 Green Hills

AVR32 IAR

Freescale

68HC08 Cosmic

68HC12, S12 Cosmic, IAR, Metrowerks

MAC71xx Green Hills

Mcore DIABDATA Wind River

MPC55x, MPC56x DIABDATA Wind River, Green Hills, Metrowerks

MPC55xx, MPC56xx DIABDATA Wind River, Green Hills, Metrowerks

S12X Cosmic, Metrowerks

Fujitsu

16FX Fujitsu

16LX Fujitsu

FR30, FR50, FR60 Fujitsu

MB86 Green Hills

Infineon

C167 Keil, Tasking, TaskingVX

Tricore Tasking

XC16x Keil, Tasking, TaskingVX

XC2000 TaskingVX

Intel

PXA27x Green Hills

Microchip

dsPIC30 Microchip

PIC18 Microchip

PIC24 Microchip

Controller Compiler

NXP

LPC2XXX Green Hills

SAF7780 ARM, Green Hills

SJA20xx Green Hills

OKI

ML67 Green Hills, IAR

ML665S OKI


78kO IAR

H8 tiny Renesas

H8S Renesas

H8SX Renesas

M16C Renesas, IAR, Tasking

M32C Renesas, IAR

M32R Renesas, GAIO

R32C Renesas, IAR

R8C IAR

SH2 IAR, Renesas, GAIO

V850 Green Hills, IAR

STmicroelectronics

ST10 Keil, Tasking

STR9 GNU

Texas Instruments

MSP 430 IAR

TMS 320 Texas Instruments

TMS 470 Texas Instruments, Green Hills

TMS 570 Texas Instruments

Toshiba

TLCS-900 Toshiba

TX19, TX39, TX49 Green Hills

TX19A Toshiba

Vector

CANoe osCAN Emulation Microsoft VisualC

Wide Availability of osCAN Supported Microcontrollers and Compilers

EMBEDDED SOFTWARE


5/0

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 BootloaderThe 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 with-

out needing to remove the ECU. This results in the following capa-

bilities:

> 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/CCPThe 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 componentECUs 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 reprogram-

med with ECU software, even if it does not originate from the

automotive OEM.

Since the Request/Response method provides inadequate protec-

tion 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 compressionAutomotive electronics is continuously becoming more complex,

and so it requires more extensive software. Suitable data com-

pression methods can be used to transport the increasing amo-

unts of data more quickly on data buses; they reduce transmission

times drastically. Vector offers optimized solutions for the Flash

Bootloader and flash tools.

Flash toolsDifferent data and diagnostic formats are used by different auto-

motive 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 for-

mats, Vector offers authoring and flash tools for specific use

cases in its CANdelaFlash and CANditoFlash products.

Flashing CANopen ECUsVector 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/1

FLASHING

>> CONTENTS

Flash Bootloader 5/2Option “Security (Crypto)” 5/4Data Compression Option 5/5

EEPROM Emulations Modul (EepM) 5/6Flashen with CCP and XCP 5/8CANdelaFlash 5/10vFlash 5/12


5/2

Flash BootloaderECU reprogramming via CAN, LIN, FlexRay, MOST and Ethernet

Application AreasThe Vector Flash Bootloader is a universal and compact solution for

quick, efficient and reliable reprogramming of ECUs during devel-

opment, 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 multi-

processor 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.

FunctionsThe flash download is executed according to OEM requirements

using either the KWP2000 or UDS diagnostic protocol. The Boot-

loader 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 ECU’s RAM mem-

ory if needed. Then it erases the old ECU software and reprograms

the flash memory with the new data it receives over the bus sys-

tem. If the flash procedure is interrupted, it can be repeated at

any time.


> 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

Flashing over CAN, LIN, FlexRay, MOST and Ethernet


5/3

FLASHING

> Bus-specific communication stack

The Bootloader communicates with the flash tool via the bus-

specific communication stack. For the CAN bus, a specially opti-

mized 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.

ConfigurationYou configure the Bootloader with the GENy configuration tool,

adapting it to the specific requirements of your application. Fur-

ther 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 user-

friendly 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.

Configuring flash blocks with GENy


The Flash Bootloader is available for many commonly used

microcontrollers and in OEM-specific variants. For more

information go to:

www.vector.com/fvd/ or contact us at:

E-mail: [email protected]: +49 711 80670-400


5/4

Flash Bootloader: Option “Security (Crypto)”Data encryption, validation and authentication during flash programming

The Vector Flash Bootloader lets you program ECUs over a bus sys-

tem 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 crypto-

graphic routines with standardized interfaces in scalable security

classes for this purpose.

Application AreasOption Security for the Vector Flash Bootloader lets you efficient-

ly prevent flashing and unauthorized execution of protected soft-

ware in the ECU. The option contains secure, qualitatively high-

end cryptographic functions from the company Cryptovision.

Upon request, you can also obtain extended Seed/Key methods

for ECU access protection.

FunctionsOption Security for the Vector Flash Bootloader meets the require-

ments 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 meth-

od 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.

◆


> Protection against unauthorized ECU access

> Secure downloads

> Efficient program execution monitoring by signature

checking

Generating,transmittingand verifyinga digitalsignature

Scope of Delivery

> Configurable C source code; integrated in the Bootloader

> Tool HexView for efficient computation of the signatures

> Documentation


5/5

FLASHING

With the Vector Flash Bootloader you can program ECUs via a bus

system without having to remove the ECU. Compression and sub-

sequent decompression of the flash data is recommended to

reduce download time.

Application AreasSome automotive OEMs specify the use of data compression in

their flash procedures to accelerate the flash procedure at a con-

stant 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). Compres-

sion also offers many benefits when short cycle times are speci-

fied, as in end-of-line programming.

The data compression option of the Vector Flash Bootloader lets

you efficiently compress all of your flash data. It utilizes an opti-

mized LZ77 method and is especially well suited for use in auto-

motive ECUs. Implementation in the Bootloader’s decompression

module is very efficient in terms of execution time and memory. It

is available on all microcontrollers for which a Bootloader is avail-

able.

FunctionsThe compression method used in this module enables a compres-

sion rate of 40–60%, 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 Bootloader’s OEM Download

Manager calls the decompression function, and then it programs

the decompressed data in flash memory via the Multiple Memory

Manager.

◆

Flash Bootloader: Data Compression OptionFast Flash Programming


> Reduced download times in flashing

> Efficient decompression module for the ECU

> Offers support in data compression

> Bus system independent

Compression and decompression of flash data

Scope of Delivery

> Configurable C source code; integrated in Bootloader

> Tool HexView for compression of the flash data

> Documentation


5/6

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.

Application AreasFlash memory cannot be erased or written in the same way as con-

ventional 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.

FunctionsThe Vector EEPROM Emulation Module (EepM) manages predefined

flash areas by taking all hardware-specific constraints into con-

sideration. Reading and writing of changeable nonvolatile data

via the EepM is fully transparent to the application. It is easy to

access the stored data by identifiers that are predefined or flexi-

bly defined at runtime.

Differences between EEPROMs and Flash MemoryFlash 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 DataEssentially, 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 reli-

able 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 ofthe EepM


> 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

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/7

FLASHING

Reliable AccessIn 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 simultane-

ously using predefined context pointers. If a Vector Flash Boot-

loader is integrated into the ECU, the context pointers make it

possible to use the EEPROM Emulation module from the Flash

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 consulta-

tion in system design.

ConfigurationThe 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 ◆

Contact and AvailabilityVector offers EEPROM Emulation Modules for a number ofhardware platforms with different internal or external flashmemories. You will find additional information on the Inter-net at: http://www.vector.com/vi_eepm_availability_enor upon request E-mail: [email protected]: +49 711 80670 400.

Resource optimizationby use of EepM from theVector Flash Bootloader


5/8

Flashing with CCP and XCPUsing the CCP/XCP protocol for flash programming

The CAN Calibration Protocol (CCP) – and its successor, the Univer-

sal 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 areasFlashing via CCP and XCP is primarily used to update calibration

data and parameter data in the calibration process. After a chan-

ge has been made to the data in the calibration tool, the new data

is written to the ECU’s flash memory via the bus system. First, a

flash kernel (see illustration, left) is transferred to the ECU, is

written into RAM and is started by the application. Besides con-

taining the CCP and XCP protocols for communication, it also con-

tains 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 especial-

ly space-saving solution.

Less widely used but technically feasible is the option of replacing

the entire application by flashing via CCP and XCP.

Failsafe reprogrammingUnfortunately, 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 perma-

nently 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 supportThe flash download is executed by CANape. ◆

Advantages

> Calibration and reprogramming with the same software

component

> Use CANape as a flash tool

> Reset-safe solutions are available

Flashing via an XCP bootloaderFlashing via XCP using a flash kernel


5/9

FLASHING


EMBEDDED SOFTWARE


V2.1

201

0-10

Controller Compiler Available for [1]

AnalogDevices

BlackFin VisualDSP CAN

Atmel

AVR IAR CAN, LIN

AVR32 IAR CAN

Freescale

DSP56F83xx Metrowerks CAN

HC08, MCS08 Cosmic, Metrowerks (Hiware) CAN, LIN

HC12, Star12, Star12x, MCS12xE

Cosmic, IAR, Metro-werks (Hiware) CAN

i.MX25 GNU CAN

MAC71xx, MAC72xx ARM, IAR CAN

MPC 55x, 56x, 5200 DIABDATA Wind River, Metrowerks CAN

MPC 55xx, 56xx DIABDATA Wind River CAN, FlexRay

Fujitsu

16FX Fujitsu CAN

16LX Fujitsu CAN

FR60 Fujitsu CAN

Jade GNU CAN

Infineon

C16x (external AMD-Flash) Tasking CAN

Tricore GNU, Tasking CAN, FlexRay

XC16x Keil, Tasking CAN

XC2000 Tasking CAN

Microchip

dsPIC24 Microchip C30 CAN

dsPIC33 Microchip C30 CAN

PIC18 Microchip, Hi-Tech CAN, LIN

National

CR16 IAR CAN

Controller Compiler Available for [1]


78k0 IAR CAN, LIN

78K0R IAR CAN

H8S Renesas CAN

M16C Renesas, IAR CAN

M32C Renesas, IAR CAN

M32R Renesas CAN

R32C IAR CAN

R8C Renesas, IAR CAN

SH2 Renesas CAN

V85x Renesas (NEC), Green Hills, IAR CAN, LIN, FlexRay

STmicroelectronics

ST9 GNU CAN

ST10 Tasking CAN

STM8a Cosmic CAN

Texas Instruments

TI OMAP 59xx Texas Instruments CAN

TMS320 Texas Instruments CAN

TMS470 Texas Instruments, ARM CAN

TMS570 Texas Instruments, ARM CAN, FlexRay

Toshiba

TLCS900 Toshiba CAN

TX19 Green Hills CAN

TX49 Green Hills CAN

[1] Please contact Vector ([email protected]) 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.

Wide Availability of Flash Bootloader and EepM Supported Microcontrollers and Compilers

EMBEDDED SOFTWARE


5/10

Application AreasToday the development process for an ECU is very complex. While

previously just a few ECUs were “flashable” in the vehicle, in futu-

re all ECUs will have a flash capability.

The large number of ECUs that are networked together in the vehi-

cle, 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 imple-

mented in both ECU development at a supplier and in test vehicle

or preproduction development at the vehicle OEM.

FunctionsCANdelaFlash supports the import and export to the standardized

ODX format completely. ODX Flash Containers can thereby be pre-

pared 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 particu-

lar it supports the development process with other Vector pro-

ducts 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)

Process-assured generation of ODX Flash Container

CANdelaFlash 2.0Management 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

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


5/11

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 DataThe management and the acquisition of flash data are done com-

fortably 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 repro-

gramming). 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 ◆

Flash data managementwith CANdela Flash:Structure of the CANdelaFlash data


5/12

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

vFlash is a very easy-to-use tool for programming one or more

ECUs. Because of its flexible approach, it can support the differ-

ent flash specifications of a wide variety of automotive OEMs

without requiring modifications by the end user.

Application AreasvFlash 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 indi-

vidually 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 program-

ming by the push of a button. In remote control mode, vFlash can

be executed from the command line or controlled via a C pro-

gramming 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 tool’s very fast

transmission rate significantly reduces flash times in the case of

large amounts of data.

FunctionsvFlash utilizes flash projects to save and exchange the configura-

tion to program individual ECUs. Flash projects contain all rele-

vant 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 configura-

tions, the flash projects may be exchanged in the Pack&Go for-

mat. In this case, all relevant settings together with the data files

are packed in an archive file.


> 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

Flash process with vFlash


5/13

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 auto-

motive 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 them-

selves as necessary. All that is needed for this is Microsoft Visual

Studio for C#; the Express Edition can be obtained from Microsoft

free-of-charge.

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

CANcaseXL)

System Requirements

Windows XP (32-bit) Windows Vista (32 bit)Windows 7 (32/64 bit)

Processor PC with min. 1.6 GHz PC with min. 1.6 GHz

RAM 1 GB 2 GB

◆

vFlash User Interface

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 differ-

ent automotive OEMs.

Please contact us at: www.vector.com/contact


6/0

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.

ModularityTrainings 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.

Customer-Specific TrainingsAdditionally, we offer customized training courses, where we com-

bine or expand the contents according to your needs. If desired we

can also conduct all training courses at your company site. We would

be glad to provide you with a quotation based on your specific needs.

Please contact our training consultants:

Vector Informatik: [email protected]

Vector Consulting Services: [email protected]

Vector CANtech: [email protected]

Vector Scandinavia: [email protected]

Vector France: [email protected]

Vector Japan: [email protected]

Vector Great Britain: [email protected]

Vector Korea: [email protected]

The Training TeamOur 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 cur-

rent trends and developments.

PremisesWe conduct our trainings in generously appointed and modern class-

rooms, 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.

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.


TRAINING

6/1


6/8

Germany


DIRECTIONS TO VECTOR

6/9

USA and Great BritainSubsidiaries: Vector CANtech Inc., Vector GB Limited


6/10

France and SwedenSubsidiaries: Vector France S.A.S., VecScan AB



6/11

Japan and KoreaSubsidiaries: Vector Japan Co., Ltd., Vector Korea IT Inc.


6/12

India and ChinaSubsidiaries: Vector Informatik India Pvt. Ltd., Vector Informatik China



6/13


Your contact

www.vector.com Get Price Quote

Germany and all countries not named below

Vector Informatik GmbHVector 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 Camélinat 92240 Malakoff FRANCE Tel.: +33 1 4231 4000 Fax: +33 1 4231 4009

Sweden, Denmark, Norway, Finland, Iceland

VecScan AB Theres Svenssons Gata 9 41755 Göteborg SWEDEN Tel.: +46 31 764 7600 Fax: +46 31 764 7619

United Kingdom & Ireland

Vector GB Limited Rhodium, Central BoulevardBlythe Valley ParkSolihull, BirminghamWest Midlands, B90 8ASUNITED KINGDoM Tel.: +44 121 50681-50Fax: +44 121 50681-69

China

Vector Informatik GmbH Shanghai Representative Office Unit 1701, Sunyoung CenterNo. 398 Jiangsu RoadChangning DistrictShanghai 200050P.R. CHINATel.: +86 21 6432 53530Fax: +86 21 6432 5308

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-guSeoul 152-848REPUBLIC oF KoREA Tel.: +82 2 8070 600Fax: +82 2 8070 601

India

Vector Informatik India Prv. Ltd.4/1/1/1, 3rd floor, Sutar IconSus RoadPashanPune 411021INDIATel.: +91 20 2587 2023Fax: +91 20 2587 2025

F F

Catalog ECU Software en

Documents

Transcript of Catalog ECU Software en