Hands-On Workshop: AUTOSAR Training (Reserved Seat Required) FTF-ACC-F1243 Marius Rotaru | Technical Leader - Automotive Software J U N E . 2 0 1 5 TM External Use Agenda • AUTOSAR Motivation and Principles − Vision and Objectives − Development Cooperation − Architecture of the Standard − Migration of the Standard • AUTOSAR Configuration Methodology & Tools • AUTOSAR MCAL • AUTOSAR OS • Examples: Hands-on Training − LAB1: Blinking LED − LAB2: Dimming LED TM External Use 1 #FTF2015 AUTOSAR Motivation and Principles TM External Use 2 #FTF2015 Embedded Software Android Mars Curiosity Rover 11.8 MLoC F-35 Joint Strike Fighter 5MLoC 23.5 MLoC There is A LOT of Embedded Software in Automotive! Mercedes S Class ~100MLoC Source: http://spectrum.ieee.org/green-tech/advanced-cars/this-car-runs-on-code http://www.informationisbeautiful.net/visualizations/million-lines-of-code/ TM External Use 3 #FTF2015 AUTOSAR Standardization Technology partnerships and open standards encouraging “plug-and-play” approach Freescale, a reliable partner for automotive software and hardware innovation: Standardization MSR Manufacturer-Supplier Relationship • Driving member of the OSEK/VDXTM OSEK/VDX consortium, with own operating system implementation Hersteller Initiative Software ASAM ODX • Founding member of the LINTM consortium FlexRay™ Protocol HIS TM • Founding member of FLEXRAY partnership Local Interconnect Network Media Orientated System Transport • First semiconductor vendor to join AUTOSARTM partnership Source: (AUTomotive Open System ARchitecture) TM External Use 4 #FTF2015 AUTOSAR Vision AUTOSAR aims to improve the complexity management of integrated E/E architectures through increased reuse and exchangeability of software modules between OEMs and suppliers. OEM b Exchangeability between suppliers’ OEM c OEM a Platform b.1 solutions Platform b.2 Platform b.n Supplier A Supplier B Platform c.1 Platform c.2 Platform a.1 Chassis Chassis Platform c.n Platform a.2 Safety Safety Platform a.n Body/ Telematics Exchangeability Comfort OEM d between Supplier C manufacturers’ Body/Comfort applications Powertrain Telematics OEM f Platform d.1 Platform d.2 Platform d.n OEM e Exchangeability between vehicle Platform f.1 Platform f.2 platforms Source: Platform f.n Autosar_GuidedTour.pdf Platform e.1 Platform e.2 Platform e.n TM External Use 5 #FTF2015 AUTOSAR Vision AUTOSAR aims to standardize the software architecture of ECUs. AUTOSAR paves the way for innovative electronic systems that further improve performance, safety and environmental friendliness. Customer needs Yesterday AUTOSAR • Adaptive Cruise Control • Lane Departure Warning • Advanced Front Application Software Lighting System Software standardized Using standards • Communication Stack HW-specific • OSEK Hardware • Diagnostics Hardware • CAN, FlexRay • Hardware and software will be widely independent of each other • Development can be de-coupled by horizontal layers. This reduces development time and costs • The reuse of software increases at OEM as well as at suppliers. This enhances quality and efficiency Source: Autosar_GuidedTour.pdf TM External Use 6 #FTF2015 AUTOSAR Objectives PO1: PO6: Transferability of Sustainable utilization of software natural resources PO2: Architecture PO7: Scalability to different Collaboration between vehicle and platform various partners variants PO8: PO3: Standardization of basic Different functional software functionality of domains Application Methodology automotive ECUs Interfaces PO4: Definition of an open PO9: architecture Applicable automotive international standards and state-of-the-art PO5: technologies Dependable systems Source: AutoSAR_RS_ProjectObjectives.pdf Autosar_GuidedTour.pdf TM External Use 7 #FTF2015 AUTOSAR Main Working Topics Architecture • Architecture: Software architecture including a complete basic software Application Methodology Interfaces stack for ECUs — the so called AUTOSAR Basic Software — as an integration platform for hardware independent software applications. • Methodology: Architecture Defines exchange formats and description templates to Application enable a seamless configuration process of the basic Methodology Interfaces software stack and the integration of application software in ECUs. It includes even the methodology how to use this framework. • Application Interfaces: Architecture Specification of interfaces of typical automotive applications from all domains in terms of syntax and semantics, which Application Methodology Interfaces should serve as a standard for application software. Source: Autosar_GuidedTour.pdf TM External Use 8 #FTF2015 AUTOSAR — Concept and Functional Domain Functional Domains The AUTOSAR project objectives will be met by specifying and Vehicle standardizing the central ‘centric’ architectural elements across Powertrain functional domains, allowing Safety industry competition to focus on Chassis (active/ passive) implementation. AUTOSAR Human Telematics Machine Interface Body and Comfort Cooperate on standards, Passenger compete on implementation. ‘centric’ Source: Autosar_GuidedTour.pdf TM External Use 9 #FTF2015 AUTOSAR — Cooperation Structure and Partners AutoSAR Partners (Nov. 2014) TM Source: , actual status at http://www.AUTOSAR.org External Use 10 #FTF2015 Basic AUTOSAR Approach SW AUTOSAR SW AUTOSAR SW AUTOSAR SW AUTOSAR 2 3 n 1 Software Component - - - - C C C C 1 Virtual Integration 1 (SW-C) description Independent of hardware ... Virtual Functional Bus. Integration of SW-C via 2 Virtual Functional Bus (VFB) Virtual Functional Bus 3 2 ECU Description Introduction of Hardware 3 4 Attributes Tools supporting development of software components 4 System Constraints Holistic view of the entire System Constraint ECU 5 Description system, both software and Descriptions 5 hardware. 5 Mapping of SW-C on ECU ECU Description Description specific ECU ECU I ECU II ECU n ECU Configuration AUTOSAR AUTOSAR AUTOSAR AUTOSAR 6 Configuration of Basic Run-Time Environment SW-C 1 SW-C 2 SW-C3 ... SW-C n Software Modules Separation of system into its RTE 6 RTE 6 RTE 6 (BSW) and Run-Time ECU (plus common Basic Basic Basic Environment (RTE) Software Software Software infrastructure). System Gateway Description Flex Ray CAN Source: TM External Use 11 #FTF2015 AUTOSAR Architecture — Components and Interface View Source: TM External Use 12 #FTF2015 AUTOSAR Layered Software Architecture Basic structure distinguishes four basic layers. Application Layer Software Components Runtime Environment Basic Software Basic SoftwareBasic ECU ECU Microcontroller Resources Source: TM External Use 13 #FTF2015 AUTOSAR Layered Architecture The AUTOSAR Basic Software is further divided in the layers: Services, ECU Abstraction, Microcontroller Abstraction and Complex Drivers. Application Layer Runtime Environment Services Layer Complex ECU Abstraction Layer Drivers Microcontroller Abstraction Layer Microcontroller Source: TM External Use 14 #FTF2015 AUTOSAR Layered Architecture The Basic Software Layers are further divided into functional groups. Examples of Services are System, Memory and Communication Services. Application Layer Runtime Environment System Services Memory Services Communication Services I/O Hardware Abstraction Complex Drivers Onboard Device Memory Hardware Communication Abstraction Abstraction Hardware Abstraction Microcontroller Drivers Memory Drivers Communication Drivers I/O Drivers Source: Microcontroller Source: TM External Use 15 #FTF2015 AUTOSAR Freescale Solution • Freescale Software Products include the AUTOSAR Operating System, AUTOSAR MCAL Drivers and Complex Device Drivers • The full AUTOSAR RTE (Runtime Environment) stack is available through our integration partners Integration Partners AUTOSAR stack Freescale OS + MCAL + CDD TM External Use 16 #FTF2015 AUTOSAR Documents http://wwww.autosar.org Published Releases For information only, see disclaimer Two documents exist for each BSW module: - SRS: Software Requirement Specification - SWS: Software Specification TM External Use 17 #FTF2015 AUTOSAR — Application Migration Uncontrolled software design Structured design 1 2 Single-sided RTE with software Partial introduction of AUTOSAR BSW components (SW-C) and legacy BSW with legacy SW-Cs to BSW adapters 3 4 Complete AUTOSAR BSW with Fully AUTOSAR compliant ECU adapters for legacy SW-Cs 5 6 Legacy software AUTOSAR compliant Software Source: RTE AUTOSAR BSW Hardware components SW components Adapter Autosar_GuidedTour.pdf TM External Use 18 #FTF2015 AUTOSAR Configuration Methodology and Tools TM External Use 19 #FTF2015 Basic Software Configuration Process Freescale AUTOSAR Integration Partners receive Freescale MCAL and OS releases for pre-integration into their proprietary AUTOSAR BSW products. TM External Use 20 #FTF2015 AUTOSAR Methodology and Templates — Waterfall View .arxml System Configure BSW Specific (MCAL/OS) Configuration System .arxml Input: System System Extract ECU Configuration Specific .arxml Description: Information System ECU Extract of Configure System ECU .arxml .exe Configuration: System ECU Generate ECU Configuration Executable Executable Values System ECU • The AUTOSAR Methodology is foreseen to support activities, descriptions and use of tools in AUTOSAR . The notation of the Software Process Engineering meta-model (SPEM) is used • The AUTOSAR methodology is not a complete process description but rather a common technical approach for some steps of system development • Outside the scope of the AUTOSAR standard is: . Description of tools (which add value to the ‘Activities’