NP8P128A13BSM60E Micron Technology Inc, NP8P128A13BSM60E Datasheet - Page 32

• Manufacturer Part Number: NP8P128A13BSM60E
• Manufacturer: Micron Technology Inc

Specifications of NP8P128A13BSM60E

• Lead Free Status / Rohs Status: Supplier Unconfirmed

10.1.7
Table 14: Block Locking State Transitions
Notes:
1.
2.
3.
4.
5.
Datasheet
32
WP#
0
0
0
0
1
1
1
1
Additional illegal states are shown but are not recommended for normal, non-erroneous operational modes.
“Erase/Write Allowed?” shows whether a block’s current locking state allows erase or write.
At power-up or device reset, blocks default to locked state [001] if WP# = 0, the recommended default.
Blocks in “virtual lock-down” appear to be in locked-down state when WP#=V
[110].
This column shows results of writing the four locking commands via WP# toggle from the current locking state.
LAT
1
0
0
1
1
0
0
1
1
LAT
Locking Operations During Erase Suspend
Block lock configurations can be performed during an erase suspend by using the
standard locking command sequences to unlock, lock, or lock-down a block. This is
useful when another block needs to be updated while an erase operation is suspended.
To change block locking during an erase operation, first write the Erase Suspend
command, then check the Status Register until it indicates that the erase operation has
suspended. Next write the desired lock command sequence to a block; the lock state
will be changed. After completing lock, read, or program operations, resume the erase
operation with the Erase Resume command (D0h).
If a block is locked or locked-down during a suspended erase of the same block, the
locking status bits will change immediately. But, when resumed, the erase operation
will complete. Locking operations cannot occur during write suspend.
“Write State Machine” on page 80
Nested lock or write commands during erase suspend can return ambiguous Status
Register results. 60h followed by 01h commands lock a block. A Configuration Setup
command (60h) followed by an invalid command produces a lock command Status
Register error (SR.4 and SR.5 = 1). If this error occurs during erase suspend, SR.4 and
SR.5 remain at 1 after the erase resumes. When erase completes, the previous locking
command error hides the Status Register’s erase errors. A similar situation occurs if a
write operation error is nested within an erase suspend.
Current State
0
0
1
0
1
0
1
0
1
Unlocked
Locked (default)
Virtual lock-down
Locked-Down
Unlocked
Locked
Lock-Down Disabled
Lock-Down Disabled
Name
(1)
(4)
Erase/Write
Allowed?
Yes
Yes
Yes
No
No
No
No
No
shows valid commands during erase suspend.
(1)
000
000
011
011
100
100
110
110
Lock Command Input Result
UnLock
(Next State)
001
001
011
011
101
101
111
111
Lock
IL
. WP# = 1 changes [010] to unlocked state
Numonyx® Omneo™ P8P Datasheet
(5)
011
011
011
011
111
111
111
111
Down
Lock-
100
101
110
111
000
001
010
011
Toggle
Result
State)
(Next
WP#
Appendix A,
August 2010
D1
Readout
Locking
0
0
1
1
0
0
1
1
Status
316144-07
D0
0
1
1
1
0
1
0
1