Vector Webinar AUTOSAR Basics 20121009 en

ECU development with AUTOSAR An introduction for AUTOSAR beginners
Webinar 2012-10-09
2012 . Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V 0.01 2012-09-27
General Information
Your speaker today:
Marco Gerschek
Working for the Vector Product Line Embedded Software as Team Leader Sales MICROSAR, CANbedded, Flashing, Real-Time Operating Systems and related services Contact: Phone: +49 711 80670-3836 Email: marco.gerschek@vector.com
General Information
Duration: approx. 30 minutes Questions:

> > >
Please use the Q&A features of Webex Question will be answered after the presentation Or send us later on your questions
A link to the presented slides will be sent by e-mail to all registered participants after this event
Agenda
General Information > Why AUTOSAR Introduction to AUTOSAR Vector AUTOSAR Solution OEM Solutions Services related to MICROSAR
2012 . Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 4
Why AUTOSAR
The challenge:

E/E complexity is growing fast
Quantity of software is exploding

Many different hardware platforms are used Development processes and data formats are not harmonized
The main objective of AUTOSAR:
Improve software quality and reduce costs by re-use

Re-use of functions across carlines and across OEM boundaries Re-use of basic software
Re-use of development methods and tools
Why AUTOSAR
History Embedded Software at Vector
Security
Vector was the first independent vendor of Basic Software
OBD AUTOSAR 4 Ethernet/IP Monitor & Debug Smart Charging Safety AUTOSAR 3
MEM FlexRay Projects LIN FBL Diagnostics OS CAN + NM 1994

Slide: 6
2004: AUTOSAR Member 2007: 1st AUTOSAR Release
1996
1998
2000
2002
2004
2006
2008
2010
2012
2014
2012 . Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Why AUTOSAR
Example CANbedded Communication Stack
HIS (German: Hersteller Initiative Software) ('OEM software initiative') an interest group consisting of the car manufacturers Audi, BMW, DaimlerChrysler
Agenda
General Information Why AUTOSAR > Introduction to AUTOSAR Vector AUTOSAR Solution OEM Solutions Services related to MICROSAR
Introduction to AUTOSAR
AUTOSAR Partnership
Targets and Goals
Standardize Development Process and exchange formats >>> Methodology + Templates Standardize Functionality >>> Functional Interfaces Specify a clear interface between basic software modules and application >>> RTE Define open reference architecture for ECU software
System Services
Application Layer
AUTOSAR Runtime Environment (RTE)
MEM
Communic ation Services CAN/LIN /FR COM Drivers
I/O Hardware
Com plex Drive rs
SYS
MEM
>>> Basic Software
SYS Drivers
Memory Drivers
I/O Drivers
Microcontroller
AUTOSAR Workflow
Complete SW functionality of the vehicle is defined as a system of SWCs... SWC1 Virtual Function Bus SWC2 VFB SWC2 SWC3 System Description* ..and distributed to ECUs
ECU1
SWC1
ECU2
SWC3
Software Component Description*
An extract is created for each ECU...
The ECU is configured based on the ECU Extract. SWC1 SWC2
ECU1
SWC1
RTE
SWC2
Basic Software (BSW)

ECU Configuration Description (ECUC)*
Extract of System Description*

Slide: 11
AUTOSAR Status AUTOSAR
is a key enabler for high performance electronic systems

is a broadly used standard in Europe AUTOSAR 3.x:
First specification: 2007
Mature solution used for series production 2010ff

Adaptations necessary OEM-specific extensions
AUTOSAR 4.x:
First specification: 2009
First mature specification: 2012 (4.0.3) 4.0.3 is the right version for development start in 2012 New functions: safety, variant handling, Ethernet/IP, multicore,
Agenda
General Information Why AUTOSAR Introduction to AUTOSAR > Vector AUTOSAR Solution OEM Solutions Services related to MICROSAR
Vector AUTOSAR Solution

AUTOSAR Toolset
Logical & Software Architecture Design PREEvision
SWC2 SWC1 SWC3 SWC1 SWC3 SWC2
Calibration CANape
Development of Application Software Virtual Integration Platform (VIP)

S1 S2
ECU-/System-Test CANoe
SWC Detailed Design (RTE Configuration) DaVinci Developer
SWC1
SWC2 RTE
SWC Unit Test DaVinci Component Tester
RTE Configuration BSW Configuration DaVinci Configurator Pro
Basic Software (BSW) AUTOSAR ECU

S1 S2
ECU Monitoring and Debugging CANoe.AMD

