Server firmware version management method and system

Abstract

The invention provides a server firmware version management method and system, the method is applied to a main programmable chip side, and the method comprises the following steps: sending a target compatibility list reading request to a slave programmable chip; receiving a target compatibility list; the target compatibility list comprises a main programmable chip version list, and the main programmable chip version list comprises a version number of at least one main programmable chip; the version corresponding to the version number of the master programmable chip in the master programmable chip version list is compatible with the current version of the slave programmable chip; the current version of the master programmable chip is compared with the target compatibility list to determine whether the firmware version of the master programmable chip is compatible with the firmware version of the slave programmable chip. According to the method and the device, the efficiency of judging the compatibility between the firmware version in a certain programmable chip and the firmware versions of other programmable chips in the server can be improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of servers, and in particular to a server firmware version management method and system. BACKGROUND

[0002] In a server, multiple programmable chips such as BIOS, BMC, CPLD, etc. are involved. The firmware is generated after engineers complete design, programming and debugging, and it is also code that can be downloaded into an editable chip for running. In the entire life cycle of a server, there are many firmware versions for each programmable chip, and if the firmware versions being used in two programmable chips are not compatible, incompatibility may occur, which may further cause server communication or running abnormalities and form a fault.

[0003] In particular, during the production and assembly process, if the firmware version downloaded into a certain programmable chip is incompatible with the firmware versions of other programmable chips and a fault occurs, it is usually difficult for production personnel to locate which firmware version of the programmable chip is incompatible with the firmware version just downloaded into the programmable chip. Sometimes it may even be considered that it is caused by hardware or other problems, thereby wasting a lot of time to solve the problem. SUMMARY

[0004] To solve the above problems, the present application provides a server firmware version management method and system, which automatically judges whether the firmware version of a master programmable chip is compatible with the firmware version of a slave programmable chip by comparing the current version of the master programmable chip with a target compatibility list, thereby improving the efficiency of firmware version compatibility judgment of the master programmable chip and the slave programmable chip.

[0005] In a first aspect, the present application provides a server firmware version management method, which is applied to a master programmable chip side, and the method comprises:

[0006] sending a request for reading a target compatibility list to a slave editable chip;

[0007] receiving the target compatibility list; the target compatibility list contains a master programmable chip version list, and the master programmable chip version list contains at least one version number of the master programmable chip; the version corresponding to the version number of the master programmable chip in the master programmable chip version list is compatible with the current version of the slave programmable chip;

[0008] comparing the current version of the master programmable chip with the target compatibility list to determine whether the firmware version of the master programmable chip is compatible with the firmware version of the slave editable chip by judging whether the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list.

[0009] Optionally, before the step of sending a read target compatibility list request to the slave editable chip, the method further comprises:

[0010] reading the current version number of the slave programmable chip, and confirming that the current version of the master programmable chip is incompatible with the current version of the slave programmable chip when the reading of the current version number of the slave programmable chip fails;

[0011] The step of sending a read target compatibility list request to the slave editable chip comprises:

[0012] sending a read target compatibility list request to the slave editable chip when the reading of the version number of the slave programmable chip succeeds.

[0013] Optionally, after the step of comparing the current version of the master programmable chip with the target compatibility list, the method further comprises:

[0014] accessing a local compatibility list, and confirming whether the current version number of the slave programmable chip is in the local compatibility list according to the current version number of the slave programmable chip;

[0015] The local compatibility list contains a slave programmable chip version list, and the slave programmable chip version list contains at least one version number of the slave programmable chip; the version corresponding to the version number of the slave programmable chip in the slave programmable chip version list is compatible with the current version of the master programmable chip.

[0016] Optionally, the method further comprises:

[0017] when it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list, and the version number corresponding to the current version of the master programmable chip is not in the master programmable chip version list, issuing a version incompatible prompt message.

[0018] Optionally, the method further comprises:

[0019] when it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list, and the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list, updating the local compatibility list to store the current version number of the slave editable chip in the local compatibility list.

[0020] Optionally, the method further comprises:

[0021] when it is confirmed that the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list, issuing a version compatible prompt message;

[0022] when it is confirmed that the current version number of the slave programmable chip is in the local compatibility list, issuing a version compatible prompt message.

[0023] Optionally, the main programmable chip comprises a BMC, a BIOS or a CPLD.

