Markus Maier / ETAS GmbH Development of AUTOSAR SW Components Tools and Methods
1 16.04.2008 © Copyright 2004, ETAS GmbH – LiveDevices Ltd. – Vetronix Corp. All rights reserved. The names and designations used in this document are trademarks or brands belonging to the respective owners. Development of AUTOSAR Software Agenda • Status Quo • ECU Software and System Architecture • Today and Tomorrow • Development of AUTOSAR Application Software • Conclusion
2 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Status Quo The Complexity of E/E Systems in Automotive increases exponentially Number of Systems Communication 50 10 4 40 10 3 30 10 2 20 10 1 Count 10 10 0 1990 1995 2000 2005 2010 1990 1995 2000 2005 2010 bus (CAN/MOST/LIN) # components on comm. # components Daimler BMW Audi VW #signals #sender/receiver pairs
Source: VW 2005, Fachkongreß Automobil-Elektronik Source: BMW, Frischkorn, BoCSE 2002 Computation Power Codesize 10 4 10 12 10 10 10 3 10 10 10 8 10 2 10 8 10 6 LoC MIPS 1 6 4 10 10 10 kByte 10 0 10 4 10 2 1990 1995 2000 2005 2010 1990 1995 2000 2005 2010
performance of engine control kB high-end TV LoC for high-end car
Source: NEC, 2006 (TOP57) Source: Daimler-Chrysler 2004; Philips
3 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Status Quo Software as major driver for Innovation and as a Qualityissue
4 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Components AUTOSAR is coming
• AUTOSAR – software architecture • helps to avoid OEM/Tier1 specific SW architectures • makes commercial SW components and modules possible • makes commercial tools possible • reduces dependencies on dedicated suppliers • makes integration of „proven“ third party software possible – e.g. OEM to ECU supplier • helps to concentrate on new/innovative functions – instead of interface/integration problems • helps to gain development efficiency • helps to increase SW quality • helps to cope with complexity
5 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR Software Agenda • Status Quo • ECU Software and System Architecture • Today and Tomorrow • Development of AUTOSAR Application Software • Conclusion
6 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Software- and System-Architecture of ECUs Today: Proprietary Software-Architecture Application Software Application
Application SW components exchange Operating System data with each other and with the SW- SW- Comp. 1 Comp. 2 basic software. Interface are mostly proprietary! Exchange of components
leads to high effort at different SW- SW- SW- interfaces and components. Comp. 3 Comp. 4 Comp. 5 BasicSoftware Basic Software for Basic Software Proprietary (OEM-specific) Basic SW for Communication & for I/O communication, network management Network Mngt. and I/O. Specific developments do not lead to differentiation of brands. Micro Controller Abstraction
ECU Hardware ECU
Bus
7 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Software- and System-Architecture of ECUs Tomorrow: AUTOSAR – Standardized Software Architecture
Encapsulation of application SW Operating System components by AUTOSAR SW- SW- SW- interfaces. All external Comp. 1 Comp. 2 Comp. n communication has to use this AUTOSAR AUTOSAR … AUTOSAR Interface Interface Interface interface.
AUTOSAR-RTE The AUTOSAR-RTE (Runtime Environment) is the central communication element. Every Basic Software Modules (BSMs) communication within the ECU, over the network or with sensors / actuators (I/O) has to use the RTE. Micro Controller Abstraction
ECU Hardware ECU
Bus
8 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Software- and System-Architecture of ECUs Today: ECU network Vehicle domain Gateway ECU
One ECU controls one or Powertrain Bus more systems of one domain. Therefore all necessary function are integrated into Chassis Bus the same ECU. ECU
ECUs do exchange via vehicle network “just” a few data. Comfort Bus Functions, distribute overKarosserie several ECUs, are still rare. Passive Safety
Infotainment Bus
Vehicle E/E-Systems in the vehicle
9 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Software- and System-Architecture of ECUs Tomorrow: AUTOSAR separates function from ECU
The AUTOSAR Virtual Function Bus is a new level of abstraction. It supports a design of SW components (functions) Feature independent from ECU mapping within the vehicle network. This leads to higher flexibility and better reuse.
Virtual Function Bus
Bus
10 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Software- and System-Architecture of ECUs Future: Function oriented Architecture for higher Flexibility
Functions can be mapped and integrated to Electronic Vehicle Functions ECU in the network as SW components.
SW-Comp. 1 SW-Comp. 2 Driver Assistance ECU Network ECU SW-Comp. 2 SW-Comp. 4 Sensor
„Move“ „Reuse“
Setpoint Device
Actuator
Sensor
Engine Management Vehicle Dynamics Transmission ECU ECU ECU
„Integrate“ „Add“ „Replace“
11 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Software- and System-Architecture of ECUs What disappears? What comes up? What stays?
• What disappears? • Proprietary Basic Software with proprietary interface towards the application software
• What comes up? • Standardized Basic Software Modules • RTE (Runtime Environment) make application software independent from Basic SW and specialities of ECU hardware • Application SW Components with standardized interface description (syntax and specific signals)
• What stays? • Application Software as a brand differentiating key element for the development of new vehicle functions
12 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR Software Agenda • Status Quo • ECU Software and System Architecture • Today and Tomorrow • Development of AUTOSAR Application Software • Conclusion
13 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Components Model based versus manual Software Development
Model based Development Manuel Development Specification of • as executable Model • as text Functions • Coding Guidelines Implementation • Modelling Guideline (e.g. MISRA)
Optimization • tool based • manually
• Automatically (inherent Coding • manually MISRA compliance) Reuse and • Validated Models and/or • Source code or SW Integration SW Components Components • Efficient Validation and Verification of functions on • Verification of Quality Insurance Model Level implemented functions • Autom. Code Generation
14 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Components Model based Methods and Tools - Overview What comes up? 0 AUTOSAR-Compliance! Modelling and simulation of 0 SW components on PC Environment Model SW Integrated Integration of SW (Vehicle, Driver 1 Component 1 Function 2 components on PC and Environment) Virtual Prototyping integrated 2 functions on PC 4 3 Rapid Prototyping in real Virtual World 3 vehicles
Real World 4 Implementation and autom. 5 code gen. of ECU SW Comp. What stays? ECU function tests with HiL 5 6 systems 6 Function validation and Real vehicle, real driver parameter calibration in real and real environment vehicle
15 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Software Modelling and Automatic Code Generation of Software Components
Example - Tool Solution: What stays? • Modelling of SW Components Model of ASCET Simu- Model link with ASCET SW Comp. Model 2 AUTOSAR AUTOSAR Interface • Automatic Code Generation Interface ASCET-MD of AUTOSAR compliant ECU SW Components 1 What comes up? • Specification of AUTOSAR- Interfaces for SW Components in the Model ASCET-SE • Import of Interface ASCET ECU SW Comp. Specification into ASCET SW Comp. AUTOSAR (AUTOSAR XML-Import) Interface 1 Proven and certified Code Generator, more than 60 Mio. ECUs with ASCET-Code on AUTOSAR-RTE the road 2 M2M-Transformation from Simulink to ASCET-Models possible
16 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Software Integration of Software Components on PC
Software Integrated Function Component
Simulin What stays? ASCET ® System Operating ASCET Simulinkk ® SW- Tool-Solution: Model Model C Code • Integration of ASCET-, Komp. Komp.Model ComponentKomp. ® RTA-OSEK Simulink , and C-Code- Prop. Interf. Prop. Interf. ….. AUTOSAR AUTO.Interface Interf. AUTO.Interface Interf. Interface Components What comes up? AUTOSARVirtual Runtime Online Environment AUTOSAR-RTE (RTE) • Integration of AUTOSAR Migration SW Components using a
INTECRIO RTE on PC Operating System Operating SW-Komp.ASCET SW-Komp.Simulink ® SW-Komp.C-Code • AUTOSAR compliant Model1 Model2 Componentn operating system RTA- RTA-OSEK AUTOSAR AUTOSAR .. AUTOSAR OSEK on PC Interface Interface Interface • Integration of prop. and
AUTOSARVirtual Runtime Online AUTOSAREnvironment (RTE) AUTOSAR SW Components • Export of RTE configuration for tool chain
17 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Software Virtual Prototyping on PC
Integrated Function Environment Model
What stays? • Test of integrated functions Tool-Solution: already on the PC: • Simulation of Environment • Verification of Scheduling and communication • Precalibrarion of functions on PC with INCA (automatically) INTECRIO INCA What comes up? • Method provides valuable test RTA-TRACE results due to HW abstraction by RTE • Test of integrated functions prior to the mapping on ECUs
18 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Software Rapid Prototyping in the Vehicle
Integrated Function
What stays? Tool-Solution: • Early Validation of Function INTECRIO Prototypes in the vehicle • Integration of Prototypes via Bypass RTA-TRACE and Vehicle Bus Interfaces (ETK, CAN, LIN, FlexRay) into exiting ECU Networks • Verification of timing behaviour and ES900 Family communication What comes up? VFB • Rapid Prototyping Hardware with AUTOSAR-RTE and -OS Bypass Interface • Standardized Method with Virtual Vehicle Bus Function Bus (VFB) as „Bypass Interface“
19 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Software What disappears? What comes up? What stays?
• What disappears? • Proprietary Methods and Tools for the Development of ECU Functions
• What comes up? • AUTOSAR provides the framework (AUTOSAR Interfaces) for SW Components, which are use to create higher level System Functions • Tools for Integration and Validation for SW Components form different suppliers
• What stays? • Functional Algorithms will not be defined by AUTOSAR and can be developed with established tools • RTE enables – together with appropriate tools – an easy migration from existing proprietary SW components to AUTOSAR SW components /ECUs
20 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR SW Software Reengineering of an Engine Management System towards AUTOSAR
Goal : AUTOSAR migration of existing engine management functions
Development Process : Modelling tool (here: ASCET) : • Partitioning of existing functions into AUTOSAR Software Comp. • Creation of AUTOSAR Interface Wrapper • Automatic Generation of AUTOSAR Reference: ATZ Elektronik, Volume 4, 2007 compliant ECU code Result: Integration tool (here: INTECRIO) : • AUTOSAR can be implemented with existing tools • Integration of AUTOSAR SW Comp. • Depending on requirements (e.g. IP protection or into Engine Management Function modularisation) it is easily possible to reparation • Validation of function with Virtual application SW into differently designed AUTOSAR and Rapid Prototyping SW Components
21 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR Software Agenda • Status Quo • ECU Software and System Architecture • Today and Tomorrow • Development of AUTOSAR Application Software • Conclusion
22 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Development of AUTOSAR Application Software Conclusion
• AUTOSAR standardizes the software architecture of electronic systems for vehicles – to cope with complexity, to increase software quality and to gain more freedom for innovations • AUTOSAR RTE (Runtime Environment) is the central element to separate application and basic software – to enable the development of well encapsulated and reusable software components • AUTOSAR compliant software components / models can be specified in standardized manner by the OEM and can be integrated into the ECUs by the suppliers • ETAS provides already today model based tools and methods to develop AUTOSAR series software at outstanding quality
23 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions Thank you for your attention!
Your questions are welcome
24 16.04.2008 Markus Maier - ETAS GmbH / Software Engineering Solutions