BMC Firmware Recovery via Boot Loader Flash Reprogramming
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing server technologies face challenges in efficiently recovering baseboard management controller (BMC) firmware without disassembling flash memories when both active and backup BMC firmware fail, impacting maintainability and reliability.
Innovation Solution
A method and system for automatically recovering BMC firmware by starting a boot loader from a flash memory, obtaining backup firmware from an external storage device through the boot loader, and burning it to a flash memory, enabling its startup without server disassembly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If BMC firmware is stored in flash memory for automatic startup, then system reliability is improved, but when firmware fails, manual disassembly is required for recovery which reduces ease of repair
Solution Approach 1:
The patent implements a preliminary action by pre-burning a boot loader into a dedicated flash memory (first flash memory) before any firmware failure occurs. This boot loader is prepared in advance to automatically execute when BMC firmware startup fails, enabling automatic recovery without manual intervention. The boot loader contains pre-configured functionality to detect firmware failures and initiate recovery procedures, thus resolving the contradiction by maintaining reliability through flash memory storage while eliminating the need for manual disassembly during repair.
Solution Approach 2:
The patent implements self-service by enabling the BMC system to automatically detect firmware startup failures and recover without external human intervention. The boot loader automatically detects when BMC firmware cannot start, retrieves backup firmware from an external storage device, and performs the burning process autonomously. This self-service mechanism resolves the technical contradiction by maintaining system reliability through flash memory storage while achieving ease of repair through automatic self-recovery capabilities.
2Reliability
If backup BMC firmware is stored in a separate flash memory, then fault tolerance is improved, but device complexity increases due to multiple flash memories
Solution Approach 1:
The patent applies segmentation by dividing the flash memory storage into distinct functional segments: a first flash memory dedicated to storing the boot loader, and a second flash memory dedicated to storing BMC firmware. This segmentation allows each component to have a specialized function, improving fault tolerance through clear separation of concerns while managing complexity through organized, purpose-specific storage allocation. The boot loader and BMC firmware operate independently in their respective segments, enabling reliable recovery without requiring complex cross-contamination handling.
Solution Approach 2:
The patent implements multi-functionality by designing the boot loader with universal capabilities to handle various BMC firmware failure scenarios. The boot loader can detect different types of firmware startup failures, retrieve backup firmware from external storage devices through multiple interfaces, and perform burning operations to restore functionality. This universal boot loader design achieves fault tolerance across multiple failure modes while avoiding the need for separate specialized recovery mechanisms for each failure type, thus managing device complexity.
3Productivity
If automatic firmware recovery is implemented through boot loader, then productivity is improved, but device complexity increases due to additional boot loader component
Solution Approach 1:
The patent applies merging by integrating the recovery functionality directly into the boot loader component, combining the startup and recovery functions into a single unified element. The boot loader serves dual purposes: normally it facilitates BMC firmware startup, and when failure occurs, it automatically executes recovery procedures including detecting the failure, retrieving backup firmware from external storage, and burning the restored firmware. This merging of functions into one component achieves high recovery productivity while avoiding the complexity of adding separate dedicated recovery hardware or software modules.
Data Source
AI summary
The present disclosure discloses a fault recovery method. The method includes: in response to a server being powered on or reset, starting baseboard management controller firmware from one or more flash memories storing the baseboard management controller firmware; in response to a failure of the starting the baseboard management controller firmware from the flash memories, starting a boot loader from a flash memory in which the boot loader is burned; in response to the boot loader being successfully started, obtaining backup baseboard management controller firmware from an external storage device through the boot loader, and burning the backup baseboard management controller firmware to any one of the flash memories; and in response to the burning being completed, resetting the server, and enabling the flash memory to start the backup baseboard management controller firmware from the flash memory in which the backup baseboard management controller firmware is burned.