EV-16 — Software / Control Units

ASSUMPTION — This lesson introduces the ECU/software architecture at the system level. UDS/diagnostics detail is in BMS Academy → BMS-15.

1. ECU Architectures

Architecture	Description
Traditional	One ECU per function
Domain	Grouped by function (powertrain, body, ADAS)
Central compute	A powerful central computer
Zonal	Grouped by location (zone controller)

FACT — Zonal architecture reduces wiring and complexity; combined with central compute it forms the basis of the “software-defined vehicle”.

2. Domains

• Powertrain — motor/inverter/battery control.
• Body — doors, lighting, comfort.
• Vehicle motion — braking, steering, suspension.
• ADAS — sensor fusion, driving assistance.

3. OTA, Bootloader, UDS, DTC

• OTA — over-the-air software update.
• Bootloader — secure loading/starting of software.
• UDS (ISO 14229) — diagnostic service protocol.
• DTC — Diagnostic Trouble Code.

4. AUTOSAR

FACT — AUTOSAR is an architecture framework standardizing ECU software into application, services, abstraction layers, and drivers (detail: BMS-16).

5. FAQ

What is the difference between domain and zonal architectures?

FACT — Domain groups by function (powertrain, ADAS); zonal groups by location and reduces wiring.

Why does OTA matter?

FACT — It updates software without a service visit; secure updates require cryptographic verification.

6. Summary

• Domain groups by function; zonal groups by location.
• Central compute + zonal = software-defined vehicle.
• OTA/bootloader for updates; UDS/DTC for diagnostics.
• AUTOSAR standardizes the software architecture.

7. Sources and Verification Note

Standards are ISO/AUTOSAR-referenced.

• ISO 14229, AUTOSAR, SAE J1715.

Next Lesson

• EV-17 — 12V / 48V / HV: power distribution and sleep/wake-up.