CN117421156A - Firmware management method, device, equipment and machine-readable storage medium - Google Patents
Firmware management method, device, equipment and machine-readable storage medium Download PDFInfo
- Publication number
- CN117421156A CN117421156A CN202311162187.0A CN202311162187A CN117421156A CN 117421156 A CN117421156 A CN 117421156A CN 202311162187 A CN202311162187 A CN 202311162187A CN 117421156 A CN117421156 A CN 117421156A
- Authority
- CN
- China
- Prior art keywords
- firmware
- storage area
- abnormal
- main
- server
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 24
- 230000002159 abnormal effect Effects 0.000 claims abstract description 80
- 230000005856 abnormality Effects 0.000 claims abstract description 31
- 238000000034 method Methods 0.000 claims abstract description 29
- 230000002452 interceptive effect Effects 0.000 claims abstract description 20
- 238000011084 recovery Methods 0.000 claims abstract description 19
- 238000012795 verification Methods 0.000 claims description 24
- 238000011010 flushing procedure Methods 0.000 claims 2
- 239000000758 substrate Substances 0.000 claims 1
- 230000003993 interaction Effects 0.000 abstract description 5
- 230000008439 repair process Effects 0.000 abstract description 3
- 238000005192 partition Methods 0.000 description 22
- 230000006870 function Effects 0.000 description 10
- 238000004590 computer program Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 3
- 230000001680 brushing effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1497—Details of time redundant execution on a single processing unit
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/42—Bus transfer protocol, e.g. handshake; Synchronisation
- G06F13/4282—Bus transfer protocol, e.g. handshake; Synchronisation on a serial bus, e.g. I2C bus, SPI bus
Abstract
The present disclosure provides a firmware management method, apparatus, device, and machine-readable storage medium, the method comprising: the method comprises the steps of maintaining interactive connection with a hardware storage device through an interface, configuring a first storage area and a second storage area in the hardware storage device, storing main firmware in the first storage area, and storing reserved firmware in the second storage area; responding to an event of main firmware abnormality, reading the firmware stored in the second storage area through the currently maintained interactive connection with the hardware storage device and operating the firmware; and according to an abnormality recovery unit included in the standby firmware, the first storage area is refreshed to recover the abnormal main firmware. According to the technical scheme, the storage area of the main firmware and the storage area of the standby firmware are configured on the same hardware storage device, so that when the standby firmware is started due to abnormality of the main firmware, the interaction connection with the hardware storage device where the main firmware is positioned can be maintained through the interface, and the repair and the refreshing of the main firmware through software are realized.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a firmware management method, apparatus, device, and machine-readable storage medium.
Background
BMC (Baseboard Management Controller) is a software and hardware device located on a server for managing and monitoring various aspects of the server. A BMC is typically an integrated circuit chip with separate components such as a processor, memory, and network interface that are independent of the host system's processor and operating system. With remote management, monitoring and sensor management, power management, etc. of the server.
BIOS (Basic Input/Output System) is the Basic Input/Output System in a computer System. It is a set of firmware (firmware is a software representation of hardware) that is solidified on the computer motherboard, responsible for self-checking, initializing hardware devices at computer start-up, and providing the most basic system operating functions.
In modern computer systems, servers play a critical role in hosting critical business applications, storing and processing large amounts of data, and providing functions such as network services and resource sharing. The stability and reliability of the server are critical to ensuring the continuity of the service and the safety of the data.
In server hardware, BMC and BIOS are two key components. The BMC, as a server management subsystem, is responsible for remote management, monitoring and controlling of the server, while the BIOS is the key firmware to start the system and initialize the hardware devices.
However, BMC and BIOS firmware may experience abnormal conditions such as firmware corruption, configuration errors, upgrade failures, etc. for various reasons. These abnormal conditions may cause the server to not start up normally, the hardware devices to not initialize normally, or even to be remotely managed and monitored.
Disclosure of Invention
In view of this, the disclosure provides a firmware management method, a device, an electronic apparatus, and a machine-readable storage medium, so as to improve the problem that the firmware abnormality affects the operation of the service.
The technical scheme is as follows:
the present disclosure provides a firmware management method applied to a server including and including only one piece of hardware storage device for storing firmware, the method including: the method comprises the steps of maintaining interactive connection with a hardware storage device through an SPI interface, configuring a first storage area and a second storage area in the hardware storage device, storing main firmware in the first storage area, and storing reserved firmware in the second storage area; responding to an event of main firmware abnormality, reading the firmware stored in the second storage area through the currently maintained interactive connection with the hardware storage device and operating the firmware; and according to an abnormality recovery unit included in the standby firmware, the first storage area is refreshed to recover the abnormal main firmware.
As a technical solution, the method for refreshing a first storage area to restore abnormal main firmware according to an abnormality restoring unit included in the firmware includes: detecting a non-abnormal flag bit, and if the non-abnormal flag bit is not marked, executing a step of refreshing a first storage area to restore abnormal main firmware according to an abnormal restoring unit included in the spare firmware; the non-exception flag bit is marked when the non-main firmware exception event cause selects to enter the standby firmware.
As a technical scheme, the non-abnormal flag bit is used for being detected by the server when the server is started, so that the server responds to the event that the non-abnormal flag bit is marked when the server is started, and the non-abnormal flag bit is kept in interactive connection with the hardware storage device through the SPI interface, reads the firmware of the second storage area and operates.
As a technical solution, the method for refreshing a first storage area to restore abnormal main firmware according to an abnormality restoring unit included in the firmware includes: preferentially using the updated mirror image after stability verification to write the first storage area so as to recover the abnormal main firmware, and if the updated mirror image after stability verification does not exist, using the initial mirror image to write the first storage area so as to recover the abnormal main firmware; and the updated mirror image after the stability verification is a mirror image which is written into the second storage area after the stability verification is performed for a preset time period.
The present disclosure also provides a firmware management apparatus applied to a server including and including only one piece of hardware storage apparatus for storing firmware, the method comprising: the first module is used for maintaining the interactive connection with the hardware storage device through the SPI interface, configuring a first storage area and a second storage area in the hardware storage device, storing main firmware in the first storage area, and storing reserved firmware in the second storage area; the second module is used for responding to the event of the abnormality of the main firmware, reading the standby firmware stored in the second storage area and running through the currently maintained interactive connection with the hardware storage device; and the third module is used for refreshing the first storage area according to an abnormality recovery unit included in the standby firmware so as to recover the abnormal main firmware.
As a technical solution, the method for refreshing a first storage area to restore abnormal main firmware according to an abnormality restoring unit included in the firmware includes: detecting a non-abnormal flag bit, and if the non-abnormal flag bit is not marked, executing a step of refreshing a first storage area to restore abnormal main firmware according to an abnormal restoring unit included in the spare firmware; the non-exception flag bit is marked when the non-main firmware exception event cause selects to enter the standby firmware.
As a technical scheme, the non-abnormal flag bit is used for being detected by the server when the server is started, so that the server responds to the event that the non-abnormal flag bit is marked when the server is started, and the non-abnormal flag bit is kept in interactive connection with the hardware storage device through the SPI interface, reads the firmware of the second storage area and operates.
As a technical solution, the method for refreshing a first storage area to restore abnormal main firmware according to an abnormality restoring unit included in the firmware includes: preferentially using the updated mirror image after stability verification to write the first storage area so as to recover the abnormal main firmware, and if the updated mirror image after stability verification does not exist, using the initial mirror image to write the first storage area so as to recover the abnormal main firmware; and the updated mirror image after the stability verification is a mirror image which is written into the second storage area after the stability verification is performed for a preset time period.
The present disclosure also provides an electronic device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor executing the machine-executable instructions to implement the aforementioned firmware management method.
The present disclosure also provides a machine-readable storage medium storing machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the aforementioned firmware management method.
The technical scheme provided by the disclosure at least brings the following beneficial effects:
by configuring the storage area of the main firmware and the storage area of the standby firmware on the same hardware storage device, when the standby firmware is started due to the abnormality of the main firmware, the interaction connection with the hardware storage device where the main firmware is positioned can be still maintained through the SPI interface, so that the repair and the refreshing of the main firmware through software are realized.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings that are required to be used in the embodiments of the present disclosure or the description of the prior art will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments described in the present disclosure, and other drawings may also be obtained according to these drawings of the embodiments of the present disclosure to those skilled in the art.
FIG. 1 is a flow chart of a firmware management method in one embodiment of the present disclosure;
FIG. 2 is a block diagram of a firmware management apparatus in one embodiment of the present disclosure;
fig. 3 is a hardware configuration diagram of an electronic device in one embodiment of the present disclosure.
Reference numerals: a first module 21, a second module 22, a third module 23.
Detailed Description
The terminology used in the embodiments of the disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to any or all possible combinations including one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in the embodiments of the present disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. Depending on the context, furthermore, the word "if" used may be interpreted as "at … …" or "at … …" or "in response to a determination".
In the technical scheme, a double-Flash scheme is adopted to ensure service operation, and the service operation is performed in a main partition called Flash1 and in a spare partition called Flash 2. When the Flash1 is damaged, the operation is automatically switched to the Flash2 by means of a register in the chip. According to the scheme, redundant Flash is used for achieving main and standby, corresponding Flash is selected through FWMSPICS, so that Flash1 cannot be accessed when Flash2 is operated, and firmware cannot be recovered by software re-erasing of Flash 1.
In view of the above, the present disclosure provides a firmware management method, apparatus, electronic device, and machine-readable storage medium, so as to improve the problem that the firmware abnormality affects the operation of the service.
The specific technical scheme is as follows.
In one embodiment, the present disclosure provides a firmware management method applied to a server including and including only one piece of hardware storage device for storing firmware, the method including: the method comprises the steps of maintaining interactive connection with a hardware storage device through an SPI interface, configuring a first storage area and a second storage area in the hardware storage device, storing main firmware in the first storage area, and storing reserved firmware in the second storage area; responding to an event of main firmware abnormality, reading the firmware stored in the second storage area through the currently maintained interactive connection with the hardware storage device and operating the firmware; and according to an abnormality recovery unit included in the standby firmware, the first storage area is refreshed to recover the abnormal main firmware.
Specifically, as shown in fig. 1, the method comprises the following steps:
step S11, the interactive connection with the hardware storage device is kept through an SPI interface, a first storage area and a second storage area are configured in the hardware storage device, main firmware is stored in the first storage area, and reserved firmware is stored in the second storage area;
step S12, in response to an event of main firmware abnormality, reading the firmware stored in the second storage area through the currently maintained interactive connection with the hardware storage device and running;
step S13, according to an abnormality recovery unit included in the standby firmware, the first storage area is refreshed to recover the abnormal main firmware.
By configuring the storage area of the main firmware and the storage area of the standby firmware on the same hardware storage device, when the standby firmware is started due to the abnormality of the main firmware, the interaction connection with the hardware storage device where the main firmware is positioned can be still maintained through the SPI interface, so that the repair and the refreshing of the main firmware through software are realized.
In one embodiment, the method for refreshing the first storage area to restore the abnormal main firmware according to the abnormality restoring unit included in the spare firmware includes: detecting a non-abnormal flag bit, and if the non-abnormal flag bit is not marked, executing a step of refreshing a first storage area to restore abnormal main firmware according to an abnormal restoring unit included in the spare firmware; the non-exception flag bit is marked when the non-main firmware exception event cause selects to enter the standby firmware.
In one embodiment, the non-abnormal flag bit is used for being detected by the server when the server is started, so that the server responds to the event that the non-abnormal flag bit is marked when the server is started, and the interaction connection with the hardware storage device is maintained through the SPI interface, and the firmware of the second storage area is read and operated.
In one embodiment, the method for refreshing the first storage area to restore the abnormal main firmware according to the abnormality restoring unit included in the spare firmware includes: preferentially using the updated mirror image after stability verification to write the first storage area so as to recover the abnormal main firmware, and if the updated mirror image after stability verification does not exist, using the initial mirror image to write the first storage area so as to recover the abnormal main firmware; and the updated mirror image after the stability verification is a mirror image which is written into the second storage area after the stability verification is performed for a preset time period.
In one embodiment, a flash (hardware storage device) is used to implement the primary and secondary partitions, and after the primary and secondary partitions are switched to each other, the primary partition can still be accessed. The flash space is divided into two parts, namely a front half part is used as a main partition, and a rear half part is used as a standby partition. Under normal conditions, the BMC is started in the main partition, and the user can use the functions normally.
There are two sources of firmware for exception recovery: (1) a factory image, which is considered reliable, which is used when there is no updated image; (2) the user updated mirror image is uploaded when the user upgrades and can be obtained in places such as a official network. When a user upgrades, the image file upgraded at the time is saved, but the state of the image file just upgraded is unreliable, so that 10 minutes of observation time is set, and abnormal conditions such as BMC restarting and the like do not occur within 10 minutes, and the new firmware is used for recovering the firmware abnormally.
After the main partition is abnormal and enters the standby partition, the trusted abnormal recovery firmware is used for carrying out abnormal recovery, the main partition is refreshed again, and the original configuration is kept unchanged. After successful brushing, the main partition is automatically switched to complete the abnormal recovery.
In order to judge whether the main firmware of the main partition is abnormal to enter the spare partition, defining a non-abnormal flag bit, wherein the non-abnormal flag bit can be a flag file, if the flag bit is manually switched to the spare partition, the flag file is generated, and the abnormal recovery flow is not executed. If the exception is in the spare partition, the flag file is not available, the main firmware exception is considered to happen, if the exception recovery function is started, the latest recovery mirror image is acquired, and the main partition is started to be brushed. After the brushing is finished, the issuing command is switched to the main partition, and the main partition is restored to be normal.
The image source of the BIOS is only obtained by uploading by a user, and when the user successfully updates the new BIOS image and the BIOS can normally run in the new version, the BIOS image can be considered to be available and used as an abnormal recovery image. When the BIOS starts an exception, an interrupt is sent to the BMC application, and after the exception is received, an exception recovery process is started.
According to the technical scheme, the single flash double partition is realized, and the address of the main partition can be accessed when the spare partition runs.
In one embodiment, the present disclosure also provides a firmware management apparatus, as in fig. 2, applied to a server, where the server includes and only includes a piece of hardware storage device for storing firmware, the method includes: the first module is used for maintaining the interactive connection with the hardware storage device through the SPI interface, configuring a first storage area and a second storage area in the hardware storage device, storing main firmware in the first storage area, and storing reserved firmware in the second storage area; the second module is used for responding to the event of the abnormality of the main firmware, reading the standby firmware stored in the second storage area and running through the currently maintained interactive connection with the hardware storage device; and the third module is used for refreshing the first storage area according to an abnormality recovery unit included in the standby firmware so as to recover the abnormal main firmware.
In one embodiment, the method for refreshing the first storage area to restore the abnormal main firmware according to the abnormality restoring unit included in the spare firmware includes: detecting a non-abnormal flag bit, and if the non-abnormal flag bit is not marked, executing a step of refreshing a first storage area to restore abnormal main firmware according to an abnormal restoring unit included in the spare firmware; the non-exception flag bit is marked when the non-main firmware exception event cause selects to enter the standby firmware.
In one embodiment, the non-abnormal flag bit is used for being detected by the server when the server is started, so that the server responds to the event that the non-abnormal flag bit is marked when the server is started, and the interaction connection with the hardware storage device is maintained through the SPI interface, and the firmware of the second storage area is read and operated.
In one embodiment, the method for refreshing the first storage area to restore the abnormal main firmware according to the abnormality restoring unit included in the spare firmware includes: preferentially using the updated mirror image after stability verification to write the first storage area so as to recover the abnormal main firmware, and if the updated mirror image after stability verification does not exist, using the initial mirror image to write the first storage area so as to recover the abnormal main firmware; and the updated mirror image after the stability verification is a mirror image which is written into the second storage area after the stability verification is performed for a preset time period.
The device embodiments are the same as or similar to the corresponding method embodiments and are not described in detail herein.
In one embodiment, the present disclosure provides an electronic device including a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor executing the machine-executable instructions to implement the aforementioned firmware management method, and from a hardware level, a hardware architecture diagram may be shown with reference to fig. 3.
In one embodiment, the present disclosure provides a machine-readable storage medium storing machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the aforementioned firmware management method.
Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that may contain or store information, such as executable instructions, data, or the like. For example, a machine-readable storage medium may be: RAM (Radom Access Memory, random access memory), volatile memory, non-volatile memory, flash memory, a storage drive (e.g., hard drive), a solid state drive, any type of storage disk (e.g., optical disk, dvd, etc.), or a similar storage medium, or a combination thereof.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, which may be in the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware when implementing the present disclosure.
It will be apparent to those skilled in the art that embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Moreover, these computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be appreciated by those skilled in the art that embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (which may include, but are not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.
The foregoing is merely an embodiment of the present disclosure and is not intended to limit the present disclosure. Various modifications and variations of this disclosure will be apparent to those skilled in the art. Any modifications, equivalent substitutions, improvements, or the like, which are within the spirit and principles of the present disclosure, are intended to be included within the scope of the claims of the present disclosure.
Claims (10)
1. A firmware management method applied to a server including and including only one piece of hardware storage device for storing firmware, the method comprising:
the method comprises the steps of maintaining interactive connection with a hardware storage device through an SPI interface, configuring a first storage area and a second storage area in the hardware storage device, storing main firmware in the first storage area, and storing reserved firmware in the second storage area;
responding to an event of main firmware abnormality, reading the firmware stored in the second storage area through the currently maintained interactive connection with the hardware storage device and operating the firmware;
and according to an abnormality recovery unit included in the standby firmware, the first storage area is refreshed to recover the abnormal main firmware.
2. The method according to claim 1, wherein the flushing the first storage area to restore the abnormal main firmware according to the abnormality restoring unit included in the spare firmware includes:
detecting a non-abnormal flag bit, and if the non-abnormal flag bit is not marked, executing a step of refreshing a first storage area to restore abnormal main firmware according to an abnormal restoring unit included in the spare firmware;
the non-exception flag bit is marked when the non-main firmware exception event cause selects to enter the standby firmware.
3. The method of claim 2, wherein the step of determining the position of the substrate comprises,
the non-abnormal flag bit is used for being detected by the server when the server is started, so that the server responds to the event that the non-abnormal flag bit is marked when the server is started, and the interactive connection with the hardware storage device is maintained through the SPI interface, and the firmware of the second storage area is read and operated.
4. The method according to claim 1, wherein the flushing the first storage area to restore the abnormal main firmware according to the abnormality restoring unit included in the spare firmware includes:
preferentially using the updated mirror image after stability verification to write the first storage area so as to recover the abnormal main firmware, and if the updated mirror image after stability verification does not exist, using the initial mirror image to write the first storage area so as to recover the abnormal main firmware;
and the updated mirror image after the stability verification is a mirror image which is written into the second storage area after the stability verification is performed for a preset time period.
5. A firmware management apparatus for application to a server, said server comprising and including only one piece of hardware storage means for storing firmware, said apparatus comprising:
the first module is used for maintaining the interactive connection with the hardware storage device through the SPI interface, configuring a first storage area and a second storage area in the hardware storage device, storing main firmware in the first storage area, and storing reserved firmware in the second storage area;
the second module is used for responding to the event of the abnormality of the main firmware, reading the standby firmware stored in the second storage area and running through the currently maintained interactive connection with the hardware storage device;
and the third module is used for refreshing the first storage area according to an abnormality recovery unit included in the standby firmware so as to recover the abnormal main firmware.
6. The apparatus of claim 5, wherein the writing the first storage area according to the exception recovery unit included in the firmware to recover the exception main firmware comprises:
detecting a non-abnormal flag bit, and if the non-abnormal flag bit is not marked, executing a step of refreshing a first storage area to restore abnormal main firmware according to an abnormal restoring unit included in the spare firmware;
the non-exception flag bit is marked when the non-main firmware exception event cause selects to enter the standby firmware.
7. The apparatus of claim 6, wherein the device comprises a plurality of sensors,
the non-abnormal flag bit is used for being detected by the server when the server is started, so that the server responds to the event that the non-abnormal flag bit is marked when the server is started, and the interactive connection with the hardware storage device is maintained through the SPI interface, and the firmware of the second storage area is read and operated.
8. The apparatus of claim 5, wherein the writing the first storage area according to the exception recovery unit included in the firmware to recover the exception main firmware comprises:
preferentially using the updated mirror image after stability verification to write the first storage area so as to recover the abnormal main firmware, and if the updated mirror image after stability verification does not exist, using the initial mirror image to write the first storage area so as to recover the abnormal main firmware;
and the updated mirror image after the stability verification is a mirror image which is written into the second storage area after the stability verification is performed for a preset time period.
9. An electronic device, comprising: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to perform the method of any one of claims 1-4.
10. A machine-readable storage medium storing machine-executable instructions which, when invoked and executed by a processor, cause the processor to implement the method of any one of claims 1-4.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311162187.0A CN117421156A (en) | 2023-09-08 | 2023-09-08 | Firmware management method, device, equipment and machine-readable storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311162187.0A CN117421156A (en) | 2023-09-08 | 2023-09-08 | Firmware management method, device, equipment and machine-readable storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN117421156A true CN117421156A (en) | 2024-01-19 |
Family
ID=89523662
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202311162187.0A Pending CN117421156A (en) | 2023-09-08 | 2023-09-08 | Firmware management method, device, equipment and machine-readable storage medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN117421156A (en) |
-
2023
- 2023-09-08 CN CN202311162187.0A patent/CN117421156A/en active Pending
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9836606B2 (en) | Secure recovery apparatus and method | |
US8341386B2 (en) | Method for updating basic input/output system and method for repairing thereof | |
JPWO2013103023A1 (en) | Information processing apparatus, information processing method, and computer program | |
US20070174704A1 (en) | Computer program automatic recovery activation control method and system | |
US20060036832A1 (en) | Virtual computer system and firmware updating method in virtual computer system | |
US11550655B2 (en) | System and method for monitoring and upgrading a dual-flash device | |
US11481278B2 (en) | System and method for recovering an operating system after a runtime hang using a dual-flash device | |
US11243780B2 (en) | System and method for operating system installation using a dual-flash device | |
CN111506454A (en) | Method and system for recovering and updating basic input/output system | |
US11797389B2 (en) | System and method for recovering an operating system after an upgrade hang using a dual-flash device | |
WO2017080225A1 (en) | Data partition recovery method and apparatus and terminal | |
CN109582332B (en) | System upgrading method and device for Internet camera | |
JP6599725B2 (en) | Information processing apparatus, log management method, and computer program | |
TWI764454B (en) | Firmware corruption recovery | |
US9910747B2 (en) | Parallel mirrored copying with write consistency | |
US11740969B2 (en) | Detecting and recovering a corrupted non-volatile random-access memory | |
CN117421156A (en) | Firmware management method, device, equipment and machine-readable storage medium | |
CN115827069A (en) | Starting control method, system and device for server mainboard | |
US10592329B2 (en) | Method and electronic device for continuing executing procedure being aborted from physical address where error occurs | |
US10360173B2 (en) | Server event log storage and retrieval system | |
TWI777664B (en) | Booting method of embedded system | |
CN117234544B (en) | Method and device for recovering system of server equipment | |
JP6149624B2 (en) | Firmware execution apparatus, firmware execution method, computer program, and computer apparatus | |
US20220374223A1 (en) | Server and updating method for mac address | |
CN108415788B (en) | Data processing apparatus and method for responding to non-responsive processing circuitry |
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 |