AUTOSAR E/E Design Flow Solution. - Optimizing Functional / Logical Architecture Design with EAST-ADL and AUTOSAR

Transcription

1 AUTOSAR E/E Design Flow Solution - Optimizing Functional / Logical Architecture Design with EAST-ADL and AUTOSAR GM Soh Sr. Application Engineer

2 Trend E/E architecture trends Description Objective Standardization Integrate architecture design and implementation AUTOSAR EAST ADL Bi-directional flow of information Improve productivity Improve flexibility Enable professional tooling Use feedback from implementation projects during architecture design Attention to Timing requirements Integrated development with an engineering data back-bone Standardized timing models All development organization working towards same model in one tool Reduce number of timing problems Improve network design Improved availability of design data Improved re-use of design components Support methodology and workflow 2

3 Trend : Standardization AUTOSAR the biggest standardization effort in Automotive E/E Becoming adopted in Europe now Still early stages but direction is clear A factor in all new development flows EAST-ADL complementing AUTOSAR with higher level definitions such as features, requirements etc Benefits A common language for OEMs, Tier 1s and tool vendors to communicate design information Enables professional tools Standard concepts improves productivity 3

4 - supports architecture design Provides definition for SW components and allocation to ECUs Mechanism to define logical functionality and report resource usage Provides definition for ECUs and their resources Simplify relocation of functionality Key importance for architecture optimization Improves reuse of SW components and ECUs Key importance for architecture optimization Enable early virtual validation Find errors early and shorten total development time Enable early metrics generation Provides defintions and format for interchange of information with other development activites 4

5 Size of Project Signature 150 Companies Total 5 Almost Every OEM worldwide Every T1 Supplier Every T2 Supplier

6 AUTOSAR Timeline 6

7 Trend : Integrate architecture design with implementation Logical Architecture design SWC description [SWC Template] SWC description [SWC Template] Port description Port description Interface description Interface description Runnable description Memory usage WCET/CPU usage Model Based Development Software Development Function design Virtual Testing SYS description [SYS Template] SWC description [SWC Template] Communication Mappings Port description Interface description ECU resource description Runnable description [ECU Template] Sensors/actuators Pins Memory resources CPU resources ECU SW Design and configuration Logical Topology EDS Design Network Design 7

8 Trend : Attention to Timing Requirements Great progress have been made with respect to timing in both AUTOSAR and EAST ADL last years OEMs now try to capture timing requirements at the functional level Stimulus Delay Constraint D Response Brake Pedal Position Monitor Brake Controller Brake Force Actuation Stimulus Response Stimulus Response Stimulus Response Delay Constraint A Delay Constraint C Delay Constraint B 8

9 Trend : Attention to timing requirements Specified at function level Max:50ms Analyzed for example in network design 9

10 Trend : Engineering data backbone supports architecture design Tool that is used by almost all E/E Developers Design Data Storage Multi-user Access Configuration Management Change Control Option and Variant Management Report Generation Makes information available at the right time and format Supports development methodology Promotes reuse of design components 10

11 Engineering data-backbone with VSA Design data in one central place Everyone has access to latest design data they need Rights and roles controls access Multiple views of the system model Requirements management Change management Status management Function Engineer ECU Engineer Test Engineer Network Designer Systems Architect Project Manager Project Manager Controlled Access Supplier 11

12 Engineering Data Backbone One model multiple views Project management Requirement Function Design Use Case 12 Change management

13 Problem with information getting outdated Traditional situation with document based development : Relative Quality Requirements / Specification Design / Architecture Implementation / source code Manufacturing data time 13

14 Keep information updated Desired communicating processes situation supported by engineering data backbone: Relative Quality Requirements / Specification Design / Architecture Implementation / source code Manufacturing data time 14

15 Requirements EE Architecture Design EE Design Process Network Software Electrical Hardware PCB / IC MCAD Enterprise Eco-system (PDM / PLM, EPR / MRP, Suppliers..) Many disciplines acting within the context of a broad eco-system often beyond it s control Each element operates with a localized view of a V-Diagram Each element is (usually) poorly integrated, presenting major challenges for design oversight and IT support levels 15

