A method, system and terminal for refreshing BIOS based on Genoa platform saving parameters

Abstract

The application discloses a method, system and terminal for saving parameters to refresh BIOS based on a Genoa platform, and the method comprises the following steps: initializing an AFU tool under an ipmitool environment based on the Genoa platform; determining the type of the AFU tool according to the bit number of an operating system under the current Genoa platform; judging whether the first parameter in the operating system command is a BIOS.bin file; if yes, determining that the target BIOS version and the original BIOS version belong to the same project; updating the information of the original BIOS version into the information of the target BIOS version; judging whether the second parameter in the operating system command is / save or / SAVE; if yes, performing a parameter refreshing operation without saving; otherwise, performing a parameter refreshing operation with saving. The system comprises an initialization module, an AFU refreshing instruction determining module, a first parameter judging module, an updating module, a second parameter judging module and a parameter refreshing module. Through the application, batch BIOS refreshing can be realized, the BIOS refreshing efficiency is effectively improved, and the stability of the refreshing operation is improved.

Description

Technical Field

[0001] This application relates to the technical field of BIOS (Basic Input Output System) flashing in servers, and in particular to a method, system, and terminal for flashing BIOS based on the Genoa platform by saving parameters. Background Technology

[0002] In server design, there are often multiple instances of BIOS upgrades and downgrades. In practice, default values ​​for setup options are typically set based on customer needs, and most of these default values ​​differ from those set by the server manufacturer. To avoid customers frequently updating these default values ​​with each BIOS update, preserving the default values ​​of setup options is crucial during BIOS upgrades and downgrades. In other words, how to save parameters when refreshing the BIOS is an important technical issue.

[0003] Currently, the method for saving parameters when refreshing the BIOS is usually achieved through AFU (AMI Firmware Update, a utility tool for upgrading the BIOS; AMI stands for American Megatrends, a BIOS vendor) tools with specific parameters. Different refresh commands are used for different functions. Specifically, the command for refreshing with saved parameters is: `. / AFUBIOS.bin / p / b / k / l / x`, and the command for refreshing without saving parameters is `. / AFU BIOS.bin / p / b / n / k / l / x`, where ` / n` means to refresh and clear the BIOS NVRAM (Non-Volatile Random Access Memory) area. The BIOS stores the parameters that need to be saved in the NVRAM, thus preserving this area without affecting the data. When the BIOS refresh is complete and the computer boots up, the BIOS will retrieve the data from this NVRAM and overwrite the new BIOS NVRAM area, thereby achieving the goal of refreshing the BIOS without clearing the BIOS parameters.

[0004] However, current methods for saving parameters when flashing the BIOS use different flashing commands for different functions, and the commands for whether to save parameters are relatively complex. Especially for flashing the BIOS flash, many commands are required, making existing AFU tools inconvenient to operate and complicated for testers. Therefore, the current method of saving parameters when flashing the BIOS has low flashing efficiency. Summary of the Invention

[0005] This application provides a method, system, and terminal for saving parameters and refreshing the BIOS based on the Genoa platform, in order to solve the problem that the BIOS refresh efficiency is low in the prior art.

[0006] To address the aforementioned technical problems, the embodiments of this application disclose the following technical solutions:

[0007] A method for saving parameters and flashing the BIOS based on the Genoa platform, the method comprising:

[0008] Initialize the AFU tool based on the Genoa platform in the ipmitool environment;

[0009] The type of AFU tool is determined based on the bitness of the operating system under the current Genoa platform. The types of AFU tools include: 64-bit AFU tools and 32-bit AFU tools.

[0010] Determine if the first argument in an operating system command is the BIOS.bin file;

[0011] If so, determine that the target BIOS version and the original BIOS version belong to the same item;

[0012] Update the original BIOS version information to the target BIOS version information;

[0013] Determine whether the second parameter in the operating system command is / save or / SAVE;

[0014] If so, perform a save parameter refresh operation;

