Firmware Installation via Non-Operational Storage and Parallel Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Complex devices with multiple subsystems face challenges in efficiently updating firmware across all subsystems without risking corruption or interruption, particularly during the installation process.
Innovation Solution
The implementation of a non-operational storage area and an Early Boot Installer manager that downloads firmware bundles in parallel, allowing for resilient firmware updates by separating the installation process from the live firmware copies and using a version database to manage versions and determine necessary updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware is updated in place without a separate storage area, then the update process is simpler, but there is a high risk of corrupting live firmware copies and causing device interruptions
Solution Approach 1:
The storage system is segmented into distinct areas: a first storage area for live firmware copies and a second storage area for firmware updates. This segmentation allows independent management of operational and update firmware, preventing corruption of live firmware during update operations and enabling reliable firmware management.
2Productivity
If firmware updates are performed sequentially across subsystems, then each subsystem is updated carefully, but the total update time increases significantly
Solution Approach 1:
Firmware updates are downloaded and stored in the second storage area before being installed on subsystems. The Early Boot Installer manager prepares the update environment in advance, allowing parallel installation across multiple subsystems while maintaining safety through pre-validation and controlled deployment.
Solution Approach 2:
The Early Boot Installer manager acts as an intermediary between the firmware update storage and the subsystems. It coordinates the parallel installation process, managing multiple firmware installations simultaneously while ensuring each subsystem receives valid firmware, thus maintaining reliability while improving productivity.
3Reliability
If the device boots normally during firmware installation, then system operations continue, but the firmware installation may be interrupted causing corruption
Solution Approach 1:
The system performs preliminary actions by downloading and storing firmware updates in the second storage area before the device needs to reboot. This advance preparation ensures that when the device does reboot for installation, the firmware is already ready and validated, preventing interruptions and corruption while minimizing downtime.
Solution Approach 2:
The dual storage area structure provides a cushioning mechanism where the second storage area serves as a buffer for firmware updates. This allows the system to prepare updates in advance and isolate them from the live firmware, protecting against installation interruptions and ensuring integrity while managing the necessary device downtime efficiently.
Data Source
AI summary
A firmware bundle is download to a non-operational storage area without changing a live copy of firmware in a device. The firmware bundle is downloaded in order to reboot the device to deploy one or more downloaded firmware packages from the non-operational storage area to the device, launch an Early Boot Installer manager to spawn and monitor the status of one or more Early Boot Installer processes contained in the firmware bundle download, determine in parallel whether a firmware install to one or more subsystems of the device is desire, and install the downloaded firmware package in parallel to one or more subsystems of the device.