• Dual Bank Architecture for Concurrent
Read/Write Operation
– 16 Mbit Bottom Sector Protection
- SST36VF1601E: 12 Mbit + 4 Mbit
– 16 Mbit Top Sector Protection
- SST36VF1602E: 4 Mbit + 12 Mbit
• Single 2.7-3.6V for Read and Write Operations
• Superior Reliability
– Endurance: 100,000 cycles (typical)
– Greater than 100 years Data Retention
• Low Power Consumption:
– Active Current: 6 mA typical
– Standby Current: 4 µA typical
– Auto Low Power Mode: 4 µA typical
• Hardware Sector Protection/WP# Input Pin
– Protects the 4 outermost sectors (8 KWord)
in the larger bank by driving WP# low and
unprotects by driving WP# high
• Hardware Reset Pin (RST#)
– Resets the internal state machine to reading
array data
• Byte# Pin
– Selects 8-bit or 16-bit mode
• Sector-Erase Capability
– Uniform 2 KWord sectors
• Chip-Erase Capability
• Block-Erase Capability
– Uniform 32 KWord blocks
• Erase-Suspend / Erase-Resume Capabilities
• Security ID Feature
– SST: 128 bits
– User: 128 bits
• Fast Read Access Time
– 70 ns
• Latched Address and Data
• Fast Erase and Program (typical):
– Sector-Erase Time: 18 ms
– Block-Erase Time: 18 ms
– Chip-Erase Time: 35 ms
– Program Time: 7 µs
• Automatic Write Timing
– Internal V
Generation
PP
• End-of-Write Detection
– Toggle Bit
– Data# Polling
– Ready/Busy# pin
• CMOS I/O Compatibility
• Conforms to Common Flash Memory Interface (CFI)
• JEDEC Standards
– Flash EEPROM Pinouts and command sets
• Packages Available
– 48-ball TFBGA (6mm x 8mm)
– 48-lead TSOP (12mm x 20mm)
• All non-Pb (lead-free) devices are RoHS compliant
PRODUCT DESCRIPTION
The SST36VF1601E and SST36VF1602E are 1M x16 or
2M x8 CMOS Concurrent Read/Write Flash Memory manufactured with SST’s proprietary, high performance CMOS
SuperFlash memory technology. The split-gate cell design
and thick oxide tunneling injector attain better reliability and
manufacturability compared with alternate approaches.
The devices write (Program or Erase) with a 2.7-3.6V
power supply and conform to JEDEC standard pinouts for
x8/x16 memories.
Featuring high performance Program, these devices provide a typical Program time of 7 µsec and use the Toggle
Bit, Data# Polling, or RY/BY# to detect the completion of
the Program or Erase operation. To protect against inadvertent write, the devices have on-chip hardware and Software Data Protection schemes. Designed, manufactured,
and tested for a wide spectrum of applications, these
devices are offered with a guaranteed endurance of 10,000
cycles. Data retention is rated at greater than 100 years.
These devices are suited for applications that require convenient and economical updating of program, configuration, or data memory. For all system applications, the
devices significantly improve performance and reliability,
while lowering power consumption. 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 less than alternative flash technologies. These devices
also improve flexibility while lowering the cost for program,
data, and configuration storage applications.
The SST logo and SuperFlash are registered trademarks of Silicon Storage Technology, Inc.
CSF is a trademark of Silicon Storage Technology, Inc.
These specifications are subject to change without notice.
Page 2
Data Sheet
16 Mbit Concurrent SuperFlash
SST36VF1601E / SST36VF1602E
SuperFlash technology provides fixed Erase and Program
times, independent of the number of Erase/Program
cycles that have occurred. Therefore the system software
or hardware does not have 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, these
devices are offered in 48-ball TFBGA and 48-lead TSOP
packages. See Figures 5 and 6 for pin assignments.
Device Operation
Memory operation functions are initiated using standard
microprocessor write sequences. A command is written by
asserting WE# low while keeping CE# low. The address
bus is latched on the falling edge of WE# or CE#, whichever occurs last. The data bus is latched on the rising edge
of WE# or CE#, whichever occurs first.
Auto Low Power Mode
These devices also have the Auto Lower Power mode
which puts them in a near standby mode within 500 ns
after data has been accessed with a valid Read operation.
This reduces the I
active Read current to 4 µA typically.
DD
While CE# is low, the devices exit Auto Low Power mode
with any address transition or control signal transition used
to initiate another Read cycle, with no access time penalty.
Concurrent Read/Write Operation
The dual bank architecture of these devices allows the
Concurrent Read/Write operation whereby the user can
read from one bank while programming or erasing in the
other bank. For example, reading system code in one bank
while updating data in the other bank.
C
ONCURRENT READ/WRITE STATE
Bank 1Bank 2
ReadNo Operation
ReadWrite
WriteRead
WriteNo Operation
No OperationRead
No OperationWrite
Note: For the purposes of this table, write means to perform Block-
or Sector-Erase or Program operations as applicable to the
appropriate bank.
Read Operation
The Read operation is controlled by CE# and OE#; both
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 a high impedance
state when either CE# or OE# is high. Refer to the Read
cycle timing diagram for further details (Figure 7).
Program Operation
These devices are programmed on a word-by-word or
byte-by-byte basis depending on the state of the BYTE#
pin. Before programming, one must ensure that the sector
which is being programmed is fully erased.
The Program operation is accomplished in three steps:
1. Software Data Protection is initiated using the
three-byte load sequence.
2. Address and data are loaded.
During the Program operation, the addresses are
latched on the falling edge of either CE# or WE#,
whichever occurs last. The data is latched on the
rising edge of either CE# or WE#, whichever
occurs first.
3. The internal Program operation is initiated after
the rising edge of the fourth WE# or CE#, whichever occurs first. The Program operation, once initiated, will be completed typically within 7 µs.
See Figures 8 and 9 for WE# and CE# controlled Program
operation timing diagrams and Figure 23 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 additional tasks. Any
commands issued during an internal Program operation
are ignored.
These devices offer both Sector-Erase and Block-Erase
operations. These operations allow the system to erase the
devices on a sector-by-sector (or block-by-block) basis. The
sector architecture is based on a uniform sector size of 2
KWord. The Block-Erase mode is based on a uniform block
size of 32 KWord. The Sector-Erase operation is initiated by
executing a six-byte command sequence with a SectorErase 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 rising edge of the sixth WE# pulse. The internal Erase operation begins after the sixth WE# pulse. Any
commands issued during the Sector- or Block-Erase operation are ignored except Erase-Suspend and EraseResume. See Figures 13 and 14 for timing waveforms.
Chip-Erase Operation
The devices provide a Chip-Erase operation, which allows
the user to erase all sectors/blocks to the “1” state. This is
useful when a device must be quickly erased.
The Chip-Erase operation is initiated by executing a sixbyte command sequence with Chip-Erase command (10H)
at address 555H 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 valid Read is Toggle Bit or Data# Polling. Any commands issued during the Chip-Erase operation are
ignored. See Table 5 for the command sequence, Figure
12 for timing diagram, and Figure 27 for the flowchart.
When WP# is low, any attempt to Chip-Erase will be
ignored.
Erase-Suspend/Erase-Resume Operations
The Erase-Suspend operation temporarily suspends a
Sector- or Block-Erase operation thus allowing data to be
read from any memory location, or program data into any
sector/block that is not suspended for an Erase operation.
The operation is executed by issuing a one-byte command
sequence with Erase-Suspend command (B0H). The
device automatically enters read mode no more than 10 µs
after the Erase-Suspend command had been issued. (T
ES
maximum latency equals 10 µs.) Valid data can be read
from any sector or block that is not suspended from an
Erase operation. Reading at address location within erasesuspended sectors/blocks will output DQ
DQ
at “1”. While in Erase-Suspend mode, a Program
6
toggling and
2
operation is allowed except for the sector or block selected
for Erase-Suspend. To resume Sector-Erase or BlockErase operation which has been suspended, the system
must issue an Erase-Resume command. The operation is
executed by issuing a one-byte command sequence with
Erase Resume command (30H) at any address in the onebyte sequence.
Write Operation Status Detection
These devices provide one hardware and two software
means to detect the completion of a Write (Program or
Erase) cycle in order to optimize the system Write cycle
time. The hardware detection uses the Ready/Busy# (RY/
BY#) output pin. The software detection includes two status bits: Data# Polling (DQ
End-of-Write detection mode is enabled after 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 Ready/Busy# (RY/
BY#), a Data# Polling (DQ
be simultaneous with the completion of the Write cycle. If
this occurs, the system may get an erroneous result, i.e.,
valid data may appear to conflict with either DQ
order to prevent 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 Write cycle has completed, otherwise the rejection is valid.
The devices include a Ready/Busy# (RY/BY#) output signal. RY/BY# is an open drain output pin that indicates
whether an Erase or Program operation is in progress.
Since RY/BY# is an open drain output, it allows several
devices to be tied in parallel to V
via an external pull-up
DD
resistor. After the rising edge of the final WE# pulse in the
command sequence, the RY/BY# status is valid.
When RY/BY# is actively pulled low, it indicates that an
Erase or Program operation is in progress. When RY/BY#
is high (Ready), the devices may be read or left in standby
mode.
Byte/Word (BYTE#)
The device includes a BYTE# pin to control whether the
device data I/O pins operate x8 or x16. If the BYTE# pin is
at logic “1” (V
data I/0 pins DQ
) the device is in x16 data configuration: all
IH
-DQ15 are active and controlled by CE#
0
and OE#.
If the BYTE# pin is at logic “0”, the device is in x8 data configuration: only data I/O pins DQ
-DQ7 are active and con-
0
trolled by CE# and OE#. The remaining data pins DQ
DQ
are at Hi-Z, while pin DQ15 is used as the address
14
input A
for the Least Significant Bit of the address bus.
-1
Data# Polling (DQ7)
When the devices are in an internal Program operation, any
attempt to read DQ
true data. Once the Program operation is completed, DQ
will produce true data. During internal Erase operation, any
attempt to read DQ
Erase operation is completed, DQ
Data# Polling is valid after the rising edge of fourth 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 10 for Data# Polling (DQ
) timing diagram and Figure 24 for a flowchart.
7
will produce the complement of the
7
will produce a ‘0’. Once the internal
7
will produce a ‘1’. The
7
Toggle Bits (DQ6 and DQ2)
During the internal Program or Erase operation, any consecutive attempts to read DQ
and “0”s, i.e., toggling between 1 and 0. When the internal
Program or Erase operation is completed, the DQ
stop toggling. The device is then ready for the next operation. The toggle bit is valid after the rising edge of the fourth
WE# (or CE#) pulse for Program operations. For Sector-,
Block-, or Chip-Erase, the toggle bit (DQ
rising edge of sixth WE# (or CE#) pulse. DQ
“1” if a Read operation is attempted on an Erase-suspended Sector/Block. If Program operation is initiated in a
sector/block not selected in Erase-Suspend mode, DQ
toggle.
An additional Toggle Bit is available on DQ
used in conjunction with DQ
sector is being actively erased or erase-suspended. Table 1
shows detailed status bit information. The Toggle Bit (DQ
is valid after the rising edge of the last WE# (or CE#) pulse
of a Write operation. See Figure 11 for Toggle Bit timing
diagram and Figure 24 for a flowchart.
-
8
TABLE 1: WRITE OPERATION STATUS
StatusDQ
7
Normal
Operation
EraseSuspend
Mode
Note: DQ7, DQ
Standard
Program
Standard
Erase
Read From
Erase
Suspended
Sector/Block
Read From
Non-Erase
Suspended
Sector/Block
ProgramDQ7# ToggleN/A0
and DQ2 require a valid address when reading
status information. The address must be in the bank where
the operation is in progress in order to read the operation status. If the address is pointing to a different bank (not busy),
the device will output array data.
The devices 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 less than 5
ns will not initiate a Write cycle.
V
Power Up/Down Detection: The Write operation is
DD
inhibited when V
Write Inhibit Mode:
high will inhibit the Write operation. This prevents inadvertent writes during power-up or power-down.
is less than 1.5V.
DD
Forcing OE# low, CE# high, or WE#
Hardware Block Protection
The devices provide hardware block protection which protects the outermost 8 KWord in the larger bank. The block
is protected when WP# is held low. See Figures 1, 2, 3,
and 4 for Block-Protection location.
A user can disable block protection by driving WP# high.
This allows data to be erased or programmed into the protected sectors. WP# must be held high prior to issuing the
Write command and remain stable until after the entire
Write operation has completed. If WP# is left floating, it is
internally held high via a pull-up resistor, and the Boot
Block is unprotected, enabling Program and Erase operations on that block.
Software Data Protection (SDP)
These devices provide the JEDEC standard 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, providing optimal protection from inadvertent Write operations,
e.g., during the system power-up or power-down. Any
Erase operation requires the inclusion of the six-byte
sequence. The devices are shipped with the Software Data
Protection permanently enabled. See Table 5 for the specific software command codes. During SDP command
sequence, invalid commands will abort the device to Read
mode within T
V
but no other value during any SDP command
IH,
sequence.
The contents of DQ15-DQ8 can be VIL or
RC.
Common Flash Memory Interface (CFI)
These devices also contain the CFI information to
describe the characteristics of the devices. In order to
enter the CFI Query mode, the system must write the
three-byte sequence, same as the Software ID Entry command with 98H (CFI Query command) to address 555H in
the last byte sequence. See Figure 16 for CFI Entry and
Read timing diagram. Once the device enters the CFI
Query mode, the system can read CFI data at the
addresses given in Tables 6 through 8. The system must
write the CFI Exit command to return to Read mode from
the CFI Query mode.
Hardware Reset (RST#)
The RST# pin provides a hardware method of resetting the
devices to read array data. When the RST# pin is held low
for at least T
return to Read mode (see Figure 20). When no internal
Program/Erase operation is in progress, a minimum period
of T
RHR
Read can take place (see Figure 19).
The Erase operation that has been interrupted needs to be
reinitiated after the device resumes normal operation mode
to ensure data integrity.
is required after RST# is driven high before a valid
Security ID
The SST36VF160xE devices offer a 256-bit Security ID
space. The Secure ID space is divided into two 128-bit segments—one factory programmed segment and one user
programmed segment. The first segment is programmed
and locked at SST with a unique, 128-bit number. The user
segment is left un-programmed for the customer to program as desired. To program the user segment of the
Security ID, the user must use the Security ID Program
command. End-of-Write status is checked by reading the
toggle bits. Data# Polling is not used for Security ID End-ofWrite detection. Once programming is complete, the Sec
ID should be locked using the User Sec ID Program LockOut. This disables any future corruption of this space. Note
that 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 three-byte command
sequence with Query Sec ID command (88H) at address
555H in the last byte sequence. See Figure 18 for timing
diagram. To exit this mode, the Exit Sec ID command
should be executed. Refer to Table 5 for more details.
5
Page 6
Data Sheet
16 Mbit Concurrent SuperFlash
SST36VF1601E / SST36VF1602E
Product Identification
The Product Identification mode identifies the devices and
manufacturer. For details, see Table 2 for software operation, Figure 15 for the Software ID Entry and Read timing
diagram and Figure 25 for the Software ID Entry command
sequence flowchart. The addresses A
bank address. When the addressed bank is switched to
Product Identification mode, it is possible to read another
address from the same bank without issuing a new Software ID Entry command.
TABLE 2: P
Manufacturer’s IDBK0000H00BFH
Device ID
SST36VF1601EBK0001H734BH
SST36VF1602EBK0001H734AH
Note: BK = Bank Address (A19-A18)
RODUCT IDENTIFICATION
FUNCTIONAL BLOCK DIAGRAM
and A18 indicate a
19
AddressData
T2.0 1274
Product Identification Mode
Exit/CFI Mode Exit
In order to return to the standard Read mode, the Software
Product Identification mode must be exited. Exit is accomplished 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 causes the device to behave abnormally, e.g., not read
correctly. Please note that the Software ID Exit/CFI Exit
command is ignored during an internal Program or Erase
operation. See Table 5 for the software command code, Figure 17 for timing waveform and Figure 26 for a flowchart.
CE#Chip Enable To activate the device when CE# is low.
OE#Output EnableTo gate the data output buffers
WE#Write EnableTo control the Write operations
RST#Hardware ResetTo reset and return the device to Read mode
RY/BY#Ready/Busy#To output the status of a Program or Erase operation
WP#Write ProtectTo protect and unprotect top or bottom 8 KWord (4 outermost sectors) from Erase or
BYTE#Word/Byte Configuration To select 8-bit or 16-bit mode.
V
DD
V
SS
NCNo ConnectionUnconnected pins
Address InputsTo provide memory addresses. During Sector-Erase and Hardware Sector Protection,
A
address lines will select the sector. During Block-Erase A19-A15 address
19-A11
lines will select the block.
-DQ0Data Input/OutputTo output data during Read cycles and receive input data during Write cycles
Data is internally latched during a Write cycle. The outputs are in tri-state when
OE# or CE# is high.
DQ15 is used as data I/O pin when in x16 mode (BYTE# = “1”)
and LBS Address
A-1 is used as the LSB address pin when in x8 mode (BYTE# = “0”)
RY/BY# is a open drain output, so a 10KΩ - 100KΩ pull-up resistor is required
to allow RY/BY# to transition high indicating the device is ready to read.
Program operation.
Power SupplyTo provide 2.7-3.6V power supply voltage
1. Address format A10-A0 (Hex), Addresses A19-A11 can be VIL or VIH, but no other value, for the command sequence when in x16 mode.
2. DQ
3. WA = Program word/byte address
4. SA
5. For SST36VF1601E,
6. SIWA = User Security ID Program word/byte address
7. The User Security ID Program Lock-out command must be executed in x16 mode (BYTE#=V
8. The device does not remain in Software Product Identification mode if powered down.
9. A
10. Both Software ID Exit operations are equivalent
11. If users never lock after programming, User Sec ID can be programmed over the previously unprogrammed bits (data=1) using the
10,11
When in x8 mode, Addresses A
-DQ8 can be VIL or VIH, but no other value, for the command sequence
15
for Sector-Erase; uses A19-A11 address lines
X
BA
for Block-Erase; uses A19-A15 address lines
X
SST ID is read with A
User ID is read with A
Lock Status is read with A
For SST36VF1602E,
SST ID is read with A
User ID is read with A
Lock Status is read with A
For SST36VF1601E, valid Word-Addresses for User Sec ID are from 00010H-00017H.
For SST36VF1602E, valid Word-Addresses for User Sec ID are from C0010H-C0017H.
All 4 cycles of User Security ID Program and Program Lock-out must be completed before going back to Read-Array mode.
and A18 = BKX (Bank Address): address of the bank that is switched to Software ID/CFI Mode
19
With A
= 0;SST Manufacturer’s ID = 00BFH, is read with A0 = 0
17-A1
User Sec ID mode again (the programmed “0” bits cannot be reversed to “1”).
For SST36VF1601E, valid Word-Addresses for User Sec ID are from 00010H-00017H.
For SST36VF1602E, valid Word-Addresses for User Sec ID are from C0010H-C0017H.
Absolute Maximum Stress Ratings (Applied conditions greater than those listed under “Absolute Maximum
Stress Ratings” may cause permanent damage to the device. This is a stress rating only and functional operation
of the device at these conditions or conditions greater than those defined in the operational sections of this data
sheet is not implied. Exposure to absolute maximum stress rating conditions may affect device reliability.)
Note: This device also supports CE# controlled Chip-Erase operation. The WE# and CE# signals
are interchageable as long as minimum timings are met. (See Table 14)
X can be V
Note: This device also supports CE# controlled Block-Erase operation. The WE# and CE#
signals are interchageable as long as minimum timings are met. (See Table 14)
BAX = Block Address
X can be VIL or VIH, but no other value.
Note: This device also supports CE# controlled Sector-Erase operation. The WE# and CE#
signals are interchageable as long as minimum timings are met. (See Table 14)
SA
X can be V