[0015] If not, perform a refresh operation without saving parameters.

[0016] Optionally, before initializing the AFU tool in the ipmitool environment based on the Genoa platform, the method further includes:

[0017] Match the corresponding ipmitool environment according to the operating system version in the Genoa platform.

[0018] Optionally, the type of the AFU tool is determined based on the bitness of the operating system under the current Genoa platform, specifically as follows:

[0019] If the operating system under the current Genoa platform is 64-bit, select the 64-bit AFU tool;

[0020] If the operating system under the current Genoa platform is 32-bit, select the 32-bit AFU tool.

[0021] Optionally, performing the save parameter refresh operation includes:

[0022] The ipmitool tool is invoked to send a command to save BIOS parameters to the BMC (Baseboard Management Controller);

[0023] Based on the obtained command to save BIOS parameters, the BMC synchronizes the modified parameters on the BIOS setup to the EEPROM.

[0024] Optionally, after performing the save parameter refresh operation, the method further includes:

[0025] Perform a soft reboot based on the obtained reboot command;

[0026] When the boot process reaches the post stage, the parameters that need to be saved obtained from the BMC EEPROM are synchronized to BIOSsetup.

[0027] Optionally, after performing the refresh operation without saving parameters, the method further includes:

[0028] Perform a soft reboot based on the obtained reboot command.

[0029] A system for saving parameters and refreshing the BIOS based on the Genoa platform, the system comprising:

[0030] The initialization module is used to initialize the AFU tool in the ipmitool environment based on the Genoa platform.

[0031] The AFU refresh instruction determination module is used to determine the type of the AFU tool based on the bitness of the operating system under the current Genoa platform. The types of AFU tools include: 64-bit AFU tools and 32-bit AFU tools.

[0032] The first parameter judgment module is used to determine whether the first parameter in the operating system command is the BIOS.bin file. If it is, it determines that the target BIOS version and the original BIOS version belong to the same project and starts the update module; otherwise, it does not start the update module.

[0033] The update module is used to update the information of the original BIOS version to the information of the target BIOS version when the first parameter in the target BIOS version is a BIOS.bin file;

[0034] The second parameter judgment module is used to determine whether the second parameter in the operating system command is / save or / SAVE. If it is, the parameter refresh module is started; otherwise, the parameter refresh operation is performed without saving.

[0035] The parameter refresh module is used to perform a save parameter refresh operation when the second parameter in the operating system command is / save or / SAVE.

[0036] Optionally, the system also includes an environment setup module, used to match the corresponding ipmitool environment according to the version of the operating system in the Genoa platform.

[0037] Optionally, the system further includes:

[0038] The restart module is used to perform a save parameter refresh operation and, after performing a non-save parameter refresh operation, to perform a soft reboot based on the obtained reboot command;

[0039] The synchronization module is used to perform parameter saving and refreshing operations, and after a soft reboot, when the system boots up to the post stage, it synchronizes the parameters that need to be saved from the BMC EEPROM to the BIOS setup.

[0040] A terminal, the terminal comprising: a processor and a memory communicatively connected to the processor, wherein,

[0041] The memory stores instructions that can be executed by the processor, which are then executed by the processor to enable the processor to perform the method described above for saving parameters and refreshing the BIOS based on the Genoa platform.

[0042] The technical solutions provided by the embodiments of this application may include the following beneficial effects:

