CN219533773U

CN219533773U - Firmware burning circuit and system

Info

Publication number: CN219533773U
Application number: CN202320293304.6U
Authority: CN
Inventors: 请求不公布姓名
Original assignee: Shanghai Biren Intelligent Technology Co Ltd
Current assignee: Shanghai Bi Ren Technology Co ltd
Priority date: 2023-02-22
Filing date: 2023-02-22
Publication date: 2023-08-15
Anticipated expiration: 2033-02-22

Abstract

The utility model provides a firmware burning circuit and a system, which belong to the technical field of circuit design, wherein the circuit comprises: the system comprises a first burning branch, a second burning branch, a multiplexer and a firmware memory, wherein the first burning branch adopts a PCIE link, and the second burning branch comprises a microcontroller and a bus interface; the microcontroller is used for: under the condition that a first control command and a first firmware file to be burned are received through a bus interface, outputting a first control signal to a control end of the multiplexer, and outputting the first firmware file to a second input end of the multiplexer; the multiplexer is used for: under the condition that the first control signal is received, the first firmware file is output to the firmware memory, and the firmware memory is used for burning based on the first firmware file. When a problem occurs in the first recording branch, the multiplexer can be controlled by the first control signal so as to record through the second recording branch, and the reliability of the recording circuit is effectively improved.

Description

Firmware burning circuit and system

Technical Field

The present utility model relates to the field of circuit design technologies, and in particular, to a firmware burning circuit and a system.

Background

After the graphics processor (graphics processing unit, GPU) is powered on and reset, the graphics processor needs to load the graphics card basic input output system (Video Basic Input Output System, VBIOS) firmware in Flash memory (Flash) through a serial peripheral interface (Serial Peripheral Interface, SPI) to work normally. When the VBIOS firmware in the SPI Flash is damaged or needs to be upgraded, the burning problem of the GPU VBIOS is involved.

At present, the writing scheme of the GPU VBIOS is completed through an in-band high-speed serial computer expansion bus standard (peripheral component interconnect express, PCIE), and the GPU needs to be connected to the GPU through PCIE under an Operating System (OS) of a server, then firmware needing to be written is transferred to a microprocessor (Microprocessor Unit, MPU) inside the GPU through PCIE by using a developed writing instruction under the OS, and then the MPU writes the firmware into the SPI Flash through SPI.

However, since the present scheme is completed in-band, the writing of the GPU VBIOS strongly depends on the stability of the PCIE link and the normal operation of the GPU, and in the case that the PCIE link has a problem or the GPU cannot normally operate, the writing of the GPU VBIOS cannot be performed normally, and the reliability of the writing line is low.

Disclosure of Invention

The utility model provides a firmware burning circuit and a firmware burning system, which are used for solving the problem of low reliability of a burning circuit in the prior art.

The utility model provides a firmware burning circuit, comprising: the system comprises a first burning branch, a second burning branch, a multiplexer and a firmware memory, wherein the first burning branch adopts a high-speed serial computer expansion bus standard PCIE link, and the second burning branch comprises a microcontroller and a bus interface;

the input end of the first burning branch is connected to the first output end of the server, the output end of the first burning branch is connected to the first input end of the multiplexer, the input end of the second burning branch is connected to the second output end of the server, the first output end of the second burning branch is connected to the second input end of the multiplexer, the second output end of the second burning branch is connected to the control end of the multiplexer, the output end of the multiplexer is connected to the firmware memory, the first end of the bus interface is used as the input end of the second burning branch, the second end of the bus interface is connected to the input end of the microcontroller, the first output end of the microcontroller is used as the first output end of the second burning branch, and the second output end of the microcontroller is used as the second output end of the second burning branch;

the microcontroller is used for: under the condition that a first control command from the server and a first firmware file to be burned are received through the bus interface, outputting a first control signal to a control end of the multiplexer, and outputting the first firmware file to a second input end of the multiplexer;

the multiplexer is used for: and under the condition that the first control signal is received, outputting the first firmware file to the firmware memory for burning by the firmware memory based on the first firmware file.

According to the firmware programming circuit provided by the utility model, the first programming branch comprises a processing module and a PCIE interface;

