CN115437658A - Firmware maintenance method and system - Google Patents

Firmware maintenance method and system Download PDF

Info

Publication number
CN115437658A
CN115437658A CN202211075039.0A CN202211075039A CN115437658A CN 115437658 A CN115437658 A CN 115437658A CN 202211075039 A CN202211075039 A CN 202211075039A CN 115437658 A CN115437658 A CN 115437658A
Authority
CN
China
Prior art keywords
memory
control module
firmware
memory control
processing unit
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
Application number
CN202211075039.0A
Other languages
Chinese (zh)
Inventor
王江
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xunmu Information Technology Shanghai Co Ltd
Original Assignee
Xunmu Information Technology Shanghai Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Xunmu Information Technology Shanghai Co Ltd filed Critical Xunmu Information Technology Shanghai Co Ltd
Priority to CN202211075039.0A priority Critical patent/CN115437658A/en
Publication of CN115437658A publication Critical patent/CN115437658A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • G06F8/63Image based installation; Cloning; Build to order
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • G06F13/38Information transfer, e.g. on bus
    • G06F13/40Bus structure
    • G06F13/4063Device-to-bus coupling
    • G06F13/4068Electrical coupling
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Stored Programmes (AREA)

Abstract

The application discloses a firmware maintenance method and a system thereof. The firmware maintenance method comprises the following steps: establish through bus interface and plug-in card and be connected, wherein, the plug-in card includes: the logic device comprises a selector and a memory control module which are connected, and the selector selectively connects the memory with the processing unit or the memory control module; setting the memory control module to cause the selector to connect the memory to the memory control module; after the memory is connected with the memory control module, the memory control module is accessed to burn the new firmware into the memory; after burning the new firmware into the memory, setting a memory control module to enable the selector to connect the memory to the processing unit; after the memory is connected with the processing unit, the memory control module is arranged to trigger the processing unit to reload the new firmware.

Description