[0024] In a second aspect, the present application provides a server firmware version management system, which is configured on the side of a main programmable chip, and comprises:

[0025] a sending module configured to send a target compatibility list request to a slave programmable chip;

[0026] a receiving module configured to receive a target compatibility list, wherein the target compatibility list comprises a main programmable chip version list, and the main programmable chip version list comprises at least one version number of the main programmable chip; the version corresponding to the version number of the main programmable chip is compatible with the current version of the slave programmable chip;

[0027] a comparison module configured to compare the current version of the main programmable chip with the target compatibility list, so as to determine whether the firmware version of the main programmable chip is compatible with the firmware version of the slave programmable chip by judging whether the version number corresponding to the current version of the main programmable chip is in the main programmable chip version list.

[0028] Optionally, the system further comprises:

[0029] a reading module configured to read the current version number of the slave programmable chip before the sending module is executed, and to confirm that the current version of the main programmable chip is incompatible with the current version of the slave programmable chip when the reading of the current version number of the slave programmable chip fails;

[0030] the sending module is further configured to send the target compatibility list request to the slave programmable chip when the reading of the version number of the slave programmable chip succeeds.

[0031] In a third aspect, the present application provides an electronic device, which comprises a main programmable chip and a slave programmable chip.

[0032] The main firmware is in communication connection with the slave firmware, and the main programmable chip is used to implement the method of any one of the first aspect.

[0033] The server firmware version management method and system provided by the embodiment of the application can quickly determine whether the current master programmable chip is compatible with the slave programmable chip by determining whether the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list, without manual intervention, thereby improving the efficiency of firmware compatibility determination of the master programmable chip and the slave programmable chip, that is, when downloading the firmware into a programmable chip, it can be quickly determined whether the firmware version of the firmware is compatible with the firmware version of other programmable chips. BRIEF DESCRIPTION OF DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor on the basis of these drawings.

[0035] Figure 1 The schematic structural block diagram of the BIOS chip of an embodiment of the present application;

[0036] Figure 2 The schematic structural block diagram of the BMC chip of an embodiment of the present application;

[0037] Figure 3 The schematic structural block diagram of the CPLD chip of an embodiment of the present application;

[0038] Figure 4 The schematic structural block diagram of the BIOS Flash of an embodiment of the present application;

[0039] Figure 5 The schematic structural block diagram of the BMC Flash of an embodiment of the present application;

[0040] Figure 6 The schematic structural block diagram of the server of an embodiment of the present application;

[0041] Figure 7 The schematic diagram of data interaction of each chip in the server in the firmware version management process of an embodiment of the present application;

[0042] Figure 8 The schematic flow chart of the server firmware version management method of an embodiment of the present application. DETAILED DESCRIPTION

[0043] For the purposes of this application, a more complete description of the application will be presented in the following detailed description. The detailed description is presented with reference to the accompanying drawings. In the drawings, the embodiments of the application are illustrated. However, the application can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the application to those skilled in the art.

[0044] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application.

[0045] As used herein, the singular forms "a", "an" and "the" include plural referents unless the context clearly dictates otherwise. It should also be understood that the term "comprising" or "having" etc., specifies the presence of stated features, integers, steps, operations, components, parts, or combinations thereof, but does not preclude the presence or addition of one or more other features, integers, steps, operations, components, parts, or combinations thereof.

[0046] In a first aspect, an embodiment of the present application provides an electronic device, the electronic device comprising: a master programmable chip and a slave programmable chip.

[0047] In combination with Figure 1 , Figure 2 and Figure 3 , it can be understood that the master programmable chip can be a programmable chip, such as a BMC (Baseboard Management Controller) chip, a BIOS (Basic Input Output System) chip or a CPLD (Complex Programmable Logic Device) chip. The slave programmable chip can be a programmable chip in communication connection with the master programmable chip. For example, the master programmable chip is a BMC, and the slave programmable chip is a BIOS or a CPLD; the master programmable chip is a BIOS or a CPLD, and the slave programmable chip is a BMC.

[0048] The master programmable chip comprises a master firmware and a local compatibility list, the local compatibility list comprising a slave programmable chip version list, the slave programmable chip version list comprising at least one version number of a slave programmable chip; the version corresponding to the version number of the slave programmable chip is compatible with the current version of the master programmable chip.

