– Endurance: 100,000 Cycles (Typical)
– Greater than 100 years Data Retention
• Low Power Consumption (typical values at 5 MHz)
– Active Current: 9 mA (typical)
– Standby Current: 3 µA (typical)
– Auto Low P ower Mode: 3 µA (typical)
• Hardware Block-Protection/WP# Input Pin
– Top Block-Protection (top 32 KWord)
for SST39VF1602/3202/6402
– Bottom Block-Protection (bottom 32 KWord)
for SST39VF1601/3201/6401
• Sector-Erase Capability
– Uniform 2 KWord sectors
• Block-Erase Capability
– Uniform 32 KWord blocks
• Chip-Erase Capability
• Erase-Suspend/Erase-Resume Capabilities
• Hardware Reset Pin (RST#)
Preliminary Specifications
• Security-ID Feature
– SST: 128 bits; User: 128 bits
• Fast Read Access Time:
– 70 ns
– 90 ns
• Latched Address and Data
• Fast Erase and Word-Program:
– Sector-Erase Time: 18 ms (typical)
– Block-Erase Time: 18 ms (typical)
– Chip-Erase Time: 40 ms (typical)
– Word-Program Time: 7 µs (typical)
• Automatic Write Timing
– Internal V
Generation
PP
• End-of-Write Detection
– Toggle Bits
– Data# Polling
• CMOS I/O Compatibility
• JEDEC Standard
– Flash EEPROM Pinouts and command sets
• Packages Available
– 48-lead TSOP (12mm x 20mm)
– 48-ball TFBGA (6mm x 8mm) for 16M and 32M
– 48-ball TFBGA (8mm x 10mm) for 64M
PRODUCT DESCRIPTION
The SST39VF160x/320x/6 40x devices are 1M x16, 2M
x16, and 4M x16 respectively, CMOS Multi-Purpose
Flash Plus (MPF+) manufactured with SST’s proprietar y,
high performance CMOS SuperFlash technology. The
split-gate cell design and thick-oxide tunneling injector
attain better reliability and manufacturability compared
with alternate approaches. The SST39VF160x/320x/640x
write (Program or Erase) with a 2.7 -3.6V power supply.
These devices conform to JEDEC standard pinouts for
x16 memories.
Featuring high performance Word-Program, the
SST39VF160x/ 320x/ 640x d evices provide a typic al WordProgram time of 7 µsec. T hese devices use Toggle Bit or
Data# Polling to indicate the completion of Program operation. To protect against inadvertent write, they have on-chip
hardware and Software Data Protection schemes.
Designed, manufactured, and tested for a wide spectrum of
applications, these d evices are offered with a guaranteed
typical endurance of 100,000 cycles. Data retention is rated
at greater than 100 years.
The SST39VF160x/320x/640x devices are suited for applications that require convenient and economical updating of
program, configuration, or data memory. For all system
applications, they significantly improve performance and
reliability, while lowering power consumption . They inherently use less energy during Erase and Program than alternative flash technologi es. The total energy consum ed is a
function of the applied voltage, current, and time of application. Since for any given voltage range, the SuperFlash
technology uses less current to program and has a shorter
erase time, the total energy consumed during any Erase or
Program operation is l ess than alter native flash technologies. These devices also im prove flexibility while lowering
the cost for program, data, and configuration storage applications.
The SuperFlash technology prov ides fixed Erase and Program times, independent of the n umbe r of Er ase/Prog r am
cycles that have occurred. Therefore the system software
or hardware does not hav e to be modified or de-rated as is
necessary with alternative flash technologies, whose
Erase and Program times increase with accumulated
Erase/Program cycles.
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 assignments.
Device Operation
Commands are used to initiate the memory operation functions of the device. Commands are written to the device
using standard microprocess or write sequences. A command is written by asse r ting WE# low whil e keeping CE#
low. The address bus is latched on the falling edge of WE#
or CE#, whichever occurs last. T he data bus is latc hed o n
the rising edge of WE# or CE#, whichever occurs first.
The SST39VF160x/320x/640x also have the Auto LowPower mode which puts the device in a near standby
mode after data has been accessed with a valid Read
operation. This reduces the I
typically 9 mA to typically 3 µA. The Auto Low Power mode
reduces the typical I
mA/MHz of Read cycle time. The d evi ce exit s the A uto Low
Power mode with any address transition or control s ignal
transition used to initiate another Read cycle, with no
access time penal ty. 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
driven hi gh.
active re ad cur rent to the ra nge of 2
DD
active read current from
DD
Read
The Read operation of the SST39VF160x/320x/640x is
controlled by C E# and OE#, bot h have to be low for the
system to obtain data from the outputs. CE# is used for
device selection. When CE# is high, the chip is deselected 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 CE# or OE# is high. Ref e r to the R ead cycl e timing
diagram for further details (Fig ure 3).
Word-Program Operation
The SST39VF160x/320x/640x are programmed on a
word-by-word basis. Before programming, the sector
where the word exists must be ful ly erased. The Program
operation is accom plished in thre e steps. The first step is
the three-byte load sequence for Software Data Protection.
The second step is to load word add ress and word data.
During the Word-Program operation, the addresses are
latched on the falling ed ge of either CE# or WE#, whi chever occurs last. The data i s latched on the r ising edge of
either CE# or WE#, whichever occurs first. The third step is
the interna l Program operation which is initiated after the
rising edge of the fourth WE# or CE#, whichever occurs
first. The Program o peration, once initiated, wil l be completed within 10 µs. See Figures 4 and 5 for WE# and CE#
controlled Pro gram operation timing diagrams a nd Figure
19 for flowcharts. Dur ing the Program operation, th e only
valid reads are Data# Polling and Toggle Bit. Dur ing the
internal Program operation, the host is free to perform additional tasks. Any commands issued during the internal Program 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-byblock) basis. The SST39VF160x/320x/640x offer both Sector-Erase and Block-Erase mode. The sector archi tecture
is based on uniform se ctor size of 2 KWord. The BlockErase mode is bas ed on uniform block size of 32 KWord.
The Sector-Erase op eration is in itiated by executing a sixbyte command sequence with Sector-Erase command
(30H) and sect or address (SA) in the l ast 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 rising edge of th e six th WE# pu lse. The int er na l Eras e
operation begins a fter the sixth WE# pulse. The End -ofErase operation can be determined using either Data#
Polling or Toggle Bit methods. See Figures 9 and 10 for timing waveforms and Figure 23 for the flowchart. Any commands issued during the Sec tor- or B lock-Era se op erat io n
are ignored. When WP# is low, any attempt to Sector(Block-) Erase the prote cted block will be ignor ed. 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 data into any
sector/block that is not sus pended for an Erase 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 Era se-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 addr ess
location withi n erase-suspende d sectors/blocks will output
DQ
toggling and DQ6 at “1”. While in Erase-Suspend
2
mode, a Word-Program operation is allowed except for the
sector or block selected for Erase-Suspend.
T o resume Sector-Erase or Block-Erase operation which has
been suspended the system must issue Erase Resume
command. The operation is executed by issuing one byte
command sequence with Erase Resume command (30H)
at any address in th e last Byte sequence .
Chip-Erase Operation
The SST39VF160x/320x/640x provide a Chip-Er ase operation, which allows the user to erase the entire memory
array to the “1” state. This is useful when the entire device
must be quickly erased.
The Chip-Erase operation is initiated by executing a sixbyte command sequence with Chip-Erase command
(10H) at address 5555H in the last byte sequence. The
Erase operation begins with the rising edge of the sixth
WE# or CE#, whichever occurs first. During the Erase
operation, the only v alid read is Toggle Bit or Data# P olling.
See Table 6 for the command sequence, Figure 9 for timing diagram, and Figure 23 for the flowchart. Any commands issued during the Chip-Erase operation are
ignored. When WP# is low, any attempt to Chip-Erase will
be ignored. During the command sequence, WP# should
be statically held high or lo w.
Write Operation Status Detection
The SST39VF160x/320x/640x provide two software
means to detect the completion of a Write (Program or
Erase) cycle, in ord er to optimize the system wri te cycle
time. The software detection includes two status bits: Data#
Polling (DQ
) and Toggle Bit (DQ6). The End-of-Write
7
detection mode is enabled afte r the rising edge of WE#,
which initiates the internal Program or Erase operation.
The actual completion of the nonvolatile write is asynchronous with the system; therefore, either a Data# Polling or Toggle Bit read may be simultaneous with the
completion of the write cycle. If this occurs, the system
may possibly get an erroneous result, i.e., valid data may
appear to conflict w it h ei th er D Q
or DQ6. In order to pre-
7
vent spurious rejection, if an erroneous result occurs, the
software routine should include a loop to read the
accessed location an additional two (2) times. If both
reads are valid, then the device has completed the Write
cycle, otherwise the reje ction is valid.
Data# Polling (DQ7)
When the SST39VF160x/320x/640x are in the internal
Program operation, any attempt to read DQ
the complement of the true data. Once the Program operation is completed, DQ
even though DQ
7
will produce true data. Note that
7
may have valid data immediately follow-
will produce
7
ing the completion of an internal Write operation, the
remaining data outputs may still be invalid: valid data on the
entire data bus will appear in subsequent successive Read
cycles after a n in te rva l of 1 µ s . Du ring internal Erase operation, any attempt t o rea d DQ
internal Erase operation is completed, DQ
will produce a ‘0’. Once the
7
will produce a
7
‘1’. The Data# P olling is v alid after the rising edge o f f ourth
WE# (or CE#) pulse for Program operation. For Sector-,
Block- or Chip-Erase, the Data# Polling is valid after the
rising edge of sixth WE# (or CE#) pulse. See Figure 6 for
Data# P olling timing diagram an d Figure 20 f or a flowchart.
Toggle Bits (DQ6 and DQ2)
During the inter nal Program or Erase ope ration, any consecutive attempts to read DQ
and “0”s, i.e., toggling between 1 and 0. Wh en the i nte rnal
Program or Erase operat ion is complete d, the DQ
stop toggling. The device is then ready for the next operation. For Sector-, Block-, or Chip-Erase, the toggle bit (DQ
is valid after the ris ing edge of six th WE# (or CE#) p ulse.
DQ
will be set to “1” if a Read operation is attempted on an
6
Erase-Suspended Sector/Block. If Program operation is initiated in a sector/block not selected in Erase-Suspend
mode, DQ
will toggle .
6
An additional Toggle Bit is available on DQ
used in conjunction with DQ
sector is being actively erased or erase-suspended. T able 1
shows detailed status bits information. The Toggle Bit
(DQ
) is valid after the rising edge of the last WE# (or CE#)
2
pulse of Write operation. See Figure 7 for Toggle Bit timing
diagram and Figure 20 for a flowchart.
TABLE 1: WRITE OPERATION STATUS
StatusDQ7DQ
Normal
Operation
EraseSuspend
Mode
Note: DQ7 and DQ2 require a valid address when reading
The SST39VF160x/320x/640x provide both hardware and
software features to protect nonvolatile data from inadvertent
writes.
Hardware Data Protection
Noise/Glitch Protection: A WE# or CE# pulse of le ss than 5
ns will not init iate a write cycle .
V
Power Up/Down Detection: The Write operation is
DD
inhibited when V
Write Inhibit Mode:
is less than 1.5V.
DD
Forcing OE# low, CE# high, or WE#
high will inhibit the W r ite operation. This prevents inadvertent writes during p ow er-up o r po wer- down.
Hardware Block Protection
The SST39VF1602/3202/6402 support top hardware block
protection, which protects the top 32 KWord block of the
device. The SST39VF1601/3201/6401 support bottom
hardware block protection, which protects the bottom 32
KWord block of the device. The Boot Block address ranges
are descri bed in Table 2. Program an d Erase operations
are prevented on the 32 KWord when WP# is low. If WP# is
left floating, it is internally h eld high via a pull-u p resistor,
and the Boot Block is unp rotected, enabling Program an d
Erase operations on that block.
The RST# pin provides a hardware method of resetting the
device to read array data. When the RST# pin is held low
for at least T
any in-progress operation will terminate and
RP,
return to Read mode. When no internal Program/Erase
operation is in progress, a minimum period of T
RHR
is
required after RST# is driven high before a valid Read can
take place (see Figure 15).
The Erase or Program operation that has been interrupted
needs to be reinitiated after the device resumes normal
operation mode to ensure data integrity .
Software Data Protection (SDP)
The SST39VF160x/320x/640x provide the JEDEC
approved Software Data Protection scheme for all data
alteration operations, i.e., Program and Erase. Any Program operation requires the inclusion of the three-byte
sequence. The three-byte load sequence is used to initiate
the Program operation, p roviding optimal protection from
inadvertent Write operations, e.g., during the system
power-up or power-down. Any Erase operation requires the
inclusion of six-byte sequence. These devices are shipped
with the Software Data Protection permanently enabled.
See T ab le 6 for the specific software command codes. During SDP command sequence, invalid commands will abort
the de v ice t o re a d mode w i th in T
DQ
can be VIL or VIH, but no other value, during any SDP
8
The contents of DQ15-
RC.
command sequence.
Common Flash Memory Interface (CFI)
The SST39VF160x/320x/640x also contain the CFI information to describe the characteristics of the device. In
order to enter the CFI Query mode, the system must write
three-byte sequence, same as product ID entry command
with 98H (CFI Query command) to address 5555H in the
last byte sequence. Once the de vice enters the CFI Query
mode, the system can read CFI data at the addresses
given in Tables 7 through 10. The system must write the
CFI Exit command to return to Read mode from the CFI
Query mode.
The Product Identificatio n mode id entifies th e devices as
the SST39VF1601, SST39VF1602, SST39VF3201,
SST39VF3202, SST39VF6401, SST39VF6402, and
manufacturer as SST. This mode may be accessed software operations. Users may use the Software Product
Identification operation to identify the par t (i.e., using the
device ID) when using multiple manufacturers in the same
socket. For details, see Table 6 for software operation,
Figure 11 for the Software ID Entry a nd Read tim ing diagram and Figure 21 for the Software ID Entry command
sequence flowchart.
The SST39VF160x/320x/640x devices offer a 256-bit
Security ID space. The Secure ID space is divided into two
128-bit segment s - one factory programmed seg ment an d
one user programmed seg ment. The first segment is programmed and locked at SS T with a ra ndom 128-bi t number. The user segment is left un-programmed for the
customer to program as desired.
To program the user segm ent of the Security ID, the user
must use the Security ID Word-Program command. To
detect end-of-write for the SEC ID, read the toggle bits. Do
not use Data# Polling. Once this is complet e, the Sec ID
should be locked using the User Sec ID Program Lock-Out.
This disables any future corr up ti on of this sp ac e. Note tha t
regardless of whether or not the Sec ID is locked, neither
Sec ID segment can be erased.
The Secure ID space can be queried by executing a threebyte command sequence with Enter Sec ID command
(88H) at address 5555H in th e last byte sequence. To exit
this mode, the Exit Sec ID command should be executed.
Refer to Table 6 for more details.
Product Identification Mode Exit/
CFI Mode Exit
In order to return to the standard Read mode, the Software
Product Identific ation mode must be exited. Exit is acco mplished by issuing the Software ID Exit command
sequence, which returns the device to the Read mode.
This command may also be used to reset the device to the
Read mode after any inadvertent transient condition that
apparently caus es the device to behave abnor mally, e.g. ,
not read correct ly. Please note th at the Software ID Exit/
CFI Exit command is ignored during an internal Program or
Erase operation. See Table 6 for software command
codes, Figure 13 for timing waveform, and Figures 21 and
22 for flowcharts.
WP#Write ProtectTo protect the top/bottom boot block from Erase/Program operation when grounded.
RST#ResetTo reset and return the device to Read mod e .
CE#Chip EnableTo activate the device when CE# is low.
OE#Output EnableTo gate the data output buffers.
WE#Write EnableTo control the Write operations.
V
DD
V
SS
NCNo ConnectionUnconnected pins.
1. AMS = Most significant address
A
MS
Address InputsTo provide memory addresses.
0
During Sector-Erase A
During Block-Erase A
Data Input/outputT o outpu t d ata during Read cycles and rece ive input data during Write cycles.
0
MS-A15
address lines will select the sector.
MS-A11
address lines will select the block.
Data is internally latched during a Write cycle.
The outputs are in tri-state when OE# or CE# is high.
Power SupplyTo provide power supply voltage: 2.7-3.6V
Ground
= A19 for SST39VF1601/1602, A20 for SST39VF3201/3202, and A21 for SST39VF6401/6402
can be VIL or VIH, but no other value, for Command sequence for SST39VF1601/1602,
can be VIL or VIH, but no other value, for Command sequence for SST39VF3201/3202,
- A21 can be VIL or VIH, but no other value, for Command sequence for SST39VF6401/6402.
SST ID is read with A
User ID is read with A
= 0000FFH. Unlocked: DQ3 = 1 / Locked: DQ3 = 0.
7-A0
SST39VF1601 Device ID = 234BH, is read with A
SST39VF1602 Device ID = 234AH, is read with A
SST39VF3201 Device ID = 235BH, is read with A
SST39VF3202 Device ID = 235AH, is read with A
SST39VF6401 Device ID = 236BH, is read with A
SST39VF6402 Device ID = 236AH, is read with A
TABLE 7: CFI QUERY IDENTIFICATION STRING1 FOR SST39VF16 0X/320X/640X
AddressDataData
10H0051HQuery Unique ASCII string “QRY”
11H0052H
12H0059H
13H0001HPrimary OEM command set
14H0007H
15H0000HAddress for Primary Extended Table
16H0000H
17H0000HAlternate OEM command set (00H = none exists)
18H0000H
19H0000HAddress for Alternate OEM extended Table (00H = none exits)
1AH0000H
1. Refer to CFI publication 100 for more details.
TABLE 8: SYSTEM INTERFACE INFORMATIONFOR SST39VF 160X/320X/640X
AddressDataData
1BH0027HV
1CH0036HVDD Max (Program/Erase)
1DH0000HVPP min. (00H = no VPP pin)
1EH0000HVPP max. (00H = no VPP pin)
1FH0003HTypical time out for Word-Program 2
20H0000HTypical time out for min. size buffer program 2N µs (00H = not supported)
21H0004HT ypic al time out for individual Sector/Block-Erase 2N ms (24 = 16 ms)
22H0005HT y pic al time out for Chip-Erase 2
23H0001HMaximum time out for Word-Program 2N times typical (21 x 23 = 16 µs)
24H0000HMaximum time out for buffer program 2N times typical
25H0001HMaximum time out for individual Sector/Block-Erase 2
26H0001HMaximum time out for Chip-Erase 2N times typical (21 x 25 = 64 ms)
Preliminary Specifications
Absolute Maximum Stress Ratings (Applied conditions greater than those listed under “Absolute Maximum
Stress Ratings” may cause pe r manent dama ge to the device. This is a stres s rating only and funct ional operatio n
of the device at these conditions or conditions greater tha n those defined in the ope rational sections of this data
sheet is not implied. Exposure to absolute maximum stress rating conditions may affect device reliability.)
OE# High to High-Z Output2030ns
Output Hold from Address Change00ns
RST# Pulse Width500500ns
1
RST# High before Read5050ns
RST# Pin Low to Read Mode2020µs
This parameter does not apply to Chip-Erase operations.
UnitsMinMaxMinMax
T16.3 1223
TABLE 17: PROGRAM/ERASE CYCLE TIMIN G PARAMETERS
SymbolParameterMinMaxUnits
T
BP
T
AS
T
AH
T
CS
T
CH
T
OES
T
OEH
T
CP
T
WP
T
WPH
T
CPH
T
DS
T
DH
T
IDA
T
SE
T
BE
T
SCE
1. This parameter is measured only for initial qualification and after a design or process change that could affect this parameter.
Word-Program Time10 µs
Address Setup Time0ns
Address Hol d Time30ns
WE# and CE# Setup Time0ns
WE# and CE# Hold Time0ns
OE# High Setup Time0ns
OE# High Hold Time10ns
CE# Pulse Width40ns
WE# Pulse Width40ns
1
WE# Pulse Width High30ns
1
CE# Pulse Width High30ns
Data Setup Time30ns
1
Data Hold Time0ns
1
Software ID Access and Exit Time150ns
Sector-Erase25ms
Block-Erase25ms
Chip-Erase50ms
Note: Device ID = 234BH for 39VF1601, 234AH for 39VF1602, 235BH for 39VF3201, 235AH for 39VF3202,
236BH for 39VF6401, and 236AH for 39VF6402,
WP# must be held in proper logic state (V
X can be V
IL
or V
IH,
but no other value
FIGURE 11: SOFTWARE ID ENTRYAND READ
T
IDA
T
AA
00BF
or VIH) 1 µs prior to and 1 µs after the command sequence
IL
Device ID
1223 F11.2
ADDRESS A
DQ
Three-Byte Sequence for CFI Query Entry
14-0
55552AAA5555
CE#
OE#
T
T
WP
IDA
WE#
T
15-0
WPH
XX55XXAAXX98
T
AA
SW0SW1SW2
Note: WP# must be held in proper logic state (VIL or VIH) 1 µs prior to and 1 µs after the command sequence