The Road To Electronics Consolidation In The Vehicle

What’s behind the drive to system-level design and why it’s so difficult.


I’ve been at Mentor for more than six months as the director of automotive marketing. It’s an exciting technology space with many great stories to tell, most stemming from the fact that the automotive industry is being disrupted like never before. Indeed, I’ve heard it said more than once that there will be more change in the next 5 to 10 years than there has been since the days of Henry Ford and Alfred P. Sloan. That’s about right.

We increasingly hear about centralizing the processing power in cars down to two processors—one to handle all communications with the driver, and the other to process the autonomous-driving functions. This could also enable the so-called deep-learning for cars concept, where a few powerful processors analyze the huge amounts of data generated by the cameras and sensors in a car to “learn” how to drive the car more safely and effectively, the other handing all network and data management. But from a vehicle architecture perspective, just how realistic is it to centralize around a handful of processors?

This question touches on several disparate points, such as electrical and electronic system architecture, sourcing strategy by car makers for SoCs and the vehicle increasingly being defined as a software platform more so than hardware. Architectures and SoC evolution are good topics to discuss when we look at ECU consolidation, but what about physical constraints that car makers need to deal with: weight, and space constraints for example. The trend towards ECU consolidation is definitely happening, but to standardize on two big processors for communication and autonomous functions may result in running significantly more cabling around the car, adding weight and cost.

Finding the Sweet Spot to a Multi-Dimensional Problem
Today’s automotive networks may look complex and inefficient, but they actually find the sweet spot between function, cost and vehicle weight. Ask any wiring harness manufacturer. First, there is the problem of physically fitting an expanded wiring harness into space constrained environment such as doors. Automakers can decide to add more ECUs and create greater distribution of network to reduce cabling size, weight and cost.

Macleod Figure 1

Another issue is whether to have an Ethernet backbone for data flowing through the vehicle. That certainly makes sense, but it will not replace CAN and LIN communications for things like door, mirror and seat control, the main body electronics functions that make up a significant part of the vehicle ECU network. That’s why new entrants to the auto industry with electric vehicles have, to date, designed distributed architectures, to manage vehicle weight which is particularly relevant when we consider new energy, and the direct impact on range.

It quickly becomes apparent that the problem is multi-dimensional—how to bring the latest automotive innovations to market faster, on budget, keep the vehicle weight to a minimum, and leverage decades of legacy software and network hardware. The two mega compute processors address only part of this, and arguably create all kinds of new problems.

Consolidation: Slowly but Surely
Every part of the vehicle is becoming electrified, and the road to consolidation may be appealing, and have cost benefits on-paper, but squeezing out those benefits means a complete re-write of today’s EE systems, something car makers don’t like.

Will the infotainment head unit and driver information system (cluster) converge? Absolutely and this makes sense. Will we see ECU consolidation driving vehicle networks from >100 processors in-car to just 2, 5 or even 10? Not anytime soon.

Consider the aspects of SoC design, and the challenges of running a vehicle from 2 main processors. Getting an automotive-grade SoC onto the road is not the same as getting it into a cellphone. The processors need to be zero defect for the life of the vehicle, have full functional safety compliance to ASIL-D level, be secure from external attacks and have secure partitioning around the vehicle. This is not a trivial task and there are only a handful of companies who can provide these processors.

Macleod Figure 2

Of course, with advanced process geometries, SoC vendors are designing fewer unique automotive microprocessor designs per technology node, due to design and manufacturing cost. So there is an argument that this will provide a catalyst for integration of function, and result in less unique, but more powerful processors with increasing functionality. But even if this trend proves true, the comfort and body electronics functions will remain distributed as long as we have copper wire and standard automotive communications networks.

Larger Paradigm Shift to System Design

The issue of consolidation is really a smaller part of the larger trend of the auto industry shifting from a manufacturing focus to a consumer-based focus, in response to drivers’ expectations for the latest and greatest technologies in their cars. This in turn is creating demand for shorter design cycles, software updates over the life of the car—for example, updating in vehicle infotainment systems to keep them relevant–and system engineering support to integrate this into the existing vehicle architecture.

The processor is just one part of this larger challenge. As we said, the wider question is how to make this not only secure, but also have zero defect for the life of the car, while still getting to market faster and staying within budget. It is this shift from component design to vehicle electrical design that is the real challenge that car OEM’s face, requiring system design expertise to implement a new architecture within these constraints. Some premium OEM’s are developing custom electrical architectures dependent of the model and the options selected by the buyer. Other automakers find that a more distributed architecture reduces cost in different ways: such as eliminating extra wiring and complexity.

The question of reducing the number of ECU’s in a car is still a valid one from a megatrend perspective, but it doesn’t capture the reality of EE car design today and the myriad of challenges that car makers face. Sweeping up all the ECUs into handful of powerful processors sounds like a great idea for a prototype architecture, but making it work is a different question, as OEM’s well understand. This is why the current hot topic of deep learning for cars as the catalyst for ECU consolidation is a great subject to talk about, but first there are a few engineering design constraints that need to be considered. It will be an interesting road to get there, but we aren’t there just yet.

You’ll find more of my thoughts on automotive technology on Mentor Blogs, where you’ll also find a longer bio. More importantly, I’d love to hear your thoughts, either below or via Twitter @AndyMacleod_MG.

Leave a Reply

(Note: This name will be displayed publicly)