ECU development with AUTOSAR” · General Information Your speaker today: Christian Runge Working...

© 2012 . Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.

V0.01 2012-09-27

AUTOSAR Webinar 2013-03-12

„ECU development with AUTOSAR”An introduction for AUTOSAR beginners


Slide: 2

Agenda

> General Information

Why AUTOSAR

Introduction to AUTOSAR

Vector AUTOSAR Solution

OEM Solutions

Characteristics of MICROSAR

General Information

Your speaker today:

Christian Runge

Working for the Vector Product Line Embedded Software as Senior Account Manager

MICROSAR, CANbedded, Flashing, Real-Time Operating Systems and related services

Contact:

Phone: +49 711 80670-3904

Email: [email protected]

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


Slide: 5

Agenda

General Information

> Why AUTOSAR



OEM Solutions



Slide: 6

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


Slide: 7

Why AUTOSARHistory Embedded Software at Vector

Diagnostics

OS

CAN + NM

FBL

LIN

Projects

FlexRay

MEM

1994 1998 2000 2002 2004 2006 2008 20101996 2012 2014

AUTOSAR 3

Safety

Smart Charging

Monitor & Debug

Ethernet/IP

OBD

Security

AUTOSAR 4 Vector was the first independent vendor of

Basic Software

2004: AUTOSAR Member2007: 1st AUTOSAR Release


Slide: 8

Why AUTOSARExample CANbedded Communication Stack

HIS (German: Hersteller Initiative Software) ('OEM software initiative')an interest group consisting of the car manufacturers Audi, BMW, DaimlerChrysler

HIS (German: Hersteller Initiative Software) ('OEM software initiative')an interest group consisting of the car manufacturers Audi, BMW, DaimlerChrysler


Slide: 9

Agenda

General Information

Why AUTOSAR

> Introduction to AUTOSAR


OEM Solutions



Slide: 10

Introduction to AUTOSARAUTOSAR Partnership


Slide: 11

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

>>> Basic Software

AUTOSAR Runtime Environment (RTE)

Application Layer

ComplexDrive

rs

Microcontroller

SYSDrivers

Memory Drivers

I/O Drivers

I/O Hardware

MEM

MEM

SYS

COM Drivers

CAN/LIN/FR

Communication

Services

System Services

Targets and GoalsIntroduction to AUTOSAR


Slide: 12

VFB

Virtual Function Bus

SWC1

SWC2 SWC3

ECU1

SWC1

SWC2

ECU2

SWC3

System Description*

Extract of System Description*ECU ConfigurationDescription (ECUC)*


Software Component Description*

*

SWC1 SWC2

Basic Software (BSW)

RTE

Complete SW functionality of the vehicle is defined as a system of SWCs... ..and distributed to ECUs

An extract is created for each ECU...

The ECU is configured based on the ECU Extract.

ECU1

SWC1

SWC2

AUTOSAR Workflow


Slide: 13


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

AUTOSAR Status


Slide: 14

Agenda

General Information

Why AUTOSAR


> Vector AUTOSAR Solution

OEM Solutions



Slide: 15


RTE ConfigurationBSW Configuration

DaVinciConfigurator Pro

ECU Monitoring and Debugging

CANoe.AMD

ECU-/System-Test

CANoe

Calibration

CANape

SWC Unit Test

DaVinciComponent Tester

SWC1

SWC2

SWC3

SWC1

SWC2

SWC3

SWC1


RTE

AUTOSAR ECU

SWC Detailed Design(RTE Configuration)

DaVinci Developer

Logical & SoftwareArchitecture Design

PREEvision

Development of Application Software

Virtual Integration Platform (VIP)

SWC2

AUTOSAR Toolset

S1 S2

S1 S2


Slide: 16

VFB

Virtual Function Bus

SWC1

SWC2 SWC3

ECU1

SWC1

SWC2

ECU2

SWC3

System Description*

Extract of System Description*ECU ConfigurationDescription (ECUC)*


