Shared Boot Memory to Reduce BIOS and BMC Inspection Time
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing computing systems face boot performance degradation due to prolonged firmware inspection processes, which increase boot time and result in significant downtime, especially in server environments, leading to increased costs and revenue loss.
Innovation Solution
Implementing a computing system with a single non-volatile memory module to store both BIOS and BMC firmware, utilizing a baseboard management controller (BMC) with an internal bus and root of trust to verify and manage firmware integrity, and employing an SPI simulator to emulate communication protocols, thereby reducing the need for redundant hardware and simplifying firmware update processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware is stored in separate non-volatile memory modules for BIOS and BMC, then firmware integrity can be verified through root of trust, but boot time increases due to repetitive inspection processes
Solution Approach 1:
The patent combines BIOS firmware and BMC firmware into a single non-volatile memory module, eliminating the need for separate verification processes. The root of trust verifies the entire firmware image once during manufacturing, and this verified image is then used by both BIOS and BMC, removing repetitive inspection steps that previously increased boot time.
Solution Approach 2:
The firmware integrity verification is performed in advance during the manufacturing process rather than during each boot operation. The root of trust validates the firmware image before it is programmed into the non-volatile memory, so that subsequent boot operations can proceed without repeating the verification process, thereby reducing boot time while maintaining reliability.
2Adaptability or versatility
If separate non-volatile memory modules are used for BIOS and BMC firmware, then firmware updates can be managed independently, but hardware complexity and connection requirements increase
Solution Approach 1:
The patent merges the storage of BIOS and BMC firmware into a single non-volatile memory module, reducing the number of hardware connections and components. This simplification is achieved while maintaining independent firmware update capability through software-based partitioning and version management within the unified memory space.
Solution Approach 2:
The single non-volatile memory module serves multiple functions: storing BIOS firmware, storing BMC firmware, and providing a unified verification target for the root of trust. This multi-functional approach eliminates the need for separate memory modules while maintaining the ability to manage different firmware types independently through software control.
3Reliability
If root of trust verifies boot firmware before system boot, then system security is enhanced, but boot performance degrades due to increased inspection time
Solution Approach 1:
The root of trust verification is moved to the manufacturing process, occurring before the firmware is programmed into the non-volatile memory. This preliminary verification ensures system security is maintained while eliminating the need for repeated verification during boot operations, thereby preserving boot performance.
Solution Approach 2:
The patent creates a verified copy of the firmware image during manufacturing that is then programmed into the non-volatile memory. The root of trust validates this copy once during production, and the system boots from this pre-verified firmware, eliminating the need for repeated security checks during boot while maintaining system security.
Data Source
AI summary
A computing system includes a central processing unit (CPU), a baseboard management controller (BMC) coupled to the CPU via a first communication protocol, and a boot non-volatile memory. The BMC includes a first communication protocol controller, a BMC memory, a root of trust, and an internal BMC bus. The internal BMC bus is configured to communicatively couple the BMC memory, the first communication protocol controller, and the root of trust. The boot non-volatile memory is coupled to the BMC via the first communication protocol controller. The boot non-volatile memory is configured to store basic input/output system (BIOS) firmware and/or BMC firmware.