CN114281065A

CN114281065A - Electronic control unit flashing method and device for vehicle and diagnostic equipment

Info

Publication number: CN114281065A
Application number: CN202111630611.0A
Authority: CN
Inventors: 刘均; 庄文龙
Original assignee: Shenzhen Launch Technology Co Ltd
Current assignee: Shenzhen Launch Technology Co Ltd
Priority date: 2021-12-28
Filing date: 2021-12-28
Publication date: 2022-04-05

Abstract

The application is suitable for the technical field of vehicle diagnosis, and provides a method and a device for flashing an electronic control unit of a vehicle and diagnostic equipment, wherein the method comprises the following steps: reading signature information of a flash file, wherein the signature information comprises information used for indicating an Electronic Control Unit (ECU) to be flashed which is applicable to the flash file; sending the signature information to an ECU to be flashed; receiving feedback information sent by the ECU to be flashed, wherein the feedback information is used for indicating whether the flash file can be used for flashing; and if the feedback information indicates that the flash file can be used for flash, performing flash on the ECU to be flashed according to the flash file. By the method, the problem that the refreshed ECU has faults when the ECU is refreshed by adopting an error refresh file can be solved.

Description

Electronic control unit flashing method and device for vehicle and diagnostic equipment

Technical Field

The application belongs to the technical field of vehicle diagnosis, and particularly relates to a method and a device for flashing an electronic control unit of a vehicle, diagnostic equipment and a computer-readable storage medium.

Background

With the continuous development of automotive electronics, Electronic Control Units (ECUs) are widely used in modern automobiles.

Under the condition that the ECU software of the vehicle is changed or the ECU software is required to be upgraded due to defects, manufacturers or users need to update the ECU software to upgrade the firmware. The term "ECU flashing" (flashing/reproducing/DownLoading) refers to writing ECU data or programs into the ECU storage unit.

However, when the ECU is flashed, the correct flash file needs to be selected, otherwise, the flashed ECU fails.

Disclosure of Invention

The embodiment of the application provides a vehicle electronic control unit flashing method and device and diagnosis equipment, and can solve the problem that an existing ECU is in failure when the ECU is flashed by an erroneous flashing file.

In a first aspect, an embodiment of the present application provides a method for flashing an electronic control unit of a vehicle, which is applied to a diagnostic device, and includes:

reading signature information of a flash file, wherein the signature information comprises information used for indicating an Electronic Control Unit (ECU) to be flashed which is applicable to the flash file;

sending the signature information to an ECU to be flashed;

receiving feedback information sent by the ECU to be flashed, wherein the feedback information is used for indicating whether the flash file can be used for flashing;

and if the feedback information indicates that the flash file can be used for flash, performing flash on the ECU to be flashed according to the flash file.

In a second aspect, an embodiment of the present application provides a method for flashing an electronic control unit of a vehicle, which is applied to the electronic control unit of the vehicle, and includes:

receiving signature information sent by diagnostic equipment, wherein the signature information comprises information of an Electronic Control Unit (ECU) to be flashed for indicating that a flash file is applicable;

comparing the signature information with information stored by an ECU, if the signature information and the information are the same, generating feedback information for indicating that the flash file can be used for flash, and if the signature information and the information are different, generating feedback information for indicating that the flash file cannot be used for flash;

and sending the feedback information to the diagnosis equipment.

In a third aspect, an embodiment of the present application provides an electronic control unit writing device of a vehicle, which is applied to a diagnostic device, and includes:

the system comprises a signature information reading module, a data processing module and a data processing module, wherein the signature information reading module is used for reading the signature information of a flash file, and the signature information comprises information used for indicating an Electronic Control Unit (ECU) to be flashed, which is applicable to the flash file;

the signature information sending module is used for sending the signature information to the ECU to be flashed;

a feedback information receiving module, configured to receive feedback information sent by the ECU to be flashed, where the feedback information is used to indicate whether the flash file can be flashed;

and the flash module is used for performing flash on the ECU to be flashed according to the flash file if the feedback information indicates that the flash file can be used for flash.