the first end of the PCIE interface is used as the input end of the first burning branch, the second end of the PCIE interface is connected to the input end of the processing module, and the output end of the processing module is used as the output end of the first burning branch;

the processing module is used for: and outputting the second firmware file to the first input end of the multiplexer under the condition that the second firmware file to be burned is received through the PCIE interface.

According to the firmware burning circuit provided by the utility model, the microcontroller is further used for: outputting a second control signal to a control terminal of the multiplexer under the condition that a second control command from the server is received through the bus interface;

the multiplexer is further configured to: and outputting the second firmware file to the firmware memory for burning based on the second firmware file under the condition that the second control signal is received.

According to the firmware burning circuit provided by the utility model, the server is used for: and sending the first control command and the first firmware file to the microcontroller through the bus interface when an instruction for representing that the processing module is executing service is received.

According to the firmware burning circuit provided by the utility model, the microcontroller is integrated in the processing module.

According to the firmware burning circuit provided by the utility model, the processing module is further used for: and after the burning of the firmware memory is completed, loading the burned firmware file from the firmware memory.

According to the firmware burning circuit provided by the utility model, the server is used for: and under the condition that an ipmitool command input by a user through a Baseboard Management Controller (BMC) serial port or a server system is received, the first control command and the first firmware file are sent to the microcontroller through the bus interface.

According to the firmware burning circuit provided by the utility model, the server comprises an operating system module and a management controller;

the output end of the operating system module is used as a first output end of the server, and the output end of the management controller is used as a second output end of the server.

According to the firmware burning circuit provided by the utility model, the output end of the management controller is connected with the input end of the second burning branch through the system management bus SMBus.

The utility model also provides a firmware burning system, which comprises: the firmware burning circuit of any one of the embodiments.

Compared with the firmware burning circuit and the firmware burning system which only depend on PCIE links to conduct firmware burning in the related art, the firmware burning circuit and the firmware burning system provided by the utility model have the advantages that when the PCIE links are in a problem, or the GPU on the PCIE links cannot normally work, the firmware is not normally burned, and the reliability of a burning line is low; in addition, under the condition that the burning cannot be normally performed by utilizing the scheme in the related technology, the burning can only be performed in an off-line burning mode, so that the server is required to be powered down, the GPU on the PCIE link is disassembled, the off-line burning is performed by utilizing a specific burning environment and a specific tool, and then the related environment of the GPU, such as a heat dissipation environment, is rebuilt, so that the normal service operation of the server is easily influenced, and the operation and the maintenance are difficult.

Drawings

In order to more clearly illustrate the utility model or the technical solutions of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are some embodiments of the utility model, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic diagram of a firmware burning circuit according to the present utility model;

FIG. 2 is a schematic diagram of a prior art firmware burning circuit;

FIG. 3 is a schematic diagram of an off-line recording of a firmware recording circuit according to the prior art;

FIG. 4 is a second schematic diagram of the firmware burning circuit according to the present utility model;

fig. 5 is a schematic diagram of a firmware burning system according to the present utility model.

Reference numerals:

100: a firmware burning circuit; 200: a server;

101: a first burning branch; 102: a second burning branch; 103: a multiplexer; 104: a firmware memory;

1011: a processing module; 1012: PCIE interface;

1021: a microcontroller; 1022: a bus interface;

201: an operating system module; 202: and managing the controller.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present utility model more apparent, the technical solutions of the present utility model will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present utility model, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the utility model without making any inventive effort, are intended to be within the scope of the utility model.

The firmware burning circuit and system of the present utility model are described below with reference to the accompanying drawings.

Fig. 1 is a schematic diagram of a firmware burning circuit according to the present utility model, and as shown in fig. 1, the firmware burning circuit 100 includes:

the first burning branch 101, the second burning branch 102, the multiplexer 103 and the firmware memory 104, wherein the first burning branch 101 adopts a PCIE link, and the second burning branch 102 comprises a microcontroller 1021 and a bus interface 1022.

The circuit connection structure is specifically as follows:

