autosar methodology @bmw. bmw pia client fscsm auth bmw omc cbs bmw stm bmw wur swt bmw rmh pndm pns...

16
AUTOSAR METHODOLOGY @BMW. Bernd Jäger, 28th September 2016 9th AUTOSAR Open Conference, Gothenburg

Upload: truongtruc

Post on 20-Jun-2018

789 views

Category:

Documents


31 download

TRANSCRIPT

Page 1: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR METHODOLOGY @BMW.

Bernd Jäger, 28th September 20169th AUTOSAR Open Conference, Gothenburg

Page 2: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

2

3

4

5

1

7

6

AUTOSAR Methodology at BMW Page 2

OVERVIEW.

AUTOSAR Versions and Roadmap

Configuration Process until Generation 2015

Vision Generation 2021 and Current Status Generation 2018

Tool Architecture

Tool Development

ECU Configuration Flow

AUTOSAR Tool Requirements for the Future

Page 3: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

BAC4 Rel. 3Generation 2021

In use until ~ 2035

AUTOSAR Methodology at BMW Page 3

PLATFORM SOFTWARE ROADMAP GENERATIONS 2008 UNTIL 2021. VERSION OVERVIEW.

SC6 Generation 2008

In use until ~ 2022

BAC2/3Generation 2011

BAC4 Rel. 1Generation 2015

BAC4 Rel. 2Generation 2018

In use until ~ 2025

In use until ~ 2029

In use until ~ 2032

7er

X5

MCV

One platform SW architecture for all electronic control units.

Adaptive AUTOSAR 1.0Delivery as example

AUTOSAR 2.1/3.0

AUTOSAR 1.0/2.0

AUTOSAR 4.0

AUTOSAR 4.2+

Delivery as series production code

AUTOSAR 4.2

Introduction ofAIDA-Symphony

Page 4: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 4

AIDA SYMPHONY ROADMAP.ECU CONFIGURATION PROCESS GENERATION 2015.

Current Status:− Different Tools generate AUTOSAR configuration files.− The ECU Integrator has to merge and

add missing parameters.

Experiences− 3-8 Weeks per export needed, until mapping

correct and tested (empirical determined).− Risk of remaining consistency errors high− Late changes in on board network are not

feasible due to manual D2SMapping− Diagnostic Configuration errors found

2 weeks after first integration

Generation 2015

Zedis

CAFEditor

DiagnosticConfigurator

AUTOSAR System toolconfigurator, generator

Xyz.arxmlSystem Template

Dem.arxmlDcm.arxml

Coding.arxml

ECU.arxml

Odx

Artext, AUTOSAR BuilderXyz.arxml

SWCD

3-8 weeks needed

Iteration cycles by supplier

BNE

ECU IntegratorBMW

Page 5: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 5

AIDA SYMPHONY ROADMAP.EXAMPLE SYSTEM FUNCTION PARAMETERS.

32 system function components with 1200 parameters can lead up to 30000 configurations per ECU.

Example DSC: 320 Parameter (static configuration) can lead to approx. 400 different configurations.480 Parameter (dynamic configuration) can lead to approx. 29.400 different configurations.

Manual work at supplier site led to a lot of different errors.

Sys. Function Components with the number of configuration parameters:

Diagnose Programmierung Automotive Security

Sonstige

DCM 297 Blu 36 Auth 36 Dlog 102

DEM 174 Bm 11 Swt 47 EthDiagMM 45

ObdM 32 Cpl 107 StbMB 12 Fnm 11

Edch 28 Fscsm 45 StbP 16 PiaClient 20

Darh 12 Nrv 6 Coding 32

StdDiag 12 Prog 28 PnDm 34

PnS 16

PnDm 34

Additional 70

PduR

Xxx Interface

NvM

TCP/IP

Dcm

I/O Signal Interface

StbM

SoAd

Trcv. Ext.Drv

MemIfWdgIf

Ea Fee

BMWEthDiagMM

IPduM

BMW BUtil

BMW Cpl

Cal

E2E-Lib

Crc-Lib

AUTOSAR Runtime Environment (RTE)

Microcontroller

BMW System Function Software-Components (SW-C) Sample Application SW-Cs (optional)

BMW StdDiag

BMW Coding

BMW Pia Client

BMW Fscsm

BMW Auth

BMW Omc

BMW Cbs

BMW Stm

BMW Wur

BMW Swt

BMW Rmh

BMW PnDm

BMW PnS

BMW Pia ClientSample

BMW CodingSample

BMW WurSample

BMW SysTime

BMW Dlog

BMW Darh

BMW ObdM

BMW Edch

BMW Vin

Onboard DeviceAbstraction

EcuM

Dem FiM

Dlt

Com

M

