Live Firmware Activation in Memory Sub-Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional memory sub-systems require rebooting or restarting of the host system to obtain updated firmware parameters, which can significantly impact system availability and usability.
Innovation Solution
The memory sub-system is capable of booting in two modes: normal and restart modes, allowing it to store parameters in non-volatile memory and switch to updated firmware without reconfiguring with the host system, thus avoiding the need for rebooting or restarting the host system.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the memory sub-system reconfigures with the host system to obtain updated firmware parameters, then the firmware is updated, but the host system must be rebooted or restarted which reduces system availability
Solution Approach 1:
The memory sub-system stores firmware parameters in non-volatile memory during normal operation before a firmware update is needed. When updating firmware, the system retrieves these pre-stored parameters instead of reconfiguring with the host, eliminating the need for host reboot and maintaining system availability while enabling firmware updates
2Loss of time
If the memory sub-system stores parameters in non-volatile memory and boots in restart mode, then host system reboot is avoided, but the system must maintain two boot modes and parameter storage mechanisms
Solution Approach 1:
The boot process is segmented into two distinct modes: normal mode which communicates with the host system to obtain parameters, and restart mode which uses pre-stored parameters from non-volatile memory. This segmentation allows the system to choose the appropriate boot mode based on whether a firmware update is being performed, reducing host reboot time while managing complexity through clear mode differentiation
3Ease of operation
If the memory sub-system communicates with the host system during boot to obtain parameters, then the firmware can be updated, but the system requires host system reconfiguration which impacts usability
Solution Approach 1:
Firmware parameters are preliminarily stored in the memory sub-system's non-volatile memory during normal operation. When a firmware update is needed, the system boots in restart mode and retrieves these pre-stored parameters without requiring host system reconfiguration, thereby simplifying the firmware update process and eliminating host downtime while maintaining ease of operation
Data Source
AI summary
A memory system having memory components and a processing device to: communicate with a host system to obtain, from the host system, at least one host specified parameter during booting up of the host system; execute first firmware to process requests from the host system using the at least one host specified parameter, the requests including storing data into the memory components and retrieving data from the memory components; install second firmware while running the first firmware; store the at least one host specified parameter; and reboot into executing the second firmware using the at least one host specified parameter, without rebooting of the host system.