TNI Software Agenda - Irisa

MF 

standards 

� Needs in the Industry 

� Request from OEM’s 

� AUTOSAR : 

TNI Software 

Autosar 

Agenda 

�Needs and request 

�Presentation of AUTOSAR Concepts 

�Presentation of AUTOSAR Tools

Demanded Safety 

& Quality 

Million 

1000 

Unitary 

100 

Optimization / Volume 

standards 

AUTOSAR Concepts 

Why Autosar 

In Vehicle EE trends 

100% proven 

Traceable 

CMMI Levels 

Tested 

Improvements 

Digital control 

Indispensable 

Critical 

Complexity

Automotive OEM request 

Reduce Number of ECU for standard Functions 

� Engine Control 

� Breaking Control 

� Body Computer 

� Automatic Transmission 

� Gear selector 

� Steering Column 

� Steering Wheel 

� Steering angle sensor 

� Electric power steering 

� Parking Sensor 

� Dashboard 

� Adaptive Cruise Control 

� Tyre Pressure control 

� Air Bag unit Control 

� Driver Door 

� Passenger Door 

� Passive Entry 

� Driver seat ECU Trunk 

� Passenger seat 

� Left Headlight unit Control 

� Right Headlight control 

� Air Conditioning 

� Alarm Sensor/roof control 

� Rain/sun sensor 

� External light control 

� Alarm unit control 

� Infotainment 

Leave room for innovation 

NEW functions are first implemented as new ECU’s 

Driving Mechanics 

� 2WD/4WD control 

� 4-wheel steering 

� Power steering 

� Brake by wire 

� Collision warning 

� Suspension control 

� Distribution systems (Gateway) 

Driving Electrical 

� ISAD alternator 

� Start and Stop 

� Rear lamp clusters - LED 

� Side-direction indicators - LED 

Driving Comfort 

� Memory seat, mirror, steer Positions 

� Electronic compass 

� Electro chromic mirrors 

� Power roof 

� Electric sunroof 

� Off driving lines warning 

� Parking helps 

Driving Infotainment 

� Integrated cell phone 

� Traffic information system 

� GPS 

Driving Safety 

� Vision enhancement 

� Exterior camera 

� Interior camera 

That will later be ported to 

software

And Prepare the Future 

Toward partially open Automotive EE Architecture 

Growth drivers:Telematics - Passenger Cars 

Car-Specific Features Non-Car-Specific Features (B2C) 

Intelligent Transportation 

•Brake-by-GPS 

•Headlights-by-GPS 

•Adaptive cruise control 

Navigation and Traffic 

•Basic navigation 

•Dynamic navigation 

•Traffic information 

Safety and Emergency 

• Automatic airbag 

notification 

• Emergency call 

• Roadside assistance 

• Vehicle tracking 

Vehicle Services 

•Remote diagnostics 

•Warranty failure detection 

•Scheduled maintenance 

•Software updates 

Information 

•General news 

•Customized news 

•Points of interest 

Mobile Communication 

mobile phones 

hands-free operation/ 

voice recognition PDAs 

Mobile Communication 

•E-mail 

•Internet/ Intranet 

•Phone 

Multimedia and Entertainment 

•Music downloads 

•Video downloads 

•Interactive games

Upgradeability 

of Devices 

Growth drivers:Telematics - Commercial Vehicles 

Vehicle-Related Services Transport-Related Services 

Vehicle Management Services 

� Trip analysis (technical) 

� Maintenance planning 

� Problem management 

� Trip recording (technical) 

� etc. 

Vehicle Fleet Management Services 

� Operating cost analysis 

� Maintenance cost analysis 

� Benchmarking 

� Vehicle history 

� etc. 

Transport Management Services 

� Sending orders 

� Mapping 

� Dynamic routing 

� Shipment tracking 

� Trip recording (logistics), etc. 

Logistics Services 

� Trip recording 

� Route planning 

� Order management, etc. 

Enabling Technologies 

Car-Specific Features Non-Car-Specific Features 

Improvement of existing Human- 

Machine Interface (HMI) Solutions 

Importance of HMI 

�Defines ease and safety of 

operation 

�Reduces cognitive load on 

drivers 

�Defines end-user acceptance 

�Main area of differentiation 

�Represents 60-80% of cost 

of device 

Major Technological Changes 

�Hands-free operation 

- voice recognition 

- text-to-speech 

- speech-to-text 

�Intelligent dialog systems 

�Customization (reconfigurable 

screens) 

Convergence of Wireless Technologies 

�Intercommunication/Operability 

between various communication 

technologies (wireless LAN, Bluetooth, 

GMS, GPRS) 

�Multiple rendering technologies 

Process Stability/Security 

� codification protocols 

New Innovative Applications 

� e.g. “IP v6” protocols

Direct fuel 

Injection 

Electric throttle 

valve control 

42-V converter 

Growth Drivers - Electronics 

Steer-by-wire 

Electrically assisted 

power Steering 

Keeping Growth ? 

Active suspension 

Forecast price trends up to 2007 

Source Mc Kinsey 

Brake-by-wire

Rapid progresses in 

hyper-specialized & disjoint 

Electronics disciplines… 

Disjoint Vehicle Domains 

Disjoint Software Projects 

Disjoint Hardware Platforms 

Motorola 

Bus 

ctl1 

E1 

MPBC_GLOBAL 

BOOT_DBG 

SMCARD 

IIC1_2 

m_pi_bus 

UART1_3 

CLOCKS 

ECU 

FPBC_MPIC EJTAG PR3940 

FPIMI 

pSOS 

Memory MMI RTOS 

TM_3218 

f_pi_bus 

FR_MEM 

M_bridge 

PCI 

DE 

USB 

IEEE1394 

C_Bridge 

MBS 

ICP1_2 

VMPG 

VMPG_ 

AUX 

VIP1_2 

TPIC 

GPIO 

SPDIO 

AIO1_3 

t_pi_bus 

MSP1_2 

SSI 

1990 - Designing ECU’s ECU 

ECU1 

TPBC 

… Led to regression in 

understanding the whole 

Vehicle System. 

STM 

Bus 

ctl1 

E2 

ECU2 

Bus 

ctl2 

PHILIPS

Motorola 

Bus 

ctl1 

E1 

OSEK 

ARM2 

Bus 

ctl2 

ECU1 

1995 : Defining Network 

and Messaging 

Systems of Today - “The Multiplex Era” 

Infineon 

Bus 

ctl1 

E2 

ECU2 

Bus 

ctl2 

OSEK 

Renesas 

Bus 

ctl1 

E3 

ECU3 

Bus 

ctl2 

2000 – Model based design

OSEK 

CPU1 

Bus 

ctl1 

E1 

OSEK 

CPU2 

Bus 

ctl2 

200X… 

APPLICATION DISTRIBUTION 

ECU1 

DISTRIBUTED APPLICATION 

OSEK 

CPU 

Bus 

ctl1 

ECU2 

Bus 

ctl2 

DISTRIBUTED APPLICATION 

E2 

standards 

E4 

OSEK 

CPU 

Bus 

ctl1 

ECU4 

Bus 

ctl2 

OSEK 

CPU3 

Bus 

ctl1 

E3 

ECU3 

Bus 

ctl2

MSR 

(Manufacturer Supplier Relationship) 

ASAM ODX 

(Association for Standardization of 

Automation and Measuring Systems) 

HIS 

(Manufacturers Initiative Software) 

EAST-EEA 

A long search 

“Automotive Open Systems Architecture” 

Sub-Function Sub-Function Sub-Function 

SW- 

Component 

SW- 

Module 

ECU 1 

SW- 

Component 

SW- 

Module 

SW-Module 

Runtime Environment 

Function 

Requirements 

SW- 

Component 

SW- 

Component 

SW- 