Wdg

M

Bsw

M

AU

TOS

AR

OS

Gpt

Wdg

MC

U

Cor

eTst

MCU Drivers

Memory HW Abstraction Communication HW Abstraction

FlsT

st

Ram

Tst

Fls

Eep

Lin

Can Fr Eth

Spi

Memory Drivers Communication Drivers

Driver for ext. ADC ASIC

Driver for ext. I/O ASIC

BMW PnS

I/O Hardware Abstraction Complex Drivers

BMW Srv

Pw

m

Adc Dio

Por

t

Icu

I/O Drivers

XCP

SD

Nm

Xxx

Tp

XxxS

M

BM

W C

anTS

ynB

BM

W F

rTS

ynB

EthT

Syn

Memory ServicesSystem Services Communication Services

Libraries

LD/Com

SomeIpXf

Nm

lf

Debug

Page 6: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 6

AIDA SYMPHONY ROADMAP.VISION 2021.

Vision for 2021BMW provides the BMW System Software (BMW specific parts of the BAC architecture) and for integration ECUs domain specific customer function Software Components. In addition BMW delivers an ECU-specific configuration, which is based on all information BMW knows, and will partially fill the final configuration of the ECU. The partial configuration will be verified , continuously exported and support best the continuous integration approach.

Goal 2015 for Symphony in Generation 2018BMW provides for diagnostic at least 60% of the configuration parameters and for the remaining system functions 20% in an AUTOSAR tool readable xml file. The communication stack will be configured up to 70%. Integration ECUs will get the Software Component Descriptions for the application components delivered by BMW and partly the configuration of the RTE.

Page 7: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 7

AIDA SYMPHONY ROADMAP. WHICH FILE CONFIGURES WHICH MODULE IN AUTOSAR 4.2.2

AUTOSAR Standard BMW Specific

PduR

Xxx Interface

NvM

TCP/IP

SD

Dcm

I/O Signal Interface

StbM

SoAd

Trcv. Ext.Drv

MemIfWdgIf

Ea Fee

BMWEthDiagMM

Debug

BMW BUtil

BMW Cpl

Cal

E2E-Lib

Crc-Lib

AUTOSAR Runtime Environment (RTE)

Microcontroller

BMW System Function Software-Components (SW-C) Sample Application SW-Cs (optional)

BMW StdDiag

BMW Coding

BMW Pia Client

BMW Fscsm

BMW Auth

BMW Omc

BMW Cbs

BMW Stm

BMW Wur

BMW Swt

BMW Rmh

BMW PnDm

BMW PnS

BMW Pia ClientSample

BMW CodingSample

BMW WurSample

BMW SysTime

BMW Dlog

BMW Darh

BMW ObdM

BMW Edch

BMW Vin

Onboard Device Abstraction

EcuM

Dem FiM Dlt

Com

M

Wdg

M

Bsw

M

AU

TOS

AR

OS

Gpt

Wdg

MC

U

Cor

eTst

MCU Drivers

Som

eIpX

f

Memory HW Abstraction Communication HW Abstraction

FlsT

st

Ram

Tst

Fls

Eep

Lin

Can Fr Eth

Spi

Memory Drivers Communication Drivers

Driver for ext. ADC ASIC

Driver for ext. I/O ASIC

BMW PnS

I/O Hardware Abstraction Complex Drivers

BMW Srv

Pw

m

Adc Dio

Por

t

Icu

I/O Drivers

XCP

Ipdu

M

Nm

fN

m

Xxx

Tp

XxxS

M

BM

W C

anTS

yn

BM

W F

rTS

yn

EthT

Syn

Memory ServicesSystem Services Communication Services

Configured in SP2018

Libraries

Com

Configured by ECU System Description

Configured with Service Needs

Configured by ECU Configuration (ECUC)

Page 8: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 8

AIDA SYMPHONY ROADMAP.ECU CONFIGURATION PROCESS FOR GENERATION 2018

Target generation 2018 for newly developed ECUsThe ECU Integrator receives two ECU specific configuration files from BMW.

Goal with AIDA Symphony− Daily export with consistency checked possible.− Risk of remaining consistency errors low− Late changes in on-board network are possible− Diagnostic configuration 1st time right

Zedis

System functionrequirements ECU

Configuration

fibex

ECU System

Descriptionarxml

Prima

Permanent enhancement of consistency checks

ContinuousVerification

BNE

CAFEditor ECUC.arxml

Delivery of verified and consistent configurations

Generation 2018

PduR

Xxx Interface

NvM

TCP/IP

Dcm

I/O Signal Interface

StbM

SoAd

Trcv. Ext.Drv

MemIfWdgIf

Ea Fee

BMWEthDiagMM

IPduM

