AUTOSAR Basic Software - A Training Course

Day 1: Introduction & AUTOSAR Architecture Overview

• Overview of the AUTOSAR Classic Platform.
• Exploring software layers and ECU architecture.
• Examining the role of Basic Software (BSW) within the layered architecture.
• Insights into the Microcontroller Abstraction Layer (MCAL).
• Introduction to AUTOSAR configuration methodologies and XML-based workflows.
• High-level overview of ETAS ISOLAR-A/B.

Day 2: Services and ECU Abstraction Layers

• Summary of the Service Layer.
• Watchdog Manager (WdgM) functionalities.
• Diagnostic Event Manager (DEM) operations.
• NVRAM Manager (NvM) mechanisms.
• Detailed look at the ECU Abstraction Layer.
• I/O hardware interface management.
• Abstraction of communication and memory resources.
• Fundamentals 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 concepts: tasks, scheduling, and events.
• Understanding the RTE (Runtime Environment).
• The role of the RTE in integrating application software with BSW.
• The process of RTE generation.

Day 4: System Integration & Configuration Practice

• In-depth usage of configuration tools, specifically ETAS ISOLAR-A and B.
• Workflow for system configuration and integration.
• Integrating application software components (SWCs).
• Techniques for debugging and resolving integration challenges.
• Best practices and standard workflows for AUTOSAR projects.

Mandatory Setup Requirements (to be confirmed):

Software:

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

Hardware (for onsite or hybrid formats):

• Evaluation board (e.g., Infineon TriCore AURIX or NXP S32K).
• Debugger (Lauterbach, iSYSTEM, or PEmicro).
• CAN interface (USB-to-CAN if simulating a physical bus).