A system firmware boot method, apparatus, device, and computer storage medium

By reading a preset storage address from the BIOS image and remotely booting the target system firmware image, the problem of limited system firmware booting is solved, and a fast boot effect is achieved.

CN116088945BActive Publication Date: 2026-11-17INSPUR SUZHOU INTELLIGENT TECH CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202211521577.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-11-30
Publication Date
2026-11-17
Estimated Expiration
2042-11-30

AI Technical Summary

Technical Problem

In existing technologies, the booting of system firmware is limited by the ROMLayout space address and size of the BIOS chip, resulting in poor system scalability and hindering fast booting.

Method used

The system reads the preset storage address from the BIOS image, including addresses outside the BIOS storage area, determines the target system firmware image to be booted, and achieves fast boot by remotely booting the target system firmware image.

Benefits of technology

It breaks the limitation of BIOS storage space on system firmware, enables fast system firmware boot, and avoids frequent rewriting of BIOS storage space.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116088945B_ABST
    Figure CN116088945B_ABST
Patent Text Reader

Abstract

This application discloses a system firmware booting method, apparatus, device, and computer storage medium applied to a BIOS, which performs initialization operations; reads a preset storage address from the BIOS image, the preset storage address including addresses outside the BIOS storage area; determines the target system firmware image to be booted based on the preset storage address; and remotely boots the target system firmware image to start the corresponding target system firmware. In this application, the BIOS remotely boots the target system firmware image based on the preset storage address to start the target system firmware. Since the preset storage address is an address outside the BIOS storage area, this application is equivalent to determining the target system firmware image from an address outside the BIOS storage area to remotely boot the target system firmware, breaking the limitation of BIOS storage space on system firmware, eliminating the need for frequent rewriting of BIOS storage space or system firmware, and facilitating fast system firmware boot.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of server technology, and more specifically, to a system firmware boot method, apparatus, device, and computer storage medium. Background Technology

[0002] After the server is powered on, the BIOS (Basic Input / Output System) firmware completes the initialization before entering the operating system, such as the CPU, memory, and drivers. During operating system startup, some peripherals are initialized. For example, Linux Boot is a Linux system firmware that includes Linux kernel drivers and other Linux-based optional functions. Taking a BIOS based on UEFI (Uniform Extended Firmware Interface), for instance, peripheral initialization during the DXE / BDS stage can be partially replaced by Linux Boot, thus allowing for a smoother transition to the Linux operating system.

[0003] In existing solutions, the system firmware is typically packaged into a BIOS image that has excluded some DXE / BDS functions and executed. The advantage of this method is that it avoids repeatedly performing the same peripheral initialization operations, reduces boot time, and completes a smooth transition from BIOS to Linux. The disadvantage is that it is limited by the address and size of the ROMLayout space where the BIOS chip is located, which makes the system firmware subject to space constraints, resulting in poor system scalability and hindering the fast boot of the system firmware.

[0004] In conclusion, how to quickly boot the system firmware is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a system firmware boot method, which can solve, to some extent, the technical problem of how to quickly boot system firmware. This application also provides a system firmware boot apparatus, device, and computer-readable storage medium.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] A system firmware boot method, applied to BIOS, includes:

[0008] Perform initialization operations;

[0009] Read a preset storage address from the BIOS image, where the preset storage address includes addresses outside the BIOS storage area;

[0010] The target system firmware image to be started is determined based on the preset storage address;

[0011] Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0012] Preferably, reading the preset storage address from the BIOS image includes:

[0013] The preset storage address is read from the BIOS image, and the preset storage address includes the server's own memory.

[0014] Preferably, reading the preset storage address from the BIOS image includes:

[0015] The preset storage address is read from the BIOS image, and the preset storage address includes persistent memory connected to the server.

[0016] Preferably, reading the preset storage address from the BIOS image includes:

[0017] The preset storage address, which includes a public access area, is read from the BIOS image.

[0018] Preferably, reading the preset storage address from the BIOS image includes:

[0019] The preset storage address is read from the BIOS image, and the preset storage address includes the server southbridge device.

[0020] Preferably, the remote booting of the target system firmware image includes:

[0021] The target system firmware image is remotely booted via BMC.

