Vector Webinar AUTOSAR Method 20130417 PDF

AUTOSAR Method
Webinar 2013-04-17
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
V2.1 2013-04-16
Agenda
> Introduction
AUTOSAR Method
Exchange Formats
Workflows OEM-TIER1
Workflows TIER1
Webinar Series
Slide: 2
Introduction
Current Workflow (non-AUTOSAR)
Network communication of the The ECU is configured based

vehicle is specified on the DBC, FIBEX, LDF file.
ECU
ECU1 ECU2
Applications
Basic Software
(BSW)
DBC, FIBEX, LDF
Slide: 3
Introduction
New Terms in AUTOSAR – What do they mean?
System Description
Virtual Function System Template

Bus
AUTOSAR XML
ECU
Configuration
Basic Software
Software
Component
Slide: 4
Agenda
Introduction
> AUTOSAR Method
Exchange Formats
Workflows OEM-TIER1
Workflows TIER1
Webinar Series
Slide: 5
AUTOSAR Method
Complete SW functionality of the vehicle is

..and distributed 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 based

each ECU... on the ECU Extract.
ECU1 SWC1 SWC2
SWC1
RTE
SWC2
Basic Software
(BSW)
ECU Configuration *
Extract of System Description* Description (ECUC)*
Slide: 6
AUTOSAR Method
Example: Components view for interior lighting control
Right Door
Door Contact
Left Door
Dimmer
Switch Light
Slide: 7
AUTOSAR Method
Example: Communication
Software
Components
Left Right Door

Switch Dimmer Light
Door Door Contact
Virtual Function Bus
Ports Connector
Slide: 8
AUTOSAR Method
Example: Distribution of components
Roof ECU Front ECU
Door Left Right

Switch Dimmer Light
Contact Door Door
RTE RTE
Basic SW Basic SW
Controller Controller
Bus
Slide: 9
Agenda
Introduction
AUTOSAR Method
> Exchange Formats
Workflows OEM-TIER1
Workflows TIER1
Webinar Series
Slide: 10
Exchange Formats
Templates and Description Files
Templates Descriptions
SW Component SW Component
Template Description
ECU Resource ECU Resource

System System
 Standardized set of design artifacts  Concrete specification based on the

Template
 Associated XML Schema
 Represented as XML file
 Defined by
 Defined by the OEM or TIER1
Slide: 11
Exchange Formats
Software Component Description
The AUTOSAR “Software Component

Description” contains the following SW Component
information SWC Description
 Ports and Interfaces (sender/receiver, client/server)

 Runnable Entities with trigger events, port access, etc
 Resource needs of the component (memory, CPU time, etc.)
 Structure and format are described by the “Software Component

Template”.
Slide: 12
Exchange Formats
ECU Resource Description
The AUTOSAR “ECU Resource ECU

Description” contains the following ECU Resource
information Description
 Description of the hardware being used

> Sensors, actuators
> Memory
> Processor
> Communications periphery
> Pin assignments
 The structure and format are described by the “ECU Resource

Template”.
Slide: 13
Exchange Formats
System Constraint Description
The AUTOSAR “System Constraint System

Description” contains the following Constraint
information: Description
 Information of network topology

 Limitations (“Constraints”)
 Protocol
 Given communication matrix (PDUs, signals, …)
 Baud rate, timing
 Structure and format are described by the “System Template”.
Slide: 14
Exchange Formats
System Description
Decisions
- mapping of ports to communication signals
- mapping of SWCs to ECUs
SW-
Component
Description ECU 1
Extract
System- AUTOSAR AUTOSAR

Constraint System System System ECU 2
Description Configuration Description Description Extract
Editor Extractor
ECU
Resource ECU n
Description Extract
(HW only)
iterative process
The AUTOSAR “System Description” The AUTOSAR “ECU Extract of

contains the actual configuration of System Description” contains
the overall system the subset for one ECU
Slide: 15
Agenda
Introduction
AUTOSAR Method
Exchange Formats
> Workflows OEM-TIER1
Workflows TIER1
Webinar Series
Slide: 16
Workflows OEM-TIER1
AUTOSAR Workflow with OEM and TIER1
 OEM creates an ECU-specific extract of the vehicle system design

 TIER1 configures AUTOSAR ECU based on this extract
OEM TIER1
arxml arxml arxml
System Description ECU Configuration

