Separate Storage of BIOS Debug Components
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The limited capacity of SPI Flash memory in computer systems restricts the storage of updated BIOS debug messages and debug file references, necessitating costly motherboard rework and potential disruptions in debugging and system maintenance, especially as firmware requirements become more sophisticated.
Innovation Solution
Implementing a system where supplemental BIOS components, such as debug messages and UEFI drivers, are stored separately from the main BIOS firmware on external non-volatile storage, allowing them to be selectively loaded when needed, thereby reducing the required SPI Flash memory capacity and enabling debugging without hardware updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If debug strings and debug file references are embedded in the firmware code during build time, then debugging capability is improved, but security is worsened and SPI Flash memory capacity is consumed
Solution Approach 1:
The firmware is segmented into two parts: the core BIOS code stored in SPI Flash memory and the debug strings stored in a separate external file. This segmentation allows the core firmware to remain small and secure while debugging capabilities are preserved through external access to debug strings.
Solution Approach 2:
Debug strings and debug file references are extracted from the firmware binary and stored in a separate external file rather than being embedded in the BIOS code. This extraction reduces the SPI Flash memory requirement and improves security by removing sensitive debug information from the firmware image.
2Ease of manufacture
If SPI Flash memory capacity is reduced to 16 MB to reduce system cost, then manufacturing cost is improved, but debugging capability is worsened
Solution Approach 1:
Debug strings are extracted from the firmware and stored externally, allowing the SPI Flash memory to be reduced to 16 MB while preserving full debugging capability through external file access.
Solution Approach 2:
An external file serves as an intermediary between the BIOS code and debug strings, allowing the small 16 MB SPI Flash to store only the essential BIOS code while debug information is accessed from the external file during runtime.
3Ease of operation
If a larger capacity SPI Flash memory part is installed to accommodate debug mode BIOS, then debugging capability is improved, but manufacturing cost is worsened
Solution Approach 1:
Debug strings are extracted and stored in a separate external file rather than being included in the BIOS firmware, allowing the use of smaller, less expensive SPI Flash memory parts while maintaining full debugging capability.
4Reliability
If debug strings are removed from firmware to improve security, then security is improved, but debugging capability is worsened
Solution Approach 1:
Debug strings are extracted from the firmware binary and stored in a separate external file, improving security by removing sensitive information from the firmware image while preserving debugging capability through external access.
Solution Approach 2:
An external file acts as an intermediary that provides debug strings to the BIOS at runtime without requiring them to be embedded in the firmware, thus maintaining security while enabling debugging.
Data Source
AI summary
Systems and methods are provided for supporting use of system BIOS components (e.g., such as BIOS debug messages, debugger firmware, UEFI drivers, etc.) that are stored separately from the remainder of system BIOS firmware for an information handling system. The system BIOS components may represent only a portion of the total BIOS firmware, and may be selectively retrieved and loaded from the separate storage into system memory when needed by the system BIOS for operating purposes (e.g., such as debugging operations).