[0022] Preferred options also include:

[0023] Execute UEFI process

[0024] A system firmware boot device, applied to BIOS, comprising:

[0025] The first execution module is used to perform initialization operations;

[0026] The first reading module is used to read a preset storage address from the BIOS image, wherein the preset storage address includes an address outside the BIOS storage area;

[0027] The first determining module is used to determine the target system firmware image to be started based on the preset storage address;

[0028] The first boot module is used to remotely boot the target system firmware image to boot the corresponding target system firmware.

[0029] A system firmware boot device, comprising:

[0030] Memory, used to store computer programs;

[0031] A processor, configured to implement the steps of any of the above-described system firmware boot methods when executing the computer program.

[0032] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above-described system firmware boot methods.

[0033] This application provides a system firmware booting method applied to a BIOS, which performs initialization operations; reads a preset storage address from the BIOS image, the preset storage address including addresses outside the BIOS storage area; determines the target system firmware image to be booted based on the preset storage address; and remotely boots the target system firmware image to start the corresponding target system firmware. In this application, after performing initialization operations, the BIOS reads the preset storage address from its own BIOS image and determines the target system firmware image to be booted based on the preset storage address. Finally, it remotely boots the target system firmware image to start the corresponding target system firmware. Since the preset storage address is an address outside the BIOS storage area, this application is equivalent to determining the target system firmware image from an address outside the BIOS storage area to remotely boot the target system firmware, breaking the limitation of BIOS storage space on system firmware. This eliminates the need for frequent rewriting of BIOS storage space or system firmware, facilitating faster system firmware booting. The system firmware booting device, apparatus, and computer-readable storage medium provided in this application also solve the corresponding technical problems. Attached Figure Description

[0034] 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, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0035] Figure 1 A first flowchart of a system firmware boot method provided in this application embodiment;

[0036] Figure 2 A second flowchart of a system firmware boot method provided in an embodiment of this application;

[0037] Figure 3 A third flowchart of a system firmware boot method provided in an embodiment of this application;

[0038] Figure 4 A fourth flowchart of a system firmware boot method provided in an embodiment of this application;

[0039] Figure 5 A fifth flowchart illustrating a system firmware boot method provided in an embodiment of this application;

[0040] Figure 6 A sixth flowchart of a system firmware boot method provided in an embodiment of this application;

[0041] Figure 7 This is a schematic diagram of the structure of a system firmware boot device provided in an embodiment of this application;

[0042] Figure 8 This application provides a schematic diagram of the structure of a system firmware boot device.

[0043] Figure 9 This is another structural schematic diagram of a system firmware boot device provided in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of 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 of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] After the server is powered on, the BIOS (Basic Input / Output System) firmware completes the initialization before entering the operating system, such as the CPU, memory, and drivers. During operating system startup, some peripherals are initialized. For example, Linux Boot is a Linux system firmware that includes Linux kernel drivers and other Linux-based optional functions. Taking a BIOS based on UEFI (Uniform Extended Firmware Interface), for instance, peripheral initialization during the DXE / BDS stage can be partially replaced by Linux Boot, thus allowing for a smoother transition to the Linux operating system.

[0046] In existing solutions, the system firmware is typically packaged into a BIOS image that has partially excluded DXE / BDS functions for execution. The advantage of this method is that it avoids repeatedly performing the same peripheral initialization operations, reduces boot time, and facilitates a smooth transition from BIOS to Linux. However, the disadvantage is that the system firmware is constrained by the ROMLayout space address and size of the BIOS chip, resulting in poor system scalability and hindering fast system firmware booting. The system firmware boot solution provided in this application enables fast system firmware booting.

[0047] Please see Figure 1 , Figure 1 This is a first flowchart of a system firmware boot method provided in an embodiment of this application.

[0048] This application provides a system firmware boot method applied to BIOS, which may include the following steps:

[0049] Step S101: Perform initialization operations.

[0050] In practical applications, the BIOS can perform initialization operations first to prepare for subsequent system firmware boot. The type of initialization operation performed by the BIOS can be determined according to the specific application scenario, and this application does not impose any specific restrictions here.

[0051] Step S102: Read the preset storage address from the BIOS image. The preset storage address includes addresses outside the BIOS storage area.

