Automotive Embedded System Development in AUTOSAR Contents What

Automotive Embedded System Development in AUTOSAR

Contents What is AUTOSAR from a Technical Point of View Example AUTOSAR System Automotive Embedded System Development in AUTOSAR 2

What is AUTOSAR (AUTomotive Open System Architecture) Ø De-facto standard, jointly developed by automobile manufacturers, suppliers and tool developers. Ø More than 100 member companies Ø Homepage : www. autosar. org The idea of AUTOSAR Ø Standardized and uniquely-specified interfaces basic software modules help to master the increasing complexity Ø The consequence is reusability, efficiency and easy handling of electronic in the automobile AUTOSAR Target and Goal Ø Ø Define open reference architecture for ECU software Specify a clear interface between basis software components and application Reusability Growing software quality 3

What is AUTOSAR partnership 10 Core Partners 48 Associate Members Cape. Ware 52 Premium Members OEM Tier 1 Standard Software Source: 4 Tools Semiconductors

What is AUTOSAR Project Objectives Ø AUTOSAR vision is an improved complexity management of highly integrated E/E architectures through an increased reuse of SW modules between OEM and suppliers. 5

What is AUTOSAR Benefits from AUTOSAR 6

AUTOSAR from a Technical Point of View AUTOSAR Layered Architecture AUTOSAR Software Component Interface Application Software Component Actuator Software Component Sensor Software Component AUTOSAR Interface Standardized Interface API 0 API 3 Private Interfaces inside Basic Software possible Operating System Standardized Inteface API 2 VFB & RTE relevant API 1 RTE relevant . . . AUTOSAR Interface AUTOSAR Runtime Environment (RTE) ECU Firmware Standard Software AUTOSAR Software Application Software Component Standardized AUTOSAR Interface Standardized Interface AUTOSAR Interface Services Communication ECU Abstraction Standardized Interface Basic Software ECU-Hardware 7 Standardized Interface Microcontroller Abstraction AUTOSAR Interface Complex Device Drivers

AUTOSAR from a Technical Point of View AUTOSAR Layered Architecture 8

AUTOSAR from a Technical Point of View Methodology Ø Derive E/E architecture from formal descriptions of soft- and hardware components Functional software is described formally in terms of “software Components” (SW-C). Using “Software Component Descriptions” as input, the “Virtual Functional Bus” validates the interaction of all components and interfaces before software implementation. Mapping of “Software Components” to ECUs and configuration of basic software. The AUTOSAR Methodology supports the generation of an E/E architecture. 9

AUTOSAR from a Technical Point of View AUTOSAR SW-C (Software Component) Ø Application is divided into SW-Cs. Ø Software Components consist of £ Ports Interface to other SW-Cs £ Runnable Entities (or Runnables) Procedures which contain the actual implementation Triggered cyclically or on event (e. g. data reception) £ Other software components Composite components for hierarchical design Ø Three types of SW-C £ Atomic SW-C £ Composite SW-C £ Sensor/Actuator SW-C 10

AUTOSAR from a Technical Point of View RTE (Runtime Environment) Ø Ø Ø Implementation of Virtual Functional Bus Interface between SW-Cs and Basic Software All calls to basic software pass through the RTE Communication method : Send/Receive signals, Client/Server functionality Triggering of runnables : Cyclically or On event 11

AUTOSAR from a Technical Point of View MCAL (Microcontroller Abstraction Layer) Ø MCAL is the lowest software layer of the Basic Software Ø It contains internal drivers, which are software modules with direct access to the microcontroller internal peripherals and memory mapped microcontroller external devices Ø Make higher software layers independent of microcontroller 12

AUTOSAR from a Technical Point of View EAL (ECU Abstraction Layer) Ø The EAL interfaces the drivers of the MACL Ø It also contains drivers for external devices Ø It offers an API for access to peripherals and divides regardless of their location and their connection to the microcontroller (port pins, type of interface) Ø Make higher software layers independent of ECU hardware layout 13

AUTOSAR from a Technical Point of View Services Layer Ø Services Layer is the highest layer of the Basic software which also applies for its relevance for the application software Ø The Services layer offers £ Operating system functionality £ Vehicle network communication and management services £ Memory services (NVRAM management) £ Diagnostic services £ ECU state management Ø Provide basic services for application and Basic Software modules 14

Example AUTOSAR System : Lighting System Software Component View 15

Example AUTOSAR System : Lighting System Virtual Functional Bus View 16

Example AUTOSAR System : Lighting System Mapped System 17

Example AUTOSAR System : Lighting System Basic Software Architecture 18