Escolar Documentos
Profissional Documentos
Cultura Documentos
1/1
1/1
This catalog provides you an overview of Vector products and Services of the application area ECU Software:
ECU Software
Embedded software like real time operating systems (RTOS) ECUs. Basic software for AUTOSAR. Development services for soft-
and communication modules for e. g. CAN, LIN, FlexRay and Ether- ware components.
net. Software for memory management and for reprogramming of
Please request other catalogs in the application areas Development of Distributed Systems, ECU Testing, ECU Calibration,
Process Management, Vehicle Diagnostics, or request further information about the Vector Solutions for various tasks in automotive
networking: Internet: www.vector.com/catalog/ • E-mail: catalog@vector.com
1/2 The following table shows an overview of network protocols and bus systems, which can be used for electronic networking of distributed sys-
tems. The 4th column shows the Vector products that are applicable to the appropriate bus system respectively protocol or exchange format.
Protocol resp.
Description Application Area Appropriate Vector Product Page
Exchange Format
J1939/ J1939 is a communication protocol based on CAN for real- Commercial vehicle CANoe.J1939 ●
ISO11783 time data exchange between electronic control units engineering, CANalyzer.J1939 ●
(ECUs) in the area of commercial vehicles. railway engineering, CANoe.ISO11783 ●
It describes the information exchanged between the ECUs agricultural CANbedded J1939 3/6
in such a system. ISO11783 is a further development for engineering CANape ●
agricultural engineering.
NMEA 2000 NMEA 2000® is a communication protocol based on J1939 Marine engineering CANoe.NMEA2000 ●
from the National Marine Electronics Association (NMEA) CANalyzer.NMEA2000 ●
for the realtime data exchange between electronic control CANbedded J1939 3/6
1/3
units in maritime electronics.
J1587/ SAE J1708 defines a serial, bidirectional network for use in Commercial vehicles CANoe/CANalyzer.J1587 ●
J1708 the commercial vehicle industry. The SAE J1587 Standard engineering
regulates communication and standardized data exchange
between different ECU based on SAE J1708 networks.
CANopen The CANopen profile family specifies standardized commu- Automation CANoe.CANopen ●
nication mechanisms and device functionalities. engineering, CANalyzer.CANopen ●
CANopen is maintained by “CAN in Automation” (CiA), and CAN embedded CANerator CANopen 3/28
can be implemented free of license. ProCANopen ●
CANeds ●
CANopen Master Source Code 3/22
CANopen Slave Source Code 3/26
J2534 The SAE J2534 standard defines the re-programming of Vehicle ECUs, PassThru XL Library ●
ECUs via a PassThru interface. The purpose of this standard Diagnostics, PassThru
is to provide a unified communication capability via a re-programming
standardized PC interface basically intended for flashing
but also for diagnostics and other purposes.
Ethernet/IP Ethernet-based networks and the protocols built upon Car2x, vehicles engi- CANoe.IP ●
them are used in IT networks for decades. In the meantime neering, automation CANalyzer.IP ●
they continue to grow in importance in the embedded engineering, factory MICROSAR IP 2/20
environment. The main focus is on transmission of periodic automation
signals and real-time capability.
XCP/CCP XCP is an improved and generalized version of the CAN Cali- Automotive engineer- CANape ●
bration Protocol V2.1. (CCP). XCP can be used also in non- ing, development of XCP software component 3/30
CAN networks (e.g. FlexRay, SPI, SCI). The main benefit of electronic control CANoe Option XCP ●
XCP is the independence concerning the transport layer. units, measurement GL1000, GL3000/4000/4200 ●
and calibration
KWP2000/ Keyword Protocol 2000 (KWP2000; ISO 14230) and “Unified Diagnostics of vehicle CANape ●
UDS Diagnostic Services” (UDS; ISO 14229) are standardized electronic control CANdelaStudio ●
diagnostic protocols for electronic control units. units, measurement CANdesc 3/14
The physical access to the ECU is possible via a serial con- and calibration CANoe ●
nection (“K-line” KWP-on-K-Line) or via CAN (KWP-on-CAN, CANdito ●
UDS-on-CAN). CANoe.DiVa ●
CANditoFlash 5/12
Indigo ●
ODX The ODX format (Open Diagnostic Data Exchange) is based Diagnostics of vehicle CANdelaStudio ●
on the ASAM-MCD-2D-Basic working draft. Manufacturers electronic control CANdelaFlash 5/10
of vehicles, electronic control units, and testers can write units CANdito ●
and exchange electronic control unit data in the uniform CANape ●
ODX format, which covers all manufacturers. CANoe ●
CANditoFlash 5/12
Indigo ●
CANoe.DiVa ●
RP1210 The RP1210 specification defines an open interface (API) Commercial vehicles RP1210 API ●
between Windows-based applications and in-vehicle com- engineering, engine
munication networks. This interface offers functionality control
for bus systems – such as CAN and J1708 – as well as for
higher layer protocols such as J1939 and J1587.
◆
1/4 The following matrix gives you an overview which Vector products support you in your specific application area.
++ = main application area; + = additional application area
Development
ECU Software Process
Vector Product of Distributed ECU Testing Diagnostics ECU Calibration Page
Components Management
Systems
ASAP2 Editor ++ ●
ASAP2 Lib ++ ●
ASAP2 Tool-Set ++ ●
AUTOSAR
Basis 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 + ++ ●
CANditoFlash + ++ 5/12
CANeds ++ ●
CANerator
++ 3/28
CANopen
CANextender ++ ●
CANgraph + ++ ●
CANister ++ ●
CANlog 3 und 4 ++ ●
CANoe + ++ + ●
CANoe.DiVa + ++ ●
CANopen Master
++ 3/22
Source Code
CANopen Slave
++ 3/26
Source Code
APPLICATION AREAS OF THE VECTOR PRODUCTS
Development Steuergeräte-
Steuergeräte- ECU Software Prozess-
Process
Vector Product of Distributed ECU Testing Diagnostics ECU Calibration Software- Seite
Page
Kalibrierung Components management
Management
Systems Komponenten
CANscope ++ ●
CANstressD/DR ++ ●
COMPASS ++ ●
DaVinci
Component Tester ++ 2/44
Configurator Pro ++ 2/48 1/5
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
OEMs and brands from A-Z (1) If your OEM is not included in the list, please contact your Vector 1/7
> Alfa Romeo, Aston Martin, Audi Sales representative. Vector can develop basic software for other
> Bentley, BMW, Brilliance, Bugatti, Buick automotive OEMs and brands upon request. An independent vari-
> Cadillac, Chevrolet, Chrysler, Citroen, Claas ant of the basic software is available for non-OEM-specific com-
> DAF, Dongfeng, Daimler, Daimler Commercial Vehicles munication. ◆
> FAW, FAW-VW, Ferrari, Fiat, Fisker, Ford
> GAC, GMC, GM-Daewoo
> Holden, Honda, Hummer, Hyundai
> Jaguar
> Kia
> Lamborghini, Lancia, Land Rover, Lincoln
> MAN Commercial Vehicles, Maybach, Mazda, Mercedes, Mercury,
Mini, Mitsubishi
> 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/8 project team. This gives you maximum workload relief and ideal
Overview of Your Advantages transparency.
> Customized support
> Quick implementation of your application ECU Software
> Sustained build-up of your know-how In the development of ECU software, we can offer you the follow-
ing support:
In each phase of your development, you can benefit from our
competence. We support you with our services on your projects. > Consulting and conceptualization
Beginning with the goals you set, we work together with you to > Introduction of new operating systems
create a customized action plan and package. In the process, you > Optimization of existing software architectures
will benefit from our expertise. > Interfacing of basic software to the application in
multiprocessor ECUs
Application Areas > Design of “mixed SIL” systems
You get support from Vector in: > Support in migration of ECUs to FlexRay and to AUTOSAR
> Developing the ECU software
> Developing safety-relevant systems > Software development for:
> Designing in-vehicle networking > Customer-specific components
> An entire ECU
In this context, Vector supports you with: > Systems with safety-relevant content per ISO DIS 26262
> Individual concept development and consulting on technology
> Creating specifications > Integration and testing
> Assuming responsibility for an entire project > Support, on-site or Hotline, for startup and use of Vector
standard components
We support you from prototype development to production devel- > Integration and configuration of embedded standard
opment based on a process that is optimally aligned to your components in your projects
needs. Projects are implemented in close coordination with your > Customer-specific adaptations and extensions to standard
Vector software
Contact
We would be glad to support you on your projects. Please feel
free to contact us at: www.vector.com/contact
> OEM or Tier-1 specific integration reviews for standard Vector Besides creating defined work products, one of our primary goals 1/9
components is sustained transfer of the underlying know-how. Multi-day work-
shops and close cooperation in the services framework guarantee
Model-based software development can also be performed. intensive knowledge transfer to your professional teams.
◆
In-Vehicle Networking
In the development of in-vehicle networking, you get the follow-
ing support from Vector:
> Consulting and conceptualization
> Distribution of vehicle functions
> Creation and extension of network architectures
> Optimization of system layout
> Definition of routing concepts for gateways
1/10 Vector supports suppliers of control modules in their development > NM user data access during communication-related events
efforts right from the start. The support is based on the Standard > BusOff implementation
Software Integration Package. This service offers you professional > Specific hardware checks
support in integrating standard software into your project. > Implement communication-related error memory entries (DTC’s
for BusOff, message timeouts)
Overview of Advantages > Error memory handler access with regard to several system
> Time savings as a result of standard features integrated by states like overvoltage/undervoltage, Sleep Mode, BusOff and
Vector clamp state change
> Lets you focus on your application > Integration of transport protocol, diagnostics and DTC Handler
> ECU behavior of first submitted samples is specification- > Integration of proprietary protocols/layers
conformant on the communication bus > EEPROM RAM emulation (HIS-conformant) for verifying
flashability
> Flashing with the OEM-defined tool chain
Application Areas
The “Standard Software Integration Package” from Vector is used
on projects for several OEMs.
The initial focus here is on single-channel CAN controllers.
Overview of architecture
ECU SOFTWARE
Special Functions
We would be glad to handle development and integration
tasks for other contents of your project, such as:
> Project-specific components or
> A functional ECU application.
Scope of Delivery
> Delivery of integrated standard software in complete project
tree, with make support and runtime environment
> Documentation
> Test report
> Local startup
> Hotline/support
The core idea of AUTOSAR is to master the growing complexity of DaVinci – The AUTOSAR Tools from Vector
software in modern vehicles by standardization. The development > DaVinci Developer is the optimal tool for graphic-based defini-
partnership founded by leading automotive OEMs and suppliers tion of AUTOSAR software components and for configuration
set the goal of defining an open reference architecture for ECU and generation of the MICROSAR RTE.
software. Many advantages are realized by standardization and > DaVinci Component Tester lets you conveniently test AUTOSAR
2/0 using clearly specified interfaces between the basic software software components on a PC.
modules to the functional software : e.g. re-usability of the same > DaVinci Configurator Pro is used to create a consistent config-
software for different microcontrollers and functions with a uration of the MICROSAR basic software from Vector and of
simultaneous increase in quality. basic software from third-party suppliers. The proven GENy tool
is used for the communication modules.
Vector, your Trusted Partner for AUTOSAR Projects > DaVinci Configurator Kit optimally supports you in integrating
As one of the first premium members of the AUTOSAR Consortium, modules you have developed (e.g. complex device drivers) in
Vector has been actively involved in the development of new tech- DaVinci Configurator Pro.
nology for a long time. This active participation was recognized by
the AUTOSAR Consortium in awarding Vector the first AUTOSAR MICROSAR – The AUTOSAR Basic Software Modules from Vector
Premium Member Award in 2007. Vector‘s experience with With MICROSAR, Vector offers AUTOSAR-conformant software
AUTOSAR is also reflected in AUTOSAR tools and the basic soft- modules for efficient development of production-mature ECUs.
ware, which is already being used in numerous production pro- They are based on AUTOSAR Release 3.x and cover all aspects of
jects. the AUTOSAR standard.
Practice-based extensions and features implemented in anticipa-
Overview of the Vector AUTOSAR Solution tion of AUTOSAR Release 4.0 complete this solution, e.g. with sup-
Vector supports you in all development phases of projects with port of Ethernet, encrypted communication, FlexRay IsoTp, XCP
tailor-made AUTOSAR solutions for design, development and and J1939.
implementation: 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 11.05.2010 11:32 Uhr Seite 2/1
AUTOSAR
>> CONTENTS
AUTOSAR Prototype Bundle 2/2 MICROSAR IO 2/36
MICROSAR 2/6 MICROSAR RTE 2/38
MICROSAR OS 2/10 Identity Manager for AUTOSAR 2/40
MICROSAR COM 2/12 DaVinci Developer 2/42
MICROSAR CAN 2/14 DaVinci Component Tester 2/44
MICROSAR FR 2/16 DaVinci Configurator Pro 2/48
MICROSAR LIN 2/18 DaVinci Configurator Kit 2/50
MICROSAR IP 2/20 AUTOSAR Services 2/52
MICROSAR MOST 2/22
MICROSAR MEM 2/24
MICROSAR SYS 2/26
MICROSAR DIAG 2/28
MICROSAR CAL 2/32
MICROSAR EXT 2/34
AUTOSAR Prototype Bundle
The complete bundle for developing prototype ECUs conforming to the AUTOSAR standard
Additional Tools
AUTOSAR
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.
For more information on individual training events and dates
on the Internet please visit: www.vector-academy.com
GENy tool offers special support in configuring the communica- > Fully compatible with OSEK OS
tion basic software. > Supports Schedule Tables
All tools perform consistency checks, making it easier for you to
design complex AUTOSAR applications. MICROSAR SYS
Also included are tools used to generate input data for DaVinci Contains the AUTOSAR basic software modules
Developer and DaVinci Configurator Pro: You can create network > Communication Manager (COMM) 2/3
communication descriptions for CAN, LIN or FlexRay networks > Cyclic Redundancy Check Routines (CRC)
with Network Designer. It supports you with functions for defin- > ECU Manager (ECUM)
ing signals, distributing signals to messages and importing/ > Development Error Tracer (DET)
exporting network data via standard formats. > Watchdog Manager (WDGM)
The CANdelaStudio tool is used to define diagnostic data for your > Watchdog Interface (WDGIF)
networks and ECUs. You can export this data via standard > Scheduler Module (SCHM)
formats, and use the data in automatic configuration of the
MICROSAR diagnostic basic software. MICROSAR DIAG
Contains the AUTOSAR basic software modules
The included MICROSAR basic software modules efficiently and > Diagnostic Event Manager (DEM)
flexibly implement all basic functions and numerous other func- > Diagnostic Communication Manager (DCM)
tions of AUTOSAR Release 3.x. The modules are bundled in func- > Function Inhibition Manager (FIM)
tionally interrelated MICROSAR products:
MICROSAR MEM
MICROSAR RTE Contains the AUTOSAR basic software modules
> Contains the AUTOSAR RTE (Runtime Environment) > NVRAM Manager (NVM)
> Memory Abstraction Interface (MEMIF)
MICROSAR OS > EEPROM Abstraction (EA)
Contains the AUTOSAR basic software module Operating System (OS) > Flash EEPROM Emulation (FEE)
> Implementation of “Scalability Class” SC1 (SC2-SC4 available as
option if supported by processor)
Designing software components with DaVinci Developer Configuration of the Basic Software with DaVinci Configurator Pro
MICROSAR CAN MICROSAR COM
Contains the AUTOSAR basic software modules Contains the AUTOSAR basic software modules
> CAN Interface (CANIF) > Communication (COM)
> CAN Transport Protocol (CANTP) > Network Management Interface (NM)
> CAN Network Management (CANNM) > PDU Router (PDUR)
2/4 > CAN State Manager (CANSM) > I-PDU Multiplexer (IPDUM) available as option
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®.
Further Options
The AUTOSAR Prototype Bundles CAN, LIN and FlexRay may be
used with one another in any combination.
MICROSAR is the AUTOSAR solution for your ECU software. You can configure all necessary MICROSAR BSW modules based on
MICROSAR consists of the MICROSAR RTE and MICROSAR basic your project’s requirements, and after generation you can inte-
software modules (BSW), which cover all aspects of the AUTOSAR grate them with the functional software. This produces a com-
standard. Each AUTOSAR BSW module is assigned to a MICROSAR plete set of ECU software. If the functional software consists of
package. For detailed descriptions of individual packages and the AUTOSAR-conformant SWCs, you will need a run-time environment
MICROSAR RTE, please refer to the separate datasheets. Vector (RTE). The MICROSAR RTE handles communication between the
combines the BSW modules needed in individual “software inte- SWCs and their access to data and services from the BSW modules.
gration packages”. Along with managing the entire flow of information, the
MICROSAR RTE also assures consistency in the exchange of infor-
Application Areas mation.
The BSW modules of the MICROSAR packages assure basic func-
tionality of the ECU. They contain the implementations of Properties
AUTOSAR standard services you will need for your functional soft- Development of the MICROSAR basic software modules is founded
ware. You are able to develop your functional software platform on the Vector development process for standard modules, which is
based on SPICE Level 3. All MICROSAR packages offer the follow- AUTOSAR Release 3.x and Extensions
ing features: All MICROSAR basic software modules fundamentally conform to
> Efficient memory utilization and short execution times AUTOSAR Release 3.x. In addition, it is possible to integrate MCAL
> Available for production use drivers of the previous Release 2.1.
> Conformant to AUTOSAR Release 3.x Modules from MICROSAR IP, MICROSAR J1939 and XCP already
> Assistants and timely checks support you in achieving contain important functionality from Release 4.0. Moreover, the 2/7
consistent configuration of your basic software MICROSAR MOST package lets you connect any AUTOSAR ECU to a
> Scalable, adaptable to your specific application MOST ring. All of these extensions are compatible with the rest of
> Optimally integrated into your development process the MICROSAR basic software modules of Release 3.x.
> User-selectable configuration point (pre-compile, link-time
or post-build) Consistent and Simple Configuration
> Communication stack is versatile in its use With AUTOSAR, the work of manually developing or adapting the
> Supports multiple ECUs basic functionality of ECU software is replaced by configuration of
> Optional delivery as source code the BSW modules. The intuitive, user-friendly and well coordi-
nated AUTOSAR tools from Vector (DaVinci) support the user in
Production Use this process. The DaVinci tools require an “ECU Extract of System
The MICROSAR BSW modules are already being used in production Description” file as input. It is also possible to produce a configu-
projects. MICROSAR lets you benefit from Vector’s many years of ration based on commonly used network description files (DBC,
experience in implementing embedded standard software. Before FIBEX, LDF, etc.).
delivery, all MICROSAR Software modules undergo systematic Early in the configuration process, all DaVinci tools check the
integration tests for the specific conditions of your application validity of individual parameters, complex parameter groups and
(hardware platform, compiler, processor device, OEM, with/with- their interrelationships. In case of invalid configurations, the
out RTE, etc.). Upon request, these tests may be extended to tools make recommendations for corrections, if possible. This
cover software modules from third-party producers (e.g. MCAL extension of the AUTOSAR method simplifies integration of the
drivers). In addition, each product includes a sample program. basic software in your ECU and reduces integration time. For more
details on DaVinci tools from Vector, please refer to the relevant
datasheets.
DaVinci tools are used to consistently configure the MICROSAR RTE and MICROSAR BSW modules
> You can configure the MICROSAR BSW modules with DaVinci approaches offers optimal results. Bottom-up is especially well-
Configurator Pro. Vector recommends the proven GENy configu- suited to MICROSAR DIAG and MICROSAR IO, while top-down is
ration tool for configuring the communication-related ideal for the other MICROSAR BSW modules.
MICROSAR modules. GENy is supplied with DaVinci Configurator In the bottom-up approach, the configuration of the interfaces of
Pro. GENy enables cross-module configuration of specific param- the functional software is done by using the basic software. This
2/8 eters and parameter groups. This saves you time compared to involves using DaVinci Developer to automatically generate SWC
step-wise configuration of individual BSW modules; it also service ports (including runnables) based on BSW service ports.
ensures a compatible configuration of interdependent modules. This approach gives you quick training in AUTOSAR, and you can
> The MICROSAR RTE is configured with DaVinci Developer, the create your first functionally-capable ECU in a short period of time.
design tool for SWCs. 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
Scalability modules – in part automatically. This reduces configuration effort
In addition to fulfilling AUTOSAR requirements, the MICROSAR significantly.
BSW modules also provide a number of functional extensions. The
extended configuration options let you deactivate unnecessary User-Selectable Configuration Point
functions to optimize the MICROSAR code for your application. The configuration point of all MICROSAR basic software modules is
This scalability makes the MICROSAR modules the optimal solution user-selectable. Per AUTOSAR Configuration Conformance Classes
for both small and challenging applications. MICROSAR is already CCC1 to CCC3, you can select the configuration point for each BSW
being implemented in a wide range of ECUs, such as steering module; choices are: pre-compile, link-time or post-build.
angle sensors, door ECUs, engine ECUs, central gateways, etc. GENy offers optimal process support for the post-build configured
MICROSAR may also be used with other operating systems such as communications-related MICROSAR modules. Post-build lets you
Linux or QNX. replace certain parameter values from the communication matrix
without compiling in the ECU. GENy has a special graphic mode
Flexible Development Process that is exclusively used to edit post-build parameters. Afterwards,
With the DaVinci tools it is possible to execute a top-down config- GENy generates platform-specific HEX files, which can be flashed
uration or a bottom-up configuration to integrate the MICROSAR directly to the ECU. The MICROSAR BSW modules check for com-
products in your development process. A combination of the two patibility of the replaced configuration at runtime.
You use DaVinci Configurator Pro to configure the BSW You use DaVinci Developer to create the MICROSAR RTE
modules for your application
AUTOSAR
MICROSAR OS
Modul
AUTOSAR
For a gateway ECU, you do not need any additional software. The
Overview of Advantages COM and PDUR BSW modules from MICROSAR COM enable routing
> Code and execution time optimized by application-specific of signals and TP or application messages.
configuration
> Very efficient signal access via function macros Functions
> Contains important functionality of AUTOSAR Release 4.0 The BSW modules from MICROSAR COM contain functions defined
2/12
and many other useful extensions in AUTOSAR Release 3.x:
> Extended support for NM coordinators > Services of the COM module organize transmission of messages
> NM module: OSEK NM compatibility is configurable according to their send type (cyclic, event-triggered, etc.). A
> Supports simultaneous operation of AUTOSAR NM and OSEK key task is to implement bus-independent signals of the func-
NM in NM migration projects tional software in PDUs.
> The PDU Router (PDUR) distributes the PDUs to the bus-specific
The basic software modules (BSW) of MICROSAR COM include AUTOSAR communication modules, so that they can transmit
AUTOSAR services for ECU communication. These services can the information. In the opposite direction, the PDUR receives
support any number of communication channels. They are bus-in- the PDUs and routes them to the relevant services of the NM,
dependent and are needed in every communication stack. Per COM or DCM modules or to other networks (gateway).
AUTOSAR architecture, they handle control and full integration in > The Generic Network Management Interface (NM) bundles
the ECU software of bus-specific communication modules from inter-bus network management activities of all of the ECU’s
MICROSAR CAN, MICROSAR FR, MICROSAR LIN, MICROSAR IP and communication channels. As NM coordinator, it synchronizes
MICROSAR MOST. wake-up and sleep of the communication channels.
> Optionally, a user may use an I-PDU Multiplexer (IPDUM) in the
Application Areas communication stack of the ECU software. IPDUM supports
MICROSAR COM lets users develop their functional software by a multiple usage of fixed I-PDUs with variable data contents.
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.
MICROSAR COM
Modules
AUTOSAR
The following functions are optionally available: > NM: Synchronous sleep and wake-up of multiple networks via
> COM: TX deadline monitoring different NM coordinators
> PDUR: TP layer fan-out and zero cost operation > NM: Backup coordinator
> PDUR: Transmit cancellation and change parameter request > NM: Pre-compile optimizations such as use of function macros
> NM: Support of OSEK NM (configurable)
Furthermore, the BSW modules from MICROSAR COM contain the > NM: Mixed operation of OSEK and AUTOSAR-NM on one channel 2/13
following functionalities. Some of them are part of AUTOSAR
Release 4.0 (ASR 4.0): Scope of Delivery
> COM: Indication and timeout flags for signals and signal groups > Software modules as library with C header files, optionally as
> COM: Signal conversion. This conversion may be configured source code
with an A2L ASAP2 database. > Command line based generator (for Windows NT/2000/XP/Vista)
> COM: Invalidity declaration of TX signals in case of RX signal > BSW modules description
timeout > DLLs for configuration with GENy
> COM: Deactivation of the TX confirmation interrupt > Documentation and sample programs with makefiles
> COM: Pre-compile optimizations such as function macros for
very efficient signal access The complete AUTOSAR solution from Vector
> COM, PDUR: Transport of long I-PDUs and signals via CANTP and The AUTOSAR solution from Vector consists of the DaVinci
via J1939 as specified in ASR 4.0. Other TPs are available upon tools, MICROSAR-basic software and the MICROSAR RTE.
request. You will find information on properties of BSW modules from
> COM: Extension by signal callout functions, e. g. to integrate the MICROSAR packages and detailed descriptions of func-
gateways as complex device drivers. tional features of individual DaVinci Tools in the relevant
> PDUR: Generic interface for integrating a TP and bus communi- datasheets.
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 from MICORSAR CAN
The MICROSAR CAN package contains the BSW modules defined in Functions
the AUTOSAR architecture for CAN communication: CANIF, CANNM, The BSW modules in MICROSAR CAN contain functions defined in
CANTP, CANSM and CANXCP. AUTOSAR Release 3.x.
The following functions are available as options for the CANIF
Application Areas module:
2/14 MICROSAR CAN is used to handle communication in CAN networks. > Support of an external CAN controller
It is also well-suited as a foundation for calibration with XCP, > Increased number of Full CAN objects by combining multiple
gateways or flashing. CAN controllers on one physical CAN bus (Common CAN)
You can also combine MICROSAR CAN with the separately available > Individual polling of messages in Full CAN objects
MICROSAR J1939TP package to enable operation of an AUTOSAR > Support of multiple Basic CAN objects to further optimize
ECU in a J1939 network. The BAM and CMDT transport protocols acceptance filters
are available for this. > Rx queue for short interrupt execution times
MICROSAR CAN
modules
AUTOSAR
> CANSM: Checks whether states were successfully set in the CAN
driver (CANDRV) or CAN transceiver driver (CANTRCV). In case of You will find information on properties of BSW modules from
error, an automatic repetition is executed. the MICROSAR packages and detailed descriptions of func-
> CANTP: Supports full duplex communication tional features of individual DaVinci Tools in the relevant
> CANTP: Supports mixed addressing (11 bit CAN ID); typically for datasheets.
CAN/LIN gateway applications 2/15
> CANTP: Optimized routing per ASR 4.0 (e.g. with Burst Trans- Other MICROSAR Products for a Complete CAN Communication
mission) together with the PDUR from MICORSAR COM. Stack
> CANTP: ISO 15765-2 compatibility is configurable Based on the AUTOSAR architecture, a complete communication
> CANTP: Sets BlockSize and STmin at runtime stack for CAN can be formed using MICROSAR CAN together with
> BAM and CMDT: Transport protocols for J1939 networks the BSW modules from the separately available MICROSAR COM,
available as option MICROSAR CAL and MICROSAR EXT packages. To interface
MICROSAR CAN to the application and the hardware, you will still
Scope of Delivery need the following BSW modules:
> Software modules as library with C header files, optionally as > Hardware-specific CAN driver (CANDRV) from MICROSAR CAL
source code > Hardware-specific transceiver control (CANTRCV) from
> Command line based generator (for Windows NT/2000/XP/ MICROSAR EXT
Vista) > General communication modules (COM, NM, PDUR, IPDUM) from
> BSW modules description MICROSAR COM
> DLLs for configuration with GENy Modules in MICROSAR CAL and MICROSAR EXT are available for
> Documentation and sample programs with makefiles many microcontrollers and transceivers.
The complete AUTOSAR Solution from Vector Other relevant MICROSAR Products for CAN
The AUTOSAR solution from Vector consists of the DaVinci > DCM and DEM from MICROSAR DIAG
tools, MICROSAR-basic software and the MICROSAR RTE. > DET, ECUM and COMM from MICROSAR SYS
> XCP ◆
Vector offers you MICROSAR FR, an AUTOSAR-conformant package In addition, the BSW modules from MICROSAR FR contain the fol-
for FlexRay communication. It contains the following BSW mod- lowing services. Some of them are part of ASR 4.0:
ules defined in the AUTOSAR architecture: FRIF, FRNM, FRTP or > FRIF: Automatic repetition of job list execution in case of errors
FRISOTP, FRSM and FRXCP. or loss of bus synchronization
> FRSM: Support of ECU Passive mode (ASR 4.0)
2/16 Application Areas > FRNM: Pre-compile optimizations, e.g. for single-channel
MICROSAR FR is used to handle communication in FlexRay net- systems
works. Furthermore, it is ideal as a foundation for calibration with > FRNM and FRSM: Detection and recovery from synchronization
XCP, gateways or flashing. losses (Long/Short Term Sync) (ASR 4.0)
> FRSM: Immediate startup after passive wakeup (ASR 4.0)
Overview of Advantages
> Small code size and short execution times due to optimized Operating System
administration of job lists of the FlexRay interfaces FlexRay basic software modules can be used entirely without an
> Either the FRTP (AUTOSAR) or FRISOTP (ISO 10681) operating system. However, it makes sense to use an AUTOSAR OS
transport protocol may be used or a conventional OSEK-OS (e.g. Vector osCAN). Ideally suited for
> Support of ECU passive mode in the FlexRay State Manager FlexRay applications is MICROSAR OS from Vector.
> Early detection of synchronization losses
Scope of Delivery
> Software modules as library with C header files, optionally as
Functions source code
The BSW modules in MICROSAR FR contain functions defined in > Command line based generator (for Windows NT/2000/XP/
AUTOSAR Release 3.x. In anticipation of AUTOSAR Release 4.0 (ASR Vista)
4.0), MICROSAR FR also includes the BSW module FRISOTP, conform- > BSW modules description
ant to ISO 10681. It is compatible with the rest of the MICROSAR BSW > DLLs for configuration with GENy
modules, and upon request it can replace FRTP in your FlexRay com- > Documentation and sample programs with makefiles
munication stack. The following function is available as an option:
> FRISOTP: Unknown Message Length Transmission
MICROSAR
FlexRay
modules
AUTOSAR
MICROSAR LIN contains the BSW modules defined in the AUTOSAR > LINIF: Configurable wakeup delay
architecture for LIN communication: LINIF, LINTP, LINSM. Per > LINIF/LINSM: Production/Development Error Reporting
AUTOSAR, LINTP is a component of LINIF. (DEM/DET) has been extended by additional and more precise
events
Application Areas > LINIF and LINTP: Separately configurable memory mapping of
2/18 MICROSAR LIN is used to handle communication tasks for a LIN configuration data for LINIF and LINTP. This is especially
Master in a LIN network. In addition, it may be used as a founda- appealing for controllers with segmented memory. The
tion for gateways or flashing. MICROSAR LIN product includes two separate generators for
LINIF and LINTP for this purpose.
Overview of Advantages > LINTP: Extends gateway functionality for precise switchover of
> Core component of the complete LIN communication stack the schedule tables for diagnostic requests and responses
for AUTOSAR ECUs > LINSM: Extended interface for monitoring the LINSM sub-
> Optimized routing of diagnostic requests to LIN Slaves modes for controlled switchover of the LIN schedule tables
> Quick start of the LIN channel > LINSM: Optimized startup behavior by automatic selection of a
> Reliable switching of schedule tables possible schedule table (configurable)
> Based on Vector’s many years of experience with produc-
tion software for LIN 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
Functions ECU Configuration Description and is considered when configur-
The BSW modules in MICROSAR LIN contain functions defined in ing the master. This lets the master evaluate the response error
AUTOSAR Release 3.x. bits sent by the slaves and then initiate the associated DEM
In addition, BSW modules from MICROSAR LIN contain the follow- events.
ing services. Some of them are specified in AUTOSAR Release 4.0
(ASR 4.0):
MICROSAR LIN
modules
AUTOSAR
Scope of Delivery > Hardware-specific LIN driver (LINDRV) from MICROSAR CAL
> Software modules as library with C header files, optionally as > Hardware-specific transceiver control (LINTRCV) from
source code MICROSAR EXT
> Command line based generator (for Windows NT/2000/XP/ > General communication modules (COM, PDUR) from MICROSAR
Vista) COM
> BSW modules description The modules in MICROSAR CAL and MICROSAR EXT are available for 2/19
> DLLs for configuration with GENy many different microcontrollers and transceivers.
> Documentation and sample programs with makefiles
Other Relevant MICROSAR Products for LIN
The complete AUTOSAR Solution from Vector > DET, ECUM and COMM from MICROSAR SYS ◆
The AUTOSAR solution from Vector consists of the DaVinci
tools, MICROSAR-basic software and the MICROSAR RTE.
You will find information on properties of BSW modules from
the MICROSAR packages and detailed descriptions of func-
tional features of individual DaVinci Tools in the relevant
datasheets.
MICROSAR IP
modules
AUTOSAR
MICROSAR
MOST
modules
AUTOSAR
For gateways, in particular, Vector offers customized solutions MICROSAR MOST to the application and hardware you will need
that take into account the special aspects of OEM-specific data the following BSW modules:
formats in configuration. > Hardware specific MOST driver (MOSTDRV) from MICROSAR CAL
> General communication modules (COM, PDUR) from MICROSAR
Scope of Delivery COM
> Software modules as library with C header files, optionally as 2/23
source code Low-Level Driver
> Command line based generator (for Windows NT/2000/XP/ In the framework of project work, Vector would be glad to
Vista) create a Low-Level Driver for interfacing SMSC-NetServices
> BSW module description to your specific hardware.
> DLLs for configuration with GENy
> Documentation and sample programs with makefiles
Other Relevant MICROSAR Products for MOST
The complete AUTOSAR Solution from Vector > DCM and DEM from MICROSAR DIAG
The AUTOSAR solution from Vector consists of the DaVinci > DET, ECUM and COMM from MICROSAR SYS ◆
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.
MICROSAR MEM
AUTOSAR Basic Software Modules for Memory Management
MICROSAR MEM
V2.3 2010-06
modules
> NVM: Dedicated interface for the DCM diagnostic module for The complete AUTOSAR Solution from Vector
direct read-out and manipulation of data blocks (ASR4.0) Vector offers a fully tuned AUTOSAR solution for developing AUTOSAR
> NVM and EA: Additional configurable transaction security, which ECUs with its DaVinci and MICROSAR products.
is a standard feature of the FEE module You will find information on properties of BSW modules from the
> Fixed defined maximum execution times for all functions in the MICROSAR packages as well as detailed descriptions of functional
MICROSAR MEM BSW modules. This yields system optimizations features of the DaVinci Tools in separate datasheets.
that shorten access times.
> FEE: High-performance administration of stored memory data
> FEE: Common usage of FEE module by Flash Bootloader (FBL) Other MICROSAR Products for a Complete Memory Stack
and application possible - also with common memory blocks. An Based on the AUTOSAR architecture, a complete memory stack for
update of the ECU software can be done without adjustment of your ECU can be formed with memory services from MICROSAR MEM
the FBL. together with other platform-specific BSW modules from the
> FEE: Update support for adjustment of non volatile memory after separately available MICROSAR CAL and MICROSAR EXT packages.
ECU re-programming. This is done with a new configuration > Hardware-specific FLSDRV and/or EEPDRV from MICROSAR CAL
table (content and size). > DRVEXT from MICROSAR EXT for external memory chips
> FEE/EA: Redundant storage of management data for increased
reliability of data access In addition, it is easy to integrate MCAL drivers from semiconduc-
tor manufacturers in the MICROSAR memory stack.
Scope of Delivery
> Software modules as library with C header files, optionally as You can protect your memory data with the checksum module
source code (CRC) at your desired security level. To do this, you will need the
> Command line based generator (for Windows NT/2000/ LIBS module from MICROSAR SYS.
XP/Vista)
> BSW modules description
> Description files for DaVinci Configurator Pro
> Documentation and sample programs with makefiles
MICROSAR SYS
modules
AUTOSAR
> SCHM: The Schedule Manager provides the time base for all BSW Scope of Delivery
modules. > Software modules as library with C header files, optionally as
> WDGM and WDGIF: The Watchdog Manager monitors the func- source code
tional software for proper operation. If the Watchdog time > Command line based generator (for Windows NT/2000/XP/
expires, it triggers an ECU reset. Vista)
> BSW modules description 2/27
The following functions are optionally available: > Description files for DaVinci Configurator Pro
> DET: Support of service ports > Documentation and sample programs with makefiles
> COMM: Support of the COMM bus type “Internal”
The complete AUTOSAR Solution from Vector
In addition, the following extensions are included. Some of them The AUTOSAR solution from Vector consists of the DaVinci
are part of AUTOSAR Release 4.0 (ASR 4.0): tools, MICROSAR-basic software and the MICROSAR RTE.
> COMM: Compatibility with OSEK NM You will find information on properties of BSW modules from
> COMM: Link-time implementation the MICROSAR packages and detailed descriptions of func-
> ECUM: Supports validation of the reason for wake-up in Power tional features of individual DaVinci Tools in the relevant
SetUp and Run modes datasheets.
> ECUM: Implementation variant pre-compile or post-build
available ◆
> Support of activation/deactivation of PDU groups and NM-PDUs
for diagnostics (Service Communication Control) as well as the
ECU Passive Mode (ASR4.0)
Configuration
The ECUM module can be configured with either GENy or DaVinci
Configurator Pro.
MICROSAR DIAG
AUTOSAR Basic Software Modules for the UDS Protocol
Summary of Advantages suited for the series use and is available already for many OEMs.
> Customized solutions available for many automotive OEMs For ECUs without diagnostics specification an OEM independent
> Vector’s numerous years of experience in the diagostics field package of MICROSAR DIAG is available.
> Contains all necessary extensions for use in production
> Supports OBDII for DCM per AUTOSAR 3.1 MICORSAR DIAG can be used for current and future legal require-
> Also supports WWH-OBD (Euro VI) ments such as EURO VI. The support of OBDII (ISO 15031/ SAE
> Variants handling already included for diagnostic configuration J1979) as well as WWH-OBD (ISO27145) is available as an option.
> Configurable via ODX format with CANdelaStudio
> Application code templates are generated for the ECU software 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
MICROSAR DIAG contains the AUTOSAR-compatible implementa- ECU. This avoids redundancies in the ECU software, because identi-
tion of UDS protocol ISO 14229-1:2006 and is ideal as diagnostic cal interfaces to the same data, services or DTCs are combined in
software for your vehicle project. MICROSAR DIAG performs a num- the generated diagnostic code.
ber of tasks. Offering:
> OEM-specific implementation of the diagnostic protocol for Functions
communication between tester and ECU MICROSAR DIAG contains the three BSW modules DCM, DEM and
> Fault memory and management FIM from the AUTOSAR architecture. Their functions are described
> Disabling of certain functionalities based on active fault entries in the following sections.
Combined with CANdelaStudio − the widely used specification tool
for creating diagnostic data − you get a complete diagnostic solu- Diagnostic Event Manager (DEM) Functions
tion from a single source. According to AUTOSAR, it is the OEM who specifies diagnostic
functionality. Only interfaces are defined for the DEM module, so
Application Areas that users can develop their own functional software (SWCs) inde-
Diagnostics are not completely specified in AUTOSAR. Beyond the pendent of the use case.
standard each OEM has there own specifications. For this reason Vector can offer you DEM variants that have been modified for
Vector offers MICROSAR DIAG with OEM specific extensions. It is many different OEMs. These variants cover the requirements of the
V2.4 2010-04
MICROSAR DIAG
modules
specific carmakers. A generic OEM-independent variant is also In addition, the DCM contains the following extensions to
available. This version supports the following functions as AUTOSAR as standard features:
standard features: > Inclusion of the most important UDS Services not contained in
> Administration of all DTC status bits per the UDS standard AUTOSAR 3.0 (In the table below you will find an overall view of
> Definition of individual snapshot records and extended records all supported UDS services and associated tasks of the applica-
> Pre-defined extended records (e.g. OccurenceCounter) tion software).
> Implementation of counter and time-based error debounce > OEM-specific extensions (e.g. RoutineControl Service, ECU-
algorithms PassiveMode)
> Suppression of low-priority errors when memory is full > Variants handling for diagnostic configurations
> Flexible unlearning (aging) of errors > Link-time configuration
> Variants handling for diagnostic configuration > Multiple client support
> Link-time configuration > Seamless interaction with the Vector Flash Bootloader
> Compressed configuration data to optimize code size > Generation of an application code template for the ECU software
The following AUTOSAR functions are optionally available: Function Inhibition Manager (FIM) Functions
> Support of combined errors All functions of AUTOSAR Release 3.x are standard features of the
> Implementation of additional error debounce algorithms (e.g. MICROSAR FIM. The following functions are optionally available:
frequency-based) > Post-build configuration
> Post-build configurability > Periodic or event-based evaluation of FIM status to prevent
> J1939 diagnostic interfaces for DM1-3 bursts in processor loading
> Export of an ASAP2 file for read-out of momentary status
Diagnostic Communication Manager (DCM) Functions information over XCP
The DCM contains functions defined in AUTOSAR Release 3.0.
The following functions are optionally available: Configuration and Parameterization
> Support of OBDII (ISO15031) per AUTOSAR 3.1 You can adapt BSW modules from MICROSAR DIAG to meet the
> Post-build configuration needs of your application by modifying the configuration. Since
> Support of multiple diagnostic protocols per AUTOSAR diagnostic-specific parameterization of the DCM is limited using
the standard AUTOSAR 3.0 exchange file “ECU Configuration Other Relevant Vector Products
Description”, the MICROSAR DCM modules are parameterized by a You can combine MICROSAR DIAG with the following MICROSAR
CDD file. You can create them quickly and easily or import them products to fulfill relevant ISO standards:
from the most commonly used ODX dialects with the proven “diag- > MICROSAR CAN (ISO 15765-3 or ISO/DIS 14229-3)
nostic authoring tool” CANdelaStudio. > MICROSAR FR (ISO/DIS 14229-4)
The DEM may be configured via either a CDD file or an “ECU Con- > MICROSAR IP (ISO/DIS 14229-5)
figuration Description”. To parameterize MICROSAR DIAG you will need CANdelaStudio. For
more information on this, see the separate datasheet in Vector’s
Scope of Delivery diagnostics catalog.
> Software modules as a library with C header files, optionally as
source code
> Command line based generator (for Windows NT/2000/
XP/Vista)
> BSW module description
> DLLs for configuration with GENy
> Documentation and sample programs with makefiles
> Converters for CANdela diagnostic descriptions
The MICROSAR CAL drivers work together optimally with the rest of
Overview of advantages the MICROSAR packages. You just add other packages (e.g.
> Optimal support of microcontroller peripherals MICROSAR CAN, MICROSAR MEM, etc.) depending on the require-
> Simplified configuration, since configurator considers ments of your application, and this gives you a complete communi-
parameter dependencies cation stack or memory management per AUTOSAR specification.
> Development accelerated by plausibility and completeness
2/32
tests in the configurator Functions
> Resource-saving, since functionalities can be deactivated The MICROSAR CAL package contains the driver modules Adc, Can,
> Reduced hardware requirements due to optimal utilization Fr, Lin, Dio, Eep, Fls, Gpt, Icu, Mcu, Port, Pwm, Spi and Wdg. They
of hardware buffers conform to AUTOSAR Release 3.x and are available for many com-
> Gateway developments are supported by efficient auxiliary monly used microcontrollers.
functions
In addition, MICROSAR CAL contains the following extensions.
The MICROSAR CAL package contains the drivers for controlling Some are from AUTOSAR Release 4.0 (ASR 4.0):
the microcontroller’s peripherals. It is fully compatible with the > Ethernet driver (ETHDRV) (ASR 4.0)
AUTOSAR specification “Microcontroller Abstraction Layer”. Each > Implementation of Interrupt Service Routines as CAT1, CAT2 or
MICROSAR CAL driver is optimized controller-specifically. void-void function (configurable)
> Flexible integration of error handling with user-configurable
Application Areas interface names such as Det, Dem, etc.
MICROSAR CAL gives you a turn-key solution for driving your > CANDRV: Notification (Callback) on message reception and
microcontroller peripherals. So, it is not necessary to make after successfully sending a message. This makes it possible to
changes to the functional software when switching to different automatically execute application-specific code.
hardware. All you need to do is switch out MICROSAR CAL to inte- > DIODRV: User-configurable locating of the pins within a
grate the appropriate drivers. ChannelGroup
> ICUDRV: Notification of measurement buffer overrun
> MCUDRV: Reset mechanisms are user-configurable for the
function Mcu_PerformReset().
MICROSAR CAL
modules
AUTOSAR
MICROSAR EXT
modules
AUTOSAR
Additional Services
Vector 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. ◆
MICROSAR IO
module
AUTOSAR
This SWC description later flows into modeling of the entire ECU Other Relevant MICROSAR Products
software, which could be created with DaVinci Developer, for If I/O signals are accessed via an external device, your I/O Stack
example. Here, the Vector design and configuration tool ensures will need an additional suitable driver from MICROSAR EXT.
that ECU signals defined in MICROSAR IO are integrated in the
overall data flow of the ECU software. This modeling is the foun- Additional Services
dation for later generation of the RTE. Vector would be glad to support you in the development of the “IO 2/37
Hardware Abstraction Layer” of your special ECU in the framework
Scope of Delivery of project work. You benefit from Vector‘s detailed knowledge of
> Software modules as library with C header files, optionally as the AUTOSAR specification and methodology as well as its exten-
source code sive experience in integration of ECU software. ◆
> Command line based generator (for Windows NT/2000/XP/
Vista)
> BSW modules description
> Description files for DaVinci Configurator Pro
> Documentation and sample programs with makefiles
ated for the specific ECU and, if applicable, the BSW modules. It is
Overview of Advantages also possible to use a SWC in multiple instances on one ECU.
> Easy to configure and scalable
> In-depth consistency check of the configuration In generating the MICROSAR RTE, the user can choose between
> Highly optimized code with intelligent synchronization two modes:
mechanisms > Contract Phase Generation for developing individual SWCs in an
2/38
> Quick entry into working with AUTOSAR, e. g. based on early phase. In this case, the generator just creates a header
generated code templates for the software components file for each SWC instead of the entire RTE. This makes it possi-
(SWCs) ble to compile the SWCs individually, e.g. to transfer them to a
> Well-suited for migration projects development partner as object code.
> RTE generation for the entire ECU software. The code generated
MICROSAR RTE (Run Time Environment) is the scalable and highly in this mode is highly efficient and requires only little memory
optimized AUTOSAR runtime environment from Vector. The RTE is a space. It is optimized for the entire ECU configuration and
module introduced by AUTOSAR that manages communication makes few demands on system resources due to short execution
between the software components (SWCs). It assures consistency times and minimal interrupt disable times. One way this is
of the overall information flow and represents the interface bet- achieved is by using intelligent synchronization mechanisms
ween the functional software, basic software (BSW) and complex that are tuned to the properties of the hardware used.
device drivers (CDD). The SWCs, RTE, CDD and BSW modules
together form the overall AUTOSAR ECU software. Functions
The MICROSAR RTE contains functions defined in AUTOSAR
Application Areas Releases 3.x:
When the functional software of an ECU is implemented by > Sender/Receiver and Client/Server communication
AUTOSAR-conformant SWCs, the user needs the RTE as a runtime > Mode management
environment. This modular layout of the ECU software offers the > Inter-runnable variables as well as Exclusive Areas
user maximum flexibility: SWCs that have been manually devel- > Trigger for runnables
oped or designed by model-based tools can be re-used in multiple > Support of calibration parameters and Per-Instance Memory
ECU projects. The RTE only needs to be reconfigured and regener- > Multiple instancing of SWCs
MICROSAR RTE
module
AUTOSAR
Even if just a few signals are identical in the PDUs, they can still During operation, when diagnostic services are requested that are
be overlaid. The RTE implements this by the so-called Fan-in or not relevant to the active Identity, the appropriate negative res-
Fan-out mechanism. ponse is automatically sent.
Diagnostics
To describe the diagnostics of an ECU, one diagnostic description
file (CDD) is needed per ECU. Just as done for communications,
identical diagnostic services are overlaid, and so only one
instance of them exists. As usual, the user configures the opti-
mized superset of all diagnostic services in GENy.
Configuration process of
multiple ECUs
EMBEDDED SOFTWARE
Altera
NIOS II GNU, Tasking X
Atmel
AVR32 IAR X [4] X
Freescale
i.MX25 GNU X
MAC7100 ARM, IAR X X
S12, S12X Cosmic, Metrowerks X X X X X
MPC55xx, MPC56xx Cosmic, Green Hills, X X X X [4] X
Metrowerks, Wind
River
Fujitsu
16FX Fujitsu X
FR60 Fujitsu X X X
MB86 GNU X X
Infineon
CIC310 X
(External Controller)
TriCore GNU, Green Hills, X X X [4] X
Tasking
XC2000 Tasking X X X
Microchip
dsPic33F Microchip X
Renesas Electronics (NEC/Renesas)
78K0R IAR X
V85x Green Hills, IAR, X X X X [4] X
Renesas (NEC)
M32C Renesas, IAR X X X
M32R Renesas X
R32C Renesas, IAR X X X X
SH2 Renesas X
V2.0 2010-05
Texas Instruments
TMS320 Texas Instruments X
TMS470 Texas Instruments X X
TMS570 Texas Instruments X X X X X
Vector
CANoe osCAN Microsoft VisualC X X X X X X
Emulation
[1] = As alternative to MICROSAR OS you can use an osCAN operating system in AUTOSAR systems.
[2] = Some of the MCAL drivers are created by hardware manufacturers and correspond partly to AUTOSAR release 2.1.
[3] = 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
Functions
Overview of advantages DaVinci Developer offers extensive functions for defining and
> Convenient graphical definition of software components integrating AUTOSAR SWCs:
> Clear representation of complex systems > Graphical definition of SWCs with extensive layout functions
> Special functions simplify data exchange between OEM and > Definition of port interfaces and data types
ECU developer > Definition of port prototypes with service needs and communi-
2/42
> Easy connection to configuration management tools cation specification, e.g. initial values and timeouts
> Consistent configuration of the MICROSAR RTE > Definition of runnable entities with activation events and port
access
DaVinci Developer is the professional tool for designing AUTOSAR > Support for all types of AUTOSAR SWCs and application compo-
software components (SWCs) and for configuring the MICROSAR nents, compositions, calibration and service components
RTE. Convenient graphical editors let you design the structure and > Import and export of AUTOSAR XML formats (System Descrip-
interfaces of the functional software for your ECU quickly and tion Template, Software Component Template)
clearly, and they facilitate smooth integration of the functional > Support for various AUTOSAR XML versions in parallel.
software with the ECU‘s basic software. > Signal import from commonly used network description formats
(DBC, FIBEX, LDF)
Application Areas > Data mapping of port data to network signals
DaVinci Developer supports ECU developers in developing > Consistency check of the SWC definition and the RTE
AUTOSAR-conformant ECUs. You can use DaVinci Developer as an configuration
architecture tool to define application software architectures. > Interface to model-based development tools via AUTOSAR-SWC
DaVinci Developer is also well-suited as an integration tool you description files
can use to consistently integrate existing AUTOSAR SWCs in an
ECU. This means that DaVinci Developer is a flexible tool that can Workflows and AUTOSAR Methods
be used in different OEM projects. DaVinci Developer can be flexibly used in a distributed develop-
Finally, DaVinci Developer lets you consistently configure the ment process based on the AUTOSAR method. For this purpose,
MICROSAR RTE based on previously defined AUTOSAR SWCs. the tool offers extensive functionality for data exchange between
OEM and ECU developer:
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
> Import/Update function to support an iterative development DaVinci Developer works seamlessly with DaVinci Configurator Pro
process to create a consistent overall configuration. For example, the
> Diff and Merge functions with configurable presettings for indi- service components and IO hardware abstraction components
vidual objects. This makes it possible to extend OEM-generated generated by DaVinci Configurator Pro can be conveniently
SWCs by adding port prototypes and runnable entities. imported and linked to the application SWCs. DaVinci Developer
> Library concept for reusing components or interfaces in offers special support by automatically creating suitable service 2/43
multiple ECU projects port prototypes and server runnables for the application SWCs.
> Connection to configuration management systems with fine- Finally, the RTE configuration is saved AUTOSAR-conformantly in
granulation versioning of individual objects, e. g. SWCs an ECU configuration file.
Testing atomic AUTOSAR software components with Testing a composition of multiple software components
DaVinci Component Tester with DaVinci Component Tester
AUTOSAR
Functional principle:
Interfacing DaVinci Component Tester to CANoe
AUTOSAR
Functional principle:
Interfacing DaVinci Component Tester to NUnit
DaVinci Configurator Pro
Configuration of AUTOSAR Basic Software
Vector’s DaVinci Configurator Pro is the professional tool for con- > Support of commonly used network description formats (DBC,
figuring the Basic Software (BSW) modules of an AUTOSAR ECU FIBEX, LDF) and/or the AUTOSAR “ECU Extract of System
according to the AUTOSAR standard. Description”
> Flexible generation options for optimal integration in existing
Properties and Advantages development processes
2/48 DaVinci Configurator Pro was created as an open tool for configur- > Project assistant for easily creating and updating ECU projects
ing and generating BSW modules. It is a practical, intuitive and
user-friendly implementation of the AUTOSAR method. In addi- Application Areas
tion, its multi-stage and rule-based validation process assures DaVinci Configurator Pro supports users in configuring, validating
consistency of all configuration parameters between modules. and generating BSW modules from Vector (MICROSAR), third party
For user-friendly configuration of the BSW modules, DaVinci producers (e.g. MCALs from semiconductor manufacturers) and
Configurator Pro uses so-called DaVinci description files which are user-developed BSW modules.
included in the scope of delivery of Vector AUTOSAR BSW modules
(MICROSAR). The DaVinci Configurator Kit from Vector, available Functions
as a separate product, makes it easy to create these DaVinci de- DaVinci Configurator Pro offers users two different configuration
scription files on your own. As an alternative, if only an AUTOSAR modes: Comfort Mode and GCE Mode.
“BSWMD” file exists, DaVinci Configurator Pro offers the Generic
Configuration Editor (GCE) mode for modules. This makes it an The Comfort Mode supports you extensively in configuring the
ideal central configuration tool. BSW modules. Using the DaVinci description files you can:
DaVinci Configurator Pro is also characterized by the following > Edit configuration parameters over a user-oriented interface,
properties: e.g. to show complex configuration relationships in simplified
> Support of all available AUTOSAR releases (2.1, 3.0 and 3.1), form
also in mixed forms within a project > Validate parameters across modules
> Project-oriented working mode by simple activation or deacti- > Define the value range of input values
vation of individual BSW modules > Display configurations in GCE or Comfort Mode
> Show the syntax of internal module APIs and callouts
> Display implementation-specific help texts
Beyond the functional features defined in AUTOSAR, the GCE Mode Scope of Delivery
of DaVinci Configurator Pro offers the following supplemental > Windows-based configurators: DaVinci Configurator Pro and
functions: GENy
> Clearly organized display of all software modules based on the > DaVinci Initial ECUC Generator, DaVinci ECUC Updater, DaVinci
AUTOSAR architecture ECUC Difference Analyser
> Copying of configurations of individual BSW modules from 2/49
other projects Additional Services
> Efficient searching and modification of AUTOSAR containers, > Creating DaVinci description files for convenient and user-
parameters and references over the entire project definable configuration, validation and generation of any
> Easy integration of external code generators desired modules with DaVinci Configurator Pro
> Flexible definition of target directories > Hotline, special workshops and training events on the topic of
> Add module-specific documents for quick access embedded software and AUTOSAR ◆
> 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.
DaVinci Configurator Pro supports you in conveniently configuring, validating and generating AUTOSAR BSW modules.
DaVinci Configurator Kit
Creating configuration interfaces and generators for user-developed software modules
DaVinci Configurator
Kit supports you in
integrating your
software module in
DaVinci Configurator
Pro
AUTOSAR
Services
Vector can support you with standard software for your pro-
jects, as well as with customized services such as a hotline,
special workshops and training on the topic of embedded
software and AUTOSAR. For more information go to
www.microsar.com or contact us directly.
Additional Services
The following development tools are included with the DaVinci > Designing convenient configuration interfaces and supplemen-
Configurator Kit: tal validation rules for software modules of third party
> Eparm to define and pre-configure individual parameters producers, such as MCAL drivers or IO hardware abstraction
for a module > Completely creating complex device drivers
> Clix to flexibly lay out user interfaces for displaying and > Extensions of AUTOSAR standard BSW modules 2/51
editing the module configuration in DaVinci Configurator > Developing customer-specific AUTOSAR software components
Pro (SWCs)
> Erule to create complex rules for data checking and file > Working out individual strategies for migration of your existing
generation systems to AUTOSAR
> Cryps to encrypt DaVinci description files created with > Hotline, special workshops and training events on the topic of
Eparm, Clix and Erule embedded software and AUTOSAR ◆
> Elic to incorporate user-developed modules in existing
DaVinci Configurator Pro licenses
Scope of Delivery
> DaVinci Configurator Pro (developer license)
> Tools for generating the DaVinci description files
> Extensive technical documentation of interfaces, as well as
numerous application examples
> Command line based code generator
> 3 days of training
> 20 hours of hotline support
AUTOSAR
3/1
CANbedded
Embedded Software for the Controller Area Network (CAN)
The Vector CANbedded environment consists of a number of con- For distributed applications in automotive networks, it is benefi-
figurable source code components that provide functions which cial if all ECUs contain an identical protocol stack. This will guar-
cover the basic communication requirements in automotive appli- antee CAN bus compatibility.
cations. These functions – based on the CAN protocol – make it > Reduced development costs for implementation and testing
possible to exchange information with other ECUs. > Highly optimized software algorithms make it possible to use
inexpensive hardware
Features and Advantages > Careful development and wide usage in various ECUs makes
The Vector embedded software components provide a wide range CANbedded very reliable.
of features that are indispensable for ECUs in automotive applica-
tions. The software components integrate Vector’s experience in Functions
the areas of embedded software and CAN communication: The basic concept of CANbedded is to provide an interface that is
3/2
> Standard components based on generic code that are scalable simple to use and can be used in all applications. The standard-
for application-specific requirements ized interface includes:
> Low ROM and RAM resource requirements > Basic initialization of the hardware and software
> Efficient run time > Cyclical call of the corresponding state machine (if timing
> Automatic generation of parameter settings and configuration aspects are necessary)
information > Functions needed to change the internal state of the CANbedded
> Simple integration in application software software components.
> Compatibility with Vector’s analysis, simulation and calibration Asynchronous events resulting from CAN bus activities such as
tools receiving messages, wake-up functions or different error states
> Compatibility with the requirements of automobile are forwarded to the application via callback functions.
manufacturers Some applications must run multiple CAN buses. For such applica-
You can use the PC-based configuration tool GENy to configure tions, the CAN Driver – and often the higher CANbedded software
the CANbedded software components for each target node. components as well – must provide a multi-channel interface;
therefore, all Vector software components are available in a multi-
channel version.
Overview on the
CANbedded software
components
COMMUNICATION SOFTWARE
Training
As part of our training program, we offer a range of classes
and workshops on CANbedded at our classrooms or at your
business site.
For more information and the dates of our training courses,
please visit our homepage on the internet at:
www.vector-academy.com
Availability
CANbedded software components for vehicles are available
for many common microcontrollers. For more information
please visit: www.canbedded.com
3/4
Additional Services
Vector also offers services covering the following aspects:
> Adaptation of the CANbedded environment
> Expansion of standard components
> Software components for other bus systems such as FlexRay,
Ethernet or MOST based on AUTOSAR
3/5
CANbedded J1939
Embedded Software Components for J1939 Applications
Functions
The following J1939 software components are available:
> J1939 Base Module: Contains queues for sending and receiving
J1939 messages (PGNs), static address claiming (J1939-NM)
and an interface to OSEK/VDX-OS
LIN (Local Interconnect Network) is a cost-effective, serial com- Modifications and settings in detail:
munication system for distributed electronic control units in the > Adaptation of ECU-specific parameters to the network design
motor vehicle. The LIN protocol is specified by the LIN Consor- > Configuration of the LIN driver to the properties of the specific
tium, of which Vector is an Associate Member. ECU e.g. oscillator frequency, UART, etc.
> Configuration of diagnostic services for LIN Slave ECUs
Features and Advantages
> Definition of message and signal callbacks
Increasing software complexity makes it advantageous to imple-
ment standardized software components. Vector’s expertise ac-
The object codes of the LIN software components are compiled and
quired in developing and working with other protocols has been
linked with the application. Vector’s LIN simulation and analysis
utilized throughout the development of LIN software components:
tools (e.g. CANoe.LIN and CANalyzer.LIN) are available for inte-
> Standard software components based on a portion of the gen-
3/8 gration, analysis and for test purposes. For physical bus access one
erated code are scalable for application-specific requirements
of Vector’s XLI-Interface products can be purchased; these pro-
> Automatic generation of parameter settings and configurations
ducts serve as universal, serial bus interfaces for the LIN bus.
> Runtime efficiency
Timing control of the LIN software components is achieved by
> Low demand for ROM and RAM memory
having tasks called periodically by the application or an operating
> Simple interfacing to the application software
system. Therefore the LIN driver does not require any auxiliary
> Compatibility with other Vector products including analysis,
timers.
simulation, and calibration tools
> Support of LIN 1.2/1.3/2.0 and LIN 2.1
Functions
> Support of multi-channel LIN configurations
The fundamental objective of the implementation is to provide an
LIN networks are described in the LDF (LIN Description File) for- interface that is easy to use and satisfies all applications. The
mat according to the “LIN Configuration Language Specification”. standardized interface offers these features:
This includes all of the information needed to define signals, mes- > Initialization of the LIN hardware
sages, baud rate and schedule tables. A configuration tool is used > User-configurable baudrate (Recommended: 2400, 9600, and
to adapt all LIN software components to ECU-specific require- 19200 Baud)
ments. The tool imports either LDFs or NCF files (Node Capability > Sending of LIN messages (confirmation by flags and callback
File) for parameterization. functions)
Training Availability
As part of our training program, we offer a range of classes Our LIN software components for motor vehicle ECUs are
and workshops on CANbedded LIN Communication. available for a large number of commonly used microcontrol-
For more information and the dates of our training courses, lers.
please visit: www.vector-acadamy.com For further information please visit:
http://www.vector.com/vi_canbedded_lin_en.html
> Receiving of LIN messages (notification by flags and callback This makes it easy to implement CAN-LIN gateways, which are usu-
functions) ally implemented as master network nodes.
> Sleep and wakeup handling
> Protocol error handling LIN Master Transport Layer
> Timeout monitoring of messages Since the master ECU usually has an auxiliary CAN channel, over
> Checking of runtime behavior during the development phase which diagnostics are performed from a tester, the main task of
(debugging) the LIN master is to pass the received tester requests to the rele-
vant LIN slaves. The LIN Diagnostic Transport Layer (DTL) is used
Application Areas for this; it offers two API types according to the LIN 2.0 and 2.1
LIN was developed to round out a collection of automotive proto- specifications:
col standards, but it has been adopted in other areas such as > DTL Raw is used if the data already exist in segmented form
3/9
automation engineering as well. The focus is on cost-effective (routing of CAN TP messages on LIN).
communication networks for ECU subsystems with low data rates. > DTL Cooked accepts assembled data and segments them accord-
LIN therefore supplements existing bus protocols. ing to LIN bus requirements (Diagnostic Service Data Units).
Licenses
When the same hardware interface and same compiler are used
the acquired licenses can be used for all devices of a processor
type and any desired projects.
COMMUNICATION SOFTWARE
3/11
CANbedded Gateway
Standard Embedded Software Components for CAN and LIN Routing
Gateway
between CAN
and LIN buses
COMMUNICATION SOFTWARE
Training
In the framework of our training program, we can offer you
various training events and workshops on our software com-
ponents in our classrooms as well as at your business site.
For more information on individual training events and dates
please visit: www.vector-academy.com
By default, message routing always utilizes the most recent data. Configuration
If data is transmitted less frequently than the data is processed by The CANbedded Gateway is configured with GENy, the configura-
the associated Rx event, the CANbedded Gateway sends the data tion and code generator tool from Vector. The configuration pro-
of the last Rx event. Neither the signal layout within the message cess is based on a DBC or LDF/NCF description file. Routing rela-
nor the signal values are changed here. tionships are defined either:
The user can control gateway activities by configuring “condition- > Automatically by OEM-specific algorithms based on clear rules
al routing”. This saves on bandwidth during critical phases, such > Manually by targeted selection of the signals and messages to
as during software flashing or diagnostic sessions. This is done by be implemented
defining routing groups and assigning routing relationships to
one or more routing groups. At runtime, the application can ena- Scope of Delivery
ble or disable routing of individual groups with the help of an API. > Configuration tool as executable Windows program 3/13
> C source code
TP Routing > C header files
The TP Gateway is responsible for routing the transport protocol > Documentation ◆
data. Diagnostic requests from CAN to LIN and the associated
responses from LIN to CAN might be transmitted, for example.
Using the ISO transport protocol component from CANbedded, it
is possible to support different protocol addressing modes on the
CAN bus.
Metrowerks
Silicon Labs
[1] = Currently in development
C8051F5XX Keil X
STmicroelectronics
SPC56xx DIABDATA X X
Wind River,
Green Hills,
Metrowerks
ST7 Cosmic, Hiware X X
ST9 Cosmic, GNU X X
Vector’s CANdesc (desc = diagnostic embedded software compo- The diagnostic functionalities and diagnostic data for an ECU are
nent) enables vehicle and electronic control unit (ECU) manufac- described in the specification phase using CANdelaStudio and sto-
turers to implement the diagnostic protocol uniformly across red in a consistent database (CANdela). This ECU diagnostic specifi-
different OEMs and their vehicle lines. CANdesc supports diagnos- cation can directly be used to generate the CANdesc code. Changes
tic communication via CAN, MOST, FlexRay. Any other bus system in this specification during the vehicle development can therefore
will be also supported using an optional abstract transport layer be cost-efficiently updated in the ECU by a simple regeneration.
interface. This guarantees that the specification and the implementation al-
CANdesc can be ordered seamlessly integrated in the CANbedded ways fit together.
world and also for stand-alone usage in a supplier-specific envi- The vehicle and ECU manufacturer can use the CANdela data base
ronment. To guarantee efficiency for different OEMs and vehicles, also for parameterization of test systems. Thus a continuous pro-
3/14 CANdesc is fully generated code. The generation process is based cess chain beginning with the specification, continuing with imple-
on the project-specific CANdela data base. mentation and finishing with integration and functional testing
To ease and speed up the usage, a diagnostic code template is can be offered.
generated which fully implements all interfaces. Using this tem-
plate a basically working diagnostic implementation is immedi- ECU Manufacturers:
ately available. CANdesc covers the vehicle manufacturer diagnostic protocol and
transported data completely. This assures that
Features and Advantages > timing and content requirements of the diagnostic protocol are
Vehicle Manufacturers: implemented correctly.
CANdesc offers assurance to the vehicle manufacturer that the > simplification of a product line concept in the diagnostic area in
diagnostic specification is implemented uniformly in all ECUs of a spite of multiple ECU variants and vehicle manufacturers is
vehicle model. possible
Using CANdesc and CANdelaStudio, the comprehensive CANdela ap- > development costs for implementation and testing effort are
proach to diagnostics (see also product description for CANdela – reduced
CANdelaStudio), provides the greatest benefit. > Predictability of the correct and complete diagnostic implemen-
tation is significantly increased.
Generation of ECU
diagnostic software
component
EMBEDDED SOFTWARE
Supported OEMs
For OEM-specific Basic Software
Vector offers embedded software for diagnostics and flash boot- OEM Diagnostic Software Flash Bootloader
loader for a large number of OEMs. Additionally, a version without
J
vendor-specific characteristics is available.
The diagnostic software and flash bootloader are available for both, Jaguar / X X
Landrover
conventional (CANbedded) and AUTOSAR-compliant ECUs. They
contain OEM-specific diagnostic services, fault memory or flash M
processes. MAN X X
Depending on the OEM the scope of the available diagnostic solu- Mazda X X
tion differs, e.g. UDS or KWP2000 is used as diagnostic protocol.
Mitsubishi X X
Please contact Vector to find the optimal solution for you require-
ments. N
NAC X X
OEM Diagnostic Software Flash Bootloader
Nissan X X
B
P
BAIC X
Porsche X X
BMW X X
PSA X X
C
R
Chery X
Renault X X
Chrysler X X
S
Claas X X
SAIC X X
D
SsangYong X X
Daimler X X
Suzuki X
F
T
FAW X X
Toyota X
FIAT X X
V
Fisker X X
Volvo AB X X
Ford X X
VW/Audi X X
G
GAC X X
OEM independent X X
Geely X
GM X X
H Vector is pleased to support further OEMs on request.
Honda X
HMC X X
I
Isuzu X
V2.1 2010-05
Configuration
The CCL can be configured with the configuration tool GENy. In
this process, GENy utilizes information from the communication
database (e.g. the DBC file from the OEM) as well as the user’s
manual settings.
Based on our many years of working together with automotive The steps: Develop an ECU that will later be used for both door
OEMs and suppliers, Vector knows these continually recurring use sides. Load the database that covers the ECUs in the GENy config-
cases well and has developed optimized solutions especially for uration tool and select both ECUs simultaneously. Configure the
them. Identity Manager as a physical multiple ECU and assign a separate
identity to each of the nodes (Left ECU, Right ECU).
Use cases
Practice shows that it is primarily the following three use cases There are essentially two different ways to proceed in coding: If
that recur frequently: the message layout is identical between the identities, utilize the
manual buffer overlay in GENy. This means that the same signal
> Physical multiple ECU APIs can be used regardless of the currently active identity. So,
> Virtual multiple ECU only one application needs to be developed, but the ECU acts dif-
> Multiple configurations ECU ferently to the outside world depending on the identity which is
initialized. The differences are automatically read out from the
The solution approaches presented below lead to substantial sim- DBC file.
plification, reduce administrative effort and thereby reduce costs.
In the second case, buffer overlaying is not needed. Instead, dif-
Identity ferentiate between the left and right sides using generated mac-
An identity identifies an ECU. It determines which variant of ros in the code. It is also easy to implement crossovers of receive
the ECU should be activated (e. g. which door side). So, an and send messages between the two door ECUs while optimizing
identity is the configuration of an ECU that is active at run resources.
time, based on a description file. An ECU’s identity is set
when the ECU is initialized. This software is loaded in the left and right ECUs. The decision on
whether the software is to be installed in the left or right door
ECU is made with each new initialization. A simple function call
establishes the ECU’s identity.
COMMUNICATION SOFTWARE
3/19
Higher-performance control modules also contain more memory
space. This makes it possible to represent multiple ECUs (e.g.
gateway and radio) in one CPU, saving on additional hardware.
These are referred to as virtual multiple ECUs. A typical application involving multiple configurations is the
development of ECUs for both a current car line and a new car line.
The different communication nodes are derived from one data- These ECUs are also referred to as carry over ECUs. Changes made
base. In the configuration tool GENy, you only need to select tho- within the associated database are often very extensive. It is pos-
se nodes that will be implemented and then configure a virtual sible to use a completely different signal layout or use different
multiple ECU in the Identity Manager. All nodes are assigned to messages for different model series. The new configuration could
one identity. The identity operates from a node superset and all even support a different number of CAN buses.
necessary information on the nodes.
First, develop the software for both car lines. In doing so, treat
each car line as though it were assigned to one (or more) 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. ◆
GENy
PC-Tool for Configuring Embedded Software Components
GENy is the convenient configuration tool for software compo- This makes GENy a scalable and fully generic configuration edi-
nents from Vector. It was created for development processes of tor/generator that permits consistent configuration from a single
the future. It is used to configure CANbedded components, integration environment, even in complex heterogeneous
AUTOSAR communication modules and the Flash Bootloader for systems. Vector’s many years of experience in the area of ECU
use in production ECUs. development ensures optimal workflows between OEM and sup-
pliers without altering their tasks or roles.
Features and Advantages
GENy is a developmental offshoot of the previous configuration GENy is a collection of components (not a rigid program block);
tools CANgen and DBKOMgen. The GENy architecture was com- therefore it can also be expanded very easily by adding auxiliary
pletely redesigned based on experience with those two tools. components.
3/20
The following properties characterize the design: GENy’s graphic interface makes it very easy to use and intuitive.
> Thoroughly modular structure due to its static framework, GENy always appears with the same “look and feel” independent
stand-alone graphic user interface (GUI) and dynamically of the components to be configured. The configuration data is
reloadable components shown and processed in a hierarchical tree structure. This makes
> Reloadable hierarchies make it well suited for any configuration navigation user friendly, and the user gets a clear view of all
task (CANbedded, LIN, FlexRay) options.
> A cleverly designed framework mechanism interprets and
manages dependencies in configuring components The Configuration View can be modified manually or via an exter-
> XML is used throughout as the file format, both for the compo- nal XML file. The latter is essential for an OEM-specific appearance
nent descriptions (Attributes) and data saving of GENy’s GUI and guarantees that parameters will have functio-
> Open interfaces offer simple expandability nally relevant preset values.
Tool tips and the online help function help to save time and imme-
diately gives you the information needed about possible compo-
nent settings. Plausibility checks prevent invalid settings and the-
reby prevent errors.
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
The generation process is logged in the Message Window, and this Application Areas
indicates potential errors (e. g. mistakes in configuring) and The GENy configuration tool is always used in conjunction with
other important information. This is done to avoid tedious debug- other Vector software components for communication and diag-
ging efforts. nostics. GENy fulfills AUTOSAR Consortium requirements. ◆
Characteristics:
> Configuration templates for different application types
> System-wide parameters only need to be configured once
> There is only one XML-based configuration file
> Expandable due to open interfaces
> For the Windows operating systems 2000, XP and Vista 3/21
Functions
GENy is the tool for configuring any software component. Config-
uration and parameter files can be generated to integrate them in
the application project.
Functional capabilities of GENy include the configuration of:
> Embedded software components for CAN, LIN, and FlexRay
> Flash Bootloaders
> AUTOSAR BSW (communication modules)
The Master Source Code allows the user to expand his products’ Functions
firmware with CANopen master functionality. The software is The source code offers the following functionalities:
especially suited for integration into control systems. > Network Management (NMT) – control of the connected nodes
via the NMT message. Guarding and heartbeat are still carried
Features and Advantages out.
The Master Source Code makes available all functions necessary > PDO Handling – the actual process data are transmitted via
for a CANopen master. This implements the following standards of PDOs. The PDOs can be configured via the object directory.
the user organization CAN in Automation (CiA): PDOs are also handled synchronously.
> CiA DS 301 Version 4.02, Application Layer and Communication > Local Object Directory – the code makes available its own object
Profile directory via the bus, which can be expanded by the user.
> CiA DS 302 Version 3.1, Framework for programmable CANopen > SDO Handling – the user can initiate individual SDO requests
3/22
Devices via the SDO handler.
> DSP 405 Version 2.0, Interface and Device Profile for > Configuration Manager (CMT) – with this, central configuration
IEC61131-3 Programmable Devices of the connected CANopen nodes can occur in embedded
systems.
Because of its generic structure, slaves with any profile can be
connected. The user can choose to incorporate the software into a Special Functions
project or construct the CANopen functionality as an independent The software supports the storage of data in non-volatile
task in the system. memory. There are interfaces available for connection to a
With the use of the CANopen source code, significant time savings file system or flash memory.
can be achieved during product development. The user can con- On system start, the “boot slave” functionality is supported
centrate on the integration of his own application; the implemen- completely. The network management itself takes care of the
tation of the CANopen protocol is thus simplified significantly. correct starting and configuration of the connected nodes.
The failure control is also taken over by the CANopen master.
Application Areas > Adaptation for Vector CANopen driver under Windows 95/98/NT
The code can be used everywhere customers would like to equip and Microsoft compiler VC++ 6.0
their control systems with CANopen functionality. Users are first > Power PC
and foremost companies that manufacture CANopen devices, as
well as system integrators who must create entire systems. Data Interface
The data interface makes it possible to uncouple the application
Hardware Interfaces from the CANopen stack as the communication task. This makes it
The software is written in ANSI-C and therefore can run on the possible to implement a single processor or a multi-processor sys-
most various platforms. At a minimum, the use of a 16 bit micro- tem. In the latter case, the data interface is placed on a physical
controller should be considered. For addressing various CAN con- DPRAM:
troller types, adaptations are available. The interface of the CAN > Command queue – the command queue is used by the control
3/23
driver is designed so that it is an easy matter to move to other system to send requests to the application layer. This includes
CAN controllers. transmitting initialization data or requests of function compo-
Board Support Packages (BSP) are available for a few evaluation nents (for example to execute SDOs).
environments. A BSP consists of a makefile, a text file with the > Event queue – the event queue carries the data stream from the
settings of the #defines, and a file with the necessary system application layer to the control system. This data consists
adaptations. Even if the user has another target environment, essentially of asynchronous confirmations (for example a res-
these files provide valuable information on porting to customer ponse to an SDO request) and events (for example error states).
hardware. Currently, the following BSPs are available: > Process image – the application acts with the CANopen network
> Adaptation for evaluation board ec376 with Motorola 68376 essentially by means of a process map. This map contains all I/O
from Würz Elektronik GmbH and GNU compiler or Microtec data and other process variables that are to be transmitted by
Research Compiler the CANopen master.
> Adaptation for kitCON 164CI with Infineon SAB164CI from
Phytec GmbH and tasking compiler
Network Management SDO Handling
This module assumes responsibility for administering and moni- The SDO handler makes it possible for the application to have
toring nodes that are connected in the network. For this to hap- access to the object directories of the connected CANopen nodes.
pen, the nodes that are to be accessed and monitored must be It is possible to transmit data blocks in either direction. The
declared. The corresponding parameters for error monitoring “expedited download/upload protocol” is used for objects up to a
(guarding and heartbeat) must also be transmitted. This informa- size of 4 bytes. For objects larger than 4 bytes, the “segmented
tion is stored in the local object directory and can then be reque- download/upload protocol” is used.
sted externally via the bus and internally via the DPRAM. The The block transfer is also implemented and can be initiated in a
monitoring and start of nodes runs largely automatically. number of ways, one of which is by the user.
It is possible to run multiple SDO transfers in parallel (only for dif-
3/24 PDO Handling ferent SDOs).
The PDO handler has the task of accepting received PDOs from the
slaves and forwarding them to the process map of the data inter- Local Object Directory
face. In the other direction, it transmits values from the applica- The Local Object Directory enables access to the master functions
tion to the slaves. This can take place cyclically (by SYNC) or it can and to master parameters and variables over the network. This
be event-driven (by change). makes it possible to configure the master over the network or to
The assignment between PDO and storage of data takes place operate it through locally available functions (displays or inputs
exclusively via the local object directory. The application is thus and outputs). The Configuration Manager is especially activated
completely uncoupled from concrete communication tasks. this way.
The variables in the object directory can be accessed by the appli-
cation through the corresponding SDO read/write requests by
indicating the own node ID.
COMMUNICATION SOFTWARE
The CANopen Slave Source Code contains all CANopen services For special application areas there are expansion modules availa-
required for implementing a slave. It thus offers the user the com- ble for the Slave Source Code, which can be ordered separately:
munication functionality required for internal device development. > Mini-Master
> LSS Master
Features and Advantages > LSS Slave
Significant time savings can be achieved during product develop-
ment by using the CANopen source code. The user can concentrate Application Areas
on the integration of the application; the implementation of the The code can be used everywhere customers would like to equip
CANopen protocol is simplified significantly. The code corresponds their devices with CANopen functionality, especially in systems
to the most recent version of the CANopen DS-301 communication where resources are at a premium.
3/26 profile enabling a secure and CANopen-conforming implementa-
tion of the project. SDO Server
To simplify connection of internal application data to the object The SDO Server offers an object directory and supports all defined
directory, there are exemplary entries already in the object direc- SDO transfer mechanisms such as expedited transfer, segmented
tory. Using these specifications, it is easy to create your own entries. transfer, and block transfer for up to two parallel SDO servers.
Functions
Overview of advantages XCP Professional contains all necessary functions for communica-
> Can be activated/deactivated in production operation ting with the XCP Master, such as:
> Easy to configure with PC-based tool > Synchronous data acquisition based on DAQ lists
> Low memory requirement and short execution times based > Read and write accesses
on scaling of the software component to your requirements > Initialization and switchover of the memory area for calibration
> Transport layers available for CAN, FlexRay and Ethernet data
> Compatible with MICROSAR BSW modules (AUTOSAR) > Support of time stamps
> Protection against unauthorized writing and reading in memory
Application Areas > Shutoff of XCP in production operation by a single function call
3/30 Automotive in-vehicle ECUs are measured and calibrated with the > Access protection by Seed & Key support
XCP Protocol (Universal Calibration Protocol) – the successor to CCP > Synchronous data stimulation (STIM) and Resume mode
(CAN Calibration Protocol). XCP was standardized by ASAM (Asso- > Flash and EEPROM programming
ciation for Standardization of Automation and Measuring Systems), > Communication mode: Block transfer
a process in which Vector played a leading role. By clearly differen- > Transmission of service request packets
tiating the Protocol Layer and Transport Layer, XCP is able to sup- > Support of AUTOSAR CRC modules
port many different bus systems: CAN, FlexRay and Ethernet. > Bit modification and short download
On the PC side, the CANape tool is used as the XCP master. Its > Configuration by GENy
counterpart in the ECU is the XCP slave. This is implemented by > Generation of an a2l file based on the ECU configuration
the XCP Professional software component. It not only contains all
ASAM functional content, but useful extensions as well. Synchronous Data Stimulation (STIM)
You can use XCP Professional together either with a conventional To optimize algorithms and parameters, you can use XCP over the
communication stack or in AUTOSAR systems. In either case, it is bus system to read a measured signal from the ECU (DAQ) and
unnecessary to modify the XCP software. If a software stack by a modify it with a simulation model (e.g. MATLAB). The re-com-
third-party producer is used, small modifications to the XCP puted value is then written back to the ECU (STIM). Reading and
Transport Layer (TL) may be necessary. Vector would be glad to writing are performed synchronously in a predefined time interval
assist you in this area. (Bypassing).
Training
In the framework of our training program, we can offer you
various training events and workshops for XCP in our class-
rooms or at your business site.
For more information on individual training events and dates
on the Internet go to: www.vector-academy.com
The key properties of CANape related to measurement and cali- Additional information can be found in the “ECU Calibration”
bration are: product catalog.
> 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
Operating Systems
4/1
osCAN
The real-time operating system based on the OSEK/VDX standard
Application Areas
Overview of advantages Due to its static operating system architecture, osCAN is small and
> Small, fast and resource-saving operating system core fast, and its use is beneficial wherever resources such as memory
> Short boot times and processing time are in short supply. osCAN is especially ideal
> Stack monitoring at runtime (deactivatable) when extremely short boot times are necessary.
> Internal fault trace (deactivatable)
> Component management for integration of sub-projects Functions
> Supplied as source code As a fully preemptive multitasking operating system, osCAN offers
> Quality process fulfills SPICE Level 3 priority-driven task management and a wide variety of synchro-
> Graphic configuration tool for easy configuration of the nization mechanisms. It can generate cyclic and singular time
operating system intervals as well as behave in an event-driven way. Its flexible
> Simplified execution time analysis of osCAN applications by interrupt strategy makes it possible to use system services even
supplied TimingAnalyzer within interrupt service routines.
> Available for many 8, 16, 32 and 64 bit microcontrollers In addition to functions defined in the standard, osCAN offers:
> Monitoring of stack utilization at runtime
osCAN is a preemptive real-time multitasking operating system > Internal tracing of system calls
4/2
with properties optimized for use on microcontrollers. Vector’s > Extended error checking at runtime
many years of experience in developing operating systems and > Clear and concise documentation of the configuration in HTML
drivers has made osCAN a small and robust operating system core. With the optional High Resolution Timer, you can implement reso-
It is certified to OSEK/VDX specification 2.2. This open standard lutions higher than 1ms for the timers, without simultaneously
of the automotive industry provides a foundation for long-term increasing interrupt load. Depending on the controller, resolu-
stability and availability. tions in the microseconds range are possible.
OPERATING SYSTEMS
Training
In the framework of our training program, we offer various
training events and workshops for osCAN in our classrooms
as well as at the business sites of our customers.
For more information on individual training events and dates
please visit: www.vector-academy.com
Supporting Tools
Complete solution from Vector The TimingAnalyzer design assistant simulates and computes
Vector provides you a completely tuned solution for devel- task execution times for you. The analysis is performed for each
oping ECUs. Along with the operating system, you get proto- task and each interrupt with the following parameters: Priority,
cols and drivers for CAN, LIN or FlexRay. For more detailed period, execution time and deadline. The graphic user interface
information, please refer to the relevant datasheets. offers clear and concise visualization of system behavior.
With the help of the CANoe osCAN Library, your application can
Configuration
be compiled into a DLL and integrated in a network simulation
An easy-to-use graphic configuration tool lets you define all oper-
under CANoe. This allows the application to be tested even before
ating system resources before compiling. To assure portability,
the availability of first hardware prototypes.
the configuration is saved in the standardized OIL format (OSEK
Implementation Language). Many emulators already offer the option of observing application
The configuration tool offers component management, which lets behavior on the operating system services level (OSEK Aware-
you implement sub-applications simultaneously in parallel pro- ness). osCAN supports the ORTI interface required for this.
cesses. Next, the sub-applications are integrate into a total appli-
Some UML and SDL modeling tools give you the option of configu-
cation. This enables short development times and spatially sepa-
ring models for use with an OSEK/VDX operating system. This is 4/3
rate developments.
possible, for example, with:
> MATLAB/Simulink from Mathworks
Properties:
> TargetLink from dSPACE
> Easy to operate graphic user interface
> Automatic checking for completeness and consistency
> Convenient system scaling Related Vector products:
> Component management > CANoe osCAN Library
> ORTI support > TimingAnalyzer
> High Resolution Timer
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.
4/5
TimingAnalyzer
Schedulability analysis/Trace visualization
The foundation for designing real-time systems is an analysis of A graphic diagram offers an intuitive overview of the timing. It
the schedulability of tasks (schedulability analysis). Systems that gives the application engineer a better understanding of program
employ a real-time operating system, such as the OSEK/VDX oper- processing in the ECU. It also considerably reduces the risk of
ating system or AUTOSAR OS, consist of tasks and interrupt service creating unreliable systems.
routines (ISR). Schedulability analysis shows whether a task or
ISR could miss its deadline when all circumstances are taken into Functions
considerations. In the analysis, the TimingAnalyzer studies the timing of both
tasks and ISRs. A special algorithm considers mutual interactions
Properties and Advantages resulting from use of the “resource” operating system service. In
The TimingAnalyzer simulates scheduling tables and computes the TimingAnalyzer you can input the time with which a task or
schedulability. The analysis is performed for each task and ISR ISR occupies the specific OSEK resource.
with the information: priority, period, execution time and dead-
line. Various algorithms from scheduling theory may be selected. The graphic representation simulates a possible task switching
In the default setting, the best algorithm is selected for a given sequence. The simulated schedule can be examined by zooming in
data record. and measuring time intervals. Bitmaps of the graphic diagram can
be saved for documentation purposes.
4/6
By using the TimingAnalyzer you can avoid the difficult and time-
consuming work involved in determining worst case timing situa- Special functions
tions, which is usually done by testing. The TimingAnalyzer is a > Schedulability analysis
tool for integrating familiar software components into a runnable > Graphic simulation of schedules
system. The time savings in terms of program creation and the > Import and display of emulator traces
test phase translate into cost savings as well.
Processor use is computed and output as a percentage. Processor
use is optimized by modifying calibration parameters, leading to
an efficient design that conserves on hardware resources.
Data Import
Besides 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 Areas
The TimingAnalyzer is an efficient tool for all development
departments that use real-time operating systems. Special atten-
tion was given to supporting OSEK/VDX and AUTOSAR real-time
operating systems and their applications.
Availability
The TimingAnalyzer is available in combination with the
OSEK/VDX-conformant operating system osCAN as well as the
AUTOSAR-conformant MICROSAR OS. 4/7
Scope of Delivery
> Graphic analysis tool for Windows NT/2000/XP/
Vista/Windows 7
> Documentation in electronic form
> Sample files ◆
EMBEDDED SOFTWARE
Vector
PIC24 Microchip CANoe osCAN Emulation Microsoft VisualC
Today, systems for downloading software to ECUs are used in all Data compression
phases of ECU development. Vector offers a number of software Automotive electronics is continuously becoming more complex,
solutions to meet various requirements: and so it requires more extensive software. Suitable data com-
> Flash Bootloader for CAN, LIN, FlexRay, MOST and Ethernet pression methods can be used to transport the increasing amo-
> Flashing via CCP/XCP unts of data more quickly on data buses; they reduce transmission
> Option for the Flash Bootloader: Security component times drastically. Vector offers optimized solutions for the Flash
> Option for the Flash Bootloader: Data compression Bootloader and flash tools.
> PC-based flash tool
Flash tools
Flash Bootloader Different data and diagnostic formats are used by different auto-
The Flash Bootloader lets you program ECUs with new software motive OEMs for programming ECUs. Meanwhile, ODX and ODX-F
within an in-vehicle network. In particular, when the ECU is have become established at some automotive OEMs as a standard
mounted at a hard to access location in the vehicle, the Flash data format for ECU programming.
Bootloader offers the advantage of updating ECU software with- To master the many different data and diagnostic exchange for-
out needing to remove the ECU. This results in the following capa- mats, Vector offers authoring and flash tools for specific use
bilities: cases in its CANdelaFlash and CANditoFlash products.
> Reprogramming during the development phase
> End-of-line programming Flashing CANopen ECUs
> Software updating in the Service area (After Sales) Vector also offers Flash Bootloaders for the special requirements
involved in flashing CANopen ECUs. Vector can adapt them to your
Reprogramming is performed via CAN, FlexRay, MOST or Ethernet platform in the context of project work.
5/0
utilizing a diagnostic protocol (UDS or KWP2000). A special LIN
Flash Bootloader is available for LIN Slave ECUs. EEPROM Emulation Module (EepM)
The EEPROM Emulation Module (EepM) lets you efficiently store
Programming via XCP/CCP nonvolatile data of any desired length in program or data flash
The use of XCP or CCP is an alternative to reprogramming with the memory. The module is called directly by the application. To save
Flash Bootloader. This variant is primarily used to optimize ECU on resources, the module can be used by either the application or
parameters. Since XCP/CCP programming is generally used in the the Flash Bootloader.
development phase, unlike the Flash Bootloader, security aspects
play a subordinate role here.
Security component
ECUs can only be reprogrammed if the ECU has been unlocked
beforehand with the help of a request/response (Seed/Key)
method. As soon as the ECU is unlocked, it can also be 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.
FLASHING
5/1
Flash Bootloader
Flashing via CAN, LIN, FlexRay, MOST and Ethernet
Functions
Advantages The component has a scalable security system containing the fol-
> Protects against unauthorized ECU access lowing cryptographic functions:
> Validates the download process
> Only authentic software from the supplier or automotive > Hash function (SHA-1 or RIPEMD-160)
OEM is flashable > Signature computation with H-MAC (Class C)
> Secure transmission by data encryption > RSA methods for public/private key (Class CCC)
> Symmetrical data encryption with AES (Class AAA)
Application areas
The Flash Bootloader offers the option of reprogramming ECUs via Signatures can be computed during ECU development with the
the bus system. To prevent unauthorized access, the Seed/Key supplied HexView tool. For production applications, use of
method is generally used. This type of protection is entirely suffi- CANdelaFlash is recommended. This tool creates ODX-F containers
cient for simple ECUs. that contain information on the security class and signatures. ◆
The flash tool reads the compressed flash data and transfers it to
the ECU’s Flash Bootloader via an OEM-defined flash process. The
received data is then decompressed in the Flash Bootloader.
Application areas
Data compression can be performed in all ECUs, regardless of the
microcontroller used. Data compression is an important tool when
larger quantities of data need to be downloaded (e.g. in the Info-
tainment area) or fixed time intervals are set (e.g. max. 3 mi-
nutes for programming an ECU). That is why most automotive
OEMs make provisions for the use of data compression in their
5/5
flash processes.
Functions
The Vector compression method is based on an optimized LZ77
method, which is especially well suited for the automotive ECU
environment. It enables a compression rate of 40–60 %, reducing
In recent years, flash memory has become more cost-effective access the stored data by identifiers that are predefined or flexi-
and faster than conventional EEPROMs. New microcontrollers are bly defined at runtime.
often offered without EEPROM memory and just have a larger
internal flash memory. Since writing to flash memory, unlike Special Functions
EEPROMs, is not by the byte but by the page, it is only possible to The EEPROM Emulation module is configurable and so it can be
achieve optimized utilization of the flash memory with the help of adapted to the requirements of the application. It enables:
an EEPROM emulation. > Simultaneous emulation of multiple EEPROMs
> Integration of different flash hardware
Overview of Advantages
> Usable for external and internal flash
> Usable for data and program flash Differences between EEPROMs and Flash Memory
> Conserves resources and optimizes flash lifetime Flash memories cannot be written byte-by-byte. Their smallest
> Possible to use EEPROM emulation module together with writing unit, known as a page, extends over a number of bytes. A
the Vector Flash Bootloader page cannot be overwritten directly. First, it must be erased
together with all of the pages of a sector (smallest erasing unit).
The page length and sector length are hardware-dependent, and
Application Areas sector lengths may also vary within a flash memory.
Flash memory cannot be erased or written in the same way as con-
ventional EEPROMs. EEPROM emulation in flash memory makes it Efficient Structuring of Nonvolatile Data
possible for an application to store changed nonvolatile data in a Essentially, the use of a flash memory requires that the data to be
flash memory, just as in a conventional EEPROM. stored is defined in so-called records. They are addressable by
5/6
unique identifiers, and besides the stored data they also contain
Functions management information. This information assures quick and reli-
The Vector EEPROM Emulation Module (EepM) manages predefined able read access to valid data. The application either defines the
flash areas by taking all hardware-specific constraints into con- length of a record either statically during software configuration
sideration. Reading and writing of changeable nonvolatile data or dynamically at runtime, depending on the configuration.
via the EepM is fully transparent to the application. It is easy to
Software
architecture of
the EepM
FLASHING
Resource optimization
by use of EepM from the
Vector Flash Bootloader
Flashing with CCP and XCP
Using the CCP/XCP protocol for flash programming
Flashing via XCP using a flash kernel Flashing via an XCP bootloader
FLASHING
5/9
EMBEDDED SOFTWARE
Controller Compiler Available for [1] Controller Compiler Available for [1]
AnalogDevices Renesas Electronics (NEC/Renesas)
BlackFin VusualDSP CAN 78k0 IAR CAN, LIN
Atmel H8S Renesas CAN
AVR IAR CAN, LIN M16C Renesas, IAR CAN
AVR32 IAR CAN M32C Renesas, IAR CAN
Freescale M32R Renesas CAN
DSP56F83xx Metrowerks CAN R32C IAR CAN
Cosmic, Metrowerks R8C Renesas, IAR CAN
HC08, MCS08 CAN, LIN
(Hiware)
SH2 Renesas CAN
HC12, Star12, Cosmic, IAR, Metro-
CAN
Star12x, MCS12xE werks (Hiware) Renesas (NEC),
V85x CAN, LIN, FlexRay
Green Hills, IAR
i.MX25 GNU CAN
STmicroelectronics
MAC71xx, MAC72xx ARM, IAR CAN
ST9 GNU CAN
DIABDATA Wind
MPC 55x, 56x, 5200 CAN
River, Metrowerks ST10 Tasking CAN
DIABDATA Wind STM8a Cosmic CAN
MPC 55xx, 56xx CAN, FlexRay
River
Fujitsu Texas Instruments
TI OMAP 59xx Texas Instruments CAN
16FX Fujitsu CAN
TMS320 Texas Instruments CAN
16LX Fujitsu CAN
Texas Instruments,
FR60 Fujitsu CAN TMS470 CAN
ARM
Jade GNU CAN Texas Instruments,
TMS570 CAN, FlexRay
ARM
Infineon
Toshiba
C16x (external
Tasking CAN
AMD-Flash) TLCS900 Toshiba CAN
Tricore GNU, Tasking CAN, FlexRay TX19 Green Hills CAN
XC16x Keil, Tasking CAN TX49 Green Hills CAN
XC2000 Tasking CAN
Microchip [1] Please contact Vector (embedded@vector.com) if your
controller is not on the list or if you need additional support for a
dsPIC24 Microchip C30 CAN
not listed bus system. In general CAN, LIN, FlexRay, Ethernet and
dsPIC33 Microchip C30 CAN MOST can be supported.
PIC18 Microchip, Hi-Tech CAN, LIN
Functions
Properties Overview CANdelaFlash supports the import and export to the standardized
> Import and Export of ODX Flash Containers ODX format completely. ODX Flash Containers can thereby be pre-
> Modularization of flash data pared at an early stage in the development process. These ODX
> Management of software revision levels and part numbers Flash Containers have become a standard for modern flash tools
> Administration of data for Flash ROMs used in development and production.
> Reuse of diagnostic descriptions from CANdelaStudio CANdelaFlash fits seamlessly into existing tool chains. In particu-
> Can be used by both vehicle manufacturers and suppliers lar it supports the development process with other Vector pro-
> Comfortable user interface ducts such as CANdelaStudio. Another advantage of CANdelaFlash
is that it supports modularization of flash data, e.g. post-flashing
Application Areas of individual ECU functionalities (gear shift programs, idle-speed
Today the development process for an ECU is very complex. While control, country variants, etc.).
previously just a few ECUs were “flashable” in the vehicle, in futu- CANdelaFlash offers a simple and easy-to-use interface. For
re all ECUs will have a flash capability. example, the organization of a CANdelaFlash document is shown
The large number of ECUs that are networked together in the vehi- in a tree view, and most entries are made via easy-to-use tables
cle, and their growing complexity and amount of programmable with intuitive input masks.
data will require management of the flash data for an assured
process. In the future the flashing of ECU sub-functionalities will Functions at a Glance:
also come to the forefront. > Assignment of software revision levels and part numbers
CANdelaFlash is a software tool designed to manage these > Assignment of the various software revision levels to specific
requirements. ECUs in the vehicle
5/10
CANdelaFlash should be used wherever process-assured flashing > Identification of valid target ECUs. Checking whether the
of ECU functionalities (full or partial) is required. It can be imple- session is valid for the ECU that has to be programmed.
mented in both ECU development at a supplier and in test vehicle > User-friendly acquisition and management of binary and
or preproduction development at the vehicle OEM. hexadecimal data for Flash ROMs (e.g. import of source files
in “Intel Hex” and “Motorola S-Record” formats)
> Use of templates for new CANdelaFlash documents Structure of the CANdelaFlash Data
> Creation and editing of sessions and data blocks The management and the acquisition of flash data are done com-
> User-friendly editing of the segments of a data block including fortably via the user interface in the following structure:
extensive consistency checks > Flash description:
> Grouping of sessions into so-called Flash Classes Reference to multiple ECUs (CANdelaStudio ECU-specific
> Cut, copy, and paste functions for objects of the CANdelaFlash descriptions; *.cdd files)
document > Base Session:
> Searching of the CANdelaFlash database for objects by their Optional definition of session defaults for a project
names > Sessions:
> Import and Export of the CANdelaFlash document into ODX 2.0 Session with list of data blocks. This is a list of jobs for upload/
and ODX 2.1 data format download (initial programming, reprogramming, partial repro-
> Import/export of embedded flash data from/to ODX gramming). The data blocks reference the flash data (reusable
> Creation and editing by authors, revision entries, and brief in different sessions) and they specify the segments of flash
descriptions data for upload/download.
> Interfacing to external tools by user-defined actions > Memory layouts:
> Plug-In interface for linking customer-specific security DLLs Description of the memory layouts of several ECUs
for CRC and signature calculation > Flash classes:
> Support of customized user settings User-defined organization of sessions in any desired number of
> Reuse of diagnostic data (from CANdelaStudio) flash classes
> Detailed recording of program sequences (Output Window) > Flash data:
> Read and write of PDX archives (Packaged ODX) Database of reusable flash data ◆
5/11
> Expanded format checking in attribute masks via specification
of regular expressions in the template
CANditoFlash 5.0
Easy Flashing in the Development Process and in End-of-Line Programming
The following functions are provided in flash job programming in System Requirements
CANape/CANdito: > Windows XP, Vista (32-bit version) or Windows 7 (32- and 64-bit
> OEM-specific flash job: Simple, problem-oriented library func- version)
tions for instancing and parameterizing diagnostic functions > Vector CAN hardware interfaces
> Easy access to flash parameters
> Convenient import of flash data
> Library is expandable (e.g. for import of customer-specific data)
Supported Protocols
> ISO 15765 Diagnostics on CAN
> ISO 14229 Unified Diagnostic Services on CAN (UDS)
Configuration dialog:
Flashing based on ODX-F data
Seminar or Workshop?
Vector offers seminars and workshops on Vector software tools as
well as the latest bus technologies and protocols at Vector Group
locations worldwide.
VectorAcademy seminars serve to communicate theoretical basics,
while workshops distinguish themselves through their applicability,
practical examples, and exercises.
Modularity
Trainings are partly constructed of several independent, one-day
modules designed to follow one another. Beginners and advanced
users can adjust their individual training program to suit their own
needs.
Customer-Specific Trainings
Additionally, 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: academy@de.vector.com
6/0 Vector Consulting Services: info@vector-consulting.de
Vector CANtech: academy@us.vector.com
Vector Scandinavia: academy@se.vector.com
Vector France: academy@fr.vector.com
Vector Japan: academy@jp.vector.com
Vector Great Britain: academy@uk.vector.com
Vector Korea: academy@kr.vector.com
Premises
We 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.
Katalog E Diagnose '10 02.02.2010 10:39 Uhr Seite 4/2
Germany
4/2
Vector Katalog Diagnose EN 04.02.2010 13:16 Uhr Seite 4/3
DIRECTIONS TO VECTOR
4/3
Katalog E Diagnose '10 02.02.2010 10:39 Uhr Seite 4/4
4/4
Katalog E Diagnose '10 02.02.2010 10:40 Uhr Seite 4/5
DIRECTIONS TO VECTOR
4/5
Katalog E Diagnose '10 02.02.2010 10:40 Uhr Seite 4/6
4/6
Your Contact
China
Vector Informatik GmbH
Shanghai Representative Office
Suite 605, Tower C,
Everbright Convention Center
No. 70 Caobao Road, Xuhui District
Shanghai 200235
P.R. CHINA
Tel.: +86 21 6432 53530
Fax: +86 21 6432 5308