[0052] In practical applications, after performing initialization, the BIOS can read preset memory addresses from the BIOS image. These preset memory addresses include addresses outside the BIOS memory area; that is, addresses outside the BIOS memory area are read. The type of preset memory address can be dynamically adjusted according to specific application scenarios, and this application does not impose any specific limitations on it.

[0053] Step S103: Determine the target system firmware image to be booted based on the preset storage address.

[0054] In practical applications, after the BIOS reads the preset storage address from the BIOS image, it can determine the target system firmware image to be booted based on the preset storage address, so that the corresponding target system firmware can be booted subsequently.

[0055] In specific application scenarios, when the BIOS image is compiled, a separate module can be created to execute the system firmware image through configuration in the INF file. In this module, the agreed address of the system firmware image can be written, that is, the preset storage address can be written. When the BIOS executes this module, it can execute the system firmware from the preset storage address through the StartImage method.

[0056] It should be noted that, in specific application scenarios, the type of target system firmware image can be determined according to actual needs. For example, when the target system firmware image is a Linux Boot firmware image, necessary Linux Boot functions, such as certain peripheral drivers and operating system kernels, can be selected according to the business needs of the operating system. The generated Linux Boot firmware image file can be stored in the preset storage address. Furthermore, the Linux Boot firmware image can be customized with Linux drivers, kernel versions, or boot parameters to achieve customization. This application does not make any specific restrictions here.

[0057] Step S104: Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0058] In practical applications, after the BIOS determines the target system firmware image to be booted based on the preset storage address, it can remotely boot the target system firmware image to start the corresponding target system firmware.

[0059] In specific application scenarios, considering the large number of system firmwares in a server, in order to meet the boot requirements of multiple system firmwares, multiple system firmware images can be created simultaneously according to different needs. For example, multiple Linux Boot firmware images can be created, and then the required Linux Boot image can be directly selected for booting through software control. For example, the required Linux Boot image can be selected for booting through software under the OS (Operating System), or it can be selected for booting through the server firmware, such as through the BMC (Baseboard Management Controller). This application does not make specific limitations here.

[0060] It should be noted that during the remote booting of the target system firmware image, the BIOS can also save relevant information that is beneficial to subsequent boot operations as needed, in order to facilitate subsequent boot operations. This application does not make specific limitations here.

[0061] To facilitate understanding of the system firmware boot method provided in this application, assuming the target system firmware is Linux Boot firmware, the boot process of Linux Boot firmware can be as follows: The user creates a Linux Boot firmware image and stores it in a preset storage address on the server; the server's BIOS first performs an initialization operation, then reads the preset storage address from the BIOS image, the preset storage address including addresses outside the BIOS storage area, then determines the Linux Boot firmware image to be booted based on the preset storage address, and finally remotely boots the Linux Boot firmware image to boot the corresponding Linux Boot firmware.

[0062] This application provides a system firmware boot method applied to a BIOS, which performs initialization operations; reads a preset storage address from the BIOS image, the preset storage address including addresses outside the BIOS storage area; determines the target system firmware image to be booted based on the preset storage address; and remotely boots the target system firmware image to start the corresponding target system firmware. In this application, after performing initialization operations, the BIOS reads a preset storage address from its own BIOS image and determines the target system firmware image to be booted based on the preset storage address. Finally, it remotely boots the target system firmware image to start the corresponding target system firmware. Since the preset storage address is an address outside the BIOS storage area, this application is equivalent to determining the target system firmware image from an address outside the BIOS storage area to remotely boot the target system firmware, breaking the limitation of BIOS storage space on system firmware. This eliminates the need for frequent rewriting of BIOS storage space or system firmware, facilitating faster system firmware boot.

[0063] Please see Figure 2 , Figure 2 This is a second flowchart of a system firmware boot method provided in an embodiment of this application.

[0064] This application provides a system firmware boot method applied to BIOS, which may include the following steps:

[0065] Step S201: Perform initialization operations.

[0066] Step S202: Read the preset storage address from the BIOS image. The preset storage address includes the server's own memory.

