EB tresos Classic AUTOSAR Training

Introduction & Basic AUTOSAR

Concepts
Introduction

Chapter overview

• Motivation for AUTOSAR

• Major AUTOSAR objectives
• AUTOSAR organization and evaluation of Standards
• AUTOSAR concepts
• Software components (SW-C)
• Virtual function bus (VFB)
• Runtime Environment (RTE)
• Basic Software (BSW)

© Elektrobit (EB) 2022 | Confidential 2

Motivation for AUTOSAR

In cooperation with
Introduction – Motivation for AUTOSAR

Technology Changes

© Elektrobit (EB) 2022 | Confidential 4

Aims and benefits of using AUTOSAR

Yesterday AUTOSAR • Hardware and software – widely

independent of each other
• Development can be de-coupled

Methodology
Standardized
Software by horizontal layers, reducing
Application
Software development time and costs
• Reuse of software enhances
quality and efficiency
• Companies cooperate in

HW-specific
(ECUs)
standardization and compete in
Hardware Hardware implementation
Hardware
Hardware

© Elektrobit (EB) 2022 | Confidential 5

Introduction – Motivation for AUTOSAR

(AUTomotive Open System ARchitecture)

is a worldwide development partnership of vehicle manufacturers,
suppliers, service providers and companies from the automotive
electronics, semiconductor and software industry.

© Elektrobit (EB) 2022 | Confidential 6

Major AUTOSAR objectives

In cooperation with
Major AUTOSAR objectives

Main Working Topics

Architecture

Acceptance
Methodology
Tests

Application
Interfaces

© Elektrobit (EB) 2022 | Confidential 8

Major AUTOSAR objectives

Main working topics

Main Working Topics

Architecture

Software architectures including a complete basic

Acceptance
Methodology software stack for ECUs – the so called AUTOSAR Basic
Tests
Software – as an integration platform for hardware
independent software applications.
Application
Interfaces

© Elektrobit (EB) 2022 | Confidential 9

Major AUTOSAR objectives

Main working topics

Main Working Topics

Architecture

Defines exchange formats and description templates to

Acceptance enable a seamless configuration process of the basic
Methodology
Tests software stack and the integration of application
software in ECUs. It includes even the methodology
how to use this framework.
Application
Interfaces

© Elektrobit (EB) 2022 | Confidential 10

Major AUTOSAR objectives

Main working topics

Main Working Topics

Architecture

Specification of interfaces of typical automotive

Acceptance
Methodology applications from all domains in terms of syntax and
Tests
semantics, which should serve as a standard for
application software.
Application
Interfaces

© Elektrobit (EB) 2022 | Confidential 11

Major AUTOSAR objectives

Main working topics

Main Working Topics

Architecture

Specification of test cases intending to validate the

Acceptance
Methodology behavior of an AUTOSAR implementation with
Tests
AUTOSAR application software components or within
one vehicle network.
Application
Interfaces

© Elektrobit (EB) 2022 | Confidential 12

AUTOSAR organization
and evolution of Standards

In cooperation with
AUTOSAR organization and evolution of Standards

The platforms are organized by 5 AUTOSAR standards

Acceptance Application
Test Interfaces

Classic Platform (CP) Adaptive Platform (AP)

Foundation (FO)

© Elektrobit (EB) 2022 | Confidential 14

AUTOSAR organization and evolution of Standards

Classic Platform vs. Adaptive Platform

Technical characteristics

Based on OSEK Based on POSIX

Execution of code directly from ROM App. is loaded from persistent memory into RAM

Same address space for all applications Each application has its own (virtual) address space
(MPU support for safety) (MMU support)
Optimized for signal-based communication Service-oriented communication
(CAN, FlexRay)
Fixed task configuration Support of multiple (dynamic) scheduling strategies

Specification Specification and code

© Elektrobit (EB) 2022 | Confidential 15

