AUTOSAR Classic Platform Guide by Piest Systems

WWW.PIESTSYSTEMS.COM
AUTOSAR Classic Platform Guide

AUTOSAR CLASSIC PLATFORM
The AUTOSAR Classic Platform architecture is structured into three main software layers running on a
microcontroller: the application layer, runtime environment (RTE), and basic software (BSW).
Application Layer: Largely hardware-independent, this layer contains software components that implement the
system's functionality.
Runtime Environment (RTE): Acts as the complete interface between the application software and the
underlying BSW, facilitating communication between software components and providing access to the basic
software.
Basic Software (BSW): This layer is further divided into three major sub-layers and complex drivers:
Services: Provide essential infrastructure for system management, memory handling, and communication
services.
ECU Abstraction: Isolates hardware dependencies, allowing the software to interact with the electronic
control unit (ECU) in a hardware-independent manner.
Microcontroller Abstraction: Handles low-level control of the microcontroller, ensuring consistent access to
the hardware.

AUTOSAR ARCHITECTURE
The core idea behind the standardized ECU software architecture is the clear separation between hardware-
independent application software and hardware-dependent basic software (BSW), facilitated by the runtime
environment (RTE) acting as a software abstraction layer. This abstraction layer, positioned between the
application and basic software, allows OEM-specific and competitive software applications to be developed on the
upper side, while ensuring standardization and OEM-independence for basic software on the lower side.
Key features of the AUTOSAR software architecture include its scalability, allowing the ECU software to adapt
across various vehicle models and variants, the ability to distribute functional software modules (applications)
across different ECUs, and the seamless integration of software modules from different providers.
The basic software within the AUTOSAR architecture is further categorized into layers such as services, ECU
abstraction, and microcontroller abstraction. The RTE manages the data exchange between these layers and the
application layer, enabling a component-oriented, hardware-independent software structure. This approach allows
software components (SWCs) to be developed without needing specific hardware knowledge, and provides
flexibility to relocate SWCs across different ECUs during the development process.

METHODOLOGY AND
TEMPLATES
AUTOSAR not only introduces a standardized software architecture but also a harmonized methodology for
developing automotive software. This methodology is designed to enhance collaboration among the various
stakeholders involved in modern automotive projects.
AUTOSAR provides a framework for specifying all the necessary elements to integrate software components on an
ECU and link multiple ECUs through different bus systems within a network. The methodology outlines the
relationships between activities and work products, supporting the various tasks, descriptions, and tool usage in
the AUTOSAR environment.
The descriptions, stored in .arxml files, follow AUTOSAR Templates, which define both the formal exchange format
(AUTOSAR Schema) and the associated semantic constraints. These descriptions contain the information
generated or utilized within the AUTOSAR methodology. Various generators use this information to configure and
create the Runtime Environment (RTE) and AUTOSAR basic software, including the operating system.

APPLICATION LAYER
The AUTOSAR Application Layer is one of the core layers in the AUTOSAR software architecture. It is where the
application-specific software components are developed, and it provides the necessary abstraction from the
underlying hardware and middleware. This layer allows developers to focus on the functionality of the application
without needing to worry about the details of hardware or basic system software.

RUN TIME ENVIRONMENT
The AUTOSAR Runtime Environment (RTE) is a critical part of the AUTOSAR architecture, acting as a
middleware layer that enables communication between software components (SWCs) and the underlying basic
software (BSW) or microcontroller abstraction layer (MCAL). Its main purpose is to facilitate the seamless
integration of software components across Electronic Control Units (ECUs), ensuring that different components
can interact with each other and with hardware in a standardized way.

SYSTEM SERVICES
AUTOSAR System Services refer to a set of foundational services provided by the AUTOSAR Basic Software
(BSW) that facilitate the efficient management and operation of ECUs (Electronic Control Units) in an
automotive system. These services play a crucial role in ensuring the proper functioning of the entire AUTOSAR
architecture, offering key functionalities such as memory management, communication, diagnostic services,
and more.

