Vector Webinar: AUTOSAR Configuration Process - … management (CM) system Requires diff/merge...
Transcript of Vector Webinar: AUTOSAR Configuration Process - … management (CM) system Requires diff/merge...
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
V2.0 2013-04-18
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.
Slide:
Agenda
> Introduction
AUTOSAR ECU Configuration Description
ECU Configuration Workflow
Multi-User Workflow
Webinar Series
2
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 3
VFB
Virtual Function Bus
SWC1
SWC2 SWC3
Introduction
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
AUTOSAR Method
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 4
Introduction
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 Extract(XML)
AUTOSAR Method
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 5
Introduction
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
RTE Config
OS Config
ECU ConfigurationDescription
Basic SW Module A
Config
AUTOSAR Method
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 6
Introduction
RTE Config
OS Config
ECU ConfigurationDescription
Basic SW Module A
Config
1000s of parameters
Large XML file
Realistic file size
Small ECU: e.g. 10 MB
Large ECU: e.g. 50 MB
AUTOSAR Method
© 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
7
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide:
AUTOSAR ECU Configuration Description
8
What is a parameter?
ParameterDefinition Parameter
Name
Multiplicity (e.g. 0..1, 1..n)
Type (integer, enum, …)
Min/Max values, literals
Description
…
Value of the parameter within the configuration of a concrete ECU
References
Example:
NVM_CRC16
Example:
Name: NvmBlockUsedCrcType
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:
AUTOSAR ECU Configuration Description
9
Containers and Parameters
ParameterDefinition Parameter
References
ContainerDefinition Container
References
ContainerDefinition Container
References
ParameterDefinition Parameter
References
ParameterDefinition Parameter
References
Parameters are hierarchically organized in Containers
A container consists of
Parameters
sub-containers
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:
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
AUTOSAR ECU Configuration Description
10
ApplicationO
S
RTE
IO
Com
ple
x D
rive
rs
SY
S
DIA
G COM
MEM
CA
N LIN
J1939TP
XC
P IPFR
CAL EXT
Microcontroller
MO
ST
NetworkServicesLibrary
xml
Basic SW Module Description (BSWMD)
Basic Software Module Description
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide:
AUTOSAR ECU Configuration Description
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)
11
Key for success: configuration tools
Challenges
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 12
AUTOSAR ECU Configuration Description
Support for integration of MCALs and add-on modules
Migration (platform switch)
Development of tool extensions (Validation rules, configuration GUI, code generators)
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)
© 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
13
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide:
ECU Configuration WorkflowOverview
DBCLDF
Input files provided by OEMContains communicationinformation, neededfor the ECU
.c .hRTE header and code filesSWC header files
Software Component Description files
.xml Embedded Coder
TargetLink
.cdd/.odx
CANdela Diagnostic Data Other AUTOSAR tools
.c .hBSW module configuration header and code files
Fibex
.XML
ECU Extract of System Description provided by OEMContains system information, needed for the ECU
DaVinci Developer
PREEvision
DaVinci Configurator ProConfiguration of RTE + BSW
ECU Extract of System Description
ECU ConfigurationDescription
.xml
.xml
SystemDesc Conversion
Base ECUC Generation
Editing and
Generation
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide:
ECU Configuration WorkflowIntegration of third party BSW (MCALs, Complex Driver)
.c .hRTE header and code filesSWC header files
BSWMD
ExternalCode Generator
.c .hBSW module configuration header and code files
DaVinci Configurator ProConfiguration of RTE + BSW
.hBSW module configuration header and code files
.c .hBSW module configuration header and code files
Code GeneratorPlug-in
GUIPlug-inBSWMD
MICROSARMICROSAR
Third Party
Third Party
.c
Third PartyEparm
BSWMD creation
Generic Configuration Editor
Comfort Editors
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
16
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 17
Multi-User WorkflowGeneral
AUTOSAR ECU
Developer 1
Developer 3
Developer 2
ECU SW Integrator
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 customer’s CM (configuration management) system
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 18
Component responsibles Each component (e.g. SWC, BSW
module or cluster) has one responsible
Only the component responsible is allowed to change the component
Multi-User Workflow
SWC1 SWC2
BSW
RTE
AUTOSAR ECU
OS CAN MEM
ComponentDeveloper 1
ComponentDeveloper 3
ComponentDeveloper 2
ECU SWIntegrator
Several possible ways to organize responsibilities, e.g.
SWC1 SWC2
BSW
RTE
AUTOSAR ECU
OS CAN MEM
FeatureDeveloper 1
FeatureDeveloper 2
ECU SWIntegrator
Feature responsibles Feature developer makes changes
in potentially all SWCs or BSW modules
Overlapping modifications – several users change e.g. same SWC
No strict assignment of user to SWC/BSW-Module
Responsibilities
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 19
Multi-User Workflow
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 configuration management (CM) system
Requires diff/merge
Exclusive editing Only one person allowed to change
an object
Typically realized via check-out control strategy of CM system
Requires sequencing of work packages – difficult to organize!
Avoids merge
Access Strategy
CMv1 v3v2v0
merge
CMv1 v3v2v0
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide:
Multi-User Workflow
Standalone Diff-Tool Compare two ARXML files (any content)
Show differences in native view
DaVinci Tools Generic diff/merge of SWCs and ECUC
Read-only display of objects like SWCs, Port Interfaces, Data Types, modules
Available for all relevant objects, e.g.> SWCs
> Port Interfaces
> Data Types
> Module Configurations
20
Tool Support
Result
BA
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 21
Multi-User Workflow
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
Fine-grained Configuration Management
SWC1.xml
Os.xml
CanIf.xml
CanTp.xml
Rte.xml ...
SWC2.xml
...SWCs(DaVinci DCF Workspace)
BSW Config(Split ECUC Files)
SWC1 SWC2
BSW
RTE
ECU1
OS CAN MEM
r/w
ECU_Comp.xml
r/w
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 22
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 Vectorhttp://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
© 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector.
Slide: 23
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