Module 

ECU 3 

SW- 

Component 

SW- 

Module 


(logical) 

functional 

Architecture 

SW 

Component 

Architecture 

(physical) 

EE - 

Architecture 

Vehicle Bus

2000 

2000 

2006 

2007 - .. 

Application 

Application 

Application 

spécific 

generic 

OS 

OS 

OS 

Network 

Strategy Drivers 

Network 

Network

Autosar 15 OEM’s 

AUTOSAR Organisation 

Vision 

Mission 

Objectives 

Strategy 

� Challenges – Solutions 

� Organizational Structure 

Tactics 

� Technical Concept / Methodology 

� Roadmap / Project Plan 

Operations 

� Work Groups / Work 

Packages 

� Meeting Schedules

SW Component 

Template 

Data Exchange Formats 

Specification of µC-Abstraction 

Open connectivity to different 

tools 

Specification of Basic-SW Core 

Implementation of 

µC-Abstraction 

Timelines 

Implementation 

Basic-SW Core 

Standardization of interfaces of all vehicle domains 

Eased integration of 3rd party 

software components 

Definition of roles and responsibilities 

for the new processes 

HW replacement 

without need for 

SW adaptation of 

functions or 

applications 

Concentration 

of resources on 

innovations 

Availability of RTE 

Independence from 

communication 

technology 

Basis for partitioning 

and relocation of 

functions 

Open connectivity for 

3rd party software 

2006 

AUTOSAR– Vision 

The vision is an improved complexity management of 

highly integrated E/E architectures through an increased 

reuse and exchangeability of SW modules between 

OEMs and suppliers. 

OEM a 

Platform a.1 

Platform a.2 

Platform a.n 

Exchangeabil 

ity between 

manufacturer’s 

applications 

OEM b 

Platform b.1 

Platform b.2 

Platform b.n 

Supplier A 

�Chassis 

�Safety 

�Body/Comfort 

�Multimedia 

OEM f 

Platform f.1 

Platform f.2 

Platform f.n 

OEM e 

Platform e.1 

Platform e.2 

Platform e.n 

Supplier B 

� Chassis 

� Safety 

� Telematics 

� Multimedia 

Supplier C 

� Chassis 

� Body/Comfort 

� Telematics 

� Multimedia 

Exchangeabi 

lity between 

vehicle 

platforms 

OEM c 

Platform c.1 

Platform c.2 

Platform c.n 

Exchangeabili 

ty between 

supplier’s 

solutions 

OEM d 

Platform d.1 

Platform d.2 

Platform d.n

AUTOSAR– Project Objectives 

The AUTOSAR project goals will be met by specifying and 

standardizing the central architectural elements across functional 

domains, allowing industry competition to focus on implementation. 

Project Objectives Functional Domains 

� Consideration of availability and safety 

requirements 

� Redundancy activation 

� Scalability to different vehicle and platform variants 

� Implementation and standardization of basic 

system functions as an OEM wide “Standard Core“ 

solution 

� Transferability of functions throughout network 

� Integration of functional modules from multiple 

suppliers 

� Maintainability throughout the whole “Product Life 

Cycle“ 

� Increased use of “Commercial off the shelf 

hardware“ 

� Software updates and upgrades over vehicle 

lifetime 

Cooperate on standards, 

compete on implementation 

Vehicle 

´centric‘ 

Chassis 

Multimedia/ 

Telematics 

Powertrain 

AUTOSAR 

Body/ 

Comfort 

Safety 

(active/ 

passive) 

Man 

Machine 

Interface 

Passenger 

´centric‘ 

13 First Tier – 8 Semiconductor – 10 

Software…

AUTOSAR – Central Objective: Transferability 

The ability to transfer functions or SW modules supports the reuse of IP 

and design flexibility, in addition to simplifying the integration task and 

reducing of development costs. 

OS 

v_warn() 

Example of functional transferability : Pedal Management Use Case 

SW Component 

2 

... 

Basic system functions 

core functions, drivers 

Hardware 

SW-C n-1 SW-C n 

AUTOSAR-RTE for ECU1 

SPAL 

OS 

get_v() 

ECU 1 ECU 2 

Pedal 

Mgmt. 

Technical benefits include 

� Reuse of Intellectual Property 

� Increase in design flexibility 

� Simplification of the integration task 

� Reduction of SW development costs 

... 

SW-C 

n+m-1 




Hardware 

Pedal 

SW-C 

n+m 

SPAL

Challenge 

- Non-competitive 

functions have to 

be adapted to OEM 

specific 

environments 

- Effort wasted on 

implementation and 

optimization of 

components, which 

add no value 

recognized by the 

customer 

Challenge 

- Microcontroller End 

of Life � re-design 

effort 

- Microcontroller 

upgrade due to new 

performance need 

(caused by new 

functions) � redesign 

effort 

- Lack of guidelines 

for use/ buy of SW 

components 

- No standardized 

processes for SW 

as a product 

- Unclear legal 

situation 

AUTOSAR – Challenges/ 

Solutions/ Benefits (1 of 3) 

Solution 

Open and 

standardized 

software 

interfaces (intraand 

inter-ECU, 

layered 

architecture) 

Basic SW Core 

Benefit AUTOSAR project 

Objective addressed 

- Reusability of 

modules cross- 

OEM 

- Exchangeability 

of components 

from different 

suppliers 

- Enhancement of 

SW Quality 

- Concentration on 

functions with 

competitive value 

� Scalability to different vehicle 

and platform variants 

� Transferability of functions 

throughout network 

� Integration of functional 

modules from multiple 

suppliers 

� Increased use of “Commercial 

off the shelf hardware“ 

� Software updates and 

upgrades over vehicle lifetime 

� Implementation and 

standardization of basic 

system functions as an OEM 

wide “Standard Core“ solution 



Solution 

Microcontroller 

Abstraction 

Business Model 

(Application Layer 

and Standard Layer) 

Benefit AUTOSAR project Objective 

addressed 

Microcontroller can 

be exchanged 

without need for 

adjustments in SW/ 

functions/ 

applications 

- Integration of 3 rd 

party SW 

Components 

- Common 

understanding/gui 

delines between 

suppliers and 

OEMs 

- Transparency of 

SW costs 





suppliers 

� Maintainability throughout the 

whole “Product Life Cycle“ 







suppliers

Challenge 

- Large effort when 

relocating functions 

between ECUs 

- Large effort when 

reusing functions 

- Complex tool chains 

- Limited data 

exchange between 

tools of different 

vendors 



Solution 

Runtime 

Environment 

Standardized data 

exchange formats 

Rights and Duties 

Benefit AUTOSAR project Objective 

addressed 

- Encapsulation of 

functions creates 

independence from 

communication 

technology 

- Communication 

easier through 

standardized 

communication 

- Partitioning and 

relocatability of 

functions possible 

- Improved quality of 

tools through 

maturation against 

a stable standard 

Core Partner (OEM & Tier 1 Supplier) 

� Organizational control 

� Technical contributions 

� Administrative control 

� Definition of external Information 

(web-release, clearance, etc.) 

� Leadership of Working groups 

� Involvement in Working groups 

Premium Members 

(incl. Tool Manufacturers) 

� Leadership of Working groups 

� Involvement in Working groups 

� Technical contributions 

� Access to current information 

Associate Members 

� Access to finalized documents 

� Utilization of Standards 





suppliers 









suppliers 





AUTOSAR – Partnership Structure 

A three tier structure, proven in similar initiatives, is implemented 

for the development partnership. Appropriate rights and duties are 

allocated to the various tiers. 

Contract Sections 

Development 

Agreement 

Premium Member 

Agreement 

Associate Member 

Agreement 

Support Roles 

� Development 

Member 

Agreement 

� Attendee 

Agreement

WP 

WP 

1 

