CN114201195A

CN114201195A - Firmware refreshing method and device and electronic equipment

Info

Publication number: CN114201195A
Application number: CN202111431903.1A
Authority: CN
Inventors: 杨濠宇
Original assignee: Suzhou Inspur Intelligent Technology Co Ltd
Current assignee: Suzhou Inspur Intelligent Technology Co Ltd
Priority date: 2021-11-29
Filing date: 2021-11-29
Publication date: 2022-03-18

Abstract

The invention relates to the field of computer science, in particular to a firmware refreshing method, a firmware refreshing device and electronic equipment. By changing the link, the firmware can be refreshed only by changing the file in the external equipment connected to the link without the participation of any native file when the firmware is refreshed, so that the restriction of the native file on the firmware refreshing is reduced, and the success rate of the firmware refreshing is greatly improved.

Description

Firmware refreshing method and device and electronic equipment

Technical Field

The invention relates to the technical field of computer science, in particular to a firmware configuration method and device and electronic equipment.

Background

The Basic Input Output System (BIOS) is a set of programs that are fixed on a Read-Only Memory (ROM) chip on a main board in a service area, and stores the most important Basic Input and Output programs of a computer, System setting information, a power-on self-test program, and a System boot bootstrap program.

The BIOS performs customized development for customer requirements, or processes BUGs (BUGs) in the development process, adds new functions, and the like, and needs to frequently perform firmware refreshing of the BIOS.

The present BIOS refreshing method is to directly burn and write Flash memory chip except using burner. The BIOS may also be refreshed out-of-band using a Baseboard Management Controller (BMC). The BMC is an independent system, and is independent of other hardware (such as a Central Processing Unit (CPU), a memory, etc.) on the system, and is also independent of a BIOS, an Operating System (OS), etc., but the BMC may interact with the BIOS and the OS, which may perform a better platform management function. The BIOS file is required to be uploaded into the BMC storage area for out-of-band refreshing, and the BMC erases and writes the flash memory so as to refresh the BIOS.

And a corresponding refreshing program can be executed under a unified extensible firmware interface or a system to carry out in-band refreshing, and the refreshing mode can be applied to scenes that the BMC out-of-band refreshing function is not complete and the like. In the current in-band refresh process, a BIOS refresh program needs to be used to trigger a System Management Interrupt (SMI) in a System or a unified extensible firmware interface, so that a CPU enters a System Management Mode (SMM), and in the System Management Mode, an SMI Interrupt processing function corresponding to BIOS refresh is executed to refresh the BIOS into a flash memory through operations such as read-write verification, and the BIOS is refreshed.

The key point of this process is that firstly, the BIOS flush code is a section of SMI interrupt handling function, and the code exists in the current server BIOS, so the function of in-band flush requires that the BIOS support the execution of the SMI interrupt handling function in advance, and the CPU needs to be in the SMM mode. The SMM mode has the highest authority to avoid the influence of a system or other factors, and meanwhile, in the mode, if BIOS refreshing fails due to the fact that a BIOS file to be refreshed or a refreshing program is jammed for unknown reasons, the BIOS firmware can be recovered only in a burning mode of a burner, and refreshing can not be carried out again by restarting the BIOS refreshing program. Due to the safety consideration, the flash chip is often welded on the mainboard, the hardware design is also needed to be considered, and sometimes the hardware needs to be refreshed for burning, which is very inconvenient.

In the prior art, when a Basic Input Output System (BIOS) file in a storage device is damaged, a BIOS recovery (BIOS) mode is usually adopted to restore the BIOS.

For example: when the BIOS file is damaged and the computer cannot normally start, the intact BIOS file is imported into a storage medium, when the BIOS code is executed, a General Purpose Input/Output (GPIO) port is automatically detected, the BIOS code is judged to be BIOS recovery when the BIOS code is currently started, the BIOS file is refreshed into a flash memory (flash), and after the BIOS code is refreshed, the BIOS code which is refreshed in the flash memory is continuously executed.

However, when BIOS recovery is implemented in a BIOS recovery manner, files of BIOS codes up to the time of executing recovery must be complete, and it is guaranteed that recovery operations can be completed smoothly.

Therefore, a method and an apparatus for configuring firmware, and an electronic device are needed to overcome the above-mentioned drawbacks.

Disclosure of Invention

In view of this, embodiments of the present invention provide a firmware refreshing method and apparatus, and an electronic device, so as to solve the problem of dependence on a native file during firmware refreshing.

According to a first aspect, an embodiment of the present invention provides a firmware refreshing method, including:

acquiring the working state of a refreshing detection device to determine whether the target firmware needs to be refreshed or not;

