MYX29GL01GS11DPIV2 Datasheet, PDF (7/68 Pages) Micross Components – Tin-lead ball metallurgy

1Gb GL-S MirrorBit^® Eclipse^™
Flash Memory
MYX29GL01GS11DPIV2*
*Advanced information. Subject to change without notice.
When a program or erase command is issued while one of the non-volatile ASOs is entered, the EA operates
on the ASO. The ASO is not readable while the EA is active. When the EA is completed the ASO remains
entered and is again readable. Suspend and Resume commands are ignored during an EA operating on any
of these ASOs.
2.1
Flash Memory Array
The MYX29GL01GS11DPIV2 family has an uniform sector architecture with a sector size of 128 kB.
Table 3: MYX29GL01GS11DPIV2 Sector and Memory Address Map
Sector Size (kbyte) Sector Count
128
1024
Sector Range
SA00
:
SA1023
Address Range (16-Bit)
0000000h-000FFFFh
:
3FF0000h-3FFFFFFh
Notes
Sector Starting Address
–
Sector Ending Address
Note: This table has been condensed to show sector related information for an entire device on a single page
Sectors and their address ranges that are not explicitly listed (such as SA001-SA510) have sectors starting and
ending addresses that form the same pattern as all other sectors of that size. For example, all 128 kB sectors
have the pattern XXX0000h-XXXFFFFh.
2.2
Device ID and CFI (ID-CFI) ASO
There are two traditional methods for systems to identify the type of flash memory installed in the system. One
has traditionally been called Autoselect and is now referred to as Device Identification (ID). The other method is
called Common Flash Interface (CFI).
For ID, a command is used to enable an address space overlay where up to 16 word locations can be read to
get JEDEC manufacturer identification (ID), device ID, and some configuration and protection status information
from the flash memory. The system can use the manufacturer and device IDs to select the appropriate driver
software to use with the flash device.
CFI also uses a command to enable an address space overlay where an extendable table of standard
information about how the flash memory is organized and operates can be read. With this method the driver
software does not have to be written with the specifics of each possible memory device in mind. Instead the
driver software is written in a more general way to handle many different devices but adjusts the driver behavior
based on the information in the CFI table.
MYX29GL01GS11DPIV2
Revision 1.0 - 01/26/2015
7
Form #: CSI-D-685 Document 001