MD2534-D2G-X-P SanDisk, MD2534-D2G-X-P Datasheet - Page 36

• Manufacturer Part Number: MD2534-D2G-X-P
• Description: IC MDOC H3 2GB FBGA
• Manufacturer: SanDisk

Specifications of MD2534-D2G-X-P

• Format - Memory: FLASH
• Memory Type: FLASH - Nand
• Memory Size: 2G (256M x 8)
• Interface: Parallel
• Voltage - Supply: 1.65 V ~ 1.95 V, 2.5 V ~ 3.6 V
• Operating Temperature: -40°C ~ 85°C
• Package / Case: 115-TFBGA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Speed: -

6.3.4 Power Failure Management
Embedded TrueFFS uses algorithms based on “erase after write” instead of "erase before write" to
ensure data integrity during normal operation and in the event of a power failure. Used areas are
reclaimed for erasing and writing the flash management information into them only after an
operation is complete. This procedure serves as a check on data integrity.
The “erase after write” algorithm is also used to update and store mapping information on the
flash memory. This keeps the mapping information coherent even during power failures. The only
mapping information held in RAM is a table pointing to the location of the actual mapping
information. This table is reconstructed during power-up or after reset from the information stored
in the flash memory.
To prevent data from being lost or corrupted, Embedded TrueFFS uses the following
mechanisms:
• When writing, copying, or erasing the flash device, the data format remains valid at all
• A data sector cannot exist in a partially written state. The operation is either successfully
6.3.5 Error Detection/Correction
Embedded TrueFFS implements a unique Error Correction Code (ECC) algorithm to ensure data
reliability. Refer to Section 3.5 for further information on the EDC/ECC mechanism.
6.3.6
In addition to standard storage device functionality, the DOC driver provides extended
functionality. This functionality goes beyond simple data storage capabilities to include features
such as: formatting the media, read/write protection, boot partition(s) access and other options.
This unique functionality is available in all DOC drivers through the standard I/O control
command of the native file system.
6.3.7
Migrating from mDOC G3/G4/H1 and mDOC G3/G4 -based MCP to mDOC H3 and mDOC H3 -
based MCP can be done by TrueFFS 7.1.
TrueFFS 7.1 supports all mDOC product line including mDOC G3/G4/H1 and mDOC H3.
DOC driver 1.0 and higher provides stand alone SW support for mDOC H3 only. It does not
support mDOC G3/G4 and H1.
When using different software modules (e.g. Block Device DOC driver, Boot application,
formatting utilities, etc.) to access mDOC H3 it is crucial to verify that all software modules are
based on the same code base version. It is also important to use only tools (e.g. DOCFORMAT,
DOCINFO, DOCGETIMAGE, DOCPUTIMAGE, etc.) from the same version as the DOC
drivers used by the application. Failure to do so may lead to unexpected results, such as lost or
36
intermediate stages. Previous data is never erased until the operation has been completed and
the new data has been verified.
completed, in which case the new sector contents are valid, or the operation has not yet been
completed or has failed, in which case the old sector contents remain valid.
Special Features through I/O Control (IOCTL) Mechanism
Compatibility
Data Sheet (Preliminary) Rev. 0.2
mDOC H3 Embedded Flash Drive
92-DS-1205-10