ECU upgrade method, device and readable storage medium

Abstract

The ECU upgrade method includes a step of acquiring a set first encapsulation file, in which first vehicle model information and first upgrade content related information corresponding to the first vehicle model information are encapsulated; a step of acquiring the first vehicle model information and the first upgrade content related information based on the first encapsulation file; a step of acquiring first upgrade process related information corresponding to the first vehicle model information from a setting memory based on the first vehicle model information; and a step of performing an ECU upgrade process on a vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information.

Description

[Technical Field]

[0001] (Reference to related applications) This application claims priority to a Chinese patent application bearing application number 202111481969.1 and entitled "ECU upgrade method, device and readable storage medium," filed with the State Intellectual Property Office of the People's Republic of China on December 6, 2021, the entire contents of which are incorporated herein by reference.

[0002] TECHNICAL FIELD Embodiments of the present disclosure relate to the technical field of software upgrade, and more particularly to an ECU upgrade method, apparatus, and readable storage medium. [Background technology]

[0003] Software is a key component of automotive controllers. During the development, production, and after-sales service stages, both automotive controller suppliers and automotive manufacturers have a need for software updates and upgrades. For example, upgrading the software of an ECU (Electronic Control Unit, also known as an electronic control unit, driving computer, or on-board computer) can be used to fix bugs, add new functions, and more.

[0004] Currently, according to a specific vehicle model and the corresponding upgrade needs, a corresponding ECU upgrade program is intentionally designed, and based on this, an ECU upgrade can be carried out for the vehicle model.

[0005] However, due to the diversity of vehicle models and the continuous changes in upgrade demand, the corresponding upgrade program design needs to be duplicated, so the overall upgrade effect is not high. Summary of the Invention

[0006] One objective of the embodiments of the present disclosure is to provide a new technical means for ECU upgrade.

[0007] An ECU upgrade method according to a first aspect of the present disclosure includes the steps of: acquiring a configured first encapsulated file, in which first vehicle model information and first upgrade content-related information corresponding to the first vehicle model information are encapsulated; acquiring the first vehicle model information and the first upgrade content-related information based on the first encapsulated file; acquiring first upgrade process-related information corresponding to the first vehicle model information from a configuration memory based on the first vehicle model information; and performing an ECU upgrade process on a vehicle having the first vehicle model information based on the first upgrade process-related information and the first upgrade content-related information.

[0008] Preferably, the first upgrade content related information includes upgrade content and upgrade parameters, the upgrade parameters include a physical addressing identifier ID, a function addressing ID, a response ID, a write key, and a CAN bus baud rate, and the upgrade content includes project chip information, a project code, and a vehicle model key.

[0009] Preferably, the step of obtaining the first upgrade process related information corresponding to the first vehicle model information from the configuration memory includes the step of obtaining the first upgrade process related information corresponding to the first vehicle model information stored in the local memory when the current upgrade mode corresponds to the developer mode, and the step of obtaining the first upgrade process related information corresponding to the first vehicle model information stored in the remote server when the current upgrade mode does not correspond to the developer mode, and both the local memory and the remote server store a configuration mapping relationship between the vehicle model information and the upgrade process related information.

[0010] Preferably, before the step of acquiring first upgrade process related information corresponding to the first vehicle model information stored in the local memory, the method further includes the steps of: acquiring the first vehicle model information in response to a selection operation corresponding to the first vehicle model information, when the current upgrade mode corresponds to the developer mode; acquiring the corresponding upgrade process related information in response to an operation to edit the upgrade process related information; and constructing a mapping relationship between the first vehicle model information and the acquired upgrade process related information and storing the constructed mapping relationship in the local memory.

[0011] Preferably, the step of performing ECU upgrade processing on a vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information includes a step of performing ECU upgrade processing on a vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information and a set test abnormality situation when the current upgrade mode corresponds to the developer mode.

[0012] Preferably, after the step of performing an ECU upgrade process on a vehicle having the first vehicle model information based on a set test abnormality situation, the method further includes the steps of obtaining a first upgrade result, determining whether the first upgrade result is the same as a setting upgrade result corresponding to the test abnormality situation, and if the first upgrade result is the same as the setting upgrade result, storing the setting mapping relationship stored in the local memory in the remote server.

[0013] Preferably, the test abnormal conditions include an abnormal message, an error check code, a high CAN bus load, and continuous writes.

[0014] Preferably, before the step of obtaining the set first encapsulated file, the method further includes the steps of, when the current upgrade mode corresponds to the developer mode, obtaining the first vehicle model information in response to a selection operation corresponding to the first vehicle model information, obtaining the first upgrade content related information in response to an operation to edit upgrade content related information, and performing an encapsulation process on the first vehicle model information and the first upgrade content related information in response to a set encapsulation command corresponding to the first vehicle model information to obtain the first encapsulated file.

[0015] Preferably, after the step of acquiring the first upgrade content related information, the method further includes the steps of: storing a mapping relationship between the first vehicle model information and the first upgrade content related information in a remote server; acquiring the first vehicle model information in response to a selection operation corresponding to the first vehicle model information; acquiring the first upgrade content related information corresponding to the first vehicle model information from the remote server; and performing an encapsulation process on the first vehicle model information and the first upgrade content related information in response to a setting encapsulation command corresponding to the first vehicle model information based on the acquired first upgrade content related information to acquire the first encapsulated file.

[0016] An ECU upgrade device according to a second aspect of the present disclosure includes a first acquisition module that acquires a set first encapsulated file, wherein the first encapsulated file encapsulates first vehicle model information and first upgrade content related information corresponding to the first vehicle model information; a second acquisition module that acquires the first vehicle model information and the first upgrade content related information based on the first encapsulated file; a third acquisition module that acquires first upgrade process related information corresponding to the first vehicle model information from a setting memory based on the first vehicle model information; and a processing module that performs an ECU upgrade process on a vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information.

[0017] An ECU upgrade device according to a third aspect of the present disclosure includes a memory and a processor, wherein the memory stores a computer program and the processor executes the computer program to realize the method according to the first aspect of the present disclosure.

[0018] An ECU upgrade system according to an embodiment of the fourth aspect of the present disclosure includes a host computer and a vehicle, wherein the host computer includes an ECU upgrade device according to the second or third aspect of the present disclosure, and the vehicle includes an ECU.