In a fourth aspect, an embodiment of the present application provides a diagnostic apparatus, including: comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the method according to the first aspect when executing the computer program.

In a fifth aspect, the present application provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the method according to the first aspect or the second aspect.

In a sixth aspect, embodiments of the present application provide a computer program product, which, when run on a diagnostic device, causes the diagnostic device to perform the method of the first aspect.

Compared with the prior art, the embodiment of the application has the advantages that:

in the embodiment of the application, the signature information includes information of the ECU to be flashed for indicating that the flash file is applicable, so that after the diagnostic device sends the signature information corresponding to the flash file to the ECU, the ECU can verify whether the flash file is applicable to be flashed by the flash file. That is, the diagnostic device performs the flash on the ECU to be flashed after receiving the feedback information indicating that the flash file can be used for flash sent by the ECU, so that it can be ensured that the ECU to be flashed is flashed with the correct flash file, and the problem that the flash ECU fails when the ECU is flashed with the wrong flash file can be avoided.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below.

Fig. 1 is a flowchart of a method for flashing an electronic control unit of a vehicle applied to a diagnostic device according to an embodiment of the present application;

FIG. 2 is a flowchart of an electronic control unit flashing method applied to a vehicle of the electronic control unit according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a brushing device of an electronic control unit of a vehicle applied to a diagnostic device according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a diagnostic apparatus according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.

Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.

Reference throughout this specification to "one embodiment" or "some embodiments," or the like, means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated otherwise.

The first embodiment is as follows:

at present, when an automobile is off-line, ECU software is changed or the ECU software has defects and needs to be upgraded, a user (a manufacturer or an individual user) needs to write the ECU software or data in a flash mode. In the flashing process, the flashing file for flashing the ECU can be selected in the following two ways:

one is selected from local, and the other is selected after the flash file is downloaded from the background.

Since the file formats of the flash files of different ECUs are the same, the file names of some flash files are named directly by using the part number, and different configurations may exist in the same ECU, the user may select the wrong flash file (e.g., the flash file to other ECUs) when selecting the flash file. Even if the user selects the wrong flash file, the flash of the ECU can be realized, and the flash ECU can be just damaged to cause the flash ECU to not work normally.

In order to avoid the problem that an ECU is in failure due to the fact that the ECU is flashed by adopting an error flash file, the embodiment of the application provides a flash method of an electronic control unit of a vehicle. In the method, the signature information of each flash file is recorded in advance in each flash file, and the signature information comprises information used for indicating the ECU to be flashed, which is applicable to the flash file, so that when the ECU needs to be flashed, the ECU can verify whether the flash file is suitable for flashing the ECU according to the signature information of the flash file, and therefore the fault of the ECU due to the flash of the wrong flash file can be avoided.

The electronic control unit flashing method of the vehicle according to the embodiment of the present application will be described below with reference to the drawings.

Fig. 1 shows a flowchart of a brushing method for an electronic control unit of a vehicle, which is applied to a diagnostic device and detailed as follows:

in step S11, signature information of the flash file is read, the signature information including information indicating the ECU to be flashed to which the flash file is applicable.

Specifically, after a new flash file is generated or an existing flash file is modified, signature information of the flash file needs to be generated at the same time, and the generated signature information is stored in the flash file. In some embodiments, to increase the read speed of the signature information, the signature information is stored in a designated location of the flash file. Since the storage location of the signature information is fixed, the diagnostic apparatus can quickly locate the storage location of the signature information and read out the signature information.

In this embodiment, after the diagnostic device obtains the flash file, the flash file is not directly used to flash the ECU, but the corresponding signature information is read from the flash file.

Step S12, the signature information is sent to the ECU to be flashed.

In this embodiment, after receiving the signature information, the ECU to be flashed verifies whether the signature information is suitable for being flashed by the flash file corresponding to the signature information according to the signature information, obtains a verification result, and determines feedback information fed back to the diagnostic device according to the verification result.

And step S13, receiving feedback information sent by the ECU to be flashed, wherein the feedback information is used for indicating whether the flash file can be flashed.