[0043] This application provides a method for saving parameters and refreshing the BIOS based on the Genoa platform. The method first initializes an AFU tool in the ipmitool environment on the Genoa platform, determining the AFU tool type based on the current platform's operating system bitness. Then, it first checks if the first parameter in the operating system command is a BIOS.bin file. If it is, the original BIOS version information is updated to the target BIOS version information. Next, it checks if the second parameter is a save-related / save or / SAVE. If it is, a save parameter refresh operation is performed; otherwise, the BIOS version is updated directly without saving. Compared to existing technologies, this embodiment mainly uses the first two parameters in the operating system command to perform in-band BIOS version updates and determine whether to save parameters. The commands used are more concise, and after upgrading and optimizing the AFU tool, the operation is more convenient and easier for testers to use, improving the efficiency of saving parameters and refreshing the BIOS, making in-band BIOS upgrades more efficient. This embodiment is based on the Genoa platform and performs BIOS version upgrades in the ipmitool environment. The ipmitool environment can integrate commands, and the method in this invention can achieve batch machine refresh operations, greatly improving BIOS refresh efficiency. Furthermore, this embodiment performs BIOS version upgrades within the ipmitool environment. The parameters saved by this upgrade method are not limited to the range provided by AMI, but have a wider applicable range, which is beneficial for widespread use. In this embodiment, "in-band" generally refers to the operation method performed under the operating system.

[0044] Furthermore, in this embodiment, when performing the parameter saving and refreshing operation, the BMC is used to synchronize the modified parameters on the BIOS setup to the EEPROM. Compared to the existing method of using NVRAM area storage, the parameter saving and refreshing method in this application can avoid storing some unnecessary operations of the original BIOS version, thereby affecting the normal operation of the target BIOS version. Moreover, the use of the BMC's EEPROM for parameter saving in this embodiment allows for convenient retrieval of information from the original BIOS version when necessary, resulting in higher storage stability and thus improving the efficiency of saving parameters and refreshing the BIOS.

[0045] This application also provides a system for saving parameters and refreshing the BIOS based on the Genoa platform. This system mainly includes: an initialization module, an AFU refresh instruction determination module, a first parameter judgment module, an update module, a second parameter judgment module, and a parameter refresh module. Through the initialization module, this embodiment initializes the AFU tool in the ipmitool environment based on the Genoa platform, and performs parameter saving and BIOS refreshing in the ipmitool environment, enabling batch machine refresh operations and greatly improving BIOS refresh efficiency. Furthermore, this embodiment performs BIOS version upgrades in the ipmitool environment. The parameters saved by this upgrade method are not limited to the parameter range provided by AMI, but have a wider applicable parameter range, which is beneficial for widespread use.

[0046] Through the first parameter judgment module and the second parameter judgment module, this embodiment performs in-band BIOS version update and determines whether to save parameters based on the first two parameters in the operating system command. The commands used are more concise, and the operation is more convenient after upgrading and optimizing the AFU tool. It is also more convenient for testers to operate, which helps to improve the efficiency of saving parameters and refreshing BIOS, making in-band BIOS upgrade more efficient.

[0047] This application also provides a terminal that has the same technical effects as the above-mentioned method and system for saving parameters and refreshing BIOS based on the Genoa platform, which will not be described in detail here.

[0048] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0049] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0050] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0051] Figure 1 A flowchart illustrating a method for saving parameters and refreshing BIOS based on the Genoa platform, provided in an embodiment of this application;

[0052] Figure 2 This is a schematic diagram of a system for saving parameters and refreshing the BIOS based on the Genoa platform, provided as an embodiment of this application. Detailed Implementation

[0053] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of this application.

[0054] To better understand this application, the embodiments of this application will be explained in detail below with reference to the accompanying drawings.

[0055] Example 1

[0056] See Figure 1 , Figure 1 This is a flowchart illustrating a method for saving parameters and refreshing the BIOS based on the Genoa platform, as provided in an embodiment of this application. Figure 1 As can be seen, the method for saving parameters and refreshing the BIOS based on the Genoa platform in this embodiment mainly includes the following processes:

[0057] S1: Initialize the AFU tool in the ipmitool environment based on the Genoa platform.

[0058] The Genoa platform is the name of AMD's next-generation server CPU based on the SP5 architecture.

[0059] This embodiment is based on the Genoa platform and performs BIOS flashing in the ipmitool environment. Since the ipmitool environment can achieve command integration, this method can perform batch BIOS version upgrade and downgrade operations when generating machines, thereby effectively improving BIOS flashing efficiency.