Firmware maintenance method and system
Technical Field
The present application relates to the field of computer technologies, and in particular, to a firmware maintenance method and system.
Background
With the development of industries such as artificial intelligence, image recognition, social software, block chaining and the like, various card insertion layers are in endless, for example: peripheral Component Interconnect Express (PCIe) cards. PCIe cards typically contain devices such as a special purpose processor, a network processor, or a Field Programmable Gate Array (FPGA), which rely on their firmware for boot-up, which is typically stored in external memory.
Firmware sometimes needs to be maintained due to the defect repair, the functional characteristic increase and the like, and generally, firmware maintenance of the PCIe plug-in card needs to be implemented by controlling a processor or an FPGA on the PCIe plug-in card through a PCIe channel by using an electronic device where the firmware is located.
However, in the firmware maintenance process, if abnormal conditions occur to cause firmware maintenance interruption, firmware maintenance failure or firmware damage, the PCIe card cannot work due to incomplete firmware, the electronic device cannot communicate with the PCIe card, and even cannot be repaired online, so that an engineer must open a server chassis and burn the complete firmware into a memory by using tools such as a programmer on site, and thus, the existing firmware maintenance method has the problems of poor maintainability, incapability of remote repair, high maintenance cost and increased downtime of the electronic device.
Therefore, how to provide a solution to the above technical problems is a problem to be solved by those skilled in the art.
Disclosure of Invention
The embodiment of the application provides a firmware maintenance method and a firmware maintenance system, which can solve the problems of poor maintainability, incapability of remote repair, high maintenance cost and increased downtime of an electronic device in the conventional firmware maintenance method.
In order to solve the technical problem, the present application is implemented as follows:
the application provides a firmware maintenance method, which comprises the following steps: establish through bus interface and plug-in card and be connected, wherein, the plug-in card includes: the logic device comprises a selector and a memory control module which are connected with each other, the selector selectively connects the memory with the processing unit or the memory control module, and the memory control module is connected with the processing unit; setting the memory control module to cause the selector to select to connect the memory to the memory control module; after the memory is connected to the memory control module, accessing the memory control module to burn the new firmware into the memory through the memory control module; after burning the new firmware into the memory, setting a memory control module to enable the selector to select to connect the memory to the processing unit; and after the memory is connected to the processing unit, setting the memory control module to trigger the processing unit to reload the new firmware in the memory.
The application provides a firmware maintenance system, which comprises: a card and an electronic device. The card insertion includes: the logic device comprises a selector and a memory control module which are connected with each other, the selector selectively connects the memory with the processing unit or the memory control module, and the memory control module is connected with the processing unit. The electronic device includes: the control unit is connected with the bus interface, and the bus interface is connected with the plug-in card; the control unit is configured to set the memory control module to cause the selector to select the memory to be connected to the memory control module; then, accessing the memory control module to burn the new firmware into the memory through the memory control module; then, setting a memory control module to cause the selector to select to connect the memory to the processing unit; thereafter, the memory control module is set to trigger the processing unit to reload the new firmware in the memory.
In the embodiment of the present application, a logic device is added to the plug-in card, and a bus interface on the plug-in card is fully utilized, so that the electronic device sets or accesses a memory control module of the logic device through the bus interface to program a memory on the plug-in card (i.e., to burn a new firmware into the memory). In the firmware maintenance process, the processing unit on the plug-in card is not needed, so that the electronic device can still maintain the firmware of the plug-in card under the condition that the processing unit on the plug-in card cannot work normally, the problems of poor maintainability, incapability of remote repair, high maintenance cost and increased downtime of the electronic device in the conventional firmware maintenance method can be solved, and the firmware maintenance method has the advantages of high reliability and convenience in maintenance.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a block diagram of one embodiment of a firmware maintenance system according to the present application;
FIG. 2 is a block diagram of another embodiment of a firmware maintenance system according to the present application;
FIG. 3 is a flowchart of an embodiment of a firmware maintenance method according to the present application; and
FIG. 4 is a flowchart of another embodiment of a firmware maintenance method according to the present application.
Detailed Description
Embodiments of the present invention will be described below with reference to the accompanying drawings. In the drawings, the same reference numerals indicate the same or similar components or process flows.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, and/or components, but do not preclude the presence or addition of further features, integers, steps, operations, components, and/or groups thereof.
It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may be present. In contrast, when an element is described as being "directly connected" or "directly coupled" to another element, there are no intervening elements present.
Please refer to fig. 1, which is a block diagram illustrating a firmware maintenance system according to an embodiment of the present application. As shown in fig. 1, the firmware maintenance system 100 includes: plug-in card 110 and electronic device 120, plug-in card 110 includes: the processing unit 112, the logic device 114 and the memory 116, the logic device 114 includes a selector 50 and a memory control module 60 which are connected with each other, the selector 50 selectively connects the memory 116 with the processing unit 112 or the memory control module 60, and the memory control module 60 is connected with the processing unit 112; the electronic device 120 includes a motherboard (main) 122, and the main board 122 includes: the bus interface 70 and the control unit 80 are connected, and the control unit 80 is connected to the bus interface 70.
Wherein, the insertion card 110 can be but not limited toLimited to smart card, graphics Processing Unit (GPU) card or dsp card, the Processing Unit 112 may be, but is not limited to, a processor or a field programmable logic array, the memory 116 may be, but is not limited to, a flash memory (SPI) with Serial Peripheral Interface (SPI) or an Integrated Circuit bus (I) 2 C) The interface may be an electrically-erasable programmable read-only memory (EEPROM), and the control Unit 80 may be, but not limited to, a Baseboard Management Controller (BMC) or a Central Processing Unit (CPU). In some embodiments, add-in card 110 may be, but is not limited to, a peripheral component interconnect express (PCIe) add-in card having a standard PCIe add-in slot interface; the motherboard 122 has a standard peripheral component fast interconnection slot, so that plug-in cards 110 developed by different manufacturers can be inserted into peripheral component fast interconnection slots of different motherboards 122; the electronic device 120 may be, but is not limited to, a server or a personal computer.
In this embodiment, the memory 116 is a flash memory having a serial peripheral interface, and the processing unit 112 and the memory control module 60 also have a serial peripheral interface, so that the selector 50 can selectively connect the serial peripheral interface of the memory 116 with the serial peripheral interface of the processing unit 112 or the serial peripheral interface of the memory control module 60. In another embodiment, the memory 116 is an electrically erasable programmable read-only memory having an integrated circuit bus interface, and the processing unit 112 and the memory control module 60 also have an integrated circuit bus interface, such that the selector 50 can selectively connect the integrated circuit bus interface of the memory 116 with the integrated circuit bus interface of the processing unit 112 or the integrated circuit bus interface of the memory control module 60.
When the add-in card 110 is inserted into a slot of the motherboard 122, the motherboard 122 of the electronic device 120 establishes a connection with the add-in card 110 through the bus interface 70 (i.e., the bus interface 70 is configured to establish a connection with the add-in card 110); the control unit 80 is configured to set the memory control module 60 such that the selector 50 selects to connect the memory 116 to the memory control module 60; then, accessing the memory control module 60 to burn the new firmware into the memory 116 through the memory control module 60; the memory control module 60 is then arranged to cause the selector 50 to select the connection of the memory 116 to the processing unit 112; memory control module 60 is then set up to trigger processing unit 112 to reload the new firmware in memory 116.
Specifically, the electronic device 120 reads the new firmware from the network or the hard disk via the motherboard 122 (i.e., acquires the new firmware) based on the firmware maintenance requirements of the add-in card 110; next, the control unit 80 of the motherboard 122 sets the memory control module 60 through the bus interface 70, so that the selector 50 selects to connect the serial peripheral interface of the memory 116 to the serial peripheral interface of the memory control module 60; then, the control unit 80 of the motherboard 122 accesses the memory control module 60 through the bus interface 70 to transmit the new firmware to the memory control module 60, so that the new firmware is burned into the memory 116 through the memory control module 60; then, the control unit 80 of the motherboard 122 sets the memory control module 60 through the bus interface 70, so that the selector 50 selects to switch the serial peripheral interface of the memory 116 to the serial peripheral interface of the processing unit 112; finally, the control unit 80 of the motherboard 122 sets the memory control module 60 via the bus interface 70, so that the memory control module 60 triggers the processing unit 112 to reload the new firmware in the memory 116.
In one example, for a field programmable logic array, firmware refers to a configuration file of the field programmable logic array, and thus, when the processing unit 112 is a field programmable logic array, the control unit 80 triggers the processing unit 112 to reload new firmware in the memory 116 through the memory control module 60, and the control unit 80 may trigger the field programmable logic array to reload new configuration file in the memory 116 through the memory control module 60 (i.e., the control unit 80 is configured to set the memory control module 60 to trigger the field programmable logic array to reload new firmware in the memory 116).
In another example, for a processor, the firmware is its boot code, and thus, when the processing unit 112 is a processor, the control unit 80 triggers the processing unit 112 to reload the new firmware in the memory 116 through the memory control module 60, and the processor can be restarted for the control unit 80 through the memory control module 60 to reload the new firmware in the memory 116 (i.e., the control unit 80 is configured to set the memory control module 60 to restart the processor to reload the new firmware in the memory 116).
In one embodiment, by default, the selector 50 connects the memory 116 to the processing unit 112.
Please refer to fig. 2, which is a block diagram illustrating a firmware maintenance system according to another embodiment of the present application. As shown in fig. 2, the memory control module 60 includes a control register 62, and the control unit 80 is configured to set the control register 62 to control the selection of the selector 50 (i.e., to control the selector 50 to connect the memory 116 to the processing unit 112 or the memory control module 60) or to trigger a restart signal or a reload signal to the processing unit 112 (i.e., to restart the processor or to trigger the field programmable logic array to reload new firmware in the memory 116).
In one embodiment, the Bus interface 70 is a System Management Bus (SMB) interface, the logic device 114 is a complex programmable logic device, and the logic device 114 may further include: the memory control module 60 may include a system management bus controller 90 connected to a system management bus interface (i.e., the bus interface 70): memory controller 64, command register 66, and data register 68; control unit 80 is configured to read and write command register 66 and data register 68 through system management bus controller 90 to cause memory controller 64 to access memory 116 through command register 66 and data register 68 and to burn the new firmware into memory 116. Specifically, the memory controller 64 is configured to send write commands to the memory 116 through the command register 66; and sends the data of the new firmware to memory 116 through data register 68.
In addition, the command register 66 may also be used to store commands that the memory controller 64 sends to the memory 116, such as: read commands, write commands, erase commands, etc.; the data register 68 may also be used to store data associated with the commands stored by the command register 66 and to store data returned by the memory controller 64 after the commands have been executed.
In one example, where the memory 116 is a flash memory, the memory controller is a serial peripheral interface controller. In another example, where the memory 116 is an electrically erasable programmable read only memory, the memory controller is an integrated circuit bus controller.
In one embodiment, bus interface 70 is a system management bus interface, and plug-in card 110 is a peripheral component interconnect express plug-in card; when the card 110 cannot normally operate, the system management bus interface (i.e., the bus interface 70) is further configured to establish a connection with a peripheral component fast interconnect card (i.e., the card 110) that cannot normally operate, and the control unit 80 is further configured to set the memory control module 60 of the peripheral component fast interconnect card (i.e., the plug-in card 110) that cannot normally operate, so that the selector 50 selects to connect the memory 116 to the memory control module 60; then, the memory control module 60 is accessed to read back the current firmware stored in the memory 116 through the memory control module 60 and stored in a file on an external memory, which may be but is not limited to, the disk 10 of the electronic device 120; it is then determined whether the current firmware stored by the memory 116 is corrupted based on the read back file stored by the external memory. In some embodiments, the disk 10 may be, but is not limited to, other non-disk type memory, such as a solid state disk. In some embodiments, the electronic device 120 may be, but is not limited to, a server or a personal computer, and the disk 10 may be, but is not limited to, a disk installed in the server or the personal computer.
Specifically, after a failed peripheral component fast interconnect plug-in card (i.e., the plug-in card 110 which cannot normally operate) returned in the production process or operation is inserted into a peripheral component fast interconnect slot of the motherboard 122, the motherboard 122 establishes a connection with the plug-in card 110 which cannot normally operate through a system management bus interface (i.e., the bus interface 70); next, the control unit 80 sets the memory control module 60 of the add-in card 110 that cannot normally operate through the system management bus interface (i.e., the bus interface 70), so that the selector 50 selects to connect the memory 116 to the memory control module 60; then, the control unit 80 accesses the memory control module 60 through the system management bus interface 70 to read back the current firmware stored in the memory 116 and store the current firmware in a file form on the disk 10 of the electronic device 120; then, the control unit 80 compares whether the read file is consistent with the correct file (i.e. the file corresponding to the complete current firmware), and if so, determines that the current firmware stored in the memory 116 is intact, and the reason why the add-in card 110 cannot work normally is elsewhere; otherwise, it is determined that the current firmware stored in the memory 116 is corrupted. Thus, firmware maintenance system 100 can aid in fault location for a failed add-in card 110 that returns during production or during operation.
In one embodiment, the bus interface 70 is a system management bus interface, the logic device 114 is a complex programmable logic device, and the logic device 114 may further include: a system management bus controller 90 connected to the system management bus interface (i.e. bus interface 70), the memory control module 60 may include: memory controller 64, command register 66, and data register 68; the control unit 80 is configured to read and write the command register 66 and the data register 68 through the system management bus controller 90, to cause the memory controller 64 to access the memory 116 through the command register 66 and the data register 68, and to read back the current firmware stored by the memory 116. In particular, the memory controller 64 is configured to send read commands to the memory 116 through the command register 66; and the data of the current firmware stored by memory 116 is read back to memory 116 through data register 68.
In an embodiment, the control unit 80 is further configured to, when determining that the current firmware stored in the memory 116 is damaged, access the memory control module 60 to burn, into the memory 116, lossless firmware corresponding to the current firmware through the memory control module 60. Thus, if add-in card 110 fails due to firmware corruption, firmware maintenance system 100 can facilitate easy repair without the use of additional tools such as a burner.
In one embodiment, the bus interface 70 is a system management bus interface, the logic device 114 is a complex programmable logic device, and the logic device 114 may further include: the memory control module 60 may include a system management bus controller 90 connected to a system management bus interface (i.e., the bus interface 70): memory controller 64, command register 66, and data register 68; the control unit 80 is configured to read and write the command register 66 and the data register 68 through the system management bus controller 90, so that the memory controller 64 accesses the memory 116 through the command register 66 and the data register 68, and burns the complete and correct current firmware (i.e., the lossless firmware corresponding to the current firmware) into the memory 116.
Please refer to fig. 3, which is a flowchart illustrating a firmware maintenance method according to an embodiment of the present application. As shown in fig. 3, the firmware maintenance method is applied to an electronic device, and includes: establish through bus interface and plug-in card and be connected, wherein, the plug-in card includes: the method comprises the following steps that a processing unit, a logic device and a memory are arranged, wherein the logic device comprises a selector and a memory control module which are connected with each other, the selector selectively connects the memory with the processing unit or the memory control module, and the memory control module is connected with the processing unit (step 310); setting a memory control module to cause a selector to select to connect the memory to the memory control module (step 320); after the memory is connected to the memory control module, accessing the memory control module to burn the new firmware into the memory through the memory control module (step 330); after burning the new firmware into the memory, setting a memory control module to make the selector select to connect the memory to the processing unit (step 340); and after connecting the memory to the processing unit, setting the memory control module to trigger the processing unit to reload the new firmware in the memory (step 350).
Therefore, the electronic device sets or accesses the memory control module of the logic device additionally arranged on the plug-in card through the bus interface so as to burn the new firmware into the memory on the plug-in card and trigger the processing unit on the plug-in card to reload the new firmware in the memory, thereby solving the problems of poor maintainability, incapability of remote repair, high maintenance cost and increased downtime of the electronic device in the case of firmware maintenance failure of the conventional firmware maintenance method. For a detailed description, reference may be made to the related description of the above embodiments, which is not repeated herein.
In an embodiment, the memory control module may include a control register; the setting the memory control module in steps 320 and 340 may include: the control register is provided to control the selection of the selector. In other words, the selector may connect the memory to the processing unit or the memory control module based on the data of the control register. For detailed description, reference may be made to the related description of the above embodiments, which are not repeated herein.
In one embodiment, the bus interface may be a system management bus interface, the logic device may be a complex programmable logic device, and the logic device may further include: the system management bus controller is connected with the system management bus interface, and the memory control module can comprise: the memory controller, the command register and the data register, wherein the memory controller is connected to the command register and the data register, and therefore, the accessing the memory control module to burn the new firmware into the memory through the memory control module in step 330 may include: and reading and writing the command register and the data register through the system management bus controller so that the memory controller accesses the memory through the command register and the data register and burns the new firmware into the memory. Specifically, the memory controller sends a write command to the memory through the command register and sends data of the new firmware to the memory through the data register, and therefore, the memory controller burns the new firmware into the memory through the command register and the data register. For a detailed description, reference may be made to the related description of the above embodiments, which is not repeated herein.
In an embodiment, the memory control module may include a control register; the setting the memory control module of step 350 may include: the control register is set to trigger a restart signal or a reload signal to the processing unit.
In one embodiment, the processing unit may be a processor or a field programmable logic array, and triggering the processing unit to reload the new firmware in the memory in step 350 may include: restarting the processor to reload the new firmware in the memory; or to trigger the field programmable logic array to reload the new firmware in the memory. For detailed description, reference may be made to the related description of the above embodiments, which are not repeated herein.
Please refer to fig. 4, which is a flowchart illustrating a firmware maintenance method according to another embodiment of the present application. In this embodiment, the bus interface is a system management bus interface, the plug-in card is a peripheral component interconnect express plug-in card, and the firmware maintenance method may further include, in addition to steps 310 to 350: establishing connection with the peripheral component fast interconnected plug-in card incapable of working normally through a system management bus interface, and setting a memory control module to enable a selector to select to connect the memory to the memory control module (step 410); after the memory is connected to the memory control module, accessing the memory control module to read back the current firmware stored in the memory through the memory control module and store the current firmware in the external memory in the form of a file (step 420); a determination is made as to whether the current firmware stored by the memory is corrupted based on the read back file stored by the external memory (step 430). Therefore, the efficacy of fault location can be achieved. For a detailed description, reference may be made to the related description of the above embodiments, which is not repeated herein. It should be noted that the drawing steps 310 to 350 are omitted to avoid overcomplicating the drawing of fig. 4.
In an embodiment, the firmware maintenance method may further include: when the current firmware stored in the memory is determined to be damaged, the memory control module is accessed to burn the lossless firmware corresponding to the current firmware into the memory through the memory control module (step 440). Therefore, the effect of conveniently repairing the firmware can be realized. For a detailed description, reference may be made to the related description of the above embodiments, which is not repeated herein.
It should be noted that, if there is no causal relationship between the above steps, the present application does not limit the execution sequence.
In summary, in the firmware maintenance method and system of the present application, the logic device is added to the plug-in card, and the bus interface on the plug-in card is fully utilized, so that the electronic device sets or accesses the memory control module of the logic device through the bus interface to program the memory on the plug-in card (i.e. burn the new firmware into the memory). In the firmware maintenance process, the processing unit on the plug-in card is not needed, so that the electronic device can still maintain the firmware on the plug-in card under the condition that the processing unit on the plug-in card cannot work normally, the problems of poor maintainability, incapability of remote repair, high maintenance cost and increased downtime of the electronic device in the case of firmware maintenance failure in the conventional firmware maintenance method can be solved, and the firmware maintenance method has the advantages of high reliability and convenience in maintenance.
In addition, for the plug-in card with a fault returned in the production process or the operation process, the firmware maintenance method and the system thereof can help to locate the fault. In addition, if the card insertion fails due to firmware damage, the firmware maintenance method and the system thereof can help repair conveniently without using additional tools such as a burner and the like.
While the invention has been described using the above embodiments, it should be noted that these descriptions are not intended to limit the invention. Rather, this invention encompasses modifications and similar arrangements as would be apparent to one skilled in the art. The scope of the claims is, therefore, to be construed in the broadest possible manner to cover all such modifications and similar arrangements.

