Firmware upgrading method and system, electronic device and storage medium

Abstract

This application relates to the field of firmware upgrade technology, and particularly to firmware upgrade methods, systems, electronic devices, and storage media. The firmware upgrade method includes: responding to an upgrade start command from a lower-level device, coupling the lower-level device with a host computer to enter upgrade mode; and having the host computer perform a firmware upgrade on at least one of the firmware objects to be upgraded, based on the firmware package to be upgraded, by reusing the pathways between different types of firmware objects to be upgraded in the lower-level device. This allows the lower-level device to upgrade all different types of firmware objects to be upgraded in the lower-level device by connecting to the host computer through only one external interface, effectively saving hardware costs. Furthermore, if the lower-level device needs to be fixed to a machine, it can perform the above steps without disassembly.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of firmware upgrade, in particular to a firmware upgrade method and system, an electronic device and a storage medium. BACKGROUND

[0002] SLT is the abbreviation of System Level Test, and the test process is roughly as follows: the chip is pressed into the chip socket on the SLT test board by the sorting machine, the test mainboard powers on the test subboard to run the system level test case, and then the sorting machine is notified to classify the chip according to the test result. Since the SLT test board needs to be fixed on the sorting machine, it brings difficulties to the firmware upgrade of the SLT test board. For the firmware upgrade of the SLT test board, there are currently the following solutions:

[0003] 1. Disassemble the SLT test board, connect the computer, and use a special program to upgrade the firmware. Disadvantages: time-consuming, factory line installation and disassembly of the test board are the work of engineering personnel, and firmware upgrade is the work of test personnel, which wastes coordination and waiting time, and the test board needs to be tested again after reinstallation.

[0004] 2. Leave an external upgrade interface on the SLT test board, and the SLT test board can at least test two chips at the same time. According to the case of one test mainboard and two test subboards, three external upgrade interfaces are needed, and if four chips are tested at the same time, more upgrade interfaces are needed. Disadvantages: due to multiple upgrade connections, connection errors are prone to occur during operation, increasing the difficulty of operation for the operator, and the hardware cost is also increased.

[0005] 3. Insert a special format upgrade U disk or SD card. Disadvantages: the test mainboard needs to implement additional upgrade code, and an external screen or speaker is needed for result feedback before upgrading, and firmware update needs to be re-made. SUMMARY

[0006] The present application provides a firmware upgrade method, system, electronic device and storage medium, which can complete firmware upgrade of all modules on the slave machine without disassembling the slave machine fixed in a certain position of other machines, and further, only one upgrade interface and upgrade button need to be added, effectively solving the hardware cost.

[0007] In a first aspect, a firmware upgrade method is provided. The method comprises: in response to an upgrade start instruction of a slave machine, coupling the slave machine with a master machine to enter an upgrade mode; and based on a to-be-upgraded firmware package, upgrading firmware of at least one of different types of to-be-upgraded firmware objects in the slave machine by multiplexing paths between the to-be-upgraded firmware objects.

[0008] In some embodiments, the firmware upgrade of the at least one of the firmware objects to be upgraded based on the firmware package to be upgraded comprises: firmware upgrade of at least one of the mainboard, the daughterboard and the auxiliary module.

[0009] In some embodiments, the firmware package to be upgraded is packaged into a complete firmware package, and comprises: mainboard firmware, daughterboard firmware, auxiliary module firmware, daughterboard upgrade program, auxiliary module upgrade program and firmware description file.

[0010] In some embodiments, the firmware upgrade of the at least one of the firmware objects to be upgraded based on the firmware package to be upgraded comprises: transmitting the auxiliary module upgrade program or the daughterboard upgrade program to achieve firmware upgrade of the auxiliary module or the daughterboard decoupled from the mainboard firmware.

[0011] In some embodiments, the firmware upgrade of at least one of the mainboard, the daughterboard and the auxiliary module comprises: if the mainboard is selected to be upgraded, firmware programming of the mainboard in the upgrade mode; after the firmware programming of the mainboard succeeds, restarting to enter the firmware program of the mainboard, and multiplexing the access between the mainboard and the daughterboard and the auxiliary module to perform firmware upgrade of other objects; and if the mainboard is not selected to be upgraded, restarting to enter the firmware program of the mainboard, and multiplexing the access between the mainboard and the daughterboard and the auxiliary module to perform firmware upgrade of other objects.