MEMORY SERVICES
AUTOSAR Memory Services are a key component of the AUTOSAR architecture, providing standardized
interfaces and services for managing memory in automotive embedded systems. These services ensure the
safe and efficient storage, retrieval, and management of data across various memory types in Electronic
Control Units (ECUs), such as flash memory, RAM, and EEPROM.

CRYPTO SERVICES
AUTOSAR Crypto Services are part of the AUTOSAR standard designed to provide cryptographic functionalities
essential for secure communication, data integrity, and authentication in automotive systems. With the
increasing complexity of automotive networks and the growing need for cybersecurity, AUTOSAR introduced
crypto services as part of its standard to ensure that electronic control units (ECUs) can securely communicate
and handle sensitive data.

OFF BOARD COMMUNICATION
SERVICES
AUTOSAR (Automotive Open System Architecture) defines off-board communication services as part of its
broader framework for vehicle communication and software architecture. These services facilitate interaction
between the vehicle's on-board systems and external entities, such as diagnostic tools, service centers, or
cloud-based systems.

COMMUNICATION SERVICES
AUTOSAR communication services provide a standardized way for software components within an Electronic
Control Unit (ECU) and between ECUs to communicate over a network. These services are part of the AUTOSAR
Basic Software (BSW) layer and facilitate the seamless exchange of data across different bus systems. The
communication services abstract the complexities of underlying hardware and network protocols, making it
easier for developers to design and implement automotive applications.

ONBOARD DEVICE ABSTRACTION
AUTOSAR Onboard Device Abstraction (ODA) is a layer within the AUTOSAR architecture that enables hardware
independence by abstracting device-specific details from the application layer. This abstraction allows for
seamless integration of hardware and software components across different ECUs without requiring
modifications to the application code when the hardware changes.

MEMORY HARDWARE ABSTRACTION
AUTOSAR's Memory Hardware Abstraction (MemHwAb) is a crucial layer within the AUTOSAR architecture that
provides an abstraction of the memory hardware for automotive applications. This layer allows the software
components to access memory devices in a hardware-independent way, promoting portability and scalability
across different ECUs.

CRYPTO HARDWARE ABSTRACTION
The AUTOSAR Crypto Hardware Abstraction (Crypto HSM) is a part of the AUTOSAR Classic Platform and
provides an abstraction layer for cryptographic operations that are performed in hardware. It is designed to
ensure that software components can access cryptographic functionalities independently of the underlying
hardware, enabling portability and flexibility across different ECUs.

WIRELESS COMMUNICATION
HARDWARE ABSTRACTION
The AUTOSAR Crypto Hardware Abstraction (Crypto HSM) is a part of the AUTOSAR Classic Platform and
provides an abstraction layer for cryptographic operations that are performed in hardware. It is designed to
ensure that software components can access cryptographic functionalities independently of the underlying
hardware, enabling portability and flexibility across different ECUs.

COMMUNICATION HARDWARE
ABSTRACTION
Communication hardware abstraction in AUTOSAR refers to a layer within the architecture that isolates the
application software from the specific details of the underlying hardware. This allows the software components
to communicate across various hardware platforms without requiring hardware-specific modifications.

I/O (INPUT/OUTPUT) HARDWARE
ABSTRACTION
I/O (Input/Output) hardware abstraction is a key concept in embedded systems, especially in standards like
AUTOSAR, where it provides a layer of separation between the hardware and software.
The purpose of I/O hardware abstraction is to decouple the application software from the specific details of the
hardware, such as microcontrollers or peripherals. This allows for easier portability of software across different
hardware platforms. The abstraction layer manages the communication between the software and the hardware
by providing standardized interfaces and services.

MICROCONTROLLER DRIVERS
AUTOSAR Microcontroller Drivers, part of the AUTOSAR Basic Software (BSW) layer, are responsible for
abstracting the hardware-specific details of a microcontroller unit (MCU) and providing a standardized interface
for higher-level software modules. This abstraction simplifies the development process by allowing software
components to interact with the microcontroller hardware without worrying about its specific implementation.

