Vehicle central domain controller software upgrading method and system based on a flashing diagnostic instrument

Abstract

The application provides a vehicle central domain controller software upgrading method and system based on a flashing diagnostic instrument, including the following steps: connecting the flashing diagnostic instrument to Switch through an Ethernet ETH network cable; establishing a UDP connection with MPU; initiating an identity verification request to MPU; verifying whether the identity of the flashing diagnostic instrument is legal; initiating a file transmission request to MPU, sending a controller flashing program compressed file to MPU; receiving and storing the compressed file; sending a file verification value; MPU receives the file verification value and calculates the file verification value; MPU compares whether the two file verification values are consistent; initiating an installation request to MPU; MPU decompresses the compressed file and parses the file content; judging whether the decompressed file content is legal; MPU downloads the MCU flashing program file to Nor Flash, downloads the communication SoC flashing program file to the internal memory of the communication SoC, writes the MPU flashing program file to eMMC, and respectively performs flashing update; sending an installation result to the flashing diagnostic instrument; and resetting the central domain controller by the flashing diagnostic instrument.

Description

Technical Field

[0001] This invention belongs to the field of controller flashing technology, specifically relating to a method and system for upgrading the software of a vehicle central domain controller based on a flashing diagnostic tool. Background Technology

[0002] In the current field of new energy commercial vehicles, the technology is gradually evolving towards an Ethernet-based domain control architecture, which typically includes a central domain controller, a cockpit domain controller, and an autonomous driving domain controller.

[0003] Central domain controllers run operating systems such as Linux and RTOS, and contain various types of CPUs including MCUs and MPUs, as well as different types of memory such as Nor Flash and eMMC. Application software packages often start at 10MB. Different controllers have different hardware and functions, and their control software also varies.

[0004] In the existing technology, the software upgrade of the controller is usually carried out by CAN flashing. However, the existing CAN flashing method has the following drawbacks: (1) The flashing speed is slow. In the actual production line, it takes about 2 minutes to flash a 1MB application file, and 20 minutes to flash a 10MB software package. This is unacceptable for vehicles that are about to be removed from the production line and put into storage; (2) Generally, for controllers with a single MCU, the application software package is usually less than 1MB, which cannot effectively upgrade the software of the central domain controller with multiple CPU modules and multiple memory types. Summary of the Invention

[0005] To address the shortcomings of the prior art, the present invention aims to provide a method and system for upgrading vehicle central domain controller software based on a diagnostic flashing tool.

[0006] To achieve the above objectives, the present invention adopts the following technical solution:

[0007] Option 1

[0008] This invention provides a method for upgrading the software of a vehicle central domain controller based on a flashing diagnostic tool, characterized by the following features: the central domain controller includes a main control SoC, a communication SoC, a switch, a Nor Flash, and an eMMC. The main control SoC contains an MCU and an MPU connected via internal RPC communication. The MPU is connected to the communication SoC and the switch via Ethernet (ETH) communication. The communication SoC has internal memory for storing its program. The Nor Flash is connected to the MCU for storing its program. The eMMC is connected to the MPU for storing its program. The method includes the following steps:

[0009] Step S1: Connect the flashing diagnostic tool to the Switch via an Ethernet (ETH) cable;

[0010] Step S2: The diagnostic tool establishes a UDP connection with the MPU.

[0011] Step S3: The flashing diagnostic tool sends an identity verification request to the MPU;

[0012] Step S4: The MPU verifies whether the identity of the flashing diagnostic tool is valid. If valid, proceed to step S5.

[0013] Step S5: The flashing diagnostic tool initiates a file transfer request to the MPU and sends a compressed file containing the controller flashing program file, the MPU flashing program file, and the communication SoC flashing program file to the MPU.

[0014] Step S6: The MPU receives and stores the controller flashing program compressed file;

[0015] Step S7: The flashing diagnostic tool sends a file verification value to the MPU;

