Numonyx™ Embedded Flash Memory (J3 v. D)
The Configuration command may only be given when the device is not busy or
suspended. Check SR.7 for device status. An invalid configuration code will result in
SR.4 and SR.5 being set.
Note:
STS Pulse mode is not supported in the Clear Lock Bits and Set Lock Bit commands.
Table 26: STS Configuration Coding Definitions
D7
D6
D5
D4
D3
D2
D1
D0
Pulse on
Program
Complete (1)
Pulse on Erase
Complete (1)
Reserved
D[1:0] = STS Configuration
Codes
Notes
00 = default, level mode; device
ready indication
Controls HOLD to a memory controller to prevent accessing a flash memory subsystem
while any flash device's WSM is busy.
Generates a system interrupt pulse when any flash device in an array has completed a
block erase. Helpful for reformatting blocks after file system free space reclamation or
“cleanup.”
01 = pulse on Erase Complete
10 = pulse on Program Complete
Not supported on this device.
11 = pulse on Erase or Program
Complete
Generates system interrupts to trigger servicing of flash arrays when either erase or
program operations are completed, when a common interrupt service routine is desired.
Notes:
1.
2.
3.
When configured in one of the pulse modes, STS pulses low with a typical pulse width of 500 ns.
An invalid configuration code will result in both SR4 and SR5 being set.
Reserved bits are invalid should be ignored.
9.7
Security and Protection
Numonyx™ Embedded Flash Memory (J3 v. D) device offer both hardware and software
security features. Block lock operations, PRs and VPEN allow users to implement
various levels of data protection.
9.7.1
Normal Block Locking
Numonyx™ Embedded Flash Memory (J3 v. D) has the unique capability of Flexible
Block Locking (locked blocks remain locked upon reset or power cycle): All blocks are
unlocked at the factory. Blocks can be locked individually by issuing the Set Block Lock
Bit command sequence to any address within a block. Once locked, blocks remain
locked when power is removed, or when the device is reset.
All locked blocks are unlocked simultaneously by issuing the Clear Block Lock Bits
command sequence to any device address. Locked blocks cannot be erased or
programmed. Table 27 summarizes the command bus-cycles.
Table 27: Block Locking Command Bus-Cycles
Setup Write Cycle
Confirm Write Cycle
Command
Address Bus
Data Bus
Address Bus
Data Bus
Set Block Lock Bit
Block Address1
Device Address2
0060h
0060h
Block Address
Device Address
0001h
00D0h
Clear Block Lock Bits
Notes:
1.
2.
In case of 256 Mb device (2x128), the command should be issued to the base address of the die
In case of 256 Mb device (2x128), the command sequence must be repeated for each die at its base address
November 2007
308551-05
Datasheet
43