MEMORY DRIVERS
AUTOSAR memory drivers are part of the AUTOSAR Basic Software (BSW) layer and handle the management
and operation of memory devices in automotive systems. These drivers abstract the hardware-specific details,
allowing higher software layers to interact with different types of memory (like EEPROM, Flash, RAM, etc.) in a
standardized way.

CRYPTO DRIVERS
AUTOSAR Crypto Drivers are integral components in the AUTOSAR (Automotive Open System Architecture)
framework, designed to handle cryptographic operations within automotive systems. They provide secure
communication and data protection by implementing encryption, decryption, and other cryptographic functions
necessary for automotive applications.

WIRELESS COMMUNICATION DRIVERS
AUTOSAR (Automotive Open System Architecture) includes specifications for various communication protocols
and services, including those for wireless communication. While the AUTOSAR standard primarily focuses on
in-vehicle communication technologies such as CAN, LIN, and Ethernet, there is increasing interest in
integrating wireless communication methods due to their potential to enhance vehicle connectivity and
functionality.

COMMUNICATION DRIVERS
AUTOSAR communication drivers are essential components within the AUTOSAR framework, responsible for
managing communication between software components and ECUs (Electronic Control Units) over different bus
systems. They ensure reliable data exchange and support various communication protocols. Here’s an overview
of the key AUTOSAR communication drivers:

I/O (INPUT/OUTPUT) DRIVERS
AUTOSAR I/O drivers, also known as AUTOSAR I/O Services, are a critical component in the AUTOSAR
architecture, handling the communication between software components and the hardware interfaces of an
ECU (Electronic Control Unit).

COMPLEX DRIVERS
AUTOSAR I/O drivers, also known as AUTOSAR I/O Services, are a critical component in the AUTOSAR
architecture, handling the communication between software components and the hardware interfaces of an
ECU (Electronic Control Unit).

MICROCONTROLLER
In the AUTOSAR framework, the microcontroller plays a crucial role as a foundational hardware component for
embedded automotive systems. Here’s a summary of its significance and role:
Microcontroller Integration: AUTOSAR provides guidelines for integrating microcontrollers into automotive
ECUs (Electronic Control Units). It defines how software components interact with the microcontroller
hardware, ensuring consistency and compatibility across different platforms.
1.
Microcontroller Abstraction: The AUTOSAR standard includes the Microcontroller Abstraction Layer
(MCAL), which abstracts the microcontroller hardware details from the higher layers of software. This
allows developers to write software that is independent of the specific microcontroller used, facilitating
easier adaptation to different hardware.
2.
Configuration and Calibration: AUTOSAR defines tools and methods for configuring and calibrating
microcontroller-related parameters, such as I/O ports, timers, and communication interfaces. This ensures
that the microcontroller’s capabilities are used efficiently and correctly.
3.
Interfacing with Other ECUs: The AUTOSAR standard specifies how microcontrollers in different ECUs
should communicate with each other over various bus systems (e.g., CAN, LIN, FlexRay, Ethernet). This
ensures interoperability and reliable communication within the vehicle’s network.
4.
Supporting Software Layers: The microcontroller supports various AUTOSAR software layers, including the
Basic Software (BSW), which includes drivers and services that interact directly with the microcontroller
hardware. The Basic Software provides essential functionalities such as memory management,
communication, and diagnostics.
5.
By providing a structured approach to integrating and utilizing microcontrollers, AUTOSAR enhances the
development process, improves software portability, and ensures consistent performance across different
automotive platforms.

MICROCONTROLLER

+91-9071123555
info@piestsystems.com
JOIN NOW
Don't Hesitate to Reach Out!
Call or WhatsApp Us for More
Information

AUTOSAR Classic Platform Guide by Piest Systems

More Related Content

Similar to AUTOSAR Classic Platform Guide by Piest Systems

More from PiestSystems

Recently uploaded

AUTOSAR Classic Platform Guide by Piest Systems