 Introduction to AUTOSAR

Stephen Waldron MSc MEng CEng MIET – Local Product Line Manager, Vector GB
Tuesday 5th May 2015
V2.0.12 | 2015-04-20
 Why AUTOSAR?
E/E Complexity and Software Quantity is Growing Fast

80% of Adaptive headlights

Active steering
automotive Curve warning
innovations are Stop and Go
based on software Lane keeping assistance
Automated parking
Collision mitigation
Hybrid powertrain
Road trains
Electronic Brake Control
Telediagnostics
Car-2-car communication
Software updates

Airbags
Electronic stability control
Active body control
Adaptive gearbox control
Adaptive cruise control
Emergency call
Airbags
Electronic stability control
Active body control
Adaptive gearbox control
Adaptive cruise control
Emergency call

Gearbox control Gearbox control Gearbox control

Traction control Traction control Traction control
Anti lock brakes Anti lock brakes Anti lock brakes
Electronic fuel injection Electronic fuel injection Electronic fuel injection Electronic fuel injection
Cruise control Cruise control Cruise control Cruise control

1975 1985 1995 2005 2015

2
 Why AUTOSAR?
Development of Technology

Single Complex electronics Complex electronics

electronic system within network between
systems the vehicle vehicles and
infrastructure
1990 2005 2020

1 ECU 5 ECUs 25 ECUs 50 ECUs 100 ECUs

CAN  MOST  LIN  FlexRay  Eth/IP  CAN FD

3
4 bit  8 bit  16 bit  32 bit  64 bit
 Why AUTOSAR?
The objectives of 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 development methods and tools

 Re-use of basic software

4
 Why AUTOSAR?
The AUTOSAR Partnership

(AUTomotive Open System ARchitecture)

is a worldwide development partnership of car manufacturers, suppliers and

other companies from the electronics, semiconductor and software industry.

5
 Why AUTOSAR?
The AUTOSAR Partnership

Core Partners
Development Members

Associate Members

Attendees

Premium Members

Generic Standard Tools and Semi-

TIER 1 Software Services conductor

6
 Why AUTOSAR?
AUTOSAR is still growing

2015

2014
AR 4.2.2
2013 ? pages
?m
AR 4.2.1
19572 pages
2009 AR 4.1.3
1,99 m

16871 pages
1,71 m

2007
AR 4.0.2
12128 pages
1,23 m
AR 3.2.1
8486 pages
0,87 m

7
 AUTOSAR 4 Layered Architecture
MICROSAR – Vector’s full range of Basic Software modules

8
 Function Oriented Development – supported with AUTOSAR
Function centric (rather than ECU centric) design

Requirements

1. Requirements

PowerMirrorCtrl
SwitchMatrix PowerMirrorPass
Architecture

y:PM_y y:PM_y x+:pm_pass_x+ Assembly Net x+:pm_pass_x+

2. Mapping to Functions
Logical/SW

x:PM_x x:PM_x y+:pm_pass_y+ y+:pm_pass_y+

sel:PM_selection sel:PM_selection y-:pm_pass_y- y-:pm_pass_y-
x-:pm_pass_x- x-:pm_pass_x-
Type: PowerMirr...

Type: SwitchMatrix

PowerMirrorDriver
x-:pm_driv_x- x-:pm_driv_x-
y+:pm_driv_y+ y+:pm_driv_y+
PowerManagement y-:pm_driv_y- y-:pm_driv_y-
KeyIn:KeyIn def12:KeyIn x+:pm_driv_x+ Assembly Net x+:pm_driv_x+
Type: PowerMirr...
Type: PowerMan... Type: PowerMirrorCtrl

- -
Network/HW
Architecture

Pass Door Ctrl Driver Door Ctrl

PassengerMirror DriverMirror

3. Mapping to ECUs
- cv2:4w - Door Ctrl _0
KA_Pass - -

- - - DoorLIN:LIN SwtichMatrix

BatMng CANPT:CANC Gateway Body Ctrl

PowerSupply -
- - -
Ground

9
 Current Workflow (non-AUTOSAR)
Before AUTOSAR

Network communication of The ECU is configured based on

the vehicle is specified the DBC, FIBEX, LDF file.

ECU 1

Applications
ECU1 ECU2

Basic Software
(BSW)

ECU n
DBC, FIBEX, LDF
Applications

Basic Software
(BSW)

10
 AUTOSAR
AUTOSAR Workflow

