AUTOSAR Method. Webinar

Transcription

1 AUTOSAR Method Webinar V

2 Agenda >Introduction AUTOSAR Method Exchange Formats Workflows OEM-TIER1 Workflows TIER1 Webinar Series Slide: 2

3 Introduction Current Workflow (non-autosar) Network communication of the vehicle is specified The ECU is configured based on the DBC, FIBEX, LDF file. ECU1 ECU2 ECU Applications Basic Software (BSW) DBC, FIBEX, LDF Slide: 3

4 Introduction New Terms in AUTOSAR What do they mean? System Description Virtual Function Bus ECU Configuration System Template AUTOSAR XML Basic Software Software Component Slide: 4

5 Agenda Introduction > AUTOSAR Method Exchange Formats Workflows OEM-TIER1 Workflows TIER1 Webinar Series Slide: 5

6 AUTOSAR Method Complete SW functionality of the vehicle is defined as a system of SWCs... SWC1 Virtual Function Bus VFB SWC2 SWC3..and distributed to ECUs ECU1 ECU2 SWC1 SWC3 SWC2 Software Component Description* System Description* An extract is created for each ECU... The ECU is configured based on the ECU Extract. ECU1 SWC1 SWC2 SWC1 SWC2 Basic Software (BSW) RTE Extract of System Description* ECU Configuration Description (ECUC)* * Slide: 6

7 AUTOSAR Method Example: Components view for interior lighting control Right Door Door Contact Left Door Switch Dimmer Light Slide: 7

8 AUTOSAR Method Example: Communication Software Components Switch Left Door Right Door Door Contact Dimmer Light Virtual Function Bus Ports Connector Slide: 8

9 AUTOSAR Method Example: Distribution of components Roof ECU Front ECU Switch Dimmer Light Door Contact Left Door Right Door RTE RTE Basic SW Basic SW Controller Controller Bus Slide: 9

10 Agenda Introduction AUTOSAR Method > Exchange Formats Workflows OEM-TIER1 Workflows TIER1 Webinar Series Slide: 10

11 Exchange Formats Templates and Description Files Templates Descriptions SW Component Template SW Component Description ECU Resource Template ECU Resource Description System Template System Description Standardized set of design artifacts Associated XML Schema Defined by Concrete specification based on the Template Represented as XML file Defined by the OEM or TIER1 Slide: 11

12 Exchange Formats Software Component Description The AUTOSAR Software Component Description contains the following information SWC SW 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. Slide: 12

13 Exchange Formats ECU Resource Description The AUTOSAR ECU Resource Description contains the following information ECU ECU 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. Slide: 13

14 Exchange Formats System Constraint Description The AUTOSAR System Constraint Description contains the following information: System 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. Slide: 14

15 Exchange Formats System Description Decisions - mapping of ports to communication signals - mapping of SWCs to ECUs SW- Component Description ECU 1 Extract System- Constraint Description AUTOSAR System Configuration Editor System Description AUTOSAR System Description Extractor ECU 2 Extract ECU Resource Description (HW only) iterative process ECU n Extract 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: 15

16 Agenda Introduction AUTOSAR Method Exchange Formats > Workflows OEM-TIER1 Workflows TIER1 Webinar Series Slide: 16

17 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 (SYSD) ECU-specific extract ECU Configuration (ECUC) Note: OEM and TIER1 may also be organizational units within one company ( System Responsible vs. ECU responsible ) Slide: 17

18 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

19 Workflows OEM-TIER1 ECU-specific extract of system design AUTOSAR 3 ECU1 ECU Composition Comp2 SWC2 Service SWC1 Comp1 SWC3 SWC4 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 AUTOSAR 4 System Extract (SYSEX) ECU Composition OEM SWCs (subset of SYSD) Atomic SWCs Compositions Typ. no service SWCs Communication Data Mapping 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 ECU1 ECU Composition Comp1 SWC3 Flattening ECU1 ECU Composition SWC2 SWC4 xm l Service SWC1 SWC3 SWC4 Slide: 19 xml

20 Workflows OEM-TIER1 Content of ECU-Extract provided by OEM - Examples Example 1: Network-oriented approach Example 2: Functional system design approach Example 3: Functional system design approach with OEM SWCs Service Components Service Mapping Atomics Service Components Service Mapping Atomics Service Components Service Mapping 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

21 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

22 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 xml ECU-specific extract DaVinci Developer DaVinci Configurator Pro Slide: 22

23 Agenda Introduction AUTOSAR Method Exchange Formats Workflows OEM-TIER1 > Workflows TIER1 Webinar Series Slide: 23

24 Workflows TIER1 ECU Configuration List of implementations of SW Components ECU Configuration Description (XML) RTE Config AUTOSAR RTE Configurator ECU Extract (XML) Base ECU Configuration Generator OS Config Configurator for OS, COM, etc. Configurator for other Basic SW Basic SW Module A Config MCAL Configurator Slide: 24

25 Workflows TIER1 Component development process Generate Component API Component API (*.h) Implement Component Component Implementation (*.c) SW Component Description (XML) Perform Unit Test Create Test Cases Component Test Cases Slide: 25

26 Workflows TIER1 Executable ECU ECU Configuration Description RTE Config OS Config AUTOSAR RTE Generator Generator for OS, COM,... Library *.obj Software components *.c RTE.c OS.c Software Components AUTOSAR RTE OS Other Basic SW Generator *.c other Basic Software Basic SW Module A Config MCAL Generator MCAL.c MCAL Slide: 26

27 Workflows TIER1 Tool Support Slide:

28 Webinar Series The webinar series about AUTOSAR ( ECU development with AUTOSAR - An introduction for AUTOSAR beginners Introduction to the AUTOSAR Method for ECU development AUTOSAR Configuration Process - How to handle 1000s of parameters Reliable Testing of AUTOSAR ECUs MICROSAR Safe: AUTOSAR basic software for safety-relevant ECUs (ISO 26262) 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 Registration to the upcoming Webinars and the list of recorded Webinars: The overview of Vector s training services: Slide: 28

29 Thank you for your attention. For detailed information about Vector and our products please have a look at: Author: Vector Informatik GmbH Ingersheimer Str Stuttgart Slide: 29