ECU-specific extract
(SYSD) (ECUC)
Note: “OEM” and “TIER1” may also be organizational units within one company (“System Responsible” vs. “ECU responsible”)
Slide: 17
Workflows OEM-TIER1
Challenges
 Typically, an OEM cannot provide the full content of the ECU-specific

system design because
 Some content is only known after ECU integration (e.g. Service
Components)
 Some content is not in the responsibility of the OEM (e.g. SW
implementation details)
 Consequence
 TIER1 must complete the ECU-specific system design
> Different approaches in AUTOSAR 3 and AUTOSAR 4
 Iterations must be supported: TIER1 work must not be lost when

getting updated system description from OEM
AUTOSAR XML format allows also ECUEX files with only a subset of this content!
Slide: 18
Workflows OEM-TIER1
ECU-specific extract of system design
AUTOSAR 3 AUTOSAR 4
ECU1 ECU1
System Extract (SYSEX)
ECU Composition
 ECU Composition ECU Composition
Comp1 Comp1
Comp2  OEM SWCs (subset of SYSD)
SWC3  Atomic SWCs SWC3
SWC2
 Compositions SWC4
SWC4
 Typ. no service SWCs
 Communication
Service
 Data Mapping xm
SWC1
l
“Flattening”
ECU Extract (ECUEX) ECU Extract (ECUEX) ECU1

 ECU Composition  ECU Composition
ECU Composition
 OEM SWCs (subset of SYSD)  OEM SWCs (same as in SYSYEX)
 Atomic SWCs  Atomic SWCs SWC3
SWC2
 Compositions  No Compositions
SWC4
 TIER1 SWCs (not part of SYSD)  TIER1 SWCs (not part of SYSEX)
Service
 Atomic SWCs  Atomic SWCs
SWC1
 Compositions  Service SWCs
 Service SWCs  Service Mapping
 Service Mapping  Communication
 Communication  Data Mapping
 Data Mapping
Slide: 19
xml
Workflows OEM-TIER1
Content of ECU-Extract provided by OEM - Examples
Example 1: Example 2: Example 3:

Network-oriented Functional system Functional system design
approach design approach approach with OEM SWCs
Service Service Service

Components Components Components
Service Service Service

Mapping Mapping Mapping
Atomics Atomics Atomics
Compositions Compositions Compositions
Data Mapping Data Mapping Data Mapping
ECU Composition ECU Composition ECU Composition
Communication Communication Communication
AUTOSAR XML format allows any degree of freedom! TIER1 OEM

Slide: 20
Workflows OEM-TIER1
Experiences
 Ideal situation: clearly separated responsibility regarding the content of

the ECUEX
 No conflicts due to concurrent modification of same content by OEM
and TIER1
 Realistic: TIER1 requires flexibility to make modifications within content
created by OEM
 Add TIER1 standard SW, which is not in responsibility of OEM
> Additional ports (Service Ports, Application Ports)
> Additional top-level components
 Define additional networks, which are not in responsibility of OEM

> e.g. private CAN within the ECU, LIN to sensor cluster
 Fix issues in the OEM content to avoid delays in development
Slide: 21
Workflows OEM-TIER1
Tool Support
 Tool support for iterations in the workflow (supports the mentioned use
cases)
 Set up a project based on an ECUEX from OEM
 Allow modification of design data by TIER1
 Incorporate changes in the ECUEX via automatic update/merge
> Update the design data, which were originally imported via ECUEX
> Keep the design data added by TIER1 unchanged
 Convenience
 Diff viewer to analyze the modifications
 Automation of update workflow
DaVinci
Developer
xml
DaVinci
Configurator
ECU-specific
Pro
extract
Slide: 22
Agenda
Introduction
AUTOSAR Method
Exchange Formats
Workflows OEM-TIER1
> Workflows TIER1
Webinar Series
Slide: 23
Workflows TIER1
ECU Configuration
List of
implementations
of SW
Components
ECU Configuration
Description (XML) AUTOSAR
RTE
Configurator
RTE
Config
Base Configurator for

ECU Extract OS, COM, etc.
ECU
(XML) Configuration
Generator OS Config
Configurator
for other Basic
SW
Basic SW
Module A
Config MCAL
Configurator
Slide: 24
Workflows TIER1
Component development process
Component Component
Generate Implement Implementation
Component API Component
(*.h) (*.c)
API
SW Component
Description Perform
(XML) Unit Test
Create Component
Test Cases Test Cases
Slide: 25
Workflows TIER1
Executable ECU
Library
*.obj
Software components
*.c
Software
ECU Configuration AUTOSAR Components
Description RTE
RTE.c
Generator
RTE AUTOSAR RTE

