Embedded Controller Boot Firmware Restoration via SPI Flash Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional boot recovery systems for information handling systems are inconvenient, complex, and unable to restore a damaged boot block, often requiring user intervention, additional hardware, or chipset-dependent methods, and are not effective in restoring the entire boot firmware region within Flash memory.
Innovation Solution
The system configures a Flash memory device to store EC application firmware, boot firmware, and backup boot firmware, allowing an embedded controller to directly access the Flash memory via a Serial Peripheral Interface bus during the boot process, enabling the restoration of boot firmware without user intervention, additional hardware, or chipset dependencies.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional boot recovery systems store recovery BIOS image in internal or external storage devices, then the damaged main BIOS image can be replaced, but user intervention is required and the system becomes complex with additional hardware dependencies
Solution Approach 1:
The system performs automatic boot recovery without user intervention by having the embedded controller detect BIOS corruption and automatically restore from backup stored in Flash memory during the boot process
Solution Approach 2:
The Flash memory device serves multiple functions: storing EC application firmware, boot firmware, and backup boot firmware, eliminating the need for separate storage devices for recovery images
2Reliability
If conventional boot recovery systems use external storage devices for recovery BIOS image, then recovery is possible, but the system requires additional hardware and manual insertion of storage devices
Solution Approach 1:
The recovery BIOS image is merged with the main BIOS image storage location in the same Flash memory device, eliminating the need for separate external storage devices while maintaining full recovery capability
Solution Approach 2:
The recovery functionality is extracted from external storage dependencies and integrated into the embedded controller with local backup storage, removing the need for external hardware
3Reliability
If the boot block is stored in ROM, then it provides reliable boot code, but it cannot be restored if damaged and requires service center intervention
Solution Approach 1:
A backup copy of the boot block is prepared in advance in the Flash memory device, allowing automatic restoration if the primary boot block in ROM becomes damaged without requiring service center intervention
4Reliability
If the entire boot firmware region is restored, then complete system reliability is achieved, but conventional systems can only restore partial BIOS regions
Solution Approach 1:
The embedded controller is designed with universal access capability to the entire boot firmware region in Flash memory, allowing restoration of any or all regions rather than being limited to specific BIOS images
Data Source
AI summary
An information handling system (IHS) may include a platform controller hub (PCH), an embedded controller (EC) configured to execute a boot block stored in ROM to initiate a boot process for the IHS, a Flash memory device configured to store EC application firmware, boot firmware and backup boot firmware, which is substantially identical to the boot firmware, and an SPI bus that directly connects the EC to the Flash memory device during a portion of the boot process when the PCH is in reset. The EC uses the SPI bus to access the Flash memory device, retrieve the EC application firmware stored therein, store a local copy of the EC application firmware in internal RAM and execute the local copy of the EC application firmware while the PCH is in reset. The EC application firmware stored in RAM includes boot recovery firmware, which may be executed by the EC to restore the boot firmware if the boot firmware is damaged or corrupt.