AUTOSAR Workflow
Complete SW functionality of the vehicle is defined as a system of SWCs... SWC1 PREEvision Virtual Function Bus SWC2 VFB SWC3 ..and distributed to ECUs
ECU1
SWC1 SWC2
ECU2
PREEvision
SWC3
Software Component Description*
System Description* DaVinci Developer DaVinci Configurator Pro
An extract is created for each ECU... PREEvision DaVinci Developer
The ECU is configured based on the ECU Extract. SWC1 SWC2
ECU1
SWC1 SWC2
RTE
Basic Software (BSW)
ECU Configuration Description (ECUC)*
Extract of System Description*

Slide: 15

Workflow AUTOSAR 4.x
PREEvision
DaVinci Developer .XML

ECU Extract of System Description provided by OEM
Contains system information, needed for the ECU
DBC
LDF
Input files provided by OEM
.xml
Software Component Description files
Embedded Coder TargetLink
Fibex
Contains communication information, needed for the ECU
DaVinci Configurator Pro

Configuration of RTE + BSW
SystemDesc Conversion
.xml
ECU Extract of System Description
.c
.h
RTE header and code files SWC header files BSW module configuration header and code files
Editing and
Generation
.c .h
.cdd/ .odx
CANdela Diagnostic Data
Base ECUC Generation .xml

ECU Configuration Description
Other AUTOSAR tools

MICROSAR Basic Software Architecture

MICROSAR Safe - Introduction
The following slides shall give an overview about Vectors AUTOSAR Basic Software to be used in safety related ECUs Assumptions

ECU contains SW that fulfills safety requirements: ASIL Software ECU contains SW that is developed acc. lower ASIL than the Safety Software: QM Software
The general considerations can be carried over from this simplified example to more complex systems with different ASILs (e.g. QM + ASIL-B + ASIL-D)
Goal
Find an optimal architecture to minimize the amount of software that has to be developed acc. to the highest ASIL
Avoid ASIL lift-up

MICROSAR Safe - Introduction
ECU Safety Concept Functional Safety Requirements for ECU SW
Safety Software
ASIL Software needs to have a sufficiently low rate of systematic failures - ensured by measures like
process & development methods and

additional safety mechanisms (redundancy / plausibility-checks) in case of complex algorithms
as defined in ISO 26262 Part 6

MICROSAR Safe - Safety Software is Object to interference Threats of other elements Functional Safety Requirements for ECU SW
ECU Safety Concept
1. Memory 2. CPU Time 3. Communication
random faults syst. faults
Safety Software
syst. faults
HW
QM Software
Freedom from Interference has to be ensured

MICROSAR Safe - Options to ensure Freedom from Interference
ASIL Software protects itself against interference 2. Defense Additional mechanisms block/detect interference

Project specific qualification 1. Qualification
SafeContext SafeWatchdog SafeCOM
3. Barriers
Safety Software
random faults syst. faults
syst. faults
HW
QM Software
4. Silence
QM Sub-elements do not interfere with ASIL sub-elements
SilentBSW

MICROSAR Safe Modules - Cooperation TTTech & Vector
Agenda
General Information Why AUTOSAR Introduction to AUTOSAR Vector AUTOSAR Solution > OEM Solutions Services related to MICROSAR
OEM Solutions
Current Status
SOP of a complete AUTOSAR solution (BSW + RTE)
2010 AUTOSAR 3.x 2011 2012 2013 2014 2015 2016
AUTOSAR 4.x
AUTOSAR 3.x is used in serial production projects by: Audi & Volkswagen BMW Daimler Fiat / Chrysler Volvo Trucks AUTOSAR 4.x is used in serial production projects by: BMW Volvo Car Use of AUTOSAR 4.x is announced by Ford GM PSA Toyota
OEM Solutions
Daimler SLP10 Overview
Application
MICROSAR RTE
MICROSAR DIAG COMM CRC MICROSAR SYS MICROSAR COM DCM NVM COM MICROSAR MEM DEM IPDUM NM PDUR MICROSAR IO DEMSC ROELITE
Flash
Boot Loader MICROSAR OS
DET ECUM SCHM WDGM WDGIF
MEMIF
J1939TP1
LINTP2 MICROSAR LIN MICROSAR FR MICROSAR CAN CANXCP1 CANTP CANNM CANSM CANIF
MICROSAR IP1
FIM
FRTP FRNM
SOAD IPBASE ETHSM ETHIF
IOHWAB
FRXCP1
ETHXCP1
OS
EA
Complex Drivers
LINSM
XCP1
XCP FEE
FRSM
FRIF
LINIF
Flash
WDGDRV CANDRV GPTDRV EEPDRV FLSDRV
MICROSAR CAL3
PORTDRV ETHDRV1 PWMDRV DRVEXT3 MCUDRV ADCDRV DIODRV ICUDRV LINDRV SPIDRV FRDRV
MICROSAR EXT3
ETHTRCV1 CANTRCV LINTRCV FRTRCV
Boot
Loader
Microcontroller
Daimler SLP Daimler HLP Vector MICROSAR product Service by Vector Not used for OEM
1 2
Available extensions for AUTOSAR 3.x Option included in LINIF Hardware dependent
available for preferred platforms
OEM Solutions
BMW BAC4.0 Overview
OEM Solutions
VW MQB Overview
E2E Protection Wrapper
Application
MICROSAR RTE
Crypto Lib E2E Lib COMM MICROSAR SYS CRC DET ECUM BSWM SCHM XCP1 WDGM WDGIF MICROSAR DIAG
Wrapper UDS SDS MICROSAR MEM Wrapper NVM
MICROSAR COM KS
COM
IPDUM
NM
PDUR
BAP
MEMIF
MICROSAR CAN
MICROSAR LIN
Flash MICROSAR OS Boot Loader
LINTP2 MICROSAR FR
MICROSAR IP1
DEH
MOST IF
IOHWAB
CANXCP1 CANTP CANNM CANSM CANIF MICROSAR CAL

