CN106775847B - Board card software version updating method and device - Google Patents
Board card software version updating method and device Download PDFInfo
- Publication number
- CN106775847B CN106775847B CN201611090012.3A CN201611090012A CN106775847B CN 106775847 B CN106775847 B CN 106775847B CN 201611090012 A CN201611090012 A CN 201611090012A CN 106775847 B CN106775847 B CN 106775847B
- Authority
- CN
- China
- Prior art keywords
- checksum
- external
- upgrade file
- target software
- board card
- 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.)
- Active
Links
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
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
Abstract
The embodiment of the invention discloses a method and a device for updating a board software version. The method comprises the following steps: when detecting that an external upgrading file exists, acquiring a checksum of the external upgrading 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; and 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. By the technical scheme of the invention, the software can be prevented from being repeatedly updated, and the reliability and the accuracy of software updating are improved.
Description
Technical Field
The embodiment of the invention relates to a software updating technology, in particular to a method and a device for updating a board software version.
Background
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, software in the boards needs to be updated.
At present, a commonly adopted software updating method is that when a usb disk containing a software upgrade package file is inserted into a board card, the board card immediately updates corresponding software in the board card as long as the board card detects the upgrade package file.
The prior art scheme has the defects that if the USB flash disk is inserted on the board card after the software is updated, and when the board card is powered off and then powered on again, the software updating operation can be repeatedly carried out, and time is wasted.
Disclosure of Invention
The embodiment of the invention provides a method and a device for updating a board software version, which are used for preventing software from being updated repeatedly and improving the reliability and accuracy of software updating.
In a first aspect, an embodiment of the present invention provides a method for updating a board software version, including:
when detecting that an external upgrading file exists, acquiring a checksum of the external upgrading 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;
and 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.
In a second aspect, an embodiment of the present invention further provides a device for updating a board software version, where the device includes:
the system comprises an upgrade file check sum acquisition unit, a verification unit and a verification unit, wherein the upgrade file check sum acquisition unit is used for acquiring the check sum of an external upgrade file when the external upgrade file is detected;
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;
and 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.
According to the embodiment of the invention, whether the checksum of the target software in the board card is consistent with the checksum of the external upgrade file is confirmed, and the target software is updated only when the checksum and the external upgrade file are inconsistent, so that the problem of software repeated updating caused by human misoperation in the prior art is solved, the effect of preventing software repeated updating is achieved, and the reliability and accuracy of software updating are improved.
Drawings
Fig. 1 is a schematic flowchart of a method for updating a board software version according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a method for updating a board software version according to a second embodiment of the present invention;
fig. 3 is a schematic flowchart of a method for updating a board software version according to a third embodiment of the present invention;
fig. 4 is a schematic flowchart of a method for updating a board software version according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of a board software version updating apparatus according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic flowchart of a method for updating a board software version according to an embodiment of the present invention. The method can be suitable for the situation of updating the software version in the board card, and can be executed by a board card software version updating device which can be composed of hardware and/or software and can be generally integrated in the board card and all circuit boards with software version updating functions. The method specifically comprises the following steps:
and S110, acquiring the checksum of the external upgrade file when the external upgrade file is detected.
The external upgrade file can be arranged on an external memory outside the board card, and the external memory is connected with the board card. In particular, a checksum is the sum of a set of data items for verification purposes, i.e., the checksum may be used to characterize different versions of the same type of file. And calculating the checksum of the external upgrading file during compiling, automatically adding the checksum to the file name, and reading the file name of the external file to obtain the checksum of the external upgrading file.
Illustratively, the external upgrade file is arranged in the usb disk, and when the usb disk is inserted into the board card, the board card automatically reads the file name of the external upgrade file in the usb disk, so as to obtain the checksum of the external upgrade file.
S120, 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 is confirmed.
Specifically, when the board card chip is in an empty state, that is, there is no data, the installed software records the checksum of each software package to serve as a standard for software version comparison. When a plurality of external upgrading files exist in the external memory, the external upgrading files respectively correspond to different target software according to different types of the external upgrading files, and therefore whether the checksum of the target software corresponding to the external upgrading files in the board card is consistent with the checksum of the external upgrading files is respectively confirmed.
Specifically, the triggering condition for the checksum comparison process may be that the checksum comparison process is triggered before the board is triggered to automatically update the target software, that is, when an external upgrade file is detected in the normal operation process of the board, or when an external file is detected in the power-on process of the board. The verification and comparison process triggered when the board card normally runs is carried out in an operating system; and the checksum comparison process triggered when the board card is powered on is executed in a hardware driving layer. For example, for a television board, the operating system may be Supernova, and the hardware driver layer may be Mboot layer.
Specifically, the purpose of the checksum comparison is to detect whether the version of the target software in the board card is consistent with that of the external upgrade file, so as to determine whether the target software is updated. If the checksums are consistent, the version of the target software is consistent with that of the external upgrade file, namely the target software is updated and does not need to be updated; if the checksums are not consistent, the version of the target software is not consistent with that of the external upgrade file, that is, the target software is not updated, and the target software needs to be updated. The advantage of carrying out the checksum comparison lies in that when misoperation occurs, the board card can be effectively prevented from repeatedly updating the updated target software.
And S130, 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.
Specifically, if the checksum of the target software is inconsistent with the checksum of the external upgrade file, it indicates that the versions of the target software and the external upgrade file are inconsistent, that is, the target software is not updated, so that the target software is updated based on the external upgrade file. And when the checksums are inconsistent, the target software is updated, so that the target software is not updated based on the external upgrade file, and the reliability and the accuracy of the update process of the target software are improved.
According to the technical scheme of the embodiment, whether the checksum of the target software in the board card is consistent with the checksum of the external upgrade file or not is confirmed, and the target software is updated only when the checksum and the external upgrade file are inconsistent, so that the problem of repeated software updating caused by manual misoperation in the prior art is solved, the effect of preventing the repeated software updating is achieved, and the reliability and the accuracy of the software updating are improved.
On the basis of the above technical solution, before the checksum of the external upgrade file is obtained when the external upgrade file is detected, it is preferable to further add: and recording the checksum of the installation files of all the software in the board card.
Specifically, when the board card chip is in an empty state, that is, there is no data, the checksum of the installation file is recorded as the checksum of the installed target software in the software installation process based on the installation file, so as to provide the checksum of the target software for the subsequent checksum comparison process.
Example two
Fig. 2 is a schematic flowchart of a method for updating a board software version according to a second embodiment of the present invention. The embodiment is optimized based on the above embodiment, and provides a preferable method for updating the board software version, specifically, when an external upgrade file is detected, obtaining a checksum of the external upgrade file is further optimized, including: when the board card detects that the external storage equipment is connected, detecting whether an external upgrading file exists in the external storage equipment; and if the external upgrading file exists in the external storage equipment, acquiring the checksum of the external upgrading file.
S210, when the board card detects that the external storage device is connected, whether an external upgrading file exists in the external storage device is detected.
The external storage device is a device capable of storing files except for the board card, and preferably may be a USB disk, and the external storage device may be connected to the board card through various interfaces, for example, a USB (Universal serial bus) interface.
Specifically, when the board card detects that the external storage device is connected to the interface of the external storage device, whether an external upgrade file exists in the external storage device is detected, optionally, whether the external upgrade file exists in the external storage device can be judged by identifying the file type, and whether the external upgrade file exists can also be judged by identifying the file name. The advantage of detecting whether the external upgrade file exists in the external storage device is that the problem that the memory space of the board card is occupied due to the fact that the update operation is started by mistake when the external storage device without the external upgrade file is connected with the board card can be prevented, and therefore reliability and accuracy of software update are improved.
S220, if the external upgrading file exists in the external storage device, the checksum of the external upgrading file is obtained.
Specifically, if an external upgrade file exists in the external storage device, the file name of the external upgrade file is read, so that the checksum recorded in the file name is obtained; if no external upgrade file exists in the external storage device, the board card maintains the existing state unchanged, i.e., no subsequent judgment and update operation is performed. The purpose of obtaining the external upgrade file checksum is to provide the checksum of the external upgrade file for subsequent checksum comparison.
Illustratively, if an external upgrade file exists in the usb disk connected to the board card, the board card automatically reads the file name of the external upgrade file, calculates the external upgrade file during compiling, and provides a checksum written in the file name, and compares the checksum of the external upgrade file with the checksum of the target software in the board card.
And S230, 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.
And S240, 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.
According to the technical scheme, whether the external upgrade file exists in the external memory connected with the board card or not is detected, the checksum of the external upgrade file is obtained when the external upgrade file exists, whether the checksum of the target software in the board card is consistent with the checksum of the external upgrade file or not is confirmed, and the target software is updated when the checksum and the checksum are inconsistent, so that the effect of preventing software from being updated repeatedly is achieved, and the reliability and accuracy of software updating are improved.
EXAMPLE III
Fig. 3 is a schematic flowchart of a method for updating a board software version according to a third embodiment of the present invention. The present embodiment is optimized based on the foregoing embodiments, and provides a preferred method for updating a board software version, specifically, after determining whether a checksum of target software corresponding to an external upgrade file in a board is consistent with a checksum of the external upgrade file, the method further includes: 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.
And S310, acquiring the checksum of the external upgrade file when the external upgrade file is detected.
S320, 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 not, executing S330; if yes, go to S340.
And S330, updating the target software based on the external upgrade file.
And S340, maintaining the default working state of the board card.
Specifically, if 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, it indicates that the target software corresponding to the external upgrade file in the board card has been updated based on the external upgrade file, and no repeated update operation is required. Maintaining the default operating state of the board means that the previous operating state of the board is kept unchanged without any other updating operation.
For example, when the board card is powered on and started, an external upgrade file is detected, and the checksum of the external upgrade file is detected to be consistent with the checksum of the corresponding target software, the board card does not perform an update operation on the target software any more, but continues to be powered on and started. The advantage of doing so is that repeated updates of the target software can be prevented, improving the reliability and accuracy of the software update.
According to the technical scheme of the embodiment, whether the checksum of the target software in the board card is consistent with the checksum of the external upgrade file is determined, the target software is updated only when the checksum of the target software in the board card is inconsistent with the checksum of the external upgrade file, and the default working state of the board card is maintained when the checksum of the target software in the board card is consistent with the checksum of the external upgrade file, so that the effect of preventing repeated software updating is achieved, and the reliability and accuracy of software updating are improved.
Example four
Fig. 4 is a schematic flowchart of a method for updating a board software version according to a fourth embodiment of the present invention. The present embodiment is optimized based on the foregoing embodiments, and provides a preferred board software version updating method, specifically, before updating the target software based on the external upgrade file, the method further includes: reading the checksum of the external upgrade file; and replacing the checksum corresponding to the target software in the board card with the checksum.
S410, when the external upgrade file is detected, the checksum of the external upgrade file is obtained.
And S420, 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.
And S430, if the checksum of the target software is inconsistent with the checksum of the external upgrade file, reading the checksum of the external upgrade file.
Specifically, the fact that the checksum of the target software is inconsistent with the checksum of the external upgrade file means 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, and the purpose of obtaining the checksum of the external upgrade file again at this time is to replace the checksum of the target software after updating.
And S440, replacing the checksum corresponding to the target software in the board card with the checksum.
Specifically, the checksum is used as one of the marks of the version information of the target software, and the checksum corresponding to the target software is replaced by the checksum of the external upgrade file, so that the problem that after the target software is updated, repeated updating operation is triggered by mistake due to the fact that the checksum is not matched with the updated target software can be avoided.
For example, for a television board, before software update, software inside the board records a checksum of a new software installation file and transmits the checksum to the Mboot layer for recording, while an old version of the software checksum data is erased and then software update is performed. The method has the advantages that when the board card is powered on again after power failure, the problem of repeated updating caused by the fact that the software is updated and the checksum of the software is not updated can be solved when the hardware driving layer is used for checking and comparing, and the reliability and the accuracy of software updating are improved.
And S450, updating the target software based on the external upgrade file.
According to the technical scheme of the embodiment, whether the checksum of the target software in the board card is consistent with the checksum of the external upgrade file is determined, the target software is updated only when the checksum of the target software in the board card is inconsistent with the checksum of the external upgrade file, and the default working state of the board card is maintained when the checksum of the target software in the board card is consistent with the checksum of the external upgrade file, so that the effect of preventing repeated software updating is achieved, and the reliability and accuracy of software updating are improved.
EXAMPLE five
Fig. 5 is a schematic flowchart of a board software version updating apparatus according to a fifth embodiment of the present invention. The device can be suitable for the situation of software version updating in the board card, can be composed of hardware and/or software, and can be generally integrated in the board card and all circuit boards containing software version updating functions. Referring to fig. 5, the board software version updating apparatus includes: an upgrade file verification and acquisition unit 510, a verification and consistency confirmation unit 520, and a target software update unit 530, which are described in detail below.
An upgrade file checksum obtaining unit 510, configured to obtain a checksum of an external upgrade file when the external upgrade file is detected;
a checksum consistency confirming unit 520, configured to confirm whether a checksum of the target software corresponding to the external upgrade file in the board card is consistent with a checksum of the external upgrade file;
a target software updating unit 530, 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, the method further includes:
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.
Optionally, the upgrade file checksum obtaining unit 510 is specifically configured to:
when the board card detects that an external storage device is connected, detecting whether an external upgrade file exists in the external storage device;
and if the external upgrading file exists in the external storage equipment, acquiring a checksum of the external upgrading file.
Optionally, the method further includes:
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.
Optionally, the method further includes:
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.
The product can execute the method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention 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.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611090012.3A CN106775847B (en) | 2016-12-01 | 2016-12-01 | Board card software version updating method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611090012.3A CN106775847B (en) | 2016-12-01 | 2016-12-01 | Board card software version updating method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106775847A CN106775847A (en) | 2017-05-31 |
| CN106775847B true CN106775847B (en) | 2020-12-29 |
Family
ID=58915517
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611090012.3A Active CN106775847B (en) | 2016-12-01 | 2016-12-01 | Board card software version updating method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106775847B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107562622A (en) * | 2017-08-29 | 2018-01-09 | 郑州云海信息技术有限公司 | A kind of method of testing and system of checking MCS system firmware automatically updating functions |
| CN108334373A (en) * | 2017-10-16 | 2018-07-27 | 深圳市路畅科技股份有限公司 | A kind of method and system of more MCU upgradings |
| CN113157307A (en) * | 2020-01-07 | 2021-07-23 | 普天信息技术有限公司 | Software version upgrading method and device |
| CN111510220B (en) * | 2020-04-08 | 2021-10-08 | 武汉光迅科技股份有限公司 | Receive and dispatch optical module with USBType-C electricity mouth |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008049060A2 (en) * | 2006-10-18 | 2008-04-24 | Toby Klusmeyer | System, method, and device for updating programmable electronic equipment with a transport device from a deployment server via the internet or other communication medium |
| CN102117218A (en) * | 2011-02-17 | 2011-07-06 | 中兴通讯股份有限公司 | Embedded equipment and method for downloading program of programmable logic device in same |
| CN102184109A (en) * | 2011-04-12 | 2011-09-14 | 杭州华三通信技术有限公司 | Boot software automatic updating control method and device |
| CN102236569A (en) * | 2011-07-20 | 2011-11-09 | 大唐移动通信设备有限公司 | Embedded system and starting method thereof |
| US8271933B1 (en) * | 2009-12-30 | 2012-09-18 | Cadence Design Systems, Inc. | Pin unspecific device planning for printed circuit board layout |
| CN104428751A (en) * | 2014-06-27 | 2015-03-18 | 华为技术有限公司 | Program data updating method and equipment |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102541593A (en) * | 2011-12-20 | 2012-07-04 | 福建星网视易信息系统有限公司 | Rapid comparison method of versions of remote files |
| CN103197597B (en) * | 2013-04-09 | 2015-11-04 | 上海维宏电子科技股份有限公司 | The method that the upgrading of the kinetic control system be separated with human-computer interaction interface controls |
| CN103473088B (en) * | 2013-08-30 | 2018-01-02 | 北京远特科技股份有限公司 | A kind of single-chip microcomputer online upgrading method and system |
| CN104539696B (en) * | 2014-12-26 | 2018-09-11 | 北京像素软件科技股份有限公司 | A kind of method and system of client incremental update |
| CN105068831A (en) * | 2015-07-30 | 2015-11-18 | 深圳市创凯电子有限公司 | Program upgrading method and apparatus |
-
2016
- 2016-12-01 CN CN201611090012.3A patent/CN106775847B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2008049060A2 (en) * | 2006-10-18 | 2008-04-24 | Toby Klusmeyer | System, method, and device for updating programmable electronic equipment with a transport device from a deployment server via the internet or other communication medium |
| US8271933B1 (en) * | 2009-12-30 | 2012-09-18 | Cadence Design Systems, Inc. | Pin unspecific device planning for printed circuit board layout |
| CN102117218A (en) * | 2011-02-17 | 2011-07-06 | 中兴通讯股份有限公司 | Embedded equipment and method for downloading program of programmable logic device in same |
| CN102184109A (en) * | 2011-04-12 | 2011-09-14 | 杭州华三通信技术有限公司 | Boot software automatic updating control method and device |
| CN102236569A (en) * | 2011-07-20 | 2011-11-09 | 大唐移动通信设备有限公司 | Embedded system and starting method thereof |
| CN104428751A (en) * | 2014-06-27 | 2015-03-18 | 华为技术有限公司 | Program data updating method and equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106775847A (en) | 2017-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106775847B (en) | Board card software version updating method and device | |
| US20140310698A1 (en) | Apparatus and method for upgrading firmware of mobile terminal | |
| CN111324192A (en) | System board power supply detection method, device, equipment and storage medium | |
| TWI470420B (en) | Dubugging method and computer system using the smae | |
| CN102467440A (en) | Internal memory error detection system and method | |
| CN106547653B (en) | Computer system fault state detection method, device and system | |
| CN101853171A (en) | On-line upgrade method and device of complicated programmable logical device | |
| US20150067316A1 (en) | Electronic device and testing method | |
| CN113190256B (en) | Upgrading method, device and equipment | |
| JP6880961B2 (en) | Information processing device and log recording method | |
| CN109614118A (en) | A kind of SPI Flash firmware burning method and device | |
| CN103455288A (en) | Information processing apparatus and control method | |
| CN112015587B (en) | Method and device for enhancing reliability of operating system | |
| CN110196730B (en) | Hot patch management method, device and storage medium of application program | |
| KR100706471B1 (en) | Method for update of firm ware in an electronic products | |
| CN106130815B (en) | Board level testing method and device | |
| CN106293708B (en) | Information processing method and storage device | |
| CN114496053A (en) | Data anomaly detection method, device and equipment and computer readable storage medium | |
| US8626992B2 (en) | Storage device with identification information | |
| CN108279937B (en) | Parameter calling method and device, storage medium and electronic equipment | |
| CN113867812A (en) | Method, system, equipment and medium for BMC to acquire link information | |
| CN107766251B (en) | Detection method, system and device for loading image and readable storage medium | |
| JP2009003557A (en) | Device start time diagnostic method, diagnostic program, and start time diagnostic device | |
| CN111857785A (en) | MCU starting method and device and terminal equipment | |
| CN110909378A (en) | Automatic detection method and device, storage medium and electronic equipment |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |