CN112162765A - Firmware upgrading method, upper computer and storage medium - Google Patents
Firmware upgrading method, upper computer and storage medium Download PDFInfo
- Publication number
- CN112162765A CN112162765A CN202010883678.4A CN202010883678A CN112162765A CN 112162765 A CN112162765 A CN 112162765A CN 202010883678 A CN202010883678 A CN 202010883678A CN 112162765 A CN112162765 A CN 112162765A
- Authority
- CN
- China
- Prior art keywords
- firmware
- data packet
- preset
- data
- conversion box
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 74
- 238000006243 chemical reaction Methods 0.000 claims abstract description 155
- 238000003745 diagnosis Methods 0.000 claims abstract description 124
- 238000004891 communication Methods 0.000 claims abstract description 27
- 238000005538 encapsulation Methods 0.000 claims description 86
- 230000006870 function Effects 0.000 claims description 27
- 230000004044 response Effects 0.000 claims description 20
- 238000004590 computer program Methods 0.000 claims description 16
- 230000005540 biological transmission Effects 0.000 claims description 10
- 230000008569 process Effects 0.000 abstract description 23
- 238000009434 installation Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 3
- 238000004806 packaging method and process Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Abstract
The application provides a firmware upgrading method, an upper computer and a storage medium, relates to the technical field of vehicle diagnosis, and can effectively solve the problems of complexity and time consumption in the process of upgrading the VCI firmware of a diagnosis conversion box. The method comprises the following steps: if the communication connection between the local computer and the diagnosis conversion box is determined, acquiring a first version number of firmware in the diagnosis conversion box; acquiring a second version number of the firmware in the local computer from a preset configuration file of the local computer; if the firmware in the diagnosis conversion box needs to be upgraded according to the first version number and the second version number, reading a firmware data packet of the firmware in the local machine according to a preset firmware data reading rule; and sending the firmware data packet to the diagnosis conversion box, and upgrading the firmware in the diagnosis conversion box.
Description
Technical Field
The present application relates to the field of vehicle diagnosis technologies, and in particular, to a firmware upgrading method, an upper computer, and a storage medium.
Background
In the Vehicle diagnosis process, when the upper computer diagnoses the Vehicle based on the standard diagnosis mode obd, the upper computer needs to be connected with a diagnosis conversion box (VCI) connected to the obd Interface through the obd Interface, and after the diagnosis instrument is connected with the VCI, the Vehicle needs to be diagnosed. The firmware of the VCI is used as the bottom layer of the firmware, so that the program code which allows the VCI to run may need to be upgraded in order to meet the compatibility problem with the upper computer in the use process of the VCI.
Currently, a user is required to confirm whether a new firmware version exists on the official website and determine whether the VCI firmware needs to be upgraded according to the introduction of the new firmware version. And in the upgrading process, a new firmware version and a firmware upgrading control program need to be downloaded. Thus, the firmware upgrade process for the entire VCI is cumbersome and time consuming.
Disclosure of Invention
The embodiment of the application provides a firmware upgrading method, an upper computer and a storage medium, and can effectively solve the problems of complexity and time consumption in the process of upgrading the VCI firmware of a diagnosis conversion box.
In a first aspect, the present application provides a firmware upgrading method applied to an upper computer, the method including:
judging whether the upper computer establishes communication connection with the diagnosis conversion box;
if yes, acquiring a first version number of firmware in the diagnosis conversion box;
acquiring a second version number of the firmware from a preset configuration file;
comparing the first version number with the second version number, and judging whether the firmware in the diagnosis conversion box needs to be upgraded or not according to the comparison result of the first version number and the second version number;
if so, reading a firmware data packet of the firmware according to a preset firmware data reading rule;
and sending the firmware data packet to the diagnosis conversion box, and upgrading the firmware in the diagnosis conversion box.
In an optional implementation manner, the determining whether the upper computer establishes a communication connection with the diagnostic conversion box specifically includes:
acquiring the virtual IP address of the upper computer,
judging whether the virtual IP address is in a preset IP address range or not;
if yes, connecting according to the virtual IP address and a preset port of the diagnosis conversion box;
and determining to establish communication connection with the diagnosis conversion box according to a system function return value of the upper computer, wherein the system function return value is the acquired response value of the preset port.
In an optional implementation manner, the comparing the first version number with the second version number, and determining whether the firmware in the diagnostic conversion box needs to be upgraded according to a comparison result between the first version number and the second version number specifically includes:
comparing the first version number and the second version number;
if the first version number is consistent with the second version number, determining that the firmware in the diagnosis conversion box does not need to be upgraded;
and if the first version number is not consistent with the second version number, determining that the firmware in the diagnosis conversion box needs to be upgraded.
In an optional implementation manner, the reading the firmware data packet of the firmware according to a preset firmware data reading rule includes:
and sequentially reading firmware data with preset size from the firmware data installed on the upper computer to obtain at least one firmware data packet with preset size.
In an optional implementation manner, sending the firmware data packet to the diagnostic conversion box, and upgrading the firmware in the diagnostic conversion box includes:
sequentially encapsulating at least one firmware data packet with a preset size according to a preset data encapsulation protocol to obtain at least one network data packet to be transmitted;
and sending at least one network data packet to be transmitted to the diagnosis conversion box, and upgrading the firmware of the diagnosis conversion box.
In an alternative implementation form of the present invention,
the preset data encapsulation protocol comprises data content, a data type field, a data packet state, a data packet sequence number and a data packet size;
sequentially encapsulating the firmware data packet with at least one preset size according to a preset data encapsulation protocol to obtain at least one network data packet to be transmitted, including:
if the firmware data packet is a first firmware data packet, writing the first firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as a continuous transmission, writing the sequence number of the data packet of the preset data encapsulation protocol as zero, and writing the size of the data packet of the preset data encapsulation protocol as the preset size to obtain a first network data packet;
if the firmware data packet is a second firmware data packet, writing the second firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as a continuous transmission, writing the sequence number of the data packet of the preset data encapsulation protocol as a non-zero value, and writing the size of the data packet of the preset data encapsulation protocol as the preset size to obtain a second network data packet;
if the firmware data packet is a third firmware data packet, writing the third firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as completion, writing the sequence number of the data packet of the preset data encapsulation protocol as nonzero, and writing the data packet size of the preset data encapsulation protocol as actual data length to obtain a third network data packet.
In an optional implementation manner, after sending the firmware data packet to the diagnostic conversion box and upgrading the firmware in the diagnostic conversion box, the method includes:
if response information returned by the diagnosis conversion box is received within a preset time length, determining that the firmware in the diagnosis conversion box is upgraded;
and if the response information returned by the diagnosis conversion box is not received within the preset time, determining that the firmware upgrading in the diagnosis conversion box is not completed, and generating and displaying upgrading error prompt information.
In a second aspect, the present application provides a host computer, including:
the first judgment module is used for judging whether the upper computer is in communication connection with the diagnosis conversion box;
the first acquisition module is used for acquiring a first version number of firmware in the diagnosis conversion box after the upper computer is in communication connection with the diagnosis conversion box;
the second obtaining module is used for obtaining a second version number of the firmware from a preset configuration file;
the second judging module is used for comparing the first version number with the second version number and judging whether the firmware in the diagnosis conversion box needs to be upgraded or not according to the comparison result of the first version number and the second version number;
the reading module is used for reading a firmware data packet of the firmware according to a preset firmware data reading rule when the firmware in the diagnosis conversion box needs to be upgraded;
and the upgrading module is used for sending the firmware data packet to the diagnosis conversion box and upgrading the firmware in the diagnosis conversion box.
In an optional implementation manner, the first determining module includes:
an acquisition unit for acquiring a virtual IP address of the upper computer,
the judging unit is used for judging whether the virtual IP address is in a preset IP address range or not;
the connection unit is used for connecting the virtual IP address with a preset port of the diagnosis conversion box when the virtual IP address is in a preset IP address range;
the first determining unit is used for determining to establish communication connection with the diagnosis conversion box according to a system function return value of the upper computer, wherein the system function return value is the acquired response value of the preset port.
In an optional implementation manner, the second determining module includes:
a comparing unit, configured to compare the first version number and the second version number;
a second determining unit configured to determine that upgrading of the firmware installed on the diagnostic converter box is not required if the first version number is identical to the second version number;
a third determining unit, configured to determine that the firmware installed on the diagnostic converter box needs to be upgraded if the first version number does not match the second version number.
In an optional implementation manner, the reading module is specifically configured to:
and sequentially reading firmware data with preset size from the firmware data of the local installation firmware to obtain at least one firmware data packet with preset size.
In an optional implementation manner, the upgrade module includes:
an obtaining unit, configured to sequentially package at least one firmware data packet of a preset size according to a preset data package protocol to obtain at least one network data packet to be transmitted;
and the sending unit is used for sending at least one network data packet to be transmitted to the diagnosis conversion box and upgrading the firmware of the diagnosis conversion box.
In an optional implementation manner, the preset data encapsulation protocol includes data content, a data type field, a data packet status, a data packet sequence number, and a data packet size;
obtaining a unit comprising:
the first obtaining subunit is configured to, if the firmware data packet is a first firmware data packet, write the first firmware data packet into data content of the preset data encapsulation protocol, write a data type field of the preset data encapsulation protocol as an upgrade packet, write a data packet state of the preset data encapsulation protocol as a continuous transmission, write a data packet sequence number of the preset data encapsulation protocol as zero, and write a data packet size of the preset data encapsulation protocol as the preset size to obtain a first network data packet;
a second obtaining subunit, configured to, if the firmware data packet is a second firmware data packet, write the second firmware data packet into the data content of the preset data encapsulation protocol, write the data type field of the preset data encapsulation protocol as an upgrade packet, write the data packet state of the preset data encapsulation protocol as a continuous transmission, write the sequence number of the data packet of the preset data encapsulation protocol as non-zero, write the size of the data packet of the preset data encapsulation protocol as the preset size, and obtain a second network data packet;
and the third obtaining subunit is configured to, if the firmware data packet is a third firmware data packet, write the third firmware data packet into the data content of the preset data encapsulation protocol, write the data type field of the preset data encapsulation protocol as an upgrade packet, write the data packet state of the preset data encapsulation protocol as a completion, write the sequence number of the data packet of the preset data encapsulation protocol as a nonzero number, and write the size of the data packet of the preset data encapsulation protocol as an actual data length to obtain a third network data packet.
In an optional implementation manner, the method further includes:
the first determining module is used for determining that the firmware in the diagnosis conversion box is upgraded if response information returned by the diagnosis conversion box is received within a preset time length;
and the second determining module is used for determining that the firmware upgrading in the diagnosis conversion box is not finished if the response information returned by the diagnosis conversion box is not received within the preset time length, and generating and displaying upgrading error prompt information.
In a third aspect, the present application provides an upper computer, including a memory, configured to store a firmware upgrade program in a diagnostic conversion box; a processor configured to implement the steps of the firmware upgrade method according to the first aspect or any optional manner of the first aspect when executing the firmware upgrade program.
In a fourth aspect, the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, performs the steps of the firmware upgrade method according to the first aspect or any alternative of the first aspect.
In a fifth aspect, an embodiment of the present application provides a computer program product, which, when the computer program product runs on an upper computer, causes the upper computer to execute the steps of the firmware upgrading method in the diagnostic conversion box according to the first aspect or any optional manner of the first aspect.
The firmware upgrading method provided by the application is adopted, whether the firmware installed on the diagnosis conversion box needs to be upgraded or not can be directly determined by the upper computer according to the first version number of the diagnosis conversion box installation firmware and the second version number of the upper computer installation firmware, and further when the firmware installed on the diagnosis conversion box needs to be upgraded, the upper computer reads rules according to preset firmware data, reads a firmware data packet of the local installation firmware, and sends the firmware data packet to the diagnosis conversion box, and is right, the firmware in the diagnosis conversion box is upgraded, so that the firmware upgrading process is simplified, and the time required by firmware upgrading is saved.
It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the embodiments or drawings supported by the prior art description, and it is obvious that the drawings in the following description are only embodiments of the present application, and those skilled in the art can also obtain other drawings according to these drawings without inventive labor.
Fig. 1(a) is a flowchart of a firmware upgrade method provided in a first embodiment of the present application;
fig. 1(b) is a schematic view of a scenario of a firmware upgrade method provided in an embodiment of the present application;
FIG. 2 is a flowchart illustrating an implementation of S101 shown in FIG. 1;
FIG. 3 is a flowchart of a specific implementation of S104;
FIG. 4 is a flowchart of a firmware upgrade method according to a second embodiment of the present application;
FIG. 5 is a schematic diagram of an upper computer provided in a third embodiment of the present application;
fig. 6 is a schematic diagram of an upper computer according to a fourth 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 should be understood that the terms "first," "second," "third," and the like in the description of the present application and in the appended claims, are used for distinguishing between descriptions that are not intended to indicate or imply relative importance.
It should also be appreciated that 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. It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The following describes an exemplary firmware upgrade method provided in the present application by using a specific embodiment.
Referring to fig. 1(a), fig. 1(a) is a flowchart of a firmware upgrade method according to a first embodiment of the present application. The firmware upgrading method in this embodiment may be executed by an upper computer, and the upper computer may be implemented by hardware and/or software. In the embodiment of the present application, the upper computer includes, but is not limited to, a diagnosis computer or a server having functions of reading, analyzing and displaying diagnosis data in various vehicle diagnosis application scenarios. The firmware upgrade method as shown in fig. 1(a) may include:
and S101, judging whether the upper computer is in communication connection with the diagnosis conversion box.
It should be noted that, as shown in fig. 1(b), fig. 1(b) is an application scenario schematic diagram of the firmware upgrading method provided in the embodiment of the present application. As can be seen from fig. 1(b), the upper computer 1101 and the vehicle 1102 need to perform diagnostic protocol conversion by the diagnostic conversion box 1103. In the process of diagnosing a fault of the vehicle 1102, one end of the diagnostic converter box (VCI box) 1103 is plugged into a diagnostic interface (OBD interface) of the vehicle 1102, and the other end is connected to the upper computer 1101 through a USB cable or connected to the upper computer 1101 through wireless communication (WIFi, bluetooth, etc.). The diagnosis conversion box 1103 may be referred to as a lower computer, and the upper computer 1101 may be referred to as a diagnostic apparatus.
Although the firmware installed in the diagnostic converter box 1103 is the same as the firmware installed in the upper computer 1101, in a specific use process, for example, in a process of diagnosing the vehicle 1102 by the upper computer 1101, the firmware in the upper computer 1101 is updated in version as the functions of the upper computer 1101 are improved. However, the firmware in the diagnostic converter box 1103 may always be in the original version, so that the firmware in the upper computer 1101 and the firmware in the diagnostic converter box 1103 are not consistent in version, which may cause a problem that the diagnostic converter box 1103 is incompatible with the upper computer 1101.
In the embodiment of the application, after the upper computer is started, it is required to determine whether to establish a communication connection with the diagnostic conversion box, and specifically, it is determined whether a virtual IP address of the upper computer is within an IP address range assignable to the diagnostic conversion box by traversing the network card of the host computer, so as to determine whether to establish a communication connection with the diagnostic conversion box.
As shown in fig. 2, fig. 2 is a flowchart of a specific implementation of S101 in fig. 1. As can be seen from fig. 2, S101 includes S1011 to S1014. The details are as follows:
s1011, acquiring the virtual IP address of the upper computer.
The virtual IP address may be an IP address randomly assigned by the diagnostic switch box to the upper computer.
S1012, judging whether the virtual IP address is in a preset IP address range.
In an embodiment of the application, the preset IP address range is an effective IP address range assignable to the diagnostic conversion box, and whether the upper computer is in a communication range with the diagnostic conversion box can be determined by determining whether a virtual IP address of the upper computer is in the effective IP address range assignable to the diagnostic conversion box. For example, the diagnostic switch box may be assigned a valid IP address range of 192.168.100.150 to 192.168.100.254. Assuming that the virtual IP address of the upper computer is 192.168.100.159, it is determined that the virtual IP address of the upper computer is within the range of valid IP addresses assignable by the diagnostic conversion box. For another example, assuming that the virtual IP address of the upper computer is 192.168.100.255, it is determined that the virtual IP address of the upper computer is not within the range of valid IP addresses assignable by the diagnostic converter box.
Illustratively, after the upper computer is started, a thread for traversing the network card of the upper computer is created, the thread for traversing the network card of the upper computer traverses the network card of the upper computer once according to a preset time interval, for example, every 0.5 second, 0.7 second or 0.9 second, the virtual IP address of the upper computer is obtained, and whether the obtained virtual IP address is within an effective IP address range assignable by the diagnostic conversion box is compared.
And S1013, if so, connecting according to the virtual IP address and a preset port number of the diagnosis conversion box.
For example, the port number of the preset port of the diagnostic switch box is 22535, and the connection is made through the virtual IP address and the port with the port number 22535.
And S1014, determining to establish communication connection with the diagnosis conversion box according to a system function return value of the upper computer, wherein the system function return value is the acquired response value of the preset port.
The system function return value may be a response value of the preset port acquired by the system function, and may be represented by a handle. For example, if the handle returned by the system function is negative, that is, the response value of the system function of the upper computer to the preset port is negative, it is determined that the communication connection with the diagnostic conversion box fails. It should be noted that, after determining that the communication connection with the diagnostic conversion box fails, the network card of the upper computer needs to be traversed again to obtain the virtual IP address of the upper computer again, so as to further confirm whether the communication connection with the diagnostic conversion box is established.
And if the handle returned by the system function is positive, that is, the response value of the system function of the upper computer to the preset port is positive, determining that the communication connection with the diagnosis conversion box is successfully established.
And S102, if so, acquiring a first version number of the firmware in the diagnosis conversion box.
In the embodiment of the application, after the upper computer is determined to be in communication connection with the diagnosis conversion box, the first version number of the firmware in the diagnosis conversion box is obtained.
It should be noted that the diagnostic conversion box is provided with the same firmware as the upper computer, but the firmware is automatically upgraded when the upper computer is in use, but the firmware upgrade in the diagnostic conversion box usually requires a special operation. As a result, after a period of use, the version number corresponding to the firmware in the diagnostic conversion box may not coincide with the version number corresponding to the firmware in the upper computer.
In this embodiment, the upper computer may obtain the first version number of the firmware in the diagnostic conversion box online. Optionally, the upper computer establishes tcp connection with the obtained virtual ip address and a preset port of the diagnostic conversion box, for example, a port number of the preset port is 22400; and then the upper computer sends an instruction for acquiring the estimated version to the diagnosis conversion box, and analyzes and extracts a first version number of the firmware version returned by the diagnosis conversion box.
S103, acquiring a second version number of the firmware from a preset configuration file.
In this embodiment, the preset configuration file is an INI configuration file in an installation directory of the upper computer installation firmware, and the INI configuration file stores a second version number of the firmware installed on the upper computer.
It will be appreciated that the second version number is an updated version number of the firmware relative to the first version number. Typically, the second version number is a new version number relative to the first version number.
And S104, comparing the first version number with the second version number, and judging whether the firmware in the diagnosis conversion box needs to be upgraded or not according to the comparison result of the first version number and the second version number.
It will be appreciated that comparing the first version number to the second version number allows a determination to be made as to whether an upgrade to the firmware within the diagnostic conversion cartridge is required.
For example, before determining that the firmware installed on the diagnostic converter box needs to be upgraded according to the first version number and the second version number, the method may include: comparing the first version number and the second version number; if the first version number is consistent with the second version number, determining that the firmware installed on the diagnostic conversion box does not need to be upgraded; and if the first version number is not consistent with the second version number, determining that the firmware installed on the diagnostic conversion box needs to be upgraded.
Optionally, in an embodiment of the present application, if the first version number is not consistent with the second version number, it indicates that the second version number is a version number after upgrade, and it is a new version number relative to the first version number.
And S105, if yes, reading the firmware data packet of the firmware according to a preset firmware data reading rule.
Illustratively, reading the firmware data packet installed by the upper computer may include: and sequentially reading firmware data with preset size from the firmware data of the local installation firmware to obtain at least one firmware data packet with preset size.
Wherein the preset size may be a preset data frame length determined according to a preset diagnostic protocol. For example, the preset size is 4 megabits, 6 megabits, 7 megabits, or the like.
In the embodiment of the present application, the upper computer reads the firmware data corresponding to the firmware in the installation directory, and reads data of a preset size, for example, 4 megabits of data, 6 megabits of data, or 7 megabits of data each time. In this embodiment, it is assumed that the data length corresponding to the 4 million data is 4096 frames, the data length corresponding to the 6 million data is 6144 frames, and the data length corresponding to the 7 million data is 7168 frames.
S106, sending the firmware data packet to the diagnosis conversion box, and upgrading the firmware in the diagnosis conversion box.
Optionally, before sending the firmware data packet to the diagnostic conversion box and upgrading the firmware in the diagnostic conversion box, the method may further include: the upper computer enables the upgrade button of the diagnosis conversion box, so that the upgrade button of the diagnosis conversion box displays an upgrade indication, for example, the color of the upgrade button is lightened, or an indicator lamp beside the upgrade button is lightened, and the like.
And the upper computer detects the upgrade request information sent by the diagnosis conversion box after enabling the upgrade button of the diagnosis conversion box. Illustratively, after an upgrade instruction is displayed on an upgrade button of the diagnostic converter box, the user clicks the upgrade button according to the upgrade instruction, and the diagnostic converter box sends the upgrade request information to the upper computer after detecting that the upgrade instruction triggered by the user clicking the upgrade button.
And after detecting the upgrading request information sent by the diagnosis conversion box, the upper computer sends the firmware data packet to the diagnosis conversion box to upgrade the firmware in the diagnosis conversion box.
In an embodiment of the present application, sending the firmware data packet to the diagnostic converter box, and upgrading the firmware in the diagnostic converter box may include: and according to a preset data packaging format, packaging the firmware data packet to obtain a network data packet, and sending the network data packet to the diagnosis conversion box.
Illustratively, as shown in fig. 3, fig. 3 is a flowchart of a specific implementation of S106. As can be seen from fig. 3, S106 includes S1061 to S1062, which are detailed as follows:
s1061, sequentially encapsulating at least one firmware data packet with a preset size according to a preset data encapsulation protocol to obtain at least one network data packet to be transmitted.
In this embodiment, the preset data encapsulation protocol includes data content, a data type field, a data packet status, a data packet sequence number, and a data packet size.
Optionally, the data type field may include an upgrade package and MD5 files, such as upgrade package denoted with 02 and MD5 file denoted with 01; the packet state may include resume and completion, e.g., resume at 55 and completion at FF; the data packet sequence number sequentially increases from the first packet 00 in order, and starts from 01 when the overflow occurs.
Illustratively, sequentially encapsulating at least one firmware data packet of a preset size according to a preset data encapsulation protocol to obtain at least one network data packet to be transmitted, including:
if the firmware data packet is a first firmware data packet, writing the first firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as a continuous transmission, writing the sequence number of the data packet of the preset data encapsulation protocol as zero, and writing the size of the data packet of the preset data encapsulation protocol as the preset size to obtain a first network data packet.
The first firmware data packet is a first packet firmware data packet, and the first network data packet is a first packet network data packet transmitted for the first time.
If the firmware data packet is a second firmware data packet, writing the second firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as a continuous transmission, writing the sequence number of the data packet of the preset data encapsulation protocol as a non-zero value, and writing the size of the data packet of the preset data encapsulation protocol as the preset size to obtain a second network data packet.
And the second firmware data packet is all data packets except the first firmware data packet and the third firmware data packet.
If the firmware data packet is a third firmware data packet, writing the third firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as completion, writing the sequence number of the data packet of the preset data encapsulation protocol as nonzero, and writing the data packet size of the preset data encapsulation protocol as actual data length to obtain a third network data packet.
Wherein the third firmware packet is a last firmware packet.
S1062, sending at least one to-be-transmitted network data packet to the diagnostic converter box, and upgrading firmware of the diagnostic converter box.
Through the analysis, the firmware upgrading method provided by the embodiment of the application can directly determine whether the firmware installed on the diagnosis conversion box needs to be upgraded or not according to the first version number of the firmware installed on the diagnosis conversion box and the second version number of the firmware installed on the upper computer, and further when the firmware installed on the diagnosis conversion box needs to be upgraded, the upper computer reads the firmware data packet of the firmware installed on the local computer according to the preset firmware data reading rule, sends the firmware data packet to the diagnosis conversion box, and upgrades the firmware in the diagnosis conversion box, so that the firmware upgrading process is simplified, and the time required by firmware upgrading is saved.
As shown in fig. 4, fig. 4 is a flowchart of a firmware upgrade method according to a second embodiment of the present application. Compared with the embodiment shown in fig. 1, the specific implementation processes of S401 to S406 are the same as those of S101 to S106, except that S407 to S408 are further included after S406. The details are as follows:
s401, judging whether the upper computer is in communication connection with the diagnosis conversion box.
S402, if yes, acquiring a first version number of the firmware in the diagnosis conversion box.
And S403, acquiring a second version number of the firmware from a preset configuration file.
S404, comparing the first version number with the second version number, and judging whether the firmware in the diagnosis conversion box needs to be upgraded according to the comparison result of the first version number and the second version number.
S405, if yes, reading a firmware data packet of the firmware according to a preset firmware data reading rule.
S406, sending the firmware data packet to the diagnosis conversion box, and upgrading the firmware in the diagnosis conversion box.
And S407, if response information returned by the diagnosis conversion box is received within a preset time, determining that the firmware in the diagnosis conversion box is upgraded.
In this embodiment, the preset time duration is a preset response time duration for the upper computer to wait for the diagnostic converter box, and in the response time duration, if corresponding information returned by the diagnostic converter box is received, it is determined that the diagnostic converter box reads the network data packet that is completely transmitted, and it is determined that the firmware in the diagnostic converter box is completely upgraded.
Further, after sequentially sending the network data packets to the diagnosis conversion box, the upper computer may further determine whether the sent network data packet is the last packet, and after confirming that the last packet of the network data packet is successfully sent, determine that the firmware in the diagnosis conversion box is upgraded.
S408, if the response information returned by the diagnosis conversion box is not received within the preset time, determining that the firmware upgrading in the diagnosis conversion box is not completed, and generating and displaying upgrading error prompt information.
Through the analysis, the firmware upgrading method provided by the application can be used for directly determining whether the firmware installed on the diagnosis conversion box needs to be upgraded or not by the upper computer according to the first version number of the diagnosis conversion box installation firmware and the second version number of the upper computer installation firmware, and further when the firmware installed on the diagnosis conversion box needs to be upgraded, the upper computer reads a rule according to preset firmware data, reads a firmware data packet of the local installation firmware, sends the firmware data packet to the diagnosis conversion box, and upgrades the firmware in the diagnosis conversion box, so that the firmware upgrading process is simplified, and the time required by firmware upgrading is saved. 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.
Based on the firmware upgrading method provided by the above embodiment, an embodiment of an apparatus for implementing the above method embodiment is further provided in the embodiment of the present invention.
Referring to fig. 5, fig. 5 is a schematic diagram of an upper computer according to a third embodiment of the present application. The modules included are used to perform the steps in the embodiment corresponding to fig. 1. Please refer to fig. 1 for the related description of the corresponding embodiment. For convenience of explanation, only the portions related to the present embodiment are shown. Referring to fig. 5, the upper computer 5 includes:
the first judging module 501 is used for judging whether the upper computer is in communication connection with the diagnosis conversion box;
a first obtaining module 502, configured to obtain a first version number of firmware in the diagnostic conversion box after the upper computer establishes a communication connection with the diagnostic conversion box;
a second obtaining module 503, configured to obtain a second version number of the firmware from a preset configuration file;
a second determining module 504, configured to compare the first version number with the second version number, and determine whether the firmware in the diagnostic conversion box needs to be upgraded according to a comparison result between the first version number and the second version number;
a reading module 505, configured to read a firmware data packet of the firmware according to a preset firmware data reading rule when the firmware in the diagnostic conversion box needs to be updated;
an upgrade module 506, configured to send the firmware data packet to the diagnostic conversion box, and upgrade the firmware in the diagnostic conversion box.
In an optional implementation manner, the first determining module 501 includes:
an acquisition unit for acquiring a virtual IP address of the upper computer,
the judging unit is used for judging whether the virtual IP address is in a preset IP address range or not;
the connection unit is used for connecting the virtual IP address with a preset port of the diagnosis conversion box when the virtual IP address is in a preset IP address range;
the first determining unit is used for determining to establish communication connection with the diagnosis conversion box according to a system function return value of the upper computer, wherein the system function return value is the acquired response value of the preset port.
In an optional implementation manner, the second determining module 504 includes:
a comparing unit, configured to compare the first version number and the second version number;
a second determining unit configured to determine that upgrading of the firmware installed on the diagnostic converter box is not required if the first version number is identical to the second version number;
a third determining unit, configured to determine that the firmware installed on the diagnostic converter box needs to be upgraded if the first version number does not match the second version number.
In an optional implementation manner, the reading module 505 is specifically configured to:
and sequentially reading firmware data with preset size from the firmware data of the local installation firmware to obtain at least one firmware data packet with preset size.
In an optional implementation manner, the upgrade module includes:
an obtaining unit, configured to sequentially package at least one firmware data packet of a preset size according to a preset data package protocol to obtain at least one network data packet to be transmitted;
and the sending unit is used for sending at least one network data packet to be transmitted to the diagnosis conversion box and upgrading the firmware of the diagnosis conversion box.
In an optional implementation manner, the preset data encapsulation protocol includes data content, a data type field, a data packet status, a data packet sequence number, and a data packet size;
obtaining a unit comprising:
the first obtaining subunit is configured to, if the firmware data packet is a first firmware data packet, write the first firmware data packet into data content of the preset data encapsulation protocol, write a data type field of the preset data encapsulation protocol as an upgrade packet, write a data packet state of the preset data encapsulation protocol as a continuous transmission, write a data packet sequence number of the preset data encapsulation protocol as zero, and write a data packet size of the preset data encapsulation protocol as the preset size to obtain a first network data packet;
a second obtaining subunit, configured to, if the firmware data packet is a second firmware data packet, write the second firmware data packet into the data content of the preset data encapsulation protocol, write the data type field of the preset data encapsulation protocol as an upgrade packet, write the data packet state of the preset data encapsulation protocol as a continuous transmission, write the sequence number of the data packet of the preset data encapsulation protocol as non-zero, write the size of the data packet of the preset data encapsulation protocol as the preset size, and obtain a second network data packet;
and the third obtaining subunit is configured to, if the firmware data packet is a third firmware data packet, write the third firmware data packet into the data content of the preset data encapsulation protocol, write the data type field of the preset data encapsulation protocol as an upgrade packet, write the data packet state of the preset data encapsulation protocol as a completion, write the sequence number of the data packet of the preset data encapsulation protocol as a nonzero number, and write the size of the data packet of the preset data encapsulation protocol as an actual data length to obtain a third network data packet.
In an optional implementation manner, the method further includes:
the first determining module is used for determining that the firmware in the diagnosis conversion box is upgraded if response information returned by the diagnosis conversion box is received within a preset time length;
and the second determining module is used for determining that the firmware upgrading in the diagnosis conversion box is not finished if the response information returned by the diagnosis conversion box is not received within the preset time length, and generating and displaying upgrading error prompt information.
It should be noted that, because the contents of information interaction, execution process, and the like between the modules are based on the same concept as that of the embodiment of the method of the present application, specific functions and technical effects thereof may be specifically referred to a part of the embodiment of the method, and details are not described here.
Fig. 6 is a schematic diagram of an upper computer according to a fourth embodiment of the present application. As shown in fig. 6, the upper computer 6 of this embodiment includes: a processor 600, a memory 601, and a computer program 602, such as a firmware upgrade program, stored in the memory 601 and operable on the processor 600. The processor 600 executes the computer program 602 to implement the steps in the above-described embodiments of the firmware upgrade method, such as the steps 101 to 104 shown in fig. 1. Alternatively, the processor 600 executes the computer program 602 to implement the functions of the modules/units in the above device embodiments, such as the functions of the modules 501 to 504 shown in fig. 5.
Illustratively, the computer program 602 may be partitioned into one or more modules/units that are stored in the memory 601 and executed by the processor 600 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution process of the computer program 602 in the upper computer 6. For example, the computer program 602 may be divided into a first obtaining module, a second obtaining module, a reading module and an upgrading module, and specific functions of each module please refer to the related description in the embodiment corresponding to fig. 5, which is not described herein again.
The upper computer may include, but is not limited to, a processor 600 and a memory 601. Those skilled in the art will appreciate that fig. 6 is only an example of the upper computer 6, and does not constitute a limitation to the upper computer 6, and may include more or less components than those shown, or some components in combination, or different components, for example, the video processing device may further include an input-output device, a network access device, a bus, and the like.
The Processor 600 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The storage 601 may be an internal storage unit of the upper computer 6, such as a hard disk or a memory of the upper computer 6. The memory 601 may also be an external storage device of the upper computer 6, 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 equipped on the upper computer 6. Further, the memory 601 may also include both an internal storage unit and an external storage device of the upper computer 6. The memory 601 is used for storing the computer program 602 and other programs and data supported by the upper computer 6. The memory 601 may also be used to temporarily store data that has been output or is to be output.
An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the firmware upgrading method can be implemented.
The embodiment of the application provides a computer program product, and when the computer program product runs on an upper computer, the upper computer can realize the firmware upgrading method when executing.
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.
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.
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 (10)
1. A firmware upgrading method is applied to an upper computer, and comprises the following steps:
judging whether the upper computer establishes communication connection with the diagnosis conversion box;
if yes, acquiring a first version number of firmware in the diagnosis conversion box;
acquiring a second version number of the firmware from a preset configuration file;
comparing the first version number with the second version number, and judging whether the firmware in the diagnosis conversion box needs to be upgraded or not according to the comparison result of the first version number and the second version number;
if so, reading a firmware data packet of the firmware according to a preset firmware data reading rule;
and sending the firmware data packet to the diagnosis conversion box, and upgrading the firmware in the diagnosis conversion box.
2. The method according to claim 1, wherein the determining whether the upper computer establishes a communication connection with the diagnostic converter box specifically comprises:
acquiring the virtual IP address of the upper computer,
judging whether the virtual IP address is in a preset IP address range or not;
if yes, connecting according to the virtual IP address and a preset port of the diagnosis conversion box;
and determining to establish communication connection with the diagnosis conversion box according to a system function return value of the upper computer, wherein the system function return value is the acquired response value of the preset port.
3. The method according to claim 1 or 2, wherein the comparing the first version number with the second version number, and determining whether the firmware in the diagnostic conversion box needs to be upgraded according to a comparison result of the first version number with the second version number specifically includes:
comparing the first version number and the second version number;
if the first version number is consistent with the second version number, determining that the firmware in the diagnosis conversion box does not need to be upgraded;
and if the first version number is not consistent with the second version number, determining that the firmware in the diagnosis conversion box needs to be upgraded.
4. The method according to claim 3, wherein the reading the firmware data packet of the firmware according to the preset firmware data reading rule comprises:
and sequentially reading firmware data with preset size from the firmware data installed on the upper computer to obtain at least one firmware data packet with preset size.
5. The method of claim 4, wherein sending the firmware data packet to the diagnostic converter box to upgrade the firmware in the diagnostic converter box comprises:
sequentially encapsulating at least one firmware data packet with a preset size according to a preset data encapsulation protocol to obtain at least one network data packet to be transmitted;
and sending at least one network data packet to be transmitted to the diagnosis conversion box, and upgrading the firmware of the diagnosis conversion box.
6. The method of claim 5, wherein the predetermined data encapsulation protocol comprises data content, data type field, packet status, packet sequence number, and packet size;
sequentially encapsulating the firmware data packet with at least one preset size according to a preset data encapsulation protocol to obtain at least one network data packet to be transmitted, including:
if the firmware data packet is a first firmware data packet, writing the first firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as a continuous transmission, writing the sequence number of the data packet of the preset data encapsulation protocol as zero, and writing the size of the data packet of the preset data encapsulation protocol as the preset size to obtain a first network data packet;
if the firmware data packet is a second firmware data packet, writing the second firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as a continuous transmission, writing the sequence number of the data packet of the preset data encapsulation protocol as a non-zero value, and writing the size of the data packet of the preset data encapsulation protocol as the preset size to obtain a second network data packet;
if the firmware data packet is a third firmware data packet, writing the third firmware data packet into the data content of the preset data encapsulation protocol, writing the data type field of the preset data encapsulation protocol as an upgrade packet, writing the data packet state of the preset data encapsulation protocol as completion, writing the sequence number of the data packet of the preset data encapsulation protocol as nonzero, and writing the data packet size of the preset data encapsulation protocol as actual data length to obtain a third network data packet.
7. The method according to any one of claims 4 to 6, wherein after sending the firmware data packet to the diagnostic converter box to upgrade the firmware in the diagnostic converter box, the method comprises:
if response information returned by the diagnosis conversion box is received within a preset time length, determining that the firmware in the diagnosis conversion box is upgraded;
and if the response information returned by the diagnosis conversion box is not received within the preset time, determining that the firmware upgrading in the diagnosis conversion box is not completed, and generating and displaying upgrading error prompt information.
8. A host computer, comprising:
the first judgment module is used for judging whether the upper computer is in communication connection with the diagnosis conversion box;
the first acquisition module is used for acquiring a first version number of firmware in the diagnosis conversion box after the upper computer is in communication connection with the diagnosis conversion box;
the second obtaining module is used for obtaining a second version number of the firmware from a preset configuration file;
the second judging module is used for comparing the first version number with the second version number and judging whether the firmware in the diagnosis conversion box needs to be upgraded or not according to the comparison result of the first version number and the second version number;
the reading module is used for reading a firmware data packet of the firmware according to a preset firmware data reading rule when the firmware in the diagnosis conversion box needs to be upgraded;
and the upgrading module is used for sending the firmware data packet to the diagnosis conversion box and upgrading the firmware in the diagnosis conversion box.
9. A host computer, comprising:
a memory for storing a firmware upgrade program in the diagnostic conversion box;
a processor for implementing the firmware upgrade method according to any one of claims 1 to 7 when executing the firmware upgrade program.
10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, implements a firmware upgrade method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010883678.4A CN112162765A (en) | 2020-08-28 | 2020-08-28 | Firmware upgrading method, upper computer and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010883678.4A CN112162765A (en) | 2020-08-28 | 2020-08-28 | Firmware upgrading method, upper computer and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112162765A true CN112162765A (en) | 2021-01-01 |
Family
ID=73860411
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010883678.4A Pending CN112162765A (en) | 2020-08-28 | 2020-08-28 | Firmware upgrading method, upper computer and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112162765A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112764781A (en) * | 2021-01-28 | 2021-05-07 | 深圳市科陆电子科技股份有限公司 | Platform area intelligent terminal, alternate acquisition board firmware upgrading method, system and storage medium |
| CN113835729A (en) * | 2021-09-23 | 2021-12-24 | 深圳市元征科技股份有限公司 | Upgrading method and device, terminal equipment and computer readable storage medium |
| CN116520815A (en) * | 2023-07-03 | 2023-08-01 | 合众新能源汽车股份有限公司 | Remote diagnosis method, device, computer equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102073319A (en) * | 2011-01-25 | 2011-05-25 | 武汉理工大学 | Multifunctional comprehensive type electric control automobile fault diagnosis system |
| US20140012947A1 (en) * | 2012-07-06 | 2014-01-09 | Softing Ag | Apparatus for controlling communication between a host system and control devices |
| CN103744707A (en) * | 2014-01-20 | 2014-04-23 | 深圳市道通科技有限公司 | Method, device and system for upgrading program of VCI (virtual channel identifier) equipment |
| CN105138373A (en) * | 2015-08-27 | 2015-12-09 | 深圳市元征软件开发有限公司 | Vehicle diagnosis device firmware upgrading method and device |
| CN105591824A (en) * | 2016-01-14 | 2016-05-18 | 杭州赫智电子科技有限公司 | Method and system for firmware upgrade |
| CN108228222A (en) * | 2017-12-27 | 2018-06-29 | 努比亚技术有限公司 | A kind of upgrade method of firmware data, mobile terminal and computer storage media |
| CN109725921A (en) * | 2019-01-07 | 2019-05-07 | 深圳市道通科技股份有限公司 | A kind of method, apparatus and automobile fault diagnostic apparatus of the update of VCI equipment firmware |
-
2020
- 2020-08-28 CN CN202010883678.4A patent/CN112162765A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102073319A (en) * | 2011-01-25 | 2011-05-25 | 武汉理工大学 | Multifunctional comprehensive type electric control automobile fault diagnosis system |
| US20140012947A1 (en) * | 2012-07-06 | 2014-01-09 | Softing Ag | Apparatus for controlling communication between a host system and control devices |
| CN103744707A (en) * | 2014-01-20 | 2014-04-23 | 深圳市道通科技有限公司 | Method, device and system for upgrading program of VCI (virtual channel identifier) equipment |
| CN105138373A (en) * | 2015-08-27 | 2015-12-09 | 深圳市元征软件开发有限公司 | Vehicle diagnosis device firmware upgrading method and device |
| CN105591824A (en) * | 2016-01-14 | 2016-05-18 | 杭州赫智电子科技有限公司 | Method and system for firmware upgrade |
| CN108228222A (en) * | 2017-12-27 | 2018-06-29 | 努比亚技术有限公司 | A kind of upgrade method of firmware data, mobile terminal and computer storage media |
| CN109725921A (en) * | 2019-01-07 | 2019-05-07 | 深圳市道通科技股份有限公司 | A kind of method, apparatus and automobile fault diagnostic apparatus of the update of VCI equipment firmware |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112764781A (en) * | 2021-01-28 | 2021-05-07 | 深圳市科陆电子科技股份有限公司 | Platform area intelligent terminal, alternate acquisition board firmware upgrading method, system and storage medium |
| CN113835729A (en) * | 2021-09-23 | 2021-12-24 | 深圳市元征科技股份有限公司 | Upgrading method and device, terminal equipment and computer readable storage medium |
| CN113835729B (en) * | 2021-09-23 | 2024-01-05 | 深圳市元征科技股份有限公司 | Upgrading method, upgrading device, terminal equipment and computer readable storage medium |
| CN116520815A (en) * | 2023-07-03 | 2023-08-01 | 合众新能源汽车股份有限公司 | Remote diagnosis method, device, computer equipment and storage medium |
| CN116520815B (en) * | 2023-07-03 | 2023-10-17 | 合众新能源汽车股份有限公司 | Remote diagnosis method, device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112162765A (en) | Firmware upgrading method, upper computer and storage medium | |
| CN110515366B (en) | Fault diagnosis method and device | |
| CN108227675B (en) | Vehicle diagnosis method, device, terminal and computer-readable storage medium | |
| CN108494771B (en) | Electronic device, firewall opening verification method and storage medium | |
| CN112286170B (en) | Vehicle ECU (electronic control Unit) flashing method, device and equipment and storage medium | |
| CN103164368B (en) | The method and system of a kind of embedded device compatible different addresses mapped inner-storage chip | |
| CN103365701A (en) | Work method of analog card reader and analog communication system | |
| CN104111844A (en) | Method and system for installing application programs into mobile terminals | |
| CN111176695A (en) | Vehicle ECU configuration method, server and terminal | |
| KR100757229B1 (en) | Method and apparatus for diagnosing operating systems resources to support USB device driver development on Linux systems | |
| WO2023174217A1 (en) | Vehicle ethernet diagnosis method and apparatus, and device and medium | |
| CN107656765A (en) | A kind of method, system and the terminal device of equipment initialization | |
| CN115022223A (en) | Method and system for carrying out automatic test on TBOX through UDS | |
| CN113835729A (en) | Upgrading method and device, terminal equipment and computer readable storage medium | |
| CN109491890A (en) | The interface scans method and terminal device of application program | |
| CN105681038B (en) | A kind of debugging permission control method and system based on mobile terminal | |
| CN115454896A (en) | SMBUS-based SSD MCTP control message verification method and device, computer equipment and storage medium | |
| CN112416509B (en) | Virtual machine control system and related equipment | |
| CN112087346B (en) | Diagnostic conversion box state determination method, upper computer and storage medium | |
| CN113177014A (en) | Serial port communication method based on inspection mode and serial port chip | |
| CN112650677A (en) | Interface calling method, device, server and storage medium | |
| CN107171824B (en) | Wifi disconnection processing method of terminal, terminal and storage device | |
| CN101561760A (en) | Method for upgrading firmware of interface card | |
| CN114116362B (en) | Verification equipment use management method, system, storage medium and equipment | |
| CN114503041B (en) | Vehicle diagnosis method, diagnosis connector and diagnosis device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210101 |