the input end of the first writing branch 101 is connected to the first output end of the server 200, the output end of the first writing branch 101 is connected to the first input end (2) of the multiplexer 103, the input end of the second writing branch 102 is connected to the second output end of the server 200, the first output end of the second writing branch 102 is connected to the second input end (3) of the multiplexer 103, the second output end of the second writing branch 102 is connected to the control end (4) of the multiplexer 103, the output end (1) of the multiplexer 103 is connected to the firmware memory 103, the first end of the bus interface 1022 is used as the input end of the second writing branch 102, the second end of the bus interface 1022 is connected to the input end of the microcontroller 1021, the first output end of the microcontroller 1021 is used as the first output end of the second writing branch 102, and the second output end of the microcontroller 1021 is used as the second output end of the second writing branch 102;

the microcontroller 1021 is configured to: in the case that a first control command and a first firmware file to be burned from the server 200 are received through the bus interface 1022, a first control signal is output to the control terminal of the multiplexer 103, and the first firmware file is output to the second input terminal of the multiplexer 103;

the multiplexer 103 is configured to: upon receiving the first control signal, the first firmware file is output to the firmware memory 104, so that the firmware memory 104 burns based on the first firmware file.

It should be noted that, the GPU Board that normally works in the server system requires that the GPU VBIOS can be stably and conveniently burned, so that a reasonable GPU Board (Board) and hardware system scheme should be designed in combination with the server system.

In the prior art, the implementation is completed by using an in-band PCIE, fig. 2 is a schematic structural diagram of a firmware burning circuit in the prior art, as shown in fig. 2, a GPU needs to be found by using a PCIE under an OS of a server system, then a burning instruction is used under the OS to transfer a firmware file to be burned to an MPU inside the GPU through the PCIE, and then the MPU burns the firmware file into an SPI Flash through an SPI.

However, since the prior art scheme is only completed in-band, depending on the stability of PCIE link and normal operation of GPU, the burning condition is harsh and fault tolerance is poor, and when the following three cases occur, the scheme cannot be burned any more:

(1) A PCIE link presents a problem, resulting in failure to find a corresponding GPU under the OS;

(2) The firmware in the current SPI Flash is destroyed, so that the GPU cannot work normally;

(3) When the firmware is upgraded, the wrong firmware version is burnt, so that the GPU cannot work normally.

When the above situation causes that the prior art scheme cannot be implemented, the method can only be carried out by an off-line burning mode. Fig. 3 is a schematic diagram of offline programming of a firmware programming circuit in the prior art, as shown in fig. 3, in which a GPU board needs to be detached from a server, a heat sink is removed, and a specific offline programming tool is used to perform programming in combination with a host computer software, for example, the host computer is connected to a personal computer (personal computer, PC) through an SPI, which brings new problems:

1) The GPU board card or the module must be disassembled from the server, so that the power of the server is required to be cut off, the server is taken off from the cabinet, the normal service operation of the server is affected, and difficulties are brought to operation and maintenance;

2) When the data center is used for recording, a specific recording environment and tools are needed, if the conditions are not met, the problem cannot be timely handled on the site of the data center, and the timeliness is poor;

3) When the GPU board card is burnt, the radiating fins of the GPU board card need to be dismantled, and the GPU board card is possibly damaged; after the burning is finished, a heat radiation environment needs to be rebuilt, such as operations of re-brushing heat radiation paste, attaching heat radiation strips and the like, and more uncertainty is introduced to the reliability of the board.

Aiming at the problems, the method and the device increase the out-of-band firmware burning mode on the basis of the original technical scheme.

Specifically, in the firmware programming circuit provided by the utility model, the firmware programming circuit comprises a first programming branch and a second programming branch, wherein the output ends of the first programming branch and the second programming branch are respectively connected to a multiplexer, and the multiplexer determines whether the firmware memory is programmed by the first programming branch or the second programming branch based on a signal received by a control end;

for the second burning branch, specifically, the second burning branch includes a microcontroller and a bus interface, the microcontroller may be connected to the server through the bus interface, for example, the microcontroller may be connected to the server through a bus interface of a system management bus (System Management Bus, SMBus), and when a first control command from the server and a first firmware file to be burned are received, the first control signal is output to a control end of the multiplexer, and the first firmware file is output to a second input end of the multiplexer, and when the first control signal is received, the multiplexer communicates the second input end of the multiplexer with an output end of the multiplexer, that is, outputs the first firmware file to the firmware memory, so that the firmware memory can burn based on the first firmware file.