[0016] Step S8: The MPU receives the file verification value as the preset file verification value, and calculates the file verification value based on the received controller flashing program compressed file as the current file verification value.

[0017] Step S9: The MPU compares the current file checksum with the preset file checksum. If they match, proceed to step S10.

[0018] Step S10: The flashing diagnostic tool sends an installation request to the MPU;

[0019] Step S11: The MPU decompresses the controller software upgrade compressed file and parses its contents;

[0020] Step S12: The MPU determines whether the contents of the decompressed file are valid based on the built-in flash file list. If valid, proceed to step S13.

[0021] Step S13: The MPU downloads the MCU flashing program file to the Nor Flash via RPC, downloads the communication SoC flashing program file to the internal memory of the communication SoC via Ethernet (ETH), writes the MPU flashing program file to the eMMC, and performs flashing updates accordingly.

[0022] Step S14: The MPU sends the installation result to the flashing diagnostic tool;

[0023] Step S15: Installation successful. Reset the central domain controller using the diagnostic tool.

[0024] The vehicle central domain controller software upgrade method based on a flashing diagnostic tool provided by this invention may also have the following feature: wherein, in step S13, the flashing update of the MCU specifically includes the following sub-steps:

[0025] Step S13-1-1: The MPU calls the MCU's flashing service via RPC;

[0026] In step S13-1-2, the MPU sends the MCU flashing program file to the MCU via RPC;

[0027] Step S13-1-3: The MCU erases the data in the inactive partition of the Nor Flash and writes the program file to be flashed into the inactive partition.

[0028] In step S13-1-4, the MCU sets the currently running partition to inactive and sets the partition where the new program is written to to active.

[0029] Step S13-1-5: MCU reset, start the active partition, and run the new program.

[0030] The vehicle central domain controller software upgrade method based on a flashing diagnostic tool provided by this invention may also have the following feature: wherein, in step S13, the flashing update of the MPU specifically includes the following sub-steps:

[0031] Step S13-2-1: The MPU erases the data in the inactive partition of the eMMC and writes the program file to be flashed into the inactive partition.

[0032] In step S13-2-2, the MPU sets the currently running partition to inactive and sets the partition where the new program is written to to active.

[0033] Step S13-2-3: MPU reset, start the active partition, and run the new program.

[0034] The vehicle central domain controller software upgrade method based on a flashing diagnostic tool provided by this invention may also have the following feature: wherein, in step S13, the flashing update of the communication SoC specifically includes the following sub-steps:

[0035] Step S13-3-1: The MPU initiates UDP communication with the communication SoC and sends the communication SoC flashing program file to the communication SoC.

[0036] Step S13-3-2: The MPU sends an update command to the communication SoC;

[0037] Step S13-3-3: The communication SoC backs up the currently running program and overwrites the running program with the new program;

[0038] Step S13-3-4: Reset the communication SoC and run the new program.

[0039] The vehicle central domain controller software upgrade method based on a flashing diagnostic tool provided by this invention may also have the following feature: wherein the MCU is connected to the vehicle's CAN bus and is responsible for receiving CAN messages from the entire vehicle.

[0040] The vehicle central domain controller software upgrade method based on a flashing diagnostic tool provided by the present invention may also have the following feature: wherein the communication SoC has a 4G network to provide the central domain controller with Internet access capability.

[0041] Option Two

[0042] The present invention also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the vehicle central domain controller software upgrade method based on a flashing diagnostic tool as described in <Scheme 1>.

[0043] Option 3

[0044] The present invention also provides a vehicle central domain controller software upgrade system based on a flashing diagnostic tool, characterized in that the system is used to execute the steps of the vehicle central domain controller software upgrade method based on a flashing diagnostic tool in <Scheme 1>.

