M29W160ET, M29W160EB
APPENDIX C. BLOCK PROTECTION
Block protection can be used to prevent any oper-
ation from modifying the data stored in the Flash
memory. Each Block can be protected individually.
Once protected, Program and Erase operations
on the block fail to change the data.
There are three techniques that can be used to
control Block Protection, these are the Program-
mer technique, the In-System technique and Tem-
porary Unprotection. Temporary Unprotection is
controlled by the Reset/Block Temporary Unpro-
tection pin, RP; this is described in the Signal De-
scriptions section.
Programmer Equipment Chip Unprotect Flow-
chart. Table 27, Programmer Technique Bus Op-
erations, gives a summary of each operation.
The timing on these flowcharts is critical. Care
should be taken to ensure that, where a pause is
specified, it is followed as closely as possible. Do
not abort the procedure before reaching the end.
Chip Unprotect can take several seconds and a
user message should be provided to show that the
operation is progressing.
In-System Technique
The In-System technique requires a high voltage
level on the Reset/Blocks Temporary Unprotect
pin, RP. This can be achieved without violating the
maximum ratings of the components on the micro-
processor bus, therefore this technique is suitable
for use after the Flash memory has been fitted to
the system.
Unlike the Command Interface of the Program/
Erase Controller, the techniques for protecting and
unprotecting blocks could change between differ-
ent Flash memory suppliers.
Programmer Technique
The Programmer technique uses high (V ) volt-
ID
age levels on some of the bus pins. These cannot
be achieved using a standard microprocessor bus,
therefore the technique is recommended only for
use in Programming Equipment.
To protect a block follow the flowchart in Figure 19,
In-System Block Protect Flowchart. To unprotect
the whole chip it is necessary to protect all of the
blocks first, then all the blocks can be unprotected
at the same time. To unprotect the chip follow Fig-
ure 20, In-System Chip Unprotect Flowchart.
The timing on these flowcharts is critical. Care
should be taken to ensure that, where a pause is
specified, it is followed as closely as possible. Do
not allow the microprocessor to service interrupts
that will upset the timing and do not abort the pro-
cedure before reaching the end. Chip Unprotect
can take several seconds and a user message
should be provided to show that the operation is
progressing.
To protect a block follow the flowchart in Figure 17,
Programmer Equipment Block Protect Flowchart.
During the Block Protect algorithm, the A19-A12
Address Inputs indicate the address of the block to
be protected. The block will be correctly protected
only if A19-A12 remain valid and stable, and if
Chip Enable is kept Low, V , all along the Protect
IL
and Verify phases.
The Chip Unprotect algorithm is used to unprotect
all the memory blocks at the same time. This algo-
rithm can only be used if all of the blocks are pro-
tected first. To unprotect the chip follow Figure 18,
Table 27. Programmer Technique Bus Operations, BYTE = V or V
IH
IL
Address Inputs
Data Inputs/Outputs
DQ15A–1, DQ14-DQ0
Operation
E
G
W
A0-A19
A9 = V , A12-A19 Block Address
ID
V
V
V
V
Pulse
Pulse
Block Protect
X
X
IL
ID
ID
IL
IL
Others = X
A9 = V , A12 = V , A15 = V
ID
IH
IH
V
V
Chip Unprotect
ID
Others = X
A0 = V , A1 = V , A6 = V , A9 = V ,
IL
IH
IL
ID
Block Protection
Verify
Pass = XX01h
Retry = XX00h
V
V
V
V
V
A12-A19 Block Address
Others = X
IL
IL
IL
IL
IH
IH
A0 = V , A1 = V , A6 = V , A9 = V ,
IL
IH
IH
ID
Block Unprotection
Verify
Retry = XX01h
Pass = XX00h
V
A12-A19 Block Address
Others = X
34/40
NUMONYX [ NUMONYX B.V ]