1 

AUTOSAR 

AUTOSAR 

Concept 

Concept 

VFB 

Specification 

Requirements 

on Basic SW 

Impact of 

dependable 

Systems 

Input Tools 

WP 

WP 

5 

5 

Test 

Test 

and 

and 

Integration 

Integration 

WP 5.x.x 

Particular SW-C 

tests 

WP 5.x.x 

Integration 

AUTOSAR-SW 

in ECU 

WP 5.x.x 

Creation process 

description 

WP 5.x.x 

Exemplary 

demonstration 

of an application 

WP 

WP 

2 

2 

System 

System 

Generation 

Generation 

Spec SW 

Component 

Templ 

Spec ECU 

Resource 

Templ 

Spec of Sys 

Constraint 

Templ 

Autosar contribution 

AUTOSAR 

WP 

WP 

3 

3 

ECU 

ECU 

configuration 

configuration 

WP 

WP 

WP 

4 

4 

ECU 

ECU 

SW 

SW 

Generation 

Generation 

ECU 

configuration 

description 

RTE 

Specification 

Specification of 

Basic SW 

.1 CAN/LIN .2 COM/NM 

Template 

Template 

team 

team 

Impl. ”existing” 

BSW 

Qualification/ 

conformance 

testing 

”existing” 

BSW 

.3 Debugging 

.4 Diagnostics .5 FlexRay .6 Gateway 

.7 Interp. .8 Mem. Serv. 

.9 Mode 

Mgmt 

.10 MOST ** .11 OS .12 SPAL 

Autosar Contribution 

WP 

WP 

10 

10 

Data 

Data 

Description 

Description 

WP 10.x 

Body Comfort 

WP 10.x 

Powertrain 

WP 10.x Chassis 

WP 10.x Safety 

WP 10.x 

Multimedia/ 

Telematics 

WP 10.x HMI 

AUTOSAR 

WP 20 

Enabling of 

AUTOSAR 

Exploitation

Business Consulting Services 

AUTOSAR – Reporting Process 

�Executive 

Board 

�Steering 

Committee 

�PL Team 

�Working 

Groups 

Define project 

goal 

Define targets 

Define targets 

and deliverables 

of WGs 

Status of each 

deliverable in 

Report Card 

Monthly report 

consolidation 

(monthly) 

standards 

Accept report; 

define key issues 

Create Project Overview; 

prepare key issues 

(each year) 

Presentation of 

WG content 

(each quarter) 

Detailed 

Presentation of 

WG content 

Milestone 

Reporting 

(each half year) 

AUTOSAR Concepts 

Autosar what

Application 

Software 

Component 

AUTOSAR 

Interface 

AUTOSAR 

Interface 

Complex 

Device 

Driver 

� Abstract interfaces 

� Virtual Function Bus 

� ECU Description template 

• Micro Controler Abstraction layer 

� SWC Description template 

• Standard Peripheral Abstraction Layer 

� System constraint template 

� RTE generated 

Autosar concepts 

AUTOSAR- ECU Software Architecture 

AUTOSAR 


Component 

Actuator 


Component 

AUTOSAR 

Interface 

AUTOSAR Runtime Environment 

AUTOSAR 

Interface 

ECU 

Abstraction 

Standardized 

Interface 

Standardized 

Interface 

Standardized 

Peripheral 

Controller 

Abstraction 

Provide 

Interface d 

Sensor 


Component 

AUTOSAR 

Interface 

Standardized 

AUTOSAR 

Interface 

ECU-Hardware 

Standardized 

Interface 

Services Communication 

Standardized 

Interface 

Requested 

Interface 

AUTOSAR 


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

Standardized 

Interface 

Basic Software 

ECU 

Firmware 

Standard 


Application 


Component 

AUTOSAR 

Interface 

Standardized 

Interface 

Operating 

System 

Standardized 

Interface 

Automotive Open System 

Architecture (AUTOSAR): 

� Standardized, openly disclosed 

interfaces 

� HW independent SW layer 


� Redundancy activation 

AUTOSAR RTE: 

by specifying interfaces and their 

communication mechanisms, the 

applications are decoupled from 

the underlying HW and Basic SW, 

enabling the realization of Standard 

Library Functions. 

Key: 

API 0 

VFB & RTE relevant 

API 1 

RTE relevant 

API 2 

API 3 

Private interface

Use Case ‘Front Light Management’ mapped 

to AUTOSAR architecture 

Switch event 

check_switch () 

switch_event 

(event) 

AUTOSAR 

Interface 

Complex 

Device 

Driver 

ECU-Hardware 

AUTOSAR 

Interface 

Complex 

Device 

Driver 

AUTOSAR 

Interface 

HW independent 

Services 

(e.g. State- 

Machines, 

Subscribing) 

Light Request 

switch_event (event) 

request_light 

(type, mode) 

ECU 

Abstraction 

Front-Light Manager 

request_light (type, mode) 

get_keyposition ( ) 

set_light (type, mode) 

set_dboard(type,mode) 

AUTOSAR RTE 

set_current 

(...) 

ECU 

Abstraction 


(standardized) 

standardized Interface 

DIO PWM ADC 

AUTOSAR 

Interface 

HW dependent 

Services 

(NVRAM, timer, 

fault memory, 

etc.) 

SPAL 


set_dboard (type,mode) 

HW dependent Services 


fault memory, 

etc.) 

Microcontroller Abstraction 

Headlight 

set_light 

(type, mode) 

set_current (...) 

standardized 

Interface 

COM Driver 

SW-Component 

n 

AUTOSAR 

Interface 

standardized interface 

Application 


... 

Operating 

Systems 

Exchange of type of front light and 

consequences to the Use Case mapping 

Switch event 

check_switch () 

switch_event 

(event) 

ECU-Hardware 

AUTOSAR 

Interface 

HW independent 

Services 

(e.g. State- 

Machines, 

Subscribing) 

Light Request Front-Light Manager 

switch_event (event) request_light (type, mode) 

request_light 


(type, mode) 

set_light (type, mode) 

set_dboard(type,mode) 

AUTOSAR 

Interface 

ECU 

Abstraction 

AUTOSAR RTE 

set_light(...) 

Headlight ECU 

Abstraction 


(standardized) 

standardized Interface 

DIO PWM DIO ADC 

AUTOSAR 

Interface 

HW dependent 

Services 


fault memory, 

etc.) 

SPAL 


set_dboard 

(type,mode) 

HW dependent Services 


fault memory, 

etc.) 

Microcontroller Abstraction 

Xenon Headlight light 

set_light 

(type, mode) 

set_current (...) 

standardized 

Interface 

COM Driver 

SW-Component 

n 

AUTOSAR 

Interface 

standardized interface 

Application 


... 

Operating 

Systems

Virtual Integration 

Independent of hardware 

Virtual Functional Bus 

Introduction of HW Attributes 

Holistic view of the entire system, 

both tangible and intangible 

ECU Configuration 

Run Time Environment 

Separation of system into its ECU 

(plus common infrastructure) 

SW Component 

SW Component 

SW Description 

Description 

Component 

Description 

SW Component 1 


SW Component m 

AUTOSAR – System Design 

AUTOSAR – System Design – 

Implementation Process 

Input: Requirements & Vehicle Info 

System Constraint 

Description 

Generate System- & ECU- 

Generate System & ECU 

Configuration Generate System Description & ECU 

Configuration Description 

Configuration System Configuration 

Description 

ECU 1 

ECU n 

Generate Configuration 


Information Generate Configuration 

for each ECU 

Information for each ECU 

ECU Information 1 for each ECU 

ECU 2 

ECU n 

Generation of Software 


Executables Generation of for 

Modules for each 

Software each ECU 

ECU 

ECU Modules 1 for each ECU 

ECU 2 

ECU n 

