MX25U1635FZNI-10G [Macronix]

Flash, 4MX4, PDSO8, WSON-8;
MX25U1635FZNI-10G
型号: MX25U1635FZNI-10G
厂家: MACRONIX INTERNATIONAL    MACRONIX INTERNATIONAL
描述:

Flash, 4MX4, PDSO8, WSON-8

时钟 光电二极管 内存集成电路
文件: 总96页 (文件大小:1853K)
中文:  中文翻译
下载:  下载PDF数据表文档文件
MX25U1635F  
MX25U1635F  
1.8V, 16M-BIT [x 1/x 2/x 4]  
CMOS MXSMIO® (SERIAL MULTI I/O)  
FLASH MEMORY  
Key Features  
• Fast read for SPI mode and QPI mode  
• 1.65 to 2.0 volt for read, erase, and program operations  
• 12-WLCSP (Wafer-Level Chip Scale Package)  
• Multi I/O Support - Single I/O, Dual I/O and Quad I/O  
• Program Suspend/Resume & Erase Suspend/Resume  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
1
MX25U1635F  
Contents  
1. FEATURES ..............................................................................................................................................................4  
2. GENERAL DESCRIPTION .....................................................................................................................................6  
Table 1. Additional Feature..........................................................................................................................7  
3. PIN CONFIGURATIONS .........................................................................................................................................8  
4. PIN DESCRIPTION..................................................................................................................................................8  
5. BLOCK DIAGRAM...................................................................................................................................................9  
6. DATA PROTECTION..............................................................................................................................................10  
Table 2. Protected Area Sizes...................................................................................................................11  
Table 3. 4K-bit Secured OTP Definition ....................................................................................................12  
7. MEMORY ORGANIZATION...................................................................................................................................13  
Table 4. Memory Organization ..................................................................................................................13  
8. DEVICE OPERATION............................................................................................................................................14  
8-1. Quad Peripheral Interface (QPI) Read Mode .......................................................................................... 16  
9. COMMAND DESCRIPTION...................................................................................................................................17  
Table 5. Command Set..............................................................................................................................17  
9-1. Write Enable (WREN).............................................................................................................................. 21  
9-2. Write Disable (WRDI)............................................................................................................................... 22  
9-3. Read Identification (RDID)....................................................................................................................... 23  
9-4. Release from Deep Power-down (RDP), Read Electronic Signature (RES) ........................................... 24  
9-5. Read Electronic Manufacturer ID & Device ID (REMS)........................................................................... 26  
9-6. QPI ID Read (QPIID) ............................................................................................................................... 27  
Table 6. ID Definitions ..............................................................................................................................27  
9-7. Read Status Register (RDSR)................................................................................................................. 28  
9-8. Write Status Register (WRSR)................................................................................................................. 32  
Table 7. Protection Modes.........................................................................................................................33  
9-9. Read Data Bytes (READ) ........................................................................................................................ 36  
9-10. Read Data Bytes at Higher Speed (FAST_READ) .................................................................................. 37  
9-11. Dual Read Mode (DREAD)...................................................................................................................... 39  
9-12. 2 x I/O Read Mode (2READ) ................................................................................................................... 40  
9-13. Quad Read Mode (QREAD) .................................................................................................................... 41  
9-14. 4 x I/O Read Mode (4READ) ................................................................................................................... 42  
9-15. Burst Read............................................................................................................................................... 45  
9-16. Performance Enhance Mode................................................................................................................... 46  
9-17. Performance Enhance Mode Reset......................................................................................................... 49  
9-18. Sector Erase (SE).................................................................................................................................... 50  
9-19. Block Erase (BE32K)............................................................................................................................... 51  
9-20. Block Erase (BE) ..................................................................................................................................... 52  
9-21. Chip Erase (CE)....................................................................................................................................... 53  
9-22. Page Program (PP) ................................................................................................................................. 54  
9-23. 4 x I/O Page Program (4PP).................................................................................................................... 56  
9-24. Deep Power-down (DP)........................................................................................................................... 57  
9-25. Enter Secured OTP (ENSO).................................................................................................................... 58  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
2
MX25U1635F  
9-26. Exit Secured OTP (EXSO)....................................................................................................................... 58  
9-27. Read Security Register (RDSCUR)......................................................................................................... 58  
Table 8. Security Register Definition .........................................................................................................59  
9-28. Write Security Register (WRSCUR)......................................................................................................... 59  
9-29. Write Protection Selection (WPSEL)........................................................................................................ 60  
9-30. Single Block Lock/Unlock Protection (SBLK/SBULK).............................................................................. 63  
9-31. Read Block Lock Status (RDBLOCK)...................................................................................................... 65  
9-32. Gang Block Lock/Unlock (GBLK/GBULK) ............................................................................................... 65  
9-33. Program Suspend and Erase Suspend ................................................................................................... 66  
Table 9. Readable Area of Memory While a Program or Erase Operation is Suspended.........................66  
Table 10. Acceptable Commands During Program/Erase Suspend after tPSL/tESL................................67  
Table 11. Acceptable Commands During Suspend (tPSL/tESL not required)...........................................67  
9-34. Program Resume and Erase Resume..................................................................................................... 69  
9-35. No Operation (NOP) ................................................................................................................................ 69  
9-36. Software Reset (Reset-Enable (RSTEN) and Reset (RST)) ................................................................... 69  
9-37. Read SFDP Mode (RDSFDP).................................................................................................................. 71  
Table 12. Signature and Parameter Identification Data Values ................................................................72  
Table 13. Parameter Table (0): JEDEC Flash Parameter Tables..............................................................73  
Table 14. Parameter Table (1): Macronix Flash Parameter Tables ...........................................................75  
10. RESET..................................................................................................................................................................77  
Table 15. Reset Timing..............................................................................................................................77  
11. POWER-ON STATE .............................................................................................................................................78  
12. ELECTRICAL SPECIFICATIONS........................................................................................................................79  
Table 16. Absolute Maximum Ratings.......................................................................................................79  
Table 17. Capacitance...............................................................................................................................79  
Table 18. DC Characteristics.....................................................................................................................81  
Table 19. AC Characteristics ....................................................................................................................82  
13. OPERATING CONDITIONS.................................................................................................................................84  
Table 20. Power-Up Timing and VWI Threshold .......................................................................................86  
13-1. Initial Delivery State................................................................................................................................. 86  
14. ERASE AND PROGRAMMING PERFORMANCE..............................................................................................87  
15. LATCH-UP CHARACTERISTICS........................................................................................................................87  
16. ORDERING INFORMATION................................................................................................................................88  
17. PART NAME DESCRIPTION...............................................................................................................................89  
18. PACKAGE INFORMATION..................................................................................................................................90  
18-1. 8-pin SOP (200mil) .................................................................................................................................. 90  
18-2. 8-land WSON (6mm x 5mm).................................................................................................................... 91  
18-3. 8-land USON (4mm x 4mm) .................................................................................................................... 92  
18-4. 8-land USON (4mm x 3mm) .................................................................................................................... 93  
18-5. 12-ball WLCSP ........................................................................................................................................ 94  
19. REVISION HISTORY ...........................................................................................................................................95  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
3
MX25U1635F  
Figures  
Figure 1. Serial Modes Supported...............................................................................................................................................15  
Figure 2. Serial Input Timing........................................................................................................................................................16  
Figure 3. Output Timing ...............................................................................................................................................................16  
Figure 4. Enable QPI Sequence (Command 35H) ......................................................................................................................17  
Figure 5. Reset QPI Mode (Command F5H) ...............................................................................................................................17  
Figure 6. Write Enable (WREN) Sequence (SPI Mode) ..............................................................................................................22  
Figure 7. Write Enable (WREN) Sequence (QPI Mode)..............................................................................................................22  
Figure 8. Write Disable (WRDI) Sequence (SPI Mode)...............................................................................................................23  
Figure 9. Write Disable (WRDI) Sequence (QPI Mode)...............................................................................................................23  
Figure 10. Read Identification (RDID) Sequence (SPI mode only)..............................................................................................24  
Figure 11. Read Electronic Signature (RES) Sequence (SPI Mode)...........................................................................................25  
Figure 12. Read Electronic Signature (RES) Sequence (QPI Mode) ..........................................................................................26  
Figure 13. Release from Deep Power-down (RDP) Sequence (SPI Mode) ................................................................................26  
Figure 14. Release from Deep Power-down (RDP) Sequence (QPI Mode)................................................................................26  
Figure 15. Read Electronic Manufacturer & Device ID (REMS) Sequence (SPI Mode only) .....................................................27  
Figure 16. Read Status Register (RDSR) Sequence (SPI Mode) ...............................................................................................29  
Figure 17. Read Status Register (RDSR) Sequence (QPI Mode)...............................................................................................29  
Figure 18. Program/Erase flow with read array data ...................................................................................................................30  
Figure 19. Program/Erase flow without read array data (read P_FAIL/E_FAIL flag) ...................................................................31  
Figure 20. Write Status Register (WRSR) Sequence (SPI Mode)..............................................................................................33  
Figure 21. Write Status Register (WRSR) Sequence (QPI Mode)..............................................................................................33  
Figure 22. WRSR flow .................................................................................................................................................................35  
Figure 23. WP# Setup Timing and Hold Timing during WRSR when SRWD=1 ..........................................................................36  
Figure 24. Read Data Bytes (READ) Sequence (SPI Mode only)...............................................................................................37  
Figure 25. Read at Higher Speed (FAST_READ) Sequence (SPI Mode) ...................................................................................39  
Figure 26. Read at Higher Speed (FAST_READ) Sequence (QPI Mode)...................................................................................39  
Figure 27. Dual Read Mode Sequence (Command 3B)..............................................................................................................40  
Figure 28. 2 x I/O Read Mode Sequence (SPI Mode only) .........................................................................................................41  
Figure 29. Quad Read Mode Sequence (Command 6B).............................................................................................................42  
Figure 30. 4 x I/O Read Mode Sequence (SPI Mode).................................................................................................................44  
Figure 31. 4 x I/O Read Mode Sequence (QPI Mode).................................................................................................................44  
Figure 32. W4READ (Quad Read with 4 dummy cycles) Sequence ..........................................................................................45  
Figure 33. SPI Mode....................................................................................................................................................................46  
Figure 34. QPI Mode ...................................................................................................................................................................46  
Figure 35. 4 x I/O Read enhance performance Mode Sequence (SPI Mode).............................................................................48  
Figure 36. 4 x I/O Read enhance performance Mode Sequence (QPI Mode).............................................................................49  
Figure 37. Performance Enhance Mode Reset for Fast Read Quad I/O (SPI Mode)..................................................................50  
Figure 38. Performance Enhance Mode Reset for Fast Read Quad I/O (QPI Mode) .................................................................50  
Figure 39. Sector Erase (SE) Sequence (SPI Mode) .................................................................................................................51  
Figure 40. Sector Erase (SE) Sequence (QPI Mode).................................................................................................................51  
Figure 41. Block Erase 32KB (BE32K) Sequence (SPI Mode)...................................................................................................52  
Figure 42. Block Erase 32KB (BE32K) Sequence (QPI Mode) ..................................................................................................52  
Figure 43. Block Erase (BE) Sequence (SPI Mode)....................................................................................................................53  
Figure 44. Block Erase (BE) Sequence (QPI Mode) ...................................................................................................................53  
Figure 45. Chip Erase (CE) Sequence (SPI Mode)....................................................................................................................54  
Figure 46. Chip Erase (CE) Sequence (QPI Mode)....................................................................................................................54  
Figure 47. Page Program (PP) Sequence (SPI Mode)................................................................................................................56  
Figure 48. Page Program (PP) Sequence (QPI Mode) ...............................................................................................................56  
Figure 49. 4 x I/O Page Program (4PP) Sequence (SPI Mode only)...........................................................................................57  
Figure 50. Deep Power-down (DP) Sequence (SPI Mode) .........................................................................................................58  
Figure 51. Deep Power-down (DP) Sequence (QPI Mode).........................................................................................................58  
Figure 52. Write Protection Selection (WPSEL) Sequence (Command 68) ...............................................................................62  
Figure 53. WPSEL Flow...............................................................................................................................................................63  
Figure 54. Block Lock Flow..........................................................................................................................................................64  
Figure 55. Block Unlock Flow ......................................................................................................................................................65  
Figure 56. Suspend to Read Latency ..........................................................................................................................................69  
Figure 57. Resume to Suspend Latency .....................................................................................................................................69  
Figure 58. Suspend to Program Latency.....................................................................................................................................69  
Figure 59. Resume to Read Latency...........................................................................................................................................70  
Figure 60. Software Reset Recovery...........................................................................................................................................71  
Figure 61. Reset Sequence (SPI mode)......................................................................................................................................71  
Figure 62. Reset Sequence (QPI mode) .....................................................................................................................................71  
Figure 63. Read Serial Flash Discoverable Parameter (RDSFDP) Sequence............................................................................72  
Figure 64. RESET Timing............................................................................................................................................................78  
Figure 65. Maximum Negative Overshoot Waveform..................................................................................................................80  
Figure 66. Maximum Positive Overshoot Waveform....................................................................................................................80  
Figure 67. Input Test Waveforms and Measurement Level .........................................................................................................81  
Figure 68. Output Loading...........................................................................................................................................................81  
Figure 69. AC Timing at Device Power-Up ..................................................................................................................................85  
Figure 70. Power-Down Sequence..............................................................................................................................................86  
Figure 71. Power-up Timing.........................................................................................................................................................87  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
4
MX25U1635F  
1.8V 16M-BIT [x 1/x 2/x 4] CMOS MXSMIO(SERIAL MULTI I/O)  
FLASH MEMORY  
1. FEATURES  
GENERAL  
SOFTWARE FEATURES  
Supports Serial Peripheral Interface -- Mode 0 and  
Mode 3  
16,777,216 x 1 bit structure or 8,388,608 x 2 bits (two  
I/O read mode) structure or 4,194,304 x 4 bits (four  
I/O read mode) structure  
Input Data Format  
- 1-byte Command code  
Advanced Security Features  
- Block lock protection  
Equal Sectors with 4K byte each, or Equal Blocks  
with 32K byte each or Equal Blocks with 64K byte  
each  
The BP0-BP3 status bit defines the size of the area  
to be software protection against program and erase  
instructions  
- Additional 4k-bit secured OTP for unique identifier  
Auto Erase and Auto Program Algorithm  
- Any Block can be erased individually  
Single Power Supply Operation  
- 1.65 to 2.0 volt for read, erase, and program op-  
erations  
Latch-up protected to 100mA from -1V to Vcc +1V  
Low Vcc write inhibit is from 1.0V to 1.4V  
Automatically erases and verifies data at selected  
sector or block  
-
Automatically programs and verifies data at select-  
ed page by an internal algorithm that automatically  
times the program pulse widths (Any page to be  
programed should have page in the erased state  
first)  
-
PERFORMANCE  
High Performance  
- Fast read for SPI mode  
- 1 I/O: 104MHz with 8 dummy cycles  
- 2 I/O: 84MHz with 4 dummy cycles, equivalent  
to 168MHz  
- 4 I/O: 104MHz with 2+4 dummy cycles, equiva-  
lent to 416MHz  
- Fast read for QPI mode  
- 4 I/O: 84MHz with 2+2 dummy cycles, equiva-  
lent to 336MHz  
- 4 I/O: 104MHz with 2+4 dummy cycles, equiva-  
lent to 416MHz  
- Fast program time: 0.5ms(typ.) and 1.5ms(max.)/  
page (256-byte per page)  
- Byte program time: 12us (typical)  
- 8/16/32/64 byte Wrap-Around Burst Read Mode  
- Fast erase time: 35ms (typ.)/sector (4K-byte per  
sector); 200ms(typ.)/block (32K-byte per block),  
350ms(typ.) /  
Status Register Feature  
Command Reset  
Program/Erase Suspend  
Electronic Identification  
JEDEC 1-byte manufacturer ID and 2-byte device  
-
ID  
- RES command for 1-byte Device ID  
- REMS command for 1-byte manufacturer ID and  
1-byte device ID  
Support Serial Flash Discoverable Parameters  
(SFDP) mode  
HARDWARE FEATURES  
SCLK Input  
- Serial clock input  
SI/SIO0  
- Serial Data Input or Serial Data Input/Output for 2  
x I/O read mode and 4 x I/O read mode  
SO/SIO1  
block (64K-byte per block)  
- Serial Data Output or Serial Data Input/Output for  
2 x I/O read mode and 4 x I/O read mode  
WP#/SIO2  
- Hardware write protection or serial data Input/Out-  
put for 4 x I/O read mode  
RESET#/SIO3  
- Hardware Reset pin or Serial input & Output for 4  
x I/O read mode  
PACKAGE  
- 8-pin SOP (200mil)  
Low Power Consumption  
- Low active read current: 20mA(typ.) at 104MHz,  
15mA(typ.) at 84MHz  
- Low active erase current: 18mA (typ.) at Sector  
Erase, Block Erase (32KB/64KB); 20mA at Chip  
Erase  
- Low active programming current: 20mA (typ.)  
- Standby current: 10uA (typ.)  
- 8-land WSON (6mm x 5mm)  
- 8-land USON (4mm x 4mm)  
- 8-land USON (4mm x 3mm)  
- 12-ball WLCSP  
- All devices are RoHS Compliant and Halogen-  
free  
Deep Power Down: 1.5uA(typ.)  
Typical 100,000 erase/program cycles  
20 years data retention  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
5
MX25U1635F  
2. GENERAL DESCRIPTION  
MX25U1635F is a 16,777,216 bit Serial NOR Flash memory, which is configured as 2,097,152 x 8 internally. When  
it is in two or four I/O read mode, the structure becomes 8,388,608 bits x 2 or 4,194,304 bits x 4. MX25U1635F fea-  
ture a serial peripheral interface and software protocol allowing operation on a simple 3-wire bus while it is in single  
I/O mode. The three bus signals are a clock input (SCLK), a serial data input (SI), and a serial data output (SO).  
Serial access to the device is enabled by CS# input.  
When it is in two I/O read mode, the SI pin and SO pin become SIO0 pin and SIO1 pin for address/dummy bits in-  
put and data output. When it is in four I/O read mode, the SI pin, SO pin and WP# pin become SIO0 pin, SIO1 pin,  
SIO2 pin and SIO3 pin for address/dummy bits input and data output.  
The MX25U1635F MXSMIO(Serial Multi I/O) provides sequential read operation on the whole chip.  
After program/erase command is issued, auto program/erase algorithms which program/erase and verify the speci-  
fied page or sector/block locations will be executed. Program command is executed on byte basis, or page (256  
bytes) basis, or word basis for erase command is executed on 4K-byte sector, 32K-byte block, or 64K-byte block, or  
whole chip basis.  
To provide user with ease of interface, a status register is included to indicate the status of the chip. The status read  
command can be issued to detect completion status of a program or erase operation via the WIP bit.  
Advanced security features enhance the protection and security functions, please see security features section for  
more details.  
The MX25U1635F utilizes Macronix's proprietary memory cell, which reliably stores memory contents even after  
100,000 program and erase cycles.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
6
MX25U1635F  
Table 1. Additional Feature  
Protection and Security  
Flexible Block Protection (BP0-BP3)  
4K-bit security OTP  
MX25U1635F  
V
V
Read Performance  
MX25U1635F  
I/O mode  
SPI  
QPI  
I/O  
1 I/O  
8
1I /2O  
8
2 I/O  
4
1I/4O  
8
4 I/O  
4
4 I/O  
6
4 I/O  
4
4 I/O  
6
Dummy Cycle  
Frequency  
104MHz 104MHz 84 MHz 104MHz 84 MHz 104MHz 84 MHz 104MHz  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
7
MX25U1635F  
3. PIN CONFIGURATIONS  
8-PIN SOP (200mil)  
4. PIN DESCRIPTION  
SYMBOL DESCRIPTION  
CS#  
Chip Select  
Serial Data Input (for 1 x I/O)/ Serial  
Data Input & Output (for 2xI/O or 4xI/  
O read mode)  
1
2
3
4
CS#  
SO/SIO1  
WP#/SIO2  
GND  
VCC  
8
7
6
5
RESET#/SIO3  
SCLK  
SI/SIO0  
SI/SIO0  
Serial Data Output (for 1 x I/O)/ Serial  
Data Input & Output (for 2xI/O or 4xI/  
O read mode)  
SO/SIO1  
SCLK  
Clock Input  
8-LAND WSON (6mmx5mm)  
Write Protection Active Low or Serial  
WP#/SIO2 Data Input & Output (for 4xI/O read  
mode)  
Hardware Reset Pin Active low or  
RESET#/SIO3 Serial Data Input & Output (for 4xI/O  
read mode)  
1
2
3
4
VCC  
CS#  
SO/SIO1  
WP#/SIO2  
GND  
8
7
6
5
RESET#/SIO3  
SCLK  
SI/SIO0  
VCC  
+ 1.8V Power Supply  
GND  
Ground  
Note: The pin of RESET#/SIO3 or WP#/SIO2 will  
remain internal pull up function while this  
pin is not physically connected in system  
configuration.However, the internal pull up  
function will be disabled if the system has  
physical connection to RESET#/SIO3 or WP#/  
SIO2 pin.  
8-LAND USON(4mmx4mm), 8-LAND USON(4mmx3mm)  
1
2
3
4
VCC  
CS#  
SO/SIO1  
WP#/SIO2  
GND  
8
7
6
5
RESET#/SIO3  
SCLK  
SI/SIO0  
12-BALL BGA (WLCSP) TOP View  
1
2
3
4
A
B
NC  
NC  
CS#  
VCC  
SO/SIO1  
RESET#/SIO3  
SCLK  
C
D
WP#/SIO2  
NC SI/SIO0  
GND  
NC  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
8
MX25U1635F  
5. BLOCK DIAGRAM  
Address  
Generator  
Memory Array  
Y-Decoder  
SI/SIO0  
SO/SIO1  
SIO2 *  
Data  
Register  
SIO3 *  
WP# *  
SRAM  
Buffer  
Sense  
Amplifier  
HOLD# *  
RESET# *  
CS#  
Mode  
Logic  
State  
Machine  
HV  
Generator  
SCLK  
Clock Generator  
Output  
Buffer  
* Depends on part number options.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
9
MX25U1635F  
6. DATA PROTECTION  
During power transition, there may be some false system level signals which result in inadvertent erasure or pro-  
gramming. The device is designed to protect itself from these accidental write cycles.  
The state machine will be reset as standby mode automatically during power up. In addition, the control register  
architecture of the device constrains that the memory contents can only be changed after specific command se-  
quences have completed successfully.  
In the following, there are several features to protect the system from the accidental write cycles during VCC power-  
up and power-down or from system noise.  
• Valid command length checking: The command length will be checked whether it is at byte base and completed  
on byte boundary.  
• Write Enable (WREN) command: WREN command is required to set the Write Enable Latch bit (WEL) before is-  
suing other commands to change data.  
Deep Power Down Mode: By entering deep power down mode, the flash device is under protected from writing  
all commands except Release from deep power down mode command (RDP) and Read Electronic Signature  
command (RES) and softreset command.  
Advanced Security Features: there are some protection and security features which protect content from inad-  
vertent write and hostile access.  
I. Block lock protection  
- The Software Protected Mode (SPM) use (BP3, BP2, BP1, BP0) bits to allow part of memory to be protected  
as read only. The protected area definition is shown as "Table 2. Protected Area Sizes", the protected areas are  
more flexible which may protect various area by setting value of BP0-BP3 bits.  
- The Hardware Proteced Mode (HPM) use WP#/SIO2 to protect the (BP3, BP2, BP1, BP0) bits and Status Reg-  
ister Write Protect bit.  
- In four I/O and QPI mode, the feature of HPM will be disabled.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
10  
MX25U1635F  
Table 2. Protected Area Sizes  
Status bit  
Protect Level  
16Mb  
BP3  
0
BP2  
0
BP1  
0
BP0  
0
0 (none)  
0
0
0
1
1 (1block, protected block 31st)  
0
0
1
0
2 (2blocks, protected block 30th~31st)  
3 (4blocks, protected block 28th~31st)  
4 (8blocks, protected block 24th~31st)  
5 (16blocks, protected block 16th~31st)  
6 (32blocks, protected all)  
0
0
1
1
0
1
0
0
0
1
0
1
0
1
1
0
0
1
1
1
7 (32blocks, protected all)  
1
0
0
0
8 (32blocks, protected all)  
1
0
0
1
9 (32blocks, protected all)  
1
1
1
1
1
1
0
0
1
1
1
1
1
1
0
0
1
1
0
1
0
1
0
1
10 (16blocks, protected block 0th~15th)  
11 (24blocks, protected block 0th~23rd)  
12 (28blocks, protected block 0th~27th)  
13 (30blocks, protected block 0th~29th)  
14 (31blocks, protected block 0th~30th)  
15 (32blocks, protected all)  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
11  
 
