AutoSAR Overview

FESAWorkshopatKTH20100412
Prof.JakobAxelsson
VolvoCarsand
MlardalenUniversity

Thispresentationisbased onatutorial prepared bythe

AutoSAR Consortium

AUTOSAR Members

StatusJune2007

10 Core Partners
10CorePartners

49PremiumMembers

57AssociateMembers

ExchangeabilityandReuseofSWComponents
OEMb

Exchangeability
betweensupplier
between
supplierss
solutions

OEMa

OEMc

Platformb.1
Platformb.2
Platformb.n

Platforma.1
Platforma.2
Platforma.n

Exchangeability
between
manufacturers
applications

SupplierA
Chassis
Safety
Body/Comfort
Multimedia

SupplierB
Chassis
Safety
Telematics
Multimedia

SupplierC
Body/Comfort
Powertrain
Telematics
T l
ti
Multimedia

OEM f
OEMf
OEMe

Platformc.1
Platformc.2
Platformc.n

OEMd

Platformd.1
Platformd.2
Platformd.n

Exchangeability

Platformf.1
Platformf.2
Platformf.n
Platforme.1
Platforme.2
Platforme.n

betweenvehicle
platforms

Changing AutomotiveSWDevelopment
Automotive SW Development
Conventional
Software

AUTOSAR
ApplicationSoftware
standardized
AUTOSAR
HWspecific

Hardware

Hardware

Hardwareandsoftware willbewidelyindependent ofeachother.

p
p
willbesimplified.
p
Developmentprocesses
Thisreducesdevelopmenttimeandcosts.
Reuseofsoftwareincreases atOEMaswellasatsuppliers.
Thisenhances alsoquality andefficiency.
AutomotiveSoftwarewillbecomeaproduct.

AUTOSAR Main Working Topics

AUTOSARMainWorkingTopics
Architecture

Application
Methodology
Interfaces

Architecture

Application
Methodology
Interfaces

Architecture

Application
Methodology
Interfaces

Architecture:
Softwarearchitectureincludingacompletebasicorenvironmental
g
p
softwarestackforECUs thesocalledAUTOSARBasicSoftware as
anintegrationplatformforhardwareindependentsoftware
applications.
Methodology:
Exchangeformatsordescriptiontemplatestoenableaseamless
configurationprocessofthebasicsoftwarestackandthe
i
integrationofapplicationsoftwareinECUsanditincludeseventhe
i
f
li i
f
i
di i l d
h
methodologyhowtousethisframework.
ApplicationInterfaces:
Specificationofinterfacesoftypicalautomotiveapplicationsfrom
alldomainsintermsofsyntaxandsemantics,whichshouldserveas
a standard for application software.
astandardforapplicationsoftware.
5

Intra andInterECUCommunication
Portsimplementtheinterfaceaccordingto
thecommunicationparadigm(hereclient
serverbased).
ECUI
Portsaretheinteraction
pointsofacomponent.
Appli
cation
SWC
Thecommunicationis
A
channeledviatheRTE.
Thecommunicationlayer
inthebasicsoftwareis
encapsulatedandnot
RTE
visibleattheapplication
l
layer.

BSW

ECUII
Appli
cation
SWC
B

Appli
cation
SWC
C

Application

Ports
VFB

RTE

AUTOSAR
Infrastructure
BSW

Sensor

Hardware

CommunicationBus
CommunicationPath

AUTOSAR Methodology
AUTOSARMethodology
VFBview
SWC
Description

SWC
SWC
SWC
Description Description Description

AUTOSAR
SWC
n

AUTOSAR
SWC
3

AUTOSAR
SWC
2

AUTOSAR
SWC
1

...

Standardizeddescriptiontemplatesfor
St
d di d d
i ti t
l t f
applicationsoftwarecomponents
(interfacesandBSWrequirements)

VirtualFunctionalBus
ECU
Descriptions

SystemConstraint
Description

Standardizedexchangeformatsand
methodologyforcomponent,ECU,
andsystemlevel

Toolsupportingdeployment
ofSWcomponents

Mapping
ECUI

ECUII

ECUm
AUTTOSAR
SSWC
n

AUTOSAR
SSWC
2

AUTOSAR
SSWC
3

AUTOSAR
SSWC
1

...

RTE

RTE

RTE

Basic
Software

Basic
Software

Basic
Software

Toolsfor
supportofcomponentmapping
generationofRTE,i.e.inter and
intra ECU communication
intraECUcommunication
StandardizedBasicSoftware(BSW)
architecture,detailedspecifications
for implementation and configuration
forimplementationandconfiguration
ofBSW

Gateway

AutoSAR Descriptions
ECUs

SoftwareComponents
SwitchEval
SWComponentDescription

ECUResource
Description

ECUResource
Description

ECUResource
Description

BlinkInputModule
SwitchEval
SWComponentDescription

