MD3331-D64-V3-X SanDisk, MD3331-D64-V3-X Datasheet - Page 50

• Manufacturer Part Number: MD3331-D64-V3-X
• Manufacturer: SanDisk
• Type: Flash Diskr

Specifications of MD3331-D64-V3-X

• Density: 64MByte
• Operating Supply Voltage (typ): 3.3V
• Operating Temperature (min): -40C
• Operating Temperature (max): 85C
• Package Type: FBGA
• Mounting: Surface Mount
• Pin Count: 69
• Operating Temperature Classification: Industrial
• Operating Supply Voltage (min): 2.5V
• Operating Supply Voltage (max): 3.6V
• Programmable: Yes
• Lead Free Status / Rohs Status: Not Compliant

9.5.3
The Busy signal (BUSY#) indicates that Mobile DiskOnChip Plus has not yet completed internal
initialization. After reset, BUSY# is asserted while the IPL is downloaded into the internal boot
block and the Data Protection Structures (DPS) are downloaded to the Protection State Machines.
After the download process is completed, BUSY# is negated. It can be used to delay the first access
to Mobile DiskOnChip Plus until it is ready to accept valid cycles.
Note: The TrueFFS driver does NOT use this signal to indicate that the flash is in busy state (e.g.
9.5.4
When using a standard interface, Mobile DiskOnChip Plus can be configured for 8-bit, 16-bit or 32-
bit bus operations.
8-Bit (Byte) Data Access Mode
When configured for 8-bit operation, IF_CFG should be negated. Data should then be driven only
on the low data bus signals D[7:0]. D[15:8] and BHE# are internally pulled up and may be left
floating.
16-Bit (Word) Data Access Mode
When configured for 16-bit operation, IF_CFG should be asserted. The following definition is
compatible with 16-bit platforms using the BHE#/BLE# protocol:
•
•
•
•
•
Table 4 shows the active data bus lanes in 16-bit configuration.
Note: Although Mobile DiskOnChip Plus 16/32MB uses 8-bit access to the internal flash, it can be
50
When the host BLE# signal asserts Mobile DiskOnChip Plus A0, data is valid on D[7:0].
When the host BHE# signal asserts Mobile DiskOnChip Plus BHE#, data is valid on D[15:8].
When both A[0] and BHE# are at logic 0, data is valid on D[15:0].
No data is transferred when both BHE# and A0 are logic 1.
16-bit hosts that do not support byte transfers may hardwire the A0 and BHE# inputs to logic 0.
program, read, or erase).
connected to a 16-bit bus. The TrueFFS driver handles all issues regarding routing data to and
from Mobile DiskOnChip Plus. The Programmable Boot Block is accessed as a true 16-bit
device. It responds with the appropriate data when the CPU issues either an 8-bit or 16-bit
read cycle.
Busy Signal
Working with 8/16/32-Bit Systems with a Standard Interface
BHE#
0
0
1
1
Inputs
Table 4: Active Data Bus Lanes in 16-bit Configuration
A0
0
1
0
1
Data Sheet, Rev. 1.8
Data Bus Activity
D[7:0]
D[15:8]
Transfer Type
No Operation
Even Byte
Odd Byte
Word
Mobile DiskOnChip Plus 16/32MByte
95-SR-000-10-8L