16 Responsibilities - split between OEM & Suppliers Requirements EE Architecture Design OEMS Network Software Electrical Hardware PCB / IC MCAD Suppliers Enterprise Eco-system (PDM / PLM, EPR / MRP, Suppliers..) Split differs by OEM but the principle is consistent This presentation drops Hardware Design as a topic as it is largely handled by suppliers We will also refer to Enterprise Systems only within the context of the remaining sections 16

17 The Problem of Optimizing Vehicle Architectures No. of No. of Connectors Connectors Pos. of Slots Pos. of Slots No. of Slots No. of Slots Resource Resource Usage Usage Variants Variants Options Options Hardwired Hardwired vs. vs. multiplexed multiplexed Topology Topology High-power/ High-power power/ Low-power Low-power switches switches No. of ECUs No. of ECUs Latencies Latencies CO2 CO2 Performance Scalability Reliability Comfort Comfort Cost Weight Packaging Power Power consumption consumption Carry-over Carry-over components components Functionality Functionality Smart Smart Sensors/actuators Sensors/actuators HW/SW HW/SW Partitioning Partitioning Distribution Distribution of of Functions Functions Communication Communication scheme scheme 17

18 Cost scalability - Theoretical objectives cost Typically non-desired relation -Too high cost for low feature cars means bad margin Typically desired relation -Low feature car has low cost -High feature content has higher cost Low High Feature content of car (based on selected variants and options) 18

19 Practical objectives Cost Expected sales volume (%) Most important to optimize cost for this segement 40% Low 10% 20% 20% 10% Feature content of car (based on selected variants and High options) 19

20 EE Design without hardware & the eco-system shown Requirements EE Architecture Design VSA COM Capital Logic VSB Network BSW VST Stack UML Software Bridgepoint Capital Capital Electrical Integrator Harness VSI Capital Enterprise Seamless design flow from requirements to: EE Architecture exploration/design Network Design System integration & physical implementation Harness Engineering CHS Architect Harness Dressing Electrical Vehicle MCAD Topology Topology CATIA NX Pro/E PDM 20

21 Products and Technologies VSA (Vehicle Systems Architect) EE Architecture- Design & Network-Design (LIN, CAN, FlexRay) VSA Interaction Layer VSB BSW VST VSI VSI (Vehicle Systems Integrator) Virtual Functional Bus Simulato VST (Vehicle Systems Test) TTCN3 based testing of SWC and BSW VSB (Vehicle Systems Builder) AR BSW Configuration & Build BSW AR Basic Software Mentor 21 Graphics Confidential

22 AUTOSAR SW development tools SW architecture definition HW architecture definition Volcano VST ECU/BSW validation Volcano VSA BridgePoint Model driven design SW to HW arch. mapping Volcano VSA Com Designer Network design Volcano VSB ECU design VSI VSI VSI SW architecture System level Full virtual validation validation validation 22 Mentor VSx Overview Company AL VSx Design Confidential Flow November 2009

23 VSx Platform VSA COM Designer VSB ECU Configuration and Builder VST TTCN3 Based SWC and BSW testing and conformance testing VSI Softwareund AUTOSARverificationsund simulation API Customer Plugin VSA AUTOSAR Metamodel Handling Eclipse 23

24 VSA Vehicle Systems Architect VSA VSB BSW 24 Initials, AL VSx Presentation Design Flow Subject, November Month

25 VSA - Vehicle Systems Architect VSA manages mainly logical architecture aspects SWC definition, composition and mapping Topology design ECU internal aspects (CPU load, memory) Network design (LIN, CAN, FlexRay, Ethernet) VSA is Mentor Graphics product for E/E architecture design Bridge the gap between logical function design and implementation in an electrical architecture Bridge the gap between the logical and electrical architecture aspects 25

26 VSA Architecture POINT TOOLS Vehicle Function Description Editor ECU Resource Editor Topology Editor Signal/ Group Editor Vehicle System Editor / Function Mapper Cluster Builders CAN FR LIN Metrics Generator GUI Layer Functional Layer Eclipse Framework Basic infrastructure Backplane File Imp/Exp Interface Version Control Interface SQL Database Interface Customer Specific Interface ECU Extractor File Merger Tool AUTOSAR VTP (fix,net) LDF, NCF Fibex DBC Version Control System e.g. SVN SQL DB Customer Specific Files/DB OPTIONAL 26