Optionally, the firmware burning circuit may be, but not limited to, a smart card, a GPU board, a digital signal processing card, or the like.

Alternatively, the firmware memory may be, but is not limited to, a Flash memory (Flash memory) with SPI or an electrically erasable programmable read-only memory (EEPROM) with an integrated circuit bus (Inter-Integrated Circuit, I2C) interface;

optionally, the server may comprise a baseboard management controller (Baseboard Management Controller, BMC) or a central processor (Central Processing Unit, CPU), for example, may be connected by the BMC to the second burning branch, in particular to the microcontroller via a bus interface, to send control signals and firmware files to the microcontroller.

It should be noted that, the BMC is a core of the out-of-band management system in the server, and may perform operations such as monitoring and management independently of the in-band system of the PCIE of the server.

Compared with the firmware programming circuit provided by the embodiment of the utility model which only depends on PCIE links to perform firmware programming in the related art, the problem of the PCIE links or the problem of low reliability of the programming circuit exists because the GPU on the PCIE links cannot normally operate, the second programming branch is additionally arranged on the basis of the original in-band PCIE links (first programming branch), and the multiplexer is used for selecting the first programming branch or the second programming branch to perform the programming, so that when the first programming branch has the problem, the multiplexer is controlled by the first control signal to output the first firmware file from the second programming branch to the firmware memory to perform the programming, namely the second programming branch is used for performing the programming, thereby effectively improving the reliability of the programming circuit;

in addition, under the condition that the burning cannot be normally performed by utilizing the scheme in the related technology, the burning can only be performed in an off-line burning mode, so that the server is required to be powered down, the GPU on the PCIE link is disassembled, the off-line burning is performed by utilizing a specific burning environment and a specific tool, and then the related environment of the GPU, such as a heat dissipation environment, is rebuilt, so that the normal service operation of the server is easily influenced, and the operation and the maintenance are difficult.

Optionally, fig. 4 is a second schematic structural diagram of the firmware burning circuit provided by the present utility model, as shown in fig. 4, the first burning branch 101 includes a processing module 1011 and a PCIE interface 1012;

a first end of the PCIE interface 1012 is used as an input end of the first writing branch 101, a second end of the PCIE interface 1012 is connected to an input end of the processing module 1011, and an output end of the processing module 1011 is used as an output end of the first writing branch 101;

the processing module 1011 is configured to: in the case that a second firmware file to be burned is received through the PCIE interface 1012, the second firmware file is output to the first input terminal of the multiplexer 103.

Specifically, for the first recording branch, the first recording branch includes a processing module and a PCIE interface, and when the server sends the second firmware file to be recorded to the processing module through the PCIE interface, the processing module sends the second firmware file to the multiplexer, specifically whether to use the second firmware file of the first recording branch to record, and also needs to see the received control signal of the multiplexer.

Alternatively, the processing module may comprise a GPU.

It should be noted that, for the GPU, the firmware that needs to be loaded may be VBIOS firmware, the VBIOS firmware needs to be loaded for the normal operation of the GPU, and the specific GPU may load the VBIOS firmware through the SPI interface.

Optionally, the microcontroller 1021 is further configured to: in case of receiving a second control command from the server 200 through the bus interface 1022, outputting a second control signal to the control terminal of the multiplexer 103;

the multiplexer 103 is further configured to: and outputting the second firmware file to the firmware memory 104 for burning by the firmware memory 104 based on the second firmware file when the second control signal is received.

Specifically, when receiving the second control command from the server through the bus interface, the microcontroller may output a second control signal to the control end of the multiplexer, so that the multiplexer outputs the second firmware file transmitted through the first recording branch to the firmware memory, and the firmware memory records based on the second firmware file.

Alternatively, the control signals may include a first control signal and a second control signal, and the control signals received by the multiplexer may all be sent by the server through the microcontroller and the bus interface;

alternatively, the first control signal and the second control signal may be at different levels, for example, the first control signal is at a low level and the second control signal is at a high level; the multiplexer can connect the first burning branch and the firmware memory under the condition of receiving the high level; and under the condition of receiving the low level, connecting the second burning branch circuit with the firmware memory.

