Flash Memory EEPROM Emulation with Redundant Blocks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional flash memory systems face challenges in emulating EEPROM functionality due to flash memory block failures, which can result in data loss and system failure, as they cannot handle bit shorts or block disabilities effectively.
Innovation Solution
The implementation of a redundant and spare block system within flash memory, where EEPROM data is duplicated across multiple blocks, allowing for seamless data recovery and continuation of operations even in case of block failures, using an EEPROM emulation module to manage data distribution and swapping between Active, Alternate, and Redundant/Spare blocks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If flash memory is used to emulate EEPROM functionality, then cost and size requirements are reduced, but data loss occurs when flash block failures happen
Solution Approach 1:
The flash memory is divided into multiple functional blocks: active blocks for current EEPROM emulation operations, alternate blocks for standby operations, and spare blocks for replacement when failures occur. This segmentation allows the system to isolate failures to specific blocks while maintaining overall system functionality through redundant blocks.
Solution Approach 2:
Different blocks are assigned different roles based on their operational status and health condition. Healthy blocks serve as active or alternate blocks for normal operations, while degraded or failed blocks are designated as spare blocks for replacement purposes. This local quality differentiation optimizes the use of available memory resources.
2Reliability
If conventional EEPROM emulation techniques are used, then flash memory restrictions are accepted, but catastrophic data loss occurs when bit failures short the word line
Solution Approach 1:
The system performs preliminary actions by continuously monitoring flash block health status and proactively identifying potential failures before they cause data loss. When a block shows signs of degradation or failure, the system switches to alternate blocks in advance, preventing catastrophic data loss when the failed block becomes inoperative.
Solution Approach 2:
Redundant alternate blocks and spare blocks are prepared in advance as cushioning against potential failures. These backup blocks remain ready to assume operations if the active block fails, providing a safety buffer that prevents data loss without requiring complex real-time recovery mechanisms.
3Duration of action of stationary object
If flash memory blocks are used for EEPROM emulation, then silicon area is reduced, but wear from extensive program and erase cycles causes latent defects
Solution Approach 1:
When a flash block reaches its endurance limit or develops latent defects from extensive program and erase cycles, the system discards the degraded block from active service and recovers it as a spare block. This allows the system to continue operations using healthy alternate blocks while the degraded block can be refreshed or replaced, effectively extending the overall system endurance.
Data Source
AI summary
A defect resistant EEPROM emulator (110) uses one or more redundant and/or spare blocks (213) in addition to active and alternate blocks (211, 212) and stores a duplicate copy of EEPROM data records either in the active and redundant blocks or in duplicate rows in the active block to ensure that EEPROM emulation can continue without data loss in the event a catastrophic failure occurs within a block.