Adaptive AUTOSAR Extending the Scope of … | 2017-09-26 Vector GB Ltd Annual Conference 2017,...
Transcript of Adaptive AUTOSAR Extending the Scope of … | 2017-09-26 Vector GB Ltd Annual Conference 2017,...
V0.1 | 2017-09-26
Vector GB Ltd Annual Conference 2017, September 27th – 28th
Adaptive AUTOSAR – Extending the Scope of AUTOSAR-based Embedded Software
2
Use Cases for Adaptive AUTOSAR
Introduction
2D/3D accel. support in POSIX systems
Video Codecs, Streaming support, multi-media library, etc…
Infotainment
Image- and preprocessing of Camera/Radar/LIDAR
Sensor Fusion and Machine Learning
Highly Automated Driving
Connectivity
“App-Store” for automotive applications
Installation and update over the air
Dynamic Software Platform
Car-2-X (LTE, WiFi, GPS, etc.)
Multimedia (USB, SD-Card, NFC, etc.)
source: fotolia
3
New use cases bring new requirements
Incremental Deployment > Allow download of individual applications
> Allow dynamic initialization and scheduling of applications
> Allow dynamic initialization of service needs (e.g. communication)
High performance computing > Support of faster CPU architectures
(e.g. 64 Bit ARM and Intel architectures)
> Support of hardware accelerators (e.g. GPUs)
> Efficient multicore exploitation
Requirements for Adaptive AUTOSAR
Introduction
Foundation (FO)
common requirements
Classic Platform (CP)
Adaptive Platform
(AP)
Efficient software development > Object-orientation and use of dynamic memory
> Integration of existing software (e.g. GUI-toolkits)
AUTOSAR decided to rearrange and extend the standard
Both standards must be compatible with each other
Each standard targets different ECU types
4
2
Classic AUTOSAR
Adaptive AUTOSAR
1
3 Conclusion
5
We’ve come a long way with AUTOSAR classic
It supported many use cases right from the start > Communication (CAN, LIN, FlexRay)
> NV memory
> diagnostics
> network management
Introduction
Classic AUTOSAR
Over time several features were added
6
SOAD
We’ve come a long way with AUTOSAR classic
It supported many use cases right from the start > Communication (CAN, LIN, FlexRay)
> NV memory
> diagnostics
> network management
Ethernet Support
Classic AUTOSAR
ETHIF
ETHSM
TCPIP
IPv4, ARP, ICMPv4 IPv6, NDP, ICMPv6
UDP, TCP, DHCPv4, DHCPv6
COMM SD
BSWM
LDCOM COM
PDUR
UDPNM
TLS
RTE
SWC SWC SWC
SOMEIPXF
Over time several features were added > Ethernet
ETHTRCV ETH ETHSWT
Hardware
7
Hardware
We’ve come a long way with AUTOSAR classic
It supported many use cases right from the start > Communication (CAN, LIN, FlexRay)
> NV memory
> diagnostics
> network management
Multicore Support
Classic AUTOSAR
MIC
RO
SAR D
IAG
Core 1 Core 2
MICROS. SYS X
CP
MIC
RO
SAR M
EM
MIC
RO
SAR C
OM
MU
NIC
ATIO
N
MIC
RO
SAR I
O
Com
ple
x D
rivers
MICROSAR CAL MICROSAR
EXT Core Test
ECU State Manager Satellite
Com
ple
x D
rivers
Watchdog Manager Satellite
ECU State Manager
Watchdog Manager
Multicore RTE
SWC SWC SWC
MIC
RO
SAR O
S
Multi-
Core
SWC
Over time several features were added > Ethernet
> Multicore
8
We’ve come a long way with AUTOSAR classic
It supported many use cases right from the start > Communication (CAN, LIN, FlexRay)
> NV memory
> diagnostics
> network management
Safety Features
Classic AUTOSAR
Safe RTE
SWC SWC c SWC SWC
SafeOS
SafeBSW
Safe
WD
G
MCAL
Hardware
E2E
ASIL QM
Over time several features were added > Ethernet
> Multicore
> Safety
9
RTE
SWC SWC SWC
We’ve come a long way with AUTOSAR classic
It supported many use cases right from the start > Communication (CAN, LIN, FlexRay)
> NV memory
> diagnostics
> network management
Security Features
Classic AUTOSAR
Hardware
CRYDRV (HSM)
CRYDRV (SHE)
CRYDRV (SW)
CRYIF
CSM
SHE HSM
Channel SH
E
Channel H
W-R
SA
CSM queuing &
prioritization
AES AES RSA
Over time several features were added > Ethernet
> Multicore
> Safety
> Security
10
We’ve come a long way with AUTOSAR classic
It supported many use cases right from the start > Communication (CAN, LIN, FlexRay)
> NV memory
> diagnostics
> network management
POSIX Support (Vector-proprietary)
Classic AUTOSAR
Over time several features were added > Ethernet
> Multicore
> Safety
> Security
> POSIX (Vector-proprietary)
Ethernet CAN
Guest OS
RTE
SWC SWC SWC
POSIX OS
PDUR
Diagnostics COM
MIC
RO
SAR M
EM
MIC
RO
SAR S
YS
CAN Socket BSD Socket
POSIX Process
Hardware
11
Feature-rich
Stable
Real-time capable
Scalable
Resource efficient
Still improving
We’ve ended up with a platform that is
We’ve come a long way with AUTOSAR classic
It supported many use cases right from the start > Communication (CAN, LIN, FlexRay)
> NV memory
> diagnostics
> network management
Conclusion
Classic AUTOSAR
Over time several features were added > Ethernet
> Multicore
> Safety
> Security
> POSIX (Vector-proprietary)
> V2G (Vector-proprietary)
> Time synchronization
> …
12
2
Classic AUTOSAR
Adaptive AUTOSAR
1
3 Conclusion
13
AUTOSAR Runtime for Adaptive Applications (ARA)
Architecture
Adaptive AUTOSAR
Adaptive AUTOSAR Foundation Adaptive AUTOSAR Services
(Virtual) Machine / Hardware
AUTOSAR Runtime Environment
for Adaptive Applications
Software Configuration Management
Service
Signal-2-Service Mapping
Service
Diagnostics
Service
Identity Access Management
API
Execution Management
API ARA::EXEC
Operating System
API POSIX PSE51
Persistency
API ARA::PER
C++ std library
Logging and Tracing
API
Cryptography
API
Communication Management
API ARA::COM
REST
API ARA::REST
Network Management
API
Time Synchronization
API
AdaptiveApplication
API
AdaptiveApplication
Service API
Software Cluster
AdaptiveApplication
API
AdaptiveApplication
Service API
Software Cluster
AdaptiveApplication
Service API
Software Cluster
BSD BSD BSD
BSD
BSD
BSD BSD
Platform Health Management
API
14
Applications
Adaptive AUTOSAR
Manifest
Instance Configuration
Application
> Multi-threaded
> Execution states
> Manifest contains platform related information (recovery action, dependencies to services or libraries)
> Instance config contains application specific static information (variant, options, …)
Interfaces
> ara::com for communication with adaptive services (basic services and user applications)
> PSE51 is the usable OS API subset
> The Adaptive AUTOSAR Foundation clusters (Execution Management, Persistency, etc.) are available via direct APIs
AdaptiveApplication
POSIX Process
INIT:
RUN:
SHUTDOWN:
Thre
ad
Thre
ad
Thre
ad
Adaptive AUTOSAR Services
Adaptive AUTOSAR
Foundation
ara::com Direct API PSE51
C++ Stdlib
POSIX OS
15
Overview ara::com
Adaptive AUTOSAR
Service-oriented communication
Location-transparent
Supports multiple communication bindings
AUTOSAR model defines available bindings for each service provider and consumer
Explicit support for optimized shared memory implementations
Services
APP 1 APP 2
ara::com
Applications connected at runtime (Service Discovery)
Find service instances dynamically without hardwiring in model
Connection between proxies and skeletons can be recovered
Real-time support: Developers’ choice of polling or event-driven processing of communication
16
Application Code Service Description (ARXML)
Tools and Workflow
Adaptive AUTOSAR
libara
libsomeip
Logic
SOME/IP Config
AppSWCTypes
Port
Auth
ori
ng T
ool
Soft
ware
Configura
tion M
anagem
ent
ServiceInterface ServiceInterface ServiceInterface
ECU
SOMEIPd
ComServer
Diag
EM
Installed APP
Application Manifest (JSON)
BIN
Instance Manifest(s)
(JSON)
Installed APP
Application Manifest (JSON)
BIN
Instance Manifest(s)
(JSON)
POSIX IPC
BSD Sock
Deploy Package
/opt/myApp/
Application Manifest
./etc/MANIFEST.arxml
BIN
./bin/myApp
Instance Manifest(s)
./etc/instance1.arxml
./etc/instance2.arxml
Genera
tors
Port Port
Static
Proxies / Skeletons
SOME/IP Serializer
E2E Serializer
POSIX IPC
Generated Com
piler
17
Hypervisor combines Safety and Linux
Adaptive AUTOSAR
SafePOSIX (e.g. PikeOS)
Linux
Hypervisor (e.g. PikeOS)
Barrier: Safe and Secure
QM Application
QM Adaptive AUTOSAR
Safe Application
Safe Adaptive AUTOSAR
µController
18
2
Classic AUTOSAR
Adaptive AUTOSAR
1
3 Conclusion
19
AUTOSAR Classic Platform - CP
Technical Comparison of Both Standards
Conclusion
AUTOSAR Adaptive Platform - AP
Real Time Requirements
Computing Power
Safety Critical
Executed in place (ROM)
Developed in C
Whole stack compiled and linked in one piece
All applications share one address space (MPU-based)
All modules completely specified
Focus on signal-oriented communication (AUTOSAR COM)
Loaded at startup (RAM)
Developed in C++
Software components as loadable POSIX processes
Each process has its own address space (MMU-based)
Less modules, only APIs specified
Focus on service oriented communication (SOME/IP)
20
Powertrain / Chassis
Central Computing
Cluster
A Possible E/E-Architecture
Conclusion
Body Infotainment ADAS & Safety
EMS Radar
Camera
Camera
Connectivity
ESP
Airbag
Smart Charging
3G/LTE WiFi Car2X
CAN | LIN | Ethernet
Switch Switch
Connectivity Control
Off-Board Tester
Switch
Switch
Classic Platform (CP)
Adaptive Platform (AP)
21
Conclusion
Conclusion
The new Adaptive Platform complements
the existing Classic Platform
The Classic Platform will host deep
embedded functions
The Adaptive Platform will host resource
intensive, high-order functions
Vector will continue to contribute to AUTOSAR
and provide implementations and tools for
both Classic and Adaptive AUTOSAR
For more information:
https://vector.com
https://www.youtube.com/user/vectorchannel
Contact your local sales agent for
> Evaluation Bundle, Prototype, Training
22 © 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V0.1 | 2017-09-26
For more information about Vector and our products please visit www.vector.com
Author: Dr. Bastian Zimmer, Oliver Garnatz Vector Germany