AUTOSAR Configuration Process

- How to handle 1000s of parameters

Webinar 2013-04-19

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

V2.0 2013-04-18
Agenda

> Introduction

AUTOSAR ECU Configuration Description

ECU Configuration Workflow

Multi-User Workflow

Webinar Series

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

Slide: 2
Introduction
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)*
2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.

Slide: 3
Introduction
AUTOSAR Method

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

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

Slide: 4
Introduction
AUTOSAR Method
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

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

Slide: 5
Introduction
AUTOSAR Method

ECU Configuration 1000s of parameters

Description Large XML file
Realistic file size
RTE Small ECU: e.g.
Config 10 MB
Large ECU: e.g.
50 MB
OS Config

Basic SW
Module A
Config

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

Slide: 6
Agenda

Introduction

> AUTOSAR ECU Configuration Description

ECU Configuration Workflow

Multi-User Workflow

Webinar Series

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

Slide: 7
AUTOSAR ECU Configuration Description
What is a parameter?

Parameter References
Parameter
Definition

Name
Value of the parameter
Multiplicity (e.g. 0..1, 1..n) within the configuration of
Type (integer, enum, ) a concrete ECU

Min/Max values, literals

Description

Example: Example:
Name: NvmBlockUsedCrcType NVM_CRC16
Multiplictiy: 1:1
Type: enum (NVM_NOCRC, NVM_CRC16,
NVM_CRC32)

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

Slide: 8
AUTOSAR ECU Configuration Description
Containers and Parameters

Parameters are hierarchically organized in Containers

A container consists of
Parameters
sub-containers

Container References
Container
Definition

References
Parameter
Parameter
Definition

References
Parameter
Parameter
Definition

Container References
Container
Definition

References
Parameter
Parameter
Definition

Example:
Name: NvmBlockDescriptor
Multiplictiy: 1:65536
2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.

Slide: 9
AUTOSAR ECU Configuration Description
Basic Software Module Description

Basic Software Module Description (BSWMD) contains

Parameter definitions
Preconfigured values, recommended values
XML format
Schema defined by AUTOSAR
Content defined by BSW vendor
May contain AUTOSAR standard parameters, and vendor specific parameters
Typically one file per BSW module

Application
RTE

COM

DIAG

Complex Drivers
xml J1939TP

MEM
SYS

MOST

IO
LIN

FR
OS

IP
CAN
Basic SW Module
XCP

Network
Description Services
Library
(BSWMD)
CAL EXT

Microcontroller

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

Slide: 10
AUTOSAR ECU Configuration Description
Challenges

Degree of freedom is reduced by

Parameters (indirectly) given by the OEM
> Network communication description
> Parts of the diagnostic description
Parameters given by preconfiguration (preconfigured by the basic SW
supplier)
But
Still there are lots of parameters to be set
Dependencies between parameters
Additional challenges due to project situation
> Several developers work in parallel at the same ECU
> BSW is supplied by several vendors (e.g. Vector, micro-controller
manufacturer)

Key for success: configuration tools

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

Slide: 11
AUTOSAR ECU Configuration Description
Tool Support

Comfort Views
Structured display of the ECU configuration
Assistance for creating the configuration
Derive parameters from the ECU Extract of System Description
Automatic baud rate calculation, hardware masks
Automatic fragmentation of EEPROM blocks,
Validation (e.g. is configuration of FullCAN objects consistent)

Support for integration of MCALs and

add-on modules
Migration (platform switch)
Development of tool extensions
(Validation rules, configuration GUI,
code generators)

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

Slide: 12
Agenda

Introduction

AUTOSAR ECU Configuration Description

> ECU Configuration Workflow

Multi-User Workflow

Webinar Series

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

Slide: 13
ECU Configuration Workflow
Overview

PREEvision

DaVinci Developer

Input files provided by

.xml
.XML DBC OEM Embedded Coder
LDF
Contains communication Software Component
ECU Extract of
Fibex information, needed Description files
System for the ECU TargetLink
Description
provided by
OEM DaVinci Configurator Pro
Contains Configuration of RTE + BSW
system
information,
needed for the SystemDesc
ECU Conversion RTE header and
.c .h code files
SWC header files
.xml Editing and
ECU Extract of BSW module
System Description
Generation
.c .h configuration header
and code files
.cdd/ Base ECUC
.odx Generation
CANdela
Diagnostic Data
.xml Other AUTOSAR tools
ECU Configuration
Description

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