Optionally, the server 200 is configured to: upon receiving an instruction to characterize that the processing module 1011 is executing a service, the first control command and the first firmware file are sent to the microcontroller 1021 via the bus interface 1022.

Specifically, when the server receives an instruction to characterize that the processing module of the first burning branch is executing the service, the server can send a first control command and a first firmware file to the microcontroller through the bus interface so as to burn the firmware memory through the second burning branch, thereby avoiding occupation of a PCIE link of the first burning branch, affecting the execution of the service by the processing module and effectively improving the reliability of the execution of the service by the processing module.

Optionally, the service executed by the above-mentioned processing module may be a GPU service, where the operation of the GPU service is that a CPU in the server transmits a service instruction through a PCIE link (first burning branch), and firmware burning may be performed by an in-band PCIE manner when the processing module does not execute the service, so as to avoid the occupation of the PCIE link from affecting the operation of the service.

Alternatively, the microcontroller 1021 may be a microcontroller integrated in the processing module 1011.

Specifically, when the processing module cannot work normally, the technical staff can set the microcontroller (Microcontroller Unit, MCU) integrated in the processing module to still work normally, in this case, the MCU in the second burning branch can be the MCU integrated in the processing module, and compared with the MCU which is additionally and independently set, the embodiment of the utility model directly uses the MCU in the processing module to form the second burning branch, thereby simplifying the circuit structure to a certain extent and improving the integration degree of the circuit.

Optionally, the processing module 1011 is further configured to: after the firmware memory 104 is burned, the burned firmware file is loaded from the firmware memory 104.

Alternatively, after the firmware memory 104 is burned, the burned firmware file may be loaded in the firmware memory 104 through the SPI.

Specifically, after the firmware memory is burned, for example, after an instruction for characterizing that the firmware memory is burned is received, the processing module may load the burned firmware file in the firmware memory through the SPI, for example, load VBIOS firmware in the SPI Flash through the SPI interface, so as to work normally.

Optionally, the server 200 is configured to: and under the condition that an ipmitool command input by a user through a BMC serial port or a server system is received, the first control command and the first firmware file are sent to the microcontroller through the bus interface.

Specifically, when the user determines that the current first burning branch is unavailable for burning, the ipmitool command is input to the server through the BMC serial port or the server system, and when the server receives the ipmitool command, the first control command and the first firmware file can be sent to the microcontroller through the bus interface, so that the first firmware file is transmitted to the multiplexer through the microcontroller, and then the multiplexer sends the first firmware file to the firmware memory for burning, namely, the firmware burning is realized through the second burning branch.

Optionally, as shown in fig. 4, the server 200 includes an operating system module 201 and a management controller 202;

an output of the operating system module 201 serves as a first output of the server 200, and an output of the management controller 202 serves as a second output of the server 200.

Specifically, an operating system module in the server is connected to the first burning branch so as to transmit a second firmware file to the firmware memory through the first burning branch for firmware burning; and the management controller in the server is connected with the second burning branch circuit so as to transmit the first firmware file to the firmware memory through the second burning branch circuit for firmware burning.

Alternatively, the management controller may be, but is not limited to, a BMC.

Optionally, as shown in fig. 4, the output end of the management controller 202 is connected to the input end of the second recording branch 102 through an SMBus.

On the other hand, the embodiment of the utility model also provides a firmware burning system, which comprises: the server and the firmware burning circuit of any of the above embodiments.

Optionally, the server includes an operating system module and a management controller, which may be, but is not limited to, a BMC.

The firmware burning system provided by the embodiment of the utility model is specifically described below.

On the basis of the prior art, the method for adding the out-of-band SMBus can burn firmware in SPI Flash of the GPU through the BMC under the server system.

It should be noted that, SPI Flash is a storage device with an SPI interface, and is used for storing VBIOS firmware, and after GPU is powered on and reset, firmware is loaded from SPI Flash through the SPI interface.