ECU 1 

ECU 2 

ECU n 




on ECU 

on ECU 

on ECU 

ECU 1 

ECU 2 

ECU n 

ECU Resource 

ECU Resource 

ECU Description 

Description 

Resource 

Description 

Iterative corrections 

and/or optimizations 

(if required)

Abstract view 

Sensor/actuator comp. 

Sensor/actuator CCD. 

AUTOSAR – Sensor/Actuator 

Component Implementation 1 : CDD 

Phys. 

event 

HW 

ECU A 

other ECU or 

sensor/ actuator 

connected by bus 

HW 

sensor/ 

actuator 

AUTOSAR software architecture 

ECU 

HW 

ECU 

HW 

ECU 

SW 

SPAL 

SW COM 

Driver 

SW 

ECU abstr. 

SW 

CDD 

SW 

COM 

HW Sensor : Sensor/ Actuator, conversion physical value �� measurable quantity 

HW ECU : Input/Output circuit e.g motor gate drive (transistor bridge) , resistor-capacitor element, ... 

SW CDD : Complex Device Driver 

RTE 

Sensor SW 

Comp. 

SW Comp. 

Connectors 

AUTOSAR – Sensor/Actuator Component 

Implementation 2 : ECU abstraction 

Abstract view 


Sensor/actuator ECU abstr. 

Phys. 

event 

HW 

ECU A 

other ECU or 




HW 

sensor/ 

actuator 

ECU 

HW 

ECU 

HW 

ECU 

SW 

SPAL 

SW COM 

Driver 

SW 

ECU abstr. 

SW 

CDD 

SW 

COM 




RTE 

Sensor SW 

Comp. 

SW Comp. 

Connectors

AUTOSAR – Sensor/Actuator Component 

Implementation 3 : COM driver 

Abstract view 


Sensor/actuator COM 





VFB abstract 

solution 1 

SW- 

Comp. 

VFB 

Phys. 

event 

requirements 

resources 

SW comp. 

optional 

Sensor/ 

actuator 

Comp. 

HW 

ECU A 

other ECU or 



Sensor/ 

actuato 

r 

CDD 

HW 

sensor/ 

actuator 

ECU 

HW 

ECU 

HW 

ECU 

SW 

SPAL 

SW COM 

Driver 

SW 

ECU abstr. 

SW 

CDD 

SW 

COM 

RTE 

Sensor SW 

Comp. 

SW Comp. 

Connectors 

AUTOSAR – System View 

requirements 

resources 

Sensor/ 

actuator comp. 

solution 2 

SW- 

Comp. 

VFB 

optional 

Sensor/ 

actuator 

Comp. 

Different solutions are possible depending 

on sensor/actuator 

requirements/complexity. 

Sensor/ 

actuato 

r 

ECU 

abstractio 

n 

solution 3 

SW- 

Comp. 

VFB 

optional 

Sensor/ 

actuator 

Comp. 

Sensor/ 

actuato 

r 

COM 

LIN,CAN

Example: speed warning device 

= tool based 

SW-Component 

Template 

AUTOSAR – System Design 

Description 

„get_v()“ 

Description 

„v_warn()“ 

Function Bus Integrator 

Virtual Functional Bus 

� SW-Component-Description „get_v()“ describes a function to acquire the current vehicle speed 

and defines the necessary resources (such as memory, run-time and computing power 

requirements, etc.) 

� Function „v_warn()“ makes use of „get_v()“ 

� „Virtual Integration“ by check of 

- completeness of SW-Component-Descriptions (entirety of interconnections) 

- integrity/correctness of interfaces 

� The Virtual Functional Bus is completely absorbed in the AUTOSAR-Runtime-Environment (RTE) 

and Basic-SW later on 

AUTOSAR – Input Descriptions (1 of 3) 

� Step 1a): Description of SW-Components independently of hardware 

Draw-up SW-Component-Descriptions 

= tool based 

Description 

Information about each SW component 

e.g. get_v() 

- interfaces, behavior (repetition rate, ...) 

- direct hardware interfaces (I/O) 

- requirements on run-time performance 

(memory, computing power, throughput, 

timing/latency, …) 

- ... 

AUTOSAR-Description 

Editor 

SW Component 

3 

Description 

„get_v()“ 

... 

Description 

SW Component 

m

SW 

Component 

Description 

WP 2.1.1.1 

WP 2.1.2.1 

AUTOSAR – The SW Component 

Description 

SW Component Description 

� general characteristics (name, manufacturer, etc.) 

� Communication properties: � 

- p_ports 

- r_ports 

- interfaces 

- timing / schedule 

- signal quality 

� inner structure (composition) � 

- sub-components 

- connections 

� required HW resources: � 

- processing time 

- scheduling 

- memory (size, type, etc.) 

� performance � 

� safety � 


� Step 1b): Description of hardware independently of application software 

Draw-up necessary ECU-Resource-Descriptions for each electronic control unit 

= tool based 

Information about each ECU 

e.g. ECU1 

- sensors and actuators 

- hardware interfaces 

- HW attributes (memory, processor, 

computing power, …) 

- connections and bandwidths, etc. 

- ... 


Editor 

ECU-Resource 

-Description 

ECU 1

AUTOSAR – The ECU Resource Description 

ECU 

Resource 

Description 

WP 2.1.1.2 

WP 2.1.2.2 

ECU Resource Description 

� general characteristics (name, manufacturer, etc.) � 

� SIL � 

� temperature (own, environment, cooling/heating) � 

� power supply: - modes � 

- energy management 

� EMC � 

� available signal processing methods � 

� available programming capabilities � 

� diagnosis � 

� available HW: � - architecture (e.g. multiprocessor) 

- memory 

-µC 

- interfaces (CAN, LIN, MOST, FlexRay) 

- periphery (sensor / actuator) 

- connectors (i.e. number of pins) 

� SW below RTE for micro controller (amount, performance 

characteristics) � 

� signal path “Pin23(µC)=0x5678=symbolic name=phys. Variable” 

from Pin to ECU-abstraction � 


� Step 1c): Description of system constraints 

Draw-up System-Constraint-Description 

= tool based 

System Information 

overall system 

- bus systems, protocols, 

communication matrix and 

attributes (e.g. data rates, 

timing, …) 

- function clustering 

- function deployment 

(distribution to ECU) 

- ... 


Editor 

System- 

Constraint 

Description

AUTOSAR – The System Description 

System 

Constraint 

Description 

WP 2.1.1.3 

WP 2.1.2.3 

System Constraint Description 

� network topology � 

- bus systems: CAN, LIN, MOST, FlexRay 

- connected ECUs, Gateways 

- power supply, system activation 

� communication (for each channel) � 

- K-matrix 

- gateway table 

� Mapping / Clustering of SW components � 

� scheduling, task partition, priorities � 

� functional requirements (relevant to customer) ? 

- timing (end-to-end) 

-…. 

� Step 2: Distribution of SW-Component-Descriptions to all ECU in consideration of ECU- 

Resources available and constraints given in the System-Description 

Configuration on the basis of descriptions (not on the basis of implementations!) of SW-Components, 

ECU-Resources and System-Description 

Description 

AUTOSAR – System Configuration 

„get_v()“ 

... 

AUTOSAR-System Generator (Distribution of SW-Component-Descriptions 

considering ressources available) 

ECU-Resource 

-Description 

ECU 1 

Description 

„v_warn()“ 

ECU-Resource 

-Description 

ECU 2 

= tool based 

Description 

SW Component 

3 

ECU-Resource 

-Description 

ECU 3 

Description 

... 

SW Component 

n 

ECU-Resource 

-Description 

ECU m 

System- 

Constraint 

Description 

Configuration- 

Descript. Configuration- ECU1 

- Description Descript. Configuration- 1, ECU2 