Software Component Description*

*

SWC1 SWC2


RTE

Complete SW functionality of the vehicle is defined as a system of SWCs... ..and distributed to ECUs

An extract is created for each ECU...

The ECU is configured based on the ECU Extract.

ECU1

SWC1

SWC2

AUTOSAR Workflow

PR

EEvi

sion

PR

EEvi

sion

PR

EEvi

sion

DaV

inci

Dev

elop

er

DaV

inci

Dev

elop

erD

aVin

ci C

onfi

gu

rato

r P

ro


Slide: 17

Vector AUTOSAR SolutionWorkflow AUTOSAR 4.x

DBCLDF

Input files provided by OEMContains communicationinformation, neededfor the ECU

Software Component Description files

.xml Embedded Coder

TargetLink

.cdd/.odx

CANdela Diagnostic Data Other AUTOSAR tools

Fibex

.XML

ECU Extract of System Description provided by OEMContains system information, needed for the ECU

DaVinci Developer

PREEvision

DaVinci Configurator ProConfiguration of RTE + BSW

ECU Extract of System Description

ECU ConfigurationDescription

.xml

.xml

SystemDesc Conversion

Base ECUC Generation

Editing and

Generation

.c .hBSW module configuration header and code filesRTE header and code filesSWC header files


Slide: 18

Vector AUTOSAR SolutionMICROSAR Basic Software – Architecture


Slide: 19

Differences between MICROSAR 3 and MICROSAR 4

MIC

RO

SA

R L

IBS

CAL

CRC

E2E

Application

MIC

RO

SA

R O

S

MICROSAR RTE

MIC

RO

SA

R I

O

Complex

DriversMIC

RO

SA

R S

YS

MICROSAR COM

MIC

RO

SA

R M

EM

MIC

RO

SA

R C

AN

MIC

RO

SA

R L

IN

MIC

RO

SA

R I

P

MIC

RO

SA

R F

R

MICROSAR CAL MICROSAR EXT

Microcontroller

OS

COMM

DET

ECUM

SCHM

WDGM

WDGIF

NVM

MEMIF

EA

FEE

COM IPDUM NM PDUR

CANTP

CANNM

CANSM

CANIF

CANXCP

LINTP

LINSM

LINIF

FRTP

FRNM

FRSM

FRIF

SOAD

ETHXCP

IPBASE2

ETHIF

IOH

WAB

DRVEX

T3

CAN

TRCV

LIN

TRCV

FRTR

CV

GPT

DRV

WD

GD

RV

MCU

DRV

FLSD

RV

EEPD

RV

CAN

DRV

LIN

DRV

SPI

DRV

FRD

RV

ICU

DRV

PWM

DRV

AD

CD

RV

DIO

DRV

PORTD

RV

ETH

DRV

FRXCP

Project and servicesStandard Software

ETH

TRCV

ETHSM

1 Available extensions for AUTOSAR2 Includes all required modules according to RFC 3 Includes EEPEXT, FLSEXT, and WDGEXT

FRISOTP1

MIC

RO

SA

R M

OS

T1

MOST IF

MO

ST

DRV

1

DISP

NetworkServicesLibrary1

3rd Party Services

BSWM

E2E Protection Wrapper

IICD

RV

RAM

TST

MIC

RO

SA

R A

MD

XCP

DLT

DBG

MIC

RO

SA

R D

IAG

DCM

DEM

FIM J1939TP

LINNM

New relevant ASR4 modulesASR 4.0 already realized Modified seriously for ASR4

STBM

CSMCO

RET

ST

FLASH

TST



Slide: 20

Vector AUTOSAR SolutionMulticore Solution


Slide: 21

Vector AUTOSAR SolutionFlash Boot Loader

Vector is authorized FBL supplier for all OEMs using AUTOSAR

Extended Features

Multi processor, multiple memory devices

Pipelined Programming

Security

Gateway

Compression

…


Slide: 22

