CN106775847B - A kind of board card software version update method and device - Google Patents

Abstract

The embodiment of the present invention discloses a method and device for updating a software version of a board card. The method includes: acquiring the checksum of the external upgrade file when detecting that there is an external upgrade file; confirming the checksum of the target software corresponding to the external upgrade file in the board and the verification of the external upgrade file If the checksum of the target software is inconsistent with the checksum of the external upgrade file, the target software is updated based on the external upgrade file. Through the technical scheme of the present invention, repeated software updates can be prevented, and the reliability and accuracy of software updates can be improved.

Description

A kind of board card software version update method and device

technical field

Embodiments of the present invention relate to a software update technology, and in particular, to a method and device for updating a software version of a board card.

Background technique

With the development of science and technology, more and more electronic devices are provided with pluggable boards, and in the production process of the boards, the software in the boards needs to be updated.

At present, the commonly used software update method is that when the U disk containing the software upgrade package file is inserted into the board, the board will immediately update the corresponding software in the board as long as the upgrade package file is detected.

The defect of the prior art solution is that if the U disk is still inserted on the board after the software update is completed, and when the board is powered on again after being powered off, the software update operation will be repeated, which wastes time.

SUMMARY OF THE INVENTION

Embodiments of the present invention provide a board card software version update method and device, so as to prevent repeated software updates and improve the reliability and accuracy of software updates.

In a first aspect, an embodiment of the present invention provides a method for updating a software version of a board card, including:

When detecting that there is an external upgrade file, obtain the checksum of the external upgrade file;

Confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file;

If the checksum of the target software is inconsistent with the checksum of the external upgrade file, the target software is updated based on the external upgrade file.

In a second aspect, an embodiment of the present invention further provides a device for updating a software version of a board card, the device comprising:

an upgrade file checksum obtaining unit, configured to obtain the checksum of the external upgrade file when an external upgrade file is detected;

a checksum consistency confirmation unit, used to confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file;

A target software update unit, configured to update the target software based on the external upgrade file if the checksum of the target software is inconsistent with the checksum of the external upgrade file.

In the embodiment of the present invention, by confirming whether the checksum of the target software in the board is consistent with the checksum of the external upgrade file, the target software will be updated only when the two are inconsistent, which solves the problem of human error in the prior art. The resulting problem of repeated software updates achieves the effect of preventing repeated software updates, and improves the reliability and accuracy of software updates.

Description of drawings

1 is a schematic flowchart of a method for updating a board software version according to Embodiment 1 of the present invention;

2 is a schematic flowchart of a method for updating a board software version according to Embodiment 2 of the present invention;

3 is a schematic flowchart of a method for updating a board software version according to Embodiment 3 of the present invention;

4 is a schematic flowchart of a method for updating a board software version according to Embodiment 4 of the present invention;

FIG. 5 is a schematic structural diagram of an apparatus for updating a software version of a board card according to Embodiment 5 of the present invention.

Detailed ways

The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention, but not to limit the present invention. In addition, it should be noted that, for the convenience of description, the drawings only show some but not all structures related to the present invention.

Example 1

FIG. 1 is a schematic flowchart of a method for updating a software version of a board card according to Embodiment 1 of the present invention. The method can be applied to the case of updating the software version in the board, and the method can be executed by a device for updating the software version of the board, which can be composed of hardware and/or software, and can generally be integrated in the board and all software versions update function on the board. Specifically include the following:

S110. Obtain the checksum of the external upgrade file when it is detected that there is an external upgrade file.

The external upgrade file can be set on an external memory other than the board, and the external memory is connected to the board. Specifically, the checksum is the sum of a set of data items for verification purposes, that is, the checksum can be used to represent different versions of the same type of file. When the external upgrade file is compiled, the checksum is calculated and automatically added to the file name. By reading the file name of the external file, the checksum of the external upgrade file can be obtained.

Exemplarily, the external upgrade file is set in the U disk, and when the U disk is inserted into the board, the board automatically reads the file name of the external upgrade file in the U disk, so as to obtain the checksum of the external upgrade file.

S120. Confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file.

Specifically, when the board chip is in an empty chip, that is, there is no data, the installed software will record the checksum of each software package as a standard for software version comparison. When there are multiple external upgrade files in the external memory, they correspond to different target software according to the different types of external upgrade files, so as to confirm the checksum of the target software corresponding to the external upgrade files in the board and the difference between the external upgrade files. Checksums are consistent.

