why autosar - vector

V0.1 | 2019-07-09

Why AUTOSAR

2

u Motivation for AUTOSAR

AUTOSAR roadmap and history

Vector and AUTOSAR

Advantages of MICROSAR

Agenda

3

Growing E/E Complexity

Motivation for AUTOSAR

1975 1985 2005 20151995

Electronic Injection control

Cruise Control

Electronic Injection control

Cruise Control

Gearbox ControlTraction ControlAnti Lock Breaks

Gearbox ControlTraction ControlAnti Lock BreaksElectronic Injection controlCruise Control

AirbagsElectronic Stability ControlActive Body ControlAdaptive Cruise ControlEmergency Call

AirbagsElectronic Stability ControlActive Body ControlAdaptive Cruise ControlEmergency CallGearbox ControlTraction ControlAnti Lock BreaksElectronic Injection controlCruise Control

Adaptive headlightsActive steeringCurve warningStop and GoLane Keeping assistanceAutomated ParkingCollision mitigationElectronic Break ControlCar 2 Car communicationTele-diagnosticsSoftware updates over the air

4

Quantity of Software rising very steeply


1990 2000 2015 2020

Single Electronic

Control Unit

Multiple Electronic

Control UnitsDomain Control Units

*In 2010, some vehicles had about 10 million SLOC and

by 2016 this expanded by a factor of 15, to roughly 150 million lines*McKinsey&Company Report Feb’18‘Rethinking car software and electronic architecture’

HPC (High Performance Computing )

CAN MOST LIN FLEXRAY ETHERNET

Multicore8 Bit 16 bit 32 bit 64 bit

5

Hardware / Software Platforms


Multicore

u Many different hardware platforms are used

u Embedded systems traditionally do not support full hardware abstraction

u Limited modularity of the software

u Poor reusability: Software must often be rewritten from scratch when hardware (processor type) is changed

u Variability: Suppliers have to support a large variety of OEMs and vehicle platform variants with their software

Hardware

Software

7

AUTOSAR Slogan


Two different AUTOSAR statements:

“Cooperate on standards – compete on implementation”

Hardware

Software

Hardware

Software

8

Objectives


u Serviceability over the entire product life cycle

u Software updates and upgrades over the entire life of a vehicle

u Abstraction of hardware from software, making development more flexible.

u Shift development activities from implementation to configuration

u Improvement in software quality by standardized BSW

u Competition is focused onto OEM-relevant features

u Reusability of functions across vehicle networks and across OEM boundaries.

9

Objective


AUTOmotive Open System ARchitecture

u Improve software quality and reduce costs by RE-USE

u Re–use of functions across carlines and across OEM boundaries

u Re–use of development methods and tools

u Re–use of basic software

10

Standardization


Interfaces MethodologyExchange Formats

11

Layered View: Simplified


Run Time Environment

Application Layer

Complex(Device)

Drivers/ CDD

Microcontroller

Service Layer

ECU Abstraction Layer

Microcontroller Abstraction Layer

12

Layered View: Detailed


Application

AUTOSAR Runtime Environment (RTE)

ComplexDeviceDrivers

I/OHardware

Abstraction

Comm.Services

MemoryServices

Comm.Hardware

Abstraction

MemoryHardware

Abstraction

SystemService

OnboardDevice

Abstraction

Micro-contoller

Drivers

MemoryDrivers

Comm.Drivers

I/ODrivers

Microcontroller


ECU AbstractionLayer

ServiceLayer

13

Standardization of Interfaces


ECU Hardware

RTE

ActuatorSoftware

Component

AUTOSARInterface

ApplicationSoftware

Component

SensorSoftware

Component

ApplicationSoftware

Component

..............

AUTOSARSoftware

Basic Software

StandardizedInterface

AUTOSARInterface

AUTOSARInterface

AUTOSARInterface

MicrocontrollerAbstraction

StandardizedAUTOSARInterface

Services


ECUAbstraction

AUTOSARInterface


ComplexDeviceDrivers

AUTOSARInterface


Communication



OperatingSystem

Sta

nd

ard

ize

dIn

tefa

ce

AUTOSARSoftware

Component

Interface

ECUFirmware

StandardSoftware

Source: http://www.autosar.org

14

Standardization of Exchange Formats


BUS Protocols

LDF

DBC

FIBEX

DBC

FIBEX

System Description/ECU Extract

(AutosaR XMLformat)

(AutosaR XML format)

ECUC Configuration

ECUC Configuration

ECUC Configuration

ECUC Configuration

ECUC Configuration

16

Standardization of Methodology


VFB

Virtual Function Bus

SWC1

SWC2 SWC3

Software Component Description*

SW functionality of the vehicle is defined as a

system of SWCs ...

ECU1

SWC1

SWC2

ECU2

SWC3

System Description*

… and mapped to ECUs

An extract is created for each

ECU...

ECU1

SWC1

SWC2

Extract of System Description*ECU Configuration

Description (ECUC)* *

SWC1 SWC2

Basic Software (BSW)

