Solution Slides: Adaptive MICROSAR€¦ · Adaptive –best of two worlds ... Dynamic Software Platform Additional, high performance ECUs hosting applications for upcoming use cases

V1.00.00 | 2019-10-09

Ready for Next Generation ECUs

Solution Adaptive MICROSAR

© 2019. Vector North America Inc. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1.00.00 | 2019-10-09

Automotive Trends

Automated DrivingElectrification

Connectivity

Required EnablersOffboard Eco Systems

Major Automotive Topics

Supercomputers On Board

Connectivity

2


Automotive Trends

Cloud / Backend

Embedded Systems

safe

secure

embedded integration and debugging

automotive supply chain

automotive communication protocols

automotive diagnostics

support of high performance processors

high bandwidth

service based architectures

open source, agile development

dynamic and updatable

internet

AUTOSAR Classic

3


support of high performance processors

high bandwidth

service based architectures

open source, agile development

dynamic and updatable

internet

Adaptive AUTOSAR

Adaptive – best of two worlds

Automotive Trends

Cloud / Backend

➔ system and mobility strategies

➔ deep learning

On board Supercomputers

➔ multipurpose computing servers

➔ connectivity, gateways, HMI

➔ automated driving

mastered by OEM

Embedded Systems

➔ intelligent sensors and actuators

➔ basic functions

➔ fallback computing

AUTOSAR Adaptive safe

secure





safe

secure





AUTOSAR Classic

4


Being Prepared for the Next-Generation of ECUs

Introduction

ADAS

Infotainment

source: fotolia

Connectivity

Dynamic Software Platform

Additional, high performance ECUs

hosting applications for upcoming use cases

Adaptive MICROSAR is a complete basic software solution up to ASIL D

Development of applications in the

ecosystem of POSIX-based OS (Linux, PikeOS,

QNX, Integrity, …)

Seamless interoperability with

classic AUTOSAR ECUs

Applications installed and started during runtime

5


Current statically connected HW resources

Introduction

Steering Angle Park Assist ActivationCAN

video line

video line

…

Hardwired video lines between ECUs

Pre-defined CAN messages on bus

Exclusive camera usage

6


Flexible use of HW resources

Introduction

Smart sensors/actuators provide HW over service interface

All ECUs connected via Ethernet

Compound service, using base services as lower layer

Applications can provide services for e.g. HMI integration

No function oriented wiring

Switch

Service Interfaces

7


Drivers for Adaptive AUTOSAR

Introduction

2D/3D acceleration 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, Wi-Fi, GPS, etc.)

Multimedia (USB, SD-Card, NFC, etc.)

source: fotolia

8


Use Cases for POSIX/Virtualization in Automotive Systems

Introduction

MCUCore 1

(POSIX)Core 1 or 2

(MICROSAR)

IPC IPC

MEM

Hypervisor

POSIX besides MICROSAR(current safety set-up)

ECUMCU 1 (POSIX) MCU 2

(MICROSAR)

IPC IPCSPI/ETH

MCUProcess 1 (native POSIX)

IPC

MEM

POSIX

Process 2 (MICROSAR)

IPC OS

POSIX besides MICROSAR(previously used set-up)

POSIX besides MICROSAR(current QM set-up)

MCUProcess 1

(ADAPTIVE)Process 2

(ADAPTIVE)

POSIX

Middleware

Adaptive Autosar(upcoming perspective)

Applications as Driver

1

2

3

4(Hypervisor)

9


Automotive Trends

Introduction

Fundamentals

Details and Functional Clusters

Activities and Roadmap

Agenda

10


AUTOSAR Classic Platform - CP

AUTOSAR Product Comparison

Fundamentals

AUTOSAR Adaptive Platform - AP

All modules completely specified

Developed in C

Whole stack compiled and linked in one piece

Will still remain in the current focus

Configuration compiled in

Less modules, only API specification

Developed in C++

Services as POSIX processes, separately installable

Service oriented communication (SOME/IP)

Configuration loaded from manifest files

(Virtual) Machine / Hardware

AUTOSAR Runtime Environment

for Adaptive Applications

SWC

COMOS API

SWC

COMOS API

SWC

COMOS API

Application Layer

Runtime Environment

Memory Services

Communication Services

I/O Hardware Abstraction

Complex Drivers

I/O DriversCommunication

DriversMemory Drivers

Microcontroller Drivers

Onboard Device Abstraction

Communication Hardware

Abstraction

Memory Hardware

Abstraction

System Services

Microcontroller

Application Software

Component

AUTOSAR Interface

ActuatorSoftware

Component

AUTOSAR Interface

Sensor Software

Component

AUTOSAR Interface

ApplicationSoftware

Component

AUTOSAR Interface

Adaptive Platform Foundation

Adaptive Platform Services

Update & Configuration Management

Service (ucm)

Network Management

Service (nm)

Diagnostics

Service (diag)

Time Synchronization