MOST DRV1
FRXCP1 FRTP FRNM FRSM FRIF
ETHXCP
MICROSAR MOST1
MICROSAR IO
Complex Drivers
OS
EA
FIM
LINSM
DISP
XCP
FEE
LINIF
SMSC Net Services
MICROSAR EXT
ETHTRCV1 PORTDRV LINTRCV1 CANTRCV PWMDRV DRVEXT1 ADCDRV DIODRV ICUDRV FRTRCV SPIDRV
WDGDRV
Microcontroller
Vector Product 3rd Party 3rd Party distributed by VW
1 2
ETHDRV1
MCUDRV
CANDRV
GPTDRV
EEPDRV
FLSDRV
LINDRV
FRDRV
Available extensions for AUTOSAR 3.1 Option included in LINIF
OEM Solutions
Audi MLBevo Overview
E2E Protection Wrapper
Application
MICROSAR RTE
Crypto Lib E2E Lib COMM MICROSAR SYS CRC DET ECUM BSWM SCHM XCP1 WDGM WDGIF MICROSAR DIAG
Wrapper UDS SDS MICROSAR MEM Wrapper DEH NVM
MICROSAR COM KS
COM
IPDUM
NM
PDUR
BAP
MEMIF
MICROSAR CAN
MICROSAR LIN
LINTP3 MICROSAR FR
MOST IF
IOHWAB
CANXCP1 CANTP CANNM CANSM CANIF MICROSAR CAL

MOST DRV1
FRXCP1 FRTP FRNM FRSM FRIF MICROSAR IP1
ETHXCP
MICROSAR MOST1
MICROSAR IO
Complex Drivers
OS
EA
FIM
LINSM
DISP
XCP
FEE
LINIF
SMSC Net Services
MICROSAR EXT
ETHTRCV1 PORTDRV LINTRCV1 CANTRCV PWMDRV DRVEXT1 ADCDRV DIODRV ICUDRV FRTRCV SPIDRV
WDGDRV
Microcontroller
AUTOSAR Stack MLBevo AUTOSAR Modules Vector 3rd Party 3rd Party distributed by Audi
ETHDRV1
MCUDRV
CANDRV
GPTDRV
EEPDRV
FLSDRV
LINDRV
FRDRV
Not used for OEM
1 2 3
Available extensions for AUTOSAR 3.x BAM and CMDT Option available Option included in LINIF
OEM Solutions
FIAT FGA Overview (II)
Application
MICROSAR RTE
MICROSAR DIAG COMM DET MICROSAR SYS ECUM BSWM SCHM CRC XCP1 WDGM WDGIF XCP FEE MICROSAR COM DCM NVM COM IPDUM NM PDUR FGACDD
DEM MICROSAR MEM MEMIF J1939TP1,2 LINTP3 MICROSAR FR CANXCP MICROSAR CAN EA CANTP CANNM
ClassB NM
1
FIM
MICROSAR LIN
MICROSAR IP1
FRTP FRISOTP1 FRNM FRSM FRIF
MOST IF
SOAD IPBASE5 ETHSM ETHIF
IOHWAB
FRXCP1
ETHXCP
MICROSAR MOST1
MICROSAR IO
Complex
Drivers
OS
LINSM
DISP
CANSM CANIF
LINIF
Network Services Library
MICROSAR CAL
MOST DRV1
MICROSAR EXT
ETHTRCV1 PORTDRV LINTRCV1 CANTRCV PWMDRV DRVEXT1 ADCDRV DIODRV ICUDRV SPIDRV FRTRCV
WDGDRV
Microcontroller
1
ETHDRV1
MCUDRV
CANDRV
GPTDRV
EEPDRV
FLSDRV
LINDRV
FRDRV
Available extensions for AUTOSAR 3.x BAM and CMDT Option available Option included in LINIF Includes CAL, CPL and CRC Includes Socket, DHCP (Client), UDP, TCP, ICMP, ARP and IPV4
FGA AUTOSAR Stack Vector MICROSAR product
FGA module Service by Vector
Not used by FGA
2 3 4 5
Agenda
General Information Why AUTOSAR Introduction to AUTOSAR Vector AUTOSAR Solution OEM Solutions > Services related to MICROSAR
Services related to MICROSAR

