Low-impact firmware update via microcontroller task offloading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Firmware updates on multi-core systems often require system reboots, leading to significant downtime and disruption of service, making the process risky and expensive for datacenter operations.
Innovation Solution
A low-impact firmware update method that offloads system management tasks and interrupt handling from the targeted microcontroller to another microcontroller, allowing for secure, rapid updates without disrupting service by using a security entity to authenticate and coordinate the update without processing cycles from host software.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If firmware update is performed using conventional method, then firmware can be updated, but system reboot is required causing service disruption
Solution Approach 1:
The system is segmented into multiple microcontrollers (first microcontroller for firmware update, second microcontroller for task offloading). This segmentation allows the firmware update to occur on one microcontroller while another continues to handle system management tasks, enabling updates without complete system reboot and thus maintaining service continuity while minimizing downtime.
Solution Approach 2:
System management tasks and interrupt handling are offloaded to the second microcontroller before the firmware update on the first microcontroller. This preliminary action ensures that critical functions are already handled by the second microcontroller, so when the first microcontroller reboots for the update, service disruption is minimized or eliminated.
2Reliability
If firmware update is performed frequently, then security issues and bugs can be addressed, but service disruption increases
Solution Approach 1:
By segmenting the microcontroller system into update-capable and task-handling components, the patent enables frequent firmware updates to be performed on the first microcontroller without requiring repeated full system reboots. The second microcontroller maintains system management functions during updates, allowing security patches to be applied frequently without proportionally increasing service disruption.
Solution Approach 2:
The second microcontroller continues to perform system management tasks and interrupt handling continuously during the firmware update process on the first microcontroller. This continuity of useful action ensures that critical system functions remain operational throughout frequent update cycles, maintaining service availability while security issues are addressed.
3Device complexity
If system management tasks are handled by the same microcontroller being updated, then simpler architecture is used, but update requires complete system reboot
Solution Approach 1:
The patent divides the microcontroller system into separate functional units: the first microcontroller dedicated to firmware updates and the second microcontroller dedicated to system management tasks. This segmentation increases architectural complexity but eliminates the need for complete system reboots during updates, reducing reboot time and enabling faster firmware deployment.
Solution Approach 2:
The second microcontroller acts as an intermediary that takes over system management tasks and interrupt handling during the firmware update process. This intermediary allows the first microcontroller to be completely rebooted for updates without losing system management capability, thus reducing reboot time and enabling more frequent updates.
Data Source
AI summary
Disclosed are techniques for performing a low-impact firmware update to a first microcontroller. In an aspect, a security entity communicatively coupled to the first microcontroller receives an update to firmware of the first microcontroller, authenticates the update to the firmware of the first microcontroller to prevent a security-related rollback, offloads system management tasks and interrupt handling from the first microcontroller to at least a second microcontroller communicatively coupled to the first microcontroller, coordinates installation of the update to the firmware of the first microcontroller without taking processing cycles from host software, and restores, to the first microcontroller, system management states occurring after the system management tasks and interrupt handling are offloaded from the first microcontroller.