A Course On AUTOSAR Basics

Download as pdf or txt
Download as pdf or txt
You are on page 1of 29

A Course

On
AUTOSAR Basics

Chapter 01-
INTRODUCTION Instructor:
TO AUTOSAR ABHAI TIWARI
➢ What is AUTOSAR?
01 ➢ AUTOSAR Objectives

INTRODUCTION ➢ Benefits of using AUTOSAR


➢ AUTOSAR architecture Vs Non AUTOSAR Architecture
TO AUTOSAR ➢ AUTOSAR Platforms
➢ What is AUTOSAR?
01 ➢ AUTOSAR Objectives

INTRODUCTION ➢ Benefits of using AUTOSAR


➢ AUTOSAR architecture Vs Non AUTOSAR Architecture
TO AUTOSAR ➢ AUTOSAR Platforms
What It is an open and standardized software architecture for
automotive electronic control units (ECUs).
is
AUTOSAR? AUTOSAR was developed by a consortium of
(AUTOMOTIVE OPEN SYSTEM ARCHITECTURE) automotive manufacturers, suppliers, and software companies. The goal
of AUTOSAR is to make automotive software development
more efficient, reusable, and portable.

Application Layer
AUTOSAR is based on a layered architecture. The top layer is the
RTE Application Software (ASW), which contains the software components
that implement the specific functions of the ECU, such as engine
control, transmission control, and braking control.

Basic Software Layer (BSW)


The bottom layer is the Basic Software (BSW), which provides the basic
services that all AUTOSAR software components need, such as
memory management, communication, and error handling.
Microcontroller
AUTOSAR
PARTNERS
(More Than 350 AUTOSAR Partners)
AUTOSAR PARTNERS ➢ AUTOSAR was formed in July 2003 by Bavarian Motor Works (BMW),
Robert Bosch, Continental, Mercedes Benz (formerly Daimler-Benz, then
DaimlerChrysler), Siemens VDO, and Volkswagen to promote an open
industry standard for automotive electrical-electronic (E/E) architecture.

➢ In November 2003, Ford Motor Company joined as a core partner, and


in December, Stellantis (formerly PSA Peugeot Citroën) and Toyota
Motor Corporation joined.

➢ The following November, General Motors also became a core partner.


These companies are responsible for organizing, managing and
controlling the AUTOSAR development partnership. In this core, the
board defines the overall strategy and roadmap.

9
AUTOSAR PARTNERS
➢ The following Premium Partner Plus are currently making
use of the standards.

➢ In addition, they are collaborating with Core, Premium


and Development Partners to define the AUTOSAR
standards themselves:

3
➢ The following Premium Partners are currently
AUTOSAR PARTNERS making use of the standards.

➢ In addition, they are collaborating with Core and


Development Partners in order to define the
AUTOSAR standards themselves:

68
➢ The following Development Partners are currently making
AUTOSAR PARTNERS use of the standards.

➢ In addition, they are collaborating with Core and Premium


Partners in order to define the AUTOSAR standards
themselves:

80
AUTOSAR PARTNERS ➢ The following Associate Partners are currently making use of
the standard documents AUTOSAR has already released:

164
AUTOSAR PARTNERS ➢ The following Attendees are currently collaborating with
Core, Premium and Development Partners in order to define
the AUTOSAR standards themselves:
41
➢ What is AUTOSAR?
01 ➢ AUTOSAR Objectives
➢ Benefits of using AUTOSAR
INTRODUCTION ➢ AUTOSAR architecture Vs Non AUTOSAR Architecture
TO AUTOSAR ➢ Difference Between general BSP & AUTOSAR
➢ AUTOSAR Classic Vs AUTOSAR Adaptive
Major AUTOSAR Objectives

Architecture

Acceptance
Methodology
Tests

Application
Interfaces
Major AUTOSAR Objectives

Architecture ❑ The AUTOSAR software architecture is designed


to be modular, reusable, and scalable. This makes
it easy to develop and maintain complex
automotive software systems.
Acceptance
Methodology ❑ The AUTOSAR software architecture which
Tests
include a complete basic software stack for ECUs
(Called as BSW).

❑ This also provides integration platform for


Application hardware independent software applications.
Interfaces
Major AUTOSAR Objectives

Architecture ❑ It defines file exchange formats and description


templates to enable a seamless configuration
process of the basic software stack.

❑ It also defines the integration of application


Acceptance
Methodology software in ECUs
Tests
❑ Moreover, It also includes the methodology how
to use this framework.
Application
Interfaces
Major AUTOSAR Objectives

❑ Specification of interfaces of typical automotive