SW functionality of the vehicle is

… and mapped to ECUs
defined as a system of SWCs ...
ECU1 ECU2
SWC1
SWC1 SWC3

Virtual Function Bus

SWC2
VFB
SWC2 SWC3

Software Component Description* System Description*

An extract is created for The ECU is configured

each ECU... in detail

ECU1 SWC1 SWC2

SWC1
RTE
SWC2
Basic Software
(BSW)

ECU Configuration
Extract of System Description* Description (ECUC)* *
11
 Why AUTOSAR?
Degree of AUTOSAR usage is different for different aspects

ASPECT TODAY FUTURE

well used in Europe; will be used broadly

BSW + RTE starting in US, Asia (~ 2017)
(Japan, Korea, China)

12
 Why AUTOSAR?
Degree of AUTOSAR usage is different for different aspects

ASPECT TODAY FUTURE

well used in Europe; will be used broadly

BSW + RTE starting in US, Asia (~ 2017)
(Japan, Korea, China)

Data formats
will be the standard
(System Only few OEMs
(~ 2020)
description)

13
 Why AUTOSAR?
Degree of AUTOSAR usage is different for different aspects

ASPECT TODAY FUTURE

well used in Europe; will be used broadly

BSW + RTE starting in US, Asia (~ 2017)
(Japan, Korea, China)

Data formats
will be the standard
(System Only few OEMs
(~ 2020)
description)

Distribution of Full function oriented

Development
application software development by OEM
methodology
(SWC) by OEM (> 2020)

14
 Why AUTOSAR
Degree of AUTOSAR usage is different for different aspects

ASPECT TODAY FUTURE

well used in Europe; will be used broadly

BSW + RTE starting in US, Asia (~ 2017)
(Japan, Korea, China)

Data formats
will be the standard
(System Only few OEMs
(~ 2020)
description)

Distribution of Full function oriented

Development
application software development by OEM
methodology
(SWC) by OEM (~ 2020)

Push: Introduction of new functionalities (Safety, Ethernet/IP, …)

Hurdle: Compatibility to legacy solution (NM, data formats, …)

15
 Usage of AUTOSAR – Vector’s Evaluation
OEM Adoptions

AUTOSAR Communication
OEM Scope Methodology
Version Definition
OEM A 3.x Communication System Descr. SWC+BSW
OEM B 3.x Comm. / complete DBC, LDF SWC+BSW
OEM C 3.x CAN / LIN / FR DBC, LDF, Fibex SWC+BSW
OEM D 3.x  4.x CAN / LIN DBC, LDF SWC+BSW
OEM E 3.x CAN / LIN DBC, LDF SWC+BSW
OEM F 4.x CAN DBC BSW
OEM G 3.x  4.x complete DBC, LDF, Fibex BSW
OEM H 4.x CAN / LIN / FR DBC, LDF, Fibex BSW
OEM I 4.x CAN / LIN / FR System Descr. SWC+BSW
OEM J 4.x complete Fibex SWC+BSW
OEM K 4.x CAN & FlexRay System Descr. SWC+BSW
OEM L 3.x/4.x Communication ? SWC+BSW

Differences in Differences in data

functionality formats and workflow

 AUTOSAR is a standard … with a growing number of variants

16
 Usage of AUTOSAR – Vector’s Evaluation
Market Evaluation

1. The number of OEMs using AUTOSAR is growing

2. The number of Tier1s using AUTOSAR is growing

3. The AUTOSAR functionality is growing

4. The invest of tool providers to support AUTOSAR is growing

5. Alternative solutions are losing ground

 The market is certainly growing – approx. 25% per year

17
 Vector AUTOSAR Solution
Products and Services

V2.0.12 | 2015-04-20
 Vector AUTOSAR Toolchain
Vector AUTOSAR Toolchain
SWC2

Logical & Software SWC1

Calibration
Architecture Design SWC3

PREEvision CANape
SWC2

SWC1
SWC3
Development of ECU-/System-Test
Application Software

vVIRTUALtarget S1 S2 CANoe

SWC1 SWC2 ECU Monitoring

SWC Detailed Design and Debugging
RTE
DaVinci Developer CANoe.AMD

Basic Software
(BSW)
RTE Configuration Virtual Integration
BSW Configuration AUTOSAR ECU
DaVinci Configurator Pro vVIRTUALtarget
S1 S2

19
 Vector AUTOSAR Solution
PREEvision

 System design of vehicles or

