Abstract: In one aspect, a system includes a service processor (SP), having a processor, a non-volatile memory and a communication interface. The SP receives a component information of components of a host computer from a basic input/output system (BIOS) being executed at a central processing unit (CPU) of the host computer through the communication interface, and stores the received component information in the non-volatile memory. When the SP receives an instruction to display a physical layout of the components of the host computer, the SP retrieves the component information for each of the components stored in the non-volatile memory, and generates corresponding display information for each of the components based on the retrieved component information. Then the SP may send the display information to a remote management computer to display a graphical diagram of the physical layout on a display device at the remote management computer.

Abstract: Certain aspects direct to systems and methods of BIOS failover update with a service processor (SP) having direct serial peripheral interface (SPI) access to a basic input/output system (BIOS) chip of a host computer. In certain embodiments, the SP receives a failover backup image from a BIOS being executed at a CPU of the host computer through a system interface, and stores the failover backup image in the volatile memory. Then the SP monitors operation of the BIOS by receiving, from the BIOS, a notification signal. When the SP detects an error in the operation of the BIOS based on the notification signal, the SP sends a copy of the failover backup image to the BIOS chip of the host computer through the SPI to replace a current BIOS image stored in the BIOS chip of the host computer with the copy of the failover backup image.

Abstract: In certain aspects, a system for out-of-band configuring BIOS setting data (BIOSSD) includes a host computer and a service processor (SP). The SP stores a BIOSSD collection and a human interface data (HID) collection. The HID collection includes questions for data of the BIOSSD collection and corresponding options for each question. When a remote management computer sends to the SP an information request, the SP retrieves the HID collection and transmits the questions and the corresponding options to the remote management computer. In response to a command indicating a selected corresponding option, the SP changes corresponding data of the BIOSSD collection according to the command. When the BIOS executed at the host computer issues a BIOSSD update request to the SP, the SP transmits a copy of the BIOSSD collection to the BIOS chip of the host computer to replace the BIOSSD collection stored in the BIOS chip.

Abstract: Certain aspects direct to BIOS update with a service processor (SP) without access through a serial peripheral interface (SPI). In certain embodiments, the system includes a SP, which includes a processor, a non-volatile memory, a volatile memory and a system interface. The SP receives a BIOS image from a remote management computer, and stores the BIOS image in the volatile memory. When the SP receives, from a BIOS executed at a central processing unit (CPU) of a host computer through the system interface, a request for the BIOS image, the SP sends a copy of the BIOS image in response to the request for the BIOS image to the host computer through the system interface such that the BIOS executed at the CPU of the host computer replaces a current BIOS image stored in a BIOS chip with the copy of the BIOS image.

Abstract: Certain aspects direct to systems and methods of BIOS failover update with a service processor (SP) having direct serial peripheral interface (SPI) access to a basic input/output system (BIOS) chip of a host computer. In certain embodiments, the SP receives a failover backup image from a BIOS being executed at a CPU of the host computer through a system interface, and stores the failover backup image in the volatile memory. Then the SP monitors operation of the BIOS by receiving, from the BIOS, a notification signal. When the SP detects an error in the operation of the BIOS based on the notification signal, the SP sends a copy of the failover backup image to the BIOS chip of the host computer through the SPI to replace a current BIOS image stored in the BIOS chip of the host computer with the copy of the failover backup image.

Abstract: Certain aspects direct to basic input/output system (BIOS) failover update with a service processor (SP). In certain embodiments, the system includes a host computer and a SP. A CPU of the host computer loads and executes a current BIOS image stored in a BIOS chip to a memory as a BIOS instance. The SP receives, from the executed BIOS instance at the host computer, a BIOS image as a failover backup image, and stores the failover backup image in the volatile memory of the SP. When an error occurs at the host computer, the executed BIOS instance sends a request for the failover backup image to the SP. In response, the SP sends a copy of the failover backup image to the host computer such that the executed BIOS instance may replace the current BIOS image stored in the BIOS chip with the copy of the failover backup image.