[0012] In some embodiments, the multiplexing of the access between the mainboard and the daughterboard and the auxiliary module to perform firmware upgrade of other objects comprises: if the auxiliary module is selected to be upgraded, sending auxiliary module upgrade program from the upper computer to the lower computer to perform firmware programming of the auxiliary module; after the firmware programming of the auxiliary module succeeds, if the daughterboard is selected to be upgraded, sending daughterboard upgrade program from the upper computer to the lower computer to perform firmware programming of the daughterboard; and if the auxiliary module is not selected to be upgraded, and if the daughterboard is selected to be upgraded, sending daughterboard upgrade program from the upper computer to the lower computer to perform firmware programming of the daughterboard.

[0013] In some embodiments, the firmware programming of the mainboard comprises: reading the device type of the mainboard, checking whether the device type of the mainboard matches the mainboard device type in the firmware package to be upgraded; if not matching, prompting an error and exiting firmware programming; if matching, reading the current firmware version, checking whether the current firmware version is consistent with the version in the firmware package to be upgraded; and if not consistent, starting firmware programming of the mainboard.

[0014] In some embodiments, the firmware burning of the auxiliary module comprises: reading a device type of the auxiliary module, checking whether the device type of the auxiliary module matches a device type of the auxiliary module in the firmware package to be upgraded, prompting an error and exiting the firmware burning if not matching, reading a current firmware version if matching, checking whether the current firmware version is consistent with a version in the firmware package to be upgraded, and starting the firmware burning of the auxiliary module if not consistent.

[0015] In some embodiments, the method further comprises: performing an integrity check on the firmware package to be upgraded by the host computer; and obtaining an upgrade instruction according to the result of the integrity check, wherein the firmware upgrade of at least one of the objects to be upgraded based on the firmware package to be upgraded comprises: performing the firmware upgrade of part of the objects or all of the objects according to the upgrade instruction.

[0016] In some embodiments, the coupling of the lower computer to the host computer to enter the upgrade mode comprises: connecting the host computer to the lower computer through only one external interface.

[0017] In some embodiments, the lower computer is provided with an upgrade button, and the response to the upgrade start instruction of the lower computer comprises: responding to the start instruction through the upgrade button.

[0018] In the second aspect, a firmware upgrade system is provided. The system comprises a host computer and a lower computer, the lower computer is coupled to the host computer through only one external interface, and the host computer upgrades the lower computer through the firmware upgrade method mentioned above.

[0019] In some embodiments, the host computer comprises a computer, and the lower computer comprises a system-level test board.

[0020] In the third aspect, an electronic device is provided. The electronic device comprises: a memory configured to store a computer program; and a processor configured to invoke the computer program to execute the firmware upgrade method mentioned above.

[0021] In the fourth aspect, a computer readable storage medium is provided. The computer readable storage medium stores program instructions, which are executed to implement the firmware upgrade method mentioned above.

[0022] According to the embodiment of the present application, in response to the upgrade starting instruction of the lower machine, the lower machine is coupled with the upper machine to enter the upgrade mode; and the upper machine upgrades at least one of the firmware objects to be upgraded based on the firmware package to be upgraded by multiplexing the paths among different types of firmware objects to be upgraded in the lower machine. In this way, the lower machine only needs to be connected with the upper machine through one external interface, and the upgrade of all different types of firmware objects to be upgraded in the lower machine can be realized, thereby effectively saving the hardware cost. If the lower machine needs to be fixed on a certain machine, the above steps can be performed without disassembly.

[0023] The above summary of the application is only a summary of the technical solutions of the present application. In order to enable those skilled in the art to more clearly understand the technical solutions of the present application, and then can be implemented according to the content of the description and the drawings, and in order to enable the above and other purposes, characteristics and advantages of the present application to be more easily understood, the following will be described in combination with the specific embodiments of the present application and the accompanying drawings. BRIEF DESCRIPTION OF DRAWINGS

[0024] The accompanying drawings are only used to show the principles, implementation manners, applications, characteristics and effects of the specific embodiments of the present application and other related contents, and cannot be considered as limitations of the present application.

[0025] Figure 1 is a flow chart showing a firmware upgrade method according to an embodiment of the present disclosure;

[0026] Figure 2 is a mainboard upgrade flowchart according to an embodiment of the present disclosure;