[0019] A computer-readable storage medium according to a fifth aspect of the present disclosure stores a computer program that causes a processor to implement the method according to the first aspect of the present disclosure.

[0020] One beneficial effect of the embodiment of the present disclosure is to obtain a configured first encapsulated file, in which first vehicle model information and first upgrade content-related information corresponding to the first vehicle model information are encapsulated; obtain the first vehicle model information and the first upgrade content-related information based on the first encapsulated file; obtain first upgrade process-related information corresponding to the first vehicle model information from the configuration memory based on the first vehicle model information; and perform an ECU upgrade process for a vehicle having the first vehicle model information based on the first upgrade process-related information and the first upgrade content-related information. As can be seen, the introduction of an encapsulated file in which vehicle model information and corresponding upgrade content-related information are encapsulated can address the diversification of vehicle models and their various upgrade needs. This embodiment obtains upgrade content-related information and upgrade process-related information corresponding to a vehicle model based on the encapsulated file, and then performs an ECU upgrade for the vehicle of that vehicle model based on the information. This universal upgrade method can be applied to ECU upgrade purposes for various vehicle models and various upgrade needs, eliminating the need for duplication of intentional upgrade program design, thereby improving the overall upgrade effect.

[0021] Other features and advantages of the embodiments of the present disclosure will become apparent from the following detailed description of exemplary embodiments of the present disclosure, taken in conjunction with the drawings. [Brief explanation of the drawings]

[0022] The drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the present disclosure and, together with the description, serve to explain the principles of the embodiments of the present disclosure.

[0023] [Figure 1] 1 is a schematic diagram illustrating a configuration of an electronic device capable of implementing an ECU upgrade method according to an embodiment. [Figure 2] 1 is a flowchart of an ECU upgrade method according to an embodiment. [Figure 3] 10 is a flowchart of an ECU upgrade method according to another embodiment. [Figure 4] 1 is a block diagram illustrating the principle of an ECU upgrade device according to an embodiment. [Figure 5] 1 is a schematic diagram illustrating the hardware configuration of an ECU upgrade device according to an embodiment. [Figure 6] 1 is a block diagram illustrating the principle of an ECU upgrade system according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0024] Various exemplary embodiments of the present disclosure will be described in detail below with reference to the drawings. It should be noted that unless otherwise specifically stated, the relative arrangement of components and steps, numerical expressions and values ​​described in these embodiments do not limit the scope of the present invention.

[0025] The following description of at least one exemplary embodiment is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.

[0026] Techniques, methods and devices known to those skilled in the art are not discussed in detail, but where appropriate, said techniques, methods and devices should be considered part of the specification.

[0027] In all examples shown and discussed herein, any specific values ​​should be construed as illustrative only and not limiting, and therefore, other examples of the exemplary embodiments may have different values.

[0028] It should be noted that similar symbols and letters represent similar things in the following drawings, so that once something is defined in one drawing, it need not be further discussed in subsequent drawings. <Hardware configuration>

[0029] FIG. 1 is a schematic diagram of an electronic device 1000 capable of implementing an embodiment of the present disclosure.

[0030] The electronic device 1000 may be a smartphone, a portable computer, a desktop computer, a tablet computer, a server, etc., but is not limited thereto.

[0031] The electronic device 1000 includes, but is not limited to, a processor 1100, a memory 1200, an interface device 1300, a communication device 1400, a display device 1500, an input device 1600, a speaker 1700, a microphone 1800, and the like. Here, the processor 1100 may be a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MCU), or the like that executes a computer program. The computer program may be written in an instruction set of an architecture such as x86, Arm, RISC, MIPS, or SSE. The memory 1200 may include, for example, a read-only memory (ROM), a random access memory (RAM), a non-volatile memory such as a hard disk, and the like. The interface device 1300 may include, for example, a USB interface, a serial interface, a parallel interface, and the like. The communication device 1400 may perform wired communication using, for example, optical fiber or cable, or wireless communication, and may specifically include Wi-Fi communication, Bluetooth (registered trademark) communication, 2G / 3G / 4G / 5G communication, and the like. The display device 1500 is, for example, a liquid crystal display, a touch display, etc. The input device 1600 may include, for example, a touch screen, a keyboard, a sensory input device, etc. The speaker 1700 outputs an audio signal. The microphone 1800 collects an audio signal.

[0032] When applied to an embodiment of the present disclosure, the memory 1200 of the electronic device 1000 stores a computer program that controls and operates the processor 1100 to implement a method according to an embodiment of the present disclosure. A person skilled in the art can design the computer program according to the technical means disclosed in the present disclosure. How the computer program controls and operates the processor is well known in the art, and therefore will not be described in detail here. The electronic device 1000 may be installed with a smart operating system (e.g., a system such as Windows®, Linux®, Android®, or IOS®) and application software.

[0033] Those skilled in the art should understand that although FIG. 1 shows multiple devices of the electronic device 1000, the electronic device 1000 of an embodiment of the present disclosure may relate to only some of the devices, such as the processor 1100 and the memory 1200.

[0034] Hereinafter, embodiments and examples of the present invention will be described with reference to the drawings. <Example of the method>

[0035] 2 is a flowchart of an ECU upgrade method according to an embodiment of the present invention, which is implemented by, for example, the electronic device 1000 shown in FIG.

[0036] In detail, the ECU upgrade device for executing the ECU upgrade method may be installed in a host computer, and the software program for realizing the ECU upgrade method may be installed in the host computer as a general-purpose ECU upgrade tool, which may be a personal computer or the like.

[0037] In this way, the host computer can use the general-purpose ECU upgrade tool to perform upgrade processing on the application program of the ECU of the vehicle slave computer, thereby achieving the expected upgrade effects such as bug fixes, device additions, etc. As can be seen from the above, the introduction of ECU upgrade functionality has played a major role in promoting the development of automotive ECUs and is an essential tool for automotive ECUs.

[0038] Specifically, the ECU upgrade can be realized based on communication over a CAN (controller area network) bus. Thus, in a possible implementation, the host computer can realize the upgrade process for the vehicle ECU through a USB-CAN interface card.