Fig. 5 is a schematic diagram of a firmware burning system provided by the present utility model, as shown in fig. 5, on the basis of the prior art scheme, an MCU and an SPI Multiplexer (MUX) unit are added in the present utility model, and an SPI MUX of either one is selected in the present utility model. The MCU is connected to a BMC in the server system through the SMBus, the SPI MUX is equipment supporting one of two SPI channels, the SPI channels are gated by outputting different control signals to the control end of the SPI MUX, an Output Enable (OE) can be used for representing the control end of the SPI MUX, the BMC can send a command to the MCU through the SMBus to set the control signal of the SPI MUX high or low, and when the control signal is high, the SPI MUX gates 1-2; when the control signal is low, 1-3 is gated.

The burning process is specifically as follows:

when the GPU PCIE link (first burning branch) works normally and the GPU can be found through PCIE under the operating system module, the existing in-band PCIE mode is used for burning;

when the GPU cannot be found through PCIE under the operating system module, the out-of-band mode is used, and the programming is completed through the BMC:

s1, sending a command to an MCU (micro control unit) through a BMC (baseboard management controller) serial port on a server or using an ipmitool command under a server system by the BMC through the SMBus, setting a control signal of SPI MUX low, and gating 1-3, wherein SPI Flash is hung under the MCU;

s2, transmitting a firmware file to be burned (a first firmware file) to the MCU by the BMC through the SMBus, and burning the MCU into the SPI Flash through the SPI after receiving the first firmware file to be burned;

s3, after the burning is finished, the BMC sends a command to the MCU through the SMBus, the control signal of the SPI MUX is set high, 1-2 is gated, and the SPI Flash is hung under the GPU;

s4, resetting the GPU to load the new VBIOS firmware.

The existing writing mode of the GPU VBIOS depends on the stability of a PCIE link and the normal operation of the GPU, and once the GPU is abnormal, the on-line writing mode cannot be used for updating. The utility model increases the burning mode of the out-of-band SMBus while maintaining the original burning mode, and has the following beneficial effects compared with the prior art scheme:

1) The maintainability is strong. The method and the device support the in-band PCIE and the out-of-band SMBus to burn the VBIOS firmware of the GPU, and even if the GPU cannot work normally, the BMC can burn the firmware of the SPI Flash through the SMBus without disassembling the device and the card for offline burning;

2) The reliability is higher. The GPU completes loading the VBIOS firmware after the starting-up reset, so that the VBIOS firmware of the running GPU can be burnt at any time. The operation of the GPU service is that the CPU transmits service instructions through PCIE, and the service instructions can be burnt in an in-band PCIE mode when no service is executed; when the GPU is executing the service, the service can be burnt in an SMBus mode, so that the service operation is prevented from being influenced by occupation of PCIE links.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present utility model, and are not limiting; although the utility model has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present utility model.

Claims

1. A firmware burning circuit, comprising: the system comprises a first burning branch, a second burning branch, a multiplexer and a firmware memory, wherein the first burning branch adopts a high-speed serial computer expansion bus standard PCIE link, and the second burning branch comprises a microcontroller and a bus interface;

2. The firmware burning circuit of claim 1, wherein the first burning branch comprises a processing module and a PCIE interface;

3. The firmware burning circuit of claim 2, wherein,

the microcontroller is further configured to: outputting a second control signal to a control terminal of the multiplexer under the condition that a second control command from the server is received through the bus interface;

4. A firmware burning circuit according to claim 2 or 3, wherein the server is configured to: and sending the first control command and the first firmware file to the microcontroller through the bus interface when an instruction for representing that the processing module is executing service is received.

5. The firmware burning circuit of claim 2, wherein the microcontroller is a microcontroller integrated in the processing module.

6. A firmware burning circuit according to claim 2 or 3, wherein the processing module is further configured to: and after the burning of the firmware memory is completed, loading the burned firmware file from the firmware memory.

7. The firmware burning circuit of claim 1, wherein the server is configured to: and under the condition that an ipmitool command input by a user through a Baseboard Management Controller (BMC) serial port or a server system is received, the first control command and the first firmware file are sent to the microcontroller through the bus interface.

8. The firmware burning circuit of claim 1, wherein the server comprises an operating system module and a management controller;

9. The firmware burning circuit of claim 8, wherein an output of the management controller is connected to an input of the second burning branch through a system management bus SMBus.

10. A firmware burning system, comprising: a server and a firmware burning circuit as claimed in any one of claims 1 to 9.