Claims (16)

1. A firmware maintenance method, comprising:
establish a connection with a plug-in card through a bus interface, wherein the plug-in card includes: the logic device comprises a selector and a memory control module which are connected with each other, the selector selectively connects the memory with the processing unit or the memory control module, and the memory control module is connected with the processing unit;
setting the memory control module to cause the selector to select to connect the memory to the memory control module;
after the memory is connected to the memory control module, accessing the memory control module to burn new firmware into the memory through the memory control module;
after burning the new firmware into the memory, setting the memory control module to enable the selector to select to connect the memory to the processing unit; and
after the memory is connected to the processing unit, the memory control module is configured to trigger the processing unit to reload the new firmware in the memory.
2. The firmware maintenance method of claim 1, wherein the bus interface is a system management bus interface, and the plug-in card is a peripheral component interconnect express (PCI) plug-in card, the firmware maintenance method further comprising:
establishing connection with the peripheral component fast interconnect card which can not work normally through the system management bus interface, and setting the memory control module to enable the selector to select to connect the memory to the memory control module;
after the memory is connected to the memory control module, accessing the memory control module to read back the current firmware stored by the memory through the memory control module and store the current firmware on an external memory in a file form; and
determining whether the current firmware stored by the memory is corrupted based on the read back file stored by the external memory.
3. The firmware maintenance method of claim 2, further comprising:
and when the current firmware stored in the memory is judged to be damaged, accessing the memory control module to burn the lossless firmware corresponding to the current firmware into the memory through the memory control module.
4. The firmware maintenance method of claim 1, wherein the memory control module comprises a control register; the step of setting the memory control module includes:
and setting the control register to control the selection of the selector or trigger a restart signal or a reload signal to the processing unit.
5. The firmware maintenance method of claim 1, wherein the bus interface is a system management bus interface, the logic device is a complex programmable logic device, and the logic device further comprises: a system management bus controller connected to the system management bus interface, the memory control module comprising: the memory controller is connected with the command register and the data register; the step of accessing the memory control module to burn new firmware into the memory through the memory control module comprises:
and reading and writing the command register and the data register through the system management bus controller so that the memory controller accesses the memory through the command register and the data register and burns the new firmware into the memory.
6. The firmware maintenance method of claim 5, wherein the memory controller accesses the memory through the command register and the data register, and the step of burning the new firmware into the memory comprises:
the memory controller sending a write command to the memory through the command register; and
the memory controller sends the data of the new firmware to the memory through the data register.
7. The firmware maintenance method of claim 1, wherein the processing unit is a processor or a field programmable logic array, and the step of triggering the processing unit to reload the new firmware in the memory comprises:
rebooting the processor to reload the new firmware in the memory; or
Triggering the field programmable logic array to reload the new firmware in the memory.
8. A firmware maintenance system, comprising:
a paddle card, comprising: the logic device comprises a selector and a memory control module which are connected with each other, the selector selectively connects the memory with the processing unit or the memory control module, and the memory control module is connected with the processing unit; and
an electronic device, comprising:
a bus interface configured to establish a connection with the add-in card; and
a control unit connected to the bus interface and configured to set the memory control module so that the selector selects the memory to be connected to the memory control module; then, accessing the memory control module to burn new firmware into the memory through the memory control module; then, setting the memory control module to cause the selector to select to connect the memory to the processing unit; thereafter, the memory control module is configured to trigger the processing unit to reload the new firmware in the memory.
9. The firmware maintenance system of claim 8, wherein the bus interface is a system management bus interface, the plug-in card is a peripheral component interconnect express (PCI express) plug-in card, the system management bus interface further configured to establish a connection with the PCI express plug-in card that is not functioning properly; the control unit is further configured to set the memory control module of the peripheral component interconnect express card that is not normally operable to cause the selector to select the memory to be connected to the memory control module; then, accessing the memory control module to read back the current firmware stored by the memory through the memory control module and store the current firmware in a file form on an external memory; then, it is determined whether the current firmware stored by the memory is corrupted based on the read back file stored by the external memory.
10. The firmware maintenance system of claim 9, wherein the control unit is further configured to access the memory control module to burn, by the memory control module, the lossless firmware corresponding to the current firmware into the memory when determining that the current firmware stored in the memory is corrupted.
11. A firmware maintenance system as in claim 9, wherein the memory is a flash memory or an eeprom, the memory control module comprises a memory controller that is a serial peripheral interface controller or an ic bus controller, and the external memory is a disk or a solid state disk of a server or a personal computer.
12. The firmware maintenance system of claim 8, wherein the memory control module includes a control register, the control unit configured to set the control register to control selection of the selector or to trigger a restart signal or a reload signal to the processing unit.
13. The firmware maintenance system of claim 8, wherein the bus interface is a system management bus interface, the logic device is a complex programmable logic device, the logic device further comprising: a system management bus controller connected to the system management bus interface, the memory control module comprising: a memory controller, a command register and a data register; the control unit is configured to read and write the command register and the data register through the system management bus controller, so that the memory controller accesses the memory through the command register and the data register and burns the new firmware into the memory.
14. The firmware maintenance system of claim 13, wherein the memory controller is configured to send a write command to the memory through the command register; and sending data of the new firmware to the memory through the data register.
15. A firmware maintenance system as claimed in claim 8, wherein the processing unit is a processor or a field programmable logic array; the control unit is configured to set the memory control module to restart the processor or trigger the field programmable logic array to reload the new firmware in the memory.
16. A firmware maintenance system as claimed in claim 8, wherein the selector connects the memory to the processing unit by default.
CN202211075039.0A 2022-09-02 2022-09-02 Firmware maintenance method and system Pending CN115437658A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211075039.0A CN115437658A (en) 2022-09-02 2022-09-02 Firmware maintenance method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211075039.0A CN115437658A (en) 2022-09-02 2022-09-02 Firmware maintenance method and system

