The world's largest supply platform for sources of shortages and hard-to-find parts

Introduction of an upgrade test scheme for domain controllers

Published Time: 2022-08-18 16:05:35
The traditional auto ECU realizes software update by diagnostic brushing, and the data amount is small, generally in tens of KB to tens of MB; With the continuous advancement of the new four modernizations of automobiles, the architecture of domain contro

The traditional auto ECU realizes software update by diagnostic brushing, and the data amount is small, generally in tens of KB to tens of MB; With the continuous advancement of the new four modernizations of automobiles, the architecture of domain controller or central calculator on automobiles has evolved into MPU/SOC+MCU scheme, and the amount of data for MPU/SOC software upgrade is often hundreds of MB or even several GB. DoIP plus diagnostic services (0x34, 0x36) are used to transmit the upgrade package data. The process is tedious and the bandwidth utilization is low.


When sending the 36 service through DoIP, it waits for a TCP ACK from the transport layer, a 0x8002 packet from DoIP (0x8002 is not used in the simplified version), and a positive response from the controller before continuing to send data. Therefore, for the large amount of data in the upgrade package, manufacturers have adopted a variety of new methods to achieve domain controller software upgrade.


The master node initiates the upgrade task to realize the upgrade of the secondary node domain controller. This process is mainly carried out in the car. The master node first establishes an upgrade task for the slave node through the "SOA protocol", then sends the upgrade package to the slave node through the "IT protocol", and controls the upgrade process through the "SOA protocol". Compared with using diagnostic services to upgrade software, this process is simple and efficient, and can achieve the purpose of upgrading software quickly.