28F640L30, 28F128L30, 28F256L30
possible output states during commands: Read Array, Read Status or Read ID/CFI, depending on the
command given to the chip; This partition's output state is retained until a new command is given to the chip
at that Partition Address; For example, this allows the user to set partition #1's output state to Read Array,
and partition #4's output state to Read Status; Every time the partition address is changed to partition #4
(without issuing a new command), the Status will be read from the chip.
2. "Illegal commands" include commands outside of the allowed command set (allowed commands: 40H [pgm],
20H [erase], etc.)
3. If a "Read Array" is attempted from a busy partition, the result will be "garbage" data. The key point is that the
output mux for that partition will be pointing to the "array", but garbage data will be output. When the user
returns to this partition address some time in the future, the output mux will be in the "Read Array" state from
its last visit. "Read ID" and "Read Query" commands do the exact same thing in the device. The ID and
Query data are located at different locations in the address map.
4. 1st and 2nd cycles of "2 cycles write commands" must be given to the same partition address, or unexpected
results will occur.
5. The 2nd cycle of the following 2 cycle commands will be ignored by the user interface: Program Setup, Erase
Setup, OTP Setup and Lock/Unlock/Lock-down/CR setup when issued in an "illegal condition". Illegal
conditions are such as "pgm setup while busy", "erase setup while busy", etc.
6. The Clear Status command only clears the error bits in the status register if the device is not in the following
modes: WSM running (Pgm Busy, Erase Busy, Pgm Busy In Erase Suspend, OTP Busy, BEFP modes).
7. BEFP writes are only allowed when the status register bit #0 = 0, or else the data is ignored.
8. The "current state" is that of the "chip" and not of the "partition"; Each partition "remembers" which output
(Array, ID/CFI or Status) it was last pointed to on the last instruction to the "chip", but the next state of the chip
does not depend on where the partition's output mux is presently pointing to.
9. Confirm commands (Lock Block, Unlock Block, Lock-Down Block, Configuration Register) perform the
operation and then move to the Ready State.
10.All two cycle commands will be considered as a contiguous whole during device suspend states. Individual
commands will not be parsed separately. Thus for example the second cycle of an erase command issued in
program suspend will NOT resume the program operation.
Datasheet
73
INTEL [ INTEL ]
