2
Preliminary Specifications
16 Mbit / 32 Mbit / 64 Mbit Multi-Purpose Flash Plus
SST39VF1601 / SST39VF3201 / SST39VF6401
SST39VF1602 / SST39VF3202 / SST39VF6402
©2003 Silicon Sto rage Technology, Inc. S71223-03-000 11/03
To meet high density, surface mount requirements, the
SST39VF160x/320x/640x are offered in 48-lead TSOP
and 48-ball TFBGA packages. See Figures 1 and 2 for
pin assignme nts .
Device Operation
Commands are used to initiate the memory operation func-
tions of the device. Commands are written to the device
using standard microprocessor write sequences. A com-
mand is written by asse rtin g WE# low while keepi ng CE#
low. The address bus is latched on the falling edge of WE#
or CE#, whichever oc curs l ast. T he data bus is latc hed o n
the rising edge of WE# or CE#, whiche ver occurs first.
The SST39VF160x/320x/640x also have the Auto Low
Power mode which puts the device in a near standby
mode after data has been accessed with a valid Read
operation. This reduces the IDD active read current from
typically 9 mA to typically 3 µA. The A uto Low P ow er mode
reduces the typical IDD activ e re ad cur rent to the ra nge of 2
mA/MHz o f Read cycle t ime. The de vice e xits the A uto Lo w
Power mode with any address transition or control signal
transition used to initiate another Read cycle, with no
access time penalty. Note that the device does not enter
Auto-Low Power mode after power-up with CE# held
steadily low, until the first address transition or CE# is
driv en hi gh.
Read
The Read operation of the SST39VF160x/320x/640x is
cont rolled by C E# and O E#, bot h have to b e low for t he
system to obtain data from the outputs. CE# is used for
device selection. When CE# is high, the chip is dese-
lected and only standby power is consumed. OE# is the
output control and is used to gate data from the output
pins. The data bus is in high impedance state when
either C E# or OE# is high. R ef er to the Rea d cycle t iming
diagram fo r f urther deta ils (Figur e 3).
Word-Program Operation
The SST39VF160x/320x/640x are programmed on a
word-by-word basis. Before programming, the sector
where th e word exists mus t be fully erased . The Program
operation is accomplished in three steps. The first step is
the three-byte load sequence f or Software Data Protection.
The second step is to load word address and word data.
During the Word-Program operation, the addresses are
latched on the falling edge of either CE# or WE#, which-
eve r occur s last. T he data i s latched on the r ising edge o f
either CE# or WE#, whiche ver occurs first. The third step is
the internal Program operation which is initiated after the
rising edge of the fourth WE# or CE#, whichever occurs
first. The Program operation, once initiated, will be com-
pleted within 10 µs. See Figures 4 and 5 f or WE# and CE#
controlled Program operation timing diagrams and Figure
19 for flowcharts. During the Program operation, the only
valid reads are Data# Polling and Toggle Bit. During the
internal Program operation, the host is free to perform addi-
tional tasks. Any commands issued during the internal Pro-
gram operation are ignored. During the command
sequence, WP# should be statically held high or low.
Sector/Block-Erase Operation
The Sector- (or Block-) Erase operation allows the system
to erase the device on a sector-by-sector (or block-by-
block) basis. The SST39VF160x/320x/640x offer both Sec-
tor-Erase and Block-Erase mode. The sector architecture
is based on uniform sector size of 2 KWord. The Block-
Erase m ode is based on uniform block size of 32 K Wor d.
The Sec tor-Erase op eration is in itiated by executi ng a six-
byte command sequence with Sector-Erase command
(30H) and sector address (SA) in the last bus cycle. The
Block-Erase operation is initiated by executing a six-byte
command sequence with Block-Erase command (50H)
and block address (BA) in the last bus cycle. The sector or
block address is latched on the falling edge of the sixth
WE# pulse, while the command (30H or 50H) is latched on
the ri sing edge of th e sixth WE # puls e. The int er na l Erase
operation begins after the sixth WE# pulse. The End-of-
Erase operation can be determined using either Data#
P olling or Toggle Bit methods. See Figures 9 and 10 for tim-
ing waveforms and Figure 23 for the flowchart. Any com-
mands i s su ed during the S ec tor- or Bl ock-Era se op erat io n
are ignored. When WP# is low, any attempt to Sector-
(Block-) Erase the protected block will be ignored. During
the command sequence, WP# should be statically held
high or low.
Erase-Suspend/Erase-Resume Commands
The Erase-Suspend operation temporarily suspends a
Sector- or Block-Erase operation thus allowing data to be
read from any memor y loca tion, or program dat a into any
sector /block that i s not sus pended for an Eras e operation .
The operation is executed by issuing one byte command
sequence with Erase-Suspend command (B0H). The
device automatically enters read mode typically within 20
µs after the Erase-Suspend command had been issued.
Valid data can be read from any sector or block that is not
suspended from an Erase operation. Reading at address
locati on within erase-suspended sectors/blocks will output
DQ2 toggling and DQ6 at “1”. While in Erase-Suspend
mode, a W ord-Program operation is allowed except for the
sector or block selected for Erase-Suspend.