MX25U1635F  
II. Additional 4K-bit secured OTP for unique identifier: to provide 4K-bit one-time program area for setting de-  
vice unique serial number - Which may be set by factory or system customer.  
- Security register bit 0 indicates whether the chip is locked by factory or not.  
- To program the 4K-bit secured OTP by entering 4K-bit secured OTP mode (with Enter Security OTP command),  
and going through normal program procedure, and then exiting 4K-bit secured OTP mode by writing Exit Security  
OTP command.  
- Customer may lock-down the customer lockable secured OTP by writing WRSCUR(write security register) com-  
mand to set customer lock-down bit1 as "1". Please refer to "Table 8. Security Register Definition" for security  
register bit definition and "Table 3. 4K-bit Secured OTP Definition" for address range definition.  
- Note: Once lock-down whatever by factory or customer, it cannot be changed any more. While in 4K-bit secured  
OTP mode, array access is not allowed.  
Table 3. 4K-bit Secured OTP Definition  
Address range  
xxx000~xxx00F  
xxx010~xxx1FF  
Size  
Standard Factory Lock  
ESN (electrical serial number)  
N/A  
Customer Lock  
128-bit  
3968-bit  
Determined by customer  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
12  
 
MX25U1635F  
7. MEMORY ORGANIZATION  
Table 4. Memory Organization  
Block(64K-byte) Block(32K-byte) Sector (4K-byte)  
Address Range  
511  
1FF000h  
1FFFFFh  
63  
individual 16 sectors  
lock/unlock unit:4K-byte  
504  
503  
1F8000h  
1F7000h  
1F8FFFh  
1F7FFFh  
31  
62  
61  
60  
59  
58  
496  
495  
1F0000h  
1EF000h  
1F0FFFh  
1EFFFFh  
488  
487  
1E8000h  
1E7000h  
1E8FFFh  
1E7FFFh  
30  
individual block  
lock/unlock unit:64K-byte  
480  
479  
1E0000h  
1DF000h  
1E0FFFh  
1DFFFFh  
472  
471  
1D8000h  
1D7000h  
1D8FFFh  
1D7FFFh  
29  
464  
1D0000h  
1D0FFFh  
individual block  
lock/unlock unit:64K-byte  
47  
02F000h  
02FFFFh  
5
4
3
2
1
0
40  
39  
028000h  
027000h  
028FFFh  
027FFFh  
2
1
individual block  
lock/unlock unit:64K-byte  
32  
31  
020000h  
01F000h  
020FFFh  
01FFFFh  
24  
23  
018000h  
017000h  
018FFFh  
017FFFh  
16  
15  
010000h  
00F000h  
010FFFh  
00FFFFh  
8
7
008000h  
007000h  
008FFFh  
007FFFh  
individual 16 sectors  
lock/unlock unit:4K-byte  
0
0
000000h  
000FFFh  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
13  
 
MX25U1635F  
8. DEVICE OPERATION  
1. Before a command is issued, status register should be checked to ensure device is ready for the intended op-  
eration.  
2. When incorrect command is inputted to this device, it enters standby mode and remains in standby mode until  
next CS# falling edge. In standby mode, SO pin of the device is High-Z.  
3. When correct command is inputted to this device, it enters active mode and remains in active mode until next  
CS# rising edge.  
4. Input data is latched on the rising edge of Serial Clock (SCLK) and data shifts out on the falling edge of SCLK.  
The difference of Serial mode 0 and mode 3 is shown as "Figure 1. Serial Modes Supported".  
5. For the following instructions: RDID, RDSR, RDSCUR, READ, FAST_READ, DREAD, 2READ, 4READ, QREAD,  
W4READ, RDSFDP, RES, REMS, QPIID, RDBLOCK, the shifted-in instruction sequence is followed by a data-  
out sequence. After any bit of data being shifted out, the CS# can be high. For the following instructions: WREN,  
WRDI, WRSR, SE, BE32K, BE, CE, PP, 4PP, DP, ENSO, EXSO, WRSCUR, WPSEL, SBLK, SBULK, GBULK,  
SUSPEND, RESUME, NOP, RSTEN, RST, EQIO, RSTQIO the CS# must go high exactly at the byte boundary;  
otherwise, the instruction will be rejected and not executed.  
6. While a Write Status Register, Program or Erase operation is in progress, access to the memory array is ne-  
glected and will not affect the current operation of Write Status Register, Program, Erase.  
Figure 1. Serial Modes Supported  
CPOL CPHA  
shift in  
shift out  
SCLK  
SCLK  
(Serial mode 0)  
(Serial mode 3)  
0
1
0
1
SI  
MSB  
SO  
MSB  
Note:  
CPOL indicates clock polarity of Serial master, CPOL=1 for SCLK high while idle, CPOL=0 for SCLK low while not  
transmitting. CPHA indicates clock phase. The combination of CPOL bit and CPHA bit decides which Serial mode is  
supported.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
14  
 
 
MX25U1635F  
Figure 2. Serial Input Timing  
tSHSL  
tSHCH  
tCHCL  
CS#  
tCHSL  
tSLCH  
tCHSH  
SCLK  
tDVCH  
tCHDX  
tCLCH  
MSB  
LSB  
SI  
High-Z  
SO  
Figure 3. Output Timing  
CS#  
tCH  
SCLK  
tCLQV  
tCLQV  
tCL  
tSHQZ  
tCLQX  
SO  
tCLQX  
LSB  
ADDR.LSB IN  
SI  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
15  
 
MX25U1635F  
8-1. Quad Peripheral Interface (QPI) Read Mode  
QPI protocol enables user to take full advantage of Quad I/O Serial Flash by providing the Quad I/O interface in  
command cycles, address cycles and as well as data output cycles.  
Enable QPI mode  
By issuing 35H command, the QPI mode is enabled.  
Figure 4. Enable QPI Sequence (Command 35H)  
CS#  
MODE 3  
MODE 0  
2
3
4
5
6
7
0
1
SCLK  
SIO0  
35  
SIO[3:1]  
Reset QPI (RSTQIO)  
To reset the QPI mode, the RSTQIO (F5H) command is required. After the RSTQIO command is issued, the device  
returns from QPI mode (4 I/O interface in command cycles) to SPI mode (1 I/O interface in command cycles).  
Note:  
For EQIO and RSTQIO commands, CS# high width has to follow "write spec" tSHSL (defined in "Table 19. AC Char-  
acteristics") for next instruction.  
Figure 5. Reset QPI Mode (Command F5H)  
CS#  
SCLK  
SIO[3:0]  
F5  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
16  
 
