AUTOSAR Layered Architecture Overview - AUTOSAR Classic BSW

AUTOSAR Three-Layer Model

AUTOSAR Classic Platform (CP) divides ECU software into three layers with strictly enforced dependency rules:

Layer	Contents	Key Rule
Application Layer	Atomic SWCs, Composition SWCs, Sensor/Actuator SWCs	Communicates exclusively via RTE ports — no direct BSW calls
RTE (Runtime Environment)	Generated glue code — Rte_Read/Write/Call/Result APIs	Decouples SWCs from each other and from BSW
BSW (Basic Software)	Services, ECU Abstraction, MCAL, Complex Drivers	Provides platform services to RTE and to other BSW modules

AUTOSAR CP Layer Stack

  ┌──────────────────────────────────────────────────────────┐
  │            Application Layer (SWCs)                       │
  │  WheelSpeedSWC   EngineCtrlSWC   DiagSWC   ...           │
  └─────────────────────────┬────────────────────────────────┘
                            │ Rte_Read / Rte_Write / Rte_Call
  ┌─────────────────────────▼────────────────────────────────┐
  │            RTE (Runtime Environment) — GENERATED         │
  └─────────────────────────┬────────────────────────────────┘
                            │ BSW module APIs
  ┌──────────┬──────────────▼──────────┬──────────────────────┐
  │ Services │  ECU Abstraction Layer  │  MCAL                │
  │ COM/NvM  │  CanIf / LinIf / PduR  │  CanDrv / SpiDrv /  │
  │ DCM/DEM  │  IoHwAb                │  AdcDrv / PwmDrv    │
  └──────────┴─────────────────────────┴──────────────────────┘
                            │ Register access
  ┌──────────────────────────────────────────────────────────┐
  │                   Microcontroller Hardware                │
  └──────────────────────────────────────────────────────────┘

BSW Cluster Structure

Cluster	Modules	Purpose
Services Layer	COM, PduR, NvM, DCM, DEM, FIM, EcuM, BswM, OS, SchM	ECU-independent services available to RTE and application
ECU Abstraction Layer	CanIf, LinIf, FrIf, SpiHandlerDriver, IoHwAb	Hardware-independent abstraction
MCAL	CanDrv, AdcDrv, PwmDrv, SpiDrv, FlsDrv, WdgDrv	Direct hardware access — microcontroller specific
Complex Drivers	Custom per-project sensor drivers	Hardware access not covered by standard MCAL

MCAL & ECU Abstraction Layer

MCAL Module	SWS Spec	Provides
CanDrv	SWS_CANDriver	CAN controller HW — Can_Write, Can_SetControllerMode
AdcDrv	SWS_ADCDriver	ADC conversion — Adc_StartGroupConversion, Adc_ReadGroup
PwmDrv	SWS_PWMDriver	PWM duty cycle — Pwm_SetDutyCycle
FlsDrv	SWS_FLASHDriver	Flash erase/program — Fls_Erase, Fls_Write
WdgDrv	SWS_WatchdogDriver	Watchdog trigger — Wdg_SetMode

Release History & Production Impact

Release	Year	Key Change
R3.2	2011	Stabilised — still common in powertrain ECUs
R4.0	2012	Multi-core OS, IOC, ASIL partitioning
R4.2	2014	Memory protection (OsApplication), AR4 NvM extensions
R4.4+	2016+	Improved ETH, updated MCAL SWS

⚠️ Version Lock-In

OEM SWC ARXML is typically locked to a specific AUTOSAR release. Mixing a Tier-1 BSW stack (e.g., R4.4) with OEM SWC ARXML for R4.2 causes RTE generation failures. Always confirm the AUTOSAR release version in the integration specification before starting.

Summary

The AUTOSAR CP layered architecture's primary goal is hardware independence through the MCAL and software reusability through standardised BSW APIs. Strict layer dependency rules — enforced by the RTE generator — prevent direct coupling between Application and BSW.

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.