[0067] In practical applications, during the process of reading a preset storage address from the BIOS image, the preset storage address can be read from the BIOS image itself. This preset storage address includes the server's own memory. In other words, when the server's own memory is available, the target system firmware image can be stored in the server's own memory, for example, by transferring the target system firmware image to the server's own memory via a network card.

[0068] Step S203: Determine the target system firmware image to be booted based on the preset storage address.

[0069] Step S204: Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0070] To facilitate understanding of the system firmware boot method provided in this application, assuming the target system firmware is Linux Boot firmware, the boot process of Linux Boot firmware in this embodiment can be as follows: The user creates a Linux Boot firmware image and stores it in a preset storage address on the server; the server's BIOS first performs an initialization operation, then reads the preset storage address from the BIOS image, the preset storage address including the server's own memory, then determines the Linux Boot firmware image to be booted based on the server's own memory, and finally remotely boots the Linux Boot firmware image to boot the corresponding Linux Boot firmware.

[0071] Please see Figure 3 , Figure 3 This is a third flowchart of a system firmware boot method provided in an embodiment of this application.

[0072] This application provides a system firmware boot method applied to BIOS, which may include the following steps:

[0073] Step S301: Perform initialization operations.

[0074] Step S302: Read the preset storage address from the BIOS image. The preset storage address includes the persistent memory connected to the server.

[0075] In practical applications, during the process of reading the preset storage address from the BIOS image, the preset storage address can be read from the BIOS image. The preset storage address includes the persistent memory connected to the server. That is, the target system firmware image can be stored in the persistent memory connected to the server, such as in the server's AEP memory (Apache PassDIMMs). In specific application scenarios, in order to facilitate the maintenance of the system firmware image in the persistent memory connected to the server, it can be remotely updated through server firmware BMC or OS network transmission, etc. This application does not make specific limitations here.

[0076] Step S303: Determine the target system firmware image to be booted based on the preset storage address.

[0077] Step S304: Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0078] To facilitate understanding of the system firmware boot method provided in this application, assuming the target system firmware is Linux Boot firmware, the boot process of Linux Boot firmware in this embodiment can be as follows: The user creates a Linux Boot firmware image and stores it in a preset storage address on the server; the server's BIOS first performs an initialization operation, then reads the preset storage address from the BIOS image, the preset storage address including the persistent memory connected to the server, then determines the Linux Boot firmware image to be booted based on the persistent memory connected to the server, and finally remotely boots the Linux Boot firmware image to boot the corresponding Linux Boot firmware.

[0079] Please see Figure 4 , Figure 4 This is a fourth flowchart of a system firmware boot method provided in an embodiment of this application.

[0080] This application provides a system firmware boot method applied to BIOS, which may include the following steps:

[0081] Step S401: Perform initialization operations.

[0082] Step S402: Read the preset storage address from the BIOS image. The preset storage address includes the public access area.

[0083] In practical applications, during the process of reading a preset storage address from the BIOS image, the preset storage address can be read from the BIOS image. This preset storage address includes the public access area. That is, the target system firmware image can be stored in the server's public access area, such as in the public access area of ​​the BIOS and BMC, like video memory.

[0084] Step S403: Determine the target system firmware image to be booted based on the preset storage address.

[0085] Step S404: Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0086] To facilitate understanding of the system firmware boot method provided in this application, assuming the target system firmware is Linux Boot firmware, the boot process of Linux Boot firmware in this embodiment can be as follows: The user creates a Linux Boot firmware image and stores it in a preset storage address on the server; the server's BIOS first performs an initialization operation, then reads the preset storage address from the BIOS image, the preset storage address includes a public access area, then determines the Linux Boot firmware image to be booted based on the public access area, and finally remotely boots the Linux Boot firmware image to boot the corresponding Linux Boot firmware.

[0087] Please see Figure 5 , Figure 5 The fifth flowchart of a system firmware boot method provided in this application embodiment.

[0088] This application provides a system firmware boot method applied to BIOS, which may include the following steps:

[0089] Step S501: Perform initialization operation.

[0090] Step S502: Read the preset storage address from the BIOS image. The preset storage address includes the server southbridge device.