[0027] Figure 3 is an auxiliary module upgrade flowchart according to an embodiment of the present disclosure;

[0028] Figure 4 is a subboard upgrade flowchart according to an embodiment of the present disclosure;

[0029] Figure 5 is an example of a meta description file in a firmware package according to an embodiment of the present disclosure;

[0030] Figure 6 is a firmware loading flowchart according to an embodiment of the present disclosure;

[0031] Figure 7 is a module diagram of a firmware upgrade system according to an embodiment of the present disclosure;

[0032] Figure 8 is a schematic diagram of a firmware upgrade system according to an embodiment of the present disclosure;

[0033] Figure 9 is a module schematic diagram illustrating an electronic device according to an embodiment of the disclosure. DETAILED DESCRIPTION

[0034] To make the possible application scenarios, technical principles, specific schemes that can be implemented, purposes and effects achieved, etc. of the present application clear, the following will be described in detail in combination with the specific embodiments listed and the accompanying drawings. The embodiments described herein are only used to more clearly illustrate the technical schemes of the present application, and therefore only serve as examples, but cannot limit the protection scope of the present application.

[0035] In this article, the term "embodiment" means that the specific features, structures or characteristics described in combination with the embodiment can be included in at least one embodiment of the present application. The term "embodiment" appearing at various positions in the specification does not necessarily refer to the same embodiment, and does not particularly limit the independence or association between other embodiments. In principle, in the present application, as long as there is no technical contradiction or conflict, each technical feature mentioned in each embodiment can be combined in any way to form a corresponding implementable technical scheme.

[0036] Unless otherwise defined, the meanings of the technical terms used herein are the same as those commonly understood by those skilled in the art to which the present application belongs; the use of related terms in this article is only for the purpose of describing specific embodiments, and is not intended to limit the present application.

[0037] In the description of the present application, the phrase "and / or" is a description of the logical relationship between the objects, which means that there can be three relationships, for example, A and / or B, which means that there are three cases: A exists, B exists, and A and B exist at the same time. In addition, the character " / " in this article generally represents that the associated objects before and after are a "or" logical relationship.

[0038] In the present application, the phrases such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual quantity, primary and secondary or order relationship between the entities or operations.

[0039] In the present application, without more limitation, the phrase "including", "containing", "having" or other similar expressions used in the statement means to cover non-exclusive inclusion, and these expressions do not exclude the presence of other elements in the process, method or product including the described elements, so that the process, method or product including a series of elements can not only include those limited elements, but also include other elements not explicitly listed, or also include the elements inherent to such process, method or product.

[0040] In the present application, "greater than", "less than", "exceed" and the like are understood as not including the number; "above", "below", "within" and the like are understood as including the number. In addition, in the description of the embodiments of the present application, the meaning of "multiple" is two or more (including two), and similar expressions related to "multiple" are also understood in this way, for example, "multiple groups", "multiple times" and the like, unless otherwise explicitly and specifically limited.

[0041] As mentioned in the background art, the existing several solutions for firmware upgrade on the SLT test board either need to disassemble the SLT test board or need multiple external interfaces, etc. In the present application, only one upgrade port of the SLT test board is needed to interconnect with the computer, and all firmware upgrades on the SLT test board are completed through the upgrade program on the computer. The specific implementation is described as follows:

[0042] Figure 1 is a flowchart showing a firmware upgrade method 100 according to an embodiment of the present disclosure. As shown in Figure 1 , the method 100 includes steps S101 to S102.

[0043] In step S101, in response to an upgrade start instruction of the lower machine, the lower machine is coupled with the upper machine to enter an upgrade mode.

[0044] In the present embodiment, the lower machine is a system-level test board (i.e. SLT test board), and the upper machine is a computer. The lower machine is provided with an upgrade button and an external interface. The lower machine is connected to the upper machine through only one external interface, and the user can power on the system-level test board through the start of the upgrade button, so that the system-level test board enters the upgrade mode. In other embodiments, the lower machine can be any test board containing different types of firmware objects to be upgraded, and / or a test board that needs to be fixed on a certain machine structure when working, and the upper machine can normally send program instructions to the lower machine, etc. In the present embodiment, the lower machine is taken as an example of a system-level test board, and the different types of firmware objects to be upgraded thereof include: mainboard, daughterboard and auxiliary module.

