Memory Read-Write Verification Method for Margin Check Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing memory read-write verification methods require repeated system-level verifications and rewrites, leading to increased system consumption and a risk of overwriting data.
Innovation Solution
A memory read-write verification method that performs margin verification on all input/output operations, determines the need for a write operation based on the verification results, and executes the write operation only on failing IO, followed by a subsequent verification to confirm the write success.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If margin verify is performed on all IO after each write operation, then write reliability is improved, but system consumption increases and verify efficiency decreases
Solution Approach 1:
The patent applies local quality by performing margin verify selectively on only those IO that fail the preliminary verify check, rather than verifying all IO uniformly. This differentiated verification approach ensures reliable detection of write failures while reducing unnecessary verification operations on successful writes, thereby lowering system consumption.
Solution Approach 2:
The patent implements partial action by conducting a preliminary margin verify on all IO first, then performing a second verify only on the subset of IO that failed the initial check. This partial verification strategy avoids the excessive action of verifying all IO twice, optimizing the balance between reliability and efficiency.
2Reliability
If rewrite operation is performed whenever write fails, then data accuracy is improved, but verify efficiency decreases and over write risk increases
Solution Approach 1:
The patent employs feedback mechanisms where the result of the preliminary margin verify directly determines whether a rewrite operation is needed. The verify result feeds back into the decision-making process, allowing the system to skip unnecessary rewrite operations when the initial write is successful, thereby maintaining data accuracy while improving verify efficiency.
Solution Approach 2:
The patent performs a preliminary margin verify before the actual write operation to predict potential failures. This preliminary action allows the system to prepare for possible rewrite operations only when necessary, avoiding unnecessary rewrites and reducing the risk of overwriting correct data.
3Reliability
If entire system performs Margin 0 or Margin 1 verify, then verification completeness is improved, but device complexity increases
Solution Approach 1:
The patent segments the verification process into two distinct stages: a preliminary margin verify that checks all IO, and a subsequent targeted verify that only checks IO failing the first stage. This segmentation allows the system to maintain verification completeness while reducing the complexity of any single verification operation, as each stage can be optimized independently.
Data Source
AI summary
Disclosed is a memory read-write verification method. Firstly, margin verify is carried out on all input/output (IO) of the memory according to input data, readout data corresponding to each piece of the IO is acquired according to a verify result, and whether to execute a write operation on the IO corresponding to the readout data is determined according to the readout data. Then, the write operation is executed on IO on which the write operation is required to be executed. Finally, the margin verify is carried out again after the write operation is completed, and whether write-in of corresponding IO succeeds is determined according to a verify result. Thus, rewrite-in can be avoided, and verify efficiency can be improved.