BIOS Storage Segmentation for Conflict-Free Firmware Reboot Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional BIOS code storage subsystem modifications in computing devices result in prolonged system unavailability due to conflicts between the BIOS and Baseboard Management Controller (BMC) when verifying integrity and scheduling memory repairs, leading to freezing or hanging issues.
Innovation Solution
Implement a separate BIOS code storage device and data storage device with distinct communication buses, allowing BIOS code storage device modifications to be performed during system initialization, rather than runtime, thereby avoiding simultaneous access conflicts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If BIOS modification is performed during runtime in System Management Mode, then memory repair operations can be scheduled, but system becomes unavailable and may freeze or hang due to BMC verification conflicts
Solution Approach 1:
The BIOS modification information is prepared and stored in the BIOS data storage device before the actual BIOS code storage device modification occurs. The system schedules memory repair operations in advance by storing modification information in a separate data storage area, then performs the actual modification during initialization rather than runtime, eliminating conflicts with BMC verification operations.
2Reliability
If BIOS code storage device is modified during runtime, then memory repair can be scheduled, but modification time is prolonged due to System Management Mode constraints
Solution Approach 1:
Modification information is prepared in advance and stored in the BIOS data storage device during runtime. The actual BIOS code storage device modification is deferred to initialization time when the system is restarting, which eliminates the prolonged System Management Mode constraint and reduces overall system unavailability.
Solution Approach 2:
The system performs BIOS modification during periodic initialization sequences rather than during continuous runtime operations. By scheduling modifications to occur during natural system restarts and initializations, the system minimizes disruption to operational availability while ensuring repairs are performed.
3Reliability
If separate BIOS code storage device and data storage device are used with distinct communication buses, then modification conflicts are avoided, but device complexity increases
Solution Approach 1:
The BIOS storage subsystem is segmented into two distinct components: a BIOS code storage device for storing executable BIOS code and a BIOS data storage device for storing modification information and configuration data. Each component has its own communication bus, which eliminates access conflicts during modification operations while maintaining manageable system architecture.
Data Source
AI summary
A BIOS code storage subsystem modification system includes a computing device having BIOS code storage device modification subsystem coupled to a BIOS storage system that includes a BIOS code storage device and a BIOS data storage device. The BIOS code storage device modification subsystem receives a BIOS code storage device modification interrupt and, in response, provides BIOS code storage device modification information in the BIOS data storage device. Subsequent to providing the BIOS code storage device modification information in the BIOS data storage device, the BIOS code storage device modification subsystem causes the computing device to perform a first reboot. During a first initialization of the computing device in response to the first reboot, a BIOS in the computing device identifies the BIOS code storage device modification information in the BIOS data storage device, and uses the BIOS code storage device modification information to modify the BIOS code storage device.