[0045] Compared with existing technologies, the vehicle central domain controller software upgrade method based on a flashing diagnostic tool provided by this invention, on the one hand, enables the flashing of central domain controllers with multiple CPUs and various storage types, filling the gap in the industry for flashing methods of this type of domain controller architecture; on the other hand, the entire file transfer during the flashing process is based on Ethernet. The speed of traditional CAN bus is generally 500Kbit / s, while the speed of automotive Ethernet is 200 times that of CAN bus, reaching a transmission speed of 100Mbit / s. According to actual tests, the method of this invention can transfer a 10MB compressed file in only about 10 seconds, which greatly improves the speed of vehicle offline software flashing.

[0046] Furthermore, since the program of each controller is backed up, even if an accident occurs during flashing, the domain controller program can automatically switch back to the original program to continue running through the rollback algorithm. This prevents the vehicle from being unable to go offline due to a flashing accident, avoiding the problem of traditional ECUs not having backups and being unable to roll back to the original program to continue running if a problem is found after flashing a new program. Attached Figure Description

[0047] Figure 1This is a structural block diagram of the central domain controller in an embodiment of the present invention;

[0048] Figure 2 This is a flowchart of the operation of the central domain controller software upgrade method based on the flashing diagnostic instrument in an embodiment of the present invention;

[0049] Figure 3 This is a flowchart illustrating the MCU flashing and updating process in an embodiment of the present invention;

[0050] Figure 4 This is a flowchart illustrating the MPU flashing and updating process in an embodiment of the present invention; and

[0051] Figure 5 This is a flowchart illustrating the action of flashing and updating the communication SoC in an embodiment of the present invention. Detailed Implementation

[0052] The following will further explain the concept, specific structure, and technical effects of the present invention in conjunction with the accompanying drawings, so as to fully understand the purpose, features, and effects of the present invention.

[0053] <Example>

[0054] Figure 1 This is a structural block diagram of the central domain controller in an embodiment of the present invention.

[0055] like Figure 1 As shown, in this embodiment, the central domain controller for the vehicle includes a main control SoC, a communication SoC, a switch, a Nor Flash, and an eMMC.

[0056] The main control SoC contains an MCU and an MPU, which are connected through internal RPC communication.

[0057] The MPU connects to the communication SoC and the Switch via Ethernet (ETH) communication.

[0058] The MCU is connected to the vehicle's CAN bus and is responsible for receiving CAN messages from the entire vehicle.

[0059] The communication SoC has internal memory for storing its programs. In this embodiment, the communication SoC has a 4G network for providing internet access to the central domain controller.

[0060] The switch can connect to the flashing diagnostic tool via Ethernet (ETH) communication.

[0061] The NOR Flash is connected to the MCU and is used to store the MCU's program.

[0062] The eMMC is connected to the MPU and is used to store the MPU's program.

[0063] Figure 2 This is a flowchart of the operation of the central domain controller software upgrade method based on the flashing diagnostic instrument in an embodiment of the present invention; Figure 3 This is a flowchart illustrating the MCU flashing and updating process in an embodiment of the present invention; Figure 4 This is a flowchart of the MPU flashing and updating operation in an embodiment of the present invention; Figure 5 This is a flowchart illustrating the action of flashing and updating the communication SoC in an embodiment of the present invention.

[0064] like Figure 2 As shown in the figure, this embodiment provides a method for upgrading the software of a vehicle central domain controller based on a flashing diagnostic tool, which is used to upgrade the software of the central domain controller when the vehicle is taken off the production line. The method for upgrading the software of a vehicle central domain controller based on a flashing diagnostic tool includes the following steps S1 to S15.

[0065] Step S1: Connect the flash diagnostic tool to the Switch via an Ethernet (ETH) cable.

[0066] Step S2: The diagnostic tool establishes a UDP connection with the MPU.

[0067] Step S3: The flashing diagnostic tool sends an identity verification request to the MPU.

[0068] Step S4: The MPU verifies whether the identity of the flashing diagnostic device is valid. If valid, proceed to step S5; otherwise, enter the end state.

[0069] Step S5: The flashing diagnostic tool initiates a file transfer request to the MPU, sending the controller flashing program compressed file to the MPU.