Config
Generator for
OS.c
OS, COM, ...
OS Config OS
Other Basic
*.c
SW Generator other Basic
Software
Basic SW
Module A MCAL MCAL.c
Config Generator MCAL
Slide: 26
Workflows TIER1
Tool Support
Slide:
Webinar Series
 The webinar series about AUTOSAR (http://www.vector.com/vi_autosar_webinars_en.html):
 2013-03-12 ECU development with AUTOSAR - An introduction for AUTOSAR beginners

 2013-04-16 Introduction to the AUTOSAR Method for ECU development
 2013-04-19 AUTOSAR Configuration Process - How to handle 1000s of parameters
 2013-04-26 Reliable Testing of AUTOSAR ECUs
 2013-05-07 MICROSAR Safe: AUTOSAR basic software for safety-relevant ECUs (ISO 26262)
 2013-01-22 Analyzing and testing of ECU-internal (AUTOSAR) parameter using
CANoe.XCP and CANoe.AMD
 Various Webinars on MICROSAR OS – the AUTOSAR operating system from Vector
http://www.vector.com/vi_operatingsystems_webinars_en.html
 Registration to the upcoming Webinars and the list of recorded Webinars:

http://www.vector.com/vi_webinars_en.html
 The overview of Vector’s training services:

http://www.vector.com/vi_training_en.html
Slide: 28
Thank you for your attention.
For detailed information about Vector

and our products please have a look at:
www.vector.com
Author:
Vector Informatik GmbH

Ingersheimer Str. 24
70499 Stuttgart
Slide: 29

Vector Webinar AUTOSAR Method 20130417 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vector Webinar AUTOSAR Method 20130417 PDF

Uploaded by

Copyright:

Available Formats

AUTOSAR Method

Network communication of the The ECU is configured based

DBC, FIBEX, LDF

Virtual Function System Template

> AUTOSAR Method

Complete SW functionality of the vehicle is

Virtual Function Bus

Software Component Description* System Description*

An extract is created for The ECU is configured based

ECU1 SWC1 SWC2

Left Right Door

Virtual Function Bus

Roof ECU Front ECU

Door Left Right

> Exchange Formats

ECU Resource ECU Resource

 Standardized set of design artifacts  Concrete specification based on the

The AUTOSAR “Software Component

information SWC Description

 Ports and Interfaces (sender/receiver, client/server)

 Structure and format are described by the “Software Component

The AUTOSAR “ECU Resource ECU

 Description of the hardware being used

 The structure and format are described by the “ECU Resource

The AUTOSAR “System Constraint System

 Information of network topology

 Structure and format are described by the “System Template”.

System- AUTOSAR AUTOSAR

The AUTOSAR “System Description” The AUTOSAR “ECU Extract of

> Workflows OEM-TIER1

 OEM creates an ECU-specific extract of the vehicle system design

arxml arxml arxml

System Description ECU Configuration

 Typically, an OEM cannot provide the full content of the ECU-specific

 Iterations must be supported: TIER1 work must not be lost when

ECU Extract (ECUEX) ECU Extract (ECUEX) ECU1

Example 1: Example 2: Example 3:

Service Service Service

Service Service Service

Atomics Atomics Atomics

Compositions Compositions Compositions

Data Mapping Data Mapping Data Mapping

ECU Composition ECU Composition ECU Composition

Communication Communication Communication

AUTOSAR XML format allows any degree of freedom! TIER1 OEM

 Ideal situation: clearly separated responsibility regarding the content of

 Define additional networks, which are not in responsibility of OEM

 Fix issues in the OEM content to avoid delays in development

> Workflows TIER1

Base Configurator for

RTE AUTOSAR RTE

 The webinar series about AUTOSAR (http://www.vector.com/vi_autosar_webinars_en.html):

 2013-03-12 ECU development with AUTOSAR - An introduction for AUTOSAR beginners

 Registration to the upcoming Webinars and the list of recorded Webinars:

 The overview of Vector’s training services:

For detailed information about Vector

Vector Informatik GmbH

You might also like