Embed Size (px)
Citation preview
Adaptive AUTOSAR:
Infrastructure Software for
Advanced Driver Assistance
Chris Thibeault
June 7, 2016
Elektrobit Tech Day – June 7, 2016
Agenda for Adaptive Platform
• Introduction
• Goals for the presentation
‒ What is the Adaptive Platform?
‒ Why do you need Adaptive Platform?
• Requirements for future vehicle infrastructure
• Changing architectures for vehicles and ECUs
• Basic principles and scope of Adaptive Platform
• EB’s experience and plans
• Summary
© Elektrobit (EB), 2016 2
Elektrobit Tech Day – June 7, 2016
AUTOSAR is a Software: AUTOSAR is a software abstraction layer between the Application Code and
the ECU Hardware, i.e. Microcontroller. THE AUTOSAR software is comprised of three basic
components:
1. Microcontroller Abstraction Layer (MCAL)
2. Basic Software (BSW)
3. Operating System (OS)
-> See next slide for an example
© Elektrobit (EB), 2016 3
Hardware
Software
Conventional
Application Software
Hardware
AUTOSAR
standardized
HW-specific
AUTOSAR
What is ? AUTomotive Open System ARchitecture
Elektrobit Tech Day – June 7, 2016
EB tresos AutoCore 7 based on AUTOSAR 4.0.3 & RfCs 4.1.x / 4.2
© Elektrobit (EB), 2016 4
OS
Os
Ap
pli
cati
on
IP
SoAd
TcpIp
EthIf
UdpNm
EthSm
Com ServicesCom, PduR, IPduM
CAN
CanAs
CanIf
CanTp
CanNm
CanSm
LIN
LinIf
LinTp
LinNm
LinSm
FlexRay
FrAs
FrIf
FrTp
FrNm
FrSm
Runtime EnvironmentRte, RteAs
Memory
MemAs
Crc
Ea
Fee
MemIf
NvM
Base
Configurators
HidWiz
PbcfgM
SvcAs
Workflows
Det
EcuC
Make
MemMap
Platform
DoIP
Libs
CDD
Ba
sic
So
ftw
are
Fr*
FrTrcv*CanTrcv*
RamTst* Can Eth*
EthTrcv*
Lin
LinTrcv
Eep
Fls
FlsTst
Wdg AdcMcu
Port
Dio
Icu
Gpt
Pwm
Spi
IoHwAbs
SD
XCP
Watchdog
WdgM
Wdglf
Dbg
Mode
Mgmt.
ComM
EcuM
BswM
Nm
Diagnostic
Dem
Dcm
FiM
Crypto
Application SWCApplication SWCApplication
SWCApplication SWCApplication SWC Application SWC
CAL
CPL*
LD COM
SOMEIPXF
COMXF
Transformer
TimeSyncStbM
CanTSyn
FrTSyn
EthTSyn
CSM
CRYSHE
CRY*
SECOC
ACG
3rd Party
OEM
ACM *EB / 3rd Party
AssistantNew
E2EXF
Current car infrastructure
• Basic software mostly based on
AUTOSAR Classic or comparable system
Pro:
• Efficient on small microcontrollers
• Well suited for time-critical, safe and
secure applications
Con:
• Only proprietary solutions for fail-over
and redundant functionality
• Fixed, inflexible communication
mechanisms
Elektrobit Tech Day – June 7, 2016
© Elektrobit (EB), 2016 5
AUTOSAR
App App
CPU
ECU 1
AUTOSAR
App App
CPU
ECU 2
Gateway
ECU 3 ECU 4
OBD
Connector
Requirements for a future car infrastructure
• Main drivers
‒ Automated/Autonomous Driving
‒ Car-2-X applications
• Cloud based services
• Requirements
‒ High computing power
‒ High data rates
‒ High availability, fail-operational
systems
‒ Updates over the air
Elektrobit Tech Day – June 7, 2016
© Elektrobit (EB), 2016 6
Elektrobit Tech Day – June 7, 2016
Requirements for a future car infrastructure
© Elektrobit (EB), 2016 7
Requirements Technical Solution
High computing power High Performance Controllers and GPUs
High data rates Ethernet (1 GigE, 10 GigE)
High availability, fail-operational systems Redundancy Concept
Service oriented architecture (SOA)
Update over the air Usage of file systems
Reliable security mechanisms
Service oriented architecture (SOA)
Future architecture of a car infrastructure
• Split up ECUs in low performance IO Controller and high performance controller
• Establish a service oriented architecture (SOA)
• Performance Controller
‒ High computation power
‒ Widespread, POSIX-like Operating System (e.g. Linux)
• IO Controller
‒ Provide Sensor and Actuator Services
‒ Deeply embedded, real-time Operating System (e.g. AUTOSAR)
Elektrobit Tech Day – June 7, 2016
© Elektrobit (EB), 2016 8
Gateway
IO
IO
IO
Cloud
PF
IO
IO
IO
PF
Elektrobit Tech Day – June 7, 2016
ECU Hardware Architecture for Performance Controllers
© Elektrobit (EB), 2016 9
Core PartitioningPure Autosar
Hypervisor
App App
Core 1
ECU
Core 2
AUTOSARPerformance
Platform
App App
Core 1
ECU
Core 2
AUTOSAR
Performance
Platform
App App
Core 1
ECU
Core 2
AUTOSAR
Hypervisor
Performance Platform
App App
Core 1
ECU
Core 2
Microcontroller Partitioning
Performance
Platform
App App
Micro 1
ECU
Micro 2
AUTOSAR
Pure Performance
Performance Microprocessor
“Classic AUTOSAR”
Elektrobit Tech Day – June 7, 2016
Architecture of the Adaptive Platform
© Elektrobit (EB), 2016 10
Linux Kernel
AUTOSAR SWCs
QM
RTE
AUTOSAR
OSBSWDsCom
E2E
TimE
AUTOSAR SWCs
QM
“Adaptive AUTOSAR”
EB tresos AdaptiveCore
Adaptive
SWCs
Adaptive
SWCs
Elektrobit Tech Day – June 7, 2016
Adaptive Platform – Basic Principles
• Posix-like OS (e.g. Linux)
‒ Well known standard
‒ Provides Filesystem, dynamic processes, for example.
‒ High potential for reuse of Software for other domains (military,
industrial, automation, aerospace,…)
• Service Oriented Architecture (SOA)
‒ Register services in an ECU
‒ Publish services to other ECUs (SOME/IP)
‒ Concepts are oriented on CommonAPI from GENIVI.
© Elektrobit (EB), 2016 11
Elektrobit Tech Day – June 7, 2016
Scope of Adaptive Platform1
© Elektrobit (EB), 2016 12
• Communication Services
‒ New Middleware – ARA
‒ SOME/IP
‒ TCP/IP over Ethernet
• Classic AUTOSAR
‒ Compatibility layer for
AUTOSAR 4.x SWCs
‒ Communication via SOME/IP
• Methodology
‒ Extension of existing ARXML scheme
• Adaptive OS services
‒ POSIX
‒ Scheduling and Triggering
‒ Execution Manager
• Platform Services
‒ Security
‒ Persistence
‒ Diagnostic Manager
‒ Time Services
‒ Parameter API
‒ Diagnostic Log & Trace
1 Specification may be subject to change
Elektrobit Tech Day – June 7, 2016
Adaptive AUTOSAR Roadmap
© Elektrobit (EB), 2016 13
Elektrobit Tech Day – June 7, 2016
AUTOSAR Roadmap
© Elektrobit (EB), 2016 14
Elektrobit Tech Day – June 7, 2016
EB tresos AdaptiveCore
© Elektrobit (EB), 2016 15
• OS Services
‒ Execution Manager
‒ POSIX interface (PSE51)
• Platform Services
‒ Diagnostics
‒ Logging (DLT)
• Communication Services
‒ Communication middleware
(starting point: CommonAPI)
‒ SOME/IP via Ethernet
“Adaptive AUTOSAR”“Adaptive AUTOSAR”
POSIX OS (Linux)
Adaptive
SWCs
Adaptive
SWCs
Lib
rari
es
(e.g
. O
pe
nC
L)
OS
Se
rvic
es
Pla
tfo
rm S
erv
ice
s
Co
mm
. S
erv
ice
s
Elektrobit Tech Day – June 7, 2016
Starting Point for the Adaptive Platform at EB
EB Platform for Autonomous Driving
© Elektrobit (EB), 2016 16
NVIDIA DRIVE™ PX
Performance Microprocessors A/BSafety MCU
AUTOSAR SWCs
ASIL-D Generic
Linux
Applications
Linux Kernel
Libraries
AUTOSAR SWCs
QM
Can | Ethernet | SPI | FlexRay | Lin
AUTOSAR SWCs
QM
Safety RTE
EB tresos
Safety OS
BSW
MCAL
E2E
TimE
RTE
AUTOSAR
OSBSWDsCom
E2E
TimE
AUTOSAR SWCs
QM
Elektrobit Tech Day – June 7, 2016
Summary for Adaptive Platform
• Adaptive Platform is not a replacement for Classic Platform.
• The Adaptive platform was created to tackle new requirements
related to Automated/Autonomous Driving / Cloud interaction:
‒ High Computing Power
‒ High Communication Data Rates – Ethernet / IP Based
‒ Fail-Operational / High Availability systems
‒ Over the air updates
• The basic principles of Adaptive AUTOSAR are:
‒ Usage of a Linux based OS (POSIX)
‒ Service Oriented Communication
• And, of course, all this must be done Safely and Securely!
© Elektrobit (EB), 2016 17
![Towards adaptive autosar: a system-level approach · AUTOSAR[1] adopts a static configuration approach where the whole system configuration with all its resources is known at design-time](https://img.pdfslide.net/doc/110x75/5e966713795c5a1235649537/towards-adaptive-autosar-a-system-level-approach-autosar1-adopts-a-static-configuration.jpg)