Abstract: Certain aspects of the present disclosure relate to a system for replicating BIOS setting data (BIOSSD) across computers. The system includes a plurality of computers, and each computer is connected to a service processor (SP). Each computer includes a BIOS chip, which stores a first BIOSSD collection. The SP stores a second BIOSSD collection. When the first BIOSSD collection is newer, the SP receives a copy of the first BIOSSD collection from the computer to replace the second BIOSSD collection. When the second BIOSSD collection is newer, the SP transmits a copy of the second BIOSSD collection to the computer to replace the first BIOSSD collection in the BIOS chip. A remote management may request and obtain from the SP the updated second BIOSSD collection such that the remote management computer may send the copy the updated second BIOSSD collection to other SP's for update.

Abstract: Methods, systems, apparatus, and computer-readable media for dynamically updating a computer system and firmware image utilizing an option ROM (“OPROM”) data structure. When a hardware configuration of a computer system is modified, a corresponding OPROM within the firmware image is modified. An OPROM data structure is created in a firmware image. Each data structure contains identification data corresponding to the data structure as well as an OPROM entry for each OPROM within the firmware image. Each OPROM entry has identification data pointing to the corresponding OPROM and identification data corresponding to the OPROM and associated hardware device. Firmware program modules utilize the OPROM data structure to identify the correct OPROMs for use with the computer system hardware configuration. An application searches for a unique signature associated with the OPROM data structure and modifies OPROM entries as hardware devices and associated OPROMs are added to and removed from the computer system.

Abstract: Methods, systems, apparatus, and computer-readable media for customizing a computer system firmware image utilizing a firmware configuration data structure. At least one firmware configuration data structure is created in a firmware image. Each data structure contains configuration data stored within a data field. A data structure signature identifying the data structure is stored within a data field of the data structure. A pointer to the configuration data within the data structure is stored in at least one firmware program module. An application may search for a firmware configuration data structure according to the data structure signature and content signatures corresponding to specific data entries, retrieve the applicable data structure and data entry, and store modifications to data stored therein.

Abstract: Methods, systems, apparatus, and computer-readable media for dynamically updating a computer system and firmware image utilizing an option ROM (“OPROM”) data structure. When a hardware configuration of a computer system is modified, a corresponding OPROM within the firmware image is modified. An OPROM data structure is created in a firmware image. Each data structure contains identification data corresponding to the data structure as well as an OPROM entry for each OPROM within the firmware image. Each OPROM entry has identification data pointing to the corresponding OPROM and identification data corresponding to the OPROM and associated hardware device. Firmware program modules utilize the OPROM data structure to identify the correct OPROMs for use with the computer system hardware configuration. An application searches for a unique signature associated with the OPROM data structure and modifies OPROM entries as hardware devices and associated OPROMs are added to and removed from the computer system.

Abstract: Methods, systems, apparatus, and computer-readable media for customizing a computer system firmware image utilizing a firmware configuration data structure. At least one firmware configuration data structure is created in a firmware image. Each data structure contains configuration data stored within a data field. A data structure signature identifying the data structure is stored within a data field of the data structure. A pointer to the configuration data within the data structure is stored in at least one firmware program module. An application may search for a firmware configuration data structure according to the data structure signature and content signatures corresponding to specific data entries, retrieve the applicable data structure and data entry, and store modifications to data stored therein.

Abstract: A method, system, apparatus, and computer-readable medium for exchanging data between an application program and a firmware in a computer system having multiple CPUs are provided. According to the method, an application program stores an input parameter for the firmware program in a register of the CPU on which it is executing. Data is also stored in a register of the CPU that identifies the CPU as having generated a SMI. The application program then generates a software SMI. In response to the SMI, a SMM dispatcher executing within the SMM causes the current contents of all the registers of the CPUs to be saved. The SMM dispatcher then identifies the CPU that generated the SMI by searching the saved register contents to locate the data stored by the application program that identifies the CPU as having generated the software SMI. Once the CPU has been identified, the input parameter can be retrieved from the saved register contents for the identified CPU.