MX25U1635F  
9. COMMAND DESCRIPTION  
Table 5. Command Set  
Read/Write Array Commands  
Mode  
SPI  
SPI/QPI  
SPI  
SPI  
SPI/QPI  
SPI  
2READ  
DREAD  
(1I / 2O read  
command)  
Command  
(byte)  
READ  
(normal read)  
FAST READ  
(fast read data)  
4READ  
(4 x I/O read)  
(2 x I/O read  
W4READ  
command) Note1  
1st byte  
03 (hex)  
ADD1(8)  
ADD2(8)  
ADD3(8)  
0B (hex)  
ADD1(8)  
3B (hex)  
ADD1(8)  
ADD2(8)  
ADD3(8)  
Dummy(8)  
BB (hex)  
ADD1(4)  
ADD2(4)  
ADD3(4)  
Dummy(4)  
EB (hex)  
ADD1(2)  
E7 (hex)  
ADD1  
2
nd byte  
3rd byte  
4th byte  
5th byte  
ADD2(8)  
ADD2(2)  
ADD2  
ADD3(8)  
ADD3(2)  
ADD3  
Dummy(8)/(4)*  
Dummy(6)  
Quad I/O read  
Dummy(4)  
Quad I/O read  
n bytes read out n bytes read out n bytes read out n bytes read out  
until CS# goes  
high  
until CS# goes  
high  
by Dual Output  
until CS# goes  
high  
by 2 x I/O until  
CS# goes high  
with 6 dummy for with 4 dummy  
cycles  
cycles  
Action  
Mode  
SPI  
SPI/QPI  
SPI  
SPI/QPI  
SPI/QPI  
SPI/QPI  
4PP  
(quad page  
program)  
BE 32K  
(block erase  
32KB)  
BE  
Command  
(byte)  
QREAD  
(1I/4O read)  
PP  
SE  
(block erase  
64KB)  
(page program)  
(sector erase)  
1st byte  
6B (hex)  
ADD1(8)  
ADD2(8)  
ADD3(8)  
Dummy(8)  
02 (hex)  
ADD1  
ADD2  
ADD3  
38 (hex)  
ADD1  
ADD2  
ADD3  
20 (hex)  
ADD1  
ADD2  
ADD3  
52 (hex)  
ADD1  
ADD2  
ADD3  
D8 (hex)  
ADD1  
2
nd byte  
3rd byte  
4th byte  
5th byte  
ADD2  
ADD3  
n bytes read out  
by Quad output  
until CS# goes  
high  
to program the  
selected page  
quad input to  
program the  
selected page  
to erase the  
selected sector  
to erase the  
selected 32K  
block  
to erase the  
selected block  
Action  
Mode  
SPI/QPI  
Command  
(byte)  
1st byte  
CE  
(chip erase)  
60 or C7 (hex)  
2
nd byte  
3rd byte  
4th byte  
5th byte  
to erase whole  
chip  
Action  
* For the Fast Read command (0Bh), when it is under QPI mode, the dummy cycle is 4 clocks.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
17  
MX25U1635F  
Register/Setting Commands  
RDSR  
(read status  
register)  
WRSR  
(write status  
register)  
WPSEL  
EQIO  
Command  
(byte)  
WREN  
(write enable)  
WRDI  
(write disable)  
(Write Protect  
Selection)  
(Enable QPI)  
Mode  
1st byte  
SPI/QPI  
06 (hex)  
SPI/QPI  
04 (hex)  
SPI/QPI  
05 (hex)  
SPI/QPI  
01 (hex)  
Values  
SPI/QPI  
68 (hex)  
SPI  
35 (hex)  
2
nd byte  
3rd byte  
4th byte  
5th byte  
sets the (WEL) resets the (WEL) to read out the  
to write new  
values of the  
status register  
to enter and  
enable individal  
block protect  
mode  
Entering the QPI  
mode  
write enable latch write enable latch  
values of the  
bit  
bit  
status register  
Action  
PGM/ERS  
Suspend  
(Suspends  
PGM/ERS  
Resume  
(Resumes  
RDP  
(Release from  
deep power  
down)  
DP  
Command  
(byte)  
RSTQIO  
(Reset QPI)  
SBL  
(Deep power  
down)  
(Set Burst Length)  
Program/Erase) Program/Erase)  
Mode  
QPI  
SPI/QPI  
B0 (hex)  
SPI/QPI  
30 (hex)  
SPI/QPI  
B9 (hex)  
SPI/QPI  
SPI/QPI  
C0 (hex)  
Value  
1st byte  
F5 (hex)  
AB (hex)  
2
nd byte  
3rd byte  
4th byte  
5th byte  
Exiting the QPI  
mode  
enters deep  
power down  
mode  
release from  
deep power down  
mode  
to set Burst length  
Action  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
18  
MX25U1635F  
ID/Security Commands  
REMS (read  
electronic  
electronic ID) manufacturer (QPI ID Read)  
& device ID)  
RDID  
(read identific-  
Command  
(byte)  
RES (read  
QPIID  
ENSO (enter EXSO (exit  
RDSFDP  
secured OTP) secured OTP)  
ation)  
Mode  
SPI  
SPI/QPI  
SPI  
QPI  
SPI/QPI  
5A (hex)  
ADD1(8)  
ADD2(8)  
ADD3(8)  
Dummy(8)  
SPI/QPI  
B1 (hex)  
SPI/QPI  
C1 (hex)  
1st byte  
9F (hex)  
AB (hex)  
90 (hex)  
AF (hex)  
2
nd byte  
x
x
x
x
3rd byte  
4th byte  
5th byte  
x
ADD(Note 2)  
outputs JEDEC to read out  
output the  
ID in QPI  
interface  
Read SFDP  
mode  
to enter the to exit the 4K-  
4K-bit secured bit secured  
ID: 1-byte  
Manufacturer  
ID & 2-byte  
Device ID  
1-byte Device Manufacturer  
ID  
ID & Device ID  
OTP mode  
OTP mode  
Action  
RDSCUR  
WRSCUR  
SBLK  
SBULK  
RDBLOCK  
GBLK  
GBULK  
(gang block  
unlock)  
COMMAND  
(byte)  
(read security (write security (single block (single block (block protect (gang block  
register)  
SPI/QPI  
2B (hex)  
register)  
SPI/QPI  
2F (hex)  
lock  
SPI/QPI  
36 (hex)  
unlock)  
SPI/QPI  
39 (hex)  
read)  
SPI/QPI  
3C (hex)  
lock)  
SPI/QPI  
7E (hex)  
Mode  
1st byte  
SPI/QPI  
98 (hex)  
2
nd byte  
ADD1  
ADD2  
ADD3  
ADD1  
ADD2  
ADD3  
ADD1  
ADD2  
ADD3  
3rd byte  
4th byte  
5th byte  
to read value to set the lock-  
individual  
block (64K-  
individual block read individual whole chip  
(64K-byte) or block or sector write protect  
whole chip  
unprotect  
of security  
register  
down bit as  
"1" (once lock- byte) or sector sector (4K-  
down, cannot (4K-byte) write byte) unprotect  
write protect  
status  
Action  
be update)  
protect  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
19  
MX25U1635F  
Reset Commands  
RST  
(Reset  
Memory)  
COMMAND  
NOP  
RSTEN  
(byte)  
(No Operation) (Reset Enable)  
Mode  
1st byte  
SPI/QPI  
00 (hex)  
SPI/QPI  
66 (hex)  
SPI/QPI  
99 (hex)  
2
nd byte  
3rd byte  
4th byte  
5th byte  
Action  
(Note 4)  
Note 1: The count base is 4-bit for ADD(2) and Dummy(2) because of 2 x I/O. And the MSB is on SO/SIO1 which is different  
from 1 x I/O condition.  
Note 2: ADD=00H will output the manufacturer ID first and ADD=01H will output device ID first.  
Note 3: It is not recommended to adopt any other code not in the command definition table, which will potentially enter the hid-  
den mode.  
Note 4: The RSTEN command must be executed before executing the RST command. If any other command is issued  
in-between RSTEN and RST, the RST command will be ignored.  
Note 5: The number in parentheses after "ADD" or "Data" stands for how many clock cycles it has. For example, "Data(8)"  
represents there are 8 clock cycles for the data in.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
20  
MX25U1635F  
9-1. Write Enable (WREN)  
The Write Enable (WREN) instruction is for setting Write Enable Latch (WEL) bit. For those instructions like PP, 4PP,  
SE, BE32K, BE, CE, and WRSR, which are intended to change the device content WEL bit should be set every time  
after the WREN instruction setting the WEL bit.  
The sequence of issuing WREN instruction is: CS# goes low→sending WREN instruction code→ CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
Figure 6. Write Enable (WREN) Sequence (SPI Mode)  
CS#  
0
1
2
3
4
5
6
7
Mode 3  
Mode 0  
SCLK  
Command  
06h  
SI  
High-Z  
SO  
Figure 7. Write Enable (WREN) Sequence (QPI Mode)  
CS#  
0
1
Mode 3  
SCLK  
Mode 0  
Command  
SIO[3:0]  
06h  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
21  
 
MX25U1635F  
9-2. Write Disable (WRDI)  
The Write Disable (WRDI) instruction is to reset Write Enable Latch (WEL) bit.  
The sequence of issuing WRDI instruction is: CS# goes low→sending WRDI instruction code→CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The WEL bit is reset by following situations:  
- Power-up  
- Reset# pin driven low  
- Completion of Write Disable (WRDI) instruction  
- Completion of Write Status Register (WRSR) instruction  
- Completion of Page Program (PP) instruction  
- Completion of Quad Page Program (4PP) instruction  
- Completion of Sector Erase (SE) instruction  
- Completion of Block Erase 32KB (BE32K) instruction  
- Completion of Block Erase (BE) instruction  
- Completion of Chip Erase (CE) instruction  
- Pgm/Ers Suspend  
Figure 8. Write Disable (WRDI) Sequence (SPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
SCLK  
Command  
04h  
SI  
High-Z  
SO  
Figure 9. Write Disable (WRDI) Sequence (QPI Mode)  
CS#  
0
1
Mode 3  
SCLK  
Mode 0  
Command  
SIO[3:0]  
04h  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
22  
 
MX25U1635F  
9-3. Read Identification (RDID)  
The RDID instruction is for reading the manufacturer ID of 1-byte and followed by Device ID of 2-byte. The Macro-  
nix Manufacturer ID and Device ID are listed as "Table 6. ID Definitions".  
The sequence of issuing RDID instruction is: CS# goes low→ sending RDID instruction code→24-bits ID data out  
on SO→ to end RDID operation can drive CS# to high at any time during data out.  
While Program/Erase operation is in progress, it will not decode the RDID instruction, therefore there's no effect on  
the cycle of program/erase operation which is currently in progress. When CS# goes high, the device is at standby  
stage.  
Figure 10. Read Identification (RDID) Sequence (SPI mode only)  
CS#  
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18  
28 29 30 31  
Mode 3  
Mode 0  
SCLK  
SI  
Command  
9Fh  
Manufacturer Identification  
Device Identification  
High-Z  
SO  
7
6
5
3
2
1
0
15 14 13  
MSB  
3
2
1
0
MSB  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
23  
 
MX25U1635F  
9-4. Release from Deep Power-down (RDP), Read Electronic Signature (RES)  
The Release from Deep Power-down (RDP) instruction is terminated by driving Chip Select (CS#) High. When Chip  
Select (CS#) is driven High, the device is put in the Stand-by Power mode. If the device was not previously in the  
Deep Power-down mode, the transition to the Stand-by Power mode is immediate. If the device was previously  
in the Deep Power-down mode, the transition to the Stand-by Power mode is delayed by tRES2, and Chip Select  
(CS#) must remain High for at least tRES2(max), as specified in "Table 19. AC Characteristics". Once in the Stand-  
by Power mode, the device waits to be selected, so that it can receive, decode and execute instructions. The RDP  
instruction is only for releasing from Deep Power Down Mode. Reset# pin goes low will release the Flash from deep  
power down mode.  
RES instruction is for reading out the old style of 8-bit Electronic Signature, whose values are shown as "Table 6.  
ID Definitions". This is not the same as RDID instruction. It is not recommended to use for new design. For new de-  
sign, please use RDID instruction.  
Even in Deep power-down mode, the RDP and RES are also allowed to be executed, only except the device is in  
progress of program/erase/write cycle; there's no effect on the current program/erase/write cycle in progress.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The RES instruction is ended by CS# goes high after the ID been read out at least once. The ID outputs repeat-  
edly if continuously send the additional clock cycles on SCLK while CS# is at low. If the device was not previously  
in Deep Power-down mode, the device transition to standby mode is immediate. If the device was previously in  
Deep Power-down mode, there's a delay of tRES2 to transit to standby mode, and CS# must remain to high at least  
tRES2(max). Once in the standby mode, the device waits to be selected, so it can be receive, decode, and execute  
instruction.  
Figure 11. Read Electronic Signature (RES) Sequence (SPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
10  
28 29 30 31 32 33 34 35 36 37 38  
SCLK  
Command  
ABh  
t
3 Dummy Bytes  
RES2  
SI  
23 22 21  
MSB  
3
2
1
0
Electronic Signature Out  
High-Z  
7
6
5
4
3
2
0
1
SO  
MSB  
Deep Power-down Mode  
Stand-by Mode  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
24  
 
MX25U1635F  
Figure 12. Read Electronic Signature (RES) Sequence (QPI Mode)  
CS#  
MODE 3  
0
1
2
3
4
5
6
7
SCLK  
MODE 0  
3 Dummy Bytes  
Command  
ABh  
SIO[3:0]  
X
X
X
X
X
X
H0 L0  
MSB LSB  
Data Out  
Data In  
Stand-by Mode  
Deep Power-down Mode  
Figure 13. Release from Deep Power-down (RDP) Sequence (SPI Mode)  
CS#  
t
RES1  
0
1
2
3
4
5
6
7
Mode 3  
Mode 0  
SCLK  
SI  
Command  
ABh  
High-Z  
SO  
Deep Power-down Mode  
Stand-by Mode  
Figure 14. Release from Deep Power-down (RDP) Sequence (QPI Mode)  
CS#  
t
RES1  
Mode 3  
Mode 0  
0
1
SCLK  
Command  
SIO[3:0]  
ABh  
Deep Power-down Mode  
Stand-by Mode  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
25  
 
MX25U1635F  
9-5. Read Electronic Manufacturer ID & Device ID (REMS)  
The REMS instruction is an alternative to the Release from Power-down/Device ID instruction that provides both the  
JEDEC assigned manufacturer ID and the specific device ID.  
The REMS instruction is very similar to the Release from Power-down/Device ID instruction. The instruction is initi-  
ated by driving the CS# pin low and shift the instruction code "90h" followed by two dummy bytes and one bytes ad-  
dress (A7~A0). After which, the Manufacturer ID for Macronix (C2h) and the Device ID are shifted out on the falling  
edge of SCLK with most significant bit (MSB) first. The Device ID values are listed in "Table 6. ID Definitions". If the  
one-byte address is initially set to 01h, then the device ID will be read first and then followed by the Manufacturer  
ID. The Manufacturer and Device IDs can be read continuously, alternating from one to the other. The instruction is  
completed by driving CS# high.  
Figure 15. Read Electronic Manufacturer & Device ID (REMS) Sequence (SPI Mode only)  
CS#  
0
1
2
3
4
5
6
7
8
9 10  
Mode 3  
Mode 0  
SCLK  
Command  
90h  
2 Dummy Bytes  
SI  
15 14 13  
3
2
1
0
High-Z  
SO  
CS#  
47  
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46  
SCLK  
ADD (1)  
7
6
5
4
3
2
0
1
SI  
Manufacturer ID  
Device ID  
7
6
5
4
3
2
1
0
7
7
6
5
4
3
2
0
1
SO  
MSB  
MSB  
MSB  
Notes:  
(1) ADD=00H will output the manufacturer's ID first and ADD=01H will output device ID first.  
(2) Instruction is either 90(hex).  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
26  
 
MX25U1635F  
9-6. QPI ID Read (QPIID)  
User can execute this QPIID Read instruction to identify the Device ID and Manufacturer ID. The sequence of  
issue QPIID instruction is CS# goes low→sending QPI ID instruction→→Data out on SO→CS# goes high. Most  
significant bit (MSB) first.  
After the command cycle, the device will immediately output data on the falling edge of SCLK. The manufacturer ID,  
memory type, and device ID data byte will be output continuously, until the CS# goes high.  
Table 6. ID Definitions  
Command Type Command  
MX25U1635F  
Manufactory ID  
C2  
Memory type  
Memory density  
35  
RDID / QPIID  
RES  
9Fh / AFh  
ABh  
25  
Electronic ID  
35  
Manufactory ID  
C2  
Device ID  
35  
REMS  
90h  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
27  
 
MX25U1635F  
9-7. Read Status Register (RDSR)  
The RDSR instruction is for reading Status Register Bits. The Read Status Register can be read at any time (even  
in program/erase/write status register condition). It is recommended to check the Write in Progress (WIP) bit before  
sending a new instruction when a program, erase, or write status register operation is in progress.  
The sequence of issuing RDSR instruction is: CS# goes low→ sending RDSR instruction code→ Status Register data  
out on SO.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
Figure 16. Read Status Register (RDSR) Sequence (SPI Mode)  
CS#  
0
1
2
3
4
5
6
7
8
9 10 11 12 13 14 15  
Mode 3  
Mode 0  
SCLK  
SI  
command  
05h  
Status Register Out  
Status Register Out  
High-Z  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7
MSB  
MSB  
Figure 17. Read Status Register (RDSR) Sequence (QPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
N
SCLK  
SIO[3:0]  
05h  
H0 L0 H0 L0 H0 L0  
H0 L0  
MSB  
LSB  
Status Byte Status Byte Status Byte  
Status Byte  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
28  
 
MX25U1635F  
For user to check if Program/Erase operation is finished or not, RDSR instruction flow are shown as follows:  
Figure 18. Program/Erase flow with read array data  
start  
WREN command  
RDSR command*  
No  
WEL=1?  
Yes  
Program/erase command  
Write program data/address  
(Write erase address)  
RDSR command  
No  
WIP=0?  
Yes  
RDSR command  
Read WEL=0, BP[3:0], QE,  
and SRWD data  
Read array data  
(same address of PGM/ERS)  
No  
Verify OK?  
Yes  
Program/erase successfully  
Program/erase fail  
Yes  
Program/erase  
another block?  
* Issue RDSR to check BP[3:0].  
* If WPSEL = 1, issue RDBLOCK to check the block status.  
No  
Program/erase completed  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
29  
 
MX25U1635F  
Figure 19. Program/Erase flow without read array data (read P_FAIL/E_FAIL flag)  
start  
WREN command  
RDSR command*  
No  
WEL=1?  
Yes  
Program/erase command  
Write program data/address  
(Write erase address)  
RDSR command  
No  
WIP=0?  
Yes  
RDSR command  
Read WEL=0, BP[3:0], QE,  
and SRWD data  
RDSCUR command  
P_FAIL/E_FAIL =1 ?  
Yes  
No  
Program/erase successfully  
Program/erase fail  
Yes  
Program/erase  
another block?  
* Issue RDSR to check BP[3:0].  
* If WPSEL = 1, issue RDBLOCK to check the block status.  
No  
Program/erase completed  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
30  
 
MX25U1635F  
Status Register  
The definition of the status register bits is as below:  
WIP bit. The Write in Progress (WIP) bit, a volatile bit, indicates whether the device is busy in program/erase/write sta-  
tus register progress. When WIP bit sets to 1, which means the device is busy in program/erase/write status register  
progress. When WIP bit sets to 0, which means the device is not in progress of program/erase/write status register  
cycle.  
WEL bit. The Write Enable Latch (WEL) bit, a volatile bit, indicates whether the device is set to internal write enable  
latch. When WEL bit sets to 1, which means the internal write enable latch is set, the device can accept program/  
erase/write status register instruction. When WEL bit sets to 0, which means no internal write enable latch; the device  
will not accept program/erase/write status register instruction. The program/erase command will be ignored if it is ap-  
plied to a protected memory area. To ensure both WIP bit & WEL bit are both set to 0 and available for next program/  
erase/operations, WIP bit needs to be confirm to be 0 before polling WEL bit. After WIP bit confirmed, WEL bit needs  
to be confirmed as 0.  
BP3, BP2, BP1, BP0 bits. The Block Protect (BP3, BP2, BP1, BP0) bits, non-volatile bits, indicate the protected area (as  
defined in "Table 2. Protected Area Sizes") of the device to against the program/erase instruction without hardware  
protection mode being set. To write the Block Protect (BP3, BP2, BP1, BP0) bits requires the Write Status Register (WRSR)  
instruction to be executed. Those bits define the protected area of the memory to against Page Program (PP), Sector  
Erase (SE), Block Erase 32KB (BE32K), Block Erase (BE) and Chip Erase (CE) instructions (only if Block Protect bits  
(BP3:BP0) set to 0, the CE instruction can be executed). The BP3, BP2, BP1, BP0 bits are "0" as default, which is un-  
protected.  
QE bit. The Quad Enable (QE) bit, non-volatile bit, while it is "0" (factory default), it performs non-Quad and WP#,  
RESET# are enable. While QE is "1", it performs Quad I/O mode and WP#, RESET# are disabled. In the other  
word, if the system goes into four I/O mode (QE=1), the feature of HPM and RESET will be disabled.  
SRWD bit. The Status Register Write Disable (SRWD) bit, non-volatile bit, is operated together with Write Protection  
(WP#/SIO2) pin for providing hardware protection mode. The hardware protection mode requires SRWD sets to 1 and  
WP#/SIO2 pin signal is low stage. In the hardware protection mode, the Write Status Register (WRSR) instruction is  
no longer accepted for execution and the SRWD bit and Block Protect bits (BP3, BP2, BP1, BP0) are read only. The  
SRWD bit defaults to be "0".  
Status Register  
bit7  
bit6  
bit5  
BP3  
(level of  
protected  
block)  
bit4  
BP2  
(level of  
protected  
block)  
bit3  
BP1  
(level of  
protected  
block)  
bit2  
BP0  
(level of  
protected  
block)  
bit1  
bit0  
SRWD (status  
register write  
protect)  
QE  
(Quad  
Enable)  
WEL  
(write enable  
latch)  
WIP  
(write in  
progress bit)  
1=Quad  
Enable  
0=not Quad  
Enable  
1=write  
enable  
0=not write 0=not in write  
1=write  
operation  
1=status  
register write  
disable  
(note 1)  
(note 1)  
(note 1)  
(note 1)  
enable  
operation  
Non-volatile Non-volatile Non-volatile Non-volatile Non-volatile Non-volatile  
bit bit bit bit bit bit  
volatile bit  
volatile bit  
Note 1: see the "Table 2. Protected Area Sizes".  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
31  
MX25U1635F  
9-8. Write Status Register (WRSR)  
The WRSR instruction is for changing the values of Status Register Bits. Before sending WRSR instruction, the  
Write Enable (WREN) instruction must be decoded and executed to set the Write Enable Latch (WEL) bit in ad-  
vance. The WRSR instruction can change the value of Block Protect (BP3, BP2, BP1, BP0) bits to define the pro-  
tected area of memory (as shown in "Table 2. Protected Area Sizes"). The WRSR also can set or reset the Quad  
enable (QE) bit and set or reset the Status Register Write Disable (SRWD) bit in accordance with Write Protection (WP#/  
SIO2) pin signal, but has no effect on bit1(WEL) and bit0 (WIP) of the status register. The WRSR instruction cannot  
be executed once the Hardware Protected Mode (HPM) is entered.  
The sequence of issuing WRSR instruction is: CS# goes low→ sending WRSR instruction code→ Status Register  
data on SI→CS# goes high.  
The CS# must go high exactly at the 8 bites or 16 bits data boundary; otherwise, the instruction will be rejected and  
not executed. The self-timed Write Status Register cycle time (tW) is initiated as soon as Chip Select (CS#) goes  
high. The Write in Progress (WIP) bit still can be checked during the Write Status Register cycle is in progress. The  
WIP sets 1 during the tW timing, and sets 0 when Write Status Register Cycle is completed, and the Write Enable  
Latch (WEL) bit is reset.  
Figure 20. Write Status Register (WRSR) Sequence (SPI Mode)  
CS#  
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15  
Mode 3  
Mode 0  
SCLK  
command  
01h  
Status  
Register In  
SI  
4
2
1
0
7
6
5
3
MSB  
High-Z  
SO  
Note : The CS# must go high exactly at 8 bits or 16 bits data boundary to completed the write register command.  
Figure 21. Write Status Register (WRSR) Sequence (QPI Mode)  
CS#  
Mode 3  
Mode 0  
Mode 3  
Mode 0  
0
1
2
3
SCLK  
SR in  
Command  
01h  
H0 L0  
SIO[3:0]  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
32  
 
MX25U1635F  
Software Protected Mode (SPM):  
-
When SRWD bit=0, no matter WP#/SIO2 is low or high, the WREN instruction may set the WEL bit and can  
change the values of SRWD, BP3, BP2, BP1, BP0. The protected area, which is defined by BP3, BP2, BP1,  
BP0, is at software protected mode (SPM).  
-
When SRWD bit=1 and WP#/SIO2 is high, the WREN instruction may set the WEL bit can change the values of  
SRWD, BP3, BP2, BP1, BP0. The protected area, which is defined by BP3, BP2, BP1, BP0, is at software pro-  
tected mode (SPM)  
Note:  
If SRWD bit=1 but WP#/SIO2 is low, it is impossible to write the Status Register even if the WEL bit has previously  
been set. It is rejected to write the Status Register and not be executed.  
Hardware Protected Mode (HPM):  
-
When SRWD bit=1, and then WP#/SIO2 is low (or WP#/SIO2 is low before SRWD bit=1), it enters the hardware  
protected mode (HPM). The data of the protected area is protected by software protected mode by BP3, BP2,  
BP1, BP0 and hardware protected mode by the WP#/SIO2 to against data modification.  
Note:  
To exit the hardware protected mode requires WP#/SIO2 driving high once the hardware protected mode is entered.  
If the WP#/SIO2 pin is permanently connected to high, the hardware protected mode can never be entered; only can  
use software protected mode via BP3, BP2, BP1, BP0.  
If the system enter QPI or set QE=1, the feature of HPM will be disabled.  
Table 7. Protection Modes  
Mode  
Status register condition  
WP# and SRWD bit status  
Memory  
Status register can be written  
in (WEL bit is set to "1") and  
the SRWD, BP0-BP3  
Software protection  
mode (SPM)  
WP#=1 and SRWD bit=0, or  
WP#=0 and SRWD bit=0, or  
WP#=1 and SRWD=1  
The protected area  
cannot  
be program or erase.  
bits can be changed  
The SRWD, BP0-BP3 of  
status register bits cannot be  
changed  
The protected area  
cannot  
be program or erase.  
Hardware protection  
mode (HPM)  
WP#=0, SRWD bit=1  
Note:  
1. As defined by the values in the Block Protect (BP3, BP2, BP1, BP0) bits of the Status Register, as shown in  
"Table 2. Protected Area Sizes".  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
33  
MX25U1635F  
Figure 22. WRSR flow  
start  
WREN command  
RDSR command  
No  
WEL=1?  
Yes  
WRSR command  
Write status register  
data  
RDSR command  
No  
WIP=0?  
Yes  
RDSR command  
Read WEL=0, BP[3:0], QE,  
and SRWD data  
No  
Verify OK?  
Yes  
WRSR successfully  
WRSR fail  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
34  
 
MX25U1635F  
Figure 23. WP# Setup Timing and Hold Timing during WRSR when SRWD=1  
WP#  
CS#  
tSHWL  
tWHSL  
0
1
2
3
4
5
6
7
8
9
10 11 12  
13 14  
15  
SCLK  
01h  
SI  
High-Z  
SO  
Note: WP# must be kept high until the embedded operation finish.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
35  
 
MX25U1635F  
9-9. Read Data Bytes (READ)  
The read instruction is for reading data out. The address is latched on rising edge of SCLK, and data shifts out on  
the falling edge of SCLK at a maximum frequency fR. The first address byte can be at any location. The address  
is automatically increased to the next higher address after each byte data is shifted out, so the whole memory can  
be read out at a single READ instruction. The address counter rolls over to 0 when the highest address has been  
reached.  
The sequence of issuing READ instruction is: CS# goes low→sending READ instruction code→ 3-byte address on  
SI→ data out on SO→to end READ operation can use CS# to high at any time during data out.  
Figure 24. Read Data Bytes (READ) Sequence (SPI Mode only)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
10  
28 29 30 31 32 33 34 35 36 37 38 39  
SCLK  
command  
03h  
24-Bit Address  
23 22 21  
MSB  
3
2
1
0
SI  
Data Out 1  
Data Out 2  
High-Z  
2
7
6
5
4
3
1
7
0
SO  
MSB  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
36  
 
MX25U1635F  
9-10. Read Data Bytes at Higher Speed (FAST_READ)  
The FAST_READ instruction is for quickly reading data out. The address is latched on rising edge of SCLK, and  
data of each bit shifts out on the falling edge of SCLK at a maximum frequency fC. The first address byte can be at  
any location. The address is automatically increased to the next higher address after each byte data is shifted out,  
so the whole memory can be read out at a single FAST_READ instruction. The address counter rolls over to 0 when  
the highest address has been reached.  
Read on SPI Mode The sequence of issuing FAST_READ instruction is: CS# goes low→ sending FAST_READ  
instruction code→ 3-byte address on SI→1-dummy byte (default) address on SI→ data out on SO→ to end FAST_  
READ operation can use CS# to high at any time during data out.  
Read on QPI Mode The sequence of issuing FAST_READ instruction in QPI mode is: CS# goes low→ sending  
FAST_READ instruction, 2 cycles→ 24-bit address interleave on SIO3, SIO2, SIO1 & SIO0→4 dummy cycles→data  
out interleave on SIO3, SIO2, SIO1 & SIO0→ to end QPI FAST_READ operation can use CS# to high at any time  
during data out.  
While Program/Erase/Write Status Register cycle is in progress, FAST_READ instruction is rejected without any im-  
pact on the Program/Erase/Write Status Register current cycle.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
37  
MX25U1635F  
Figure 25. Read at Higher Speed (FAST_READ) Sequence (SPI Mode)  
CS#  
0
1
2
3
4
5
6
7
8
9
10  
28 29 30 31  
Mode 3  
Mode 0  
SCLK  
Command  
0Bh  
24-Bit Address  
SI  
23 22 21  
3
2
1
0
High-Z  
SO  
CS#  
47  
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46  
SCLK  
Dummy Cycle  
7
6
5
4
3
2
0
1
SI  
DATA OUT 2  
DATA OUT 1  
7
6
5
4
3
2
1
0
7
7
6
5
4
3
2
0
1
SO  
MSB  
MSB  
MSB  
Figure 26. Read at Higher Speed (FAST_READ) Sequence (QPI Mode)  
CS#  
0
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
Mode 3  
Mode 0  
SCLK  
Command  
0Bh  
SIO(3:0)  
X
X
H0 L0 H1 L1  
MSB LSB MSB LSB  
A5 A4 A3 A2 A1 A0  
24-Bit Address  
X
X
Data In  
Data Out 1 Data Out 2  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
38  
 
MX25U1635F  
9-11. Dual Read Mode (DREAD)  
The DREAD instruction enable double throughput of Serial Flash in read mode. The address is latched on rising  
edge of SCLK, and data of every two bits (interleave on 2 I/O pins) shift out on the falling edge of SCLK at a maxi-  
mum frequency fT. The first address byte can be at any location. The address is automatically increased to the next  
higher address after each byte data is shifted out, so the whole memory can be read out at a single DREAD instruc-  
tion. The address counter rolls over to 0 when the highest address has been reached. Once writing DREAD instruc-  
tion, the following data out will perform as 2-bit instead of previous 1-bit.  
The sequence of issuing DREAD instruction is: CS# goes low  
sending DREAD instruction  
3-byte address on  
SI  
8-bit dummy cycle  
data out interleave on SO1 & SO0  
to end DREAD operation can use CS# to high at  
any time during data out.  
While Program/Erase/Write Status Register cycle is in progress, DREAD instruction is rejected without any impact  
on the Program/Erase/Write Status Register current cycle.  
Figure 27. Dual Read Mode Sequence (Command 3B)  
CS#  
30 31 32  
39 40 41 42 43 44 45  
0
1
2
3
4
5
6
7
8
9
SCLK  
Data Out  
Data Out  
1
8 dummy  
cycle  
Command  
24 ADD Cycle  
2
D4 D2  
D6 D4  
D7 D5  
A23 A22  
A1 A0  
3B  
D6  
D7  
D0  
SI/SIO0  
High Impedance  
D1  
D5 D3  
SO/SIO1  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
39  
 
MX25U1635F  
9-12. 2 x I/O Read Mode (2READ)  
The 2READ instruction enable double throughput of Serial Flash in read mode. The address is latched on rising  
edge of SCLK, and data of every two bits (interleave on 2 I/O pins) shift out on the falling edge of SCLK at a maxi-  
mum frequency fT. The first address byte can be at any location. The address is automatically increased to the next  
higher address after each byte data is shifted out, so the whole memory can be read out at a single 2READ instruc-  
tion. The address counter rolls over to 0 when the highest address has been reached. Once writing 2READ instruc-  
tion, the following address/dummy/data out will perform as 2-bit instead of previous 1-bit.  
The sequence of issuing 2READ instruction is: CS# goes low sending 2READ instruction 24-bit address inter-  
leave on SIO1 & SIO0 4 dummy cycles on SIO1 & SIO0 data out interleave on SIO1 & SIO0 to end 2READ  
operation can use CS# to high at any time during data out.  
While Program/Erase/Write Status Register cycle is in progress, 2READ instruction is rejected without any impact  
on the Program/Erase/Write Status Register current cycle.  
Figure 28. 2 x I/O Read Mode Sequence (SPI Mode only)  
CS#  
Mode 3  
Mode 0  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
10  
17 18 19 20 21 22 23 24 25 26 27 28 29 30  
SCLK  
Data  
Data  
4 Dummy  
cycle  
12 ADD Cycles  
Command  
Out 1  
Out 2  
D6 D4 D2 D0 D6 D4 D2 D0  
A22 A20 A18  
A23 A21 A19  
A4 A2 A0  
BBh  
SI/SIO0  
D7 D5 D3 D1 D7 D5 D3 D1  
A5 A3 A1  
SO/SIO1  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
40  
 
MX25U1635F  
9-13. Quad Read Mode (QREAD)  
The QREAD instruction enable quad throughput of Serial Flash in read mode. The address is latched on rising  
edge of SCLK, and data of every four bits (interleave on 4 I/O pins) shift out on the falling edge of SCLK at a  
maximum frequency fQ. The first address byte can be at any location. The address is automatically increased  
to the next higher address after each byte data is shifted out, so the whole memory can be read out at a single  
QREAD instruction. The address counter rolls over to 0 when the highest address has been reached. Once writ-  
ing QREAD instruction, the following data out will perform as 4-bit instead of previous 1-bit.  
The sequence of issuing QREAD instruction is: CS# goes low  
sending QREAD instruction → 3-byte address  
on SI  
8-bit dummy cycle  
data out interleave on SO3, SO2, SO1 & SO0  
to end QREAD operation can  
use CS# to high at any time during data out.  
While Program/Erase/Write Status Register cycle is in progress, QREAD instruction is rejected without any im-  
pact on the Program/Erase/Write Status Register current cycle.  
Figure 29. Quad Read Mode Sequence (Command 6B)  
CS#  
29 30 31 32 33  
38 39 40 41 42  
0
1
2
3
4
5
6
7
8
9
SCLK  
Data  
Out 2  
Data  
Out 3  
Command  
6B  
8 dummy cycles  
24 ADD Cycles  
Data  
Out 1  
A23A22  
A2 A1 A0  
D4 D0 D4 D0 D4  
SI/SO0  
SO/SO1  
SO2  
High Impedance  
High Impedance  
High Impedance  
D5 D1 D5 D1 D5  
D6 D2 D6 D2 D6  
SO3  
D7 D3 D7 D3 D7  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
41  
 
MX25U1635F  
9-14. 4 x I/O Read Mode (4READ)  
The 4READ instruction enable quad throughput of Serial Flash in read mode. A Quad Enable (QE) bit of status Reg-  
ister must be set to "1" before sending the 4READ instruction. The address is latched on rising edge of SCLK, and  
data of every four bits (interleave on 4 I/O pins) shift out on the falling edge of SCLK at a maximum frequency fQ.  
The first address byte can be at any location. The address is automatically increased to the next higher address af-  
ter each byte data is shifted out, so the whole memory can be read out at a single 4READ instruction. The address  
counter rolls over to 0 when the highest address has been reached. Once writing 4READ instruction, the following  
address/dummy/data out will perform as 4-bit instead of previous 1-bit.  
4 x I/O Read on SPI Mode (4READ) The sequence of issuing 4READ instruction is: CS# goes low sending  
4READ instruction 24-bit address interleave on SIO3, SIO2, SIO1 & SIO0 2+4 dummy cycles data out inter-  
leave on SIO3, SIO2, SIO1 & SIO0 to end 4READ operation can use CS# to high at any time during data out.  
4 x I/O Read on QPI Mode (4READ) The 4READ instruction also support on QPI command mode. The sequence of  
issuing 4READ instruction QPI mode is: CS# goes low sending 4READ instruction 24-bit address interleave on  
SIO3, SIO2, SIO1 & SIO0 2+4 dummy cycles data out interleave on SIO3, SIO2, SIO1 & SIO0 to end 4READ  
operation can use CS# to high at any time during data out.  
Another sequence of issuing 4 READ instruction especially useful in random access is : CS# goes low sending  
4 READ instruction 3-bytes address interleave on SIO3, SIO2, SIO1 & SIO0 performance enhance toggling bit  
P[7:0] 4 dummy cycles data out still CS# goes high  
CS# goes low (reduce 4 Read instruction) 24-bit ran-  
dom access address.  
In the performance-enhancing mode, P[7:4] must be toggling with P[3:0] ; likewise P[7:0]=A5h, 5Ah, F0h or 0Fh can  
make this mode continue and reduce the next 4READ instruction. Once P[7:4] is no longer toggling with P[3:0]; like-  
wise P[7:0]=FFh,00h,AAh or 55h and afterwards CS# is raised and then lowered, the system then will escape from  
performance enhance mode and return to normal operation.  
While Program/Erase/Write Status Register cycle is in progress, 4READ instruction is rejected without any impact  
on the Program/Erase/Write Status Register current cycle.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
42  
MX25U1635F  
Figure 30. 4 x I/O Read Mode Sequence (SPI Mode)  
CS#  
23 24  
10 11 12 13 14 15 16 17 18 19 20 21 22  
Mode 3  
Mode 0  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
SCLK  
Data  
Out 1  
Data  
Out 2 Out 3  
Data  
4 Dummy  
Cycles  
Command  
EBh  
6 ADD Cycles  
Performance  
enhance  
indicator (Note)  
A20 A16 A12 A8 A4 A0  
D4 D0 D4 D0 D4 D0  
P4 P0  
SIO0  
SIO1  
SIO2  
SIO3  
A21 A17 A13 A9 A5 A1  
A22 A18 A14 A10 A6 A2  
D5 D1 D5 D1 D5 D1  
D6 D2 D6 D2 D6 D2  
P5 P1  
P6 P2  
A23 A19 A15 A11 A7 A3  
D7 D3 D7 D3 D7 D3  
P7 P3  
Note:  
1. Hi-impedance is inhibited for the two clock cycles.  
2. P7≠P3, P6≠P2, P5≠P1 & P4≠P0 (Toggling) is inhibited.  
Figure 31. 4 x I/O Read Mode Sequence (QPI Mode)  
CS#  
0
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
18  
19  
20  
MODE 3  
MODE 0  
MODE 3  
MODE 0  
SCLK  
EB  
SIO[3:0]  
H0 L0 H1 L1 H2 L2 H3 L3  
A5 A4 A3 A2 A1 A0  
24-bit Address  
X
X
X
X
X
X
MSB  
Data Out  
Data In  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
43  
 
MX25U1635F  
Figure 32. W4READ (Quad Read with 4 dummy cycles) Sequence  
CS#  
Mode 3  
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19 20 21 22 23  
SCLK  
Mode  
4 Dummy  
Cycles  
Data Data Data  
Out 1 Out 2 Out 3  
Command  
E7h  
6 ADD Cycles  
D4 D0 D4 D0 D4 D0  
D4  
A20 A16 A12 A8 A4 A0  
SIO0  
SIO1  
SIO2  
D5 D1 D5 D1 D5 D1  
D6 D2 D6 D2 D6 D2  
D5  
D6  
A21 A17 A13 A9 A5 A1  
A22 A18 A14 A10 A6 A2  
A23 A19 A15 A11 A7 A3  
D7 D3 D7 D3 D7 D3  
D7  
SIO3  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
44  
 
MX25U1635F  
9-15. Burst Read  
This device supports Burst Read in both SPI and QPI mode.  
To set the Burst length, following command operation is required  
Issuing command: “C0h” in the first Byte (8-clocks), following 4 clocks defining wrap around enable with “0h” and  
disable with“1h”.  
Next 4 clocks is to define wrap around depth. Definition as following table:  
Data  
00h  
01h  
02h  
03h  
1xh  
Wrap Around  
Wrap Depth  
8-byte  
Yes  
Yes  
Yes  
Yes  
No  
16-byte  
32-byte  
64-byte  
X
The wrap around unit is defined within the 256Byte page, with random initial address. It’s defined as “wrap-around  
mode disable” for the default state of the device. To exit wrap around, it is required to issue another “C0h” command  
in which data=‘1xh”. Otherwise, wrap around status will be retained until power down or reset command. To change  
wrap around depth, it is requried to issue another “C0h” command in which data=“0xh”. QPI “0Bh” “EBh” and SPI “EBh”  
“E7h” support wrap around feature after wrap around enable. Burst read is supported in both SPI and QPI mode.  
The device id default without Burst read.  
Figure 33. SPI Mode  
CS#  
0
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
Mode 3  
Mode 0  
SCLK  
SIO  
D7  
D6  
D5  
D4  
D3  
D2  
D1  
D0  
C0h  
Figure 34. QPI Mode  
CS#  
0
1
2
3
Mode 3  
Mode 0  
SCLK  
C0h  
H0  
L0  
SIO[3:0]  
MSB LSB  
Note: MSB=Most Significant Bit  
LSB=Least Significant Bit  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
45  
 
MX25U1635F  
9-16. Performance Enhance Mode  
The device could waive the command cycle bits if the two cycle bits after address cycle toggles.  
Performance enhance mode is supported in both SPI and QPI mode.  
In QPI mode, “EBh” “0Bh” and SPI “EBh” “E7h” commands support enhance mode. The performance enhance  
mode is not supported in dual I/O mode.  
After entering enhance mode, following CS# go high, the device will stay in the read mode and treat CS# go low of  
the first clock as address instead of command cycle.  
To exit enhance mode, a new fast read command whose first two dummy cycles is not toggle then exit. Or issue  
”FFh” data cycle to exit enhance mode.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
46  
MX25U1635F  
Figure 35. 4 x I/O Read enhance performance Mode Sequence (SPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19 20 21 22  
n
SCLK  
Data  
Out 1  
Data  
Out 2  
Data  
Out n  
4 Dummy  
Cycles  
Command  
EBh  
6 ADD Cycles  
Performance  
enhance  
indicator (Note)  
P4 P0  
D4 D0 D4 D0  
D4 D0  
A20 A16 A12 A8 A4 A0  
SIO0  
SIO1  
SIO2  
SIO3  
A21 A17 A13 A9 A5 A1  
A22 A18 A14 A10 A6 A2  
D5 D1 D5 D1  
D6 D2 D6 D2  
D5 D1  
D6 D2  
P5 P1  
P6 P2  
A23 A19 A15 A11 A7 A3  
D7 D3 D7 D3  
D7 D3  
P7 P3  
CS#  
n+1  
...........  
n+7......n+9 ........... n+13  
...........  
Mode 3  
Mode 0  
SCLK  
4 Dummy  
Cycles  
Data  
Out 1  
Data  
Out 2  
Data  
Out n  
6 ADD Cycles  
Performance  
enhance  
indicator (Note)  
D4 D0 D4 D0  
D4 D0  
P4 P0  
A20 A16 A12 A8 A4 A0  
SIO0  
SIO1  
SIO2  
SIO3  
D5 D1 D5 D1  
D6 D2 D6 D2  
D5 D1  
D6 D2  
A21 A17 A13 A9 A5 A1  
A22 A18 A14 A10 A6 A2  
P5 P1  
P6 P2  
D7 D3 D7 D3  
D7 D3  
A23 A19 A15 A11 A7 A3  
P7 P3  
Note:  
1. Performance enhance mode, if P7≠P3 & P6≠P2 & P5≠P1 & P4≠P0 (Toggling), ex: A5, 5A, 0F, if not using  
performance enhance recommend to keep 1 or 0 in performance enhance indicator.  
2. Reset the performance enhance mode, if P7=P3 or P6=P2 or P5=P1 or P4=P0, ex: AA, 00, FF  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
47  
 
MX25U1635F  
Figure 36. 4 x I/O Read enhance performance Mode Sequence (QPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
10  
11  
12  
13  
14  
15  
16  
17  
SCLK  
EBh  
SIO[3:0]  
X
X
X
X
H0 L0 H1 L1  
MSB LSB MSB LSB  
A5 A4 A3 A2 A1 A0  
P(7:4)P(3:0)  
Data In  
4 dummy  
cycles  
Data Out  
performance  
enhance  
indicator  
CS#  
SCLK  
n+1 .............  
Mode 0  
SIO[3:0]  
X
X
X
X
H0 L0 H1 L1  
MSB LSB MSB LSB  
A5 A4 A3 A2 A1 A0  
P(7:4)P(3:0)  
4 dummy  
cycles  
Data Out  
6 Address cycles  
performance  
enhance  
indicator  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
48  
 
MX25U1635F  
9-17. Performance Enhance Mode Reset  
To conduct the Performance Enhance Mode Reset operation in SPI mode, FFh command code, 8 clocks, should be  
issued in 1I/O sequence. In QPI Mode, FFFFFFFFh command code, 8 clocks, in 4I/O should be issued.  
If the system controller is being Reset during operation, the flash device will return to the standard SPI operation.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
Figure 37. Performance Enhance Mode Reset for Fast Read Quad I/O (SPI Mode)  
Mode Bit Reset  
for Quad I/O  
CS#  
Mode 3  
Mode 3  
1
2
3
4
5
6
7
SCLK  
Mode  
Mode 0  
FFh  
SIO0  
SIO1  
SIO2  
Don’t Care  
Don’t Care  
Don’t Care  
SIO3  
Figure 38. Performance Enhance Mode Reset for Fast Read Quad I/O (QPI Mode)  
Mode Bit Reset  
for Quad I/O  
CS#  
Mode 3  
Mode 3  
1
2
3
4
5
6
7
SCLK  
Mode  
Mode 0  
FFFFFFFFh  
SIO[3:0]  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
49  
 
MX25U1635F  
9-18. Sector Erase (SE)  
The Sector Erase (SE) instruction is for erasing the data of the chosen sector to be "1". The instruction is used for  
any 4K-byte sector. A Write Enable (WREN) instruction must execute to set the Write Enable Latch (WEL) bit before  
sending the Sector Erase (SE). Any address of the sector (see "Table 4. Memory Organization") is a valid address  
for Sector Erase (SE) instruction. The CS# must go high exactly at the byte boundary (the latest eighth of address  
byte been latched-in); otherwise, the instruction will be rejected and not executed.  
Address bits [Am-A12] (Am is the most significant address) select the sector address.  
The sequence of issuing SE instruction is: CS# goes low→ sending SE instruction code→ 3-byte address on SI→  
CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The self-timed Sector Erase Cycle time (tSE) is initiated as soon as Chip Select (CS#) goes high. The Write in  
Progress (WIP) bit still can be checked during the Sector Erase cycle is in progress. The WIP sets 1 during the  
tSE timing, and sets 0 when Sector Erase Cycle is completed, and the Write Enable Latch (WEL) bit is reset. If  
the sector is protected by BP3, BP2, BP1, BP0 bits, the Sector Erase (SE) instruction will not be executed on the  
sector.  
Figure 39. Sector Erase (SE) Sequence (SPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
29 30 31  
SCLK  
24-Bit Address  
Command  
20h  
SI  
23 22  
2
1
0
MSB  
Figure 40. Sector Erase (SE) Sequence (QPI Mode)  
CS#  
Mode 3  
0
1
2
3
4
5
6
7
SCLK  
Mode 0  
24-Bit Address  
Command  
SIO[3:0]  
20h A5 A4 A3 A2 A1 A0  
MSB LSB  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
50  
 
MX25U1635F  
9-19. Block Erase (BE32K)  
The Block Erase (BE32K) instruction is for erasing the data of the chosen block to be "1". The instruction is used  
for 32K-byte block erase operation. A Write Enable (WREN) instruction must execute to set the Write Enable Latch  
(WEL) bit before sending the Block Erase (BE32K). Any address of the block (see "Table 4. Memory Organization")  
is a valid address for Block Erase (BE32K) instruction. The CS# must go high exactly at the byte boundary (the lat-  
est eighth of address byte been latched-in); otherwise, the instruction will be rejected and not executed.  
The sequence of issuing BE32K instruction is: CS# goes low→ sending BE32K instruction code→ 3-byte address  
on SI→CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The self-timed Block Erase Cycle time (tBE32K) is initiated as soon as Chip Select (CS#) goes high. The Write  
in Progress (WIP) bit still can be checked during the Block Erase cycle is in progress. The WIP sets 1 during the  
tBE32K timing, and sets 0 when Block Erase Cycle is completed, and the Write Enable Latch (WEL) bit is reset. If  
the block is protected by BP3, BP2, BP1, BP0 bits, the Block Erase (BE32K) instruction will not be executed on the  
block.  
Figure 41. Block Erase 32KB (BE32K) Sequence (SPI Mode)  
CS#  
0
1
2
3
4
5
6
7
8
9
29 30 31  
Mode 3  
Mode 0  
SCLK  
Command  
52h  
24-Bit Address  
SI  
23 22  
MSB  
2
0
1
Figure 42. Block Erase 32KB (BE32K) Sequence (QPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
SCLK  
24-Bit Address  
Command  
SIO[3:0]  
52h A5 A4 A3 A2 A1 A0  
MSB  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
51  
 
MX25U1635F  
9-20. Block Erase (BE)  
The Block Erase (BE) instruction is for erasing the data of the chosen block to be "1". The instruction is used for  
64K-byte block erase operation. A Write Enable (WREN) instruction must execute to set the Write Enable Latch (WEL)  
bit before sending the Block Erase (BE). Any address of the block (Please refer to "Table 4. Memory Organization")  
is a valid address for Block Erase (BE) instruction. The CS# must go high exactly at the byte boundary (the latest  
eighth of address byte been latched-in); otherwise, the instruction will be rejected and not executed.  
The sequence of issuing BE instruction is: CS# goes low→ sending BE instruction code→ 3-byte address on SI→  
CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The self-timed Block Erase Cycle time (tBE) is initiated as soon as Chip Select (CS#) goes high. The Write in  
Progress (WIP) bit still can be checked during the Block Erase cycle is in progress. The WIP sets 1 during the tBE  
timing, and sets 0 when Block Erase Cycle is completed, and the Write Enable Latch (WEL) bit is reset. If the block  
is protected by BP3, BP2, BP1, BP0 bits, the Block Erase (BE) instruction will not be executed on the block.  
Figure 43. Block Erase (BE) Sequence (SPI Mode)  
CS#  
0
1
2
3
4
5
6
7
8
9
29 30 31  
Mode 3  
Mode 0  
SCLK  
Command  
D8h  
24-Bit Address  
SI  
23 22  
2
0
1
MSB  
Figure 44. Block Erase (BE) Sequence (QPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
SCLK  
24-Bit Address  
Command  
SIO[3:0]  
D8h A5 A4 A3 A2 A1 A0  
MSB  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
52  
 
MX25U1635F  
9-21. Chip Erase (CE)  
The Chip Erase (CE) instruction is for erasing the data of the whole chip to be "1". A Write Enable (WREN) instruc-  
tion must execute to set the Write Enable Latch (WEL) bit before sending the Chip Erase (CE). The CS# must go  
high exactly at the byte boundary, otherwise the instruction will be rejected and not executed.  
The sequence of issuing CE instruction is: CS# goes low→sending CE instruction code→CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The self-timed Chip Erase Cycle time (tCE) is initiated as soon as Chip Select (CS#) goes high. The Write in  
Progress (WIP) bit still can be checked during the Chip Erase cycle is in progress. The WIP sets 1 during the tCE  
timing, and sets 0 when Chip Erase Cycle is completed, and the Write Enable Latch (WEL) bit is reset. If the chip is  
protected by BP3, BP2, BP1, BP0 bits, the Chip Erase (CE) instruction will not be executed. It will be only execut-  
ed when BP3, BP2, BP1, BP0 all set to "0".  
Figure 45. Chip Erase (CE) Sequence (SPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
SCLK  
SI  
Command  
60h or C7h  
Figure 46. Chip Erase (CE) Sequence (QPI Mode)  
CS#  
0
1
Mode 3  
SCLK  
Command  
60h or C7h  
Mode 0  
SIO[3:0]  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
53  
 
MX25U1635F  
9-22. Page Program (PP)  
The Page Program (PP) instruction is for programming memory bits to "0". One to 256 bytes can be sent to the de-  
vice to be programmed. A Write Enable (WREN) instruction must be executed to set the Write Enable Latch (WEL)  
bit before sending the Page Program (PP). If more than 256 data bytes are sent to the device, only the last 256  
data bytes will be accepted and the previous data bytes will be disregarded. The Page Program instruction requires  
that all the data bytes fall within the same 256-byte page. The low order address byte A[7:0] specifies the starting  
address within the selected page. Bytes that will cross a page boundary will wrap to the beginning of the selected  
page. The device can accept (256 minus A[7:0]) data bytes without wrapping. If 256 data bytes are going to be pro-  
grammed, A[7:0] should be set to 0.  
The sequence of issuing PP instruction is: CS# goes low→ sending PP instruction code→ 3-byte address on SI→ at  
least 1-byte on data on SI→ CS# goes high.  
The CS# must be kept low during the whole Page Program cycle; The CS# must go high exactly at the byte boundary (the  
latest eighth bit of data being latched in), otherwise the instruction will be rejected and will not be executed.  
The self-timed Page Program Cycle time (tPP) is initiated as soon as Chip Select (CS#) goes high. The Write in  
Progress (WIP) bit still can be checked during the Page Program cycle is in progress. The WIP sets 1 during the  
tPP timing, and sets 0 when Page Program Cycle is completed, and the Write Enable Latch (WEL) bit is reset. If the  
page is protected by BP3, BP2, BP1, BP0 bits, the Page Program (PP) instruction will not be executed.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
54  
MX25U1635F  
Figure 47. Page Program (PP) Sequence (SPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
3
4
5
6
7
8
9
10  
28 29 30 31 32 33 34 35 36 37 38 39  
SCLK  
Command  
02h  
Data Byte 1  
24-Bit Address  
23 22 21  
MSB  
3
2
1
0
7
6
5
4
3
2
0
1
SI  
MSB  
CS#  
40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55  
SCLK  
Data Byte 2  
Data Byte 3  
Data Byte 256  
7
6
5
4
3
2
0
7
6
5
4
3
2
0
7
6
5
4
3
2
0
1
1
1
SI  
MSB  
MSB  
MSB  
Figure 48. Page Program (PP) Sequence (QPI Mode)  
CS#  
Mode 3  
Mode 0  
0
1
2
SCLK  
Command  
02h  
24-Bit Address  
SIO[3:0]  
H0 L0 H1 L1 H2 L2 H3 L3  
H255 L255  
A5 A4 A3 A2 A1 A0  
......  
Data Byte Data Byte Data Byte Data Byte  
Data Byte  
256  
Data In  
1
2
3
4
P/N: PM1901  
Rev. 1.6, January 17, 2017  
55  
 
MX25U1635F  
9-23. 4 x I/O Page Program (4PP)  
The Quad Page Program (4PP) instruction is for programming the memory to be "0". A Write Enable (WREN) in-  
struction must execute to set the Write Enable Latch (WEL) bit and Quad Enable (QE) bit must be set to "1" before  
sending the Quad Page Program (4PP). The Quad Page Programming takes four pins: SIO0, SIO1, SIO2, and  
SIO3 as address and data input, which can improve programmer performance and the effectiveness of application.  
The 4PP operation frequency supports as fast as 104MHz. The other function descriptions are as same as standard  
page program.  
The sequence of issuing 4PP instruction is: CS# goes low→ sending 4PP instruction code→ 3-byte address on  
SIO[3:0]→ at least 1-byte on data on SIO[3:0]→CS# goes high.  
Figure 49. 4 x I/O Page Program (4PP) Sequence (SPI Mode only)  
CS#  
10 11 12 13 14 15 16 17 18 19 20 21  
Data Data Data Data  
0
1
2
3
4
5
6
7
8
9
Mode 3  
Mode 0  
SCLK  
Command  
38h  
6 ADD cycles  
Byte 1 Byte 2 Byte 3 Byte 4  
A16 A12 A8 A4 A0  
A20  
D4 D0 D4 D0 D4 D0  
D0  
D4  
SIO0  
SIO1  
SIO2  
SIO3  
A21 A17 A13 A9 A5 A1  
A22 A18 A14 A10 A6 A2  
D5 D1 D5 D1 D5 D1 D5 D1  
D6 D2 D6 D2 D6 D2 D6 D2  
A23 A19 A15 A11 A7 A3 D7 D3 D7 D3 D7 D3 D7 D3  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
56  
 
MX25U1635F  
9-24. Deep Power-down (DP)  
The Deep Power-down (DP) instruction is for setting the device on the minimizing the power consumption (to enter-  
ing the Deep Power-down mode), the standby current is reduced from ISB1 to ISB2). The Deep Power-down mode  
requires the Deep Power-down (DP) instruction to enter, during the Deep Power-down mode, the device is not ac-  
tive and all Write/Program/Erase instruction are ignored. When CS# goes high, it's only in deep power-down mode  
not standby mode. It's different from Standby mode.  
The sequence of issuing DP instruction is: CS# goes low→sending DP instruction code→CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
Once the DP instruction is set, all instructions will be ignored except the Release from Deep Power-down mode  
(RDP) and Read Electronic Signature (RES) instruction and softreset command. (those instructions allow the ID be-  
ing reading out). When Power-down, or software reset command the deep power-down mode automatically stops,  
and when power-up, the device automatically is in standby mode. For DP instruction the CS# must go high exactly  
at the byte boundary (the latest eighth bit of instruction code been latched-in); otherwise, the instruction will not be  
executed. As soon as Chip Select (CS#) goes high, a delay of tDP is required before entering the Deep Power-down  
mode.  
Figure 50. Deep Power-down (DP) Sequence (SPI Mode)  
CS#  
tDP  
0
1
2
3
4
5
6
7
Mode 3  
Mode 0  
SCLK  
SI  
Command  
B9h  
Stand-by Mode  
Deep Power-down Mode  
Figure 51. Deep Power-down (DP) Sequence (QPI Mode)  
CS#  
t
DP  
Mode 3  
Mode 0  
0
1
SCLK  
Command  
SIO[3:0]  
B9h  
Stand-by Mode  
Deep Power-down Mode  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
57  
 
MX25U1635F  
9-25. Enter Secured OTP (ENSO)  
The ENSO instruction is for entering the additional 4K-bit secured OTP mode. The additional 4K-bit secured OTP is  
independent from main array, which may use to store unique serial number for system identifier. After entering the  
Secured OTP mode, and then follow standard read or program procedure to read out the data or update data. The  
Secured OTP data cannot be updated again once it is lock-down.  
The sequence of issuing ENSO instruction is: CS# goes low→ sending ENSO instruction to enter Secured OTP  
mode→ CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
Please note that WRSR/WRSCUR commands are not acceptable during the access of secure OTP region, once se-  
curity OTP is lock down, only read related commands are valid.  
9-26. Exit Secured OTP (EXSO)  
The EXSO instruction is for exiting the additional 4K-bit secured OTP mode.  
The sequence of issuing EXSO instruction is: CS# goes low→ sending EXSO instruction to exit Secured OTP  
mode→ CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
9-27. Read Security Register (RDSCUR)  
The RDSCUR instruction is for reading the value of Security Register bits. The Read Security Register can be read  
at any time (even in program/erase/write status register/write security register condition) and continuously.  
The sequence of issuing RDSCUR instruction is : CS# goes low→sending RDSCUR instruction→Security Register  
data out on SO→ CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The definition of the Security Register bits is as below:  
Secured OTP Indicator bit. The Secured OTP indicator bit shows the chip is locked by factory before ex- factory or  
not. When it is "0", it indicates non-factory lock; "1" indicates factory-lock.  
Lock-down Secured OTP (LDSO) bit. By writing WRSCUR instruction, the LDSO bit may be set to "1" for cus-  
tomer lock-down purpose. However, once the bit is set to "1" (lock-down), the LDSO bit and the 4K-bit Secured OTP  
area cannot be update any more. While it is in 4K-bit secured OTP mode, main array access is not allowed.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
58  
MX25U1635F  
Erase Fail bit. The Erase Fail bit is a status flag, which shows the status of last Erase operation. It will be set to  
"1", if the erase operation fails or the erase region is protected. It will be set to "0", if the last operation is successful.  
Please note that it will not interrupt or stop any operation in the flash memory.  
Program Fail bit. The Program Fail bit is a status flag, which shows the status of last Program operation. It will be  
set to "1", if the program operation fails or the program region is protected. It will be set to "0", if the last operation is  
successful. Please note that it will not interrupt or stop any operation in the flash memory.  
Erase Suspend bit. Erase Suspend Bit (ESB) indicates the status of Erase Suspend operation. Users may use  
ESB to identify the state of flash memory. After the flash memory is suspended by Erase Suspend command, ESB  
is set to "1". ESB is cleared to "0" after erase operation resumes.  
Program Suspend bit. Program Suspend Bit (PSB) indicates the status of Program Suspend operation. Users may  
use PSB to identify the state of flash memory. After the flash memory is suspended by Program Suspend command,  
PSB is set to "1". PSB is cleared to "0" after program operation resumes.  
Table 8. Security Register Definition  
bit7  
bit6  
bit5  
bit4  
bit3  
bit2  
bit1  
bit0  
ESB  
(Erase  
PSB  
(Program  
LDSO  
(indicate if  
Secured OTP  
indicator bit  
WPSEL  
E_FAIL  
P_FAIL  
Reserved  
Suspend bit) Suspend bit) lock-down)  
0=normal  
Program  
succeed  
1=indicate  
Program  
failed  
0 = not lock-  
0=normal  
Erase  
succeed  
1=indicate  
Erase failed  
(default=0)  
0=Erase  
is not  
suspended suspended  
1= Erase 1= Program  
suspended suspended  
0=Program  
is not  
0=normal  
WP mode  
1=individual  
mode  
down  
1 = lock-down  
(cannot  
program/  
erase  
0 = non-  
factory  
lock  
1 = factory  
lock  
-
(default=0)  
(default=0)  
(default=0)  
(default=0)  
OTP)  
Non-volatile  
bit  
Non-volatile  
bit (OTP)  
Non-volatile  
bit (OTP)  
Volatile bit  
Volatile bit  
Volatile bit  
Volatile bit  
Volatile bit  
(OTP)  
9-28. Write Security Register (WRSCUR)  
The WRSCUR instruction is for changing the values of Security Register Bits. The WREN (Write Enable) instruction  
is required before issuing WRSCUR instruction. The WRSCUR instruction may change the values of bit1 (LDSO  
bit) for customer to lock-down the 4K-bit Secured OTP area. Once the LDSO bit is set to "1", the Secured OTP area  
cannot be updated any more.  
The sequence of issuing WRSCUR instruction is :CS# goes low→ sending WRSCUR instruction → CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The CS# must go high exactly at the boundary; otherwise, the instruction will be rejected and not executed.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
59  
 
MX25U1635F  
9-29. Write Protection Selection (WPSEL)  
There are two write protection methods provided on this device, (1) Block Protection (BP) mode or (2) individual  
block protection mode. The protection modes are mutually exclusive. The WPSEL bit selects which protection mode  
is enabled. If WPSEL=0 (factory default), BP mode is enabled and individual block protection mode is disabled. If  
WPSEL=1, individual block protection mode is enabled and BP mode is disabled. The WPSEL command is used  
to set WPSEL=1. A WREN command must be executed to set the WEL bit before sending the WPSEL command.  
Please note that the WPSEL bit is an OTP bit. Once WPSEL is set to “1”, it cannot be programmed back to “0”.  
Every time after the system is powered-on, and the Security Register bit 7(WPSEL) is checked if WPSEL=1.  
When WPSEL=1, it is in individual block protection mode,all the blocks or sectors will be write protected by  
default. User may only unlock the blocks or sectors via SBULK and GBULK instruction. Program or erase functions  
can only be operated after the Unlock instruction is conducted.  
When WPSEL = 0: Block Protection (BP) mode,  
The memory array is write protected by the BP3~BP0 bits.  
When WPSEL =1: Individual block protection mode,  
Blocks are individually protected by their own SRAM lock bits which are set to “1” after power up. SBULK and SBLK  
command can set SRAM lock bit to “0” and “1”. The Individual block protection instructions SBLK, SBULK, RD-  
BLOCK, GBLK, GBULK…etc are activated to conduct block lock protection. The BP3~BP0 bits of the Status Reg-  
ister are disabled and have no effect. Hardware protection is performed by driving WP#=0. Once WP#=0 all blocks  
and sectors are write protected regardless of the state of each SRAM lock bit.  
The sequence of issuing WPSEL instruction is: CS# goes low → send WPSEL instruction to enable the individual  
block protect mode → CS# goes high.  
WPSEL instruction function flow is as follows:  
BP and SRWD if WPSEL=0  
WP# pin  
BP3 BP2 BP1 BP0  
SRWD  
64KB  
64KB  
64KB  
(1) BP3~BP0 is used to define the protection group region.  
(The protected area size see "Table 2. Protected Area  
Sizes")  
(2) “SRWD=1 and WP#=0” is used to protect BP3~BP0. In this  
case, SRWD and BP3~BP0 of status register bits can not  
be changed by WRSR  
.
.
.
64KB  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
60  
MX25U1635F  
The individual block lock mode is effective after setting WPSEL=1  
4KB  
4KB  
SRAM  
SRAM  
• Power-Up: All SRAM bits=1 (all blocks are default protected).  
All array cannot be programmed/erased  
TOP 4KBx16  
Sectors  
• SBLK/SBULK(36h/39h):  
- SBLK(36h): Set SRAM bit=1 (protect) : array can not be  
programmed/erased  
4KB  
SRAM  
SRAM  
- SBULK(39h): Set SRAM bit=0 (unprotect): array can be  
programmed/erased  
64KB  
- All top 4KBx16 sectors and bottom 4KBx16 sectors  
and other 64KB uniform blocks can be protected and  
unprotected by SRAM bits individually by SBLK/SBULK  
command set.  
SRAM  
Uniform  
64KB blocks  
• GBLK/GBULK(7Eh/98h):  
- GBLK(7Eh): Set all SRAM bits=1,whole chip is protected  
and cannot be programmed/erased.  
- GBULK(98h): Set all SRAM bits=0,whole chip is  
unprotected and can be programmed/erased.  
- All sectors and blocks SRAM bits of whole chip can be  
protected and unprotected at one time by GBLK/GBULK  
command set.  
64KB  
4KB  
SRAM  
SRAM  
Bottom  
4KBx16  
Sectors  
• RDBLOCK(3Ch):  
- use RDBLOCK mode to check the SRAM bits status after  
SBULK /SBLK/GBULK/GBLK command set.  
4KB  
SBULK / SBLK / GBULK / GBLK / RDBLOCK  
Figure 52. Write Protection Selection (WPSEL) Sequence (Command 68)  
CS#  
0
1
2
3
4
5
6
7
SCLK  
SI  
Command  
68  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
61  
 
MX25U1635F  
Figure 53. WPSEL Flow  
start  
WREN command  
RDSCUR(2Bh) command  
WPSEL=1?  
Yes  
No  
WPSEL disable,  
block protected by BP[3:0]  
WPSEL(68h) command  
RDSR command  
WIP=0?  
No  
Yes  
RDSCUR(2Bh) command  
No  
WPSEL=1?  
Yes  
WPSEL set successfully  
WPSEL set fail  
WPSEL enable.  
Block protected by individual lock  
(SBLK, SBULK,  
… etc).  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
62  
 
MX25U1635F  
9-30. Single Block Lock/Unlock Protection (SBLK/SBULK)  
These instructions are only effective after WPSEL was executed. The SBLK instruction is for write protection a spec-  
ified block (or sector) of memory, using AMAX-A16 or (AMAX-A12) address bits to assign a 64Kbyte block (or 4K bytes  
sector) to be protected as read only. The SBULK instruction will cancel the block (or sector) write protection state.  
This feature allows user to stop protecting the entire block (or sector) through the chip unprotect command (GBULK).  
The WREN (Write Enable) instruction is required before issuing SBLK/SBULK instruction.  
The sequence of issuing SBLK/SBULK instruction is: CS# goes low → send SBLK/SBULK (36h/39h)  
instruction→send 3-byte address assign one block (or sector) to be protected on SI pin → CS# goes high. The CS#  
must go high exactly at the byte boundary, otherwise the instruction will be rejected and not be executed.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
SBLK/SBULK instruction function flow is as follows:  
Figure 54. Block Lock Flow  
Start  
RDSCUR(2Bh) command  
No  
WPSEL=1?  
WPSEL command  
Yes  
WREN command  
SBLK command  
( 36h + 24bit address )  
RDSR command  
No  
WIP=0?  
Yes  
RDBLOCK command  
( 3Ch + 24bit address )  
No  
Data = FFh ?  
Yes  
Block lock successfully  
Block lock fail  
Yes  
Lock another block?  
No  
Block lock completed  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
63  
 
MX25U1635F  
Figure 55. Block Unlock Flow  
start  
RDSCUR(2Bh) command  
No  
WPSEL=1?  
Yes  
WPSEL command  
WREN command  
SBULK command  
( 39h + 24bit address )  
RDSR command  
No  
WIP=0?  
Yes  
RDBLOCK command to verify  
( 3Ch + 24bit address )  
Yes  
Data = FF ?  
No  
Block unlock successfully  
Block unlock fail  
Yes  
Unlock another block?  
Unlock block completed?  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
64  
 
MX25U1635F  
9-31. Read Block Lock Status (RDBLOCK)  
This instruction is only effective after WPSEL was executed. The RDBLOCK instruction is for reading the status of  
protection lock of a specified block (or sector), using AMAX-A16 (or AMAX-A12) address bits to assign a 64K bytes block (4K  
bytes sector) and read protection lock status bit which the first byte of Read-out cycle. The status bit is"1" to indicate  
that this block has be protected, that user can read only but cannot write/program /erase this block. The status bit is  
"0" to indicate that this block hasn't be protected, and user can read and write this block.  
The sequence of issuing RDBLOCK instruction is: CS# goes low → send RDBLOCK (3Ch) instruction → send  
3-byte address to assign one block on SI pin → read block's protection lock status bit on SO pin → CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
9-32. Gang Block Lock/Unlock (GBLK/GBULK)  
These instructions are only effective after WPSEL was executed. The GBLK/GBULK instruction is for enable/disable  
the lock protection block of the whole chip.  
The WREN (Write Enable) instruction is required before issuing GBLK/GBULK instruction.  
The sequence of issuing GBLK/GBULK instruction is: CS# goes low → send GBLK/GBULK (7Eh/98h) instruction  
→CS# goes high.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
The CS# must go high exactly at the byte boundary, otherwise, the instruction will be rejected and not be executed.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
65  
MX25U1635F  
9-33. Program Suspend and Erase Suspend  
The Suspend instruction interrupts a Page Program, Sector Erase, or Block Erase operation to allow access to  
the memory array. After the program or erase operation has entered the suspended state, the memory array can  
be read except for the page being programmed or the sector or block being erased ("Table 9. Readable Area of  
Memory While a Program or Erase Operation is Suspended").  
Table 9. Readable Area of Memory While a Program or Erase Operation is Suspended  
Suspended Operation  
Page Program  
Readable Region of Memory Array  
All but the Page being programmed  
All but the 4KB Sector being erased  
All but the 32KB Block being erased  
All but the 64KB Block being erased  
Sector Erase (4KB)  
Block Erase (32KB)  
Block Erase (64KB)  
When the serial flash receives the Suspend instruction, there is a latency of tPSL or tESL ("Figure 56. Suspend to  
Read Latency") before the Write Enable Latch (WEL) bit clears to “0” and the PSB or ESB sets to “1”, after which  
the device is ready to accept one of the commands listed in "Table 10. Acceptable Commands During Program/  
Erase Suspend after tPSL/tESL" (e.g. FAST READ).  
Refer to "Table 19. AC Characteristics" for tPSL and tESL timings.  
"Table 11. Acceptable Commands During Suspend (tPSL/tESL not required)" lists the commands for which the tPSL  
and tESL latencies do not apply. For example, RDSR, RDSCUR, RSTEN, and RST can be issued at any time after  
the Suspend instruction.  
Security Register bit 2 (PSB) and bit 3 (ESB) can be read to check the suspend status (please refer to "Table 8.  
Security Register Definition"). The PSB (Program Suspend Bit) sets to “1” when a program operation is suspended.  
The ESB (Erase Suspend Bit) sets to “1” when an erase operation is suspended. The PSB or ESB clears to “0”  
when the program or erase operation is resumed.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
66  
 
MX25U1635F  
Table 10. Acceptable Commands During Program/Erase Suspend after tPSL/tESL  
Suspend Type  
Command Name  
Command Code  
Program Suspend  
Erase Suspend  
READ  
FAST READ  
DREAD  
QREAD  
2READ  
4READ  
W4READ  
RDSFDP  
RDBLOCK  
RDID  
03h  
0Bh  
3Bh  
6Bh  
BBh  
EBh  
E7h  
5Ah  
3Ch  
9Fh  
AFh  
90h  
35h  
B1h  
C1h  
F5h  
06h  
30h  
C0h  
02h  
38h  
QPIID  
REMS  
EQIO  
ENSO  
EXSO  
RSTQIO  
WREN  
RESUME  
SBL  
PP  
4PP  
Table 11. Acceptable Commands During Suspend (tPSL/tESL not required)  
Suspend Type  
Command Name  
Command Code  
Program Suspend  
Erase Suspend  
WRDI  
RDSR  
RDSCUR  
RES  
04h  
05h  
2Bh  
ABh  
66h  
99h  
00h  
RSTEN  
RST  
NOP  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
67  
 
 
MX25U1635F  
Figure 56. Suspend to Read Latency  
tPSL / tESL  
Read Command  
Suspend Command  
CS#  
tPSL: Program Latency  
tESL: Erase Latency  
Figure 57. Resume to Suspend Latency  
tPRS / tERS  
Suspend  
Resume  
Command  
CS#  
Command  
tPRS: Program Resume to another Suspend  
tERS: Erase Resume to another Suspend  
9-33-1. Erase Suspend to Program  
The “Erase Suspend to Program” feature allows Page Programming while an erase operation is suspended. Page  
Programming is permitted in any unprotected memory except within the sector of a suspended Sector Erase  
operation or within the block of a suspended Block Erase operation. The Write Enable (WREN) instruction must be  
issued before any Page Program instruction.  
A Page Program operation initiated within a suspended erase cannot itself be suspended and must be allowed to  
finish before the suspended erase can be resumed. The Status Register can be polled to determine the status of  
the Page Program operation. The WEL and WIP bits of the Status Register will remain “1” while the Page Program  
operation is in progress and will both clear to “0” when the Page Program operation completes.  
Figure 58. Suspend to Program Latency  
tPSL / tESL  
Suspend Command  
Program Command  
CS#  
tPSL: Program Latency  
tESL: Erase Latency  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
68  
 
 
 
MX25U1635F  
9-34. Program Resume and Erase Resume  
The Resume instruction resumes a suspended Page Program, Sector Erase, or Block Erase operation. Before  
issuing the Resume instruction to restart a suspended erase operation, make sure that there is no Page Program  
operation in progress.  
Immediately after the serial flash receives the Resume instruction, the WEL and WIP bits are set to “1” and the PSB  
or ESB is cleared to “0”. The program or erase operation will continue until finished ("Figure 59. Resume to Read  
Latency") or until another Suspend instruction is received. A resume-to-suspend latency of tPRS or tERS must be  
observed before issuing another Suspend instruction ("Figure 57. Resume to Suspend Latency").  
Please note that the Resume instruction will be ignored if the serial flash is in “Performance Enhance Mode”. Make  
sure the serial flash is not in “Performance Enhance Mode” before issuing the Resume instruction.  
Figure 59. Resume to Read Latency  
tSE/tBE/tBE32K/tPP  
Read Command  
Resume Command  
CS#  
9-35. No Operation (NOP)  
The "No Operation" command is only able to terminate the Reset Enable (RSTEN) command and will not affect any  
other command.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are don't care  
when during SPI mode.  
9-36. Software Reset (Reset-Enable (RSTEN) and Reset (RST))  
The Software Reset operation combines two instructions: Reset-Enable (RSTEN) command and Reset (RST)  
command. It returns the device to a standby mode. All the volatile bits and settings will be cleared then, which  
makes the device return to the default status as power on.  
To execute Reset command (RST), the Reset-Enable (RSTEN) command must be executed first to perform the  
Reset operation. If there is any other command to interrupt after the Reset-Enable command, the Reset-Enable will  
be invalid.  
Both SPI (8 clocks) and QPI (2 clocks) command cycle can accept by this instruction. The SIO[3:1] are "don't care"  
in SPI mode.  
If the Reset command is executed during program or erase operation, the operation will be disabled, the data under  
processing could be damaged or lost.  
The reset time is different depending on the last operation. Longer latency time is required to recover from a pro-  
gram operation than from other operations.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
69  
 
 
MX25U1635F  
Figure 60. Software Reset Recovery  
Stand-by Mode  
66  
99  
CS#  
tRCR  
tRCP  
tRCE  
Mode  
Figure 61. Reset Sequence (SPI mode)  
CS#  
Mode 3  
Mode 3  
Mode 0  
SCLK  
Mode 0  
Command  
Command  
99h  
66h  
SIO0  
Figure 62. Reset Sequence (QPI mode)  
tSHSL  
CS#  
MODE 3  
MODE 3  
MODE 0  
MODE 3  
MODE 0  
SCLK  
MODE 0  
Command  
Command  
SIO[3:0]  
66h  
99h  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
70  
 
MX25U1635F  
9-37. Read SFDP Mode (RDSFDP)  
The Serial Flash Discoverable Parameter (SFDP) standard provides a consistent method of describing the functional  
and feature capabilities of serial flash devices in a standard set of internal parameter tables. These parameter tables  
can be interrogated by host system software to enable adjustments needed to accommodate divergent features  
from multiple vendors. The concept is similar to the one found in the Introduction of JEDEC Standard, JESD68 on  
CFI.  
The sequence of issuing RDSFDP instruction is same as FAST_READ: CS# goes low→send RDSFDP instruction  
(5Ah)→send 3 address bytes on SI pin→send 1 dummy byte on SI pin→read SFDP code on SO→to end RDSFDP  
operation can use CS# to high at any time during data out.  
SFDP is a JEDEC Standard, JESD216.  
Figure 63. Read Serial Flash Discoverable Parameter (RDSFDP) Sequence  
CS#  
0
1
2
3
4
5
6
7
8
9
10  
28 29 30 31  
SCLK  
Command  
5Ah  
24 BIT ADDRESS  
SI  
23 22 21  
3
2
1
0
High-Z  
SO  
CS#  
47  
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46  
SCLK  
Dummy Cycle  
7
6
5
4
3
2
0
1
SI  
DATA OUT 2  
DATA OUT 1  
7
6
5
4
3
2
1
0
7
7
6
5
4
3
2
0
1
SO  
MSB  
MSB  
MSB  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
71  
 
MX25U1635F  
Table 12. Signature and Parameter Identification Data Values  
SFDP Table below is for MX25U1635FBAI-10G, MX25U1635FM2I-10G, MX25U1635FZBI-10G,  
MX25U1635FZNI-10G and MX25U1635FZUI-10G  
Add (h) DW Add Data (h/b) Data  
Description  
Comment  
(Byte)  
(Bit)  
(Note1)  
(h)  
00h  
07:00  
53h  
53h  
01h  
02h  
03h  
04h  
05h  
15:08  
23:16  
31:24  
07:00  
15:08  
46h  
44h  
50h  
00h  
01h  
46h  
44h  
50h  
00h  
01h  
SFDP Signature  
Fixed: 50444653h  
SFDP Minor Revision Number  
SFDP Major Revision Number  
Start from 00h  
Start from 01h  
This number is 0-based. Therefore,  
0 indicates 1 parameter header.  
Number of Parameter Headers  
Unused  
06h  
07h  
08h  
09h  
0Ah  
0Bh  
23:16  
31:24  
07:00  
15:08  
23:16  
31:24  
01h  
FFh  
00h  
00h  
01h  
09h  
01h  
FFh  
00h  
00h  
01h  
09h  
00h: it indicates a JEDEC specified  
header.  
ID number (JEDEC)  
Parameter Table Minor Revision  
Number  
Parameter Table Major Revision  
Number  
Parameter Table Length  
(in double word)  
Start from 00h  
Start from 01h  
How many DWORDs in the  
Parameter table  
0Ch  
0Dh  
0Eh  
07:00  
15:08  
23:16  
30h  
00h  
00h  
30h  
00h  
00h  
First address of JEDEC Flash  
Parameter table  
Parameter Table Pointer (PTP)  
Unused  
0Fh  
10h  
11h  
12h  
13h  
31:24  
07:00  
15:08  
23:16  
31:24  
FFh  
C2h  
00h  
01h  
04h  
FFh  
C2h  
00h  
01h  
04h  
ID number  
(Macronix manufacturer ID)  
Parameter Table Minor Revision  
Number  
Parameter Table Major Revision  
Number  
it indicates Macronix manufacturer  
ID  
Start from 00h  
Start from 01h  
Parameter Table Length  
(in double word)  
How many DWORDs in the  
Parameter table  
14h  
15h  
16h  
07:00  
15:08  
23:16  
60h  
00h  
00h  
60h  
00h  
00h  
First address of Macronix Flash  
Parameter table  
Parameter Table Pointer (PTP)  
Unused  
17h  
31:24  
FFh  
FFh  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
72  
MX25U1635F  
Table 13. Parameter Table (0): JEDEC Flash Parameter Tables  
SFDP Table below is for MX25U1635FBAI-10G, MX25U1635FM2I-10G, MX25U1635FZBI-10G,  
MX25U1635FZNI-10G and MX25U1635FZUI-10G  
Add (h) DW Add Data (h/b) Data  
Description  
Comment  
(Byte)  
(Bit)  
(Note1)  
(h)  
00: Reserved, 01: 4KB erase,  
10: Reserved,  
11: not support 4KB erase  
Block/Sector Erase sizes  
Write Granularity  
01:00  
01b  
0: 1Byte, 1: 64Byte or larger  
02  
03  
1b  
0b  
Write Enable Instruction Required 0: not required  
for Writing to Volatile Status  
1: required 00h to be written to the  
Registers  
status register  
30h  
E5h  
0: use 50h opcode,  
1: use 06h opcode  
Write Enable Opcode Select for  
Writing to Volatile Status Registers  
Note: If target flash status register is  
nonvolatile, then bits 3 and 4 must  
be set to 00b.  
04  
0b  
Contains 111b and can never be  
changed  
Unused  
07:05  
111b  
4KB Erase Opcode  
31h  
32h  
33h  
15:08  
16  
20h  
1b  
20h  
F1h  
FFh  
(1-1-2) Fast Read (Note2)  
0=not support 1=support  
Address Bytes Number used in  
addressing flash array  
00: 3Byte only, 01: 3 or 4Byte,  
10: 4Byte only, 11: Reserved  
18:17  
19  
00b  
0b  
Double Transfer Rate (DTR)  
Clocking  
0=not support 1=support  
(1-2-2) Fast Read  
(1-4-4) Fast Read  
(1-1-4) Fast Read  
Unused  
0=not support 1=support  
0=not support 1=support  
0=not support 1=support  
20  
21  
1b  
1b  
22  
1b  
23  
1b  
Unused  
31:24  
FFh  
Flash Memory Density  
37h:34h 31:00  
00FF FFFFh  
(1-4-4) Fast Read Number of Wait 0 0000b: Wait states (Dummy  
04:00  
38h  
0 0100b  
states (Note3)  
Clocks) not support  
44h  
EBh  
08h  
6Bh  
(1-4-4) Fast Read Number of  
Mode Bits (Note4)  
000b: Mode Bits not support  
07:05  
010b  
EBh  
(1-4-4) Fast Read Opcode  
39h  
3Ah  
3Bh  
15:08  
20:16  
(1-1-4) Fast Read Number of Wait 0 0000b: Wait states (Dummy  
0 1000b  
states  
Clocks) not support  
(1-1-4) Fast Read Number of  
Mode Bits  
000b: Mode Bits not support  
23:21  
31:24  
000b  
6Bh  
(1-1-4) Fast Read Opcode  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
73  
MX25U1635F  
SFDP Table below is for MX25U1635FBAI-10G, MX25U1635FM2I-10G, MX25U1635FZBI-10G,  
MX25U1635FZNI-10G and MX25U1635FZUI-10G  
Add (h) DW Add Data (h/b) Data  
Description  
Comment  
(Byte)  
(Bit)  
(Note1)  
(h)  
(1-1-2) Fast Read Number of Wait 0 0000b: Wait states (Dummy  
04:00  
0 1000b  
states  
Clocks) not support  
3Ch  
08h  
(1-1-2) Fast Read Number of  
Mode Bits  
000b: Mode Bits not support  
07:05  
15:08  
20:16  
000b  
3Bh  
(1-1-2) Fast Read Opcode  
3Dh  
3Eh  
3Fh  
3Bh  
04h  
BBh  
(1-2-2) Fast Read Number of Wait 0 0000b: Wait states (Dummy  
0 0100b  
states  
Clocks) not support  
(1-2-2) Fast Read Number of  
Mode Bits  
000b: Mode Bits not support  
23:21  
000b  
(1-2-2) Fast Read Opcode  
(2-2-2) Fast Read  
Unused  
31:24  
00  
BBh  
0b  
0=not support 1=support  
0=not support 1=support  
03:01  
04  
111b  
1b  
40h  
FEh  
(4-4-4) Fast Read  
Unused  
07:05  
111b  
FFh  
FFh  
Unused  
43h:41h 31:08  
45h:44h 15:00  
FFh  
FFh  
Unused  
(2-2-2) Fast Read Number of Wait 0 0000b: Wait states (Dummy  
20:16  
46h  
0 0000b  
000b  
states  
Clocks) not support  
00h  
(2-2-2) Fast Read Number of  
Mode Bits  
000b: Mode Bits not support  
23:21  
(2-2-2) Fast Read Opcode  
Unused  
47h  
31:24  
FFh  
FFh  
FFh  
FFh  
49h:48h 15:00  
(4-4-4) Fast Read Number of Wait 0 0000b: Wait states (Dummy  
20:16  
4Ah  
0 0100b  
states  
Clocks) not support  
44h  
(4-4-4) Fast Read Number of  
Mode Bits  
000b: Mode Bits not support  
23:21  
010b  
EBh  
0Ch  
20h  
0Fh  
52h  
10h  
D8h  
00h  
FFh  
(4-4-4) Fast Read Opcode  
4Bh  
4Ch  
4Dh  
4Eh  
4Fh  
50h  
51h  
52h  
53h  
31:24  
07:00  
15:08  
23:16  
31:24  
07:00  
15:08  
23:16  
31:24  
EBh  
0Ch  
20h  
0Fh  
52h  
10h  
D8h  
00h  
FFh  
Sector/block size = 2^N bytes (Note5)  
0x00b: this sector type doesn't exist  
Sector Type 1 Size  
Sector Type 1 erase Opcode  
Sector Type 2 Size  
Sector/block size = 2^N bytes  
0x00b: this sector type doesn't exist  
Sector Type 2 erase Opcode  
Sector Type 3 Size  
Sector/block size = 2^N bytes  
0x00b: this sector type doesn't exist  
Sector Type 3 erase Opcode  
Sector Type 4 Size  
Sector/block size = 2^N bytes  
0x00b: this sector type doesn't exist  
Sector Type 4 erase Opcode  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
74  
MX25U1635F  
Table 14. Parameter Table (1): Macronix Flash Parameter Tables  
SFDP Table below is for MX25U1635FBAI-10G, MX25U1635FM2I-10G, MX25U1635FZBI-10G,  
MX25U1635FZNI-10G and MX25U1635FZUI-10G  
Add (h) DW Add Data (h/b) Data  
Description  
Comment  
2000h=2.000V  
2700h=2.700V  
3600h=3.600V  
(Byte)  
(Bit)  
(Note1)  
(h)  
07:00  
15:08  
00h  
20h  
00h  
20h  
Vcc Supply Maximum Voltage  
61h:60h  
1650h=1.650V  
2250h=2.250V  
2350h=2.350V  
2700h=2.700V  
23:16  
31:24  
50h  
16h  
50h  
16h  
Vcc Supply Minimum Voltage  
63h:62h  
H/W Reset# pin  
0=not support 1=support  
00  
1b  
H/W Hold# pin  
0=not support 1=support  
0=not support 1=support  
0=not support 1=support  
01  
02  
03  
0b  
1b  
1b  
Deep Power Down Mode  
S/W Reset  
Reset Enable (66h) should be  
issued before Reset Opcode  
1001 1001b  
(99h)  
65h:64h  
F99Dh  
S/W Reset Opcode  
11:04  
Program Suspend/Resume  
Erase Suspend/Resume  
Unused  
0=not support 1=support  
0=not support 1=support  
12  
13  
1b  
1b  
14  
1b  
Wrap-Around Read mode  
Wrap-Around Read mode Opcode  
0=not support 1=support  
15  
1b  
66h  
67h  
23:16  
C0h  
C0h  
64h  
08h:support 8B wrap-around read  
16h:8B&16B  
32h:8B&16B&32B  
Wrap-Around Read data length  
31:24  
64h  
64h:8B&16B&32B&64B  
Individual block lock  
0=not support 1=support  
00  
01  
1b  
0b  
Individual block lock bit  
(Volatile/Nonvolatile)  
0=Volatile 1=Nonvolatile  
0011 0110b  
(36h)  
Individual block lock Opcode  
09:02  
10  
Individual block lock Volatile  
protect bit default protect status  
0=protect 1=unprotect  
0b  
C8D9h  
6Bh:68h  
Secured OTP  
Read Lock  
Permanent Lock  
Unused  
0=not support 1=support  
0=not support 1=support  
0=not support 1=support  
11  
12  
1b  
0b  
13  
0b  
15:14  
31:16  
11b  
FFh  
FFh  
Unused  
FFh  
FFh  
Unused  
6Fh:6Ch 31:00  
MX25U1635FBAI-10G-SFDP_2014-06-18  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
75  
MX25U1635F  
Note 1: h/b is hexadecimal or binary.  
Note 2: (x-y-z) means I/O mode nomenclature used to indicate the number of active pins used for the opcode (x),  
address (y), and data (z). At the present time, the only valid Read SFDP instruction modes are: (1-1-1), (2-2-2),  
and (4-4-4)  
Note 3: Wait States is required dummy clock cycles after the address bits or optional mode bits.  
Note 4: Mode Bits is optional control bits that follow the address bits. These bits are driven by the system controller  
if they are specified. (eg,read performance enhance toggling bits)  
Note 5: 4KB=2^0Ch, 32KB=2^0Fh, 64KB=2^10h  
Note 6: All unused and undefined area data is blank FFh for SFDP Tables that are defined in Parameter  
Identification Header. All other areas beyond defined SFDP Table are reserved by Macronix.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
76  
MX25U1635F  
10. RESET  
Driving the RESET# pin low for a period of tRLRH or longer will reset the device. After reset cycle, the device is at  
the following states:  
- Standby mode  
- All the volatile bits such as WEL/WIP/SRAM lock bit will return to the default status as power on.  
If the device is under programming or erasing, driving the RESET# pin low will also terminate the operation and data  
could be lost. During the resetting cycle, the SO data becomes high impedance and the current will be reduced to  
minimum.  
Figure 64. RESET Timing  
CS#  
tRHRL  
SCLK  
tRH  
tRS  
RESET#  
tRLRH  
Table 15. Reset Timing  
Symbol Alt. Parameter  
Min.  
1
15  
15  
Typ.  
Max.  
Unit  
us  
ns  
tRLRH  
tRS  
Reset Pulse Width  
Reset Setup Time  
Reset Hold Time  
tRH  
ns  
Reset Recovery Time (During instruction decoding)  
Read  
20  
20  
12  
20  
20  
us  
us  
ms  
us  
us  
tRCR  
tRHRL tRCE Reset Recovery Time  
tRCP  
Erase  
Program  
Reset Recovery Time (for WRSR operation)  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
77  
 
MX25U1635F  
11. POWER-ON STATE  
The device is at the following states after power-up:  
- Standby mode (please note it is not deep power-down mode)  
- Write Enable Latch (WEL) bit is reset  
The device must not be selected during power-up and power-down stage until the VCC reaches the following levels:  
- VCC minimum at power-up stage and then after a delay of tVSL  
- GND at power-down  
Please note that a pull-up resistor on CS# may ensure a safe and proper power-up/down level.  
An internal power-on reset (POR) circuit may protect the device from data corruption and inadvertent data change  
during power up state. When VCC is lower than VWI (POR threshold voltage value), the internal logic is reset and  
the flash device has no response to any command.  
For further protection on the device, if the VCC does not reach the VCC minimum level, the correct operation is not  
guaranteed. The write, erase, and program command should be sent after the below time delay:  
- tVSL after VCC reached VCC minimum level  
The device can accept read command after VCC reached VCC minimum and a time delay of tVSL.  
Please refer to the "Figure 71. Power-up Timing".  
Note:  
- To stabilize the VCC level, the VCC rail decoupled by a suitable capacitor close to package pins is recommend-  
ed. (generally around 0.1uF)  
- At power-down stage, the VCC drops below VWI level, all operations are disable and device has no response  
to any command. The data corruption might occur during this stage if a write, program, erase cycle is in pro-  
gress.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
78  
MX25U1635F  
12. ELECTRICAL SPECIFICATIONS  
Table 16. Absolute Maximum Ratings  
Rating  
Value  
Ambient Operating Temperature  
Storage Temperature  
Applied Input Voltage  
Applied Output Voltage  
VCC to Ground Potential  
Industrial grade  
-40°C to 85°C  
-65°C to 150°C  
-0.5V to VCC+0.5V  
-0.5V to VCC+0.5V  
-0.5V to 2.5V  
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 to VCC+1.0V or -1.0V for period up to 20ns.  
Figure 66. Maximum Positive Overshoot Waveform  
Figure 65. Maximum Negative Overshoot Waveform  
20ns  
0V  
VCC+1.0V  
-1.0V  
2.0V  
20ns  
Table 17. Capacitance  
TA = 25°C, f = 1.0 MHz  
Symbol Parameter  
Min.  
Typ.  
Max.  
Unit  
pF  
Conditions  
VIN = 0V  
CIN  
Input Capacitance  
6
8
COUT Output Capacitance  
pF  
VOUT = 0V  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
79  
 
MX25U1635F  
Figure 67. Input Test Waveforms and Measurement Level  
Input timing reference level  
0.8VCC  
Output timing reference level  
0.7VCC  
AC  
Measurement  
Level  
0.5VCC  
0.3VCC  
0.2VCC  
Note: Input pulse rise and fall time are <5ns  
Figure 68. Output Loading  
25K ohm  
DEVICE UNDER  
TEST  
+1.8V  
CL  
25K ohm  
CL=30pF Including jig capacitance  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
80  
 
 
 
MX25U1635F  
Table 18. DC Characteristics  
Temperature = -40 C to 85 C, VCC = 1.65V ~ 2.0V  
°
°
Symbol Parameter  
Notes  
Min.  
Typ.  
Max.  
Units Test Conditions  
VCC = VCC Max,  
uA  
ILI  
Input Load Current  
1
±2  
VIN = VCC or GND  
VCC = VCC Max,  
uA  
ILO  
Output Leakage Current  
1
1
±2  
35  
15  
VOUT = VCC or GND  
VIN = VCC or GND,  
CS# = VCC  
ISB1 VCC Standby Current  
10  
uA  
Deep Power-down  
Current  
VIN = VCC or GND,  
CS# = VCC  
ISB2  
1.5  
uA  
f=104MHz, (4 x I/O read)  
mA SCLK=0.1VCC/0.9VCC,  
SO=Open  
20  
15  
8
f=84MHz,  
mA SCLK=0.1VCC/0.9VCC,  
SO=Open  
ICC1 VCC Read  
1
1
f=33MHz,  
mA SCLK=0.1VCC/0.9VCC,  
SO=Open  
VCC Program Current  
Program in Progress,  
CS# = VCC  
ICC2  
(PP)  
20  
10  
25  
20  
mA  
VCC Write Status  
ICC3  
Program status register in  
mA  
Register (WRSR) Current  
progress, CS#=VCC  
VCC Sector/Block (32K,  
ICC4 64K) Erase Current  
(SE/BE/BE32K)  
Erase in Progress,  
CS#=VCC  
1
1
18  
20  
25  
25  
mA  
VCC Chip Erase Current  
Erase in Progress,  
CS#=VCC  
ICC5  
(CE)  
mA  
VIL  
VIH  
VOL  
Input Low Voltage  
Input High Voltage  
Output Low Voltage  
-0.5  
0.2VCC  
VCC+0.4  
0.2  
V
V
0.8VCC  
V
V
IOL = 100uA  
IOH = -100uA  
VOH Output High Voltage  
VCC-0.2  
Notes:  
1. Typical values at VCC = 1.8V, T = 25 C. These currents are valid for all product versions (package and speeds).  
°
2. Typical value is calculated by simulation.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
81  
MX25U1635F  
Table 19. AC Characteristics  
Temperature = -40 C to 85 C, VCC = 1.65V ~ 2.0V  
°
°
Symbol Alt. Parameter  
Clock Frequency for the following instructions:  
Min.  
Typ.(2)  
Max. Unit  
fSCLK  
fC FAST_READ, PP, SE, BE, BE32K, CE, DP, RES, RDP,  
WREN, WRDI, RDID, RDSR, WRSR  
D.C.  
104 MHz  
fRSCLK  
fTSCLK  
fR Clock Frequency for READ instructions (6)  
fT Clock Frequency for 2READ instructions  
fQ Clock Frequency for 4READ instructions (5)  
50  
84  
MHz  
MHz  
84/104 MHz  
Others (fSCLK)  
Normal Read (fRSCLK)  
Others (fSCLK)  
Normal Read (fRSCLK)  
4.5  
9
4.5  
9
0.1  
0.1  
5
ns  
ns  
ns  
tCH(1)  
tCL(1)  
tCLH Clock High Time  
tCLL Clock Low Time  
ns  
tCLCH(12)  
tCHCL(12)  
Clock Rise Time (peak to peak)  
Clock Fall Time (peak to peak)  
tSLCH tCSS CS# Active Setup Time (relative to SCLK)  
tCHSL CS# Not Active Hold Time (relative to SCLK)  
tDVCH tDSU Data In Setup Time  
V/ns  
V/ns  
ns  
ns  
ns  
5
2
tCHDX  
tCHSH  
tSHCH  
tDH Data In Hold Time  
5
5
5
7
ns  
ns  
ns  
ns  
CS# Active Hold Time (relative to SCLK)  
CS# Not Active Setup Time (relative to SCLK)  
Read  
tSHSL tCSH CS# Deselect Time  
Write/Erase/Program  
30  
ns  
tSHQZ(12) tDIS Output Disable Time  
8
8
6
ns  
ns  
ns  
ns  
ns  
ns  
us  
us  
us  
us  
us  
ms  
ms  
us  
ms  
Loading: 30pF  
Loading: 15pF  
Clock Low to Output Valid  
tCLQV  
tV  
Loading: 30pF/15pF  
tHO Output Hold Time  
Write Protect Setup Time  
Write Protect Hold Time  
tCLQX  
tWHSL(3)  
tSHWL(3)  
tDP(12)  
tRES1(12)  
tRES2(12)  
tRCR  
tRCP  
tRCE  
tW  
tBP  
0
20  
100  
CS# High to Deep Power-down Mode  
CS# High to Standby Mode without Electronic Signature Read  
CS# High to Standby Mode with Electronic Signature Read  
Recovery Time from Read  
Recovery Time from Program  
Recovery Time from Erase  
Write Status Register Cycle Time  
Byte-Program  
Page Program Cycle Time  
10  
30  
30  
20  
20  
12  
40  
30  
1.5  
12  
0.5  
tPP  
0.008+  
(nx0.004) (8)  
35  
tPP(7)  
Page Program Cycle Time (n bytes)  
1.5  
ms  
tSE  
tBE32  
tBE  
Sector Erase Cycle Time  
200  
1
2
20  
20  
20  
ms  
s
s
Block Erase (32KB) Cycle Time  
Block Erase (64KB) Cycle Time  
Chip Erase Cycle Time  
Erase Suspend Latency  
Program Suspend Latency  
0.2  
0.35  
10  
tCE  
s
tESL(9)  
tPSL(9)  
tPRS(10)  
tERS(11)  
us  
us  
us  
us  
Latency between Program Resume and next Suspend  
Latency between Erase Resume and next Suspend  
0.3  
0.3  
100  
400  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
82  
 
MX25U1635F  
Notes:  
1. tCH + tCL must be greater than or equal to 1/ Frequency.  
2. Typical values given for TA=25 C. Not 100% tested.  
°
3. Only applicable as a constraint for a WRSR instruction when SRWD is set at 1.  
4. Test condition is shown as "Figure 67. Input Test Waveforms and Measurement Level", "Figure 68. Output Load-  
ing".  
5. When dummy cycle=4 (In both QPI & SPI mode), maximum clock rate=84MHz; when dummy cycle=6 (In both  
QPI & SPI mode), maximum clock rate=104MHz.  
6. The maximum clock rate=33MHz when reading secured OTP area.  
7. While programming consecutive bytes, Page Program instruction provides optimized timings by selecting to pro-  
gram the whole 256 bytes or only a few bytes between 1~256 bytes.  
8. “n”=how many bytes to program. In the formula, while n=1, byte program time=12us.  
9. Latency time is required for Erase/Program Suspend until WIP bit is "0".  
10. For tPRS, minimum timing must be observed before issuing the next program suspend command. However, a  
period equal to or longer than the typical timing is required in order for the program operation to make progress.  
11. For tERS, minimum timing must be observed before issuing the next erase suspend command. However, a  
period equal to or longer than the typical timing is required in order for the erase operation to make progress.  
12. The value guaranteed by characterization, not 100% tested in production.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
83  
 
 
 
MX25U1635F  
13. OPERATING CONDITIONS  
At Device Power-Up and Power-Down  
AC timing illustrated in "Figure 69. AC Timing at Device Power-Up" and "Figure 70. Power-Down Sequence" are  
for the supply voltages and the control signals at device power-up and power-down. If the timing in the figures is ig-  
nored, the device will not operate correctly.  
During power-up and power-down, CS# needs to follow the voltage applied on VCC to keep the device not to be  
selected. The CS# can be driven low when VCC reach Vcc(min.) and wait a period of tVSL.  
Figure 69. AC Timing at Device Power-Up  
VCC(min)  
VCC  
GND  
tVR  
tSHSL  
CS#  
tSHCH  
tSLCH  
tCHSL  
tCHSH  
SCLK  
tDVCH  
tCHCL  
tCHDX  
tCLCH  
MSB IN  
LSB IN  
SI  
High Impedance  
SO  
Symbol  
Parameter  
Notes  
Min.  
Max.  
Unit  
tVR  
VCC Rise Time  
1
500000  
us/V  
Notes :  
1. Sampled, not 100% tested.  
2. For AC spec tCHSL, tSLCH, tDVCH, tCHDX, tSHSL, tCHSH, tSHCH, tCHCL, tCLCH in the figure, please refer to  
"Table 19. AC Characteristics".  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
84  
 
 
MX25U1635F  
Figure 70. Power-Down Sequence  
During power-down, CS# needs to follow the voltage drop on VCC to avoid mis-operation.  
VCC  
CS#  
SCLK  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
85  
 
 
MX25U1635F  
Figure 71. Power-up Timing  
V
CC  
V
(max)  
CC  
Chip Selection is Not Allowed  
V
(min)  
CC  
Device is fully accessible  
tVSL  
V
WI  
time  
Note: VCC (max.) is 2.0V and VCC (min.) is 1.65V.  
Table 20. Power-Up Timing and VWI Threshold  
Symbol Parameter  
Min.  
800  
1.0  
Max.  
Unit  
us  
V
tVSL(1)  
VWI(1)  
VCC(min) to CS# low (VCC Rise Time)  
Write Inhibit Voltage  
1.4  
Note: 1. These parameters are characterized only.  
13-1. Initial Delivery State  
The device is delivered with the memory array erased: all bits are set to 1 (each byte contains FFh). The Status  
Register contains 00h (all Status Register bits are 0).  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
86  
 
 
MX25U1635F  
14. ERASE AND PROGRAMMING PERFORMANCE  
PARAMETER  
Min.  
Typ.(1)  
Max. (2)  
40  
Unit  
ms  
ms  
s
Write Status Register Cycle Time  
Sector Erase Cycle Time (4KB)  
Block Erase Cycle Time (32KB)  
Block Erase Cycle Time (64KB)  
Chip Erase Cycle Time  
35  
0.2  
200  
1
0.35  
10  
2
s
20  
s
Byte Program Time (via page program command)  
Page Program Time  
12 (5)  
0.5 (5)  
100,000  
30  
us  
1.5  
ms  
cycles  
Erase/Program Cycle  
Note:  
1. Typical erase assumes the following conditions: 25 C, 1.8V, and all zero pattern.  
°
2. Under worst conditions of 85 C and 1.65V.  
°
3. System-level overhead is the time required to execute the first-bus-cycle sequence for the programming com-  
mand.  
4. The maximum chip programming time is evaluated under the worst conditions of 0 C, VCC=1.8V, and 100K cy-  
°
cle with 90% confidence level.  
5. Typical program assumes the following conditions: 25 C, 1.8V, and checkerboard pattern.  
°
15. LATCH-UP CHARACTERISTICS  
Min.  
Max.  
Input Voltage with respect to GND on all power pins, SI, CS#  
Input Voltage with respect to GND on SO  
-1.0V  
-1.0V  
2 VCCmax  
VCC + 1.0V  
+100mA  
Current  
-100mA  
Includes all pins except VCC. Test conditions: VCC = 1.8V, one pin at a time.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
87  
MX25U1635F  
16. ORDERING INFORMATION  
Please contact Macronix regional sales for the latest product selection and available form factors.  
CLOCK  
(MHz)  
PART NO.  
MX25U1635FM2I-10G  
MX25U1635FZNI-10G  
MX25U1635FZUI-10G  
MX25U1635FZBI-10G  
MX25U1635FBAI-10G  
TEMPERATURE  
-40 C to 85 C  
PACKAGE  
Remark  
8-SOP  
(200mil)  
8-WSON  
(6mmx5mm)  
8-USON  
(4mmx4mm)  
8-USON  
(4mmx3mm)  
12-BALL  
104  
°
°
104  
104  
104  
104  
-40 C to 85 C  
° °  
-40 C to 85 C  
°
°
-40 C to 85 C  
°
°
Ball Diameter  
0.25mm  
-40 C to 85 C  
°
°
WLCSP  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
88  
MX25U1635F  
17. PART NAME DESCRIPTION  
MX 25 1635F ZN  
U
I
10 G  
OPTION:  
G: RoHS Compliant & Halogen-free  
SPEED:  
10: 104MHz  
TEMPERATURE RANGE:  
I: Industrial (-40°C to 85°C)  
PACKAGE:  
M2: 8-SOP (200mil)  
ZN: 8-WSON (6mmx5mm)  
ZU: 8-USON (4mmx4mm)  
ZB: 8-USON (4mmx3mm)  
BA: 12-BALL WLCSP, Ball Diameter 0.25mm  
DENSITY & MODE:  
1635F: 16Mb  
TYPE:  
U: 1.8V  
DEVICE:  
25: Serial Flash  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
89  
MX25U1635F  
18. PACKAGE INFORMATION  
18-1. 8-pin SOP (200mil)  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
90  
MX25U1635F  
18-2. 8-land WSON (6mm x 5mm)  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
91  
 
MX25U1635F  
18-3. 8-land USON (4mm x 4mm)  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
92  
MX25U1635F  
18-4. 8-land USON (4mm x 3mm)  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
93  
MX25U1635F  
18-5. 12-ball WLCSP  
NC  
CS#  
VCC  
NC  
e
e
1
2
1
2
e
e
SO/SIO1 RESET#/SIO3  
WP#/SIO2 SCLK  
NC  
GND  
SI/SIO0 NC  
e
e
1
2
1
2
e
e
Please contact local Macronix sales channel for complete package dimensions.  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
94  
MX25U1635F  
19. REVISION HISTORY  
Revision No. Description  
Page  
Date  
1.0  
1. Removed "Advanced Information"  
P4  
FEB/22/2013  
2. Added 8-USON (4mmx3mm) package informarion  
P5,8,85,86,90  
1.1  
1. Modified Package Information  
P88~90  
APR/25/2013  
OCT/23/2013  
1.2  
1. Added DREAD function  
2. Added QREAD function  
3. Updated DREAD(1-1-2) / QREAD(1-1-4) in SFDP Table  
4. Modified Data Retention value  
5. Modified Erase Suspend & Figure 55  
6. Added note on WP# setup  
P7,14,17,39  
P7,14,17,41  
P72,73  
P4  
P66,67  
P35  
7. Modified VCC to Ground Potential  
P78  
8. Updated Erase time, Consumption current and Page Program P4  
9. Updated ISB1, ISB2, ICC1, ICC3 and ICC4 in DC Table  
10. Updated tBP, tSE, tBE32, tBE and tCE in AC Table  
11. Updated Erase time and Byte Program time  
1. Added WLCSP package and Part No.  
1. Removed Advanced Information of MX25U1635FZNI-10G and P87  
MX25U1635FZUI-10G  
P80  
P81  
P86  
1.3  
1.4  
P5,8,87,88,93 APR/07/2014  
JUN/25/2014  
1.5  
1. Updated Block Diagram  
P9  
MAR/17/2015  
2. Updated Note 6 of SFDP Tables  
P76  
3. Added program/erase suspend/resume parameters  
4. Updated program/erase suspend/resume descriptions  
5. Updated notes of Table 19. AC Characteristics  
6. Added Write Protection Selection (WPSEL) Sequence figure  
7. Added descriptions of Security Register E_FAIL/P_FAIL,  
ESB/PSB  
P82-83  
P66-69  
P82-83  
P61  
P59  
8. Updated Write Protection Selection (WPSEL) descriptions  
1. Updated tVR values  
2. Added a statement for product ordering information  
3. Modified "9-22. Page Program (PP)" descriptions  
4. Content modification.  
P60  
P84  
P88  
P54  
P20,46  
P8  
1.6  
JAN/17/2017  
5. Added the note for the internal pull up status of  
RESET#/SIO3 and WP#/SIO2  
6. Updated "18-2. 8-land WSON (6mm x 5mm)"  
P91  
P/N: PM1901  
Rev. 1.6, January 17, 2017  
95  
MX25U1635F  
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-2017. All rights reserved, including the trademarks and tradename  
thereof, such as Macronix, MXIC, MXIC Logo, MX Logo, Integrated Solutions Provider, Nbit, Macronix NBit, eLiteFlash,  
HybridNVM, HybridFlash, HybridXFlash, XtraROM, Phines, KH Logo, BE-SONOS, KSMC, Kingtech, MXSMIO, Macronix  
vEE, Macronix MAP, Rich Book, Rich TV, OctaRAM, OctaBus, OctaFlash 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.  
96  

相关型号:

SI9130DB

5- and 3.3-V Step-Down Synchronous Converters

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9135LG-T1

SMBus Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9135LG-T1-E3

SMBus Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9135_11

SMBus Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9136_11

Multi-Output Power-Supply Controller

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9130CG-T1-E3

Pin-Programmable Dual Controller - Portable PCs

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9130LG-T1-E3

Pin-Programmable Dual Controller - Portable PCs

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9130_11

Pin-Programmable Dual Controller - Portable PCs

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9137

Multi-Output, Sequence Selectable Power-Supply Controller for Mobile Applications

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9137DB

Multi-Output, Sequence Selectable Power-Supply Controller for Mobile Applications

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9137LG

Multi-Output, Sequence Selectable Power-Supply Controller for Mobile Applications

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY

SI9122E

500-kHz Half-Bridge DC/DC Controller with Integrated Secondary Synchronous Rectification Drivers

Warning: Undefined variable $rtag in /www/wwwroot/website_ic37/www.icpdf.com/pdf/pdf/index.php on line 217
-
VISHAY