[0060] The method for flashing the BIOS in this embodiment is mainly based on AMI's AFU tool and ipmitool tool, as well as commands such as echo, if, and elif.

[0061] Furthermore, before step S1, there is also step S0: matching the corresponding ipmitool environment according to the version of the operating system in the Genoa platform.

[0062] For example, Red Hat 7 requires compatibility with the ipmtool 7 environment, Red Hat 8 requires compatibility with the ipmtool 8 environment, and Red Hat 9 requires compatibility with the ipmtool 9 environment.

[0063] S2: Determine the type of AFU tool based on the bitness of the operating system under the current Genoa platform.

[0064] In this embodiment, the types of AFU tools include 64-bit AFU tools and 32-bit AFU tools. Specifically, if the current operating system under the Genoa platform is 64-bit, a 64-bit AFU tool is selected; if the current operating system under the Genoa platform is 32-bit, a 32-bit AFU tool is selected.

[0065] This embodiment encapsulates the existing AFU tool in AMI, and the encapsulated AFU tool is updateLnx.sh.

[0066] S3: Determine if the first parameter in the operating system command is the BIOS.bin file.

[0067] In other words, it determines whether the first parameter is the BIOS.bin file that needs to be updated. If the first parameter in the operating system command is a BIOS.bin file, proceed to step S4: determine whether the target BIOS version and the original BIOS version belong to the same category.

[0068] S5: Update the information of the original BIOS version to the information of the target BIOS version.

[0069] The process ends if the first parameter in the operating system command is not the BIOS.bin file.

[0070] Based on steps S3-S5 above, this embodiment determines whether the first parameter is a BIOS.bin file. If so, it directly executes the command `. / AFU BIOS.bin / p / b / n / k / l / x` to clear the BIOS information on the current machine and flash the BIOS to be updated onto the machine. When determining whether the BIOS.bin file to be updated is consistent with the existing BIOS.bin file on the machine, the default AMI method is to verify the project name (Project_tag). If both bin files share the same Project_tag, the verification passes, and the BIOS flashing process begins. Because the default AMI verification method is incompatible with different project names for the same BIOS version, and because the BIOS.bin file is named according to AMI's naming convention:

[0071] Project_tag.Project_Major_Version.Project_Minor_Version.bin. The naming convention for the BIOS.bin file in this method is:

[0072] The file is named Project_tag.Project_Major_Version.Project_Minor_Version.Project_Sub_Version.bin. Therefore, although verifying Project_tag may pass, after the BMC web update of the BIOS version, the BMC will fail the verification.

[0073] After applying `Project_tag.Project_Major_Version.Project_Minor_Version.Project_Sub_Version`, the byte length may exceed the limit, resulting in a garbled message in the refresh log and impacting refresh efficiency. To accommodate these scenarios simultaneously, this solution uses `BIOS_tag` for verification; that is, `BIOS.tag` is defined by...

[0074] The system is composed of Project_Major_Version, Project_Minor_Version, and Project_Sub_Version. Then, it performs a double refresh check based on the different FW_VERSION_GUIDs of different projects. Only when both conditions pass the check can the next refresh step be performed.

[0075] See also Figure 1 It can be seen that after updating the information of the original BIOS version to the information of the target BIOS version, step S6 is executed: determine whether the second parameter in the operating system command is / save or / SAVE.

[0076] In other words, it determines whether the second parameter is a save parameter refresh command.

[0077] If the second parameter in the operating system command is / save or / SAVE, proceed to step S7: perform the save parameter refresh operation.

[0078] Specifically, step S7 includes:

[0079] S71: Invokes the ipmitool tool to send a command to save BIOS parameters to the BMC;

[0080] S72: Based on the obtained command to save BIOS parameters, the BMC synchronizes the modified parameters on the BIOS setup to the EEPROM.

