CN104834575A - Firmware recovery method and device - Google Patents
Firmware recovery method and device Download PDFInfo
- Publication number
- CN104834575A CN104834575A CN201510229002.2A CN201510229002A CN104834575A CN 104834575 A CN104834575 A CN 104834575A CN 201510229002 A CN201510229002 A CN 201510229002A CN 104834575 A CN104834575 A CN 104834575A
- Authority
- CN
- China
- Prior art keywords
- firmware
- module
- current version
- version
- cpu
- 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.)
- Granted
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention provides a firmware recovery method and device, which are applied to a CPU (Central Processing Unit) of a BMC (Baseboard Management Controller) in a server. The server comprises a main CPU, a BMC CPU and a plurality of modules, wherein the plurality of modules are connected with the BMC CPU and each module includes firmware needed for respective operation. The method comprises performing the following processing to each module when CPU start fails: determining whether the firmware in the current version in the module is available or not; acquiring firmware in a version to which the corresponding module has already been successfully upgraded from storage equipment when the firmware in the current version is not available; performing firmware recovery to the corresponding module according to the firmware in the version to which the corresponding module has already been successfully upgraded. The firmware recovery method and device provided by the invention have the advantages that the risk that the main CPU cannot start can be effectively reduced and the situation that the system cannot start due to version incompatibility can be detected.
Description
Technical field
The application relates to server technology field, particularly relates to a kind of firmware restoration method and device.
Background technology
Firmware is the program code of the bottom that equipment is run.Owing to there is leak or the constantly upgrading of what's new needs in the firmware in server, when firmware upgrade failure, server will have very large probability to start, and maintenance difficulty is very big, affect and normally use.
Firmware is kept at ROM (Read-Only Memory by prior art, ROM (read-only memory)) in, and the mode adopting two panels ROM to back up, in main ROM when firmware upgrade failure, be switched to backup ROM to run, unsuccessfully cause system to start to avoid upgrading.But, when exist in server a large amount of need the firmware of backup time, this technical scheme will increase the cost of server, and cannot solve firmware upgrade success but cannot starting of causing due to incompatible version.
Summary of the invention
In view of this, the application provides a kind of firmware restoration method and device.
Particularly, the application is achieved by the following technical solution:
The application provides a kind of firmware restoration method, be applied on the baseboard management controller BMC central processor CPU in server, described server comprises host CPU, described BMC CPU and multiple module, described multiple module is connected with described BMC CPU, comprise the firmware needed for each self-operating in each module, the method comprises:
When described host CPU starts unsuccessfully, each module described is handled as follows:
In determination module, whether current version firmware can be used;
When described current version firmware is unavailable, from memory device, obtain the version firmware that respective modules was successfully upgraded;
According to described version firmware of successfully upgrading, firmware restoration is carried out to described respective modules.
The application provides a kind of firmware restoration device, be applied on the baseboard management controller BMC central processor CPU in server, described server comprises host CPU, described BMC CPU and multiple module, described multiple module is connected with described BMC CPU, comprise the firmware needed for each self-operating in each module, this device comprises:
Determining unit, for when described host CPU starts unsuccessfully, determines in each module, whether current version firmware can be used;
Acquiring unit, for when described current version firmware is unavailable, obtains the version firmware that respective modules was successfully upgraded from memory device;
Recovery unit, for carrying out firmware restoration according to described version firmware of successfully upgrading to described respective modules.
Described as can be seen from above, the application adopts and carries out firmware restoration independent of the BMC system of main system, when determining that the host CPU caused due to firmware upgrade starts unsuccessfully, arbitrary version firmware that respective modules successfully upgraded can be obtained carry out firmware restoration from memory device.Effectively can reduce by the application the risk that host CPU cannot start, and can detect that the system caused due to incompatible version cannot start.
Accompanying drawing explanation
Fig. 1 is the server architecture schematic diagram shown in the application one exemplary embodiment;
Fig. 2 is a kind of firmware restoration method flow diagram shown in the application one exemplary embodiment;
Fig. 3 is the underlying hardware structural representation of a kind of firmware restoration device place equipment shown in the application one exemplary embodiment;
Fig. 4 is the structural representation of a kind of firmware restoration device shown in the application one exemplary embodiment.
Embodiment
Here will be described exemplary embodiment in detail, its sample table shows in the accompanying drawings.When description below relates to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawing represents same or analogous key element.Embodiment described in following exemplary embodiment does not represent all embodiments consistent with the application.On the contrary, they only with as in appended claims describe in detail, the example of apparatus and method that some aspects of the application are consistent.
Only for describing the object of specific embodiment at term used in this application, and not intended to be limiting the application." one ", " described " and " being somebody's turn to do " of the singulative used in the application and appended claims is also intended to comprise most form, unless context clearly represents other implications.It is also understood that term "and/or" used herein refer to and comprise one or more project of listing be associated any or all may combine.
Term first, second, third, etc. may be adopted although should be appreciated that to describe various information in the application, these information should not be limited to these terms.These terms are only used for the information of same type to be distinguished from each other out.Such as, when not departing from the application's scope, the first information also can be called as the second information, and similarly, the second information also can be called as the first information.Depend on linguistic context, word as used in this " if " can be construed as into " ... time " or " when ... time " or " in response to determining ".
Usually HOST (master) CPU (Central Processing Unit is comprised in server, central processing unit) and BMC (Baseboard Management Controller, baseboard management controller) CPU, wherein, host CPU is used for business processing, and BMC CPU is used for server state monitoring, outband management and firmware upgrade etc.When the firmware upgrade in server makes mistakes, such as, server power failure in escalation process, then server cannot normally start.
In order to avoid the problems referred to above, prior art adopts the mode of ROM backup, increases a slice ROM in the server and carries out firmware backup, when main ROM upgrading makes mistakes, is switched to backup ROM, utilizes the firmware in backup ROM to start server; Or directly for server selects a slice Large Copacity ROM, mark off boot section, main area and spare area from this ROM, boot section is first run under normal circumstances, guide CPU to be operated in main area, when main area upgrading makes mistakes, be switched to spare area and start server.Technique scheme reduces the probability that server can not start to a certain extent, but too increases the cost of server simultaneously, and cannot solve firmware upgrade success but cannot starting of causing due to incompatible version.
For prior art Problems existing, the application proposes a kind of firmware restoration method, the method adopts carries out firmware restoration independent of the BMC system of main system, when determining that the host CPU caused due to firmware upgrade starts unsuccessfully, arbitrary version firmware that respective modules successfully upgraded can be obtained carry out firmware restoration from memory device.
See Fig. 1, be the server architecture schematic diagram shown in the embodiment of the present application, this schematic diagram illustrate only the main modular in server.HOST CPU is used for business processing; PCH (Platform ControllerHub, south bridge) is for the Peripheral Interface of extension CPU; BMC CPU is used for server state monitoring, outband management and firmware upgrade etc.; BMC ROM is for storing the program of BMC system; ME (Management Engine, management engine) is for initialization and management whole system; BIOS (BasicInput Output System, Basic Input or Output System (BIOS)) is for saved system setting and system self-triggered program etc.; LOGIC (logic) is the digital integrated circuit of a kind of user constitutive logic function voluntarily according to needing separately; Memory device is for preserving the information such as server log.Wherein, preserve respective module in ME, BIOS and LOGIC module respectively and run required firmware.
See Fig. 2, be an embodiment process flow diagram of the application's firmware restoration method, this embodiment is described firmware restoration process.
Step 201, when described host CPU starts unsuccessfully, in determination module, whether current version firmware can be used.
See Fig. 1, the module (ME, BIOS and LOGIC module) of carrying out firmware upgrade and recovery in the embodiment of the present application, is needed all to be connected on BMC CPU, so that BMC CPU operates corresponding module.In below describing, mentioned module all refers to the module comprising firmware.
When host CPU starts unsuccessfully, whether BMC CPU inquires about current version firmware in coupled modules and can use, to determine whether because firmware upgrade causes host CPU to start.BMC CPU all proceeds as follows each module:
The firmware information of current version firmware in acquisition module, verifies the firmware information obtained, is handled as follows according to check results.
When the firmware information verified is incorrect, illustrate that this module may be made mistakes when upper once firmware upgrade, cause the firmware that is written in module incorrect, or this firmware damages in operational process, now, confirms that in this module, current version firmware is unavailable.
When the firmware information verified is correct, successful writing module when last firmware upgrade is described.Now, can judge whether the upgrading mark that there is this module further, this upgrading is masked as the mark arranged after BMC CPU successfully writes firmware to module.
When there is this upgrading mark, after last firmware upgrade is described, host CPU unsuccessful startup, may be because incompatible version causes host CPU to start, now, determine that in this module, current version firmware is unavailable equally.
When there is not this upgrading mark, last firmware upgrade success is described, and after upgrading, host CPU once normally started.Here need supplementary notes a bit, after module successfully writes firmware (namely arranging upgrading mark), if host CPU starts successfully, BMC CPU can remove upgrading mark.Therefore, when firmware information correctly and do not exist again upgrading mark (the current version firmware in module once successfully started) time, confirm that in this module, current version firmware can be used, this time host CPU starts is not unsuccessfully because firmware upgrade mistake causes, without the need to carrying out firmware version recovery, prompting keeper carries out other investigation.
Step 202, when described current version firmware is unavailable, obtains the version firmware that respective modules was successfully upgraded from memory device.
When unavailable by the current version firmware in step 201 determination module, start firmware restoration flow process.In the embodiment of the present application; all version firmwares of once successfully upgrading all are kept in memory device; when current version firmware is unavailable, arbitrary version firmware of successfully upgrading before can obtaining from memory device recovers, and certainly usually can select the version firmware that success is in the recent period upgraded.Without restriction to memory device, as long as can storing firmware, such as expansion ROM, the existing storer of system be as external memory storage etc.As preferably, mentioned in server that configure storage devices is for preserving the files such as daily record in aforementioned description, the application's preferred embodiment directly utilizes this memory device to preserve the firmware version of each module, therefore, can not increase extra hardware cost.Such as, the external memory such as SD (Secure Digital MemoryCard, safe digital card), eMMC (Embedded Multi Media Card, embedded multi-media card) can be selected as memory device.
Step 203, carries out firmware restoration according to described version firmware of successfully upgrading to described respective modules.
As previously mentioned, preserve all version firmwares of successfully upgrading in memory device, each version firmware just can be saved in memory device after successful writing module, also can after firmware success writing module and host CPU is successfully restarted time, then carry out firmware preservation.For rear a kind of preserving type, be specially, when host CPU starts successfully, in judge module, whether current version firmware is preserved, if current version firmware is not preserved in module, is then saved in memory device by the current version firmware in this module.This processing mode can ensure that each version firmware preserved in memory device is all the firmware of restarting authenticated (eliminating incompatible version problem) after successfully upgrading through host CPU, to improve in memory device preserve the validity of firmware, save storage space.
In addition, except the firmware of each module can be preserved separately in memory device, the compatible Matching Relationship of modules current operation firmware version can also be preserved, detailed process is: by after in module, current version firmware is saved in memory device, obtain the current version information of firmware in all modules, the corresponding relation of the current version information of firmware in record modules, this corresponding relation is saved in memory device, so that at service exception, (the incompatible upper-layer service process caused is abnormal between due to disparate modules firmware or between firmware and operating system, such as, network is obstructed, running software reports an error, degradation under CPU handling property) time, BMC CPU can recover order (such as according to the version received, user can when judging service exception, order is recovered) by the operation interface input version of server, automatically a version information corresponding relation preserved is selected from memory device, firmware restoration is carried out to multiple module simultaneously, to ensure the normal operation of business.
Described as can be seen from above, the application adopts and carries out firmware restoration independent of the BMC system of main system, when determining that the host CPU caused due to firmware upgrade starts unsuccessfully, arbitrary version firmware that respective modules successfully upgraded can be obtained carry out firmware restoration from memory device.Effectively can reduce by the application the risk that host CPU cannot start, and can detect that the system caused due to incompatible version cannot start.
Now still for Fig. 1, introduce firmware restoration process in detail.
In Fig. 1, BMC CPU can carry out firmware upgrade and recovery to ME, BIOS and LOGIC module.Suppose, the current version of firmware number run in modules is ME2.0, BIOS3.0 and LOGIC2.0, and in memory device, saved firmware and the edition compatibility relation (the version corresponding relation of ME2.0, BIOS3.0 and LOGIC2.0) of above-mentioned version, under current version compatibility relation, server service normal operation.
Carry out firmware upgrade to ME module, upgraded version is, after ME3.0, ME3.0 firmware successfully writes ME module, arrange upgrading and be designated 1.Now, host CPU is restarted.If host CPU is restarted unsuccessfully, host CPU notices unexpected message to BMC CPU.BMC CPU knows that host CPU is restarted unsuccessfully, the firmware information in verification modules, to determine whether because the host CPU caused of upgrading starts unsuccessfully.
Be specially, when BIOS module and LOGIC module verification succeeds, and when ME module verifies unsuccessfully, illustrate that in ME module, current version firmware is unavailable, need to carry out firmware restoration; Or when BIOS module, LOGIC module and ME module all verification succeeds, but when upgrading is designated 1, illustrate that firmware upgrade write is successful, but host CPU normally cannot start, therefore, the upgraded version in ME module is unavailable, needs to carry out firmware restoration.
When BIOS module, LOGIC module and ME module all verification succeeds, and when upgrading is designated 0, illustrate that host CPU was once successfully restarted after firmware upgrade, therefore, this time start unsuccessfully not because firmware upgrade causes, keeper needs to carry out other investigation.
When determining that ME module needs to carry out firmware restoration, the version firmware of once successfully upgrading in ME module is obtained from memory device, such as, ME2.0, re-writes ME module and carries out firmware restoration, supposes that ME2.0 is the version once normally run, therefore, after firmware restoration, host CPU can normally start, thus the normal process of the business of guarantee.
Above-mentioned is the firmware restoration process of host CPU when starting unsuccessfully.Suppose, ME3.0 successfully writes ME module, and host CPU starts successfully, and current upgrading is masked as 1, illustrates that current is that first after firmware upgrade successfully starts, arranges upgrading and be masked as 0.
BMC CPU can after host CPU normally starts, judge whether preserved ME3.0 version firmware in memory device, when not preserving, ME3.0 firmware is saved in memory device, and preserves the firmware version compatibility relation (the version corresponding relation of ME3.0, BIOS3.0 and LOGIC2.0) run in current modules.
Suppose, current host CPU starts normal, but business cannot normal process, user issues version recovery order by the operation interface of server to BMC CPU, BMC CPU can recover order according to version and delete current disabled edition compatibility relation, from memory device, select other edition compatibility relation of once preserving to carry out overall firmware restoration, such as, select the version corresponding relation of ME2.0, BIOS3.0 and the LOGIC2.0 preserved to carry out firmware restoration, can normal business processing be carried out with Deterministic service device.
Corresponding with the embodiment of aforementioned firmware restoration method, present invention also provides the embodiment of firmware restoration device.
The embodiment of the application's firmware restoration device can be applied on the server.Device embodiment can pass through software simulating, also can be realized by the mode of hardware or software and hardware combining.For software simulating, as the device on a logical meaning, be run computer program instructions corresponding in BMCROM by the BMC CPU of its place server to be formed.Say from hardware view, as shown in Figure 3, for a kind of hardware structure diagram of the application's firmware restoration device place server, except the BMC CPU shown in Fig. 3, module and BMC ROM, in embodiment, the server at device place is usually according to the actual functional capability of this server, other hardware can also be comprised, this is repeated no more.
Please refer to Fig. 4, is the structural representation of the firmware restoration device in the application's embodiment.This firmware restoration device comprises determining unit 401, acquiring unit 402 and recovery unit 403, wherein:
Determining unit 401, for when described host CPU starts unsuccessfully, determines in each module, whether current version firmware can be used;
Acquiring unit 402, for when described current version firmware is unavailable, obtains the version firmware that respective modules was successfully upgraded from memory device;
Recovery unit 403, for carrying out firmware restoration according to described version firmware of successfully upgrading to described respective modules.
Further,
Described memory device is external memory.
Further,
Described determining unit 401, specifically for obtaining the firmware information of current version firmware in described module; When described firmware information is incorrect, or described firmware information is correct and when there is upgrading mark, confirm that in described module, current version firmware is unavailable, described upgrading is masked as the mark arranged after described BMC CPU successfully writes firmware to module; When described firmware information correctly and do not exist upgrading mark time, confirm that in described module, current version firmware can be used.
Further, described firmware restoration device, also comprises:
Clearing cell, during for starting successfully when described host CPU and there is upgrading mark, removes described upgrading mark.
Further, described firmware restoration device, also comprises:
Storage unit, for when described host CPU starts successfully, in judge module, whether current version firmware is preserved; When in described module, current version firmware is not preserved, current version firmware in described module is saved in described memory device.
Further, described firmware restoration device, also comprises:
Described storage unit, also for after being saved in described memory device by current version firmware in described module, obtains the current version information of firmware in described multiple module; The corresponding relation of the current version information of firmware in described multiple module is saved in described memory device;
Described recovery unit 403, also for when service exception, the version receiving input recovers order, selects the version information corresponding relation of multiple modules of preserving; Version information corresponding relation according to selecting carries out firmware restoration to described multiple module.
In said apparatus, the implementation procedure of the function and efficacy of unit specifically refers to the implementation procedure of corresponding step in said method, does not repeat them here.
For device embodiment, because it corresponds essentially to embodiment of the method, so relevant part illustrates see the part of embodiment of the method.Device embodiment described above is only schematic, the wherein said unit illustrated as separating component or can may not be and physically separates, parts as unit display can be or may not be physical location, namely can be positioned at a place, or also can be distributed in multiple network element.Some or all of module wherein can be selected according to the actual needs to realize the object of the application's scheme.Those of ordinary skill in the art, when not paying creative work, are namely appreciated that and implement.
The foregoing is only the preferred embodiment of the application, not in order to limit the application, within all spirit in the application and principle, any amendment made, equivalent replacements, improvement etc., all should be included within scope that the application protects.
Claims (12)
1. a firmware restoration method, be applied on the baseboard management controller BMC central processor CPU in server, it is characterized in that, described server comprises host CPU, described BMC CPU and multiple module, described multiple module is connected with described BMC CPU, comprise the firmware needed for each self-operating in each module, the method comprises:
When described host CPU starts unsuccessfully, each module described is handled as follows:
In determination module, whether current version firmware can be used;
When described current version firmware is unavailable, from memory device, obtain the version firmware that respective modules was successfully upgraded;
According to described version firmware of successfully upgrading, firmware restoration is carried out to described respective modules.
2. the method for claim 1, is characterized in that:
Described memory device is external memory.
3. the method for claim 1, is characterized in that, in described determination module, whether current version firmware can be used, and comprising:
Obtain the firmware information of current version firmware in described module;
When described firmware information is incorrect, or described firmware information is correct and when there is upgrading mark, confirm that in described module, current version firmware is unavailable, described upgrading is masked as the mark arranged after described BMC CPU successfully writes firmware to module;
When described firmware information correctly and do not exist upgrading mark time, confirm that in described module, current version firmware can be used.
4. method as claimed in claim 3, it is characterized in that, described method also comprises:
When described host CPU starts successfully and there is upgrading mark, remove described upgrading mark.
5. the method as described in as arbitrary in Claims 1-4, it is characterized in that, described method also comprises:
When described host CPU starts successfully, in judge module, whether current version firmware is preserved;
When in described module, current version firmware is not preserved, current version firmware in described module is saved in described memory device.
6. method as claimed in claim 5, is characterized in that:
Described current version firmware in described module is saved in described memory device after, also comprise:
Obtain the current version information of firmware in described multiple module;
The corresponding relation of the current version information of firmware in described multiple module is saved in described memory device;
Described method also comprises:
When service exception, the version receiving input recovers order, selects the version information corresponding relation of multiple modules of preserving; Version information corresponding relation according to selecting carries out firmware restoration to described multiple module.
7. a firmware restoration device, be applied on the baseboard management controller BMC central processor CPU in server, it is characterized in that, described server comprises host CPU, described BMC CPU and multiple module, described multiple module is connected with described BMC CPU, comprise the firmware needed for each self-operating in each module, this device comprises:
Determining unit, for when described host CPU starts unsuccessfully, determines in each module, whether current version firmware can be used;
Acquiring unit, for when described current version firmware is unavailable, obtains the version firmware that respective modules was successfully upgraded from memory device;
Recovery unit, for carrying out firmware restoration according to described version firmware of successfully upgrading to described respective modules.
8. device as claimed in claim 7, is characterized in that:
Described memory device is external memory.
9. device as claimed in claim 7, is characterized in that:
Described determining unit, specifically for obtaining the firmware information of current version firmware in described module; When described firmware information is incorrect, or described firmware information is correct and when there is upgrading mark, confirm that in described module, current version firmware is unavailable, described upgrading is masked as the mark arranged after described BMC CPU successfully writes firmware to module; When described firmware information correctly and do not exist upgrading mark time, confirm that in described module, current version firmware can be used.
10. device as claimed in claim 9, it is characterized in that, described device also comprises:
Clearing cell, during for starting successfully when described host CPU and there is upgrading mark, removes described upgrading mark.
11. as arbitrary in claim 7 to 10 as described in device, it is characterized in that, described device also comprises:
Storage unit, for when described host CPU starts successfully, in judge module, whether current version firmware is preserved; When in described module, current version firmware is not preserved, current version firmware in described module is saved in described memory device.
12. devices as claimed in claim 11, it is characterized in that, described device also comprises:
Described storage unit, also for after being saved in described memory device by current version firmware in described module, obtains the current version information of firmware in described multiple module; The corresponding relation of the current version information of firmware in described multiple module is saved in described memory device;
Described recovery unit, also for when service exception, the version receiving input recovers order, selects the version information corresponding relation of multiple modules of preserving; Version information corresponding relation according to selecting carries out firmware restoration to described multiple module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510229002.2A CN104834575B (en) | 2015-05-07 | 2015-05-07 | A kind of firmware restoration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510229002.2A CN104834575B (en) | 2015-05-07 | 2015-05-07 | A kind of firmware restoration method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104834575A true CN104834575A (en) | 2015-08-12 |
| CN104834575B CN104834575B (en) | 2018-04-06 |
Family
ID=53812483
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510229002.2A Active CN104834575B (en) | 2015-05-07 | 2015-05-07 | A kind of firmware restoration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104834575B (en) |
Cited By (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105589712A (en) * | 2015-08-24 | 2016-05-18 | 杭州昆海信息技术有限公司 | BMC module updating method and apparatus |
| CN105897623A (en) * | 2016-03-25 | 2016-08-24 | 杭州昆海信息技术有限公司 | Data transmission method and apparatus |
| CN106775636A (en) * | 2016-11-17 | 2017-05-31 | 广州极飞科技有限公司 | battery firmware processing method, device and charging cabinet system |
| CN107046605A (en) * | 2016-02-05 | 2017-08-15 | 日本冲信息株式会社 | Image processing apparatus, image processing system and its firmware program updating method |
| CN107220545A (en) * | 2017-05-31 | 2017-09-29 | 郑州云海信息技术有限公司 | A kind of hardware encryption system, method and server |
| CN107239312A (en) * | 2017-06-09 | 2017-10-10 | 深圳天珑无线科技有限公司 | A kind of method and device of system upgrade |
| CN107729038A (en) * | 2017-11-27 | 2018-02-23 | 英业达科技有限公司 | The baseboard management controller of firmware update and renewable firmware |
| CN108009054A (en) * | 2017-12-27 | 2018-05-08 | 江苏徐工信息技术股份有限公司 | A kind of double eMMC backup storage systems and method |
| CN108123815A (en) * | 2016-11-29 | 2018-06-05 | 郑州云海信息技术有限公司 | A kind of ARM servers and the BIOS upgrade methods for retaining configuration information |
| CN108304198A (en) * | 2018-01-29 | 2018-07-20 | 郑州云海信息技术有限公司 | A kind of firmware update, device and the medium of Intel ME |
| CN109918135A (en) * | 2019-02-21 | 2019-06-21 | 新华三技术有限公司 | Logical code restoration methods and electronic equipment in a kind of CPLD |
| CN111130856A (en) * | 2019-12-06 | 2020-05-08 | 山东英信计算机技术有限公司 | Server configuration method, system, equipment and computer readable storage medium |
| CN111198832A (en) * | 2020-01-02 | 2020-05-26 | 联想(北京)有限公司 | Processing method and electronic equipment |
| CN112214353A (en) * | 2020-10-16 | 2021-01-12 | 深圳市广和通无线股份有限公司 | Firmware recovery method and device, computer equipment and storage medium |
| CN112783536A (en) * | 2021-03-15 | 2021-05-11 | 英业达科技有限公司 | Server system for updating firmware by using baseboard management controller |
| CN113064813A (en) * | 2021-03-04 | 2021-07-02 | 山东英信计算机技术有限公司 | Board-mounted firmware version detection method and device |
| WO2021212943A1 (en) * | 2020-04-23 | 2021-10-28 | 苏州浪潮智能科技有限公司 | Server power supply maintenance method, apparatus and device, and medium |
| CN113703535A (en) * | 2021-07-30 | 2021-11-26 | 苏州浪潮智能科技有限公司 | Connection configuration method and system of multi-node server and OCP card |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6113652A (en) * | 1995-04-27 | 2000-09-05 | General Data Comm, Inc. | Communications network equipment capable of non-disruptive software upgrade |
| CN101587451A (en) * | 2008-05-20 | 2009-11-25 | 研祥智能科技股份有限公司 | Data backup and recovery method based on extensible firmware interface (EFI) firmware |
| CN101657794A (en) * | 2007-04-13 | 2010-02-24 | 国际商业机器公司 | Automated firmware restoration to a peer programmable hardware device |
| CN102141940A (en) * | 2010-12-29 | 2011-08-03 | Tcl集团股份有限公司 | Device, method and system for recovering firmware update |
| CN102455945A (en) * | 2010-10-27 | 2012-05-16 | 鸿富锦精密工业（深圳）有限公司 | Base board management controller recovery system and use method thereof |
| CN103970567A (en) * | 2014-04-28 | 2014-08-06 | 浪潮电子信息产业股份有限公司 | Method for online upgrading of cloud storage system firmware |
| CN104536848A (en) * | 2014-12-22 | 2015-04-22 | 小米科技有限责任公司 | Firmware recovery method, device and terminal |
-
2015
- 2015-05-07 CN CN201510229002.2A patent/CN104834575B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6113652A (en) * | 1995-04-27 | 2000-09-05 | General Data Comm, Inc. | Communications network equipment capable of non-disruptive software upgrade |
| CN101657794A (en) * | 2007-04-13 | 2010-02-24 | 国际商业机器公司 | Automated firmware restoration to a peer programmable hardware device |
| CN101587451A (en) * | 2008-05-20 | 2009-11-25 | 研祥智能科技股份有限公司 | Data backup and recovery method based on extensible firmware interface (EFI) firmware |
| CN102455945A (en) * | 2010-10-27 | 2012-05-16 | 鸿富锦精密工业（深圳）有限公司 | Base board management controller recovery system and use method thereof |
| CN102141940A (en) * | 2010-12-29 | 2011-08-03 | Tcl集团股份有限公司 | Device, method and system for recovering firmware update |
| CN103970567A (en) * | 2014-04-28 | 2014-08-06 | 浪潮电子信息产业股份有限公司 | Method for online upgrading of cloud storage system firmware |
| CN104536848A (en) * | 2014-12-22 | 2015-04-22 | 小米科技有限责任公司 | Firmware recovery method, device and terminal |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105589712A (en) * | 2015-08-24 | 2016-05-18 | 杭州昆海信息技术有限公司 | BMC module updating method and apparatus |
| CN105589712B (en) * | 2015-08-24 | 2019-09-06 | 新华三信息技术有限公司 | BMC module update method and device |
| CN107046605A (en) * | 2016-02-05 | 2017-08-15 | 日本冲信息株式会社 | Image processing apparatus, image processing system and its firmware program updating method |
| CN105897623A (en) * | 2016-03-25 | 2016-08-24 | 杭州昆海信息技术有限公司 | Data transmission method and apparatus |
| CN105897623B (en) * | 2016-03-25 | 2019-04-30 | 新华三信息技术有限公司 | A kind of transmission method and device of data |
| CN106775636A (en) * | 2016-11-17 | 2017-05-31 | 广州极飞科技有限公司 | battery firmware processing method, device and charging cabinet system |
| CN108123815A (en) * | 2016-11-29 | 2018-06-05 | 郑州云海信息技术有限公司 | A kind of ARM servers and the BIOS upgrade methods for retaining configuration information |
| CN107220545A (en) * | 2017-05-31 | 2017-09-29 | 郑州云海信息技术有限公司 | A kind of hardware encryption system, method and server |
| CN107239312A (en) * | 2017-06-09 | 2017-10-10 | 深圳天珑无线科技有限公司 | A kind of method and device of system upgrade |
| CN107729038A (en) * | 2017-11-27 | 2018-02-23 | 英业达科技有限公司 | The baseboard management controller of firmware update and renewable firmware |
| CN108009054A (en) * | 2017-12-27 | 2018-05-08 | 江苏徐工信息技术股份有限公司 | A kind of double eMMC backup storage systems and method |
| CN108304198A (en) * | 2018-01-29 | 2018-07-20 | 郑州云海信息技术有限公司 | A kind of firmware update, device and the medium of Intel ME |
| CN109918135A (en) * | 2019-02-21 | 2019-06-21 | 新华三技术有限公司 | Logical code restoration methods and electronic equipment in a kind of CPLD |
| CN111130856A (en) * | 2019-12-06 | 2020-05-08 | 山东英信计算机技术有限公司 | Server configuration method, system, equipment and computer readable storage medium |
| CN111198832A (en) * | 2020-01-02 | 2020-05-26 | 联想(北京)有限公司 | Processing method and electronic equipment |
| WO2021212943A1 (en) * | 2020-04-23 | 2021-10-28 | 苏州浪潮智能科技有限公司 | Server power supply maintenance method, apparatus and device, and medium |
| CN112214353A (en) * | 2020-10-16 | 2021-01-12 | 深圳市广和通无线股份有限公司 | Firmware recovery method and device, computer equipment and storage medium |
| CN113064813A (en) * | 2021-03-04 | 2021-07-02 | 山东英信计算机技术有限公司 | Board-mounted firmware version detection method and device |
| CN112783536A (en) * | 2021-03-15 | 2021-05-11 | 英业达科技有限公司 | Server system for updating firmware by using baseboard management controller |
| CN113703535A (en) * | 2021-07-30 | 2021-11-26 | 苏州浪潮智能科技有限公司 | Connection configuration method and system of multi-node server and OCP card |
| CN113703535B (en) * | 2021-07-30 | 2023-08-18 | 苏州浪潮智能科技有限公司 | Connection configuration method and system for multi-node server and OCP card |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104834575B (en) | 2018-04-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104834575A (en) | Firmware recovery method and device | |
| US8468389B2 (en) | Firmware recovery system and method of baseboard management controller of computing device | |
| US20030163753A1 (en) | Automatic BIOS recovery in a multi-node computer system | |
| US9858067B2 (en) | Electronic system with update control mechanism and method of operation thereof | |
| US7797416B2 (en) | Computer system, management server, and mismatched connection configuration detection method | |
| CN103150231A (en) | Computer booting method and computer system | |
| CN102906710B (en) | A kind of Bootrom backup method and device | |
| US20130117518A1 (en) | System controller, information processing system and method of saving and restoring data in the information processing system | |
| US20140365818A1 (en) | Method relating to configurable storage device and adaptive storage device array | |
| CN110007971A (en) | A kind of information processing method and device, equipment, storage medium | |
| US10853213B2 (en) | Validation of installation of removeable computer hardware components | |
| US8312215B2 (en) | Method and system for resolving configuration conflicts in RAID systems | |
| CN103475514B (en) | Node, group system and BIOS without BMC repair and upgrade method | |
| CN111090537B (en) | Cluster starting method and device, electronic equipment and readable storage medium | |
| JP2017078998A (en) | Information processor, log management method, and computer program | |
| CN116724297A (en) | Fault processing method, device and system | |
| WO2023109880A1 (en) | Service recovery method, data processing unit and related device | |
| US20130111454A1 (en) | Technique for updating program being executed | |
| CN109086085B (en) | Operating system start management method and device | |
| US11740969B2 (en) | Detecting and recovering a corrupted non-volatile random-access memory | |
| KR100605031B1 (en) | A method for upgrading and restoring embeded systems by using usb memory device | |
| CN110688130A (en) | Physical machine deployment method, physical machine deployment device, readable storage medium and electronic equipment | |
| CN115904831A (en) | Starting method of server firmware and terminal | |
| CN104407806A (en) | Method and device for revising hard disk information of redundant array group of independent disk (RAID) | |
| CN113867812A (en) | Method, system, equipment and medium for BMC to acquire link information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 310052 Binjiang District, Zhejiang Province, Changhe Road, No. 11, building 466, building Applicant after: Huashan Information Technology Co., Ltd. Address before: 310052 Binjiang District, Zhejiang Province, Changhe Road, No. 11, building 466, building Applicant before: Hangzhou Kun Hai Information Technology Co., Ltd |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Patentee after: Xinhua Sanxin Information Technology Co., Ltd. Address before: 310052 11th Floor, 466 Changhe Road, Binjiang District, Hangzhou City, Zhejiang Province Patentee before: Huashan Information Technology Co., Ltd. |
|
| CP01 | Change in the name or title of a patent holder |