NAND08GAH0A NUMONYX [Numonyx B.V], NAND08GAH0A Datasheet - Page 93

• Manufacturer Part Number: NAND08GAH0A
• Manufacturer: NUMONYX [Numonyx B.V]

NAND08GAH0A, NAND16GAH0D
10.4.10
10.4.11
10.4.12
10.4.13
Read, Write, Erase and Forced Erase timeout conditions
The time period after which a timeout condition for read/write/erase operations occurs are
(device independent) 10 times longer than the typical access/program times for the
operations listed below. A device must complete the command within this time period, or
give up and return an error message. If the host does not get a response within the defined
timeout time it must assume that the device is not going to respond and try to recover (e.g.
reset the device, power cycle, reject).
The typical access and program times are defined as follows:
●
●
●
●
●
Memory array partitioning
It is the same as in the MultiMediaCard mode (see
Lock/Unlock commands
In SPI mode the Lock and Unlock commands are the same as in MultiMediaCard mode (see
Section 5.5.3
Application specific commands
The only difference between the MultiMediaCard and SPI modes is the APP_CMD status bit
which is not available in SPI mode.
Read
The read access time is defined as the sum of the two times given by the CSD
parameters TAAC and NSAC. These device parameters define the typical delay
between the end bit of the read command and the start bit of the data block. This
number is device dependent.
Write
The R2W_FACTOR field in the CSD is used to calculate the typical block program time
obtained by multiplying the read access time by this factor. It applies to all write/erase
commands (e.g. SET(CLEAR)_WRITE_PROTECT, PROGRAM_CSD(CID) and the
block write commands).
Erase
The duration of an erase command is (in order of magnitude) the number of write
blocks to be erased multiplied by the block write delay.
Forced Erase
The Forced Erase timeout is specified in
Read ahead in Multiple Block Read operation
In Multiple Block Read operations, in order to improve the read performance, the device
may fetch data from the memory array, ahead of the host. In this case, when the host is
reading the last addresses of the memory, the device attempts to fetch data beyond the
last physical memory address and generates an ADDRESS_OUT_OF_RANGE error.
Therefore, even if the host times the stop transmission command to stop the device
immediately after the last byte of data was read, the device may already have
generated the error, and it will show in the response to the stop transmission command.
The host should ignore this error.
and
Section
5.5.4).
Table
Section
Serial peripheral interface (SPI) mode
16.
3).
93/116