AUTOSAR Basic Software - A Training Course

Day 1: Introduction & AUTOSAR Architecture Overview

• Fundamental concepts of the AUTOSAR Classic Platform.
• Examination of software layers and ECU architectural designs.
• Exploring the significance of Basic Software (BSW) within the layered model.
• Detailed look at the Microcontroller Abstraction Layer (MCAL).
• Introduction to AUTOSAR configuration methodologies and the XML-based workflow.
• Overview of the ETAS ISOLAR-A/B toolset.

Day 2: Services and ECU Abstraction Layers

• Overview of the Service Layer components.
• Managing system health via the Watchdog Manager (WdgM).
• Handling fault logging with the Diagnostic Event Manager (DEM).
• Controlling non-volatile memory using the NVRAM Manager (NvM).
• Understanding the ECU Abstraction Layer.
• Integration of I/O hardware interfaces.
• Abstraction mechanisms for communication and memory management.
• Core concepts of the OS and memory operating modes.

Day 3: Communication Stack and Runtime Environment

• Basics of the COM Stack, including PDUR, COM, and CAN/LIN drivers.
• AUTOSAR OS functionalities: task management, scheduling, and event handling.
• In-depth analysis of the RTE (Runtime Environment).
• The critical role of RTE in bridging application software and BSW.
• Processes involved in RTE generation.

Day 4: System Integration & Configuration Practice

• Detailed application of configuration tools, specifically ETAS ISOLAR-A and B.
• Workflow for system configuration and integration.
• Integrating application software components (SWCs) into the system.
• Techniques for debugging and resolving integration challenges.
• Best practices for managing the AUTOSAR project lifecycle.

Setup requirements (verification required):

Software Environment:

• ETAS ISOLAR-A and/or ISOLAR-B (latest version).
• Appropriate AUTOSAR schema (e.g., 4.2.x or 4.3.x, aligned with project needs).
• Compiler toolchain for code generation simulation (e.g., GNU ARM or IAR).
• Demo BSW project provided by ETAS or a custom setup.
• XML/XSD validation tools (optional).

Hardware Setup (for onsite or hybrid formats):

• Evaluation board (e.g., Infineon TriCore AURIX or NXP S32K).
• Debugger unit (Lauterbach, iSYSTEM, or PEmicro).
• CAN interface hardware (USB-to-CAN adapter for simulated physical buses).