Publications (1)

Publication Number Publication Date
CN115437658A true CN115437658A (en) 2022-12-06

Family

ID=84247718

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211075039.0A Pending CN115437658A (en) 2022-09-02 2022-09-02 Firmware maintenance method and system

Country Status (1)

Country Link
CN (1) CN115437658A (en)

Similar Documents

Publication Publication Date Title
US20110093741A1 (en) Method for recovering bios and computer system thereof
CN102339242A (en) Computer system data recovery device
US20120303940A1 (en) System, method and program product to manage firmware on a system board
US20140047224A1 (en) Method of flashing bios using service processor and computer system using the same
CN110928499A (en) Flash memory embedded in chip, chip and starting method of chip
CN110377296B (en) System and method for supporting Flash burning of server main control board
US10824517B2 (en) Backup and recovery of configuration files in management device
CN103761198A (en) Memory chip and data protection method
CN106909382B (en) Method and device for outputting different types of system starting information
CN115437658A (en) Firmware maintenance method and system
WO2022199622A1 (en) Method for running startup program of electronic device, and electronic device
CN113377425B (en) BMC firmware generation method and device, BMC starting method and device and storage medium
US11586504B2 (en) Electronic apparatus and boot method thereof
CN111459730A (en) PCH (physical channel) end parameter adjusting method and system under Whitley platform
CN112667444A (en) System upgrading method, storage medium and terminal equipment
TWI417888B (en) An embedded chip system, a method for burning a wafer, and a computer program product
CN110888766A (en) Chip starting method
CN117931246B (en) Method and device for upgrading EC firmware, electronic equipment and storage medium
TWI764342B (en) Startup status detection system and method thereof
CN113867812B (en) Method, system, equipment and medium for BMC to acquire link information
CN113703816B (en) Server device and method for avoiding firmware from being unable to be updated again
CN213211012U (en) Online upgrading device of laser radar system and laser radar system
TWI768198B (en) Microcontroller, memory module, and method for updating firmware of the microcontroller
US20240036854A1 (en) Method and device of updating and testing multiple embedded controllers
CN118093240A (en) Hard disk fault processing method, device, computer equipment, storage medium and program product

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