[0045] Therefore, in the present embodiment, the firmware of the mainboard, daughterboard and auxiliary module, the upgrade program of the daughterboard and auxiliary module, and the firmware description file are packaged together into a Zip package as a complete firmware package to be upgraded. The description file records the information of each program (type | version | supported chip | signature digest, etc.). Packaging the programs together can prevent the user from selecting the wrong firmware and prevent firmware from being misburned.

[0046] In some embodiments, after the lower-level machine enters upgrade mode, the upper-level machine performs an integrity check on the firmware package to be upgraded and obtains upgrade instructions based on the integrity check results. The firmware package to be upgraded is packaged into a complete firmware package, including: motherboard firmware, daughterboard firmware, auxiliary module firmware, daughterboard upgrade program, auxiliary module upgrade program, and firmware description file, which can be a ZIP package as described above. The upgrade instructions can be: the user selects a full upgrade, or the user selects a partial upgrade. ZIP compression combined with signature ensures firmware integrity and tamper-proof protection.

[0047] In step S102, the host computer performs a firmware upgrade on at least one of the firmware objects to be upgraded based on the firmware package by reusing the pathways between different types of firmware objects to be upgraded in the slave computer. This mainly involves the host computer performing firmware upgrades on one or more of the different types of firmware objects to be upgraded according to upgrade instructions, such as upgrading at least one of the motherboard, daughterboard, and auxiliary modules. Specifically, this can be achieved by transmitting the upgrade program for the auxiliary module or the upgrade program for the daughterboard, thereby decoupling the firmware upgrade of the auxiliary module or the daughterboard from the motherboard firmware.

[0048] In some embodiments, if the motherboard is selected for upgrade, the firmware of the motherboard is flashed in the upgrade mode; after the firmware of the motherboard is successfully flashed, the firmware program of the motherboard is restarted and the path between the motherboard and the daughterboard and the auxiliary module is reused to perform firmware upgrades of other objects; and if the motherboard is not selected for upgrade, the firmware program of the motherboard is restarted and the path between the motherboard and the daughterboard and the auxiliary module is reused to perform firmware upgrades of other objects.

[0049] In some embodiments, firmware flashing of the motherboard includes: reading the device type of the motherboard, checking whether the device type of the motherboard matches the motherboard device type in the firmware package to be upgraded; if they do not match, prompting an error and exiting firmware flashing; if they match, reading the current firmware version, checking whether the current firmware version is consistent with the version in the firmware package to be upgraded; and if they do not match, starting firmware flashing of the motherboard.

[0050] Figure 2 A schematic diagram of the motherboard upgrade process is shown, such as... Figure 2As shown, after the user selects motherboard upgrade, the system reads the motherboard device type and checks if it matches the motherboard device type in the firmware package to be upgraded. If they do not match, the upgrade fails. If they match, the system reads the current firmware version and checks if it is consistent with the version in the firmware package to be upgraded. If they are consistent, the system indicates that the versions are the same and jumps to the motherboard program restart step. If they are inconsistent, the system starts testing the motherboard firmware flashing and determines if the flashing is successful. If the flashing fails, the upgrade fails. If the flashing is successful, the system restarts the motherboard program restart step, and the host computer transmits the daughterboard and auxiliary module upgrade programs to the test motherboard, entering the auxiliary module upgrade process. If the user does not select motherboard upgrade, the system jumps to the motherboard program restart step. The transmission of the test daughterboard and auxiliary module upgrade programs during the upgrade process decouples them from the test motherboard firmware. Because the original upgrade software programs for the test daughterboard and auxiliary modules were directly placed on the test motherboard, the test motherboard needed to continuously release updates whenever the test daughterboard and auxiliary modules changed. This application places the upgrade software programs for the test daughterboard and auxiliary modules on the host computer for distribution, which directly decouples the upgrade software programs for the test daughterboard and auxiliary modules from the test motherboard firmware. This eliminates the need for continuous updates to the test motherboard firmware.

[0051] In some embodiments, the reusing of the path between the motherboard, the daughterboard, and the auxiliary module for firmware upgrades of other objects includes: if the auxiliary module is selected for upgrade, the host computer sends an auxiliary module upgrade program to the slave computer to flash the firmware of the auxiliary module; after the firmware flashing of the auxiliary module is successful, if the daughterboard is selected for upgrade, the host computer sends a daughterboard upgrade program to the slave computer to flash the firmware of the daughterboard; and if the auxiliary module is not selected for upgrade, and if the daughterboard is selected for upgrade, the host computer sends a daughterboard upgrade program to the slave computer to flash the firmware of the daughterboard.