Specifically, the trigger condition for the checksum comparison process may be before the board is triggered to automatically update the target software, that is, when an external upgrade file is detected during the normal operation of the board, or when the board is powered on. When an external file is detected, the checksum comparison process is triggered. The checksum comparison process triggered when the board is running normally is performed in the operating system; the checksum comparison process triggered when the board is powered on is performed at the hardware driver layer. Exemplarily, for a TV board, the operating system may be Supernova, and the hardware driver layer may be the Mboot layer.

Specifically, the purpose of performing the checksum comparison is to detect whether the version of the target software in the board is consistent with that of the external upgrade file, so as to determine whether the target software has been updated. If the checksum is consistent, it means that the version of the target software is the same as that of the external upgrade file, that is, the target software has been updated and no further update is required; The software has not been updated, and the target software needs to be updated. The advantage of performing the checksum comparison is that it can effectively prevent the board from repeatedly updating the updated target software when a misoperation occurs.

S130. If the checksum of the target software is inconsistent with the checksum of the external upgrade file, update the target software based on the external upgrade file.

Specifically, if the checksum of the target software is inconsistent with the checksum of the external upgrade file, it means that the versions of the target software and the external upgrade file are inconsistent, that is, the target software has not been updated, so the target software is updated based on the external upgrade file. When the checksum is inconsistent, updating the target software can ensure that the target software has not been updated based on the external upgrade file, thereby improving the reliability and accuracy of the target software updating process.

In the technical solution of this embodiment, by confirming whether the checksum of the target software in the board is consistent with the checksum of the external upgrade file, the target software will be updated only when the two are inconsistent, which solves the problem of artificial intelligence in the prior art. The problem of repeated software updates caused by operational errors achieves the effect of preventing repeated software updates and improves the reliability and accuracy of software updates.

On the basis of the above technical solution, before obtaining the checksum of the external upgrade file when it is detected that there is an external upgrade file, it is preferable to further add: record the checksum of all software installation files in the board.

Specifically, when the board chip is in an empty chip, that is, there is no data, the checksum of the installation file will be recorded as the checksum of the installed target software during the software installation process based on the installation file, which is used for subsequent verification. The sum comparison process provides the checksum of the target software.

Embodiment 2

FIG. 2 is a schematic flowchart of a method for updating a software version of a board card according to Embodiment 2 of the present invention. This embodiment is optimized on the basis of the above-mentioned embodiments, and provides a preferred method for updating the software version of the board card. Specifically, when an external upgrade file is detected, the checksum of the external upgrade file is further optimized to include: when the external upgrade file is detected. When the board detects that an external storage device is connected, it detects whether there is an external upgrade file in the external storage device; if there is an external upgrade file in the external storage device, it obtains the checksum of the external upgrade file.

S210. When the board detects that an external storage device is connected, detect whether there is an external upgrade file in the external storage device.

Among them, the external storage device refers to a device that can store files other than the board card, preferably a U disk, and the external storage device can be connected to the board card through various interfaces, such as a USB (Universal Serial Bus, Universal Serial Bus) interface .

Specifically, when the board detects that an external storage device is connected to its interface, it detects whether there is an external upgrade file in the external storage device. Optionally, it can determine whether there is an external upgrade file in the external storage device by identifying the file type. You can also judge whether there is an external upgrade file by identifying the file name. The advantage of detecting whether there is an external upgrade file in an external storage device is that it can prevent the update operation from incorrectly starting when an external storage device without an external upgrade file is connected to the board and occupying the memory space of the board, thereby improving software updates. reliability and accuracy.

S220. If an external upgrade file exists in the external storage device, obtain a checksum of the external upgrade file.

Specifically, if there is an external upgrade file in the external storage device, the file name of the external upgrade file is read to obtain the checksum recorded in the file name; if there is no external upgrade file in the external storage device, the board maintains the current status. The state remains unchanged, that is, no subsequent judgment update operations are performed. The purpose of obtaining the checksum of the external upgrade file is to provide the checksum of the external upgrade file for subsequent checksum comparison.

Exemplarily, if there is an external upgrade file in the U disk connected to the board, the board automatically reads the file name of the external upgrade file, and extracts the checksum calculated and written into the file name when the external upgrade file is compiled. , and compare it with the checksum of the target software in the board as the checksum of the external upgrade file.

S230. Confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file.

S240. If the checksum of the target software is inconsistent with the checksum of the external upgrade file, update the target software based on the external upgrade file.

The technical solution of this embodiment is to detect whether there is an external upgrade file in the external memory connected to the board, and only obtain the checksum of the external upgrade file when it exists, and confirm that the checksum of the target software in the board is the same as that of the external upgrade file. Whether the checksum of the upgrade file is consistent, the target software will be updated only when the two are inconsistent, which achieves the effect of preventing repeated software updates and improves the reliability and accuracy of software updates.