[0081] If the second parameter in the operating system command is not / save or / SAVE, proceed to step S8: perform a refresh operation without saving parameters.

[0082] In other words, when the second parameter is empty, a refresh operation without saving parameters is performed, directly clearing all BIOS information on the current machine and refreshing the BIOS version that needs to be updated onto the machine.

[0083] Furthermore, in this embodiment, after performing the save parameter refresh operation and after performing the non-save parameter refresh operation, a soft reboot is also performed to ensure that the refreshed BIOS takes effect.

[0084] Specifically, regarding the process of performing the save parameter refresh operation, after step S72, the following steps are also included:

[0085] S73: Perform a soft reboot based on the obtained reboot command;

[0086] S74: When the boot process reaches the post stage, the parameters that need to be saved obtained from the BMC EEPROM will be synchronized to the BIOS setup.

[0087] After the BIOS flash is completed, step S73 ensures that the target BIOS version takes effect. Furthermore, this embodiment uses a soft reboot to flash the BIOS, eliminating the need to power off the machine and thus preventing data loss due to the reboot, which improves data security and stability during the BIOS flashing process. Step S74 synchronizes the parameters to be saved from the BMC EEPROM to the BIOS setup, ensuring that the data in the target BIOS version is the latest version.

[0088] For performing a refresh operation without saving parameters, after step S8, step S9 is also included: performing a soft reboot based on the obtained reboot command.

[0089] The technical effect of performing a soft reboot after performing a refresh operation without saving parameters is the same as the technical effect of a soft reboot in step S73, and will not be repeated here.

[0090] In summary, this embodiment encapsulates the existing AFU tool in AMI, borrowing the `echo` command to determine different AFU refresh commands under different conditions in the OS. When saving parameters in-band, the parameters to be saved are synchronized to the BMC EEPROM. Then, during boot after flashing the BIOS, the parameters to be saved are obtained in the POST stage via the `ipmi` command and synchronized to the BIOS Setup. The encapsulated AFU tool is `updateLnx.sh`. Copy the AFU, `updateLnx.sh`, and the BIOS bin file to be upgraded / downgraded to a folder under the operating system. The operation is performed using the command `. / updateLnx.sh BIOS.bin`. If BIOS options need to be saved, execute the command `. / updateLnx.sh BIOS.bin / save` (this embodiment is case-insensitive for `save`); if parameters do not need to be saved, directly execute `. / updateLnx.sh BIOS.bin`. This method of flashing BIOS versions makes in-band BIOS upgrades and downgrades more convenient, and the commands for saving parameters are simpler. This tool can completely erase other changes to the original BIOS version while preserving the original BIOS setup parameters, resulting in a cleaner and more complete BIOS flash. Furthermore, this tool does not rely on the BIOS's NVRAM area and can operate within the BMC EEPROM, making the BIOS version flashing operation more stable. Additionally, this tool can save any parameters from the BIOS Setup, unaffected by the scope of AMI tools, making it highly versatile. Finally, this tool can perform batch BIOS version upgrades and downgrades on production machines, saving significant manpower and resources, and reducing production costs.

[0091] Example 2

[0092] exist Figure 1 Based on the illustrated embodiment, see also Figure 2 , Figure 2 This is a schematic diagram of a system for saving parameters and refreshing the BIOS based on the Genoa platform, provided as an embodiment of this application. Figure 2 As can be seen, the system for saving parameters and refreshing the BIOS based on the Genoa platform in this embodiment mainly includes: an initialization module, an AFU refresh instruction determination module, a first parameter judgment module, an update module, a second parameter judgment module, and a parameter refresh module.