and when local refreshing is required, switching the file reading link of the target firmware to a target device from the memory, so that the memory reads the file from the target device for refreshing.

By changing the link, the firmware can be refreshed only by changing the file in the external equipment connected to the link without the participation of any native file when the firmware is refreshed, so that the restriction of the native file on the firmware refreshing is reduced, and the success rate of the firmware refreshing is greatly improved.

With reference to the first aspect, in a first implementation manner of the first aspect, the obtaining the operating state of the refresh detection device to determine whether the target firmware needs to be refreshed includes obtaining the operating state of the refresh detection device, where the obtaining the operating state of the refresh detection device to determine whether the target firmware needs to be refreshed

And detecting the working state through a first detector to obtain the working state of the refreshing detection equipment.

Whether the refreshing is really needed or not is detected by the working state, the working state can be manually modified, so that the accuracy of the working state can be ensured, and meanwhile, the working state can be manually modified, so that even if software is completely damaged, a refreshing instruction can be ensured to be smoothly transmitted, and the refreshing stability is ensured.

With reference to the first aspect, in a second implementation manner of the first aspect, the switching the file read link of the target firmware to the target device includes:

and sending a signal to a line control module to enable the line control module to switch a file reading link of the target firmware to a target device through a memory.

The circuit control module changes the file reading address into the target equipment, so that the target firmware can be refreshed by reading the code in the target equipment even if the code in the memory is completely damaged, and meanwhile, as the complete code for refreshing is stored in the target equipment, the smooth transmission of a refreshing instruction can be ensured even if the software is completely damaged, and the refreshing stability is ensured.

With reference to the first aspect, in a third implementation manner of the first aspect, when the target firmware needs to be refreshed, switching a file reading link of the target firmware from a memory to a target device, so that the memory reads a file from the target device for refreshing includes:

judging whether the circuit control module is refreshed or not to obtain a judgment result;

and enabling the target firmware to read a file from the target equipment for refreshing based on the judgment result.

And meanwhile, because the file in the target equipment is copied into the memory in the refreshing process, excessive software and hardware operation steps are not involved, and the refreshing stability is greatly enhanced.

With reference to the first aspect, in a fourth embodiment of the first aspect, the method further includes:

and presetting the memory so that the memory can be read.

By setting the memory in advance, the refreshing operation of the memory in the next refreshing process can be smoothly carried out, and the stability of the refreshing process is greatly improved.

With reference to the second embodiment of the first aspect, in a fifth embodiment of the first aspect, the target device includes:

the target device is set in advance so that a file which can provide refreshing is contained in the target device.

By setting the target in advance, the refreshing operation in the next refreshing process is guaranteed, and the stability of the refreshing process is greatly improved.

According to a second aspect, an embodiment of the present invention provides a firmware refreshing apparatus, including:

the acquisition module is used for acquiring the working state of the refreshing detection equipment so as to determine whether the target firmware needs to be refreshed or not;

and the first processing module is used for switching the file reading link route memory of the target firmware to the target equipment when local refreshing is required, so that the target firmware reads the file from the target equipment for refreshing.

According to the firmware refreshing device provided by the embodiment of the invention, the link is changed, so that the firmware can be refreshed only by changing the file in the external equipment connected to the link without the participation of any primary file when the firmware is refreshed, the restriction of the primary file on firmware refreshing is reduced, and the success rate of firmware refreshing is greatly improved.

According to a third aspect, an embodiment of the present invention provides an electronic device, including: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory having stored therein computer instructions, and the processor executing the computer instructions to perform the method for configuring a computational core according to the first aspect or any one of the embodiments of the first aspect.

According to a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer instructions for causing a computer to execute the method for configuring a computing core according to the first aspect or any one of the implementation manners of the first aspect.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a flow chart of a firmware refresh method according to an embodiment of the present invention;

FIG. 2 is a flow chart of a firmware refresh method according to an embodiment of the present invention;

FIG. 3A is a hardware topology diagram of a firmware refresh method according to an embodiment of the invention;

FIG. 3B is a flow chart of a firmware refresh method according to an embodiment of the invention;

FIG. 4 is a block diagram of a firmware refresh apparatus according to an embodiment of the present invention;

fig. 5 is a schematic diagram of a hardware structure of an electronic device according to an embodiment of the present invention. .

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

According to the firmware refreshing method provided by the embodiment of the invention, the link is changed, so that the firmware can be refreshed only by changing the file in the external equipment connected to the link without the participation of any primary file when the firmware is refreshed, the restriction of the primary file on firmware refreshing is reduced, and the success rate of firmware refreshing is greatly improved.