[0070] Specifically, the controller flashing program compressed file includes MCU flashing program files, MPU flashing program files, and communication SoC flashing program files.

[0071] Step S6: The MPU receives and stores the controller flashing program compressed file.

[0072] Step S7: The flashing diagnostic tool sends a file verification value to the MPU.

[0073] In step S8, the MPU receives the file verification value as the preset file verification value and calculates the file verification value based on the received controller flashing program compressed file as the current file verification value.

[0074] Step S9: The MPU compares the current file checksum with the preset file checksum. If they match, proceed to step S10; otherwise, proceed to the end state.

[0075] Step S10: The flashing diagnostic tool sends an installation request to the MPU.

[0076] In step S11, the MPU decompresses the controller software upgrade compressed file and parses its contents.

[0077] In step S12, the MPU determines whether the contents of the decompressed file are valid based on the built-in flash file list. If valid, proceed to step S13; otherwise, enter the end state.

[0078] In step S13, the MPU downloads the MCU flashing program file to the Nor Flash via RPC, downloads the communication SoC flashing program file to the internal memory of the communication SoC via Ethernet (ETH), writes the MPU flashing program file to the eMMC, and performs flashing updates accordingly.

[0079] Specifically, such as Figure 3 As shown, the MCU flashing and updating process includes the following sub-steps:

[0080] In step S13-1-1, the MPU calls the MCU's flashing service via RPC.

[0081] In step S13-1-2, the MPU sends the MCU flashing program file to the MCU via RPC.

[0082] Step S13-1-3: The MCU erases the data in the inactive partition of the Nor Flash and writes the program file to be flashed into the inactive partition.

[0083] In step S13-1-4, the MCU sets the currently running partition to inactive and sets the partition where the new program is written to to active.

[0084] Step S13-1-5: MCU reset, start the active partition, and run the new program.

[0085] like Figure 4 As shown, the flashing and updating of the MPU specifically includes the following sub-steps:

[0086] Step S13-2-1: The MPU erases the data in the inactive partition of the eMMC and writes the program file to be flashed into the inactive partition.

[0087] In step S13-2-2, the MPU sets the currently running partition to inactive and sets the partition where the new program is written to to active.

[0088] Step S13-2-3: MPU reset, start the active partition, and run the new program.

[0089] like Figure 5 As shown, the flashing and updating of a communication SoC specifically includes the following sub-steps:

[0090] In step S13-3-1, the MPU initiates UDP communication with the communication SoC and sends the communication SoC flashing program file to the communication SoC.

[0091] In step S13-3-2, the MPU sends an update command to the communication SoC.

[0092] In step S13-3-3, the communication SoC backs up the currently running program and overwrites the running program with the new program.

[0093] Step S13-3-4: Reset the communication SoC and run the new program.

[0094] Step S14: The MPU sends the installation result to the flashing diagnostic tool.

[0095] Step S15: Installation successful. Reset the central domain controller using the diagnostic tool.

[0096] This invention also provides a vehicle central domain controller software upgrade system based on a flashing diagnostic tool, which is used to perform the steps of the vehicle central domain controller software upgrade method based on the flashing diagnostic tool described above.

[0097] This invention also provides a storage medium storing a computer program that, when executed by a processor, implements the steps of the vehicle central domain controller software upgrade method based on a flashing diagnostic tool as described above.

[0098] The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk.

[0099] The above embodiments are preferred embodiments of the present invention and are not intended to limit the scope of protection of the present invention.

Claims