RTE

The ECU is configured in detail

17

AUTOSAR Workflow with OEM and TIER1


u Interface between OEM* and TIER1*: ECU Extract of System Description (ECUEX)

u OEM creates ECUEX based on vehicle system design

u TIER1 configures AUTOSAR ECU based on ECUEX

TIER1xml

ECU Extract of System

Description

OEM

*Note: “OEM” and “TIER1” may also be organizational units within one company (“System Responsible” vs. “ECU responsible”)

18

Objectives - Achieved


u Reusability of functions over different vehicles.

Function Library

Seat Adjustment A

Seat Adjustment B

Lighting

Seat Heating

Air Conditioning

Vehicle A

Code Generation

Vehicle B

Hardware Topology

Distributed System

Software Configuration

19


u AUTOSAR roadmap and history

Vector and AUTOSAR


Agenda

20


(AUTomotive Open System ARchitecture)

is a worldwide development partnership of car manufacturers, suppliers and other companies from the electronics, semiconductor and software industry.

21

AUTOSAR Partnership


Core Partners

Development Partners

Associate Partners

Premium Partners

Generic TIER 1

Attendees

Tools and Services

Semi-conductor

Standard Software

Vector Informatik GmbH

22

AUTOSAR Partnership


2010.10.19: up-to-date status see www.autosar.org

http://www.autosar.org/

23

History


u AUTOSAR 2.0

u specifications on components (BSW and RTE)

u AUTOSAR 2.1

u includes specifications on development methodology and templates

u first descriptions for application interfaces (body and interior electronics)

u AUTOSAR 3.0

u > 20 compositions from the body, powertrain, and chassis domain

u Specifications of standardized application interfaces (powertrain, chassis domain)

u harmonized the concept for wakeup of ECUs and startup of networks

u state managers for the bus systems CAN, LIN, and FlexRay added

u AUTOSAR 3.1

u OBDII (new revisions of the DCM, DEM, FIM specifications,…)

Release 2.090 files

Release 2.1120 files

Release 3.0 Release 3.1141 files

Release 4.0183 files

2006-05 2007-03 2008-05 2008-09 2009-122002-08

Initialdiscussions

Future

Maintenance

existing Releases

24

History


u AUTOSAR 4.0 Rev1 (2009-12)

u Functional Safety (Memory Partitioning, Time Determinism, Program Flow Monitoring, E2E, BSWM Defensive Behavior, Dual µC, E-Gas Monitoring)

u Architectural Improvements (Error Handling, Multi Core, Boot loader Interaction)

u RTE enhancement (Triggered Events, Integrity and Scaling at Ports, API Enhancement)

u COM (LIN 2.1 Spec, FR 3.0 Spec , FlexRay ISO TP, XCP for ASR, Large Data Types, TCP/IP + DoIp, J1939Tp, TTCAN)

u Functional (NM coordination, ASR Scheduler)

u Conformance Test specifications (CT Specs, only Rev1 and Rev2, but not >Rev2)

u AUTOSAR 3.2 Rev1 (2011-05)

u Partial Networking

u Robustness Features (state manager modules)

u Improvement of error handling (e.g. production vs. development errors)

u Back-porting of AUTOSAR 4.0 features into AUTOSAR 3.2> Parts of the Safety Concept (E2E communication protection) > Extended CDD Concept > BSW Mode Manager > FlexRay ISO TP

Release 4.0Rev1

Release 4.0Rev2

2009-12 2011-04

Future

Maintenance

existing Releases

Release 3.2Rev1

2011-05

Release 4.0Rev3

2012-01

Release 3.2Rev2

2012-06

Release 4.1Rev1

2013-03

Release 4.2Rev1

2014-10

Release 4.2Rev2

2014-07

26



u Vector and AUTOSAR


Agenda

27

History/Facts

Vector and AUTOSAR

u History

u AUTOSAR Premium Member since 2004

u Support AUTOSAR 3 solution since 2008

u Support AUTOSAR 4 solution since 2013

u Facts

u Contribution in 16 work packages

u More than 1500 person years of engineering invested

u 1st delivery of AUTOSAR 3 BSW in Mar.2008 and 1st SOP in 2010

u > 500 serial production projects

u Most used solution in the world

u More than 250 engineers are working on Vector AUTOSAR solution

2004 2006 2008 2010 2012 2014 2016

AUTOSAR Premium Member

AUTOSAR 3

AUTOSAR 4

2018

28



Vector and AUTOSAR

u Advantages of MICROSAR

Agenda

29

MICROSAR – The Vector Solution for AUTOSAR ECU Software


RTE

Service Layer

ECU Abstraction Layer


u MICROSAR Consists of RTE and Basic Software Modules

u Covers all aspects of the AUTOSAR Standard

u Many Extensions and Add-Ons.

30

MICROSAR Basic Software at a glance


V4.3

31

MICROSAR Basic Software at a glance


V4.3

32

The MICROSAR Solution consists of packages that contain the

BSW ModulesContent

