Non-Volatile Memory Configuration Data Integrity via Block Redundancy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing non-volatile semiconductor memory devices face reliability issues during Multiple Times Program (MTP) configuration operations due to potential data loss from sudden power drops or faulty blocks, which can lead to performance or security vulnerabilities, especially during system boot when default configuration settings cannot be changed before booting.
Innovation Solution
The solution involves using two or more blocks to store non-volatile configuration settings data, with old data retained until new data is written, and implementing additional flow control to ensure data integrity by marking valid blocks and removing faulty ones, allowing only good blocks to store configuration data and adding new blocks as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If non-volatile configuration settings data is stored in a single block, then device complexity is reduced, but reliability deteriorates due to potential data loss from sudden power drops or bad blocks
Solution Approach 1:
The configuration storage is divided into multiple blocks (first block and second block) instead of using a single block. This segmentation allows the system to distribute configuration data across multiple storage locations, preventing single-point failures and enabling redundancy for improved reliability.
Solution Approach 2:
Each block is assigned a specific role in the configuration storage hierarchy. The first block stores default configuration data while the second block stores updated configuration data. This local quality differentiation allows the system to maintain both old and new configuration versions with distinct functional characteristics.
2Reliability
If old configuration data is retained until new data is written, then reliability is improved by preventing data loss, but device complexity increases due to additional flow control requirements
Solution Approach 1:
The system performs preliminary validation and preparation before writing new configuration data. The configuration update process includes verifying data integrity, preparing the target block, and ensuring proper timing sequences. This preliminary action prevents premature overwriting and ensures data integrity throughout the transition.
Solution Approach 2:
The system implements feedback mechanisms to monitor the configuration writing process. Status flags and verification procedures provide continuous feedback on whether the write operation is complete and successful. This feedback loop allows the system to detect and correct potential issues before they compromise data integrity.
3Reliability
If only good blocks are used to store configuration settings data, then reliability is improved, but device complexity increases due to block list management
Solution Approach 1:
The system automatically monitors and manages the health status of storage blocks without external intervention. Bad block detection and identification procedures continuously assess block integrity, and the system self-adjusts by removing failed blocks from the active configuration list. This self-service approach maintains reliability while minimizing the need for complex external management.
4Reliability
If multiple blocks are used to store configuration data, then reliability is improved during MTP operations, but manufacturing complexity increases
Solution Approach 1:
The multiple blocks are designed with universal structure and function, allowing them to be used interchangeably for configuration storage. Each block can serve as either the primary or backup configuration storage location depending on its current validity status. This multi-functionality simplifies manufacturing by using identical block structures for different purposes throughout the device lifecycle.
Data Source
AI summary
A method provides the capability to maintain a configuration settings data image stored by a non-volatile memory device. The configuration settings data image can be multiple times programmed (MTP) without sacrificing reliability of the semiconductor device in the event of spurious power fluctuations, intermittent or bad memory storage blocks storing the configuration settings data image.