On October 22, 2019, WPG Holdings, a leading semiconductor component distributor dedicated to the Asia-Pacific market , announced that its subsidiary WPI has launched an ADAS domain controller system solution based on NXP S32V234 + MPC5744P.
Traditional cars use a distributed electrical and electronic architecture, and the various ECUs in the car are connected together through CAN or LIN buses. Now the number of ECUs in cars has increased to dozens or even hundreds, and the distributed architecture is therefore facing challenges. With the advent of the era of autonomous driving , the perception, control, and decision-making systems involved in car driving are becoming more and more complex, and the information interaction and control between systems are also increasing. All parties hope that it can become a modular , portable, and easy-to-manage automotive subsystem, and the concept of automotive domain controller DCU has therefore been proposed. According to different functions, the automotive network architecture can be divided into body domain, power domain, chassis domain, ADAS domain, external network domain, and infotainment domain.
Figure 1- A display board of the ADAS domain controller system solution launched by WPG World Peace based on NXP products
As an important component of future smart cars, ADAS domain controllers have functions such as multi -sensor fusion, positioning, path planning, decision control, wireless communication, and high-speed communication. They can flexibly configure and adjust the required functions according to customer requirements, and facilitate platform-based and modular production and manufacturing . Vehicle manufacturers can integrate platforms with similar structures across platforms, which not only facilitates production, but also increases the protection of information security, killing two birds with one stone for vehicle manufacturers.
The ADAS domain controller solution based on NXP S32V234 + MPC5744P launched by WPG World Peace requires the use of a powerful core processor to control most of the functions originally belonging to each ECU in the domain, thereby replacing the traditional distributed architecture. The S32V234 used in this solution is a core processor designed for safe computing-intensive applications in the field of vision and sensor fusion, with a quad-core Cor te x-A53 + Cortex-M4 processor, two APEX-2 vision accelerators, 3D GPU , and built-in ISP.
ADAS domain controller meets the safety function level requirements of automobiles. The SIP ADAS domain controller solution baseboard uses the MCU MPC5744P that meets the ISO-26262 ASIL requirements. It can manage and monitor the system power supply and handle system functional failures in real time, making the entire system reach ASIL-D level.
Figure 2-Block diagram of the ADAS domain controller system solution launched by WPG World Peace based on NXP products
Core technology advantages
S32V234 has super processing power, Cortex-M4 + 4-core Cortex-A53, main frequency reaches 1GHz, including GPU, APEX 2 professional image acceleration processing unit, which can meet the visual application needs of different fields such as automobile, industry and consumer;
Built-in ISP image signal processing module, supporting up to 8-way camera image input simultaneously;
The MPC574xP series of automotive-grade MCUs is the industry's first automotive-grade MCU to achieve functional safety ISO-26262 ASIL-D Qualification certification , a new generation of the MPC5643L.
Connect related sensors or modules, such as ultrasonic sensors for parking assistance, and report status to the gateway (eg HDC2080 is to simulate sensor reading);
Software update: Update the software of ADAS domain controller through vehicle communication protocol;
Functional safety: strictly monitor the power management of the ADAS domain controller and handle system dysfunctions accordingly. Even if a system operation error occurs, the ADAS domain control function can still be maintained within the normal operating range, reducing the damage caused by system failures.
ADAS-related intelligent driving functions are concentrated into DCU, and connected to the central gateway through a variety of interfaces such as Ethernet and CAN bus for information exchange and functional operations.
Solution Specifications
The motherboard is matched with the baseboard. The motherboard is the minimum system of S32V234, and the baseboard is the system with S32V234 peripheral interface and MPC5744P as the main chip.
Motherboard size: 82.0mm x 63.3mm, baseboard size: 220mm x 160mm;
Rich CAN, LIN and vehicle Ethernet interfaces , supporting access to various external devices (77G radar module, ultrasonic radar, etc.), and supporting communication with the vehicle ECU and central gateway via CAN and vehicle Ethernet;
Supports image data output via FPD-Link, HD MI display output, and storage function of PCIE to USB interface .
Previous article:Weighing sensors are used to prevent overloaded vehicles from collapsing highway bridges
Next article:Huawei to develop radar and build in-vehicle sensor ecosystem for self-driving cars
- Popular Resources
- Popular amplifiers
- Car key in the left hand, liveness detection radar in the right hand, UWB is imperative for cars!
- After a decade of rapid development, domestic CIS has entered the market
- Aegis Dagger Battery + Thor EM-i Super Hybrid, Geely New Energy has thrown out two "king bombs"
- A brief discussion on functional safety - fault, error, and failure
- In the smart car 2.0 cycle, these core industry chains are facing major opportunities!
- The United States and Japan are developing new batteries. CATL faces challenges? How should China's new energy battery industry respond?
- Murata launches high-precision 6-axis inertial sensor for automobiles
- Ford patents pre-charge alarm to help save costs and respond to emergencies
- New real-time microcontroller system from Texas Instruments enables smarter processing in automotive and industrial applications
- LED chemical incompatibility test to see which chemicals LEDs can be used with
- Application of ARM9 hardware coprocessor on WinCE embedded motherboard
- What are the key points for selecting rotor flowmeter?
- LM317 high power charger circuit
- A brief analysis of Embest's application and development of embedded medical devices
- Single-phase RC protection circuit
- stm32 PVD programmable voltage monitor
- Introduction and measurement of edge trigger and level trigger of 51 single chip microcomputer
- Improved design of Linux system software shell protection technology
- What to do if the ABB robot protection device stops
- Allegro MicroSystems Introduces Advanced Magnetic and Inductive Position Sensing Solutions at Electronica 2024
- Car key in the left hand, liveness detection radar in the right hand, UWB is imperative for cars!
- After a decade of rapid development, domestic CIS has entered the market
- Aegis Dagger Battery + Thor EM-i Super Hybrid, Geely New Energy has thrown out two "king bombs"
- A brief discussion on functional safety - fault, error, and failure
- In the smart car 2.0 cycle, these core industry chains are facing major opportunities!
- The United States and Japan are developing new batteries. CATL faces challenges? How should China's new energy battery industry respond?
- Murata launches high-precision 6-axis inertial sensor for automobiles
- Ford patents pre-charge alarm to help save costs and respond to emergencies
- New real-time microcontroller system from Texas Instruments enables smarter processing in automotive and industrial applications
- [Ateli Development Board AT32F421 Review] + Buttons are coming
- Uncover the secrets of the internal components of the power supply. Have you learned it?
- STEVAL-IDB008V1M Bluetooth evaluation board information
- Does anyone know what solar panel this is?
- 【Silicon Labs Development Kit Review】+ Serial Port Input and Output
- 【NXP Rapid IoT Review】+Download Materials
- Which Hall sensor 49E is used for steering of children's electric stroller?
- Personally, I feel that online classes are not very useful for individual students.
- Software design underlying logic
- When we make PCB, should we provide steel mesh files to the board factory?