[0093] The system comprises the following modules: an initialization module for initializing the AFU tool within the ipmitool environment on the Genoa platform; an AFU refresh command determination module for determining the type of AFU tool based on the bitness of the operating system on the current Genoa platform (including 64-bit and 32-bit AFU tools); a first parameter judgment module for determining whether the first parameter in the operating system command is a BIOS.bin file; if so, it determines that the target BIOS version and the original BIOS version belong to the same project and starts the update module; otherwise, it does not start the update module; an update module for updating the information of the original BIOS version to the information of the target BIOS version when the first parameter in the target BIOS version is a BIOS.bin file; a second parameter judgment module for determining whether the second parameter in the operating system command is / save or / SAVE; if so, it starts the parameter refresh module; otherwise, it performs a parameter refresh operation without saving; and a parameter refresh module for performing a parameter refresh operation with saving when the second parameter in the operating system command is / save or / SAVE.

[0094] The AFU refresh instruction determination module is used to select a 64-bit AFU tool if the current operating system under the Genoa platform is 64-bit, and to select a 32-bit AFU tool if the current operating system under the Genoa platform is 32-bit.

[0095] Furthermore, the system also includes an environment setup module, which is used to match the corresponding ipmitool environment according to the version of the operating system in the Genoa platform.

[0096] The system also includes a reboot module and a synchronization module. The reboot module is used to perform a save parameter refresh operation and a non-save parameter refresh operation, and then perform a soft reboot based on the obtained reboot command. The synchronization module is used to perform the save parameter refresh operation and perform a soft reboot, and then synchronize the parameters that need to be saved obtained from BMCEEPROM to the BIOS setup when the system reaches the post stage during boot.

[0097] For parts not described in detail in this embodiment, please refer to [link / reference]. Figure 1 The embodiments shown are interchangeable and will not be described in detail here.

[0098] Example 3

[0099] This application also provides a terminal, which includes: a processor and a memory communicatively connected to the processor, wherein the memory stores instructions executable by the processor, and the instructions are executed by the processor to enable the processor to perform the above-described method of saving parameters and refreshing the BIOS based on the Genoa platform.

[0100] The method by which the processor saves parameters and refreshes the BIOS based on the Genoa platform is as follows:

[0101] 1) Match the corresponding ipmitool environment according to the operating system version in the Genoa platform.

[0102] 2) Initialize the AFU tool in the ipmitool environment based on the Genoa platform.

[0103] 3) Determine the type of AFU tool based on the bitness of the operating system under the current Genoa platform. The types of AFU tools include 64-bit AFU tools and 32-bit AFU tools.

[0104] 4) Determine if the first parameter in the operating system command is the BIOS.bin file.

[0105] 5) If the first parameter in the operating system command is the BIOS.bin file, it is determined that the target BIOS version and the original BIOS version belong to the same project.

[0106] 6) Update the information of the original BIOS version to the information of the target BIOS version.

[0107] 7) Determine whether the second parameter in the operating system command is / save or / SAVE.

[0108] 8) If the second parameter in the operating system command is / save or / SAVE, perform a save parameter refresh operation.

[0109] 9) If the second parameter in the operating system command is not / save or / SAVE, perform a refresh operation without saving parameters.

[0110] 10) After performing the save parameter refresh operation and the non-save parameter refresh operation, perform a soft reboot based on the obtained reboot command.

[0111] 11) When performing the save parameter refresh operation, after performing a soft reboot, when the system boots up to the post stage, the parameters that need to be saved obtained from the BMC EEPROM will be synchronized to the BIOS setup.

[0112] For parts not described in detail in this embodiment, please refer to [link / reference]. Figure 1 and Figure 2 The embodiments shown will not be described in detail here.

[0113] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for saving parameters and refreshing BIOS based on the Genoa platform, characterized in that, The method includes: Initialize the AFU tool based on the Genoa platform in the ipmitool environment; The type of AFU tool is determined based on the bitness of the operating system under the current Genoa platform. The types of AFU tools include: 64-bit AFU tools and 32-bit AFU tools. In response to the first parameter in the operating system command being the BIOS.bin file, the system determines that the target BIOS version and the original BIOS version belong to the same item, and updates the information of the original BIOS version to the information of the target BIOS version. In response to the second parameter in the operating system command being / save or / SAVE, a save parameter refresh operation is performed, which includes: The ipmitool tool is invoked to send a command to save BIOS parameters to the Baseboard Management Controller (BMC). In response to the command to save BIOS parameters, the BMC synchronizes the modified parameters on the BIOS setup to the EEPROM. If the second parameter in the operating system command is not / save or / SAVE, perform a refresh operation without saving parameters.

