Shankar MOORTHY

https://www.linkedin.com/in/shankar-moorthy-88683475/

AUTOSAR

CONTENTS:

1. what is AUTOSAR?

2. Key Features of AUTOSAR

3. Different layers of AUTOSAR

4. Application Layer

4.1. Autosar application SWC - Software components

4.2. Design and communication of Software components

5. Basic Software Layer

5.1. Service Layer

5.2. ECU Abstraction Layer

5.3. Microcontroller Abstraction Layer

5.4. Complex drivers

1.what is AUTOSAR?

AUTOSAR (AUTomotive Open System ARchitecture) is an open and standardized

automotive software architecture, jointly developed by automobile manufacturers,
suppliers and tool developers.

2.KEY FEATURES:

–Exchangeability and Integration of functions between carmakers and ECU

suppliers.

–Increased scope of automatic code generation and configuration.

 – Implementation and standardization of Software architecture and basic functions.

• Defined methodology. It’s a Software tool-driven approach :

• Architecture Authoring Tools.
• Configuration Tools.
• Code Generation Tools.

• AUTOSAR provides a common software infrastructure for automotive systems

based on a

–Standardized architecture.

–Application Interface.

–Defined methodology.

• AUTOSAR requires a complete, exact definition of the entire SW Architecture,

including :
• Hundreds of SW Components.
• Thousands of ports and interfaces.
• Hundreds of data types, ranges.
• Complete interconnection of SW Components.
• Configuration of Real-Time Operating System.
• Configuration of the Basic SW.

• It facilitates the reuse of SW components across different applications and

different ECUs.
• It increases the scope and amount of automatic code generation, from
application components only to interconnection generation, operating system,
communication, and basic SW configuration

3.DIFFERENT LAYERS OF AUTOSAR:

 The following diagram depicts the basic autosar architecture which
contains 3 basic layers which relies on the hardware microcontroller are: Application
Layer, RTE(Run Time Environment) Layer and BSW(Basic Software) Layer.

Application Layer:

The application layer contains the SWCs (software components), which realize
the application functionality of the ECU's mainly the sensor SWC components.

RTE(Run Time Environment) Layer:

The RTE layer intergrates the SWCs with BSW layer. It implements the data
exchange and controls the integration between the application software
components(SWCs) and the BSW.

BSW(Basic Software) Layer:

The basic software layer contains three sub layers: Service layer, ECU Abstraction
layer and Microcontroller Abstraction Layer.

Service layer - It provides various services such as vehicle network

communication, management service, diagnostics services, memory
management, ECU state management, mode management and Logical and
temporal flow monitoring.

ECU Abstraction layer - It contains the drivers for external peripheral

components which offers uniform communication to all features of an ECU
communication, memory or I/O irrespective of these services are as part of
microcontroller or realized by the peripheral components.
 Microcontroller Abstraction Layer - It contains internal drivers with direct
access to microcontroller and internal peripherals.

4. APPLICATION LAYER:

The application layer contains the SWCs (software components), which realize
the application functionality of the ECU's mainly the sensor SWC components.

AUTOSAR standard specifies the application layer implementation using

"component" concept.

4.1 Autosar application SWC - Software components:

These software components implementation is defined as runnable entities.

• Application is divided into SW-Cs.

• Software Components consist of
• 1.Ports - Interface to other SW-Cs
• 2.Runnable Entities (or Runnables) - Procedures which contain the actual
implementation.

4.2. Design and communication of Software components:

The fundamental design concept of the AUTOSAR is the communication or

interface between the application and the Infrastructure or how the ECU functionality is
implemented by means of open software architecture which contains different software
layers and how the communication and the interface takes place between the SWCs of
the AUTOSAR layer.

The application of the AUTOSAR consists of "Interconnected software components"

and the communication between the software components mainly takes place by means
of two ports.

Client / server port - Server is the provider of the service requested and Client is
the user of the service.

Sender / Receiver port - Sender sends the requested information to one or more
receiver and receiver receives the information in synchronous as well as asynchronous
environment.
 During the design phase the SWCs can be integrated with their environment like OS,
driver, hardware etc.., based on VFB - Virtual Function bus. VFB is the abstraction of
the Autosar SWC interconnections of the entire vehicle. After the deployment of SWC in
the vehicle network architecture , the communication between the SWCs of the RTE
and BSW of the ECU's is by ECU local communication or as network based
communication as shown below.

5. Basic Software Layer:

Autosar has defined set of BSW modules. They are responsible for different
tasks such as:

• Operating system service

• Accessing to non volatile memory
• Communication via CAN, LIN, Flexray and ethernet
• Handling of diagnostics
• Access to I/O ports
• System services like ECU state management, Diagonostic event manager etc..,

These tasks are handled by three different sub layers in AUTOSAR: Service layer,
ECU Abstraction layer and Microcontroller Abstraction Layer.

In addition, complex drivers can be integrated into AUTOSAR ECU. They are used to
access the features of ECU which is not covered by the standard BSW of the
AUTOSAR.It offers the functionality such as drivers for autosar external drivers, special
requirement for complex sensor and actuators.

It is further subdivided into following functional groups

5.1. Service Layer:

It provides various services such as vehicle network communication,

management service, diagnostics services, memory management, ECU state
management, mode management and Logical and temporal flow monitoring.
 It provides basic services for applications and basic software modules.

As per the image above, the service layer architecture includes three sub modules in it -
System services, Memory services and communication services.

System services:

It is the group of modules and functions which can be used by modules of all
layers. The functional sub layers of system services includes

• COM manager
• BSW mode manager
 • ECU state manager
• Diagnostic event manager

Memory Services:

It is responsible for non volatile data management like saving, loading, checksum,
protection and verification, reliable storage etc., It consists of only one module called

• NVRAM manager(NvM)

Communication services:

It interfaces the communication drivers via communication hardware abstraction .It

consists of group of modules for vehicle communication like

• CAN network manager

• CAN state manager
• CAN transport layer
• COM
• Ethernet state Manager
• Flexray autosar transport layer

5.2. ECU Abstraction Layer:

It contains the drivers for external peripheral components which offers uniform
communication to all features of an ECU communication, memory or I/O irrespective of
these services are as part of microcontroller or realized by the peripheral components. It
interfaces the drivers of the Microcontroller Abstraction Layer. It also contains drivers for
external devices. It offers an API for access to peripherals and devices regardless of
their location (µC ,internal/external) and their connection to the µC (port pins, type of
interface).
It is further sub divided into onboard device abstraction, memory hardware abstraction,
communication hardware abstraction and I/O hardware abstraction layers as mentioned
in above functional architecture.

On-board device abstraction:

It contains drivers for ECU on board device mainly

• Watchdog Interface(WdgIf)

Memory hardware abstraction:

 It abstracts from location of peripheral memory devices and ECU hardware layout
and it consists of following sub modules

• Memory abstraction interface (MemIf)

• Flash EEPROM emulation (Fee)
• EEPROM abstraction(Ea)

Communication hardware abstraction:

It abstracts from the location of communication controllers and ECU hardware layout
and it consists of following sub modules

• CAN interface
• LIN interface
• Flexray interface
• TTCAN interface
• Ethernet Interface

I/O hardware abstraction:

It is the group of modules which abstracts from the location of peripheral I/O devices
and ECU layout. It consists of

• I/O signal interface

• Driver for external ADC ASIC
• Driver for external I/O ASIC

5.3. Microcontroller Abstraction Layer:

It is the lowest layer of BSW which contains device drivers. It contains internal
drivers with direct access to microcontroller and internal peripherals.
This MCAL layer is further sub divided into microcontroller drivers, memory drivers,
communication drivers, I/O drivers.

Microcontroller drivers:

It contains the drivers for internal peripherals functions with direct microcontroller
access. It consists of

• MCU driver
• Watchdog driver
• GPT driver
Memory drivers:

It consists of drivers for on chip memory devices and memory mapped external
memory devices. The sub modules are

• Internal EEPROM drivers

• Internal Flash drivers

Communication drivers:

It consists of drivers for ECU on board and vehicle communication. The sub
modules are

• Ethernet driver
• Flexray driver
• CAN driver
• LIN driver
• SPI handler driver

I/O drivers:

It consists of drivers for analog and digital I/O. The sub modules are

• PORT driver
• DIO driver
• ADC driver
• PWM driver
• ICU driver

5.4. Complex drivers:

The complex drivers can be integrated into AUTOSAR ECU. They are used to
access the features of ECU which is not covered by the standard BSW of the
AUTOSAR.It offers the functionality such as drivers for autosar external drivers, special
requirement for complex sensor and actuators. It provides the possibility to integrate
special purpose functionality which are not specified within AUTOSAR, with a very high
timing constraints or for migration purposes etc.,