[0052] In some embodiments, firmware flashing of the auxiliary module includes: reading the device type of the auxiliary module, checking whether the device type of the auxiliary module matches the device type of the auxiliary module in the firmware package to be upgraded; if they do not match, an error is displayed and firmware flashing is exited; if they match, reading the current firmware version, checking whether the current firmware version is consistent with the version in the firmware package to be upgraded; and if they do not match, starting firmware flashing of the auxiliary module. Firmware flashing of the daughterboard includes: reading the device type of the daughterboard, checking whether the device type of the daughterboard matches the device type of the daughterboard in the firmware package to be upgraded; if they do not match, an error is displayed and firmware flashing is exited; if they match, reading the current firmware version, checking whether the current firmware version is consistent with the version in the firmware package to be upgraded; and if they do not match, starting firmware flashing of the daughterboard.

[0053] Figure 3 A schematic diagram of the auxiliary module upgrade process 300 is shown, as follows: Figure 3 As shown, if the user selects to upgrade the auxiliary module, the auxiliary module device type is read, and it is checked whether the auxiliary module device type matches the auxiliary module device type in the firmware package to be upgraded. If they do not match, an upgrade failure message is displayed. If they match, the current firmware version is read, and it is checked whether the current firmware version is consistent with the version in the firmware package to be upgraded. If they are consistent, a message indicating that the versions are the same is displayed, and the process jumps to the daughterboard upgrade process. If they are inconsistent, the auxiliary module firmware flashing begins, and it is determined whether the firmware flashing is successful. If flashing fails, an upgrade failure message is displayed. If flashing is successful, the process jumps to the daughterboard upgrade process. If the user does not select to upgrade the auxiliary module, the process jumps directly to the daughterboard upgrade process.

[0054] Figure 4 A schematic diagram of the daughterboard upgrade process 400 is shown, as follows: Figure 4 As shown, if the user selects daughterboard upgrade, the daughterboard device type is read, and it is checked whether the daughterboard device type matches the daughterboard device type in the firmware package to be upgraded. If they do not match, an upgrade failure message is displayed. If they match, the current firmware version is read, and it is checked whether the current firmware version is consistent with the version in the firmware package to be upgraded. If they are consistent, a message indicating that the versions are the same is displayed, and the process jumps to complete the upgrade. If they are inconsistent, the daughterboard firmware flashing test begins to determine whether the flashing is successful. If it fails, an upgrade failure message is displayed. If it succeeds, a message indicating that the flashing is successful is displayed, and the upgrade is completed.

[0055] According to embodiments of the present invention, firmware upgrades for all modules on the SLT test board can be completed without disassembling the board, while only requiring an additional upgrade interface and button, effectively saving hardware costs. In terms of the upgrade process, it ensures that the SLT test board will not become unusable (in case of upgrade anomalies), preventing operators from selecting the wrong firmware or maliciously modifying the firmware.

[0056] Figure 5 This diagram illustrates an example of a meta description file within the firmware package to be upgraded. Figure 5 The following explains some of the functions and parameters:

[0057] MainProgram: Test motherboard firmware.

[0058] CustomData: Runtime motherboard parameters, which can effectively reduce the frequency of motherboard firmware updates and are passed when entering the motherboard program.

[0059] BoardProgram: Test subboard firmware.

[0060] AidProgram: Auxiliary module firmware.

[0061] BoardTool: Subboard upgrade program.

[0062] AidTool: Auxiliary module upgrade program.

[0063] Signature: The signature of all content in the meta tag, which is verified by the PC upgrade tool when loading the firmware.

[0064] Figure 6 A schematic diagram of the firmware loading process 600 is shown. (For example...) Figure 6 As shown, the firmware is unpacked. If unpacking fails, an invalid firmware message is displayed. If unpacking is successful, meta.json is read. If reading fails, an invalid firmware message is displayed. If reading is successful, the signature is verified. If verification fails, an invalid firmware message is displayed. If verification is successful, the hash is checked. If hash verification fails, an invalid firmware message is displayed. If hash verification is successful, the firmware is loaded successfully and the firmware content is displayed.

