How to choose smart car domain controller chip

(1) Job requirements

The power domain control MCU can support major power applications such as BMS. Its requirements are as follows:

· High main frequency, main frequency 600MHz~800MHz

· RAM 4MB

· High functional safety level requirements, which can reach ASIL-D level;

· Support multi-channel CAN-FD;

· Support 2G Ethernet;

· Reliability is not lower than AEC-Q100 Grade1;

· Support firmware verification function (national secret algorithm);

(2) Performance requirements

High performance: The product integrates ARM Cortex R5 dual-core lock-step CPU and 4MB on-chip SRAM to support the growing demand for computing power and memory in automotive applications. ARM Cortex-R5F CPU clocked at up to 800MHz.

High safety: The automotive reliability standard AEC-Q100 reaches Grade 1 level, and the ISO26262 functional safety level reaches ASIL D. The dual-core lock-step CPU used can achieve diagnostic coverage of up to 99%. The built-in information security module integrates true random number generator, AES, RSA, ECC, SHA and hardware accelerators that comply with national and commercial secret standards. The integration of these information security functions can meet the needs of applications such as secure boot, secure communication, and secure firmware updates and upgrades.

4. Body domain control chip

The body domain is mainly responsible for the control of various functions of the body. With the development of the entire vehicle, there are more and more body domain controllers. In order to reduce the cost of the controller and the weight of the entire vehicle, integration requires all functional devices, from the front part of the vehicle to the middle part of the vehicle and the rear part of the vehicle. For example, the rear brake lights, rear position lights, tailgate locks, and even double struts are integrated into a total controller.

Body domain controllers generally integrate functions such as BCM, PEPS, TPMS, and Gateway. They can also be expanded to add functions such as seat adjustment, rearview mirror control, and air conditioning control. They can comprehensively and uniformly manage each actuator and allocate system resources reasonably and effectively. The body domain controller has many functions, as shown in the figure below, but is not limited to the functions listed here.

Body Domain Controller Function Table

(1) Job requirements

The main demands of automotive electronics for MCU control chips are better stability, reliability, security, real-time and other technical characteristics, as well as higher computing performance and storage capacity, and lower power consumption indicators. The body domain controller has gradually transitioned from decentralized functional deployment to a large controller that integrates basic drives, key functions, lights, doors, windows, etc. of all body electronics. The design of the body domain control system integrates lighting, wipers and washing , central door lock, window and other controls, PEPS smart keys, power management, etc., as well as various development and design technologies such as gateway CAN, scalable CANFD and FLEXRAY, LIN network, Ethernet and other interfaces and modules.

Generally speaking, the working requirements of the MCU main control chip for the above-mentioned control functions in the body domain are mainly reflected in the aspects of computing processing performance, functional integration, communication interface, and reliability. In terms of specific requirements, due to the large functional differences in different functional application scenarios in the body domain, body applications such as electric windows, automatic seats, and electric tailgates also have needs for efficient motor control. Such body applications require MCUs integrated with FOC. Electronic control algorithms and other functions. In addition, different application scenarios in the car body domain have different interface configuration requirements for chips. Therefore, it is usually necessary to select a body domain MCU based on the function and performance requirements of specific application scenarios, and on this basis, comprehensively weigh factors such as product cost performance, supply capabilities, and technical services.

(2) Performance requirements

The main reference indicators of body domain control MCU chips are as follows:

· Performance: ARM Cortex-M4F @144MHz, 180DMIPS, built-in 8KB instruction Cache, supports Flash acceleration unit execution program with 0 wait.

· Large-capacity encrypted memory: up to 512K Bytes eFlash, supports encrypted storage, partition management and data protection, supports ECC verification, 100,000 erasing and writing times, and 10 years of data retention; 144K Bytes SRAM, supports hardware parity check.

· Integrated rich communication interfaces: supports multiple GPIO, USART, UART, SPI, QSPI, I2C, SDIO, USB2.0, CAN 2.0B, EMAC, DVP and other interfaces.

· Integrated high-performance analog devices: supports 12bit 5Msps high-speed ADC, rail-to-rail independent operational amplifier, high-speed analog comparator, 12bit 1Msps DAC; supports external input independent reference voltage source, multi-channel capacitive touch keys; high-speed DMA controller.