API (tsync)

Execution Management

API (exec)

Logging & Tracing

API (log)

Core Types

API (core)

Communication Management

API (com)

State Management

Service (sm)

Signal to Service Mapping

Service (s2s)Persistency

API (per)

Cryptography

API (crypto)

Identity Access Management

API (iam)

Platform Health Management

API (phm)

RESTful

API (rest)

Operating System

POSIX PSE51 / C++ STL

11


AUTOSAR Classic Platform - CP

AUTOSAR Product Comparison

Fundamentals

AUTOSAR Adaptive Platform - AP

Application Layer

Runtime Environment

Memory Services

Communication Services

I/O Hardware Abstraction

Complex Drivers

I/O DriversCommunication

DriversMemory Drivers

Microcontroller Drivers

Onboard Device Abstraction

Communication Hardware

Abstraction

Memory Hardware

Abstraction

System Services

Microcontroller

Application Software

Component

AUTOSAR Interface

ActuatorSoftware

Component

AUTOSAR Interface

Sensor Software

Component

AUTOSAR Interface

ApplicationSoftware

Component

AUTOSAR Interface

Real Time Requirements

Computing Power

Safety Critical

(Virtual) Machine / Hardware

SWC SWC SWC

ARA ARA ARA

AUTOSAR Runtime Environment

for Adaptive Applications

Adaptive Platform Foundation

Adaptive Platform Services

Update & Configuration Management

Service (ucm)

Network Management

Service (nm)

Diagnostics

Service (diag)

Time Synchronization

API (tsync)

Execution Management

API (exec)

Logging & Tracing

API (log)

Core Types

API (core)

Communication Management

API (com)

State Management

Service (sm)

Signal to Service Mapping

Service (s2s)Persistency

API (per)

Cryptography

API (crypto)

Identity Access Management

API (iam)

Platform Health Management

API (phm)

RESTful

API (rest)

Operating System

POSIX PSE51 / C++ STL

12


Adaptive Applications

Fundamentals

Manifest

InstanceConfiguration

Application

> Multi-threaded

> Execution states

> Manifest contains platform related information (recovery action, dependencies to services or libraries)

> Instance configuration 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

Application (1:n Executables)

POSIX Process

INIT:

RUN:

SHUTDOWN:Thre

ad

Thre

ad

Thre

ad

Adaptive AUTOSAR Services

ara::com

Adaptive AUTOSAR

Foundation

Direct APIPSE51

C++ Stdlib

POSIX OS

13


Guided configuration via IDE in Eclipse Plugin Implementation available for several platforms

Application logic is strictly separated from configuration (see /opt/ deployment directory)

Code examples based on Vector’s implementation

Vector’s Adaptive Implementation

Fundamentals

14


Application CodeService Description (ARXML)

Tools and Workflow

Fundamentals

libara

libsomeip

Logic

SOME/IP Config

AppSWCTypes

Port

Auth

oring T

ool

Soft

ware

Configura

tion M

anagem

ent

ServiceInterfaceServiceInterfaceServiceInterface

Vehicle

SOMEIPd

ComServer

Diagnostics

Execution Manage-

ment

Installed APP

Executable Config. (JSON)

BIN

InstanceConfig.(JSON)

Installed APP

Executable Config. (JSON)

BIN

Instance Config.(JSON)

POSIX IPC

BSD Sock

Deploy Package

/opt/myApp/

Execution Manifest

./etc/MANIFEST.arxml

BIN

./bin/myApp

Instance Manifest(s)

./etc/instance1.arxml

./etc/instance2.arxml

Genera

tors

PortPort

Static

Proxies / Skeletons

SOME/IP Serializer

E2ESerializer

POSIX IPC

GeneratedC

om

piler

15


Tooling: DaVinci Adaptive Tool Suite

Fundamentals

1. Assistants for various tasks like creation of SOME/IP deployment

2. Easy to understand DSL to represent ARXML models. With linting support

3. Auto-completion for references and model elements

4. Built-in CFG-5 generators. Direct modelling feedback and resolution suggestions

5. Cheat Sheets guide through the process of service creation

1

2

3

4

5

16


1. Diagram-based design of service interfaces

2. Modeling of implementation details of the service interfaces

3. Design of the SW components, executables and adaptive applications

4. Table-based editing of deploy-ment aspects as SOMEIP IDs

5. Graphical design of Ethernettopologies

6. Assistant for creation and mapping of service instances on machines

7. Import and export of different model subsets in AUTOSAR XML

PREEvision: Adaptive system design with PREEvision

Fundamentals

1 2

3

4

5

Service Interface

Description

7

AdaptiveSystem

Description

Manifest

6

17


Adaptive MICROSAR Evaluation Bundle

Fundamentals

Prepared build scripts for native Linux

Adaptive MICROSARsource included

Implement your services using Eclipse

Test your applicationdirectly in native environment

Bundle is available off-the shelf and includes:

> 2 day training at Vector for one person

> Application Developer Guide

> DaVinci Adaptive Tool Suite (1 year license)

18


Automotive Trends

Introduction

Fundamentals



Agenda

19


Communication: ara::com


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

20


Startup

OS launches Execution Manager (EM) (PID1, “init”)

EM inspects system for installed applications

E.g., scan filesystem in /opt/ for application manifests

EM runs startup applications (fork(), exec())

e.g., bring up IP stack

EM consults Machine State Manager to determine desired machine state

Machine state defines set of applications desired to run

EM starts/stops applications to reach desired machine state (fork(), exec(), signal(SIGTERM))

EM configures scheduling parameters & resource limits

Configuration data obtained from application manifest

EM monitors for machine state changes or process termination

Execution Management: ara::exec


ECU running

21


Diagnostic Manager

Diagnostics: Overview


ara::com

Diagnostic Request Diagnostic Response

Tester

No fundamental changes to existing diagnostic workflows (like development, production, workshop,…) due to Adaptive Platform

Main Tasks

ISO 14229-5 (UDSonIP)

Including fault-memory (DTC) handling

Including transport layers (i.e. DoIP –ISO 13400-x)

Configurable via AUTOSAR Diagnostic Extract (DEXT)

ARA service

Uses ara::com interfaces

Application (Software Components)

Diagnostic CodingCallbacksDiagnostic Measurements

CallbacksDiagnostic Routines

Diagnostic Monitor

Diagnostic Monitor

Diagnostic Monitor

Faults

22


Diagnostics: Configuration workflow (DEXT)


refe

rences

PREEvision

CANdelaStudio

System Design

Diagnostic Design

DEXT

MANIFEST(Design)

23


Persistency: ara::per

Key-Value Storage library based access to non-volatile memory for Adaptive Applications.

Multiple values stored in one storage location

Addressing of single values by using a key as identifier

Multiple storage locations/databases can be used

Database format not specified by AUTOSAR


Stream Storage

Raw access to storage locations/files

Used for access to files in any format

API derived from C++ Standard Library std::fstream classes

24


Identity and Access Management

Offers intra ECU and inter ECU access management

A policy decision point decides whether resource access is granted or not


Adaptive Application “x”

Functional ClusterIdentity and Access

Management

1. Request action2. Is Application “x”

authorized?

3. Yes

4. Perform request (e.g. access resource, communicate, get information, etc.)

database

processed execution manifests

Policy enforcement point (PEP)

Policy decision point (PDP)

OEM PDP Application

25


Automotive Trends

Introduction

Fundamentals



Agenda

26


Use cases such as highly automated driving easily demand safety up to ASIL D

Architecture in high performance controllers is complex due to many involved abstraction layers:

BSP from semiconductor vendor

Hypervisor

Multiple Operating Systems

POSIX libraries

Adaptive AUTOSAR Basic Software

Service Oriented Applications Components

Typically many vendors involved for these components

Vector is providing the complete and ready to go solution for such controllers out of one hand.

Safety as a necessity for high performance ECUs


AA partition n

…

DM

…

PikeOS

IP Stack

File System

EM COM AA partition 0

Platform Applications

Partition Pool for Adaptive Applications (AA)

Ethernet

27


Vectors Adaptive Activities


Available Off-the-shelf Products

Specification of Adaptive

platform

Multiple POSIX systems integrated

Series Production

Development

Integrated tool concept

Evaluation Bundle

Products synchronized with Autosar specification

Linux

QNX

PikeOS

Integrity

All feature teams are covered

Active participation in all working groups

Series production projects have been started for many customers

28


Planned Adaptive MICROSAR Roadmap


Adaptive MICROSAR R3:

Production Release(QM)

2018 2019 2020

Adaptive MICROSARR5:

Production Release(ASIL D)

Adaptive MICROSAR R1:

Development Release

PikeOS/MICROSAR Integration

Development Release


Production Release (ASIL D)


Production Release(QM)

Adaptive MICROSAR development started in 2015

Adaptive MICROSAR used in many evaluation and prototyping projects

Adaptive MICROSAR used in the first series production projects

29


Project n

Continuous Development

Tools & BSW

Project Phases Overview


Evaluation Package

Development ShareUp to 12 deliveries per year

OEM Add-on

SIPBase Package

Nominationfrom OEM

SLPMA

18% year

Ongoing updates

Project 1

License

Production SIP

OEM Add-on

SIPBase Package

Production License

Branch/Freeze

MA18% year

MA18% year

MA35% year

MA35% year

Custom Prototypeno branch possible

30


Author:Ralf FritzVector North America

For more information about Vectorand our products please visit

www.vector.com

http://www.vector.com/

Documents

Solution Slides: Adaptive MICROSAR€¦ · Adaptive –best of two worlds ... Dynamic Software Platform Additional, high performance ECUs hosting applications for upcoming use cases