BlinkInputModule

SSupportedprotocols:
t d
t l
CAN,LIN,FlexRay

BlinkMaster
SMLS

System
Description

SWComponentDescription

LightActuatorsControl

BCH

BCV

BlinkMaster

LightActuatorsControl

CAN
LIN

SWComponentDescription

LightSourceSetting

LightSourceSetting
LML

LMR

SWComponentDescription

AUTOSARSystemDesignProcess
Input: Requirements & Vehicle Info
Input:Requirements&VehicleInfo

1a

1c
SWComponent
SW
Component
Description

System
D
Description
i ti

1b
ECUResource
ECU
Resource
Description

2
ConfigureSystem
& generate extracts
&generateextracts
ofECUdescriptions

Iterativecorrections
and/oroptimizations
(ifrequired)

Configure
g
eachECU
SWComponent

GenerateSW
executables
t bl
foreachECU

SWexecutables
SW
executables
foreachECU
9

AUTOSARSystemDesignProcess
Input:Requirements&VehicleInfo

1a

1c
SWComponent
Description

System
Description

1b
ECUResource
Description

2
ConfigureSystem
&generateextracts
ofECUdescriptions

SWComponentDescription
Generalcharacteristics (name,manufacturer,etc.)
Communicationproperties:
p_ports
r_ports
interfaces
SWComponent
innerstructure(composition)
subcomponents
connections
requiredHWresources:
processingtime
scheduling
memory(size,type,etc.)

Iterativecorrections
and(/oroptimizations
(ifrequired)

Configure
eachECU

GenerateSW
executables
foreachECU

SWexecutables
foreachECU

10

AUTOSARSystemDesignProcess
Input:Requirements&VehicleInfo

1a

1c
SWComponent
Description

System
Description

1b
ECUResource
Description

ConfigureSystem
&generateextracts
Iterativecorrections
ofECUdescriptionsECUResourceDescription
and(/oroptimizations
Generalcharacteristics (name,manufacturer,etc.)(ifrequired)
Temperature (own,environment,cooling/heating)

Configure
eachECU

Availablesignalprocessingmethods
Availableprogrammingcapabilities

SWComponent

AvailableHW:

GenerateSW
executables
foreachECU

C,architecture(e.g.multiprocessor)
memory
interfaces(CAN,LIN,MOST,FlexRay)
periphery(sensor/actuator)
connectors(i.e.numberofpins)

SWbelowRTEformicrocontroller
SignalpathfromPintoECUabstraction

SWexecutables
foreachECU

11

AUTOSARSystemDesignProcess
Input:Requirements&VehicleInfo

1a

1c
SWComponent
Description

System
Description

1b
ECUResource
Description

2
ConfigureSystem
&generateextracts
SystemDescription
ofECUdescriptions

Networktopology
bussystems:CAN,LIN,FlexRay
3 connectedECUs,Gateways
powersupply,systemactivation
Configure

SWComponent

Iterativecorrections
and(/oroptimizations
(ifrequired)

eachECU
Communication(foreachchannel)
Kmatrix
gatewaytable

GenerateSW
Mapping/ClusteringofSWcomponents
executables
foreachECU

SWexecutables
foreachECU

12

AUTOSARMetamodel
Themetamodel ismodeled
inUML
Thestructureofthe
informationcanbeclearly
visualized
Theconsistencyofthe
informationisguaranteed
UsingXML,adataexchange
formatcanbegenerated
automatically out of the
automaticallyoutofthe
metamodel

13

METAMODEL
Datatype

SW
SW
Component
Interface

MODEL
Mirror
Adjustment

Mirror
Actuator

Application InterfacestoEase Reuse

Data Type Name

LongAccBase

ESP-Sensors
ESP-Sensors
Base Sensor Signals

Data Type Name

YawRateBase

Description

Yaw rate measured along vehicle z- axis

(i.e. compensated for orientation).
Coordinate system according to ISO
8855

Data Type

S16

Integer Range

-32768..+32767

Physical Range

-2,8595..+2,8594

Ph i l Offset
Physical
Off t

Unit

rad/sec

Remarks

This data element can also be used to

instantiate a redundant sensor interface.
Range might have to be extended for
future applications (passive safety).

I1
Interface of ESP
and VLC

nterface of ESP and

external yaw rate
controller

2nd
2nd Yaw
Yaw
Rate
RateController
Controller

I6

I4

ESP
ESP
SW-Component
SW-Component

System-level Brake
Actuator Interface

Vehicle
Vehicle
Longitudinal
Longitudinal
Controller
Controller
Standard Signals
from ESP

I2

I3

Information signals
g
from other functions /
domains

Command signals to
other functions /
domains

I7
I5

Brake
Brake Actuator
Actuator

Standardizedapplicationinterfaceson
systemlevel
(ESPsystem,chassisdomain)

Data Type Name

RollRateBase

14