2. The method for saving parameters and refreshing BIOS based on the Genoa platform according to claim 1, characterized in that, Before initializing the AFU tool in the ipmitool environment based on the Genoa platform, the method also includes: Match the corresponding ipmitool environment according to the operating system version in the Genoa platform.

3. The method for saving parameters and refreshing BIOS based on the Genoa platform according to claim 1, characterized in that, The type of the AFU tool is determined based on the bitness of the operating system under the current Genoa platform, specifically as follows: If the operating system under the current Genoa platform is 64-bit, select the 64-bit AFU tool; If the operating system under the current Genoa platform is 32-bit, select the 32-bit AFU tool.

4. The method for saving parameters and refreshing BIOS based on the Genoa platform according to claim 1, characterized in that, After performing the save parameter refresh operation, the method further includes: Perform a soft reboot based on the obtained reboot command; During the Power-On Self-Test (POST) phase of power-on, the parameters that need to be saved are obtained from the BMC EEPROM via ipmitool and synchronized to the BIOS setup.

5. The method for saving parameters and refreshing BIOS based on the Genoa platform according to claim 1, characterized in that, After performing a refresh operation without saving parameters, the method further includes: Perform a soft reboot based on the obtained reboot command.

6. A system for saving parameters and refreshing BIOS based on the Genoa platform, characterized in that, The system includes: The initialization module is used to initialize the AFU tool in the ipmitool environment based on the Genoa platform. The AFU refresh instruction determination module is used to determine the type of the AFU tool based on the bitness of the operating system under the current Genoa platform. The types of AFU tools include: 64-bit AFU tools and 32-bit AFU tools. The first parameter judgment module is used to determine whether the first parameter in the operating system command is the BIOS.bin file. If it is, it determines that the target BIOS version and the original BIOS version belong to the same project and starts the update module; otherwise, it does not start the update module. The update module is used to update the information of the original BIOS version to the information of the target BIOS version when the first parameter in the target BIOS version is a BIOS.bin file; The second parameter judgment module is used to determine whether the second parameter in the operating system command is / save or / SAVE. If it is, the parameter refresh module is started; otherwise, the parameter refresh operation is performed without saving. The parameter refresh module is used to perform a save parameter refresh operation when the second parameter in the operating system command is / save or / SAVE. The parameter refresh module includes: The ipmitool calling unit is used to call the ipmitool tool and send a command to save BIOS parameters to the baseboard management controller (BMC). The BMC synchronization unit is used to enable the BMC to respond to the command to save BIOS parameters and synchronize the modified parameters on the BIOS setup to the EEPROM.

7. A system for saving parameters and refreshing BIOS based on the Genoa platform according to claim 6, characterized in that, The system also includes an environment setup module, which is used to match the corresponding ipmitool environment according to the version of the operating system in the Genoa platform.

8. A system for saving parameters and refreshing BIOS based on the Genoa platform according to claim 6, characterized in that, The system also includes: The restart module is used to perform a save parameter refresh operation and, after performing a non-save parameter refresh operation, to perform a soft reboot based on the obtained reboot command; The synchronization module is used to obtain the parameters that need to be saved from the BMC EEPROM through ipmitool when the POST stage is executed during power-on, and synchronize them to the BIOS setup.

9. A terminal, characterized in that, The terminal includes: a processor and a memory communicatively connected to the processor, wherein... The memory stores instructions that can be executed by the processor, which are executed by the processor to enable the processor to perform the method for saving parameters and refreshing the BIOS based on the Genoa platform as described in any one of claims 1 to 5.

Images