[0039] The CAN bus protocol is a standard bus protocol for automotive computer control systems and embedded industrial control local area networks. The automotive CAN bus belongs to the in-vehicle bus network of C-class automobiles. C-class networks are used in systems with high requirements for high speed, real-time performance, and reliability, and generally operate at speeds of 500 kbps or higher.

[0040] In particular, the automotive ECU may have two CAN IDs to receive diagnostic messages, one physical addressing ID and one functional addressing ID, and a standard addressing scheme may be used to apply the diagnostic messages.

[0041] In this way, the host computer and the slave computers can transmit data via the CAN network according to the communication protocol flow. Specifically, data exchange is realized between the slave computer ECU and the host computer's general-purpose ECU upgrade tool through the protocol service, and the application program of the slave computer ECU is finally upgraded.

[0042] Possibly, the communication protocol on which the upgrade process is based may be the ISO 15765 protocol. The ISO 15765 protocol, a communication standard based on road vehicle Controller Area Network (CAN) diagnostic systems, is a standard protocol in the automotive industry.

[0043] In detail, the ISO15765 architecture may include, in order, an application layer (e.g., corresponding to a diagnostic application), a network layer, a data link layer, and a physical layer, where communication in the network layer complies with ISO15765-2 and communication in the application layer complies with ISO15765-3.

[0044] In detail, ISO15765-2 defines two communication methods: single-frame transmission and multi-frame transmission. For example, when fewer than eight valid data items are transmitted during communication between a slave computer and an ECU, single-frame transmission can be used. When eight or more valid data items are transmitted, multi-frame transmission can be used, with the first frame, flow control frame, and subsequent frames being used in that order. As an important part of CAN communication software design, automotive ECUs must analyze these received messages to obtain complete diagnostic services.

[0045] In particular, ISO15765-3 defines a refresh program process and related diagnostic services, which are used when a slave computer refreshes an in-vehicle ECU.

[0046] Specifically, a bootloader may be fixed in the ECU. The bootloader is a boot load and may run before the operating system kernel runs. Based on this, a generic ECU upgrade tool in the host computer may communicate with the bootloader in the slave computer to complete the ECU upgrade operation in the slave computer.

[0047] Based on the above, as shown in FIG. 2, the ECU upgrade method of this embodiment may include the following steps S210 to S240.

[0048] In step S210, the set first encapsulated file is obtained, and the first vehicle model information and the first upgrade content related information corresponding to the first vehicle model information are encapsulated in the first encapsulated file.

[0049] Specifically, to accommodate different vehicle models and changing demands, developers can develop corresponding upgrade content-related information, which may include information such as upgrade content and upgrade parameters.

[0050] Developers can develop upgrade content and upgrade parameter information by combining it with the original ECU application program file. Possible upgrade parameters include physical addressing ID, function addressing ID, response ID, write key, CAN bus baud rate, etc. Possible upgrade content may include project chip information, project code, vehicle model key, etc.

[0051] In detail, vehicle fault diagnosis, as a technology to ensure the safety and maintainability of automobiles, has become increasingly important in the development of automotive electronics, and considering that diagnostic services are widely applied to automotive ECUs, developers can design a universal ECU upgrade tool based on the diagnostic protocol.

[0052] In particular, the general-purpose ECU upgrade tool of this embodiment relates to, for example, a basic upgrade module, a development module, and a test module, and can integrate these modules together.

[0053] Developers can develop upgrade information based on the development module, and Tasker can upgrade the ECU based on the basic upgrade module. In developer mode, upgrade testing can be performed based on the test module, and if the test results are as expected, the system can switch to normal mode. When upgrading an ECU in normal mode, testing is not required.

[0054] Specifically, different users can be granted different required functions based on authorization techniques. For example, in developer mode, a related developer is granted authorization to the base upgrade module, development module, test module, and external development configuration folder, and can use each module with the granted authorization. In normal mode, a related developer is granted authorization to the base upgrade module, and can use this module with the granted authorization, but is not granted authorization to the development module, test module, and external development configuration folder. The developer can store developed content in the external development configuration folder.

[0055] In this embodiment, authorization technologies are combined to open corresponding functions to different user groups, and the security and confidentiality of the software are maximized. In this way, this embodiment not only facilitates development and testing by automotive electronics R&D engineers, simplifies upgrade operations, and effectively prevents incorrect upgrades, but also plays an important role in subsequent system upgrades and maintenance.

[0056] To avoid the need for the tasker in charge of the upgrade operation to know the specific details of the upgrade content-related information and to facilitate accurate transmission of the upgrade content-related information, the upgrade content-related information and the corresponding vehicle model information may be encapsulated into a comprehensive encapsulation file by a secondary encapsulation tool, so that the corresponding ECU upgrade goal can be achieved by simply introducing the encapsulation file based on the general-purpose ECU upgrade tool.

[0057] Based on this, in one embodiment of the present disclosure, before obtaining the set first encapsulated file, the above method may further include the following steps A1 to A3.

[0058] In step A1, if the current upgrade mode corresponds to the developer mode, the first vehicle model information is acquired in response to a selection operation corresponding to the first vehicle model information.

[0059] Specifically, in the developer mode, the developer can develop and design information related to upgrade content through the development module of the general-purpose ECU upgrade tool. For example, when a new vehicle model or a change in ECU demand for an existing vehicle model occurs, the developer can develop and design corresponding information related to upgrade content. In this way, the developer selects vehicle model information on the upgrade tool operation screen, and the ECU upgrade device can acquire the selected vehicle model information accordingly.

[0060] In step A2, the first upgrade content related information is acquired in response to an operation for editing the upgrade content related information.

[0061] In this step, the developer can edit the information related to the upgrade content, and the ECU upgrade device can obtain the corresponding information related to the upgrade content, such as information on the upgrade content and upgrade parameters.

[0062] In step A3, in response to a setting encapsulation command corresponding to the first vehicle model information, an encapsulation process is performed on the first vehicle model information and the first upgrade content related information to obtain the first encapsulated file.

[0063] Specifically, a secondary encapsulation tool is used to encapsulate the vehicle model information and the corresponding upgrade content information together. During the encapsulation process, the key information contained therein can be encrypted to prevent leakage of the key information. For example, a .zck file can be generated by the secondary encapsulation.

[0064] In this embodiment, the vehicle model information and the upgrade content related information are encapsulated in advance to obtain an encapsulated file, so that the ECU upgrade process can be performed based on the direct introduction of the encapsulated file.