[0049] The slave programmable chip includes firmware and a target compatibility list, the target compatibility list includes a master programmable chip version list, and the master programmable chip version list includes a version number of at least one master programmable chip; the version corresponding to the version number of the master programmable chip is compatible with a current version of the slave programmable chip.

[0050] It should be noted that the positions of the firmware and the compatibility list corresponding to the master programmable chip or the slave programmable chip are different due to the specific packaging structure.

[0051] Specifically, the chips of BIOS and BMC include two parts of normal firmware and the corresponding compatibility list, that is, the firmware of BIOS and BMC are independent of the corresponding compatibility list, and each occupies an independent storage space. The compatibility list of CPLD is included in the CPLD firmware, that is, the compatibility list of CPLD is located in the same storage space as the CPLD firmware. Among them, the compatibility list of BIOS firmware includes a BMC version list compatible with the current version of BIOS; similarly, the compatibility list of BMC firmware also includes a BIOS version list and a CPLD version list compatible with the current version of BMC; the compatibility list of CPLD firmware includes a BMC version list compatible with the current version of CPLD. Among them, the compatibility lists of BMC and BIOS are additionally packaged into a complete firmware together with the firmware after the firmware of BIOS and the firmware of BMC are generated. The compatibility list of CPLD is stored in the register or Rom of CPLD after the CPLD code is edited, and the compatibility list is automatically included in the CPLD firmware after the CPLD firmware is generated.

[0052] In combination with Figure 4 and Figure 5 , BIOS and BMC will write the corresponding compatibility list to the corresponding Flash storage area each time the firmware version is upgraded, that is, each time the BIOS version is upgraded, the compatible BMC version information is written to the NVRAM variable area of the BIOS Flash; when the BMC version is upgraded, the compatible BIOS version information is written to the NVRAM variable area of the BMC Flash. In this way, when the server upgrades the firmware, the compatibility list corresponding to the firmware is upgraded at the same time, avoiding the additional operation of changing the compatibility list in the future and reducing the possibility of omission.

[0053] In the second aspect, the application provides a server, in combination with Figure 6The server comprises a CPU (Central Processing Unit), a BMC, a CPLD and a PCH (Platform Controller Hub). The PCH is in communication connection with the CPU through a DMI (Direct Media Interface) bus. The PCH is in communication connection with the BMC through an eSPI (Enhanced Serial Peripheral Interface) bus, and the CPLD is in communication connection with the BMC through an I2C (Inter-Integrated Circuit) bus. The BIOS is configured in the PCH.

[0054] The BIOS firmware, the BMC firmware and the CPLD firmware version management method in the server comprises a compatibility conflict detection method of each firmware and an automatic upgrade method of a compatibility list stored in each programmable chip, and is combined with Figure 7 , and the specific operation process is as follows:

[0055] Stage 101: The BMC is the active initiator of the entire compatibility detection. After the server is powered on, the BMC first reads the CPLD version number. If the reading fails, it indicates that the BMC and the CPLD are incompatible, and the compatibility detection result is directly displayed on the HTML (Hyper Text Markup Language) webpage of the BMC, that is, a prompt information of "the current CPLD and BMC version are incompatible" is displayed to inform the user. If the reading is successful, the next step is entered.

[0056] Stage 102: The BMC sends a reading compatibility list request to the CPLD through the I2C, then the CPLD reads out the CPLD compatibility list from the internal register or Rom, and feeds back the read CPLD compatibility list to the BMC. After the BMC obtains the CPLD compatibility list, it confirms whether the current BMC version number is in the CPLD compatibility list;

[0057] If yes, the compatibility detection result is that the current BMC and CPLD are compatible, and the next step is entered;

[0058] If no, the detection result is that the current BMC version number is not in the CPLD compatibility list, and the next step is directly entered to continue to confirm the compatibility of the version.

[0059] Stage 103: The BMC accesses the BMC compatibility list in the BMC Flash through the SPI bus, and confirms whether the CPLD version number is in the BMC compatibility list;

[0060] If yes, it indicates that the current BMC and CPLD are compatible, and there is no need to update the compatibility list.

[0061] If the CPLD version number is not in the BMC compatibility list, and the detection result in stage 102 is that the current BMC version is not in the CPLD compatibility list, it indicates that the BMC and CPLD are incompatible, and the compatibility detection result that the current CPLD and BMC version are incompatible is directly displayed on the HTML webpage of the BMC, informing the user.

