00_AUTOSAR基础知识介绍_AUTOSAR BASIC INTRODUCTION.pdf

AutoSAR BASIC INTRODUCTION

1. 24/10/2018
AUTOSAR Training Part Ⅰ
•V01
Classic Fundamental

2. Contents
1.Why AUTOSAR
2.Introduction to AUTOSAR
3.AUTOSAR Architecture
4.Methodology of AUTOSAR
5.AUTOSAR Interfaces
24/10/2018 2

3. Why AUTOSAR
01

4. Development of Functionality
24/10/2018 4

5. Why AUTOSAR
24/10/2018 5
The challenge:
E/E complexity is growing fast
Quantity of software is exploding
Many different hardware platforms are used
Development processes and data formats are not harmonized
The main objective of
Improve software quality and reduce costs by re-use
Reuseof functions across carlines and across OEM boundaries
Reuseof basic software
Reuseof development methods and tools

6. Why AUTOSAR
24/10/2018 6
Source: Explore AUTOSAR Conference in Pune 2012

7. 10 years
24/10/2018 7
Source: 6
th
AUTOSAR Open Conference

8. 10 years
24/10/2018 8
Source: 6
th
AUTOSAR Open Conference

9. Introduction to AUTOSAR
02

10. Introduction to AUTOSAR
24/10/2018 10

11. Introduction to AUTOSAR
24/10/2018 11
“Cooperate on standards –compete on implementation”
Two different AUTOSAR statements:

12. Introduction to AUTOSAR
24/10/2018 12

13. AUTOSAR Accomplishments
24/10/2018 13
StandardizeDevelopment Process and exchange formats
>Methodology + Templates
StandardizeFunctionality
>Functional Interfaces
Specify a clear interfacebetween basic
software modules and application
>RTE
Define open reference architecturefor
ECU software
>Basic Software

14. AUTOSAR Architecture
03

15. AUTOSAR Architecture
24/10/2018 15
Automotive Open System Architecture (AUTOSAR)
>Standardized, openly disclosed
interfaces
>HW independent SW layer
>Transferability of functions
Redundancy activation
AUTOSAR RTE:
by specifying interfaces and their
communication mechanisms, the
applications are decoupled from
the underlying HW and Basic SW,
enabling the realization of Standard Library Functions.

16. AUTOSAR Basic Software
24/10/2018 16

17. AUTOSAR Basic Software Modules
24/10/2018 17

18. AUTOSAR Basic Software
24/10/2018 18
80 BSW modules abstracted by 3 layers

19. Service Layer
24/10/2018 19
Task
>Services for application
Functionality
>Diagnostics, NVRAM Management, OS, Communication
>Memory and ECU management

20. ECU Abstraction Layer
24/10/2018 20
Task
>Make higher levels independent of ECU hardware
Functionality
>Driver for external devices
>Interface for internal and external periphery (IO)

21. Microcontroller Abstraction Layer
24/10/2018 21
Task
>Make higher layers independent of microcontroller
Functionality
>Drivers with direct access to internal periphery of µC
>Memory-mapped devices external to µC

22. Complex Device Drivers
24/10/2018 22
Task
>Offer functionality for complex sensors and actuators
Functionality
>Direct access to resources for critical applications
>Examples: Injection control, tire pressure monitoring

23. Methodology of
AUTOSAR
04

24. Methodology of AUTOSAR
24/10/2018 24
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/Earchitecture

25. Methodology of AUTOSAR
24/10/2018 25
Following the AUTOSAR Methodology, the E/E architecture is
derived from the formal description of software and hardware components

26. Methodology of AUTOSAR
24/10/2018 26

27. Overview
24/10/2018 27

28. AUTOSAR Interfaces
05

29. AUTOSAR Interfaces
24/10/2018 29

30. AUTOSAR Interfaces
24/10/2018 30

31. AUTOSAR Interfaces
24/10/2018 31

32. AUTOSAR Interfaces
24/10/2018 32

33. Thank You