For example, if the verification result indicates that the ECU is suitable to be flashed by the flash file, the feedback information includes information that agrees to the flash. On the contrary, if the verification result shows that the ECU is not suitable for being flashed by the flash file, the feedback information comprises information refusing to flash.

In step S14, if the feedback information indicates that the flash file can be used for flash, the ECU to be flashed is flashed according to the flash file.

Specifically, after the diagnostic equipment analyzes the information which agrees to the flash from the feedback information, the flash file where the signature information is located is used for flash of the ECU to be flashed.

In the embodiment of the application, before the diagnostic device uses the flash file to flash the ECU to be flashed, the diagnostic device reads the corresponding signature information from the flash file, and sends the signature information to the ECU to be flashed, so that the ECU can verify whether the ECU is suitable for the flash file corresponding to the signature information, and generate corresponding feedback information according to the verification result. After the diagnostic equipment receives the feedback information sent by the ECU to be flashed, if the feedback information indicates that the ECU to be flashed can be flashed by using the flash file, the ECU to be flashed is flashed according to the flash file. Since the signature information includes information indicating the ECU to be flashed to which the flash file is applicable, after the diagnostic device sends the signature information corresponding to the flash file to the ECU, the ECU can verify whether the flash file is suitable for being flashed. That is, the diagnostic device performs the flash on the ECU to be flashed after receiving the feedback information indicating that the flash file can be used for flash sent by the ECU, so that it can be ensured that the ECU to be flashed is flashed with the correct flash file, and the problem that the flash ECU fails when the ECU is flashed with the wrong flash file can be avoided.

In some embodiments, the signature information includes at least one of the following parameters:

part number, flash-writable hardware version number range, flash-writable software version number range, and flash-written software version number.

The part number is an Identification (ID) number that uniquely identifies the ECU, such as 1198654.

The flash hardware version number range is used for identifying that the hardware version number of the ECU can be upgraded within the flash hardware version number range. Of course, the range of flash-able hardware version numbers may be a range, such as 01.00.00-05.00.00, and the hardware version numbers of the ECUs at 01.00.00-05.00.00 may be flashed using the current flash file. The flash-able hardware version number may also be a designated value (i.e., a version), such as 01.00.00-01.00.00, and only the hardware version number of the ECU of 01.00.00 can be flashed with the current flash file.

The range of the software version number that can be flashed is the software version number that can use the current flash file, and the function of the range of the software version number that can be flashed is similar to that of the hardware version number that can be flashed, and is not described herein again.

The software version number after flashing refers to the version number which is changed by the software version number of the ECU to be flashed after the ECU adopts the current flash file for flashing. For example, assuming that the software version number of the ECU to be flashed is 01.00.00 and the software version number after flashing is 02.00.00, the software version number of the ECU to be flashed is changed from 01.00.00 to 02.00.00 after the ECU to be flashed is flashed with the current flash file.

In some embodiments, the signature information is stored in a header of the flash file. Correspondingly, the step S11 includes:

the signature information added to the header of the flash file is read.

In the embodiment of the application, because the header of the flash file is easy to locate, the diagnostic device can quickly read the signature information from the header of the flash file.

In some embodiments, the signature information includes parameters recorded in the header of the flash file in sequence and in a fixed number of bytes, and the reading the signature information added to the header of the flash file includes:

and correspondingly reading each parameter added to the header of the flash file according to the sequence of recording each parameter in the header of the flash file and the fixed byte number corresponding to each parameter to obtain the signature information.

Specifically, when the diagnostic device reads the parameters, if the parameters recorded in the header are recorded in a preset encoding format, the diagnostic device needs to perform corresponding decoding according to the encoding format adopted by the recorded parameters. For example, if the parameters are encoded in ASCII (or UNICODE) codes and stored in the header of the flash file, the diagnostic device reads the information in the header of the flash file and then decodes the read information according to the encoding format of the ASCII codes. For example, if the part number 1198654 is converted into ASCII code 0x31313938363534 and stored in the header of the flash file during storage, the diagnostic device reads 0x31313938363534 and then converts 0x31313938363534 into 1198654.