Embodiment 3

FIG. 3 is a schematic flowchart of a method for updating a software version of a board card according to Embodiment 3 of the present invention. This embodiment is optimized on the basis of the above-mentioned embodiments, and provides a preferred method for updating the software version of the board card. Specifically, the checksum of the target software corresponding to the external upgrade file in the board card and the checksum of the external upgrade file are confirmed in the board card. After checking whether the checksum is consistent, it is further optimized as follows: if the checksum of the target software is consistent with the checksum of the external upgrade file, the default working state of the board is maintained.

S310. Obtain the checksum of the external upgrade file when it is detected that there is an external upgrade file.

S320. Confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file. If no, execute S330; if yes, execute S340.

S330. Update the target software based on the external upgrade file.

S340. Maintain the default working state of the board.

Specifically, if the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file, it means that the target software corresponding to the external upgrade file in the board has been updated based on the external upgrade file, and there is no need to Repeat the update operation again. Maintaining the default working state of the board refers to keeping the previous working state of the board unchanged without performing any other update operations.

Exemplarily, when an external upgrade file is detected when the board is powered on, and it is detected that the checksum of the external upgrade file is consistent with the checksum of the corresponding target software, the board will no longer update the target software. , but continue to power up the board. The advantage of this is that it can prevent the repeated update of the target software, and improve the reliability and accuracy of the software update.

The technical solution of this embodiment is to confirm whether the checksum of the target software in the board is consistent with the checksum of the external upgrade file. When the two are inconsistent, the target software will be updated, and if they are consistent, the default of the board will be maintained. The working state has achieved the effect of preventing repeated software updates, and improved the reliability and accuracy of software updates.

Embodiment 4

FIG. 4 is a schematic flowchart of a method for updating a software version of a board card according to Embodiment 4 of the present invention. This embodiment is optimized on the basis of the above-mentioned embodiments, and provides a preferred method for updating the software version of the board card. Specifically, before updating the target software based on the external upgrade file, the further optimization further includes: reading Checksum of the external upgrade file; replace the checksum with the corresponding checksum of the target software in the board.

S410. Obtain the checksum of the external upgrade file when it is detected that there is an external upgrade file.

S420. Confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file.

S430. If the checksum of the target software is inconsistent with the checksum of the external upgrade file, read the checksum of the external upgrade file.

Specifically, the inconsistency between the checksum of the target software and the checksum of the external upgrade file indicates that the version of the target software is different from the version of the external upgrade file, that is, the target software needs to be updated. At this time, the checksum of the external upgrade file is obtained again. The purpose is to replace the checksum after the target software is updated.

S440. Replace the checksum with the checksum corresponding to the target software in the board.

Specifically, the checksum is used as one of the signs of the target software version information, and the purpose of replacing the checksum of the external upgrade file with the checksum corresponding to the target software is to prevent the target software from being updated due to the difference between the checksum and the updated target software. The target software does not match the problem, which causes the repeated update operation to be triggered by mistake.

Exemplarily, for a TV board, before the software is updated, the software in the board needs to record the checksum of the new software installation file and transfer it to the Mboot layer for recording, while the software checksum data of the old version will be recorded. be wiped before a software update. The advantage of this is that when the board is powered off and then powered on again, the checksum comparison at the hardware driver layer can prevent the problem of repeated updates caused by the software update but the software checksum is not updated. Improve the reliability and accuracy of software updates.

S450. Update the target software based on the external upgrade file.

The technical solution of this embodiment is to confirm whether the checksum of the target software in the board is consistent with the checksum of the external upgrade file. When the two are inconsistent, the target software will be updated, and if they are consistent, the default of the board will be maintained. The working state has achieved the effect of preventing repeated software updates, and improved the reliability and accuracy of software updates.

Embodiment 5

FIG. 5 is a schematic flowchart of an apparatus for updating a software version of a board card according to Embodiment 5 of the present invention. The device can be applied to the situation of updating the software version in the board. The device can be composed of hardware and/or software, and can generally be integrated in the board and all circuit boards that include the function of updating the software version. Referring to FIG. 5 , the board card software version update device includes an upgrade file checksum acquisition unit 510 , a checksum consistency confirmation unit 520 , and a target software update unit 530 . Each module will be described in detail below.

an upgrade file checksum obtaining unit 510, configured to obtain the checksum of the external upgrade file when an external upgrade file is detected;