Overview
Training, Installation, Support, Reviews

CANbedded, MICROSAR
Coaching
Workshops, Concepts
Extended Integration Package
System Functions and Software Integration
Complete ECU Software
Extend of service
CANbedded, MICROSAR CANbedded, MICROSAR CANbedded, MICROSAR
CANbedded, MICROSAR
CANbedded, MICROSAR
Customer specific projects
Embedded Standard Software Product Services
Technical Consulting Engineering Services
Great view from the top worth climbing up!
Legacy
Zugspitze
Slide: 34
Mount Everest
Webinar Series
The webinar series about AUTOSAR (http://www.vector.com/vi_autosar_webinars_en.html):

2012-10-09 ECU development with AUTOSAR - An introduction for AUTOSAR beginners 2012-10-16 Introduction to the AUTOSAR Method for ECU development 2012-10-23 AUTOSAR Configuration Process - How to handle 1000s of parameters 2012-10-30 Reliable Testing of AUTOSAR ECUs (in preparation) 2012-12-10 MICROSAR Safe: AUTOSAR basic software for safety-relevant ECUs (ISO 26262) Various Webinars on MICROSAR OS the AUTOSAR operating system from Vector http://www.vector.com/vi_operatingsystems_webinars_en.html
Registration to the upcoming Webinars and the list of recorded Webinars: http://www.vector.com/vi_webinars_en.html The overview of Vectors training services: http://www.vector.com/vi_training_en.html
35
Thank you for your attention. For detailed information about Vector and our products please visit www.vector.com Author: Marco Gerschek Vector Informatik GmbH

Vector Webinar AUTOSAR Basics 20121009 en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vector Webinar AUTOSAR Basics 20121009 en

Uploaded by

Copyright:

Available Formats

ECU development with AUTOSAR An introduction for AUTOSAR beginners

Your speaker today:

Duration: approx. 30 minutes Questions:

E/E complexity is growing fast

Quantity of software is exploding

The main objective of AUTOSAR:

Improve software quality and reduce costs by re-use

Re-use of development methods and tools

Vector was the first independent vendor of Basic Software

MEM FlexRay Projects LIN FBL Diagnostics OS CAN + NM 1994

2004: AUTOSAR Member 2007: 1st AUTOSAR Release

AUTOSAR Runtime Environment (RTE)

Communic ation Services CAN/LIN /FR COM Drivers

Com plex Drive rs

>>> Basic Software

Software Component Description*

An extract is created for each ECU...

The ECU is configured based on the ECU Extract. SWC1 SWC2

Basic Software (BSW)

Extract of System Description*

is a key enabler for high performance electronic systems

First specification: 2007

Mature solution used for series production 2010ff

First specification: 2009

Vector AUTOSAR Solution

Development of Application Software Virtual Integration Platform (VIP)

SWC Detailed Design (RTE Configuration) DaVinci Developer

SWC Unit Test DaVinci Component Tester

RTE Configuration BSW Configuration DaVinci Configurator Pro

Basic Software (BSW) AUTOSAR ECU

ECU Monitoring and Debugging CANoe.AMD

Vector AUTOSAR Solution

Software Component Description*

System Description* DaVinci Developer DaVinci Configurator Pro

An extract is created for each ECU... PREEvision DaVinci Developer

The ECU is configured based on the ECU Extract. SWC1 SWC2

Extract of System Description*

Vector AUTOSAR Solution

DaVinci Developer .XML

Input files provided by OEM

Embedded Coder TargetLink

Contains communication information, needed for the ECU

DaVinci Configurator Pro

Base ECUC Generation .xml

Other AUTOSAR tools

Vector AUTOSAR Solution

Vector AUTOSAR Solution

Avoid ASIL lift-up

Vector AUTOSAR Solution

process & development methods and

as defined in ISO 26262 Part 6

Vector AUTOSAR Solution

ECU Safety Concept

1. Memory 2. CPU Time 3. Communication

random faults syst. faults

Freedom from Interference has to be ensured

Vector AUTOSAR Solution

Project specific qualification 1. Qualification

SafeContext SafeWatchdog SafeCOM

random faults syst. faults

QM Sub-elements do not interfere with ASIL sub-elements

Vector AUTOSAR Solution

DET ECUM SCHM WDGM WDGIF