27 VSA tool flow Network Design Function Design SWC Design VSA Metrics Function Design SW Composition Design Function Allocation SWC ECU Allocation ECU Design ECU resource Memory usage ECU Cost ECU Topology Topology Design Network metrics 27

28 ECU SW design and configuration - VSB VSA VSI VST VSB BSW 28 Initials, AL VSx Presentation Design Flow Subject, November Month

29 Vehicle Systems Builder The Vehicle Systems Builder (VSB) is Mentors tool for ECU SW developers/integrators that need to integrate and configure AUTOSAR BSW modules based on system description Setup ECU internal configurations such as NVRAM Map runables to tasks Schedule tasks 29

30 VSB Activities VSB External tool ECU Scheduling WCET Analysis AR System Description ECU extract (Other legacy files) Configuration editor Postbuild Locator COM Configuration MEM Configuration Import/Export Merger ECU Builder Compiler/Linker, RTE & Config generators DIAG Configuration I/O Configuration Binary image 30 Constraints and consistency

31 Embedded Software or Basic Software - BSW VSA VSI VST VSB BSW 31 Initials, AL VSx Presentation Design Flow Subject, November Month

32 Mentor AUTOSAR BSW AUTOSAR Runtime Environment (RTE) System Services Onboard Device Abstraction Memory Services Memory HW Abstraction Comm Services Comm HW Abstraction I/O HW Abstrac -tion Microcontroller Drivers Memory Drivers Comm Drivers I/O Drivers ECU HW 32 Complex Drivers Autosar OS BSW scheduler ECU state M COM Mgr GTP Driver Int WDG Driver MCU Driver MCU core test Ext E2PRM Driver Int E2PRM Driver Ext Flash Driver Int Flash Driver I2C Driver SPI Driver CAN Driver LIN Driver FRy Driver ICU Driver PWM Driver ADC Driver DIO Driver Port Driver System Chip Driver Ext WDG Driver E2PRM Ifc Flash Ifc Mem Ifc CAN Interf LIN Interf FRy Interf CAN Trv Drv LIN Trv Drv FRy Trv Drv CAN NM Drv LIN NM Drv Fry NM Drv I/O signal based Interface FIM DEM WDG Mgr DET Ext Time S Oder func NVRAM Mgr NVRAM Test RAM Test Autosr COM PDU Router PDU Mux CAN TPL FRy TPL Gen NM DCM CAN XCP FRy XCP MENTOR MCAL or integration from IC Vendor

33 VST Vehicle System Test VSA VSI VST VSB BSW 33 Initials, AL VSx Presentation Design Flow Subject, November Month

34 34 Page 34

35 VSI Vehicle System Integrator VSA VSI VST VSB BSW 35 Initials, AL VSx Presentation Design Flow Subject, November Month

36 Virtual Systems Integrator Multi-lingual multi-processor Model Driven Development environment Design verification and validation of embedded software in distributed systems Initial target: AUTOSAR Integrates C/C++, UML, Simulink, EDGE debug, etc 36 BC, AL VSx VSI Design demo flow Flow for AUTOSAR, November 2009 Sept 2008

37 VSI Application Software Development Software Modeling Sourcing functionality Algorithmic Modeling C code Generate XML XML XML XML C/C++ C/C++ C/C++ C/C++ C code Generate Operating System System Services Models use code generated from BridgePoint UML, Simulink, etc. or hand coding 37 BC, AL VSx VSI Design demo flow Flow for AUTOSAR, November 2009 Sept 2008

38 Summary 38 Initials, AL VSx Presentation Design Flow Subject, November Month

39 Summary Mentor Graphics Vehicle Systems Design Suite covers Architecture design VSA Network Design ECU configuration, design and test VFB level simulation Overall goals Enable optimisation of the E/E architecture Enable (early) virtual verification of the system Correctness by design Digital Continuity from requirements to realisation Interaction Layer VSB BSW VST VSI 39

40 40 Initials, AL VSx Presentation Design Flow Subject, November Month

41 NEXT PRESENTATION ECU Software and Conformance Testing Supporting AUTOSAR Bill Chown, Mentor Graphics 41 Initials, AL VSx Presentation Design Flow Subject, November Month