ECUs
 Software components
 Network communication
 Mapping
 Supports also various
architecture levels beyond
AUTOSAR

20
 Vector AUTOSAR Solution
DaVinci Developer

 Creation of SWC descriptions

with graphical or table-based
editors
 Definition of SWC internal
behavior (runnable entities)
 Consistency check of the SWCs

21
 Vector AUTOSAR Solution
DaVinci Configurator Pro

 Creation of ECU configurations

 MICROSAR BSW and RTE
 Third party BSW (MCALs)
 Specific editors for each BSW
domain
 Validation of ECU configuration
 Generation of configurable part
of BSW and RTE

22
 Vector AUTOSAR Solution
vVIRTUALtarget*

ECU Configuration

SWC1 SWC2

RTE

BSW

MCAL
MCAL VIP

 Early integration of ECU SW in a

virtual environment
 Parallel development supported
 Real MCAL and VIP MCAL in
same configuration file
Test Tool
 Automatic configuration of
VIP MCAL based on real
MCAL VIP MCAL
MCAL
Virtual
Integration Test Suite
 CANoe or other tools as test
Platform Real ECU tool
*Planned feature

23
 Vector AUTOSAR Solution
CANoe/CANape

 Stimulation and measurement

of ECU interfaces
 Bus Communication
 I/O
 Access of ECU internal data
 BSW States
 SWC communication
 Calibration of ECU parameters

24
 Basic Software as a Product
Requirements of the ECU supplier – and our answer

High performance & high quality for all projects

powerful optimized mature all all all all
tooling code product OEMs µCs functions types
ARM, CAN, CAN FD,
ASPICE Level 3, AUTOSAR: Evaluation,
supportive GUI Atmel, LIN, FR,
ISO 26262, PLA Audi, BMW, Prototype,
with comfort Freescale, MOST,
approach, ALM+, Daimler, Production,
views, multi-user, pre- Infineon, Ethernet,
5th generation of FCA, GM, SIP, EIP,
diff & merge, configuration, Microchip, SOME/IP, SD,
configuration tool, HMC, JLR, Safety,
automatisms, minimal ASR- NXP, AVB, DoIP,
20 years of Patac, 3rd party
validation, all ASR overhead, HW Panasonic, SCC, XCP,
experience, 1,200 Porsche, integration,
data formats, part optimized Renesas, J1939, OBD,
person years ASR Toyota, VAB, SWC
of Vector ASR tool drivers and OS Spansion, Postbuild, FBL,
development, VCC, VW, ... integration,
chain, STM, TI, ASIL-D,
> 500 ASR CBD: around the
vVIRTUALtarget Xilinx Security,
projects > 40 globe
> 100 Multicore, ...

with planning reliability with value for money

up-front turnkey no hidden focus scalable long term
specification delivery costs on TCO license benefit
delivery date fixed price
license only cost saving
quote based on defined for integration in turnkey product
what is needed, programs,
detailed customers use customer project, instead of project
flexible business flat-rate, volume
questionnaire case; tested on maintenance incl. work
model discount
target HW spec changes

This is unique around the world!

25
 Why AUTOSAR
AUTOSAR is a challenge

AUTOSAR
is very beneficial

but
introduction is a challenge

it is good to have
mature equipment
and experienced guidance

26
 AUTOSAR Basics
AUTOSAR Know-how

 Free of charge E-learning:

http://vector.com/vi_autosar_solutions_en.html

 AUTOSAR Workshop:
http://vector.com/vi_class_autosar_de.html

 Further Webinars and Recordings:

http://vector.com/vi_autosar_webinars_en.html
> 2015-05-08: MICROSAR Safe – AUTOSAR basic software for safety-relevant ECUs
according to ISO 26262
> In preparation: AUTOSAR Ethernet Stack / Audio/Video Bridging over Ethernet /
J1939 and ISOBUS in AUTOSAR / …
> Recordings: AUTOSAR Methodology / AUTOSAR Design using PREEvision / Model-
based design / Configuration Process / Testing and debugging
 Regular webinar invitation e-mailing

 Information about Vector’s AUTOSAR Solution:

http://vector.com/vi_autosar_solutions_en.html

27
 For more information about Vector
and our products please visit

www.vector.com

Presenter:
Stephen Waldron MSc MEng CEng MIET
Local Product Line Manager, Vector GB

28 © 2014. . All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V2.0.12 | 2015-04-20