In the embodiment of the present application, when the signature information includes at least 2 parameters, the parameters included in the signature information are stored in the header of the flash file in sequence in advance, and each parameter is stored in a fixed number of bytes. It should be noted that the fixed number of bytes here means that the same type of parameter is stored in the same number of bytes when different flash files are stored, and the number of bytes corresponding to different types of parameters may be the same or different, which is not limited herein. For example, the number of bytes occupied by the part number is set to be 10, the number of bytes occupied by the range of the hardware version number capable of being flashed is set to be 12, and the like.

In some embodiments, the signature information occupies a fixed number of bytes, for example, 128 bytes are occupied, and less than 128 bytes are complemented by 0.

In some embodiments, each parameter included in the signature information and the unique identifier corresponding to each parameter are stored in the header of the flash file. The header of the flash file stores each parameter included in the signature information and also stores the unique identifier corresponding to each parameter, so that when the diagnostic equipment reads the signature information, the diagnostic equipment only needs to identify each unique identifier, and can identify the corresponding parameter according to the unique identifier. That is, in the embodiment of the present application, the parameters of the signature information do not need to be stored in the header of the flash file in a fixed order, and accordingly, the diagnostic device does not need to read the parameters in the fixed order, and can also identify which parameter is read.

In some embodiments, in order for the ECU to be flashed to know the actions it needs to perform after receiving the signature information, step S12 includes:

and A1, determining the verification service identifier corresponding to the ECU to be flashed.

And the verification service identifier is used for instructing the ECU to execute a verification action on the signature information.

In this embodiment, different ECUs may correspond to the same authentication service identifier or different authentication service identifiers. For example, the engine corresponds to a validation service identification of 0x310 f.

A2, generating a verification message containing the signature information and the verification service identification, and sending the verification message to the ECU to be refreshed.

In this embodiment, the diagnostic device fills the signature information into the corresponding position of the message according to the automobile diagnostic protocol to obtain the verification message. For example, when the ECU to be flashed is the ECU of the engine, a verification message containing 0x310f + signature information is sent to the ECU to be flashed. Where 0x310f indicates that the ECU of the engine is required to verify the signature information later.

In the embodiment of the application, because the verification message includes the verification service identifier, after receiving the verification message, the ECU to be refreshed can know that the ECU needs to verify the signature information behind the verification service identifier according to the verification service identifier included in the verification message, so that the ECU to be refreshed can be ensured to verify the signature information in time.

In some embodiments, the electronic control unit flashing method of the vehicle further comprises:

and if the feedback information indicates that the flash file can not be used for flash, stopping flash of the ECU to be flashed.

In the embodiment of the application, when the diagnostic device analyzes that the ECU to be flashed cannot be flashed by using the current flash file from the feedback information, the ECU to be flashed is stopped being flashed.

Further, if the feedback information also includes an error code, the error code is analyzed, and an analysis result is displayed. The error codes are codes corresponding to parameters which are not matched with the parameters of the ECU to be written in the signature information, and the analysis result is interpretation information corresponding to the error codes. For example, assuming that the part number in the signature information does not match the part number of the ECU to be flashed, and the corresponding code for that part number is 001, the feedback information further includes "001". When the diagnostic device acquires "001" from the feedback information, the "001" is compared with the codes corresponding to the parameters included in the signature information, and it is determined that the "001" is the code corresponding to the part number, and the displayed analysis result may be that the "part number" does not match. Because the analysis result corresponding to the error code is displayed and is the interpretation information corresponding to the error code, the user can know the reason why the ECU refuses to be written by the current written file in time.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Example two:

fig. 2 shows a flowchart of another vehicle electronic control unit flashing method provided in an embodiment of the present application, where the flashing method is applied to an ECU of a vehicle, such as an ECU to be flashed applied in the first embodiment, and is detailed as follows:

step S21, receiving the signature information sent by the diagnostic device, the signature information including information indicating the electronic control unit ECU to be flashed to which the flash file applies.

Step S22 compares the signature information with the information stored in the ECU, and if the signature information and the information are the same, generates feedback information indicating that the flash file can be flashed, and if the signature information and the information are different, generates feedback information indicating that the flash file cannot be flashed.