[0062] If the CPLD version number is not in the BMC compatibility list, and the detection result in stage 102 is that the current BMC version is in the CPLD compatibility list, it indicates that the BMC and CPLD are compatible, and thus the BMC compatibility list in the BMC Flash is updated through the BMC to include the current CPLD version number in the compatibility list of the current BMC.

[0063] Stage 104: After completing the compatibility conflict detection or / and compatibility list update between the CPLD and the BMC, the BMC initiates a request to the BIOS to read the BIOS version number. If the reading fails, it indicates that the BMC and the BIOS are incompatible, and the compatibility detection result is directly displayed on the HTML webpage of the BMC, i.e., a prompt information that the current BIOS and BMC version are incompatible is displayed, informing the user. If the reading succeeds, the next step is entered.

[0064] Stage 105: The BMC sends a request to read the compatibility list to the BIOS through eSPI, and then the BIOS reads the BIOS compatibility list in the NVRAM in the BIOS Flash through SPI, and feeds back the BIOS compatibility list to the BMC. After obtaining the BIOS compatibility list, the BMC confirms whether the current BMC version number is in the BIOS compatibility list. If yes, it indicates that the current BMC and BIOS are compatible, and the next step is entered. If no, it indicates that the current BMC version number is not in the BIOS compatibility list, and the next step is directly entered to continue to confirm the compatibility of the version.

[0065] Stage 106: The BMC accesses the BMC compatibility list in the BMC Flash through SPI to confirm whether the BIOS version number is in the BMC compatibility list.

[0066] If the BIOS version number is in the BMC compatibility list, and the query result in stage 105 is that the current BMC version number is in the BIOS compatibility list, it indicates that the BMC and BIOS are compatible, and there is no need to update the compatibility list.

[0067] If the BIOS version number is in the BMC compatibility list, and the query result in stage 105 is "the current BMC version is not in the BIOS compatibility list", it indicates that the BMC and the BIOS are compatible, the current BMC version number is informed to the BIOS by the BMC through eSPI, and the BIOS is informed to update the compatibility list in the BIOS Flash;

[0068] If the BIOS version number is not in the BMC compatibility list, and the query result in stage 105 is "the current BMC version is not in the BIOS compatibility list", it indicates that the BMC and the BIOS are incompatible, and the compatibility detection result is directly displayed on the HTML webpage of the BMC, that is, the prompt information "the current BIOS is incompatible with the BMC version" is displayed to inform the user;

[0069] If the BIOS version number is not in the BMC compatibility list, and the query result in stage 105 is "the current BMC version number is in the BIOS compatibility list", it indicates that the BMC and the BIOS are compatible, and the BMC updates the BMC compatibility list in the BMC Flash, and the current BIOS version number is listed in the compatibility list of the current BMC.

[0070] It should be noted that when the new function of BIOS and BMC interaction is added to the function of the server, the BIOS firmware and the BMC firmware need to be upgraded at the same time to ensure that the server can be started normally and the new interactive function can be realized; if only the function of the BIOS side or the BMC side is added, only the corresponding firmware needs to be upgraded.

[0071] In a third aspect, the present application provides a server firmware version management method, which is applied to the master programmable chip side in the first aspect, and in combination with Figure 8 The method comprises steps S101 to S103.

[0072] Step S101: sending a read target compatibility list request to the slave programmable chip.

[0073] In an optional embodiment, before the step of sending the read target compatibility list request to the slave programmable chip, the method further comprises: reading the current version number of the slave programmable chip, and when the reading of the current version number of the slave programmable chip fails, confirming that the current version of the master programmable chip is incompatible with the current version of the slave programmable chip.

[0074] In the embodiment, the step of reading the current version number of the slave programmable chip comprises: sending a read slave programmable chip version number request, receiving and reading the current version number of the slave programmable chip sent by the slave programmable chip.

[0075] Further, the step of sending a request for reading the target compatibility list to the slave editable chip comprises: sending the request for reading the target compatibility list to the slave editable chip when the reading of the version number from the slave editable chip is successful.

[0076] Step S102: receiving the target compatibility list sent by the slave editable chip.

[0077] The target compatibility list comprises a master programmable chip version list. The master programmable chip version list comprises at least one version number of a master programmable chip. The version corresponding to the version number of the master programmable chip in the master programmable chip version list is compatible with the current version of the slave programmable chip.

