| Function Category | Platform | Rationale |
|---|---|---|
| ADAS: camera/radar fusion, path planning | Adaptive AP | Requires POSIX, ML inference (TensorFlow Lite), high compute, OTA update |
| Connectivity: V2X, remote diagnostics | Adaptive AP | Dynamic service discovery, SOME/IP-SD, TLS — not feasible on Classic CP |
| Powertrain: fuel injection, engine control | Classic CP | Hard real-time (µs deadlines), ASIL-D, direct MCAL access to injectors |
| Chassis: EPS, ABS, ESC | Classic CP | ASIL-D, deterministic latency, direct PWM/sensor MCAL |
| Body: door modules, lights | Classic CP | Low cost, ASIL-A, LIN bus, long production lifetime |
Domain Split: Adaptive for ADAS, Classic for Chassis
Zonal ECU Architecture
Zone Controller SoC: Classic + Adaptive Concurrent
Zone Controller ECU (e.g., NXP S32G3) ┌──────────────────────────────────────────────────────────┐ │ Cortex-R52 cores (2-4) Cortex-A53 cores (4) │ │ ┌────────────────────────┐ ┌───────────────────┐ │ │ │ AUTOSAR Classic CP │ │ AUTOSAR Adaptive │ │ │ │ Actuator control │ IPC │ Service broker │ │ │ │ CAN/LIN gateways │◄─────►│ OTA management │ │ │ │ Watchdog supervision │ │ SOME/IP services │ │ │ └────────────────────────┘ └───────────────────┘ │ │ │ │ │ │ CAN/LIN to zone devices Ethernet backbone to HPC │ └──────────────────────────────────────────────────────────┘
💡 Zone vs Domain Architecture
The industry is transitioning from domain ECUs (one ECU per function domain: body, chassis, powertrain) to zonal ECUs (one ECU per vehicle zone: front-left, rear, central). Zonal controllers consolidate multiple Classic CP functions (previously spread across 3–5 ECUs) onto one SoC, while also hosting Adaptive services for OTA and connectivity. This reduces wire harness length by 30–50% but significantly increases the integration complexity of each ECU.
Diagnostic Topology: Single DoIP Entry
DoIP Diagnostic Routing
Diagnostic Tester (CANoe / OBD tool)
│ UDS over DoIP (ISO 13400-2) — Ethernet
▼
Adaptive ECU: ara::diag DoIP server
ara::diag::DiagServer receives UDS request
│ Routing decision: which target ECU?
├──► Target=0x01 (self): Adaptive DCM handles locally
├──► Target=0x10 (Classic EPS ECU): forward via CAN UDS tunnel
│ ara::diag → CAN_DiagForwarder BSW SWC → CanTp → CAN bus → DCM on EPS ECU
└──► Target=0x20 (Classic Body ECU): forward via LIN diagnostic
ara::diag → LIN_DiagForwarder → LinTp → LIN bus → DCM on Body ECU| Routing Path | Protocol | Latency Overhead |
|---|---|---|
| DoIP tester → Adaptive DoIP server | Ethernet (100 Mbps) | <1 ms |
| Adaptive → Classic via CAN UDS tunnel | CanTp (500 kbps) | 5–15 ms per segment |
| Adaptive → Classic via LIN diagnostic | LinTp (20 kbps) | 20–50 ms per segment |
Security Boundary: TrustZone Partition
CCrypto_TrustZone.c
/* AUTOSAR Crypto stack uses Secure World key material */
/* Classic CP runs in Normal World; key operations go to Secure World via SMC */
/* In Classic CP SWC: request key derivation via Crypto API */
Crypto_JobType cryptoJob = {
.jobId = CRYPTO_JOB_KEY_DERIVE,
.jobPriority = CRYPTO_PRIORITY_NORMAL,
.jobInfo = &keyDeriveInfo,
.cryptoKeyId = CRYPTO_KEY_ID_VEHICLE_SECRET, /* Secure World key handle */
.targetCryptoKeyId = CRYPTO_KEY_ID_SESSION,
};
Crypto_ProcessJob(CRYPTO_DRIVER_ID_HSM, &cryptoJob);
/* SMC call: Normal World → Secure World HSM driver */
/* Key material never leaves Secure World — only derived session key returned */Summary
Hybrid Classic+Adaptive architectures separate function domains by real-time requirements and compute needs, not by hardware boundaries. The zonal ECU concentrates this complexity onto one SoC. The three integration challenges — DoIP diagnostic routing across domains, IPC gateway latency budgets, and TrustZone security boundaries for key material — must each be explicitly designed and validated before the first vehicle integration.
🔬 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.