OTP Memory File Allocation Table Backwards Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
One-time programmable (OTP) or few-time programmable (FTP) memory technologies are not compatible with existing consumer electronic devices that use DOS FAT12/16 file systems, requiring firmware updates to work with these devices, which limits market compatibility and user convenience.
Innovation Solution
A method where a host allocates clusters from one end of the memory address range and a controller allocates from the other end, with allocation information recorded in volatile memory to update the File Allocation Table (FAT) in nonvolatile memory, allowing backwards compatibility without firmware upgrades, enabling OTP or FTP memories to work with existing devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If OTP or FTP memory technologies are used, then memory cost is reduced, but compatibility with existing consumer electronic devices is lost
Solution Approach 1:
The patent introduces a file system translation layer that acts as an intermediary between the OTP/FTP memory and the host device's file system. This translation layer converts the host's standard DOS FAT12/16 file system operations into operations compatible with OTP/FTP memory constraints, enabling compatibility without requiring firmware updates in host devices.
Solution Approach 2:
The patent segments the file system functionality into two parts: the standard DOS FAT12/16 file system interface that host devices expect, and the OTP/FTP-specific file system implementation that handles the actual memory operations. This segmentation allows the memory device to present a standard interface while internally managing OTP/FTP-specific constraints.
2Adaptability or versatility
If firmware updates are implemented to enable OTP/FTP memory compatibility, then compatibility is improved, but market availability is limited
Solution Approach 1:
The file system translation layer resides within the memory device itself, serving as a self-contained intermediary that eliminates the need for firmware updates in host devices. This approach expands market availability by allowing OTP/FTP memory to work with any standard DOS FAT12/16 compatible device without requiring coordination or updates across the ecosystem.
3Stability of the object's composition
If allocation information is stored only in nonvolatile memory, then data persistence is improved, but update capability is lost
Solution Approach 1:
The patent implements a preliminary action by maintaining allocation information in volatile memory before committing changes to nonvolatile memory. This allows the system to quickly update allocation information in response to host requests, and only persists changes to nonvolatile memory when appropriate, thereby enabling both rapid updates and data persistence.
Solution Approach 2:
The patent employs a dynamic allocation information storage strategy where allocation information is kept in volatile memory during active operations to enable rapid updates, and selectively transferred to nonvolatile memory for persistence. This dynamic approach allows the system to switch between speed (volatile) and persistence (nonvolatile) based on operational needs.
Data Source
AI summary
In a nonvolatile memory system, a host allocates clusters and records allocation information in a File Allocation Table that is stored in the nonvolatile memory. A controller separately allocates certain data and records allocation in a record in a volatile memory. File Allocation Table information provided to the host is modified according to the record in the volatile memory.