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

• 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: -

mDOC H3 Embedded Flash Drive
When mDOC H3 is configured for Virtual RAM Boot mode, the mode is retained after Reset as
well. While in this mode, read cycles from the entire mDOC H3 128KB memory window return
virtual RAM data.
Access to an address that is not within the physical window of this configuration (2KB in 8KB
window or 32KB in 128KB window), initiates a download operation in which the required data is
copied from the NAND flash to the physical SRAM. The mDOC H3 BUSY# output is asserted
for the duration of the download, to indicate that the data is not ready, holding the platform in a
wait state. When the download is completed the BUSY# line will be de-asserted. This handshake
mechanism is compatible with CPU bus controllers that support automatic insertion of wait states
based on the state of a /RDY signal. The platform must be capable of being held in a wait state
for an arbitrary period during each download process, without interference from watchdog timers.
The download is transparent to the host software; XIP and random access to any location within
the full virtual address space are therefore supported.
To exit the virtual mode, the host CPU should perform a write into the mDOC H3 window, to an
address as follows:
• 8KB mode: A11 = 1 and A12 = 0
• 128KB mode: A11-A15 = 0 and A16 = 1
For more information on how to boot from mDOC H3 in Virtual RAM Boot mode, please contact
your local msystems sales office.
8.1.3
Paged RAM Boot
The Paged RAM Boot feature uses the IPL SRAM as two 1KB sections. The first section
provides constant data, while the other section can be downloaded sequentially with flash data.
One application of this feature is to support Secure Boot requirements. The Paged RAM Boot
feature does not require support of the BUSY# output.
After a hardware or software reset, mDOC H3 initializes the first 2KB of XIP RAM with data
stored in the first 2KB of the pre-programmed IPL. The Paged RAM Boot feature permits 1KB
virtual pages (up to 254KB total) to be downloaded sequentially to the XIP RAM, upon receiving
the proper command sequence. Since the mDOC H3 BUSY# output is not asserted by a page-
load operation, a polling procedure is required to determine when the download is complete. An
XIP operation from the mDOC H3 RAM is not supported during this polling operation, so it must
be executed from system RAM or ROM instead.
When two mDOC H3 devices are cascaded, Paged RAM downloads occur only on the first
mDOC H3 device in the cascaded configuration (device-0).
For more information on booting from mDOC H3 in Paged RAM Boot mode, please contact your
local msystems sales office.
54
Data Sheet (Preliminary) Rev. 0.2
92-DS-1205-10