- Description - Description Descript. 2, 5, ECUm 

- ... - Description - Description 6, k, 

- Resources - ... - Description n, 

- ... - Ressources - ... 

- ... - Ressources 

- ... 

... 

System Configuration 

Description 

- e.g. mapping of signals 

to CAN matrices 

- ... 

an iterative process

AUTOSAR – ECU-Configuration 

� Step 3: Generation of required configuration information for AUTOSAR-Infrastructure per ECU 

AUTOSAR - ECU Configuration Generator 

= tool based 

Configuration- 

Descript. ECU1 

- Description 1, 

- Description 2, 

- ... 

- Resources 

- ... 


Description 

- e.g. mapping of signals 

to CAN matrices 

- ... 

AUTOSAR-RTE-Config-Info 

- communication 

mechanisms 

- transport protocols 

- ... 

1) if need be extract for ECU1 only 

2) SPAL: Standardized Peripheral Abstraction Layer 

AUTOSAR-Configuration 

ECU1 

AUTOSAR-RTE-File 

- configuration of 

the AUTOSAR-RTE 

OIL-Files 


the OS 

SPAL DIL-File 1) 

- configuration 

of SPAL 

Config-Info files 

- NM, I/O, CAN 

protocols 

� Step 4: Generation of software executables required on the basis of the configuration information 

for each electronic control unit (example ECU1) 

AUTOSAR-Configuration 

ECU1 

AUTOSAR-RTE-File 


the AUTOSAR-RTE 

OIL-Files 


the OS 

SPAL DIL-File 1) 

- configuration 

of SPAL 

Config-Info files 

- NM, I/O, CAN 

protocols 

= tool based 

AUTOSAR – Generation of 

Software Executables 

AUTOSAR-Library 

- communication 

- transport 

protocols, ... 

(code, macros, 

Objects, ...) 

Tooling 

AUTOSAR-RTE 

Generator 1) 

OS 

Generator 1) 

SPAL- 

Generator 1) 

further 

Generators 

1) preliminary names 

SPAL 

etc 

- ... 

SW-Components ECU1 

(derived partially from the Virtual Function Bus) 

AUTOSAR-RTE 

OS 



Hardware

OS 

Example: view for one ECU 

� Implementation of functions independent on distribution on different ECU 

as communication will be done via ECU-individual AUTOSAR-RTE exclusively 

uint get_v (void) 

{ 

... 

return v; 

} 

void v_warn (void) 

{ 

... 

vn = get_v(); 

... 

return; 

} 

AUTOSAR – Implementation (1 of 2) 

Example: view for two ECU 

OS 

get_v() v_warn() ... 

AUTOSAR-RTE 

SW Component 

n-1 


core functions, SPAL 

Hardware Drivers 

� Implementation of functions independent on distribution on different ECU 

as communication will be done via ECU-individual AUTOSAR-RTE exclusively 

SW Component 

n 

AUTOSAR – Implementation (2 of 2) 

SW Com- 

get_v() 

ponent 2 

SW Com- SW Component 

n-1 ponent n ... 

uint get_v (void) 

{ ... 

return v; 

} void v_warn (void) 

{ ... 

vn = get_v(); 

return; 

} 





Bus system 

(FlexRay, CAN, MOST, ...) 

OS 

v_warn() 

SW Comp. ... 

n+1 

SW Comp. 

n+m-1 





SW Comp. 

n+m

phys. 

event 

HW 

ECU 

A 

Description 

Software Description 

Component Software 1 

Component 


Component 

Description 

Description 

Description 

ECU 1 


Component 


Component 

Description 

System 

Constraints 

AUTOSAR – Assignment of Basic 

SW Components 

HW 

Sensor/ 

actuator 

HW 

ECU 

HW 

ECU 

ECU 

ECU 

resource 

template 

SW 

SPAL 

SW 

COM Driver 

Basic-SW 

component 

SW 

ECU abstr. 

SW 

CDD 

SW 

COM 

HW Sensor : Sensor/Actuator, conversion physical value �� measurable quantity 



Allocate Software Components to different ECU 

Configuration 

Description 

ECU 1 

Configuration 

Description 

ECU n 

System 

Configuration 

RTE 

SW - 

component 

template 

Sensor SW 

Comp. 

SW-Comp. 

Connectors 

AUTOSAR –Methodology 

Software Generation 

System 

ECU 

Configuration 

Files 

generation 

ECU 

Configuration 

Files 

generation 

AUTOSAR 

RTE Files 

OIL Files 

Basic SW 

Files 

AUTOSAR 

RTE Tool 

OS Tool 

Basic SW 

Tools 

SoftComp*.o 

rte.c 

os.c 

*.c 

SPAL Files SPAL Tool spal.c 

AUTOSAR 

RTE Files 

OIL Files 

Basic SW 

Files 

SoftComp*.o 

AUTOSAR 

RTE Tool 

rte.c 

OS Tool os.c 

Basic SW 

Tools 

*.c 

SPAL Files SPAL Tool spal.c 

Compiler & Linker 

Compiler & Linker 

ECU 1 


Components 

AUTOSAR 

RTE 

OS 

Basic 


SPAL 

ECU n 


Components 

AUTOSAR 

RTE 

OS 

Basic 


SPAL

OEM a 

Platform a.1 

Platform a.2 

Platform a.n 

Exchangeability 

between 

manufacturer’s 

applications 

OEM b 

Platform b.1 

Platform b.2 

Platform b.n 

standards 

OEM f 

OEM e 

Platform e.1 

Platform e.2 

Platform e.n 

Supplier A 

�Chassis 

�Chassis 

�Safety �Safety 



�Multimedia 

�Multimedia 

Platform f.1 

Platform f.2 

Platform f.n 

Supplier B 

�� Chassis 

�� Safety 

�� Telematics 

�� Multimedia 

Supplier C 

�� Chassis 

�� Body/Comfort 

�� Telematics 

�� Multimedia 

Autosar Benefits 

The request 


between 

supplier’s 

solutions 


between 

vehicle 

platforms 

OEM c 

Platform c.1 

Platform c.2 

Platform c.n 

OEM d 

Platform d.1 

Platform d.2 

Platform d.n

AUTOSAR Standard Benefits 

� For new functions and vehicle projects 

� Facilitate EE architecture adaptation to car 

platforms 

� Allow function reuse and exchange in EE 

architectures 

� Integration of multi-tier functional modules 

� Facilitate use of COTS HW 

� For production vehicles 

� Facilitate embedded software update and 

upgrade 

� Ease ECU maintenance 

Summary AUTOSAR Architecture 

Software Layers 

� AUTOSAR Basic Software 

� AUTOSAR RTE Runtime Environment 

� AUTOSAR Application Level

Generic 

SW-C 

Description 

XML 

ECU 

Description 

XML 

System 

Description 

XML 

Configure System 

AUTOSAR Methodology 

EE Architecture ECU Software 

System 

Configuration 

XML 

Communication 

Matrix 

XML 

ECU Extract 

Per ECU Specific 

Custom 

System 

Configuration 

XML 


SW-C 

XML 

BSW Module 

Description 

XML 

Required 

Services 

XML 

Configure ECU 

Service Interfaces 

Atomic SW-C 

Allocation 

RTE, OS, … 

Other 

BSW 

Complete ECU Description 

Description de la 

XML 

configuration ECU 

Code Generation 

RTE 

OS 

COM 

Other BSW 

DIO 

SPI 

E2PROM 

AUTOSAR WP 1 – The AUTOSAR 

Concept 

� Specification of the mechanisms and interfaces of the virtual functional 

bus, Specification of OSAR Requirements on the basic Software Modules, 

Regarding Effects caused by Dependable Systems (high Availability, 

Safety-relevant) on the OSAR concept, … 

� 

