Nissan and Honda have entered into a joint development agreement to establish common specifications for core vehicle computers and software intended for their next-generation software-defined vehicles (SDVs). The planned collaboration covers multiple electronic control units (ECUs), an in-vehicle operating system, key middleware and vehicle-control software.

The companies plan to apply the jointly developed electrical and electronic, or E/E, architecture in both companies’ next-generation SDVs from fiscal year 2029 onward. That is a planned application timeframe, not a confirmed production or customer-delivery date.

The announcement does not identify specific vehicle models, markets, hardware suppliers, software platforms or customer-facing features.

Contents

What Nissan and Honda are standardising

The agreement covers foundational parts of an SDV’s computing and software stack.

The companies will work on common specifications for multiple core ECUs within the vehicle’s E/E architecture. An ECU is an embedded computer that performs control or processing functions. The agreement includes two broad types:

  • High-performance main ECUs, described in the announcement as high-performance computers using system-on-chips, or SoCs.
  • Zone ECUs, which oversee functions associated with particular areas of a vehicle.

An SoC integrates multiple computing components onto a single semiconductor device. In an automotive system, a high-performance computer can provide substantially greater centralised processing capacity than a collection of smaller, narrowly focused controllers.

The agreement also includes an in-vehicle operating system, key middleware and vehicle-control software. Middleware is the software layer that provides common services and interfaces between the operating-system or platform layer and higher-level applications or control software.

Together, these elements form part of the infrastructure on which an SDV can run. A software-defined vehicle is one in which software plays a major role in determining functions and behaviour, potentially allowing features and control systems to be updated or expanded through software during the vehicle’s life.

The release describes standardisation of specifications and software technologies. It does not establish that Nissan and Honda will use identical implementations in every vehicle, or that the companies will share all resulting software.

Why the E/E architecture matters

A vehicle’s E/E architecture is the overall arrangement of its electronic control units, computing hardware, communication networks, sensors, actuators and software. It determines how information moves through the vehicle and how software can coordinate functions such as propulsion, safety systems, energy management and other vehicle controls.

The announced architecture covers multiple ECU roles, including high-performance main ECUs and zone ECUs. Zone ECUs generally aggregate or manage functions associated with physical areas of the vehicle, while high-performance computers can handle more demanding processing centrally.

This approach can provide a common technical foundation for vehicle software, but it also makes the underlying interfaces and software layers important. Common specifications can, in principle, reduce the number of unique systems that engineers must develop and maintain across vehicle programmes.

That potential does not by itself demonstrate that the resulting vehicles will be better, safer or cheaper. The practical outcome will depend on the final hardware, software architecture, validation process, cybersecurity measures, maintenance model and how the system is adapted to different vehicle platforms.

What the companies say they expect to gain

Nissan and Honda describe the agreement as part of their broader strategic partnership. They say that standardising foundational ECU and software technologies could improve development efficiency, accelerate innovation, reduce development costs and create economies of scale.

These are company-stated aims rather than measured results. The announcement does not quantify expected engineering savings, cost reductions, performance improvements or production volumes.

The companies also place the collaboration within broader objectives related to carbon neutrality and a future with zero traffic fatalities involving their vehicles. The supplied announcement does not provide technical evidence showing how this specific standardisation effort would achieve either objective.

If the common architecture is successfully developed and validated, sharing specifications or selected software foundations could allow the two manufacturers to coordinate parts of their engineering work while retaining different vehicle designs and product strategies. That is a possible consequence of the agreement, not an outcome demonstrated by the announcement.

Sources