[0091] In practical applications, during the process of reading the preset storage address from the BIOS image, the preset storage address includes the server southbridge device. That is, the target system firmware image can be stored in the server southbridge device, such as the server PCH (Platform Controller Hub). Correspondingly, the target system firmware image can be remotely executed via the debugging function in the PCH, etc. This application does not impose specific limitations on this.

[0092] Step S503: Determine the target system firmware image to be booted based on the preset storage address.

[0093] Step S504: Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0094] To facilitate understanding of the system firmware boot method provided in this application, assuming the target system firmware is Linux Boot firmware, the boot process of Linux Boot firmware in this embodiment can be as follows: The user creates a Linux Boot firmware image and stores it in a preset storage address on the server; the server's BIOS first performs an initialization operation, then reads the preset storage address from the BIOS image, the preset storage address includes the server's southbridge device, then determines the Linux Boot firmware image to be booted based on the server's southbridge device, and finally remotely boots the Linux Boot firmware image to boot the corresponding Linux Boot firmware.

[0095] Please see Figure 6 , Figure 6 The sixth flowchart is provided for a system firmware boot method according to an embodiment of this application.

[0096] This application provides a system firmware boot method applied to BIOS, which may include the following steps:

[0097] Step S601: Perform initialization operation.

[0098] Step S602: Read the preset storage address from the BIOS image. The preset storage address includes addresses outside the BIOS storage area.

[0099] Step S603: Determine the target system firmware image to be booted based on the preset storage address.

[0100] Step S604: Remotely boot the target system firmware image via BMC to boot the corresponding target system firmware.

[0101] In practical applications, during the process of remotely booting the target system firmware image, the BIOS can use the BMC to remotely boot the target system firmware image, thereby enabling the target system firmware to boot quickly with the help of the BMC.

[0102] In practical applications, during the system firmware boot process, the BIOS can also execute the original UEFI process as needed. In specific application scenarios, the BIOS can determine whether to execute the original UEFI process through Setup control, the OS can determine whether to execute the original UEFI process through registers, or the BMCWeb user interaction page can control whether the BIOS executes the original UEFI process. This allows the BIOS to control the execution of the original UEFI process and meet the corresponding management needs of the user.

[0103] To facilitate understanding of the system firmware boot method provided in this application, assuming the target system firmware is Linux Boot firmware, the boot process of Linux Boot firmware in this embodiment can be as follows: The user creates a Linux Boot firmware image and stores it in a preset storage address on the server; the server's BIOS first performs an initialization operation, then reads the preset storage address from the BIOS image, the preset storage address includes addresses outside the BIOS storage area, then determines the Linux Boot firmware image to be booted based on the preset storage address, and finally remotely boots the Linux Boot firmware image through the BMC to boot the corresponding Linux Boot firmware.

[0104] Please see Figure 7 , Figure 7 This is a schematic diagram of a system firmware boot device provided in an embodiment of this application.

[0105] This application provides a system firmware boot device, applied to a BIOS, which may include:

[0106] The first execution module 101 is used to perform initialization operations;

[0107] The first reading module 102 is used to read a preset storage address from the BIOS image. The preset storage address includes addresses outside the BIOS storage area.

[0108] The first determining module 103 is used to determine the target system firmware image to be started based on a preset storage address;

[0109] The first boot module 104 is used to remotely boot the target system firmware image to boot the corresponding target system firmware.

[0110] This application provides a system firmware boot device applied to a BIOS, wherein the first reading module may include:

[0111] The first reading unit is used to read the preset storage address from the BIOS image. The preset storage address includes the server's own memory.

[0112] This application provides a system firmware boot device applied to a BIOS, wherein the first reading module may include:

[0113] The second read unit is used to read a preset storage address from the BIOS image. The preset storage address includes the persistent memory connected to the server.

[0114] This application provides a system firmware boot device applied to a BIOS, wherein the first reading module may include:

[0115] The third read unit is used to read the preset storage address from the BIOS image. The preset storage address includes the public access area.

[0116] This application provides a system firmware boot device applied to a BIOS, wherein the first reading module may include:

[0117] The fourth read unit is used to read the preset storage address from the BIOS image. The preset storage address includes the server southbridge device.

[0118] This application provides a system firmware boot device applied to a BIOS, wherein the first boot module may include:

[0119] The first boot unit is used to remotely boot the target system firmware image via the BMC.