� 1.1 Specification / Standardization 

WP 1.1.1 Specification of the mechanisms and interfaces of the virtual functional bus 

for AUTOSAR-compliant coding (e.g. function calls, memory access) [Prio 1] 

� Draft Specification: AR_Spec_of_VFB_WP111_V077_d.pdf 

WP 1.1.2 Specification of AUTOSAR requirements on the Basic Software Modules 

[Prio 1] 

� Draft Specification: AUTOSAR_SRS_BasicSWModules_V08d.doc 

� AUTOSAR_WP1.1.2_SoftwareArchitecture_V1.1.ppt 

� AUTOSAR_WP1.1.2_BasicSoftwareModules_V1.5.xls 

WP 1.1.3 Review of effects caused by dependable Systems (high availability, safetyrelevant) 

on the AUTOSAR concept [Prio 2] 

� Draft Specification: WP1.1.3_Analysis Document_V0.7_d.pdf 

WP 1.1.4 Consideration of Software-Component Transfer during operation and lifetime 

� WP 1.2 Coupling of graphical development tools to AUTOSAR (later project 

phase) 

� bold: WP is active (or complete), otherwise not yet underway 

ADC 

*.c 

*.c 

*.h *.h

AUTOSAR WP 2 – Input Formats 

for System Generation (1 of 2) 

� Specification of a description element for a software component 

(software component template) and a description element to 

handle available hardware resources (electronic control units, 

memory, computing performance, sensors, actuators, and so on). 

� 

� 2.1 Inputs 

� 2.1.1 Specification / Standardization 

WP 2.1.1.1 Specification of the Software Component Template [Prio 1] 

� Draft Specification: AUTOSAR_WP2.1.1.1_SWC-Attributes_v1.7_d.pdf 

� Draft Specification: AUTOSAR_WP2.1.1.1_ModelingGuide_v0.6_d.pdf 

� AR_WP2.1.1.1_ScopeInSWArch_V001_f.ppt 

� WP2.1.1.1_RTEfromDesignToImplementationView.ppt 

WP 2.1.1.2 Specification of the ECU Resource Template [Prio 1] 

� Draft Specification: WP2.1.1.2_DesignDocument_ResourceTemplateECU_V014_d_W97.pdf 

WP 2.1.1.3 Specification of the System-Constraint Template [Prio 2] 

� Draft Specification: AUTOSAR_SpecificationofSystemConstraintTemplateWP2113_V0.4_d.pdf 

� 2.1.2 Input Tools - Definition and implementation of tools for 

creating Software-Component/ ECU Resource/ System Constraint 

Descriptions from the respective Templates 

AUTOSAR WP 2 – Input Formats 

for System Generation (2 of 2) 

� WP 2.2 Algorithms and mechanisms of the 

AUTOSAR-System Generator 

� WP 2.3 System Generator Tool

AUTOSAR WP 3 – ECU 

Configuration 

� The ECU-configuration is the process delivering configuration 

files of the particular run time environment modules ( run time 

Environment & Basic-SW) for each specific ECU from the 

information (used resources, implemented software components 

and communication relations) that are generated by the OSAR 

system generator. 

� 


� 3.1.1 Specification / Standardization of Configuration Templates 

WP 3.1.1.1 Specification of the ECU Configuration Template 

WP 3.1.1.2 Specification of the System Configuration Template 

� 3.1.2 Tools for visualization of Configuration Templates 

WP 3.1.2.1 Tool for Visualization of ECU Configuration Template 

WP 3.1.2.2 Tool for Visualization of System-Configuration-Template 

� WP 3.2 Algorithms and mechanisms of the AUTOSAR ECU 

Configurator 

� WP 3.3 Definition and implementation of the tool to configure 

AUTOSAR ECUs (AUTOSAR ECU Configurator) 

AUTOSAR WP 4 – ECU Software 

Generation (1 of 2) 

� Specification / Standardization of the Input formats, Tools 

to create and visualize the input formats, Algorithms and 

Standards for the Run Time Environment, evaluation of 

“existing” Basis-SW, Hardware Abstraction Layer, 

AUTOSAR Run Time Environment Generator, … 

� 


� 4.1.1 Specification/standardization of the input formats 

WP 4.1.1.1 Specification of a Runtime Environment Configuration 

Language 

WP 4.1.1.2 Input formats of “existing” basic-SW 

WP 4.1.1.3 Specification of a HAL Configuration Language (HIS: 

Device Implementation Language, DIL) 

� 4.1.2 Tools to create and visualize the input formats 

WP 4.1.2.1 Implementation of a tool to create and visualize the 

configuration language of the AUTOSAR Runtime Environment 

WP 4.1.2.2 Definition and implementation of a tool to create and 

visualize the configuration language of “existing” Basic-SW 

WP 4.1.2.3 Definition and implementation of a tool to create and 

visualize the Device Implementation Language (DIL)

AUTOSAR WP 4 – ECU Software 

Generation (2 of 2) 

� 4.2 Algorithms/Standards 

� 4.2.1 AUTOSAR Runtime Environment 

WP 4.2.1.1 Specification / Standardization of the AUTOSAR Runtime 

Environment 

WP 4.2.1.2 Implementation of the AUTOSAR Runtime Environment 

WP 4.2.1.3 Qualification and conformance testing of the AUTOSAR 


� 4.2.2 ”Existing” Basic-SW 

WP 4.2.2.1 Specification / Standardization of ”existing” Basic-SW 

WP 4.2.2.2 Implementation of ”existing” Basic-SW 

WP 4.2.2.3 Qualification and conformance testing of ”existing” Basic-SW 

� 4.2.3 Hardware Abstraction Layer HAL 

WP 4.2.3.1 Specification / Standardization of the HAL 

WP 4.2.3.2 Implementation and testing of the HAL SW-Components 

WP 4.2.3.3 Qualification and conformance testing of the HAL 

� 4.3 Tooling 

WP 4.3.1 Definition and implementation of tools to generate the 

AUTOSAR Runtime Environment (AUTOSAR-RTE-Generator) 

WP 4.3.2 Generators for Basic-SW 

WP 4.3.3 Definition and Implementation of a tool to configure and 

generate the HAL 

AUTOSAR WP 5 – Test- and 

Integration Process 

� Product oriented Test and Integration; process 

oriented Integration. 

� 

� 5.1 Test and integration (product oriented) 

WP 5.1.1 Particular SW-Component tests (AUTOSARcompliance) 

WP 5.1.2 Integration of AUTOSAR-SW in ECU (Target-ECU) 

WP 5.1.3 Integration of the ECU into the system environment 

� 5.2 Integration (process oriented) 

WP 5.2.1 Creation of a process description 

WP 5.2.2 Exemplary demonstration of an application

AUTOSAR WP 10 – Data description 

� The content of this WP is the formulation of unified functional 

interfaces of all vehicle domains. Functional libraries are not 

expected. 

� Against that unified functions showing clear semantics of the 

interfaces are published in function catalogues of the AUTOSARpartnership 

(like the MOST function catalogues). 

� All specified functions have to satisfy the AUTOSAR-SW-Component- 

Template. Only description methods that are given in the AUTOSAR- 

SW-Component Template can be used. 

� WP 10.1 Data description for the functional domain body/comfort 

� Draft Specification: AUTOSAR_WP10.1_ExteriorLight_v1.0_d.pdf 

� AUTOSAR_ExteriorLight_v1.0_d.ppt 

� WP 10.2 Data description for the functional domain power train 

WP 10.3 Data description for the functional domain chassis/driving dynamics 

� WP 10.4 Data description for the functional domain safety 

� WP 10.5 Data description for the functional domain telematics/multimedia 

� WP 10.6 Data description for the functional domain man-machine-interface 

VFB Concept 

WP1.1.1 

AUTOSAR – WP Dependencies 