Agenda

General Information

Why AUTOSAR



> OEM Solutions



Slide: 23

OEM Solutions

SOP of a complete AUTOSAR solution (BSW + RTE)

2010 2011 2012 2013 2014 2015 2016 …

AUTOSAR 3.x

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

Current Status


Slide: 24

ApplicationM

ICR

OS

AR

OS

MICROSAR RTE

MIC

RO

SA

R I

O

Complex

DriversMIC

RO

SA

R S

YS

MICROSAR COM

MIC

RO

SA

R M

EM

MIC

RO

SA

R C

AN

MIC

RO

SA

R L

IN

MIC

RO

SA

R F

R

MICROSAR CAL3

Microcontroller

OS

COMM

CRC

DET

ECUM

SCHM

WDGM

WDGIF

NVM

MEMIF

EA

FEE

COM IPDUM NM PDUR

J1939TP1

CANTP

CANNM

CANSM

CANIF

LINTP2

LINSM

LINIF

FRTP

FRNM

FRSM

FRIF

IOH

WAB

GPT

DRV

WD

GD

RV

MCU

DRV

FLSD

RV

EEPD

RV

CAN

DRV

LIN

DRV

SPI

DRV

FRD

RV

ICU

DRV

PWM

DRV

AD

CD

RV

DIO

DRV

PORTD

RV

1Available extensions for AUTOSAR 3.x2Option included in LINIF3 Hardware dependent

Daimler SLP

Daimler HLPavailable for preferred platforms

Vector MICROSAR product

Service by Vector

Flash

Boot

Loader

Flash

Boot

Loader

Not used for OEM

DEMSC ROELITE

MICROSAR EXT3

DRVEX

T3

CAN

TRCV

LIN

TRCV

FRTR

CV

XC

P1

XCP

MIC

RO

SA

R D

IAG DCM

DEM

FIM

MIC

RO

SA

R I

P1

SOAD

IPBASE

ETHIF

ETHSM

ETH

TRCV

1

ETH

DRV

1

ETHXCP1FRXCP1

CANXCP1

Daimler SLP10 OverviewOEM Solutions


Slide: 25

BMW BAC4.0 OverviewOEM Solutions


Slide: 26

Application

MIC

RO

SA

R D

IAG

XC

P1

XCP

MICROSAR RTE

MIC

RO

SA

R I

O

Wrapper

MIC

RO

SA

R C

AN

MIC

RO

SA

R L

IN

MIC

RO

SA

R I

P1

MIC

RO

SA

R F

RCANTP

CANNM

CANSM

CANIF

CANXCP1

LINTP2

LINSM

LINIF

FRTP

FRNM

FRSM

FRIF

SOAD

ETHXCP

IPBASE

ETHIF

FRXCP1

ETHSM

MIC

RO

SA

R M

OS

T1

MOST IF

DISP

SMSCNet Services


1 Available extensions for AUTOSAR 3.12 Option included in LINIF

3rd PartyVector Product

3rd Party distributed by VW

Flash

Boot

Loader

MIC

RO

SA

R O

S

MIC

RO

SA

R S

YS

OS MIC

RO

SA

R M

EM

NVM

MEMIF

EA

FEE

MICROSAR COM

COM IPDUM NM PDUR

Complex

Drivers

BAP

KS


DRVEX

T1

CAN

TRCV

LIN

TRCV

1

FRTR

CV

GPT

DRV

WD

GD

RV

MCU

DRV

FLSD

RV

EEPD

RV

CAN

DRV

LIN

DRV

SPI

DRV

FRD

RV

ICU

DRV

PWM

DRV

AD

CD

RV

DIO

DRV

PORTD

RV

ETH

DRV

1

ETH

TRCV

1

MO

ST

DRV

1

Microcontroller

Wrapper

IOH

WAB

FIM

VW MQB Overview

COMM

CRC

DET

ECUM

SCHM

WDGM

WDGIF

E2E Lib

