1.8 Volt Intel
Wireless Flash Memory with 3 Volt I/O
22
Datasheet
4.3
Read Query (CFI)
This device contains a separate CFI query
database
that acts as an “on-chip datasheet.” The CFI
information within this device can be accessed by issuing the Read Query command and supplying
a specific address. The address is constructed from the base address of a partition plus a particular
offset corresponding to the desired CFI field.
Appendix B, “Common Flash Interface” on page 80
shows accessible CFI fields and their address offsets. Issuing the Read Query command to a
partition that is programming or erasing puts that partition in read query mode while the partition
continues to program or erase in the background.
4.4
Read Status Register
The device’s status register displays program and erase operation status. A partition’s status can be
read after writing the Read Status Register command to any location within the partition’s address
range. Read-status mode is the default read mode following a Program, Erase, or Lock Block
command sequence. Subsequent single reads from that partition will return its status until another
valid command is written.
Table 7.
Device Identification Codes
Item
Address
1
Data
Description
Base
Offset
Manufacturer ID
Partition
00h
0089h
Device ID
Partition
01h
8852h
32-Mbit TPD
8853h
32-Mbit BPD
8854h
64-Mbit TPD
8855h
64-Mbit BPD
8856h
128-Mbit TPD
8857h
128-Mbit BPD
Block Lock Status
(2)
Block
02h
D0 = 0
Block is unlocked
D0 = 1
Block is locked
Block Lock-Down Status
(2)
Block
02h
D1 = 0
Block is not locked-down
D1 = 1
Block is locked down
Configuration Register
Partition
05h
Register Data
Protection Register Lock Status
Partition
80h
Lock Data
Protection Register
Partition
81h - 88h
Register Data
Multiple reads required to read
the entire 128-bit Protection
Register.
NOTES:
1. The address is constructed from a base address plus an offset. For example, to read the Block Lock Status
for block number 38 in a BPD, set the address to the BBA (0F8000h) plus the
offset
(02h), i.e. 0F8002h.
Then examine bit 0 of the data to determine if the block is locked.
2. See
Section 7.1.4, “Block Lock Status” on page 38
for valid lock status.