AUTOSAR organization and evolution of Standards
AUTOSAR – Core Partners and Partners

9 Core Partners 53 Premium Partners 38 Development Partners

General OEM

Generic Tier 1

Standard Software

Tools and Services

127 Associate Partners

Semiconductors 21 Attendees

© Elektrobit (EB) 2022 | Confidential 1616

AUTOSAR organization and evolution of Standards

AUTOSAR Milestones

First release (1.0) Release 2.0/2.1 Release 4.0 Release 4.1.1

Basic SW complete Feature enrichment • Timing analysis
• Multicore support
• Diagnostics
• Functional safety
Release 3.0/3.1 • Acceptance testing
Additional features • Ethernet
•…
•…
AUTOSAR Derived New development
founded applications methods

2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013

© Elektrobit (EB) 2022 | Confidential 17

AUTOSAR organization and evolution of Standards

AUTOSAR Milestones
Release 4.3.0 Release 4.3.1 Release 4.4
• Hardware Test • Quality • Remote Event Communication Manager
Management on • Interface Module for • Harmonization of Physcial Units for ASW and
Startup and Shutdown Ethernet and IP testing BSW Based on ASAM
• Crypto Interface • Macro Encapsulation Of • Security Policy Manager Module
• V2X Support Library Calls • AUTOSAR Real Time Interface
• Extended Buffer Access • Error Detection and • RTE Implementation Plug-Ins
for Rapid Prototyping Correction for • LIN-Support for LIN slave
Release 4.2.1
• SOME/IP Transport Communication
• Large data communication via Ethernet • Ethernet Wake on data line
Protocol Decentralized
and CAN FD • Formal Model Query and Blueprint Derivation
Configuration
•… Mechanisms
• Bus-Mirroring
• Extended Serialization for Data Structures in
SOME/IP with tag/length/value encoding

2013 2014 2015 2016 2017 2018

© Elektrobit (EB) 2022 | Confidential 18

AUTOSAR organization and evolution of Standards

AUTOSAR Milestones
Release 19-11 Release 20-11 Release 21-11
• BSW Multicore Distribution • Ethernet: Wakeup On Dataline, • Functional Safety: e.g. Mode Dependent Configuration, System
• Non-Volatile Data Handling 10BASE-T1S Health Monitoring
Enhancements • Security: Intrusion Detection System • Data Distribution Service (DDS) Security
Manager (IdsM)
• Firmware over the Air • Memory Stack Rework
• Classic Platform Flexibility
• IPSec Protocol
• Rework of PNC related ComM and NM
• Communication (Signal Service
handling
Translation)
• Diagnostics (DoIP Extension)
For details, please refer to www.autosar.org
→ Standards
→ Classic Platform
→ Search for “Release Overview”

2019 2020 2021 Future

© Elektrobit (EB) 2022 | Confidential 19

AUTOSAR organization and evolution of Standards

AUTOSAR releases / EB tresos ACG Versions

H1 2012 H2 2012 H1 2013 H2 2013 H1 2014 H2 2014 H1 2015 H2 2015 H1 2016 H2 2016 H1 2017 H2 2017 H1 2018 H2 2018 H1 2019 H2 2019 H1 2020 H2 2020 H1 2021 H2 2021 H1 2022

AUTOSAR Releases

ASR 4.0.3 ASR 4.1.1 ASR 4.1.2 ASR 4.1.3 ASR 4.2.1 ASR 4.2.2 ASR 4.3.0 ASR 4.3.1 ASR 4.4 ASR 19-11 ASR 20-11 ASR 20-11
01/2012 03/2013 10/2013 03/2014 10/2014 07/2015 11/2016 12/2017 10/2018 12/2019 12/2020 12/2020

ACG 7
ACG7 supports selected RfCs and selected Features based on
AUTOSAR 4.0.3, 4.1.x and 4.2.x

