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 defined as a system of SWCs... ..and distributed to ECUs ECU1 SWC1 ECU2 SWC1 SWC3 Virtual Function Bus SWC2 VFB SWC2 SWC3 Software Component Description* An extract is created for each ECU... ECU1 System Description* The ECU is configured based on the ECU Extract. SWC1 SWC2 SWC1 RTE SWC2 Extract of System Description* Basic Software (BSW) ECU Configuration 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 ECU Extract (XML) Base ECU Configuration Generator Configurator for OS, COM, etc. OS Config Configurator for other Basic SW 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: 4 MCAL Configurator Introduction AUTOSAR Method Library *.obj Software components *.c ECU Configuration Description RTE Config AUTOSAR RTE Generator Software Components RTE.c AUTOSAR RTE Generator for OS, COM, ... OS.c OS OS Config Basic SW Module A Config Other Basic SW Generator *.c MCAL Generator MCAL.c © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 5 other Basic Software MCAL Introduction AUTOSAR Method ECU Configuration Description RTE Config  1000s of parameters  Large XML file  Realistic file size  Small ECU: e.g. 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 Definition References  Name  Multiplicity (e.g. 0..1, 1..n)  Type (integer, enum, …)  Min/Max values, literals  Description  … Parameter  Value of the parameter within the configuration of a concrete ECU 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 References Container Definition Parameter Definition Parameter Definition Container Definition Parameter Definition Container References Parameter References References References 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 Parameter Container Parameter 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 CAL Microcontroller © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 10 EXT Complex Drivers Network Services Library IO MOST IP FR LIN J1939TP CAN MEM DIAG XCP OS SYS xml Basic SW Module Description (BSWMD) COM 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 .XML DBC LDF ECU Extract of System Description provided by OEM Contains system information, needed for the ECU .cdd/ .odx CANdela Diagnostic Data Input files provided by OEM Fibex Contains communication information, needed for the ECU .xml Software Component Description files TargetLink DaVinci Configurator Pro Configuration of RTE + BSW SystemDesc Conversion .xml Editing and ECU Extract of System Description Generation .c .h RTE header and code files SWC header files .c .h BSW module configuration header and code files Base ECUC Generation .xml ECU Configuration Description © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: Embedded Coder Other AUTOSAR tools ECU Configuration Workflow Integration of third party BSW (MCALs, Complex Driver) DaVinci Configurator Pro MICROSAR Configuration of RTE + BSW MICROSAR Comfort Editors BSWMD Generic Configuration Editor Third Party Eparm BSWMD creation BSWMD GUI Plug-in Code Generator Plug-in .c .h RTE header and code files SWC header files .c .h BSW module configuration header and code files Third Party .c .h BSW module configuration header and code files Third Party External Code Generator  .h BSW module configuration header 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: .c 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 customer’s CM (configuration management) system Developer 2 Developer 1 AUTOSAR ECU Developer 3 © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 17 ECU SW Integrator Multi-User Workflow Responsibilities Several possible ways to organize responsibilities, e.g. Component responsibles   Each component (e.g. SWC, BSW module or cluster) has one responsible Only the component responsible is allowed to change the component Component Developer 1 SWC1 SWC2 Component Developer 2 RTE Component Developer 3 OS MEM CAN BSW ECU SW Integrator AUTOSAR ECU Feature responsibles    Feature developer makes changes in potentially all SWCs or BSW modules Feature Developer 1 SWC1 SWC2 RTE Overlapping modifications – several users change e.g. same SWC OS No strict assignment of user to SWC/BSW-Module AUTOSAR ECU © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 18 Feature Developer 2 CAN MEM BSW ECU SW Integrator 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 configuration management (CM) system  Requires diff/merge merge CM v0 v1 v2 v3 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 CM v0 © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 19 v1 v2 v3 Multi-User Workflow Tool Support   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 © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 20 A  B  Result 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 SWCs (DaVinci DCF Workspace) SWC1 .xml SWC2 .xml r/w ... SWC1 ECU_ Comp .xml RTE OS BSW Config (Split ECUC Files) Os. xml CanIf. xml CanTp. xml Rte. xml ... © 2013. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. Slide: 21 SWC2 CAN BSW ECU1 MEM 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 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: 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
© Copyright 2024 Paperzz
