| Artifact | Direction | Contains |
|---|---|---|
| System Description ARXML | OEM → Tier-1 | Full vehicle SW architecture, all ECU instances, signal routing |
| ECU Extract ARXML | OEM → Tier-1 (per ECU) | Single ECU subset — SWC ports, COM signals, bus assignment |
| SWC ARXML | OEM → Tier-1 | Behavioural description of each OEM-developed SWC |
| BSW Integration Spec | OEM → Tier-1 | Target MCU, AUTOSAR release, memory map, OS task structure |
OEM–Tier-1 Handover Artifacts
Three Development Phases
AUTOSAR CP Development Phases
Phase 1: Architecture Design (OEM)
├── Define SWC composition in SystemDesk
├── Define bus topology (CAN/LIN/FlexRay databases)
└── Generate ECU Extracts per ECU
Phase 2: BSW Configuration (Tier-1)
├── Import ECU Extract into DaVinci/tresos
├── Configure COM signals, PDU routing, MCAL params
├── Configure DCM sessions/DIDs, DEM events, NvM blocks
└── Generate BSW + RTE code
Phase 3: SWC Implementation (OEM / Tier-1)
├── Implement runnable bodies against generated Rte_.h
├── Unit test with RTE stub replacements
└── Integrate and test on target ECU Toolchain Role Split
| Tool | Vendor | Phase | Role |
|---|---|---|---|
| SystemDesk | dSPACE | Phase 1 | System-level ARXML authoring, ECU Extract generation |
| DaVinci Developer | Vector | Phase 2–3 | SWC ARXML authoring, RTE code generation |
| DaVinci Configurator Pro | Vector | Phase 2 | BSW module configuration and validation |
| ISOLAR-AB / ISOLAR-EVE | EB | Phase 1–2 | System design + ECU configuration (Elektrobit projects) |
| tresos Studio | EB | Phase 2 | BSW-only ECU configuration (alternative to DaVinci) |
AUTOSAR CP Version Mismatch
| Symptom | Root Cause | Fix |
|---|---|---|
| Schema validation error on import | ECU Extract ARXML is R4.2; tool expects R4.4 | Migrate ARXML with schema migration scripts |
| RTE gen: unknown port prototype | New R4.4 attribute not in R4.2 SWC ARXML | Add missing attribute with default value |
| BSW module: parameter not found | BSWMD is R4.4; config was R4.2 param names | Update parameter names per BSW supplier delta doc |
Summary
AUTOSAR CP methodology is a contractual as much as a technical process. The ECU Extract and SWC ARXML handover documents are the contractual interface between OEM and Tier-1. Version alignment and artifact traceability are the two pillars of a stable integration workflow.
🔬 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.