CN110647333A - Firmware upgrading method and equipment configured to upgrade firmware therein - Google Patents
Firmware upgrading method and equipment configured to upgrade firmware therein Download PDFInfo
- Publication number
- CN110647333A CN110647333A CN201810666976.0A CN201810666976A CN110647333A CN 110647333 A CN110647333 A CN 110647333A CN 201810666976 A CN201810666976 A CN 201810666976A CN 110647333 A CN110647333 A CN 110647333A
- Authority
- CN
- China
- Prior art keywords
- firmware
- version
- storage area
- new
- area
- 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 22
- 230000002159 abnormal effect Effects 0.000 claims description 21
- 238000012544 monitoring process Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 6
- 238000004891 communication Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 230000001154 acute effect Effects 0.000 description 1
- 239000013078 crystal Substances 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 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
Abstract
The invention relates to a method for upgrading firmware of equipment, which comprises the following steps: the equipment acquires the new version firmware; the boot program of the equipment erases the current firmware version from the application program area of the equipment and writes the new firmware version into the application program area; the equipment obtains the running state information of the written firmware; and when the running state information meets the first condition, the bootstrap program erases the new version firmware from the application program area and writes the current version firmware into the application program area. The firmware upgrading process does not need manual intervention, and the continuity and the stability of equipment operation are improved.
Description
Technical Field
The present invention relates to the field of firmware upgrading technology, and more particularly, to a firmware upgrading method and corresponding device.
Background
In the normal use process of various user devices, the firmware program of the device always needs to be upgraded for various reasons, for example, to overcome bugs existing in the original firmware, to enhance the compatibility of the device, and to develop new functions of the device. However, the upgrading of the firmware has a risk of upgrading failure, and once the upgrading fails, the equipment of the user cannot be used normally. The above problems are particularly acute or particularly problematic in embedded devices.
To avoid this, some existing solutions are to save two versions of the application (firmware) in the device at the same time, and if the device is running abnormally due to a firmware upgrade failure, a backup program may be started. However, this situation makes the device resource overhead large, e.g., the program space utilization low. Another part of the existing solutions is that the backup firmware is only provided with networking functionality, and if a firmware upgrade fails, an attempt is made to re-download a new version of firmware using the networking-capable backup firmware, but this can delay the upgrade process, impact the user experience, and even require manual intervention.
Disclosure of Invention
An object of the present invention is to provide a mechanism for implementing automatic rollback when a firmware upgrade fails without manual intervention.
In order to achieve the above purpose, the present invention provides a technical solution:
a method of upgrading firmware of a device, comprising: a) the equipment acquires the new version firmware; b) the boot program of the equipment erases the current version firmware from the application program area of the equipment and writes the new version firmware into the application program area; c) the equipment acquires the running state information of the written firmware; and d), when the running state information meets the first condition, the bootstrap program erases the new version firmware from the application program area and writes the current version firmware into the application program area.
Preferably, the first condition comprises at least one of: the stable operation time of the new firmware version is less than the first time; the restarting frequency of the new firmware version exceeds a first threshold value; the new version of firmware generates a predetermined exception; and the number of times the new version firmware enters the abnormal interruption exceeds a second threshold.
Preferably, step a) further comprises: and storing the new version firmware into a first storage area in a memory of the equipment, wherein the memory further comprises a second storage area, and the second storage area stores the current version firmware.
Preferably, step c) further comprises: and reporting the firmware upgrading record and the abnormal interruption record stored in the memory to the cloud server together.
Preferably, step b) further comprises: the boot process performs integrity and/or legitimacy checks on the written firmware.
Preferably, step d) further comprises: the boot program extracts the current version firmware from the second storage area to write into the application program area.
The present invention also discloses an apparatus configured to upgrade firmware therein, the apparatus comprising: the storage unit comprises a first storage area and a second storage area, wherein the first storage area is used for storing the new version firmware acquired by the equipment, and the second storage area is used for storing the current version firmware of the equipment; an application area for running the written firmware to implement functionality of the device; the boot program module is respectively coupled with the storage unit and the application program area and is used for erasing the current version firmware from the application program area and writing the new version firmware into the application program area when the firmware is upgraded; and when the running state information of the written firmware meets a first condition, extracting the current version firmware from the second storage area and writing the current version firmware into the application program area.
According to the method for upgrading the firmware of the equipment, provided by the invention, when the upgrading of the new version firmware fails, the equipment can automatically return to the current version firmware without manual intervention, so that the continuity and the stability of the operation of the equipment are improved. According to the equipment provided by the invention, especially the embedded equipment, the firmware version can be automatically upgraded and backed, the upgrading process is fast, and the user experience is good.
Drawings
Fig. 1 is a flowchart illustrating a firmware upgrading method for an embedded device according to a first embodiment of the present invention.
Fig. 2 is a block diagram of an embedded device according to a second embodiment of the present invention.
Detailed Description
In the following description specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that embodiments of the invention may be practiced without these specific details. In the present invention, specific numerical references such as "first element", "second device", and the like may be made. However, specific numerical references should not be construed as necessarily subject to their literal order, but rather construed as "first element" as opposed to "second element".
The specific details set forth herein are merely exemplary and may be varied while remaining within the spirit and scope of the invention. The term "coupled" is defined to mean either directly connected to a component or indirectly connected to the component via another component.
It should be noted that, although the embodiments of the present invention have been described with respect to embedded devices, those skilled in the art will appreciate that the concepts and features of the present invention can be applied to other devices in an equivalent, alternative or combined manner without departing from the claims of the present invention, and still achieve similar technical effects.
Preferred embodiments of methods, systems and devices suitable for implementing the present invention are described below with reference to the accompanying drawings. Although embodiments are described with respect to a single combination of elements, it is to be understood that the invention includes all possible combinations of the disclosed elements. Thus, if one embodiment includes elements A, B and C, while a second embodiment includes elements B and D, the invention should also be considered to include A, B, C or the other remaining combinations of D, even if not explicitly disclosed.
As shown in fig. 1, a firmware upgrade method for an embedded device according to a first embodiment of the present invention includes the following steps S10-S14.
Step S10, the embedded device determines whether there is a new firmware version to be acquired.
In particular, this step is an optional step. As can be appreciated by those skilled in the art, the firmware upgrading process can be initiated by the embedded device or initiated by the cloud server dedicated to upgrading. In this step, the embedded device can know whether a new version of firmware is available for acquisition by notification from the external system. The external system may include, for example, a cloud server, or a dedicated firmware upgrade notification unit.
And step S11, the embedded device acquires the new version firmware.
In this step, the embedded device may obtain the new version firmware by downloading, for example, from the cloud server. Alternatively, the embedded device may obtain the new version firmware from an accessed memory card (e.g., an SD card). The embedded device may also obtain new versions of firmware from external systems via the USB bus. In particular, a new version of firmware is obtained by an application on the device.
After the download (or otherwise acquisition) is complete, the embedded device preferably performs an integrity and/or legitimacy check on the new version of firmware. In particular, the integrity and/or legitimacy checks are performed by an application on the device.
More specifically, the embedded device has a memory or a storage space outside the application program area, for example, a Flash memory, which may also be a hard disk, a storage area in the main chip of the device (if the storage area in the main chip is large enough), an SD card, or the like. The memory stores the firmware of the current version; optionally, the current version of firmware is marked as "backup". The embedded equipment stores the acquired new firmware into a memory; optionally, the new version of firmware is also marked as "temporary". The memory may also store firmware upgrade records and/or abort records as appropriate. It should be noted that the new version firmware and the current version firmware can be regarded as being stored in two storage areas (e.g. the first storage area and the second storage area, or the "temporary" storage area and the "backup" storage area), respectively, but there is no limitation to the structure of the memory, either logically or physically.
Alternatively, the memory may include two logically or physically separable storage areas for storing firmware: the embedded device stores the acquired new version firmware into a first storage area in the memory, and the memory further comprises a second storage area, and the second storage area stores the current version firmware.
Step S12, the boot program of the embedded device erases the current version firmware from the application area of the embedded device and writes the new version firmware into the application area.
As an example, to write a new version of firmware, the embedded device will reboot, and the MCU of the embedded device enters the boot program.
The boot program detects that a new firmware exists, and selects to enter an upgrading mode; in the upgrading mode, the boot program erases the firmware of the current version and writes the firmware of the new version into the application program area; the bootstrap program also carries out integrity and validity check on the written firmware again, if the check result is abnormal, the following step S14 can be directly skipped to select firmware version rollback, if the check result is normal, the bootstrap program normally skips to the newly written firmware program, and then the embedded device runs the new firmware version to realize various functionalities.
Optionally, after writing the new version firmware to the application area, the boot program also modifies the flag of the new version firmware from "temporary" to "used". The current version firmware maintains a "backup" flag.
Alternatively, a similar operation may be performed by modifying the storage tag of the first storage area and the second storage area. The first and second memory areas may be distinguished by a storage flag, for example, the storage flag of the first memory area is "01", the storage flag of the second memory area is "02", the first memory area will become the second memory area, and the second memory area will become the first memory area by changing the storage flag of the first memory area to "02" and the storage flag of the second memory area to "01".
Step S13, the embedded device obtains the running state information of the written firmware.
During the execution of a new version of firmware, the application may periodically (e.g., every 5 minutes) write an elapsed time flag to the time storage location of the memory. The time storage location may be a specific storage area in the memory. In particular, since most embedded devices are clocked in a crystal mode, the embedded devices preferably write an elapsed time flag. In the case of non-embedded devices, the time stamp may also be written directly.
Meanwhile, the embedded device may further record the following various kinds of operating state information on the written firmware in, for example, other predetermined storage areas of the memory: stable running time of the new version firmware; the number of times the new version of firmware is restarted; an abort type for the new version of firmware; and the number of times the new version firmware enters an abort.
Step S14, when the running state information satisfies the first condition, the boot program erases the new version firmware from the application program area and writes the current version firmware into the application program area.
Typically, a boot program is automatically run by the device upon startup or restart. The boot program may read the operating state information from the memory.
According to a preferred embodiment of the present invention, the first condition may be any one or a combination of more than one of the following. These items include: the stable operation time of the new firmware version is less than the first time; the restarting frequency of the new firmware version exceeds a first threshold value; the new version of firmware generates a predetermined exception; and the number of times the new version firmware enters the abnormal interruption exceeds a second threshold. The first condition may further include a number of times the new version firmware generates the predetermined exception exceeds a third threshold.
Specifically, the predetermined exception generally includes an exception generated by a new firmware version in a specific scenario, such as a Bug triggered under a special communication or special operation. The predetermined exception may be, for example, a hard error (Hardfault). Typically, the interrupt program will save an exception log in an exception log area of memory. The type of the abnormal interrupt may be obtained by reading a log generated after the abnormal interrupt (e.g., whether a predetermined abnormality is generated), or may be obtained by reading another log or may be obtained in real time.
As a specific example, if the written firmware operating state information satisfies a first condition, for example, the number of times of restarting the new firmware version exceeds a corresponding threshold or the number of times of abnormal interruption exceeds a corresponding threshold (for example, 6 times) within a certain time (i.e., a first duration, for example, 30 minutes) according to the elapsed time flag recorded in the memory, the first condition is considered to be satisfied. The satisfaction of the first condition by the operating state information can indicate that there is a problem with the new version of firmware (e.g., program Bug, incompatibility with current devices, or other problems) and that a firmware (version) rollback operation is required.
In a firmware version rollback operation, in particular, the boot program may modify the flag of the new version firmware from "used" to "invalid" and then modify the flag of the current version firmware from "backup" to "valid"; the bootstrap program further rewrites the firmware of the current version into an application program area in the embedded equipment; the boot program starts the firmware of the current version, and the application program realizes the corresponding function of the embedded equipment.
In addition, the embedded device can report the firmware upgrading record and the abnormal interruption record stored in the memory to the cloud server together, so that the cloud server can verify the program Bug of the new firmware or the incompatibility problem.
As a specific example, if a user triggers a specific scenario and the new firmware version causes a system crash of the embedded device within the first duration, the diagnostic program of the embedded device may log an exception log into an exception log area of the memory, for example. At this time, the bootstrap program of the embedded device restarts again, checks the abnormal log, and if the crash meets the predetermined abnormal type, or the number of abnormal interrupts in the log reaches a first threshold (for example, 6 times), or the crash meets the predetermined abnormal type in the log reaches a second threshold, the bootstrap program changes the state of the new version firmware from "used" to "invalid", and changes the state of the current version firmware from "backup" to "valid". Subsequently, the boot program performs a firmware version rollback operation according to the current version of firmware in the "valid" state, that is, writes the firmware version rollback operation into an application program area of the embedded device, so as to ensure that the user continues to use the embedded device.
As another specific example, if a user triggers a specific scenario, whether within a first time period or not, and the new firmware version causes a system crash of the embedded device, the diagnostic program of the embedded device may log an exception to an exception log area, for example, of the memory. At this time, the bootstrap program of the embedded device restarts again, checks the abnormal log, and if the crash meets the predetermined abnormal type, or the number of abnormal interrupts in the log reaches a first threshold (for example, 6 times), or the crash meets the predetermined abnormal type in the log reaches a second threshold, the bootstrap program changes the state of the new version firmware from "used" to "invalid", and changes the state of the current version firmware from "backup" to "valid". Subsequently, the boot program performs a firmware version rollback operation according to the current version of firmware in the "valid" state, that is, writes the firmware version rollback operation into an application program area of the embedded device, so as to ensure that the user continues to use the embedded device.
That is, in determining whether the predetermined anomaly or the abnormal interruption has reached the predetermined number of times, a time limit may be set (i.e., only within the time limit is counted); or not provided; or a longer time limit may be set, for example only counted for a second period of time (e.g., two days). The technical effect brought by the mode is as follows: after a longer time (e.g., two days), it may still be rolled back automatically (i.e., a firmware version rollback operation is performed).
In some embodiments of the invention, at least a portion of the system may be implemented using a distributed set of computing devices connected by a communications network, or may be implemented based on a "cloud". In such a system, multiple computing devices operate together to provide services by using their shared resources.
A "cloud" based implementation may provide one or more advantages, including: openness, flexibility and extensibility, centrally manageable, reliable, scalable, optimized for computing resources, having the ability to aggregate and analyze information across multiple users, connecting across multiple geographic areas, and the ability to use multiple mobile or data network operators for network connectivity.
On the other hand, if the running state information does not meet the first condition, the running of the new firmware version is normal, so that the firmware version rollback operation is not required.
For example, if the system restart times do not exceed a limit value within a specified time, the new version firmware is considered to run normally; at this time, the state of the new version firmware in the first storage area of the memory is modified to be 'valid', the state of the current version firmware in the second storage area is modified to be 'previous version', and backup or erasure of the 'previous version' firmware can be selected. Because the first storage area and the second storage area can be distinguished by the storage mark, under the condition that the new version firmware is upgraded successfully, the first storage area can be set as the second storage area, so that the new second storage area backs up the currently running firmware version, and the original second storage area is set as the new first storage area to download the possibly updated firmware version later.
Preferably, the embedded device restarts each time, the bootstrap program checks the integrity and the validity of the application program (firmware), if the integrity and the validity check result are abnormal and the result is still abnormal after a plurality of retries, the bootstrap program judges that the new version firmware has a problem, modifies the state of the new version firmware in the first storage area of the memory to 'invalid', and modifies the state of the current version firmware in the second storage area of the memory to 'valid'; and then the rollback operation is carried out by using the current version firmware which is set to the effective mark.
As shown in fig. 2, a second embodiment of the present invention provides a user device, as a more specific example, an embedded device, which includes a memory (including but not limited to Flash memory, other storage or storage space), an application area 201, and a bootstrap module 301. Optionally, the memory is external to or integrated with the device.
The memory specifically includes a first storage area 101 and a second storage area 102, where the first storage area 101 is used for storing the new version firmware acquired by the embedded device, and the second storage area 102 is used for backing up the current version firmware of the embedded device.
The application area 201 is used to run the written firmware to implement the functionality of the embedded device.
The boot program module 301 is coupled to the memory and the application program area 201, respectively, and when firmware is upgraded, it erases the current version firmware from the application program area and writes the new version firmware into the application program area; and when firmware rollback is performed, the boot program module 301 extracts the current version firmware from the second storage area and writes the current version firmware into the application program area.
As a further improvement of the memory, the first storage area 101 and the second storage area 102 are logical storage areas distinguished by flag bits, in other words, the flag bits of the two storage areas are reset, that is, the original first storage area can be set as a new second storage area, and the original second storage area can be set as a new first storage area.
The application area 201 preferably includes an operation monitoring unit for recording operation state information of the written firmware. When the operation state information indicates that there is a problem with the new firmware version, the boot program module 301 starts a firmware version rollback operation according to the notification of the operation monitoring unit.
The above description is only for the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Various modifications may be made by those skilled in the art without departing from the spirit of the invention and the appended claims.
Claims (10)
1. A method of upgrading firmware of a device, comprising:
a) the equipment acquires the new version firmware;
b) the boot program of the equipment erases the current firmware version from the application program area of the equipment and writes the new firmware version into the application program area;
c) the device obtains the running state information of the written firmware; and
d) and when the running state information meets a first condition, the bootstrap program erases the new version firmware from the application program area and writes the current version firmware into the application program area.
2. The method of claim 1, wherein the operational status information comprises at least one of:
stable running time of the new version firmware;
the number of times the new version of firmware is restarted;
an abort type for the new version of firmware; and
the number of times the new version of firmware enters an abort.
3. The method of claim 2, wherein the first condition comprises at least one of:
the stable operation time of the new firmware version is less than the first time;
the restarting frequency of the new firmware version exceeds a first threshold value;
the new version firmware generates a predetermined exception; and
and the number of times of the new version firmware entering the abnormal interruption exceeds a second threshold value.
4. The method of claim 1, wherein step a) further comprises:
and storing the new version firmware into a first storage area in a memory of the equipment, wherein the memory further comprises a second storage area, and the second storage area stores the current version firmware.
5. The method of claim 4, wherein step c) further comprises:
and reporting the firmware upgrading record and the abnormal interruption record stored in the memory to a cloud server together.
6. The method of claim 4, wherein step b) further comprises:
the boot program performs integrity and/or legitimacy checks on the written firmware.
7. The method of claim 4, wherein step d) further comprises:
the boot program extracts the current version firmware from the second storage area to write into the application program area.
8. An apparatus configured to upgrade firmware therein, the apparatus comprising:
the storage unit comprises a first storage area and a second storage area, wherein the first storage area is used for storing the new version firmware acquired by the equipment, and the second storage area is used for storing the current version firmware of the equipment;
an application area for running the written firmware to implement functionality of the device; and
the boot program module is respectively coupled with the storage unit and the application program area and used for erasing the current version firmware from the application program area and writing the new version firmware into the application program area when the firmware is upgraded; and when the running state information of the written firmware meets a first condition, extracting the current version firmware from the second storage area and writing the current version firmware into the application program area.
9. The apparatus of claim 8, wherein the first storage area and the second storage area are logical storage areas distinguished by a flag bit.
10. The apparatus according to claim 8 or 9, wherein the application program area comprises an operation monitoring unit for recording operation state information of the written firmware.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810666976.0A CN110647333A (en) | 2018-06-26 | 2018-06-26 | Firmware upgrading method and equipment configured to upgrade firmware therein |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810666976.0A CN110647333A (en) | 2018-06-26 | 2018-06-26 | Firmware upgrading method and equipment configured to upgrade firmware therein |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110647333A true CN110647333A (en) | 2020-01-03 |
Family
ID=68988955
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810666976.0A Pending CN110647333A (en) | 2018-06-26 | 2018-06-26 | Firmware upgrading method and equipment configured to upgrade firmware therein |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110647333A (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200081697A1 (en) * | 2018-09-06 | 2020-03-12 | Arm Limited | Methods for performing a rollback-capable software update at a device |
| CN111240723A (en) * | 2020-03-13 | 2020-06-05 | 乐普医学电子仪器股份有限公司 | Method for upgrading embedded program |
| CN112130912A (en) * | 2020-08-28 | 2020-12-25 | 山东云海国创云计算装备产业创新中心有限公司 | Method and device for preventing refresh failure of device to be refreshed |
| CN112433739A (en) * | 2020-11-11 | 2021-03-02 | 广州鲁邦通物联网科技有限公司 | Firmware upgrading method |
| CN112667265A (en) * | 2021-01-20 | 2021-04-16 | 北京经纬恒润科技股份有限公司 | Method and device for updating bootstrap program |
| CN112817620A (en) * | 2021-01-08 | 2021-05-18 | 日立楼宇技术（广州）有限公司 | Controller terminal program updating method, device, computer equipment and storage medium |
| CN112988213A (en) * | 2021-04-13 | 2021-06-18 | 荣耀终端有限公司 | Program data updating method, electronic equipment and computer storage medium |
| CN113157303A (en) * | 2021-05-27 | 2021-07-23 | 盈合(深圳)机器人与自动化科技有限公司 | Upgrading method, embedded system, terminal and computer storage medium |
| CN113672258A (en) * | 2021-08-16 | 2021-11-19 | 一汽解放汽车有限公司 | System upgrading method and device for vehicle, computer equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050033933A1 (en) * | 2003-08-04 | 2005-02-10 | Hetrick William A. | Systems and methods for modifying disk drive firmware in a raid storage system |
| CN101436138A (en) * | 2007-11-16 | 2009-05-20 | 苏州科达通信技术发展有限公司 | Control device and control method for software upgrade and dynamic rolling back |
| CN105912356A (en) * | 2016-03-31 | 2016-08-31 | 武汉光迅科技股份有限公司 | Optical module firmware program online upgrade method supporting version fallback |
| CN107506194A (en) * | 2017-08-24 | 2017-12-22 | 北京百悟科技有限公司 | Application version, which retracts, determines method and device |
-
2018
- 2018-06-26 CN CN201810666976.0A patent/CN110647333A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050033933A1 (en) * | 2003-08-04 | 2005-02-10 | Hetrick William A. | Systems and methods for modifying disk drive firmware in a raid storage system |
| CN101436138A (en) * | 2007-11-16 | 2009-05-20 | 苏州科达通信技术发展有限公司 | Control device and control method for software upgrade and dynamic rolling back |
| CN105912356A (en) * | 2016-03-31 | 2016-08-31 | 武汉光迅科技股份有限公司 | Optical module firmware program online upgrade method supporting version fallback |
| CN107506194A (en) * | 2017-08-24 | 2017-12-22 | 北京百悟科技有限公司 | Application version, which retracts, determines method and device |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20200081697A1 (en) * | 2018-09-06 | 2020-03-12 | Arm Limited | Methods for performing a rollback-capable software update at a device |
| US11556326B2 (en) * | 2018-09-06 | 2023-01-17 | Arm Limited | Methods for performing a rollback-capable software update at a device |
| CN111240723A (en) * | 2020-03-13 | 2020-06-05 | 乐普医学电子仪器股份有限公司 | Method for upgrading embedded program |
| CN112130912A (en) * | 2020-08-28 | 2020-12-25 | 山东云海国创云计算装备产业创新中心有限公司 | Method and device for preventing refresh failure of device to be refreshed |
| CN112433739A (en) * | 2020-11-11 | 2021-03-02 | 广州鲁邦通物联网科技有限公司 | Firmware upgrading method |
| CN112817620A (en) * | 2021-01-08 | 2021-05-18 | 日立楼宇技术（广州）有限公司 | Controller terminal program updating method, device, computer equipment and storage medium |
| CN112817620B (en) * | 2021-01-08 | 2023-09-26 | 日立楼宇技术（广州）有限公司 | Controller terminal program updating method, device, computer equipment and storage medium |
| CN112667265A (en) * | 2021-01-20 | 2021-04-16 | 北京经纬恒润科技股份有限公司 | Method and device for updating bootstrap program |
| CN112988213A (en) * | 2021-04-13 | 2021-06-18 | 荣耀终端有限公司 | Program data updating method, electronic equipment and computer storage medium |
| CN112988213B (en) * | 2021-04-13 | 2023-11-14 | 荣耀终端有限公司 | Program data updating method, electronic equipment and computer storage medium |
| CN113157303A (en) * | 2021-05-27 | 2021-07-23 | 盈合(深圳)机器人与自动化科技有限公司 | Upgrading method, embedded system, terminal and computer storage medium |
| CN113672258A (en) * | 2021-08-16 | 2021-11-19 | 一汽解放汽车有限公司 | System upgrading method and device for vehicle, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110647333A (en) | Firmware upgrading method and equipment configured to upgrade firmware therein | |
| JP4363676B2 (en) | Computer system | |
| US7694165B2 (en) | Automation of bare metal recoveries | |
| US20140310698A1 (en) | Apparatus and method for upgrading firmware of mobile terminal | |
| US20110004871A1 (en) | Embedded electronic device and firmware updating method thereof | |
| US20150089479A1 (en) | Method for pre-testing software compatibility and system thereof | |
| CN110333891A (en) | The method of enhanced OTA upgrading based on Internet of Things | |
| JP2006527423A (en) | Computer operation system repair method | |
| CN112612524A (en) | Method, device and equipment for starting Linux system and storage medium | |
| US20200250313A1 (en) | Bios recovery and update | |
| CN104915226A (en) | Network device software starting method, device and network device | |
| CN109101247B (en) | Method and device for installing driver and server | |
| CN103970564A (en) | Automatic repairing and upgrading method of embedded operating system and embedded operating system with automatic repairing and upgrading functions | |
| CN111090546B (en) | Method, device and equipment for restarting operating system and readable storage medium | |
| CN113190256B (en) | Upgrading method, device and equipment | |
| CN115658113A (en) | Server self-starting method and device, readable storage medium and electronic equipment | |
| CN112416411B (en) | Upgrading method and device, equipment end, server and computer readable medium | |
| JP6599725B2 (en) | Information processing apparatus, log management method, and computer program | |
| CN113032183A (en) | System management method, device, computer equipment and storage medium | |
| US10509646B2 (en) | Software update rollbacks using file system volume snapshots | |
| KR100832269B1 (en) | Program update method and system for wireless communication terminal | |
| CN115951949A (en) | Recovery method and device for configuration parameters of BIOS (basic input output System) and computing equipment | |
| CN111897543A (en) | Software management method, device, management equipment and storage medium | |
| CN112433739B (en) | Firmware upgrading method | |
| CN114741119A (en) | System starting method and device, computer equipment and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200103 |