[0065] The development of the upgrade content-related information can generally be repeated multiple times. To facilitate obtaining an encapsulation file based on the latest information, the developed upgrade content-related information can be stored and updated in a remote server each time. When an encapsulation process needs to be performed, the related information can be automatically updated and loaded from the remote server to complete the encapsulation operation.

[0066] Based on this, in one embodiment of the present disclosure, after obtaining the first upgrade content related information, the method may further include the following steps B1 to B4.

[0067] In step B1, a mapping relationship between the first vehicle model information and the first upgrade content related information is stored in a remote server.

[0068] In this step, all the information related to the upgrade content developed by each developer is stored in the remote server in real time, realizing the effect of real-time and batch update of information.

[0069] In step B2, the first vehicle model information is acquired in response to a selection operation corresponding to the first vehicle model information.

[0070] In particular, in the developer mode, the developer can perform encapsulation operations through the development module of the general-purpose ECU upgrade tool. For example, the developer selects vehicle model information on the upgrade tool operation screen, and the ECU upgrade device can obtain the selected vehicle model information accordingly.

[0071] In step B3, the first upgrade content related information corresponding to the first vehicle model information is obtained from the remote server.

[0072] In this step, the upgrade content related information corresponding to the selected vehicle model can be automatically updated and loaded from a remote server for encapsulation.

[0073] In step B4, based on the acquired first upgrade content related information, in response to the setting encapsulation command corresponding to the first vehicle model information, an encapsulation process is performed on the first vehicle model information and the first upgrade content related information to acquire the first encapsulated file.

[0074] Specifically, an encapsulation process can be performed based on the automatically loaded upgrade content-related information to obtain an encapsulated file, which can be used in the ECU upgrade process in developer mode and normal mode.

[0075] In step S220, the first vehicle model information and the first upgrade content related information are obtained based on the first encapsulated file.

[0076] In this step, the basic upgrade module of the general-purpose ECU upgrade tool performs information binding on the imported encapsulated file, thereby obtaining the vehicle model information and upgrade content-related information contained therein.

[0077] In step S230, first upgrade process related information corresponding to the first vehicle model information is obtained from the configuration memory based on the first vehicle model information.

[0078] In particular, the upgrade process related information may include information about the upgrade process and an upgrade key.

[0079] In this step, the basic upgrade module of the general-purpose ECU upgrade tool can obtain upgrade process related information corresponding to the vehicle model information from the configuration memory.

[0080] Specifically, the configuration memory stores a comprehensive database of upgrade process-related information, such as a comprehensive database of upgrade processes for each vehicle model and a comprehensive database of key algorithms. In a possible implementation, these comprehensive databases can be downloaded from the configuration memory, and the vehicle model information obtained by binding can be used to query the corresponding upgrade process and upgrade key information, and the upgrade process can be performed based on this.

[0081] In detail, when there are situations such as new vehicle models or changes in ECU demand for existing vehicle models, developers can use the development module of the general-purpose ECU upgrade tool to develop and design information related to the upgrade process.

[0082] To facilitate the execution of the upgrade process at different stages, the upgrade process related information at different stages may be stored in different memories, preferably in a local memory, for example, in a configured external folder, in the developer mode, and in a remote server in the normal mode.

[0083] Thus, in one embodiment of the present disclosure, the step of obtaining the first upgrade process related information corresponding to the first vehicle model information from the configuration memory may include the following step C1 or step C2.

[0084] In step C1, if the current upgrade mode corresponds to the developer mode, obtain first upgrade process related information corresponding to the first vehicle model information stored in a local memory, which stores a setting mapping relationship between the vehicle model information and the upgrade process related information.

[0085] In detail, in the developer mode, the setting mapping relationship is downloaded from the local memory, for example, from a set external folder, and the corresponding upgrade process related information is queried based on the vehicle model information obtained by binding, and the ECU upgrade process in the developer mode can be performed based on this.

[0086] Thus, in one embodiment of the present disclosure, before obtaining the first upgrade process related information corresponding to the first vehicle model information stored in the local memory, the method may further include the following steps D1 to D3.

[0087] In step D1, if the current upgrade mode corresponds to the developer mode, the first vehicle model information is acquired in response to a selection operation corresponding to the first vehicle model information.

[0088] Specifically, in the developer mode, the developer can use the development module of the general-purpose ECU upgrade tool to develop and design information related to the upgrade process. For example, when a new vehicle model or a change in the ECU requirements of an existing vehicle model occurs, the developer can develop and design the corresponding information related to the upgrade process. In this way, the developer selects vehicle model information on the upgrade tool operation screen, and the ECU upgrade device can acquire the selected vehicle model information accordingly.

[0089] In step D2, in response to an operation for editing the upgrade process related information, the corresponding upgrade process related information is obtained.

[0090] In this step, the developer can edit the information related to the upgrade process, and the ECU upgrade device can obtain the corresponding information related to the upgrade process, such as information about the upgrade process and the upgrade key.

[0091] In step D3, a mapping relationship is established between the first vehicle model information and the acquired upgrade process related information, and the established mapping relationship is stored in the local memory.

[0092] To facilitate the ECU upgrade process in developer mode, compiled upgrade process related information may be stored in local memory.

[0093] For example, considering that the general-purpose ECU upgrade tool of the host computer mainly communicates with the bootloader of the slave computer to complete the ECU upgrade process, in developer mode, the bootloader engineer of the slave computer can edit the ECU upgrade process information and key algorithms for the new vehicle model in an external folder according to the configuration file format specification and store the edited results in the external folder. In this way, during the corresponding upgrade process, the upgrade process is performed by obtaining the upgrade process-related information from the external configuration folder. This implementation method can facilitate the development and debugging work of the bootloader engineer.

[0094] As can be seen, in the developer mode, developers only need to edit the process file and key algorithm file to complete the ECU upgrade development work for new vehicle models.

[0095] Furthermore, once the ECU upgrade process in developer mode has been successfully completed and the ECU upgrade process can be carried out in normal mode, i.e., after the configuration files for the developed information related to each upgrade process have been debugged and determined, the configuration files can be uploaded to a comprehensive database, for example, on a remote server, and the development and design of the upgrade tool for the new vehicle model can be completed, allowing the ECU upgrade process to be carried out in normal mode.

