FUM00701
44
4.13 Clear Block Lock Bit Command
A locked block can be unlocked by writing the Clear
Block Lock Bit command. The features of clear block
lock bit is as follows:
• Any block can be independently unlocked by clearing
its block lock bit.
• The time required to be unlocked is less than the
minimum command cycle time (minimum time from
the rising edge of CE# or WE# to write the command
to the next rising edge of CE# or WE#).
• Block erase, full chip erase or (page buffer) program
on an unlocked block can be executed (see Table 11
and Table 12).
The Clear Block Lock Bit command is a two-cycle
command. At the first cycle, command (60H) and an
address within the block to be unlocked is written to the
target partition. At the second cycle, command (D0H) and
the same address as the first cycle is written. Read
operations to the target partition output the status register
data until another valid command is written. After writing
the second cycle command, the block lock bit is cleared
within the minimum command cycle time and the
corresponding block is unlocked. To check the unlock
status, write the Read Identifier Codes/OTP command
(90H) and an address within the target block. Subsequent
reads at Block Base Address +2 (see Table 6 through
Table 8) will output the lock/unlock status of that block.
The lock/unlock status is represented by the output pin
DQ0. If the output of DQ0 is "0", the block lock bit is
cleared correctly. Figure 12 shows clear block lock bit
flowchart.
The two-cycle command sequence ensures that block is
not accidentally unlocked. An invalid Clear Block Lock
Bit command sequence will result in both status register
bits SR.5 and SR.4 being set to "1" and the operation will
not be executed.
The Clear Block Lock Bit command is available when the
power supply voltage is specified level, independent of
the voltage on VPP.
4.14 Set Block Lock-Down Bit Command
The block lock-down bit, when set, increases the security
for data protection. The block lock-down bit has the
following functions.
• Any block can be independently locked-down by
setting its block lock-down bit.
• The time required to be locked-down is less than the
minimum command cycle time (minimum time from
the rising edge of CE# or WE# to write the command
to the next rising edge of CE# or WE#).
• Locked-down block is automatically locked
regardless of WP# at VIL or VIH.
• When WP# is VIL, locked-down blocks are protected
from lock status changes.
• When WP# is VIH, the lock-down bits are disabled
and locked-down blocks can be individually unlocked
by software command. These blocks can then be
re-locked and unlocked as desired while WP# remains
VIH. When WP# goes VIL, blocks that were
previously marked lock-down return to the lock-down
state regardless of any changes made while WP# was
VIH (see Table 13).
• At power-up or device reset, all blocks are not locked-
down regardless of the states before power-off or reset
operation.
(Lock-down bit is volatile.)
• Lock-down bit cannot be cleared by software, only by
power-off or device reset.
The Set Block Lock-down Bit command is a two-cycle
command. At the first cycle, command (60H) and an
address within the block to be locked-down is written to
the target partition. At the second cycle, command (2FH)
and the same address as the first cycle is written. Read
operations to the target partition output the status register
data until another valid command is written. After writing
the second cycle command, the block lock-down bit is set
within the minimum command cycle time and the
corresponding block is locked-down. To check the lock-
down status, write the Read Identifier Codes/OTP
command (90H) and an address within the target block.
Subsequent reads at Block Base Address +2 (see Table 6
through Table 8) will output the lock/unlock status of that
block. The lock-down status is represented by the output
pin DQ1. If the output of DQ1 is "1", the block lock-down
bit is set correctly. Figure 11 shows set block lock-down
bit flowchart.
Appendix to Spec No.: MFM2-J13207 Model No.: LRS1383 March 1, 2001
Rev. 2.20