AUTOSAR Basic Software - A Training Course

Day 1: Foundational Concepts and AUTOSAR Framework Analysis

• Fundamental principles of the AUTOSAR Classic Platform
• Hierarchical software structure and Electronic Control Unit (ECU) design standards
• Functional role of Basic Software (BSW) within the stratified model
• Microcontroller Abstraction Layer (MCAL) implementation details
• Standardization of configuration procedures and XML-based data flows
• Functional overview of ETAS ISOLAR-A/B tools for government applications

Day 2: Service Protocols and Abstraction Mechanisms

• Comprehensive review of the Service Layer
• Watchdog Manager (WdgM) operational specifications
• Diagnostic Event Manager (DEM) error handling protocols
• Non-Volatile RAM Manager (NvM) data persistence strategies
• ECU Abstraction Layer integration standards
• I/O hardware interface management
• Communication and memory abstraction techniques
• Operating System fundamentals and memory state control

Day 3: Communication Architecture and Runtime Operations

• Core COM Stack components: PDUR, COM, and CAN/LIN driver protocols
• AUTOSAR OS management: task allocation, scheduling algorithms, and event handling
• Runtime Environment (RTE) functional requirements
• Strategic role in bridging application software and BSW layers
• Procedural standards for RTE generation

Day 4: System Consolidation and Configuration Protocols

• Advanced utilization of ETAS ISOLAR-A and B for system configuration
• Standardized workflows for system setup and integration
• Incorporation of application software components (SWCs)
• Methodologies for resolving integration defects and troubleshooting
• Establishment of project workflows and best practices for government operations

Mandatory Infrastructure Verification:

Software Environment:

• ETAS ISOLAR-A and/or ISOLAR-B (current version required)
• Applicable AUTOSAR schema standards (e.g., 4.2.x or 4.3.x based on project scope)
• Compiler toolchain (e.g., GNU ARM or IAR for simulation purposes)
• ETAS-provided demo BSW project or equivalent custom setup
• XML/XSD validation utilities (where applicable)

Hardware Requirements (for onsite or hybrid environments):

• Evaluation platform (e.g., Infineon TriCore AURIX or NXP S32K)
• Debugging equipment (Lauterbach, iSYSTEM, or PEmicro)
• CAN interface hardware (USB-to-CAN for simulated bus environments)