[0096] In step C2, if the current upgrade mode does not correspond to the developer mode, obtain first upgrade process related information corresponding to the first vehicle model information stored in a remote server, which stores a setting mapping relationship between the vehicle model information and the upgrade process related information.

[0097] In detail, in the normal mode, the setting mapping relationship is downloaded from the remote server, and the corresponding upgrade process related information is queried based on the vehicle model information obtained by binding, and the ECU upgrade process in the normal mode can be performed based on this.

[0098] In step S240, an ECU upgrade process is performed on the vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information.

[0099] In detail, the general-purpose ECU upgrade tool extracts upgrade process-related information, obtains upgrade content-related information, and then automatically configures an upgrade communication flow, based on which the ECU upgrade process can be performed to update and upgrade the application program of the ECU.

[0100] Through testing, it has been found that the upgrade method of this embodiment can be adapted to different vehicle models by introducing different target files, and the upgrade content can be smoothly downloaded to the vehicle's ECU according to the corresponding upgrade process. After the download is complete, the ECU is powered on again, and the new program is loaded and runs smoothly.

[0101] As can be seen from the above, the ECU upgrade method according to this embodiment acquires a pre-defined first encapsulated file, which encapsulates first vehicle model information and first upgrade content-related information corresponding to the first vehicle model information. The first vehicle model information and the first upgrade content-related information are acquired based on the first encapsulated file. Based on the first vehicle model information, first upgrade process-related information corresponding to the first vehicle model information is acquired from the configuration memory. Based on the first upgrade process-related information and the first upgrade content-related information, an ECU upgrade process is performed on a vehicle having the first vehicle model information. As can be seen from the above, the introduction of an encapsulated file encapsulating vehicle model information and corresponding upgrade content-related information makes it possible to address a variety of vehicle models and upgrade needs. This embodiment acquires upgrade content-related information and upgrade process-related information corresponding to a vehicle model based on the encapsulated file, and then performs an ECU upgrade on the vehicle of that vehicle model based on the information. This universal upgrade method is applicable to ECU upgrades for various vehicle models and various upgrade needs, eliminating the need for duplication of intentional upgrade program design, thereby improving the overall upgrade effect.

[0102] As described above, a test can be performed when performing the ECU upgrade process in developer mode, and if the test passes, the ECU upgrade process can be performed in normal mode.

[0103] Based on this, in one embodiment of the present disclosure, step S240 of performing ECU upgrade processing on a vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information may include a step of performing ECU upgrade processing on a vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information and the set test abnormality situation when the current upgrade mode corresponds to the developer mode.

[0104] Specifically, the ECU upgrade test can be performed in developer mode based on the test mode of the universal ECU upgrade tool, where the test module simulates abnormal situations during the ECU upgrade process and tests the operation of the ECU, including the bootloader program, based on the simulated abnormal situations.

[0105] Possibly, the test abnormal conditions may include abnormal messages, error check codes, high CAN bus load, continuous writes, and the like.

[0106] Accordingly, after performing the ECU upgrade process on the vehicle having the first vehicle model information based on the set test abnormality situation, the method may further include the following steps E1 to E3.

[0107] In step E1, a first upgrade result is obtained.

[0108] By performing an upgrade test under a set test abnormal situation, the corresponding upgrade result can be obtained, and the upgrade result can be compared with the expected upgrade result to determine whether the upgrade process is performed as expected.

[0109] In step E2, it is determined whether the first upgrade result is the same as the setting upgrade result corresponding to the test abnormal situation.

[0110] In this step, the consistency between the actual upgrade result and the expected upgrade result can be determined. If the information developed by the developer is correct, the consistency result can generally be obtained, and conversely, the developer can make operations such as adjusting the development information as necessary.

[0111] In step E3, if the first upgrade result is the same as the configuration upgrade result, the configuration mapping relationship stored in the local memory is stored in the remote server.

[0112] In this step, after obtaining the consistency result, the information developed by the developer is stored in the remote server, so that when performing ECU upgrade in normal mode, the corresponding information can be obtained from the remote server.

[0113] Unlike the developer mode, when performing an ECU upgrade in the normal mode, there is no need to perform an upgrade test. In this way, in the normal mode, the upgrade process can be directly performed based on the upgrade process-related information and the upgrade content-related information, as described in step S240 above.

[0114] As can be seen from the above, the ECU upgrading method according to this embodiment can have at least the following features.

[0115] (1) Applicable to various vehicle models. Compared to traditional intentional upgrade tools, one vehicle model corresponds to at least one upgrade tool, which makes the development and design work complicated and requires a large amount of repetitive work, resulting in high development costs, a long development cycle, and is unfavorable for the effective use of resources. In contrast, this embodiment provides a universal ECU upgrade tool that can be used for almost all vehicle models designed according to the ISO 15765 protocol. In this way, there is no need to duplicate the development work of the ECU upgrade tool. This, of course, reduces the steps and various costs required to update application software.

[0116] (2) The upgrade process is flexible and allows for secondary expansion. In conventional intentional upgrade tools, the upgrade process and parameter information are fixed, so if the upgrade process information or parameter information needs to be changed during the entire project due to changes in the overall system allocation or customer demand, the software source code needs to be modified and redistributed, and after multiple debugging and testing of the bootloader slave computer or the interaction between the system and other parts, the response time is long and it is difficult to adapt to new changes. In contrast, the general-purpose ECU upgrade tool according to this embodiment has the feature of customization, and can customize the user screen language, tool, and specific upgrade process of the ECU device to be upgraded according to the upgrade needs, thereby realizing all the upgrade functions defined in the requirement document of the ECU device to be upgraded.

[0117] (3) The complexity of software upgrade operations is low. Compared with conventional manual upgrade tools, when upgrading ECUs of different vehicle models, it is necessary to switch between different tools and the user needs to input upgrade information, which makes the operation more complicated. In contrast, the general-purpose ECU upgrade tool of this embodiment can complete the bulk upgrade by introducing only one encapsulated file during the upgrade operation using its normal upgrade module.