[0065] By using the above method 100, the operational difficulty of firmware upgrades for SLT test boards on the factory line can be directly reduced, firmware upgrades for SLT test boards with multiple architectures can be made compatible, firmware mis-burning can be prevented, and the compatibility of motherboard firmware can be improved.

[0066] Figure 7 A schematic diagram of the firmware upgrade system 700 is shown. (As shown) Figure 7 As shown, a firmware upgrade system 700 includes a host computer 701 and a slave computer 702; the slave computer 702 is coupled to the host computer 701 through only one external interface, and the host computer 701 performs firmware upgrade on the slave computer 702 through the aforementioned firmware upgrade method.

[0067] In some embodiments, the host computer 701 includes a computer, and the slave computer 702 includes a system-level test board.

[0068] in Figure 8 This illustration shows one implementation of a firmware upgrade system. The host computer 701 is a computer, and the slave computer 702 is an SLT test board. The slave computer 702 has an upgrade button and an external interface. The slave computer 702 is connected to the host computer 701 only through the external interface. The user enters upgrade mode by pressing the upgrade button to power on the system-level test board. The slave computer 702 contains test boards for different types of firmware objects to be upgraded, including: a motherboard, a daughterboard, and auxiliary modules.

[0069] In practical use, when the user powers on the system-level test board by pressing the upgrade button, the system-level test board enters upgrade mode. After the lower-level computer 702 enters upgrade mode, the upper-level computer 701 performs an integrity check on the firmware package to be upgraded and obtains the upgrade command. The firmware package to be upgraded, as described above, is a ZIP package, and its contents include: motherboard firmware, daughterboard firmware, auxiliary module firmware, daughterboard upgrade program, auxiliary module upgrade program, and firmware description file. The upgrade command can be: the user selects to upgrade all, or the user selects to upgrade part. ZIP compression combined with signature ensures the integrity and tamper-proof nature of the firmware. The upper-level computer 701 performs one or more firmware upgrades of the different types of firmware objects to be upgraded according to the upgrade command.

[0070] The specific steps for upgrading one or more of the different types of firmware objects according to the upgrade instructions have been mentioned in the above firmware upgrade method and will not be repeated here.

[0071] In the firmware upgrade system 700, the lower-level machine 702 only needs to be connected to the upper-level machine 701 through an external interface to upgrade all different types of firmware objects to be upgraded in the lower-level machine 702, effectively saving hardware costs. Moreover, if the lower-level machine 702 needs to be fixed on a certain machine, it can perform firmware upgrades without disassembly.

[0072] Figure 9 A schematic diagram of an electronic device 900 is shown. The electronic device 900 includes: a memory 901 configured to store a computer program; and a processor 902 configured to invoke the computer program to execute the aforementioned firmware upgrade method.

[0073] Another aspect of this disclosure provides a computer-readable storage medium. The computer-readable storage medium stores program instructions that are executed to implement the aforementioned firmware upgrade method.

[0074] Finally, it should be noted that although the above embodiments have been described in the text and drawings of this application, this should not limit the scope of patent protection of this application. Any technical solutions that are based on the essential concept of this application and utilize the content described in the text and drawings of this application, resulting in equivalent structural or procedural substitutions or modifications, as well as the direct or indirect application of the technical solutions of the above embodiments to other related technical fields, are all included within the scope of patent protection of this application.

Claims

1. A firmware upgrade method, characterized in that, include: In response to the upgrade start command from the lower-level machine, the lower-level machine is coupled to the upper-level machine to enter the upgrade mode; as well as The host computer performs firmware upgrades on at least one of the firmware objects to be upgraded based on the firmware package by reusing the pathways between different types of firmware objects to be upgraded in the slave computer. The firmware upgrade based on the firmware package to be upgraded includes upgrading at least one of the following: upgrading the firmware of the motherboard, the daughterboard, and the auxiliary module. The firmware package to be upgraded is packaged into a complete firmware package, and includes: motherboard firmware, daughterboard firmware, auxiliary module firmware, daughterboard upgrade program, auxiliary module upgrade program, and firmware description file. The coupling of the lower-level machine with the upper-level machine to enter the upgrade mode includes: making the lower-level machine connect to the upper-level machine through only one external interface.

