| | |

AUTOSAR CLASSIC PLATFORM – INTRODUCTION

ByPrakash Shakti
AUTOSAR CLASSIC PLATFORM – INTRODUCTION
The AUTOSAR Classic Platform is a standardized software architecture for embedded ECUs in vehicles. It provides a structured, layered approach to develop, integrate and reuse software components, ensuring reliability, portability and scalability across different ECUs and suppliers.
Standardized
Reliable
Efficient Software Architecture
Key Benefits
  • Standardized, Modular, and Scalable Architecture
    AUTOSAR provides a common software architecture that enables modular development and supports systems ranging from simple ECUs to complex vehicle platforms.
  • High Reusability and Portability Across ECUs and Projects
    Software components are designed for reuse, reducing development time and allowing applications to be easily ported between different ECUs and vehicle programs.
  • Support for Real Time and Safety Critical Applications
    AUTOSAR is designed to support deterministic behavior and functional safety requirements for automotive systems such as braking, steering, and powertrain control.
  • Improved Quality, Maintainability, and Testability
    A standardized software structure simplifies development, testing, debugging, maintenance, and long term software evolution.
  • Independence from Hardware and Basic Software
    The layered architecture separates application software from hardware specific details, enabling easier hardware replacement and software portability.
  • Standardized by AUTOSAR for a Consistent Ecosystem
    AUTOSAR defines common interfaces, methodologies, and software standards, enabling interoperability between automotive manufacturers, suppliers, and development tools.
1. WHAT IS AUTOSAR CLASSIC PLATFORM?
  • Part of the AUTOSAR software ecosystem.
  • Targeted for resource constrained ECUs with real time and safety requirements.
  • Provides a standardized Basic Software (BSW) layer and Runtime Environment (RTE).
  • Application software is developed on top of the BSW using standard AUTOSAR interfaces.
  • Widely used in powertrain, chassis, body, and other embedded automotive ECUs.
AUTOSAR Software Ecosystem Application Software (Software Components) AUTOSAR Classic Platform (Basic Software) Microcontroller Hardware
2. LAYERED ARCHITECTURE
Application Layer
(Software Components)
Runtime Environment (RTE)
Basic Software (BSW)
Microcontroller Abstraction Layer (MCAL)
Microcontroller

Application Layer

Application logic is implemented as AUTOSAR Software Components (SWCs).

3. AUTOSAR CLASSIC PLATFORM ARCHITECTURE
Application Layer (SWCs)
Runtime Environment (RTE)
Basic Software (BSW)

System Services

  • ECU State Manager
  • BSW Mode Manager
  • Watchdog Manager
  • …

Memory Services

  • NVRAM Manager
  • Memory Manager
  • …

Communication Services

  • COM
  • PduR
  • …

I/O Hardware Abstraction

  • I/O Hardware Abstraction
  • Complex Drivers
  • …
Microcontroller Abstraction Layer (MCAL)
Microcontroller
Application Layer
RTE
BSW
MCAL
Hardware
4. BASIC SOFTWARE (BSW) MODULES
The Basic Software (BSW) layer consists of standardized modules that provide common services for the application software and hide hardware-specific details.
BSW Module Purpose
System Services Services for ECU management, state management, watchdog, timers, diagnostics, and other system functions.
Memory Services Management of non volatile memory, RAM, and memory abstraction services.
Communication Services Communication stack including COM, PduR, Transport Protocol (Tp), CAN Interface, LIN Interface, and related communication modules.
I/O Hardware Abstraction Provides abstraction and control of I/O hardware and complex devices, including drivers for sensors, actuators, and other peripherals.
5. RUNTIME ENVIRONMENT (RTE)
The Runtime Environment (RTE) acts as the communication layer between AUTOSAR Software Components (SWCs) and the Basic Software (BSW).
  • Provides communication between software components and the Basic Software (BSW).
  • Offers standardized communication ports such as Sender/Receiver, Client/Server, and Mode ports.
  • Enables timing management, data consistency, and execution control for software components.
  • Remains independent of the underlying Basic Software (BSW) implementation, improving software portability and reusability.
RTE Interaction Example SWC A (Sender) RTE SWC B (Receiver) BSW Services (e.g., COM, NvRAM)
6. COMMUNICATION STACK EXAMPLE
AUTOSAR Software Stack Application (SWC) RTE COM PduR CanTp CAN Interface CAN Driver AUTOSAR Software MCAL
7. SOFTWARE COMPONENT (SWC)
A Software Component (SWC) is the basic building block of application software in the AUTOSAR Classic Platform.
  • Basic unit of application software.
  • Encapsulates the application logic.
  • Interacts with other Software Components (SWCs) and the Basic Software (BSW) through the Runtime Environment (RTE).
  • Supports different types of communication ports, including Provided Ports (P-Port) and Required Ports (R-Port).
SWC Example SWC Provided Port Required Port
8. KEY FEATURES
  • Layered and Modular Architecture
    Organizes software into well-defined layers and modules, making development, maintenance, and integration easier.
  • Hardware Independence
    Separates application software from hardware-specific implementation, enabling software portability across different ECU platforms.
  • High Reusability and Portability
    Allows software components to be reused across multiple ECUs, vehicle platforms, and development projects.
  • Standardized Interfaces (RTE and BSW)
    Uses standardized interfaces between Software Components (SWCs), the Runtime Environment (RTE), and Basic Software (BSW) to ensure interoperability.
  • Real Time and Deterministic Behavior
    Supports predictable software execution required for time-critical automotive applications.
  • Scalable Across Different ECUs
    Supports a wide range of ECU types, from simple body controllers to complex powertrain and safety ECUs.
  • Supports Safety and Security Requirements
    Provides architectural support for developing applications that meet automotive functional safety and cybersecurity requirements.
  • Compliant with Automotive Standards
    Designed to work with industry standards such as ISO 26262 for functional safety and ISO 21434 for automotive cybersecurity.
  • Tool and Vendor Independence
    Promotes interoperability between development tools and software from different AUTOSAR-compliant vendors, reducing vendor lock-in.
9. TYPICAL APPLICATION AREAS
🚗
Powertrain
🛞
Chassis
🚙
Body & Comfort
🛞
ADAS / Safety
🔋
Energy Management
10. STANDARDS & REFERENCES
  • AUTOSAR Specifications
    Classic Platform Release (Latest Version)
  • ISO 26262
    Functional Safety for Road Vehicles
  • ISO 21434
    Road Vehicles Cybersecurity Engineering
  • OSEK/VDX
    Operating System specification that forms the basis of the AUTOSAR Operating System (AUTOSAR OS)
11. IN SUMMARY
The AUTOSAR Classic Platform provides a standardized, layered software architecture for embedded automotive ECUs.
It improves software quality, reusability, portability, and maintainability while supporting real time performance, functional safety, and cybersecurity requirements for modern vehicle applications.

Similar Posts