[0118] (4) Wider functional coverage. In contrast to traditional intentional upgrade tools, due to factors such as project planning or user initial planning omissions, some auxiliary analysis and testing functions, such as local data storage and the use of diversified CAN devices, are missing, which is detrimental to efficient system project testing. In contrast, the general-purpose ECU upgrade tool of this embodiment has a wide range of functions and integrates upgrade, testing, and development functions, resulting in high human-machine interactivity. In particular, when used by a bootloader slave computer development engineer, this tool can be used conveniently and quickly to flexibly configure the process and complete the development work of the slave computer.

[0119] (5) Easy to develop. The general-purpose ECU upgrade tool according to this embodiment provides maximum convenience for developers of slave computer bootloaders to perform personalized configurations and reduces the development work of the upgrade tool. In contrast, with traditional intentional upgrade tools, when introducing a new project, developers need to develop the project from the beginning, which requires a lot of time and effort in the development process from tool design, encoding realization to debugging and distribution.

[0120] (6) It reduces the level of user operation and makes it easier to manage. Unlike traditional manual upgrade tools, technicians must pay attention to the accuracy of the upgrade operation and the upgrade tool at the station, and must also manage each upgrade tool. Upgrade operation errors include inaccurate upgrade information entered during operation. Upgrade tool errors are caused by the increased difficulty of upgrading tools due to the upgrade needs of different vehicle models. In some serious upgrade error situations, components must be removed from the entire vehicle and then the program must be updated via the debug port. This increases the workload and is likely to damage the vehicle itself. Furthermore, upgrades for different vehicle models require the use of different upgrade tools, and different ECUs for the same vehicle model require different versions of the tools, making upgrade tool management more difficult and increasing the number of errors during use by each user department of the automaker. In contrast, the generic ECU upgrade tool according to this embodiment is applicable to a wide range of vehicle models, has easy-to-operate software, and has a single version, significantly reducing the requirements for user operation level. When using the generic ECU upgrade tool, by linking to a remote server, the latest and most complete information can be updated locally, eliminating the need for cumbersome version management work for the ECU upgrade tool.

[0121] (7) High user experience. The design method of the universal ECU upgrade tool according to this embodiment adheres to the user-centric design principle, taking into consideration several aspects of user experience, including system response time, error information processing method, user command method, and user interface language. The tool is highly customizable and extensible, greatly enhancing flexibility in responding to situations such as development, debugging, problem investigation, maintenance, and demand changes, effectively meeting user needs. The universal ECU upgrade tool not only improves work efficiency, but also saves more labor and material costs.

[0122] (8) Safe and reliable. The universal ECU upgrade tool of this embodiment includes a basic upgrade module, a development module, and a test module, and these modules can be integrated into one. In this embodiment, authorization technologies are combined to open up corresponding functions to different user groups, thereby maximizing software security and confidentiality. This embodiment not only facilitates development and testing by automotive electronics R&D, simplifies upgrade operations, and effectively prevents incorrect upgrades, but also plays an important role in subsequent system upgrades and maintenance.

[0123] (9) Meet market demand. This embodiment provides a general-purpose, integrated ECU upgrade tool that adapts to the development of automotive diagnostic technology, meets the market development trend, and has great significance and value in the reliability, accuracy, and stability of automotive ECU upgrade tools.

[0124] (10) It is easy to develop products. The universal ECU upgrade tool of this embodiment is highly flexible, safe, and reliable. Automobile manufacturers can use the universal ECU upgrade tool to quickly expand new upgrade process specifications and apply the tool to different controllers in different vehicle models. This avoids reinventing the wheel for automakers and key customers, reducing product development difficulty, development cycles, and development and management costs, while also improving product development efficiency and product quality and stability.

[0125] 3 is a flowchart of an ECU upgrade method according to an embodiment of the present invention, which may be implemented by the electronic device 1000 shown in FIG.

[0126] As shown in FIG. 3, the method of this embodiment may include the following steps S301 to S319.

[0127] In step S301, if the current upgrade mode corresponds to the developer mode, the first vehicle model information is acquired in response to a selection operation corresponding to the first vehicle model information.

[0128] In step S302, in response to an operation to edit the upgrade content related information, first upgrade content related information corresponding to the first vehicle model information is acquired.

[0129] In step S303, the mapping relationship between the first vehicle model information and the first upgrade content related information is stored in a remote server.

[0130] In step S304, the first vehicle model information is acquired in response to a selection operation corresponding to the first vehicle model information.

[0131] In step S305, the first upgrade content related information corresponding to the first vehicle model information is obtained from the remote server.

[0132] In step S306, based on the acquired first upgrade content related information, in response to a setting encapsulation command corresponding to the first vehicle model information, an encapsulation process is performed on the first vehicle model information and the first upgrade content related information to obtain a first encapsulated file.

[0133] In step S307, if the current upgrade mode corresponds to the developer mode, the first vehicle model information is acquired in response to a selection operation corresponding to the first vehicle model information.

[0134] In step S308, in response to an operation to edit the upgrade process related information, first upgrade process related information corresponding to the first vehicle model information is obtained.

[0135] In step S309, a mapping relationship between the first vehicle model information and the first upgrade process related information is established, and the established mapping relationship is stored in the local memory.

[0136] In step S310, the first encapsulated file is obtained.

[0137] In step S311, the first vehicle model information and the first upgrade content related information are obtained based on the first encapsulated file.

[0138] In step S312, if the current upgrade mode corresponds to the developer mode according to the first vehicle model information, the first upgrade process related information stored in the local memory is obtained.

[0139] In step S313, based on the first upgrade process related information, the first upgrade content related information, and the set test abnormality conditions, an ECU upgrade process is performed on the vehicle having the first vehicle model information, and a first upgrade result is obtained.

[0140] In step S314, it is determined whether the first upgrade result is the same as the setting upgrade result corresponding to the test abnormal situation.

[0141] In step S315, if the first upgrade result is the same as the configuration upgrade result, the configuration mapping relationship stored in the local memory is stored in the remote server.

[0142] In step S316, the first encapsulated file is obtained.

[0143] In step S317, the first vehicle model information and the first upgrade content related information are obtained based on the first encapsulated file.

[0144] In step S318, if the current upgrade mode does not correspond to the developer mode based on the first vehicle model information, obtain first upgrade process related information corresponding to the first vehicle model information stored in the remote server.

[0145] In step S319, an ECU upgrade process is performed on the vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information. <Device Example>