BMW BUtil

BMW Cpl

Cal

E2E-Lib

Crc-Lib

AUTOSAR Runtime Environment (RTE)

Microcontroller

BMW System Function Software-Components (SW-C) Sample Application SW-Cs (optional)

BMW StdDiag

BMW Coding

BMW Pia Client

BMW Fscsm

BMW Auth

BMW Omc

BMW Cbs

BMW Stm

BMW Wur

BMW Swt

BMW Rmh

BMW PnDm

BMW PnS

BMW Pia ClientSample

BMW CodingSample

BMW WurSample

BMW SysTime

BMW Dlog

BMW Darh

BMW ObdM

BMW Edch

BMW Vin

Onboard DeviceAbstraction

EcuM

Dem FiM Dlt

Com

M

Wdg

M

Bsw

M

AU

TOS

AR

OS

Gpt

Wdg

MC

U

Cor

eTst

MCU Drivers

Memory HW Abstraction Communication HW Abstraction

FlsT

st

Ram

Tst

Fls

Eep

Lin

Can Fr Eth

Spi

Memory Drivers Communication Drivers

Driver for ext. ADC ASIC

Driver for ext. I/O ASIC

BMW PnS

I/O Hardware Abstraction Complex Drivers

BMW Srv

Pw

m

Adc Dio

Por

t

Icu

I/O Drivers

XCP

SD

Nm

Xxx

Tp

XxxS

M

BM

W C

anTS

ynB

BM

W F

rTS

ynB

EthT

Syn

Memory ServicesSystem Services Communication Services

Libraries

LD/Com

SomeIpXf

Nm

lf

Debug

ECU Integrator(Supplier)BMW

Page 9: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 9

AIDA SYMPHONY ROADMAP.TOOL ARCHITECTURE. Plugin

integrated in Symphony Product

Project specific Pluginwritten by Project

ASCENT

Import

User Interface

Autosar Export

Platform

Core System

Validate

In-Place Enrichments

Symphony ASCENT Repository

PRIMA Connector

PRIMA Trafo

nuDIB Integration

nuDIBTrafo

EMF ARTOP 4.5 Workflows IncQuerySphinx Git SVNMylyn

FileConnector

FIBEXTrafo

ZEDISConnector

ZEDISTrafo

XtextEclipse Team

PRIMAImport-WF

ADDImport-WF

BNEImport-WF

ZEDISImport-WF

Validation UI

Bundle UI

Workflow UI

WikiManual

Server + ClientProduct

SysParam UI

Logging

Symphony Build Server

Validation Core Validation Util KOM Validation Basic Validations Extended Validations

Import Common

Model Access

Sym1.x Core

Model Conversion

SymFibex Core

Bundle2.x Core Fibex 4.1.1 Core

Workspace Core

AR Integration

AR 4.2.x CoreWorkflow Core

Processing Model

Sym Core Conversion

DEMPorts

DCMPorts

ParamCoding

EthernetServices

DummySignals

VariantResolution

ECUExtractor

ECUCompos.

MDEPlugins

CAFEConnector

CAFETrafo

CAFEImport-WF

ASCENTConnector

ExtractPackager

Extract Doc

Sys Desc Gen ECU-C Gen

FP COD

DEM DCM

PIA PWF

DType CAN/FR

SWC IF

Eth SwBnMp

Comp FlatMp

IB

ARXMLSplitter

ARXMLExtractor

Ecu PL Sys Func Owner SymAdm

CAFEBNEADDPRIMA ZEDIS

Page 10: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 10

AIDA SYMPHONY WORKFLOW.ECLIPSE DEVELOPMENT ENVIRONMENT AND TOOLS.

FibexImport

Magic Draw

FibexModel

Ecore-Model

Development Enviroment

Xtext

Eclipse Project

AUTOSARExport

Internal data model

Ecore-Model

ArtopEcore-Model

AR Model

xml

export MWE 2

generatejava classes

EclipseEnterprise Arch.

xml

Symphony Eclipse Development

Sphinx

Mylyn Junit

EMF + Sphinx

InternalModel

Coding is similar to fibex import.

IncQuery Log4J

Artop Xtend

Mylyn: Eclipse Feature to interconnect to tickets systems like JIRA.

Junit: Test Framework for Java Units.

IncQuery: Framework to decscribe complex queries to EMF models.

Log4J: Standard Logging Framework in Java Environment.

ARTOP: Sphinx based framework to use AUTOSAR models.

Xtend: Extension of JAVA programming language especially to develop model transformations.

Xtext: Framework to develop applications based on own text based languages.

Sphinx: Extension of EMF (Eclipse Modeling Framework) to use models in own applications.

MWE2: Framework to program Workflows.

Jira

Git Gerrit