Slide:
 ECU Configuration Workflow
Integration of third party BSW (MCALs, Complex Driver)

DaVinci Configurator Pro

Configuration of RTE + BSW
MICROSAR
MICROSAR
Comfort Editors
BSWMD RTE header and
.c .h code files
SWC header files

Generic
BSW module
Configuration Editor
.c .h configuration header
Third Party and code files
Eparm
GUI
BSWMD creation
BSWMD Plug-in Third Party
Code Generator BSW module
Plug-in .c .h configuration header
and code files

Third Party
BSW module
External .c .h configuration header
Code Generator and code files

Configuration and Generation

Via standard tool features (Generic Configuration Editor, call of external code generators)
Via specific Plug-Ins (GUI, code generator based on DaVinci Configurator technology)

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

Slide:
Agenda

Introduction

AUTOSAR ECU Configuration Description

ECU Configuration Workflow

> Multi-User Workflow

Webinar Series

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

Slide: 16
Multi-User Workflow
General

Several developers are working in parallel at the same AUTOSAR ECU

Integration effort must be small
AUTOSAR configuration artifacts (AUTOSAR XML files) must be managed
consistently with other artifacts of ECU development (code files,
specification documents, test environments, ...)
Use customers CM (configuration management) system

Developer 1 Developer 2

AUTOSAR ECU

Developer 3 ECU SW Integrator

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

Slide: 17
Multi-User Workflow
Responsibilities

Several possible ways to organize responsibilities, e.g.

Component responsibles Component

Component SWC1 SWC2
Each component (e.g. SWC, BSW Developer 1 Developer 2
module or cluster) has one RTE
responsible ECU SW
Component OS CAN MEM
Only the component responsible is Developer 3 Integrator
BSW
allowed to change the component
AUTOSAR ECU

Feature responsibles
Feature developer makes changes Feature Feature
SWC1 SWC2
in potentially all SWCs or BSW Developer 1 Developer 2
modules RTE

Overlapping modifications several OS CAN MEM ECU SW

users change e.g. same SWC Integrator
BSW
No strict assignment of user to AUTOSAR ECU
SWC/BSW-Module

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

Slide: 18
Multi-User Workflow
Access Strategy

Two general approaches regarding development process/access strategy

Concurrent editing
Several persons change in parallel
the same objects (e.g. SWCs or
BSW module configurations)
Typically realized via branches in a merge
configuration management (CM)
system v0 v1 v2 v3
Requires diff/merge CM

Exclusive editing
Only one person allowed to change
an object
Typically realized via check-out
control strategy of CM system
v0 v1 v2 v3
Requires sequencing of work CM
packages difficult to organize!
Avoids merge

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

Slide: 19
Multi-User Workflow
Tool Support

Standalone Diff-Tool

Compare two ARXML files (any content)
Show differences in native view
A

B

DaVinci Tools

Generic diff/merge of SWCs and ECUC
Read-only display of objects like SWCs,

Result

Port Interfaces, Data Types, modules

Available for all relevant objects, e.g.
> SWCs
> Port Interfaces
> Data Types
> Module Configurations

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

Slide: 20
Multi-User Workflow
Fine-grained Configuration Management

Split-up the project data into several files

Define access rights based on individual files (reflected in file state r/o vs. r/w)
Only the modified files need to be merged
File granularity can be selected when setting-up the project
Single file
Split files

r/w r/w
SWCs SWC1 SWC2
(DaVinci DCF
SWC1
.xml
SWC2
.xml
... ECU_
Comp
.xml RTE
Workspace)
OS CAN MEM
BSW Config Os. CanIf. Rte.
(Split ECUC Files) xml xml
CanTp.
xml xml ... BSW

ECU1

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

Slide: 21
Webinar Series

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

2013-01-22 Analyzing and testing of ECU-internal (AUTOSAR) parameter using

CANoe.XCP and CANoe.AMD
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-06-05 AUTOSAR System and Software Design with PREEvision

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 Vectors training services:

http://www.vector.com/vi_training_en.html

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

Slide: 22
 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

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

Slide: 23