Storage Controller Firmware Checks for MCU Failure Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage devices face issues where microcontroller units incorrectly report errors for normal constituent elements, necessitating a solution to accurately determine microcontroller unit failures and recover them.
Innovation Solution
Implementing a storage system with a storage controller that performs first and second checks on the microcontroller unit's firmware code, using non-volatile memory to verify the microcontroller's status, and performs recovery when necessary, including checks on communication status, reset vectors, and firmware code matches.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the microcontroller unit monitors statuses of constituent elements and outputs abnormality signals, then error detection capability is improved, but false error reporting occurs when constituent elements are actually normal
Solution Approach 1:
The storage controller performs feedback verification by checking firmware codes and communication status of the microcontroller unit. When an abnormality signal is received, the storage controller executes a first check on firmware code integrity and a second check on communication status, then compares results with reference values stored in non-volatile memory to determine whether the abnormality is genuine or false.
Solution Approach 2:
The storage controller acts as an intermediary between the microcontroller unit and the host device. It intercepts abnormality signals from the microcontroller unit, performs verification checks through intermediate steps (firmware comparison, communication testing), and only reports to the host after confirming the abnormality is legitimate, thereby filtering out false errors.
2Measurement precision
If the storage controller performs multiple checks on firmware code and communication status, then false error identification is improved, but system complexity increases
Solution Approach 1:
Reference firmware codes and communication status values are pre-stored in non-volatile memory during manufacturing. When verification is needed, the storage controller simply compares current readings against these pre-prepared reference values, avoiding the need to perform complex analysis routines during operation and reducing real-time computational complexity.
3Ease of repair
If recovery operations are performed using firmware codes from non-volatile memory, then microcontroller unit recovery is improved, but data management complexity increases
Solution Approach 1:
A reference copy of the correct firmware code is maintained in the non-volatile memory portion of the storage device. When the microcontroller unit's firmware is suspected to be corrupted, the storage controller retrieves this stored copy and uses it to overwrite the potentially defective firmware in the microcontroller unit, enabling recovery without external intervention.
Data Source
AI summary
Some example embodiments provide a storage device including a non-volatile memory; a microcontroller unit configured to monitor statuses of constituent elements of the storage device and output an abnormality signal based on the constituent elements not being in a normal status; and a storage controller configured to perform a first check and a second check different from the first check on a first firmware code stored in the microcontroller unit in response to the abnormality signal and perform recovery by using a second firmware code stored in the non-volatile memory based on at least one of the first check and the second check having failed.