[0120] This application provides a system firmware boot device for use in BIOS, which may further include:

[0121] The second execution module is used to execute the UEFI process.

[0122] This application also provides a system firmware boot device and a computer-readable storage medium, both of which have the corresponding effects of the system firmware boot method provided in the embodiments of this application. Please refer to... Figure 8 , Figure 8 This is a schematic diagram of the structure of a system firmware boot device provided in an embodiment of this application.

[0123] This application provides a system firmware boot device, including a memory 201 and a processor 202. The memory 201 stores a computer program, and the processor 202 executes the computer program to perform the following steps:

[0124] Perform initialization operations;

[0125] Read the preset storage address from the BIOS image. The preset storage address includes addresses outside the BIOS storage area.

[0126] The target system firmware image to be booted is determined based on the preset storage address;

[0127] Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0128] This application provides a system firmware boot device, including a memory 201 and a processor 202. The memory 201 stores a computer program. When the processor 202 executes the computer program, it performs the following steps: reading a preset storage address from the BIOS image. The preset storage address includes the server's own memory.

[0129] This application provides a system firmware boot device, including a memory 201 and a processor 202. The memory 201 stores a computer program. When the processor 202 executes the computer program, it performs the following steps: reading a preset storage address from the BIOS image. The preset storage address includes persistent memory connected to the server.

[0130] This application provides a system firmware boot device, including a memory 201 and a processor 202. The memory 201 stores a computer program, and when the processor 202 executes the computer program, it performs the following steps: reading a preset storage address from the BIOS image, the preset storage address including a public access area.

[0131] This application provides a system firmware boot device, including a memory 201 and a processor 202. The memory 201 stores a computer program, and when the processor 202 executes the computer program, it performs the following steps: reading a preset storage address from the BIOS image, the preset storage address including the server southbridge device.

[0132] This application provides a system firmware boot device, including a memory 201 and a processor 202. The memory 201 stores a computer program, and when the processor 202 executes the computer program, it performs the following steps: remotely booting the target system firmware image via BMC.

[0133] This application provides a system firmware boot device, including a memory 201 and a processor 202. The memory 201 stores a computer program, and when the processor 202 executes the computer program, it performs the following steps: executing a UEFI process.

[0134] Please see Figure 9 Another system firmware boot device provided in this application embodiment may further include: an input port 203 connected to the processor 202 for transmitting commands input from the outside to the processor 202; a display unit 204 connected to the processor 202 for displaying the processing results of the processor 202 to the outside; and a communication module 205 connected to the processor 202 for enabling communication between the system firmware boot device and the outside. The display unit 204 may be a display panel, a laser scanner, or the like; the communication methods used by the communication module 205 include, but are not limited to, Mobile High Definition Link (HML), Universal Serial Bus (USB), High Definition Multimedia Interface (HDMI), wireless connectivity: Wi-Fi, Bluetooth, Bluetooth Low Energy, and IEEE 802.11s-based communication technologies.

[0135] Of course, in practical applications, the various components in the system firmware boot device can be coupled together through a bus system. The bus system is used to enable communication and connection between these components. In addition to a data bus, a bus system can also include a power bus, a control bus, and a status signal bus, etc.

[0136] The memory in this application embodiment is used to store various types of data to support the operation of the electronic device. Examples of such data include any computer program used to operate on the electronic device.

[0137] It is understood that memory can be volatile or non-volatile, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM). The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memory.

[0138] The methods disclosed in the embodiments of this application can be applied to a processor or implemented by a processor. A processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above methods can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory. The processor reads the program in the memory and, in conjunction with its hardware, completes the steps of the aforementioned methods.

[0139] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a memory that stores a computer program. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it performs the following steps:

[0140] Perform initialization operations;

[0141] Read the preset storage address from the BIOS image. The preset storage address includes addresses outside the BIOS storage area.

[0142] The target system firmware image to be booted is determined based on the preset storage address;

[0143] Remotely boot the target system firmware image to boot the corresponding target system firmware.

[0144] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it performs the following steps: reading a preset storage address from a BIOS image, the preset storage address including the server's own memory.

[0145] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it performs the following steps: reading a preset storage address from a BIOS image, the preset storage address including persistent memory connected to the server.