[0146] 4 is a principle block diagram of an ECU upgrade device 400 according to an embodiment. As shown in FIG. 4, the ECU upgrade device 400 may include a first acquisition module 410, a second acquisition module 420, a third acquisition module 430, and a processing module 440.

[0147] The first acquisition module 410 acquires a set first encapsulated file. The first encapsulated file encapsulates first vehicle model information and first upgrade content-related information corresponding to the first vehicle model information. The second acquisition module 420 acquires the first vehicle model information and the first upgrade content-related information based on the first encapsulated file. The third acquisition module 430 acquires first upgrade process-related information corresponding to the first vehicle model information from a configuration memory based on the first vehicle model information. The processing module 440 performs an ECU upgrade process for a vehicle having the first vehicle model information based on the first upgrade process-related information and the first upgrade content-related information.

[0148] The ECU upgrade device 400 may be the electronic device 1000 shown in FIG.

[0149] In this embodiment, a first encapsulated file is acquired, which encapsulates first vehicle model information and first upgrade content-related information corresponding to the first vehicle model information. The first vehicle model information and first upgrade content-related information are acquired based on the first encapsulated file. The first upgrade process-related information corresponding to the first vehicle model information is acquired from the configuration memory based on the first vehicle model information. An ECU upgrade process is performed for a vehicle having the first vehicle model information based on the first upgrade process-related information and the first upgrade content-related information. As can be seen, the introduction of an encapsulated file containing vehicle model information and corresponding upgrade content-related information can address the diverse vehicle models and upgrade needs. This embodiment acquires upgrade content-related information and upgrade process-related information corresponding to a vehicle model based on the encapsulated file, and then performs an ECU upgrade for the vehicle of that vehicle model based on the information. This universal upgrade method can be applied to ECU upgrades for various vehicle models and various upgrade needs, eliminating the need for duplication of intentional upgrade program design, thereby improving the overall upgrade effect.

[0150] In one embodiment of the present disclosure, the third acquisition module 430 acquires the first upgrade process related information stored in the local memory corresponding to the first vehicle model information if the current upgrade mode corresponds to the developer mode, and acquires the first upgrade process related information stored in the remote server corresponding to the first vehicle model information if the current upgrade mode does not correspond to the developer mode. Both the local memory and the remote server store a configuration mapping relationship between vehicle model information and upgrade process related information.

[0151] In one embodiment of the present disclosure, when the current upgrade mode corresponds to the developer mode, the ECU upgrade device 400 may further include: a module for acquiring the first vehicle model information in response to a selection operation corresponding to the first vehicle model information; a module for acquiring corresponding upgrade process related information in response to an operation for editing the upgrade process related information; and a module for constructing a mapping relationship between the first vehicle model information and the acquired upgrade process related information and storing the constructed mapping relationship in the local memory.

[0152] In one embodiment of the present disclosure, when the current upgrade mode corresponds to the developer mode, the processing module 440 performs ECU upgrade processing for a vehicle having the first vehicle model information based on the first upgrade process related information, the first upgrade content related information, and the set test abnormality situation.

[0153] The ECU upgrade device 400 may include a test module that obtains a first upgrade result, determines whether the first upgrade result is the same as a configuration upgrade result corresponding to the test abnormal situation, and stores the configuration mapping relationship stored in the local memory in the remote server if the first upgrade result is the same as the configuration upgrade result.

[0154] In one embodiment of the present disclosure, when the current upgrade mode corresponds to the developer mode, the ECU upgrade device 400 may further include a module for acquiring the first vehicle model information in response to a selection operation corresponding to the first vehicle model information, a module for acquiring the first upgrade content related information in response to an operation to edit upgrade content related information, and a module for performing an encapsulation process on the first vehicle model information and the first upgrade content related information in response to a setting encapsulation command corresponding to the first vehicle model information, to acquire the first encapsulated file.

[0155] In one embodiment of the present disclosure, the ECU upgrade device 400 may further include a module for storing a mapping relationship between the first vehicle model information and the first upgrade content related information in a remote server, a module for acquiring the first vehicle model information in response to a selection operation corresponding to the first vehicle model information, and a module for acquiring the first upgrade content related information corresponding to the first vehicle model information from the remote server.

[0156] FIG. 5 is a schematic diagram of the hardware configuration of an ECU upgrading device 500 according to another embodiment.

[0157] 5, the ECU upgrade device 500 includes a processor 510 and a memory 520. The memory 520 stores an executable computer program. The processor 510 executes any of the above method embodiments under the control of the computer program.

[0158] The ECU upgrade device 500 may be the electronic device 1000 shown in FIG.

[0159] Each module of the ECU upgrade device 500 described above may be realized by the processor 510 in this embodiment executing a computer program stored in the memory 520, or may be realized by other circuit configurations, which are not limited here.

[0160] This embodiment also provides an ECU upgrade system. As shown in the figure, Fig. 6 is a principle block diagram of an ECU upgrade system 600 according to one embodiment. The ECU upgrade system 600 includes a host computer 610 and a vehicle 620. The host computer 610 includes an ECU upgrade device according to any one of the embodiments of the present disclosure, and the vehicle 620 includes an ECU.

[0161] In this way, the host computer, with the included ECU upgrade device, can perform the upgrade process on the ECU of the vehicle, which may be any type of vehicle.

[0162] The present invention may be a system, a method and / or a computer program product, which may include a computer-readable storage medium having stored thereon computer-readable program instructions for causing a processor to implement aspects of the present invention.

[0163] A computer-readable storage medium may be a tangible device capable of retaining and storing instructions for use by an instruction execution device. A computer-readable storage medium may be, for example, but is not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanically encoded devices such as punch cards or protrusion structures in grooves on which instructions are stored, and any suitable combination of the above. As used herein, a computer-readable storage medium is not to be construed as a momentary signal itself, such as, for example, radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted over electrical wires.

[0164] The computer-readable program instructions described herein can be downloaded to each computing / processing device from a computer-readable storage medium, or can be downloaded to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface of each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in the computer-readable storage medium of each computing / processing device.

[0165] The computer-readable program instructions for carrying out the operations of the present invention may be source or object code written in any combination of one or more programming languages, including assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In a remote computer scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider). In some embodiments, the state information of the computer-readable program instructions is used to customize electronic circuitry, such as a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA), that can implement aspects of the present invention by executing the computer-readable program instructions.