In this embodiment, the ECU compares each parameter included in the signature information with each parameter pre-stored in the ECU, and if each parameter is the same, it indicates that the signature information is the same as the stored information, otherwise, it indicates that the signature information is different from the stored information.

Step S23, the feedback information is sent to the diagnostic device.

In the embodiment of the application, the signature information includes information of the ECU to be flashed for indicating that the flash file is suitable for, so that the ECU can verify whether the flash file is suitable for being flashed by the current flash file according to the received signature information, and further generate corresponding feedback information and send the corresponding feedback information to the diagnostic device. In this way, the diagnostic equipment can select the current flash file to flash the ECU after the feedback information indicates that the flash file can be used for flash, so that the problem that the flash ECU has a fault when the ECU is flashed by adopting an error flash file can be avoided.

The meaning of each parameter is the same as that of the first embodiment, and is not described herein again.

In some embodiments, if the signature information includes a part number, a range of flash-able hardware version numbers, a range of flash-able software version numbers, and a flash-enabled software version number, step S22 includes:

firstly, judging whether the part number in the signature information is consistent with the part number of the ECU, if not, generating feedback information for indicating that the flash file cannot be used for flash, and further, the feedback information also comprises a code corresponding to the part number, so that a user can know the reason why the flash file cannot be used for flash through a diagnosis device, which is caused by the inconsistency between the part number of the flash file and the part number of the ECU.

And if the part number in the signature information is consistent with the part number of the ECU, the flash file is the flash file of the current ECU. And then judging whether the hardware version number of the current ECU is in the range of the erasable hardware version number in the signature information, if so, judging whether the software version number of the current ECU is in the range of the erasable software version number in the signature information, if so, indicating that the current ECU can be erased by adopting the erasing file, otherwise, indicating that the current ECU cannot be erased by adopting the erasing file.

In some embodiments, the step S21 includes:

and receiving a verification message sent by the diagnostic equipment, wherein the verification message comprises signature information and a verification service identifier corresponding to the ECU.

In the embodiment of the application, the verification message comprises the verification service identifier, so that after receiving the verification message, the ECU can know that the ECU needs to verify the signature information behind the verification service identifier according to the verification service identifier included in the verification message, and can verify the signature information in time.

In some embodiments, the feedback information is sent to the diagnostic device in the form of a message. For example, if the current ECU is an engine ECU and the engine ECU can be flashed with the flash file, the engine ECU returns a message indicating that the verification is successful, such as 0x710f00, indicating that the flash can be performed. If the engine ECU cannot be flashed with this flash file, a message is returned to the diagnostic device rejecting the flash, such as 0x710f 02. It should be noted that the message in which the feedback information is located is to correspond to the verification message, for example, if the verification service identifier in the verification message is 0x310f, the feedback information needs to include 0x710f, and if the verification service identifier is 0x310a, the feedback information needs to include 0x710 a. When it is determined that the current flash file can be flashed, the feedback information includes 0x710f00, i.e., the following byte 00 indicates that the current flash file can be flashed.

Example three:

corresponding to the vehicle electronic control unit writing method of the first embodiment, fig. 3 shows a block diagram of a vehicle electronic control unit writing device provided in the embodiment of the present application, and for convenience of description, only the relevant parts of the embodiment of the present application are shown.

Referring to fig. 3, the electronic control unit writing device 3 of the vehicle is applied to a diagnostic apparatus including: a signature information reading module 31, a signature information sending module 32, a feedback information receiving module 33, and a flash module 34. Wherein:

and the signature information reading module 31 is configured to read signature information of the flash file, where the signature information includes information indicating an electronic control unit ECU to be flashed to which the flash file is applicable.

And the signature information sending module 32 is used for sending the signature information to the ECU to be flashed.

And a feedback information receiving module 33, configured to receive feedback information sent by the ECU to be flashed, where the feedback information is used to indicate whether the flash file can be flashed.

And the flashing module 34 is configured to flash the ECU to be flashed according to the flashing file if the feedback information indicates that the flashing file can be used for flashing.