[0146] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it performs the following steps: reading a preset storage address from a BIOS image, the preset storage address including a public access area.

[0147] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it performs the following steps: reading a preset storage address from a BIOS image, wherein the preset storage address includes a server southbridge device.

[0148] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it performs the following steps: remotely booting the target system firmware image via BMC.

[0149] This application provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it performs the following steps: executing a UEFI process.

[0150] The computer-readable storage media involved in this application include random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or any other form of storage media known in the art.

[0151] In the several embodiments provided in this application, it should be understood that the disclosed apparatus, terminal, and method can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0152] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0153] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0154] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0155] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0156] For descriptions of relevant parts in the system firmware booting apparatus, device, and computer-readable storage medium provided in this application's embodiments, please refer to the detailed description of the corresponding parts in the system firmware booting method provided in this application's embodiments; they will not be repeated here. Furthermore, parts of the technical solutions provided in this application that are consistent with the implementation principles of corresponding technical solutions in the prior art have not been described in detail to avoid excessive elaboration.

[0157] It should also be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0158] The above description of the disclosed embodiments enables those skilled in the art to make or use 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 system firmware booting method, characterized by, Applied to BIOS, including: Perform initialization operations; The system firmware image stored in the BIOS image is read from a preset storage address, which includes addresses outside the BIOS storage area. The preset storage address includes the server's own memory, external persistent memory, public access area, or server southbridge device. The system firmware image stored in the persistent memory is remotely updated via BMC or operating system network transmission. The target system firmware image to be started is determined based on the preset storage address; The target system firmware image is stored on the server PCH. The target system firmware image is remotely started via BMC to start the corresponding target system firmware. The target system firmware image is remotely executed through the debugging function in the PCH. When there are multiple Linux Boot firmware images, the required Linux Boot image is selected for startup through operating system software or server firmware. The relevant information about the startup operation during the startup process of the target system firmware is saved. The Linux Boot firmware image contains customized Linux drivers, kernel versions or startup parameters. During compilation, the BIOS image creates a separate module to execute the system firmware image via an INF file configuration. In this module, the preset storage address is written so that when the BIOS executes this module, the system firmware is executed from the preset storage address via StartImage. The UEFI process is executed; during the boot process of the target system firmware, the BIOS determines whether to execute the UEFI process through Setup control; or the operating system determines whether to execute the UEFI process through registers; or the BMC Web user interaction page controls whether to execute the UEFI process, so that the execution process of the UEFI process is under user control.

2. A system firmware boot device, characterized in that, Applied to BIOS, including: The first execution module is used to perform initialization operations; The first reading module is used to read a preset storage address from the BIOS image. The preset storage address includes an address outside the BIOS storage area. The preset storage address includes the server's own memory, external persistent memory, public access area, or server southbridge device. The system firmware image stored in the persistent memory is remotely updated via BMC or operating system network transmission. The first determining module is used to determine the target system firmware image to be started based on the preset storage address; The first boot module is used to store the target system firmware image on the server PCH, remotely boot the target system firmware image via BMC to start the corresponding target system firmware, and remotely execute the target system firmware image through the debugging function in the PCH; when there are multiple Linux Boot firmware images, the required Linux Boot image is selected for booting through operating system software or server firmware; saves relevant information about the boot operation during the boot process of the target system firmware; customizes Linux drivers, kernel versions or boot parameters in the Linux Boot firmware image; wherein, when the BIOS image is compiled, a separate module is created to execute the system firmware image through the configuration method of INF file. In this module, the preset storage address is written so that when the BIOS executes this module, the system firmware is executed from the preset storage address through StartImage; The second execution module is used to execute the UEFI process. During the boot process of the target system firmware, the BIOS determines whether to execute the UEFI process through Setup control; or determines whether to execute the UEFI process through registers in the operating system; or controls whether to execute the UEFI process through the BMC Web user interaction page, so that the execution process of the UEFI process is under user control.

3. A system firmware boot device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the system firmware boot method as described in claim 1 when executing the computer program.

4. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the system firmware boot method as described in claim 1.

Citation Information

Patent Citations

  • Starting method, device and equipment of embedded system and storage medium

    CN112732345A