Jenkins

Page 11: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 11

AIDA SYMPHONY WORKFLOW.TOOL DEVELOPMENT WORKFLOW.

Jenkins

developer

fetch

developer partial unit tests

Gerrit(master)

Gerrit(master)

Automatic Test Execution

Master DevelopmentTrunk

Slave DevelopmentTrunk

Gerrit(master)

Gerrit(Commit branch)

Production

Code change

Tests passed

commit Check out

Unit Testscomplete

Integration tests(Golden Reference)

Testspassed

Testspassed

Code reviewspassed

Status o.k.Code

reviews

MergeFinal Testing

passedTests

Development

Code Checkins from otherdevelopers

Page 12: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Methodology at BMW Seite 12

AIDA SYMPHONY WORKFLOW.EXAMPLE ECU CONFIGURATION WORKFLOW.

1. Fill Input data bases 2. Choose corresponding input versions of Input data bases

3. Generate export4. Check warnings or errors and change

input database until valid export possible

5. Import artefacts with your AUTOSAR Tooling

6. Complete configuration

7. Start AUTOSAR and BMW generators

Tooling from BMW

Tooling of supplier

CAFE

BACARXMLADD

ZEDIS

Central Dept.

SymphonySF-UI

AUTOSARgenerator

Arttgenerator

Manual Configuration

(GUI)

BoleroEvalboardMAKE

ECU PL

Module parameterDescription files

ECU PL

Supplier

PRIMA

SupplierBMW

*.c*.hASCENTSymphony

Gerrit(master)

Database ofAUTOSAR

Tooling

Gerrit(master)

PartialApplication

SWCDs

BNE AUTOSAR Tooling

SupplierLibrary

BMW Library

AUTOSARRTE

Generator

RTE *.h

ECU System Description.arxmlECU C.arxml

ECU System Description.arxmlECU C.arxml

BAC

Ref.

Page 13: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Tooling

AIDA Symphony delivers ECU System Description and ECUCs for an ECU Project

The integrator imports the partially filled ECUCs provided by AIDA Symphony to the AUTOSAR Tool

Integrator completes the ECUC configuration

Integrator generates the BSW and BMW System Function modules (BAC4).

ECU System Description Files are imported to the RTE Generator

RTE is generated

Software is compiled and linked

AIDA SYMPHONY WORKFLOW.HOW IS THE ECU CONFIGURATION AND SW BUILT MANAGED IN THE PROJECT?

3

RTE

4

5

2

67

x Description on next page.

Sym

phon

y

AUTOSAR ECUC Editor

SupplierSWCD

ECU SystemDescription

ECUCs

BMW SWCD and BSWMD

1AUTOSAR

Workspace

a

ECU Software

b

RTE + Project Source Files

ECU Software

1

2

3

4

5

6

7

Page 14: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

AUTOSAR Tooling related issues:

1. Removed ECUC values may not be removed in the AUTOSAR Tooling.

2. Changed ECUC values may not be correctly updated in AUTOSAR Tooling.

3. Some parameters are reset to default when the ECU System Description is imported.

4. Top-level shall be processed correctly (SystemTemplate Chapter 10, the standard approach)

Integrator related task (Can not be automated except by specific project rule sets):

1. BMW provides a partially filled ECU configuration

Sometimes the integrator has to extend the provided configuration with the project/ HW specific content.

Examples are: Runnable to OS Task mapping, diagnostic debouncing information, BSW main cycle times, etc.

AIDA SYMPHONY WORKFLOW.CHALLENGES FOR PROJECTS TO AUTOMATE WORKFLOW

a

b

Page 15: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

Page 15

AIDA SYMPHONY ROADMAP.FUTURE REQUIREMENTS ON AUTOSAR TOOLING AND SPECIFICATION.

AUTOSAR Tooling

AUTOSAR Tool Chain shall be run-able on Linux.

Full tool functionality shall be controllable by command line.

1st and 2nd Tier Suppliers to support completely integrated tool flow to enable real continuous integration.

AUTOSAR Specification

Usage of Diagnostic Extract Template, released in AUTOSAR 4.2.2 would reduce the pre-configuration of diagnostic modules by 40% compared to today’s approach of BMW

Upstream Mapping rules between the BSW Parameters and the M2 Parameters need to be completed in the next Release of the AUTOSAR Standard.

AUTOSAR Methodology at BMW

Page 16: AUTOSAR METHODOLOGY @BMW. BMW Pia Client Fscsm Auth BMW Omc Cbs BMW Stm BMW Wur Swt BMW Rmh PnDm PnS BMW Pia Client Sample BMW Coding Sample BMW Wur Sample BMW SysTime Dlog BMW Darh

BACKUP.

Seite 16