ACG 8
ACG8 supports selected RfCs and selected Features based on
AUTOSAR 4.0.3, 4.1.x , 4.2.x, 4.3.x, 4.4.x, 19-11, 20-11
Current
Release

Implementation of the AUTOSAR Classic Platform → Autocore Generic (ACG) 8.7.0 8.7.1 8.7.2 8.8.0 8.8.2 8.8.4

Implementation of the corresponding tooling → EB tresos Studio 26.1 26.2 27 27.1 28.0 28.2

© Elektrobit (EB) 2022 | Confidential 20

AUTOSAR Concepts

In cooperation with
AUTOSAR Concepts

Software architecture of AUTOSAR Classic Platform

▪ An AUTOSAR application consists of one
or more (interconnected) Software
components (SW-C)

▪ Run Time Environment (RTE) is a

communication centre for inter- and
intra-ECU information exchange.
It realizes the communication defined in
the Virtual Functional Bus (VFB) on one
specific ECU

▪ The Basic Software (BSW) is a

standardized software layer that
provides standard ECU functionality (OS,
low level drivers, bus-communication,
diagnostics, memory management etc.)

© Elektrobit (EB) 2022 | Confidential 23

AUTOSAR Concepts

Software architecture of AUTOSAR Classic Platform

Application Actuator Sensor Application
Software Software Software AUTOSAR Software
Component Component Component Software Component

Runtime Environment
AUTOSAR
Interface
Services Communication
Complex Device Standardized
Drivers AUTOSAR
Operating ECU Abstraction Interface
System
Standardized
Interface
Basic Software Microcontroller Abstraction

ECU-Hardware

© Elektrobit (EB) 2022 | Confidential 24

AUTOSAR Concepts

Software Components and Virtual Function Bus

• Software components (SW-C): Application software to run in an AUTOSAR system
• Communication between SW-Cs through well defined Ports and Interfaces using Assembly connectors
• The High-level communication abstraction is called Virtual Function Bus (VFB)

SW-C SW-C SW-C SW-C

A B C n

Ports and
Interfaces

Assembly
connectors
Virtual Functional Bus

© Elektrobit (EB) 2022 | Confidential 25

 AUTOSAR Concepts

Virtual Function Bus

▪ Simplified picture of the VFB (without Ports)

SW-C SW-C SW-C SW-C

A B C n

VFB

© Elektrobit (EB) 2022 | Confidential 26

 AUTOSAR Concepts

Virtual Function Bus

▪ During system design phase, the SW-Cs are partitioned to ECUs (SW-C to ECU mapping)
▪ This results in two different types of communication paths:
▪ Intra-ECU (inside one ECU)
▪ Inter-ECU (between different ECUs)

ECU 1 ECU 2 ECU N

SW-C SW-C SW-C SW-C

A B C n

VFB

© Elektrobit (EB) 2022 | Confidential 27

AUTOSAR Concepts

Runtime Environment (RTE)

▪ The Runtime Environment (RTE) is the only interface to the SW-Cs

▪ The RTE implements the VFB on each ECU
▪ The RTE uses Network (CAN/Ethernet/FlexRay/LIN) buses for inter-ECU communication via the Basic Software Layer (BSW)
ECU 1 ECU 2 ECU N

SW-C A SW-C B SW-C C SW-C n

RTE RTE … RTE

BSW BSW BSW

Gateway
Flex Ray CAN

© Elektrobit (EB) 2022 | Confidential 28

AUTOSAR Concepts - Summarized

In cooperation with
AUTOSAR Concepts - Summarized

Software Components and Virtual Function Bus

AUTOSAR defines four key concepts:
– Software components (SW-C) SW-C SW-C
SW-C SW-C
– A piece of software to be run in an A
… n
B C
AUTOSAR system
– Virtual Functional Bus (VFB) Application
– High level communication Interfaces Virtual Functional Bus
abstraction
– Run Time Environment (RTE)
– Implements the VFB on one ECU Methodology
ECU 1 ECU 2 ECU m
– Basic Software (BSW) SW-C SW-C SW-C SW-C
– Standard software for standard ECU A B C … n
functionality (OS, communication,
Architecture RTE RTE RTE
memory, hardware drivers, diagnostics
BSW BSW BSW
etc)