·Supports internal RC or external crystal clock input and high reliability reset.

· Built-in calibrated RTC real-time clock, supports leap year perpetual calendar, alarm events, and periodic wake-up.

·Support high-precision timing counter.

· Hardware-level security features: cryptographic algorithm hardware acceleration engine, supports AES, DES, TDES, SHA1/224/256, SM1, SM3, SM4, SM7, MD5 algorithms; Flash storage encryption, multi-user partition management (MMU), TRNG true Random number generator, CRC16/32 operation; supports write protection (WRP), multiple read protection (RDP) levels (L0/L1/L2); supports secure boot, program encrypted download, and secure updates.

· Support clock failure monitoring and anti-tamper monitoring.

· Has 96-bit UID and 128-bit UCID.

· Highly reliable working environment: 1.8V～3.6V/-40℃～105℃.

(3) Industrial pattern

Body domain electronic systems are in the early stages of growth for both foreign and domestic companies. Foreign companies have profound technical accumulation in single-function products such as BCM, PEPS, doors and windows, and seat controllers. At the same time, the product lines of major foreign companies cover a wide range, laying the foundation for them to make system integration products. Domestic companies have certain advantages in the application of new energy vehicle bodies. Take BYD as an example. In BYD's new energy vehicles, the body domain is divided into three domains: left, right and rear, and the products for system integration are re-arranged and defined. However, in terms of body domain control chips, the main suppliers of MCUs are still international chip manufacturers such as Infineon, NXP, Renesas, Microchip, and ST. Domestic chip manufacturers currently have a low market share.

(4) Industry barriers

From a communications perspective, there is an evolution of traditional architecture - hybrid architecture - and ultimately Vehicle Computer Platform. Changes in communication speed and price reduction of basic computing power with high functional security are key here. In the future, it may be possible to gradually achieve compatibility with different functions at the electronic level of the basic controller. For example, the body domain controller can integrate traditional BCM, PEPS, ripple anti-pinch and other functions. Relatively speaking, the technical barriers of body domain control chips are lower than those in the power domain, cockpit domain, etc. Domestic chips are expected to be the first to make major breakthroughs in the body domain and gradually realize domestic substitution. In recent years, domestic MCUs have achieved very good development momentum in the body field and rear assembly market.

5. Cockpit domain control chip

Electrification, intelligence, and networking have accelerated the development of automotive electronic and electrical architecture toward domain control, and the cockpit domain is also developing rapidly from in-vehicle audio and video entertainment systems to smart cockpits. The cockpit is presented with a human-computer interaction interface, but whether it is the previous infotainment system or the current smart cockpit, in addition to a SOC with powerful computing speed, it also requires an MCU with high real-time performance to handle data interaction with the entire vehicle. The gradual popularity of software-defined cars, OTA, and Autosar in the smart cockpit domain has made the requirements for MCU resources in the cockpit domain increasingly higher. Specifically, the demand for FLASH and RAM capacity is increasing, and the demand for PIN Count is also increasing. More complex functions require stronger program execution capabilities and richer bus interfaces.

(1) Job requirements

In the cockpit domain, the MCU mainly implements system power management, power-on sequence management, network management, diagnosis, vehicle data interaction, button, backlight management, audio DSP/FM module management, system time management and other functions.

MCU resource requirements:

· There are certain requirements for the main frequency and computing power, the main frequency is not less than 100MHz and the computing power is not less than 200DMIPS;

· Flash storage space is not less than 1MB, with code Flash and data Flash physical partitions;

· RAM is not less than 128KB;

· High functional safety level requirements, which can reach ASIL-B level;

·Support multiple ADCs;

·Support multi-channel CAN-FD;

· Vehicle regulatory grade AEC-Q100 Grade1;

· Support online upgrade (OTA), Flash supports dual banks;

· Requires an information encryption engine of SHE/HSM-light level and above to support secure startup;

· Pin Count is not less than 100PIN;

(2) Performance requirements

· IO supports wide voltage power supply (5.5v~2.7v), and the IO port supports overvoltage use;