Architecture application from all domains in terms of syntax
and semantics.

❑ Specification of interfaces should serve as a


standard for application software.
Acceptance
Methodology
Tests

Application
Interfaces
Major AUTOSAR Objectives

❑ The Acceptance Tests are the Specifications of


Architecture test cases intending to validate the behavior of an
AUTOSAR implementation with AUTOSAR
application software components or within one
vehicle network.

Acceptance Methodology
Tests

Application
Interfaces
➢ What is AUTOSAR?
01 ➢ AUTOSAR Objectives

INTRODUCTION ➢ Benefits of using AUTOSAR


➢ AUTOSAR architecture Vs Non AUTOSAR Architecture
TO AUTOSAR ➢ AUTOSAR Classic Vs AUTOSAR Adaptive
• Benefits of a Software Framework
• The AUTOSAR Software
Framework promotes software
module reuse and exchangeability.

• Benefits of the AUTOSAR Middleware


Approach
• AUTOSAR paves the way for innovative
electronic systems with improved performance,
safety and security.
• Hardware and software widely independent of each
other
• Decouplable development (by abstraction) through
horizontal layers; therefore, reduced development time
and costs
• Enhanced quality and efficiency through software
reuse
Benefits of Exploiting the Standard

Tool Provider New Market Entrance


OEM Supplier
Benefits of Exploiting the Standard

OEM Supplier Tool Provider New Market Entrant

• Establish distributed • Enhance efficient • Have an interface • Enable new business


development among variant handling with development models through
suppliers • Reuse software processes standardized
• Compete on modules across interfaces
innovative functions OEMs • Embed tools into an
with increased • Increase efficiency overall tool • Understand easily
design flexibility of application environment how automotive
• Simplify software development software is
and system • Invent new business developed
integration models
• Reduce overall
software
development costs
Benefits of Exploiting the Standard

OEM Supplier Tool Provider New Market Entrant

• Establish distributed • Enhance efficient • Have an interface • Enable new business


development among variant handling with development models through
suppliers • Reuse software processes standardized
• Compete on modules across interfaces
innovative functions OEMs • Embed tools into an
with increased • Increase efficiency overall tool • Understand easily
design flexibility of application environment how automotive
• Simplify software development software is
and system • Invent new business developed
integration models
• Reduce overall
software
development costs
Benefits of Exploiting the Standard

OEM Supplier Tool Provider New Market Entrant

• Establish distributed • Enhance efficient • Have an interface • Enable new business


development among variant handling with development models through
suppliers • Reuse software processes standardized
• Compete on modules across interfaces
innovative functions OEMs • Embed tools into an
with increased • Increase efficiency overall tool • Understand easily
design flexibility of application environment how automotive
• Simplify software development software is
and system • Invent new business developed
integration models
• Reduce overall
software
development costs
Benefits of Exploiting the Standard

OEM Supplier Tool Provider New Market Entrant

• Establish distributed • Enhance efficient • Have an interface • Enable new business


development among variant handling with development models through
suppliers • Reuse software processes standardized
• Compete on modules across interfaces
innovative functions OEMs • Embed tools into an
with increased • Increase efficiency overall tool • Understand easily
design flexibility of application environment how automotive
• Simplify software development software is
and system • Invent new business developed
integration models
• Reduce overall
software
development costs
➢ What is AUTOSAR?
01 ➢ AUTOSAR Objectives

INTRODUCTION ➢ Benefits of using AUTOSAR


➢ AUTOSAR architecture Vs Non AUTOSAR Architecture
TO AUTOSAR ➢ AUTOSAR Classic Vs AUTOSAR Adaptive
AUTOSAR architecture Vs Non AUTOSAR Architecture

Non AUTOSAR Architecture AUTOSAR Architecture

Application

OS HAL

Device Drivers

Microcontroller
➢ What is AUTOSAR?
01 ➢ AUTOSAR Objectives

INTRODUCTION ➢ Benefits of using AUTOSAR


➢ AUTOSAR architecture Vs Non AUTOSAR Architecture
TO AUTOSAR ➢ AUTOSAR Platforms
Four Pillars Form the

The AUTOSAR Platforms Standard Solution for


Today´s Automobiles

Reat Time Safety Computing


Platform Req. Critical Power

High (Micro-
High (up to Low (~1000
Classic Second
ASIL-D) DMIPs)
Range)

High (At Three Pillars for


Mid (Milli- High (> 20.0
Adaptive Sec Range)
Least ASIL-
DMIPs) ADAS Applications
B)

Collaboration
Low
(e.g. (Seconds)
QM ~10.0 DMIPs
Infotainment)
Thank You

You might also like