MICROSAR MCAL Driver for driving the microcontroller periphery

MICROSAR CAN Basic software modules for CAN communication

MICROSAR COM Basic software modules for network-independent communication and gateways

MICROSAR EXT Driver for driving external chips

MICROSAR FR Basic software modules for FlexRay communication

MICROSAR DIAG Basic software modules for diagnostics

MICROSAR IO Interface between the microcontroller periphery and the application

MICROSAR AVB Basic software modules for Audio/Video communication via Ethernet

MICROSAR AMD Monitoring and debugging of application and MICROSAR BSW

… …

… …

MICROSAR Basic Software Packages


33

u Full range of AUTOSAR BSW modules

u Available for production use

u Available for AUTOSAR 4.x and 3.x

u Safety-relevant projects up to ASIL-D

u With security features according to AUTOSAR 4.3

u User-selectable configuration (pre-compile, link-time or post-build)

u Supports multiple ECUs for many platforms incl. multicore microcontrollers

Vector Product for Classic AUTOSAR


MICROSAR

34

Features Recently Developed


MICROSAR4

u BSW-Split Option

u Allows Ethernet Stack to be mapped to a dedicated core

u Software Download (Over-the-air)

u Allows flash image download at application runtime

u Interaction with the Vector Bootloader for image activation

u Solution available for several OEMs

u Security

u AUTOSAR 4.3 Security Solution (incl. CSM, SECOC, CRYIF, CRYPTO)

u Key- and Freshness Value Management available for all relevant OEMs

u vHSM: execution of algorithm on a dedicated crypto core

u SOME/IP Transport Protocol

u Smart Charging

u Protocol ISO15118 BPT (Bi-directional Power Transfer)

u Protocol ISO15118 WPT (Wireless Power Transfer)

u ETH

u support of QBV according IEEE802.1

u support of RTP (Realtime Transport Protocol)

MICROSAR

35

Features Under Development


MICROSAR4

u vHSM Firmware Update

u Mirroring according to AUTOSAR 4.4

u CAN-CAN

u CAN-LIN

u ETH: SJA1105Q SRP Brige (Stream Reservation Protocol)

u Optimized message routing in PduR

MICROSAR

19Q3 19Q4

2019

20Q1 20Q219Q219Q1

2020

20Q3

36

Features Coming Next


MICROSAR4

u Secure communication using IPSec and IKIv2

u ECU authentication according to IEEE802.1x

u AUTOSAR 4.4 KeyM (certificate parsing)

MICROSAR

19Q3 19Q4

2019

20Q1 20Q219Q219Q1

2020

20Q3

37

AUTOSAR Workflow


VFB

Virtual Function Bus

SWC1

SWC2 SWC3

Software Component Description*

Complete SW functionality of the

vehicle is defined as a system of

SWCs...

ECU1

SWC1

SWC2

ECU2

SWC3

System Description*

… and distributed to ECUs

An extract is created for each

ECU...

ECU1

SWC1

SWC2

Extract of System Description*ECU Configuration

Description (ECUC)**

SWC1 SWC2


RTE

The ECU is configured based on the ECU Extract.

PR

EEvis

ion

DaV

inciD

evelo

per

DaV

inciC

on

fig

urato

r P

ro

PR

EEvis

ion

DaV

inciD

evelo

per

PR

EEvis

ion

38

Complete tool chain for all phases of the development



RTE

Application Software Development

PREEvision

DaVinci Developer

SWC Design

vVIRTUALtarget pro

SWC Execution and Test

ECU SW Integration

DaVinci Configurator Pro

vVIRTUALtarget basic

BSW/RTE Configuration

Virtual Integration

Application Software Verification

CANoe & VT System

vVIRTUALtarget pro

SWC Verification in Virtual Environment

SWC Verification within Real ECU

AUTOSAR ECU/System

AUTOSAR ECU/System

AUTOSAR ECU

System Design

PREEvision

CANdelaStudio

Architecture and Communication Design

Diagnostics Design

SWC1 SWC3

SWC2

SWC1 SWC3

SWC2

SWC1 SWC2ECU SW Verification

CANoe.AMD

ECU Monitoring and Debugging

System Verification

CANape

ECU Calibration

CANoe & CANoe.DiVa

Verification of Network Communication and Diagnostic Behavior

39

Workflow for ECU development


DaVinciConfigurator ProProject

Setup and Update

ECU-C

BSW/RTEConfiguration,SWC Integration

LegacyFiles

arxml

Input Files

SWC Design, SWC Integration

ECU-EX

DaVinciConfigurator Pro

DaVinci Tools

Gen.Code Files

Report Files

Output Files

BSWModules

bswmd

PREEvision

Script

Code Generation

CANdelaStudio

StaticCode Files

DaVinci DEV

MICROSARor custom modules

SYS-EX

Project Files

Report Files

40 © 2019. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.1 | 2019-07-09

Author:Mullangi, DivyakanthVector Germany

For more information about Vectorand our products please visit

www.vector.com

http://www.vector.com/

why autosar - vector

Documents