2. The firmware upgrade method according to claim 1, characterized in that, Upgrading firmware based on the firmware package to be upgraded at least one of the firmware objects to be upgraded includes: The auxiliary module upgrade program or the daughterboard upgrade program is transmitted to achieve firmware upgrade of the auxiliary module or the daughterboard in a decoupled manner from the motherboard firmware.

3. The firmware upgrade method according to claim 1, characterized in that, Upgrading the firmware of at least one of the motherboard, daughterboard, and auxiliary modules includes: If the motherboard is selected for upgrade, then the firmware of the motherboard is flashed in the upgrade mode; After the firmware of the motherboard is successfully flashed, the system restarts and enters the firmware program of the motherboard, reusing the pathways between the motherboard, the daughterboard, and the auxiliary module to perform firmware upgrades on other objects; and If the motherboard is not selected for upgrade, the firmware program of the motherboard will be restarted and the path between the motherboard, the daughterboard and the auxiliary module will be reused to upgrade the firmware of other objects.

4. The firmware upgrade method according to claim 3, characterized in that, Reusing the pathways between the motherboard, the daughterboard, and the auxiliary module for firmware upgrades of other objects includes: If the auxiliary module is selected for upgrade, the host computer sends the auxiliary module upgrade program to the slave computer to burn the firmware of the auxiliary module. After the firmware of the auxiliary module is successfully burned, if the sub-board is selected for upgrade, the host computer sends the sub-board upgrade program to the slave computer to perform firmware burning for the sub-board; and If the auxiliary module is not selected for upgrade, and if the sub-board is selected for upgrade, the host computer sends the sub-board upgrade program to the slave computer to perform firmware burning for the sub-board.

5. The firmware upgrade method according to claim 3, characterized in that, The firmware flashing process for the motherboard includes: Read the device type of the motherboard and check whether the device type of the motherboard matches the motherboard device type in the firmware package to be upgraded. If the firmware does not match, an error message will be displayed and the firmware flashing process will be exited. If a match is found, the current firmware version is read, and it is checked whether the current firmware version is consistent with the version in the firmware package to be upgraded; and If there is a discrepancy, begin the firmware flashing process for the motherboard.

6. The firmware upgrade method according to claim 3, characterized in that, The firmware flashing process for the auxiliary module includes: Read the device type of the auxiliary module and check whether the device type of the auxiliary module matches the device type of the auxiliary module in the firmware package to be upgraded. If the firmware does not match, an error message will be displayed and the firmware flashing process will be exited. If a match is found, the current firmware version is read, and it is checked whether the current firmware version is consistent with the version in the firmware package to be upgraded; and If there is a discrepancy, begin firmware flashing of the auxiliary module, and The firmware flashing process for the daughterboard includes: Read the device type of the sub-board and check whether the device type of the sub-board matches the device type of the sub-board in the firmware package to be upgraded. If the firmware does not match, an error message will be displayed and the firmware flashing process will be exited. If a match is found, the current firmware version is read, and it is checked whether the current firmware version is consistent with the version in the firmware package to be upgraded; and If there is a discrepancy, begin firmware burning for the sub-board.

7. The firmware upgrade method according to any one of claims 1 to 6, characterized in that, Also includes: The host computer performs an integrity check on the firmware package to be upgraded; as well as Obtain the upgrade instruction based on the integrity check results. Upgrading at least one of the firmware objects based on the firmware package to be upgraded includes: upgrading some or all of the objects according to the upgrade instruction.

8. The firmware upgrade method according to any one of claims 1 to 6, characterized in that, The lower-level machine is equipped with an upgrade button, wherein the upgrade start command responsive to the lower-level machine includes: a start command responsive to the upgrade button.

9. A firmware upgrade system, characterized in that, It includes a host computer and a slave computer, wherein the slave computer is coupled to the host computer through only one external interface, and the host computer performs firmware upgrade on the slave computer using the firmware upgrade method according to any one of claims 1 to 8.

10. The firmware upgrade system according to claim 9, characterized in that, The host computer includes a computer, and the slave computer includes a system-level test board.

11. An electronic device, characterized in that, include: Memory, configured to store computer programs; as well as The processor is configured to invoke the computer program to perform the firmware upgrade method according to any one of claims 1 to 8.

12. A computer-readable storage medium having program instructions stored thereon, characterized in that, The program instructions are executed to implement the firmware upgrade method according to any one of claims 1 to 8.

Images