AUTOSAR

AUTOSAR (AUTomotive Open System ARchitecture) is a global development partnership comprising automotive manufacturers, suppliers, and service and technology providers. Its purpose is to facilitate the software development processes of electronic control units (ECUs) in modern vehicles by defining an open and standardized software architecture.

In today’s automotive industry, software complexity has significantly increased due to advanced driver assistance systems (ADAS), autonomous functions, electric powertrains, over-the-air (OTA) updates, and connected vehicle technologies. AUTOSAR was developed to manage this complexity, ensure separation between software and hardware, and simplify the integration of components from different suppliers.

Purpose and Importance

The motivations behind AUTOSAR’s creation include:

• Increasing the reusability of software components
• Ensuring interoperability between components from different manufacturers and suppliers
• Compliance with functional safety (ISO 26262) and cybersecurity standards
• Reducing development costs and time-to-market
• Providing portability and scalability through software-hardware separation
• Supporting the infrastructure of software-defined vehicles (SDVs)

AUTOSAR Architecture

AUTOSAR is built on a layered architecture that separates software from hardware.

Layers

1. Application Layer: Composed of software components that define vehicle functions.
2. Runtime Environment (RTE): Acts as a communication bridge between application components and basic software.
3. Basic Software (BSW): Provides standardized services for memory, communication, diagnostics, and I/O operations.
4. ECU Abstraction Layer: Hides hardware-dependent functions to enable upper layers to operate independently of the underlying hardware.
5. Microcontroller Abstraction Layer (MCAL): Abstracts hardware drivers to ensure software portability across different microcontrollers.

Thanks to this architecture, a software component can be executed on different hardware platforms with minimal modifications.

AUTOSAR Platforms

Classic Platform (Classic Platform - CP)

• Designed for real-time and resource-constrained ECUs.
• Used in areas such as braking, engine control, body electronics, and safety systems.
• Based on the OSEK/VDX real-time operating system.
• Operates with a static configuration approach.

AUTOSAR Classic Platform - Simplified Software Layer Architecture (Generated by Artificial Intelligence.)

Adaptive Platform (Adaptive Platform - AP)

• Developed for modern applications requiring high computational power.
• Compatible with autonomous driving, OTA updates, and cloud-based services.
• Runs on POSIX-based operating systems (e.g., Linux, QNX).
• Offers dynamic deployment, service-oriented architecture (SOA), and advanced cybersecurity features.

Although both platforms serve different use cases, their shared goal is modularity and standardization in automotive software.

AUTOSAR Adaptive Platform - Simplified Software Layer Architecture (Generated by Artificial Intelligence.)

Tools and Ecosystem

Key toolchains used in the AUTOSAR development process:

• Vector DaVinci Developer / Configurator – Design of software components and basic software modules
• Elektrobit EB Tresos Studio – Basic software configuration
• Dassault AUTOSAR Builder – Model-based development
• Visure Requirements ALM – Requirements management, traceability, and ISO 26262 compliance

This ecosystem facilitates collaboration between manufacturers and suppliers.

Functional Safety and Application Areas

AUTOSAR is designed to comply with the ISO 26262 functional safety standard. It supports secure communication, isolation of software components, and traceability in critical applications.

Main application areas include:

• Safety-critical systems (ABS, airbags, steering)
• Autonomous driving functions
• Electric vehicle battery management systems
• OTA updates and vehicle-to-everything communication (V2X)