In accordance with an embodiment of the present invention, there is provided a firmware refresh method embodiment, it should be noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.

In this embodiment, a configuration method of a computing core is provided, which may be used in an electronic device, such as a computer, a server, a tablet computer, and the like, and fig. 1 is a flowchart of a firmware refreshing method according to an embodiment of the present invention, as shown in fig. 1, the flowchart includes the following steps:

and S11, acquiring the working state of the refresh detection device to determine whether the target firmware needs to be refreshed.

Specifically, the detection of the cap-skipping state may be selected to determine whether the target firmware needs to be refreshed.

In practical application, if a main board a exists, the cap-jumping state of the main board a is a cap-jumping state a, and the cap-jumping state a corresponds to a state where firmware refreshing is not required, the main board a is not refreshed in a current state. If the cap-jumping state is changed, taking the main board a as an example, assuming that the cap-jumping state of the main board a is modified to the cap-jumping state b, and the cap-jumping state b corresponds to the state that firmware refreshing needs to be performed, the main board a is refreshed under the condition that the main board a is in the cap-jumping state b.

It should be noted that, in practical applications, whether any target firmware needs to be refreshed or not may be determined by any means, in the above example, the motherboard and the cap-skipping state of the motherboard are taken as a basis for determining whether firmware refreshing needs to be performed, which is only an example.

Details about this step will be described later.

And S12, when local refreshing is needed, switching the file reading link of the target firmware to a target device through the memory, so that the memory reads a file from the target device for refreshing.

Specifically, when local refreshing is required, the file reading link of the target firmware is switched from the memory to the external storage device, so that the memory reads the file from the external storage device for refreshing.

Still taking the main board a as an example, in the execution process, by detecting the cap-jumping state of the main board a, it is determined that the cap-jumping state of the main board a is the cap-jumping state b, where the cap-jumping state b corresponds to a state that firmware refreshing needs to be performed, and the central processing unit switches the file reading link of the main board a from the memory to the external storage device, so that the memory reads a file from the external storage device for refreshing.

Further, in practical application, the target device may be any device, and is not limited to an external storage device, in the above example, the central processing unit switches the file reading link of the motherboard a from the memory to the external storage device, so that the memory reads the file from the external storage device for refreshing, which is only an example.

Details about this step will be described later.

In this embodiment, a firmware refreshing method is provided, which may be used in an electronic device, such as a computer, a server, a tablet computer, and the like, fig. 2 is a flowchart of the firmware refreshing method according to an embodiment of the present invention, and as shown in fig. 2, the flowchart includes the following steps:

and S21, acquiring the working state of the refresh detection device to determine whether the target firmware needs to be refreshed.

Specifically, S21 includes:

s211, detecting the working state through the first detector, and acquiring the working state of the refreshing detection device.

Specifically, the Complex Programmable Logic Device (CPLD) may be selected to detect the cap-jumping state to determine whether the target firmware needs to be refreshed.

In practical application, if a mainboard B exists, the cap-jumping state of the mainboard B is detected through a complex programmable logic device, the detection result of the cap-jumping state is that the mainboard B is in a cap-jumping state A, and the cap-jumping state A corresponds to the state without firmware refreshing, and the mainboard B is not refreshed in the current state. If the cap-jumping state is changed, taking the mainboard B as an example, the changed cap-jumping state of the mainboard B is detected by the complex programmable logic device, and if the detection result of the cap-jumping state is that the mainboard B is in the cap-jumping state B, and the cap-jumping state B corresponds to the state that firmware refreshing is required, the mainboard B is refreshed under the condition that the mainboard B is in the cap-jumping state B.

It should be noted that, in practical applications, whether any target firmware needs to be refreshed or not may be determined by any means, in the above example, the motherboard and the cap-skipping state of the motherboard are used as a basis for determining whether firmware refreshing needs to be performed, and the complex programmable logic device is used as a detector, which is only an example.

And S22, when local refreshing is needed, switching the file reading link of the target firmware to a target device through the memory, so that the memory reads a file from the target device for refreshing.

Specifically, S22 includes:

s221, sending a signal to a line control module to enable the line control module to switch the file reading link route memory of the target firmware to the target device.

Specifically, the line control module sends a signal through different buses, so that the line control module switches the file reading link of the target firmware to the target device through the memory.

Further, in a specific implementation, the read link can be switched from being connected to the flash memory through the SPI bus by the south bridge chip to being connected to the external storage device through the USB bus.

