TE28F640J3A-150

Manufacturer Part NumberTE28F640J3A-150
DescriptionTE28F640J3A-150Intel StrataFlash Memory (J3)
ManufacturerIntel Corporation
TE28F640J3A-150 datasheet
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
Page 41
42
Page 42
43
Page 43
44
Page 44
45
Page 45
46
Page 46
47
Page 47
48
Page 48
49
Page 49
50
Page 50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
Page 44/72:

Erase Operations

Download datasheet (552Kb)Embed
PrevNext
256-Mbit J3 (x8/x16)
12.0

Erase Operations

Flash erasing is performed on a block basis; therefore, only one block can be erased at a time. Once
a block is erased, all bits within that block will read as a logic level one. To determine the status of
a block erase, poll the Status Register and analyze the bits. This following section describes block
erase operations in detail.
12.1
Block Erase
Erase is executed one block at a time and initiated by a two-cycle command. A block erase setup is
first written, followed by an block erase confirm. This command sequence requires an appropriate
address within the block to be erased (erase changes all block data to FFH). Block preconditioning,
erase, and verify are handled internally by the WSM (invisible to the system). After the two-cycle
block erase sequence is written, the device automatically outputs SRD when read (see
“Block Erase Flowchart” on page
the output of the STS signal or SR.7. Toggle OE#, CE0, CE1, or CE2 to update the Status Register.
When the block erase is complete, SR.5 should be checked. If a block erase error is detected, the
Status Register should be cleared before system software attempts corrective actions. The CUI
remains in Read Status Register mode until a new command is issued.
This two-step command sequence of setup followed by execution ensures that block contents are
not accidentally erased. An invalid Block Erase command sequence will result in both SR.4 and
SR.5 being set. Also, reliable block erasure can only occur when V
If block erase is attempted while V
erase requires that the corresponding block lock-bit be cleared. If block erase is attempted when the
corresponding block lock-bit is set, SR.1 and SR.5 will be set.
12.2
Block Erase Suspend
The Block Erase Suspend command allows block-erase interruption to read or program data in
another block of memory. Once the block erase process starts, writing the Block Erase Suspend
command requests that the WSM suspend the block erase sequence at a predetermined point in the
algorithm. The device outputs SRD when read after the Block Erase Suspend command is written.
Polling SR.7 then SR.6 can determine when the block erase operation has been suspended (both
will be set). In default mode, STS will also transition to V
block erase suspend latency.
At this point, a Read Array command can be written to read data from blocks other than that which
is suspended. A program command sequence can also be issued during erase suspend to program
data in other blocks. During a program operation with block erase suspended, SR.7 will return to
“0” and STS output (in default mode) will transition to V
indicate block erase suspend status. Using the Program Suspend command, a program operation
can also be suspended. Resuming a suspended programming operation by issuing the Program
Resume command allows continuing of the suspended programming operation. To resume the
suspended erase, the user must wait for the programming operation to complete before issuing the
Block Erase Resume command.
44
63). The CPU can detect block erase completion by analyzing
CC
≤ V
, SR.3 and SR.5 will be set. Successful block
PEN
PENLK
. Specification t
OH
. However, SR.6 will remain “1” to
OL
Figure 22,
is valid and V
= V
.
PEN
PENH
defines the
WHRH
Datasheet