Imagine your car's large infotainment screen suddenly goes black, yet the engine keeps running smoothly. You tap the A/C button on the screen; the temperature setting doesn't change, but you can clearly hear the compressor running. Many car owners have experienced this kind of disconnect.
To understand what's going on here, you first need to distinguish between two components that are often confused: the ECU and the MCU.
An ECU is a complete control board, whereas an MCU is a specific chip located on that board.
Electronic Control Unit (ECU)
ECU stands for Electronic Control Unit. It is a complete circuit board-featuring circuitry, chips, and interfaces-housed within a plastic casing. You'll find one next to the engine, another by the transmission, and several others tucked inside the car doors.
Demystifying the MCU: What is an MCU?
MCU stands for Microcontroller Unit; it is the core chip *inside* the ECU. An MCU integrates a CPU, memory, and input/output interfaces onto a single chip the size of a fingernail. Every ECU contains at least one MCU chip.
To use an analogy: if the ECU is a complete computer system (including the motherboard, power supply, and casing), the MCU is the CPU chip inside that system.
A single vehicle contains dozens or even hundreds of ECUs, and each ECU houses at least one MCU.
Traditional vehicles utilize a distributed architecture where each function is assigned an independent ECU. There are separate units for the engine, transmission, air conditioning, and windows-each operating autonomously. An average family car typically has between 70 and 100 ECUs. High-end models have even more; the 2015 BMW 7 Series, for instance, utilized approximately 140 ECUs.
Each ECU contains an internal MCU chip to handle processing tasks. Consequently, the number of MCUs in a vehicle roughly corresponds to the number of ECUs.
[Image]
These ECUs have clearly defined roles. The engine ECU manages fuel injection and ignition; the A/C ECU controls the compressor and blower fan; and the body ECU handles windows, door locks, and windshield wipers. The MCU within each ECU is responsible for executing that module's specific control logic: collecting sensor data, performing calculations, and issuing commands.
In a cockpit domain controller, alongside the SoC (System on Chip) that powers the large Android display, there is also an independent MCU. In modern smart cockpits, the board located behind the large display is known as the "cockpit domain controller." This board houses two core chips: an SoC (System-on-Chip) running Android to handle the large display and applications, and a separate MCU (Microcontroller Unit) dedicated to communication and low-level control tasks.
The Android SoC cannot communicate directly with the vehicle's CAN bus. When you tap "Set A/C to 24°C" on the large display, the command is first sent to the cockpit MCU; the MCU translates it into a format the CAN bus recognizes and forwards it to the A/C ECU. Conversely, data such as temperature and fan speed fed back by the A/C ECU is transmitted back to the large display via this same MCU.
"Sleep Cockpit": The Most Imaginative Car Feature | 2021 Roundup | Sohu Auto
In addition to this, the cockpit MCU manages two other functions: power-up/sleep sequences and steering wheel controls.
When you press the "Start" button, the cockpit MCU wakes up first and powers up the various modules in sequence. When you lock the car and walk away, the cockpit MCU is the last to enter sleep mode, shutting down the necessary systems. Signals from steering wheel buttons-such as volume, track skipping, and voice commands-also pass through this MCU before being forwarded.
Therefore, if a firmware update for the MCU causes the air conditioning to temporarily malfunction, the issue lies with the cockpit MCU, not the A/C ECU.
Many car owners have encountered this scenario: after an OTA update or a software flash at the dealership, the A/C buttons on the large display become unresponsive, and the temperature cannot be adjusted. Yet, the A/C compressor keeps running, and the fan continues to blow air.
The reason is simple: during the flashing process, the cockpit MCU enters "flash mode" and pauses the transmission and reception of CAN messages. Temperature adjustment commands tapped on the display cannot be sent out, so the A/C ECU never receives them; likewise, status updates from the A/C ECU cannot be transmitted back, so the display cannot show them. Meanwhile, the MCU inside the A/C ECU continues to operate normally-hardware components like the compressor and fan keep working as intended-but the large display loses control over them.
Once the flashing is complete and the cockpit MCU reboots, bus communication is restored, and control via the large display returns to normal.
This illustrates a key point: a smart cockpit is far more complex than just a large display paired with an Android box. The MCU located behind the screen serves as the hub facilitating communication between the cockpit and the entire vehicle. While the large display acts as the "face," the MCU functions as the "nervous system."
Image
The industry is shifting from a "one function, one ECU" model to a "one domain controller managing a cluster of ECUs" approach.
Under traditional distributed architectures, the sheer number of ECUs results in wiring harnesses exceeding 4 kilometers in total length and weighing between 50 and 70 kilograms. The current trend involves consolidating multiple ECUs into domain controllers-covering the cockpit domain, intelligent driving domain, and body domain. Looking ahead, the architecture will evolve toward a centralized computing platform combined with zonal controllers.
Although the total number of ECUs is decreasing, the demand for MCU chips remains undiminished; domain controllers still require MCUs for real-time control and communication gateway functions. MCUs will not be replaced; rather, the way they are implemented is simply changing.
