S70FS01GSAGBHM210 [INFINEON]

Quad SPI Flash;
S70FS01GSAGBHM210
型号: S70FS01GSAGBHM210
厂家: Infineon    Infineon
描述:

Quad SPI Flash

文件: 总172页 (文件大小:1241K)
中文:  中文翻译
下载:  下载PDF数据表文档文件
S70FS01GS  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Features  
• SPI with multi-I/O  
- SPI clock polarity and phase modes 0 and 3  
- DDR  
- Extended addressing: 24- or 32-bit address options  
- Serial command subset and footprint compatible with S25FL1-K, S25FL-P, and S25FL-S SPI families  
- Multi I/O command subset and footprint compatible with S25FL-P, S25FL1-K, and S25FL-S SPI families  
• Read  
- Commands: Normal, Fast, Dual I/O, Quad I/O, DDR Quad I/O  
- Modes: Burst wrap, Quad peripheral interface (QPI)  
- Serial flash discoverable parameters (SFDP) and common flash interface (CFI), for configuration information.  
• Program  
- 256 or 512 bytes page programming buffer  
- Program suspend and resume  
- Automatic error correcting code (ECC) – Internal hardware ECC with single bit error correction  
• Erase  
- Hybrid sector option  
• Physical set of eight 4 KB sectors and one 224 KB sector at the top or bottom of address space with all  
remaining sectors of 256 KB  
- Uniform sector option  
• Physical uniform 256 KB blocks  
- Erase suspend and resume  
- Erase status evaluation  
- 100,000 Program-erase cycles on any sector, minimum  
- 20 year data retention, minimum  
• Security features  
- OTP array of 1024 bytes  
- Block protection:  
• Status Register bits to control protection against program or erase of a contiguous range of sectors.  
• Hardware and software control options  
- Advanced sector protection (ASP)  
• Individual sector protection controlled by boot code or password  
• Option for password control of read access  
• Technology  
- 65-nm MIRRORBIT™ Technology with Eclipse architecture  
• Single supply voltage with CMOS I/O  
- 1.7 V to 2.0 V  
• Temperature range  
- Industrial (–40 °C to +85 °C)  
- Industrial Plus (–40 °C to +105 °C)  
- Automotive, AEC-Q100 grade 3 (–40 °C to +85 °C)  
- Automotive, AEC-Q100 grade 2 (–40 °C to +105 °C)  
- Automotive, AEC-Q100 grade 1 (–40 °C to +125 °C)  
Datasheet  
www.infineon.com  
Please read the Important Notice and Warnings at the end of this document  
page 1 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Logic block diagram  
• Packages (all Pb-free)  
- 16-lead SOIC 300 mil  
- BGA-24 6 8 mm  
• 5 5 ball footprint  
Logic block diagram  
S70FS01GS Device  
S25FS512S Die 1  
SRAM  
CS#  
SCK  
MirrorBit Array  
SI/IO0  
Y Decoders  
Data Latch  
I/O  
SO/IO1  
WP#/IO2  
Control  
Logic  
RESET#/IO3  
Data Path  
S25FS512S Die 2  
SRAM  
MirrorBit Array  
Y Decoders  
Data Latch  
I/O  
Control  
Logic  
Data Path  
Datasheet  
2 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Performance summary  
Performance summary  
Maximum Read rates  
Command  
Read  
Fast Read  
Dual Read  
Clock rate (MHz)  
MBps  
6.25  
16.5  
33  
66  
80  
50  
133  
133  
133  
80  
Quad Read  
DDR Quad I/O Read  
Typical Program and Erase rates  
Operation  
Page Programming (256-bytes page buffer)  
Page Programming (512-bytes page buffer)  
4-KB Physical Sector Erase (Hybrid Sector Option)  
256-KB Sector Erase (Uniform Logical Sector Option)  
KBps  
711  
1078  
17  
275  
Typical current consumption, –40 °C to +85 °C  
Operation  
Current (mA)  
Serial Read 50 MHz  
Serial Read 133 MHz  
Quad Read 133 MHz  
Quad DDR Read 80 MHz  
Program  
10  
20  
60  
70  
60  
Erase  
60  
Standby  
Deep Power Down (DPD)  
0.07  
0.006  
Datasheet  
3 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Table of contents  
Table of contents  
Features ...........................................................................................................................................1  
Logic block diagram ..........................................................................................................................2  
Performance summary ......................................................................................................................3  
Table of contents...............................................................................................................................4  
1 Overview .......................................................................................................................................6  
1.1 General description ................................................................................................................................................6  
1.2 Migration notes .......................................................................................................................................................6  
1.3 Glossary ...................................................................................................................................................................9  
2 SPI with multiple input / output (SPI-MIO) ......................................................................................11  
3 Signal descriptions .......................................................................................................................12  
3.1 Input/Output summary ........................................................................................................................................12  
3.2 Multiple Input / Output (MIO)...............................................................................................................................13  
3.3 Serial Clock (SCK)..................................................................................................................................................13  
3.4 Chip Select (CS#)...................................................................................................................................................13  
3.5 Serial Input (SI) / IO0.............................................................................................................................................13  
3.6 Serial Output (SO) / IO1 ........................................................................................................................................13  
3.7 Write Protect (WP#) / IO2......................................................................................................................................14  
3.8 IO3 / RESET#..........................................................................................................................................................14  
3.9 Voltage Supply (VCC) .............................................................................................................................................14  
3.10 Supply and Signal Ground (VSS) .........................................................................................................................14  
3.11 Not Connected (NC) ............................................................................................................................................14  
3.12 Reserved for Future Use (RFU) ...........................................................................................................................15  
3.13 Do Not Use (DNU)................................................................................................................................................15  
3.14 Block diagrams ...................................................................................................................................................15  
4 Signal protocols............................................................................................................................17  
4.1 SPI clock modes ....................................................................................................................................................17  
4.2 Command Protocol...............................................................................................................................................18  
4.3 Interface states .....................................................................................................................................................22  
4.4 Configuration Register effects on the interface ..................................................................................................26  
4.5 Data protection.....................................................................................................................................................26  
5 Electrical specifications.................................................................................................................27  
5.1 Absolute maximum ratings ..................................................................................................................................27  
5.2 Thermal resistance ...............................................................................................................................................27  
5.3 Latchup characteristics ........................................................................................................................................27  
5.4 Operating ranges ..................................................................................................................................................28  
5.5 Power-up and power-down..................................................................................................................................29  
5.6 DC characteristics .................................................................................................................................................31  
6 Timing specifications ....................................................................................................................34  
6.1 Key to switching waveforms.................................................................................................................................34  
6.2 AC test conditions .................................................................................................................................................34  
6.3 Reset ......................................................................................................................................................................36  
6.4 SDR AC characteristics..........................................................................................................................................39  
6.5 DDR AC characteristics .........................................................................................................................................42  
7 Physical interface .........................................................................................................................45  
7.1 Connection diagrams ...........................................................................................................................................45  
7.2 Physical diagrams .................................................................................................................................................46  
8 Address space maps ......................................................................................................................48  
8.1 Overview................................................................................................................................................................48  
8.2 Flash memory array ..............................................................................................................................................48  
8.3 ID-CFI address space.............................................................................................................................................49  
8.4 JEDEC JESD216 serial flash discoverable parameters (SFDP) space .................................................................49  
Datasheet  
4 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Table of contents  
8.5 OTP address space................................................................................................................................................50  
8.6 Error correction code (ECC)..................................................................................................................................51  
8.7 Registers................................................................................................................................................................52  
9 Data Protection ............................................................................................................................74  
9.1 Secure Silicon Region (OTP).................................................................................................................................74  
9.2 Write Enable Command........................................................................................................................................75  
9.3 Block Protection ...................................................................................................................................................75  
9.4 Advanced sector protection .................................................................................................................................77  
9.5 Recommended protection process .....................................................................................................................82  
10 Commands .................................................................................................................................83  
10.1 Command set summary .....................................................................................................................................85  
10.2 Identification commands ...................................................................................................................................93  
10.3 Register Access commands ................................................................................................................................95  
10.4 Read Memory Array commands .......................................................................................................................105  
10.5 Program Flash Array Commands .....................................................................................................................113  
10.6 Erase Flash Array Commands...........................................................................................................................115  
10.7 One Time Program Array Commands ..............................................................................................................124  
10.8 Advanced Sector Protection Commands ........................................................................................................125  
10.9 Reset Commands ..............................................................................................................................................131  
10.10 DPD Commands ..............................................................................................................................................133  
11 Data Integrity ........................................................................................................................... 135  
11.1 Erase Endurance ...............................................................................................................................................135  
11.2 Data Retention ..................................................................................................................................................135  
12 Embedded Algorithm Performance Tables .................................................................................. 136  
13 Software Interface Reference..................................................................................................... 137  
13.1 Serial Flash Discoverable Parameters (SFDP) Address Map ...........................................................................137  
13.2 Device ID and Common Flash Interface (ID-CFI) Address Map .......................................................................141  
13.3 Initial Delivery State..........................................................................................................................................162  
13.4 FS01GS Behavior and Software Modifications ................................................................................................163  
14 Ordering Information ................................................................................................................ 166  
14.1 Ordering Part Number ......................................................................................................................................166  
14.2 Valid Combinations — Standard ......................................................................................................................167  
14.3 Valid Combinations — Automotive Grade / AEC-Q100....................................................................................167  
Revision history ............................................................................................................................ 168  
Datasheet  
5 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Overview  
1
Overview  
1.1  
General description  
The FS-S Family devices are Flash non-volatile memory products using:  
• MIRRORBIT™ technology - that stores two data bits in each memory array transistor  
• Eclipse architecture - that dramatically improves program and erase performance  
• 65-nm process lithography  
The FS-S family connects to a host system via a SPI. Traditional SPI single bit serial input and output (Single I/O  
or SIO) is supported as well as optional two bit (Dual I/O or DIO) and four bit wide Quad I/O (QIO) or QPI, also  
known as quad peripheral interface (QPI) serial commands. This multiple width interface is called SPI Multi-I/O  
or MIO. In addition, there are DDR read commands for QIO and QPI that transfer address and read data on both  
edges of the clock.  
The FS-S Eclipse architecture features a page programming buffer that allows up to 512-bytes to be programmed  
in one operation, resulting in faster effective programming and erase than prior generation SPI program or erase  
algorithms.  
Executing code directly from Flash memory is often called eXecute-In-Place (XIP). By using FS-S family devices at  
the higher clock rates supported, with Quad or DDR-Quad commands, the instruction read transfer rate can  
match or exceed traditional parallel interface, asynchronous, NOR Flash memories, while reducing signal count  
dramatically.  
The FS-S family products offer high densities coupled with the flexibility and fast performance required by a  
variety of mobile or embedded applications. They are an excellent solution for systems with limited space, signal  
connections, and power. They are ideal for code shadowing to RAM, executing code directly (XIP), and storing  
reprogrammable data.  
The S70FS01GS device is a dual die stack of two FS512S die.  
1.2  
Migration notes  
1.2.1  
Features comparison  
The FS-S family is command subset and footprint compatible with prior generation FL-S, FL1-K and FL-P families.  
However, the power supply and interface voltages are nominal 1.8 V.  
Table 1  
SPI families comparison  
Parameter  
FS-S  
65-nm  
MIRRORBIT™ Eclipse  
2H2015  
FL-S  
65nm  
MIRRORBIT™ Eclipse  
2H2011  
Technology node  
Architecture  
Release Date  
Density  
1Gb  
1GB  
Bus width  
x1, x2, x4  
x1, x2, x4  
Supply voltage  
1.7 V–2.0 V  
2.7 V–3.6 V / 1.65 V–3.6 V VIO  
6 MBps (50 MHz)  
17 MBps (133 MHz)  
26 MBps (104 MHz)  
52 MBps (104 MHz)  
Normal read speed (SDR)  
Fast read speed (SDR)  
Dual read speed (SDR)  
Quad read speed (SDR)  
6 MBps (50 MHz)  
16.5 MBps (133 MHz)  
33 MBps (133 MHz)  
66 MBps (133 MHz)  
Notes  
1. Only 128 Mb/256 Mb density FL-S devices have 4 KB parameter sector option.  
2. 512 Mb/1 Gb FL-S devices support 256 KB sector only.  
3. Refer to individual datasheets for further details.  
Datasheet  
6 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Overview  
Table 1  
SPI families comparison (Continued)  
Parameter  
FS-S  
80 MBps (80 MHz)  
256 B / 512 B  
256 KB  
FL-S  
80 MBps (80 MHz)  
256 B / 512 B  
256 KB  
Quad Read Speed (DDR)  
Program Buffer Size  
Erase Sector Size  
Parameter Sector Size  
Sector Erase Rate (typ.)  
4 KB (option)  
500 KBps  
4 KB (option)  
500 KBps  
0.71 MBps (256B)  
1.08 MBps (512B)  
1.0 MBps (256B)  
1.5 MBps (512B)  
Page Programming Rate (typ.)  
OTP  
1024B  
1024B  
Advanced Sector Protection  
Auto Boot Mode  
Yes  
No  
Yes  
Yes  
Erase Suspend/Resume  
Program Suspend/Resume  
Operating Temperature  
Yes  
Yes  
Yes  
Yes  
–40 °C to +85 °C / +105 °C / +125 °C  
–40 °C to +85 °C / +105 °C  
Notes  
1. Only 128 Mb/256 Mb density FL-S devices have 4 KB parameter sector option.  
2. 512 Mb/1 Gb FL-S devices support 256 KB sector only.  
3. Refer to individual datasheets for further details.  
1.2.2  
Known differences from prior generations  
Error reporting  
1.2.2.1  
The FS-S and FL-S families have error reporting status bits for program and erase operations. These can be set  
when there is an internal failure to program or erase, or when there is an attempt to program or erase a protected  
sector. In these cases, the program or erase operation did not complete as requested by the command. The  
P_ERR or E_ERR bits and the WIP bit will be set to and remain 1 in SR1V. The Clear Status Register command must  
be sent to clear the errors and return the device to standby state.  
1.2.2.2  
Secure Silicon Region (OTP)  
The FS-S size and format (address map) of the one time program area is different from FL-K and FL-P generations.  
The method for protecting each portion of the OTP area is different. For additional details, see “Secure Silicon  
Region (OTP)” on page 74.  
1.2.2.3  
Configuration Register Freeze Bit  
The Configuration Register-1 Freeze Bit CR1V[0], locks the state of the Block Protection bits (SR1NV[4:2] &  
SR1V[4:2]), TBPARM_O bit (CR1NV[2]), and TBPROT_O bit (CR1NV[5]), as in prior generations. In the FS-S and FL-S  
families the Freeze Bit also locks the state of the configuration register-1 BPNV_O bit (CR1NV[3]), and the Secure  
Silicon Region (OTP) area.  
1.2.2.4  
Sector Erase commands  
The command for erasing a 4 KB sector is supported only for use on 4 KB parameter sectors at the top or bottom  
of the FS-S device address space.  
The command for erasing an 8 KB area (two 4 KB sectors) is not supported.  
The command for erasing a 32 KB area (eight 4 KB sectors) is not supported.  
1.2.2.5  
Deep Power Down (DPD)  
The DPD function is supported in the FS-S family devices.  
Datasheet  
7 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Overview  
1.2.2.6  
WRR Single Register Write  
In some legacy SPI devices, a Write Registers (WRR) command with only one data byte would update Status  
Register 1 and clear some bits in Configuration Register 1, including the Quad Mode bit. This could result in  
unintended exit from Quad Mode. The FS-S Family only updates Status Register 1 when a single data byte is  
provided. The Configuration Register 1 is not modified in this case.  
1.2.2.7  
Hold Input not supported  
In some legacy SPI devices, the IO3 input has an alternate function as a HOLD# input used to pause information  
transfer without stopping the serial clock. This function is not supported in the FS-S family.  
1.2.2.8  
Separate Reset Input not supported  
In some legacy SPI devices, a separate hardware RESET# input is supported in packages having more than 8  
connections. The FS-S family does not support a separate RESET# input. The FS-S family provides an alternate  
function for the IO3 input as a RESET# input. When the CS# signal is HIGH and the IO3/Reset feature is enabled,  
the IO3/RESET# input is used to initiate a hardware reset when the input goes LOW.  
1.2.2.9  
Other legacy commands not supported  
• Autoboot Related Commands  
• Bank Address Related Commands  
• Dual Output Read  
• Quad Output Read  
• Quad Page Program (QPP) - replaced by Page Program in QPI Mode  
• DDR Fast Read  
• DDR Dual I/O Read  
• Write Register  
• Read Configuration Register  
• Read Status Register 1  
• Read Status Register 2  
• Program NV Data Learning Register  
• ASP Program  
• Password Program  
• PPB Erase  
• Erase Program Suspend (B0h)  
• Erase Program Resume (30h)  
Datasheet  
8 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Overview  
1.2.2.10  
New features  
The FS-S family introduces new features to Infineon SPI category memories:  
• Single 1.8 V power supply for core and I/O voltage.  
• Configurable initial read latency (number of dummy cycles) for faster initial access time or higher clock rate  
read commands  
• QPI (QPI, 4-4-4) read mode in which all transfers are 4 bits wide, including instructions  
• JEDEC JESD216 standard, serial flash discoverable parameters (SFDP) that provide device feature and  
configuration information.  
• Evaluate Erase Status command to determine if the last erase operation on a sector completed successfully.  
This command can be used to detect incomplete erase due to power loss or other causes. This command can  
be helpful to Flash File System software in file system recovery after a power loss.  
• Advanced Sector Protection (ASP) Permanent Protection. A bit is added to the ASP register to provide the option  
to make protection of the Persistent Protection Bits (PPB) permanent. Also, when one of the two ASP modes is  
selected, all OTP configuration bits in all registers are protected from further programming so that all OTP  
configuration settings are made permanent. The OTP address space is not protected by the selection of an ASP  
Mode. The Freeze bit (CR1V[0]) may be used to protect the OTP Address Space.  
• Single Chip Select (CS#) Dual Die Package (DDP) density option that uses two FS512S devices stacked within  
the same package to provide 1Gb of memory. The the two devices share the CS# input to provide a contiguous  
1 Gb (128 MB) address space. However, there are some behavior and software differences from the other  
members of the FS-S family that are described in “FS01GS Behavior and Software Modificationson page 163.  
1.3  
Glossary  
BCD = Binary Coded Decimal. A value in which each 4 bit nibble represents a decimal numeral.  
Command = All information transferred between the host system and memory during one period while CS# is  
LOW. This includes the instruction (sometimes called an operation code or opcode) and any required address,  
mode bits, latency cycles, or data.  
DDP = Dual Die Package = Two die stacked within the same package to increase the memory capacity of a single  
package. Often also referred to as a Multi-Chip Package (MCP)  
DDR = Double Data Rate = When input and output are latched on every edge of SCK.  
ECC = ECC Unit = 16 byte aligned and length data groups in the main Flash array and OTP array, each of which  
has its own hidden ECC syndrome to enable error correction on each group.  
Flash = The name for a type of Electrical Erase Programmable Read Only Memory (EEPROM) that erases large  
blocks of memory bits in parallel, making the erase operation much faster than early EEPROM.  
High = A signal voltage level VIH or a logic level representing a binary one (“1”).  
Instruction = The 8 bit code indicating the function to be performed by a command (sometimes called an  
operation code or opcode). The instruction is always the first 8 bits transferred from host system to the memory  
in any command.  
Low = A signal voltage level VIL or a logic level representing a binary zero (“0”).  
LSb = Least Significant Bit = Generally the right most bit, with the lowest order of magnitude value, within a  
group of bits of a register or data value.  
MSb = Most Significant Bit = Generally the left most bit, with the highest order of magnitude value, within a  
group of bits of a register or data value.  
N/A = Not applicable. A value is not relevant to situation described.  
Non-volatile = No power is needed to maintain data stored in the memory.  
Datasheet  
9 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Overview  
OPN = Ordering part number = The alphanumeric string specifying the memory device type, density, package,  
factory non-volatile configuration, and so on used to select the desired device.  
Page = 512-byte or 256-byte aligned and length group of data. The size assigned for a page depends on the  
Ordering Part Number.  
PCB - Printed circuit board  
Register bit references = Are in the format: Register_name[bit_number] or Register_name[bit_range_MSB:  
bit_range_LSB]  
SDR = Single data rate = When input is latched on the rising edge and output on the falling edge of SCK.  
Sector = Erase unit size; depending on device model and sector location this may be 4 KB, 64 KB, or 256 KB  
Write = An operation that changes data within volatile or non-volatile registers bits or non-volatile Flash  
memory. When changing non-volatile data, an erase and reprogramming of any unchanged non-volatile data  
is done, as part of the operation, such that the non-volatile data is modified by the write operation, in the same  
way that volatile data is modified – as a single operation. The non-volatile data appears to the host system to  
be updated by the single write command, without the need for separate commands for erase and reprogram  
of adjacent, but unaffected data.  
Datasheet  
10 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
SPI with multiple input / output (SPI-MIO)  
2
SPI with multiple input / output (SPI-MIO)  
Many memory devices connect to their host system with separate parallel control, address, and data signals that  
require a large number of signal connections and larger package size. The large number of connections increase  
power consumption due to so many signals switching and the larger package increases cost.  
The FS-S Family reduces the number of signals for connection to the host system by serially transferring all  
control, address, and data information over 4 to 6 signals. This reduces the cost of the memory package, reduces  
signal switching power, and either reduces the host connection count or frees host connectors for use in  
providing other features.  
The FS-S family uses the industry standard single bit SPI and also supports optional extension commands for two  
bit (Dual) and four bit (Quad) wide serial transfers. This multiple width interface is called SPI multi-I/O or SPI-MIO.  
Datasheet  
11 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal descriptions  
3
Signal descriptions  
3.1  
Input/Output summary  
Table 2  
Signal name  
SCK  
Signal List  
Type  
Description  
Input  
Input  
I/O  
Serial Clock  
Chip Select  
CS#  
SI / IO0  
SO / IO1  
Serial Input for single bit data commands or IO0 for Dual or Quad commands.  
Serial Output for single bit data commands. IO1 for Dual or Quad commands.  
I/O  
Write Protect when not in Quad Mode (CR1V[1] = 0 and SR1NV[7] = 1).  
IO2 when in Quad Mode (CR1V[1] = 1).  
The signal has an internal pull-up resistor and may be left unconnected in the  
host system if not used for Quad commands or write protection. If write  
protection is enabled by SR1NV[7] = 1 and CR1V[1] = 0, the host system is  
required to drive WP# HIGH or LOW during a WRAR command.  
IO3 in Quad-I/O Mode, when Configuration Register-1 QUAD bit, CR1V[1] = 1, and  
CS# is LOW.  
RESET# when enabled by CR2V[5] = 1 and not in Quad-I/O Mode, CR1V[1] = 0, or  
when enabled in Quad Mode, CR1V[1] = 1 and CS# is HIGH.  
The signal has an internal pull-up resistor and may be left unconnected in the  
host system if not used for Quad commands or RESET#.  
WP# / IO2  
I/O  
I/O  
IO3 / RESET#  
VCC  
VSS  
Supply  
Supply  
Power Supply.  
Ground.  
Not Connected. No device internal signal is connected to the package  
connector nor is there any future plan to use the connector for a signal. The  
connection may safely be used for routing space for a signal on a PCB. However,  
NC  
Unused  
any signal connected to an NC must not have voltage levels higher than VCC  
.
Reserved for Future Use. No device internal signal is currently connected to  
the package connector but there is potential future use of the connector for a  
RFU  
Reserved signal. It is recommended to not use RFU connectors for PCB routing channels  
so that the PCB may take advantage of future enhanced features in compatible  
footprint devices.  
Do Not Use. A device internal signal may be connected to the package  
connector. The connection may be used by Cypress for test or other purposes  
and is not intended for connection to any host system signal. Any DNU signal  
Reserved related function will be inactive when the signal is at VIL. The signal has an  
internal pull-down resistor and may be left unconnected in the host system or  
may be tied to VSS. Do not use these connections for PCB signal routing  
channels. Do not connect any host system signal to this connection.  
DNU  
Datasheet  
12 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal descriptions  
3.2  
Multiple Input / Output (MIO)  
Traditional SPI single bit wide commands (Single or SIO) send information from the host to the memory only on  
the Serial Input (SI) signal. Data may be sent back to the host serially on the Serial Output (SO) signal.  
Dual or Quad Input / Output (I/O) commands send instructions to the memory only on the SI/IO0 signal. Address  
or data is sent from the host to the memory as bit pairs on IO0 and IO1 or four bit (nibble) groups on IO0, IO1, IO2,  
and IO3. Data is returned to the host similarly as bit pairs on IO0 and IO1 or four bit (nibble) groups on IO0, IO1,  
IO2, and IO3.  
QPI Mode transfers all instructions, address, and data from the host to the memory as four bit (nibble) groups on  
IO0, IO1, IO2, and IO3. Data is returned to the host similarly as four bit (nibble) groups on IO0, IO1, IO2, and IO3.  
3.3  
Serial Clock (SCK)  
This input signal provides the synchronization reference for the SPI interface. Instructions, addresses, or data  
input are latched on the rising edge of the SCK signal. Data output changes after the falling edge of SCK, in SDR  
commands, and after every edge in DDR commands.  
3.4  
Chip Select (CS#)  
The chip select signal indicates when a command is transferring information to or from the device and the other  
signals are relevant for the memory device.  
When the CS# signal is at the logic HIGH state, the device is not selected and all input signals are ignored and all  
output signals are high impedance If the IO3 / RESET# option is enabled see “IO3 / RESET#” on page 14 for CS#  
signal operation. The device will be in the Standby Power Mode, unless an internal embedded operation is in  
progress. An embedded operation is indicated by the Status Register-1 Write-In-Progress bit (SR1V[1]) set to 1,  
until the operation is completed. Some example embedded operations are: Program, Erase, or Write Registers  
(WRAR) operations.  
Driving the CS# input to the logic LOW state enables the device, placing it in the Active Power Mode. After  
Power-up, a falling edge on CS# is required prior to the start of any command.  
3.5  
Serial Input (SI) / IO0  
This input signal is used to transfer data serially into the device. It receives instructions, addresses, and data to  
be programmed. Values are latched on the rising edge of serial SCK clock signal.  
SI becomes IO0 - an input and output during Dual and Quad commands for receiving instructions, addresses, and  
data to be programmed (values latched on rising edge of serial SCK clock signal) as well as shifting out data (on  
the falling edge of SCK, in SDR commands, and on every edge of SCK, in DDR commands).  
3.6  
Serial Output (SO) / IO1  
This output signal is used to transfer data serially out of the device. Data is shifted out on the falling edge of the  
serial SCK clock signal.  
SO becomes IO1 - an input and output during Dual and Quad commands for receiving addresses, and data to be  
programmed (values latched on rising edge of serial SCK clock signal) as well as shifting out data (on the falling  
edge of SCK, in SDR commands, and on every edge of SCK, in DDR commands).  
Datasheet  
13 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal descriptions  
3.7  
Write Protect (WP#) / IO2  
When WP# is driven LOW (VIL), during a WRAR command and while the Status Register Write Disable (SRWD_NV)  
bit of Status Register-1 (SR1NV[7]) is set to a 1, it is not possible to write to Status Register-1 or Configuration  
Register-1 related registers. In this situation, a WRAR command is ignored, a WRAR command selecting SR1NV,  
SR1V, CR1NV, or CR1V is ignored, and no error is set.  
This prevents any alteration of the Block Protection settings. As a consequence, all the data bytes in the memory  
area that are protected by the Block Protection feature are also hardware protected against data modification if  
WP# is LOW during a WRAR command with SRWD_NV set to 1.  
The WP# function is not available when the Quad Mode is enabled (CR1V[1] = 1). The WP# function is replaced by  
IO2 for input and output during Quad Mode for receiving addresses, and data to be programmed (values are  
latched on rising edge of the SCK signal) as well as shifting out data (on the falling edge of SCK, in SDR commands,  
and on every edge of SCK, in DDR commands).  
WP# has an internal pull-up resistance; when unconnected, WP# is at VIH and may be left unconnected in the host  
system if not used for Quad Mode or protection.  
3.8  
IO3 / RESET#  
IO3 is used for input and output during Quad Mode (CR1V[1] = 1) for receiving addresses, and data to be  
programmed (values are latched on rising edge of the SCK signal) as well as shifting out data (on the falling edge  
of SCK, in SDR commands, and on every edge of SCK, in DDR commands).  
The IO3 / RESET# signal may also be used to initiate the hardware reset function when the reset feature is enabled  
by writing Configuration Register-2 non-volatile bit 5 (CR2V[5] = 1). The input is only treated as RESET# when the  
device is not in Quad-I/O Mode, CR1V[1] = 0, or when CS# is HIGH. When Quad I/O Mode is in use, CR1V[1] = 1, and  
the device is selected with CS# LOW, the IO3 / RESET# is used only as IO3 for information transfer. When CS# is  
HIGH, the IO3 / RESET# is not in use for information transfer and is used as the RESET# input. By conditioning the  
reset operation on CS# HIGH during Quad Mode, the reset function remains available during Quad Mode.  
When the system enters a reset condition, the CS# signal must be driven high as part of the reset process and the  
IO3 / RESET# signal is driven LOW. When CS# goes HIGH the IO3 / RESET# input transitions from being IO3 to being  
the RESET# input. The reset condition is then detected when CS# remains HIGH and the IO3 / RESET# signal  
remains LOW for tRP. If a reset is not intended, the system is required to actively drive IO3 / Reset# to HIGH along  
with CS# being driven HIGH at the end of a transfer of data to the memory. Following transfers of data to the host  
system, the memory will drive IO3 HIGH during tCS. This will ensure that IO3 / Reset is not left floating or being  
pulled slowly to HIGH by the internal or an external passive pull-up. Thus, an unintended reset is not triggered by  
the IO3 / RESET# not being recognized as HIGH before the end of tRP  
.
The IO3 / RESET# signal is unused when the reset feature is disabled (CR2V[5] = 0).  
The IO3 / RESET# signal has an internal pull-up resistor and may be left unconnected in the host system if not  
used for Quad Mode or the reset function. The internal pull-up will hold IO3 / Reset HIGH after the host system  
has actively driven the signal HIGH and then stops driving the signal.  
Note that IO3 / Reset# cannot be shared by more than one SPI-MIO memory if any of them are operating in Quad  
I/O Mode as IO3 being driven to or from one selected memory may look like a reset signal to a second  
non-selected memory sharing the same IO3 / RESET# signal.  
3.9  
Voltage Supply (VCC)  
VCC is the voltage source for all device internal logic. It is the single voltage used for all device internal functions  
including read, program, and erase.  
3.10  
Supply and Signal Ground (VSS)  
VSS is the common voltage drain and ground reference for the device core, input signal receivers, and output  
drivers.  
3.11  
Not Connected (NC)  
No device internal signal is connected to the package connector nor is there any future plan to use the connector  
for a signal. The connection may safely be used for routing space for a signal on a PCB.  
Datasheet  
14 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal descriptions  
3.12  
Reserved for Future Use (RFU)  
No device internal signal is currently connected to the package connector but there is potential future use of the  
connector. It is recommended to not use RFU connectors for PCB routing channels so that the PCB may take  
advantage of future enhanced features in compatible footprint devices.  
3.13  
Do Not Use (DNU)  
A device internal signal may be connected to the package connector. The connection may be used by Cypress for  
test or other purposes and is not intended for connection to any host system signal. Any DNU signal related  
function will be inactive when the signal is at VIL. The signal has an internal pull-down resistor and may be left  
unconnected in the host system or may be tied to VSS. Do not use these connections for PCB signal routing  
channels. Do not connect any host system signal to these connections.  
3.14  
Block diagrams  
RESET#  
WP#  
RESET#  
WP#  
SI  
SO  
SI  
SO  
SCK  
SCK  
CS2#  
CS2#  
CS1#  
CS1#  
FS01GS  
Flash  
FS01GS  
Flash  
SPI  
Bus Master  
Figure 1  
Bus master and memory devices on the SPI bus - Single bit data path  
RESET#  
RESET#  
WP#  
WP#  
IO1  
IO1  
IO0  
IO0  
SCK  
SCK  
CS2#  
CS2#  
CS1#  
CS1#  
FS01GS  
Flash  
FS01GS  
Flash  
SPI  
Bus Master  
Figure 2  
Bus master and memory devices on the SPI bus - Dual bit data path  
Datasheet  
15 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal descriptions  
IO3 / RESET#  
IO2  
RESET# / IO3  
IO2  
IO1  
IO0  
SCK  
IO1  
IO0  
SCK  
CS1#  
CS1#  
FS01GS  
Flash  
SPI  
Bus Master  
Figure 3  
Bus master and memory devices on the SPI bus - Quad bit data path  
Datasheet  
16 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
4
Signal protocols  
4.1  
SPI clock modes  
4.1.1  
SDR  
The FS-S family can be driven by an embedded microcontroller (bus master) in either of the two following  
clocking modes.  
Mode 0 with Clock Polarity (CPOL) = 0 and, Clock Phase (CPHA) = 0  
Mode 3 with CPOL = 1 and, CPHA = 1  
For these two modes, input data into the device is always latched in on the rising edge of the SCK signal and the  
output data is always available from the falling edge of the SCK clock signal.  
The difference between the two modes is the clock polarity when the bus master is in Standby Mode and not  
transferring any data.  
• SCK will stay at logic LOW state with CPOL = 0, CPHA = 0  
• SCK will stay at logic HIGH state with CPOL = 1, CPHA = 1  
POL=0_CPHA=0_SCLK  
POL=1_CPHA=1_SCLK  
CS#  
SI  
MSB  
SO  
MSB  
Figure 4  
SPI SDR modes supported  
Timing diagrams throughout the remainder of the document are generally shown as both Mode 0 and 3 by  
showing SCK as both HIGH and LOW at the fall of CS#. In some cases, a timing diagram may show only Mode 0  
with SCK LOW at the fall of CS#. In such a case, mode 3 timing simply means clock is HIGH at the fall of CS# so no  
SCK rising edge set up or hold time to the falling edge of CS# is needed for Mode 3.  
SCK cycles are measured (counted) from one falling edge of SCK to the next falling edge of SCK. In Mode 0, the  
beginning of the first SCK cycle in a command is measured from the falling edge of CS# to the first falling edge of  
SCK because SCK is already LOW at the beginning of a command.  
4.1.2  
DDR  
Mode 0 and Mode 3 are also supported for DDR commands. In DDR commands, the instruction bits are always  
latched on the rising edge of clock, the same as in SDR commands. However, the address and input data that  
follow the instruction are latched on both the rising and falling edges of SCK. The first address bit is latched on  
the first rising edge of SCK following the falling edge at the end of the last instruction bit. The first bit of output  
data is driven on the falling edge at the end of the last access latency (dummy) cycle.  
SCK cycles are measured (counted) in the same way as in SDR commands, from one falling edge of SCK to the  
next falling edge of SCK. In mode 0, the beginning of the first SCK cycle in a command is measured from the falling  
edge of CS# to the first falling edge of SCK because SCK is already LOW at the beginning of a command.  
Datasheet  
17 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
CPOL=0_CPHA=0_SCLK  
CPOL=1_CPHA=1_SCLK  
CS#  
Instruction  
Address  
Mode  
Dummy / DLP  
Read Data  
Transfer_Phase  
SI  
Inst. 7  
Inst. 0  
A31 A30  
A0  
M7  
M6  
M0  
SO  
DLP7  
DLP0 D0  
D1  
Figure 5  
SPI DDR modes supported  
4.2  
Command Protocol  
All communication between the host system and FS-S family memory devices is in the form of units called  
commands.  
All commands begin with an 8-bit instruction that selects the type of information transfer or device operation to  
be performed. Commands may also have an address, instruction modifier, latency period, data transfer to the  
memory, or data transfer from the memory. All instruction, address, and data information is transferred  
sequentially between the host system and memory device.  
Command protocols are also classified by a numerical nomenclature using three numbers to reference the  
transfer width of three command phases:  
• instruction  
• address and instruction modifier(continuousreadmode bits). FortheS70FS01GS, do not enable the Continuous  
Read mode, this will cause bus contention between the two 512 Mb die.  
• data  
Single bit wide commands start with an instruction and may provide an address or data, all sent only on the SI  
signal. Data may be sent back to the host serially on the SO signal. This is referenced as a 1-1-1 command protocol  
for single bit width instruction, single bit width address and modifier, single bit data.  
Dual or Quad Input / Output (I/O) commands provide an address sent from the host as bit pairs on IO0 and IO1  
or, four bit (nibble) groups on IO0, IO1, IO2, and IO3. Data is returned to the host similarly as bit pairs on IO0 and  
IO1 or, four bit (nibble) groups on IO0, IO1, IO2, and IO3. This is referenced as 1-2-2 for Dual I/O and 1-4-4 for Quad  
I/O command protocols.  
The FS-S Family also supports a QPI Mode in which all information is transferred in 4-bit width, including the  
instruction, address, modifier, and data. This is referenced as a 4-4-4 command protocol.  
Commands are structured as follows:  
• Each command begins with CS# going LOW and ends with CS# returning HIGH. The memory device is selected  
by the host driving the Chip Select (CS#) signal LOW throughout a command.  
• The serial clock (SCK) marks the transfer of each bit or group of bits between the host and memory.  
• Each command begins with an eight bit (byte) instruction. The instruction selects the type of information  
transfer or device operation to be performed. The instruction transfers occur on SCK rising edges. However,  
some read commands are modified by a prior read command, such that the instruction is implied from the  
earlier command. This is called Continuous Read Mode. For the S70FS01GS, do not enable the Continuous Read  
Mode, this will cause bus contention between the two 512 Mb die.  
• The instruction may be stand alone or may be followed by address bits to select a location within one of several  
address spaces in the device. The instruction determines the address space used. The address may be either a  
24-bit or a 32-bit, byte boundary, address. The address transfers occur on SCK rising edge, in SDR commands,  
or on every SCK edge, in DDR commands.  
Datasheet  
18 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
• In legacy SPI mode, the width of all transfers following the instruction are determined by the instruction sent.  
Following transfers may continue to be single bit serial on only the SI or Serial Output (SO) signals, they may be  
done in two bit groups per (dual) transfer on the IO0 and IO1 signals, or they may be done in 4 bit groups per  
(quad) transfer on the IO0-IO3 signals. Within the dual or quad groups, the least significant bit is on IO0. More  
significant bits are placed in significance order on each higher numbered IO signal. Single bits or parallel bit  
groups are transferred in most to least significant bit order.  
• In QPI mode, the width of all transfers is a 4-bit wide (quad) transfer on the IO0–IO3 signals.  
• Dual and Quad I/O read instructions send an instruction modifier called Continuous Read Mode bits, following  
the address, to indicate whether the next command will be of the same type with an implied, rather than an  
explicit, instruction. These mode bits initiate or end the Continuous Read Mode. In Continuous Read Mode, the  
next command thus does not provide an instruction byte, only a new address and mode bits. For the S70FS01GS,  
do not enable the Continuous Read Mode, this will cause bus contention between the two 512 Mb die.  
• The address or mode bits may be followed by write data to be stored in the memory device or by a read latency  
period before read data is returned to the host.  
• Write data bit transfers occur on SCK rising edge, in SDR commands, or on every SCK edge, in DDR commands.  
• SCK continues to toggle during any read access latency period. The latency may be zero to several SCK cycles  
(also referred to as dummy cycles). At the end of the read latency cycles, the first read data bits are driven from  
the outputs on SCK falling edge at the end of the last read latency cycle. The first read data bits are considered  
transferred to the host on the following SCK rising edge. Each following transfer occurs on the next SCK rising  
edge, in SDR commands, or on every SCK edge, in DDR commands.  
• If the command returns read data to the host, the device continues sending data transfers until the host takes  
the CS# signal HIGH. The CS# signal can be driven HIGH after any transfer in the read data sequence. This will  
terminate the command.  
• At the end of a command that does not return data, the host drives the CS# input HIGH. The CS# signal must go  
HIGH after the eighth bit, of a stand alone instruction or, of the last write data byte that is transferred. That is,  
the CS# signal must be driven HIGH when the number of bits after the CS# signal was driven LOW is an exact  
multiple of eight bits. If the CS# signal does not go HIGH exactly at the eight bit boundary of the instruction or  
write data, the command is rejected and not executed.  
• All instruction, address, and mode bits are shifted into the device with the Most Significant Bits (MSB) first. The  
data bits are shifted in and out of the device MSB first. All data is transferred in byte units with the lowest address  
byte sent first. Following bytes of data are sent in lowest to highest byte address order i.e. the byte address  
increments.  
• All attempts to read the flash memory array during a program, erase, or a write cycle (embedded operations)  
are ignored. The embedded operation will continue to execute without any affect. A very limited set of  
commands are accepted during an embedded operation. These are discussed in the individual command  
descriptions.  
• Depending on the command, the time for execution varies. A command to read status information from an  
executing command is available to determine when the command completes execution and whether the  
command was successful.  
4.2.1  
Command sequence examples  
CS#  
SCLK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 6  
Standalone Instruction command  
Datasheet  
19 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
CS#  
SCLK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Input Data  
Figure 7  
Single Bit Wide Input command  
CS#  
SCLK  
SI  
7
6
5
4
3
2
1
0
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Data 1  
Data 2  
Figure 8  
Figure 9  
Figure 10  
Single Bit Wide Output command  
CS#  
SCLK  
SI  
SO  
7
6
5
4
3
2
1
0
31  
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2 1 0  
Phase  
Address  
Instruction  
Data 1  
Data 2  
Single Bit Wide I/O command without latency  
CS#  
SCLK  
SI  
SO  
7
6
5
4
3
2
1
0
31  
1
0
7
6
5
4
3
2
1 0  
Phase  
Address  
Instruction  
Dummy Cycles  
Data 1  
Single Bit Wide I/O command with latency  
CS#  
SCK  
IO0  
7
6
5
4
3
2
1
0
30  
31  
2
3
0
1
6
7
4
5
2
3
0
1
6
4
2
3
0
1
6
4
2
0
1
IO1  
7
5
7
5
3
Phase  
Instruction  
Address  
Mode  
Dm  
Data 1  
Data 2  
Figure 11  
Dual I/O command  
Datasheet  
20 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
CS#  
SCLK  
IO0  
7
6
5
4
3
2
1
0
28  
29  
30  
31  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO1  
IO2  
IO3  
Phase  
Address  
Instruction  
Mode  
Dummy  
D1  
D2  
D3  
D4  
Figure 12  
Figure 13  
Figure 14  
Figure 15  
Quad I/O command  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
28  
29  
30  
31  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
1
2
3
IO2  
IO3  
Phase  
Instruct.  
Address Mode  
Dummy  
D1  
D2  
D3  
D4  
Quad I/O Read command in QPI mode  
CS#  
SCLK  
IO0  
IO1  
7
6
5
4
3
2
1
0
2824201612 8  
2925211713 9  
4
5
0
1
2
3
4
5
6
7
0
1
2
3
7
7
7
7
6
6
6
6
5
5
5
5
4
4
4
4
3
2
2
2
2
1
1
1
1
0
4
5
6
7
0
4
5
6
7
0
3
3
3
0
0
0
1
2
3
1
IO2  
302622181410 6  
312723191511 7  
Address  
2
3
IO3  
Phase  
Instruction  
Mode Dummy  
DLP  
D1 D2  
DDR Quad I/O Read  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
28 24 20 16 12  
29 25 21 17 13  
8
4
0
1
2
3
4
5
6
7
0
1
2
3
7
7
7
7
6
6
6
6
5
5
5
5
4
3
3
3
3
2
2
2
2
1
0
0
0
0
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
1
2
3
9
5
6
7
4
4
4
1
1
1
IO2  
30 26 22 18 14 10  
31 27 23 19 15 11  
Address  
IO3  
Phase  
Instruct.  
Mode  
Dummy  
DLP  
D1  
D2  
DDR Quad I/O Read in QPI mode  
Additional sequence diagrams, specific to each command, are provided in “Commands” on page 83.  
Datasheet  
21 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
4.3  
Interface states  
This section describes the input and output signal levels as related to the SPI interface behavior.  
Table 3  
Interface states summary  
IO3 /  
WP# /  
IO2  
Interface state  
VCC  
SCK  
CS#  
X
SO / IO1 SI / IO0  
RESET#  
Power-Off  
Low Power  
Hardware Data Protection  
Power-On (Cold) Reset  
Hardware (Warm) Reset  
Non-Quad Mode  
<VCC (low)  
<VCC (cut-off)  
VCC (min)  
VCC (min)  
X
X
X
X
X
X
X
X
X
Z
Z
Z
Z
X
X
X
X
X
X
HH  
X
X
HL  
Hardware (Warm) Reset  
Quad Mode  
VCC (min)  
VCC (min)  
VCC (min)  
X
X
HH  
HH  
HL  
HL  
X
X
X
Z
Z
Z
X
X
Interface Standby  
Instruction Cycle  
(Legacy SPI)  
HT  
HH  
HV  
HV  
Single Input Cycle  
VCC (min)  
VCC (min)  
VCC (min)  
HT  
HT  
HT  
HL  
HL  
HL  
HH  
HH  
HH  
X
X
X
Z
Z
HV  
X
Host to Memory Transfer  
Single Latency (Dummy)  
Cycle  
Single Output Cycle  
Memory to Host Transfer  
MV  
X
Dual Input Cycle  
VCC (min)  
VCC (min)  
VCC (min)  
HT  
HT  
HT  
HL  
HL  
HL  
HH  
HH  
HH  
X
X
X
HV  
X
HV  
X
Host to Memory Transfer  
Dual Latency (Dummy) Cycle  
Dual Output Cycle  
Memory to Host Transfer  
MV  
MV  
Quad Input Cycle  
VCC (min)  
VCC (min)  
VCC (min)  
HT  
HT  
HT  
HL  
HL  
HL  
HV  
X
HV  
X
HV  
X
HV  
X
Host to Memory Transfer  
Quad Latency (Dummy)  
Cycle  
Quad Output Cycle  
Memory to Host Transfer  
DDR Quad Input Cycle  
Host to Memory Transfer  
DDR Latency (Dummy) Cycle  
DDR Quad Output Cycle  
Memory to Host Transfer  
MV  
HV  
MV  
HV  
MV  
HV  
MV  
HV  
VCC (min)  
VCC (min)  
VCC (min)  
HT  
HT  
HT  
HL  
HL  
HL  
MV or Z MV or Z MV or Z MV or Z  
MV  
MV  
MV  
MV  
Datasheet  
22 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
Legend  
Z = no driver - floating signal,  
HL = Host driving VIL,  
HH = Host driving VIH,  
HV = either HL or HH,  
X = HL or HH or Z,  
HT= toggling between HL and HH,  
ML = Memory driving VIL,  
MH = Memory driving VIH,  
MV = either ML or MH.  
4.3.1  
Power-off  
When the core supply voltage is at or below the VCC (Low) voltage, the device is considered to be powered off. The  
device does not react to external signals, and is prevented from performing any program or erase operation.  
4.3.2  
Low power hardware data protection  
When VCC is less than VCC (Cut-off) the memory device will ignore commands to ensure that program and erase  
operations can not start when the core supply voltage is out of the operating range.  
4.3.3  
Power-on (Cold) reset  
When the core voltage supply remains at or below the VCC (Low) voltage for tPD time, then rises to VCC (Minimum)  
the device will begin its Power On Reset (POR) process. POR continues until the end of tPU. During tPU, the device  
does not react to external input signals nor drive any outputs. Following the end of tPU the device transitions to  
the Interface Standby state and can accept commands. For additional information on POR, see “Power on (Cold)  
reset” on page 36.  
4.3.4  
Hardware (Warm) reset  
A configuration option is provided to allow IO3 to be used as a hardware reset input when the device is not in  
Quad Mode or when it is in Quad Mode and CS# is HIGH. When IO3 / RESET# is driven LOW for tRP time, the device  
starts the hardware reset process. The process continues for tRPH time. Following the end of both tRPH and the  
reset hold time following the rise of RESET# (tRH) the device transitions to the Interface Standby state and can  
accept commands. For additional information on hardware reset, see Note 17.  
4.3.5  
Interface standby  
When CS# is HIGH, the SPI interface is in standby state. Inputs other than RESET# are ignored. The interface waits  
for the beginning of a new command. The next interface state is Instruction Cycle when CS# goes LOW to begin a  
new command.  
While in interface standby state, the memory device draws standby current (ISB) if no embedded algorithm is in  
progress. If an embedded algorithm is in progress, the related current is drawn until the end of the algorithm  
when the entire device returns to standby current draw.  
The DPD mode is supported by the FS-S Family devices. If the device has been placed in DPD mode by the DPD  
(B9h) command, the interface standby current is (IDPD). The DPD command is accepted only while the device is  
not performing an embedded algorithm as indicated by the Status Register-1 Volatile Write In Progress (WIP) bit  
being cleared to zero (SR1V[0] = 0). While in DPD mode, the device ignores all commands except the Release from  
DPD (RES ABh) command, that will return the device to the Interface Standby state after a delay of tRES  
.
Datasheet  
23 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
4.3.6  
Instruction cycle (Legacy SPI mode)  
When the host drives the MSB of an instruction and CS# goes LOW, on the next rising edge of SCK the device  
captures the MSB of the instruction that begins the new command. On each following rising edge of SCK the  
device captures the next lower significance bit of the 8 bit instruction. The host keeps CS# LOW, and drives the  
Write Protect (WP#) and IO3/RESET signals as needed for the instruction. However, WP# is only relevant during  
instruction cycles of a WRAR command and is otherwise ignored. IO3/RESET# is driven HIGH when the device is  
not in Quad Mode (CR1V[1] = 0) or QPI Mode (CR2V[6] = 0) and hardware reset is not required.  
Each instruction selects the address space that is operated on and the transfer format used during the remainder  
of the command. The transfer format may be Single, Dual I/O, Quad I/O, or DDR Quad I/O. The expected next  
interface state depends on the instruction received.  
Some commands are stand alone, needing no address or data transfer to or from the memory. The host returns  
CS# HIGH after the rising edge of SCK for the eighth bit of the instruction in such commands. The next interface  
state in this case is Interface Standby.  
4.3.7  
Instruction cycle (QPI mode)  
In QPI Mode, when CR2V[6] = 1, instructions are transferred 4 bits per cycle. In this mode, instruction cycles are  
the same as a quad input cycle (see “Quad input cycle - Host to Memory transfer” on page 25).  
4.3.8  
Single input cycle - Host to Memory transfer  
Several commands transfer information after the instruction on the single serial input (SI) signal from host to the  
memory device. The host keeps RESET# HIGH, CS# LOW, and drives SI as needed for the command. The memory  
does not drive the Serial Output (SO) signal.  
The expected next interface state depends on the instruction. Some instructions continue sending address or  
data to the memory using additional Single Input Cycles. Others may transition to Single Latency, or directly to  
Single, Dual, or Quad Output cycle states.  
4.3.9  
Single latency (Dummy) cycle  
Read commands may have zero to several latency cycles during which read data is read from the main Flash  
memory array before transfer to the host. The number of latency cycles are determined by the Latency Code in  
the configuration register (CR2V[3:0]). During the latency cycles, the host keeps RESET# HIGH, CS# LOW. The Write  
Protect (WP#) signal is ignored. The host may drive the SI signal during these cycles or the host may leave SI  
floating. The memory does not use any data driven on SI/I/O0 or other I/O signals during the latency cycles. The  
memory does not drive the Serial Output (SO) or I/O signals during the latency cycles.  
The next interface state depends on the command structure i.e. the number of latency cycles, and whether the  
read is single, dual, or quad width.  
4.3.10  
Single output cycle - Memory to Host transfer  
Several commands transfer information back to the host on the single Serial Output (SO) signal. The host keeps  
RESET# HIGH, CS# LOW. The Write Protect (WP#) signal is ignored. The memory ignores the Serial Input (SI) signal.  
The memory drives SO with data.  
The next interface state continues to be Single Output Cycle until the host returns CS# to HIGH ending the  
command.  
4.3.11  
Dual input cycle - Host to Memory transfer  
The Read Dual I/O command transfers two address or mode bits to the memory in each cycle. The host keeps  
RESET# HIGH, CS# LOW. The Write Protect (WP#) signal is ignored. The host drives address on SI / IO0 and  
SO / IO1.  
The next interface state following the delivery of address and mode bits is a Dual Latency Cycle if there are latency  
cycles needed or Dual Output Cycle if no latency is required.  
Datasheet  
24 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
4.3.12  
Dual latency (Dummy) cycle  
Read commands may have zero to several latency cycles during which read data is read from the main Flash  
memory array before transfer to the host. The number of latency cycles are determined by the Latency Code in  
the configuration register (CR2V[3:0]). During the latency cycles, the host keeps RESET# HIGH, CS# LOW. The Write  
Protect (WP#) signal is ignored. The host may drive the SI / IO0 and SO / IO1 signals during these cycles or the host  
may leave SI / IO0 and SO / IO1 floating. The memory does not use any data driven on SI / IO0 and SO / IO1 during  
the latency cycles. The host must stop driving SI / IO0 and SO / IO1 on the falling edge at the end of the last latency  
cycle. It is recommended that the host stop driving them during all latency cycles so that there is sufficient time  
for the host drivers to turn off before the memory begins to drive at the end of the latency cycles. This prevents  
driver conflict between host and memory when the signal direction changes. The memory does not drive the  
SI / IO0 and SO / IO1 signals during the latency cycles.  
The next interface state following the last latency cycle is a Dual Output Cycle.  
4.3.13  
Dual output cycle - Memory to Host transfer  
The Read Dual Output and Read Dual I/O return data to the host two bits in each cycle. The host keeps RESET#  
HIGH, CS# LOW. The Write Protect (WP#) signal is ignored. The memory drives data on the SI / IO0 and SO / IO1  
signals during the dual output cycles.  
The next interface state continues to be Dual Output Cycle until the host returns CS# to HIGH ending the  
command.  
4.3.14  
Quad input cycle - Host to Memory transfer  
The Quad I/O Read command transfers four address or mode bits to the memory in each cycle. In QPI Mode, the  
Quad I/O Read and Page Program commands transfer four data bits to the memory in each cycle, including the  
instruction cycles. The host keeps CS# LOW, and drives the IO signals.  
For Quad I/O Read the next interface state following the delivery of address and mode bits is a Quad Latency Cycle  
if there are latency cycles needed or Quad Output Cycle if no latency is required. For QPI Mode Page Program, the  
host returns CS# HIGH following the delivery of data to be programmed and the interface returns to standby  
state.  
4.3.15  
Quad latency (Dummy) cycle  
Read commands may have zero to several latency cycles during which read data is read from the main Flash  
memory array before transfer to the host. The number of latency cycles are determined by the Latency Code in  
the configuration register (CR2V[3:0]). During the latency cycles, the host keeps CS# LOW. The host may drive the  
IO signals during these cycles or the host may leave the IO floating. The memory does not use any data driven on  
IO during the latency cycles. The host must stop driving the IO signals on the falling edge at the end of the last  
latency cycle. It is recommended that the host stop driving them during all latency cycles so that there is sufficient  
time for the host drivers to turn off before the memory begins to drive at the end of the latency cycles. This  
prevents driver conflict between host and memory when the signal direction changes. The memory does not  
drive the IO signals during the latency cycles.  
The next interface state following the last latency cycle is a Quad Output Cycle.  
4.3.16  
Quad output cycle - Memory to Host transfer  
The Quad I/O Read returns data to the host four bits in each cycle. The host keeps CS# LOW. The memory drives  
data on IO0–IO3 signals during the Quad output cycles.  
The next interface state continues to be Quad Output Cycle until the host returns CS# to HIGH ending the  
command.  
4.3.17  
DDR quad input cycle - Host to Memory transfer  
The DDR Quad I/O Read command sends address, and mode bits to the memory on all the IO signals. Four bits  
are transferred on the rising edge of SCK and four bits on the falling edge in each cycle. The host keeps CS# LOW.  
The next interface state following the delivery of address and mode bits is a DDR Latency Cycle.  
Datasheet  
25 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Signal protocols  
4.3.18  
DDR latency cycle  
DDR Read commands may have one to several latency cycles during which read data is read from the main Flash  
memory array before transfer to the host. The number of latency cycles are determined by the Latency Code in  
the configuration register (CR2V[3:0]). During the latency cycles, the host keeps CS# LOW. The host may not drive  
the IO signals during these cycles. So that there is sufficient time for the host drivers to turn off before the memory  
begins to drive. This prevents driver conflict between host and memory when the signal direction changes. The  
memory has an option to drive all the IO signals with a Data Learning Pattern (DLP) during the last 4 latency  
cycles. The DLP option should not be enabled when there are fewer than five latency cycles so that there is at  
least one cycle of high impedance for turn around of the IO signals before the memory begins driving the DLP.  
When there are more than 4 cycles of latency the memory does not drive the IO signals until the last four cycles  
of latency.  
The next interface state following the last latency cycle is a DDR Single, or Quad Output Cycle, depending on the  
instruction.  
4.3.19  
DDR quad output cycle - Memory to Host transfer  
The DDR Quad I/O Read command returns bits to the host on all the IO signals. Four bits are transferred on the  
rising edge of SCK and four bits on the falling edge in each cycle. The host keeps CS# LOW.  
The next interface state continues to be DDR Quad Output Cycle until the host returns CS# to HIGH ending the  
command.  
4.4  
Configuration Register effects on the interface  
The Configuration Register 2 volatile bits 3 to 0 (CR2V[3:0]) select the variable latency for all array read commands  
except Read and Read SDFP (RSFDP). Read always has zero latency cycles. RSFDP always has eight latency cycles.  
The variable latency is also used in the OTPR, and RDAR commands.  
The configuration register bit1 (CR1V[1]) selects whether Quad Mode is enabled to switch WP# to IO2 function,  
RESET# to IO3 function, and thus allow Quad I/O Read and QPI Mode commands. Quad Mode must also be  
selected to allow DDR Quad I/O Read commands.  
4.5  
Data protection  
Some basic protection against unintended changes to stored data are provided and controlled purely by the  
hardware design. These are described in “Data Protection” on page 74. Other software managed protection  
methods are discussed in “Data Protection” on page 74 of this document.  
4.5.1  
Power-up  
When the core supply voltage is at or below the VCC (Low) voltage, the device is considered to be powered off. The  
device does not react to external signals, and is prevented from performing any program or erase operation.  
Program and erase operations continue to be prevented during the power-on reset (POR) because no command  
is accepted until the exit from POR to the Interface Standby state.  
4.5.2  
Low power  
When VCC is less than VCC (Cut-off) the memory device will ignore commands to ensure that program and erase  
operations can not start when the core supply voltage is out of the operating range.  
4.5.3  
Clock pulse count  
The device verifies that all non-volatile memory and register data modifying commands consist of a clock pulse  
count that is a multiple of eight bit transfers (byte boundary) before executing them. A command not ending on  
an 8 bit (byte) boundary is ignored and no error status is set for the command.  
4.5.4  
DPD  
In the DPD mode, the device responds only to the Release from DPD command (RES ABh). All other commands  
are ignored during DPD Mode, thereby protecting the memory from program and erase operations.  
Datasheet  
26 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Electrical specifications  
5
Electrical specifications  
5.1  
Absolute maximum ratings  
Storage temperature plastic packages  
Ambient temperature with power applied  
VCC  
Input voltage with respect to Ground (VSS)[4]  
Output short circuit current[5]  
–65 °C to +150 °C  
–65 °C to +125 °C  
–0.5 V to +2.5 V  
–0.5 V to VCC + 0.5 V  
100 mA  
5.2  
Thermal resistance  
Table 4  
Thermal resistance  
Parameter  
Theta JA  
Theta JB  
Theta JC  
Description  
SL3016  
ZSZ024  
33  
Unit  
Thermal resistance (Junction to ambient)  
Thermal resistance (Junction to board)  
Thermal resistance (Junction to case)  
39  
8
9
11  
11  
°C/W  
5.3  
Latchup characteristics  
Table 5  
Latchup specification  
Description  
Min  
–1.0  
–1.0  
–100  
Max  
VCC + 1.0  
VCC + 1.0  
+100  
Unit  
V
V
Input voltage with respect to VSS on all input only connections  
Input voltage with respect to VSS on all I/O connections  
VCC Current  
mA  
Notes  
4. See “Input signal overshoot” on page 29 for allowed maximums during signal transition.  
5. No more than one output may be shorted to ground at a time. Duration of the short circuit should not be  
greater than one second.  
6. Stresses above those listed under “Absolute Maximum Ratings” may cause permanent damage to the device.  
This is a stress rating only; functional operation of the device at these or any other conditions above those  
indicated in the operational sections of this data sheet is not implied. Exposure of the device to absolute  
maximum rating conditions for extended periods may affect device reliability.  
7. Excludes power supply VCC. Test conditions: VCC = 1.8 V, one connection at a time tested, connections not  
being tested are at VSS  
.
Datasheet  
27 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Electrical specifications  
5.4  
Operating ranges  
Operating ranges define those limits between which the functionality of the device is guaranteed.  
5.4.1  
Power supply voltages  
VCC  
1.7 V to 2.0 V  
5.4.2  
Temperature ranges  
Table 6  
Temperature ranges  
Spec  
Parameter  
Symbol  
Conditions  
Unit  
Min  
–40  
–40  
Max  
+85  
+105  
Industrial (I) devices  
Industrial Plus (V) devices  
°C  
°C  
Automotive, AEC-Q100 grade 3 (A)  
Devices  
Automotive, AEC-Q100 grade 2 (B)  
Devices  
Automotive, AEC-Q100 grade 1 (M)  
Devices  
–40  
–40  
–40  
+85  
+105  
+125  
°C  
°C  
°C  
Ambient Temperature  
TA  
Notes  
8. Industrial Plus operating and performance parameters will be determined by device characterization and  
may vary from standard industrial temperature range devices as currently shown in this specification.  
Datasheet  
28 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Electrical specifications  
5.4.3  
Input signal overshoot  
During DC conditions, input or I/O signals should remain equal to or between VSS and VCC. During voltage  
transitions, inputs or I/Os may overshoot VSS to –1.0 V or overshoot to VCC + 1.0 V, for periods up to 20 ns.  
VSS to VCC  
- 1.0V  
< = 20 ns  
Figure 16  
Maximum negative overshoot waveform  
< = 20 ns  
VCC + 1.0V  
VSS to VCC  
Figure 17  
Maximum positive overshoot waveform  
5.5  
Power-up and power-down  
The device must not be selected at power-up or power-down (that is, CS# must follow the voltage applied on VCC  
until VCC reaches the correct value as follows:  
)
• VCC (min) at power-up, and then for a further delay of tPU  
• VSS at power-down  
A simple pull-up resistor on Chip Select (CS#) can usually be used to insure safe and proper power-up and  
power-down.  
The device ignores all instructions until a time delay of tPU has elapsed after the moment that VCC rises above the  
minimum VCC threshold (see Figure 18). However, correct operation of the device is not guaranteed if VCC returns  
below VCC (min) during tPU. No command should be sent to the device until the end of tPU  
.
The device draws IPOR during tPU. After power-up (tPU), the device is in Standby Mode, draws CMOS standby  
current (ISB), and the WEL bit is reset.  
During power-down or voltage drops below VCC(cut-off), the voltage must drop below VCC(low) for a period of tPD  
for the part to initialize correctly on power-up (see Figure 19). If during a voltage drop the VCC stays above  
VCC(cut-off) the part will stay initialized and will work correctly when VCC is again above VCC(min). In the event  
Power-on Reset (POR) did not complete correctly after power up, the assertion of the RESET# signal or receiving  
a software reset command (RESET) will restart the POR process.  
Normal precautions must be taken for supply rail decoupling to stabilize the VCC supply at the device. Each device  
in a system should have the VCC rail decoupled by a suitable capacitor close to the package supply connection  
(this capacitor is generally of the order of 0.1 µF).  
Datasheet  
29 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Electrical specifications  
Table 7  
Symbol  
CC (min) VCC (minimum operation voltage)  
CC (cut-off) VCC (Cut 0ff where re-initialization is needed)  
CC (low) VCC (low voltage for initialization to occur)  
FS-S power-up / power-down voltage and timing  
Parameter  
Min  
1.7  
1.5  
0.7  
Max  
Unit  
V
V
V
V
V
V
tPU  
tPD  
VCC (min) to Read operation  
VCC (low) time  
300  
µs  
µs  
10.0  
VCC (Max)  
VCC (Min)  
tPU  
Full Device Access  
Time  
Figure 18  
Power-up  
VCC (Max)  
No Device Access Allowed  
VCC (Min)  
Device  
tPU  
Access  
Allowe  
VCC (Cut-off)  
VCC (Low)  
tPD  
Time  
Figure 19  
Power-down and voltage drop  
Datasheet  
30 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Electrical specifications  
5.6  
DC characteristics  
Industrial  
5.6.1  
Applicable within operating –40 °C to +85 °C range.  
Table 8 FS01GS DC characteristics — Industrial  
Symbol  
Parameter  
Input low voltage  
Input high voltage  
Output low voltage  
Output high voltage  
Test conditions  
Min  
–0.5  
0.7 VCC  
Typ[10]  
Max  
0.3 VCC  
VCC + 0.4  
0.2  
Unit  
VIL  
VIH  
V
V
V
V
VOL  
VOH  
IOL = 0.1 mA  
IOH = –0.1 mA  
VCC – 0.2  
V
CC = VCC Max,  
ILI  
Input leakage current  
Output leakage current  
VIN = VIH or VSS  
CS# = VIH  
,
,
±4  
±4  
µA  
µA  
V
CC = VCC Max,  
ILO  
VIN = VIH or VSS  
CS# = VIH  
Serial SDR @ 50 MHz  
18  
25  
60  
70  
25  
45  
65  
90  
Active power supply current Serial SDR @ 133 MHz  
ICC1  
mA  
(READ)[10]  
Quad SDR @ 133 MHz  
Quad DDR @ 80 MHz  
Active power supply current  
(Page Program)  
Active power supply current  
(WRAR)  
Active power supply current  
(SE)  
Active power supply current  
(BE)  
ICC2  
ICC3  
ICC4  
ICC5  
CS# = VCC  
CS# = VCC  
CS# = VCC  
60  
60  
60  
60  
100  
100  
100  
100  
mA  
mA  
mA  
mA  
CS# = VCC  
IO3/RESET#, CS# = VCC  
;
;
;
ISB  
Standby current  
SI, SCK = VCC or VSS  
Industrial Temp  
,
140  
200  
µA  
IO3/RESET#, CS# = VCC  
IDPD  
IPOR  
Deep power down current SI, SCK = VCC or VSS  
Industrial Temp  
,
16  
120  
160  
µA  
IO3/RESET#, CS# = VCC  
SI, SCK = VCC or VSS  
Power on reset current  
mA  
Notes  
9. Typical values are at TAI = 25 °C and VCC = 1.8 V.  
10.Outputs unconnected during read data return. Output switching current is not included.  
Datasheet  
31 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Electrical specifications  
5.6.2  
Industrial Plus  
Applicable within operating –40 °C to +105 °C range.  
These values to be adjusted after DE simulation to predict the Industrial Plus capabilities.  
Table 9  
Symbol  
DC characteristics — Industrial Plus  
Parameter  
Input low voltage  
Input high voltage  
Output low voltage  
Output high voltage  
Test conditions  
Min  
–0.5  
0.7 VCC  
Typ[11]  
Max  
0.3 VCC  
VCC + 0.4  
0.2  
Unit  
VIL  
VIH  
VOL  
VOH  
V
V
V
V
IOL = 0.1 mA  
IOH = –0.1 mA  
VCC – 0.2  
V
CC = VCC Max,  
ILI  
Input leakage current  
Output leakage current  
VIN = VIH or VSS  
CS# = VIH  
,
,
±8  
±8  
µA  
µA  
V
CC = VCC Max,  
ILO  
VIN = VIH or VSS  
CS# = VIH  
Serial SDR @ 50 MHz  
18  
25  
60  
70  
25  
45  
65  
90  
Active power supply current Serial SDR @ 133 MHz  
ICC1  
mA  
(READ)[12]  
Quad SDR @ 133 MHz  
Quad DDR @ 80 MHz  
Active power supply current  
(Page Program)  
Active power supply current  
(WRAR)  
Active power supply current  
(SE)  
Active power supply current  
(BE)  
ICC2  
ICC3  
CS# = VCC  
CS# = VCC  
CS# = VCC  
60  
60  
60  
60  
100  
100  
100  
100  
mA  
mA  
mA  
mA  
ICC4  
ICC5  
CS# = VCC  
IO3/RESET#, CS# = VCC  
;
I
SB (Indus-  
Standby current  
SI, SCK = VCC or VSS  
,
140  
600  
µA  
trial Plus)  
Industrial Plus Temp  
IO3/RESET#, CS#=VCC  
;
;
IDPD  
Deep power down current SI, SCK = VCC or VSS  
Industrial Temp  
,
16  
300  
160  
µA  
IO3/RESET#, CS#=VCC  
SI, SCK = VCC or VSS  
IPOR  
Power on reset current  
mA  
Notes  
11.Typical values are at TAI = 25 °C and VCC = 1.8 V.  
12.Outputs unconnected during read data return. Output switching current is not included.  
Datasheet  
32 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Electrical specifications  
5.6.3  
Extended  
Applicable within operating –40 °C to +125 °C range.  
Table 10  
Symbol  
VIL  
DC characteristics — Extended  
Parameter  
Test Conditions  
Min  
–0.5  
0.7 VCC  
Typ[13]  
Max  
0.3 VCC  
VCC + 0.4  
0.2  
Unit  
Input low voltage  
Input high voltage  
Output low voltage  
Output high voltage  
V
V
V
V
VIH  
VOL  
VOH  
IOL = 0.1 mA  
IOH = –0.1 mA  
VCC – 0.2  
V
CC = VCC Max,  
ILI  
Input leakage current  
Output leakage current  
VIN = VIH or VSS  
CS# = VIH  
,
,
±8  
±8  
µA  
µA  
V
CC = VCC Max,  
ILO  
VIN = VIH or VSS  
CS# = VIH  
Serial SDR @ 50 MHz  
18  
25  
60  
70  
25  
50  
65  
90  
Active power supply current Serial SDR @ 133 MHz  
ICC1  
mA  
(READ)[14]  
Quad SDR @ 133 MHz  
Quad DDR @ 80 MHz  
Active power supply current  
(Page Program)  
Active power supply current  
(WRAR)  
Active power supply current  
(SE)  
Active power supply current  
(BE)  
ICC2  
ICC3  
ICC4  
CS# = VCC  
CS# = VCC  
CS# = VCC  
60  
60  
60  
60  
100  
100  
100  
100  
mA  
mA  
mA  
mA  
ICC5  
ISB  
CS# = VCC  
IO3/RESET#, CS# = VCC  
;
;
;
(Industrial Standby current  
Plus)  
SI, SCK = VCC or VSS  
,
140  
600  
µA  
Industrial Plus Temp  
IO3/RESET#, CS# = VCC  
IDPD  
IPOR  
Deep power down current SI, SCK = VCC or VSS  
,
16  
500  
160  
µA  
Industrial Temp  
IO3/RESET#, CS# = VCC  
SI, SCK = VCC or VSS  
Power on reset current  
mA  
Notes  
13.Typical values are at TAI = 25 °C and VCC = 1.8 V.  
14.Outputs unconnected during read data return. Output switching current is not included.  
5.6.4  
Active power and standby power modes  
The device is enabled and in the Active Power mode when Chip Select (CS#) is LOW. When CS# is HIGH, the device  
is disabled, but may still be in an Active Power Mode until all program, erase, and write operations have  
completed. The device then goes into the Standby Power Mode, and power consumption drops to ISB  
.
The DPD mode is supported by the FS-S Family devices. If the device has been placed in DPD Mode by the DPD  
(B9h) command, the interface standby current is (IDPD). The DPD command is accepted only while the device is  
not performing an embedded algorithm as indicated by the Status Register-1 volatile Write In Progress (WIP) bit  
being cleared to zero (SR1V[0] = 0). While in DPD Mode, the device ignores all commands except the Release from  
DPD (RES ABh) command, that will return the device to the Interface Standby state after a delay of tRES  
.
Datasheet  
33 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
6
Timing specifications  
6.1  
Key to switching waveforms  
Input  
Symbol  
Output  
Valid at logic high or low  
Valid at logic high or low  
High Impedance  
Any change permitted  
Logic high Logic low  
High Impedance Changing, state unknown Logic high Logic low  
Figure 20  
Waveform element meanings  
6.2  
AC test conditions  
Device Under  
Test  
C
L
Figure 21  
Test setup  
Table 11  
Symbol  
CL  
AC measurement conditions  
Parameter  
Load capacitance  
Input pulse voltage  
Input slew rate  
Input rise and fall times  
Input timing ref voltage  
Output timing ref voltage  
Min  
0.2 × VCC  
0.23  
Max  
30  
0.8 × VCC  
1.25  
5
Unit  
pF  
V
V/ns  
ns  
V
0.9  
0.5 × VCC  
0.5 × VCC  
V
Notes  
15.Input slew rate measured from input pulse min to max at VCC max.  
Example: (1.9 V × 0.8) – (1.9 V × 0.2) = 1.14 V; 1.14 V /1.25 V/ns = 0.9 ns rise or fall time.  
16.AC characteristics tables assume clock and data signals have the same slew rate (slope).  
Datasheet  
34 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
Input Levels  
Output Levels  
VCC - 0.2V  
VCC + 0.4V  
0.7 x VCC  
Timing Reference Level  
0.5 x VCC  
0.3 x VCC  
- 0.5V  
0.2V  
Figure 22  
Input, output, and timing reference levels  
6.2.1  
Capacitance characteristics  
Table 12  
Symbol  
Capacitance  
Parameter  
Input capacitance (applies to SCK, CS#,  
IO3/RESET#)  
Test Conditions  
1 MHz  
Min  
Max  
Unit  
pF  
CIN  
16  
16  
COUT  
Output capacitance (applies to All I/O)  
1 MHz  
pF  
Note  
17.Parameter values are not 100% tested. For more details, refer to the IBIS models.  
Datasheet  
35 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
6.3  
Reset  
6.3.1  
Power on (Cold) reset  
The device executes a power-on reset (POR) process until a time delay of tPU has elapsed after the moment that  
VCC rises above the minimum VCC threshold. See Figure 18 and Table 7. The device must not be selected (CS# to  
go HIGH with VCC) during power-up (tPU), i.e. no commands may be sent to the device until the end of tPU  
.
The IO3 / RESET# signal functions as the RESET# input when CS# is HIGH for more than tCS time or when Quad  
Mode is not enabled CR1V[1] = 0.  
RESET# is ignored during POR. If RESET# is LOW during POR and remains LOW through and beyond the end of  
t
PU, CS# must remain HIGH until tRH after RESET# returns HIGH. RESET# must return HIGH for greater than tRS  
before returning LOW to initiate a hardware reset.  
VCC  
tPU  
RESET#  
If RESET# is low at tPU end  
CS# must be high at tPU end  
tRH  
CS#  
Figure 23  
Reset LOW at the end of POR  
VCC  
tPU  
RESET#  
If RESET# is high at tPU end  
tPU  
CS#  
CS# may stay high or go low at tPU end  
Figure 24  
Reset HIGH at the end of POR  
VCC  
tPU  
tPU  
tRS  
RESET#  
CS#  
Figure 25  
POR followed by hardware reset  
Datasheet  
36 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
6.3.2  
IO3 / RESET# input initiated hardware (Warm) reset  
The IO3 / RESET# signal functions as the RESET# input when CS# is HIGH for more than tCS time or when Quad  
Mode is not enabled CR1V[1] = 0. The IO3 / RESET# input has an internal pull-up to VCC and may be left  
unconnected if Quad Mode is not used. The tCS delay after CS# goes HIGH gives the memory or host system time  
to drive IO3 HIGH after its use as a Quad Mode I/O signal while CS# was LOW. The internal pull-up to VCC will then  
hold IO3 / RESET# HIGH until the host system begins driving IO3 / RESET#. The IO3 / RESET# input is ignored while  
CS# remains HIGH during tCS, to avoid an unintended Reset operation. If CS# is driven LOW to start a new  
command, IO3 / RESET# is used as IO3.  
When the device is not in Quad Mode or, when CS# is HIGH, and IO3 / RESET# transitions from VIH to VIL for > tRP  
,
following tCS, the device will reset register states in the same manner as power-on reset but, does not go through  
the full reset process that is performed during POR. The hardware reset process requires a period of tRPH to  
complete. If the POR process did not complete correctly for any reason during power-up (tPU), RESET# going LOW  
will initiate the full POR process instead of the hardware reset process and will require tPU to complete the POR  
process.  
The RESET command is independent of the state of IO3 / RESET#. If IO3 / RESET# is HIGH or unconnected, and  
the RESET instruction is issued, the device will perform software reset.  
Additional IO3 RESET# notes:  
• IO3 / RESET# must be HIGH for tRS following tPU or tRPH, before going LOW again to initiate a hardware reset.  
• When IO3 / RESET# is driven LOW for at least a minimum period of time (tRP), following tCS, the device terminates  
any operation in progress, makes all outputs high impedance, and ignores all read/write commands for the  
duration of tRPH. The device resets the interface to standby state.  
• If Quad mode and the IO3 / RESET# feature are enabled, the host system should not drive IO3 LOW during tCS,  
to avoid driver contention on IO3. Immediately following commands that transfer data to the host in Quad Mode,  
for example, Quad I/O Read, the memory drives IO3 / Reset HIGH during tCS, to avoid an unintended Reset  
operation. Immediately following commands that transfer data to the memory in Quad Mode, e.g. Page  
Program, the host system should drive IO3 / Reset HIGH during tCS, to avoid an unintended Reset operation.  
• If Quad mode is not enabled, and if CS# is LOW at the time IO3 / RESET# is asserted LOW, CS# must return HIGH  
during tRPH before it can be asserted LOW again after tRH  
.
Table 13  
Parameter  
tRS  
Hardware Reset Parameters  
Description  
Reset Setup - Prior Reset end and RESET# HIGH before RESET# LOW  
Reset Pulse Hold - RESET# LOW to CS# LOW  
RESET# Pulse Width  
Limit  
Min  
Min  
Min  
Min  
Time Unit  
50  
35  
ns  
µs  
ns  
ns  
tRPH  
tRP  
tRH  
200  
50  
Reset Hold - RESET# HIGH before CS# LOW  
Notes  
18.IO3 / RESET# LOW is ignored during Power-up (tPU). If Reset# is asserted during the end of tPU, the device  
will remain in the reset state and tRH will determine when CS# may go LOW.  
19.If Quad Mode is enabled, IO3 / RESET# LOW is ignored during tCS  
.
20.Sum of tRP and tRH must be equal to or greater than tRPH  
.
Datasheet  
37 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
tRP  
IO3_RESET#  
CS#  
Any prior reset  
tRPH  
tRH  
tRH  
tRS  
tRPH  
Figure 26  
Hardware Reset when Quad mode is not enabled and IO3 / Reset# is enabled  
tDIS  
tRP  
IO3_RESET#  
Reset Pulse  
tCS  
tRH  
tRPH  
CS#  
Prior access using IO3 for data  
Figure 27  
Hardware Reset when Quad mode and IO3 / Reset# are enabled  
Datasheet  
38 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
6.4  
SDR AC characteristics  
Table 14  
AC characteristics  
Symbol  
Parameter  
Min  
Max  
Unit  
FSCK, R SCK clock frequency for READ and 4READ instructions  
DC  
50  
MHz  
SCK clock frequency for the following dual and quad  
FSCK, C  
DC  
DC  
133  
80  
MHz  
MHz  
commands: QOR, 4QOR, DIOR, 4DIOR, QIOR, 4QIOR  
SCK clock frequency for the following DDR commands:  
QIOR, 4QIOR  
FSCK, D  
PSCK  
WH, tCH Clock High time  
WL, tCL Clock Low time  
CRT, tCLCH Clock rise time (slew rate)  
CFT, tCHCL Clock fall time (slew rate)  
CS# High time (Read instructions)  
SCK clock period  
1/ FSCK  
50% PSCK – 5%  
50% PSCK – 5%  
0.1  
t
t
ns  
ns  
V/ns  
V/ns  
t
t
0.1  
10  
20[25]  
50  
CS# High time (Read instructions when Reset feature and  
tCS  
ns  
Quad mode are both enabled)  
CS# High time (Program/Erase Instructions)  
tCSS  
tCSH  
tSU  
CS# Active Setup time (relative to SCK)  
CS# Active Hold time (relative to SCK)  
Data in Setup time  
2
3
2
3
ns  
ns  
ns  
ns  
tHD  
Data in Hold time  
8[22]  
tV  
Clock low to output valid  
1
ns  
ns  
6[23]  
tHO  
Output Hold time  
Output disable time[24]  
Output disable time (when Reset feature and Quad Mode  
are both enabled)  
WP# Setup time[21]  
WP# Hold time[21]  
CS# High to power-down mode  
8
tDIS  
ns  
20[25]  
tWPS  
tWPH  
tDPD  
20  
100  
3
ns  
ns  
µs  
CS# High to Standby Mode without Electronic Signature  
Read  
tRES  
30  
µs  
Notes  
21.Only applicable as a constraint for WRAR instruction when SRWD is set to a 1.  
22.Full VCC range & CL = 30 pF.  
23.Full VCC range & CL = 15 pF.  
24.Output HI-Z is defined as the point where data is no longer driven.  
25.tCS and tDIS require additional time when the Reset feature and Quad Mode are enabled (CR2V[5] = 1 and  
CR1V[1] = 1).  
26.Tentative AC parameters, subject to device characterization, as DDP has increased I/O capacitance that may  
modify values slightly.  
Datasheet  
39 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
6.4.1  
Clock timing  
PSCK  
tCL  
tCH  
VIH min  
VCC / 2  
VIL max  
tCFT  
tCRT  
Figure 28  
Clock timing  
6.4.2  
Input / Output timing  
tCS  
CS#  
tCSH  
tCSH  
tCSS  
tCSS  
SCK  
tSU  
tHD  
MSB IN  
SI  
LSB IN  
SO  
Figure 29  
SPI single bit input timing  
tCS  
CS#  
SCK  
SI  
tV  
tHO  
tDIS  
SO  
MSB OUT  
LSB OUT  
Figure 30  
SPI single bit output timing  
Datasheet  
40 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
tCS  
CS#  
tCSS  
tCSH  
tCSS  
tSU  
SCLK  
tHD  
tV  
tHO  
tV  
tDIS  
MSB IN  
LSB IN  
MSB O.  
LSB OUT  
IO  
Figure 31  
SPI SDR MIO timing  
CS#  
tWPS  
WP#  
tWPH  
SCLK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
WRAR Instruction  
Input Data  
Figure 32  
WP# input timing  
Datasheet  
41 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
6.5  
DDR AC characteristics  
Table 15  
FS01GS AC characteristics 80MHz operation  
Symbol  
FSCK, R  
PSCK, R  
WH, tCH  
WL, tCL  
Parameter  
Min  
DC  
12.5  
Max  
80  
Unit  
MHz  
ns  
ns  
ns  
SCK Clock Frequency for DDR READ instruction  
SCK Clock Period for DDR READ instruction  
Clock High Time  
t
t
50% PSCK – 5%  
50% PSCK – 5%  
Clock Low Time  
CS# High Time (Read Instructions)  
CS# High Time (Read Instructions when Reset feature is  
enabled)  
10  
20  
tCS  
ns  
tCSS  
tCSH  
tSU  
tHD  
tV  
CS# Active Setup Time (relative to SCK)  
CS# Active Hold Time (relative to SCK)  
IO in Setup Time  
IO in Hold Time  
Clock Low to Output Valid  
Output Hold Time  
2
3
1.5  
1.5  
1.5  
1
6 (1)  
ns  
ns  
ns  
ns  
ns  
ns  
tHO  
Output Disable Time  
Output Disable Time (when Reset feature is enabled)  
8
20  
tDIS  
ns  
tIO_skew  
tDPD  
First IO to last IO data valid time  
CS# High to Power-down Mode  
400  
3
ps  
µs  
CS# High to Standby Mode without Electronic Signature  
Read  
tRES  
30  
µs  
Note  
27.CL = 15 pF.  
6.5.1  
DDR input timing  
tCS  
CS#  
tCSH  
tCSH  
tCSS  
tCSS  
SCK  
tHD  
tSU  
tHD  
tSU  
SI_or_IO  
SO  
MSB IN  
LSB IN  
Figure 33  
SPI DDR input timing  
Datasheet  
42 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
6.5.2  
DDR output timing  
tCS  
CS#  
SCK  
tHO  
MSB  
tV  
tV  
tDIS  
IO's  
LSB  
Figure 34  
SPI DDR output timing  
6.5.3  
DDR data valid timing using DLP  
pSCK  
tCL  
tCH  
SCK  
tIO_SKEW  
tV  
tOTT  
IO Slow  
IO Fast  
S.  
Slow D1  
Slow D2  
tV  
Fast D1  
Fast D2  
tV_min  
tHO  
tDV  
D1  
IO_valid  
D2  
Figure 35  
SPI DDR data valid window  
Datasheet  
43 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Timing specifications  
The minimum data valid window (tDV) and tV minimum can be calculated as follows:  
[29]  
tDV = Minimum half clock cycle time (tCLH  
tV _min = tHO + tIO_SKEW + tOTT  
Example:  
)
[28] – tOTT[30] – tIO_SKEW  
80 MHz clock frequency = 12.5 ns clock period, DDR operations and duty cycle of 45% or higher  
tCLH = 0.45 × PSCK = 0.45 × 12.5 ns = 5.625 ns  
Bus impedance of 45 ohm and capacitance of 22 pf, with timing reference of 0.75VCC, the rise time from 0 to 1 or  
fall time 1 to 0 is 1.4[33] × RC time constant (Tau)[33] = 1.4 × 0.99 ns = 1.39 ns  
t
OTT = rise time + fall time = 1.39 ns + 1.39 ns = 2.78 ns.  
Data valid window  
tDV = tCLH – tIO_SKEW – tOTT = 5.625 ns – 400 ps – 2.78 ns = 2.45 ns  
tV Minimum  
tV _min = tHO + tIO_SKEW + tOTT = 1.0 ns + 400 ps + 2.78 ns = 4.38 ns  
Notes  
28.tCLH is the shorter duration of tCL or tCH  
.
29.tO_SKEW is the maximum difference (delta) between the minimum and maximum tV (output valid) across all  
IO signals.  
30.tOTT is the maximum Output Transition Time from one valid data value to the next valid data value on each  
IO. tOTT is dependent on system level considerations including:  
a.Memory device output impedance (drive strength).  
b.System level parasitics on the IOs (primarily bus capacitance).  
c.Host memory controller input VIH and VIL levels at which 0 to 1 and 1 to 0 transitions are recognized.  
d.tOTT is not a specification tested by Cypress, it is system dependent and must be derived by the system  
designer based on the above considerations.  
31.tDV is the data valid window.  
32.Tau = R (Output Impedance) x C (Load capacitance).  
33.Multiplier of Tau time for voltage to rise to 75% of VCC  
.
Datasheet  
44 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Physical interface  
7
Physical interface  
7.1  
7.1.1  
Connection diagrams  
SOIC 16-lead  
Figure 36  
16-lead SOIC package, Top view[34]  
7.1.2  
BGA 24-ball, 5x5 ball footprint (ZSA024)  
Figure 37  
24-ball BGA, 5x5 ball footprint (FAB024), Top view[35, 36]  
7.1.3  
Special handling instructions for FBGA packages  
Flash memory devices in BGA packages may be damaged if exposed to ultrasonic cleaning methods. The package  
and/or data integrity may be compromised if the package body is exposed to temperatures above 150 °C for  
prolonged periods of time.  
Notes  
34.The RESET# input has an internal pull-up and may be left unconnected in the system if Quad Mode and  
hardware reset are not in use.  
35.Signal connections are in the same relative positions as FAC024 BGA, allowing a single PCB footprint to use  
either package.  
36.The RESET# input has an internal pull-up and may be left unconnected in the system if Quad Mode and  
hardware reset are not in use.  
Datasheet  
45 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Physical interface  
7.2  
Physical diagrams  
SOIC 16-lead, 300-mil body width (SL3016)  
7.2.1  
A-B  
C
0.20  
0.10  
C
D
2X  
0.33  
C
0.25  
0.10  
M
C A-B D  
C
0.10  
C
DIMENSIONS  
NOTES:  
SYMBOL  
MIN.  
NOM.  
MAX.  
2.65  
1. ALL DIMENSIONS ARE IN MILLIMETERS.  
2. DIMENSIONING AND TOLERANCING PER ASME Y14.5M - 1994.  
A
A1  
A2  
b
2.35  
0.10  
2.05  
-
3. DIMENSION D DOES NOT INCLUDE MOLD FLASH, PROTRUSIONS OR GATE BURRS.  
MOLD FLASH, PROTRUSIONS OR GATE BURRS SHALL NOT EXCEED 0.15 mm PER  
END. DIMENSION E1 DOES NOT INCLUDE INTERLEAD FLASH OR PROTRUSION.  
INTERLEAD FLASH OR PROTRUSION SHALL NOT EXCEED 0.25 mm PER SIDE.  
D AND E1 DIMENSIONS ARE DETERMINED AT DATUM H.  
4. THE PACKAGE TOP MAY BE SMALLER THAN THE PACKAGE BOTTOM. DIMENSIONS  
D AND E1 ARE DETERMINED AT THE OUTMOST EXTREMES OF THE PLASTIC BODY  
EXCLUSIVE OF MOLD FLASH, TIE BAR BURRS, GATE BURRS AND INTERLEAD  
FLASH, BUT INCLUSIVE OF ANY MISMATCH BETWEEN THE TOP AND BOTTOM OF  
THE PLASTIC BODY.  
-
0.30  
2.55  
0.51  
0.48  
-
0.31  
0.27  
0.20  
0.20  
-
b1  
c
-
0.33  
0.30  
-
-
c1  
5. DATUMS A AND B TO BE DETERMINED AT DATUM H.  
6. "N" IS THE MAXIMUM NUMBER OF TERMINAL POSITIONS FOR THE SPECIFIED  
D
E
10.30 BSC  
10.30 BSC  
7.50 BSC  
PACKAGE LENGTH.  
7. THE DIMENSIONS APPLY TO THE FLAT SECTION OF THE LEAD BETWEEN 0.10 TO  
0.25 mm FROM THE LEAD TIP.  
8. DIMENSION "b" DOES NOT INCLUDE DAMBAR PROTRUSION. ALLOWABLE DAMBAR  
PROTRUSION SHALL BE 0.10 mm TOTAL IN EXCESS OF THE "b" DIMENSION AT  
MAXIMUM MATERIAL CONDITION. THE DAMBAR CANNOT BE LOCATED ON THE  
LOWER RADIUS OF THE LEAD FOOT.  
E1  
e
1.27 BSC  
-
L
1.27  
0.40  
L1  
L2  
N
9. THIS CHAMFER FEATURE IS OPTIONAL. IF IT IS NOT PRESENT, THEN A PIN 1  
IDENTIFIER MUST BE LOCATED WITHIN THE INDEX AREA INDICATED.  
10. LEAD COPLANARITY SHALL BE WITHIN 0.10 mm AS MEASURED FROM THE  
SEATING PLANE.  
1.40 REF  
0.25 BSC  
16  
h
0.25  
0°  
-
-
-
-
0.75  
8°  
0
0 1  
0 2  
5°  
15°  
-
0°  
002-15547 *A  
Datasheet  
46 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Physical interface  
7.2.2  
Ball grid array 24-ball FBGA 8.0 x 6.0 X 1.2 mm (ZSA024)  
NOTES:  
DIMENSIONS  
SYMBOL  
1. ALL DIMENSIONS ARE IN MILLIMETERS.  
MIN.  
-
NOM.  
MAX.  
1.20  
-
A
A1  
D
-
2. DIMENSIONING AND TOLERANCING METHODS PER ASME Y14.5M-1994.  
3. BALL POSITION DESIGNATION PER JEP95, SECTION 3, SPP-020.  
0.20  
-
8.00 BSC  
6.00 BSC  
4.00 BSC  
4.00 BSC  
5
4.  
e REPRESENTS THE SOLDER BALL GRID PITCH.  
E
5. SYMBOL "MD" IS THE BALL MATRIX SIZE IN THE "D" DIRECTION.  
SYMBOL "ME" IS THE BALL MATRIX SIZE IN THE "E" DIRECTION.  
n IS THE NUMBER OF POPULATED SOLDER BALL POSITIONS FOR MATRIX SIZE  
MD X ME.  
D1  
E1  
MD  
ME  
n
5
24  
6
DIMENSION "b" IS MEASURED AT THE MAXIMUM BALL DIAMETER IN A PLANE  
PARALLEL TO DATUM C.  
b
0.35  
0.40  
0.45  
eD  
eE  
SD  
SE  
1.00 BSC  
1.00 BSC  
0.00  
7
"SD" AND "SE" ARE MEASURED WITH RESPECT TO DATUMS A AND B AND DEFINE  
THE POSITION OF THE CENTER SOLDER BALL IN THE OUTER ROW.  
WHEN THERE IS AN ODD NUMBER OF SOLDER BALLS IN THE OUTER ROW,  
0.00  
"SD" OR "SE" = 0.  
WHEN THERE IS AN EVEN NUMBER OF SOLDER BALLS IN THE OUTER ROW,  
"SD" = eD/2 AND "SE" = eE/2.  
8. "+" INDICATES THE THEORETICAL CENTER OF DEPOPULATED BALLS.  
9. A1 CORNER TO BE IDENTIFIED BY CHAMFER, LASER OR INK MARK,  
METALLIZED MARK INDENTATION OR OTHER MEANS.  
002-15078 **  
DRAWN BY  
DATE  
Datasheet  
47 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8
Address space maps  
8.1  
Overview  
8.1.1  
Extended address  
The FS-S family supports 32-bit (4 Byte) addresses to enable higher density devices than allowed by previous  
generation (legacy) SPI devices that supported only 24-bit (3 Byte) addresses. A 24-bit, byte resolution, address  
can access only 16 MB (128 Mb) maximum density. A 32-bit, byte resolution, address allows direct addressing of  
up to a 4 GB (32 GB) address space.  
Legacy commands continue to support 24-bit addresses for backward software compatibility. Extended 32-bit  
addresses are enabled in two ways:  
• Extended Address Mode — a volatile configuration register bit that changes all legacy commands to expect  
32-bits of address supplied from the host system.  
• 4 Byte address commands — that perform both legacy and new functions, which always expect 32-bit address.  
The default condition for Extended Address Mode, after power-up or reset, is controlled by a non-volatile  
configuration bit. The default Extended Address Mode may be set for 24 or 32-bit addresses. This enables legacy  
software compatible access to the first 128 Mb of a device or for the device to start directly in 32 bit address mode.  
8.1.2  
Multiple address spaces  
Many commands operate on the main Flash memory array. Some commands operate on address spaces  
separate from the main Flash array. Each separate address space uses the full 24 or 32-bit address but may only  
define a small portion of the available address space.  
8.2  
Flash memory array  
The main Flash array is divided into erase units called physical sectors of 256 KB. The FS01GS contains two  
FS512S devices stacked in a DDP. Both the lower and upper address FS512S devices must be configured to define  
the overall sector map of the entire 1 Gb (128 MB) space selected by the CS# for the DDP. The lower address  
FS512S may be configured for bottom parameter sectors or uniform sectors. The upper address FS512S may be  
configured for top parameters or uniform sectors. When the lower address FS512S is configured for bottom  
parameter sectors the upper address FS512S must be configured as uniform sectors. When the upper address  
FS512S is configured for top parameter sectors the lower address FS512S must be configured as uniform sectors.  
In this way, the overall address space of the DDP may have bottom, or top parameter sectors, or uniform sectors.  
No other configurations are supported.  
Table 16  
S70FS01GS sector address map, bottom 4 KB sectors  
Address range  
(Byte address)  
Sector size (KB)  
Sector count  
Sector range  
Notes  
SA00  
:
SA7  
SA8  
SA9  
:
00000000h–00000FFFh  
:
00007000h–00007FFFh  
00008000h–0003FFFFh  
00040000h–0007FFFFh  
:
4
8
1
Sector Starting  
Address  
224  
256  
Sector Ending  
Address  
511  
SA519  
07FC0000h–07FFFFFFh  
Datasheet  
48 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Table 17  
S70FS01GS sector address map, top 4 KB sectors  
Address range  
(Byte address)  
Sector size (KB)  
Sector count  
Sector range  
Notes  
SA00  
:
SA510  
SA511  
SA512  
:
0000000h–003FFFFh  
:
07F80000h–07FBFFFFh  
07FC0000h–07FF7FFFh  
07FF8000h–07FF8FFFh  
:
256  
224  
4
511  
1
Sector Starting  
Address  
Sector Ending  
Address  
8
SA519  
07FFF000h–07FFFFFFh  
Table 18  
S70FS01GS sector address map (Uniform sectors)  
Address range  
(Byte address)  
Sector size (KB)  
Sector count  
Sector range  
Notes  
SA00  
:
00000000h–0003FFFFh  
:
Sector Starting  
Address  
256  
512  
Sector Ending  
Address  
SA511  
07FC0000h–07FFFFFFh  
Note These are condensed tables that use a couple of sectors as references. There are address ranges that are  
not explicitly listed. All 4 KB sectors have the pattern XXXX000h–XXXXFFFh. All 256 KB sectors have the pattern  
XX00000h–XX3FFFFh, XX40000h–XX7FFFFh, XX80000h–XXCFFFFh, or XXD0000h–XXFFFFFh.  
8.3  
ID-CFI address space  
The RDID command (9Fh) reads information from a separate Flash memory address space for device  
identification (ID) and common flash interface (CFI) information. See “Device ID and Common Flash Interface  
(ID-CFI) Address Map” on page 141 for the tables defining the contents of the ID-CFI address space. The ID-CFI  
address space is programmed by Infineon and read-only for the host system.  
8.4  
JEDEC JESD216 serial flash discoverable parameters (SFDP) space  
The RSFDP command (5Ah) reads information from a separate Flash memory address space for device  
identification, feature, and configuration information, in accord with the JEDEC JESD216 standard for Serial  
Flash Discoverable Parameters. The ID-CFI address space is incorporated as one of the SFDP parameters. See  
“Serial Flash Discoverable Parameters (SFDP) Address Map” on page 137 for the tables defining the contents  
of the SFDP address space. The SFDP address space is programmed by Infineon and read-only for the host  
system.  
Datasheet  
49 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.5  
OTP address space  
Each FS-S family memory device has a 1024 byte one time program (OTP) address space that is separate from the  
main Flash array. The OTP area is divided into 32, individually lockable, 32-byte aligned and length regions.  
In the 32-byte region starting at address zero:  
• The 16 lowest address bytes are programmed by Infineon with a 128-bit random number. Only Infineon is able  
to program zeros in these bytes. Programming ones in these byte locations is ignored and does not affect the  
value programmed by Infineon. Attempting to program any zero in these byte locations will fail and set P_ERR.  
• The next 4 higher address bytes (OTP Lock Bytes) are used to provide one bit per OTP region to permanently  
protect each region from programming. The bytes are erased when shipped from Cypress. After an OTP region  
is programmed, it can be locked to prevent further programming, by programming the related protection bit  
in the OTP Lock Bytes.  
• The next higher 12 bytes of the lowest address region are Reserved for Future Use (RFU). The bits in these RFU  
bytes may be programmed by the host system but it must be understood that a future device may use those  
bits for protection of a larger OTP space. The bytes are erased when shipped from Cypress.  
The remaining regions are erased when shipped from Cypress, and are available for programming of additional  
permanent data.  
Refer to Figure 38 for a pictorial representation of the OTP memory space.  
The OTP memory space is intended for increased system security. OTP values, such as the random number  
programmed by Cypress, can be used to “mate” a flash component with the system CPU/ASIC to prevent device  
substitution.  
The configuration register FREEZE (CR1V[0]) bit protects the entire OTP memory space from programming when  
set to ‘1. This allows trusted boot code to control programming of OTP regions then set the FREEZE bit to prevent  
further OTP memory space programming during the remainder of normal power-on system operation.  
32 Byte OTP Region 31  
32 Byte OTP Region 30  
32 Byte OTP Region 29  
When programmed to 0, each lock  
bit protects its related 32 byte OTP  
region from any further  
programming  
.
.
.
32 Byte OTP Region 3  
32 Byte OTP Region 2  
32 Byte OTP Region 1  
32 Byte OTP Region 0  
Region 0 Expanded View  
...  
Reserved  
16 Byte Random Number  
Lock Bits 31 to 0  
Byte 0h  
Byte 10h  
Byte 1Fh  
Figure 38  
OTP address space  
Datasheet  
50 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Table 19  
Region  
OTP address map  
Byte address range (Hex)  
Contents  
Initial delivery state (Hex)  
Least Significant Byte of  
Infineon Programmed  
Random Number  
000  
...  
Cypress Programmed  
Random Number  
...  
Most Significant Byte of  
Infineon Programmed  
Random Number  
00F  
Region 0  
Region Locking Bits  
Byte 10 [bit 0] locks region 0  
from programming when = 0  
...  
Byte13 [bit 7] locksregion31  
from programming when = 0  
010 to 013  
All Bytes = FF  
Reserved for Future Use  
(RFU)  
014 to 01F  
020 to 03F  
040 to 05F  
...  
All Bytes = FF  
All Bytes = FF  
All Bytes = FF  
All Bytes = FF  
All Bytes = FF  
Available for User  
Programming  
Available for User  
Programming  
Available for User  
Programming  
Available for User  
Programming  
Region 1  
Region 2  
...  
Region 31  
3E0 to 3FF  
8.6  
Error correction code (ECC)  
Error detection and correction (EDC) is applied to all parts of the Flash address spaces other than registers. An  
Error correction code (ECC) is calculated for each group of bytes protected and the ECC is stored in a hidden area  
related to the group of bytes. The group of protected bytes and the related ECC are together called an ECC unit.  
• ECC is calculated for each 16 byte aligned and length ECC unit  
• Single Bit EDC is supported with 8 ECC bits per ECC unit, plus 1 bit for an ECC disable Flag  
• Sector erase resets all ECC disable flags in a sector to the default state (enabled)  
• ECC is programmed as part of the standard Program commands operation  
• ECC is disabled automatically if multiple programming operations are done on the same ECC unit.  
• Single byte programming or bit walking is allowed but disables ECC on the second program to the same 16 byte  
ECC unit.  
• The ECC disable flag is programmed when ECC is disabled  
• To re-enable ECC for an ECC unit that has been disabled, the Sector that includes the ECC unit must be erased  
• To ensure the best data integrity provided by EDC, each ECC unit should be programmed only once so that ECC  
is stored for that unit and not disabled.  
• The calculation, programming, and disabling of ECC is done automatically as part of programming operations.  
The detection and correction if needed is done automatically as part of read operations. The host system sees  
only corrected data from a read operation.  
• There is a command to read the ECC status for any ECC unit.  
Datasheet  
51 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
• EDC protects the OTP region - however a second program operation on the same ECC unit will disable ECC  
permanently on that ECC unit (OTP), hence an erase operation to re-enable the ECC enable/indicator bit is  
prohibited)  
8.7  
Registers  
Registers are small groups of memory cells used to configure how the FS-S Family memory device operates or to  
report the status of device operations. The registers are accessed by specific commands. The commands (and  
hexadecimal instruction codes) used for each register are noted in each register description.  
In legacy SPI memory devices the individual register bits could be a mixture of volatile, non-volatile, or OTP bits  
within the same register. In some configuration options the type of a register bit could change e.g. from  
non-volatile to volatile.  
The FS-S Family uses separate non-volatile or volatile memory cell groups (areas) to implement the different  
register bit types. However, the legacy registers and commands continue to appear and behave as they always  
have for legacy software compatibility. There is a non-volatile and a volatile version of each legacy register when  
that legacy register has volatile bits or when the command to read the legacy register has zero read latency. When  
such a register is read the volatile version of the register is delivered. During Power-On Reset (POR), hardware  
reset, or software reset, the non-volatile version of a register is copied to the volatile version to provide the  
default state of the volatile register. When non-volatile register bits are written the non-volatile version of the  
register is erased and programmed with the new bit values and the volatile version of the register is updated with  
the new contents of the non-volatile version. When OTP bits are programmed the non-volatile version of the  
register is programmed and the appropriate bits are updated in the volatile version of the register. When volatile  
register bits are written, only the volatile version of the register has the appropriate bits updated.  
The type for each bit is noted in each register description. The default state shown for each bit refers to the state  
after power-on reset, hardware reset, or software reset if the bit is volatile. If the bit is non-volatile or OTP, the  
default state is the value of the bit when the device is shipped from Cypress. Non-volatile bits have the same  
cycling (erase and program) endurance as the main Flash array.  
Datasheet  
52 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.1  
Status Register-1  
Status Register-1 Non-Volatile (SR1NV)  
8.7.1.1  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h)  
Table 20  
Bits  
Status Register-1 Non-Volatile (SR1NV)  
Field  
Default  
state  
Function  
Type  
Description  
name  
1 = Locks state of SRWD, BP, and  
configuration register-1 bits when  
WP# is LOW by not executing WRAR  
commands that would affect  
SR1NV, SR1V, CR1NV, or CR1V.  
0 = No protection, even when WP#  
is LOW  
Provides the default state for the  
Programming Error Status. Not  
user programmable.  
Status Register  
Write Disable  
Default  
7
SRWD_NV  
P_ERR_D  
Non-Volatile  
0
Programming Error  
Default  
Non-Volatile  
Read Only  
6
5
0
0
Provides the default state for the  
Erase Error Status. Not user  
programmable.  
Non-Volatile  
Read Only  
E_ERR_D Erase Error Default  
4
3
BP_NV2  
BP_NV1  
Protects the selected range of  
sectors (Block) from Program or  
Erase when the BP bits are  
configured as non-volatile  
(CR1NV[3] = 0). Programmed to  
111b when BP bits are configured  
to volatile (CR1NV[3] = 1).- after  
which these bits are no longer user  
programmable.  
Block Protection  
Non-Volatile  
Non-Volatile  
000b  
2
BP_NV0  
Provides the default state for the  
WEL Status. Not user  
Non-Volatile  
Read Only  
1
0
WEL_D  
WIP_D  
WEL Default  
WIP Default  
0
0
programmable.  
Provides the default state for the  
WIP Status. Not user  
programmable.  
Non-Volatile  
Read Only  
Status Register Write Non-volatile (SRWD_NV) SR1NV[7]: Places the device in the Hardware Protected Mode  
when this bit is set to 1 and the WP# input is driven LOW. In this mode, the Write Any Register (WRAR) commands  
(that select status register-1 or configuration register-1) are ignored and not accepted for execution, effectively  
locking the state of the Status Register-1 and Configuration Register-1 (SR1NV, SR1V, CR1NV, or CR1V) bits, by  
making the registers read-only. If WP# is HIGH, Status Register-1 and Configuration Register-1 may be changed  
by the WRAR commands. If SRWD_NV is 0, WP# has no effect and Status Register-1 and Configuration Register-1  
may be changed by the WRAR commands. WP# has no effect on the writing of any other registers. The SRWD_NV  
bit has the same non-volatile endurance as the main Flash array. The SRWD (SR1V[7]) bit serves only as a copy of  
the SRWD_NV bit to provide zero read latency.  
Program Error Default (P_ERR_D) SR1NV[6]: Provides the default state for the Programming Error Status in  
SR1V[6]. This bit is not user programmable.  
Erase Error (E_ERR) SR1V[5]: Provides the default state for the Erase Error Status in SR1V[5]. This bit is not user  
programmable.  
Datasheet  
53 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Block Protection (BP_NV2, BP_NV1, BP_NV0) SR1NV[4:2]: These bits define the main Flash array area to be  
software-protected against program and erase commands. The BP bits are selected as either volatile or  
non-volatile, depending on the state of the BP non-volatile bit (BPNV_O) in the configuration register CR1NV[3].  
When CR1NV[3] = 0 the non-volatile version of the BP bits (SR1NV[4:2]) are used to control Block Protection and  
the WRAR command writes SR1NV[4:2] and updates SR1V[4:2] to the same value. When CR1NV[3] = 1 the volatile  
version of the BP bits (SR1V[4:2]) are used to control Block Protection and the WRAR command writes SR1V[4:2]  
and does not affect SR1NV[4:2]. When one or more of the BP bits is set to 1, the relevant memory area is protected  
against program and erase. The Bulk Erase (BE) command can be executed only when the BP bits are cleared to  
0’s. See “Block Protection” on page 75 for a description of how the BP bit values select the memory array area  
protected. The non-volatile version of the BP bits have the same non-volatile endurance as the main Flash array.  
Write Enable Latch Default (WEL_D) SR1NV[1]: Provides the default state for the WEL Status in SR1V[1]. This bit  
is programmed by Cypress and is not user programmable.  
Write In Progress Default (WIP_D) SR1NV[0]: Provides the default state for the WIP Status in SR1V[0]. This bit is  
programmed by Cypress and is not user programmable.  
8.7.1.2  
Status Register-1 Volatile (SR1V)  
Related Commands: Write Enable (WREN 06h), Write Disable (WRDI 04h), Clear Status Register (CLSR 30h or 82h),  
Read Any Register (RDAR 65h), Write Any Register (WRAR 71h).  
Table 21  
Bits  
Status Register-1 Volatile (SR1V)  
Field  
Default  
state  
Function  
Type  
Description  
name  
Status Register  
Write Disable  
Programming Error  
Occurred  
Volatile  
7
6
5
SRWD  
P_ERR  
E_ERR  
Volatile copy of SR1NV[7].  
Read Only  
Volatile  
Read Only  
Volatile  
Read Only  
1 = Error occurred  
0 = No Error  
1= Error occurred  
0 = No Error  
Erase Error  
Occurred  
4
3
BP2  
BP1  
Protects selected range of sectors (Block)  
from Program or Erase when the BP bits  
are configured as volatile (CR1NV[3] = 1).  
Volatile copy of SR1NV[4:2] when BP bits  
are configured as non-volatile. User  
writable when BP bits are configured as  
volatile.  
Block Protection  
Volatile  
Volatile  
Volatile  
2
BP0  
SR1NV  
1 = Device accepts Write Registers (WRAR),  
program, or erase commands  
0 = Device ignores Write Registers (WRAR),  
program, or erase commands  
1
WEL  
Write Enable Latch  
Write in Progress  
This bit is not affected by WRAR, only  
WREN and WRDI commands affect this bit.  
1= Device Busy, an embedded operation is  
in progress such as program or erase  
0 = Ready Device is in Standby Mode and  
can accept commands  
This bit is not affected by WRAR, it only  
provides WIP status.  
Volatile  
Read Only  
0
WIP  
Datasheet  
54 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Status Register Write (SRWD) SR1V[7]: SRWD is a volatile copy of SR1NV[7]. This bit tracks any changes to the  
non-volatile version of this bit.  
Program Error (P_ERR) SR1V[6]: The Program Error Bit is used as a program operation success or failure  
indication. When the Program Error bit is set to a “1” it indicates that there was an error in the last program  
operation. This bit will also be set when the user attempts to program within a protected main memory sector,  
or program within a locked OTP region. When the Program Error bit is set to a “1” this bit can be cleared to zero  
with the Clear Status Register (CLSR) command. This is a read-only bit and is not affected by the WRAR  
commands.  
Erase Error (E_ERR) SR1V[5]: The Erase Error Bit is used as an Erase operation success or failure indication.  
When the Erase Error bit is set to a “1” it indicates that there was an error in the last erase operation. This bit will  
also be set when the user attempts to erase an individual protected main memory sector. The Bulk Erase  
command will not set E_ERR if a protected sector is found during the command execution. When the Erase Error  
bit is set to a “1” this bit can be cleared to zero with the Clear Status Register (CLSR) command. This is a read-only  
bit and is not affected by the WRAR commands.  
Block Protection (BP2, BP1, BP0) SR1V[4:2]: These bits define the main Flash array area to be  
software-protected against program and erase commands. The BP bits are selected as either volatile or  
non-volatile, depending on the state of the BP non-volatile bit (BPNV_O) in the configuration register CR1NV[3].  
When CR1NV[3] = 0 the non-volatile version of the BP bits (SR1NV[4:2]) are used to control Block Protection and  
the WRAR command writes SR1NV[4:2] and updates SR1V[4:2] to the same value. When CR1NV[3] = 1 the volatile  
version of the BP bits (SR1V[4:2]) are used to control Block Protection and the WRAR command writes SR1V[4:2]  
and does not affect SR1NV[4:2]. When one or more of the BP bits is set to 1, the relevant memory area is protected  
against program and erase. The Bulk Erase (BE) command can be executed only when the BP bits are cleared to  
0’s. See “Block Protection” on page 75 for a description of how the BP bit values select the memory array area  
protected.  
Write Enable Latch (WEL) SR1V[1]: The WEL bit must be set to 1 to enable program, write, or erase operations  
as a means to provide protection against inadvertent changes to memory or register values. The Write Enable  
(WREN) command execution sets the Write Enable Latch to a “1” to allow any program, erase, or write commands  
to execute afterwards. The Write Disable (WRDI) command can be used to set the Write Enable Latch to a “0” to  
prevent all program, erase, and write commands from execution. The WEL bit is cleared to 0 at the end of any  
successful program, write, or erase operation. Following a failed operation the WEL bit may remain set and  
should be cleared with a WRDI command following a CLSR command. After a power down / power up sequence,  
hardware reset, or software reset, the Write Enable Latch is set to a “0” The WRAR command does not affect this  
bit.  
Write In Progress (WIP) SR1V[0]: Indicates whether the device is performing a program, write, erase operation,  
or any other operation, during which a new operation command will be ignored. When the bit is set to a “1” the  
device is busy performing an operation. While WIP is “1, only Read Status (RDSR1 or RDSR2), Read Any Register  
(RDAR), Erase Suspend (ERSP), Program Suspend (PGSP), Clear Status Register (CLSR), and Software Reset  
(RESET) commands are accepted. ERSP and PGSP will only be accepted if memory array erase or program  
operations are in progress. The status register E_ERR and P_ERR bits are updated while WIP = 1. When P_ERR or  
E_ERR bits are set to one, the WIP bit will remain set to one indicating the device remains busy and unable to  
receive new operation commands. A Clear Status Register (CLSR) command must be received to return the device  
to Standby Mode. When the WIP bit is cleared to 0 no operation is in progress. This is a read-only bit.  
Datasheet  
55 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.2  
Status Register 2 Volatile (SR2V)  
Related Commands: Read Any Register (RDAR 65h). Status Register 2 does not have user programmable  
non-volatile bits, all defined bits are volatile read only status. The default state of these bits are set by hardware.  
Table 22  
Bits  
Status Register-2 Volatile (SR2V)  
Field  
Default  
state  
Function  
Type  
Description  
name  
7
6
5
4
3
RFU  
RFU  
RFU  
RFU  
RFU  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
0
0
0
0
0
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
1 = Sector Erase Status command result =  
Erase Completed  
0 = Sector Erase Status command result =  
Erase Not Completed  
Volatile  
Read Only  
2
ESTAT  
Erase Status  
0
Erase  
Volatile  
1 = In Erase Suspend Mode.  
1
0
ES  
PS  
0
0
Suspend  
Read Only  
0 = Not in Erase Suspend Mode.  
Program  
Suspend  
Volatile  
Read Only  
1 = In Program Suspend Mode.  
0 = Not in Program Suspend Mode.  
Erase Status (ESTAT) SR2V[2]: The Erase Status bit indicates whether the sector, selected by an immediately  
preceding Erase status command, completed the last erase command on that sector. The Erase Status command  
must be issued immediately before reading SR2V to get valid erase status. Reading SR2V during a program or  
erase suspend does not provide valid erase status. The erase status bit can be used by system software to detect  
any sector that failed its last erase operation. This can be used to detect erase operations failed due to loss of  
power during the erase operation.  
Erase Suspend (ES) SR2V[1]: The Erase Suspend bit is used to determine when the device is in Erase Suspend  
Mode. This is a status bit that cannot be written by the user. When Erase Suspend bit is set to “1, the device is in  
Erase Suspend Mode. When Erase Suspend bit is cleared to “0, the device is not in Erase Suspend Mode. Refer to  
“Erase or Program Suspend (EPS 85h, 75h)” on page 120 for details about the Erase Suspend/Resume  
commands.  
Program Suspend (PS) SR2V[0]: The Program Suspend bit is used to determine when the device is in Program  
Suspend Mode. This is a status bit that cannot be written by the user. When Program Suspend bit is set to “1, the  
device is in Program Suspend Mode. When the Program Suspend bit is cleared to “0, the device is not in Program  
Suspend Mode. Refer to “Erase or Program Suspend (EPS 85h, 75h)” on page 120 for details.  
Datasheet  
56 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.3  
Configuration Register 1  
Configuration register 1 controls certain interface and data protection functions. The register bits can be changed  
using the WRAR command.  
8.7.3.1  
Configuration Register 1 Non-volatile (CR1NV)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h).  
Table 23  
Configuration Register 1 Non-volatile (CR1NV)  
Default  
Bits Field name  
Function  
Type  
Description  
state  
7
6
RFU  
RFU  
0
0
Reserved for Future  
Use  
Non-volatile  
Reserved  
Configures Start of  
Block Protection  
and selects  
readable boot  
sector in Read  
Password Mode  
1 = BP starts at bottom (Low address)  
0 = BP starts at top (High address)  
5
TBPROT_O  
OTP  
0
Reserved for Future  
Use  
Configures BP2–0  
in Status Register  
4
3
RFU  
OTP  
OTP  
0
0
Reserved for Future Use  
1 = Volatile  
0 = Non-Volatile  
BPNV_O  
1 = 4 KB physical sectors at top, (High  
address)  
Configures  
TBPARM_O Parameter Sectors  
location  
2
OTP  
0
0 = 4 KB physical sectors at bottom (Low  
address)  
RFU in uniform sector configuration.  
Provides the default state for the QUAD  
bit.  
Provides the default state for the Freeze  
bit. Not user programmable.  
1
0
QUAD_NV Quad Non-Volatile Non-Volatile  
Non-Volatile  
0
0
FREEZE_D  
FREEZE Default  
Read Only  
Top or Bottom Protection (TBPROT_O) CR1NV[5]: This bit defines the operation of the Block Protection bits  
BP2, BP1, and BP0 in the Status Register. As described in the status register section, the BP2–0 bits allow the user  
to optionally protect a portion of the array, ranging from 1/64, ¼, ½, etc., up to the entire array. When TBPROT_O  
is set to a “0” the Block Protection is defined to start from the top (maximum address) of the array. When  
TBPROT_O is set to a “1” the Block Protection is defined to start from the bottom (zero address) of the array. The  
TBPROT_O bit is OTP and set to a “0” when shipped from Cypress. If TBPROT_O is programmed to 1, writing the  
bit with a zero does not change the value or set the Program Error bit (P_ERR in SR1V[6]).  
The desired state of TBPROT_O must be selected during the initial configuration of the device during system  
manufacture; before the first program or erase operation on the main Flash array. TBPROT_O must not be  
programmed after programming or erasing is done in the main Flash array.  
When Read Password Mode is active, TBPROT_O also selects the boot address range that is readable after power  
on reset. When TBPROT_O is cleared to a “0” the bottom (zero address) 256 KB of the array is readable. When  
TBPROT_O is set to a “1” the top (maximum address) 256 KB of the array is readable.  
CR1NV[4]: Reserved for Future Use  
Datasheet  
57 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Block Protection Non-Volatile (BPNV_O) CR1NV[3]: The BPNV_O bit defines whether the BP_NV 2–0 bits or the  
BP 2–0 bits in the Status Register are selected to control the Block Protection feature. The BPNV_O bit is OTP and  
cleared to a “0” with the BP_NV bits cleared to “000” when shipped from Cypress. When BPNV_O is set to a “0”  
the BP_NV 2–0 bits in the Status Register are selected to control the block protection and are written by the WRAR  
command. The time required to write the BP_NV bits is tW. When BPNV is set to a “1” the BP2–0 bits in the Status  
Register are selected to control the block protection and the BP_NV 2–0 bits will be programmed to binary “111.  
This will cause the BP 2–0 bits to be set to binary 111 after POR, hardware reset, or command reset. When BPNV  
is set to a 1, use the WRAR to write only the volatile version of the BP bits (SR1V[4:2]). This allows the BP bits to  
be written an unlimited number of times because they are volatile and the time to write the volatile BP bits is the  
much faster tCS volatile register write time. If BPNV_O is programmed to 1, writing the bit with a zero does not  
change the value or set the Program Error bit (P_ERR in SR1V[6]).  
TBPARM_O CR1NV[2]: TBPARM_O defines the logical location of the parameter block. The parameter block  
consists of eight 4 KB parameter sectors, which replace a 32 KB portion of the highest or lowest address sector.  
When TBPARM_O is set to a “1” the parameter block is in the top of the memory array address space. When  
TBPARM_O is set to a “0” the parameter block is at the Bottom of the array. TBPARM_O is OTP and set to a “0”  
when it ships from Cypress. If TBPARM_O is programmed to 1, writing the bit with a zero does not change the  
value or set the Program Error bit (P_ERR in SR1V[6]).  
The desired state of TBPARM_O must be selected during the initial configuration of the device during system  
manufacture; before the first program or erase operation on the main Flash array. TBPARM_O must not be  
programmed after programming or erasing is done in the main Flash array.  
TBPROT_O can be set or cleared independent of the TBPARM_O bit. Therefore, the user can elect to store  
parameter information from the bottom of the array and protect boot code starting at the top of the array, or vice  
versa. Or, the user can elect to store and protect the parameter information starting from the top or bottom  
together.  
When the memory array is configured as uniform sectors, the TBPARM_O bit is Reserved for Future Use (RFU) and  
has no effect because all sectors are uniform size.  
Quad Data Width Non-volatile (QUAD_NV) CR1NV[1]: Provides the default state for the QUAD bit in CR1V[1].  
The WRAR command affects this bit. Non-volatile selection of QPI Mode, by programming CR2NV[6] = 1, will also  
program QUAD_NV = 1 to change the non-volatile default to Quad Data Width Mode. While QPI Mode is selected  
by CR2V[6] = 1, the Quad_NV bit cannot be cleared to 0.  
Freeze Protection Default (FREEZE) CR1NV[0]: Provides the default state for the FREEZE bit in CR1V[0]. This bit  
is not user programmable.  
Datasheet  
58 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.3.2  
Configuration Register 1 Volatile (CR1V)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h).  
Table 24  
Configuration Register 1 Volatile (CR1V)  
Default  
state  
Bits Field name  
Function  
Type  
Description  
7
6
RFU  
RFU  
Reserved for Future  
Use  
Volatile  
Reserved  
Volatile copy of  
TBPROT_O  
Volatile  
Not user writable  
5
4
3
2
1
TBPROT  
RFU  
Read Only  
See CR1NV[5] TBPROT_O  
Volatile  
Read Only  
Volatile  
Read Only  
Volatile  
Read Only  
RFU  
Reserved for Future Use  
Volatile copy of  
BPNV_O  
Volatile copy of  
TBPARM_O  
Not user writable  
See CR1NV[3] BPNV_O  
Not user writable  
See CR1NV[2] TBPARM_O  
1 = Quad  
0 = Dual or Serial  
Lock current state of Block Protection  
control bits, and OTP regions  
1 = Block Protection and OTP locked  
0 = Block Protection and OTP un-locked  
BPNV  
CR1NV  
TBPARM  
QUAD  
Quad I/O Mode  
Volatile  
Volatile  
Lock-down Block  
Protection until  
next power cycle  
0
FREEZE  
TBPROT, BPNV, and TBPARM CR1V[5,3,2]: These bits are volatile copies of the related non-volatile bits of  
CR1NV. These bits track any changes to the related non-volatile version of these bits.  
Quad Data Width (QUAD) CR1V[1]: When set to 1, this bit switches the data width of the device to 4 bit - Quad  
Mode. That is, WP# becomes IO2 and IO3 / RESET# becomes an active I/O signal when CS# is LOW or the RESET#  
input when CS# is HIGH. The WP# input is not monitored for its normal function and is internally set to HIGH  
(inactive). The commands for Serial, and Dual I/O Read still function normally but, there is no need to drive the  
WP# input for those commands when switching between commands using different data path widths. Similarly,  
there is no requirement to drive the IO3 / RESET# during those commands (while CS# is LOW). The QUAD bit must  
be set to one when using the Quad I/O Read, DDR Quad I/O Read, QPI Mode (CR2V[6] = 1), and Read Quad ID  
commands. While QPI Mode is selected by CR2V[6] = 1, the Quad bit cannot be cleared to 0. Use the WRAR  
command to write the non-volatile version of the Quad bit (CR1NV[1]), which also causes an update to the volatile  
version CR1V[1]. The WRAR command must be used when it is desired to write the volatile Quad bit CR1V[1]  
without affecting the non-volatile version CR1NV[1].  
Datasheet  
59 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Freeze Protection (FREEZE) CR1V[0]: The Freeze Bit, when set to 1, locks the current state of the Block  
Protection control bits and OTP area:  
• BPNV_2-0 bits in the non-volatile Status Register 1 (SR1NV[4:2])  
• BP 2-0 bits in the volatile Status Register 1 (SR1V[4:2])  
• TBPROT_O, TBPARM_O, and BPNV_O bits in the non-volatile Configuration Register (CR1NV[5, 3, 2])  
• TBPROT, TBPARM, and BPNV bits in the volatile Configuration Register (CR1V[5, 3, 2]) are indirectly protected  
in that they are shadows of the related CR1NV OTP bits and are read only  
• the entire OTP memory space  
Any attempt to change the above listed bits while FREEZE = 1 is prevented:  
• The WRAR command does not affect the listed bits and no error status is set.  
• The OTPP command, with an address within the OTP area, fails and the P-ERR status is set.  
As long as the FREEZE bit remains cleared to logic 0 the Block Protection control bits and FREEZE are writable,  
and the OTP address space is programmable.  
Once the FREEZE bit has been written to a logic 1 it can only be cleared to a logic 0 by a power-off to power-on  
cycle or a hardware reset. Software reset will not affect the state of the FREEZE bit.  
The CR1V[0] FREEZE bit is volatile and the default state of FREEZE after power-on comes from FREEZE_D in  
CR1NV[0]. The FREEZE bit can be set in parallel with updating other values in CR1V by a single WRAR command.  
The FREEZE bit does not prevent the WRAR commands from changing the SRWD_NV (SR1NV[7]), Quad_NV  
(CR1NV[1]), or QUAD (CR1V[1]) bits.  
Datasheet  
60 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.4  
Configuration Register 2  
Configuration register 2 controls certain interface functions. The register bits can be read and changed using the  
Read Any Register and Write Any Register commands. The non-volatile version of the register provides the ability  
to set the POR, hardware reset, or software reset state of the controls. These configuration bits are OTP and may  
only have their default state changed to the opposite value one time during system configuration. The volatile  
version of the register controls the feature behavior during normal operation.  
8.7.4.1  
Configuration Register 2 Non-volatile (CR2NV)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h).  
Table 25  
Configuration Register 2 Non-volatile (CR2NV)  
Default  
Bits Field name  
Function  
Type  
Description  
state  
1 = 4 byte address  
7
6
AL_NV  
QA_NV  
Address Length  
0
0 = 3 byte address  
1 = Enabled -- QPI (4-4-4) protocol in use  
0 = Disabled -- Legacy SPI protocols in use,  
instruction is always serial on SI  
1 = Enabled -- IO3 is used as RESET# input  
when CS# is high or Quad Mode is disabled  
CR1V[1] = 1  
0 = Disabled -- IO3 has no alternate  
function, hardware reset is disabled.  
QPI  
0
0
5
IO3R_NV  
RFU  
IO3 Reset  
Reserved  
OTP  
4
3
2
1
0
1
0
0
Reserved For Future Use  
0 to 15 latency (dummy) cycles following  
read address or continuous mode bits.  
Note that bit 3 has a default value of 1 and  
may be programmed one time to 0 but  
cannot be returned to 1.  
RL_NV  
Read Latency  
0
0
Address Length Non-volatile CR2NV[7]: This bit controls the POR, hardware reset, or software reset state of the  
expected address length for all commands that require address and are not fixed 3 byte only or 4 Byte (32 bit)  
only address. Most commands that need an address are legacy SPI commands that traditionally used 3 byte  
(24 bit) address. For device densities greater than 128 Mbit a 4 Byte address is required to access the entire  
memory array. The address length configuration bit is used to change most 3 Byte address commands to expect  
4 Byte address. See Table 46 for command address length. This non-volatile Address Length configuration bit  
enables the device to start immediately (boot) in 4 Byte address mode rather than the legacy 3 Byte address  
mode.  
QPI Non-volatile CR2NV[6]: This bit controls the POR, hardware reset, or software reset state of the expected  
instruction width for all commands. Legacy SPI commands always send the instruction one bit wide (serial I/O)  
on the SI (IO0) signal. The FS-S Family also supports the QPI Mode in which all transfers between the host system  
and memory are 4 bits wide on IO0 to IO3, including all instructions. This non-volatile QPI configuration bit  
enables the device to start immediately (boot) in QPI Mode rather than the legacy Serial Instruction Mode. When  
this bit is programmed to QPI Mode, the QUAD_NV bit is also programmed to Quad Mode (CR1NV[1] = 1). The  
recommended procedure for moving to QPI Mode is to first use the WRAR command to set CR2V[6] = 1, QPI Mode.  
The volatile register write for QPI Mode has a short and well defined time (tCS) to switch the device interface into  
QPI Mode. Following commands can then be immediately sent in QPI protocol. The WRAR command can be used  
to program CR2NV[6] = 1, followed by polling of SR1V[0] to know when the programming operation is completed.  
Similarly, to exit QPI Mode, the WRAR command is used to clear CR2V[6] = 0. CR2NV[6] cannot be erased to 0  
because it is OTP.  
Datasheet  
61 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
IO3 Reset Non-volatile CR2NV[5]: This bit controls the POR, hardware reset, or software reset state of the IO3  
signal behavior. Most legacy SPI devices do not have a hardware reset input signal due to the limited signal count  
and connections available in traditional SPI device packages. The FS-S Family provides the option to use the IO3  
signal as a hardware reset input when the IO3 signal is not in use for transferring information between the host  
system and the memory. This non-volatile IO3 Reset configuration bit enables the device to start immediately  
(boot) with IO3 enabled for use as a RESET# signal.  
Read Latency Non-volatile CR2NV[3:0]: This bit controls the POR, hardware reset, or software reset state of the  
read latency (dummy cycle) delay in all variable latency read commands. The following read commands have a  
variable latency period between the end of address or mode and the beginning of read data returning to the host:  
• Fast Read  
• Dual I/O Read  
• Quad I/O Read  
• DDR Quad I/O Read  
• OTPR  
• ECCRD  
• RDAR  
This non-volatile read latency configuration bit sets the number of read latency (dummy cycles) in use so the  
device can start immediately (boot) with an appropriate read latency for the host system.  
Datasheet  
62 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Table 26  
Latency code (Cycles) versus frequency  
Read command maximum frequency (MHz)  
Fast Read (1-1-1)  
OTPR (1-1-1)  
RDAR (1-1-1)  
RDAR (4-4-4)  
DDR Quad I/O (1-4-4)  
DDR Quad I/O  
(4-4-4)[40]  
Latency  
code  
Quad I/O (1-4-4)  
Dual I/O (1-2-2)  
Quad I/O (4-4-4)  
Mode cycles = 0  
Mode cycles = 4  
Mode cycles = 2  
Mode cycles = 1  
0
1
2
3
4
5
6
7
8
50  
66  
80  
92  
80  
92  
40  
53  
66  
80  
92  
104  
116  
129  
133  
133  
133  
133  
133  
133  
133  
133  
N/A  
22  
34  
45  
57  
68  
80  
80  
80  
80  
80  
80  
80  
80  
80  
80  
104  
116  
129  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
104  
116  
129  
133  
133  
133  
133  
133  
133  
133  
133  
133  
9
10  
11  
12  
13  
14  
15  
Notes  
37.SCK frequency > 133 MHz SDR, or 80MHz DDR is not supported by this family of devices.  
38.The Dual I/O, Quad I/O, QPI, DDR Quad I/O, and DDR QPI, command protocols include Continuous Read  
Mode bits following the address. For the S70FS01GS, do not enable the Continuous Read Mode, this will  
cause bus contention between the two 512 Mb die. The clock cycles for these bits are not counted as part  
of the latency cycles shown in the table. Example: the legacy Quad I/O command has 2 Continuous Read  
Mode cycles following the address. Therefore, the legacy Quad I/O command without additional read  
latency is supported only up to the frequency shown in the table for a read latency of 0 cycles. By increasing  
the variable read latency the frequency of the Quad I/O command can be increased to allow operation up  
to the maximum supported 133 MHz frequency.  
39.Other read commands have fixed latency, e.g. Read always has zero read latency. RSFDP always has eight  
cycles of latency.  
40.DDR QPI is only supported for Latency Cycles 1 through 5 and for clock frequency of up to 68 MHz.  
Datasheet  
63 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.4.2  
Configuration Register 2 Volatile (CR2V)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h), 4BAM.  
Table 27  
Configuration Register 2 Volatile (CR2V)  
Default  
state  
Bits Field name  
Function  
Type  
Description  
1 = 4 byte address  
7
6
AL  
Address Length  
0 = 3 byte address  
1 = Enabled -- QPI (4-4-4) protocol in use  
0 = Disabled -- Legacy SPI protocols in use,  
instruction is always serial on SI  
QA  
QPI  
1 = Enabled -- IO3 is used as RESET# input  
when CS# is high or Quad Mode is disabled  
CR1V[1] = 1  
5
IO3R_S  
RFU  
IO3 Reset  
Reserved  
Volatile  
CR2NV  
0 = Disabled -- IO3 has no alternate  
function, hardware reset is disabled.  
4
3
2
1
0
Reserved for Future Use  
0 to 15 latency (dummy) cycles following  
read address or continuous mode bits  
RL  
Read Latency  
Address Length CR2V[7]: This bit controls the expected address length for all commands that require address  
and are not fixed 3 byte only or 4 Byte (32 bit) only address. See Table 46 for command address length. This  
volatile Address Length configuration bit enables the address length to be changed during normal operation. The  
four byte address mode (4BAM) command directly sets this bit into 4 byte address mode.  
QPI CR2V[6]: This bit controls the expected instruction width for all commands. This volatile QPI configuration  
bit enables the device to enter and exit QPI Mode during normal operation. When this bit is set to QPI Mode, the  
QUAD bit is also set to Quad Mode (CR1V[1] = 1). When this bit is cleared to legacy SPI Mode, the QUAD bit is not  
affected.  
IO3 Reset CR2V[5]: This bit controls the IO3 / RESET# signal behavior. This volatile IO3 Reset configuration bit  
enables the use of IO3 as a RESET# input during normal operation.  
Read Latency CR2V[3:0]: This bit controls the read latency (dummy cycle) delay in variable latency read  
commands These volatile configuration bits enable the user to adjust the read latency during normal operation  
to optimize the latency for different commands or, at different operating frequencies, as needed.  
Datasheet  
64 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.5  
Configuration Register 3  
Configuration register 3 controls certain command behaviors. The register bits can be read and changed using  
the Read Any Register and Write Any Register commands. The non-volatile register provides the POR, hardware  
reset, or software reset state of the controls. These configuration bits are OTP and may be programmed to their  
opposite state one time during system configuration if needed. The volatile version of configuration register 3  
allows the configuration to be changed during system operation or testing.  
8.7.5.1  
Configuration Register 3 Non-volatile (CR3NV)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h).  
Table 28  
Configuration Register 3 Non-volatile (CR3NV)  
Default  
Bits Field name  
Function  
Type  
Description  
state  
7
6
RFU  
RFU  
Reserved  
Reserved  
0
0
Reserved for Future Use  
Reserved for Future Use  
1 = Blank Check during erase enabled  
0 = Blank Check disabled  
1 = Wrap at 512 Bytes  
0 = Wrap at 256 Bytes  
5
4
BC_NV  
Blank Check  
0
0
02h_NV  
Page Buffer Wrap  
1 = 4 KB Erase disabled (Uniform Sector  
Architecture)  
0 = 4 KB Erase enabled (Hybrid Sector  
Architecture)  
OTP  
3
20h_NV  
4 KB Erase  
0
2
1
RFU  
RFU  
Reserved  
Reserved  
0
0
Reserved for Future Use  
Reserved for Future Use  
1 = F0h Software Reset is enabled  
0 = F0h Software Reset is disabled  
(ignored)  
Legacy Software  
Reset Enable  
0
F0h_NV  
0
Blank Check Non-volatile CR3NV[5]: This bit controls the POR, hardware reset, or software reset state of the  
blank check during erase feature.  
02h Non-volatile CR3NV[4]: This bit controls the POR, hardware reset, or software reset state of the page  
programming buffer address wrap point.  
20h Non-volatile CR3NV[3]: This bit controls the POR, hardware reset, or software reset state of the availability  
of 4 KB parameter sectors in the main Flash array address map.  
The desired state of 20h_NV must be selected during the initial configuration of the device during system  
manufacture; before the first program or erase operation on the main Flash array. 20h_NV must not be  
programmed after programming or erasing is done in the main Flash array.  
Both the lower and upper FS512S devices by default are configured to the Hybrid Sector Architecture with the  
4 KB sectors at the bottom address of the device (See TBPARM_O on Table 23). It is recommended to select one  
of the valid sector map options see Table 72.  
F0h Non-volatile CR3NV[0]: This bit controls the POR, hardware reset, or software reset state of the availability  
of the Cypress legacy FL-S family software reset instruction.  
Datasheet  
65 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.5.2  
Configuration Register 3 Volatile (CR3V)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h).  
Table 29  
Configuration Register 3 Volatile (CR3V)  
Default  
state  
Bits Field name  
Function  
Type  
Description  
7
6
RFU  
RFU  
Reserved  
Reserved  
Reserved for Future Use  
Reserved for Future Use  
1 = Blank Check during erase enabled  
0 = Blank Check disabled  
1 = Wrap at 512 Bytes  
0 = Wrap at 256 Bytes  
Volatile  
5
4
BC_V  
Blank Check  
02h_V  
Page Buffer Wrap  
1 = 4 KB Erase disabled (Uniform Sector  
Architecture)  
0 = 4 KB Erase enabled (Hybrid Sector  
Architecture)  
CR3NV  
Volatile,  
Read Only  
3
20h_V  
4 KB Erase  
2
1
RFU  
RFU  
Reserved  
Reserved  
Reserved for Future Use  
Reserved for Future Use  
1 = F0h Software Reset is enabled  
0 = F0h Software Reset is disabled  
(ignored)  
Volatile  
Legacy Software  
Reset Enable  
0
F0h_V  
Blank Check Volatile CR3V[5]: This bit controls the blank check during erase feature. When this feature is  
enabled an erase command first evaluates the erase status of the sector. If the sector is found to have not  
completed its last erase successfully, the sector is unconditionally erased. If the last erase was successful, the  
sector is read to determine if the sector is still erased (blank). The erase operation is started immediately after  
finding any programmed zero. If the sector is already blank (no programmed zero bit found) the remainder of the  
erase operation is skipped. This can dramatically reduce erase time when sectors being erased do not need the  
erase operation. When enabled the blank check feature is used within the parameter erase, sector erase, and bulk  
erase commands. When blank check is disabled an erase command unconditionally starts the erase operation.  
02h Volatile CR3V[4]: This bit controls the page programming buffer address wrap point. Legacy SPI devices  
generally have used a 256 Byte page programming buffer and defined that if data is loaded into the buffer beyond  
the 255 Byte location, the address at which additional bytes are loaded would be wrapped to address zero of the  
buffer. The FS-S Family provides a 512 Byte page programming buffer that can increase programming  
performance. For legacy software compatibility, this configuration bit provides the option to continue the  
wrapping behavior at the 256 Byte boundary or to enable full use of the available 512 Byte buffer by not wrapping  
the load address at the 256 Byte boundary.  
20h Volatile CR3V[3]: This bit controls the availability of 4 KB parameter sectors in the main Flash array address  
map. The parameter sectors can overlay the highest or lowest 32 KB address range of the device or they can be  
removed from the address map so that all sectors are uniform size. This bit shall not be written to a value different  
than the value of CR3NV[3]. The value of CR3V[3] may only be changed by writing CR3NV[3].  
F0h Volatile CR3V[0]: This bit controls the availability of the Cypress legacy FL-S family software reset  
instruction. The FS-S Family supports the industry common 66h + 99h instruction sequence for software reset.  
This configuration bit allows the option to continue use of the legacy F0h single command for software reset.  
Datasheet  
66 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.6  
Configuration Register 4  
Configuration register 4 controls the main Flash array read commands burst wrap behavior. The burst wrap  
configuration does not affect commands reading from areas other than the main Flash array e.g. read commands  
for registers or OTP array. The non-volatile version of the register provides the ability to set the start up (boot)  
state of the controls as the contents are copied to the volatile version of the register during the POR, hardware  
reset, or software reset. The volatile version of the register controls the feature behavior during normal  
operation. The register bits can be read and changed using the Read Any Register and Write Any Register  
commands. The volatile version of the register can also be written by the Set Burst Length (C0h) command.  
8.7.6.1  
Configuration Register 4 Non-volatile (CR4NV)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h).  
Table 30  
Configuration Register 4 Non-volatile (CR4NV)  
Default  
Bits Field name  
Function  
Output Impedance  
Wrap Enable  
Type  
Description  
state  
7
6
5
0
0
0
OI_O  
See Table 31.  
0 = Wrap Enabled  
1 = Wrap Disabled  
Reserved for Future Use  
Reserved for Future Use  
00 = 8-byte wrap  
01 = 16 byte wrap  
10 = 32 byte wrap  
11 = 64 byte wrap  
4
WE_O  
1
OTP  
3
2
1
RFU  
RFU  
Reserved  
Reserved  
0
0
0
WL_O  
Wrap Length  
0
0
Output Impedance Non-volatile CR4NV[7:5]: These bits control the POR, hardware reset, or software reset  
state of the IO signal output impedance (drive strength). Multiple drive strength are available to help match the  
output impedance with the system PCB environment to minimize overshoot and ringing. These non-volatile  
output impedance configuration bits enable the device to start immediately (boot) with the appropriate drive  
strength.  
Table 31  
Output impedance control  
CR4NV[7:5]  
Typical impedance to VSS Typical impedance to VCC  
Notes  
Impedance selection  
(Ohms)  
47  
(Ohms)  
45  
000  
001  
010  
011  
100  
101  
110  
111  
Factory default  
124  
71  
105  
64  
47  
45  
34  
35  
26  
28  
22  
24  
18  
21  
Datasheet  
67 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
Wrap Enable Non-volatile CR4NV[4]: This bit controls the POR, hardware reset, or software reset state of the  
wrap enable. The commands affected by Wrap Enable are: Quad I/O Read, and DDR Quad I/O Read. This  
configuration bit enables the device to start immediately (boot) in wrapped burst read mode rather than the  
legacy sequential read mode.  
Wrap Length Non-volatile CR4NV[1:0]: These bits controls the POR, hardware reset, or software reset state of  
the wrapped read length and alignment. These non-volatile configuration bits enable the device to start  
immediately (boot) in wrapped burst read mode rather than the legacy sequential read mode.  
8.7.6.2  
Configuration Register 4 Volatile (CR4V)  
Related Commands: Read Any Register (RDAR 65h), Write Any Register (WRAR 71h), Set Burst Length (SBL C0h).  
Table 32 Configuration Register 4 Volatile (CR4V)  
Default  
state  
Bits Field name  
Function  
Output Impedance  
Wrap Enable  
Type  
Description  
7
6
5
OI  
See Table 31.  
0 = Wrap Enabled  
1 = Wrap Disabled  
Reserved for Future Use  
Reserved for Future Use  
00 = 8-byte wrap  
01 = 16 byte wrap  
10 = 32 byte wrap  
11 = 64 byte wrap  
4
WE  
Volatile  
CR4NV  
3
2
1
RFU  
RFU  
Reserved  
Reserved  
WL  
Wrap Length  
0
Output Impedance CR2V[7:5]: These bits control the IO signal output impedance (drive strength). This volatile  
output impedance configuration bit enables the user to adjust the drive strength during normal operation.  
Wrap Enable CR4V[4]: This bit controls the burst wrap feature. This volatile configuration bit enables the device  
to enter and exit burst wrapped read mode during normal operation.  
Wrap Length CR4V[1:0]: These bits controls the wrapped read length and alignment during normal operation.  
These volatile configuration bits enable the user to adjust the burst wrapped read length during normal  
operation.  
Datasheet  
68 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.7  
ECC Status Register (ECCSR)  
Related Commands: ECC Read (ECCRD 18h or 19h). ECCSR does not have user programmable non-volatile bits,  
all defined bits are volatile read only status. The default state of these bits are set by hardware.  
The status of ECC in each ECC unit is provided by the 8-bit ECC Status Register (ECCSR). The ECC Register Read  
command is written followed by an ECC unit address. The contents of the status register then indicates, for the  
selected ECC unit, whether there is an error in the ECC, the ECC unit data, or that ECC is disabled for that ECC unit.  
Table 33  
ECC Status Register (ECCSR)  
Default  
state  
Bits Field name  
Function  
Type  
Description  
Reserved for Future Use  
1 = Single Bit Error found in the ECC unit  
error correction code  
0 = No error.  
7 to 3  
2
RFU  
Reserved  
0
EECC  
Error in ECC Volatile, Read only  
0
1 = Single Bit Error corrected in ECC unit  
Error in ECC  
1
0
EECCD  
ECCDI  
Volatile, Read only  
unit data  
0
0
data.  
0 = No error.  
1 = ECC is disabled in the selected ECC unit.  
0 = ECC is enabled in the selected ECC unit.  
ECC  
Volatile, Read only  
Disabled  
ECCSR[2] = 1 indicates an error was corrected in the ECC. ECCSR[1] = 1 indicates an error was corrected in the ECC  
unit data. ECCSR[0] = 1 indicates the ECC is disabled. The default state of “0” for all these bits indicates no failures  
and ECC is enabled.  
The ECCSR[7:3] are reserved. These have undefined high or low values that can change from one ECC status read  
to another. These bits should be treated as “don’t care” and ignored by any software reading status.  
Datasheet  
69 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.8  
ASP Register (ASPR)  
Related Commands: ASP Read (ASPRD 2Bh) and ASP Program (ASPP 2Fh), Read Any Register (RDAR 65h), Write  
Any Register (WRAR 71h).  
The ASP register is a 16 bit OTP memory location used to permanently configure the behavior of Advanced Sector  
Protection (ASP) features. ASPR does not have user programmable volatile bits, all defined bits are OTP.  
The default state of the ASPR bits are programmed by Cypress.  
Table 34  
ASP Register (ASPR)  
Default  
state  
Bits Field name  
Function  
Type  
Description  
15to9  
RFU  
RFU  
RFU  
RFU  
RFU  
RFU  
RFU  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
OTP  
OTP  
OTP  
OTP  
OTP  
OTP  
OTP  
1
1
1
1
1
1
1
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
8
7
6
5
4
3
0 = Password Protection Mode  
permanently enabled.  
1 = Password Protection Mode not  
permanently enabled.  
Password  
Protection Mode  
Lock Bit  
2
PWDMLB  
OTP  
1
0 = Persistent Protection Mode  
permanently enabled.  
Persistent  
Protection Mode  
Lock Bit  
1
0
PSTMLB  
RFU  
OTP  
OTP  
1
1
1 = Persistent Protection Mode not  
permanently enabled.  
Reserved  
Reserved for Future Use  
Reserved for Future Use (RFU) ASPR[15:3].  
Password Protection Mode Lock Bit (PWDMLB) ASPR[2]: When programmed to 0, the Password Protection  
Mode is permanently selected.  
Persistent Protection Mode Lock Bit (PSTMLB) ASPR[1]: When programmed to 0, the Persistent Protection  
Mode is permanently selected. This bit may also be used in combination with the Read Password Mode to  
permanently protect sectors that would otherwise not have protection when the read password is provided.  
PWDMLB (ASPR[2]) and PSTMLB (ASPR[1]) are mutually exclusive, only one may be programmed to zero.  
ASPR bits may only be programmed while ASPR[2:1] = 11b. Attempting to program ASPR bits when ASPR[2:1] is  
not = 11b will result in a programming error with P_ERR (SR1V[6]) set to 1. After the ASP Mode is selected by  
programming ASPR[2:1] = 10b or 01b, the state of all ASPR bits are locked and permanently protected from  
further programming. Attempting to program ASPR[2:1] = 00b will result in a programming error with P_ERR  
(SR1V[6]) set to 1.  
Similarly, OTP configuration bits listed in the ASP Register description (see “ASP register” on page 79), may only  
be programmed while ASPR[2:1] = 11b. The OTP configuration must be selected before selecting the ASP Mode.  
The OTP configuration bits are permanently protected from further change when the ASP Mode is selected.  
Attempting to program these OTP configuration bits when ASPR[2:1] is not = 11b will result in a programming  
error with P_ERR (SR1V[6]) set to 1.  
The ASP Mode should be selected during system configuration to ensure that a malicious program does not select  
an undesired protection mode at a later time. By locking all the protection configuration via the ASP Mode  
selection, later alteration of the protection methods by malicious programs is prevented.  
Datasheet  
70 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.9  
Password Register (PASS)  
Related Commands: Password Read (PASSRD E7h), Read Any Register (RDAR 65h) and Write Any Register (WRAR  
71h). The PASS register is a 64 bit OTP memory location used to permanently define a password for the Advanced  
Sector Protection (ASP) feature. PASS does not have user programmable volatile bits, all defined bits are OTP. A  
volatile copy of PASS is used to satisfy read latency requirements but the volatile register is not user writable or  
further described.  
Table 35  
Bits  
Password Register (PASS)  
Field  
Function  
Type  
Default state  
Description  
name  
Non-volatile OTP storage of 64 bit  
password. The password is no longer  
FFFFFFFF–FFFFFFFFh readable after the Password Protection  
Mode is selected by programming ASP  
register bit 2 to zero.  
Hidden  
Password  
63to0 PWD  
OTP  
8.7.10  
PPB Lock Register (PPBL)  
Related Commands: PPB Lock Read (PLBRD A7h, PLBWR A6h), Read Any Register (RDAR 65h).  
PPBL does not have separate user programmable non-volatile bits, all defined bits are volatile read only status.  
The default state of the RFU bits is set by hardware. The default state of the PPBLOCK bit is defined by the ASP  
Mode bits in ASPR[2:1]. There is no non-volatile version of the PPBL register.  
The PPBLOCK bit is used to protect the PPB bits. When PPBL[0] = 0, the PPB bits can not be programmed. In Read  
Password Protection Mode PPB Lock bit is also used to control the high order bits of address by forcing the  
address range to be limited to one sector where boot code is stored, until the read password is supplied.  
Table 36  
Bits  
PPB Lock Register (PPBL)  
Field  
Function  
Type  
Default state  
Description  
name  
7 to 1  
RFU  
Reserved  
Volatile  
00h  
Reserved for Future Use  
ASPR[2:1] = 1xb = Persistent 0 = PPB array protected  
Volatile  
Read  
Only  
Protect PPB  
Array  
Protection Mode = 1  
1 = PPB array may be programmed  
0
PPBLOCK  
ASPR[2:1] = 01b = Password or erased.  
Protection Mode = 0  
Datasheet  
71 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.11  
PPB Access Register (PPBAR)  
Related Commands: PPB Read (PPBRD FCh or 4PPBRD E2h), PPB Program (PPBP FDh or 4PPBP E3h), PPB Erase  
(PPBE E4h).  
PPBAR does not have user writable volatile bits, all PPB array bits are non-volatile. The default state of the PPB  
array is erased to FFh by Cypress. There is no volatile version of the PPBAR register.  
Table 37  
Bits  
PPB Access Register (PPBAR)  
Field  
Default  
state  
Function  
Type  
Description  
name  
00h = PPB for the sector addressed by the  
PPBRD or PPBP command is programmed  
to 0, protecting that sector from program  
or erase operations.  
FFh = PPB for the sector addressed by the  
PPBRD command is 1, not protecting that  
sector from program or erase operations.  
Read or Program  
per sector PPB  
7 to 0  
PPB  
Non-volatile  
FFh  
8.7.12  
DYB Access Register (DYBAR)  
Related Commands: DYB Read (DYBRD FAh or 4DYBRD E0h) and DYB Write (DYBWR FBh or 4DYBWR E1h).  
DYBAR does not have user programmable non-volatile bits, all bits are a representation of the volatile bits in the  
DYB array. The default state of the DYB array bits is set by hardware. There is no non-volatile version of the DYBAR  
register.  
Table 38  
Bits  
DYB Access Register (DYBAR)  
Field  
Default  
state  
Function  
Type  
Description  
name  
00h = DYB for the sector addressed by the DYBRD or  
DYBWR command is cleared to “0, protecting that  
sector from program or erase operations.  
FFh = DYB for the sector addressed by the DYBRD or  
DYBWR command is set to “1, not protecting that  
sector from program or erase operations.  
Read or  
Write per  
sector DYB  
7 to 0  
DYB  
Volatile  
FFh  
Datasheet  
72 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Address space maps  
8.7.13  
SPI DDR Data Learning Registers  
Related Commands: Write VDLR (WVDLR 4Ah), Data Learning Pattern Read (DLPRD 41h), Read Any Register  
(RDAR 65h), Write Any Register (WRAR 71h).  
The Data Learning Pattern (DLP) resides in an 8-bit Non-Volatile Data Learning Register (NVDLR) as well as an 8-bit  
Volatile Data Learning Register (VDLR). When shipped from Cypress, the NVDLR value is 00h. Once programmed,  
the NVDLR cannot be reprogrammed or erased; a copy of the data pattern in the NVDLR will also be written to the  
VDLR. The VDLR can be written to at any time, but on power cycles the data pattern will revert back to what is in  
the NVDLR. During the learning phase described in the SPI DDR modes, the DLP will come from the VDLR. Each IO  
will output the same DLP value for every clock edge. For example, if the DLP is 34h (or binary 00110100) then  
during the first clock edge all IO’s will output 0; subsequently, the 2nd clock edge all I/O’s will output 0, the 3rd  
will output 1, etc.  
When the VDLR value is 00h, no preamble data pattern is presented during the dummy phase in the DDR  
commands.  
Table 39  
Bits  
Non-Volatile Data Learning Register (NVDLR)  
Field  
Default  
state  
Function  
Type  
Description  
name  
OTP value that may be transferred to the host during  
DDR read command latency (dummy) cycles to  
provide a training pattern to help the host more  
accurately center the data capture point in the  
received data bits.  
Non-Volatile  
Data  
Learning  
Pattern  
7 to 0  
NVDLP  
OTP  
00h  
Table 40  
Bits  
Volatile Data Learning Register (VDLR)  
Field  
Default  
state  
Function  
Type  
Description  
name  
Takes the  
value of Volatile copy of the NVDLP used to enable and deliver  
NVDLR the Data Learning Pattern (DLP) to the outputs. The  
during VDLP may be changed by the host during system  
POR or operation.  
Volatile Data  
Learning  
Pattern  
7 to 0  
VDLP  
Volatile  
Reset  
Datasheet  
73 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
9
Data Protection  
9.1  
Secure Silicon Region (OTP)  
The device has a 1024 byte One Time Program (OTP) address space that is separate from the main Flash array.  
The OTP area is divided into 32, individually lockable, 32 byte aligned and length regions.  
The OTP memory space is intended for increased system security. OTP values can “mate” a flash component with  
the system CPU/ASIC to prevent device substitution. See “OTP address space” on page 50, “OTP Program  
(OTPP 42h)” on page 124, and “OTP Read (OTPR 4Bh)” on page 124.  
9.1.1  
Reading OTP Memory Space  
The OTP Read command uses the same protocol as Fast Read. OTP Read operations outside the valid 1 KB OTP  
address range will yield indeterminate data.  
9.1.2  
Programming OTP Memory Space  
The protocol of the OTP programming command is the same as Page Program. The OTP Program command can  
be issued multiple times to any given OTP address, but this address space can never be erased.  
Automatic ECC is programmed on the first programming operation to each 16 byte region. Programming within  
a 16 byte region more than once disables the ECC. It is recommended to program each 16 byte portion of each  
32 byte region once so that ECC remains enabled to provide the best data integrity.  
The valid address range for OTP Program is depicted in Figure 38. OTP Program operations outside the valid OTP  
address range will be ignored, without P_ERR in SR1V set to “1. OTP Program operations within the valid OTP  
address range, while FREEZE = 1, will fail with P_ERR in SR1V set to “1. The OTP address space is not protected  
by the selection of an ASP Mode. The Freeze bit (CR1V[0]) may be used to protect the OTP Address Space.  
9.1.3  
Cypress Programmed Random Number  
Cypress standard practice is to program the low order 16 bytes of the OTP memory space (locations 0x0 to 0xF)  
with a 128-bit random number using the Linear Congruential Random Number Method. The seed value for the  
algorithm is a random number concatenated with the day and time of tester insertion.  
9.1.4  
Lock Bytes  
The LSB of each Lock byte protects the lowest address region related to the byte, the MSB protects the highest  
address region related to the byte. The next higher address byte similarly protects the next higher 8 regions. The  
LSB bit of the lowest address Lock Byte protects the higher address 16 bytes of the lowest address region. In other  
words, the LSB of location 0x10 protects all the Lock Bytes and RFU bytes in the lowest address region from  
further programming. See “OTP address space” on page 50.  
Datasheet  
74 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
9.2  
Write Enable Command  
The Write Enable (WREN) command must be written prior to any command that modifies non-volatile data. The  
WREN command sets the Write Enable Latch (WEL) bit. The WEL bit is cleared to 0 (disables writes) during  
power-up, hardware reset, or after the device completes the following commands:  
• Reset  
• Page Program (PP or 4PP)  
• Parameter 4 KB Erase (P4E or 4P4E)  
• Sector Erase (SE or 4SE)  
• Bulk Erase (BE)  
• Write Disable (WRDI)  
• Write Any Register (WRAR)  
• OTP Byte Programming (OTPP)  
• Advanced Sector Protection Register Program (ASPP)  
• Persistent Protection Bit Program (PPBP)  
• Persistent Protection Bit Erase (PPBE)  
• Password Program (PASSP)  
• Program Non-Volatile Data Learning Register (PNVDLR)  
9.3  
Block Protection  
The Block Protect bits (Status Register bits BP2, BP1, BP0) in combination with the Configuration Register  
TBPROT_O bit can be used to protect an address range of the main Flash array from program and erase  
operations. The size of the range is determined by the value of the BP bits and the upper or lower starting point  
of the range is selected by the TBPROT_O bit of the configuration register (CR1NV[5]).  
The FS01GS contains two FS512S devices to provide the lower and upper half of the overall 1 Gb address space.  
Each FS512S has its own set of Block Protection configuration bits that affect only the address space of that  
FS512S but, the WP# signal is common to both devices.  
Table 41  
Upper Array Start of Protection (TBPROT_O = 0)  
Status Register Content  
Protected Memory  
(KB)  
Protected  
Fraction of  
FS512S  
512 Mb  
Memory Array  
BP2  
BP1  
BP0  
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
None  
0
Upper 64th  
Upper 32nd  
Upper 16th  
Upper 8th  
Upper 4th  
Upper Half  
All Sectors  
1024  
2048  
4096  
8192  
16384  
32768  
65536  
Datasheet  
75 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
Table 42  
Lower Array Start of Protection (TBPROT_O = 1)  
Protected Memory  
(KB)  
Status Register Content  
BP1  
Protected  
Fraction of  
FS512S  
512 Mb  
Memory Array  
BP2  
BP0  
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
None  
0
Lower 64th  
Lower 32nd  
Lower 16th  
Lower 8th  
Lower 4th  
Lower Half  
All Sectors  
1024  
2048  
4096  
8192  
16384  
32768  
65536  
When Block Protection is enabled (i.e., any BP2–0 are set to “1”), Advanced Sector Protection (ASP) can still be  
used to protect sectors not protected by the Block Protection scheme. In the case that both ASP and Block  
Protection are used on the same sector the logical OR of ASP and Block Protection related to the sector is used.  
9.3.1  
Freeze bit  
Bit 0 of Configuration Register 1 (CR1V[0]) is the FREEZE bit. The Freeze Bit, when set to 1, locks the current state  
of the Block Protection control bits and OTP area until the next power off-on cycle. Additional details in  
“Configuration Register 1 Volatile (CR1V)” on page 59.  
9.3.2  
Write Protect Signal  
The Write Protect (WP#) input in combination with the Status Register Write Disable (SRWD) bit (SR1NV[7])  
provide hardware input signal controlled protection. When WP# is LOW and SRWD is set to “1” Status Register-1  
(SR1NV and SR1V) and Configuration register-1 (CR1NV and CR1V) are protected from alteration. This prevents  
disabling or changing the protection defined by the Block Protect bits. See “Status Register-1” on page 53.  
Datasheet  
76 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
9.4  
Advanced sector protection  
Advanced sector protection (ASP) is the name used for a set of independent hardware and software methods  
used to disable or enable programming or erase operations, individually, in any or all sectors.  
Every main Flash array sector has a non-volatile Persistent Protection Bit (PPB) and a volatile dynamic protection  
bit (DYB) associated with it. When either bit is ‘0, the sector is protected from program and erase operations. The  
PPB bits are protected from program and erase when the volatile PPB Lock bit is ‘0. There are two methods for  
managing the state of the PPB Lock bit: Password Protection and Persistent Protection. An overview of these  
methods is shown in Figure 40.  
Block Protection and ASP protection settings for each sector are logically ORed to define the protection for each  
sector i.e. if either mechanism is protecting a sector the sector cannot be programmed or erased. Refer to “Block  
Protection” on page 75 for full details of the BP2-0 bits.  
The FS01GS contains two FS512S devices to provide the lower and upper half of the overall 1 Gb address space.  
Each FS512S has its own set of ASP configuration bits that affect only the address space that FS512S.  
Dynamic  
Protection  
Bits Array  
(DYB)  
Persistent  
Protection  
Bits Array  
(PPB)  
Flash  
Memory  
Array  
Sector 0  
Sector 0  
Sector 0  
Sector 1  
Sector 1  
Sector 1  
Block  
Protection  
Logic  
Sector N  
Sector N  
Sector N  
Figure 39  
Sector protection control  
Datasheet  
77 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
Power On / Reset  
ASPR[2]=0  
ASPR[1]=0  
No  
No  
Yes  
Yes  
Password Protection  
Default  
Persistent Protection  
Persistent Protection  
ASPR Bits Locked  
ASPR Bits Locked  
ASPR Bits Are  
Programmable  
PPBLOCK = 0  
PPBLOCK = 1  
PPB Bits Locked  
PPB Bits Erasable  
and Programmable  
No  
No  
PPB Lock Bit Write  
Password Unlock  
Yes  
Yes  
PPBLOCK = 1  
PPB Bits Erasable  
and Programmable  
PPBLOCK = 0  
PPB Bits Locked  
No  
PPB Lock Bit Write  
Yes  
Default Mode allows ASPR to be pro-  
grammed to permanently select the Protec-  
tion Mode.  
Persistent Protection Mode  
does not protect the PPB  
after power up. The PPB bits  
may be changed. A PPB Lock  
Bit write command protects  
the PPB bits until the next  
power off or reset.  
Password Protection Mode pro-  
tects the PPB after power up. A  
password unlock command will  
enable changes to PPB.  
A PPB Lock Bit write  
command turns protection back  
on.  
The default mode otherwise acts the same  
as the Persistent Protection Mode.  
After one of the protection modes is  
selected, ASPR is no longer programmable,  
making the selected Protection Mode per-  
manent.  
Figure 40  
Advanced sector protection overview  
Datasheet  
78 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
The Persistent Protection method sets the PPB Lock bit to “1” during POR, or Hardware Reset so that the PPB bits  
are unprotected by a device reset. There is a command to clear the PPB Lock bit to “0” to protect the PPB. There  
is no command in the Persistent Protection method to set the PPB Lock bit to “1, therefore the PPB Lock bit will  
remain at “0” until the next power-off or hardware reset. The Persistent Protection method allows boot code the  
option of changing sector protection by programming or erasing the PPB, then protecting the PPB from further  
change for the remainder of normal system operation by clearing the PPB Lock bit to “0. This is sometimes called  
Boot-code controlled sector protection.  
The Password method clears the PPB Lock bit to “0” during POR, or Hardware Reset to protect the PPB. A 64 bit  
password may be permanently programmed and hidden for the password method. A command can be used to  
provide a password for comparison with the hidden password. If the password matches, the PPB Lock bit is set  
to “1” to unprotect the PPB. A command can be used to clear the PPB Lock bit to “0. This method requires use  
of a password to control PPB protection.  
The selection of the PPB Lock bit management method is made by programming OTP bits in the ASP Register so  
as to permanently select the method used.  
9.4.1  
ASP register  
The ASP register is used to permanently configure the behavior of Advanced Sector Protection (ASP) features.  
See Table 34.  
As shipped from the factory, all devices default ASP to the Persistent Protection Mode, with all sectors  
unprotected, when power is applied. The device programmer or host system must then choose which sector  
protection method to use. Programming either of the, one-time programmable, Protection Mode Lock Bits, locks  
the part permanently in the selected mode:  
• ASPR[2:1] = “11” = No ASP Mode selected, Persistent Protection Mode is the default.  
• ASPR[2:1] = “10” = Persistent Protection Mode permanently selected.  
• ASPR[2:1] = “01” = Password Protection Mode permanently selected.  
• ASPR[2:1] = “00” is an Illegal condition, attempting to program more than one bit to zero results in a  
programming failure.  
ASP register programming rules:  
• If the Password mode is chosen, the password must be programmed prior to setting the Protection Mode Lock  
Bits.  
• Once the Protection mode is selected, the following OTP configuration Register bits are permanently protected  
from programming and no further changes to the OTP register bits is allowed:  
- CR1NV[5:2]  
- CR2NV  
- CR3NV  
- CR4NV  
- ASPR  
- PASS  
- NVDLR  
- If an attempt to change any of the registers above, after the ASP Mode is selected, the operation will fail and  
P_ERR (SR1V[6]) will be set to 1.  
The programming time of the ASP Register is the same as the typical page programming time. The system can  
determine the status of the ASP register programming operation by reading the WIP bit in the Status Register.  
See “Status Register-1” on page 53 for information on WIP.  
See “Sector protection states summary” on page 80.  
Datasheet  
79 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
9.4.2  
Persistent protection bits  
The persistent protection bits (PPB) are located in a separate nonvolatile Flash array. One of the PPB bits is  
related to each sector. When a PPB is “0, its related sector is protected from program and erase operations. The  
PPB are programmed individually but must be erased as a group, similar to the way individual words may be  
programmed in the main array but an entire sector must be erased at the same time. The PPB have the same  
program and erase endurance as the main Flash memory array. Preprogramming and verification prior to erasure  
are handled by the device.  
Programming a PPB bit requires the typical page programming time. Erasing all the PPBs requires typical sector  
erase time. During PPB bit programming and PPB bit erasing, status is available by reading the Status register.  
Reading of a PPB bit requires the initial access time of the device.  
Notes  
1. Each PPB is individually programmed to “0” and all are erased to “1” in parallel.  
2. If the PPB Lock bit is “0, the PPB Program or PPB Erase command does not execute and fails without  
programming or erasing the PPB.  
3. The state of the PPB for a given sector can be verified by using the PPB Read command.  
9.4.3  
Dynamic protection bits  
Dynamic Protection Bits are volatile and unique for each sector and can be individually modified. DYB only  
control the protection for sectors that have their PPB set to “1. By issuing the DYB Write command, a DYB is  
cleared to “0” or set to “1, thus placing each sector in the protected or unprotected state respectively. This  
feature allows software to easily protect sectors against inadvertent changes, yet does not prevent the easy  
removal of protection when changes are needed. The DYBs can be set or cleared as often as needed as they are  
volatile bits.  
9.4.4  
PPB lock bit (PPBL[0])  
The PPB Lock Bit is a volatile bit for protecting all PPB bits. When cleared to “0, it locks all PPBs, when set to “1,  
it allows the PPBs to be changed. See “PPB Lock Register (PPBL)” on page 71 for more information.  
The PLBWR command is used to clear the PPB Lock bit to “0. The PPB Lock Bit must be cleared to “0” only after  
all the PPBs are configured to the desired settings.  
In Persistent Protection Mode, the PPB Lock is set to “1” during POR or a hardware reset. When cleared to “0, no  
software command sequence can set the PPB Lock bit to “1, only another hardware reset or power-up can set  
the PPB Lock bit.  
In the Password Protection Mode, the PPB Lock bit is cleared to “0” during POR or a hardware reset. The PPB Lock  
bit can only be set to “1” by the Password Unlock command.  
9.4.5  
Sector protection states summary  
Each sector can be in one of the following protection states:  
• Unlocked — The sector is unprotected and protection can be changed by a simple command. The protection  
state defaults to unprotected when the device is shipped from Cypress.  
• Dynamically Locked — A sector is protected and protection can be changed by a simple command. The  
protection state is not saved across a power cycle or reset.  
• Persistently Locked — A sector is protected and protection can only be changed if the PPB Lock Bit is set to “1.  
The protection state is non-volatile and saved across a power cycle or reset. Changing the protection state  
requires programming and or erase of the PPB bits  
Datasheet  
80 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
Table 43  
Sector protection states  
Protection bit values  
Sector state  
PPB lock  
PPB  
1
1
DYB  
1
0
1
1
1
1
0
0
0
0
Unprotected – PPB and DYB are changeable  
Protected – PPB and DYB are changeable  
Protected – PPB and DYB are changeable  
0
1
0
1
1
0
0
1
0
1
Protected – PPB and DYB are changeable  
Unprotected – PPB not changeable, DYB is changeable  
Protected – PPB not changeable, DYB is changeable  
Protected – PPB not changeable, DYB is changeable  
Protected – PPB not changeable, DYB is changeable  
0
0
9.4.6  
Persistent protection mode  
The Persistent Protection method sets the PPB Lock bit to “1” during POR or Hardware Reset so that the PPB bits  
are unprotected by a device hardware reset. Software reset does not affect the PPB Lock bit. The PLBWR  
command can clear the PPB Lock bit to “0” to protect the PPB. There is no command to set the PPB Lock bit  
therefore the PPB Lock bit will remain at “0” until the next power-off or hardware reset.  
9.4.7  
PPB password protection mode  
PPB Password Protection Mode allows an even higher level of security than the Persistent Sector Protection  
Mode, by requiring a 64-bit password for unlocking the PPB Lock bit. In addition to this password requirement,  
after power up and hardware reset, the PPB Lock bit is cleared to “0” to ensure protection at power-up. Successful  
execution of the Password Unlock command by entering the entire password sets the PPB Lock bit to 1, allowing  
for sector PPB modifications.  
Password Protection Notes:  
• Once the Password is programmed and verified, the Password Mode (ASPR[2]=0) must be set in order to prevent  
reading the password.  
• The Password Program Command is only capable of programming “0”s. Programming a “1” after a cell is  
programmed as a “0” results in the cell left as a “0” with no programming error set.  
• The password is all “1”s when shipped from Cypress. It is located in its own memory space and is accessible  
through the use of the Password Program, Password Read, RDAR, and WRAR commands.  
• All 64-bit password combinations are valid as a password.  
• The Password Mode, once programmed, prevents reading the 64-bit password and further password  
programming. All further program and read commands to the password region are disabled and these  
commands are ignored or return undefined data. There is no means to verify what the password is after the  
Password Mode Lock Bit is selected. Password verification is only allowed before selecting the Password  
Protection Mode.  
• The Protection Mode Lock Bits are not erasable.  
• The exact password must be entered in order for the unlocking function to occur. If the password unlock  
command provided password does not match the hidden internal password, the unlock operation fails in the  
same manner as a programming operation on a protected sector. The P_ERR bit is set to one, the WIP Bit remains  
set, and the PPB Lock bit remains cleared to 0.  
Datasheet  
81 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Protection  
• The Password Unlock command cannot be accepted any faster than once every 100 µs ± 20 µs. This makes it  
take an unreasonably long time (58 million years) for a hacker to run through all the 64-bit combinations in an  
attempt to correctly match a password. The Read Status Register 1 command may be used to read the WIP bit  
to determine when the device has completed the password unlock command or is ready to accept a new  
password command. When a valid password is provided the password unlock command does not insert the  
100 µs delay before returning the WIP bit to zero.  
• If the password is lost after selecting the Password Mode, there is no way to set the PPB Lock bit.  
• ECC status may only be read from sectors that are readable. In Read Protection Mode, the addresses are forced  
to the boot sector address. ECC status is only in that sector while Read Protection Mode is active.  
9.5  
Recommended protection process  
During system manufacture, the Flash device configuration should be defined by:  
1. Programming the OTP configuration bits in CR1NV[5, 3:2], CR2NV, CR3NV, and CR4NV as desired.  
2. Program the Secure Silicon Region (OTP area) as desired.  
3. Program the PPB bits as desired via the PPBP command.  
4. Program the Non-Volatile Data Learning Pattern (NVDLR) if it will be used in DDR read commands.  
5. Program the Password register (PASS) if password protection will be used.  
6. Program the ASP Register as desired, including the selection of the persistent or password ASP Mode in  
ASPR[2:1]. It is very important to explicitly select a protection mode so that later accidental or malicious  
programming of the ASP register and OTP configuration is prevented. This is to ensure that only the intended  
OTP protection and configuration features are enabled. While programming the ASPR register:  
7. The RPME bit (ASPR[5]) may be used to select Read Password Mode to use the password to control read access  
to most of the array.  
During system power up and boot code execution:  
1. Trusted boot code can determine whether there is any need to program additional SSR (OTP area) information.  
If no SSR changes are needed the FREEZE bit (CR1V[0]) can be set to 1 to protect the SSR from changes during  
the remainder of normal system operation while power remains on.  
2. If the Persistent Protection Mode is in use, trusted boot code can determine whether there is any need to  
modify the persistent (PPB) sector protection via the PPBP or PPBE commands. If no PPB changes are needed  
the PPBLOCK bit can be cleared to 0 via the PPBL to protect the PPB bits from changes during the remainder  
of normal system operation while power remains on.  
3. The dynamic (DYB) sector protection bits can be written as desired via the DYBAR.  
Datasheet  
82 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10  
Commands  
All communication between the host system and FS-S Family memory devices is in the form of units called  
commands.  
All commands begin with an instruction that selects the type of information transfer or device operation to be  
performed. Commands may also have an address, instruction modifier, latency period, data transfer to the  
memory, or data transfer from the memory. All instruction, address, and data information is transferred  
sequentially between the host system and memory device.  
Command protocols are also classified by a numerical nomenclature using three numbers to reference the  
transfer width of three command phases:  
• instruction;  
• address and instruction modifier (mode);  
• data.  
Single bit wide commands start with an instruction and may provide an address or data, all sent only on the SI  
signal. Data may be sent back to the host serially on the SO signal. This is referenced as a 1-1-1 command protocol  
for single bit width instruction, single bit width address and modifier, single bit data.  
Dual or Quad Input / Output (I/O) commands provide an address sent from the host as bit pairs on IO0 and IO1  
or, four bit (nibble) groups on IO0, IO1, IO2, and IO3. Data is returned to the host similarly as bit pairs on IO0 and  
IO1 or, four bit (nibble) groups on IO0, IO1, IO2, and IO3. This is referenced as 1-2-2 for Dual I/O and 1-4-4 for Quad  
I/O command protocols.  
The FS-S Family also supports a QPI Mode in which all information is transferred in 4-bit width, including the  
instruction, address, modifier, and data. This is referenced as a 4-4-4 command protocol.  
Commands are structured as follows:  
• Each command begins with an eight bit (byte) instruction. However, some read commands are modified by a  
prior read command, such that the instruction is implied from the earlier command. This is called Continuous  
Read Mode. For the S70FS01GS, do not enable the Continuous Read Mode, this will cause bus contention  
between the two 512Mb die.  
• The instruction may be stand alone or may be followed by address bits to select a location within one of several  
address spaces in the device. The address may be either a 24-bit or 32-bit, byte boundary, address.  
• The SPI with Multiple IO provides the option for each transfer of address and data information to be done one,  
two, or four bits in parallel. This enables a trade off between the number of signal connections (IO bus width)  
and the speed of information transfer. If the host system can support a two or four bit wide IO bus the memory  
performance can be increased by using the instructions that provide parallel two bit (dual) or parallel four bit  
(quad) transfers.  
• In legacy SPI Multiple IO Mode, the width of all transfers following the instruction are determined by the  
instruction sent. Following transfers may continue to be single bit serial on only the SI or Serial Output (SO)  
signals, they may be done in two bit groups per (dual) transfer on the IO0 and IO1 signals, or they may be done  
in 4 bit groups per (quad) transfer on the IO0-IO3 signals. Within the dual or quad groups the least significant  
bit is on IO0. More significant bits are placed in significance order on each higher numbered IO signal. Single  
bits or parallel bit groups are transferred in most to least significant bit order.  
• In QPI Mode, the width of all transfers, including instructions, is a 4-bit wide (quad) transfer on the IO0–IO3  
signals.  
• Dual I/O and Quad I/O read instructions send an instruction modifier called mode bits, following the address,  
to indicate that the next command will be of the same type with an implied, rather than an explicit, instruction.  
The next command thus does not provide an instruction byte, only a new address and mode bits. This reduces  
the time needed to send each command when the same command type is repeated in a sequence of commands.  
• The address or mode bits may be followed by write data to be stored in the memory device or by a read latency  
period before read data is returned to the host.  
Datasheet  
83 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
• Read latency may be zero to several SCK cycles (also referred to as dummy cycles).  
• All instruction, address, mode, and data information is transferred in byte granularity. Addresses are shifted  
into the device with the most significant byte first. All data is transferred with the lowest address byte sent first.  
Following bytes of data are sent in lowest to highest byte address order i.e. the byte address increments.  
• All attempts to read the flash memory array during a program, erase, or a write cycle (embedded operations)  
are ignored. The embedded operation will continue to execute without any affect. A very limited set of  
commands are accepted during an embedded operation. These are discussed in the individual command  
descriptions. While a program, erase, or write operation is in progress, it is recommended to check that the  
Write-In Progress (WIP) bit is 0 before issuing most commands to the device, to ensure the new command can  
be accepted.  
• Depending on the command, the time for execution varies. A command to read status information from an  
executing command is available to determine when the command completes execution and whether the  
command was successful.  
• Although host software in some cases is used to directly control the SPI interface signals, the hardware interfaces  
of the host system and the memory device generally handle the details of signal relationships and timing. For  
this reason, signal relationships and timing are not covered in detail within this software interface focused  
section of the document. Instead, the focus is on the logical sequence of bits transferred in each command  
rather than the signal timing and relationships. Following are some general signal relationship descriptions to  
keep in mind. For additional information on the bit level format and signal timing relationships of commands,  
see “Command Protocol” on page 18.  
- The host always controls the Chip Select (CS#), Serial Clock (SCK), and Serial Input (SI) - SI for single bit wide  
transfers. The memory drives Serial Output (SO) for single bit read transfers. The host and memory alternately  
drive the IO0-IO3 signals during Dual and Quad transfers.  
- All commands begin with the host selecting the memory by driving CS# LOW before the first rising edge of  
SCK. CS# is kept LOW throughout a command and when CS# is returned HIGH the command ends. Generally,  
CS# remains LOW for eight bit transfer multiples to transfer byte granularity information. Some commands  
will not be accepted if CS# is returned HIGH not at an 8 bit boundary.  
Datasheet  
84 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.1  
Command set summary  
Extended addressing  
10.1.1  
To accommodate addressing above 128 Mb, there are two options:  
1. Instructions that always require a 4-Byte address, used to access up to 32 Gb of memory:  
Table 44  
Instructions details  
Command name  
Function  
Read  
Read Fast  
Instruction (Hex)  
4READ  
4FAST_READ  
4DIOR  
4QIOR  
4DDRQIOR  
4PP  
13  
0C  
BC  
EC  
EE  
12  
21  
DC  
18  
E0  
E1  
E2  
E3  
Dual I/O Read  
Quad I/O Read  
DDR Quad I/O Read  
Page Program  
Parameter 4 KB Erase  
Erase 256 KB  
ECC Status Read  
DYB Read  
4P4E  
4SE  
4ECCRD  
4DYBRD  
4DYBWR  
4PPBRD  
4PPBP  
DYBWR  
PPB Read  
PPB Program  
Datasheet  
85 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
2. A 4 Byte address mode for backward compatibility to the 3 Byte address instructions. The standard 3 Byte  
instructions can be used in conjunction with a 4 Byte address mode controlled by the Address Length  
configuration bit (CR2V[7]). The default value of CR2V[7] is loaded from CR2NV[7] (following power up,  
hardware reset, or software reset), to enable default 3-Byte (24-bit) or 4 Byte (32 bit) addressing. When the  
address length (CR2V[7]) set to 1, the legacy commands are changed to require 4-Bytes (32-bits) for the address  
field. The following instructions can be used in conjunction with the 4 Byte address mode configuration to  
switch from 3-Bytes to 4-Bytes of address field.  
Table 45  
Instructions details  
Command name  
Function  
Read  
Read Fast  
Instruction (Hex)  
READ  
FAST_READ  
DIOR  
QIOR  
DDRQIOR  
PP  
03  
0B  
BB  
EB  
ED  
02  
20  
D8  
65  
71  
D0  
42  
4B  
19  
FA  
FB  
FC  
FD  
Dual I/O Read  
Quad I/O Read  
DDR Quad I/O Read)  
Page Program  
Parameter 4 KB Erase  
Erase 256 KB  
Read Any Register  
Write Any Register  
Evaluate Erase Status  
OTP Program  
OTP Read  
P4E  
SE  
RDAR  
WRAR  
EES  
OTPP  
OTPR  
ECCRD  
DYBRD  
DYBWR  
PPBRD  
PPBP  
ECC Status Read  
DYB Read  
DYBWR  
PPB Read  
PPB Program  
Datasheet  
86 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.1.2  
FS01GS DDP  
The FS01GS contains two FS512S devices stacked in a Dual Die Package (DDP). Both devices are selected to  
decode each command instruction and address when the CS# signal, shared by both devices, goes LOW. One  
FS512S device is modified to respond to commands that have an address selecting the lower 512 Mb of the total  
1 Gb (128 MB) address space. The other FS512S device is modified to respond to commands with addresses  
selecting the upper 512 Mb of the address space. Some commands, without an address, are executed only by the  
lower address FS512S; some are executed by both devices in parallel.  
Both the lower and upper address FS512S devices must be configured, by writing to the various status and  
configuration registers in each device, to define the overall sector map and behavior of both devices for the entire  
1 Gb space selected by the single CS# for the DDP. However, several of the legacy SPI commands for register  
reading, writing or other operations do not have an explicit address in the command. For this reason, several of  
the legacy SPI commands are not supported by the FS01GS and alternate commands that include an address  
must be used to route the command to the lower or upper FS512S.  
The following commands are not supported in the FS01GS:  
• WRR (01h)  
• RDCR (35h)  
• RDSR1 (05h)  
• RDSR2 (07h)  
• PNVDLR (43h)  
• ASPP (2Fh)  
• PASSP (E8h)  
• PPBE (E4h)  
• EPS (B0h)  
• EPR (30h)  
The RDAR (65h) and WRAR (71h) commands must be used for reading and writing the registers so that the  
command address directs the operation to the lower or upper FS512S device in the DDP. New commands with a  
4 byte address are added for Bulk Erase Addressed (BEA, FEh) and PPB Erase Addressed (PPBEA, EAh) to direct  
the operation to the lower or upper FS512S device.  
A complete discussion of FS01GS behavior and software modifications is provided in “FS01GS Behavior and  
Software Modifications” on page 163.  
Datasheet  
87 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.1.3  
Command summary by function  
Table 46  
FS-S family command set (Sorted by function)  
Maximum Address  
Command  
Instruction  
value (Hex)  
Function  
Command description  
name  
frequency  
(MHz)  
length  
(Bytes)  
QPI  
Read ID (JEDEC Manufacturer ID  
RDID  
9F  
5A  
133  
50  
0
3
Yes  
Yes  
and JEDEC CFI)  
Read  
Device ID  
Read JEDEC Serial Flash  
Discoverable Parameters  
RSFDP  
RDQID  
RDAR  
WRDI  
WREN  
WRAR  
Read Quad ID  
Read Any Register  
Write Disable  
Write Enable  
Write Any Register  
AF  
65  
04  
06  
71  
133  
133  
133  
133  
133  
0
3 or 4  
0
Yes  
Yes  
Yes  
Yes  
Yes  
0
3 or 4  
Clear Status Register-1 -  
Erase/Program Fail Reset  
This command may be disabled and  
the instruction value instead used  
for a program / erase resume  
command - see “Configuration  
Register 3” on page 65  
Clear Status Register-1 (Alternate  
instruction) - Erase/Program Fail  
Reset  
CLSR  
CLSR  
30  
133  
0
0
Yes  
Register  
Access  
82  
133  
Yes  
4BAM  
SBL  
EES  
ECCRD  
4ECCRD  
DLPRD  
Enter 4 Byte Address Mode  
Set Burst Length  
Evaluate Erase Status  
ECC Read  
ECC Read  
Data Learning Pattern Read  
B7  
C0  
D0  
19  
18  
41  
133  
133  
133  
133  
133  
133  
0
0
No  
No  
Yes  
Yes  
Yes  
No  
3 or 4  
3 or 4  
4
0
Write Volatile Data Learning  
Register  
WVDLR  
4A  
133  
0
No  
Notes  
41.Commands not supported in QPI Mode have undefined behavior if sent when the device is in QPI Mode.  
42.The FS01GS does not support some commands and adds some commands. For additional information see  
“FS01GS Behavior and Software Modifications” on page 163.  
Datasheet  
88 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
Table 46  
Function  
FS-S family command set (Sorted by function) (Continued)  
Maximum Address  
Command  
name  
Instruction  
value (Hex)  
Command description  
frequency  
(MHz)  
length  
(Bytes)  
QPI  
READ  
4READ  
FAST_READ Fast Read  
4FAST_READ Fast Read  
Read  
Read  
03  
13  
0B  
0C  
BB  
BC  
EB  
EC  
ED  
EE  
02  
12  
20  
21  
D8  
DC  
60  
C7  
FE  
75  
85  
7A  
8A  
42  
50  
50  
3 or 4  
4
3 or 4  
4
3 or 4  
4
3 or 4  
4
3 or 4  
4
3 or 4  
4
3 or 4  
4
3 or 4  
4
0
0
4
0
0
0
0
No  
No  
No  
No  
No  
No  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
Yes  
No  
133  
133  
133  
133  
133  
133  
80  
DIOR  
4DIOR  
QIOR  
Dual I/O Read  
Read Flash  
Array  
Dual I/O Read  
Quad I/O Read  
Quad I/O Read  
4QIOR  
DDRQIOR DDR Quad I/O Read  
4DDRQIOR DDR Quad I/O Read  
80  
PP  
4PP  
P4E  
4P4E  
SE  
4SE  
BE  
BE  
BEA  
EPS  
EPS  
EPR  
EPR  
OTPP  
Page Program  
Page Program  
Parameter 4 KB-sector Erase  
Parameter 4 KB-sector Erase  
Erase 256 KB  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
Program  
Flash Array  
Erase Flash  
Array  
Erase 256 KB  
Bulk Erase  
Bulk Erase (alternate instruction)  
Bulk Erase Addressed  
Erase Suspend  
Program Suspend  
Erase Resume  
Erase  
/Program  
Suspend  
/Resume  
Program Resume  
OTP Program  
One Time  
Program  
Array  
3 or 4  
OTPR  
OTP Read  
4B  
133  
3 or 4  
No  
Notes  
41.Commands not supported in QPI Mode have undefined behavior if sent when the device is in QPI Mode.  
42.The FS01GS does not support some commands and adds some commands. For additional information see  
“FS01GS Behavior and Software Modifications” on page 163.  
Datasheet  
89 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
Table 46  
Function  
FS-S family command set (Sorted by function) (Continued)  
Maximum Address  
Command  
name  
Instruction  
value (Hex)  
Command description  
DYB Read  
DYB Read  
DYB Write  
frequency  
(MHz)  
length  
(Bytes)  
QPI  
DYBRD  
4DYBRD  
DYBWR  
FA  
E0  
FB  
E1  
FC  
E2  
FD  
E3  
EA  
2B  
A7  
A6  
E7  
E9  
66  
99  
F0  
FF  
B9  
AB  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
133  
3 or 4  
4
3 or 4  
4
3 or 4  
4
3 or 4  
4
4
0
0
0
0
0
0
0
0
0
0
0
Yes  
Yes  
Yes  
Yes  
No  
No  
No  
No  
No  
No  
No  
No  
No  
No  
Yes  
Yes  
No  
Yes  
Yes  
Yes  
4DYBWR DYB Write  
PPBRD  
4PPBRD  
PPBP  
PPB Read  
PPB Read  
PPB Program  
Advanced  
Sector  
Protection  
4PPBP  
PPBEA  
ASPRD  
PLBRD  
PLBWR  
PASSRD  
PASSU  
RSTEN  
RST  
PPB Program  
PBB Erase Addressed  
ASP Read  
PPB Lock Bit Read  
PPB Lock Bit Write  
Password Read  
Password Unlock  
Software Reset Enable  
Software Reset  
Legacy Software Reset  
Mode Bit Reset  
Enter DPD Mode  
Release from DPD Mode  
Reset  
RESET  
MBR  
DPD  
DPD  
RES  
Notes  
41.Commands not supported in QPI Mode have undefined behavior if sent when the device is in QPI Mode.  
42.The FS01GS does not support some commands and adds some commands. For additional information see  
“FS01GS Behavior and Software Modifications” on page 163.  
Datasheet  
90 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.1.4  
Read Device Identification  
There are multiple commands to read information about the device manufacturer, device type, and device  
features. SPI memories from different vendors have used different commands and formats for reading  
information about the memories. The FS-S Family supports the three device information commands.  
10.1.5  
Register Read or Write  
There are multiple registers for reporting embedded operation status or controlling device configuration  
options. There are commands for reading or writing these registers. Registers contain both volatile and  
non-volatile bits. Non-volatile bits in registers are automatically erased and programmed as a single (write)  
operation.  
10.1.5.1  
Monitoring operation status  
The host system can determine when a write, program, erase, suspend or other embedded operation is complete  
by monitoring the Write in Progress (WIP) bit in the Status Register. The Read from Status Register-1 command  
or Read Any Register command provides the state of the WIP bit. The program error (P_ERR) and erase error  
(E_ERR) bits in the status register indicate whether the most recent program or erase command has not  
completed successfully. When P_ERR or E_ERR bits are set to one, the WIP bit will remain set to one indicating  
the device remains busy and unable to receive most new operation commands. Only Read Any Register (RDAR  
65h), status clear (CLSR 30h or 82h), and software reset (RSTEN 66h, RST 99h or RESET F0h) are valid commands  
when P_ERR or E_ERR is set to 1. A Clear Status Register (CLSR) followed by a Write Disable (WRDI) command  
must be sent to return the device to standby state. Clear Status Register clears the WIP, P_ERR, and E_ERR bits.  
WRDI clears the WEL bit. Alternatively, Hardware Reset, or Software Reset (RST or RESET) may be used to return  
the device to standby state.  
10.1.5.2  
Configuration  
There are commands to read, write, and protect registers that control interface path width, interface timing,  
interface address length, and some aspects of data protection.  
10.1.6  
Read flash array  
Data may be read from the memory starting at any byte boundary. Data bytes are sequentially read from  
incrementally higher byte addresses until the host ends the data transfer by driving CS# input HIGH. If the byte  
address reaches the maximum address of the memory array, the read will continue at address zero of the array.  
Because the FS01GS is constructed from two FS512S devices stacked in a DDP, a sequential read access that  
reaches the maximum address of a FS512S device, will continue at address zero of the same FS512S device. A  
sequential read at address 03FFFFFFh of an FS01GS will be followed by a read at 00000000h. A sequential read at  
address 07FFFFFFh of an FS01GS will be followed by a read at 04000000h.  
There are several different read commands to specify different access latency and data path widths. DDR  
commands also define the address & data bit relationship to both SCK edges:  
• The Read command provides a single address bit per SCK rising edge on the SI signal with read data returning  
a single bit per SCK falling edge on the SO signal. This command has zero latency between the address and the  
returning data but is limited to a maximum SCK rate of 50 MHz.  
• Other read commands have a latency period between the address and returning data but can operate at higher  
SCK frequencies. The latency depends on a configuration register read latency value.  
• The Fast Read command provides a single address bit per SCK rising edge on the SI signal with read data  
returning a single bit per SCK falling edge on the SO signal.  
• Dual or Quad I/O Read commands provide address two bits or four bits per SCK rising edge with read data  
returning two bits, or four bits of data per SCK falling edge on the IO0–IO3 signals.  
• Quad DDR read commands provide address four bits per every SCK edge with read data returning four bits of  
data per every SCK edge on the IO0–IO3 signals.  
Datasheet  
91 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.1.7  
Program flash array  
Programming data requires two commands: Write Enable (WREN), and Page Program (PP). The Page Program  
command accepts from 1 byte up to 256 or 512 consecutive bytes of data (page) to be programmed in one  
operation. Programming means that bits can either be left at 1, or programmed from 1 to 0. Changing bits from  
0 to 1 requires an erase operation.  
10.1.8  
Erase flash array  
The Parameter Sector Erase, Sector Erase, or Bulk Erase commands set all the bits in a sector or the entire  
memory array to 1. A bit needs to be first erased to 1 before programming can change it to a 0. While bits can be  
individually programmed from a 1 to 0, erasing bits from 0 to 1 must be done on a sector-wide or array-wide (bulk)  
level. The Write Enable (WREN) command must precede an erase command.  
10.1.9  
OTP, block protection, and advanced sector protection  
There are commands to read and program a separate OTP array for permanent data such as a serial number.  
There are commands to control a contiguous group (block) of Flash memory array sectors that are protected from  
program and erase operations.There are commands to control which individual Flash memory array sectors are  
protected from program and erase operations. There is a mode to limit read access of the Flash array until a  
password is supplied.  
10.1.10  
Reset  
There are commands to reset to the default conditions present after power on to the device. However, the  
software reset commands do not affect the current state of the FREEZE or PPB Lock bits. In all other respects a  
software reset is the same as a hardware reset.  
10.1.11  
DPD  
The DPD Mode is supported by the FS-S Family devices. If the device has been placed in DPD Mode by the DPD  
(B9h) command, the interface standby current is (IDPD). The DPD command is accepted only while the device is  
not performing an embedded algorithm as indicated by the Status Register-1 volatile Write In Progress (WIP) bit  
being cleared to zero (SR1V[0] = 0). While in DPD Mode the device ignores all commands except the Release from  
DPD (RES ABh) command, that will return the device to the Interface Standby state after a delay of tRES  
.
10.1.12  
Reserved  
Some instructions are reserved for future use. In this generation of the FS-S Family some of these command  
instructions may be unused and not affect device operation, some may have undefined results.  
Some commands are reserved to ensure that a legacy or alternate source device command is allowed without  
effect. This allows legacy software to issue some commands that are not relevant for the current generation FS-S  
Family with the assurance these commands do not cause some unexpected action.  
Some commands are reserved for use in special versions of the FS-S not addressed by this document or for a  
future generation. This allows new host memory controller designs to plan the flexibility to issue these command  
instructions. The command format is defined if known at the time this document revision is published.  
Datasheet  
92 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.2  
Identification commands  
Read Identification (RDID 9Fh)  
10.2.1  
The Read Identification (RDID) command provides read access to manufacturer identification, device identifi-  
cation, and Common Flash Interface (CFI) information. The manufacturer identification is assigned by JEDEC. The  
CFI structure is defined by JEDEC standard. The device identification and CFI values are assigned by Cypress.  
The JEDEC Common Flash Interface (CFI) specification defines a device information structure, which allows a  
vendor-specified software Flash management program (driver) to be used for entire families of Flash devices.  
Software support can then be device-independent, JEDEC manufacturer ID independent, forward and  
backward-compatible for the specified Flash device families. System vendors can standardize their Flash drivers  
for long-term software compatibility by using the CFI values to configure a family driver from the CFI information  
of the device in use.  
Any RDID command issued while a program, erase, or write cycle is in progress is ignored and has no effect on  
execution of the program, erase, or write cycle that is in progress.  
The RDID instruction is shifted on SI. After the last bit of the RDID instruction is shifted into the device, a byte of  
manufacturer identification, two bytes of device identification, extended device identification, and CFI  
information will be shifted sequentially out on SO. As a whole this information is referred to as ID-CFI. See “Device  
ID and Common Flash Interface (ID-CFI) Address Map” on page 141 for the detail description of the ID-CFI  
contents.  
Continued shifting of output beyond the end of the defined ID-CFI address space will provide undefined data. The  
RDID command sequence is terminated by driving CS# to the logic HIGH state anytime during data output.  
The maximum clock frequency for the RDID command is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Data 1  
Data N  
Figure 41  
Read Identification (RDID) command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3 and the  
returning data is shifted out on IO0–IO3.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
D1  
D2  
D3  
D4  
D5  
Figure 42  
Read Identification (RDID) QPI mode command  
Datasheet  
93 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.2.2  
Read Quad Identification (RDQID AFh)  
The Read Quad Identification (RDQID) command provides read access to manufacturer identification, device  
identification, and Common Flash Interface (CFI) information. This command is an alternate way of reading the  
same information provided by the RDID command while in QPI Mode. In all other respects the command behaves  
the same as the RDID command.  
The command is recognized only when the device is in QPI Mode (CR2V[6] = 1). The instruction is shifted in on  
IO0-IO3. After the last bit of the instruction is shifted into the device, a byte of manufacturer identification, two  
bytes of device identification, extended device identification, and CFI information will be shifted sequentially out  
on IO0-IO3. As a whole this information is referred to as ID-CFI. See “Device ID and Common Flash Interface  
(ID-CFI) Address Map” on page 141 for the detail description of the ID-CFI contents.  
Continued shifting of output beyond the end of the defined ID-CFI address space will provide undefined data. The  
command sequence is terminated by driving CS# to the logic HIGH state anytime during data output.  
The maximum clock frequency for the command is 133 MHz.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
D1  
D2  
D3  
D4  
D5  
Figure 43  
Read Quad Identification (RDQID) command sequence  
10.2.3  
Read Serial Flash Discoverable Parameters (RSFDP 5Ah)  
The command is initiated by shifting on SI the instruction code “5Ah, followed by a 24-bit address of 000000h,  
followed by 8 dummy cycles. The SFDP bytes are then shifted out on SO starting at the falling edge of SCK after  
the dummy cycles. The SFDP bytes are always shifted out with the MSB first. If the 24-bit address is set to any  
other value, the selected location in the SFDP space is the starting point of the data read. This enables random  
access to any parameter in the SFDP space. The RSFDP command is supported up to 50 MHz.  
RSFDP is not supported in Read Password Mode before the password is provided.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
23  
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Dummy Cycles  
Data 1  
Figure 44  
RSFDP command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3 and the  
returning data is shifted out on IO0–IO3.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
20  
21  
22  
23  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruct.  
Address  
Dummy  
D1  
D2  
D3  
D4  
Figure 45  
RSFDP QPI mode command sequence  
Datasheet  
94 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3  
Register Access commands  
The following register access commands are not supported in the FS01GS: WRR (01h), RDCR (35h), RDSR1 (05h),  
RDSR2 (07h), PNVDLR (43h). The RDAR (65h) and WRAR (71h) commands must be used for reading and writing the  
registers so that the command address directs the operation to the lower or upper FS512S device in the DDP.  
10.3.1  
Write Enable (WREN 06h)  
The Write Enable (WREN) command sets the Write Enable Latch (WEL) bit of the Status Register 1 (SR1V[1]) to a  
“1. The Write Enable Latch (WEL) bit must be set to a “1” by issuing the Write Enable (WREN) command to enable  
write, program and erase commands.  
CS# must be driven into the logic HIGH state after the eighth bit of the instruction byte has been latched in on SI.  
Without CS# being driven to the logic HIGH state after the eighth bit of the instruction byte has been latched in  
on SI, the write enable operation will not be executed.  
Because the FS01GS is constructed from two FS512S devices stacked in a DDP, the WREN command sets the WEL  
bit to 1 in both FS512S devices. Only the FS512S device that later executes a write, program, or erase command  
will return the WEL bit in that device back to 0 at the end of the command execution. A Write Disable (WRDI)  
command must be issued to return the WEL bit to 0 in both devices. The WRDI command can be issued after each  
write, program, or erase command completes or once after a sequence of such commands is completed. A WREN  
command is still required before each write, program, or erase command to ensure the WEL bit is 1 before the  
command is executed.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 46  
Write Enable (WREN) command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 47  
Write Enable (WREN) command sequence QPI mode  
Datasheet  
95 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3.2  
Write Disable (WRDI 04h):  
The Write Disable (WRDI) command clears the Write Enable Latch (WEL) bit of the Status Register-1 (SR1V[1]) to  
a “0.  
The Write Enable Latch (WEL) bit may be cleared to a “0” by issuing the Write Disable (WRDI) command to disable  
Page Program (PP), Sector Erase (SE), Bulk Erase (BE), Write Registers (WRAR), OTP Program (OTPP), and other  
commands, that require WEL be set to “1” for execution. The WRDI command can be used by the user to protect  
memory areas against inadvertent writes that can possibly corrupt the contents of the memory. The WRDI  
command is ignored during an embedded operation while WIP bit = 1.  
CS# must be driven into the logic HIGH state after the eighth bit of the instruction byte has been latched in on SI.  
Without CS# being driven to the logic HIGH state after the eighth bit of the instruction byte has been latched in  
on SI, the write disable operation will not be executed.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 48  
Write Disable (WRDI) command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 49  
Write Disable (WRDI) command sequence QPI mode  
Datasheet  
96 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3.3  
Clear Status Register (CLSR 30h or 82h):  
The Clear Status Register command resets bit SR1V[5] (Erase Fail Flag) and bit SR1V[6] (Program Fail Flag). It is  
not necessary to set the WEL bit before a Clear Status Register command is executed. The Clear Status Register  
command will be accepted even when the device remains busy with WIP set to 1, as the device does remain busy  
when either error bit is set. The WEL bit will be unchanged after this command is executed.  
The legacy Clear Status Register (CLSR 30h) instruction may be disabled and the 30h instruction value instead  
used for a program / erase resume command - see “Configuration Register 3” on page 65. The Clear Status  
Register alternate instruction (CLSR 82h) is always available to clear the status register.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 50  
Clear Status Register (CLSR) command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 51  
Clear Status Register (CLSR) command sequence QPI mode  
Datasheet  
97 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3.4  
ECC Status Register Read (ECCRD 19h or 4EECRD 18h)  
To read the ECC Status Register, the command is followed by the ECC unit address, the four least significant bits  
(LSB) of address must be set to zero. This is followed by the number of dummy cycles selected by the read latency  
value in CR2V[3:0]. Then the 8-bit contents of the ECC Register, for the ECC unit selected, are shifted out on SO 16  
times, once for each byte in the ECC Unit. If CS# remains LOW the next ECC unit status is sent through SO 16 times,  
once for each byte in the ECC Unit. The maximum operating clock frequency for the ECC READ command is  
133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Dummy Cycles  
Data 1  
Figure 52  
ECC Status Register Read command sequence[43, 44]  
This command is also supported in Quad All Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two  
clock cycles per byte. The ECC read command is not supported for 0 dummy latency in Quad All Mode.  
CS  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
20  
21  
22  
23  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruct.  
Address  
Dummy  
D1  
D2  
D3  
D4  
Figure 53  
ECCRD (19h), Quad All Mode, CR2[7] = 0, command sequence  
CS  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
28  
29  
30  
31  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
4
0
4
0
1
2
3
5
6
7
1
2
3
5
6
7
1
2
3
IO2  
IO3  
Phase  
Instruct.  
Address  
Dummy  
D1  
D2  
D3  
D4  
Figure 54  
ECCRD (19h), Quad All Mode, CR2[7] = 1, or 4ECCRD (18h) command sequence  
Notes  
43.A = MSB of address = 23 for Address length (CR2V[7] = 0, or 31 for CR2V[7]=1 with command 19h.  
44.A = MSB of address = 31 with command 18h.  
Datasheet  
98 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3.5  
Write VDLR (WVDLR 4Ah)  
Before the Write VDLR (WVDLR) command can be accepted by the device, a Write Enable (WREN) command must  
be issued and decoded by the device. After the Write Enable (WREN) command has been decoded successfully,  
the device will set the Write Enable Latch (WEL) to enable WVDLR operation.  
The WVDLR command is entered by shifting the instruction and the data byte on SI.  
CS# must be driven to the logic HIGH state after the eighth (8th) bit of data has been latched. If not, the WVDLR  
command is not executed. As soon as CS# is driven to the logic HIGH state, the WVDLR operation is initiated with  
no delays. The maximum clock frequency for the PNVDLR command is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Input Data  
Figure 55  
Write VDLR (WVDLR) command sequence  
10.3.6  
Data Learning Pattern Read (DLPRD 41h)  
The instruction is shifted on SI, then the 8-bit DLP is shifted out on SO. It is possible to read the DLP continuously  
by providing multiples of eight clock cycles. The maximum operating clock frequency for the DLPRD command  
is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Register Read  
Repeat Register Read  
Figure 56  
DLP Read (DLPRD) command sequence  
10.3.7  
Enter 4 Byte Address Mode (4BAM B7h)  
The enter 4 Byte Address Mode (4BAM) command sets the volatile Address Length bit (CR2V[7]) to 1 to change  
most 3 Byte address commands to require 4 Bytes of address. The Read SFDP (RSFDP) command is the only  
3 Byte command that is not affected by the Address Length bit. RSFDP is required by the JEDEC JESD216 standard  
to always have only 3 Bytes of address.  
A hardware or software reset is required to exit the 4 Byte address mode.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 57  
Enter 4 Byte Address Mode (4BAM B7h) command sequence  
Datasheet  
99 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3.8  
Read Any Register (RDAR 65h)  
The Read Any Register (RDAR) command provides a way to read all device registers - non-volatile and volatile.  
The instruction is followed by a 3 or 4 Byte address (depending on the address length configuration CR2V[7],  
followed by a number of latency (dummy) cycles set by CR2V[3:0]. Then the selected register contents are  
returned. If the read access is continued the same addressed register contents are returned until the command  
is terminated - only one register is read by each RDAR command.  
The FS01GS requires that 4 Byte address mode is in use for this command so that the 4 Byte address will select  
the internal upper or lower FS512S device to read. The 4BAM (B7h) command is used to enter 4 Byte address  
mode before using the RDAR command. Address A26 = 0 selects the lower address FS512S and A26 = 1 selects the  
higher address FS512S.  
Reading undefined locations provides undefined data.  
The RDAR command may be used during embedded operations to read status register-1 (SR1V).  
The RDAR command is not used for reading registers that act as a window into a larger array: ECCSR, PPBAR, and  
DYBAR. There are separate commands required to select and read the location in the array accessed.  
The RDAR command will read invalid data from the PASS register locations if the ASP Password Protection Mode  
is selected by programming ASPR[2] to 0.  
Datasheet  
100 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
Table 47  
Register address map  
Byte address  
Register name  
Description  
(Hex)  
00000000  
00000001  
00000002  
00000003  
00000004  
00000005  
...  
SR1NV  
N/A  
CR1NV  
CR2NV  
CR3NV  
CR4NV  
N/A  
Non-volatile Status and Configuration Registers  
00000010  
...  
NVDLR  
N/A  
Non-volatile Data Learning Register  
Non-volatile Password Register  
Non-volatile  
00000020  
00000021  
00000022  
00000023  
00000024  
00000025  
00000026  
00000027  
...  
PASS[7:0]  
PASS[15:8]  
PASS[23:16]  
PASS[31:24]  
PASS[39:32]  
PASS[47:40]  
PASS[55:48]  
PASS[63:56]  
N/A  
00000030  
00000031  
...  
ASPR[7:0]  
ASPR[15:8]  
N/A  
00800000  
00800001  
00800002  
00800003  
00800004  
00800005  
...  
SR1V  
SR2V  
CR1V  
CR2V  
CR3V  
CR4V  
N/A  
Volatile Status and Configuration Registers  
00800010  
...  
00800040  
...  
VDLR  
N/A  
PPBL  
N/A  
Volatile Data Learning Register  
Volatile PPB Lock Register  
Datasheet  
101 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Dummy Cycles  
Data 1  
Figure 58  
Read Any Register Read command sequence[45]  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
20  
21  
22  
23  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruct.  
Address  
Dummy  
D1  
D2  
D3  
D4  
Figure 59  
Read Any Register, QPI Mode, CR2[7] = 0, command sequence  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
28  
29  
30  
31  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruct.  
Address  
Dummy  
D1  
D2  
D3  
D4  
Figure 60  
Read Any Register, QPI Mode, CR2[7] = 1 command sequence  
Note  
45.A = MSB of address = 23 for Address length CR2V[7] = 0, or 31 for CR2V[7] = 1.  
Datasheet  
102 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3.9  
Write Any Register (WRAR 71h)  
The Write Any Register (WRAR) command provides a way to write any device register - non-volatile or volatile. The  
instruction is followed by a 3 or 4 Byte address (depending on the address length configuration CR2V[7], followed  
by one byte of data to write in the address selected register.  
The FS01GS requires that 4 Byte address mode is in use for this command so that the 4 Byte address will select  
the internal upper or lower FS512S device to write. The 4BAM (B7h) command may be used to enter 4 Byte  
address mode before using the WRAR command. Address A26 = 0 selects the lower address FS512S and A26 = 1  
selects the higher address FS512S.  
Before the WRAR command can be accepted by the device, a Write Enable (WREN) command must be issued and  
decoded by the device, which sets the Write Enable Latch (WEL) in the Status Register to enable any write  
operations. The WIP bit in SR1V may be checked to determine when the operation is completed. The P_ERR and  
E_ERR bits in SR1V may be checked to determine if any error occurred during the operation.  
Some registers have a mixture of bit types and individual rules controlling which bits may be modified. Some bits  
are read only, some are OTP.  
Read only bits are never modified and the related bits in the WRAR command data byte are ignored without  
setting a program or erase error indication (P_ERR or E_ERR in SR1V). Hence, the value of these bits in the WRAR  
data byte do not matter.  
OTP bits may only be programmed to the level opposite of their default state. Writing of OTP bits back to their  
default state is ignored and no error is set.  
Non-volatile bits which are changed by the WRAR data, require non-volatile register write time (tW) to be updated.  
The update process involves an erase and a program operation on the non-volatile register bits. If either the erase  
or program portion of the update fails the related error bit and WIP in SR1V will be set to 1.  
Volatile bits which are changed by the WRAR data, require the volatile register write time (tCS) to be updated.  
Status Register-1 may be repeatedly read (polled) to monitor the Write-In-Progress (WIP) bit (SR1V[0]) and the  
error bits (SR1V[6,5]) to determine when the register write is completed or failed. If there is a write failure, the  
clear status command is used to clear the error status and enable the device to return to standby state.  
However, the PPBL register can not be written by the WRAR command. Only the PPB Lock Bit Write (PLBWR)  
command can write the PPBL register.  
The command sequence and behavior is the same as the PP or 4PP command with only a single byte of data  
provided. See “Page Program (PP 02h or 4PP 12h)” on page 113.  
The address map of the registers is the same as shown for “Read Any Register (RDAR 65h)” on page 100.  
Datasheet  
103 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.3.10  
Set Burst Length (SBL C0h)  
The Set Burst Length (SBL) command is used to configure the Burst Wrap feature. Burst Wrap is used in  
conjunction with Quad I/O Read and DDR Quad I/O Read, in legacy SPI or QPI Mode, to access a fixed length and  
alignment of data. Certain applications can benefit from this feature by improving the overall system code  
execution performance. The Burst Wrap feature allows applications that use cache, to start filling a cache line  
with instruction or data from a critical address first, then fill the remainder of the cache line afterwards within a  
fixed length (8/16/32/64-bytes) of data, without issuing multiple read commands.  
The Set Burst Length (SBL) command writes the CR4V register bits 4, 1, and 0 to enable or disable the wrapped  
read feature and set the wrap boundary. Other bits of the CR4V register are not affected by the SBL command.  
When enabled the wrapped read feature changes the related read commands from sequentially reading until the  
command ends, to reading sequentially wrapped within a group of bytes.  
When CR4V[4]=1, the Wrap Mode is not enabled and unlimited length sequential read is performed.  
When CR4V[4]=0, the Wrap Mode is enabled and a fixed length and aligned group of 8, 16, 32, or 64 bytes is read  
starting at the byte address provided by the read command and wrapping around at the group alignment  
boundary.  
The group of bytes is of length and aligned on an 8, 16, 32, or 64 byte boundary. CR4V[1:0] selects the boundary.  
See “Configuration Register 4 Volatile (CR4V)” on page 68.  
The starting address of the read command selects the group of bytes and the first data returned is the addressed  
byte. Bytes are then read sequentially until the end of the group boundary is reached. If the read continues the  
address wraps to the beginning of the group and continues to read sequentially. This wrapped read sequence  
continues until the command is ended by CS# returning HIGH.  
Table 48  
Example burst wrap sequences  
SBL data  
value  
Wrap  
boundary  
(Bytes)  
Start  
address  
(Hex)  
Address sequence (Hex)  
(Hex)  
03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E, 0F, 10, 11, 12, 13, 14, 15, 16,  
17, 18, ...  
1X  
Sequential  
XXXXXX03  
00  
00  
01  
8
8
16  
XXXXXX00 00, 01, 02, 03, 04, 05, 06, 07, 00, 01, 02, ...  
XXXXXX07 07, 00, 01, 02, 03, 04, 05, 06, 07, 00, 01, ...  
XXXXXX02 02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E, 0F, 00, 01, 02, 03, ...  
0C, 0D, 0E, 0F, 00, 01, 02, 03, 02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D,  
01  
02  
02  
16  
32  
32  
XXXXXX0C  
0E, ...  
0A, 0B, 0C, 0D, 0E, 0F, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 1A, 1B, 1C, 1D,  
XXXXXX0A  
1E, 1F, 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E, 0F, ...  
1E, 1F, 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E, 0F, 10, 11,  
12, 13, 14, 15, 16, 17, 18, 19, 1A, 1B, 1C, 1D, 1E, 1F, 00, ...  
XXXXXX1E  
03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E, 0F, 10, 11, 12, 13, 14, 15, 16,  
17, 18, 19, 1A, 1B, 1C, 1D, 1E, 1F, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 2A,  
03  
03  
64  
64  
XXXXXX03  
2B, 2C, 2D, 2E, 2F, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 3A, 3B, 3C, 3D,  
3E, 3F 00, 01, 02, ...  
2E, 2F, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 3A, 3B, 3C, 3D, 3E, 3F, 00, 01,  
02, 03, 04, 05, 06, 07, 08, 09, 0A, 0B, 0C, 0D, 0E, 0F, 10, 11, 12, 13, 14, 15,  
XXXXXX2E  
16, 17, 18, 19, 1A, 1B, 1C, 1D, 1E, 1F, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29,  
2A, 2B, 2C, 2D, , ...  
The power-on reset, hardware reset, or software reset default burst length can be changed by programming  
CR4NV with the desired value using the WRAR command.  
Datasheet  
104 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
CS#  
SCLK  
SI  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
SO  
Phase  
Instruction  
Input Data  
Figure 61  
Set Burst Length command sequence  
10.4  
Read Memory Array commands  
Read commands for the main Flash array provide many options for prior generation SPI compatibility or  
enhanced performance SPI:  
• Some commands transfer address or data on each rising edge of SCK. These are called SDR commands.  
• Some SDR commands transfer address one bit per rising edge of SCK and return data 1bit of data per rising edge  
of SCK. These are called Single width commands.  
• Some SDR commands transfer both address and data 2 or 4 bits per rising edge of SCK. These are called Dual  
I/O for 2 bit, Quad I/O, and QPI for 4 bit. QPI also transfers instructions 4 bits per rising edge.  
• Some commands transfer address and data on both the rising edge and falling edge of SCK. These are called  
DDR commands.  
• There are DDR commands for 4 bits of address or data per SCK edge. These are called Quad I/O DDR and QPI  
DDR for 4 bit per edge transfer.  
All of these commands, except QPI Read, begin with an instruction code that is transferred one bit per SCK rising  
edge. QPI Read transfers the instruction 4 bits per SCK rising edge.The instruction is followed by either a 3 or 4  
byte address transferred at SDR or DDR. Commands transferring address or data 2 or 4 bits per clock edge are  
called Multiple I/O (MIO) commands. For FS-S Family devices at 256Mb or higher density, the traditional SPI 3 byte  
addresses are unable to directly address all locations in the memory array. Separate 4 Byte address read  
commands are provided for access to the entire address space. These devices may be configured to take a 4 byte  
address from the host system with the traditional 3 byte address commands. The 4 byte address mode for  
traditional commands is activated by setting the Address Length bit in configuration register 2 to “0.  
The Quad I/O and QPI commands provide a performance improvement option controlled by mode bits that are  
sent following the address bits. The mode bits indicate whether the command following the end of the current  
read will be another read of the same type, without an instruction at the beginning of the read. These mode bits  
give the option to eliminate the instruction cycles when doing a series of Quad read accesses.  
Some commands require delay cycles following the address or mode bits to allow time to access the memory  
array - read latency. The delay or read latency cycles are traditionally called dummy cycles. The dummy cycles  
are ignored by the memory thus any data provided by the host during these cycles is “don’t care” and the host  
may also leave the SI signal at high impedance during the dummy cycles. When MIO commands are used the host  
must stop driving the IO signals (outputs are high impedance) before the end of last dummy cycle. When DDR  
commands are used the host must not drive the I/O signals during any dummy cycle. The number of dummy  
cycles varies with the SCK frequency or performance option selected via the Configuration Register 2 (CR2V[3:0])  
Latency Code. Dummy cycles are measured from SCK falling edge to next SCK falling edge. SPI outputs are  
traditionally driven to a new value on the falling edge of each SCK. Zero dummy cycles means the returning data  
is driven by the memory on the same falling edge of SCK that the host stops driving address or mode bits.  
The DDR commands may optionally have an 8 edge Data Learning Pattern (DLP) driven by the memory, on all  
data outputs, in the dummy cycles immediately before the start of data. The DLP can help the host memory  
controller determine the phase shift from SCK to data edges so that the memory controller can capture data at  
the center of the data eye.  
Datasheet  
105 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
When using SDR I/O commands at higher SCK frequencies (>50 MHz), an LC that provides 1 or more dummy cycles  
should be selected to allow additional time for the host to stop driving before the memory starts driving data, to  
minimize I/O driver conflict. When using DDR I/O commands with the DLP enabled, an LC that provides 5 or more  
dummy cycles should be selected to allow 1 cycle of additional time for the host to stop driving before the  
memory starts driving the 4 cycle DLP.  
Each read command ends when CS# is returned HIGH at any point during data return. CS# must not be returned  
HIGH during the mode or dummy cycles before data returns as this may cause mode bits to be captured  
incorrectly; making it indeterminate as to whether the device remains in Continuous Read Mode.  
10.4.1  
Read (Read 03h or 4READ 13h)  
The instruction  
• 03h (CR2V[7] = 0) is followed by a 3-byte address (A23–A0) or  
• 03h (CR2V[7] = 1) is followed by a 4-byte address (A31–A0) or  
• 13h is followed by a 4-byte address (A31–A0)  
Then the memory contents, at the address given, are shifted out on SO. The maximum operating clock frequency  
for the READ command is 50 MHz.  
The address can start at any byte location of the memory array. The address is automatically incremented to the  
next higher address in sequential order after each byte of data is shifted out. The entire memory can therefore  
be read out with one single read instruction and address 000000h provided. When the highest address is reached,  
the address counter will wrap around and roll back to 000000h, allowing the read sequence to be continued  
indefinitely.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Data 1  
Data N  
Figure 62  
Read command sequence (3-byte address, 03h or 13h)[46]  
Note  
46.A = MSB of address = 23 for CR2V[7] = 0, or 31 for CR2V[7]v = 1 or command 13h.  
Datasheet  
106 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.4.2  
Fast Read (FAST_READ 0Bh or 4FAST_READ 0Ch)  
The instruction  
• 0Bh (CR2V[7] = 0) is followed by a 3-byte address (A23–A0) or  
• 0Bh (CR2V[7] = 1) is followed by a 4-byte address (A31–A0) or  
• 0Ch is followed by a 4-byte address (A31–A0)  
The address is followed by dummy cycles depending on the latency code set in the Configuration Register  
CR2V[3:0]. The dummy cycles allow the device internal circuits additional time for accessing the initial address  
location. During the dummy cycles the data value on SO is “don’t care” and may be high impedance. Then the  
memory contents, at the address given, are shifted out on SO.  
The maximum operating clock frequency for FAST READ command is 133 MHz.  
The address can start at any byte location of the memory array. The address is automatically incremented to the  
next higher address in sequential order after each byte of data is shifted out. The entire memory can therefore  
be read out with one single read instruction and address 000000h provided. When the highest address is reached,  
the address counter will wrap around and roll back to 000000h, allowing the read sequence to be continued  
indefinitely.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Dummy Cycles  
Data 1  
Figure 63  
Fast Read (FAST_READ) command sequence (3-byte address, 0Bh [CR2V[7] = 0)[47]  
Note  
47.A = MSB of address = 23 for CR2V[7] = 0, or 31 for CR2V[7] = 1 or command 0Ch.  
Datasheet  
107 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.4.3  
Dual I/O Read (DIOR BBh or 4DIOR BCh)  
The instruction  
• BBh (CR2V[7] = 0) is followed by a 3-byte address (A23–A0) or  
• BBh (CR2V[7] = 1) is followed by a 4-byte address (A31–A0) or  
• BCh is followed by a 4-byte address (A31–A0)  
The Dual I/O Read commands improve throughput with two I/O signals — IO0 (SI) and IO1 (SO). This command  
takes input of the address and returns read data two bits per SCK rising edge. In some applications, the reduced  
address input and data output time might allow for code execution in place (XIP) i.e. directly from the memory  
device.  
The maximum operating clock frequency for Dual I/O Read is 133 MHz.  
The Dual I/O Read command has Continuous Read Mode bits that follow the address. For the S70FS01GS, do not  
enable the Continuous Read Mode, this will cause bus contention between the two 512 Mb die. The first Dual I/O  
Read command in a series starts with the 8 bit instruction, followed by address, followed by four cycles of mode  
bits not equal to Axh, followed by an optional latency period.  
Variable latency may be added after the mode bits are shifted into SI & SO before data begins shifting out of IO0  
& IO1. This latency period (dummy cycles) allows the device internal circuitry enough time to access data at the  
initial address. During the dummy cycles, the data value on SI & SO are “don’t care” and may be high impedance.  
The number of dummy cycles is determined by the frequency of SCK. The latency is configured in CR2V[3:0].  
Note that the four mode bit cycles are part of the device’s internal circuitry latency time to access the initial  
address after the last address cycle that is clocked into IO0 (SI) & IO1 (SO).  
It is important that the I/O signals be set to high-impedance at or before the falling edge of the first data out clock.  
At higher clock speeds the time available to turn off the host outputs before the memory device begins to drive  
(bus turn around) is diminished. It is allowed and may be helpful in preventing I/O signal contention, for the host  
system to turn off the I/O signal outputs (make them high impedance) during the last two “don’t care” mode  
cycles or during any dummy cycles.  
Following the latency period the memory content, at the address given, is shifted out two bits at a time through  
IO0 (SI) and IO1 (SO). Two bits are shifted out at the SCK frequency at the falling edge of SCK signal.  
The address can start at any byte location of the memory array. The address is automatically incremented to the  
next higher address in sequential order after each byte of data is shifted out. The entire memory can therefore  
be read out with one single read instruction and address 000000h provided. When the highest address is reached,  
the address counter will wrap around and roll back to 000000h, allowing the read sequence to be continued  
indefinitely.  
CS# should not be driven high during mode or dummy bits as this may make the mode bits indeterminate.  
CS#  
SCK  
IO0  
IO1  
7
6
5
4
3
2
1
0
22  
23  
2
3
0
1
6
7
4
5
2
3
0
1
6
7
4
5
2
3
0
1
6
7
4
5
2
3
0
1
Phase  
Instruction  
Address  
Mode  
Dum  
Data 1  
Data 2  
Figure 64  
Note  
Dual I/O Read command sequence (3-byte address, BBh [CR2V[7] = 0])[48]  
48.Least significant 4 bits of Mode are don’t care and it is optional for the host to drive these bits. The host may  
turn off drive during these cycles to increase bus turn around time between Mode bits from host and  
returning data from the memory. The Mode bits must not equal Axh, the Continuous Read Mode is not  
supported for the S70FS01GS.  
Datasheet  
108 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
CS#  
SCK  
IO0  
IO1  
7
6
5
4
3
2
1
0
30  
31  
2
3
0
1
6
7
4
5
2
3
0
1
6
7
4
5
2
3
0
1
6
7
4
5
2
3
0
1
Phase  
Instruction  
Address  
Mode  
Dum  
Data 1  
Data 2  
Figure 65  
Dual I/O Read command sequence (4-byte address, BBh [CR2V[7] = 1])  
10.4.4  
Quad I/O Read (QIOR EBh or 4QIOR ECh)  
The instruction  
• EBh (CR2V[7] = 0) is followed by a 3-byte address (A23–A0) or  
• EBh (CR2V[7] = 1) is followed by a 4-byte address (A31–A0) or  
• ECh is followed by a 4-byte address (A31–A0)  
The Quad I/O Read command improves throughput with four I/O signals — IO0–IO3. It allows input of the address  
bits four bits per serial SCK clock. In some applications, the reduced instruction overhead might allow for code  
execution (XIP) directly from FS-S Family devices. The QUAD bit of the Configuration Register must be set  
(CR1V[1]=1) to enable the Quad capability of FS-S Family devices.  
The maximum operating clock frequency for Quad I/O Read is 133 MHz.  
For the Quad I/O Read command, there is a latency required after the mode bits (described below) before data  
begins shifting out of IO0–IO3. This latency period (i.e., dummy cycles) allows the device’s internal circuitry  
enough time to access data at the initial address. During latency cycles, the data value on IO0–IO3 are “don’t care”  
and may be high impedance. The number of dummy cycles is determined by the frequency of SCK. The latency  
is configured in CR2V[3:0].  
Following the latency period, the memory contents at the address given, is shifted out four bits at a time through  
IO0–IO3. Each nibble (4 bits) is shifted out at the SCK frequency by the falling edge of the SCK signal.  
The address can start at any byte location of the memory array. The address is automatically incremented to the  
next higher address in sequential order after each byte of data is shifted out. The entire memory can therefore  
be read out with one single read instruction and address 000000h provided. When the highest address is reached,  
the address counter will wrap around and roll back to 000000h, allowing the read sequence to be continued  
indefinitely.  
For the S70FS01GS, do not enable the Continuous Read Mode, this will cause bus contention between the two  
512 Mb die. The Mode bits must not equal Axh, this will keep the device in standard read mode.  
Note that the two mode bit clock cycles & additional wait states (i.e., dummy cycles) allow the device’s internal  
circuitry latency time to access the initial address after the last address cycle that is clocked into IO0–IO3.  
It is important that the IO0–IO3 signals be set to high-impedance at or before the falling edge of the first data out  
clock. At higher clock speeds the time available to turn off the host outputs before the memory device begins to  
drive (bus turn around) is diminished. It is allowed and may be helpful in preventing IO0–IO3 signal contention,  
for the host system to turn off the IO0–IO3 signal outputs (make them high impedance) during the last “don’t  
care” mode cycle or during any dummy cycles.  
CS# should not be driven high during mode or dummy bits as this may make the mode bits indeterminate.  
In QPI Mode (CR2V[6] = 1), the Quad I/O instructions are sent 4 bits per SCK rising edge. The remainder of the  
command protocol is identical to the Quad I/O commands.  
Datasheet  
109 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
CS#  
SCLK  
IO0  
IO1  
7
6
5
4
3
2
1
0
20  
21  
22  
23  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
0
1
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Address  
Mode  
Instruction  
Dummy  
D1  
D2  
D3  
D4  
Figure 66  
Quad I/O Read command sequence (3-byte address, EBh [CR2V[7] = 0])  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
20  
21  
22  
23  
4
5
6
7
0
1
2
3
4
5
6
7
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
0
1
IO3  
Phase  
Instruct.  
Address Mode  
Dummy  
D1  
D2  
D3  
D4  
Figure 67  
Quad I/O Read command sequence (3-byte address, EBh [CR2V[7] = 0]) QPI mode  
CS#  
SCK  
IO0  
IO1  
7
6
5
4
3
2
1
0
28  
29  
30  
31  
4
5
6
7
0
1
2
3
4
5
6
7
0
1
0
1
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Address Mode  
Dummy  
D1  
D2  
D3  
D4  
Figure 68  
Quad I/O Read command sequence (4-byte address, ECh or EBh [CR2V[7] = 1])  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
28  
29  
30  
31  
4
5
6
7
0
1
2
3
4
5
6
7
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruct.  
Address Mode  
Dummy  
D1  
D2  
D3  
D4  
Figure 69  
Quad I/O Read command sequence (4-byte address, ECh or EBh [CR2V[7] = 1]) QPI mode  
Datasheet  
110 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.4.5  
DDR Quad I/O Read (EDh, EEh)  
The DDR Quad I/O Read command improves throughput with four I/O signals - IO0–IO3. It is similar to the Quad  
I/O Read command but allows input of the address four bits on every edge of the clock. In some applications, the  
reduced instruction overhead might allow for code execution (XIP) directly from FS-S Family devices. The QUAD  
bit of the Configuration Register must be set (CR1V[1] = 1) to enable the Quad capability.  
The instruction  
• EDh (CR2V[7] = 0) is followed by a 3-byte address (A23–A0) or  
• EDh (CR2V[7] = 1) is followed by a 4-byte address (A31–A0) or  
• EEh is followed by a 4-byte address (A31–A0)  
The address is followed by mode bits. Then the memory contents, at the address given, is shifted out, in a DDR  
fashion, with four bits at a time on each clock edge through IO0–IO3.  
The maximum operating clock frequency for DDR Quad I/O Read command is 80 MHz.  
For DDR Quad I/O Read, there is a latency required after the last address and mode bits are shifted into the  
IO0–IO3 signals before data begins shifting out of IO0–IO3. This latency period (dummy cycles) allows the device’s  
internal circuitry enough time to access the initial address. During these latency cycles, the data value on  
IO0–IO3 are “don’t care” and may be high impedance. When the Data Learning Pattern (DLP) is enabled the host  
system must not drive the IO signals during the dummy cycles. The IO signals must be left high impedance by the  
host so that the memory device can drive the DLP during the dummy cycles.  
The number of dummy cycles is determined by the frequency of SCK. The latency is configured in CR2V[3:0].  
For the S70FS01GS, do not enable the Continuous Read Mode, this will cause bus contention between the two  
512Mb die. The upper nibble (IO[7:4]) and lower nibble (IO[3:0]) of the Mode bits must not be complementary (i.e.  
5h and Ah); this keeps the device in the standard DDR Quad I/O read mode.  
The address can start at any byte location of the memory array. The address is automatically incremented to the  
next higher address in sequential order after each byte of data is shifted out. The entire memory can therefore  
be read out with one single read instruction and address 000000h provided. When the highest address is reached,  
the address counter will wrap around and roll back to 000000h, allowing the read sequence to be continued  
indefinitely.  
CS# should not be driven HIGH during mode or dummy bits as this may make the mode bits indeterminate. Note  
that the memory devices may drive the IOs with a preamble prior to the first data value. The preamble is a Data  
Learning Pattern (DLP) that is used by the host controller to optimize data capture at higher frequencies. The  
preamble drives the IO bus for the four clock cycles immediately before data is output. The host must be sure to  
stop driving the IO bus prior to the time that the memory starts outputting the preamble.  
The preamble is intended to give the host controller an indication about the round trip time from when the host  
drives a clock edge to when the corresponding data value returns from the memory device. The host controller  
will skew the data capture point during the preamble period to optimize timing margins and then use the same  
skew time to capture the data during the rest of the read operation. The optimized capture point will be  
determined during the preamble period of every read operation. This optimization strategy is intended to  
compensate for both the PVT (process, voltage, temperature) of both the memory device and the host controller  
as well as any system level delays caused by flight time on the PCB.  
Although the data learning pattern (DLP) is programmable, the following example shows example of the DLP of  
34h. The DLP 34h (or 00110100) will be driven on each of the active outputs (i.e. all four SIOs). This pattern was  
chosen to cover both “DC” and “AC” data transition scenarios. The two DC transition scenarios include data low  
for a long period of time (two half clocks) followed by a HIGH going transition (001) and the complementary LOW  
going transition (110). The two AC transition scenarios include data low for a short period of time (one half clock)  
followed by a HIGH going transition (101) and the complementary LOW going transition (010). The DC transitions  
will typically occur with a starting point closer to the supply rail than the AC transitions that may not have fully  
settled to their steady state (DC) levels. In many cases the DC transitions will bound the beginning of the data  
valid period and the AC transitions will bound the ending of the data valid period. These transitions will allow the  
host controller to identify the beginning and ending of the valid data eye. Once the data eye has been  
characterized the optimal data capture point can be chosen. See “SPI DDR Data Learning Registers” on page 73  
for more details.  
Datasheet  
111 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
In QPI Mode (CR2V[6] = 1) the DDR Quad I/O instructions are sent 4 bits per SCK rising edge. The remainder of the  
command protocol is identical to the DDR Quad I/O commands.  
CS#  
SCK  
IO0  
IO1  
7
6
5
4
3
2
1
0
20 1612 8  
21 1713 9  
4
5
0
1
2
3
4
5
6
7
0
1
2
3
7
7
7
7
6
6
6
6
5
5
5
5
4
4
4
4
3
3
3
3
2
2
2
2
1
1
1
1
0
0
0
0
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
22 181410 6  
23 191511 7  
Address  
IO3  
Phase  
Instruction  
Mode  
Dummy  
DLP  
D1 D2  
Figure 70  
DDR Quad I/O Read initial access (3-byte address, EDh [CR2V[7] = 0)  
CS#  
SCK  
IO0  
IO1  
7
6
5
4
3
2
1
0
2824201612 8  
2925211713 9  
4
5
0
1
2
3
4
5
6
7
0
1
2
3
6
6
6
6
5 4  
5 4  
5 4  
5 4  
3
3
3
3
2
1 0  
1 0  
1 0  
1 0  
4
5
6
7
0
1
2
3
4
5
6
7
0
2
2
2
IO2  
302622181410 6  
312723191511 7  
Address  
IO3  
Phase  
Instruction  
Mode  
Dummy  
DLP  
D1 D2  
Figure 71  
DDR Quad I/O Read initial access (4-byte address, EEh or EDh [CR2V[7] = 1])[49]  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
28 24 20 16 12  
29 25 21 17 13  
8
9
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
7
7
7
7
6
6
6
6
5
5
5
5
4
4
4
4
3
3
3
3
2
2
2
2
1
1
1
1
0
0
0
0
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
IO2  
30 26 22 18 14 10  
31 27 23 19 15 11  
Address  
IO3  
Phase  
Instruct.  
Mode  
Dummy  
DLP  
D1  
D2  
Figure 72  
DDR Quad I/O Read initial access (4-byte address, EEh or EDh [CR2V[7] = 1]) QPI mode[50]  
Notes  
49.Example DLP of 34h (or 00110100).  
50.Example DLP of 34h (or 00110100).  
Datasheet  
112 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.5  
Program Flash Array Commands  
10.5.1  
Program Granularity  
10.5.1.1  
Automatic ECC  
Each 16 byte aligned and 16 byte length Programming Block has a hidden Error Correction Code (ECC) value. The  
data block plus ECC form an ECC unit. In combination with Error Detection and Correction (EDC) logic the ECC is  
used to detect and correct any single bit error found during a read access. When data is first programmed within  
an ECC unit the ECC value is set for the entire ECC unit. If the same ECC unit is programmed more than once the  
ECC value is changed to disable the EDC function. A sector erase is needed to again enable Automatic ECC on that  
Programming Block. The 16 byte Program Block is the smallest program granularity on which Automatic ECC is  
enabled.  
These are automatic operations transparent to the user. The transparency of the Automatic ECC feature  
enhances data accuracy for typical programming operations which write data once to each ECC unit but,  
facilitates software compatibility to previous generations of FL family of products by still allowing for single byte  
programming and bit walking in which the same ECC unit is programmed more than once. When an ECC unit has  
Automatic ECC disabled, EDC is not done on data read from the ECC unit location.  
An ECC status register is provided for determining if ECC is enabled on an ECC unit and whether any errors have  
been detected and corrected in the ECC unit data or the ECC. The ECC Status Register Read (ECCRD) command  
is used to read the ECC status on any ECC unit.  
10.5.1.2  
Page Programming  
Page Programming is done by loading a Page Buffer with data to be programmed and issuing a programming  
command to move data from the buffer to the memory array. This sets an upper limit on the amount of data that  
can be programmed with a single programming command. Page Programming allows up to a page size (either  
256 or 512 bytes) to be programmed in one operation. The page size is determined by the configuration register  
bit CR3V[4].The page is aligned on the page size address boundary. It is possible to program from one bit up to a  
page size in each Page programming operation. It is recommended that a multiple of 16 byte length and aligned  
Program Blocks be written. This insures that Automatic ECC is not disabled. For the very best performance,  
programming should be done in full pages of 512 bytes aligned on 512 byte boundaries with each Page being  
programmed only once.  
10.5.1.3  
Single Byte Programming  
Single Byte Programming allows full backward compatibility to the legacy standard SPI Page Programming (PP)  
command by allowing a single byte to be programmed anywhere in the memory array. While single byte  
programming is supported, this will disable Automatic ECC on the 16 byte ECC unit where the byte is located.  
10.5.2  
Page Program (PP 02h or 4PP 12h)  
The Page Program (PP) command allows bytes to be programmed in the memory (changing bits from 1 to 0).  
Before the Page Program (PP) commands can be accepted by the device, a Write Enable (WREN) command must  
be issued and decoded by the device. After the Write Enable (WREN) command has been decoded successfully,  
the device sets the Write Enable Latch (WEL) in the Status Register to enable any write operations.  
The instruction  
• 02h (CR2V[7] = 0) is followed by a 3-byte address (A23–A0) or  
• 02h (CR2V[7] = 1) is followed by a 4-byte address (A31–A0) or  
• 12h is followed by a 4-byte address (A31–A0)  
and at least one data byte on SI. Depending on CR3V[4], the page size can either be 256 or 512 Bytes. Up to a page  
can be provided on SI after the 3-byte address with instruction 02h or 4-byte address with instruction 12h has  
been provided.  
Datasheet  
113 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
If more data is sent to the device than the space between the starting address and the page aligned end boundary,  
the data loading sequence will wrap from the last byte in the page to the zero byte location of the same page and  
begin overwriting any data previously loaded in the page. The last page worth of data is programmed in the page.  
This is a result of the device being equipped with a page program buffer that is only page size in length. If less  
than a page of data is sent to the device, these data bytes will be programmed in sequence, starting at the  
provided address within the page, without having any affect on the other bytes of the same page.  
Using the Page Program (PP) command to load an entire page, within the page boundary, will save overall  
programming time versus loading less than a page into the program buffer.  
The programming process is managed by the Flash memory device internal control logic. After a programming  
command is issued, the programming operation status can be checked using the Read Status Register-1  
command. The WIP bit (SR1V[0]) will indicate when the programming operation is completed. The P_ERR bit  
(SR1V[6]) will indicate if an error occurs in the programming operation that prevents successful completion of  
programming. This includes attempted programming of a protected area.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Input Data 1  
Input Data 2  
Figure 73  
Page Program (PP 02h or 4PP 12h) command sequence[51]  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
A-3  
A-2  
A-1  
A
4
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
0
1
2
3
5
IO2  
6
7
IO3  
Phase  
Instruct.  
Address  
Input D1  
Input D2  
Input D3  
Input D4  
Figure 74  
Page Program (PP 02h or 4PP 12h) QPI mode command sequence[52]  
Notes  
51.A = MSB of address = A23 for PP 02h, or A31 for 4PP 12h.  
52.A = MSB of address = A23 for PP 02h, or A31 for 4PP 12h.  
Datasheet  
114 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.6  
Erase Flash Array Commands  
Parameter 4 KB-Sector Erase (P4E 20h or 4P4E 21h)  
10.6.1  
The main Flash array address map may be configured to overlay 4 KB parameter sectors over the lowest address  
portion of the lowest address uniform sector (bottom parameter sectors) or over the highest address portion of  
the highest address uniform sector (top parameter sectors). The main Flash array address map may also be  
configured to have only uniform size sectors. The parameter sector configuration is controlled by the  
configuration bit CR3V[3]. The P4E and 4P4E commands are ignored when the device is configured for uniform  
sectors only (CR3V[3] = 1).  
The Parameter 4 KB-sector Erase commands set all the bits of a 4 KB parameter sector to 1 (all bytes are FFh).  
Before the P4E or 4P4E command can be accepted by the device, a Write Enable (WREN) command must be issued  
and decoded by the device, which sets the Write Enable Latch (WEL) in the Status Register to enable any write  
operations.  
The instruction  
• 20h [CR2V[7] = 0] is followed by a 3-byte address (A23–A0), or  
• 20h [CR2V[7] = 1] is followed by a 4-byte address (A31–A0), or  
• 21h is followed by a 4-byte address (A31–A0)  
CS# must be driven into the logic HIGH state after the twenty-fourth or thirty-second bit of the address has been  
latched in on SI. This will initiate the beginning of internal erase cycle, which involves the pre-programming and  
erase of the chosen sector of the flash memory array. If CS# is not driven HIGH after the last bit of address, the  
sector erase operation will not be executed.  
As soon as CS# is driven HIGH, the internal erase cycle will be initiated. With the internal erase cycle in progress,  
the user can read the value of the Write-In Progress (WIP) bit to determine when the operation has been  
completed. The WIP bit will indicate a “1. when the erase cycle is in progress and a “0” when the erase cycle has  
been completed.  
A P4E or 4P4E command applied to a sector that has been write protected through the Block Protection bits or  
ASP, will not be executed and will set the E_ERR status. A P4E command applied to a sector that is larger than  
4 KB will not be executed and will not set the E_ERR status.  
Datasheet  
115 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
Phase  
Instruction  
Address  
Figure 75  
Parameter Sector Erase (P4E 20h or 4P4E 21h) command sequence[53]  
This command is also supported in QPI Mode. In Quad AIl mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
A-3  
A-2  
A-1  
A
4
0
1
2
3
5
IO2  
6
7
IO3  
Phase  
Instructtion  
Address  
Figure 76  
Parameter Sector Erase (P4E 20h or 4P4E 21h) QPI mode command sequence[53]  
Note  
53.A = MSB of address = A23 for P4E 20h with CR2V[7] = 0, or A31 for P4E 20h with CR2V[7] = 1 or 4P4E 21h.  
Datasheet  
116 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.6.2  
Sector Erase (SE D8h or 4SE DCh)  
The Sector Erase (SE) command sets all bits in the addressed sector to 1 (all bytes are FFh). Before the Sector  
Erase (SE) command can be accepted by the device, a Write Enable (WREN) command must be issued and  
decoded by the device, which sets the Write Enable Latch (WEL) in the Status Register to enable any write  
operations.  
The instruction  
• D8h [CR2V[7] = 0] is followed by a 3-byte address (A23–A0), or  
• D8h [CR2V[7] = 1] is followed by a 4-byte address (A31–A0), or  
• DCh is followed by a 4-byte address (A31–A0)  
CS# must be driven into the logic HIGH state after the twenty-fourth or thirty-second bit of address has been  
latched in on SI. This will initiate the erase cycle, which involves the pre-programming and erase of the chosen  
sector. If CS# is not driven HIGH after the last bit of address, the sector erase operation will not be executed.  
As soon as CS# is driven into the logic HIGH state, the internal erase cycle will be initiated. With the internal erase  
cycle in progress, the user can read the value of the Write-In Progress (WIP) bit to check if the operation has been  
completed. The WIP bit will indicate a “1” when the erase cycle is in progress and a “0” when the erase cycle has  
been completed.  
A Sector Erase (SE) command applied to a sector that has been Write Protected through the Block Protection bits  
or ASP, will not be executed and will set the E_ERR status.  
A device configuration option (CR3V[3]) determines whether 4 KB parameter sectors are in use. When  
CR3V[3] = 0, 4 KB parameter sectors overlay a portion of the highest or lowest address 32 KB of the device address  
space. If a sector erase command is applied to a 256 KB range that is overlaid by 4 KB sectors, the overlaid 4 KB  
sectors are not affected by the erase. When CR3V[3] = 1, there are no 4 KB parameter sectors in the device address  
space and the Sector Erase command always operates on fully visible 256 KB sectors. ASP has a PPB and a DYB  
protection bit for each physical sector, including any 4 KB sectors.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
Phase  
Instruction  
Address  
Figure 77  
Sector Erase (SE D8h or 4SE DCh) command sequence[54]  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
A-3  
A-2  
A-1  
A
4
0
1
2
3
5
IO2  
6
7
IO3  
Phase  
Instructtion  
Address  
Figure 78  
Note  
Sector Erase (SE D8h or 4SE DCh) QPI mode command sequence[54]  
54.A = MSB of address = A23 for SE D8h with CR2V[7] = 0, or A31 for SE D8h with CR2V[7] = 1 or 4P4E DCh.  
Datasheet  
117 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.6.3  
Bulk Erase (BE 60h or C7h)  
The Bulk Erase (BE) command is not supported in the FS01GS. The Bulk Erase Addressed (BEA, FEh), with a 4 byte  
address, is used instead to direct the bulk erase operation to the lower or upper FS512S device.  
10.6.4  
Bulk Erase Addressed (BEA FEh)  
The Bulk Erase (BE) command is not supported in the FS01GS. The Bulk Erase Addressed (BEA) command, with  
a 4 byte address, is used instead to direct the bulk erase operation to the lower or upper FS512S device.  
The BEA command sets all bits to 1 (all bytes are FFh) inside the entire flash memory array of the address selected  
lower or upper FS512S device. The other FS512S device, that is not selected, is not affected. Before the BEA  
command can be accepted by the device, a Write Enable (WREN) command must be issued and decoded by the  
device, which sets the Write Enable Latch (WEL) in the Status Register to enable any write operations.  
CS# must be driven into the logic HIGH state after the last bit of the address has been latched in on SI. This will  
initiate the erase cycle, which involves the pre-programming and erase of the entire flash memory array of the  
selected device. If CS# is not driven HIGH after the last bit of address, the BEA operation will not be executed.  
As soon as CS# is driven into the logic HIGH state, the erase cycle will be initiated. With the erase cycle in progress,  
the user can read the value of the Write-In Progress (WIP) bit to determine when the operation has been  
completed. The WIP bit will indicate a “1” when the erase cycle is in progress and a “0” when the erase cycle has  
been completed.  
A BEA command can be executed only when the Block Protection (BP2, BP1, BP0) bits, in the selected device, are  
set to “0” s. If the BPA bits are not zero, the BEA command is not executed and E_ERR is not set. The BEA command  
will skip any sectors protected by the DYB or PPB, in the selected device, and the E_ERR status will not be set.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
Phase  
Instruction  
Address  
Figure 79  
Bulk Erase Addressed command sequence[55]  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
A-3  
A-2  
A-1  
A
4
0
1
2
3
5
IO2  
6
7
IO3  
Phase  
Instructtion  
Address  
Figure 80  
Bulk Erase Addressed command sequence QPI mode[55]  
Note  
55.A = MSB of address = A31.  
Datasheet  
118 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.6.5  
Evaluate Erase Status (EES D0h)  
The Evaluate Erase Status (EES) command verifies that the last erase operation on the addressed sector was  
completed successfully. If the selected sector was successfully erased the erase status bit (SR2V[2]) is set to 1. If  
the selected sector was not completely erased SR2V[2] is 0.  
The EES command can be used to detect erase operations failed due to loss of power, reset, or failure during the  
erase operation.  
The EES instruction is followed by a 3 or 4 byte address, depending on the address length configuration (CR2V[7]).  
The EES command requires tEES to complete and update the erase status in SR2V. The WIP bit (SR1V[0]) may be  
read using the RDSR1 (05h) command, to determine when the EES command is finished. Then the RDSR2 (07h)  
or the RDAR (65h) command can be used to read SR2V[2]. If a sector is found not erased with SR2V[2] = 0, the  
sector must be erased again to ensure reliable storage of data in the sector.  
The Write Enable command (to set the WEL bit) is not required before the EES command. However, the WEL bit  
is set by the device itself and cleared at the end of the operation, as visible in SR1V[1] when reading status.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
Phase  
Instruction  
Address  
Figure 81  
EES command sequence[56]  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
A-3  
A-2  
A-1  
A
4
0
1
2
3
5
IO2  
6
7
IO3  
Phase  
Instructtion  
Address  
Figure 82  
EES QPI mode command sequence[56]  
Note  
56.A = MSB of address = A23 for CR2V[7] = 0, or A31 for CR2V[7] = 1.  
Datasheet  
119 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.6.6  
Erase or Program Suspend (EPS 85h, 75h)  
There are three instruction codes for Program or Erase Suspend (EPS) to enable legacy and alternate source  
software compatibility.  
The EPS command allows the system to interrupt a programming or erase operation and then read from any  
other non-erase-suspended sector or non-program-suspended-page. Program or Erase Suspend is valid only  
during a programming or sector erase operation. A Bulk Erase operation cannot be suspended.  
The Write in Progress (WIP) bit in Status Register 1 (SR1V[0]) must be checked to know when the programming or  
erase operation has stopped. The Program Suspend Status bit in the Status Register-2 (SR2[0]) can be used to  
determine if a programming operation has been suspended or was completed at the time WIP changes to 0. The  
Erase Suspend Status bit in the Status Register-2 (SR2[1]) can be used to determine if an erase operation has been  
suspended or was completed at the time WIP changes to 0. The time required for the suspend operation to  
complete is tSL, see Table 53.  
An Erase can be suspended to allow a program operation or a read operation. During an erase suspend, the DYB  
array may be read to examine sector protection and written to remove or restore protection on a sector to be  
programmed.  
A program operation may be suspended to allow a read operation.  
A new erase operation is not allowed with an already suspended erase or program operation. An erase command  
is ignored in this situation.  
The FS01GS uses the EPS instruction codes differently than other FS family devices:  
• The EPS 85h instruction is used to suspend only a program operation in either the upper or lower FS512S device  
in the DDP.  
• The EPS 75h instruction is used to suspend only an erase operation in either the upper or lower FS512S device  
in the DDP.  
• The EPS B0h instruction is not supported.  
Table 49  
Commands allowed during Program or Erase Suspend  
Allowed Allowed  
Instruction  
Instruction  
Name  
During  
Erase  
During  
Code  
(Hex)  
Comment  
Program  
Suspend Suspend  
Required for array program during erase suspend. Only  
allowed if there is no other program suspended program  
operation (SR2V[0] = 0). A program command will be  
ignored while there is a suspended program. If a program  
command is sent for a location within an erase suspended  
sector the program operation will fail with the P_ERR bit  
set.  
PP  
02  
X
READ  
RDAR  
WREN  
03  
65  
06  
X
X
X
X
X
All array reads allowed in suspend  
Alternate way to read WIP to determine end of suspend  
process  
Required for program command within erase suspend.  
Required for array program during erase suspend. Only  
allowed if there is no other program suspended program  
operation (SR2V[0] = 0). A program command will be  
ignored while there is a suspended program. If a program  
command is sent for a location within an erase suspended  
sector the program operation will fail with the P_ERR bit  
set.  
4PP  
12  
13  
X
X
4READ  
X
All array reads allowed in suspend  
Datasheet  
120 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
Table 49  
Commands allowed during Program or Erase Suspend (Continued)  
Allowed Allowed  
Instruction  
Code  
Instruction  
Name  
During  
Erase  
During  
Comment  
Program  
(Hex)  
Suspend Suspend  
Clear status may be used if a program operation fails  
during erase suspend. Note the instruction is only valid if  
enabled for clear status by CR4NV[2 = 1]  
Clear status may be used if a program operation fails  
during erase suspend.  
CLSR  
CLSR  
30  
X
82  
X
EPR  
EPR  
RSTEN  
RST  
7A  
8A  
66  
99  
0B  
0C  
BB  
BC  
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Required to resume from erase or program suspend.  
Required to resume from erase or program suspend.  
Reset allowed anytime  
Reset allowed anytime  
FAST_READ  
4FAST_READ  
DIOR  
All array reads allowed in suspend  
All array reads allowed in suspend  
All array reads allowed in suspend  
All array reads allowed in suspend  
4DIOR  
It may be necessary to remove and restore dynamic  
protection during erase suspend to allow programming  
during erase suspend.  
DYBRD  
FA  
X
It may be necessary to remove and restore dynamic  
protection during erase suspend to allow programming  
during erase suspend.  
Allowed for checking persistent protection before  
attempting a program command during erase suspend.  
It may be necessary to remove and restore dynamic  
protection during erase suspend to allow programming  
during erase suspend.  
DYBWR  
PPBRD  
4DYBRD  
FB  
FC  
E0  
X
X
X
It may be necessary to remove and restore dynamic  
protection during erase suspend to allow programming  
during erase suspend.  
Allowed for checking persistent protection before  
attempting a program command during erase suspend.  
4DYBWR  
4PPBRD  
E1  
E2  
X
X
QIOR  
4QIOR  
DDRQIOR  
4DDRQIOR  
RESET  
EB  
EC  
ED  
EE  
F0  
FF  
X
X
X
X
X
X
X
X
X
X
X
X
All array reads allowed in suspend  
All array reads allowed in suspend  
All array reads allowed in suspend  
All array reads allowed in suspend  
Reset allowed anytime  
MBR  
May need to reset a read operation during suspend  
Datasheet  
121 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
Reading at any address within an erase-suspended sector or program-suspended page produces undetermined  
data.  
The WRAR, or PPB Erase commands are not allowed during Erase or Program Suspend, it is therefore not possible  
to alter the Block Protection or PPB bits during Erase Suspend. If there are sectors that may need programming  
during Erase suspend, these sectors should be protected only by DYB bits that can be turned off during Erase  
Suspend.  
After an erase-suspended program operation is complete, the device returns to the Erase Suspend Mode. The  
system can determine the status of the program operation by reading the WIP bit in the Status Register, just as  
in the standard program operation.  
tSL  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7 6 5 4 3 2 1 0  
7
6 5 4 3 2 1 0  
Phase  
Phase  
Suspend Instruction  
Read Status Instruction  
Status  
Instr. During Suspend  
Repeat Status Read Until Suspended  
Figure 83  
Program or Erase Suspend command sequence  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 84  
Erase or Program Suspend command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 85  
Erase or Program Suspend command sequence QPI mode  
Datasheet  
122 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.6.7  
Erase or Program Resume (EPR 7Ah, 8Ah)  
An Erase or Program Resume command must be written to resume a suspended operation. There are three  
instruction codes for Erase or Program Resume (EPR) to enable legacy and alternate source software  
compatibility.  
After program or read operations are completed during a program or erase suspend the Erase or Program  
Resume command is sent to continue the suspended operation.  
After an Erase or Program Resume command is issued, the WIP bit in the Status Register-1 will be set to a 1 and  
the programming operation will resume if one is suspended. If no program operation is suspended the  
suspended erase operation will resume. If there is no suspended program or erase operation the resume  
command is ignored.  
Program or erase operations may be interrupted as often as necessary e.g. a program suspend command could  
immediately follow a program resume command but, in order for a program or erase operation to progress to  
completion there must be some periods of time between resume and the next suspend command greater than  
or equal to tRS. See Table 53.  
The FS01GS uses the EPR instruction codes differently than other FS family devices:  
• The EPR 8Ah instruction is used to resume only a program operation in either the upper or lower FS512S device  
in the DDP.  
• The EPR 7Ah instruction is used to resume only an erase operation in either the upper or lower FS512S device  
in the DDP.  
• The EPR 30h instruction is not supported.  
By using separate instruction codes for program versus erase resume, the correct operation is resumed when the  
lower FS512S has one operation suspended and the upper FS512S has a different operation suspended.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 86  
Erase or Program Resume command sequence  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 87  
Erase or Program Resume command sequence QPI mode  
Datasheet  
123 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.7  
One Time Program Array Commands  
OTP Program (OTPP 42h)  
10.7.1  
The OTP Program command programs data in the One Time Program region, which is in a different address space  
from the main array data. The OTP region is 1024 bytes so, the address bits from A31 to A10 must be zero for this  
command. Refer to “OTP address space” on page 50 for details on the OTP region.  
Before the OTP Program command can be accepted by the device, a Write Enable (WREN) command must be  
issued and decoded by the device, which sets the Write Enable Latch (WEL) in the Status Register to enable any  
write operations. The WIP bit in SR1V may be checked to determine when the operation is completed. The P_ERR  
bit in SR1V may be checked to determine if any error occurred during the operation.  
To program the OTP array in bit granularity, the rest of the bits within a data byte can be set to “1.  
Each region in the OTP memory space can be programmed one or more times, provided that the region is not  
locked. Attempting to program zeros in a region that is locked will fail with the P_ERR bit in SR1V set to “1.  
Programming ones, even in a protected area does not cause an error and does not set P_ERR. Subsequent OTP  
programming can be performed only on the un-programmed bits (that is, “1” data). Programming more than  
once within an ECC unit will disable ECC on that unit.  
The protocol of the OTP Program command is the same as the Page Program command. See “Page Program (PP  
02h or 4PP 12h)” on page 113 for the command sequence.  
10.7.2  
OTP Read (OTPR 4Bh)  
The OTP Read command reads data from the OTP region. The OTP region is 1024 bytes so, the address bits from  
A31 to A10 must be zero for this command. Refer to “OTP address space” on page 50 for details on the OTP  
region. The protocol of the OTP Read command is similar to the Fast Read command except that it will not wrap  
to the starting address after the OTP address is at its maximum; instead, the data beyond the maximum OTP  
address will be undefined. The OTP Read command read latency is set by the latency value in CR2V[3:0].  
See “Fast Read (FAST_READ 0Bh or 4FAST_READ 0Ch)” on page 107 for the command sequence.  
Datasheet  
124 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.8  
Advanced Sector Protection Commands  
ASP Read (ASPRD 2Bh)  
10.8.1  
The ASP Read instruction 2Bh is shifted into SI by the rising edge of the SCK signal. Then the 16-bit ASP register  
contents are shifted out on the serial output SO, least significant byte first. Each bit is shifted out at the SCK  
frequency by the falling edge of the SCK signal. It is possible to read the ASP register continuously by providing  
multiples of 16 clock cycles. The maximum operating clock frequency for the ASP Read (ASPRD) command is  
133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Output ASPR Low Byte  
Output ASPR High Byte  
Figure 88  
ASPRD command  
10.8.2  
DYB Read (DYBRD FAh or 4DYBRD E0h)  
The instruction is latched into SI by the rising edge of the SCK signal. The instruction is followed by the 24 or 32-Bit  
address, depending on the address length configuration CR2V[7], selecting location zero within the desired  
sector. Note, the high order address bits not used by a particular density device must be zero. Then the 8-bit DYB  
access register contents are shifted out on the serial output SO. Each bit is shifted out at the SCK frequency by  
the falling edge of the SCK signal. It is possible to read the same DYB access register continuously by providing  
multiples of eight clock cycles. The address of the DYB register does not increment so this is not a means to read  
the entire DYB array. Each location must be read with a separate DYB Read command. The maximum operating  
clock frequency for READ command is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Register  
Repeat Register  
Figure 89  
DYBRD command sequence[57, 58]  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction and address is shifted in on  
IO0–IO3 and returning data is shifted out on IO0–IO3.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
A-3  
A-2  
A-1  
A
4
0
1
2
3
4
5
6
7
0
1
2
3
5
IO2  
6
7
IO3  
Phase  
Instruction  
Address  
Output DYBAR  
Figure 90  
Notes  
DYBRD QPI mode command sequence[57, 58]  
57.A = MSB of address = 23 for Address length (CR2V[7] = 0, or 31 for CR2V[7] = 1 with command FAh.  
58.A = MSB of address = 31 with command E0h.  
Datasheet  
125 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.8.3  
DYB Write (DYBWR FBh or 4DYBWR E1h)  
Before the DYB Write (DYBWR) command can be accepted by the device, a Write Enable (WREN) command must  
be issued. After the Write Enable (WREN) command has been decoded, the device will set the Write Enable Latch  
(WEL) in the Status Register to enable any write operations.  
The DYBWR command is entered by driving CS# to the logic LOW state, followed by the instruction, followed by  
the 24 or 32-Bit address, depending on the address length configuration CR2V[7], selecting location zero within  
the desired sector (note, the high order address bits not used by a particular density device must be zero), then  
the data byte on SI. The DYB Access Register is one data byte in length. The data value must be 00h to protect or  
FFh to unprotect the selected sector.  
The DYBWR command affects the P_ERR and WIP bits of the Status & Configuration Registers in the same manner  
as any other programming operation. CS# must be driven to the logic HIGH state after the eighth bit of data has  
been latched in. As soon as CS# is driven to the logic HIGH state, the self-timed DYBWR operation is initiated. While  
the DYBWR operation is in progress, the Status Register may be read to check the value of the Write-In Progress  
(WIP) bit. The Write-In Progress (WIP) bit is a “1” during the self-timed DYBWR operation, and is a “0” when it is  
completed. When the DYBWR operation is completed, the Write Enable Latch (WEL) is set to a “0”  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Input Data  
Figure 91  
DYBWR command sequence[59, 60]  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
A-3  
A-2  
A-1  
A
4
0
1
2
3
4
5
6
7
0
1
2
3
5
IO2  
6
7
IO3  
Phase  
Instruction  
Address  
Input DYBAR  
Figure 92  
DYBWR QPI mode command sequence[59, 60]  
Notes  
59.A = MSB of address = 23 for Address length (CR2V[7] = 0, or 31 for CR2V[7] = 1 with command FBh.  
60.A = MSB of address = 31 with command E1h.  
Datasheet  
126 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.8.4  
PPB Read (PPBRD FCh or 4PPBRD E2h)  
The instruction E2h is shifted into SI by the rising edges of the SCK signal, followed by the 24 or 32-Bit address,  
depending on the address length configuration CR2V[7], selecting location zero within the desired sector (note,  
the high order address bits not used by a particular density device must be zero). Then the 8-bit PPB access  
register contents are shifted out on SO.  
It is possible to read the same PPB access register continuously by providing multiples of eight clock cycles. The  
address of the PPB register does not increment so this is not a means to read the entire PPB array. Each location  
must be read with a separate PPB Read command. The maximum operating clock frequency for the PPB Read  
command is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Address  
Register  
Repeat Register  
Figure 93  
PPBRD command sequence[61, 62]  
10.8.5  
PPB Program (PPBP FDh or 4PPBP E3h)  
Before the PPB Program (PPBP) command can be accepted by the device, a Write Enable (WREN) command must  
be issued. After the Write Enable (WREN) command has been decoded, the device will set the Write Enable Latch  
(WEL) in the Status Register to enable any write operations.  
The PPBP command is entered by driving CS# to the logic LOW state, followed by the instruction, followed by the  
24- or 32-Bit address, depending on the address length configuration CR2V[7], selecting location zero within the  
desired sector (note, the high order address bits not used by a particular density device must be zero).  
The PPBP command affects the P_ERR and WIP bits of the Status & Configuration Registers in the same manner  
as any other programming operation.  
CS# must be driven to the logic HIGH state after the last bit of address has been latched in. If not, the PPBP  
command is not executed. As soon as CS# is driven to the logic HIGH state, the self-timed PPBP operation is  
initiated. While the PPBP operation is in progress, the Status Register may be read to check the value of the  
Write-In Progress (WIP) bit. The Write-In Progress (WIP) bit is a “1” during the self-timed PPBP operation, and is a  
“0” when it is completed. When the PPBP operation is completed, the Write Enable Latch (WEL) is set to a “0.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
A
1
0
Phase  
Instruction  
Address  
Figure 94  
Notes  
PPBP command sequence[63, 64]  
61.A = MSB of address = 23 for Address length (CR2V[7] = 0, or 31 for CR2V[7] = 1 with command FCh.  
62.A = MSB of address = 31 with command E2h.  
63.A = MSB of address = 23 for Address length (CR2V[7] = 0, or 31 for CR2V[7] = 1 with command FDh.  
64.A = MSB of address = 31 with command E3h.  
Datasheet  
127 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.8.6  
PPB Erase (PPBE E4h)  
The PPB Erase (PPBE) command is not supported in the FS01GS. The PPB Erase Addressed (PBBEA) command,  
with a 4 byte address, is used instead to direct the PPB erase operation to the lower or upper FS512S device.  
The PPB Erase (PPBE) command sets all PPB bits to 1. Before the PPB Erase command can be accepted by the  
device, a Write Enable (WREN) command must be issued and decoded by the device, which sets the Write Enable  
Latch (WEL) in the Status Register to enable any write operations.  
The instruction E4h is shifted into SI by the rising edges of the SCK signal.  
CS# must be driven into the logic HIGH state after the eighth bit of the instruction byte has been latched in on SI.  
This will initiate the beginning of internal erase cycle, which involves the pre-programming and erase of the entire  
PPB memory array. Without CS# being driven to the logic HIGH state after the eighth bit of the instruction, the  
PPB erase operation will not be executed.  
With the internal erase cycle in progress, the user can read the value of the Write-In Progress (WIP) bit to check if  
the operation has been completed. The WIP bit will indicate a “1” when the erase cycle is in progress and a “0”  
when the erase cycle has been completed. Erase suspend is not allowed during PPB Erase.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 95  
PPB Erase command sequence  
10.8.7  
PPB Lock Bit Read (PLBRD A7h)  
The PPB Lock Bit Read (PLBRD) command allows the PPB Lock Register contents to be read out of SO. It is  
possible to read the PPB lock register continuously by providing multiples of eight clock cycles. The PPB Lock  
Register contents may only be read when the device is in standby state with no other operation in progress. It is  
recommended to check the Write-In Progress (WIP) bit of the Status Register before issuing a new command to  
the device.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Phase  
Instruction  
Register Read  
Repeat Register Read  
Figure 96  
PPB Lock Register Read command sequence  
Datasheet  
128 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.8.8  
PPB Lock Bit Write (PLBWR A6h)  
The PPB Lock Bit Write (PLBWR) command clears the PPB Lock Register to zero. Before the PLBWR command can  
be accepted by the device, a Write Enable (WREN) command must be issued and decoded by the device, which  
sets the Write Enable Latch (WEL) in the Status Register to enable any write operations.  
The PLBWR command is entered by driving CS# to the logic LOW state, followed by the instruction.  
CS# must be driven to the logic HIGH state after the eighth bit of instruction has been latched in. If not, the PLBWR  
command is not executed. As soon as CS# is driven to the logic HIGH state, the self-timed PLBWR operation is  
initiated. While the PLBWR operation is in progress, the Status Register may still be read to check the value of the  
Write-In Progress (WIP) bit. The Write-In Progress (WIP) bit is a “1” during the self-timed PLBWR operation, and is  
a “0” when it is completed. When the PLBWR operation is completed, the Write Enable Latch (WEL) is set to a “0.  
The maximum clock frequency for the PLBWR command is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 97  
PPB Lock Bit Write command sequence  
10.8.9  
Password Read (PASSRD E7h)  
The correct password value may be read only after it is programmed and before the Password Mode has been  
selected by programming the Password Protection Mode bit to 0 in the ASP Register (ASP[2]). After the Password  
Protection Mode is selected the password is no longer readable, the PASSRD command will output undefined  
data.  
The PASSRD command is shifted into SI. Then the 64-bit Password is shifted out on the serial output SO, least  
significant byte first, most significant bit of each byte first. Each bit is shifted out at the SCK frequency by the  
falling edge of the SCK signal. It is possible to read the Password continuously by providing multiples of 64 clock  
cycles. The maximum operating clock frequency for the PASSRD command is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
6
5
4
3
2
1
0
Phase  
Instruction  
Data 1  
Data N  
Figure 98  
Password Read command sequence  
Datasheet  
129 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.8.10  
Password Unlock (PASSU E9h)  
The PASSU command is entered by driving CS# to the logic LOW state, followed by the instruction and the  
password data bytes on SI, least significant byte first, most significant bit of each byte first. The password is  
sixty-four (64) bits in length.  
CS# must be driven to the logic HIGH state after the sixty-fourth (64th) bit of data has been latched. If not, the  
PASSU command is not executed. As soon as CS# is driven to the logic HIGH state, the self-timed PASSU operation  
is initiated. While the PASSU operation is in progress, the Status Register may be read to check the value of the  
Write-In Progress (WIP) bit. The Write-In Progress (WIP) bit is a “1” during the self-timed PASSU cycle, and is a “0”  
when it is completed.  
If the PASSU command supplied password does not match the hidden password in the Password Register, an  
error is reported by setting the P_ERR bit to 1. The WIP bit of the status register also remains set to 1. It is necessary  
to use the CLSR command to clear the status register, the RESET command to software reset the device, or drive  
the RESET# input LOW to initiate a hardware reset, in order to return the P_ERR and WIP bits to 0. This returns  
the device to standby state, ready for new commands such as a retry of the PASSU command.  
If the password does match, the PPB Lock bit is set to “1. The maximum clock frequency for the PASSU command  
is 133 MHz.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
Input Password High Byte  
Phase  
Instruction  
Input Password Low Byte  
Figure 99  
Password Unlock command sequence  
Datasheet  
130 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.9  
Reset Commands  
Software controlled Reset commands restore the device to its initial power up state, by reloading volatile  
registers from non-volatile default values. However, the volatile FREEZE bit in the Configuration register CR1V[0]  
and the volatile PPB Lock bit in the PPB Lock Register are not changed by a software reset. The software reset  
cannot be used to circumvent the FREEZE or PPB Lock bit protection mechanisms for the other security  
configuration bits.  
The Freeze bit and the PPB Lock bit will remain set at their last value prior to the software reset. To clear the  
FREEZE bit and set the PPB Lock bit to its protection mode selected power on state, a full power-on-reset  
sequence or hardware reset must be done.  
The non-volatile bits in the configuration register (CR1NV), TBPROT_O, TBPARM, and BPNV_O, retain their  
previous state after a Software Reset.  
The Block Protection bits BP2, BP1, and BP0, in the status register (SR1V) will only be reset to their default value  
if FREEZE = 0.  
A reset command (RST or RESET) is executed when CS# is brought HIGH at the end of the instruction and requires  
t
RPH time to execute.  
In the case of a previous Power-up Reset (POR) failure to complete, a reset command triggers a full power up  
sequence requiring tPU to complete.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 100  
Software Reset command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 101  
Software Reset command sequence QPI mode  
10.9.1  
Software Reset Enable (RSTEN 66h)  
The Reset Enable (RSTEN) command is required immediately before a Reset command (RST) such that a software  
reset is a sequence of the two commands. Any command other than RST following the RSTEN command, will  
clear the reset enable condition and prevent a later RST command from being recognized.  
10.9.2  
Software Reset (RST 99h)  
The Reset (RST) command immediately following a RSTEN command, initiates the software reset process.  
Datasheet  
131 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.9.3  
Legacy Software Reset (RESET F0h)  
The Legacy Software Reset (RESET) is a single command that initiates the software reset process. This command  
is disabled by default but can be enabled by programming CR3V[0] = 1, for software compatibility with Cypress  
legacy FL-S devices.  
10.9.4  
Mode Bit Reset (MBR FFh)  
The Mode Bit Reset (MBR) command is used to return the device from continuous high performance read mode  
back to normal standby awaiting any new command. Because some device packages lack a hardware RESET#  
input and a device that is in a continuous high performance read mode may not recognize any normal SPI  
command, a system hardware reset or software reset command may not be recognized by the device. It is  
recommended to use the MBR command after a system reset when the RESET# signal is not available or, before  
sending a software reset, to ensure the device is released from continuous high performance read mode.  
The MBR command sends Ones on SI or IO0 for 8 SCK cycles. IO1 to IO3 are “don’t care” during these cycles.  
CS#  
SCK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 102  
Mode Bit Reset command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 103  
Mode Bit Reset command sequence QPI mode  
Datasheet  
132 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.10  
DPD Commands  
10.10.1  
Enter Deep Power Down (DPD B9h)  
Although the standby current during normal operation is relatively low, standby current can be further reduced  
with the DPD command. The lower power consumption makes the DPD command especially useful for battery  
powered applications (see IDPD in “DC characteristics” on page 31).  
The DPD command is accepted only while the device is not performing an embedded algorithm as indicated by  
the Status Register-1 volatile Write In Progress (WIP) bit being cleared to zero (SR1V[0] = 0).  
The command is initiated by driving the CS# pin LOW and shifting the instruction code “B9h” as shown in  
Figure 104. The CS# pin must be driven HIGH after the eighth bit has been latched. If this is not done the Deep  
Power-down command will not be executed. After CS# is driven HIGH, the power-down state will be entered  
within the time duration of tDPD (“Timing specifications” on page 34).  
While in the power-down state only the Release from Deep Power-down command, which restores the device to  
normal operation, will be recognized. All other commands are ignored. This includes the Read Status Register  
command, which is always available during normal operation. Ignoring all but one command also makes the  
Power Down state useful for write protection. The device always powers-up in the interface standby state with  
the standby current of ICC1  
.
CS#  
SCLK  
SI  
7
6
5
4
3
2
1
0
SO  
Phase  
Instruction  
Figure 104  
Deep Power-down command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 105  
DPD command sequence QPI mode  
Datasheet  
133 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Commands  
10.10.2  
Release from Deep Power Down (RES ABh)  
The Release from Deep Power-down command is used to release the device from the deep power-down state. In  
some legacy SPI devices the RES command could also be used to obtain the device electronic identification (ID)  
number. However, the device ID function is not supported by the RES command.  
To release the device from the deep power-down state, the command is issued by driving the CS# pin LOW,  
shifting the instruction code “ABh” and driving CS# HIGH as shown in Figure 106. Release from deep power-down  
will take the time duration of tRES (“Timing specifications” on page 34) before the device will resume normal  
operation and other commands are accepted. The CS# pin must remain HIGH during the tRES time duration.  
Hardware Reset will also release the device from the DPD state as part of the hardware reset process.  
CS#  
SCLK  
SI  
SO  
7
6
5
4
3
2
1
0
Phase  
Instruction  
Figure 106  
Release from Deep Power-down command sequence  
This command is also supported in QPI Mode. In Quad AIl Mode, the instruction is shifted in on IO0–IO3, two clock  
cycles per byte.  
CS#  
SCLK  
IO0  
IO1  
4
5
6
7
0
1
2
3
IO2  
IO3  
Phase  
Instruction  
Figure 107  
RES command sequence QPI mode  
Datasheet  
134 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Data Integrity  
11  
Data Integrity  
11.1  
Erase Endurance  
Table 50  
Erase Endurance Industrial and Industrial Plus Temperature  
Parameter  
Minimum  
Unit  
Program/Erase cycles per main Flash array sectors  
Program/Erase cycles per PPB array or non-volatile register array[65]  
100K  
100K  
PE cycle  
PE cycle  
11.2  
Data Retention  
Table 51  
Data Retention Industrial and Industrial Plus Temperature  
Minimum  
Parameter  
Data Retention Time  
Test conditions  
10K Program/Erase Cycles  
100K Program/Erase Cycles  
Unit  
time  
20  
Years  
Years  
2
Contact Cypress Sales and FAE for further information on the data integrity. An application note is available at  
www.cypress.com/appnotes.  
Note  
65.Each write command to a non-volatile register causes a PE cycle on the entire non-volatile register array.  
OTP bits and registers internally reside in a separate array that is not cycled.  
Datasheet  
135 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Embedded Algorithm Performance Tables  
12  
Embedded Algorithm Performance Tables  
Table 52  
Program and Erase Performance  
Parameter  
Symbol  
Min  
Typ[66]  
Max  
Unit  
tW  
tPP  
tSE  
Non-volatile Register Write Time  
Page Programming (512Bytes)  
Page Programming (256Bytes)  
240  
475  
360  
750  
2000  
2000  
ms  
µs  
Sector Erase Time (256 KB physical sectors)  
Sector Erase Time (64 KB or 4 KB physical sectors)  
Bulk Erase Time (S25FS512S)  
930  
240  
220  
20  
2900  
725  
720  
25  
ms  
ms  
sec  
tBE  
Evaluate Erase Status Time (4 KB physical sectors)  
tEES  
µs  
Evaluate Erase Status Time (256 KB physical or logical  
sectors)  
80  
100  
Table 53  
Program or Erase Suspend AC Parameters  
Parameter  
Typical  
Max  
Unit  
Comments  
The time from Suspend command  
until the WIP bit is 0.  
Suspend Latency (tSL  
)
40  
µs  
Minimum is the time needed to  
issue the next Suspend command  
µs but typical periods are needed for  
Program or Erase to progress to  
completion.  
Resume to next Program Suspend (tRS  
)
100  
Notes  
66.Typical program and erase times assume the following conditions: 25 °C, VCC = 1.8 V; 10,000 cycles;  
checkerboard data pattern.  
67.The programming time for any OTP programming command is the same as tPP. This includes OTPP 42h,  
PNVDLR 43h, ASPP 2Fh, and PASSP E8h.  
68.The programming time for the PPBP E3h command is the same as tPP. The erase time for PPBE E4h command  
is the same as tSE  
.
Datasheet  
136 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
13  
Software Interface Reference  
13.1  
Serial Flash Discoverable Parameters (SFDP) Address Map  
The SFDP address space has a header starting at address zero that identifies the SFDP data structure and provides  
a pointer to each parameter. One parameter is mandated by the JEDEC JESD216 standard. Cypress provides an  
additional parameter by pointing to the ID-CFI address space i.e. the ID-CFI address space is a sub-set of the SFDP  
address space. The JEDEC parameter is located within the ID-CFI address space and is thus both a CFI parameter  
and an SFDP parameter. In this way both SFDP and ID-CFI information can be accessed by either the RSFDP or  
RDID commands.  
Table 54  
SFDP Overview Map  
Byte  
Description  
address  
0000h  
,,,  
1000h  
...  
Location zero within JEDEC JESD216B SFDP space - start of SFDP header  
Remainder of SFDP header followed by undefined space  
Location zero within ID-CFI space - start of ID-CFI parameter tables  
ID-CFI parameters  
Start of SFDP parameter tables which are also grouped as one of the CFI parameter tables  
(the CFI parameter itself starts at 108Eh, the SFDP parameter table data is double word aligned  
starting at 1090h)  
1090h  
...  
Remainder of SFDP parameter tables followed by either more CFI parameters or undefined space  
Datasheet  
137 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
13.1.1  
Field Definitions  
Table 55  
SFDP Header  
SFDP byte SFDPDword  
Data  
Description  
address  
name  
This is the entry point for Read SFDP (5Ah) command i.e. location zero  
00h  
53h  
within SFDP space  
ASCII “S”  
SFDP  
Header 1st  
DWORD  
01h  
02h  
03h  
46h  
44h  
50h  
ASCII “F”  
ASCII “D”  
ASCII “P”  
SFDP Minor Revision (06h = JEDEC JESD216 Revision B)  
This revision is backward compatible with all prior minor revisions.  
Minor revisions are changes that define previously reserved fields, add  
fields to the end, or that clarify definitions of existing fields.  
Increments of the minor revision value indicate that previously  
reserved parameter fields may have been assigned a new definition or  
entire Dwords may have been added to the parameter table. However,  
the definition of previously existing fields is unchanged and therefore  
remain backward compatible with earlier SFDP parameter table  
revisions. Software can safely ignore increments of the minor revision  
number, as long as only those parameters the software was designed  
to support are used i.e. previously reserved fields and additional  
Dwords must be masked or ignored. Do not do a simple compare on  
the minor revision number, looking only for a match with the revision  
number that the software is designed to handle. There is no problem  
with using a higher number minor revision.  
04h  
05h  
06h  
01h  
SFDP  
Header 2nd  
DWORD  
SFDP Major Revision  
This is the original major revision. This major revision is compatible  
with all SFDP reading and parsing software.  
06h  
07h  
08h  
05h  
FFh  
00h  
Number of Parameter Headers (zero based, 05h = 6 parameters)  
Unused  
Parameter ID LSB (00h = JEDEC SFDP Basic SPI Flash Parameter)  
Parameter Minor Revision (00h = JESD216)  
- This older revision parameter header is provided for any legacy SFDP  
reading and parsing software that requires seeing a minor revision 0  
parameter header. SFDP software designed to handle later minor  
revisions should continue reading parameter headers looking for a  
higher numbered minor revision that contains additional parameters  
for that software revision.  
09h  
00h  
Parameter  
Header  
0
1st DWORD  
Parameter Major Revision (01h = The original major revision - all SFDP  
software is compatible with this major revision.  
Parameter Table Length (in double words = Dwords = 4 byte units) 09h  
= 9 Dwords  
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned)  
JEDEC Basic SPI Flash parameter byte offset = 1090h  
Parameter Table Pointer Byte 1  
0Ah  
0Bh  
0Ch  
01h  
09h  
90h  
Parameter  
Header  
0
0Dh  
0Eh  
0Fh  
10h  
00h  
FFh  
Parameter Table Pointer Byte 2  
Parameter ID MSB (FFh = JEDEC defined legacy Parameter ID)  
2nd DWORD  
Datasheet  
138 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 55  
SFDP Header (Continued)  
SFDP byte SFDPDword  
Data  
Description  
address  
name  
10h  
00h  
Parameter ID LSB (00h = JEDEC SFDP Basic SPI Flash Parameter)  
Parameter Minor Revision (05h = JESD216 Revision A)  
- This older revision parameter header is provided for any legacy SFDP  
reading and parsing software that requires seeing a minor revision 5  
parameter header. SFDP software designed to handle later minor  
revisions should continue reading parameter headers looking for a  
later minor revision that contains additional parameters.  
Parameter Major Revision (01h = The original major revision - all SFDP  
software is compatible with this major revision.  
Parameter Table Length (in double words = Dwords = 4 byte units) 10h  
= 16 Dwords  
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned)  
JEDEC Basic SPI Flash parameter byte offset = 1090h address  
Parameter Table Pointer Byte 1  
Parameter Table Pointer Byte 2  
Parameter ID MSB (FFh = JEDEC defined Parameter)  
Parameter ID LSB (00h = JEDEC SFDP Basic SPI Flash Parameter)  
Parameter Minor Revision (06h = JESD216 Revision B)  
Parameter Major Revision (01h = The original major revision - all SFDP  
software is compatible with this major revision.  
11h  
05h  
Parameter  
Header  
1
1st DWORD  
12h  
13h  
14h  
01h  
10h  
90h  
Parameter  
Header  
1
15h  
16h  
17h  
18h  
19h  
10h  
00h  
FFh  
00h  
06h  
2nd DWORD  
Parameter  
Header  
2
1Ah  
1Bh  
1Ch  
01h  
10h  
90h  
1st DWORD  
Parameter Table Length (in double words = Dwords = 4 byte units) 10h  
= 16 Dwords  
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned)  
JEDEC Basic SPI Flash parameter byte offset = 1090h address  
Parameter Table Pointer Byte 1  
Parameter Table Pointer Byte 2  
Parameter  
Header  
2
1Dh  
1Eh  
1Fh  
20h  
10h  
00h  
FFh  
81h  
2nd DWORD  
Parameter ID MSB (FFh = JEDEC defined Parameter)  
Parameter ID LSB (81h = SFDP Sector Map Parameter)  
Parameter Minor Revision (00h = Initial version as defined in JESD216  
Revision B)  
Parameter Major Revision (01h = The original major revision - all SFDP  
software that recognizes this parameter’s ID is compatible with this  
major revision.  
Parameter Table Length (in double words = Dwords = 4 byte units)  
OPN Dependent  
14 = 0Eh (1Gb)  
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned)  
JEDEC parameter byte offset = 10D8h  
Parameter Table Pointer Byte 1  
Parameter Table Pointer Byte 2  
Parameter ID MSB (FFh = JEDEC defined Parameter)  
21h  
00h  
Parameter  
Header  
3
22h  
01h  
1st DWORD  
0Eh  
(01Gb)  
23h  
24h  
D8h  
Parameter  
Header  
3
25h  
26h  
27h  
10h  
00h  
FFh  
2nd DWORD  
Datasheet  
139 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 55  
SFDP Header (Continued)  
SFDP byte SFDPDword  
Data  
84h  
Description  
address  
name  
28h  
Parameter ID LSB (00h = SFDP 4 Byte Address Instructions Parameter)  
Parameter Minor Revision (00h = Initial version as defined in JESD216  
Revision B)  
Parameter Major Revision (01h = The original major revision - all SFDP  
software that recognizes this parameter’s ID is compatible with this  
major revision.  
29h  
00h  
Parameter  
Header  
4
2Ah  
01h  
1st DWORD  
Parameter Table Length (in double words = Dwords = 4 byte units) (2h  
= 2 Dwords)  
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned)  
JEDEC parameter byte offset = 10D0h  
Parameter Table Pointer Byte 1  
Parameter Table Pointer Byte 2  
2Bh  
2Ch  
02h  
D0h  
Parameter  
Header  
4
2Dh  
2Eh  
2Fh  
10h  
00h  
FFh  
2nd DWORD  
Parameter ID MSB (FFh = JEDEC defined Parameter)  
Parameter ID LSB (Cypress Vendor Specific ID-CFI parameter)  
Legacy Manufacturer ID 01h = AMD / Cypress  
Parameter Minor Revision (01h = ID-CFI updated with SFDP Rev B  
table)  
Parameter Major Revision (01h = The original major revision - all SFDP  
software that recognizes this parameter’s ID is compatible with this  
major revision.  
30h  
31h  
01h  
01h  
Parameter  
Header  
5
32h  
33h  
34h  
01h  
1st DWORD  
Parameter Table Length (in double words = Dwords = 4 byte units)  
44h (1Gb ) Parameter Table Length (in double words = Dwords = 4 byte units)  
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned)  
Entry point for ID-CFI parameter is byte offset = 1000h relative to SFDP  
location zero.  
Parameter Table Pointer Byte 1  
Parameter Table Pointer Byte 2  
00h  
Parameter  
Header  
5
35h  
36h  
37h  
10h  
00h  
01h  
2nd DWORD  
Parameter ID MSB (01h = JEDEC JEP106 Bank Number 1)  
Datasheet  
140 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
13.2  
Device ID and Common Flash Interface (ID-CFI) Address Map  
13.2.1  
Field Definitions  
Table 56  
Manufacturer and Device ID  
Data  
Byte  
Description  
Manufacturer ID for Cypress  
address  
00h  
01h  
01h  
02h (1 Gb)  
Device ID Most Significant Byte - Memory Interface Type  
02h  
03h  
Device ID Least Significant Byte - Density  
21h (1 Gb)  
ID-CFI Length - number bytes following. Adding this value to the  
current location of 03h gives the address of the last valid location  
in the ID-CFI legacy address map. The legacy CFI address map  
ends with the Primary Vendor-Specific Extended Query. The  
original legacy length is maintained for backward software  
compatibility. However, the CFI Query Identification String also  
includes a pointer to the Alternate Vendor-Specific Extended  
Query that contains additional information related to the FS-S  
family.  
4Dh  
Physical Sector Architecture  
The FS-S Family may be configured with or without 4 KB  
parameter sectors in addition to the uniform sectors.  
00h (Uniform 256 KB physical  
sectors)  
04h  
05h  
06h  
81h (FS-S Family)  
xxh  
Family ID  
ASCII characters for Model  
Refer to “Ordering Information” on page 166 for the model  
number definitions.  
07h  
08h  
xxh  
xxh  
Reserved  
09h  
0Ah  
0Bh  
0Ch  
0Dh  
0Eh  
0Fh  
xxh  
xxh  
xxh  
xxh  
xxh  
xxh  
xxh  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Reserved  
Datasheet  
141 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 57  
CFI Query Identification String  
Byte  
Data  
Description  
address  
10h  
11h  
12h  
51h  
52h  
59h  
Query Unique ASCII string “QRY”  
13h  
14h  
02h  
00h  
Primary OEM Command Set  
FL-P backward compatible command set ID  
15h  
16h  
40h  
00h  
Address for Primary Extended Table  
17h  
18h  
53h  
46h  
Alternate OEM Command Set  
Ascii characters “FS” for SPI (F) interface, S Technology  
19h  
1Ah  
51h  
00h  
Address for Alternate OEM Extended Table  
Table 58  
CFI System Interface String  
Data  
Byte  
Description  
address  
1Bh  
1Ch  
1Dh  
1Eh  
1Fh  
17h  
19h  
00h  
00h  
09h  
VCC Min. (erase/program): 100 millivolts BCD)  
V
V
V
CC Max. (erase/program): 100 millivolts BCD)  
PP Min. voltage (00h = no VPP present)  
PP Max. voltage (00h = no VPP present)  
Typical timeout per single byte program 2N µs  
Typical timeout for Min. size Page program 2N µs  
(00h = not supported)  
20h  
09h  
21h  
22h  
23h  
24h  
25h  
0Ah (256KB)  
Typical timeout per individual sector erase 2N ms  
Typical timeout for full chip erase 2N ms (00h = not supported)  
Max. timeout for byte program 2N times typical  
02h  
02h  
03h  
Max. timeout for page program 2N times typical  
Max. timeout per individual sector erase 2N times typical  
Max. timeout for full chip erase 2N times typical  
(00h = not supported)  
26h  
03h  
Datasheet  
142 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 59  
Device Geometry Definition for Bottom Boot Initial Delivery State  
Byte  
Data  
Description  
address  
27h  
28h  
1Bh (1 Gb)  
02h  
Device Size = 2N bytes;  
Flash Device Interface Description;  
0000h = x8 only  
0001h = x16 only  
0002h = x8/x16 capable  
0003h = x32 only  
29h  
01h  
0004h = Single I/O SPI, 3-byte address  
0005h = Multi I/O SPI, 3-byte address  
0102h = Multi I/O SPI, 3 or 4 byte address  
Max. number of bytes in multi-byte write = 2N  
0000h = not supported  
2Ah  
2Bh  
08h  
00h  
0008h = 256B page  
0009h = 512B page  
Number of Erase Block Regions within device  
1 = Uniform Device, >1 = Boot Device  
2Ch  
03h  
2Dh  
2Eh  
2Fh  
30h  
31h  
32h  
33h  
07h  
00h  
10h  
00h  
00h  
00h  
80h  
Erase Block Region 1 Information (refer to JEDEC JEP137)  
8 sectors = 8-1 = 0007h  
4 KB sectors = 256 Bytes x 0010h  
Erase Block Region 2 Information (refer to JEDEC JEP137)  
128Mb & 256Mb:  
1 sectors = 1-1 = 0000h  
32 KB sector = 256 Bytes x 0080h  
512Mb & 1 Gb:  
1 sectors = 1-1 = 0000h  
34h  
03h (1 Gb)  
224 KB sector = 256 Bytes x 0380h  
35h  
36h  
37h  
FEh  
01h (1 Gb)  
00h  
Erase Block Region 3 Information  
128Mb & 256Mb:  
255 sectors = 255-1 = 00FEh (128 Mb)  
511 sectors = 511-1 = 01FEh (256 Mb)  
64 KB sectors = 0100h x 256 Bytes  
512Mb:  
255 sectors = 255-1 = 00FEh  
256 KB sectors = 0400h x 256 Bytes  
1 Gb:  
38h  
04h (1 Gb)  
FFh  
511 sectors = 511-1 = 01FEh  
256 KB sectors = 0400h x 256 Bytes  
39h thru 3Fh  
RFU  
Note  
69.FS-S devices are user configurable to have either a hybrid sector architecture (with eight 4 KB sectors and  
all remaining sectors are uniform 64 KB or 256 KB) or a uniform sector architecture with all sectors uniform  
64 KB or 256 KB. FS-S devices are also user configurable to have the 4 KB parameter sectors at the top of  
memory address space. The CFI geometry information of the above table is relevant only to the initial  
delivery state. All devices are initially shipped from Cypress with the hybrid sector architecture with the  
4 KB sectors located at the bottom of the array address map. However, the device configuration TBPARM  
bit CR1NV[2] may be programed to invert the sector map to place the 4 KB sectors at the top of the array  
address map. The 20h_NV bit (CR3NV[3} may be programmed to remove the 4 KB sectors from the address  
map. The Flash device driver software must examine the TBPARM and 20h_NV bits to determine if the sector  
map was inverted or hybrid sectors removed at a later time.  
Datasheet  
143 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 60  
CFI Primary Vendor-Specific Extended Query  
Byte  
Data  
Description  
address  
40h  
41h  
42h  
43h  
44h  
50h  
52h  
49h  
31h  
33h  
Query-unique ASCII string “PRI”  
Major version number = 1, ASCII  
Minor version number = 3, ASCII  
Address Sensitive Unlock (Bits 1–0)  
00b = Required, 01b = Not Required  
Process Technology (Bits 5–2)  
0000b = 0.23 µm Floating Gate  
0001b = 0.17 µm Floating Gate  
0010b = 0.23 µm MIRRORBIT™  
0011b = 0.11 µm Floating Gate  
0100b = 0.11 µm MIRRORBIT™  
0101b = 0.09 µm MIRRORBIT™  
1000b = 0.065 µm MIRRORBIT™  
45h  
21h  
Erase Suspend  
46h  
47h  
48h  
02h  
01h  
00h  
0 = Not Supported, 1 = Read Only, 2 = Read & Program  
Sector Protect  
00 = Not Supported, X = Number of sectors in group  
Temporary Sector Unprotect  
00 = Not Supported, 01 = Supported  
Sector Protect/Unprotect Scheme  
04 = High Voltage Method  
05 = Software Command Locking Method  
08 = Advanced Sector Protection Method  
49h  
08h  
Simultaneous Operation  
4Ah  
4Bh  
00h  
01h  
00 = Not Supported, X = Number of Sectors  
Burst Mode (Synchronous sequential read) support  
00 = Not Supported, 01 = Supported  
Page Mode Type, initial delivery configuration, user configurable for 512B page  
00 = Not Supported, 01 = 4 Word Read Page, 02 = 8 Read Word Page, 03 = 256 Byte  
Program Page, 04 = 512 Byte Program Page  
4Ch  
03h  
ACC (Acceleration) Supply Minimum  
00 = Not Supported, 100 mV  
ACC (Acceleration) Supply Maximum  
00 = Not Supported, 100 mV  
4Dh  
4Eh  
00h  
00h  
WP# Protection  
01 = Whole Chip  
4Fh  
50h  
07h  
01h  
04 = Uniform Device with Bottom WP Protect  
05 = Uniform Device with Top WP Protect  
07 = Uniform Device with Top or Bottom Write Protect (user configurable)  
Program Suspend  
00 = Not Supported, 01 = Supported  
Datasheet  
144 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
The Alternate Vendor-Specific Extended Query provides information related to the expanded command set  
provided by the FS-S family. The alternate query parameters use a format in which each parameter begins with  
an identifier byte and a parameter length byte. Driver software can check each parameter ID and can use the  
length value to skip to the next parameter if the parameter is not needed or not recognized by the software.  
Table 61  
CFI Alternate Vendor-Specific Extended Query Header  
Byte  
Data  
Description  
address  
51h  
52h  
53h  
54h  
55h  
41h  
4Ch  
54h  
32h  
30h  
Query-unique ASCII string “ALT”  
Major version number = 2, ASCII  
Minor version number = 0, ASCII  
Table 62  
CFI Alternate Vendor-Specific Extended Query Parameter 0  
Parameter  
relative byte  
Data  
00h  
Description  
Parameter ID (Ordering Part Number)  
Parameter Length (The number of following bytes in this parameter. Adding  
this value to the current location value + 1 = the first byte of the next  
parameter)  
address offset  
00h  
01h  
10h  
02h  
03h  
04h  
05h  
06h  
07h  
08h  
09h  
0Ah  
0Bh  
0Ch  
0Dh  
0Eh  
53h  
32h  
35h  
46h  
53h  
Ascii “S” for manufacturer (Cypress)  
Ascii “25” for Product Characters (Single Die SPI)  
Ascii “FS” for Interface Characters (SPI 1.8Volt)  
30h (1 Gb)  
31h (1 Gb) Ascii characters for density  
47h (1 Gb)  
53h  
FFh  
FFh  
FFh  
FFh  
FFh  
Ascii “S” for Technology (65nm MirrorBit)  
Reserved for Future Use  
Reserved for Future Use  
Reserved for Future Use  
0Fh  
10h  
11h  
xxh  
xxh  
ASCII characters for Model  
Refer to “Ordering Information” on page 166 for the model number  
definitions.  
Datasheet  
145 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 63  
CFI Alternate Vendor-Specific Extended Query Parameter 80h Address options  
Parameter  
relative byte  
Data  
Description  
Parameter ID (Ordering Part Number)  
Parameter Length (The number of following bytes in this parameter. Adding this  
value to the current location value + 1 = the first byte of the next parameter)  
address offset  
00h  
80h  
01h  
01h  
Bits 7:5 - Reserved = 111b  
Bit 4 - Address Length Bit in CR2V[7] - Yes = 0b  
Bit 3 - AutoBoot support - No = 1b  
Bit 2 - 4 byte address instructions supported - Yes = 0b  
Bit 1 - Bank address + 3 byte address instructions supported - No = 1b  
Bit 0 - 3 byte address instructions supported - No = 1b  
02h  
EBh  
Table 64  
CFI Alternate Vendor-Specific Extended Query Parameter 84h Suspend commands  
Parameter  
relative byte  
Data  
Description  
Parameter ID (Suspend Commands  
Parameter Length (The number of following bytes in this parameter. Adding this  
value to the current location value + 1 = the first byte of the next parameter)  
address offset  
00h  
84h  
08h  
01h  
02h  
03h  
04h  
05h  
06h  
07h  
08h  
09h  
85h  
28h  
8Ah  
64h  
75h  
28h  
7Ah  
64h  
Program suspend instruction code  
Program suspend latency maximum (s)  
Program resume instruction code  
Program resume to next suspend typical (s)  
Erase suspend instruction code  
Erase suspend latency maximum (s)  
Erase resume instruction code  
Erase resume to next suspend typical (s)  
Table 65  
CFI Alternate Vendor-Specific Extended Query Parameter 88h Data Protection  
Parameter  
relative byte  
Data  
Description  
address offset  
00h  
88h  
04h  
Parameter ID (Data Protection)  
Parameter Length (The number of following bytes in this parameter. Adding this  
value to the current location value + 1 = the first byte of the next parameter)  
OTP size 2N bytes, FFh = not supported  
01h  
02h  
03h  
0Ah  
01h  
OTP address map format, 01h = FL-S and FS-S format, FFh = not supported  
Block Protect Type, model dependent  
00h = FL-P, FL-S, FS-S  
04h  
05h  
xxh  
xxh  
FFh = not supported  
Advanced Sector Protection type, model dependent  
01h = FL-S & FS-S ASP, 03h = FS-S ASP with Read Password Enabled.  
Datasheet  
146 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 66  
CFI Alternate Vendor-Specific Extended Query Parameter 8Ch Reset Timing  
Parameter  
relative byte  
Data  
Description  
address offset  
00h  
8Ch  
06h  
Parameter ID (Reset Timing)  
Parameter Length (The number of following bytes in this parameter. Adding this  
value to the current location value + 1 = the first byte of the next parameter)  
01h  
02h  
03h  
96h  
01h  
POR maximum value  
POR maximum exponent 2N s  
Hardware Reset maximum value, FFh = not supported (the initial delivery state  
has hardware reset disabled but it may be enabled by the user at a later time)  
04h  
23h  
05h  
06h  
07h  
00h  
23h  
00h  
Hardware Reset maximum exponent 2N s  
Software Reset maximum value, FFh = not supported  
Software Reset maximum exponent 2N s  
Table 67  
CFI Alternate Vendor-Specific Extended Query Parameter 94h ECC  
Parameter  
relative byte  
Data  
Description  
address offset  
00h  
01h  
02h  
94h  
01h  
10h  
Parameter ID (ECC)  
Parameter Length (The number of following bytes in this parameter. Adding this  
value to the current location value + 1 = the first byte of the next parameter)  
ECC unit size byte, FFh = ECC disabled  
Table 68  
CFI Alternate Vendor-Specific Extended Query Parameter F0h RFU  
Parameter  
relative byte  
Data  
Description  
address offset  
00h  
F0h  
09h  
Parameter ID (RFU)  
Parameter Length (The number of following bytes in this parameter. Adding this  
value to the current location value + 1 = the first byte of the next parameter)  
01h  
02h  
...  
0Ah  
FFh  
FFh  
FFh  
RFU  
RFU  
RFU  
This parameter type (Parameter ID F0h) may appear multiple times and have a different length each time. The  
parameter is used to reserve space in the ID-CFI map or to force space (pad) to align a following parameter to a  
required boundary.  
Datasheet  
147 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
13.2.1.1  
JEDEC SFDP Rev B Parameter Tables  
From the view point of the CFI data structure, all of the SFDP parameter tables are combined into a single CFI  
Parameter as a contiguous byte sequence.  
From the viewpoint of the SFDP data structure, there are three independent parameter tables. Two of the tables  
have a fixed length and one table has a variable structure and length depending on the device density Ordering  
Part Number (OPN). The Basic Flash Parameter table and the 4-Byte Address Instructions Parameter table have  
a fixed length and are presented below as a single table. This table is section 1 of the overall CFI parameter.  
The JEDEC Sector Map Parameter table structure and length depends on the density OPN and is presented as a  
set of tables, one for each device density.  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
00h  
01h  
--  
--  
N/A  
N/A  
A5h  
CFI Parameter ID (JEDEC SFDP)  
CFI Parameter Length (The number of following  
bytes in this parameter. Adding this value to the  
80h (1Gb)h current location value + 1 = the first byte of the next  
parameter). OPN dependent:  
18Dw + 14Dw = 32Dw * 4B = 128B = 80h B (1Gb)  
Start of SFDP JEDEC parameter, located at 1090h in  
the overall SFDP address space.  
Bits 7:5 = unused = 111b  
02h  
03h  
00h  
01h  
E7h  
FFh  
Bit 4:3 = 06h is status register write instruction &  
status register is default non-volatile = 00b  
Bit 2 = Program Buffer > 64Bytes = 1  
Bits 1:0 = Uniform 4 KB erase unavailable = 11b  
Bits 15:8 = Uniform 4 KB erase opcode = not  
supported = FFh  
JEDEC Basic  
Flash  
Parameter  
Dword-1  
Bit 23 = Unused = 1b  
Bit 22 = Supports Quad Out Read = No = 0b  
Bit 21 = Supports Quad I/O Read = Yes =1b  
Bit 20 = Supports Dual I/O Read = Yes = 1b  
Bit19 = Supports DDR 0= No, 1 = Yes; FS-SAG = 0b,  
FS-SDS = 1b  
04h  
02h  
BAh  
(FSxxxSDS)  
Bit 18:17 = Number of Address Bytes, 3 or 4 = 01b  
Bit 16 = Supports Dual Out Read = No = 0b  
05h  
06h  
07h  
08h  
09h  
03h  
04h  
05h  
06h  
07h  
FFh  
FFh  
FFh  
Bits 31:24 = Unused = FFh  
JEDEC Basic  
Flash  
Parameter  
Dword-2  
Density in bits, zero based, 512 Mb = 1FFFFFFFh  
FFh  
3Fh (1 Gb)  
Datasheet  
148 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
Bits 7:5 = number of Quad I/O (1-4-4) Mode cycles =  
010b  
0Ah  
0Bh  
0Ch  
08h  
09h  
0Ah  
48h  
EBh  
FFh  
Bits 4:0 = number of Quad I/O Dummy cycles = 01000b  
(Initial Delivery State)  
JEDEC Basic  
Flash  
Parameter  
Dword-3  
Quad I/O instruction code  
Bits 23:21 = number of Quad Out (1-1-4) Mode cycles  
= 111b  
Bits 20:16 = number of Quad Out Dummy cycles =  
11111b  
0Dh  
0Eh  
0Fh  
0Bh  
0Ch  
0Dh  
FFh  
FFh  
FFh  
Quad Out instruction code  
Bits 7:5 = number of Dual Out (1-1-2) Mode cycles =  
111b  
Bits 4:0 = number of Dual Out Dummy cycles = 11111b  
JEDEC Basic  
Flash  
Dual Out instruction code  
Bits 23:21 = number of Dual I/O (1-2-2) Mode cycles =  
100b  
Bits 20:16 = number of Dual I/O Dummy cycles =  
01000b (Initial Delivery State)  
Parameter  
Dword-4  
10h  
11h  
12h  
0Eh  
0Fh  
10h  
88h  
BBh  
FEh  
Dual I/O instruction code  
Bits 7:5 RFU = 111b  
Bit 4 = QPI supported = Yes = 1b  
Bits 3:1 RFU = 111b  
JEDEC Basic  
Flash  
Parameter  
Dword-5  
Bit 0 = Dual All not supported = 0b  
13h  
14h  
15h  
16h  
17h  
11h  
12h  
13h  
14h  
15h  
FFh  
FFh  
FFh  
FFh  
FFh  
Bits 15:8 = RFU = FFh  
Bits 23:16 = RFU = FFh  
Bits 31:24 = RFU = FFh  
Bits 7:0 = RFU = FFh  
Bits 15:8 = RFU = FFh  
Bits 23:21 = number of Dual All Mode cycles = 111b  
Bits 20:16 = number of Dual All Dummy cycles =  
11111b  
JEDEC Basic  
Flash  
Parameter  
Dword-6  
18h  
16h  
FFh  
19h  
1Ah  
1Bh  
17h  
18h  
19h  
FFh  
FFh  
FFh  
Dual All instruction code  
Bits 7:0 = RFU = FFh  
Bits 15:8 = RFU = FFh  
Bits 23:21 = number of QPI Mode cycles = 010b  
Bits 20:16 = number of QPI Dummy cycles = 01000b  
JEDEC Basic  
Flash  
Parameter  
Dword-7  
1Ch  
1Dh  
1Ah  
1Bh  
48h  
EBh  
QPI Mode Quad I/O (4-4-4) instruction code  
Datasheet  
149 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
Erase type 1 size 2N Bytes = 4 KB = 0Ch for Hybrid  
(Initial Delivery State)  
Erase type 1 instruction  
Erase type 2 size 2N Bytes = 64 KB = 10h  
Erase type 2 instruction  
Erase type 3 size 2N Bytes = 256 KB = 12h  
Erase type 3 instruction  
Erase type 4 size 2N Bytes = not supported = 00h  
Erase type 4 instruction = not supported = FFh  
Bits 31:30 = Erase type 4 Erase, Typical time units  
(00b: 1 ms, 01b: 16 ms, 10b: 128 ms, 11b: 1 s) = 1S =  
11b (RFU)  
Bits 29:25 = Erase type 4 Erase, Typical time count =  
11111b ( RFU)  
1Eh  
1Ch  
0Ch  
JEDEC Basic  
Flash  
1Fh  
20h  
21h  
22h  
23h  
24h  
25h  
26h  
27h  
28h  
1Dh  
1Eh  
1Fh  
20h  
21h  
22h  
23h  
24h  
25h  
26h  
20h  
10h  
D8h  
12h  
D8h  
00h  
FFh  
82h  
42h  
11h  
Parameter  
Dword-8  
JEDEC Basic  
Flash  
Parameter  
Dword-9  
Bits 24:23 = Erase type 3 Erase, Typical time units  
(00b: 1 ms, 01b: 16 ms, 10b: 128 ms, 11b: 1 s) = 128 ms  
= 10b  
Bits 22:18 = Erase type 3 Erase, Typical time count =  
00100b (typ erase time = count + 1 * units = 5 * 128 ms  
= 640 ms)  
Bits 17:16 = Erase type 2 Erase, Typical time units  
(00b: 1 ms, 01b: 16 ms, 10b: 128 ms, 11b: 1 s) = 16 ms  
= 01b  
Bits 15:11 = Erase type 2 Erase, Typical time count =  
01000b (typ erase time = count + 1 * units = 9 * 16 ms =  
144 ms)  
Bits 10:9 = Erase type 1 Erase, Typical time units (00b:  
1 ms, 01b: 16 ms, 10b: 128 ms, 11b: 1 s) = 16 ms = 01b  
Bits 8:4 = Erase type 1 Erase, Typical time count =  
01000b (typ erase time = count + 1 * units = 9 * 16 ms  
= 144 ms)  
JEDEC Basic  
Flash  
Parameter  
Dword-10  
29h  
27h  
FFh  
Bits 3:0 = Multiplier from typical erase time to  
maximum erase time = 2 * (N + 1), N = 2h = 6x  
multiplier  
Binary Fields:  
11-11111-10-00100-01-01000-01-01000-0010  
Nibble Format:  
1111_1111_0001_0001_0100_0010_1000_0010  
Hex Format: FF_11_42_82  
Datasheet  
150 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
2Ah  
2Bh  
2Ch  
28h  
29h  
2Ah  
91h  
26h  
07h  
Bit 31 Reserved = 1b  
Bits 30:29 = Chip Erase, Typical time units (00b: 16 ms,  
01b: 256 ms, 10b: 4 s, 11b: 64 s) = 1Gb chip erase not  
supported, BEA command erases upper or lower  
512 Mb  
Bits 28:24 = Chip Erase, Typical time count,  
(count + 1) * units,  
1Gb chip erase not supported, BEA command erases  
upper or lower 512 Mb  
Bits 23 = Byte Program Typical time, additional byte  
units (0b:1 µs, 1b:8 µs) = 1 µs = 0b  
Bits 22:19 = Byte Program Typical time, additional  
byte count, (count + 1) * units, count = 0000b, (typ  
Program time = count + 1 * units = 1 * 1 µs = 1 µs  
Bits 18 = Byte Program Typical time, first byte units  
(0b:1 µs, 1b:8 µs) = 8 µs = 1b  
Bits 17:14 = Byte Program Typical time, first byte  
count, (count + 1) * units, count = 1100b, (typ  
Program time = count + 1 * units = 13 * 8 µs = 104 µs)  
Bits 13 = Page Program Typical time units (0b:8 µs,  
1b:64 µs) = 64 µs = 1b  
Bits 12:8 = Page Program Typical time count,  
(count + 1) * units, count = 00110b, (typ Program time  
= count + 1 * units = 7 * 64 µs = 448 µs)  
Bits 7:4 = Page size 2N, N = 9h, = 512B page  
Bits 3:0 = Multiplier from typical time to maximum for  
Page or Byte program = 2 * (N + 1), N = 1h = 4x  
multiplier  
JEDEC Basic  
Flash  
Parameter  
Dword-11  
2Dh  
2Bh  
E2h (1 Gb)  
128 Mb  
Binary Fields:  
1-10-01000-0-0000-1-1100-1-00110-1001-0001  
Nibble Format:  
1100_1000_0000_0111_0010_0110_1001_0001  
Hex Format: C8_07_26_91  
256 Mb  
Binary Fields:  
1-10-10001-0-0000-1-1100-1-00110-1001-0001  
Nibble Format:  
1101_0001_0000_0111_0010_0110_1001_0001  
Hex Format: D1_07_26_91  
512 Mb  
Binary Fields:  
1-11-00010-0-0000-1-1100-1-00110-1001-0001  
Nibble Format:  
1110_0010_0000_0111_0010_0110_1001_0001  
Hex Format: E2_07_26_91  
Datasheet  
151 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
2Eh  
2Fh  
30h  
2Ch  
2Dh  
2Eh  
ECh  
83h  
18h  
Bit 31 = Suspend and Resume supported = 0b  
Bits 30:29 = Suspend in-progress erase max latency  
units (00b: 128 ns, 01b: 1 µs, 10b: 8 µs, 11b: 64 µs) =  
8 µs = 10b  
Bits 28:24 = Suspend in-progress erase max latency  
count = 00100b, max erase suspend latency = count +  
1 * units = 5 * 8 µs = 40 µs  
Bits 23:20 = Erase resume to suspend interval count =  
0001b, interval = count + 1 * 64 µs = 2 * 64 µs = 128 µs  
Bits 19:18 = Suspend in-progress program max  
latency units (00b: 128 ns, 01b: 1 µs, 10b: 8 µs,  
11b: 64 µs) = 8 µs = 10b  
Bits 17:13 = Suspend in-progress program max  
latency count = 00100b, max erase suspend latency =  
count + 1 * units = 5 * 8 µs = 40 µs  
Bits 12:9 = Program resume to suspend interval count  
= 0001b, interval = count + 1 * 64 µs = 2 * 64 µs = 128 µs  
Bit 8 = RFU = 1b  
Bits 7:4 = Prohibited operations during erase suspend  
= xxx0b: May not initiate a new erase anywhere (erase  
nesting not permitted)  
JEDEC Basic  
Flash  
Parameter  
Dword-12  
+ xx1xb: May not initiate a page program in the erase  
suspended sector size  
+ x1xxb: May not initiate a read in the erase  
suspended sector size  
31h  
2Fh  
44h  
+ 1xxxb: The erase and program restrictions in bits 5:4  
are sufficient  
= 1110b  
Bits 3:0 = Prohibited Operations During Program  
Suspend  
= xxx0b: May not initiate a new erase anywhere (erase  
nesting not permitted)  
+ xx0xb: May not initiate a new page program  
anywhere (program nesting not permitted)  
+ x1xxb: May not initiate a read in the program  
suspended page size  
+ 1xxxb: The erase and program restrictions in bits 1:0  
are sufficient  
= 1100b  
Binary Fields:  
0-10-00100-0001-10-00100-0001-1-1110-1100  
Nibble Format:  
0100_0100_0001_1000_1000_0011_1110_1100  
Hex Format: 44_18_83_EC  
Datasheet  
152 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
32h  
33h  
34h  
35h  
36h  
37h  
38h  
30h  
31h  
32h  
33h  
34h  
35h  
36h  
8Ah  
85h  
7Ah  
75h  
F7h  
BDh  
D5h  
JEDEC Basic  
Flash  
Parameter  
Dword-13  
Bits 31:24 = Erase Suspend Instruction = 75h  
Bits 23:16 = Erase Resume Instruction = 7Ah  
Bits 15:8 = Program Suspend Instruction = 85h  
Bits 7:0 = Program Resume Instruction = 8Ah  
Bit 31 = Deep Power Down Supported = supported = 0  
Bits 30:23 = Enter Deep Power Down Instruction = B9h  
Bits 22:15 = Exit Deep Power Down Instruction = ABh  
Bits 14:13 = Exit Deep Power Down to next operation  
delay units = (00b: 128 ns, 01b: 1 µs, 10b: 8 µs,  
11b: 64 µs) = 1 µs = 01b  
Bits 12:8 = Exit Deep Power Down to next operation  
delay count = 11101b, Exit Deep Power Down to next  
operation delay = (count + 1) * units = 29 + 1 * 1 µs =  
30 µs  
JEDEC Basic  
Flash  
Parameter  
Dword-14  
Bits 7:4 = RFU = Fh  
Bit 3:2 = Status Register Polling Device Busy  
= 01b: Legacy status polling supported = Use legacy  
polling by reading the Status Register with 05h  
instruction and checking WIP bit[0] (0=ready;  
1=busy).  
= 01b  
Bits 1:0 = RFU = 11b  
39h  
37h  
5Ch  
Binary Fields:  
0-10111001-10101011-01-11101-1111-01-11  
Nibble Format:  
0101_1100_1101_0101_1011_1101_1111_0111  
Hex Format: 5C_D5_BD_F7  
Datasheet  
153 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
3Ah  
3Bh  
3Ch  
38h  
39h  
3Ah  
8Ch  
F6h  
5Dh  
Bits 31:24 = RFU = FFh  
Bit 23 = Hold and WP Disable = not supported = 0b  
Bits 22:20 = Quad Enable Requirements  
= 101b: QE is bit 1 of the status register 2. Status  
register 1 is read using Read Status instruction 05h.  
Status register 2 is read using instruction 35h. QE is  
set via Write Status instruction 01h with two data  
bytes where bit 1 of the second byte is one. It is  
cleared via Write Status with two data bytes where bit  
1 of the second byte is zero.  
Bits 19:16 0-4-4 Mode Entry Method  
= xxx1b: Mode Bits[7:0] = A5h Note: QE must be set  
prior to using this mode  
+ x1xxb: Mode Bit[7:0]=Axh  
+ 1xxxb: RFU  
= 1101b  
Bits 15:10 0-4-4 Mode Exit Method  
= xx_xxx1b: Mode Bits[7:0] = 00h will terminate this  
mode at the end of the current read operation  
+ xx_1xxxb: Input Fh (mode bit reset) on DQ0–DQ3 for  
8 clocks. This will terminate the mode prior to the  
next read operation.  
JEDEC Basic  
Flash  
Parameter  
Dword-15  
+ x1_xxxxb: Mode Bit[7:0] != Axh  
+ 1x_x1xx: RFU  
= 11_1101  
Bit 9 = 0-4-4 mode supported = 1  
3Dh  
3Bh  
FFh  
Bits 8:4 = 4-4-4 mode enable sequences  
= x_1xxxb: device uses a read-modify-write sequence  
of operations: read configuration using instruction  
65h followed by address 800003h, set bit 6, write  
configuration using instruction 71h followed by  
address 800003h. This configuration is volatile.  
= 01000b  
Bits 3:0 = 4-4-4 mode disable sequences  
= x1xxb: device uses a read-modify-write sequence of  
operations: read configuration using instruction 65h  
followed by address 800003h, clear bit 6, write  
configuration using instruction 71h followed by  
address 800003h.. This configuration is volatile.  
+ 1xxxb: issue the Soft Reset 66/99 sequence  
= 1100b  
Binary Fields:  
11111111-0-101-1101-111101-1-01000-1100  
Nibble Format:  
1111_1111_0101_1101_1111_0110_1000-1100  
Hex Format: FF_5D_F6_8C  
Datasheet  
154 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
3Eh  
3Fh  
40h  
3Ch  
3Dh  
3Eh  
F0h  
30h  
F8h  
Bits 31:24 = Enter 4-Byte Addressing  
= xxxx_xxx1b: issue instruction B7h (preceding write  
enable not required)  
+ xx1x_xxxxb: Supports dedicated 4-Byte address  
instruction set. Consult vendor data sheet for the  
instruction set definition.  
+ 1xxx_xxxxb: Reserved  
= 10100001b  
Bits 23:14 = Exit 4-Byte Addressing  
= xx_xx1x_xxxxb: Hardware reset  
+ xx_x1xx_xxxxb: Software reset (see bits 13:8 in this  
DWORD)  
+ xx_1xxx_xxxxb: Power cycle  
+ x1_xxxx_xxxxb: Reserved  
+ 1x_xxxx_xxxxb: Reserved  
= 11_1110_0000b  
Bits 13:8 = Soft Reset and Rescue Sequence Support  
= x1_xxxxb: issue reset enable instruction 66h, then  
issue reset instruction 99h. The reset enable, reset  
sequence may be issued on 1, 2, or 4 wires depending  
on the device operating mode.  
+ 1x_xxxxb: exit 0-4-4 mode is required prior to other  
reset sequences above if the device may be operating  
in this mode.  
= 110000b  
Bit 7 = RFU = 1  
JEDEC Basic  
Flash  
Parameter  
Dword-16  
41h  
3Fh  
A1h  
Bits 6:0 = Volatile or Non-Volatile Register and Write  
Enable Instruction for Status Register 1  
= + xx1_xxxxb: Status Register 1 contains a mix of  
volatile and non-volatile bits. The 06h instruction is  
used to enable writing of the register.  
+ x1x_xxxxb: Reserved  
+ 1xx_xxxxb: Reserved  
= 1110000b  
Binary Fields:  
10100001-1111100000-110000-1-1110000  
Nibble Format:  
1010_0001_1111_1000_0011_0000_1111_0000  
Hex Format: A1_F8_30_F0  
Datasheet  
155 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 69  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h JEDEC SFDP Rev B, Section 1,  
Basic Flash Parameter and 4 Byte Address Instructions Parameter (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
42h  
43h  
44h  
40h  
41h  
42h  
6Bh  
8Eh  
FFh  
Supported = 1, Not Supported = 0  
Bits 31:20 = RFU = FFFh  
Bit 19 = Support for non-volatile individual sector  
lock write command, Instruction = E3h = 1  
Bit 18 = Support for non-volatile individual sector  
lock read command, Instruction = E2h = 1  
Bit 17 = Support for volatile individual sector lock  
Write command, Instruction = E1h = 1  
Bit 16 = Support for volatile individual sector lock  
Read command, Instruction = E0h = 1  
Bit 15 = Support for (1-4-4) DTR_Read Command,  
Instruction = EEh = 1  
Bit 14 = Support for (1-2-2) DTR_Read Command,  
Instruction = BEh = 0  
Bit 13 = Support for (1-1-1) DTR_Read Command,  
Instruction = 0Eh = 0  
Bit 12 = Support for Erase Command – Type 4 = 0  
Bit 11 = Support for Erase Command – Type 3 = 1  
Bit 10 = Support for Erase Command – Type 2 = 1  
Bit 9 = Support for Erase Command – Type 1 = 1  
Bit 8 = Support for (1-4-4) Page Program Command,  
Instruction = 3Eh = 0  
JEDEC4Byte  
Address  
Instructions  
Parameter  
Dword-1  
45h  
43h  
FFh  
Bit 7 = Support for (1-1-4) Page Program Command,  
Instruction = 34h = 0  
Bit 6 = Support for (1-1-1) Page Program Command,  
Instruction = 12h = 1  
Bit 5 = Support for (1-4-4) FAST_READ Command,  
Instruction = ECh = 1  
Bit 4 = Support for (1-1-4) FAST_READ Command,  
Instruction = 6Ch = 0  
Bit 3 = Support for (1-2-2) FAST_READ Command,  
Instruction = BCh = 1  
Bit 2 = Support for (1-1-2) FAST_READ Command,  
Instruction = 3Ch = 0  
Bit 1 = Support for (1-1-1) FAST_READ Command,  
Instruction = 0Ch = 1  
Bit 0 = Support for (1-1-1) READ Command,  
Instruction = 13h = 1  
46h  
47h  
48h  
49h  
44h  
45h  
46h  
47h  
21h  
DCh  
DCh  
FFh  
JEDEC4Byte  
Address  
Instructions  
Parameter  
Dword-2  
Bits 31:24 = FFh = Instruction for Erase Type 4: RFU  
Bits 23:16 = DCh = Instruction for Erase Type 3  
Bits 15:8 = DCh = Instruction for Erase Type 2  
Bits 7:0 = 21h = Instruction for Erase Type 1  
Datasheet  
156 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Sector Map Parameter Table Notes:  
The following Sector Map Parameter Table provides a means to identify how the device address map is  
configured and provides a sector map for each supported configuration. This is done by defining a sequence of  
commands to read out the relevant configuration register bits that affect the selection of an address map. When  
more than one configuration bit must be read, all the bits are concatenated into an index value that is used to  
select the current address map.  
To identify the sector map configuration in FS01GS the following configuration bits are read in the following MSB  
to LSB order to form the configuration map index value:  
• Low address FS512S device CR3NV[3] - 0 = Hybrid Architecture, 1 = Uniform Architecture  
• High address FS512S device CR3NV[3] - 0 = Hybrid Architecture, 1 = Uniform Architecture  
The value of some configuration bits may make other configuration bit values not relevant (don’t care), hence  
not all possible combinations of the index value define valid address maps. Only selected configuration bit  
combinations (see Table 70) are supported by the SFDP Sector Map Parameter Table (see Table 71). Other  
combinations must not be used in configuring the sector address map when using the SFDP Sector Map  
Parameter Table (see Table 71) to determine the sector map. The following index value combinations are  
supported.  
Table 70  
Device  
Allowed Sector Configurations  
Low  
High  
Index  
value  
address  
CR3NV[3]  
address  
CR3NV[3]  
Description  
0
1
1
1
0
1
01h  
02h  
03h  
4 KB sectors at bottom with remainder 256 KB sectors  
4 KB sectors at top with remainder 256 KB sectors  
Uniform 256 KB sectors  
FS01GS  
Datasheet  
157 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 71  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B, Section  
2, Sector Map Parameter Table, 1Gb  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
4Ah  
4Bh  
4Ch  
48h  
49h  
4Ah  
FCh  
65h  
FFh  
Read lower address FS512S configuration. Note that only  
the lower or the upper address FS512S device may have  
parameter sectors. All other sectors are 256 KB.  
Bits 31:24 = Read data mask = 0000_1000b: Select bit 3 of  
the data byte for 20h_NV value  
0 = Hybrid map with 4 KB parameter sectors  
1 = Uniform map  
JEDEC  
Sector Map  
Parameter  
Dword-1  
Config.  
Bits 23:22 = Configuration detection command address  
length = 11b: Variable length  
Bits 21:20 = RFU = 11b  
Bits 19:16 = Configuration detection command latency =  
1111b: variable latency  
4Dh  
4Bh  
08h  
Detect-1  
Bits 15:8 = Configuration detection instruction = 65h:  
Read any register  
Bits 7:2 = RFU = 111111b  
Bit 1 = Command Descriptor = 0  
Bit 0 = not the end descriptor = 0  
4Eh  
4Fh  
50h  
4Ch  
4Dh  
4Eh  
JEDEC  
Sector Map  
Parameter  
Dword-2  
Config.  
04h  
00h  
00h  
Bits 31:0 = Sector map configuration detection command  
address = 00_00_00_04h: address of CR3NV  
51h  
4Fh  
00h  
Detect-1  
52h  
53h  
54h  
50h  
51h  
52h  
FCh  
65h  
FFh  
Read upper address FS512S configuration. Note that only  
the lower or the upper address FS512S device may have  
parameter sectors. All other sectors are 256 KB.  
Bits 31:24 = Read data mask = 0000_1000b: Select bit 3 of  
the data byte for 20h_NV value  
0 = Hybrid map with 4 KB parameter sectors  
1 = Uniform map  
JEDEC  
Sector Map  
Parameter  
Dword-3  
Config.  
Bits 23:22 = Configuration detection command address  
length = 11b: Variable length  
Bits 21:20 = RFU = 11b  
Bits 19:16 = Configuration detection command latency =  
1111b: variable latency  
55h  
53h  
08h  
Detect-2  
Bits 15:8 = Configuration detection instruction = 65h:  
Read any register  
Bits 7:2 = RFU = 111111b  
Bit 1 = Command Descriptor = 0  
Bit 0 = not the end descriptor = 0  
56h  
57h  
58h  
54h  
55h  
56h  
JEDEC  
Sector Map  
Parameter  
Dword-4  
Config.  
04h  
00h  
00h  
Bits 31:0 = Sector map configuration detection command  
address = 04_00_00_04h: address of CR3NV with A26  
selecting the higher address device.  
59h  
57h  
04h  
Detect-2  
Datasheet  
158 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 71  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B, Section  
2, Sector Map Parameter Table, 1Gb (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
5Ah  
5Bh  
5Ch  
58h  
59h  
5Ah  
FEh  
01h  
02h  
Bits 31:24 = RFU = FFh  
JEDEC  
Sector Map  
Parameter  
Dword-5  
Config-1  
Header  
Bits 23:16 = Region count (Dwords -1) = 02h: Three regions  
Bits 15:8 = Configuration ID = 01h: 4 KB sectors at bottom  
with remainder 256 KB sectors  
Bits 7:2 = RFU = 111111b  
Bit 1 = Map Descriptor = 1  
5Dh  
5Bh  
FFh  
Bit 0 = not the end descriptor = 0  
5Eh  
5Fh  
60h  
5Ch  
5Dh  
5Eh  
F1h  
7Fh  
00h  
Bits 31:8 = Region size = 00007Fh:  
Region size as count – 1 of 256 Byte units = 8 x 4 KB sectors  
= 32 KB  
Count = 32 KB/256 = 128, value = count – 1 = 128 – 1 = 127  
= 7Fh  
Bits 7:4 = RFU = Fh  
JEDEC  
Sector Map  
Parameter  
Dword-6  
Config-1  
Erase Type not supported = 0/ supported = 1  
Bit 3 = Erase Type 4 support = 0b  
--- Erase Type 4 is not defined  
Bit 2 = Erase Type 3 support = 0b  
--- Erase Type 3 is 256 KB erase and is supported in the  
4 KB sector region  
61h  
5Fh  
00h  
Region-0  
Bit 1 = Erase Type 2 support = 0b  
--- Erase Type 2 is 64 KB erase and is not supported in the  
4 KB sector region  
Bit 0 = Erase Type 1 support = 1b  
--- Erase Type 1 is 4 KB erase and is supported in the 4 KB  
sector region  
62h  
63h  
64h  
60h  
61h  
62h  
F4h  
7Fh  
03h  
Bits 31:8 = Region size = 00037Fh:  
Region size as count – 1 of 256 Byte units = 1 x 224 KB  
sectors = 224 KB  
Count = 224 KB/256 = 896, value = count – 1 = 896 – 1 = 895  
= 37Fh  
Bits 7:4 = RFU = Fh  
JEDEC  
Sector Map  
Parameter  
Dword-7  
Config-1  
Erase Type not supported = 0/ supported = 1  
Bit 3 = Erase Type 4 support = 0b  
--- Erase Type 4 is not defined  
Bit 2 = Erase Type 3 support = 1b  
--- Erase Type 3 is 256 KB erase and is supported in the  
32 KB sector region  
65h  
63h  
00h  
Region-1  
Bit 1 = Erase Type 2 support = 0b  
--- Erase Type 2 is 64 KB erase and is not supported in the  
32 KB sector region  
Bit 0 = Erase Type 1 support = 0b  
--- Erase Type 1 is 4 KB erase and is not supported in the  
32 KB sector region  
Datasheet  
159 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 71  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B, Section  
2, Sector Map Parameter Table, 1Gb (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
66h  
67h  
68h  
64h  
65h  
66h  
F4h  
FFh  
FBh  
Bits 31:8 = 1Gb device Region size = 07FBFFh:  
Region size as count – 1 of 256 Byte units = 511 x 256 KB  
sectors = 130816 KB  
Count = 130816 KB/256 = 523264, value = count – 1 =  
523264 – 1 = 523263 = 7FBFFh  
Bits 7:4 = RFU = Fh  
JEDEC  
Sector Map  
Parameter  
Dword-8  
Config-1  
Erase Type not supported = 0 / supported = 1  
Bit 3 = Erase Type 4 support = 0b  
--- Erase Type 4 is not defined  
Bit 2 = Erase Type 3 support = 1b  
--- Erase Type 3 is 256 KB erase and is supported in the 64  
KB sector region  
07h  
(1Gb)  
69h  
67h  
Region-2  
Bit 1 = Erase Type 2 support = 0b  
--- Erase Type 2 is 64 KB erase and is not supported in the  
64 KB sector region  
Bit 0 = Erase Type 1 support = 0b  
--- Erase Type 1 is 4 KB erase and is not supported in the  
64 KB sector region  
6Ah  
6Bh  
6Ch  
68h  
69h  
6Ah  
FEh  
02h  
02h  
Bits 31:24 = RFU = FFh  
JEDEC  
Sector Map  
Parameter  
Dword-9  
Config-2  
Header  
Bits 23:16 = Region count (Dwords – 1) = 02h: Three  
regions  
Bits 15:8 = Configuration ID = 02h: 4 KB sectors at top with  
remainder 256 KB sectors  
Bits 7:2 = RFU = 111111b  
6Dh  
6Bh  
FFh  
Bit 1 = Map Descriptor = 1  
Bit 0 = not the end descriptor = 0  
6Eh  
6Fh  
70h  
6Ch  
6Dh  
6Eh  
F4h  
FFh  
FBh  
Bits 31:8 = 1Gb device Region size = 07FBFFh:  
Region size as count-1 of 256 Byte units = 511 x 256 KB  
sectors = 130816 KB  
Count = 130816 KB/256 = 523264, value = count – 1 =  
523264 – 1 = 523263 = 7FBFFh  
Bits 7:4 = RFU = Fh  
JEDEC  
Sector Map  
Parameter  
Dword-10  
Config-2  
Erase Type not supported = 0/ supported = 1  
Bit 3 = Erase Type 4 support = 0b  
--- Erase Type 4 is not defined  
Bit 2 = Erase Type 3 support = 1b  
--- Erase Type 3 is 256 KB erase and is supported in the  
64 KB sector region  
07h  
(1Gb)  
71h  
6Fh  
Region-0  
Bit 1 = Erase Type 2 support = 0b  
--- Erase Type 2 is 64 KB erase and is not supported in the  
64 KB sector region  
Bit 0 = Erase Type 1 support = 0b  
--- Erase Type 1 is 4 KB erase and is not supported in the  
64 KB sector region  
Datasheet  
160 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 71  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B, Section  
2, Sector Map Parameter Table, 1Gb (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
72h  
73h  
74h  
70h  
71h  
72h  
F4h  
7Fh  
03h  
Bits 31:8 = Region size = 00037Fh:  
Region size as count – 1 of 256 Byte units = 1 x 224 KB  
sectors = 224 KB  
Count = 224 KB/256 = 896, value = count – 1 = 896 – 1 = 895  
= 37Fh  
Bits 7:4 = RFU = Fh  
JEDEC  
Sector Map  
Parameter  
Dword-11  
Config-2  
Erase Type not supported = 0/ supported = 1  
Bit 3 = Erase Type 4 support = 0b  
--- Erase Type 4 is not defined  
Bit 2 = Erase Type 3 support = 1b  
--- Erase Type 3 is 256 KB erase and is supported in the  
32 KB sector region  
75h  
73h  
00h  
Region-1  
Bit 1 = Erase Type 2 support = 0b  
--- Erase Type 2 is 64 KB erase and is not supported in the  
32 KB sector region  
Bit 0 = Erase Type 1 support = 0b  
--- Erase Type 1 is 4 KB erase and is not supported in the  
32 KB sector region  
76h  
77h  
78h  
74h  
75h  
76h  
F1h  
7Fh  
00h  
Bits 31:8 = Region size = 00007Fh:  
Region size as count – 1 of 256 Byte units = 8 x 4 KB sectors  
= 32 KB  
Count = 32 KB/256 = 128, value = count – 1 = 128 – 1 = 127  
= 7Fh  
Bits 7:4 = RFU = Fh  
JEDEC  
Sector Map  
Parameter  
Dword-12  
Config-2  
Erase Type not supported = 0/ supported = 1  
Bit 3 = Erase Type 4 support = 0b  
--- Erase Type 4 is not defined  
Bit 2 = Erase Type 3 support = 0b  
--- Erase Type 3 is 256 KB erase and is supported in the  
4 KB sector region  
79h  
77h  
00h  
Region-2  
Bit 1 = Erase Type 2 support = 0b  
--- Erase Type 2 is 64 KB erase and is not supported in the  
4 KB sector region  
Bit 0 = Erase Type 1 support = 1b  
--- Erase Type 1 is 4 KB erase and is supported in the 4 KB  
sector region  
7Ah  
7Bh  
7Ch  
78h  
79h  
7Ah  
JEDEC  
Sector Map  
Parameter  
Dword-13  
Config-3  
FFh  
03h  
00h  
Bits 31:24 = RFU = FFh  
Bits 23:16 = Region count (Dwords – 1) = 00h: One region  
Bits 15:8 = Configuration ID = 03h: Uniform 256 KB sectors  
Bits 7:2 = RFU = 111111b  
Bit 1 = Map Descriptor = 1  
Bit 0 = The end descriptor = 1  
7Dh  
7Bh  
FFh  
Header  
Datasheet  
161 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
Table 71  
CFI  
CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B, Section  
2, Sector Map Parameter Table, 1Gb (Continued)  
SFDP  
parameter parameter  
relative  
byte  
relative  
byte  
SFDPDword  
name  
Data  
Description  
address  
offset  
address  
offset  
7Eh  
7Fh  
80h  
7C  
7D  
7E  
F4h  
FFh  
FFh  
Bits 31:8 = 1Gb device Region size = 07FFFFh:  
Region size as count – 1 of 256 Byte units = 512 x 256 KB  
sectors = 131072 KB  
Count = 131072 KB/256 = 524288, value = count – 1 =  
524288 – 1 = 524287 = 7FFFFh  
Bits 7:4 = RFU = Fh  
JEDEC  
Sector Map  
Parameter  
Dword-14  
Config-3  
Erase Type not supported = 0 / supported = 1  
Bit 3 = Erase Type 4 support = 0b  
--- Erase Type 4 is not defined  
Bit 2 = Erase Type 3 support = 1b  
--- Erase Type 3 is 256 KB erase and is supported in the  
256 KB sector region  
81h  
7F  
07h  
Region-0  
Bit 1 = Erase Type 2 support = 0b  
--- Erase Type 2 is 64 KB erase and is not supported in the  
256 KB sector region  
Bit 0 = Erase Type 1 support = 0b  
--- Erase Type 1 is 4 KB erase and is not supported in the  
256 KB sector region  
13.3  
Initial Delivery State  
The low address device is shipped from Cypress with non-volatile bits set as follows:  
• The entire memory array is erased: i.e. all bits are set to 1 (each byte contains FFh).  
• The OTP address space has the first 16 bytes programmed to a random number. All other bytes are erased to FFh.  
• The SFDP address space contains the values as defined in the description of the SFDP address space.  
• The ID-CFI address space contains the values as defined in the description of the ID-CFI address space.  
• The Status Register 1 Non-volatile contains 00h (all SR1NV bits are cleared to 0’s).  
• The Configuration Register 1 Non-volatile contains 00h.  
• The Configuration Register 2 Non-volatile contains 08h.  
• The Configuration Register 3 Non-volatile contains 00h.  
• The Configuration Register 4 Non-volatile contains 00h.  
• The Password Register contains FFFFFFFF-FFFFFFFFh  
• All PPB bits are “1.  
• The ASP Register bits are FFFFh  
The high address device is shipped from Cypress with non-volatile bits set as follows:  
• The entire memory array is erased: i.e. all bits are set to 1 (each byte contains FFh).  
• The OTP address space has the first 16 bytes programmed to a random number. All other bytes are erased to FFh.  
• The SFDP address space contains the values as defined in the description of the SFDP address space.  
Datasheet  
162 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
• The ID-CFI address space contains the values as defined in the description of the ID-CFI address space.  
• The Status Register 1 Non-volatile contains 00h (all SR1NV bits are cleared to 0’s).  
• The Configuration Register 1 Non-volatile contains 00h.  
• The Configuration Register 2 Non-volatile contains 08h.  
• The Configuration Register 3 Non-volatile contains 00h.  
• The Configuration Register 4 Non-volatile contains 00h.  
• The Password Register contains FFFFFFFF-FFFFFFFFh  
• All PPB bits are “1.  
• The ASP Register bits are FFFFh  
13.4  
FS01GS Behavior and Software Modifications  
The FS01GS provides a Single Chip Select (CS#) Dual Die Package (DDP) density option that uses two FS512S  
devices stacked within the same package to provide 1Gb of memory. The the two devices share the CS# input to  
provide a contiguous 1 Gb (128 MB) address space. One device responds to commands directed to the lower  
512 Mb of the address space and the other device responds to commands directed to the upper 512 Mb of the  
address space.  
However there are some behavior and required software differences versus the lower density FS-S family devices.  
• Four byte address mode or four byte address commands are required to access memory locations above the  
first 128 Mb (16MB) of the FS01GS address space and the registers in each FS512S. The 4BAM (B7h) command  
is used to enter the four byte address mode.  
• A sequential read sequence does not cross the 512 Mbitboundary between the devices. A read access continuing  
beyond the end of the address space of one FS512S device, wraps around to the lowest address of the same  
device. A sequential read at address 03FFFFFFh of an FS01GS will be followed by a read at 00000000h. A  
sequential read at address 07FFFFFFh of an FS01GS will be followed by a read at 04000000h.  
• Several of the legacy SPI commands for register reading, writing or other operations do not have an explicit  
address in the command. For this reason, several of the legacy SPI commands are not supported by the FS01GS  
and alternate commands that include an address must be used to route the command to the lower or upper  
FS512S. The following commands are not supported in the FS01GS:  
- WRR (01h)  
- RDCR (35h)  
- RDSR1 (05h)  
- RDSR2 (07h)  
- PNVDLR (43h)  
- ASPP (2Fh)  
- PASSP (E8h)  
- PPBE (E4h)  
- EPS (B0h)  
- EPR (30h)  
Datasheet  
163 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
• The status and configuration registers must be configured in each device separately. The RDAR (65h) and WRAR  
(71h) commands must be used, in four byte address mode, for reading and writing the registers so that the  
command address directs the operation to the lower or upper FS512S device in the DDP. Because the RDAR and  
WRAR commands can operate in both 3 byte and 4 byte address modes, it is necessary to issue the four byte  
address mode (4BAM, B7h) command before using the RDAR and WRAR commands to access registers in the  
lower and upper FS512S devices. The registers in each device must generally be configured as though the device  
pair is acting as one monolithic device in order to simplify a later migration to a next generation monolithic 1 Gb  
device.  
- Register Bits that must be configured the same in each FS512S (note that matching non-volatile registers in  
each device must be the same and matching volatile registers must be the same but the volatile registers may  
have values different from their related non-volatile register):  
• Status Register Write Disable in SR1NV[7] and SR1V[7]  
• Configuration Register 1 bits 7 to 3 and 1 to 0 in CR1NV[7:3, 1:0]and CR1V[7:3, 1:0]  
• Configuration Register 2 bits 7 to 0 in CR2NV and CR2V  
• Configuration Register 3 bits 7 to 4 and 2 to 0 in CR3NV[7:4, 2:0] and CR3V[7:4, 2:0]  
• Configuration Register 4 bits 7 to 0 in CR4NV and CR4V  
• ASP Register bits 15 to 0 in ASPR  
• Password Register bits 63 to 0 in PASS. The password should be programmed and read back to verify the  
bits are programmed correctly in each device before selecting the Password Mode by programming the ASP  
register in each device.  
• Data Learning Pattern in NVDLR and VDLR  
- Register bits that may be configured the same or differently in each FS512S:  
• TBPARM_O in CR1NV[2] and 20h_NV in CR3NV[3]. Parameter sectors (4 KB) may optionally be located only  
at the bottom or top of the 1 Gb address space. This means only three combinations of these two configu-  
ration bits are supported as shown in the Table 72.  
Table 72  
FS01GS Parameter Sector Map options  
Device  
Lower FS512S  
TBPARM_0 20h_NV  
Upper FS512S  
Parameter sector location  
None (Uniform Sectors)  
Bottom  
TBPARM_0  
20h_NV  
X
0
X
0
1
0
1
0
X
X
1
0
1
1
0
0
Top  
Default Configuration  
• Block Protection bits in SR1NV[4:2] and SR1V[4:2]. Block protection must be configured in each FS512S as  
desired to protect the sectors in each device. The fraction of the array that is protected by the BP bits is with  
reference to the FS512S device in which the BP bits reside. Note that because the TBPROT_O bits in each  
device must be configured the same, BP protection range is oriented top or bottom in both devices.  
• The Advanced Sector Protection Dynamic (DYB) and Persistent Protection Bits (PPB) must be configured in  
each FS512S as desired to protect the sectors in each device. The 4DYBWR, 4DYBRD, 4PPBP, or 4PPBRD  
commands may be used to configure the DYB and PPB bits. Or, the DYBWR, DYBRD, PPBP, or PPBRD  
commands in four byte address mode may be used to configure the DYB and PPB bits.  
Datasheet  
164 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Software Interface Reference  
• The following commands operate on both FS512S devices in parallel:  
- 4BAM (B7h)  
- SBL (C0h)  
- WVDLR (4Ah)  
- CLSR (82h or 30h)  
- PLBWR (A6h)  
- PASSU (E9h)  
- RSTEN (66h)  
- RST (99h)  
- MBR (FFh)  
- DPD (B9h)  
- RES (ABh)  
- WREN (06h)  
• The Write Enable (WREN) command enables write operations in both devices. Write operations are  
automatically disabled in the device that completes a write operation. Write operations remain enabled in  
the device not selected by a write operation.  
- WRDI (04h)  
• A Write Disable (WRDI) command is recommended to follow the completion of any write operation, to  
disable write operations in both devices.  
• Separate suspend and resume command pairs are used for program versus erase operations.  
- The EPS (85h) command is required to suspend a program operation.  
- The EPS (75h) command is required to suspend an erase operation.  
- The EPR (8Ah) command is required to resume a program operation.  
- The EPR (7Ah) command is required to resume an erase operation.  
• New commands with a 4 byte address are added for Bulk Erase Addressed (BEA, FEh) and PPB Erase Addressed  
(PPBEA, EAh) to direct the operations to the lower or upper FS512S device.  
• Input and output capacitance is double that of other FS-S family devices due to the parallel connection of the  
two FS512S devices. This may slow the speed of output switching on the host or memory thus lowering the  
maximum transfer rates.  
• Power up, reset, and DPD current consumption is double that of other FS-S family devices due to the parallel  
operation of the two FS512S devices during these operations.  
Datasheet  
165 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Ordering Information  
14  
Ordering Information  
14.1  
Ordering Part Number  
The ordering part number is formed by a valid combination of the following:  
S70FS  
01G  
S
AG  
M
F
I
01  
1
Packing Type  
0 = Tray  
1 = Tube  
3 = 13” Tape and Reel  
Model Number (Additional Ordering Options)  
01 = SOIC16 footprint  
21 = 5 × 5 ball BGA footprint  
Temperature Range  
I = Industrial (–40 °C to +85 °C)  
V = Industrial Plus (–40 °C to +105 °C)  
A = Automotive, AEC-Q100 Grade 3 (–40 °C to +85 °C)  
B = Automotive, AEC-Q100 Grade 2 (–40 °C to +105 °C)  
M = Automotive, AEC-Q100 Grade 1 (–40 °C to +125 °C)  
Package Materials  
F = Lead (Pb)-free  
H = Low-Halogen, Lead (Pb)-free  
Package Type  
M = 16-pin SOIC  
B = 24-ball BGA 6 × 8 mm package, 1.00 mm pitch  
Speed  
AG = 133 MHz  
DS = 80 MHz DDR  
Device Technology  
S = 65 nm MirrorBit Process Technology  
Density  
01G = 1 Gb  
Device Family  
S70FS – Dual Die in Package  
Cypress Memory 1.8 Volt-only, SPI Flash Memory  
Datasheet  
166 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Ordering Information  
14.2  
Valid Combinations — Standard  
Valid Combinations list configurations planned to be supported in volume for this device. Contact your local sales  
office to confirm availability of specific valid combinations and to check on newly released combinations.  
Table 73  
Valid Combinations — Standard  
Base Ordering  
Speed  
Package and  
Temperature  
Model  
Packing  
Type  
Package Marking  
Part Number  
Option  
Number  
FS01GS + A + (Temp) + F + (Model  
Number)  
FS01GS + A + (Temp) + H + (Model  
Number)  
FS01GS + D + (Temp) + F + (Model  
Number)  
FS01GS + D + (Temp) + H + (Model  
Number)  
MFI, MFV  
BHI, BHV  
MFI, MFV  
BHI, BHV  
01  
21  
01  
21  
0, 1, 3  
0, 3  
AG  
DS  
S70FS01GS  
0, 1, 3  
0, 3  
14.3  
Valid Combinations — Automotive Grade / AEC-Q100  
Table 74 lists configurations that are Automotive Grade / AEC-Q100 qualified and are planned to be available in  
volume. The table will be updated as new combinations are released. Contact your local sales representative to  
confirm availability of specific combinations and to check on newly released combinations.  
Product Part Approval Process (PPAP) support is only provided for AEC-Q100 grade products.  
Products to be used in end-use applications that require ISO/TS-16949 compliance must be AEC-Q100 grade  
products in combination with PPAP. Non–AEC-Q100 grade products are not manufactured or documented in full  
compliance with ISO/TS-16949 requirements.  
AEC-Q100 grade products are also offered without PPAP support for end-use applications that do not require  
ISO/TS-16949 compliance.  
Table 74  
Valid Combinations — Automotive Grade / AEC-Q100  
Base Ordering  
Speed  
Package and  
Temperature  
Model  
Packing  
Type  
Package Marking  
Part Number  
Option  
Number  
FS01GS + A +(Temp) + F + (Model  
Number)  
FS01GS + A +(Temp) + H + (Model  
Number)  
FS01GS + D +(Temp) + F + (Model  
Number)  
FS01GS + D +(Temp) + H + (Model  
Number)  
MFA, MFB, MFM  
BHA, BHB, BHM  
MFA, MFB, MFM  
BHA, BHB, BHM  
01  
21  
01  
21  
0, 1, 3  
0, 3  
AG  
DS  
S70FS01GS  
0, 1, 3  
0, 3  
Datasheet  
167 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Revision history  
Revision history  
Document  
Date of release  
version  
Description of changes  
**  
2015-11-10  
Initial release.  
Updated Features (Removed “Continuous (XIP)” in Modes under “Read”).  
Updated Command Protocol (Updated description).  
Updated Electrical specifications:  
Updated DC characteristics:  
Updated Industrial:  
Updated Table 8 (Changed Icc Active current at 133 Mhz maximum from  
35 mA to 45 mA, changed Icc Deep Power down current maximum from  
100 A to 120 A).  
Updated Industrial Plus:  
Updated Table 9 (Changed Serial SDR @ 54 MHz to 50 MHz, changed Icc1  
Active Power Supply Current Read maximum value from 35 mA to 45 mA).  
Updated Address space maps:  
Updated Error correction code (ECC):  
Updated Configuration Register 1:  
Updated Configuration Register 1 Non-volatile (CR1NV):  
Updated Table 23 (Changed default state from “X” to “0” for Bits2  
TBPARM_O).  
Updated Configuration Register 2:  
Updated Configuration Register 2 Non-volatile (CR2NV):  
Updated Table 26 (Updated Note 2).  
Updated Commands:  
*A  
2016-03-18  
Updated Command set summary:  
Updated Reset (Updated description).  
Updated Read Memory Array commands:  
Updated Dual I/O Read (DIOR BBh or 4DIOR BCh)(Updated description,  
updated Note 1 in Figure 64, removed figure “Dual I/O Continuous Read  
Command Sequence (4-Byte Address [CR2V[7] = 1])”).  
Updated Quad I/O Read (QIOR EBh or 4QIOR ECh) (Updated description,  
removed figures “Continuous Quad I/O Read Command Sequence (3-Byte  
Address)” and “Continuous Quad I/O Read Command Sequence (4-Byte  
Address)”).  
Updated DDR Quad I/O Read (EDh, EEh) (Updated description, removed  
figures “Continuous DDR Quad I/O Read Subsequent Access (3-Byte  
Address)” and “Continuous DDR Quad I/O Read Subsequent Access (4-Byte  
Address)”).  
Updated Software Interface Reference:  
Updated Device ID and Common Flash Interface (ID-CFI) Address Map:  
Updated Field Definitions:  
Updated Table 68.  
Updated FS01GS Behavior and Software Modifications:  
Updated Table 72.  
Updated to new template.  
Datasheet  
168 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Revision history  
Document  
Date of release  
version  
Description of changes  
Added Extended temperature range (–40 °C to +125 °C) related information  
in all instances across the document.  
Updated Logic block diagram:  
Updated Typical Program and Erase Rates:  
Updated “256 KB Sector Erase (Uniform Logical Sector) Option” value.  
Updated Electrical specifications:  
Updated DC characteristics:  
Updated Industrial:  
*B  
2016-08-17  
Updated Table 8 (Updated typical and maximum values of ICC2, ICC3, ICC4,  
ICC5 parameters).  
Updated Industrial Plus:  
Updated Table 9 (Updated typical and maximum values of ICC2, ICC3, ICC4,  
ICC5 parameters).  
Added Data Integrity.  
Updated to new template.  
Added ECC related information in all instances across the document.  
Removed Extended Temperature Range related information in all instances  
across the document.  
Replaced VDD with VCC in all instances across the document.  
Updated Physical interface:  
Updated Physical diagrams:  
Updated SOIC 16-lead, 300-mil body width (SL3016).  
Updated Ball grid array 24-ball FBGA 8.0 x 6.0 X 1.2 mm (ZSA024).  
Updated Address space maps:  
*C  
2017-04-21  
Updated Flash memory array:  
Updated Table 17.  
Updated Data Integrity:  
Updated Data Retention:  
Updated Table 51.  
Updated to new template.  
Replaced VDD with VCC in all instances across the document.  
Added Logic block diagram.  
Updated Performance summary:  
Updated Typical current consumption, –40 °C to +85 °C (Updated details  
under “Current (mA)” column).  
Updated Other Resources:  
Updated hyperlinks.  
Updated Electrical specifications:  
*D  
2018-05-23  
Updated Power-up and power-down:  
Updated DDR data valid timing using DLP:  
Updated description.  
Removed “Data Learning Pattern Minimum Window.  
Updated Physical interface:  
Updated Physical diagrams:  
Updated Ball grid array 24-ball FBGA 8.0 x 6.0 X 1.2 mm (ZSA024).  
Updated to new template.  
Datasheet  
169 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Revision history  
Document  
Date of release  
version  
Description of changes  
Updated Overview:  
Updated Other Resources:  
Removed “Specification Bulletins.  
Updated Signal protocols:  
Updated Interface states:  
Updated Instruction cycle (QPI mode):  
Updated description.  
Updated Address space maps:  
Updated Registers:  
*E  
2018-12-14  
Updated Configuration Register 3:  
Updated Configuration Register 3 Non-volatile (CR3NV):  
Updated Table 28.  
Updated description.  
Updated Configuration Register 3 Volatile (CR3V).  
Updated Table 29.  
Updated description.  
Updated Document Title to read as “S70FS01GS, 1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V.  
Updated Performance summary:  
Updated Typical Program and Erase rates:  
Updated all values.  
Updated Overview:  
Removed “Other Resources.  
Updated SPI with multiple input / output (SPI-MIO):  
Replaced “Hardware interface” with “SPI with multiple input / output  
(SPI-MIO)” in heading.  
Updated Table 2.  
Updated Signal descriptions:  
Updated Chip Select (CS#):  
Updated description.  
Updated Write Protect (WP#) / IO2:  
Updated description.  
*F  
2022-05-04  
Updated Signal protocols:  
Updated Interface states:  
Updated Instruction cycle (Legacy SPI mode):  
Updated description.  
Updated Electrical specifications:  
Updated Thermal resistance:  
Updated Table 4.  
Updated DC characteristics:  
Updated Industrial:  
Updated Table 8.  
Updated Industrial Plus:  
Updated Table 9.  
Updated Extended:  
Updated Table 10.  
Datasheet  
170 of 172  
002-03833 Rev. *F  
2022-05-04  
1Gb (128 MB) FS-S Flash  
SPI Multi-I/O, 1.8V  
Revision history  
Document  
Date of release  
version  
Description of changes  
Updated Timing specifications:  
Updated SDR AC characteristics:  
Updated Note 21.  
Updated Input / Output timing:  
Updated Figure 32.  
Updated DDR AC characteristics:  
Updated DDR data valid timing using DLP:  
Replaced “DDR data learning pattern timing” with “DDR data valid timing  
using DLP” in heading.  
Updated Figure 35 (Updated caption only).  
Removed “Software interface.  
Updated Address space maps:  
Updated Registers:  
Updated Status Register-1:  
Updated Status Register-1 Non-Volatile (SR1NV):  
Updated Table 20.  
Updated description.  
Updated Status Register-1 Volatile (SR1V):  
Updated Table 21.  
Updated description.  
Updated Configuration Register 1:  
Updated Configuration Register 1 Non-volatile (CR1NV):  
Updated description.  
*F (cont.)  
2022-05-04  
Updated Configuration Register 1 Volatile (CR1V):  
Updated description.  
Updated Data Protection:  
Updated Write Enable Command:  
Updated description.  
Updated Commands:  
Updated Command set summary:  
Updated Command summary by function:  
Updated Table 46.  
Updated Register Access commands:  
Updated Write Disable (WRDI 04h)::  
Updated description.  
Updated Erase Flash Array Commands:  
Updated Erase or Program Suspend (EPS 85h, 75h):  
Updated description.  
Updated Software Interface Reference:  
Updated Initial Delivery State:  
Updated description.  
Migrated to Infineon template.  
Datasheet  
171 of 172  
002-03833 Rev. *F  
2022-05-04  
Please read the Important Notice and Warnings at the end of this document  
Trademarks  
All referenced product or service names and trademarks are the property of their respective owners.  
IMPORTANT NOTICE  
For further information on the product, technology,  
The information given in this document shall in no  
event be regarded as a guarantee of conditions or  
characteristics (“Beschaffenheitsgarantie”).  
Edition 2022-05-04  
Published by  
delivery terms and conditions and prices please  
contact your nearest Infineon Technologies office  
(www.infineon.com).  
Infineon Technologies AG  
81726 Munich, Germany  
With respect to any examples, hints or any typical  
values stated herein and/or any information  
regarding the application of the product, Infineon  
Technologies hereby disclaims any and all  
warranties and liabilities of any kind, including  
without limitation warranties of non-infringement of  
intellectual property rights of any third party.  
WARNINGS  
Due to technical requirements products may contain  
dangerous substances. For information on the types  
in question please contact your nearest Infineon  
Technologies office.  
© 2022 Infineon Technologies AG.  
All Rights Reserved.  
Except as otherwise explicitly approved by Infineon  
In addition, any information given in this document  
is subject to customer’s compliance with its  
obligations stated in this document and any  
applicable legal requirements, norms and standards  
concerning customer’s products and any use of the  
product of Infineon Technologies in customer’s  
applications.  
Technologies in  
authorized  
a written document signed by  
Do you have a question about this  
document?  
Go to www.infineon.com/support  
representatives  
of  
Infineon  
Technologies, Infineon Technologies’ products may  
not be used in any applications where a failure of the  
product or any consequences of the use thereof can  
reasonably be expected to result in personal injury.  
Document reference  
002-03833 Rev. *F  
The data contained in this document is exclusively  
intended for technically trained staff. It is the  
responsibility of customer’s technical departments  
to evaluate the suitability of the product for the  
intended application and the completeness of the  
product information given in this document with  
respect to such application.  

相关型号:

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