For example, taking the motherboard C as an example, in the execution process, by detecting the cap-jumping state of the motherboard C, it is determined that the cap-jumping state of the motherboard C is the cap-jumping state b, and the cap-jumping state b corresponds to the state that firmware refreshing needs to be performed, and the central processing unit switches the route of the read link, which is connected to the flash memory through the SPI bus, to the route of the external storage device through the USB bus through the south bridge chip.

Further, in practical application, the target device may be any device, and is not limited to an external storage device, in the above example, the central processing unit switches the file reading link of the motherboard C from the memory to the external storage device, so that the memory reads the file from the external storage device for refreshing, which is only an example.

S222, judging whether the circuit control module is refreshed or not to obtain a judgment result;

specifically, whether or not to perform refresh is further judged, and a refresh command is confirmed.

For example, assuming that a motherboard D determines that the cap-skipping state of the motherboard D is the cap-skipping state b by detecting the cap-skipping state of the motherboard D, the cap-skipping state b corresponds to a state that firmware refreshing needs to be performed, and the central processing unit switches the file reading link of the motherboard D from the memory to the external storage device, so that the memory reads a file from the external storage device for refreshing.

Before formal refresh, the south bridge chip H on the motherboard D detects a General-purpose input/output (GPIO) pin and checks whether refresh is confirmed.

And S223, enabling the target firmware to read a file from the target equipment for refreshing based on the judgment result.

Still taking the motherboard D as an example, after the south bridge chip on the motherboard D detects the GPIO interface, it is determined that the motherboard needs to be refreshed, and then the refreshing is implemented by copying all the refresh files in the external storage device into the flash memory.

It should be noted that, in practical applications, the further determination of whether to perform the refresh may be performed in various manners, and in the above example, the determination of whether to perform the refresh by determining to detect the output signal of the GPIO interface is merely an example, and actually, any manner may be used.

Further, in practical applications, the refresh may be implemented in any manner, and in the above example, the refresh is implemented by copying all refresh files in the external storage device to the flash memory, which is only an example, and any manner may be actually used.

As a specific application example of this embodiment, as shown in fig. 3A, the firmware refresh method includes:

the complex programmable logic device 33 detects the cap-skipping state of the target firmware, when the cap-skipping state of the target firmware is the state that the firmware needs to be refreshed, the complex programmable logic device sends a command to the central processing unit 31, the central processing unit receives the command and then sends the command to the south bridge chip 32 through the direct media interface bus, the south bridge chip 32 connects the original file reading path of the target firmware to the flash memory 35 through the serial peripheral bus, and then the target firmware is connected to the external storage medium 34 through the universal serial bus, and then the south bridge chip checks the state of the universal input/output interface, and when the target firmware needs to be refreshed, the target firmware is refreshed.

As a specific application example of this embodiment, as shown in fig. 3B, the firmware refresh method includes:

and S1, changing the state of the jump cap.

Specifically, in practical application, it is assumed that there is a motherboard X, the cap-jumping state of the motherboard X is the first cap-jumping state, and the first cap-jumping state corresponds to a state that firmware refreshing is not required, and the cap-jumping state is changed.

S2, detecting whether the cap jumping state is the state to be refreshed, if yes, executing the step S3, otherwise executing the step S6.

Specifically, still taking the motherboard X as an example, the complex programmable logic device is used to detect the cap-jumping state of the motherboard X, and the detection result of the cap-jumping state is that the motherboard B is in the cap-jumping state a, and if the cap-jumping state a corresponds to the state a, firmware refreshing is not required, then in the current state, step S6 is executed. If the cap jumping state is changed, taking the motherboard B as an example, the changed cap jumping state of the motherboard B is detected by the complex programmable logic device, and if the detection result of the cap jumping state is that the motherboard B is in the cap jumping state B, and the cap jumping state B corresponds to the state that firmware refreshing needs to be performed, in the current state, step S3 is performed.

And S3, changing the link route.

Specifically, for example, when the motherboard X is in the cap-skipping state b, the cap-skipping state of the motherboard X is detected, and it is determined that the cap-skipping state of the motherboard X is the cap-skipping state b, where the cap-skipping state b corresponds to a state that firmware refreshing needs to be performed, and the central processing unit switches the read link from the SPI bus to the flash memory to the external storage device via the USB bus.

S4, further determining whether to refresh, if yes, executing step S5, otherwise, executing step S6.

Specifically, still taking the motherboard X as an example, before the formal refresh, the south bridge chip K on the motherboard X detects the pin of the general input/output port, and checks whether the refresh is confirmed. If the refresh is confirmed, step S5 is executed, otherwise step S6 is executed.

S5, refreshing

