AUTOSAR Training

Lesson 1 • Key AUTOSAR Concepts and Terminology

Defines core vocabulary including SWC, port, interface, and composition. Precise terminology is required to read AUTOSAR specifications and tooling.

Lesson 2 • AUTOSAR Classic Platform Overview

Introduces the layered Classic Platform stack from hardware to application. Provides the structural map students reference throughout the course.

Lesson 3 • AUTOSAR Adaptive Platform Overview

Presents the service-oriented Adaptive Platform designed for high-compute ECUs. Contrasts with Classic Platform to clarify when each is appropriate.

Lesson 1 • AUTOSAR Schema and ARXML Structure

Teaches the XML schema that governs all AUTOSAR configuration files. Students gain ability to read, validate, and navigate ARXML documents.

Lesson 2 • Roles and Responsibilities in AUTOSAR Projects

Defines OEM, Tier-1 supplier, and tool vendor responsibilities within the methodology. Clarifies ownership of each ARXML artifact type.

Lesson 3 • Three-Phase AUTOSAR Methodology

Explains system design, ECU mapping, and ECU integration phases in sequence. Grounds all later tool and configuration work in a process framework.

Lesson 1 • SWC Composition and System Assembly

Assembles individual SWCs into compositions and connects ports via connectors. Composition modelling is the bridge between component design and system design.

Lesson 2 • Data Types and Data Constraints

Defines AUTOSAR primitive, composite, and implementation data types with constraints. Consistent data typing prevents integration errors across SWC boundaries.

Lesson 3 • Internal Behaviour and Runnable Design

Models runnables, inter-runnable variables, and exclusive areas within an SWC. Internal behaviour specification drives OS task mapping and scheduling.

Lesson 4 • Port and Interface Design

Covers sender-receiver, client-server, and parameter interfaces with their port variants. Port design directly controls data flow and service access patterns.

Lesson 1 • Mapping SWCs to ECU Resources

Assigns SWC instances to ECUs and maps runnables to OS tasks and alarms. Mapping decisions directly affect CPU load and scheduling behaviour.

Lesson 2 • RTE Generation and Validation

Runs the RTE generator, interprets output, and validates generated code. Validation catches mapping errors before BSW integration begins.

Lesson 3 • Sender-Receiver Communication via RTE

Configures queued and non-queued sender-receiver communication through the RTE. Correct configuration prevents data loss and race conditions.

Lesson 4 • RTE Architecture and Responsibilities

Explains how the RTE mediates between SWCs and the BSW communication stack. Understanding RTE scope prevents misuse of direct BSW API calls.

Lesson 1 • OS Module Configuration

Configures AUTOSAR OS tasks, alarms, resources, and ISRs for the target ECU. OS configuration directly determines scheduling correctness and timing behaviour.

Lesson 2 • NvM and Memory Stack Configuration

Configures NvM, MemIf, Fee, and Ea for non-volatile data management. Correct NvM configuration ensures data integrity across power cycles.

Lesson 3 • Communication Stack Configuration

Configures Com, PduR, CanIf, and Can modules for CAN-based communication. The communication stack carries all inter-ECU signals and diagnostics.

Lesson 4 • MCAL Module Configuration

Configures Port, Dio, Adc, Pwm, and Spi MCAL drivers for target hardware. MCAL is the hardware-specific foundation all upper layers depend on.

Lesson 1 • Diagnostic Event Manager Configuration

Configures Dem for fault storage, DTC management, and event debouncing. Dem feeds Dcm with fault data required for regulatory compliance.

Lesson 2 • Transport Protocol Layer Configuration

Configures CanTp and LinTp for segmented diagnostic message transport. Transport layer correctness is prerequisite for reliable Dcm operation.

Lesson 3 • Ethernet and SOME/IP Stack Overview

Introduces EthIf, SoAd, and SD modules for Ethernet-based service communication. Ethernet stacks are increasingly required for gateway and ADAS ECUs.

Lesson 4 • Diagnostic Communication Manager Configuration

Configures Dcm for UDS service handling, session control, and security access. Dcm is the gateway for all tester-to-ECU diagnostic interactions.

Lesson 1 • ara::com Service-Oriented Communication

Implements publish-subscribe and request-response patterns using ara::com APIs. ara::com is the primary inter-application communication mechanism in Adaptive.

Lesson 2 • Execution Management and Application Lifecycle

Configures Execution Management manifests and implements state machine transitions. Correct lifecycle management prevents resource conflicts between Adaptive applications.

Lesson 3 • Adaptive Platform Architecture Details

Examines the Adaptive Platform functional clusters and their interdependencies. Architectural clarity is required before configuring any Adaptive service.

Lesson 4 • Adaptive Platform Integration and Testing

Integrates multiple Adaptive applications and validates inter-service communication. Integration testing confirms manifest consistency and runtime behaviour.

Lesson 1 • Calibration and Post-Build Configuration

Configures AUTOSAR parameter components and integrates calibration data management. Post-build parameters allow field tuning without ECU reflashing.

Lesson 2 • Unit and Integration Testing Strategies

Designs unit tests for runnables and integration tests for BSW-SWC interactions. Structured testing reduces regression risk during iterative development.

Lesson 3 • Static Analysis and Code Quality

Applies MISRA-C rules and AUTOSAR C++ guidelines to generated and handwritten code. Static analysis catches defects before expensive hardware testing.

Lesson 4 • ECU Integration Build Process

Assembles generated BSW, RTE, and SWC code into a linked ECU binary. Build process mastery prevents integration failures caused by linker and memory errors.