欢迎访问ic37.com |
会员登录 免费注册
发布采购

SST36VF3204-70-4E-B3KE 参数 Datasheet PDF下载

SST36VF3204-70-4E-B3KE图片预览
型号: SST36VF3204-70-4E-B3KE
PDF下载: 下载PDF文件 查看货源
内容描述: 32兆位( X8 / X16 )并行的SuperFlash [32 Mbit (x8/x16) Concurrent SuperFlash]
分类和应用: 内存集成电路
文件页数/大小: 34 页 / 432 K
品牌: SST [ SILICON STORAGE TECHNOLOGY, INC ]
 浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第1页浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第2页浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第4页浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第5页浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第6页浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第7页浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第8页浏览型号SST36VF3204-70-4E-B3KE的Datasheet PDF文件第9页  
32 Mbit Concurrent SuperFlash
SST36VF3203 / SST36VF3204
Data Sheet
Sector- (Block-) Erase Operation
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 Sector-
Erase command (50H) and sector address (SA) in the last
bus cycle. The Block-Erase operation is initiated by execut-
ing a six-byte command sequence with Block-Erase com-
mand (30H) 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 inter-
nal Erase operation begins after the sixth WE# pulse. Any
commands issued during the Sector- or Block-Erase opera-
tion are ignored except Erase-Suspend and Erase-
Resume. See Figures 9 and 10 for timing waveforms.
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 erase-
suspended sectors/blocks will output DQ
2
toggling and
DQ
6
at “1”. While in Erase-Suspend mode, a Program
operation is allowed except for the sector or block selected
for Erase-Suspend. The Software ID Entry command can
also be executed. To resume Sector-Erase or Block-Erase
operation which has been suspended, the system must
issue an Erase-Resume command. The operation is exe-
cuted by issuing a one-byte command sequence with
Erase Resume command (30H) at any address in the last
byte sequence.
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 six-
byte 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 com-
mands issued during the Chip-Erase operation are
ignored. See Table 7 for the command sequence, Figure 8
for timing diagram, and Figure 22 for the flowchart. When
WP# is low, any attempt to Chip-Erase will be ignored.
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 sta-
tus bits: Data# Polling (DQ
7
) and Toggle Bit (DQ
6
). The
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 asynchro-
nous with the system; therefore, either a Ready/Busy# (RY/
BY#), a Data# Polling (DQ
7
), or Toggle Bit (DQ
6
) Read may
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
7
or DQ
6
. In
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, other-
wise the rejection is valid.
©2005 Silicon Storage Technology, Inc.
S71270-03-000
7/06
3