[0078] Step S103: comparing the current version of the master programmable chip with the target compatibility list to determine whether the firmware version of the master programmable chip is compatible with the firmware version of the slave editable chip by judging whether the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list.

[0079] It can be understood that for the slave programmable chip side, multiple version numbers of programmable chips compatible with the current slave programmable chip can be stored simultaneously. When the target compatibility list is sent from the slave programmable chip to the master programmable chip, only the version numbers of the master programmable chips compatible with the current slave programmable chip can be sent to the master programmable chip, that is, the target compatibility list only comprises the master programmable chip version list; or all the version numbers of the programmable chips compatible with the current slave programmable chip can be sent to the master programmable chip, that is, the target compatibility list not only comprises the master programmable chip version list but also comprises other programmable chip version lists, so that the master programmable chip extracts the master programmable chip version list from the target compatibility list for comparison.

[0080] In this embodiment, the target compatibility list only comprises the master programmable chip version list.

[0081] In an alternative embodiment, after the step of comparing the current version of the master programmable chip with the target compatibility list, the method further comprises: accessing a local compatibility list and confirming whether the current version number of the slave programmable chip is in the local compatibility list according to the current version number of the slave programmable chip.

[0082] The local compatibility list is located on the master programmable chip side. The local compatibility list comprises a slave programmable chip version list. The slave programmable chip version list comprises at least one version number of a slave programmable chip. The version corresponding to the version number of the slave programmable chip in the slave programmable chip version list is compatible with the current version of the master programmable chip.

[0083] In an alternative embodiment, the method further comprises: when it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list, and the version number corresponding to the current version of the master programmable chip is not in the master programmable chip version list, issuing a version incompatible prompt message.

[0084] In an alternative embodiment, the method further comprises: when it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list, and the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list, updating the local compatibility list to store the current version number of the slave programmable chip in the local compatibility list.

[0085] In an alternative embodiment, the method further comprises: when it is confirmed that the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list, issuing a version compatible prompt message.

[0086] The method further comprises: when the current version number of the slave programmable chip is in the local compatibility list, issuing a version compatible prompt message.

[0087] In a fourth aspect, the present application provides a server firmware version management method, which is applied to the slave programmable chip in the first aspect, and comprises steps S201 to S204.

[0088] Step S201: receiving a request for reading the version number of the slave programmable chip.

[0089] Step S202: feeding back the current version number of the slave programmable chip.

[0090] Step S203: receiving a request for reading the target compatibility list.

[0091] Step S204: feeding back the target compatibility list.

[0092] In a fifth aspect, the present application provides a server firmware version management system, which is configured in the master programmable chip in the first aspect, and comprises:

[0093] A sending module configured to send a request for reading the target compatibility list to the slave programmable chip;

[0094] A receiving module configured to receive the target compatibility list; the target compatibility list contains a master programmable chip version list, and the master programmable chip version list contains at least one version number of the master programmable chip; the version corresponding to the version number of the master programmable chip is compatible with the current version of the slave programmable chip;

[0095] The comparison module is configured to compare the current version of the master programmable chip with the target compatibility list to determine whether the firmware version of the master programmable chip is compatible with the firmware version of the slave programmable chip by judging whether the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list.

[0096] In an optional embodiment, the system further comprises:

[0097] The reading module is configured to read the current version number of the slave programmable chip before executing the sending module, and confirm that the current version of the master programmable chip is incompatible with the current version of the slave programmable chip when the reading of the current version number of the slave programmable chip fails.

[0098] The sending module is further configured to send a request for reading the target compatibility list to the slave programmable chip when the reading of the version number of the slave programmable chip succeeds.

[0099] In an optional embodiment, after the step of comparing the current version of the master programmable chip with the target compatibility list, the system further comprises:

[0100] The accessing module is configured to access the local compatibility list after executing the comparison module, and confirm whether the current version number of the slave programmable chip is in the local compatibility list according to the current version number of the slave programmable chip.

[0101] The local compatibility list contains a slave programmable chip version list, and the slave programmable chip version list contains at least one version number of a slave programmable chip; the version corresponding to the version number of the slave programmable chip in the slave programmable chip version list is compatible with the current version of the master programmable chip.

[0102] In an optional embodiment, the system further comprises:

[0103] The output module is configured to issue a prompt message of version incompatibility when it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list, and the version number corresponding to the current version of the master programmable chip is not in the master programmable chip version list.