[0166] Aspects of the present application will be described with reference to flowcharts and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.

[0167] These computer-readable program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to create a machine, which, when executed by the processor of the computer or other programmable data processing apparatus, creates an apparatus that implements the functions / acts specified in one or more blocks in the flowcharts and / or block diagrams. These computer-readable program instructions may be stored on a computer-readable storage medium, and the instructions direct the computer, programmable data processing apparatus, and / or other device to operate in a particular manner, such that the computer-readable medium on which the instructions are stored includes an article of manufacture containing instructions that implement each aspect of the functions / acts specified in one or more blocks in the flowcharts and / or block diagrams.

[0168] The computer-readable program instructions may be loaded into a computer, other programmable data processing apparatus, or other device and cause the computer, other programmable data processing apparatus, or other device to perform a series of operational steps to create a computer-implemented process, whereby the instructions executing on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in one or more blocks in the flowcharts and / or block diagrams.

[0169] The flowcharts and block diagrams in the figures illustrate possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, program segment, or part of an instruction, which includes one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions represented by the blocks may occur in a different order than that shown in the figures. For example, two blocks shown in succession may, in fact, be executed substantially simultaneously or in the reverse order, depending on the functionality involved. Note that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented in a dedicated hardware-based system that performs the specified function or operation, or in a combination of dedicated hardware and computer instructions. Those skilled in the art will recognize that a hardware implementation, a software implementation, and a combination of software and hardware implementation are all equivalent.

[0170] Although the embodiments of the present invention have been described above, the above description is illustrative and not exhaustive, and is not limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used in this specification is intended to best interpret the principles, practical applications, or technical improvements in the marketplace of the embodiments, or to enable those skilled in the art to understand the embodiments disclosed herein. The scope of the present invention is limited by the appended claims.

Claims

1. A step in which an electronic device acquires a set first encapsulation file, in which first vehicle model information and first upgrade content related information corresponding to the first vehicle model information are encapsulated; The electronic device acquires the first vehicle model information and the first upgrade content related information based on the first encapsulated file; The electronic device acquires first upgrade process related information corresponding to the first vehicle model information from a configuration memory based on the first vehicle model information; the electronic device performs an ECU upgrade process for the vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information; 1. An ECU upgrade method comprising:

2. The first upgrade content related information includes upgrade content and upgrade parameters; The upgrade parameters include a physical addressing identifier ID, a functional addressing ID, a response ID, a write key, and a CAN bus baud rate; The method of claim 1 , wherein the upgrade content includes project chip information, a project code, and a vehicle model key.

3. The step of obtaining first upgrade process related information corresponding to the first vehicle model information from a configuration memory includes: If the current upgrade mode corresponds to a developer mode, the electronic device acquires first upgrade process related information stored in a local memory, the first upgrade process related information corresponding to the first vehicle model information; If the current upgrade mode does not correspond to the developer mode, the electronic device acquires first upgrade process related information stored in a remote server, the first upgrade process related information corresponding to the first vehicle model information; The method of claim 1 , wherein the local memory and the remote server both store a configuration mapping relationship between vehicle model information and upgrade process related information.

4. Before the step of obtaining first upgrade process related information stored in a local memory and corresponding to the first vehicle model information, When the current upgrade mode corresponds to the developer mode, the electronic device acquires the first vehicle model information in response to a selection operation corresponding to the first vehicle model information; The electronic device acquires corresponding upgrade process related information in response to an operation of editing the upgrade process related information; the electronic device constructing a mapping relationship between the first vehicle model information and the acquired upgrade process related information, and storing the constructed mapping relationship in the local memory; 4. The method of claim 3, further comprising:

5. The step of performing an ECU upgrade process on a vehicle having the first vehicle model information based on the first upgrade process related information and the first upgrade content related information includes:

2. The method according to claim 1, further comprising: if the current upgrade mode corresponds to the developer mode, the electronic device simulates a test abnormal situation that occurs during the ECU upgrade process and tests the operation of the ECU based on the simulated abnormal situation.

6. After the step of testing the operation of the ECU, The electronic device performs an upgrade test under the test abnormal condition to obtain a first upgrade result; the electronic device determining whether the first upgrade result is the same as an expected upgrade result; If the first upgrade result is the same as the expected upgrade result, the electronic device stores the setting mapping relationship stored in the local memory in a remote server; 6. The method of claim 5, further comprising:

7. 6. The method of claim 5, wherein the test abnormal conditions include an abnormal message, an error check code, a high CAN bus load, and continuous writes.

8. Before the step of obtaining the first encapsulated file, When the current upgrade mode corresponds to the developer mode, the electronic device acquires the first vehicle model information in response to a selection operation corresponding to the first vehicle model information; The electronic device acquires the first upgrade content-related information in response to an operation of editing the upgrade content-related information; the electronic device performs an encapsulation process on the first vehicle model information and the first upgrade content related information in response to a setting encapsulation command corresponding to the first vehicle model information to obtain the first encapsulated file; The method of claim 1 further comprising:

9. After the step of obtaining the first upgrade content related information, the electronic device storing a mapping relationship between the first vehicle model information and the first upgrade content related information in a remote server; acquiring the first vehicle model information by the electronic device in response to a selection operation corresponding to the first vehicle model information; The electronic device acquires the first upgrade content related information corresponding to the first vehicle model information from the remote server; the electronic device executes a step of performing an encapsulation process on the first vehicle model information and the first upgrade content related information based on the acquired first upgrade content related information in response to a setting encapsulation command corresponding to the first vehicle model information, to acquire the first encapsulated file; 9. The method of claim 8, further comprising:

10. An ECU upgrade device (500) comprising a memory (520) and a processor (510), wherein the memory (520) stores a computer program, and the processor (510) executes the computer program to implement the method according to any one of claims 1 to 9.

11. A host computer (610) and a vehicle (620) are included. The host computer (610) includes the ECU upgrade device (500) according to claim 10, The ECU upgrade system (600) is characterized in that the vehicle (620) includes an ECU.

12. A computer-readable storage medium having stored thereon a computer program that causes a processor to implement the method according to any one of claims 1 to 9.

Images