MX68GL1G0F DATASHEET

MX68GL1G0F
MX68GL1G0F
DATASHEET
P/N:PM1727
REV. 1.3, OCT. 30, 2013
1
MX68GL1G0F
Contents
1. FEATURES......................................................................................................................................................... 5
2. PIN CONFIGURATION....................................................................................................................................... 6
3. PIN DESCRIPTION............................................................................................................................................. 7
4. BLOCK DIAGRAM.............................................................................................................................................. 8
5. BLOCK DIAGRAM DESCRIPTION.................................................................................................................... 9
6. BLOCK STRUCTURE....................................................................................................................................... 10
Table 1. SECTOR ARCHITECTURE ................................................................................................... 10
7. BUS OPERATION..............................................................................................................................................11
Table 2. BUS OPERATION-1............................................................................................................... 11
Table 3. BUS OPERATION-2............................................................................................................... 12
8. FUNCTIONAL OPERATION DESCRIPTION................................................................................................... 13
8-1. READ OPERATION............................................................................................................................. 13
8-2. PAGE READ........................................................................................................................................ 13
8-3. WRITE OPERATION........................................................................................................................... 13
8-4. WRITE BUFFER PROGRAMMING OPERATION............................................................................... 13
8-5. DEVICE RESET................................................................................................................................... 14
8-6. STANDBY MODE................................................................................................................................ 14
8-7. OUTPUT DISABLE.............................................................................................................................. 14
8-8. BYTE/WORD SELECTION.................................................................................................................. 15
8-9. HARDWARE WRITE PROTECT......................................................................................................... 15
8-10. ACCELERATED PROGRAMMING OPERATION ............................................................................... 15
8-11. SECTOR PROTECT OPERATION...................................................................................................... 15
8-12. AUTOMATIC SELECT BUS OPERATIONS........................................................................................ 15
8-13. SECTOR LOCK STATUS VERIFICATION........................................................................................... 15
8-14. READ SILICON ID MANUFACTURER CODE.................................................................................... 16
8-15. READ INDICATOR BIT (Q7) FOR SECURITY SECTOR.................................................................... 16
8-16. INHERENT DATA PROTECTION........................................................................................................ 16
8-17. COMMAND COMPLETION................................................................................................................. 16
8-18. LOW VCC WRITE INHIBIT.................................................................................................................. 16
8-19. WRITE PULSE "GLITCH" PROTECTION........................................................................................... 16
8-20. LOGICAL INHIBIT................................................................................................................................ 16
8-21. POWER-UP SEQUENCE.................................................................................................................... 17
8-22. POWER-UP WRITE INHIBIT............................................................................................................... 17
8-23. POWER SUPPLY DECOUPLING........................................................................................................ 17
9. COMMAND OPERATIONS............................................................................................................................... 18
9-1. READING THE MEMORY ARRAY...................................................................................................... 18
9-2. AUTOMATIC PROGRAMMING OF THE MEMORY ARRAY.............................................................. 18
9-3. ERASING THE MEMORY ARRAY....................................................................................................... 19
9-4. SECTOR ERASE................................................................................................................................. 19
9-5. CHIP ERASE...................................................................................................................................... 20
9-6. ERASE SUSPEND/RESUME.............................................................................................................. 21
9-7. SECTOR ERASE RESUME................................................................................................................ 21
9-8. PROGRAM SUSPEND/RESUME....................................................................................................... 22
P/N:PM1727
REV. 1.3, OCT. 30, 2013
2
MX68GL1G0F
9-9. PROGRAM RESUME.......................................................................................................................... 22
9-10. BUFFER WRITE ABORT..................................................................................................................... 22
9-11. AUTOMATIC SELECT OPERATIONS................................................................................................. 23
9-12. AUTOMATIC SELECT COMMAND SEQUENCE................................................................................ 23
9-13. READ MANUFACTURER ID OR DEVICE ID...................................................................................... 23
9-14.RESET ................................................................................................................................................ 24
9-15. Advanced Sector Protection/Un-protection.......................................................................................... 25
Figure 1. Advance Sector Protection/Unprotection SPB Program Algorithm....................................... 25
9-15-1.Lock Register........................................................................................................................... 26
Figure 2. Lock Register Program Algorithm......................................................................................... 26
9-15-2.Solid Protection Mode............................................................................................................. 27
9-15-3.Temporary Un-protect Solid write Protect Bits (USPB)............................................................ 28
Figure 3. SPB Program Algorithm........................................................................................................ 28
9-15-4.Solid Protection Bit Lock Bit.................................................................................................... 29
9-15-5.Password Protection Method................................................................................................... 29
Table 4. Sector Protection Status......................................................................................................... 30
9-16. SECURITY SECTOR FLASH MEMORY REGION.............................................................................. 31
9-17. FACTORY LOCKED: SECURITY SECTOR PROGRAMMED AND PROTECTED AT THE FACTORY.. ............................................................................................................................................................. 31
9-18. CUSTOMER LOCKABLE: SECURITY SECTOR NOT PROGRAMMED OR PROTECTED AT THE .... FACTORY............................................................................................................................................ 31
Table 5. COMMAND DEFINITIONS..................................................................................................... 32
10. COMMON FLASH MEMORY INTERFACE (CFI) MODE............................................................................... 35
Table 6. CFI mode: Identification Data Values..................................................................................... 35
Table 7. CFI mode: System Interface Data Values.............................................................................. 35
Table 8. CFI mode: Device Geometry Data Values.............................................................................. 36
Table 9. CFI mode: Primary Vendor-Specific Extended Query Data Values........................................ 37
11. ELECTRICAL CHARACTERISTICS............................................................................................................... 38
11-1. ABSOLUTE MAXIMUM STRESS RATINGS....................................................................................... 38
11-2. OPERATING TEMPERATURE AND VOLTAGE.................................................................................. 38
Figure 4. Maximum Negative Overshoot Waveform............................................................................ 38
Figure 5. Maximum Positive Overshoot Waveform.............................................................................. 38
Table 10. DC CHARACTERISTICS..................................................................................................... 39
Figure 6. SWITCHING TEST CIRCUITS............................................................................................. 40
Figure 7. SWITCHING TEST WAVEFORMS...................................................................................... 40
Table 11. AC CHARACTERISTICS...................................................................................................... 41
12. WRITE COMMAND OPERATION................................................................................................................... 43
Figure 8. COMMAND WRITE OPERATION........................................................................................ 43
13. READ/RESET OPERATION........................................................................................................................... 44
Figure 9. READ TIMING WAVEFORMS.............................................................................................. 44
Table 12. AC CHARACTERISTICS-RESET#....................................................................................... 45
Figure 10. RESET# TIMING WAVEFORM.......................................................................................... 45
14. ERASE/PROGRAM OPERATION.................................................................................................................. 46
Figure 11. AUTOMATIC CHIP ERASE TIMING WAVEFORM............................................................. 46
Figure 12. AUTOMATIC CHIP ERASE ALGORITHM FLOWCHART................................................... 47
P/N:PM1727
REV. 1.3, OCT. 30, 2013
3
MX68GL1G0F
Figure 13. AUTOMATIC SECTOR ERASE TIMING WAVEFORM....................................................... 48
Figure 14. AUTOMATIC SECTOR ERASE ALGORITHM FLOWCHART............................................ 49
Figure 15. ERASE SUSPEND/RESUME FLOWCHART..................................................................... 50
Figure 16. AUTOMATIC PROGRAM TIMING WAVEFORMS.............................................................. 51
Figure 17. ACCELERATED PROGRAM TIMING DIAGRAM............................................................... 51
Figure 18. CE# CONTROLLED WRITE TIMING WAVEFORM........................................................... 52
Figure 19. AUTOMATIC PROGRAMMING ALGORITHM FLOWCHART............................................ 53
15. SILICON ID READ OPERATION.................................................................................................................... 54
Figure 20. SILICON ID READ TIMING WAVEFORM........................................................................... 54
16. WRITE OPERATION STATUS........................................................................................................................ 55
Figure 21. DATA# POLLING TIMING WAVEFORMS (DURING AUTOMATIC ALGORITHMS)........... 55
Figure 22. STATUS POLLING FOR PROGRAM/ERASE.................................................................... 56
Figure 23. STATUS POLLING FOR WRITE BUFFER PROGRAM..................................................... 57
Figure 24. TOGGLE BIT TIMING WAVEFORMS (DURING AUTOMATIC ALGORITHMS)................ 58
Figure 25. TOGGLE BIT ALGORITHM................................................................................................ 59
17. PAGE READ OPERATION............................................................................................................................. 60
Figure 26. BYTE# TIMING WAVEFORM FOR READ OPERATIONS (BYTE# switching from byte
mode to word mode)............................................................................................................................ 60
Figure 27. PAGE READ TIMING WAVEFORM.................................................................................... 61
18. DEEP POWER DOWN MODE OPERATION.................................................................................................. 62
Table 13. AC CHARACTERISTICS - Deep Power Down Mode........................................................... 62
Figure 28. DEEP POWER DOWN MODE WAVEFORM ..................................................................... 62
19. WRITE BUFFER PROGRAM OPERATION................................................................................................... 63
Figure 29. WRITE BUFFER PROGRAM FLOWCHART...................................................................... 63
20. RECOMMENDED OPERATING CONDITIONS.............................................................................................. 64
Figure 30. AC Timing at Device Power-Up........................................................................................... 64
21. ERASE AND PROGRAMMING PERFORMANCE......................................................................................... 65
22. DATA RETENTION......................................................................................................................................... 65
23. LATCH-UP CHARACTERISTICS................................................................................................................... 65
24. PIN CAPACITANCE........................................................................................................................................ 65
25. ORDERING INFORMATION........................................................................................................................... 66
26. PART NAME DESCRIPTION.......................................................................................................................... 67
27. PACKAGE INFORMATION............................................................................................................................. 68
28. REVISION HISTORY ...................................................................................................................................... 70
P/N:PM1727
REV. 1.3, OCT. 30, 2013
4
MX68GL1G0F
SINGLE VOLTAGE 3V ONLY FLASH MEMORY
1. FEATURES
GENERAL FEATURES
• 2.7 to 3.6 volt for read, erase, and program operations
• Byte/Word mode switchable
- 134,217,728 x 8 / 67,108,864 x 16
• 64KW/128KB uniform sector architecture
- 1024 equal sectors
• 16-byte/8-word page read buffer
• 64-byte/32-word write buffer
• Extra 128-word sector for security
- Features factory locked and identifiable, and customer lockable
• Advanced sector protection function (Solid and Password Protect)
• Compatible with JEDEC standard
- Pinout and software compatible to single power supply Flash
PERFORMANCE
• High Performance
- Fast access time:
- MX68GL1G0F H/L: 110ns (VCC=2.7~3.6V)
- MX68GL1G0F U/D: 120ns (VCC=2.7~3.6V, V I/O=1.65 to VCC)
- Page access time:
- MX68GL1G0F H/L: 25ns
- MX68GL1G0F U/D: 30ns
- Fast program time: 10us/word
- Fast erase time: 0.5s/sector
• Low Power Consumption
- Low active read current: 10mA (typical) at 5MHz
- Low standby current: 60uA (typical)
• Minimum 100,000 erase/program cycle
• 20 years data retention
SOFTWARE FEATURES
• Program/Erase Suspend & Program/Erase Resume
• Status Reply
- Data# Polling & Toggle bits provide detection of program and erase operation completion
• Support Common Flash Interface (CFI)
HARDWARE FEATURES
• Ready/Busy# (RY/BY#) Output
- Provides a hardware method of detecting program and erase operation completion
• Hardware Reset (RESET#) Input
- Provides a hardware method to reset the internal state machine to read mode
• WP#/ACC input pin
- Hardware write protect pin/Provides accelerated program capability
PACKAGE
• 56-Pin TSOP
• 64-Ball LFBGA (11mm x 13mm)
• All devices are RoHS Compliant and Halogen-free
P/N:PM1727
REV. 1.3, OCT. 30, 2013
5
MX68GL1G0F
2. PIN CONFIGURATION
56 TSOP
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
A23
A22
A15
A14
A13
A12
A11
A10
A9
A8
A19
A20
WE#
RESET#
A21
WP#/ACC
RY/BY#
A18
A17
A7
A6
A5
A4
A3
A2
A1
NC
NC
56
55
54
53
52
51
50
49
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
A24
A25
A16
BYTE#
GND
Q15/A-1
Q7
Q14
Q6
Q13
Q5
Q12
Q4
VCC
Q11
Q3
Q10
Q2
Q9
Q1
Q8
Q0
OE#
GND
CE#
A0
NC
VI/O
64 LFBGA
8
NC
A22
A23
VIO
GND
A24
A25
NC
7
A13
A12
A14
A15
A16
BYTE#
Q15/
A-1
GND
6
A9
A8
A10
A11
Q7
Q14
Q13
Q6
5
WE#
RESET#
A21
A19
Q5
Q12
VCC
Q4
4
RY/
BY#
WP#/
ACC
A18
A20
Q2
Q10
Q11
Q3
3
A7
A17
A6
A5
Q0
Q8
Q9
Q1
2
A3
A4
A2
A1
A0
CE#
OE#
GND
1
NC
NC
NC
NC
NC
VIO
NC
NC
C
D
E
F
G
H
A
B
P/N:PM1727
REV. 1.3, OCT. 30, 2013
6
MX68GL1G0F
3. PIN DESCRIPTION
LOGIC SYMBOL
SYMBOL PIN NAME
A0~A25
Q0~Q14
Q15/A-1
CE#
WE#
OE#
RESET#
26
Address Input
Data Inputs/Outputs
Q15(Word Mode)/LSB addr(Byte Mode)
Chip Enable Input
Write Enable Input
Output Enable Input
Hardware Reset Pin, Active Low
A0-A25
Q0-Q15
(A-1)
16 or 8
CE#
OE#
Hardware Write Protect/Programming
WP#/ACC*
Acceleration input
RY/BY# Ready/Busy Output
BYTE# Selects 8 bits or 16 bits mode
VCC
+3.0V single power supply
GND
Device Ground
NC
Not Connected
VI/O
Power Supply for Input/Output
WE#
RESET#
WP#/ACC
RY/BY#
BYTE#
VI/O
Notes:
1. WP#/ACC has internal pull up.
2. VI/O voltage must tight with VCC for MX68GL1G0F H/L.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
7
MX68GL1G0F
4. BLOCK DIAGRAM
CE#
OE#
WE#
RESET#
BYTE#
WP#/ACC
CONTROL
INPUT
LOGIC
PROGRAM/ERASE
STATE
HIGH VOLTAGE
MACHINE
(WSM)
LATCH
BUFFER
FLASH
REGISTER
ARRAY
ARRAY
Y-DECODER
AND
STATE
X-DECODER
ADDRESS
A0-AM
WRITE
Y-PASS GATE
SOURCE
HV
COMMAND
DATA
DECODER
SENSE
AMPLIFIER
PGM
DATA
HV
COMMAND
DATA LATCH
PROGRAM
DATA LATCH
Q0-Q15/A-1
I/O BUFFER
AM: MSB address
P/N:PM1727
REV. 1.3, OCT. 30, 2013
8
MX68GL1G0F
5. BLOCK DIAGRAM DESCRIPTION
The "BLOCK DIAGRAM" illustrates a simplified architecture of this device. Each block in the block diagram represents one or more circuit modules in the real chip used to access, erase, program, and read the memory array.
The "CONTROL INPUT LOGIC" block receives input pins CE#, OE#, WE#, RESET#, BYTE#, and WP#/ACC.
It creates internal timing control signals according to the input pins and outputs to the "ADDRESS LATCH AND
BUFFER" to latch the external address pins A0-AM. The internal addresses are output from this block to the
main array and decoders composed of "X-DECODER", "Y-DECODER", "Y-PASS GATE", AND "FLASH ARRAY".
The X-DECODER decodes the word-lines of the flash array, while the Y-DECODER decodes the bit-lines of the
flash array. The bit lines are electrically connected to the "SENSE AMPLIFIER" and "PGM DATA HV" selectively
through the Y-PASS GATES. SENSE AMPLIFIERS are used to read out the contents of the flash memory, while
the "PGM DATA HV" block is used to selectively deliver high power to bit-lines during programming. The "I/O
BUFFER" controls the input and output on the Q0-Q15/A-1 pads. During read operation, the I/O BUFFER receives data from SENSE AMPLIFIERS and drives the output pads accordingly. In the last cycle of program command, the I/O BUFFER transmits the data on Q0-Q15/A-1 to "PROGRAM DATA LATCH", which controls the high
power drivers in "PGM DATA HV" to selectively program the bits in a word or byte according to the user input
pattern.
The "PROGRAM/ERASE HIGH VOLTAGE" block comprises the circuits to generate and deliver the necessary
high voltage to the X-DECODER, FLASH ARRAY, and "PGM DATA HV" blocks. The logic control module comprises of the "WRITE STATE MACHINE, WSM", "STATE REGISTER", "COMMAND DATA DECODER", and
"COMMAND DATA LATCH". When the user issues a command by toggling WE#, the command on Q0-Q15/A-1
is latched in the COMMAND DATA LATCH and is decoded by the COMMAND DATA DECODER. The STATE
REGISTER receives the command and records the current state of the device. The WSM implements the internal algorithms for program or erase according to the current command state by controlling each block in the
block diagram.
ARRAY ARCHITECTURE
The main flash memory array can be organized as Byte mode (x8) or Word mode (x16). The details of the address ranges and the corresponding sector addresses are shown in Table 1 .
P/N:PM1727
REV. 1.3, OCT. 30, 2013
9
MX68GL1G0F
6. BLOCK STRUCTURE
Table 1. SECTOR ARCHITECTURE
Kbytes
128
128
128
:
:
128
Sector Size
Kwords
64
64
64
:
:
64
SA0
SA1
SA2
:
:
Sector Address
A25-A16
0000000000xxxx
0000000001xxxx
0000000010xxxx
:
:
Address Range
(x16)
0000000h-000FFFFh
0010000h-001FFFFh
0020000h-002FFFFh
:
:
SA1023
1111111111xxxx
3FF0000h-3FFFFFFh
Sector
P/N:PM1727
REV. 1.3, OCT. 30, 2013
10
MX68GL1G0F
7. BUS OPERATION
Table 2. BUS OPERATION-1
OE#
Address
(Note4)
Data
I/O
Q7~Q0
X
X
X
HighZ
Byte#
Vil
Vih
Data (I/O)
Q15~Q8
HighZ
HighZ
X
X
X
HighZ
HighZ
HighZ
H
H
H
X
HighZ
HighZ
HighZ
L/H
L
H
L
AIN
DOUT
DOUT
L/H
H
L
L
H
AIN
DIN
DIN
Note1,2
H
L
L
H
AIN
DIN
DIN
Vhv
RESET#
CE#
WE#
L
Vcc ±
0.3V
H
X
Vcc±
0.3V
L
Read Mode
H
Write
Accelerate Program
Mode Select
Device Reset
Standby Mode
Output Disable
Q8-Q14=
HighZ,
Q15=A-1
WP#/
ACC
L/H
Notes:
1. The first or last sector was protected if WP#/ACC=Vil.
2. When WP#/ACC = Vih, the protection conditions of the outmost sector depends on previous protection conditions. Refer to the advanced protect feature.
3. Q0~Q15 are input (DIN) or output (DOUT) pins according to the requests of command sequence, sector protection, or data polling algorithm.
4. In Word Mode (Byte#=Vih), the addresses are AM to A0, AM: MSB of address.
In Byte Mode (Byte#=Vil), the addresses are AM to A-1 (Q15), AM: MSB of address.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
11
MX68GL1G0F
Table 3. BUS OPERATION-2
Item
AM A11
to
to
CE# WE# OE# A12 A10
Control Input
A9
A8
to
A7
A6
A5
to
A4
A3
to
A2
A1
A0 Q7 ~ Q0 Q15 ~ Q8
Sector Lock Status
Verification
L
H
L
SA
X
Vhv
X
L
X
L
H
L
01h or
00h
(Note 1)
X
Read Silicon ID
Manufacturer
Code
L
H
L
X
X
Vhv
X
L
X
L
L
L
C2H
X
Cycle 1
L
H
L
X
X
Vhv
X
L
X
L
L
H
7EH
Cycle 2
L
H
L
X
X
Vhv
X
L
X
H
H
L
28H
Cycle 3
L
H
L
X
X
Vhv
X
L
X
H
H
H
01H
Read Silicon ID
22H(Word),
XXH(Byte)
22H(Word),
XXH(Byte)
22H(Word),
XXH(Byte)
Notes:
1. Sector unprotected code:00h. Sector protected code:01h.
2. Factory locked code: WP# protects high address sector: 99h.
WP# protects low address sector: 89h
Factory unlocked code: WP# protects high address sector: 19h.
WP# protects low address sector: 09h
3. AM: MSB of address.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
12
MX68GL1G0F
8. FUNCTIONAL OPERATION DESCRIPTION
8-1. READ OPERATION
To perform a read operation, the system addresses the desired memory array or status register location by providing its address on the address pins and simultaneously enabling the chip by driving CE# & OE# LOW, and
WE# HIGH. After the Tce and Toe timing requirements have been met, the system can read the contents of the
addressed location by reading the Data (I/O) pins. If either the CE# or OE# is held HIGH, the outputs will remain
tri-stated and no data will appear on the output pins.
8-2. PAGE READ
This device offered high performance page read. Page size is 16 bytes or 8 words. The higher address Amax ~
A3 select the certain page, while A2~A0 for word mode, A2~A-1 for byte mode select the particular word or byte
in a page. The page access time is Taa or Tce, following by Tpa for the rest of the page read time. When CE#
toggles, access time is Taa or Tce. Page mode can be turned on by keeping "page-read address" constant and
changing the "intra-read page" addresses.
8-3. WRITE OPERATION
To perform a write operation, the system provides the desired address on the address pins, enables the chip by
asserting CE# LOW, and disables the Data (I/O) pins by holding OE# HIGH. The system then places data to be
written on the Data (I/O) pins and pulses WE# LOW. The device captures the address information on the falling
edge of WE# and the data on the rising edge of WE#. To see an example, please refer to the timing diagram in
"Figure 8. COMMAND WRITE OPERATION". The system is not allowed to write invalid commands (commands
not defined in this datasheet) to the device. Writing an invalid command may put the device in an undefined
state.
8-4. WRITE BUFFER PROGRAMMING OPERATION
Programs 64bytes/32words in a programming operation. To trigger the Write Buffer Programming, start by the
first two unlock cycles, then third cycle writes the Write Buffer Load command at the destined programming Sector Address. The forth cycle writes the "word locations subtract one" number.
Following above operations, system starts to write the mingling of address and data. After the programming of
the first address or data, the "write-buffer-page" is selected. The following data should be within the above mentioned page.
The "write-buffer-page" is selected by choosing address Amax-A5.
"Write-Buffer-Page" address has to be the same for all address/ data write into the write buffer. If not, operation
will ABORT.
To program the content of the write buffer page this command must be followed by a write to buffer Program confirm command.
The operation of write-buffer can be suspended or resumed by the standard commands, once the write buffer
programming operation is finished, it’ll return to normal READ mode.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
13
MX68GL1G0F
FUNCTIONAL OPERATION DESCRIPTION (cont'd)
WRITE BUFFER PROGRAMMING OPERATION (cont'd)
ABORT will be executed for the Write Buffer Programming Sequence if following condition occurs:
• The value loaded is bigger than the page buffer size during "Number of Locations to Program"
• Address written in a sector is not the same as the one assigned during the Write-Buffer-Load command.
• Address/ Data pair written to a different write-buffer-page than the one assigned by the "Starting Address"
during the "write buffer data loading" operation.
• Writing not "Confirm Command" after the assigned number of "data load" cycles.
At Write Buffer Abort mode, the status register will be Q1=1, Q7=DATA# (last address written), Q6=toggle.
A Write-to-Buffer-Abort Reset command sequence has to be written to reset the device for the next operation.
Write buffer programming can be conducted in any sequence. However the CFI functions, autoselect, Secured
Silicon sector are not functional when program operation is in progress. Multiple write buffer programming operations on the same write buffer address range without intervening erases is available. Any bit in a write buffer address range can’t be programmed from 0 back to 1.
8-5. DEVICE RESET
Driving the RESET# pin LOW for a period of Trp or more will return the device to Read mode. If the device is in
the middle of a program or erase operation, the reset operation will take at most a period of Tready1 before the
device returns to Read mode. Until the device does returns to Read mode, the RY/BY# pin will remain Low (Busy
Status).
When the RESET# pin is held at GND±0.3V, the device only consumes standby (Isbr) current. However, the device draws larger current if the RESET# pin is held at a voltage greater than GND+0.3V and less than or equal to
Vil.
It is recommended to tie the system reset signal to the RESET# pin of the flash memory. This allows the device
to be reset with the system and puts it in a state where the system can immediately begin reading boot code
from it.
8-6. STANDBY MODE
The device enters Standby mode whenever the RESET# and CE# pins are both held High except in the embedded mode. While in this mode, WE# and OE# will be ignored, all Data Output pins will be in a high impedance
state, and the device will draw minimal (Isb) current.
8-7. OUTPUT DISABLE
While in active mode (RESET# HIGH and CE# LOW), the OE# pin controls the state of the output pins. If OE# is
held HIGH, all Data (I/O) pins will remain tri-stated. If held LOW, the Byte or Word Data (I/O) pins will drive data.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
14
MX68GL1G0F
FUNCTIONAL OPERATION DESCRIPTION (cont'd)
8-8. BYTE/WORD SELECTION
The BYTE# input pin is used to select the organization of the array data and how the data is input/output on the
Data (I/O) pins. If the BYTE# pin is held HIGH, Word mode will be selected and all 16 data lines (Q0 to Q15) will
be active.
If BYTE# is forced LOW, Byte mode will be active and only data lines Q0 to Q7 will be active. Data lines Q8 to
Q14 will remain in a high impedance state and Q15 becomes the A-1 address input pin.
8-9. HARDWARE WRITE PROTECT
By driving the WP#/ACC pin LOW. The highest or lowest was protected from all erase/program operations. If
WP#/ACC is held HIGH (Vih to VCC), these sectors revert to their previously protected/unprotected status.
8-10.ACCELERATED PROGRAMMING OPERATION
By applying high voltage (Vhv) to the WP#/ACC pin, the device will enter the Accelerated Programming mode.
This mode permits the system to skip the normal command unlock sequences and program byte/word locations
directly. During accelerated programming, the current drawn from the WP#/ACC pin is no more than ICP1.
8-11.SECTOR PROTECT OPERATION
The device provides user programmable protection operations for selected sectors. Please refer to Table 1 which
show all Sector assignments.
During the protection operation, the sector address of any sector may be used to specify the Sector being protected.
8-12.AUTOMATIC SELECT BUS OPERATIONS
The following five bus operations require A9 to be raised to Vhv. Please see AUTOMATIC SELECT COMMAND
SEQUENCE in the COMMAND OPERATIONS section for details of equivalent command operations that do not
require the use of Vhv.
8-13.SECTOR LOCK STATUS VERIFICATION
To determine the protected state of any sector using bus operations, the system performs a READ OPERATION
with A9 raised to Vhv, the sector address applied to address pins A25 to A16, address pins A6, A3, A2 & A0 held
LOW, and address pin A1 held HIGH. If data bit Q0 is LOW, the sector is not protected, and if Q0 is HIGH, the
sector is protected.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
15
MX68GL1G0F
FUNCTIONAL OPERATION DESCRIPTION (cont'd)
8-14.READ SILICON ID MANUFACTURER CODE
To determine the Silicon ID Manufacturer Code, the system performs a READ OPERATION with A9 raised to
Vhv and address pins A6, A3, A2, A1, & A0 held LOW. The Macronix ID code of C2h should be present on data
bits Q7 to Q0.
8-15.READ INDICATOR BIT (Q7) FOR SECURITY SECTOR
To determine if the Security Sector has been locked at the factory, the system performs a READ OPERATION
with A9 raised to Vhv, address pin A6, A3 & A2 held LOW, and address pins A1 & A0 held HIGH. If the Security
Sector has been locked at the factory, the code 99h(H)/89h(L) will be present on data bits Q7 to Q0. Otherwise,
the factory unlocked code of 19h(H)/09h(L) will be present.
8-16.INHERENT DATA PROTECTION
To avoid accidental erasure or programming of the device, the device is automatically reset to Read mode during
power up. Additionally, the following design features protect the device from unintended data corruption.
8-17.COMMAND COMPLETION
Only after the successful completion of the specified command sets will the device begin its erase or program
operation. The failure in observing valid command sets will result in the memory returning to read mode.
8-18.LOW VCC WRITE INHIBIT
The device refuses to accept any write command when Vcc is less than VLKO. This prevents data from
spuriously being altered during power-up, power-down, or temporary power interruptions. The device
automatically resets itself when Vcc is lower than VLKO and write cycles are ignored until Vcc is greater than
VLKO. The system must provide proper signals on control pins after Vcc rises above VLKO to avoid unintentional
program or erase operations.
8-19.WRITE PULSE "GLITCH" PROTECTION
CE#, WE#, OE# pulses shorter than 5ns are treated as glitches and will not be regarded as an effective write
cycle.
8-20.LOGICAL INHIBIT
A valid write cycle requires both CE# and WE# at Vil with OE# at Vih. Write cycle is ignored when either CE# at
Vih, WE# at Vih, or OE# at Vil.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
16
MX68GL1G0F
FUNCTIONAL OPERATION DESCRIPTION (cont'd)
8-21.POWER-UP SEQUENCE
Upon power up, the device is placed in Read mode. Furthermore, program or erase operation will begin only
after successful completion of specified command sequences.
8-22.POWER-UP WRITE INHIBIT
When WE#, CE# is held at Vil and OE# is held at Vih during power up, the device ignores the first command on
the rising edge of WE#.
8-23.POWER SUPPLY DECOUPLING
A 0.1uF capacitor should be connected between the Vcc and GND to reduce the noise effect.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
17
MX68GL1G0F
9. COMMAND OPERATIONS
9-1. READING THE MEMORY ARRAY
Read mode is the default state after power up or after a reset operation. To perform a read operation, please refer to READ OPERATION in the BUS OPERATIONS section above at Table 2 and Table 3.
If the device receives an Erase Suspend command while in the Sector Erase state, the erase operation will
pause (after a time delay not exceeding 20us) and the device will enter Erase-Suspended Read mode. While in
the Erase-Suspended Read mode, data can be programmed or read from any sector not being erased. Reading
from addresses within sector (s) being erased will only return the contents of the status register, which is in fact
how the current status of the device can be determined.
If a program command is issued to any inactive (not currently being erased) sector during Erase-Suspended
Read mode, the device will perform the program operation and automatically return to Erase-Suspended Read
mode after the program operation completes successfully.
While in Erase-Suspended Read mode, an Erase Resume command must be issued by the system to reactivate
the erase operation. The erase operation will resume from where is was suspended and will continue until it
completes successfully or another Erase Suspend command is received.
After the memory device completes an embedded operation (automatic Chip Erase, Sector Erase, or Program)
successfully, it will automatically return to Read mode and data can be read from any address in the array. If the
embedded operation fails to complete, as indicated by status register bit Q5 (exceeds time limit flag) going HIGH
during the operations, the system must perform a reset operation to return the device to Read mode.
There are several states that require a reset operation to return to Read mode:
1. A program or erase failure--indicated by status register bit Q5 going HIGH during the operation. Failures during either of these states will prevent the device from automatically returning to Read mode.
2. The device is in Auto Select mode or CFI mode. These two states remain active until they are terminated by a
reset operation.
In the two situations above, if a reset operation (either hardware reset or software reset command) is not performed, the device will not return to Read mode and the system will not be able to read array data.
9-2. AUTOMATIC PROGRAMMING OF THE MEMORY ARRAY
The device provides the user the ability to program the memory array in Byte mode or Word mode. As long as
the users enters the correct cycle defined in the Table 5 (including 2 unlock cycles and the A0H program command), any byte or word data provided on the data lines by the system will automatically be programmed into the
array at the specified location.
After the program command sequence has been executed, the internal write state machine (WSM) automatically
executes the algorithms and timings necessary for programming and verification, which includes generating suitable program pulses, checking cell threshold voltage margins, and repeating the program pulse if any cells do
not pass verification or have low margins. The internal controller protects cells that do pass verification and margin tests from being over-programmed by inhibiting further program pulses to these passing cells as weaker cells
continue to be programmed.
With the internal WSM automatically controlling the programming process, the user only needs to enter the program command and data once.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
18
MX68GL1G0F
COMMAND OPERATIONS (cont'd)
AUTOMATIC PROGRAMMING OF THE MEMORY ARRAY (cont'd)
Programming will only change the bit status from "1" to "0". It is not possible to change the bit status from "0" to
"1" by programming. This can only be done by an erase operation. Furthermore, the internal write verification
only checks and detects errors in cases where a "1" is not successfully programmed to "0".
Any commands written to the device during programming will be ignored except hardware reset or program suspend. Hardware reset will terminate the program operation after a period of time no more than 10us. When the
embedded program algorithm is complete or the program operation is terminated by a hardware reset, the device will return to Read mode. Program suspend ready, the device will enter program suspend read mode.
After the embedded program operation has begun, the user can check for completion by reading the following
bits in the status register:
Status
In progress
Exceed time limit
Q7*1
Q7#
Q7#
Q6*1
Toggling
Toggling
Q5
0
1
Q1
0
N/A
RY/BY# (Note)
0
0
Note: RY/BY# is an open drain output pin and should be connected to VCC through a high value pull-up resistor.
9-3. ERASING THE MEMORY ARRAY
There are two types of erase operations performed on the memory array -- Sector Erase and Chip Erase. In
the Sector Erase operation, one or more selected sectors may be erased simultaneously. In the Chip Erase
operation, the complete memory array is erased except for any protected sectors. More details of the protected
sectors are explained in section 5.
9-4. SECTOR ERASE
The sector erase operation is used to clear data within a sector by returning all of its memory locations to the
"1" state. It requires six command cycles to initiate the erase operation. The first two cycles are "unlock cycles",
the third is a configuration cycle, the fourth and fifth are also "unlock cycles", and the sixth cycle is the Sector
Erase command. After the sector erase command sequence has been issued, an internal 50us time-out counter
is started. Until this counter reaches zero, additional sector addresses and Sector Erase commands may be
issued thus allowing multiple sectors to be selected and erased simultaneously. After the 50us time-out counter
has expired, no new commands will be accepted and the embedded sector erase operation will begin. Note that
the 50us timer-out counter is restarted after every erase command sequence. If the user enters any command
other than Sector Erase or Erase Suspend during the time-out period, the erase operation will abort and the
device will return to Read mode.
After the embedded sector erase operation begins, all commands except Erase Suspend will be ignored. The
only way to interrupt the operation is with an Erase Suspend command or with a hardware reset. The hardware
reset will completely abort the operation and return the device to Read mode.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
19
MX68GL1G0F
COMMAND OPERATIONS (cont'd)
SECTOR ERASE (cont'd)
The system can determine the status of the embedded sector erase operation by the following methods:
Status
Time-out period
In progress
Exceeded time limit
Q7
0
0
0
Q6
Toggling
Toggling
Toggling
Q3*1
0
1
1
Q5
0
0
1
Q2
Toggling
Toggling
Toggling
RY/BY#*2
0
0
0
Note:
1.The Q3 status bit is the 50us time-out indicator. When Q3=0, the 50us time-out counter has not yet reached
zero and a new Sector Erase command may be issued to specify the address of another sector to be erased.
When Q3=1, the 50us time-out counter has expired and the Sector Erase operation has already begun. Erase
Suspend is the only valid command that may be issued once the embedded erase operation is underway.
2.RY/BY# is open drain output pin and should be connected to VCC through a high value pull-up resistor.
3.When an attempt is made to erase only protected sector (s), the erase operation will abort thus preventing any
data changes in the protected sector (s). Q7 will output "0" and Q6 will toggle briefly (100us or less) before
aborting and returning the device to Read mode. If unprotected sectors are also specified, however, they will
be erased normally and the protected sector (s) will remain unchanged.
4. Q2 is a localized indicator showing a specified sector is undergoing erase operation or not. Q2 toggles when
user reads at addresses where the sectors are actively being erased (in erase mode) or to be erased (in erase
suspend mode).
9-5. CHIP ERASE
The Chip Erase operation is used erase all the data within the memory array. All memory cells containing a "0"
will be returned to the erased state of "1". This operation requires 6 write cycles to initiate the action. The first
two cycles are "unlock" cycles, the third is a configuration cycle, the fourth and fifth are also "unlock" cycles, and
the sixth cycle initiates the chip erase operation.
During the chip erase operation, no other software commands will be accepted, but if a hardware reset is received or the working voltage is too low, that chip erase will be terminated. After Chip Erase, the chip will automatically return to Read mode.
The system can determine the status of the embedded chip erase operation by the following methods:
Status
In progress
Exceed time limit
Q7
0
0
Q6
Toggling
Toggling
Q5
0
1
Q2
Toggling
Toggling
RY/BY#*1
0
0
*1: RY/BY# is open drain output pin and should be connected to VCC through a high value pull-up resistor.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
20
MX68GL1G0F
COMMAND OPERATIONS (cont'd)
9-6. ERASE SUSPEND/RESUME
After beginning a sector erase operation, Erase Suspend is the only valid command that may be issued. If system issues an Erase Suspend command during the 50us time-out period following a Sector Erase command, the
time-out period will terminate immediately and the device will enter Erase-Suspended Read mode. If the system
issues an Erase Suspend command after the sector erase operation has already begun, the device will not enter
Erase-Suspended Read mode until 20us time has elapsed. The system can determine if the device has entered
the Erase-Suspended Read mode through Q6, Q7, and RY/BY#.
After the device has entered Erase-Suspended Read mode, the system can read or program any sector (s) except those being erased by the suspended erase operation. Reading any sector being erased or programmed
will return the contents of the status register. Whenever a suspend command is issued, user must issue a resume command and check Q6 toggle bit status, before issue another erase command. The system can use the
status register bits shown in the following table to determine the current state of the device:
Status
Erase suspend read in erase suspended sector
Erase suspend read in non-erase suspended sector
Q7
Q6
Q5
Q3
Q2
Q1
RY/BY#
1
No toggle
0
N/A
toggle
N/A
1
Data
Data
1
N/A
N/A
0
Data
Erase suspend program in non-erase suspended sector Q7#
Data
Toggle
Data Data
0
N/A
When the device has suspended erasing, user can execute the command sets, such as read silicon ID, sector
protect verify, program, CFI query and erase resume.
After the device has entered Erase-Suspended Read Mode, Sector Erase, Chip Erase and Program Suspend
commands are forbidden.
9-7. SECTOR ERASE RESUME
The sector Erase Resume command is valid only when the device is in Erase-Suspended Read mode. After
erase resumes, the user can issue another Ease Suspend command, but there should be a 400us interval between Ease Resume and the next Erase Suspend command.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
21
MX68GL1G0F
COMMAND OPERATIONS (cont'd)
9-8. PROGRAM SUSPEND/RESUME
After beginning a program operation, Program Suspend is the only valid command that may be issued. The system can determine if the device has entered the Program-Suspended Read mode through Q6 and RY/BY#.
After the device has entered Program-Suspended mode, the system can read any sector (s) except those being programmed by the suspended program operation. Reading the sector being program suspended is invalid.
Whenever a suspend command is issued, user must issue a resume command and check Q6 toggle bit status,
before issue another program command. The system can use the status register bits shown in the following table
to determine the current state of the device:
Status
Q7
Q6
Q5
Program suspend read in program suspended sector
Q3
Q2
Q1
Invalid
Program suspend read in non-program suspended
Data
sector
Data
Data
RY/BY#
1
Data
Data
Data
1
When the device has Program suspended, user can execute read array, auto-select, read CFI, read security silicon. Program and Erase Suspend commands are forbidden after the device entered Program-Suspend mode.
9-9. PROGRAM RESUME
The Program Resume command is valid only when the device is in Program-Suspended mode. After program
resumes, the user can issue another Program Suspend command, but there should be a 5us interval between
Program Resume and the next Program Suspend command.
9-10.BUFFER WRITE ABORT
Q1 is the indicator of Buffer Write Abort. When Q1=1, the device will abort from buffer write and go back to read
status register shown as following table:
Status
Q7
Q6
Q5
Q3
Q2
Q1
RY/BY#
Buffer Write Busy
Q7#
Toggle
0
N/A
N/A
0
0
Buffer Write Abort
Q7#
Toggle
0
N/A
N/A
1
0
Buffer Write Exceeded Time Limit
Q7#
Toggle
1
N/A
N/A
0
0
P/N:PM1727
REV. 1.3, OCT. 30, 2013
22
MX68GL1G0F
COMMAND OPERATIONS (cont'd)
9-11.AUTOMATIC SELECT OPERATIONS
When the device is in Read mode, Program Suspended mode, Erase-Suspended Read mode, or CFI mode, the
user can issue the Automatic Select command shown in Table 5 (two unlock cycles followed by the Automatic
Select command 90h) to enter Automatic Select mode. After entering Automatic Select mode, the user can query
the Manufacturer ID, Device ID, Security Sector locked status, or Sector protected status multiple times without
issuing a new Automatic Select command.
While In Automatic Select mode, issuing a Reset command (F0h) will return the device to Read mode (or EaseSuspended Read mode if Erase-Suspend was active) or Program Suspended Read mode if Program Suspend
was active.
Another way to enter Automatic Select mode is to use one of the bus operations shown in Table 2 BUS OPERATION. After the high voltage (Vhv) is removed from the A9 pin, the device will automatically return to Read mode
or Erase-Suspended Read mode.
9-12.AUTOMATIC SELECT COMMAND SEQUENCE
Automatic Select mode is used to access the manufacturer ID, device ID and to verify whether or not secured
silicon is locked and whether or not a sector is protected. The automatic select mode has four command cycles.
The first two are unlock cycles, and followed by a specific command. The fourth cycle is a normal read cycle,
and user can read at any address any number of times without entering another command sequence. The Reset
command is necessary to exit the Automatic Select mode and back to read array.
After entering automatic select mode, no other commands are allowed except the reset command.
9-13.READ MANUFACTURER ID OR DEVICE ID
The Manufacturer ID (identification) is a unique hexadecimal number assigned to each manufacturer by the JEDEC committee. Each company has its own manufacturer ID, which is different from the ID of all other companies. The number assigned to Macronix is C2h.
After entering Automatic Select mode, performing a read operation with A1 & A0 held LOW will cause the device
to output the Manufacturer ID on the Data I/O (Q7 to Q0) pins.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
23
MX68GL1G0F
COMMAND OPERATIONS (cont'd)
9-14.RESET
In the following situations, executing reset command will reset device back to Read mode:
•
•
•
•
Among erase command sequence (before the full command set is completed)
Sector erase time-out period
Erase fail (while Q5 is high)
Among program command sequence (before the full command set is completed, erase-suspended program
included)
• Program fail (while Q5 is high, and erase-suspended program fail is included)
• Auto-select mode
• CFI mode
While device is at the status of program fail or erase fail (Q5 is high), user must issue reset command to reset
device back to read array mode. While the device is in Auto-Select mode or CFI mode, user must issue reset
command to reset device back to read array mode.
When the device is in the progress of programming (not program fail) or erasing (not erase fail), device will ignore reset command.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
24
MX68GL1G0F
9-15.Advanced Sector Protection/Un-protection
There are two ways to implement software Advanced Sector Protection on this device: Password method or
Solid methods. Through these two protection methods, user can disable or enable the programming or erasing
operation to any individual sector or the whole chip. The figure below helps to describe an overview of these
methods.
The device is default to the Solid mode. All sectors are default as unprotected when shipped from factory.
The detailed algorithm of advance sector protection is shown as follows:
Figure 1. Advance Sector Protection/Unprotection SPB Program Algorithm
Start
To choose
protection mode
set lock register bit
(Q1/Q2)
Q1=0
Solid Protection Mode
Q2=0
Password Protection Mode
Set 64 bit Password
Set
SPB Lock Bit
SPBLK = 0
SPB Lock bit locked
All SPBs can not changeable
SPBLK = 1
SPB Lock bit Unlocked
All SPBs are changeable
Dynamic write Protect bit
(DPB)
DPB=0 sector protect
Sector Array
DPB=1 sector unprotect
Solid write Protect bit (SPB)
Temporary Unprotect
SPB bit (USPB)
SPB=0 sector protect
USPB=0 SPB bit is disabled
SPB=1 sector unprotect
USPB=1 SPB bit is enabled
DPB 0
SA 0
SPB 0
USPB 0
DPB 1
SA 1
SPB 1
USPB 1
DPB 2
SA 2
SPB 2
USPB 2
:
:
:
:
:
:
:
:
DPB N-1
SA N-1
SPB N-1
USPB N-1
DPB N
SA N
SPB N
USPB N
P/N:PM1727
REV. 1.3, OCT. 30, 2013
25
MX68GL1G0F
9-15-1. Lock Register
User can choose the sector protecting method via setting Lock Register bits as Q1 and Q2. Lock Register is a
16-bit one-time programmable register. Once programming either Q1 or Q2, they will be locked in that mode and
the others will be disabled permanently. Q1 and Q2 can not be programmed at the same time, otherwise the
device will abort the operation.
If users select Password Protection mode, the password setting is required. Users can set password by issuing
password program command.
Lock Register bits
Q15-Q3
Q2
Q1
Q0
Password Protection Mode
Solid Protection Mode
Secured Silicon Sector
Don't care
Lock Bit
Lock Bit
Protection Bit
Please refer to the command for Lock Register command set about how to read and program the Lock Register
bits.
Figure 2. Lock Register Program Algorithm
START
Write Data AAH, Address 555H
Lock register command set Entry
Write Data 55H, Address 2AAH
Write Data 40H, Address 555H
Write Data A0H,
Address don’t care
Lock register data program
Write Program Data,
Address don’t care
Data # Polling Algorithm
Done
YES
NO
NO
Pass
Q5 = 1
YES
Exit Lock Register
command
Fail
Reset command
P/N:PM1727
REV. 1.3, OCT. 30, 2013
26
MX68GL1G0F
9-15-2. Solid Protection Mode
Solid write Protection Bits (SPB)
The Solid write Protection bits (SPB) are nonvolatile bit with the same endurances as the Flash memory. Each
SPB is assigned to each sector individually. The SPB is preprogrammed, and verified prior to erasure are
managed by the device, so system monitoring is not necessary.
When SPB is set to “0”, the associated sector may be protected, preventing any program or erase operation on
this sector. Whether the sector is protected depends also upon the value of the USPB, as described elsewhere.
The SPB bits are set individually by SPB program command. However, it cannot be cleared individually. Issuing
the All SPB Erase command will erase all SPB in the same time. During SPB programming period, the read and
write operations are disabled for normal sector until exiting this mode.
To unprotect a protected sector, the SPB lock bit must be cleared first by using a hardware reset or a power-up
cycle. After the SPB lock bit is cleared, the SPB status can be changed to the desired settings. To lock the Solid
Protection Bits after the modification has finished, the SPB Lock Bit must be set once again.
To verify the state of the SPB for a given sector, issuing a SPB Status Read Command to the device is required.
Refer to the flow chart for details in Figure 3.
Dynamic write Protection Bits (DPB)
The Dynamic Protection features a volatile type protection to each individual sector. It can protect sectors from
being unintentionally changed, and is easy to disable.
All Dynamic write Protection bit (DPB) can be modified individually. DPBs protect the unprotected sectors with
their SPBs cleared. To modify the DPB status by issuing the DPB Set (programmed to “0”) or DPB Clear (erased
to “1”) commands, and place each sector in the protected or unprotected state seperately. After the DPB Clear
command is issued (erased to “1”), the sector may be modified depending on the SPB state of that sector.
The DPBs are default to be erased to “1” when first shipped from factory.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
27
MX68GL1G0F
9-15-3. Temporary Un-protect Solid write Protect Bits (USPB)
Temporary Un-protect Solid write Protect Bits are volatile. They are unique for each sector and can be
individually modified. Software can temporarily unprotect write protect sectors despite of SPB's property when
DPBs are cleared. While the USPB is set (to “0”), the corresponding sector's SPB property is masked.
Notes:
1. Upon power up, the USPBs are cleared (all “1”). The USPBs can be set (to “0”) or cleared (to “1”) as often as
needed. The hardware reset will reset USPB/DPB to their default values.
2. To change the protected sector status of solid write protect bit, users don't need to clear all SPBs. The users
can just implement software to set corresponding USPB to "0", in which the corresponding DPB status is
cleared too. Consequently, the original solid write protect status of protected sectors can be temporarily
changed.
Figure 3. SPB Program Algorithm
SPB command
set entry
Program SPB
Read Q7~Q0
Twice
NO
Q6 Toggle ?
YES
Q5 = 1 ?
NO
Wait 500 µs
YES
Read Q7~Q0
Twice
Read Q7~Q0
Twice
NO
Q6 Toggle ?
YES
Q0=
'1' (Erase)
'0' (Program)
NO
YES
Program Fail
Write Reset CMD
Pass
SPB command
set Exit
Note: SPB program/erase status polling flowchart: check Q6 toggle, when Q6 stop toggle, the read status is 00H
/01H (00H for program/ 01H for erase), otherwise, the status is “fail” and “exit”.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
28
MX68GL1G0F
9-15-4. Solid Protection Bit Lock Bit
The Solid Protection Bit Lock Bit (SPBLK) is assigned to control all SPB status. It is an unique and volatile. When
SPBLK=0 (set), all SPBs are locked and can not be changed. When SPBLK=1 (cleared), all SPBs are allowed to
be changed.
There is no software command sequence requested to unlock this bit, unless the device is in the password
protection mode. To clear the SPB Lock Bit, just execute a hardware reset or a power-up cycle. In order to
prevent modification, the SPB Lock Bit must be set (SPBLK=0) after all SPBs are set to desired status.
9-15-5. Password Protection Method
The security level of Password Protection Method is higher than the Solid protection mode. The 64 bit password
is requested before modifying SPB lock bit status. When device is under password protection mode, the SPB
lock bit is set as “0”, after a power-up cycle or Reset Command.
A correct password is required for password Unlock command to unlock the SPB lock bit. Await 2us is necessary
to unlock the device after a valid password is given. After that, the SPB bits are allowed to be changed. The
Password Unlock command is issued slower than 2 μs every time, to prevent hacker from trying all the 64-bit
password combinations.
There are a few steps to start password protection mode:
(1).Set a 64-bit password for verification before entering the password protection mode. This verification is only
allowed in password programming.
(2).Set the Password Protection Mode Lock Bit to”0” to activate the password protection mode.
Once the password protection mode lock bit is programmed, the programmed Q2 bit can not be erased any more
and the device will remain permanently in password protection mode. The previous set 64-bit password can not
be retrieved or programmed. All the commands to the password-protected address will also be disabled.
All the combinations of the 64-bit password can be used as a password, and programming the password does
not require special address. The password is defaulted to be all “1” when shipped from the factory. Under
password program command, only "0" can be programmed. In order to prevent access, the Password Mode
Locking Bit must be set after the Password is programmed and verified. To set the Password Mode Lock Bit will
prevent this 64-bits password to be read on the data bus. Any modification is impossible then, and the password
can not be checked anymore after the Password Mode Lock Bit is set.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
29
MX68GL1G0F
Table 4. Sector Protection Status
DPB
clear
clear
clear
clear
set
set
set
set
Protection Bit Status
SPB
clear
clear
set
set
clear
clear
set
set
USPB
clear
set
clear
set
clear
set
clear
set
Sector Status
Unprotect
Unprotect
Protect
Unprotect
Protect
Protect
Protect
Protect
Notes: If SPBLK is set, SPB will be unchangeable.
If SPBLK is cleared, SPB will be changeable.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
30
MX68GL1G0F
9-16.SECURITY SECTOR FLASH MEMORY REGION
The Security Sector region is an extra OTP memory space of 128 words in length. The security sector can be
locked upon shipping from factory, or it can be locked by customer after shipping. Customer can issue Security
Sector Factory Protect Verify and/or Security Sector Protect Verify to query the lock status of the device. After
enter Security Sector region, it is forbidden to enter Lock Register, DPB, SPB, SPB lock region.
In factory-locked device, security sector region is protected when shipped from factory and the security silicon
sector indicator bit is set to "1". In customer lockable device, security sector region is unprotected when shipped
from factory and the security silicon indicator bit is set to "0".
9-17.FACTORY LOCKED: SECURITY SECTOR PROGRAMMED AND PROTECTED AT THE FACTORY
In a factory locked device, the Security Sector is permanently locked before shipping from the factory. The device will have a 16-byte (8-word) ESN in the security region. The ESN occupies addresses 00000h to 0000Fh in
byte mode or 00000h to 00007h in word mode.
Secured Silicon Sector
Address Range
Standard Factory Locked
0000000h-0000007h
ESN
0000008h-000007Fh
Unavailable
Express Flash
Factory Locked
ESN or Determined by
Customer
Determined by Customer
Customer Lockable
Determined by Customer
9-18.CUSTOMER LOCKABLE: SECURITY SECTOR NOT PROGRAMMED OR PROTECTED AT THE
FACTORY
When the security feature is not required, the security region can act as an extra memory space.
Security silicon sector can also be protected by two methods. Note that once the security silicon sector is protected, there is no way to unprotect the security silicon sector and the content of it can no longer be altered.
After the security silicon is locked and verified, system must write Exit Security Sector Region, go through a power cycle, or issue a hardware reset to return the device to read normal array mode.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
31
MX68GL1G0F
Table 5. COMMAND DEFINITIONS
Command
1st Bus
Cycle
2nd Bus
Cycle
3rd Bus
Cycle
4th Bus
Cycle
5th Bus
Cycle
6th Bus
Cycle
Read Reset
Mode Mode
Addr Addr
Data Data
Addr
Data
Addr
Data
Addr
Data
Addr
Data
Addr
Data
XXX
F0
Automatic Select
Factory Protect Sector Protect Verify
Silicon ID
Device ID
Verify
Word Byte Word Byte
Word
Byte
Word
Byte
555 AAA 555 AAA
555
AAA
555
AAA
AA
AA
AA
AA
AA
AA
AA
AA
2AA 555 2AA 555
2AA
555
2AA
555
55
55
55
55
55
55
55
55
555 AAA 555 AAA
555
AAA
555
AAA
90
90
90
90
90
90
90
90
(Sector) (Sector)
X00 X00 X01 X02
X03
X06
X02
X04
99/19(H)
C2h C2h ID1 ID1
00/01
00/01
89/09(L)
X0E X1C
ID2 ID2
X0F X1E
ID3 ID3
Security
Sector
Region
Word Byte
555 AAA
AA
AA
2AA 555
55
55
555 AAA
88
88
Exit Security
Sector
Word
555
AA
2AA
55
555
90
Byte
AAA
AA
555
55
AAA
90
XXX XXX
00
00
Write to
Write to
Program/ Program/
Buffer
Buffer
Sector
Program
Chip Erase
CFI Read
Erase
Erase
Program
Program
Erase
Suspend Resume
Abort Reset confirm
Word Byte Word Byte Word Byte Word Byte Word Byte Word Byte Word Byte Word Byte Word Byte
Write to
Buffer
Program
Command
1st Bus
Cycle
2nd Bus
Cycle
3rd Bus
Cycle
4th Bus
Cycle
5th Bus
Cycle
Addr
Data
Addr
Data
Addr
Data
Addr
Data
Addr
Data
555
AA
2AA
55
555
A0
Addr
Data
AAA 555 AAA 555 AAA
AA AA AA AA AA
555 2AA 555 2AA 555
55
55
55
55
55
AAA SA SA 555 AAA
A0
25
25
F0
F0
Addr SA SA
Data N-1 N-1
WA WA
WD WD
6th Bus
Cycle
Addr
WBL WBL
Data
WD WD
SA
29
SA
29
555
AA
2AA
55
555
80
555
AA
2AA
55
AAA
AA
555
55
AAA
80
AAA
AA
555
55
555
AA
2AA
55
555
80
555
AA
2AA
55
Sec555 AAA
tor
10
10 30
AAA
AA
555
55
AAA
80
AAA
AA
555
55
Sector
30
55
98
AA
98
xxx
B0
xxx
B0
xxx
30
xxx
30
WA= Write Address
WD= Write Data
SA= Sector Address
N-1= Word Count
WBL= Write Buffer Location
PWD= Password
PWDn=Password word 0, word 1, word n
ID1/ID2/ID3: Refer to Table 3 for detail ID.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
32
MX68GL1G0F
Deep Power Down
Command
4th Bus
Cycle
Addr
Data
Addr
Data
Addr
Data
Addr
Data
5th Bus
Cycle
6th Bus
Cycle
7th Bus
Cycle
8th Bus
Cycle
9th Bus
Cycle
10th Bus
Cycle
11th Bus
Cycle
Addr
Data
Addr
Data
Addr
Data
Addr
Data
Addr
Data
Addr
Data
Addr
Data
1st Bus
Cycle
2nd Bus
Cycle
3rd Bus
Cycle
Enter
Word
555
AA
2AA
55
XXX
B9
Byte
AAA
AA
555
55
XXX
B9
Password Protection
Password
Command Set
Entry
Byte Word Byte
XXX
555
AAA
AB
AA
AA
2AA
555
55
55
555
AAA
60
60
Exit
Word
XXX
AB
Password
Program
Word
XXX
A0
PWA
PWD
Byte
XXX
A0
PWA
PWD
Password
Command Set
Exit
Word Byte Word Byte Word Byte
X00
X00
00
00
XXX XXX
PWD0 PWD0 25
25
90
90
X01
X01
00
00
XXX XXX
PWD1 PWD1 03
03
00
00
X02
X02
X00
X00
PWD2 PWD2 PWD0 PWD0
X03
X03
X01
X01
PWD3 PWD3 PWD1 PWD1
Password
Read
Password
Unlock
X04
X02
X02
PWD4 PWD2 PWD2
X05
X03
X03
PWD5 PWD3 PWD3
X06
00
X04
PWD6 29 PWD4
X07
X05
PWD7
PWD5
X06
PWD6
X07
PWD7
00
29
P/N:PM1727
REV. 1.3, OCT. 30, 2013
33
MX68GL1G0F
Lock Register
Command
4th Bus
Cycle
Addr
Data
Addr
Data
Addr
Data
Addr
Data
5th Bus
Cycle
Addr
Data
1st Bus
Cycle
2nd Bus
Cycle
3rd Bus
Cycle
Command
4th Bus
Cycle
Addr
Data
Addr
Data
Addr
Data
Addr
Data
5th Bus
Cycle
Addr
Data
1st Bus
Cycle
2nd Bus
Cycle
3rd Bus
Cycle
Lock register
Command
Set Entry
Word Byte
555 AAA
AA
AA
2AA 555
55
55
555 AAA
40
40
Global Non-Volatile
Lock register
Command
Set Exit
Word Byte Word Byte Word Byte
XXX XXX XXX XXX XXX XXX
A0
A0 DATA DATA 90
90
XXX XXX
XXX XXX
Data Data
00
00
Program
Read
SPB
SPB
All SPB
SPB Status
Command
Program
Erase
Read
Set Entry
Word Byte Word Byte Word Byte Word Byte
555 AAA XXX XXX XXX XXX SA
SA
AA
AA
A0
A0
80
80 00/01 00/01
2AA 555 SA SA
00
00
55
55
00
00
30
30
555 AAA
C0
C0
Global NonGlobal Volatile Freeze
Volatile
Volatile
SPB
SPB Lock
SPB Lock
DPB
SPB Lock SPB Lock
Command
Command
Command Command DPB Set DPB Clear
Set
Status Read
Set Exit
Set Entry
Set Exit
Set Entry
Word Byte Word Byte Word Byte Word Byte Word Byte Word Byte Word Byte Word Byte
XXX XXX 555 AAA XXX XXX XXX XXX XXX XXX 555 AAA XXX XXX XXX XXX
90
90
AA
AA
A0
A0 00/01 00/01 90
90
AA
AA
A0
A0 A0
A0
XXX XXX 2AA 555 XXX XXX
XXX XXX 2AA 555 SA SA SA SA
00
00
55
55
00
00
00
00
55
55
00
00
01
01
555 AAA
555 AAA
50
50
E0
E0
Volatile
Command
Addr
Data
2nd Bus Addr
Cycle Data
3rd Bus Addr
Cycle Data
4th Bus Addr
Cycle Data
1st Bus
Cycle
5th Bus
Cycle
DPB Status DPB Command
Read
Set Exit
Word
Byte
Word Byte
SA
SA
XXX
XXX
00/01 00/01
90
90
XXX
XXX
00
00
Addr
Data
Notes:
* It is not recommended to adopt any other code not in the command definition table which will potentially enter
the hidden mode.
* For the SPB Lock and DPB Status Read "00" means lock (protect), "01" means unlock (unprotect).
P/N:PM1727
REV. 1.3, OCT. 30, 2013
34
MX68GL1G0F
10. COMMON FLASH MEMORY INTERFACE (CFI) MODE
QUERY COMMAND AND COMMAND FLASH MEMORY INTERFACE (CFI) MODE
The device features CFI mode. Host system can retrieve the operating characteristics, structure and vendorspecified information such as identifying information, memory size, byte/word configuration, operating voltages
and timing information of this device by CFI mode. If the system writes the CFI Query command "98h", to address "55h"/"AAh" (depending on Word/Byte mode), the device will enter the CFI Query Mode, any time the device is ready to read array data. The system can read CFI information at the addresses given in Table 6 ~ Table 9.
Once user enters CFI query mode, user can issue reset command to exit CFI mode and return to read array
mode. The CFI unused area is reserved by Macronix.
Table 6. CFI mode: Identification Data Values
(All values in these tables are in hexadecimal)
(Note 1)
Address (h)
Address (h)
(Word Mode) (Byte Mode)
10
20
Query-unique ASCII string "QRY"
11
22
12
24
13
26
Primary vendor command set and control interface ID code
14
28
15
2A
Address for primary algorithm extended query table
16
2C
17
2E
Alternate vendor command set and control interface ID code
18
30
19
32
Address for alternate algorithm extended query table
1A
34
Note 1. Query data are always presented on the lowest data output Q7~Q0 only, Q8~Q15 are "0".
Description
Data (h)
0051
0052
0059
0002
0000
0040
0000
0000
0000
0000
0000
Table 7. CFI mode: System Interface Data Values
Description
Vcc supply minimum program/erase voltage
Vcc supply maximum program/erase voltage
VPP supply minimum program/erase voltage
VPP supply maximum program/erase voltage
Typical timeout per single word/byte write, 2n us
Typical timeout for maximum-size buffer write, 2n us (00h, not
support)
Typical timeout per individual block erase, 2n ms
Typical timeout for full chip erase, 2n ms (00h, not support)
Maximum timeout for word/byte write, 2n times typical
Maximum timeout for buffer write, 2n times typical
Maximum timeout per individual block erase, 2n times typical
Maximum timeout for chip erase, 2n times typical (00h, not
support)
P/N:PM1727
Address (h)
(Word Mode)
1B
1C
1D
1E
1F
Address (h)
(Byte Mode)
36
38
3A
3C
3E
20
40
0006
21
22
23
24
25
42
44
46
48
4A
0009
0018
0003
0005
0003
26
4C
0002
Data (h)
0027
0036
0000
0000
0003
REV. 1.3, OCT. 30, 2013
35
MX68GL1G0F
Table 8. CFI mode: Device Geometry Data Values
Address (h)
(Word Mode)
27
Device size = 2n in number of bytes (1B=1Gb)
28
Flash device interface description (02=asynchronous x8/x16)
29
2A
Maximum number of bytes in buffer write = 2n (00h, not support)
2B
2C
Number of erase regions within device (01h:uniform, 02h:boot)
2D
Index for Erase Bank Area 1:
2E
[2E,2D] = # of same-size sectors in region 1-1
2F
[30, 2F] = sector size in multiples of 256 bytes
30
31
32
Index for Erase Bank Area 2
33
34
35
36
Index for Erase Bank Area 3
37
38
39
3A
Index for Erase Bank Area 4
3B
3C
Description
P/N:PM1727
Address (h)
(Byte Mode)
4E
50
52
54
56
58
5A
5C
5E
60
62
64
66
68
6A
6C
6E
70
72
74
76
78
Data (h)
001B
0002
0000
0006
0000
0001
00FF
0003
0000
0002
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
REV. 1.3, OCT. 30, 2013
36
MX68GL1G0F
Table 9. CFI mode: Primary Vendor-Specific Extended Query Data Values
Address (h)
(Word Mode)
40
41
42
43
44
45
46
47
48
49
4A
4B
Address (h)
(Byte Mode)
80
82
84
86
88
8A
8C
8E
90
92
94
96
4C
98
0002
4D
9A
0095
4E
9C
00A5
WP# Protection
04=Uniform sectors bottom WP# protect
05=Uniform sectors top WP# protect
4F
9E
0004/
0005
Program Suspend (0=not supported, 1=supported)
50
A0
0001
Description
Query - Primary extended table, unique ASCII string, PRI
Major version number, ASCII
Minor version number, ASCII
Unlock recognizes address (0= recognize, 1= don't recognize)
Erase suspend (2= to both read and program)
Sector protect (N= # of sectors/group)
Temporary sector unprotect (1=supported)
Sector protect/Chip unprotect scheme
Simultaneous R/W operation (0=not supported)
Burst mode (0=not supported)
Page mode (0=not supported, 01 = 4 word page, 02 = 8 word
page)
Minimum ACC(acceleration) supply (0= not supported), [D7:D4]
for volt, [D3:D0] for 100mV
Maximum ACC(acceleration) supply (0= not supported), [D7:D4]
for volt, [D3:D0] for 100mV
P/N:PM1727
Data (h)
0050
0052
0049
0031
0033
0014
0002
0001
0000
0008
0000
0000
REV. 1.3, OCT. 30, 2013
37
MX68GL1G0F
11. ELECTRICAL CHARACTERISTICS
11-1.ABSOLUTE MAXIMUM STRESS RATINGS
Storage Temperature
-65°C to +150°C
Voltage Range
VCC
-0.5V to +4.0V
VI/O
-0.5V to +4.0V
A9 , WP#/ACC
-0.5V to +10.5V
The other pins.
-0.5V to Vcc +0.5V
Output Short Circuit Current (less than one second)
200 mA
11-2.OPERATING TEMPERATURE AND VOLTAGE
Industrial (I) Grade
Surrounding Temperature (TA )
VCC Supply Voltages
-40°C to +85°C
Full VCC range
+2.7V to 3.6V
Regulated VCC range
+3.0V to 3.6V
VI/O range
+1.65V to 3.6V
NOTICE:
1.Stresses greater than those listed under ABSOLUTE MAXIMUM RATINGS may cause permanent damage
to the device. This is stress rating only and functional operational sections of this specification is not implied.
Exposure to absolute maximum rating conditions for extended period may affect reliability.
2.Specifications contained within the following tables are subject to change.
3.During voltage transitions, all pins may overshoot GND to -2.0V and Vcc to +2.0V for periods up to 20ns, see
below Figure.
Figure 5. Maximum Positive Overshoot Waveform
Figure 4. Maximum Negative Overshoot Waveform
20ns
20ns
20ns
GND
Vcc + 2.0V
GND - 2.0V
Vcc
20ns
20ns
P/N:PM1727
20ns
REV. 1.3, OCT. 30, 2013
38
MX68GL1G0F
Table 10. DC CHARACTERISTICS
Symbol Description
Min.
Typ.
Max.
Iilk
Input Leak
±8.0uA
Iilk9
A9 Leak
140uA
Iolk
Output Leak
±1.0uA
Icr1
Icr2
Read Current
Remark
A9=10.5V
CE#=Vil, OE#=Vih,
Vcc=Vccmax;
f=1MHz,
CE#=Vil, OE#=Vih,
Vcc=Vccmax;
f=5MHz,
CE#=Vil, OE#=Vih,
Vcc=Vccmax;
f=10MHz
5mA
15mA
10mA
20mA
15mA
30mA
4mA
10mA
CE#=Vil, OE#=Vih,
Vcc=Vccmax;
f=10MHz
8mA
20mA
CE#=Vil, OE#=Vih,
Vcc=Vccmax;
f=33MHz
VCC Page Read Current
Iio
VIO non-active current
0.2mA
10mA
Icw
Write Current
14mA
30mA
Isb
Standby Current
60uA
200uA
Isbr
Reset Current
60uA
200uA
Isbs
Sleep Mode Current *1
60uA
200uA
Idpd
Vcc deep power down current
4uA
40uA
1.5mA
4mA
CE#=Vil, OE#=Vih
14mA
28mA
CE#=Vil, OE#=Vih
Vol
Accelerated Pgm Current, WP#/Acc pin
(Word/Byte)
Accelerated Pgm Current, Vcc pin,
(Word/Byte)
Input Low Voltage
Input High Voltage
Very High Voltage for Auto Select/
Accelerated Program
Output Low Voltage
Voh
Ouput High Voltage
Vlko
Low Vcc Lock-out voltage *2
Icp1
Icp2
Vil
Vih
Vhv
-0.1V
0.7xVI/O
0.3xVI/O
VI/O+0.3V
9.5V
10.5V
0.45V
0.85xVI/O
2.1V
CE#=Vil, OE#=Vih
Vcc=Vcc max, other
pin disable
Vcc=Vccmax,
RESET# enable,
other pin disable
Iol=100uA
Ioh=-100uA
2.4V
Note:
1. Sleep mode enables the lower power when address remain stable for taa+30ns.
2. Not 100% tested.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
39
MX68GL1G0F
Figure 6. SWITCHING TEST CIRCUITS
3.3V
2.7KΩ
DEVICE UNDER
TEST
CL
6.2KΩ
Test Condition
Output Load Capacitance, CL : 1TTL gate, 30pF
Rise/Fall Times : 5ns
Input Pulse levels :0.0 ~ VI/O
In/Out reference levels :0.5VI/O
Figure 7. SWITCHING TEST WAVEFORMS
VI/O
VI/O / 2
0.0V
VI/O / 2
Test Points
INPUT
OUTPUT
P/N:PM1727
REV. 1.3, OCT. 30, 2013
40
MX68GL1G0F
Table 11. AC CHARACTERISTICS
VCC=2.7V~3.6V
Min. Typ. Max.
VI/O=VCC
110
Valid data output after address
VI/O=1.65 toVCC
120
VI/O=VCC
25
Page access time
VI/O=1.65 toVCC
30
VI/O=VCC
110
Valid data output after CE# low
VI/O=1.65 toVCC
120
VI/O=VCC
25
Valid data output after OE# low
VI/O=1.65 toVCC
30
Data output floating after OE# high or CE# high
20
Latency between read and write operation (Note)
35
Output hold time from the earliest rising edge of address, CE#, OE#
0
VI/O=VCC
110
Read period time
VI/O=1.65 toVCC
120
VI/O=VCC
110
Write period time
VI/O=1.65 toVCC
120
VI/O=VCC
110
Command write period time
VI/O=1.65 toVCC
120
Address setup time
0
Address setup time to OE# low during toggle bit polling
15
Address hold time
45
Address hold time from CE# or OE# high during toggle bit polling
0
Data setup time
30
Data hold time
0
Vcc setup time
500
Chip enable Setup time
0
Chip enable hold time
0
Output enable setup time
0
Read
0
Output enable hold time
Toggle & Data# Polling 10
WE# setup time
0
WE# hold time
0
CE# pulse width
35
CE# pulse width high
30
WE# pulse width
35
WE# pulse width high
30
VI/O=VCC
110
Program/Erase active time by RY/BY#
VI/O=1.65 toVCC
120
Read recover time before write
0
Read recover time before write
0
Symbol Description
Taa
Tpa
Tce
Toe
Tdf
Tsrw
Toh
Trc
Twc
Tcwc
Tas
Taso
Tah
Taht
Tds
Tdh
Tvcs
Tcs
Tch
Toes
Toeh
Tws
Twh
Tcepw
Tcepwh
Twp
Twph
Tbusy
Tghwl
Tghel
P/N:PM1727
Unit
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
us
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
REV. 1.3, OCT. 30, 2013
41
MX68GL1G0F
Symbol Description
Byte
Word
Twhwh1 Program operation
Twhwh1
Twhwh2
Tbal
Trdp
Acc program operation (Word/Byte)
Sector erase operation
Sector add hold time
Release from deep power down mode
VCC=2.7V~3.6V
Min. Typ. Max.
10
10
10
0.5
3.5
50
200
Unit
us
us
us
sec
us
us
Note : Not 100% tested.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
42
MX68GL1G0F
12. WRITE COMMAND OPERATION
Figure 8. COMMAND WRITE OPERATION
Tcwc
CE#
Vih
Vil
Tch
Tcs
WE#
Vih
Vil
Toes
OE#
Twph
Twp
Vih
Vil
Addresses
Vih
VA
Vil
Tah
Tas
Tdh
Tds
Vih
Data
Vil
DIN
VA: Valid Address
P/N:PM1727
REV. 1.3, OCT. 30, 2013
43
MX68GL1G0F
13. READ/RESET OPERATION
Figure 9. READ TIMING WAVEFORMS
CE#
Tce
Vih
Vil
Vih
WE#
OE#
Vil
Toeh
Tdf
Toe
Vih
Vil
Toh
Taa
Trc
Vih
Addresses
ADD Valid
Vil
Tsrw
Outputs
Voh
HIGH Z
DATA Valid
HIGH Z
Vol
P/N:PM1727
REV. 1.3, OCT. 30, 2013
44
MX68GL1G0F
Table 12. AC CHARACTERISTICS-RESET#
Item
Description
Setup
Speed
Unit
Trp1
RESET# Pulse Width (During Automatic Algorithms)
MIN
10
us
Trp2
RESET# Pulse Width (NOT During Automatic Algorithms)
MIN
500
ns
Trh
RESET# High Time Before Read
MIN
200
ns
Trb1
RY/BY# Recovery Time (to CE#, OE# go low)
MIN
0
ns
Trb2
RY/BY# Recovery Time (to WE# go low)
MIN
50
ns
Tready1 RESET# PIN Low (During Automatic Algorithms) to Read or Write
MAX
20
us
Tready2 RESET# PIN Low (NOT During Automatic Algorithms) to Read or Write
MAX
500
ns
Figure 10. RESET# TIMING WAVEFORM
Trb1
CE#, OE#
Trb2
WE#
Tready1
RY/BY#
RESET#
Trp1
Reset Timing during Automatic Algorithms
CE#, OE#
Trh
RY/BY#
RESET#
Trp2
Tready2
Reset Timing NOT during Automatic Algorithms
P/N:PM1727
REV. 1.3, OCT. 30, 2013
45
MX68GL1G0F
14. ERASE/PROGRAM OPERATION
Figure 11. AUTOMATIC CHIP ERASE TIMING WAVEFORM
CE#
Tch
Twhwh2
Twp
WE#
Twph
Tcs
Tghwl
OE#
Last 2 Erase Command Cycle
Twc
Address
Tas
2AAh
VA
555h
Tds
Data
Read Status
Tah
Tdh
55h
VA
In
Progress Complete
10h
Tbusy
Trb
RY/BY#
P/N:PM1727
REV. 1.3, OCT. 30, 2013
46
MX68GL1G0F
Figure 12. AUTOMATIC CHIP ERASE ALGORITHM FLOWCHART
START
Write Data AAH Address 555H
Write Data 55H Address 2AAH
Write Data 80H Address 555H
Write Data AAH Address 555H
Write Data 55H Address 2AAH
Write Data 10H Address 555H
Data# Polling Algorithm or
Toggle Bit Algorithm
NO
Data=FFh ?
YES
Auto Chip Erase Completed
P/N:PM1727
REV. 1.3, OCT. 30, 2013
47
MX68GL1G0F
Figure 13. AUTOMATIC SECTOR ERASE TIMING WAVEFORM
Read Status
CE#
Tch
Twhwh2
Twp
WE#
Twph
Tcs
Tghwl
OE#
Tbal
Last 2 Erase Command Cycle
Twc
Address
Tas
Sector
Address 0
2AAh
Tds
Tdh
55h
Sector
Address 1
Sector
Address n
Tah
VA
VA
In
Progress Complete
30h
30h
30h
Data
Tbusy
Trb
RY/BY#
P/N:PM1727
REV. 1.3, OCT. 30, 2013
48
MX68GL1G0F
Figure 14. AUTOMATIC SECTOR ERASE ALGORITHM FLOWCHART
START
Write Data AAH Address 555H
Write Data 55H Address 2AAH
Write Data 80H Address 555H
Write Data AAH Address 555H
Write Data 55H Address 2AAH
Write Data 30H Sector Address
Last Sector
NO
to Erase
YES
Data# Polling Algorithm or
Toggle Bit Algorithm
Data=FFh
NO
YES
Auto Sector Erase Completed
P/N:PM1727
REV. 1.3, OCT. 30, 2013
49
MX68GL1G0F
Figure 15. ERASE SUSPEND/RESUME FLOWCHART
START
Write Data B0H
Toggle Bit checking Q6
NO
ERASE SUSPEND
not toggled
YES
Read Array or
Program
Reading or
Programming End
NO
YES
Write Data 30H
ERASE RESUME
Continue Erase
Another
Erase Suspend ?
NO
YES
P/N:PM1727
REV. 1.3, OCT. 30, 2013
50
MX68GL1G0F
Figure 16. AUTOMATIC PROGRAM TIMING WAVEFORMS
CE#
Tch
Twhwh1
Twp
WE#
Tcs
Twph
Tghwl
OE#
Last 2 Program Command Cycle
555h
Address
Last 2 Read Status Cycle
Tah
Tas
VA
PA
Tds
VA
Tdh
A0h
Status
PD
DOUT
Data
Tbusy
Trb
RY/BY#
Figure 17. ACCELERATED PROGRAM TIMING DIAGRAM
Vcc (min)
Vcc
GND
Tvcs
Vhv
(9.5V ~ 10.5V)
WP#/ACC
Vil or Vih
Vil or Vih
250ns
250ns
P/N:PM1727
REV. 1.3, OCT. 30, 2013
51
MX68GL1G0F
Figure 18. CE# CONTROLLED WRITE TIMING WAVEFORM
WE#
Tcepw
Tws
Twh
CE#
Twhwh1 or Twhwh2
Tcepwh
Tghwl
OE#
Tah
Tas
Address
555h
Tds
Data
VA
PA
VA
Tdh
A0h
Status
PD
DOUT
Tbusy
RY/BY#
P/N:PM1727
REV. 1.3, OCT. 30, 2013
52
MX68GL1G0F
Figure 19. AUTOMATIC PROGRAMMING ALGORITHM FLOWCHART
START
Write Data AAH Address 555H
Write Data 55H Address 2AAH
Write Data A0H Address 555H
Write Program Data/Address
Data# Polling Algorithm or
Toggle Bit Algorithm
next address
Read Again Data:
Program Data?
No
YES
No
Last Word to be
Programed
YES
Auto Program Completed
P/N:PM1727
REV. 1.3, OCT. 30, 2013
53
MX68GL1G0F
15. SILICON ID READ OPERATION
Figure 20. SILICON ID READ TIMING WAVEFORM
VCC
3V
Vhv
ADD
Vih
A9
ADD
A0
Vil
Vih
Vil
Taa
A1
Taa
Taa
Taa
Vih
Vil
A2
Vih
Vil
ADD
CE#
WE#
Vih
Vil
Disable
Enable
Tce
Vih
Vil
OE#
Vih
Toe
Tdf
Vil
Toh
DATA
Q15~Q0
Toh
Toh
Toh
Vih
Vil
DATA OUT
DATA OUT
DATA OUT
DATA OUT
Manufacturer ID
Device ID
Cycle 1
Device ID
Cycle 2
Device ID
Cycle 3
P/N:PM1727
REV. 1.3, OCT. 30, 2013
54
MX68GL1G0F
16. WRITE OPERATION STATUS
Figure 21. DATA# POLLING TIMING WAVEFORMS (DURING AUTOMATIC ALGORITHMS)
Tce
CE#
Tch
WE#
Toe
OE#
Toeh
Tdf
Trc
Address
VA
VA
Taa
Toh
Q7
Complement
Complement
True
Valid Data
Q6~Q0
Status Data
Status Data
True
Valid Data
High Z
High Z
Tbusy
RY/BY#
P/N:PM1727
REV. 1.3, OCT. 30, 2013
55
MX68GL1G0F
Figure 22. STATUS POLLING FOR PROGRAM/ERASE
Start
Read Data at valid address
(Note 1)
No
Q7 = Data# ?
Yes
Q5 = 1 ?
No
Yes
Read Data at valid address
(Note 1)
No
Q7 = Data# ?
(Note 2)
Yes
Pass
Fail
Notes:
1. For programming, valid address means program address.
For erasing, valid address means erase sectors address.
2. Q7 may change simultaneously with Q5, so even Q5=1, Q7 should be reverify.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
56
MX68GL1G0F
Figure 23. STATUS POLLING FOR WRITE BUFFER PROGRAM
Start
Read Data at last write
address (Note 1)
Q7 = Data# ?
No
Yes
Q1=1 ?
Only for write
buffer program
Yes
No
No
Q5=1 ?
Read Data at last write
address (Note 1)
Yes
Read Data at last write
address (Note 1)
Q7 = Data# ?
(Note 2)
No
Q7 = Data# ?
(Note 2)
No
Yes
Write Buffer Abort
Yes
Fail
Pass
Notes:
1. For programming, valid address means program address.
For erasing, valid address means erase sectors address.
2. Q7 may change simultaneously with Q5, so even Q5=1, Q7 should be reverify.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
57
MX68GL1G0F
Figure 24. TOGGLE BIT TIMING WAVEFORMS (DURING AUTOMATIC ALGORITHMS)
Tce
CE#
Tch
WE#
Toe
OE#
Toeh
Tdf
Trc
Address
Taht
Taso
VA
VA
VA
VA
Taa
Toh
Q6/Q2
Valid Status
(first read)
Valid Status
Valid Data
(second read)
(stops toggling)
Valid Data
Tbusy
RY/BY#
VA : Valid Address
P/N:PM1727
REV. 1.3, OCT. 30, 2013
58
MX68GL1G0F
Figure 25. TOGGLE BIT ALGORITHM
Start
Read Data Twice
(Note 1)
No
Q6 Toggle ?
Yes
Q5 = 1 ?
No
Yes
Read Data Twice
(Note 1, 2)
No
Q6 Toggle ?
Yes
Pass
Fail
Notes:
1. Toggle bit Q7-Q0 should be read twice to check if it is toggling.
2. While Q5=1, the toggle bit (Q6) may stop toggling. Therefore, the system should be read again.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
59
MX68GL1G0F
17. PAGE READ OPERATION
AC CHARACTERISTICS
WORD/BYTE CONFIGURATION (BYTE#)
Test
Setup
Max.
Max.
Min.
Parameter Description
Telfl/Telfh
Tflqz
Tfhqv
CE# to BYTE# from L/H
BYTE# from L to Output Hiz
BYTE# from H to Output Active
All Speed Options
Unit
5
30
90
ns
ns
ns
Figure 26. BYTE# TIMING WAVEFORM FOR READ OPERATIONS (BYTE# switching from byte mode to
word mode)
CE#
OE#
Telfh
BYTE#
Q14~Q0
DOUT
(Q0-Q7)
Q15/A-1
VA
DOUT
(Q0-Q14)
DOUT
(Q15)
Tfhqv
P/N:PM1727
REV. 1.3, OCT. 30, 2013
60
MX68GL1G0F
Figure 27. PAGE READ TIMING WAVEFORM
VALID ADD
Amax:A3
(A-1),A0,A1,A2
1'st ADD
Taa
DATA
2'nd ADD
3'rd ADD
Tpa
Tpa
Data 1
Data 2
Data 3
Toe
OE#
Tce
CE#
Note: CE#, OE# are enable.
Page size is 8 words in Word mode, 16 bytes in Byte mode.
Address are A2~A0 for Word mode, A2~A-1 for Byte mode.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
61
MX68GL1G0F
18. DEEP POWER DOWN MODE OPERATION
Table 13. AC CHARACTERISTICS - Deep Power Down Mode
Item
WEB high to release from deep power down mode
WEB high to deep power down mode
Typ.
Max.
tRDP
100us
200us
tDP
10us
20us
Figure 28. DEEP POWER DOWN MODE WAVEFORM
CEB
WEB
ADD
DATA
tDP
55
XX
2AA
AA
55
tRDP
XX (don't care)
AB
B9
Standby mode
P/N:PM1727
Deep power down mode Standby mode
REV. 1.3, OCT. 30, 2013
62
MX68GL1G0F
19. WRITE BUFFER PROGRAM OPERATION
Figure 29. WRITE BUFFER PROGRAM FLOWCHART
Write CMD: Data=AAh, Addr=555h
Write CMD: Data=55h, Addr=2AAh
Write CMD: Data=29h, Addr=SA
Write CMD: Data=25h, Addr=SA
Polling Status
Write CMD: Data=PWC, Addr=SA
PWC=PWC-1
Yes
Write CMD:
Data=PGM_data, Addr=PGM_addr
Want to Abort ?
PWC =0?
No
Return to read Mode
No
Fail
Yes
Write a different sector
address to cause Abort
Yes
No
No
Pass
Yes
Yes
Write Buffer Abort
No
SA: Sector Address of to be Programmed page
PWC: Program Word Count
Write Abort reset CMD
to return to read Mode
P/N:PM1727
Write reset CMD
to return to read Mode
REV. 1.3, OCT. 30, 2013
63
MX68GL1G0F
20. RECOMMENDED OPERATING CONDITIONS
At Device Power-Up
AC timing illustrated in Figure 30 is recommended for the supply voltages and the control signals at device power-up (e.g. VCC and CE# ramp up simultaneously). If the timing in the figure is ignored, the device may not operate correctly.
Figure 30. AC Timing at Device Power-Up
VCC
VI/O
VCC(min)
GND
Tvr
Tvcs
VI/O(min)
GND
Tvr
Tvios
Tf
CE#
WE#
Tce
Vil
Vih
Vil
Tf
OE#
WP#/ACC
Symbol
Tvr
Tr
Tf
Tvcs
Tvios
Tr
Vil
Vih
Taa
Tr or Tf
Valid
Address
Vil
Voh
DATA
Toe
Vih
Tr or Tf
ADDRESS
Tr
Vih
High Z
Valid
Ouput
Vol
Vih
Vil
Parameter
VCC Rise Time
Input Signal Rise Time
Input Signal Fall Time
VCC Setup Time
VI/O Setup Time
Min.
20
500
500
Max.
500000
20
20
Unit
us/V
us/V
us/V
us
us
Notes:
1. VI/O<VCC+200mV.
2. Not test 100%.
P/N:PM1727
REV. 1.3, OCT. 30, 2013
64
MX68GL1G0F
21. ERASE AND PROGRAMMING PERFORMANCE
Limits
Typ. (1)
400
Max. (2)
1000
Sector Erase Time
0.5
3.5
sec
Chip Programming Time
320
1400
sec
Word Program Time
10
180
us
Total Write Buffer Time
70
140
us
ACC Total Write Buffer Time
70
Parameter
Min.
Chip Erase Time
Erase/Program Cycles
Units
sec
us
100,000
Cycles
Notes:
1. Typical program and erase times assume the following conditions: 25°C, 3.0V VCC. Programming specifications assume checkboard data pattern.
2. Maximum values are measured at VCC = 3.0 V, worst case temperature. Maximum values are valid up to and
including 100,000 program/erase cycles.
3. Erase/Program cycles comply with JEDEC JESD-47 & JESD 22-A117 standard.
4. Exclude 00h program before erase operation.
22. DATA RETENTION
Parameter
Condition
Min.
Data retention
55˚C
20
Max.
Unit
years
23. LATCH-UP CHARACTERISTICS
Min.
-1.0V
-1.0V
-100mA
Input Voltage voltage difference with GND on WP#/ACC and A9 pins
Input Voltage voltage difference with GND on all normal pins input
Vcc Current
All pins included except Vcc. Test conditions: Vcc = 3.0V, one pin per testing
Max.
10.5V
1.5Vcc
+100mA
24. PIN CAPACITANCE
Parameter Symbol
CIN2
COUT
CIN
Parameter Description
Control Pin Capacitance
Output Capacitance
Input Capacitance
Test Set
VIN=0
VOUT=0
VIN=0
P/N:PM1727
Typ.
15
17
20
Max.
70
24
30
Unit
pF
pF
pF
REV. 1.3, OCT. 30, 2013
65
MX68GL1G0F
25. ORDERING INFORMATION
PART NO.
ACCESS TIME (ns)
PACKAGE
MX68GL1G0FHXFI-11G
110
64 LFBGA
MX68GL1G0FLXFI-11G
110
64 LFBGA
MX68GL1G0FHT2I-11G
110
56 Pin TSOP
MX68GL1G0FLT2I-11G
110
56 Pin TSOP
MX68GL1G0FUXFI-12G *
120
64 LFBGA
MX68GL1G0FDXFI-12G *
120
64 LFBGA
MX68GL1G0FUT2I-12G *
120
56 Pin TSOP
MX68GL1G0FDT2I-12G *
120
56 Pin TSOP
Remark
* Advance Information
P/N:PM1727
REV. 1.3, OCT. 30, 2013
66
MX68GL1G0F
26. PART NAME DESCRIPTION
MX 68 GL 1G0 F H T2 I
11 G
OPTION:
G: RoHS Compliant & Halogen-free
SPEED:
11: 110ns
12: 120ns
TEMPERATURE RANGE:
I: Industrial (-40° C to 85° C)
PACKAGE:
T2: 56-TSOP
XF: LFBGA (11mm x 13mm)
PRODUCT TYPE (Protection when WP#=VIL):
H: VI/O=VCC=2.7 to 3.6V, Highest Address Sector Protected, uniform sector
L: VI/O=VCC=2.7 to 3.6V, Lowest Address Sector Protected, uniform sector
U: VI/O=1.65 to VCC, VCC=2.7 to 3.6V, Highest Address Sector Protected, uniform sector
D: VI/O=1.65 to VCC, VCC=2.7 to 3.6V, Lowest Address Sector Protected, uniform sector
REVISION:
F
DENSITY & MODE:
1G0: 1Gb x8/x16 Architecture
TYPE:
GL: 3V Page Mode
DEVICE:
68: Stack Die Flash
P/N:PM1727
REV. 1.3, OCT. 30, 2013
67
MX68GL1G0F
27. PACKAGE INFORMATION
P/N:PM1727
REV. 1.3, OCT. 30, 2013
68
MX68GL1G0F
P/N:PM1727
REV. 1.3, OCT. 30, 2013
69
MX68GL1G0F
28. REVISION HISTORY
Revision No.Description
Page
Date
0.01
1. Changed title from Advanced Information to Preliminary
P5
MAY/09/2012
2. Added MX68GL1G0F U/D function
P5,7,38~41
3. Added MX68GL1G0F U/D ORDERING INFORMATION
P65,66
and PART NAME DESCRIPTION
4. Modified Figure 18. CE# Controlled Write Timing WaveformP52
5. Added VI/O Setup Time
P63
1.0
Removed "Preliminary" from Feature page.
P5
JUL/27/2012
1.1
1. Added Word/Byte Configuration (BYTE#) & Figure 26 P60FEB/01/2013
2. Modified "Figure 27. PAGE READ TIMING WAVEFORM"
P61
3. Modified Icr2P39
4. Modified Chip Programming Time (typ.) from 400sec to 800sec P65
5. Added Total Write Buffer Time (max.) 360us
P65
6. Added ACC Total Write Buffer Time (max.) 360us
P65
1.2
1. Advanced Sector Protection/Un-protection description updated P25~30
2. Modified Word/Byte Configuration (BYTE#) table
P60
3. Modified Erase And Programming Performance table
P65
AUG/12/2013
1.3
1. Updated parameters for DC Characteristics. 2. Updated Erase and Programming Performance.
3. Content correction
OCT/30/2013
P5,39 P5,42,65
P25~30
P/N:PM1727
REV. 1.3, OCT. 30, 2013
70
MX68GL1G0F
Except for customized products which have been expressly identified in the applicable agreement, Macronix's
products are designed, developed, and/or manufactured for ordinary business, industrial, personal, and/or
household applications only, and not for use in any applications which may, directly or indirectly, cause death,
personal injury, or severe property damages. In the event Macronix products are used in contradicted to their
target usage above, the buyer shall take any and all actions to ensure said Macronix's product qualified for its
actual use in accordance with the applicable laws and regulations; and Macronix as well as it’s suppliers and/or
distributors shall be released from any and all liability arisen therefrom.
Copyright© Macronix International Co., Ltd. 2011~2013. All rights reserved, including the trademarks and
tradename thereof, such as Macronix, MXIC, MXIC Logo, MX Logo, Integrated Solutions Provider, NBit, Nbit,
NBiit, Macronix NBit, eLiteFlash, HybridNVM, HybridFlash, XtraROM, Phines, KH Logo, BE-SONOS, KSMC,
Kingtech, MXSMIO, Macronix vEE, Macronix MAP, Rich Au­dio, Rich Book, Rich TV, and FitCAM. The names
and brands of third party referred thereto (if any) are for identification purposes only.
For the contact and order information, please visit Macronix’s Web site at: http://www.macronix.com
MACRONIX INTERNATIONAL CO., LTD. reserves the right to change product and specifications without notice.
71