ECU Res 

Tool 

WP2.1.2.2 

Basic 

SWMod 

Concept 

WP1.1.2 

ECU Res 

Template 

WP2.1.1.2 

Not yet started Draft 

Started 

Some docs 

Final 

ECU Cfg 

WP3 

SWComp 

Template 

WP2.1.1.1 

Syst 

Const 

Template 

WP2.1.1.3 

ECU SW Gen 

WP4 

Syst Gen 

WP2.2 

SWComp 

Tool 

WP2.1.2.1 

Body/comfort 

Data desc 

WP10.1 

Syst Const 

Tool 

WP2.1.2.3 

Chassis/driving 

dynamics 

Data desc 

WP10.2 

Power Train 

Data desc 

WP10.3 

Other func 

domain 

Data desc 

WP10.X

AUTOSAR – Selected Documents 

[CDROM:\docs\misc] 

� Detailed overview of the AUTOSAR initiative: 

AUTOSAR_Detailed Version_V1.5_f.doc 

� Detailed description of all work packages: 

AUTOSAR_Workpackage Description_V2.14_r.doc 

� Definition of main requirements: 

AUTOSAR_MainRequirements_v1.5_d.doc 

� Definition of used terminology: 

AUTOSAR_Glossary_V1.4_r.doc 

� Separation of functions to domains: 

AUTOSAR_Domain Differentiation for Data Description_V1.4_d.ppt (WP10.x) 

� Overview project plan: 

Microsoft Project - AUTOSAR_Project Plan MSP98_V148.pdf 

1. The 

AUTOSAR 

Concept 

1.1 Specification 

1.1.1 VFB 

1.1.2 Basic SW 

1.1.3 Dependable Systems 

AUTOSAR – WP Participation 

2. AUTOSAR- 3. AUTOSAR 

Inputformats ECU 

2.1.1 Specification 

2.1 Inputs 

2.1.2 Input Tools 

2.2 Algorithms 

2.3 System Generator 


3.1 Inputs 

3.1.2 Tools 

3.2 Algorithms 

3.3 Autosar ECU Tool 


Workpackage 

4.1 Inputs 

4. ECU Software Generation 

4.3.1 Runtime Environment 


4.3.3 HAL 

5.1.1 SW-Component Tests 

5.1.2 Integration in ECU 

5.1.3 Integration in System 

5.2.1 Process Description 

5.2.2 Demonstration 

10. Data 

Description 

5.2 Integration 

(process oriented) 

10.1 Body/Comfort 

10.2 Power Train 

10.3 Chassis/Driving Dynamics 

10.4 Safety 

10.5 Telematics/Multidmedia 

10.6 Man-Machine Interface 

WP1.1.1 

WP1.1.2 

WP1.1.3 

WP1.1.4 

WP1.2 

WP2.1.1.1 

WP2.1.1.2 

WP2.1.1.3 

WP2.1.2 

WP2.2 

WP2.3 

WP3.1.1.1 

WP3.1.1.2 

WP3.1.2.1 

WP3.1.2.2 

WP3.2 

WP3.3 

WP4.1.1.1 

WP4.1.1.2 

WP4.1.1.3 

WP4.1.2.1 

WP4.1.2.2 

WP4.1.2.3 

WP4.2.1.1 

WP4.2.1.2 

WP4.2.1.3 

WP4.2.2.1 

WP4.2.2.2 

WP4.2.2.3 

WP4.2.3.1 

WP4.2.3.2 

WP4.2.3.3 

WP4.3.1 

WP4.3.2 

WP4.3.3 

WP5.1.1 

WP5.1.2 

WP5.1.3 

WP5.2.1 

WP5.2.2 

WP10.1 

WP10.2 

WP10.3 

WP10.4 

WP10.5 

WP10.6 

Volcano PM 1 1 1 3 3 3 3 3 1 1 1 1 1 1 2 2 2 2 2 2 1 1 1 2 2 2 3 3 3 3-5 

4.1.2 Tools 

blocked by PL Team 1 wish of PM 3 wish of PL Team 2 match between PM and PL Team 

4.2.1 Runtime Environment 

4.2 Algorithms, Standards 


4.2.3 Hardware Abstraction 

4.3 Tooling 

5. Testand 

Integration 

5.1 Test & Integration 

(product oriented) 

Ressource

�Prem 

ium 

Memb 

�Premium 

Member 

�PL-Team 

�Premium 

Member 


Start point: 

Premium Member Agreement signed 

and Integration Workshop was held 

Send request for participation 

in work groups to the Administrator 

Prepare decision making material 

Present decision making 

material to the PL-Team 

Decide on a active or passive 

participation in work packages 

Communicate the PL-Team 

decision to the premium member 

and the relevant work packages 

Responsible contact person sends the 

email address(es) of the participant(s) 

to the administrator 

�Administrator 

* * 

Active: 

Participation in work 

package meetings 


Admin@autosar.org 

Passive: 

Transparency 5 -6 


Active participation 

Send a confirmation 

(participant / cc to contact person) 

and the contact data of the relevant 

WP-Speaker to the premium 

member 

Get in contact to the WP-Speaker 

Discuss further integration steps 

(e.g. meetings, documents, …) 

Incorporate the email address to the 

relevant mailing list 


�Premium Member 

�WP-Speaker 


Passive participation 

Send a confirmation 

(participant / cc to contact person)

Document Owner 

� 

Document Responsibility 

Document Title 

Document Version 

Document Status 

Date 

26.02.04 

03.03.04 

09.03.04 

11.03.04 

19.03.04 

29.03.04 

31.03.04 

05.04.04 

13.04.04 

14.04.04 

26.04.200 

4 

1.0 

1.1 

1.2 

1.3 

1.4 

1.5 

1.6 

1.7 

1.8 

1.9 

1.10 

Document Information and Change 

History 

Version 

Changed by 

Eric Mariacher 

Eric Mariacher 

Peter Witzgall 

Fischer, Witzgall 









Prof. Heinecke AUTOSAR Spokesperson 

AUTOSAR_Company_GuidedTour_V1.10_d.ppt 

1.10 

 

Document Change History 

Change Description 

Premium introduction workshop 

Component implementation slides & update 

Update 

Template changes & update 

Corrections and changes 

Update and changes, WP participation process flow added 

Update 

Update 

Update 

Update, new VFB concept slide 

Update 

standards 

Autosar is not manual

SW Component 

SW Component 

SW Description 

Description 

Component 

Description 



SW Component m 

Development Process 

Input: Requirements & Vehicle Info 

System Constraint 

Description 

Generate System- & ECU- 

Generate System & ECU 

Configuration Generate System Description & ECU 




ECU 1 

ECU n 



Information Generate Configuration 

for each ECU 



ECU 1 

ECU 2 

ECU n 



Executables Generation of for 

Modules for each 

Software each ECU 

ECU 

Modules for each ECU 

ECU 1 

ECU 2 

ECU n 

ECU 1 

ECU 2 

ECU n 




on 

on 

ECU 

ECU 

on ECU 

� Scope of the standard support 

ECU 1 

ECU 2 

ECU n 

ECU 

ECU 

Resource 

Resource 

ECU 

Description 

Description Resource 

Description 

Iterative 

process… 

OEM 

Suppliers 

Tools for Autosar 

� Autosar meta model: 800 classes based of MOF with 

stereotypes extensions 

� The standardization is based on exchanging XML at every 

steps 

� Must be tooled: 

• Import 

• Design 

• Validate 

• Manage (rights, configuration, changes,..)

SW- 

Component 

Description 

ECU 

Resource 

Description 

(HW only) 

System- 

Constraint 

Description 

Configuration 

Component 

API 

Generator 

AUTOSAR 

System 

Configuration 

Generator 

decisions 

(e.g. mapping) 