Specifically, still taking the motherboard X as an example, after the south bridge chip on the motherboard D detects the GPIO interface, it is determined that the motherboard needs to be refreshed, and then the refresh is implemented by copying all refresh files in the external storage device into the flash memory.

In practical applications, the refresh may be implemented in any manner, and in the above example, the refresh is implemented by copying all refresh files in the external storage device into the flash memory, which is only an example, and any manner may be actually used.

S6, no refresh is performed.

In this embodiment, a firmware refreshing apparatus is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, and the details already described are not repeated. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

The present embodiment provides a firmware refreshing apparatus, as shown in fig. 4, including:

an obtaining module 41, configured to obtain a working state of the refresh detection device to determine whether the target firmware needs to be refreshed;

the first processing module 42 is configured to, when the target firmware needs to be refreshed, switch a file reading link of the target firmware to a target device, so that the target firmware reads a file from the target device for refreshing.

The firmware refresh apparatus in this embodiment is presented in the form of functional units, where a unit refers to an ASIC circuit, a processor and a memory executing one or more software or fixed programs, and/or other devices that may provide the above-described functionality.

Further functional descriptions of the modules are the same as those of the corresponding embodiments, and are not repeated herein.

An embodiment of the present invention further provides an electronic device, which has the firmware refreshing apparatus shown in fig. 5.

Referring to fig. 5, fig. 5 is a schematic structural diagram of an electronic device according to an alternative embodiment of the present invention, and as shown in fig. 5, the electronic device may include: at least one processor 51, such as a CPU (Central Processing Unit), at least one communication interface 53, memory 54, at least one communication bus 52. Wherein a communication bus 52 is used to enable the connection communication between these components. The communication interface 53 may include a Display (Display) and a Keyboard (Keyboard), and the optional communication interface 53 may also include a standard wired interface and a standard wireless interface. The Memory 54 may be a high-speed RAM Memory (volatile Random Access Memory) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The memory 54 may alternatively be at least one memory device located remotely from the processor 51. Wherein the processor 51 may be in connection with the apparatus described in fig. 5, the memory 54 stores an application program, and the processor 51 calls the program code stored in the memory 54 for performing any of the above-mentioned method steps.

The communication bus 52 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 52 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.

The memory 54 may include a volatile memory (RAM), such as a random-access memory (RAM); the memory may also include a non-volatile memory (english: non-volatile memory), such as a flash memory (english: flash memory), a hard disk (english: hard disk drive, abbreviated: HDD) or a solid-state drive (english: SSD); the memory 54 may also comprise a combination of the above types of memories.

The processor 51 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP.

The processor 51 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

Optionally, the memory 54 is also used to store program instructions. The processor 51 may call program instructions to implement a firmware refresh method as shown in any of the embodiments of the present application.

The embodiment of the invention also provides a non-transitory computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can execute the reading method of the ISO file in any method embodiment. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid State Drive (SSD), or the like; the storage medium may also comprise a combination of memories of the kind described above.

Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A firmware refresh method, comprising:

when the target firmware needs to be refreshed, switching a file reading link of the target firmware from a memory to a target device, so that the memory reads a file from the target device for refreshing.

2. The method of claim 1, wherein obtaining an operating state of a refresh detection device to determine whether a target firmware needs to be refreshed comprises obtaining an operating state of a refresh detection device to determine whether a target firmware needs to be refreshed

3. The method of claim 1, wherein switching the file read link of the target firmware to the target device comprises:

4. The method according to claim 1, wherein when the target firmware needs to be refreshed, switching a file reading link of the target firmware from a memory to a target device so that the memory reads a file from the target device for refreshing comprises:

5. The method of claim 1, further comprising:

and presetting the memory so that the memory can be read.

6. The method of claim 3, further comprising:

7. A firmware refresh apparatus, comprising:

the first processing module is used for switching a file reading link route memory of the target firmware to a target device when the target firmware needs to be refreshed, so that the target firmware reads a file from the target device for refreshing.

8. An electronic device, comprising: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the steps of the method of any one of claims 1-6.

9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1-6.

10. A firmware refresh system, comprising:

the central processing unit is connected to the south bridge chip and used for issuing a link change instruction during refreshing, so that a file reading link of the target firmware is switched to target equipment from the memory, and the memory reads a file from the target equipment for refreshing;

the south bridge chip is connected to the central processing unit, the target equipment, the memory and the detector and is used for transmitting signals among all the firmware;

the target device is connected to the south bridge chip and used for storing the refreshing file;

the memory is connected to the south bridge chip and used for storing original files and reading refreshed files during refreshing;

and the detector is connected to the south bridge chip and is used for detecting the working state of the target firmware so as to judge whether to refresh the target firmware.