CryptoLib

BSWM

UDS

SDS

DEH

OEM Solutions


Slide: 27

Application

MIC

RO

SA

R D

IAG

XC

P1

XCP

MICROSAR RTE

MIC

RO

SA

R I

O

Wrapper

UDS

SDS

MIC

RO

SA

R C

AN

MIC

RO

SA

R L

IN

MIC

RO

SA

R I

P1

MIC

RO

SA

R F

RCANTP

CANNM

CANSM

CANIF

CANXCP1

LINTP3

LINSM

LINIF

FRTP

FRNM

FRSM

FRIF

SOAD

ETHXCP

IPBASE

ETHIF

FRXCP1

ETHSM

MIC

RO

SA

R M

OS

T1

MOST IF

DISP

SMSCNet Services


3rd PartyAUTOSAR Stack MLBevo

3rd Party distributed by Audi

MIC

RO

SA

R O

S

MIC

RO

SA

R S

YS

OS

COMM

CRC

DET

ECUM

SCHM

WDGM

WDGIF

MIC

RO

SA

R M

EM

NVM

MEMIF

EA

FEE

MICROSAR COM

COM IPDUM NM PDUR

Complex

Drivers

BAP

KS


DRVEX

T1

CAN

TRCV

LIN

TRCV

1

FRTR

CV

GPT

DRV

WD

GD

RV

MCU

DRV

FLSD

RV

EEPD

RV

CAN

DRV

LIN

DRV

SPI

DRV

FRD

RV

ICU

DRV

PWM

DRV

AD

CD

RV

DIO

DRV

PORTD

RV

ETH

DRV

1

ETH

TRCV

1

MO

ST

DRV

1

Microcontroller

Wrapper

DEH

IOH

WAB

E2E Lib

CryptoLib

FIM

AUTOSAR Modules Vector

BSWM

1 Available extensions for AUTOSAR 3.x2 BAM and CMDT Option available3 Option included in LINIF

Not used for OEM

Flash

Boot

Loader

Audi MLBevo OverviewOEM Solutions


Slide: 28

ApplicationM

ICR

OS

AR

OS

MICROSAR RTE

MIC

RO

SA

R I

O

Complex

Drivers

MIC

RO

SA

R S

YS

MIC

RO

SA

R D

IAG

MICROSAR COM

MIC

RO

SA

R M

EM

MIC

RO

SA

R C

AN

MIC

RO

SA

R L

IN

XC

P1

MIC

RO

SA

R I

P1

MIC

RO

SA

R F

R


Microcontroller

OS

COMM

DET

ECUM

SCHM

WDGM

WDGIF

DCM

DEM

FIM

XCP

NVM

MEMIF

EA

FEE

COM IPDUM NM PDUR

J1939TP1,2

LINTP3

LINSM

LINIF

FRTP

FRNM

FRSM

FRIF

SOAD

ETHXCP

IPBASE5

ETHIF

IOH

WAB

DRVEX

T1

CAN

TRCV

LIN

TRCV

1

FRTR

CV

GPT

DRV

WD

GD

RV

MCU

DRV

FLSD

RV

EEPD

RV

CAN

DRV

LIN

DRV

SPI

DRV

FRD

RV

ICU

DRV

PWM

DRV

AD

CD

RV

DIO

DRV

PORTD

RV

ETH

DRV

1

FRXCP1

ETH

TRCV

1

ETHSM

1 Available extensions for AUTOSAR 3.x2 BAM and CMDT Option available3 Option included in LINIF 4 Includes CAL, CPL and CRC5 Includes Socket, DHCP (Client), UDP, TCP, ICMP, ARP and IPV4

FRISOTP1

MIC

RO

SA

R M

OS

T1

MOST IF

MO

ST

DRV

1

DISP

NetworkServicesLibrary

FGA AUTOSAR Stack

Vector MICROSAR product

FGACDD

BSWMFlash

Boot

Loader

CRC

