webinar slides: introduction to the autosar method for ... 6 vfb virtual function bus swc1 swc2 swc3...

© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.

V2.1 2013-04-16

AUTOSAR Method

Webinar 2013-04-17


Slide:

Agenda

> Introduction

AUTOSAR Method

Exchange Formats

Workflows OEM-TIER1

Workflows TIER1

Webinar Series

2


Slide: 3

Introduction

Applications

Basic Software (BSW)

The ECU is configured based on the DBC, FIBEX, LDF file.

ECU1 ECU2

DBC, FIBEX, LDF

Network communication of the vehicle is specified

ECU

Current Workflow (non-AUTOSAR)


Slide:

Introduction

4

New Terms in AUTOSAR – What do they mean?

Virtual Function Bus

AUTOSAR XML

System Description

ECU Configuration

Software Component

Basic Software

System Template


Slide:

Agenda

Introduction

> AUTOSAR Method

Exchange Formats

Workflows OEM-TIER1

Workflows TIER1

Webinar Series

5


Slide: 6

VFB


SWC1

SWC2 SWC3

AUTOSAR Method

Software Component Description*

Complete SW functionality of the vehicle is defined as a system of SWCs...

ECU ConfigurationDescription (ECUC)*

*

SWC1 SWC2

Basic Software (BSW)

RTE

The ECU is configured based on the ECU Extract.

ECU1

SWC1

SWC2

ECU2

SWC3

System Description*

..and distributed to ECUs

Extract of System Description*

An extract is created for each ECU...

ECU1

SWC1

SWC2


Slide: 7

AUTOSAR MethodExample: Components view for interior lighting control

LightSwitch

Right Door

Door Contact

Dimmer

Left Door


Slide: 8

Door

Contact

AUTOSAR Method


Right

Door

Example: Communication

Dimmer LightLeft

DoorSwitch

SoftwareComponents

Ports Connector


Slide: 9

Roof ECU

RTE

Basic SW

Controller

Front ECU

Controller

Basic SW

AUTOSAR Method

SwitchLeft

DoorDimmer Light

RTE

Example: Distribution of components

Bus

Door

Contact

Right

Door


Slide:

Agenda

Introduction

AUTOSAR Method

> Exchange Formats

Workflows OEM-TIER1

Workflows TIER1

Webinar Series

10


Slide: 11

Exchange FormatsTemplates and Description Files

Standardized set of design artifacts

Associated XML Schema

Defined by

SW ComponentDescription

ECU ResourceDescription

SystemDescription

SW ComponentTemplate

ECU ResourceTemplate

SystemTemplate

Concrete specification based on the Template

Represented as XML file

Defined by the OEM or TIER1

Templates Descriptions


Slide: 12

Exchange FormatsSoftware Component 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”.

The AUTOSAR “Software Component Description” contains the following information SWC

SW ComponentDescription


Slide: 13

Exchange FormatsECU Resource 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”.

The AUTOSAR “ECU Resource Description” contains the following information

ECUECU Resource

Description


Slide: 14

Exchange FormatsSystem Constraint 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”.

The AUTOSAR “System Constraint Description” contains the following information:

SystemConstraintDescription


Slide: 15

Exchange FormatsSystem Description

SW-ComponentDescription

System-Constraint Description

ECU Resource

Description(HW only)

System Description

AUTOSAR System

ConfigurationEditor

Decisions- mapping of ports to communication signals- mapping of SWCs to ECUs

AUTOSAR System

DescriptionExtractor

ECU 1 Extract

ECU 2 Extract

ECU n Extract

iterative process

The AUTOSAR “System Description” contains the actual configuration of the overall system

The AUTOSAR “ECU Extract of System Description” contains the subset for one ECU


Slide:

Agenda

Introduction

AUTOSAR Method

Exchange Formats

> Workflows OEM-TIER1

Workflows TIER1

Webinar Series

16


Slide: 17

Workflows OEM-TIER1

TIER1

arxml

ECU-specific extract

OEM

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

TIER1 configures AUTOSAR ECU based on this extract

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

AUTOSAR Workflow with OEM and TIER1

arxml

System Description(SYSD)

arxml

ECU Configuration(ECUC)


Slide: 18

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

Workflows OEM-TIER1Challenges

AUTOSAR XML format allows also ECUEX files with only a subset of this content!


Slide: 19

Workflows OEM-TIER1ECU-specific extract of system design

xml

ECU1

SWC2 SWC3

SWC4

ServiceSWC1

ECU Extract (ECUEX) ECU Composition OEM SWCs (same as in SYSYEX)

Atomic SWCs No Compositions

TIER1 SWCs (not part of SYSEX) Atomic SWCs Service SWCs

Service Mapping Communication Data Mapping

“Flattening”

ECU Composition

xml

ECU1

Comp1SWC3

SWC4

System Extract (SYSEX) ECU Composition OEM SWCs (subset of SYSD)

Atomic SWCs Compositions Typ. no service SWCs

Communication Data Mapping

ECU Composition

AUTOSAR 4

Comp2

ECU1

Comp1

SWC2SWC3

SWC4

ServiceSWC1

ECU Extract (ECUEX) ECU Composition OEM SWCs (subset of SYSD)

Atomic SWCs Compositions

TIER1 SWCs (not part of SYSD) Atomic SWCs Compositions Service SWCs

Service Mapping Communication Data Mapping

ECU Composition

AUTOSAR 3


Slide: 20

Workflows OEM-TIER1

TIER1 OEM

Communication

Compositions

Atomics

ServiceComponents

Data Mapping

ServiceMapping

ECU Composition

Example 1:Network-oriented approach

Communication

Compositions

Atomics

ServiceComponents

Data Mapping

ServiceMapping

ECU Composition

Example 2: Functional system design approach

Communication

Compositions

ServiceComponents

Data Mapping

ServiceMapping

ECU Composition

Atomics

Example 3:Functional system design approach with OEM SWCs

AUTOSAR XML format allows any degree of freedom!

Content of ECU-Extract provided by OEM - Examples


Slide: 21

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

Workflows OEM-TIER1Experiences


Slide: 22

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

Workflows OEM-TIER1

DaVinci Developer

DaVinci Configurator

Pro

xml

ECU-specific extract

Tool Support


Slide:

Agenda

Introduction

AUTOSAR Method

Exchange Formats

Workflows OEM-TIER1

> Workflows TIER1

Webinar Series

23


Slide: 24

Workflows TIER1

BaseECU

ConfigurationGenerator

RTE Config

OS Config

ECU ConfigurationDescription (XML)

Basic SW Module A

Config

List of implementations

of SW Components

AUTOSAR RTE

Configurator

Configurator forOS, COM, etc.

Configurator for other Basic

SW

MCAL Configurator

ECU Configuration

ECU Extract(XML)


Slide: 25

Workflows TIER1Component development process

Component Implementation

(*.c)Implement Component

PerformUnit Test

Generate Component

API

ComponentAPI(*.h)

SW Component Description

(XML)

CreateTest Cases

ComponentTest Cases


Slide: 26

Workflows TIER1

AUTOSAR RTE

Generator

Generator forOS, COM, ...

Other Basic SW Generator

MCAL Generator

RTE.c

OS.c

*.c

MCAL.c

Software components *.c

Software Components

AUTOSAR RTE

OS

other Basic Software

MCAL

Library *.obj

Executable ECU

RTE Config

OS Config

ECU ConfigurationDescription

Basic SW Module A

Config


Slide:

Workflows TIER1Tool Support


Slide: 28

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: 29

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

webinar slides: introduction to the autosar method for ... 6 vfb virtual function bus swc1 swc2 swc3...

Documents