The checksum consistency confirmation unit 520 is used to confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file;

The target software updating unit 530 is configured to update the target software based on the external upgrade file if the checksum of the target software is inconsistent with the checksum of the external upgrade file.

Optionally, also include:

The installation file checksum obtaining unit is configured to record the checksum of all software installation files in the board before obtaining the checksum of the external upgrade file when it is detected that there is an external upgrade file.

Optionally, the upgrade file checksum acquisition unit 510 is specifically used for:

When the board detects that an external storage device is connected, detect whether there is an external upgrade file in the external storage device;

If the external upgrade file exists in the external storage device, obtain a checksum of the external upgrade file.

Optionally, also include:

The working state maintenance unit is used to confirm whether the checksum of the target software corresponding to the external upgrade file in the board is consistent with the checksum of the external upgrade file, if the checksum of the target software is consistent with the checksum of the external upgrade file. If the checksum of the external upgrade file is consistent, the default working state of the board is maintained.

Optionally, also include:

a checksum reading unit, configured to read the checksum of the external upgrade file before updating the target software based on the external upgrade file;

A checksum replacement unit, configured to replace the checksum with the checksum corresponding to the target software in the board.

The above product can execute the method provided by any embodiment of the present invention, and has corresponding functional modules and beneficial effects for executing the method.

Note that the above are only preferred embodiments of the present invention and applied technical principles. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in detail through the above embodiments, the present invention is not limited to the above embodiments, and can also include more other equivalent embodiments without departing from the concept of the present invention. The scope is determined by the scope of the appended claims.

Claims (8)

1. A method for updating the software version of a board card is characterized in that the method is executed by a hardware driving layer of the board card under the condition that the board card is powered off and then powered on again, and comprises the following steps:

when the board card detects that an external storage device is connected, detecting whether an external upgrade file exists in the external storage device;

if the external upgrading file exists in the external storage equipment, acquiring a checksum of the external upgrading file by reading a file name of the external file;

confirming whether the checksum of the target software corresponding to the external upgrade file in the board card is consistent with the checksum of the external upgrade file;

if the checksum of the target software is inconsistent with the checksum of the external upgrade file, updating the target software based on the external upgrade file;

and if the checksum of the target software is consistent with the checksum of the external upgrade file, indicating that the versions of the target software and the external upgrade file are consistent, and not updating.

2. The method of claim 1, before detecting whether an external upgrade file exists in an external storage device when the board card detects that the external storage device is connected, further comprising:

and recording the checksum of the installation files of all the software in the board card.

3. The method of claim 1, after determining whether the checksum of the target software corresponding to the external upgrade file in the board card is consistent with the checksum of the external upgrade file, further comprising:

and if the checksum of the target software is consistent with the checksum of the external upgrade file, maintaining the default working state of the board card.

4. The method of claim 1, further comprising, prior to said updating the target software based on the external upgrade file:

reading the checksum of the external upgrading file;

and replacing the checksum corresponding to the target software in the board card with the checksum.

5. A board software version updating device is characterized in that the device is configured on a hardware driving layer of a board, and comprises:

the upgrade file verification and acquisition unit is specifically used for detecting that an external storage device is connected to the board card and detecting whether an external upgrade file exists in the external storage device when the board card is powered off and then powered on again; if the external upgrading file exists in the external storage equipment, acquiring a checksum of the external upgrading file by reading a file name of the external file;

the verification and consistency confirming unit is used for confirming whether the verification sum of the target software corresponding to the external upgrade file in the board card is consistent with the verification sum of the external upgrade file;

the target software updating unit is used for updating the target software based on the external upgrade file if the checksum of the target software is inconsistent with the checksum of the external upgrade file; and if the checksum of the target software is consistent with the checksum of the external upgrade file, indicating that the versions of the target software and the external upgrade file are consistent, and not updating.

6. The apparatus of claim 5, further comprising:

and the installation file checksum acquisition unit is used for recording the checksums of the installation files of all the software in the board card before acquiring the checksum of the external upgrade file when the external upgrade file is detected.

7. The apparatus of claim 5, further comprising:

and the working state maintaining unit is used for maintaining the default working state of the board card if the checksum of the target software is consistent with the checksum of the external upgrade file after confirming whether the checksum of the target software corresponding to the external upgrade file in the board card is consistent with the checksum of the external upgrade file.

8. The apparatus of claim 5, further comprising:

a checksum reading unit, configured to read a checksum of the external upgrade file before updating the target software based on the external upgrade file;

and the checksum replacing unit is used for replacing the checksum corresponding to the target software in the board card with the checksum.

Images