ECU (Electronic Control Unit) flashing inspection method, equipment and medium
By conducting detailed inspections and status diagnosis of the ECU, the accuracy and safety of the flashing process are ensured, and the problems of cumbersome and uncertain operation of traditional ECU maintenance methods are solved, which significantly improves the success rate and quality of the ECU flashing.
Patent Information
- Application Number
- CN202411694216.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-25
- Publication Date
- 2025-03-14
AI Technical Summary
Traditional ECU maintenance methods are cumbersome and time-consuming, which can easily cause damage to the ECU or related components. Fault diagnosis depends on the experience and skills of technicians, and there is great subjectivity and uncertainty.
A method for checking ECU flash writing is proposed. By reading outgoing messages from the ECU, using a predetermined flashing device for diagnosis, determining the operating status of the ECU, and conducting a comprehensive inspection of the ECU based on the set inspection items to ensure the accuracy and safety of the flashing process.
Through accurate ECU status diagnosis and detailed inspection items, we ensure that the flashing operation is carried out at the right time, avoid flashing failure or equipment damage, improve the safety and reliability of flashing, and significantly improve the success rate and quality of ECU flashing.
Smart Images

Figure CN119621415A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a method, device and medium for checking ECU flashing. Background Art
[0002] Electronic Control Unit (ECU), also known as on-board computer, consists of a microcontroller and peripheral circuits. As the core control component of the car, ECU is responsible for monitoring and managing the operation of key components such as the engine, transmission system, chassis, etc. It receives input signals from sensors, and outputs control instructions through actuators after calculation and processing, thereby achieving precise control of various systems of the car. With the continuous advancement of automotive electronic technology, the functions of ECU are becoming increasingly complex and powerful, and higher requirements are also placed on the maintenance and updating of ECU. Traditional ECU maintenance methods usually include steps such as disassembling ECU, using special equipment for fault diagnosis, and data flashing. This method is not only cumbersome and time-consuming, but also easy to cause damage to ECU or related components during disassembly and installation. In addition, the traditional method of fault diagnosis often relies on the experience and skill level of technicians, which is highly subjective and uncertain. Summary of the invention
[0003] In order to solve the above problems, the present application proposes a method for checking ECU flashing, comprising: reading the ECU to determine the outgoing message of the ECU, diagnosing the outgoing message through a predetermined flashing device to determine the operating state of the ECU; determining pre-set inspection items, and inspecting the ECU according to the inspection items to determine multiple inspection results; determining the flashing process of the ECU according to the multiple inspection results, and flashing the ECU according to the flashing process.
[0004] In one example, the ECU is checked according to the check items, specifically including: determining the flash data, and performing a format check on the flash data according to a preset format requirement; if the format of the flash data is wrong, exiting the check.
[0005] In one example, the ECU is inspected according to the inspection items, which specifically includes: determining the data of the ECU, comparing the data of the ECU with the flash data, and if the comparison result between the data of the ECU and the flash data is inconsistent, exiting the inspection.
[0006] In one example, the ECU is inspected according to the inspection items, specifically including: determining the flash writing baud rate and the ECU baud rate, and verifying the flash writing baud rate and the ECU baud rate to make the baud rate of the baud rate flash writing be consistent with the ECU baud rate; if the baud rate flash writing baud rate is inconsistent with the ECU baud rate, refreshing the flash writing baud rate.
[0007] In one example, the ECU is inspected according to the inspection items, which specifically also includes: determining a flash file, verifying the flash file according to a preset verification standard, and if the flash file is an error file, replacing the error file; determining whether the flash file in use does not match, and if the flash file in use does not match, rolling back the flash program to the previous version.
[0008] In one example, the ECU is inspected according to the inspection items, which specifically also includes: determining the BT version number of the ECU, matching the flashing program according to the BT version number, and if the BT version number does not match the flashing program, upgrading the BT file; determining whether the BT version number in use does not match, and if the BT version number in use does not match, rolling back the flashing program to the previous version.
[0009] In one example, the ECU is checked according to the check items, which specifically includes: determining the rotation speed of the vehicle, judging whether the rotation speed is zero, and if the rotation speed is zero, continuing to execute the flashing program.
[0010] In one example, the method further includes: determining whether the ECU has entered the flashing process; if the ECU has not entered the flashing process, resetting the ECU and determining whether the reset ECU has entered process control; if the ECU has entered process control, flashing the ECU.
[0011] On the other hand, the present application also proposes an ECU flash inspection device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the ECU flash inspection device can perform: reading the ECU to determine the outgoing message of the ECU, diagnosing the outgoing message through a predetermined flash device to determine the operating state of the ECU; determining pre-set inspection items, inspecting the ECU according to the inspection items to determine multiple inspection results; determining the flash process of the ECU according to the multiple inspection results, and flashing the ECU according to the flash process.
[0012] On the other hand, the present application also proposes a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured to: read the ECU to determine the outgoing message of the ECU, diagnose the outgoing message through a predetermined flashing device to determine the operating state of the ECU; determine pre-set inspection items, inspect the ECU according to the inspection items to determine multiple inspection results; determine the flashing process of the ECU according to the multiple inspection results, and flash the ECU according to the flashing process.
[0013] This application diagnoses the outgoing messages of the ECU through a predetermined flashing device, and can accurately determine the operating status of the ECU, thereby ensuring that the flashing operation is carried out at the right time, avoiding flashing failure or equipment damage caused by improper ECU status. Detailed inspection items are set, including format inspection of flashing data, comparison of ECU data with flashing data, baud rate verification, flashing file verification, and BT version number matching, etc. These inspection steps can fully cover all preparations before flashing and ensure the smooth progress of the flashing process. During the inspection process, once any non-compliant situation is found, such as incorrect flashing data format, inconsistent ECU data with flashing data, mismatched baud rate, incorrect flashing file, or mismatched BT version number, the inspection will be exited immediately, avoiding invalid flashing or operations that may cause damage to the ECU, and improving the safety and reliability of flashing. This application also takes into account factors such as the vehicle's speed and whether the ECU has entered the flashing process. The flashing operation will only be performed when the vehicle is stationary and the ECU is in the correct flashing state, further ensuring the accuracy and safety of the flashing. When the ECU has not entered the flashing process, a reset operation will be performed, and it will be determined whether the reset ECU has entered the process control. Only when the ECU is confirmed to be in the correct state will the flashing be performed. This design enhances the flexibility and controllability of the flashing process. This application has the advantages of high efficiency, safety, and reliability, and can significantly improve the success rate and quality of ECU flashing. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:
[0015] Figure 1 A flowchart of an ECU flash checking method according to an embodiment of the present application;
[0016] Figure 2 A schematic diagram of an ECU flash inspection device in an embodiment of the present application. DETAILED DESCRIPTION
[0017] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.
[0018] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.
[0019] The correctness of the parameters that need to be selected for flashing currently depends on the choice of the flashing personnel. When there is a large amount of flashing work, it is easy to make mistakes in parameter selection. Then the flashing equipment will not check these parameters, resulting in flashing failure, wasting time, reducing flashing efficiency and flashing correctness. In serious cases, it may cause the ECU to be flashed to death, unable to continue flashing new programs, and can only be returned to the factory for repair, which greatly increases the cost of flashing. Currently, there will be no prompts in the middle of the flashing process, and an error message will be reported at the end to indicate that the target program or data has not been flashed. The flashing fails, but it takes a lot of time to locate the cause of the failure to check the possible causes of the flashing failure one by one.
[0020] like Figure 1 As shown, in order to solve the above problems, an ECU flashing inspection method provided in an embodiment of the present application is applied in an ECU flashing inspection system, the system including an ECU, and the method including:
[0021] S101, reading the ECU to determine the outgoing message of the ECU, and diagnosing the outgoing message through a predetermined flashing device to determine the operation state of the ECU.
[0022] Before flashing, all kinds of flashing parameters and conditions are judged, and errors are reported during the flashing process to prompt in time. First, back up the internal program data of the ECU and check whether the ECU has outgoing messages. Then, use the flashing equipment to send diagnostic messages through standard frame and extended frame physical addressing, such as 0x19 0x01 0xFF. As long as the ECU can reply, regardless of the content, positive and negative responses are acceptable, it can be preliminarily confirmed that it is an ECU that can operate normally. If this step fails, the flashing personnel will immediately terminate the flashing process to save manpower.
[0023] S102, determining pre-set inspection items, and inspecting the ECU according to the inspection items to determine a plurality of inspection results.
[0024] In one embodiment, before flashing, the program data file needs to be initially judged according to the pre-set data standard, including format and size checks. The format check mainly confirms whether the file conforms to the currently supported HEX, S19, BIN and other formats; the size check verifies whether the memory occupied by the data is within the allowed range. If the file is too small or too large, an error will be reported to prompt the flash writer to check the data correctness. The possible reason is that the file is damaged or the download is incomplete.
[0025] In one embodiment, after the data check passes, the hardware version number and software version number of the ECU (i.e., ECU data) are compared with the information extracted from the flashing data. If the check fails, the system will report an error message indicating that the version numbers do not match, and the flashing personnel can choose to exit the process or reselect a suitable flashing program.
[0026] In one embodiment, after the verification is passed, it is confirmed that the target program is applicable to the current controller. Then a baud rate match check is performed. If the flashing baud rate does not match, the baud rate of the flashing device is adjusted to 250K, 500K, and 1000K in turn until it matches the baud rate of the ECU to be flashed. After each baud rate adjustment, the message sent by the ECU needs to be read, and the diagnostic message is sent using standard frame and extended frame physical addressing, for example, 0x19 0x01 0xFF, to confirm whether the ECU can reply. When the message sent by the ECU can be read and the ECU replies, it is considered that the ECU has resumed normal communication and the baud rate match is successful. If the baud rates still cannot be matched after trying three, the system will report an error message indicating that the connection is unstable. At this time, the flasher can exit the inspection and check whether the OBD interface connection is stable or check whether there are other interference factors in order to further solve the problem. Among them, the On-Board Diagnostics (OBD) interface is an international standard automotive communication interface and a key bridge between the vehicle and the electronic diagnostic system. It is not only used for fault diagnosis, but also plays an important role in the maintenance and modification of the vehicle.
[0027] In one embodiment, there is a verification step for flashing the PROF file. If an error occurs when using the PROF file, the system will immediately remind the flasher of the file error and display the correct matching PROF file in the system for selection. The flasher can replace the correct PROF file by clicking confirm to continue the flashing process. If the wrong PROF file is used due to an operational error and the flashing is started, the system can detect this situation and send 11 service instructions to the ECU through the UDS protocol to reset the ECU and complete the reinitialization. At this point, the program and data will automatically roll back to the backup version before the flashing started. If necessary, the flashing process can be restarted from this step.
[0028] In one embodiment, after the Prof file check is passed, the matching of the ECU's BT version number and the program to be flashed is further verified. In the process of flashing the ECU program, the BT version number is used as a key identifier to ensure that the program to be flashed matches the software version currently installed on the ECU. If the read BT version number does not match the flashing program, the system will issue an error prompt to the flashing personnel and automatically search for a matching BT file in the system. The flashing personnel can complete the upgrade of the matching BT file by clicking Confirm. If a BT file that does not match the program to be flashed is used due to an operational error, the system will detect this situation and reset the ECU through the 11 service of the UDS protocol. The program and data will automatically roll back to the previous version to ensure the integrity of the program data. After this mis-flashing occurs, the ECU can still be used normally. If the flashing personnel need to, they can restart the flashing process from the current step, choose to directly upgrade the BT or exit the check to consider replacing other matching programs.
[0029] In one embodiment, before flashing, the vehicle speed is checked to see if they are all 0. Since flashing is not allowed when the vehicle is in motion or the engine is running, this will cause the UDS to return a negative response code 22, indicating that the current conditions do not meet the flashing requirements. If the vehicle speed is not detected to be 0, the system will report an error to prompt the flasher to stop the car immediately and turn off the engine to ensure the safety of the flashing process.
[0030] S103 . Determine a flashing process of the ECU according to the multiple inspection results, and flash the ECU according to the flashing process.
[0031] After confirming that all parameters and conditions are correct, the flashing process, that is, programming mode, is officially entered. First, check whether the flashing process has been successfully entered. If not, reset the ECU by sending the 11 01 message and try to flash again. At this time, the system will prompt the flashing personnel that the ECU has been reset and there is no need to power off, thus saving time. If the system detects that the flashing process cannot be entered even after sending two ECU reset operations, it is judged that the ECU hardware may be damaged and cannot be flashed. At this time, the flashing program will exit, and professionals will troubleshoot the corresponding hardware failure, or the flashing personnel will directly replace the ECU hardware.
[0032] If the ECU enters programming mode normally after a reset, the system will further determine whether it has successfully entered the 31st process control. If it has not entered correctly, the system will report an error message "Security access failed", which may be due to incorrect calculation algorithm of the security key. It is necessary to consider whether there is an illegal flash operation and exit the flash process accordingly. If it successfully enters the 31st process, wait for the flash to succeed, and then exit the flash process.
[0033] like Figure 2As shown, the embodiment of the present application also provides an ECU flashing inspection device, including:
[0034] at least one processor; and,
[0035] a memory communicatively connected to at least one processor; wherein,
[0036] The memory stores instructions executable by at least one processor, and the instructions are executed by at least one processor to enable an ECU flashing inspection device to perform:
[0037] Reading the ECU to determine an outgoing message of the ECU, and diagnosing the outgoing message through a predetermined flashing device to determine an operating state of the ECU;
[0038] Determining pre-set inspection items, and inspecting the ECU according to the inspection items to determine a plurality of inspection results;
[0039] The flashing process of the ECU is determined according to the multiple inspection results, and the ECU is flashed according to the flashing process.
[0040] The embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions, wherein the computer executable instructions are configured as follows:
[0041] Reading the ECU to determine an outgoing message of the ECU, and diagnosing the outgoing message through a predetermined flashing device to determine an operating state of the ECU;
[0042] Determining pre-set inspection items, and inspecting the ECU according to the inspection items to determine a plurality of inspection results;
[0043] The flashing process of the ECU is determined according to the multiple inspection results, and the ECU is flashed according to the flashing process.
[0044] In the 1990s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the method flow). However, with the development of technology, many improvements to the method flow today can be regarded as direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using a hardware entity module. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask a chip manufacturer to design and produce a dedicated integrated circuit chip. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.
[0045] The controller can be implemented in any appropriate manner, for example, the controller can take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) that can be executed by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in a purely computer-readable program code manner, the controller can be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.
[0046] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
[0047] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.
[0048] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.
[0049] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.
[0050] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.
[0051] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0052] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0053] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0054] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.
[0055] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.
[0056] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.
[0057] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.
[0058] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.
Claims
1. A method for checking ECU flashing, characterized in that: include: Reading the ECU to determine an outgoing message of the ECU, and diagnosing the outgoing message through a predetermined flashing device to determine an operating state of the ECU; Determining pre-set inspection items, and inspecting the ECU according to the inspection items to determine a plurality of inspection results; The flashing process of the ECU is determined according to the multiple inspection results, and the ECU is flashed according to the flashing process.
2. The method according to claim 1, characterized in that The ECU is inspected according to the inspection items, specifically including: Determine the flash data, and perform a format check on the flash data according to a preset format requirement; if the format of the flash data is wrong, exit the check.
3. The method according to claim 2, characterized in that The ECU is inspected according to the inspection items, specifically including: Determine the data of the ECU, compare the data of the ECU with the flash data, and exit the check if the comparison result between the data of the ECU and the flash data is inconsistent.
4. The method according to claim 1, characterized in that: The ECU is inspected according to the inspection items, specifically including: Determine a flash writing baud rate and an ECU baud rate, and check the flash writing baud rate and the ECU baud rate to make the baud rate flash writing baud rate consistent with the ECU baud rate; If the baud rate writing baud rate is inconsistent with the ECU baud rate, the writing baud rate is refreshed.
5. The method according to claim 1, characterized in that The ECU is inspected according to the inspection items, specifically including: Determine a flash file, check the flash file according to a preset checking standard, and if the flash file is an error file, replace the error file; Determine whether the flash file in use does not match. If the flash file in use does not match, roll back the flash program to the previous version.
6. The method according to claim 1, characterized in that The ECU is inspected according to the inspection items, specifically including: Determine the BT version number of the ECU, match the flash program according to the BT version number, and if the BT version number does not match the flash program, upgrade the BT file; Determine whether the BT version number in use does not match. If the BT version number in use does not match, roll back the flashing program to the previous version.
7. The method according to claim 1, characterized in that The ECU is inspected according to the inspection items, specifically including: The rotation speed of the vehicle is determined, and it is judged whether the rotation speed is zero. If the rotation speed is zero, the flashing procedure is continued.
8. The method according to claim 1, characterized in that The method further comprises: Determine whether the ECU has entered the flashing process, if the ECU has not entered the flashing process, reset the ECU, and determine whether the reset ECU has entered the process control; If the ECU enters process control, the ECU is flashed.
9. An ECU flash inspection device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the ECU flashing inspection device to perform: Reading the ECU to determine an outgoing message of the ECU, and diagnosing the outgoing message through a predetermined flashing device to determine an operating state of the ECU; Determining pre-set inspection items, and inspecting the ECU according to the inspection items to determine a plurality of inspection results; The flashing process of the ECU is determined according to the multiple inspection results, and the ECU is flashed according to the flashing process.
10. A non-volatile computer storage medium storing computer executable instructions, characterized in that: The computer executable instructions are configured to: Reading the ECU to determine an outgoing message of the ECU, and diagnosing the outgoing message through a predetermined flashing device to determine an operating state of the ECU; Determining pre-set inspection items, and inspecting the ECU according to the inspection items to determine a plurality of inspection results; The flashing process of the ECU is determined according to the multiple inspection results, and the ECU is flashed according to the flashing process.