The Use of Hardware Abstraction Layers in Automated Calibration Systems
The Adaptive Platform for Future Use Cases Adaptive/Slides... · 14 Abstraction of the Target...
26
V0.1 | 2016-09-21 Vector Congress 2016 - Stuttgart, 2016-11-30 The Adaptive Platform for Future Use Cases
Transcript of The Adaptive Platform for Future Use Cases Adaptive/Slides... · 14 Abstraction of the Target...
V0.1 | 2016-09-21
Vector Congress 2016 - Stuttgart, 2016-11-30
The Adaptive Platform for Future Use Cases
2
Introduction
Adaptive AUTOSAR Architecture
Use Cases and Requirements
Adaptive AUTOSAR at Vector
Conclusion
Agenda
3
At a glance Introduction
E/E development of following years will be influenced heavily by mega trends like
connectivity, electrifications and automated driving
The use cases introduced by these mega trends will have benefits for both, customers and
OEMs
New players on the market increase the pressure on OEMs to develop and introduced
these use cases very soon
Successful and efficient development of these use cases is not possible using existing
software architectures
Adaptive AUTOSAR is a new architecture to allow implementation of these use cases
4
Automotive Megatrends Introduction
Connectivity (IoT) Automated Driving Electrification
Sophisticated sensors
Sensor fusion
Security
Safety
Highly complex algorithms
High definition maps
Map updates
Infotainment
Cloud Services
V2X
Security
OTA Update
Remote Diagnostics
Automotive APP Store
Start/Stop
Sailing
Hybrid
Multi Voltage
Charger communication
5
New Platform Requirements Introduction
Adaptive Platform
Good Hardware Abstraction
Interoperability with Classic
Update of Software
Service Oriented Architecture
Easy configuration Common Methodology for Classic and Adaptive
Security
Safety
Connection to non-AUTOSAR Services
Multi/Many Core support
Diagnostics
Libraries for high performance computing
Realtime
File handling
New Programming Model
Faster Development Cycles
The new platform has to
fulfill
Existing requirements
Changed requirements
New requirements
6
Definition of Adaptive AUTOSAR Introduction
As a partner of the Automotive industry AUTOSAR saw the necessity to define a new platform
It was clear that future cars will have heterogenous architectures
The existing architectures
had to be complemented
by another one
Adaptive AUTOSAR
Deeply Embedded
Architecture
Infotainment Architecture
Dynamic Architecture
7
Introduction
Adaptive AUTOSAR Architecture
Use Cases and Requirements
Adaptive AUTOSAR at Vector
Conclusion
Agenda
8
Agenda Adaptive AUTOSAR Architecture
Brief introduction to the Adaptive
architecture
What does the Adaptive platform mean for
application developers?
Explanation how the Adaptive platform
handles different use cases
9
Layered Architecture Adaptive AUTOSAR Architecture
Adaptive AUTOSAR Foundation
Adaptive AUTOSAR Services
Operating System
(POSIX based)
Execution Management
Bootloader
Adaptive Applications
Hardware / Virtual Machine
Persistency Management
Platform Health Management
Logging and Tracing
Software Configuration Management
Security
Management Diagnostics
Hardware Acceleration Communications
Hardware/VM
Adaptive AUTOSAR
Foundation
Adaptive AUTOSAR
Services
Adaptive Applications
10
Changes for Application Developers Adaptive AUTOSAR Architecture
Applications are processes
Single- or multi threaded
The configuration is no longer
static at compile time
Manifest files provide
configuration information
Manifests are arxml files
Configuration is done at
runtime
C++ is the main language
POSIX Operating System
Applications
Platform
POSIX OS
Persistency Emd (Execution
Manager Deamon)
App1
POSIX Process
ara::com ara::em ara::pers
SCM Service
ara::com ara::em ara::pers
Diagnostic Service
ara::com ara::em ara::pers
App2
POSIX Process
ara::com ara::em ara::pers
Middleware ara::com SOMEIPd Service
Discovery Shared Memory
ara::em
BSD Socket BSD Socket for DoIP
Manifest Manifest
11
Introduction
Adaptive AUTOSAR Architecture
Use Cases and Requirements
Adaptive AUTOSAR at Vector
Conclusion
Agenda
12
Agenda Use Cases and Requirements
The architecture will be described in more detail based on the following use cases and requirements
Hardware Abstraction
Software Update
Service Oriented Communication
Classic/Adaptive Interoperability
System Design
13
Abstraction of the Target Hardware Use Cases and Requirements
The future use cases have requirements against the
hardware
Very high computational power
Huge among of memory (RAM and ROM)
Support of Hardware Acceleration
High Speed Interfaces
The Adaptive platform must provide an efficient
abstraction of the hardware to the application
ROM
Adaptive AUTOSAR Foundation
Adaptive AUTOSAR Services
POSIX OS
Exec
BL
Adaptive Applications
Persist
Health Logging Tracing
SW Conf Security Diag
HW Accel Comm
64Bit CPU
64Bit CPU
64Bit CPU
64Bit CPU GPU Inter-
faces Eth
RAM
14
Abstraction of the Target Hardware Use Cases and Requirements
The abstraction of the hardware is the job of
an operating system
Adaptive AUTOSAR goes one step further
and abstracts also further parts of the hardware
The Persistency Management takes care about an
interface to non-volatile memory for the application
Use of Hardware acceleration (e.g. GPU) is controlled by
the Hardware Acceleration Management
Excursus: PSE-51
15
Excursus: What is POSIX? Use Cases and Requirements
POSIX - Portable Operating System Interface
Standardized interface between applications and operating system
> E.g. pthread_create, etc.
There are four POSIX profiles
PSE51: 287 APIs, small embedded system, no MMU, no file system
PSE52: 626 APIs, special purpose controllers, no MMU, simplified file system
PSE53: 754 APIs, large embedded system, with file system, with an MMU
PSE54: 912 APIs, large real-time system with all the features
Adaptive AUTOSAR allows PSE-51 only!
What if the OS supports higher POSIX profiles?
16
Update, Upgrade and Relocation of Applications Use Cases and Requirements
Connectivity allows update of software functions in ECUs
Deployment of new functions is also possible
Initial deployment during production
Driver buys applications in an “Automotive App-Store”
These mechanisms allow also relocation of software functions
among differents ECUs
ECU 1 Function
V1.0
ECU 2
Function V1.0
Function V1.0
Function V1.0
Function V1.1
add
update
move
17
Update and Relocation of Applications Use Cases and Requirements
The Adaptive Software Configuration Management
handles deployment of applications
Manifests are deployed with the actual application
and describe their properties
Manifests are arxml files
Adaptive AUTOSAR foundation modules read the
manifest files during deployment and update their
configurations
Applications can access manifest informations
through Adaptive foundation services
Adaptive Application
ara::com ara::em ara::pers Manifest
Deployment package
+
18
Service Oriented Communication Use Cases and Requirements
Flexible deployment of applications requires flexible communication
Hardwired communication paths cannot be used any longer
Service consumer must be able to find service providers at runtime
and subscribe to them
Adaptive AUTOSAR uses a service oriented communication
paradigm
The actual implementation of servers is not specified but a
means to allows service offers and subscriptions
This is implemented using SOME-IP
Cient
Server
Server
Cient
19
Interoperability with the Classic Platform Use Cases and Requirements
Software functions will be distributed among
Adaptive and Classic ECUs
High level parts of those functions will be located
in Adaptive ECUs
Deeply Embedded parts of Software functions will
run on Classic AUTOSAR ECUs
Both worlds are coupled via communication busses
Interoperability is required on the communication
bus
HW
-Int
erfa
cing
Inte
nse
Com
puta
tion ADAS ECU
Steering Sensor ECU
Eth-Switch
M
20
System Architecture Use Cases and Requirements
System architecture shall take both, Adaptive and
Classic into account
This is what the AUTOSAR methodology does
During the first stages of system architecture
development Software function are not mapped to the
Adaptive or Classic Platform
While this is a huge benefit for system architects, care
has to be taken if new features are introduced to the
Adaptive Standard
Abstract System Design
Virtual Function Bus
Implementation
<<adaptive>> <<classic>>
Manifest Code
<<adaptive>>
ECUC Code
Manifest Code
Speed (m/s)
Speed (uint16)
21
Introduction
Adaptive AUTOSAR Architecture
Use Cases and Requirements
Adaptive AUTOSAR at Vector
Conclusion
Agenda
22
Adaptive AUTOSAR Development at Vector Adaptive AUTOSAR at Vector
Demonstrator Development
Specification of Adaptive Platform
Development of a Vector
Adaptive Stack
Adaptive Demonstrator with BMW (Linux)
ICAS Demonstrator with VW (Linux)
Development of a Vector Adaptive Stack including the required tooling
Not bound to a specific target operating system
Support for Linux, QNX, Integrity, PikeOS, etc.
WP-A
WP-A3
WP-X
TF-AP
23
Roadmap Adaptive AUTOSAR at Vector
2017 2018
ASR Release 17.3: > Execution
Management > Communication/Mi
ddleware > DLT > Diagnostics > Operating System > Persistency
2019
ASR Release 17.10: > Filesystem > Package
Management > HW Acceleration > Signal based
communication > Safety and
Platform Health Management
> Security Features
ASR Release 18.03: > SW-Lockstep > FR + LIN Bus > Crypto Hardware
ASR Release 18.10: > Vehicle API > Container Support
MICROSAR Adaptive 18.06: Beta Version of serial production release Based on 17.10 Feature set
MICROSAR Adaptive 19.01: Beta Version of serial production release Based on 18.03 Feature set
2020
MICROSAR Adaptive 19.06: Final Version of serial production release Based on 18.10 Feature set
24
Introduction
Adaptive AUTOSAR Architecture
Use Cases and Requirements
Adaptive AUTOSAR at Vector
Conclusion
Agenda
25
Conclusion Conclusion
The new Adaptive Platform complements
the existing Classic Platform
The Classic Platform will be still necessary to
implement deeply embedded functionalities
while the Adaptive Platform will run high
level parts of functions
Implementing a new Architecture was the
right decision to handle future use cases
Vector will continue to contribute to AUTOSAR
and provide implementations and tools for
Classic and Adaptive AUTOSAR
26 © 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.1 | 2016-09-21
For more information about Vector and our products please visit www.vector.com
Author: Markl, Patrick Vector Germany