Service by Vector

CANTP

CANNM

CANSM

CANIF

CANXCP1

ClassB NM

FGA module Not used by FGA

OEM SolutionsFIAT FGA Overview


Slide: 29

OEM SolutionsVolvo Car AUTOSAR 4.x


Slide: 30

Agenda

General Information

Why AUTOSAR



OEM Solutions

> Characteristics of MICROSAR


Slide: 31

HW dependent modulesHW independent modules

SLP – Software License PackageHLP – Hardware License PackageSIP – Software Integration Package

MICROSAR Basic Software – SLP + HLP + SIP

SLP HLP

Configuration

Integration

Test

(OEM) Specification

Use Case

µC Derivative

Compiler Version/Optionen

xLP – Right of use

SIP

µC

SIP – Delivery



Slide: 32

Ready-to-Use

Order

SIP = Turn key delivery(faster and better tested)

Assemblyand test

Assembly by the customer

t

Supposed early delivery

Delivery of single components

Characteristics of MICROSARWhy buying a SIP?


Slide: 33


Tier1s profit from a powerful set of building blocks and get additionally anindividually tailored and tested product SIP (Software Integration Package)

Integration … of required modules properly configured … of 3rd party modules (by OEM and semiconductor vendor)

Test … of all modules in an integrated subsystem … on target hardware with target compiler … of our customer’s use case

Release of delivery based on … … OEM specific communication description … additional customer specific formats (ODX, cdd,…) … additional OEM requirements (Pre-configuration as agreed with OEM)

Quick Startup Startup manual for each OEM Reduction of configuration space for Tier1

Maintenance Individual SIP specific issue reporting Patch and update deliveries > 15 years

SIP


Slide: 34

Solution provided by the world market leader Solution for all OEMs available SPICE-3 quality

OEM specifics „ahead and beyond AUTOSAR“

Sophisticated memory solution („AUTOSAR++“)

High end configuration tool

Delivery & test optimized for HW and use case

Three MICROSAR releases per year

Warranty/liability related to single deliveries

Delivery related issue reporting

TÜV certified functional safety acc. AUTOSAR

Support of OEM specific workflows

total: 11 weeks/project/year

1 week/project/year

2 weeks/project/year


Tier1 savings:



1 week/project/year

Characteristics of MICROSARSavings


Slide: 35

Characteristics of MICROSARServices

Embedded Standard Software Technical Consulting

Engineering ServicesProduct Services

Extend of service

Customer specific projects

Training, Installation,

Support,Reviews

Coaching

Workshops,Concepts

System Functionsand Software Integration

CANbedded,MICROSAR

CANbedded,MICROSAR

CANbedded,MICROSAR

Complete ECU Software

CANbedded,MICROSAR

ExtendedIntegration

Package

CANbedded,MICROSAR

CANbedded,MICROSAR


Slide: 36


Vector provides standard software since 1995

> 50 OEM solutions supported > 100 μC / compiler pairs supported > 1000 deliveries per year

Vector supports AUTOSAR since 2004

contributing to specification 1st delivery of AUTOSAR 3 BSW in Mar.2008 > 200 serial production projects

Vector provides BSW+RTE for all OEMs using

AUTOSAR

all OEMs choosing a BSW supplier decided for Vector (Volvo AB, Daimler, Audi, Asian OEMs)

Vector is approved by BMW, Fiat, Volkswagen and Volvo Car

Vector provides a mature AUTOSAR solution

> 800 person years of engineering invested 1st SOP in 2010 most used solution in the world

MICROSAR - Vector‘s AUTOSAR Embedded Software


Slide: 37

Thank you for your attention.

For detailed information about Vectorand our products please visit

www.vector.com

Author:

Christian Runge

Vector Informatik GmbH

ECU development with AUTOSAR” · General Information Your speaker today: Christian Runge Working...

Documents

Transcript of ECU development with AUTOSAR” · General Information Your speaker today: Christian Runge Working...