introduction to adaptive autosar · elektrobit (eb) 2017 | please do not distribute outside gm and...

Introduction to Adaptive AUTOSAR

Dheeraj Sharma July 27, 2017

Elektrobit (EB) 2017 | Please do not distribute outside GM and its affiliates.

• Software Platform and scope of Adaptive AUTOSAR

• Adaptive AUTOSAR architecture and roadmap

• EB Adaptive Platform and Prototyping solution

Overview


2


Requirements for a future car infrastructure

• Main drivers

– Automated Driving

– Car-2-X applications

• Requirements

– High computing power

– High data rates

– High availability, fail-operational systems

– Update over the air


3


Consolidated E/E architecture


4

UI Computing

Cluster

Computing Cluster(s)

Smart Antenna

Gateway IO Concentrators, Actors, Sensors

Smart Sensors

Smart Sensors

Steering

Braking Battery

Engine Back-end System

Gigabit Ethernet

Reliable ECU

Performance ECU

IO Concentrators

Back-end Server



5

Future architecture of 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 with heterogeneous computing

Widespread, POSIX-like Operating System (e.g. Linux), Adaptive AUTOSAR

Extensive update capabilities

Safe & Secure

• IO Controller

Provide Sensor and Actuator Services

Deeply embedded, real-time Operating System (e.g. Classic AUTOSAR)

Limited (non-standardized) support for partial updates

Smart Antenna



6

Major Types of Adaptive Platforms

Type3: Virtual Resource Partitioning

Adaptive AUTOSAR

App App

Core 1

ECU

Core 2

Classic AUTOSAR

Automotive-grade Hypervisor

Type2: Core Partitioning

Adaptive AUTOSAR

App App

Core 1

ECU

Core 2

Classic AUTOSAR

Adaptive AUTOSAR

App App

Core 1

ECU

Core 2

Type4: Performance, MultiCore

Type1: µC Partitioning

Adaptive AUTOSAR

App App

Micro 1

ECU

Micro 2

Classic AUTOSAR

Adaptive AUTOSAR (ARA)





Overview


7



8

Adaptive AUTOSAR (ARA)

• Execution Management

Lifecycle management of platform (machine) and application (process) incl. privileges of access control and machine states

• Persistency

Load data from persistent storage and store data over boot and ignition cycle

• Communication Management

SOME/IP based including serialization and service discovery

Publish/subscribe mechanism for intra- and inter-ECU communication

• Platform Health Management

Alive Supervision

• Diagnostics

Event memory management and diagnostic service handling

• Developed in C++ (C14)

• OS will provide POSIX PSE51 interfaces to the application but Adaptive Platform will require further features



Process Model

9

Adaptive AUTOSAR Foundation

Adaptive AUTOSAR Services

(Virtual) Machine / Hardware

Application 1

API(libc) API API

Software

Configuration

Management

Service

Security

Management

Service

Diagnostics

Service

Bootloader

Operating

system

Execution

Management

Persistency

Platform Health

Management

Logging and

Tracing

Hardware

Acceleration

Communication

Management

Time

Management

Application 2

Each application lives in its own protected address space Each application lives in its own address space

Access to platform functionality via libraries

API(libc) API API

Communication via implementation specific IPC



Functional Clusters

10

AUTOSAR Runtime for Adaptive Applications

Adaptive AUTOSAR Foundation


Adaptive AUTOSAR Services

Software

Configuration

Management

Service

Security

Management

Service

Diagnostics

Service

Bootloader

Operating

system

API

Execution

Management

API

Persistency

API

Platform Health

Management

API

Logging and

Tracing

API

Hardware

Acceleration

API

Communication

Management

API

Time

Management

API

Application Application Application Application Application

Language specific APIs as part of ARA

Services provided via Communication ARA API

APIs and services exposed to applications by functional clusters



Service Interface

11


Communications

Adaptive Application

Ethernet Driver

TCP/IP

SOME/IP Transport

IPC Transport

IPC

Dispatching and Discovery

normative interface

informative interface

private interface

Public Interface Part of the adaptive AUTOSAR API and specified in the SWS. Protected Interface Interaction between functional clusters. Not normative, intended to make specification more readable and to support integration of SW into demonstrator. Private Interface Interaction between elements within a functional cluster. Not used in specifications.

C++11 Language Binding

ARA API

network

Execution

Management

API

Elektrobit (EB) 2017 | Please do not distribute outside GM and its affiliates. © Elektrobit (EB) 2016 | Confidential

• Continuous AUTOSAR releases twice a year (March, October)

• Distribution of AUTOSAR Code Base for concept validation

• Adaptive AUTOSAR specifications will be in status “development” until R18-10 (no backward compatibility granted)

AUTOSAR Adaptive Roadmap


12





Overview


13



Host

• EB tresos Studio for AdaptiveCore

• EB tresos AdaptiveCore SDK

• EB Build Environment

14

EB tresos AdaptiveCore - System

Target

• ARA Components/Adaptive Platform

• Operating System (incl. BSP)

• 3rd Party Modules


EB tresos Studio for AdaptiveCore


15

Development

• IDE for construction and qualification of application software components

Integration & Configuration

• Configuration of system manifest and binding of application software components to adaptive platform on machine and application level

System Configuration Tool OEM

Information


Target System Host System


EB tresos AdaptiveCore

OS

Application SWC Application SWC Application SWC Application SWC

Time Management

Studio

Key Features: Configurator Generators

Manifest Builder CDT for C++

16

Runtime Environment for Adaptive (ARA)

All bold names are licensable items.

EB tresos® 3rd Party

OEM AdaptiveCore HW-depend.

Tools Open Source AdaptiveCore

Generic

Alternatives

Customer EB products

OEM-specific

Platform Health Management

Persistency

Foundation

Services

Execution Management

Diagnostics

SW Configuration Management

Security Management

Logging and Tracing

HW Accerlaration

SDK

Key Features: CDT

QEMU

DEBUG

Key Features: Deploy

Run Debug

Ap

plic

atio

n

Hypervisor

Bootloader Linux

BSP

Communication Management

Ad

apti

ve P

latf

orm



17

Target support

• Development based on Yocto Linux

Development of ASIL-B Linux distribution

• Porting to other operating systems upon request

Please inquire

• Lead Target platforms

Renesas R-Car H3

• Further support planned for

Nvidia DrivePX

Intel Denverton

• Further portings on request

Please inquire

www.elektrobit.com [email protected]

We take AUTOSAR to the road!

introduction to adaptive autosar · elektrobit (eb) 2017 | please do not distribute outside gm and...

Documents