In some embodiments, the signature information reading module 31 is specifically configured to:

the signature information added to the header of the flash file is read.

In some embodiments, the signature information sending module 32 includes:

and the verification service identifier determining unit is used for determining the verification service identifier corresponding to the ECU to be flashed.

And the verification message generating unit is used for generating a verification message containing the signature information and the verification service identifier and sending the verification message to the ECU to be refreshed.

In some embodiments, the electronic control unit writing device 3 of the vehicle further includes:

and the flashing stopping module is used for stopping flashing the ECU to be flashed if the feedback information indicates that the flashing file can not be used for flashing.

Further, if the feedback information also includes an error code, the error code is analyzed, and an analysis result is displayed. The error codes are codes corresponding to parameters which are not matched with the parameters of the ECU to be written in the signature information, and the analysis result is interpretation information corresponding to the error codes.

It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.

Example four:

fig. 4 is a schematic structural diagram of a diagnostic apparatus according to an embodiment of the present application. As shown in fig. 4, the diagnostic apparatus 4 of this embodiment includes: at least one processor 40 (only one processor is shown in fig. 4), a memory 41, and a computer program 42 stored in the memory 41 and executable on the at least one processor 40, the steps of any of the various method embodiments described above being implemented when the computer program 42 is executed by the processor 40.

The diagnostic device 4 may be a desktop computer, a notebook, a palm computer, a cloud server, or other computing device. The diagnostic device may include, but is not limited to, a processor 40, a memory 41. It will be understood by those skilled in the art that fig. 4 is merely an example of the diagnostic device 4, and does not constitute a limitation of the diagnostic device 4, and may include more or less components than those shown, or some components in combination, or different components, such as input output devices, network access devices, etc.

The Processor 40 may be a Central Processing Unit (CPU), and the Processor 40 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 41 may in some embodiments be an internal storage unit of the diagnostic device 4, such as a hard disk or a memory of the diagnostic device 4. The memory 41 may also be an external storage device of the diagnostic device 4 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the diagnostic device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the diagnostic device 4. The memory 41 is used for storing an operating system, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 41 may also be used to temporarily store data that has been output or is to be output.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

An embodiment of the present application further provides a network device, where the network device includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor, the processor implementing the steps of any of the various method embodiments described above when executing the computer program.

The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.

The embodiments of the present application provide a computer program product, which when running on a diagnostic device, enables the diagnostic device to implement the steps in the above method embodiments when executed.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to the photographing apparatus/diagnostic device, the recording medium, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, and software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.

In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.

Claims

1. An electronic control unit flashing method of a vehicle, which is applied to a diagnostic apparatus, includes:

sending the signature information to an ECU to be flashed;

2. The electronic control unit flashing method of a vehicle according to claim 1, wherein the signature information includes at least one of the following parameters:

3. The electronic control unit flashing method of a vehicle of claim 2, wherein reading the signature information of the flashing file comprises:

and reading the signature information added to the header of the flash file.

4. The electronic control unit flash method of a vehicle according to claim 3, wherein the signature information includes parameters recorded in a header of the flash file in order and in a fixed number of bytes, and the reading of the signature information added to the header of the flash file includes:

and correspondingly reading each parameter added to the header of the flash file according to the sequence of each parameter recorded in the header of the flash file and the fixed byte number corresponding to each parameter to obtain the signature information.

5. The electronic control unit flashing method of a vehicle according to claim 1, wherein the sending the signature information to the ECU to be flashed includes:

determining a verification service identifier corresponding to the ECU to be flashed;

and generating a verification message containing the signature information and the verification service identifier, and sending the verification message to the ECU to be flashed.

6. The electronic control unit flashing method of a vehicle according to any one of claims 1 to 5, further comprising:

7. A method for flashing an electronic control unit of a vehicle is characterized by being applied to the electronic control unit of the vehicle and comprising the following steps:

and sending the feedback information to the diagnosis equipment.

8. An electronic control unit flash apparatus of a vehicle, applied to a diagnostic device, comprising:

9. A diagnostic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any one of claims 1 to 6 when executing the computer program.

10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.