Information / Database (no files) 

System Constraints 

Topology 

• which ECUs 

• how connected 


• ´which application 

SW-C 

(opt) CommMatrix 

• if already defined 

• Frames, Signals, 

Gateway tables 

Complex generation step: 

complex algorithm or engineering work 

(opt) Mapping 

• if already defined 

• which SW-C on which 

ECU 

• Which data in which 

Frame/Signal 

OEM 

Component 

API 

e.g. app.h 

System 

Configuration 

Description 

ECU 

extract of 

System 

Configuration 

ECU 

extract of 

System 

Configuration 

decisions 

(e.g. scheduling,..) 

AUTOSAR Tools 

AUTOSAR 

ECU 

Configuration 

Generator 

(unchanged) Topology 

• which ECUs 

• how connected 

(unchanged) Software 

• which application SW- 

C 

CommMatrix 

• Frames, Signals, 

Gateway tables 

Mapping 

• which SW on which 

ECU 

• which Data in which 

Frame/Signal 

ECU Configuration 

Description 

RTE 

Extract of 

ECU Config 

OS extract 

of ECU config 

e.g.OIL 

Basic SW Module 

Basic ASW 

Module 

extract Basic ASW 

of Module 

ECU extract configA 

of 

ECU extract configof 

ECU config 

list of 

inplementations of 

SW Components 

AUTOSAR 

RTE 

Generator 

Generator for 

OS, COM, ... 

Other Basic 

SW Generator 

MCAL- 

Generator 

Generation 

AUTOSAR Tools Use case 

AUTOSAR 

System 

Configuration 

Generator 


AUTOSAR 

System 

Configuration 

Generator 

ECU 

Extract 

Configuration 

Description 

First Tiers

AUTOSAR 

RTE 

Generator 

Generator for 

OS, COM, ... 

Other Basic 

SW Generator 

MCAL- 

Generator 

per ECU 

AUTOSAR RM 

AUTOSAR 

RTE Files 

OIL Files 

Basic SW 

Files 

MCAL Files 

Lib*.obj 

AUTOSAR 

RTE Tool 

AUTOSAR 

OS Tool 

Basis SW 

Tool 

MCAL Tool 

RTE.c 

OS.c 

*.c 

MCAL.c 

AUTOSAR Tools & SW 


Componenten*.c Software 

Compiler 

Linker 

Components 

AUTOSAR 

RTE 

OS 

Basic 


MCAL 

Tools Output Basic SW 

AUTOSAR Builder Tool Components 

� Autosar Requirement Management 

� AUTOSAR Authoring Tool, AAT 

� ECU Extract 

� SWC Conformance Validation Tool, SCVT 

� Generic Configuration Editor, GCE 

AUTOSAR Builder 

SWC Conformance 

Validation Tool 

Authoring Tool ECU Extract 

Generic Configuration 

Editor

Authoring Tool – SWC Conformance Validation 

GCE 

AUTOSAR Builder & 

AUTOSAR Architecture 

� Application Level, Description and Validation 

� BSW Level, Configuration 


ECU Extract 

AUTOSAR Builder & 

AUTOSAR Process 

� System Configuration & ECU Extract, Description and 

Validation 

� ECU Configuration, Configuration 

SCVT 

Authoring Tool ECU Extract 

GCE 

ECU Configuration

AUTOSAR Builder ATT 



EE Architecture Vision (Vehicle, Function, etc.) ECU Vision 


• Ressource Estimation 

RTE, BSW. 

• Communication Port 

• Memory 

• Sensors & Actuators 

• Gateway 

•… 


SW-C Desc. 

• Implementation 

•API 

• Composition 

• Resource Consumption 

• Mode Management 

• Calibration and 

Measurment 

SYSTEM Desc. 

• Topology 

• Mapping 

• Frames 

• Communication 

•… 

Integration of AUTOSAR Tools in AUTOSAR Process 

SW-C 

Description 

XML 

ECU 

Description 

XML 

System 

Description 

XML 

Decription of the infos for a EE Architecture 

SCVT 



Messagerie 

Système 

ECU Extract 

System 

Configuration 

SW-C Mapping 

according to the 

typology 

Decription of an ECU Configuration 

ECU Extract 

ECU 

extract 

GCE 

GCE GCE 

EXCEL 

System 

Configuration 

SW-Component 


BSW Module 

Description 

• Vendor Specific 

Service 

Requirements 

Description of the Configuration of a EE Architecture 

GCE 

GCE 

GCE 

GCE 

Authoring Tool - Ecu Extract GCE 

Configure ECU Generation of the 

Executable 

Interfaces Services 

Allocation 

Atomic SW-C 

RTE, OS, … 

Other 

BSW-M 

AAT 

Description of the Configuration of an ECU 

GCE 

EE Architecture ECU Software 


System 

Configuration 

XML 

Communication 

Matrix 

XML 

ECU Extract 

Per ECU Specific 

Systme 

Configuration 

XML 


SW-C 

XML 

BSW Module 

Description 

XML 

Required 

Services 

XML 

Configure ECU 

Service Interfaces 

Atomic SW-C 

Allocation 

RTE, OS, … 

Other 

BSW 

Complete ECU Description 

Description de la 

XML 

configuration ECU 

RTE 

Code Generation 

RTE 

OS 

COM 

Other BSW 

DIO 

SPI 

E2PROM 

ADC 

OS 

COM 

Other BSW-M 

DIO 

SPI 

E2PROM 

ADC 

*.c 

*.c 

*.h *.h

AUTOSAR Builder Platform Architecture 

� Eclipse Plug-in mechanism 

� Leverage on the mature existing tools in the market 

� Open Framework adapted to System Engineering 

Plug-in 

Plug-in 

Plug-in 

Plug-in 

Requirement Traceability 

Change Management & Variant handling 

Starting Points: ECLIPSE 

Configuration Management 

Design Repository 

Tool Architecture

� Model management 

Technical infrastructure 

� UML/MOF/MDS (model driven schema) to EMF 

� Multi resources support (files, database) 

� Model validation 

� Model extension, AUTOSAR profiles 

� Model editing 

� Tree view, forms, XML model of GUI, EMF methods generation 

� Graphical editor, Topcased 

� Collaborative support 

� Svn integration 

� Documentation 

� Jet & Birt technologies, 

� Creating jet code from the meta model 

� Code Generation 

� Jet 

� External Tool integration 

TNI’s tools 

� Autosar Builder Authoring Tool provides a specialized tool for creation of 

AUTOSAR SWC, ECU and System descriptions. 

� It provides a large subset of the AUTOSAR meta-model 

� which can be used to create complete descriptions. 

� It represents the description data organized in templates and root ARPackages. 

� Mixed representation of file and AUTOSAR elements

… Look and feel 

� It represents the AUTOSAR elements in a Tree View 

� In a tight accordance with AUTOSAR meta-model template 

� Add of intermediate grouping nodes to facilitate the comprehension and 

correct usage of AUTOSAR modeling templates. 

� For each AUTOSAR element it shows properties in Forms 

� Properties are grouped in several tabs 

� Menus options are added for managing References, etc … 

…Forms

� Graphical Editor 

� Show existing elements in a diagram 

� Create new elements 

…Graphics 

…Rules 

� Rules checking 

� Prevent the user from entering inconsistent/invalid data 

� Notify the user of committed/potential errors 

� Navigate from an error to the AUTOSAR element 

� Automatic fixing when possible

Exemple… 

Exemple…

Exemple… 

ECU Resource

SwC Design Elements 

SwC 

Compositions

SwC 

Compositions 

Delegation Connections

Assembly Connections 

Assembly Connections of Atomic Software 

Components

SwC Internal Behavior 

SwC Internal Behavior 

Runnables and Events

TNI Software Agenda - Irisa

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?