| Criterion | Description | Example Constraint |
|---|---|---|
| Safety (ASIL) | Same ASIL or lower can share ECU; higher ASIL requires freedom from interference | AEB (ASIL-B) and infotainment (QM) cannot share same OS partition without FFI |
| Latency | Function cycle time must be achievable on ECU | Sensor fusion at 30 Hz needs > 100 MIPS on chosen ECU |
| Physical proximity | Sensor/actuator must be near ECU (wire length, latency) | Radar is front-mounted; radar processing ECU should be in front zone |
| Resource budget | ROM, RAM, CPU budget must fit on ECU | Object detection NN model 8 MB ROM; zone ECU must have >= 16 MB flash |
| Independence | Functions from different ASIL levels needing independent evidence | EPS (ASIL-D) and entertainment (QM) must be on separate ECUs or OS partitions |
| Supplier responsibility | OEM vs Tier-1 boundary determines interface spec responsibility | OEM-owned functions should be on OEM-designated ECU |
Function-to-ECU Allocation Criteria
Allocation Matrix Implementation
"""Function-to-ECU allocation matrix with constraint checking."""
from dataclasses import dataclass, field
from typing import List, Dict
@dataclass
class ECU:
ecu_id: str
name: str
cpu_mips: int
rom_kb: int
ram_kb: int
max_asil: str # maximum ASIL this ECU can host
@dataclass
class Function:
func_id: str
name: str
asil: str
cpu_mips: int # required MIPS
rom_kb: int
ram_kb: int
allocated_ecu: str = ""
ASIL_ORDER = {"QM": 0, "ASIL-A": 1, "ASIL-B": 2, "ASIL-C": 3, "ASIL-D": 4}
def check_asil_compatibility(func: Function, ecu: ECU) -> bool:
return ASIL_ORDER[func.asil] <= ASIL_ORDER[ecu.max_asil]
def check_resource_fit(functions: List[Function], ecu: ECU) -> dict:
allocated = [f for f in functions if f.allocated_ecu == ecu.ecu_id]
used_cpu = sum(f.cpu_mips for f in allocated)
used_rom = sum(f.rom_kb for f in allocated)
used_ram = sum(f.ram_kb for f in allocated)
return {
"cpu_ok": used_cpu <= ecu.cpu_mips * 0.70, # 70% max load
"rom_ok": used_rom <= ecu.rom_kb * 0.80,
"ram_ok": used_ram <= ecu.ram_kb * 0.80,
"cpu_used_pct": used_cpu / ecu.cpu_mips * 100,
}ASIL Decomposition via Allocation
System requirement: EPS Torque Control ASIL-D ┌─────────────────────────────────────────────────┐ │ Option A: Single ECU ASIL-D │ │ EPS ECU (ASIL-D capable MCU, e.g. TC397) │ │ Full ASIL-D development for all SW components │ │ Cost: very high development effort │ └─────────────────────────────────────────────────┘ ┌─────────────────────────────────────────────────┐ │ Option B: ASIL-D decomposition (ISO 26262 Part 9)│ │ EPS Control ECU (ASIL-C) ─ torque calculation │ │ + │ │ EPS Monitor ECU (ASIL-A) ─ plausibility check │ │ = ASIL-D system (if independent, no CCF) │ │ Cost: lower; reuse existing ASIL-C ECU │ └─────────────────────────────────────────────────┘
Summary
Function-to-ECU allocation is the single most consequential architecture decision in an automotive project because it determines ECU count, BOM cost, harness complexity, and ASIL development effort simultaneously. The ASIL decomposition mechanism (splitting an ASIL-D requirement across two independent lower-ASIL ECUs) is the most important cost optimisation tool available to the system architect: developing an ASIL-D software component costs approximately 4x more than ASIL-B, so decomposing an ASIL-D function into ASIL-C + ASIL-A can halve the development cost. The independence requirement (no common cause failure between the two channels) is the constraint that makes this valid -- the two ECUs must have independent power supplies, independent communication paths, and independent MCU families to claim true independence.
🔬 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.