Read Status Controller for Flash Memory Error Handling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing systems for controlling flash memory accesses require the host processor to continuously check 'read status' responses after each 'page write' operation, leading to degraded system performance and excessive bandwidth usage, as the processor must stop other operations to issue and read these responses, even for rare errors.
Innovation Solution
A separate read status controller (RSC) monitors the memory device and issues 'read status' commands, reads responses, and automatically sends interrupts to the host processor when necessary, allowing the host processor to attend to other system operations and reducing the need for continuous intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the host processor continuously checks read status responses after each page write operation, then the system can detect errors, but the host processor must stop other operations leading to degraded system performance
Solution Approach 1:
The patent divides the status monitoring function into a separate dedicated controller module that operates independently from the host processor. This segmentation allows the host processor to focus on main computational tasks while the dedicated controller handles status checking and error detection, resolving the contradiction between reliability and productivity.
Solution Approach 2:
The patent introduces a dedicated controller as an intermediary between the host processor and the flash memory device. This intermediary handles the continuous status monitoring and error detection tasks, allowing the host processor to maintain high productivity while the intermediary ensures reliable error detection through continuous monitoring.
2Reliability
If the host processor issues read status commands after each page write, then write operation success can be determined, but excessive bandwidth is required leading to inefficient resource usage
Solution Approach 1:
The patent segments the bandwidth-consuming status monitoring function from the host processor and assigns it to a dedicated controller. This dedicated controller handles the continuous read status commands and verification traffic, preventing excessive bandwidth consumption from impacting the host processor's resource usage and maintaining efficient system-wide bandwidth utilization.
Solution Approach 2:
The dedicated controller performs self-service by autonomously handling status verification and error detection without requiring host processor intervention. The controller independently issues read status commands, analyzes responses, and manages error conditions, thereby reducing the bandwidth overhead on the host processor while maintaining reliable write operation verification.
3Reliability
If the host processor is diverted to service memory read status operations almost continuously, then status monitoring is maintained, but overall system performance degrades dramatically
Solution Approach 1:
The patent segments the continuous status monitoring function into a separate dedicated controller that operates independently from the host processor. This dedicated controller maintains continuous monitoring capability while the host processor remains free for other productive operations, resolving the contradiction between maintaining continuous monitoring and preserving overall system performance.
Solution Approach 2:
The dedicated controller acts as an intermediary that handles the continuous status monitoring workload. This intermediary maintains reliable continuous monitoring of memory operations while preventing the host processor from being diverted, thereby maintaining both monitoring reliability and overall system productivity.
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
A controller in a processing system can detect programmable bit sequences sent from a host processor to an external device, such as a memory, indicating whether a response from the external device needs to be read. The controller can also read a response from the external device and act appropriately, e.g., determine if an error has occurred by comparing the device's actual response to one or more programmably determined responses. Upon reading a particular response, e.g., a response indicating an error, the controller can issue an interrupt request to the host processor for further action. The controller can also track which external device access caused a particular response to occur.