© Elektrobit (EB) 2022 | Confidential 30

AUTOSAR Concepts - Summarized

Virtual Function Bus and Runtime Environment (RTE)

Non-AUTOSAR AUTOSAR
▪ Hard-coded dependencies between Applications and services ▪ Application communications exclusively with the RTE using
well defined APIs
▪ No difference between internal communication and bus
App 2 communication → Relocatability and reuse!
App 1

SW-C A SW-C B SW-C C SW-C D

App 5 App 4
App 3
RTE

Diagnostics Custom
manager Com-Stack Service

© Elektrobit (EB) 2022 | Confidential 31

Basic Software (BSW)

In cooperation with
AUTOSAR Concepts

Overview of Software Layers (Top view)

Application Layer

Runtime Environment (RTE)

Basic Software (BSW)

Microcontroller

© Elektrobit (EB) 2022 | Confidential 33

AUTOSAR Concepts

Basic Software – Layers

Application Layer

Runtime Environment

Services Layer

Complex
ECU Abstraction Layer Drivers

Microcontroller Abstraction Layer

Microcontroller

© Elektrobit (EB) 2022 | Confidential 34

AUTOSAR Concepts

Basic Software – Functional groups

Application Layer

Runtime Environment
System Services Memory Services Crypto Services Off-board Communication I/O Hardware Complex
Communication Services Abstraction Drivers
Services

Onboard Device Memory Crypto Hardware Wireless Communication

Abstraction Hardware Abstraction Communication Hardware
Abstraction HW Abstraction Abstraction

Microcontroller Memory Drivers Crypto Drivers Wireless Communication I/O Drivers

Drivers Communication Drivers
Drivers

Microcontroller

© Elektrobit (EB) 2022 | Confidential 35

AUTOSAR Concepts

Basic Software – Detailed view

Can Eth
LdCom Com NM Key
ECU Mode Manager

Dcm Sm Sm
Manager

WdgM

ComM
BswM

Dem
Lin Fr
Fim

Det
NVRAM PduR Sm Sm
Manager Fr Can Udp Crypto
Fr Can Lin Nm Nm Nm Service
DoIP, SoAd, TcpIp
Tp Tp
IPDUM Manger
Tp
I/O
HARDWARE
Memory Abstraction If ABSTRACTION
WdgIf EthIf CANIF LINIF FRIF

Complex Drivers
Crypto If
EEPROM FLASH EEPROM
OS

EXT ABSTRACTION EMULATION EXT EXT EXT Ext

Eth Eth CAN LIN FR SW-based
Wdg CAN LIN FR Crypto
AUTOSAR Libraries

EXT EXT Swt Trcv Trcv Trcv Trcv Crypto Drv

Drv EEPROM Drv FLASH Drv Drv Drv Drv Drv
EEPROM Drv
FLASH Test

Crypto Drv
FLASH Drv
RAM Test

PWM Drv
Core Test

PORT Drv
WDG Drv
MCU Drv

OCU Drv
CAN Drv

ADC Drv
GPT Drv

DIO Drv
ICU Drv
Eth Drv

LIN Drv

SPI Drv
FR Drv
Hardware

© Elektrobit (EB) 2022 | Confidential 36

Introduction & Concepts - Summary

Summary

• Motivation for AUTOSAR

• Major AUTOSAR objectives
• AUTOSAR organization and evaluation of Standards
• AUTOSAR concepts
• Software components (SW-C)
• Virtual function bus (VFB)
• Runtime Environment (RTE)
• Basic Software (BSW)

© Elektrobit (EB) 2022 | Confidential 37

Get in touch!

[email protected]
www.elektrobit.com