1. A method for upgrading the software of a vehicle central domain controller based on a flashing diagnostic tool, characterized in that: The central domain controller includes the main control SoC, communication SoC, switch, Nor Flash, and eMMC. The main control SoC includes an MCU and an MPU connected via internal RPC communication. The MPU is connected to the communication SoC and the Switch via Ethernet (ETH) communication. The communication SoC has internal memory for storing the SoC's program. The Nor Flash is connected to the MCU and is used to store the MCU's program. The eMMC is connected to the MPU and is used to store the MPU's program. The method includes the following steps: Step S1: The flashing diagnostic tool is connected to the Switch via an Ethernet (ETH) cable; Step S2: The flashing diagnostic instrument establishes a UDP connection with the MPU; Step S3: The flashing diagnostic instrument sends an identity verification request to the MPU; Step S4: The MPU verifies whether the identity of the flashing diagnostic device is valid. If valid, proceed to step S5. Step S5: The flashing diagnostic tool initiates a file transfer request to the MPU and sends a compressed file containing the MCU flashing program file, the MPU flashing program file, and the communication SoC flashing program file to the MPU. Step S6: The MPU receives and stores the controller flashing program compressed file; Step S7: The flashing diagnostic instrument sends a file verification value to the MPU; Step S8: The MPU receives the file verification value as a preset file verification value, and calculates the file verification value as the current file verification value based on the received controller flashing program compressed file. Step S9: The MPU compares the current file checksum with the preset file checksum. If they match, proceed to step S10. Step S10: The flashing diagnostic tool sends an installation request to the MPU; Step S11: The MPU decompresses the controller software upgrade compressed file and parses the file content; Step S12: The MPU determines whether the contents of the decompressed file are valid based on the built-in flash file list. If valid, proceed to step S13. Step S13: The MPU downloads the MCU flashing program file to the Nor Flash via RPC, downloads the communication SoC flashing program file to the internal memory of the communication SoC via Ethernet (ETH), writes the MPU flashing program file to the eMMC, and performs flashing updates accordingly. Step S14: The MPU sends the installation result to the flashing diagnostic instrument; Step S15: Installation successful. The flashing diagnostic tool resets the central domain controller.

2. The vehicle central domain controller software upgrade method based on a flashing diagnostic tool according to claim 1, characterized in that: in, In step S13, the flashing and updating of the MCU specifically includes the following sub-steps: Step S13-1-1: The MPU calls the MCU's flashing service via RPC; In step S13-1-2, the MPU sends the MCU flashing program file to the MCU via RPC; Step S13-1-3: The MCU erases the data in the inactive partition of the Nor Flash and writes the program file to be flashed into the inactive partition. In step S13-1-4, the MCU sets the currently running partition to inactive and sets the partition where the new program is written to to active. Step S13-1-5: The MCU is reset, the activated partition is started, and a new program is run.

3. The method for upgrading vehicle central domain controller software based on a flashing diagnostic tool according to claim 1, characterized in that: in, In step S13, the flashing and updating of the MPU specifically includes the following sub-steps: Step S13-2-1: The MPU erases the data in the inactive partition of the eMMC and writes the program file to be flashed into the inactive partition; In step S13-2-2, the MPU sets the currently running partition to inactive and sets the partition where the new program is written to to active. In step S13-2-3, the MPU is reset, the activated partition is started, and a new program is run.

4. The method for upgrading vehicle central domain controller software based on a flashing diagnostic tool according to claim 1, characterized in that: in, In step S13, the flashing and updating of the communication SoC specifically includes the following sub-steps: Step S13-3-1: The MPU initiates UDP communication with the communication SoC and sends the communication SoC flashing program file to the communication SoC. Step S13-3-2: The MPU sends an update command to the communication SoC; Step S13-3-3: The communication SoC backs up the currently running program and overwrites the running program with the new program; In step S13-3-4, the communication SoC is reset and a new program is run.

5. The method for upgrading vehicle central domain controller software based on a flashing diagnostic tool according to claim 1, characterized in that: in, The MCU is connected to the vehicle's CAN bus and is responsible for receiving CAN messages from the entire vehicle.

6. The method for upgrading vehicle central domain controller software based on a flashing diagnostic tool according to claim 1, characterized in that: in, The communication SoC has a 4G network capability to provide internet access to the central domain controller.

7. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the vehicle central domain controller software upgrade method based on a flashing diagnostic tool as described in any one of claims 1-6.

Images