[0104] In an optional embodiment, the system further comprises:

[0105] The output module is configured to update the local compatibility list to store the current version number of the slave programmable chip in the local compatibility list when it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list, and the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list.

[0106] In an optional embodiment, the output module is further configured to issue a version compatibility prompt message when confirming that the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list; and to issue a version compatibility prompt message when confirming that the current version number of the slave programmable chip is in the local compatibility list.

[0107] Throughout this specification, references to terms such as "some embodiments," "other embodiments," and "desired embodiments" indicate that a particular feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present application. The schematic descriptions of these terms throughout this specification do not necessarily refer to the same embodiment or example.

[0108] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0109] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be determined by the appended claims.

Claims

1. A method for managing server firmware versions, characterized in that: The method is applied to the main programmable chip side, and the method includes: Sending a request to read the target compatibility list from the editable chip; Receive a target compatibility list; the target compatibility list includes a master programmable chip version list, the master programmable chip version list includes at least one version number of the master programmable chip; the version corresponding to the master programmable chip version number in the master programmable chip version list is compatible with the current version of the slave programmable chip; Compare the current version of the master programmable chip with the target compatibility list to determine whether the firmware version of the master programmable chip is compatible with the firmware version of the slave editable chip by judging whether the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list.

2. The management method according to claim 1, characterized in that: Before the step of sending a request to read the target compatibility list from the editable chip, the method further includes: reading a current version number of the slave programmable chip, and when reading the current version number of the slave programmable chip fails, confirming that the current version of the master programmable chip is incompatible with the current version of the slave programmable chip; The step of sending a request to read the target compatibility list from the editable chip includes: When the version number of the slave programmable chip is read successfully, the request for reading the target compatibility list is sent to the slave editable chip.

3. The management method according to claim 2, characterized in that: After the step of comparing the current version of the master programmable chip with the target compatibility list, the method further includes: Accessing a local compatibility list and confirming, based on a current version number of the slave programmable chip, whether the current version number of the slave programmable chip is in the local compatibility list; The local compatibility list includes a slave programmable chip version list, and the slave programmable chip version list includes at least one version number of the slave programmable chip; the version corresponding to the version number of the slave programmable chip in the slave programmable chip version list is compatible with the current version of the master programmable chip.

4. The management method according to claim 3, characterized in that: The method further comprises: When it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list and the version number corresponding to the current version of the master programmable chip is not in the master programmable chip version list, a prompt message of version incompatibility is issued.

5. The management method according to claim 3, characterized in that: The method further comprises: When it is confirmed that the current version number of the slave programmable chip is not in the local compatibility list, and the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list, the local compatibility list is updated to store the current version number of the slave editable chip in the local compatibility list.

6. The management method according to claim 3, characterized in that: The method further comprises: When confirming that the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list, issuing a version compatibility prompt message; When confirming that the current version number of the slave programmable chip is in the local compatibility list, a prompt message indicating version compatibility is issued.

7. The management method according to any one of claims 1 to 6, characterized in that: The main programmable chip includes: BMC, BIOS or CPLD.

8. A server firmware version management system, characterized in that: The system is configured on the main programmable chip side, and the system includes: a sending module configured to send a request to read a target compatibility list from the editable chip; a receiving module configured to receive a target compatibility list; the target compatibility list includes a master programmable chip version list, the master programmable chip version list includes at least one version number of the master programmable chip; the version corresponding to the master programmable chip version number in the master programmable chip version list is compatible with the current version of the slave programmable chip; The comparison module is configured to compare the current version of the master programmable chip with the target compatibility list to determine whether the firmware version of the master programmable chip is compatible with the firmware version of the slave editable chip by judging whether the version number corresponding to the current version of the master programmable chip is in the master programmable chip version list.

9. The management system according to claim 8, characterized in that: The system further comprises: a reading module configured to read the current version number of the slave programmable chip before executing the sending module, and to confirm that the current version of the master programmable chip is incompatible with the current version of the slave programmable chip when reading the current version number of the slave programmable chip fails; The sending module is further configured to send the request for reading the target compatibility list to the slave editable chip when the version number of the slave programmable chip is read successfully.

10. An electronic device, characterized in that: The electronic device comprises: a master programmable chip and a slave programmable chip; The master firmware is communicatively connected to the slave firmware, and the master programmable chip is used to implement the method according to any one of claims 1 to 7.

Images