S79FL01GS
1-Gbit (128 MB) Dual-Quad MirrorBit® Flash
NVM CMOS 3.0 V Core SPI with Multi-I/O
Features
Density
– 1 Gbit (128 Mbytes)
Serial Peripheral Interface (SPI)
– SPI clock polarity and phase modes 0 and 3
– Double data rate (DDR) option
– Extended addressing: 32-bit address
READ Commands
– Dual-Quad SPI Quad Read: 104 MHz clock rate
(104 MB/s)
– Dual-Quad SPI Quad DDR Read: 80 MHz clock rate
(160 MB/s)
– Normal, Fast, Quad, Quad DDR
– AutoBoot - power up or reset and execute a Normal or
Quad read command automatically at a preselected
address
– Common flash interface (CFI) data for configuration
information.
Programming (3 Mbytes/s)
– 1024-byte page programming buffer
– Quad-input page programming (QPP) for slow clock
systems
– Automatic error checking and correction (ECC) – internal
hardware ECC with single bit error correction
Erase (1 Mbyte/s)
– Uniform 512-kbyte sectors
– Extended addressing: 24- or 32-bit address options
Cycling Endurance
– 100,000 program-erase cycles, minimum
Data Retention
– 20 year data retention, minimum
Security Features
– Separate one time program (OTP) array of 2048 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
Cypress Semiconductor Corporation
Document Number: 002-00466 Rev. *G
•
Cypress® 65 nm MirrorBit® Technology with Eclipse
Architecture
Core Supply Voltage: 2.7 V to 3.6 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)
Packages (all Pb-free)
– BGA-24 6 8 mm
– 5 5 ball (ZSA024) footprint
Software Features
– Program suspend and resume
– Erase suspend and resume
– Status register provides status of embedded erase or
programming operation
– CFI-compliant — allows the host system to identify the
flash device and determine its capabilities
– JEDEC JESD216 Serial Flash Discoverable Parameter
(SFDP) support
– User-configurable configuration register
Hardware Features
– Hardware reset input (RESET#) — resets device to
standby state
198 Champion Court
•
San Jose, CA 95134-1709
•
408-943-2600
Revised March 20, 2018
S79FL01GS
Performance Summary
Maximum Read Rates SDR Dual-Quad SPI (VCC = 2.7 V to 3.6 V)
Command
Clock Rate (MHz)
Mbytes/s
Read
50
12.5
Fast Read
133
33
Quad Read
104
104
Clock Rate (MHz)
Mbytes/s
80
160
Maximum Read Rates DDR Dual-Quad SPI (VCC = 3 V to 3.6 V)
Command
DDR Quad Read
Typical Program and Erase Rates Dual-Quad SPI
Operation
kbytes/s
Page Programming (1024-byte page buffer)
3000
512-kbyte Logical Sector Erase
1000
Typical Current Consumption, Dual-Quad SPI
Operation
Current (mA)
Serial Read 50 MHz
32 (max)
Serial Fast Read 133 MHz
66 (max)
Quad Read 104 MHz
122 (max)
Program
200 (max)
Erase
200 (max)
Standby
0.14 (typ)
Document Number: 002-00466 Rev. *G
Page 2 of 119
S79FL01GS
Contents
1.
1.1
1.2
1.3
Overview .......................................................................
General Description .......................................................
Glossary.........................................................................
Other Resources............................................................
4
4
5
5
2.
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2.11
2.12
2.13
2.14
Signal Descriptions .....................................................
Input/Output Summary...................................................
Multiple Input / Output (Dual-Quad SPI) ........................
RESET# .........................................................................
Multiple Input / Output (Dual-Quad) ...............................
Serial Clock (SCK1, SCK2)............................................
Chip Select (CS1#, CS2#) .............................................
Input Output IO0 – IO7...................................................
Core Voltage Supply (VCC) ............................................
Versatile I/O Power Supply (VIO) ...................................
Supply and Signal Ground (VSS) ...................................
Not Connected (NC) ......................................................
Reserved for Future Use (RFU).....................................
Do Not Use (DNU) .........................................................
Block Diagram................................................................
6
6
7
7
7
8
8
8
8
8
8
8
8
8
9
3.
3.1
3.2
3.3
3.4
3.5
Signal Protocols.........................................................
SPI Clock Modes .........................................................
Command Protocol ......................................................
Interface States............................................................
Configuration Register Effects on the Interface ...........
Data Protection ............................................................
10
10
11
16
19
19
4.
4.1
4.2
4.3
4.4
4.5
Electrical Specifications............................................
Absolute Maximum Ratings .........................................
Thermal Resistance .....................................................
Operating Ranges........................................................
Power-Up and Power-Down ........................................
DC Characteristics .......................................................
20
20
20
20
21
23
5.
5.1
5.2
5.3
5.4
5.5
Timing Specifications................................................
Key to Switching Waveforms .......................................
AC Test Conditions ......................................................
Reset............................................................................
SDR AC Characteristics...............................................
DDR AC Characteristics ..............................................
24
24
24
25
27
29
6.
6.1
Physical Interface ...................................................... 32
Dual-Quad 24-Ball BGA Package (ZSA024) ............... 32
7.
7.1
7.2
7.3
7.4
7.5
7.6
Address Space Maps................................................. 34
Overview ...................................................................... 34
Flash Memory Array..................................................... 34
ID-CFI Address Space ................................................. 34
JEDEC JESD216 Serial Flash Discoverable Parameters
(SFDP) Space.............................................................. 35
OTP Address Space .................................................... 35
Registers...................................................................... 37
8.
8.1
8.2
8.3
Data Protection ..........................................................
Secure Silicon Region (OTP).......................................
Write Enable Command...............................................
Block Protection ...........................................................
Document Number: 002-00466 Rev. *G
8.4
Advanced Sector Protection ......................................... 49
9.
9.1
9.2
9.3
9.4
9.5
9.6
9.7
9.8
9.9
9.10
Commands .................................................................. 53
Command Set Summary............................................... 54
Identification Commands .............................................. 60
Register Access Commands......................................... 62
Read Memory Array Commands .................................. 71
Program Flash Array Commands ................................. 78
Erase Flash Array Commands...................................... 82
One Time Program Array Commands .......................... 85
Advanced Sector Protection Commands ...................... 86
Reset Commands ......................................................... 92
Embedded Algorithm Performance Tables ................... 93
10. Data Integrity ............................................................... 94
10.1 Erase Endurance .......................................................... 94
10.2 Data Retention .............................................................. 94
11. Software Interface Reference .................................... 95
11.1 Serial Flash Discoverable Parameters (SFDP) Address
Map............................................................................... 95
11.2 Device ID and Common Flash Interface (ID-CFI) Address
Map............................................................................... 98
11.3 Device ID and Common Flash Interface (ID-CFI) ASO Map
— Automotive Only ..................................................... 114
11.4 Initial Delivery State .................................................... 114
12.
Ordering Information S79FL01GS ........................... 115
13. Revision History........................................................ 117
Document History Page ................................................... 117
Sales, Solutions, and Legal Information ......................... 119
Worldwide Sales and Design Support .......................... 119
Products ....................................................................... 119
PSoC® Solutions .........................................................119
Cypress Developer Community.................................... 119
Technical Support ........................................................119
47
47
47
48
Page 3 of 119
S79FL01GS
1. Overview
1.1
General Description
The Cypress S79FL01GS device is a flash nonvolatile memory product 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 S79FL01GS device connects two Quad I/O SPI devices with a single CS# resulting in an eight bit I/O data path. This Byte I/O
interface is called Dual-Quad I/O.
This device connects to a host system via a Serial Peripheral Interface (SPI). Traditional SPI single bit serial input and output (IO1
and IO5) is supported as well as four-bit (Quad I/O or QIO) serial commands. This multiple width interface is called SPI Multi-I/O or
MIO. In addition, the S79FL01GS device adds support for Double Data Rate (DDR) read commands for QIO that transfers address
and read data on both edges of the clock.
The Eclipse architecture features a Page Programming Buffer that allows up to 512 words (1024 bytes) to be programmed in one
operation, resulting in significantly faster effective programming (up to 3 MB/s) and erase (up to 1 MB/s) than prior generation SPI
program or erase algorithms.
Executing code directly from flash memory is often called Execute-In-Place or XIP. By using the S79FL01GS device at the higher
clock rates supported, with QIO or DDR-QIO commands, the instruction read transfer rate can match or exceed traditional parallel
interface, asynchronous, NOR flash memories while reducing signal count dramatically.
The S79FL01GS product offers high density coupled with the fastest read and write performance required by a variety of embedded
applications. It is ideal for code shadowing, XIP, and data storage.
Document Number: 002-00466 Rev. *G
Page 4 of 119
S79FL01GS
1.2
Glossary
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.
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.
Nonvolatile
No power is needed to maintain data stored in the memory.
OPN (Ordering Part Number)
The alphanumeric string specifying the memory device type, density, package, factory nonvolatile configuration,
etc. used to select the desired device.
Page
512 bytes aligned and length group of data.
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 256 kbytes.
Write
An operation that changes data within volatile or nonvolatile registers bits or nonvolatile flash memory. When
changing nonvolatile data, an erase and reprogramming of any unchanged nonvolatile data is done, as part of
the operation, such that the nonvolatile data is modified by the write operation, in the same way that volatile data
is modified – as a single operation. The nonvolatile 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.
1.3
1.3.1
Other Resources
Cypress Flash Memory Roadmap
www.cypress.com/product-roadmaps/cypress-flash-memory-roadmap
1.3.2
Links to Software
www.cypress.com/software-and-drivers-cypress-flash-memory
1.3.3
Links to Application Notes
www.cypress.com/appnotes
Document Number: 002-00466 Rev. *G
Page 5 of 119
S79FL01GS
Hardware Interface
Serial Peripheral Interface with Multiple Input / Output (SPI-MIO) Dual-Quad
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 S79FL01GS device reduces the number of signals for connection to the host system by serially transferring all control, address,
and data information over 10 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 S79FL01GS Dual-Quad SPI device uses the industry standard single bit Serial Peripheral Interface (SPI) using two Quad SPI
devices in each package (Quad SPI-1 and Quad SPI-2). This interface is called Dual-Quad and enables support of Byte wide (8 bit)
serial transfers. There is one package option available for S79FL01GS:
24-Ball BGA package with separate balls for CS1#, SCK1 (Quad SPI-1) and CS2#, SCK1 (Quad SPI-2).
For documentation simplicity, all AC timings and waveforms and DC specification are defined using single CS# (Chip Select) and
SCK (Serial Clock) signals. For S79FL01GS, the CS# signal for Quad SPI-1 and Quad SPI-2 are externally tied together, and the
SCK signal for Quad SPI-1 and Quad SPI-2 are externally tied together.
2. Signal Descriptions
2.1
Input/Output Summary
Table 2-1 Dual-Quad Input/Output Descriptions
Signal Name
Type
Description
RESET#
Input
Hardware Reset: Low = device resets and returns to standby state, ready to receive a command.
The signal has an internal pull-up resistor and may be left unconnected in the host system if not
used.
SCK1
Input
Serial Clock for Quad SPI-1
SCK2
Input
Serial Clock for Quad SPI-2
CS1#
Input
Chip Select for Quad SPI-1
CS2#
Input
Chip Select for Quad SPI-2
IO0
I/O
I/O 0 for Quad SPI-1
IO1
I/O
I/O 1 for Quad SPI-1
IO2
I/O
I/O 2 for Quad SPI-1
IO3
I/O
I/O 3 for Quad SPI-1
IO4
I/O
I/O 0 for Quad SPI-2
IO5
I/O
I/O 1 for Quad SPI-2
IO6
I/O
I/O 2 for Quad SPI-2
IO7
I/O
I/O 3 for Quad SPI-2
VCC
Supply
Core Power Supply
VSS
Supply
Ground
Unused
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 Printed Circuit Board (PCB). However, any signal connected to a NC pin must
not have voltage levels higher than the VCC absolute maximum shown on Features page (Core
Supply Voltage).
NC
Document Number: 002-00466 Rev. *G
Page 6 of 119
S79FL01GS
Table 2-1 Dual-Quad Input/Output Descriptions (Continued)
Signal Name
RFU
DNU
Type
Description
Reserved
Reserved for Future Use. No device internal signal is currently connected to the
package connector but there is potential future use for the connector for a 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.
Reserved
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 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.
Note:
1. For the BGA Package, there are two CS# and two SCK balls.
2.2
Multiple Input / Output (Dual-Quad SPI)
Quad Input / Output (I/O) commands send instructions to the memory only on the IO0 (Quad SPI-1) and IO4 (Quad SPI-2) signals.
Address is sent from the host to the memory as four bit (nibble) on IO0, IO1, IO2, IO3 (Quad SPI-1)and repeated on IO4, IO5, IO6,
IO7 (Quad SPI-2). Data is sent and returned to the host as bytes on IO0 - IO7.
2.3
RESET#
The RESET# input provides a hardware method of resetting the device to standby state, ready for receiving a command. When
RESET# is driven to logic low (VIL) for at least a period of tRP, the device:
terminates any operation in progress,
tristates all outputs,
resets the volatile bits in the Configuration Register,
resets the volatile bits in the Status Registers,
resets the Bank Address Register to zero,
loads the Program Buffer with all ones,
reloads all internal configuration information necessary to bring the device to standby mode,
and resets the internal Control Unit to standby state.
RESET# causes the same initialization process as is performed when power comes up and requires tPU time.
RESET# may be asserted low at any time. To ensure data integrity any operation that was interrupted by a hardware reset should
be reinitiated once the device is ready to accept a command sequence.
When RESET# is first asserted Low, the device draws ICC1 (50 MHz value) during tPU. If RESET# continues to be held at VSS the
device draws CMOS standby current (ISB).
RESET# has an internal pull-up resistor and may be left unconnected in the host system if not used.
The RESET# input is not available on all packages options. When not available the RESET# input of the device is tied to the inactive
state, inside the package.
2.4
Multiple Input / Output (Dual-Quad)
Quad Input / Output (I/O) commands send instructions to the memory only on the IO0 (Quad SPI-1) and IO4 (Quad SPI-2) signals.
Address is sent from the host to the memory as four bit (nibble) on IO0, IO1, IO2, IO3 (Quad SPI-1)and repeated on IO4, IO5, IO6,
IO7 (Quad SPI-2). Data is sent and returned to the host as bytes on IO0 - IO7.
Document Number: 002-00466 Rev. *G
Page 7 of 119
S79FL01GS
2.5
Serial Clock (SCK1, SCK2)
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.
2.6
Chip Select (CS1#, CS2#)
The chip select signal indicates when a command for the device is in process 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. Unless an internal Program, Erase or Write Registers (WRR) embedded operation is in progress, the
device will be in the Standby Power mode. Driving the CS# input to 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.
2.7
Input Output IO0 – IO7
These signals are input and outputs 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).
2.8
Core 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. The voltage may vary from 2.7V to 3.6V.
2.9
Versatile I/O Power Supply (VIO)
VIO functionality is not supported on the standard configuration of the S79FL01GS device. However, this VIO signal (ball E4) is
bonded out on the package and must be tied to VCC on the PCB.
2.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.
2.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 Printed Circuit Board (PCB). However, any signal connected to an
NC must not have voltage levels higher than VIO.
2.12
Reserved for Future Use (RFU)
No device internal signal is currently connected to the package connector but is there 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.
2.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.
Document Number: 002-00466 Rev. *G
Page 8 of 119
S79FL01GS
2.14
Block Diagram
Figure 2-1 SPI Host and S79FL01GS Dual-Quad SPI Device with Dual CS# and SCK Balls in the 24-ball BGA package
(5x5 ball configuration)
IO0 – IO3
SCK
CS#
RESET#
IO0 – IO3
SCK1
CS1#
RESET#
Quad SPI -1
CS2#
SCK2
Quad SPI -2
IO4 – IO7
SPI HOST
IO4 – IO7
S79FL01GS Dual-Quad SPI Device
Notes:
1. The SPI Host outputs one Chip Select (CS#) signal, that is routed to CS1# and CS2# balls on the S79FL01GS device.
2. The SPI Host outputs one Clock (SCK) signal, that is routed to SCK1 and SCK2 balls on the S79FL01GS device.
Document Number: 002-00466 Rev. *G
Page 9 of 119
S79FL01GS
3.
Signal Protocols
3.1
SPI Clock Modes
3.1.1
Single Data Rate (SDR)
The S79FL01GS device 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
Figure 3-1 Dual-Quad SPI SDR Modes Supported
CPOL=0_CPHA=0_SCK
CPOL=1_CPHA=1_SCK
CS#
IO0
MSB
IO1
IO4
MSB
MSB
IO5
MSB
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.
3.1.2
Double Data Rate (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.
Document Number: 002-00466 Rev. *G
Page 10 of 119
S79FL01GS
Figure 3-2 Dual-Quad SPI DDR Modes Supported
CPOL=0_CPHA=0_SCK
CPOL=1_CPHA=1_SCK
CS#
Instruction
Transfer_Phase
IO0
3.2
Dummy / DLP
A0 M4 M0
DL .
DL .
D0 D1
IO1
A29 A25
A1 M5 M1
DL .
DL .
D0 D1
IO2
A30 A26
A2 M6 M2
DL .
DL .
D0 D1
IO3
A31 A27
A3 M7 M3
DL .
DL .
D0 D1
A28 A24
A0 M4 M0
DL .
DL .
D0 D1
IO5
A29 A25
A1 M5 M1
DL .
DL .
D0 D1
IO6
A30 A26
A2 M6 M2
DL .
DL .
D0 D1
IO7
A31 A27
A3 M7 M3
DL .
DL .
D0 D1
Inst. 7
Inst. 0
Mode
A28 A24
IO4
Inst. 7
Address
Inst. 0
Command Protocol
All communication between the host system and S79FL01GS memory device 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 serially between the host system and memory device.
Quad Input / Output (I/O) commands provide an address sent from the host as four bit (nibble) groups on IO0, IO1, IO2, IO3 and
repeated on IO4, IO5, IO6, IO7, then followed by dummy cycles. Data is returned to the host as byte on IO0 - IO7. This is referenced
as 2-8-8 for Quad I/O command protocols.
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 8-bit (byte) instruction. The instruction is always presented only as a single bit serial
sequence on the Serial Input (SI) signal with one bit transferred to the memory device on each SCK rising edge. The
instruction selects the type of information transfer or device operation to be performed.
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.
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. This reduces the time needed to send each command when the same
command type is repeated in a sequence of commands. The mode bit transfers occur on SCK rising edge, in SDR
commands, or on every SCK edge, in DDR commands.
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 4-bit groups per (quad) transfer on
the IO0-IO3 signals. Within the 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.
Some 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
Document Number: 002-00466 Rev. *G
Page 11 of 119
S79FL01GS
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 mode bit transfers occur on SCK rising edge, in SDR
commands, or on every SCK edge, in DDR 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.
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 clock cycles after CS# signal was driven low is an exact multiple of eight cycles. If the CS#
signal does not go high exactly at the eight SCK cycle 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.
3.2.1
Command Sequence Examples
Figure 3-3 Dual-Quad Stand Alone Instruction Command
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Instruction
Note:
1. Instruction needs to be the same for both IO0 (Quad SPI-1) and IO4 (Quad SPI-2).
Document Number: 002-00466 Rev. *G
Page 12 of 119
S79FL01GS
Figure 3-4 Dual-Quad Single Bit Wide Input Command
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
SO
Phase
Instruction
Input Data
Note:
1. Instruction needs to be the same for both IO0 (Quad SPI-1) and IO4 (Quad SPI-2).
Figure 3-5 Dual-Quad Single Bit Wide I/O Command without Latency
CS#
SCK
IO0
7
6
5
4
3
2
1
0 31
1
0
IO1
3 2
1
0
3
2
1 0
IO2-IO3
IO4
7
6
5
4
3
2
1
0 31
1
0
IO5
7 6
5
4
7
6
5
4
IO6-IO7
Phase
Instruction
Address
Data 1
Data 2
Note:
1. Instruction needs to be the same for both IO0 (Quad SPI-1) and IO4 (Quad SPI-2).
Figure 3-6 Dual-Quad Single Bit Wide I/O Command with Latency
CS#
SCK
IO0
7
6
5
4
3
2
1
0 31
1
0
IO1
3
2
1
0
3
2
1
0
7
6
5
4
7
6
5
4
IO2-IO3
IO4
7
6
5
4
3
2
1
0 31
1
0
IO5
IO6-IO7
Phase
Instruction
Address
Dummy Cycles
Data 1
Data 2
Note:
1. Instruction needs to be the same for both IO0 (Quad SPI-1) and IO4 (Quad SPI-2).
Document Number: 002-00466 Rev. *G
Page 13 of 119
S79FL01GS
Figure 3-7 Dual-Quad, Quad Output Read Command
CS#
SCK
IO0
0
0
0
0
0
IO1
1
1
1
1
1
IO2
2
2
2
2
2
IO3
3
3
3
3
3
4
4
4
4
4
IO5
5
5
5
5
5
IO6
6
6
6
6
6
IO7
7
7
7
7
7
IO4
7
7
Phase
6
6
5
4
5
4
3
3
2
2
1
1
0
0
A
A
Instruction
1
1
0
0
Address
Dummy
D1 D2 D3 D4 D5
Note:
1. A = MSB of address = 23 for 3-byte address, or 31 for 4-byte address.
Figure 3-8 Dual-Quad, Quad I/O Command
CS#
SCK
IO0
7 6 5 4 3 2 1 0 28
4 0 4 0
4 0 4 0 4 0 4 0
IO1
29
5 1 5 1
5 1 5 1 5 1 5 1
IO2
30
6 2 6 2
6 2 6 2 6 2 6 2
IO3
31
7 3 7 3
7 3 7 3 7 3 7 3
SIG0
Phase
Instruction
AddressMode
Dummy D1
D2
D3
D4
Notes:
1. Instruction, Address and Mode bits needs to be the same for both IO0-IO3 (Quad SPI-1) and IO4-IO7 (Quad SPI-2).
2. The gray bits are optional, the host does not have to drive bits during that cycle.
Document Number: 002-00466 Rev. *G
Page 14 of 119
S79FL01GS
Figure 3-9 Dual-Quad DDR Quad I/O Read Command
CS#
SCK
IO0
0 28 24 20 16 12 8 4 0 4 0
7 6 5 4 3 2 1 0 0 0 0 0
IO1
7
6
5
4
3
2
1
29 25 21 17 13 9 5 1 5 1
7 6 5 4 3 2 1 0 1 1 1 1
IO2
30 26 22 18 14 10 6 2 6 2
7 6 5 4 3 2 1 0 2 2 2 2
IO3
31 27 23 19 15 11 7 3 7 3
7 6 5 4 3 2 1 0 3 3 3 3
0 28 24 20 16 12 8 4 0 4 0
7 6 5 4 3 2 1 0 4 4 4 4
IO5
29 25 21 17 13 9 5 1 5 1
7 6 5 4 3 2 1 0 5 5 5 5
IO6
30 26 22 18 14 2 6 2 6 2
7 6 5 4 3 2 1 0 6 6 6 6
IO7
31 27 23 19 15 3 7 3 7 3
7 6 5 4 3 2 1 0 7 7 7 7
IO4
Phase
7
6
5
4
3
Instruction
2
1
Address
Mode
Dummy
DLP
D1 D2 D3 D4
Notes:
1. Instruction, Address and Mode bits needs to be the same for both IO0-IO3 (Quad SPI-1) and IO4-IO7 (Quad SPI-2).
2. The gray bits are optional, the host does not have to drive bits during that cycle.
Additional sequence diagrams, specific to each command, are provided in Commands on page 53.
Document Number: 002-00466 Rev. *G
Page 15 of 119
S79FL01GS
3.3
Interface States
This section describes the input and output signal levels as related to the SPI interface behavior.
Table 3-1 Dual-Quad Interface States Summary
Interface State
VDD
SCK
CS#
RESET#
IO0 - IO7
Power-Off
< VCC (low)
X
X
X
X
Low Power
–
–
–
–
–
< VCC (cut-off)
X
X
X
X
Power-On (Cold) Reset
VCC (min)
X
HH
X
X
Hardware (Warm) Reset Non-Quad Mode
VCC (min)
X
X
HL
X
Hardware (Warm) Reset Quad Mode
VCC (min)
X
HH
HL
X
Interface Standby
VCC (min)
X
HH
HH
X
Instruction Cycle (Legacy SPI)
VCC (min)
HT
HL
HH
X
Single Input Cycle
Host to Memory Transfer
VCC (min)
HT
HL
HH
X
Single Latency (Dummy) Cycle
VCC (min)
HT
HL
HH
X
Single Output Cycle
Memory to Host Transfer
VCC (min)
HT
HL
HH
X
Quad Input Cycle
Host to Memory Transfer
VCC (min)
HT
HL
HH
X
Quad Latency (Dummy) Cycle
VCC (min)
HT
HL
HH
X
Quad Output Cycle
Memory to Host Transfer
VCC (min)
HT
HL
HH
X
DDR Quad Input Cycle
Host to Memory Transfer
VCC (min)
HT
HL
HH
X
DDR Latency (Dummy) Cycle
VCC (min)
HT
HL
HH
X
DDR Quad Output Cycle
Memory to Host Transfer
VCC (min)
HT
HL
HH
X
Hardware Data Protection
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
3.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.
3.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.
Document Number: 002-00466 Rev. *G
Page 16 of 119
S79FL01GS
3.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 25.
3.3.4
Hardware (Warm) Reset
Some of the device package options provide a RESET# input. When 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 POR followed by Hardware Reset on page 25.
3.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.
3.3.6
Instruction Cycle
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 RESET# high, CS# low.
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, Quad output, Quad I/O, DDR Single 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.
3.3.7
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
quad output commands send address to the memory using only SI but return read data using the I/O signals. The host keeps
RESET# high, CS# low, HOLD# high, and drives SI as needed for the command. The memory does not drive the Serial Output (IO1
and IO5) signals.
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, or Quad Output.
3.3.8
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 (CR[7:6]). During
the latency cycles, the host keeps RESET# high, CS# low, and SCK toggles. The host may drive the IO0 and IO4 signals during
these cycles or the host may leave IO0 and IO4 floating. The memory does not use any data driven on IO0 and IO4 or other I/O
signals during the latency cycles. In quad read commands, the host must stop driving the I/O signals on the falling edge at the end of
the last latency cycle. It is recommended that the host stop driving I/O signals during 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 Serial Output (IO0 and IO4) 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, or
quad width.
3.3.9
Dual-Quad Single Output Cycle — Memory to Host Transfer
Several commands transfer information back to the host on the Serial Outputs (IO1 and IO5) signals. The host keeps RESET# high,
CS# low. The memory ignores the Serial Input (IO0 and IO4) signals. The memory drives IO1 and IO5 with data.
The next interface state continues to be Dual Output Cycle until the host returns CS# to high ending the command.
Document Number: 002-00466 Rev. *G
Page 17 of 119
S79FL01GS
3.3.10
QPP or QOR Address Input Cycle
The Quad Page Program and Quad Output Read commands send address to the memory only on IO0 and IO4. The other IO
signals are ignored because the device must be in Quad mode for these commands thus the Hold and Write Protect features are not
active. The host keeps RESET# high, CS# low, and drives IO0.
For QPP the next interface state following the delivery of address is the Quad Input Cycle.
For QOR the next interface state following address is a Quad Latency Cycle if there are latency cycles needed or Quad Output
Cycle if no latency is required.
3.3.11
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. The Quad Page Program command
transfers four data bits to the memory in each cycle. The host keeps RESET# high, 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 Quad Page Program the host returns CS# high following
the delivery of data to be programmed and the interface returns to standby state.
3.3.12
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 (CR[7:6]). During
the latency cycles, the host keeps RESET# high, 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.
3.3.13
Quad Output Cycle — Memory to Host Transfer
The Quad Output Read and Quad I/O Read return data to the host eight bits in each cycle. The host keeps RESET# high, and 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.
3.3.14
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. Eight bits are transferred on
the rising edge of SCK and four bits on the falling edge in each cycle. The host keeps RESET# high, and CS# low.
The next interface state following the delivery of address and mode bits is a DDR Latency Cycle.
Document Number: 002-00466 Rev. *G
Page 18 of 119
S79FL01GS
3.3.15
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
(CR1[7:6]). During the latency cycles, the host keeps RESET# high and 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 Quad Output Cycle, depending on the instruction.
3.3.16
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. Eight bits are transferred on the rising edge of SCK
and four bits on the falling edge in each cycle. The host keeps RESET# high, and CS# low.
The next interface state continues to be DDR Quad Output Cycle until the host returns CS# to high ending the command.
3.4
Configuration Register Effects on the Interface
The configuration register bits 7 and 6 (CR1[7:6]) select the latency code for all read commands. The latency code selects the
number of mode bit and latency cycles for each type of instruction.
The Configuration Register Bit-1 (CR1[1]) selects whether Quad mode is enabled and allow Quad Page Program, Quad Output
Read, and Quad I/O Read commands. Quad mode must also be selected to allow Read DDR Quad I/O commands. This Quad bit is
set to 1 by default for Dual-Quad SPI.
3.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 the following sections. Other software managed protection methods are discussed in the software section (page 34)
of this document.
3.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.
3.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.
3.5.3
Clock Pulse Count
The device verifies that all program, erase, and Write Registers (WRR) commands consist of a clock pulse count that is a multiple of
eight before executing them. A command not having a multiple of 8 clock pulse count is ignored and no error status is set for the
command.
Document Number: 002-00466 Rev. *G
Page 19 of 119
S79FL01GS
4.
Electrical Specifications
4.1
Absolute Maximum Ratings
Table 4-1 Absolute Maximum Ratings
Storage Temperature Plastic Packages
–65°C to +150°C
Ambient Temperature with Power Applied
–65°C to +125°C
–0.5V to +4.0V
VCC
–0.5V to +(VIO + 0.5V)
Input Voltage with Respect to Ground (VSS) (Note 1)
100 mA
Output Short Circuit Current (Note 2)
Notes:
1. See Input Signal Overshoot on page 21 for allowed maximums during signal transition.
2. 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.
3. 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.
4.2
Thermal Resistance
Table 4-2 Thermal Resistance
Parameter
Theta JA
4.3
Description
ZSA024
Unit
Thermal resistance (junction to ambient)
38
°C/W
Operating Ranges
Operating ranges define those limits between which the functionality of the device is guaranteed.
4.3.1
Temperature Ranges
Table 4-3 Recommended Operating Ranges
Parameter
Ambient Temperature
Symbol
TA
Devices
Spec
Min
Max
Industrial (I)
–40
+85
Industrial Plus (V) (1)
–40
+105
Automotive, AEC-Q100 Grade 3 (A)
–40
+85
Automotive, AEC-Q100 Grade 2 (B)
–40
+105
Unit
°C
°C
Note:
1. 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.
Document Number: 002-00466 Rev. *G
Page 20 of 119
S79FL01GS
4.3.2
Input Signal Overshoot
During DC conditions, input or I/O signals should remain equal to or between VSS and VIO. During voltage transitions, inputs or I/Os
may overshoot VSS to –2.0V or overshoot to VCC +2.0V, for periods up to 20 ns.
Figure 4-1 Maximum Negative Overshoot Waveform
20 ns
20 ns
VIL
- 2.0V
20 ns
Figure 4-2 Maximum Positive Overshoot Waveform
20 ns
VCC + 2.0V
VIH
20 ns
4.4
20 ns
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 (generally of the order of 100 k) 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 4-3. 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.
After power-up (tPU), the device is in Standby mode (not Deep Power Down 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 4-4. 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).
Document Number: 002-00466 Rev. *G
Page 21 of 119
S79FL01GS
Table 4-4 Power-Up / Power-Down Voltage and Timing
Symbol
VCC (min)
VCC (cut-off)
VCC (low)
Parameter
Min
Max
Unit
VCC (minimum operation voltage)
2.7
V
VCC (Cut 0ff where re-initialization is needed)
2.4
V
VCC (low voltage for initialization to occur)
VCC (Low voltage for initialization to occur at embedded)
1.0
2.3
V
tPU
VCC (min) to Read operation
tPD
VCC (low) time
300
1.0
µs
µs
Figure 4-3 Power-Up
VCC
VCC(max)
VCC(min)
tPU
Full Device Access
Time
Figure 4-4 Power-Down and Voltage Drop
VCC
VCC(max)
No Device Access Allowed
VCC(min)
tPU
VCC(cut-off)
Device Access
Allowed
VCC(low)
tPD
Time
Document Number: 002-00466 Rev. *G
Page 22 of 119
S79FL01GS
4.5
DC Characteristics
Table 4-5 DC Characteristics
Symbol
Parameter
Test Conditions
Min
Typ (1)
Max
Unit
VIL
Input Low Voltage
-0.5
–
0.2xVCC
V
VIH
Input High Voltage
0.7xVCC
–
VCC+0.4
V
VOL
Output Low Voltage
IOL = 1.6 mA, VCC = VCC min
–
0.15 X VCC
V
VOH
Output High Voltage
IOH = –0.1 mA
0.85 X VCC
–
ILI
Input Leakage
Current
VCC = VCC max, VIN = VIH or
VIL
–
–
±4
µA
ILO
Output Leakage
Current
VCC = VCC max, VIN = VIH or
VIL
–
–
±4
µA
ICC1
Active Power Supply
Current (READ)
Serial SDR@50 MHz
Serial SDR@133 MHz
Quad SDR@ 80 MHz
Quad SDR@104 MHz
Quad DDR@ 80 MHz
Outputs unconnected during
read data return (2)
–
–
32
66/70 (3)
100
122
200
mA
ICC2
Active Power Supply
Current (Page
Program)
CS# = VCC
–
–
200
mA
ICC3
Active Power Supply
Current (WRR)
CS# = VCC
–
–
200
mA
ICC4
Active Power Supply
Current (SE)
CS# = VCC
–
–
200
mA
ICC5
Active Power Supply
Current (BE)
CS# = VCC
–
–
200
mA
ISB (Industrial)
Standby Current
RESET#, CS# = VCC; SI, SCK
= VCC or VSS, Industrial Temp
–
140
200
µA
ISB (Industrial
Plus)
Standby Current
RESET#, CS# = VCC; SI, SCK
= VCC or VSS, Industrial Plus
Temp
–
140
600
µA
V
Notes:
1. Typical values are at TAI = 25°C and VCC = 3V.
2. Outputs switching current is not included.
3. Industrial temperature range / Industrial Plus temperature range.
4.5.1
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.
Document Number: 002-00466 Rev. *G
Page 23 of 119
S79FL01GS
5.
5.1
Timing Specifications
Key to Switching Waveforms
Figure 5-1 Waveform Element Meanings
Input
Valid at logic high or low
High Impedance
Any change permitted
Logic High Logic Low
Valid at logic high or low
High Impedance
Changing, state unknown
Logic High Logic Low
Symbol
Output
Figure 5-2 Input, Output, and Timing Reference Levels
Input Levels
Output Levels
VCC + 0.4V
0.85 x VCC
0.7 x VCC
Timing Reference Level
0.5 x VCC
0.2 x VCC
0.15 x VCC
- 0.5V
5.2
AC Test Conditions
Figure 5-3 Test Setup
Device
Under
Test
CL
Table 5-1 AC Measurement Conditions
Symbol
Parameter
CL
Load Capacitance
Input Rise and Fall
Times
Min
Max
30
15 (4)
–
Unit
pF
2.4
ns
Input Pulse Voltage
0.2 x VCC to 0.8 VCC
V
Input Timing Ref Voltage
0.5 VCC
V
Output Timing Ref
Voltage
0.5 VCC
V
Notes:
1. Output High-Z is defined as the point where data is no longer driven.
2. Input slew rate: 1.5 V/ns.
Document Number: 002-00466 Rev. *G
Page 24 of 119
S79FL01GS
3. AC characteristics tables assume clock and data signals have the same slew rate (slope).
4. DDR Operation.
5.2.1
Capacitance Characteristics
Table 5-2 Capacitance
Parameter
Test Conditions
Min
Max
Unit
CIN
Input Capacitance (applies to SCK, CS#, RESET#)
1 MHz
–
10
pF
COUT
Output Capacitance (applies to All I/O)
1 MHz
–
10
pF
Note:
1. For more information on capacitance, please consult the IBIS models.
5.3
5.3.1
Reset
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 4-3 on page 22, Table 4-4 on page 22, and Table 5-3 on page 26. The device must not be
selected (CS# to go high with VIO) during power-up (tPU), i.e. no commands may be sent to the device until the end of tPU. RESET#
is ignored during POR. If RESET# is low during POR and remains low through and beyond the end of tPU, 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.
Figure 5-4 Reset Low at the End of POR
VCC
VIO
tPU
If RESET# is low at tPU end
RESET#
tRH
CS#
CS# must be high at tPU end
Figure 5-5 Reset High at the End of POR
VCC
tPU
RESET#
If RESET# is high at tPU end
tPU
CS# may stay high or go low at tPU end
CS#
Figure 5-6 POR followed by Hardware Reset
VCC
tPU
tRS
RESET#
tPU
CS#
Document Number: 002-00466 Rev. *G
Page 25 of 119
S79FL01GS
5.3.2
Hardware (Warm) Reset
When the RESET# input transitions from VIH to VIL 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# input provides a hardware method of resetting the flash memory device to standby state.
RESET# must be high for tRS following tPU or tRPH, before going low again to initiate a hardware reset.
When RESET# is driven low for at least a minimum period of time (tRP), the device terminates any operation in progress,
tri-states all outputs, and ignores all read/write commands for the duration of tRPH. The device resets the interface to
standby state.
If CS# is low at the time RESET# is asserted, CS# must return high during tRPH before it can be asserted low again after
tRH.
Figure 5-7 Hardware Reset
tRP
RESET#
Any prior reset
tRH
tRPH
tRH
tRS
tRPH
CS#
Table 5-3 Hardware Reset Parameters
Parameter
Description
Limit
Time
Unit
tRS
Reset Setup — Prior Reset end and RESET# high before RESET#
low
Min
50
ns
tRPH
Reset Pulse Hold — RESET# low to CS# low
Min
35
µs
tRP
RESET# Pulse Width
Min
200
ns
tRH
Reset Hold — RESET# high before CS# low
Min
50
ns
Notes:
1. RESET# Low is optional and 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.
2. Sum of tRP and tRH must be equal to or greater than tRPH.
Document Number: 002-00466 Rev. *G
Page 26 of 119
S79FL01GS
5.4
SDR AC Characteristics
Table 5-4 AC Characteristics (VCC 2.7V to 3.6V)
Symbol
Parameter
Min
Typ
Max
Unit
FSCK, R
SCK Clock Frequency for READ and 4READ
instructions
DC
–
50
MHz
FSCK, C
SCK Clock Frequency for single commands as
shown in Table 9-1 on page 56 (4)
DC
–
133
MHz
FSCK, C
SCK Clock Frequency for the following dual and
quad commands: QOR, 4QOR, QIOR, 4QIOR
DC
–
104
MHz
SCK Clock Frequency for the QPP, 4QPP
commands
DC
–
80
MHz
1/ FSCK
–
45% PSCK
–
–
FSCK, QPP
PSCK
tWH, tCH
tWL, tCL
SCK Clock Period
(5)
Clock High Time
Clock Low Time
(5)
ns
45% PSCK
–
–
ns
tCRT, tCLCH
Clock Rise Time (slew rate)
0.1
–
–
V/ns
tCFT, tCHCL
Clock Fall Time (slew rate)
0.1
–
–
V/ns
tCS
CS# High Time (Read Instructions)
CS# High Time (Program/Erase)
10
50
–
–
ns
tCSS
CS# Active Setup Time (relative to SCK)
3
–
–
ns
tCSH
CS# Active Hold Time (relative to SCK)
3
–
–
tSU
Data in Setup Time
1.5
–
tHD
Data in Hold Time
2
–
tV
tHO
3000
ns
(6)
ns
ns
Clock Low to Output Valid
0
–
8.0 (2)
7.65 (3)
6.5 (4)
Output Hold Time
2
–
–
ns
0
–
8
ns
20 (1)
–
–
ns
–
–
ns
tDIS
Output Disable Time
tWPS
WP# Setup Time
100
(1)
ns
tWPH
WP# Hold Time
tHLCH
HOLD# Active Setup Time (relative to SCK)
3
–
–
ns
tCHHH
HOLD# Active Hold Time (relative to SCK)
3
–
–
ns
tHHCH
HOLD# Non Active Setup Time (relative to SCK)
3
–
–
ns
tCHHL
HOLD# Non Active Hold Time (relative to SCK)
3
–
–
ns
tHZ
HOLD# enable to Output Invalid
–
–
8
ns
tLZ
HOLD# disable to Output Valid
–
–
8
ns
Notes:
1. Only applicable as a constraint for WRR instruction when SRWD is set to a 1.
2. Full VCC range (2.7 - 3.6V) and CL = 30 pF.
3. Regulated VCC range (3.0 - 3.6V) and CL = 30 pF.
4. Regulated VCC range (3.0 - 3.6V) and CL = 15 pF.
5. ±10% duty cycle is supported for frequencies 50 MHz.
6. Maximum value only applies during Program/Erase Suspend/Resume commands.
Document Number: 002-00466 Rev. *G
Page 27 of 119
S79FL01GS
5.4.1
Clock Timing
Figure 5-8 Clock Timing
PSCK
tCH
tCL
VIH min
VCC / 2
VIL max
tCFT
tCRT
5.4.2
Input / Output Timing
Figure 5-9 SPI SDR Dual-Quad Timing
tCS
CS#
tCSS
tCSH
tCSS
SCK
tSU
tLZ
tHD
IO
MSB IN
Document Number: 002-00466 Rev. *G
LSB IN
MSB OUT
.
tHO
tV
tDIS
LSB OUT
Page 28 of 119
S79FL01GS
5.5
DDR AC Characteristics
Table 5-5 AC Characteristics DDR Operation
Symbol
Parameter
Min
Typ
Max
Unit
DC
–
80
MHz
10.75
–
ns
FSCK, R
SCK Clock Frequency for DDR READ
instruction
PSCK, R
SCK Clock Period for DDR READ instruction
tWH, tCH
Clock High Time
45% PSCK
–
–
ns
tWL, tCL
Clock Low Time
45% PSCK
–
–
ns
tCS
CS# High Time (Read Instructions)
10
–
–
ns
tCSS
CS# Active Setup Time (relative to SCK)
3
–
–
ns
tCSH
CS# Active Hold Time (relative to SCK)
3
–
–
tSU
IO in Setup Time
1.5
–
tHD
IO in Hold Time
1.5
–
Clock Low to Output Valid
1.5
–
tHO
Output Hold Time
1.5
–
tDIS
Output Disable Time
–
–
tLZ
Clock to Output Low Impedance
0
First Output to last Output data valid time
–
tV
tO_SKEW
3000
ns
(2)
ns
ns
6.5 (1)
ns
ns
8
ns
–
8
ns
–
600
ps
Notes:
1. Regulated VCC range (3.0 - 3.6V) and CL =15 pF.
2. Maximum value only applies during Program/Erase Suspend/Resume commands.
Document Number: 002-00466 Rev. *G
Page 29 of 119
S79FL01GS
5.5.1
DDR Input Timing
Figure 5-10 SPI DDR Input Timing
tCS
CS#
tCSH
tCSS
tCSH
tCSS
SCK
tHD
tSU
tHD
tSU
IO
5.5.2
MSB IN
LSB IN
DDR Output Timing
Figure 5-11 SPI DDR Output Timing
tCS
CS#
SCK
SI
tLZ
IO
tHO
MSB
Document Number: 002-00466 Rev. *G
tV
tV
tDIS
LSB
Page 30 of 119
S79FL01GS
Figure 5-12 SPI DDR Data Valid Window
PSCK
tCL
tCH
SCK
tV
tV
tO_SKEW
tOTT
Slow
D1
IO0
Slow
D2
IO1
IO2
IO3
IO_valid
Fast
D1
Fast
D2
D1
Valid
D2
Valid
tDV
tDV
Notes:
1. tCLH is the shorter duration of tCL or tCH.
2. tO_SKEW is the maximum difference (delta) between the minimum and maximum tV (output valid) across all IO signals.
3. tOTT is the maximum Output Transition Time from one valid data value to the next valid data value on each IO.
4. tOTT is dependent on system level considerations including:
a.
b.
c.
d.
Memory device output impedance (drive strength).
System level parasitics on the IOs (primarily bus capacitance).
Host memory controller input VIH and VIL levels at which 0 to 1 and 1 to 0 transitions are recognized.
As an example, assuming that the above considerations result a memory output slew rate of 2V/ns and a 3V transition (from 1 to 0 or 0 to 1) is required by the host,
the tOTT would be:
tOTT = 3V/(2V/ns) = 1.5 ns
e. 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.
5. The minimum data valid window (tDV) can be calculated as follows:
a. As an example, assuming:
i. 80 MHz clock frequency = 12.5 ns clock period
ii. DDR operations are specified to have a duty cycle of 45% or higher
iii. tCLH = 0.45*PSCK = 0.45x12.5 ns = 5.625 ns
iv. tO_SKEW = 600 ps
v. tOTT = 1.5 ns
b. tDV = tCLH - tO_SKEW - tOTT
c. tDV = 5.625 ns - 600 ps - 1.5 ns = 3.525 ns
Document Number: 002-00466 Rev. *G
Page 31 of 119
S79FL01GS
6. Physical Interface
Table 6-1 Model Specific Connections
VIO / VCC
Versatile I/O or VCC – VIO functionality is not supported on S79FL01GS. This signal must be tied to VCC on
the PCB.
RESET#
RESET# signal is bonded out and active on the S79FL01GS. The signal has an internal pull-up resistor and
may be left unconnected in the host system if not used.
Note:
1. Refer to Table 2-1 on page 6 for signal descriptions.
6.1
6.1.1
Dual-Quad 24-Ball BGA Package (ZSA024)
Connection Diagram
Figure 6-1 Dual-Quad 24-Ball BGA, 5 x 5 Ball Footprint (ZSA024), Top View
1
2
3
4
5
RFU
CS2#
RESET#
RFU
SCK2
SCK1
VSS
VCC
RFU
VSS
CS1#
RFU
IO2
RFU
RFU
IO1
IO0
IO3
IO4
IO7
IO6
IO5
VIO/VCC
VSS
A
B
C
D
E
Note:
1. The RESET# input has an internal pull-up and may be left unconnected in the system.
Document Number: 002-00466 Rev. *G
Page 32 of 119
S79FL01GS
6.1.2
ZSA024 Physical Diagram
Figure 6-2 ZSA024 — 24-Ball BGA (8 x 6 mm) Package
NOTES:
DIMENSIONS
SYMBOL
MIN.
NOM.
MAX.
A
-
-
1.20
A1
0.20
-
-
8.00 BSC
D
1. ALL DIMENSIONS ARE IN MILLIMETERS.
2. DIMENSIONING AND TOLERANCING METHODS PER ASME Y14.5M-1994.
3. BALL POSITION DESIGNATION PER JEP95, SECTION 3, SPP-020.
4.
e REPRESENTS THE SOLDER BALL GRID PITCH.
E
6.00 BSC
D1
4.00 BSC
5. SYMBOL "MD" IS THE BALL MATRIX SIZE IN THE "D" DIRECTION.
SYMBOL "ME" IS THE BALL MATRIX SIZE IN THE "E" DIRECTION.
E1
4.00 BSC
MD
5
ME
5
n
24
b
0.35
eD
eE
0.40
1.00 BSC
1.00 BSC
SD
0.00
SE
0.00
n IS THE NUMBER OF POPULATED SOLDER BALL POSITIONS FOR MATRIX SIZE
MD X ME.
6 DIMENSION "b" IS MEASURED AT THE MAXIMUM BALL DIAMETER IN A PLANE
0.45
PARALLEL TO DATUM C.
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,
"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.
6.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.
Document Number: 002-00466 Rev. *G
Page 33 of 119
S79FL01GS
Software Interface
This section discusses the features and behaviors most relevant to host system software that interacts with the S79FL01GS memory
device.
7. Address Space Maps
7.1
Overview
7.1.1
Extended Address
The S79FL01GS device supports 32-bit addresses to enable higher density devices than allowed by previous generation (legacy)
SPI devices that supported only 24-bit addresses. A 24-bit byte resolution address can access only 16 Mbytes (128 Mbits) of
maximum density. A 32-bit byte resolution address allows direct addressing of up to a 4 Gbytes (32 Gbits) of address space.
Legacy commands continue to support 24-bit addresses for backward software compatibility. Extended 32-bit addresses are
enabled in three ways:
Bank address register — a software (command) loadable internal register that supplies the high order bits of address when
legacy 24-bit addresses are in use.
Extended address mode — a bank address register bit that changes all legacy commands to expect 32 bits of address
supplied from the host system.
New commands — that perform both legacy and new functions, which expect 32-bit address.
The default condition at power-up and after reset, is the Bank address register loaded with zeros and the extended address mode
set for 24-bit addresses. This enables legacy software compatible access to the first 128 Mbits of a device.
7.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 32-bit address but may only define a small portion of the available address
space.
7.2
Flash Memory Array
The main flash array is divided into erase units called sectors. The sectors are organized as uniform 512-kbyte sectors.
Table 7-1 S79FL01GS Sector and Memory Address Map, Uniform 512-kbyte Sectors
Sector Size (kbyte)
512
Sector Count
256
Sector Range
Address Range (8-bit)
SA00
00000000h-0003FFFFh
:
:
SA255
03FC0000h03FFFFFFh
Notes
Sector Starting Address
—
Sector Ending Address
Note: This is a condensed table that uses a sector as a reference. There are address ranges that are not explicitly listed. All 512-kB
sectors have the pattern XXXX0000h-XXXXFFFFh.
7.3
ID-CFI Address Space
The RDIDJ 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 98 for the
tables defining the contents of the ID-CFI address space. The ID-CFI address space is programmed by Cypress and read-only for
the host system.
Document Number: 002-00466 Rev. *G
Page 34 of 119
S79FL01GS
7.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 95 for the table defining the contents of the SFDP address
space. The SFDP address space is programmed by Cypress and is read-only for the host system
7.5
OTP Address Space
Each S79FL01GS memory device has a 2048-byte One Time Program (OTP) address space that is separate from the main flash
array. The OTP area is divided into 64, individually lockable, 32-byte aligned and length regions.
In the 64-byte region starting at address zero:
The 16 lowest address bytes are programmed by Cypress with a 128-bit random number. Only Cypress is able to program
these bytes.
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 7-1 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 (CR1[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.
During the programming of each OTP region, bits 0-3 are programmed on Quad SPI-1 via IO0-IO3, and bits 4-7 are programmed on
Quad SPI-2 via IO4-IO7.
Figure 7-1 OTP Address Space — Quad SPI-1 and Quad SPI-2
Quad SPI-2
Quad SPI-1
32-byte OTP Region 31
32-byte OTP Region 31
32-byte OTP Region 30
32-byte OTP Region 30
32-byte OTP Region 29
32-byte OTP Region 29
.
.
.
.
.
.
When programmed to
‘ 0‘ each lock bit
protects its related 32
byte region from any
further programming
When programmed to
‘ 0‘ each lock bit
protects its related 32
byte region from any
further programming
32-byte OTP Region 3
32-byte OTP Region 3
32-byte OTP Region 2
32-byte OTP Region 2
32-byte OTP Region 1
32-byte OTP Region 1
32-byte OTP Region 0
32-byte OTP Region 0
...
...
Lock Bits 31 to 0
Contents of Region 0
{
Reserved
Byte 1F
Document Number: 002-00466 Rev. *G
Lock Bytes
Byte 10
16-byte Random Number
Byte 0
Reserved
Byte 1F
Lock Bytes
Byte 10
16-byte Random Number
{
Lock Bits 31 to 0
Contents of Region 0
Byte 0
Page 35 of 119
S79FL01GS
Table 7-2 OTP Address Map for Quad SPI-1 and Quad SPI-2
Region
Byte Address Range (Hex)
Contents
000
Least Significant Byte of
Cypress Programmed
Random Number
...
...
00F
Most Significant Byte of
Cypress Programmed
Random Number
010 to 013
Region Locking Bits
Byte 10 [bit 0] locks region 0
from programming when = 0
...
Byte 13 [bit 7] locks region 31
from programming when = 0
All bytes = FF (1)
014 to 01F
Reserved for Future Use
(RFU)
All bytes = FF
Region 1
020 to 03F
Available for User
Programming
All bytes = FF
Region 2
040 to 05F
Available for User
Programming
All bytes = FF
...
...
Available for User
Programming
All bytes = FF
Region 31
7E0 to 7FF
Available for User
Programming
All bytes = FF
Region 0
Initial Delivery State (Hex)
Cypress Programmed
Random Number
Note:
1. It is recommended that the Lock Bytes for Quad SPI-1 and Quad SPI-2 be programmed with identical data.
Document Number: 002-00466 Rev. *G
Page 36 of 119
S79FL01GS
7.6
Registers
Registers are small groups of memory cells used to configure how the S79FL01GS 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.
The S79FL01GS Dual-Quad SPI device has a register of each type, one for each individual die. These include the Status Register 1,
Status Register 2, Configuration Register, AutoBoot Register, Bank Address Register, ASP Register, Password Register, PPB Lock
Register, PPB Access Register, DYB Access Register, and DDR Data Learning Registers. Each register must be accessed by a
command given in parallel to IO0-IO3 (Quad SPI-1) and for IO4-IO7 (Quad SPI-2). Reading and writing to each of these registers
must also be done in parallel for IO0-IO3 (Quad SPI-1) and for IO4-IO7 (Quad SPI-2).
The individual register bits may be volatile, nonvolatile, or One Time Programmable (OTP). 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 nonvolatile or OTP, the default state is the value of the bit when the device is shipped from Cypress.
Nonvolatile bits have the same cycling (erase and program) endurance as the main flash array.
Table 7-3 Register Descriptions
Type
Bit Location
Status Register 1
Register
SR1[7:0]
Abbreviation
Volatile
7:0
Configuration Register 1
CR1[7:0]
Volatile
7:0
Status Register 2
SR2[7:0]
RFU
7:0
AutoBoot Register
ABRD[31:0]
Nonvolatile
31:0
Bank Address Register
BRAC[7:0]
Volatile
7:0
ECC Status Register
ECCSR[7:0]
Volatile
7:0
ASP Register
ASPR[15:1]
OTP
15:1
ASP Register
ASPR[0]
RFU
0
Password Register
PASS[63:0]
Nonvolatile OTP
63:0
PPB Lock Register
PPBL[7:1]
Volatile
7:1
PPB Lock Register
PPBL[0]
Volatile
Read Only
0
PPB Access Register
PPBAR[7:0]
Nonvolatile
7:0
DYB Access Register
DYBAR[7:0]
Volatile
7:0
SPI DDR Data Learning Registers
NVDLR[7:0]
Nonvolatile
7:0
SPI DDR Data Learning Registers
VDLR[7:0]
Volatile
7:0
Document Number: 002-00466 Rev. *G
Page 37 of 119
S79FL01GS
7.6.1
Status Register 1 (SR1)
Related Commands: Read Status Register (RDSR1 05h), Write Registers (WRR 01h), Write Enable (WREN 06h), Write Disable
(WRDI 04h), Clear Status Register (CLSR 30h).
Table 7-4 Status Register 1 (SR1)
Bits
Field
Name
Function
Type
Default
State
Description
7
SRWD
Status
Register Write
Disable
Nonvolatile
0
1 = Locks state of SRWD, BP, and configuration register
bits when WP# is low by ignoring WRR command
0 = No protection, even when WP# is low
6
P_ERR
Programming
Error Occurred
Volatile, Read only
0
1 = Error occurred.
0 = No Error
5
E_ERR
Erase Error
Occurred
Volatile, Read only
0
1 = Error occurred
0 = No Error
4
BP2
3
BP1
2
BP0
Volatile if CR1[3]=1,
Nonvolatile if
CR1[3]=0
1 if
CR1[3]=1,
0 when
shipped
from
Cypress
1
0
Block
Protection
WEL
Write Enable
Latch
WIP
Write in
Progress
Volatile
Volatile, Read only
Protects selected range of sectors (Block) from
Program or Erase
0
1 = Device accepts Write Registers (WRR), program or
erase commands
0 = Device ignores Write Registers (WRR), program or
erase commands
This bit is not affected by WRR, only WREN and WRDI
commands affect this bit
0
1 = Device Busy, a Write Registers (WRR), program,
erase or other operation is in progress
0 = Ready Device is in standby mode and can accept
commands
The Status Register contains both status and control bits:
Status Register Write Disable (SRWD) SR1[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 SRWD, BP2, BP1, and BP0 bits of the Status Register become read-only bits and the
Write Registers (WRR) command is no longer accepted for execution. If WP# is high the SRWD bit and BP bits may be changed by
the WRR command. If SRWD is 0, WP# has no effect and the SRWD bit and BP bits may be changed by the WRR command. The
SRWD bit has the same nonvolatile endurance as the main flash array.
Program Error (P_ERR) SR1[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 locked OTP region. When the Program Error bit is set to a 1 this bit
can be reset to 0 with the Clear Status Register (CLSR) command. This is a read-only bit and is not affected by the WRR command.
Erase Error (E_ERR) SR1[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 reset to 0 with the Clear Status Register (CLSR)
command. This is a read-only bit and is not affected by the WRR command.
Block Protection (BP2, BP1, BP0) SR1[4:2]: These bits define the main flash array area to be software-protected against program
and erase commands. The BP bits are either volatile or nonvolatile, depending on the state of the BP nonvolatile bit (BPNV) in the
configuration register. 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 48
for a description of how the BP bit values select the memory array area protected. The BP bits have the same nonvolatile endurance
as the main flash array.
Write Enable Latch (WEL) SR1[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
Document Number: 002-00466 Rev. *G
Page 38 of 119
S79FL01GS
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 WRR command does not affect this bit.
Write In Progress (WIP) SR1[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), Erase Suspend (ERSP), Program Suspend (PGSP), Clear Status
Register (CLSR), and Software Reset (RESET) commands may be 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.
Document Number: 002-00466 Rev. *G
Page 39 of 119
S79FL01GS
7.6.2
Configuration Register 1 (CR1)
Related Commands: Read Configuration Register (RDCR 35h), Write Registers (WRR 01h). The Configuration Register bits can be
changed using the WRR command with sixteen input cycles.
The configuration register controls certain interface and data protection functions.
Table 7-5 Configuration Register 1 (CR1)
Bits
Field Name
7
LC1
6
LC0
5
TBPROT
4
Default
State
Function
Type
Latency Code
Nonvolatile
Configures Start of
Block Protection
OTP
0
DNU
DNU
DNU
0
Do Not Use
3
BPNV
Configures BP2-0 in
Status Register
OTP
0
1 = Volatile
0 = Nonvolatile
2
RFU
RFU
RFU
0
Reserved for Future Use
Selects number of initial read latency cycles
See Latency Code Tables
1 = BP starts at bottom (Low address)
0 = BP starts at top (High address)
QUAD
Puts the device into
Quad I/O operation
Nonvolatile
1
1 = Quad
For the S79FL01GS Dual-Quad SPI device, the
default state is set for QUAD and cannot be changed.
FREEZE
Lock current state
of BP2-0 bits in
Status Register,
TBPROT in
Configuration
Register, and OTP
regions
Volatile
0
1 = Block Protection and OTP locked
0 = Block Protection and OTP unlocked
1
0
0
0
Description
Latency Code (LC) CR1[7:6]: The Latency Code selects the number of mode and dummy cycles between the end of address and
the start of read data output for all read commands.
Some read commands send 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.
Dummy cycles provide additional latency that is needed to complete the initial read access of the flash array before data can be
returned to the host system. Some read commands require additional latency cycles as the SCK frequency is increased.
The following latency code tables provide different latency settings that are configured by Cypress.
Where mode or latency (dummy) cycles are shown in the tables as a dash, that read command is not supported at the frequency
shown. Read is supported only up to 50 MHz but the same latency value is assigned in each latency code and the command may be
used when the device is operated at 50 MHz with any latency code setting. Similarly, only the Fast Read command is supported
up to 133 MHz but the same 10b latency code is used for Fast Read up to 133 MHz and for the other dual and quad read commands
up to 104 MHz. It is not necessary to change the latency code from a higher to a lower frequency when operating at lower
frequencies where a particular command is supported. The latency code values for a higher frequency can be used for accesses at
lower frequencies.
The Enhanced High Performance settings provide latency options the same or faster than additional alternate source SPI memories.
Read DDR Data Learning Pattern (DLP) bits may be placed within the dummy cycles immediately before the start of read data, if
there are 5 or more dummy cycles. See Read Memory Array Commands on page 71 for more information on the DLP.
Table 7-6 Latency Codes for SDR Enhanced High Performance
Read
Freq.
(MHz)
LC
≤ 50
≤ 80
Fast Read
(03h, 13h)
Read Quad Out
(0Bh, 0Ch)
Quad I/O Read
(6Bh, 6Ch)
(EBh, ECh)
Mode
Dummy
Mode
Dummy
Mode
Dummy
Mode
Dummy
11
0
0
0
0
0
0
2
1
00
–
–
0
8
0
8
2
4
Document Number: 002-00466 Rev. *G
Page 40 of 119
S79FL01GS
Table 7-6 Latency Codes for SDR Enhanced High Performance
Read
Fast Read
Read Quad Out
Quad I/O Read
(03h, 13h)
(0Bh, 0Ch)
(6Bh, 6Ch)
(EBh, ECh)
Freq.
(MHz)
LC
Mode
Dummy
Mode
Dummy
Mode
Dummy
Mode
Dummy
≤ 90
01
–
–
0
8
0
8
2
4
≤104
10
–
–
0
8
0
8
2
5
≤133
10
–
–
0
8
–
–
–
–
Table 7-7 Latency Codes for DDR Enhanced High Performance
DDR Quad I/O Read
Freq. (MHz)
LC
(EDh, EEh)
Mode
Dummy
≤ 50
11
1
3
≤ 80
00
1
7
Note:
1. When using DDR I/O commands with the Data Learning Pattern (DLP) enabled, a Latency Code 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. So it is recommended to use LC 00 for DDR Quad IO Read, if the
Data Learning Pattern (DLP) for DDR is used.
Top or Bottom Protection (TBPROT) CR1[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, 1/4, 1/2, etc., up to the entire array. When TBPROT is set to a 0 the Block Protection is defined to start from the
top (maximum address) of the array. When TBPROT is set to a 1 the Block Protection is defined to start from the bottom (zero
address) of the array. The TBPROT bit is OTP and set to a 0 when shipped from Cypress. If TBPROT is programmed to 1, an
attempt to change it back to 0 will fail and set the Program Error bit (P_ERR in SR1[6]).
The desired state of TBPROT 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 must not be programmed after programming or erasing is done in
the main flash array.
CR1[4]: Reserved for Future Use
Block Protection Nonvolatile (BPNV) CR1[3]: The BPNV bit defines whether or not the BP2-0 bits in the Status Register are
volatile or nonvolatile. The BPNV bit is OTP and cleared to a0 with the BP bits cleared to 000 when shipped from Cypress. When
BPNV is set to a 0 the BP2-0 bits in the Status Register are nonvolatile. When BPNV is set to a 1 the BP2-0 bits in the Status
Register are volatile and will be reset to binary 111 after POR, hardware reset, or command reset. If BPNV is programmed to 1, an
attempt to change it back to 0 will fail and set the Program Error bit (P_ERR in SR1[6]).
CR1[2]: Reserved for Future Use.
Quad Data Width (QUAD) CR1[1]: When set to 1, this bit switches the data width of the device to 4-bit Quad mode. The commands
for Serial Read still function normally. The QUAD bit in the S79FL01GS device is factory set to 1 and should not be changed.
Freeze Protection (FREEZE) CR1[0]: The Freeze Bit, when set to 1, locks the current state of the BP2-0 bits in Status Register, the
TBPROT and TBPARM bits in the Configuration Register, and the OTP address space. This prevents writing, programming, or
erasing these areas. As long as the FREEZE bit remains cleared to logic 0 the other bits of the Configuration Register, including
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 FREEZE bit is volatile and the default state of FREEZE after power-on is 0. The FREEZE bit can be set in parallel with
updating other values in CR1 by a single WRR command.
Document Number: 002-00466 Rev. *G
Page 41 of 119
S79FL01GS
7.6.3
Status Register 2 (SR2)
Related Commands: Read Status Register 2 (RDSR2 07h).
Table 7-8 Status Register 2 (SR2)
Bits
Field Name
Function
Type
Default State
7
RFU
Reserved
–
0
Reserved for Future Use
Description
6
RFU
Reserved
–
0
Reserved for Future Use
5
RFU
Reserved
–
0
Reserved for Future Use
4
RFU
Reserved
–
0
Reserved for Future Use
3
RFU
Reserved
–
0
Reserved for Future Use
2
RFU
Reserved
–
0
Reserved for Future Use
1
ES
Erase
Suspend
Volatile, Read only
0
1 = In erase suspend mode
0 = Not in erase suspend mode
0
PS
Program
Suspend
Volatile, Read only
0
1 = In program suspend mode
0 = Not in program suspend mode
Erase Suspend (ES) SR2[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. 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 Suspend and Resume Commands (75h) (7Ah) for details
about the Erase Suspend/Resume commands.
Program Suspend (PS) SR2[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. 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 Program Suspend (PGSP 85h) and
Resume (PGRS 8Ah) on page 80 for details.
7.6.4
AutoBoot Register
Related Commands: AutoBoot Read (ABRD 14h) and AutoBoot Write (ABWR 15h).
The AutoBoot Register provides a means to automatically read boot code as part of the power on reset, hardware reset, or software
reset process.
Table 7-9 AutoBoot Register
Bits
Field Name
Function
Type
Default State
Description
31 to 9
ABSA
AutoBoot Start
Address
Nonvolatile
000000h
512 byte boundary address for the start of
boot code access
8 to 1
ABSD
AutoBoot Start
Delay
Nonvolatile
00h
0
ABE
AutoBoot Enable
Nonvolatile
0
Document Number: 002-00466 Rev. *G
Number of initial delay cycles between
CS# going low and the first bit of boot
code being transferred
1 = AutoBoot is enabled
0 = AutoBoot is not enabled
Page 42 of 119
S79FL01GS
7.6.5
Bank Address Register
Related Commands: Bank Register Access (BRAC B9h), Write Register (WRR 01h), Bank Register Read (BRRD 16h) and Bank
Register Write (BRWR 17h).
The Bank Address register supplies additional high order bits of the main flash array byte boundary address for legacy commands
that supply only the low order 24 bits of address. The Bank Address is used as the high bits of address (above A23) for all 3-byte
address commands when EXTADD=0. The Bank Address is not used when EXTADD = 1 and traditional 3-byte address commands
are instead required to provide all four bytes of address.
Table 7-10 Bank Address Register (BAR)
Bits
Field Name
Function
Type
Default
State
7
EXTADD
Extended Address
Enable
Volatile
0b
6 to 2
RFU
Reserved
Volatile
00000b
1
BA25
Bank Address
Volatile
0
A25 for 1 Gb device
0
RFU
Bank Address
Volatile
0
RFU for lower density device
Description
1 = 4-byte (32-bits) addressing required from command.
0 = 3-byte (24-bits) addressing from command + Bank
Address
Reserved for Future Use
Extended Address (EXTADD) BAR[7]: EXTADD controls the address field size for legacy SPI commands. By default (power up
reset, hardware reset, and software reset), it is cleared to 0 for 3 bytes (24 bits) of address. When set to 1, the legacy commands will
require 4 bytes (32 bits) for the address field. This is a volatile bit.
Document Number: 002-00466 Rev. *G
Page 43 of 119
S79FL01GS
7.6.6
ECC Status Register (ECCSR)
Related Commands: ECC Read (ECCRD 18h). ECCSR does not have user programmable nonvolatile bits. All defined bits are
volatile read only status. The default state of these bits are set by hardware. See Automatic ECC on page 78.
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 unit eight bit error correction code, the ECC unit of 16 Bytes of data, or that ECC is disabled for that ECC unit.
Table 7-11 ECC Status Register (ECCSR)
Bits
Field
Name
Function
7 to 3
RFU
Reserved
2
EECC
Error in ECC
1
EECCD
0
ECCDI
Default
State
Type
Description
0
Reserved for Future Use
Volatile, Read only
0
1 = Single Bit Error found in the ECC unit eight bit
error correction code
0 = No error.
Error in ECC unit
data
Volatile, Read only
0
1 = Single Bit Error corrected in ECC unit data.
0 = No error.
ECC Disabled
Volatile, Read only
0
1 = ECC is disabled in the selected ECC unit.
0 = ECC is enabled in the selected ECC unit.
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.
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.
7.6.7
ASP Register (ASPR)
Related Commands: ASP Read (ASPRD 2Bh) and ASP Program (ASPP 2Fh).
The ASP register is a 16-bit OTP memory location used to permanently configure the behavior of Advanced Sector Protection (ASP)
features.
Table 7-12 ASP Register (ASPR)
Default
State
Bits
Field Name
Function
Type
Description
15 to 9
RFU
Reserved
OTP
1
Reserved for Future Use
Reserved for Future Use
8
RFU
Reserved
OTP
(Note 1)
7
RFU
Reserved
OTP
(Note 1)
Reserved for Future Use
6
RFU
Reserved
OTP
1
Reserved for Future Use
OTP
(Note 1)
Reserved for Future Use
Reserved for Future Use
Reserved for Future Use
5
RFU
Reserved
4
RFU
Reserved
OTP
(Note 1)
3
RFU
Reserved
OTP
(Note 1)
PWDMLB
Password Protection Mode
Lock Bit
1
PSTMLB
Persistent Protection Mode
Lock Bit
0
RFU
Reserved
2
1
0 = Password Protection Mode permanently
enabled
1 = Password Protection Mode not permanently
enabled
OTP
1
0 = Persistent Protection Mode permanently
enabled
1 = Persistent Protection Mode not permanently
enabled
OTP
1
Reserved for Future Use
OTP
Note:
1. Default value depends on ordering part number, see Initial Delivery State on page 114.
Reserved for Future Use (RFU) ASPR[15:3, 0].
Document Number: 002-00466 Rev. *G
Page 44 of 119
S79FL01GS
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. PWDMLB and PSTMLB are mutually exclusive, only one may be programmed to zero.
7.6.8
Password Register (PASS)
Related Commands: Password Read (PASSRD E7h) and Password Program (PASSP E8h).
Table 7-13 Password Register (PASS)
Bits
63 to 0
7.6.9
Field
Name
Function
PWD
Hidden
Password
Type
Default State
Description
OTP
FFFFFFFFFFFFFFFFh
Nonvolatile OTP storage of 64-bit password. The
password is no longer readable after the password
protection mode is selected by programming ASP register
bit 2 to zero.
PPB Lock Register (PPBL)
Related Commands: PPB Lock Read (PLBRD A7h, PLBWR A6h)
Table 7-14 PPB Lock Register (PPBL)
Bits
Field Name
Function
Type
Default State
7 to 1
RFU
Reserved
Volatile
00h
0
7.6.10
PPBLOCK
Protect PPB
Array
Volatile
Description
Reserved for Future Use
0 = PPB array protected until next power
Persistent Protection Mode = 1 cycle or hardware reset
Password Protection Mode = 0 1 = PPB array may be programmed or
erased.
PPB Access Register (PPBAR)
Related Commands: PPB Read (PPBRD E2h)
Table 7-15 PPB Access Register (PPBAR)
Bits
7 to 0
Field Name
PPB
Function
Read or Program
per sector PPB
Document Number: 002-00466 Rev. *G
Type
Nonvolatile
Default
State
Description
FFh
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
or PPBP command is erased to 1, not protecting that
sector from program or erase operations.
Page 45 of 119
S79FL01GS
7.6.11
DYB Access Register (DYBAR)
Related Commands: DYB Read (DYBRD E0h) and DYB Program (DYBP E1h).
Table 7-16 DYB Access Register (DYBAR)
Bits
7 to 0
7.6.12
Field
Name
DYB
Function
Read or Write
per sector
DYB
Type
Volatile
Default
State
Description
FFh
00h = DYB for the sector addressed by the DYBRD or DYBP
command is cleared to 0, protecting that sector from program or
erase operations.
FFh = DYB for the sector addressed by the DYBRD or DYBP
command is set to 1, not protecting that sector from program or
erase operations.
SPI DDR Data Learning Registers
Related Commands: Program NVDLR (PNVDLR 43h), Write VDLR (WVDLR 4Ah), Data Learning Pattern Read (DLPRD 41h).
The Data Learning Pattern (DLP) resides in an 8-bit Nonvolatile 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 reset or 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 IOs 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 7-17 Nonvolatile Data Learning Register (NVDLR)
Bits
7 to 0
Field
Name
Function
NVDLP
Nonvolatile
Data Learning
Pattern
Default
State
Description
00h
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.
Type
Default
State
Description
Volatile
Takes the
value of
NVDLR
during POR
or Reset
Volatile copy of the NVDLP used to enable and deliver the Data
Learning Pattern (DLP) to the outputs. The VDLP may be
changed by the host during system operation.
Type
OTP
Table 7-18 Volatile Data Learning Register (NVDLR)
Bits
7 to 0
Field
Name
Function
VDLP
Volatile Data
Learning
Pattern
Document Number: 002-00466 Rev. *G
Page 46 of 119
S79FL01GS
8.
8.1
Data Protection
Secure Silicon Region (OTP)
The device has a 2048-byte One Time Program (OTP) address space that is separate from the main flash array. The OTP area is
divided into 32, individually lockable, 64-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 35, One Time Program Array Commands on page 85, and
OTP Read (OTPR 4Bh) on page 85.
8.1.1
Reading OTP Memory Space
The OTP Read command uses the same protocol as Fast Read. OTP Read operations outside the valid 2-kB OTP address range
will yield indeterminate data.
8.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. The valid address range for OTP Program is depicted
in Figure 7-1 on page 35. OTP Program operations outside the valid OTP address range will be ignored and the WEL in SR1 will
remain high (set to 1). OTP Program operations while FREEZE = 1 will fail with P_ERR in SR1 set to 1.
8.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.
8.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 35.
8.2
Write Enable Command
The Write Enable (WREN) command must be written prior to any command that modifies nonvolatile 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)
– Sector Erase (SE)
– Bulk Erase (BE)
– Write Disable (WRDI)
– Write Registers (WRR)
– Quad-input Page Programming (QPP)
– OTP Byte Programming (OTPP)
Document Number: 002-00466 Rev. *G
Page 47 of 119
S79FL01GS
8.3
Block Protection
The Block Protect bits (Status Register bits BP2, BP1, BP0) in combination with the Configuration Register TBPROT 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 bit of the configuration register.
Table 8-1 Upper Array Start of Protection (TBPROT = 0)
Status Register Content
Protected Fraction of Memory Array
Protected Memory (kbytes)
S79FL01GS
1024 Mb
BP2
BP1
BP0
0
0
0
None
0
0
0
1
Upper 64th
2048
0
1
0
Upper 32nd
4096
0
1
1
Upper 16th
8192
1
0
0
Upper 8th
16384
1
0
1
Upper 4th
32768
1
1
0
Upper Half
65536
1
1
1
All Sectors
131072
Protected Fraction of Memory Array
Protected Memory (kbytes)
S79FL01GS
1024 Mb
Table 8-2 Lower Array Start of Protection (TBPROT = 1)
Status Register Content
BP2
BP1
BP0
0
0
0
None
0
0
0
1
Lower 64th
2048
0
1
0
Lower 32nd
4096
0
1
1
Lower 16th
8192
1
0
0
Lower 8th
16384
1
0
1
Lower 4th
32768
1
1
0
Lower Half
65536
1
1
1
All Sectors
131072
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. Recommendation: ASP and Block Protection should not be
used concurrently. Use one or the other, but not both.
8.3.1
Freeze Bit
Bit0 of the Configuration Register is the FREEZE bit. The FREEZE bit locks the BP2-0 bits in Status Register-1 and the TBPROT bit
in the Configuration Register to their value at the time the FREEZE bit is set to 1. Once the FREEZE bit has been written to a logic 1
it cannot be cleared to a logic 0 until a power-on-reset is executed. As long as the FREEZE bit is cleared to logic 0 the status register
BP bits and the TBPROT bit of the Configuration Register are writable. The FREEZE bit also protects the entire OTP memory space
from programming when set to 1. Any attempt to change the BP bits with the WRR command while FREEZE = 1 is ignored and no
error status is set.
Document Number: 002-00466 Rev. *G
Page 48 of 119
S79FL01GS
8.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. An overview of these methods is shown in Figure 8-1
on page 49.
Block Protection and ASP protection settings for each sector are logically OR’d 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 48 for full details of
the BP2-0 bits.
Figure 8-1 Advanced Sector Protection Overview
ASP Register
One Time Programmable
Password Method Persistent Method
(ASPR[2]=0)
6.) Password Method requires a
password to set PPB Lock to ‘1’
to enable program or erase of
PPB bits
(ASPR[1]=0)
7.) Persistent Method only allows
PPB Lock to be cleared to ‘0’ to
prevent program or erase of PPB
bits. Power off or hardware reset
required to set PPB Lock to ‘1’
64 -bit Password
(One Time Protect)
4.) PPB Lock bit is volatile and
defaults to ‘1’ (persistent
mode), or ‘0’ (password mode)
upon reset
PBB Lock Bit
‘0’ = PPBs locked
‘1’ =PPBs unlocked
5.) PPB Lock = ‘0’ locks all PPBs
to their current state
Persistent
Protection Bit
(PPB)
Dynamic
Protection Bit
(DYB)
Sector 0
PPB 0
DYB 0
Sector 1
PPB 1
DYB 1
Sector 2
PPB 2
DYB 2
Memory Array
Sector N -2
PPB N -2
DYB N -2
Sector N -1
PPB N -1
DYB N -1
Sector N
PPB N
DYB N
1.) N = Highest Address Sector
a sector is protected if its PPB =’0’
or its DYB = ‘0’
2.) PPB are programmed individually
but erased as a group
3.) DYB are volatile bits
Every main flash array sector has a nonvolatile (PPB) and a volatile (DYB) protection bit 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 PPB Lock bit is 0. There are two methods for managing the state of
the PPB Lock bit, Persistent Protection and Password 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.
Document Number: 002-00466 Rev. *G
Page 49 of 119
S79FL01GS
8.4.1
ASP Register
The ASP register is used to permanently configure the behavior of Advanced Sector Protection (ASP) features. See Table 7-12
on page 44.
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 = Illegal condition, attempting to program both bits 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 Protection Mode Lock Bits are permanently protected from programming and no
further changes to the ASP register is allowed.
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 (SR1) on page 38
for information on WIP.
After selecting a sector protection method, each sector can operate in each of the following states:
Dynamically Locked — A sector is protected and can be changed by a simple command.
Persistently Locked — A sector is protected and cannot be changed if its PPB Bit is 0.
Unlocked — The sector is unprotected and can be changed by a simple command.
8.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.
8.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.
Document Number: 002-00466 Rev. *G
Page 50 of 119
S79FL01GS
8.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 and when set to 1, it allows the
PPBs to be changed.
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.
8.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 after a power cycle, software reset, or hardware reset.
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 nonvolatile and saved across a power cycle or reset. Changing the protection state requires
programming and or erase of the PPB bits
Table 8-3 Sector Protection States
Protection Bit Values
Sector State
PPB Lock
PPB
DYB
1
1
1
Unprotected – PPB and DYB are changeable
1
1
0
Protected – PPB and DYB are changeable
1
0
1
Protected – PPB and DYB are changeable
1
0
0
Protected – PPB and DYB are changeable
0
1
1
Unprotected – PPB not changeable, DYB is changeable
0
1
0
Protected – PPB not changeable, DYB is changeable
0
0
1
Protected – PPB not changeable, DYB is changeable
0
0
0
Protected – PPB not changeable, DYB is changeable
8.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.
Document Number: 002-00466 Rev. *G
Page 51 of 119
S79FL01GS
8.4.7
Password Protection Mode
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 clears the PPB Lock bit, 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 and Password Read 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. 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 and the WIP Bit remains set. In this case it is a failure to
change the state of the PPB Lock bit because it is still protected by the lack of a valid password.
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.
Document Number: 002-00466 Rev. *G
Page 52 of 119
S79FL01GS
9.
Commands
All communication between the host system and the S79FL01GS memory device 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 serially between the host system and memory device.
All instructions are transferred from host to memory as a single bit serial sequence on the SI signal.
Single bit wide commands may provide an address or data sent only on the SI signal. Data may be sent back to the host serially on
SO signal.
Quad Output commands provide an address sent to the memory only on the IO0 and IO4 signal. Data will be returned to the host as
a sequence of 8-bit (byte) groups on IO0 - IO7.
Quad Input/Output (I/O) commands provide an address sent from the host as four-bit (nibble) groups on Quad SPI-1 IO0 - IO3 and
Quad SPI-2 IO4 - IO7. Data is returned to the host similarly as 8-bit (byte) groups on IO0 - IO7.
Commands are structured as follows:
Each command begins with an eight bit (byte) instruction.
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 S79FL01GS Serial Peripheral Interface with Multiple IO provides the option for each transfer of address and data
information to be done one, 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 four-bit wide IO bus the memory
performance can be increased by using the instructions that provide parallel four-bit (quad) transfers.
The width of all transfers following the instruction are determined by the instruction sent.
All single bits or parallel bit groups are transferred in most to least significant bit order.
Some instructions send instruction modifier (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.
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 11.
– The host always controls the Chip Select (CS#), Serial Clock (SCK), and Serial Input (IO0 and IO4) for single-bit wide
transfers. The memory drives the IO0-IO7 signals during 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
Document Number: 002-00466 Rev. *G
Page 53 of 119
S79FL01GS
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.
9.1
Command Set Summary
The S79FL01GS Dual-Quad SPI device contains two Quad SPI devices (Quad SPI-1 and Quad SPI-2)) 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. Quad SPI-1 device responds to commands, address, data in and data out on IO0-IO3. Quad SPI-2 device
responds to commands, address, data in and data out on IO4-IO7. All commands are executed by both devices in parallel.
Both Quad SPI devices must be configured, by writing to the various status and configuration registers in parallel, to define the same
overall sector map and behavior of both devices, selected by each CS# for the DDP.
9.1.1
Extended Addressing
To accommodate addressing above 256 Mb, there are three options:
1. New instructions are provided with 4-byte address, used to access up to 32 Gb of memory.
Instruction Name
Description
Code (Hex)
4FAST_READ
Read Fast (4-byte Address)
0C
4READ
Read (4-byte Address)
13
4QOR
Read Quad Out (4-byte Address)
6C
4QIOR
Quad I/O Read (4-byte Address)
EC
4DDRQIOR
DDR Quad I/O Read (4-byte Address)
EE
4PP
Page Program (4-byte Address)
12
4QPP
Quad Page Program (4-byte Address)
34
4SE
Erase 512 kB (4-byte Address)
DC
2. For backward compatibility to the 3-byte address instructions, the standard instructions can be used in conjunction with
the EXTADD Bit in the Bank Address Register (BAR[7]). By default BAR[7] is cleared to 0 (following power up and
hardware reset), to enable 3-byte (24-bit) addressing. When 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 EXTADD bit to switch from
3 bytes to 4 bytes of address field.
Instruction Name
Description
Code (Hex)
READ
Read (3-byte Address)
03
FAST_READ
Read Fast (3-byte Address)
0B
QOR
Read Quad Out (3-byte Address)
6B
QIOR
Quad I/O Read (3-byte Address)
EB
DDRQIOR
DDR Quad I/O Read (3-byte Address)
ED
PP
Page Program (3-byte Address)
02
QPP
Quad Page Program (3-byte Address)
32
SE
Erase 512 kB (3-byte Address)
D8
Document Number: 002-00466 Rev. *G
Page 54 of 119
S79FL01GS
3. For backward compatibility to the 3-byte addressing, the standard instructions can be used in conjunction with the Bank
Address Register:
a. The Bank Address Register is used to switch between 128-Mbit (16-Mbyte) banks of memory, The standard 3-byte
address selects an address within the bank selected by the Bank Address Register.
i. The host system writes the Bank Address Register to access beyond the first 128 Mbits of
memory.
ii. This applies to read, erase, and program commands.
b. The Bank Register provides the high order (4th) byte of address, which is used to address the available memory at
addresses greater than 16 Mbytes.
c. Bank Register bits are volatile.
i. On power up, the default is Bank0 (the lowest address 16 Mbytes).
d. For Read, the device will continuously transfer out data until the end of the array.
i. There is no bank to bank delay.
ii. The Bank Address Register is not updated.
iii. The Bank Address Register value is used only for the initial address of an access.
Bank Address Register Bits
Bank
Memory Array Address Range (Hex)
Bit 1
Bit 0
0
0
0
00000000
00FFFFFF
0
1
1
01000000
01FFFFFF
1
0
2
02000000
02FFFFFF
1
1
3
03000000
03FFFFFF
Document Number: 002-00466 Rev. *G
Page 55 of 119
S79FL01GS
Table 9-1 S79FL01GS Command Set (sorted by function)
Function
Read Device
Identification
Register Access
Maximum
Frequency
(MHz)
Read Electronic Manufacturer Signature
90
133
Read ID (JEDEC Manufacturer ID and JEDEC CFI)
9F
133
Command Description
READ_ID
(REMS)
RDID
Read Electronic Signature
AB
50
RSFDP
RES
Read Serial Flash Discoverable Parameters
5A
133
RDSR1
Read Status Register 1
05
133
RDSR2
Read Status Register 2
07
133
RDCR
Read Configuration Register 1
35
133
WRR
Write Register (Status 1, Configuration 1)
01
133
WRDI
Write Disable
04
133
WREN
Write Enable
06
133
CLSR
Clear Status Register 1 – Erase/Program Fail Reset
30
133
ABRD
AutoBoot Register Read
14
133 (QUAD=0)
104 (QUAD=1)
ABWR
AutoBoot Register Write
15
133
BRRD
Bank Register Read
16
133
BRWR
Bank Register Write
17
133
BRAC
Bank Register Access
(Legacy Command formerly used for Deep Power
Down)
B9
133
DLPRD
Read Flash Array
Instructio
n Value
(Hex)
Command
Name
Data Learning Pattern Read
41
133
PNVDLR
Program NV Data Learning Register
43
133
WVDLR
Write Volatile Data Learning Register
4A
133
READ
Read (3- or 4-byte address)
03
50
4READ
Read (4-byte address)
13
50
FAST_READ
Fast Read (3- or 4-byte address)
0B
133
4FAST_READ
Fast Read (4-byte address)
0C
133
Read Quad Out (3- or 4-byte address)
6B
104
QOR
4QOR
Read Quad Out (4-byte address)
6C
104
QIOR
Quad I/O Read (3- or 4-byte address)
EB
104
4QIOR
Quad I/O Read (4-byte address)
EC
104
DDRQIOR
DDR Quad I/O Read (3- or 4-byte address)
ED
80
4DDRQIOR
DDR Quad I/O Read (4-byte address)
EE
80
Document Number: 002-00466 Rev. *G
Page 56 of 119
S79FL01GS
Table 9-1 S79FL01GS Command Set (sorted by function) (Continued)
Function
Program Flash Array
Erase Flash Array
One Time Program
Array
Command
Name
Instructio
n Value
(Hex)
Maximum
Frequency
(MHz)
PP
Page Program (3- or 4-byte address)
02
133
4PP
Page Program (4-byte address)
12
133
QPP
Quad Page Program (3- or 4-byte address)
32
80
QPP
Quad Page Program - Alternate instruction (3- or 4-byte
address)
38
80
4QPP
Quad Page Program (4-byte address)
34
80
PGSP
Program Suspend
85
133
PGRS
Program Resume
8A
133
BE
Bulk Erase
60
133
BE
Bulk Erase (alternate command)
C7
133
SE
Erase 512 kB (3- or 4-byte address)
D8
133
4SE
Erase 512 kB (4-byte address)
DC
133
ERSP
Erase Suspend
75
133
ERRS
Erase Resume
7A
133
OTPP
OTP Program
42
133
OTPR
OTP Read
4B
133
DYBRD
DYB Read
E0
133
DYBWR
DYB Write
E1
133
PPBRD
Advanced Sector
Protection
Command Description
PPB Read
E2
133
PPBP
PPB Program
E3
133
PPBE
PPB Erase
E4
133
ASPRD
ASP Read
2B
133
ASP Program
2F
133
PLBRD
ASPP
PPB Lock Bit Read
A7
133
PLBWR
PPB Lock Bit Write
A6
133
PASSRD
Password Read
E7
133
PASSP
Password Program
E8
133
PASSU
Password Unlock
E9
133
RESET
Software Reset
F0
133
MBR
Mode Bit Reset
FF
133
Reserved for Future
Use
MPM
Reserved for Multi-I/O-High Performance Mode (MPM)
A3
133
RFU
Reserved-18
Reserved
18
–
RFU
Reserved-E5
Reserved
E5
–
RFU
Reserved-E6
Reserved
E6
–
Reset
9.1.2
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 S79FL01GS
device supports the three most common device information commands.
Document Number: 002-00466 Rev. *G
Page 57 of 119
S79FL01GS
9.1.3
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 nonvolatile bits. Nonvolatile bits in registers are
automatically erased and programmed as a single (write) operation.
9.1.3.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 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. Under this condition, only the CLSR, WRDI, RDSR1, RDSR2, and software RESET commands are valid
commands. A Clear Status Register (CLSR) followed by a Write Disable (WRDI) command must be sent to return the device to
standby state. CLSR clears the WIP, P_ERR, and E_ERR bits. WRDI clears the WEL bit. Alternatively, Hardware Reset, or Software
Reset (RESET) may be used to return the device to standby state.
9.1.3.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.
9.1.4
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.
There are several different read commands to specify different access latency and data path widths. Double Data Rate (DDR)
commands also define the address and data bit relationship to both SCK edges:
The Read command provides a single address bit per SCK rising edge on the IO0 and IO4 signal with read data returning
a single bit per SCK falling edge on the IO1 and IO5 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 the configuration register latency code.
The Fast Read command provides a single address bit per SCK rising edge on the IO0 and IO4 signal with read data
returning a single bit per SCK falling edge on the IO1 and IO5 signal and may operate up to 133 MHz.
Quad Output read commands provide address a single bit per SCK rising edge on the IO0 and IO4 signal with read data
returning four bits of data per SCK falling edge on the IO0- IO7 signals.
Quad I/O Read commands provide address four bits per SCK rising edge with read data returning four bits of data per SCK
falling edge on the IO0-IO7 signals.
Quad Double Data Rate read commands provide address four bits per every SCK edge with read data returning eight bits
of data per every SCK edge on the IO0-IO7 signals. Double Data Rate (DDR) operation is only supported for core and I/O
voltages of 3 to 3.6V.
9.1.5
Program Flash Array
Programming data requires two commands: Write Enable (WREN), and Page Program (PP or QPP). The Page Program command
accepts from 1 byte up to 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.
9.1.6
Erase Flash Array
The Sector Erase (SE) and Bulk Erase (BE) 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 (SE) or array-wide (BE) level.
9.1.7
OTP, Block Protection, and Advanced Sector Protection
There are commands to read and program a separate One Time Programmable (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
Document Number: 002-00466 Rev. *G
Page 58 of 119
S79FL01GS
and erase operations. There are commands to control which individual flash memory array sectors are protected from program and
erase operations.
9.1.8
Reset
There is a command to reset to the default conditions present after power on to the device. There is a command to reset (exit from)
the Enhanced Performance Read Modes.
9.1.9
Reserved
Some instructions are reserved for future use. In this generation of the S79FL01GS 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 affect. This allows
legacy software to issue some commands that are not relevant for the current generation S79FL01GS device with the assurance
these commands do not cause some unexpected action.
Some commands are reserved for use in special versions of the FL-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.
Document Number: 002-00466 Rev. *G
Page 59 of 119
S79FL01GS
9.2
9.2.1
Identification Commands
Read Identification — REMS (Read_ID or REMS 90h)
The READ_ID command identifies the Device Manufacturer ID and the Device ID. The command is also referred to as Read
Electronic Manufacturer and device Signature (REMS). READ-ID (REMS) is only supported for backward compatibility and should
not be used for new software designs. New software designs should instead make use of the RDID command.
The command is initiated by shifting on SI the instruction code “90h” followed by a 24-bit address of 00000h. Following this, the
Manufacturer ID and the Device ID are shifted out on SO starting at the falling edge of SCK after address. The Manufacturer ID and
the Device ID are always shifted out with the MSB first. If the 24-bit address is set to 000001h, then the Device ID is read out first
followed by the Manufacturer ID. The Manufacturer ID and Device ID output data toggles between address 000000H and 000001H
until terminated by a low to high transition on CS# input. The maximum clock frequency for the READ_ID command is 133 MHz.
For the Dual-Quad SPI device the Read Identification (REMS) instruction and data read is only done on Quad SPI-1 using IO0 and
IO1.
Figure 9-1 READ_ID (90h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
IO1
Phase
2
1
0
7
Instruction
6
5
4
3
2
1
Manufacture ID
0
7
6
5
4
3
2
1
0
Device ID
Table 9-2 Read_ID Values
9.2.2
Device
Manufacturer ID (hex)
Device ID (hex)
S79FL01GS
01
21
Read Identification (RDID 9Fh)
The Read Identification (RDID) command provides read access to manufacturer identification, device identification, 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 deviceindependent, 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 ID-CFI Address Space on page 34 for the detail description of the IDCFI 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.
For the S79FL01GS Dual-Quad SPI device, the Read Identification (RDID) instruction and data read is only done on Quad SPI-1
using IO0 and IO1. The maximum clock frequency for the RDID command is 133 MHz.
Document Number: 002-00466 Rev. *G
Page 60 of 119
S79FL01GS
Figure 9-2 Read Identification (RDID 9Fh) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
IO1
7
Phase
9.2.3
0
6
5
Instruction
4
3
2
1
0
7
6
5
Data 1
4
3
2
1
0
Data N
Read Electronic Signature (RES) (ABh)
The RES command is used to read a single byte Electronic Signature from SO. RES is only supported for backward compatibility
and should not be used for new software designs. New software designs should instead make use of the RDID command.
The RES instruction is shifted in followed by three dummy bytes onto SI. After the last bit of the three dummy bytes are shifted into
the device, a byte of Electronic Signature will be shifted out of SO. Each bit is shifted out by the falling edge of SCK. The maximum
clock frequency for the RES command is 50 MHz.
The Electronic Signature can be read repeatedly by applying multiples of eight clock cycles.
The RES command sequence is terminated by driving CS# to the logic high state anytime during data output.
For the S79FL01GS Dual-Quad SPI device, the Read Electronic Signature (RES) instruction and data read is only done on Quad
SPI-1 using IO0 and IO1.
Figure 9-3 Read Electronic Signature (RES ABh) Command Sequence
CS#
SCK
IO0
7 6 5 4 3 2 1 0 23
1 0
IO1
7 6 5 4 3 2 1 0
Phase
Instruction (ABh)
Device ID
Dummy
Table 9-3 RES Values
9.2.4
Device
Device ID (hex)
S79FL01GS
21
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 eight
dummy cycles. The SFDP bytes are then shifted out on SO starting at the falling edge of SCK after the eight 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 maximum
clock frequency for the RSFDP command is 133 MHz.
For the S79FL01GS Dual-Quad device the Read Serial Flash Discoverable Parameters (RSFDP) instruction and data read is only
done on Quad SPI-1 using IO0 and IO1.
Figure 9-4 RSFDP Command Sequence
CS#
SCK
IO0
7
6
5
4 3
2
1 0 23
1 0
IO1
Phase
7 6
Instruction
Document Number: 002-00466 Rev. *G
Address
Dummy Cycles
5
4 3
Data 1
2 1
0
Page 61 of 119
S79FL01GS
9.3
9.3.1
Register Access Commands
Read Status Register 1 (RDSR1 05h)
The Read Status Register 1 (RDSR1) command allows the Status Register 1 contents of Quad SPI-1 to be read from IO1 and Quad
SPI-2 to be read from IO5. The Status Register 1 contents may be read at any time, even while a program, erase, or write operation
is in progress. It is possible to read the Status Register 1 continuously by providing multiples of eight clock cycles. The status is
updated for each eight cycle read. The maximum clock frequency for the RDSR1 (05h) command is 133 MHz.
Figure 9-5 Dual-Quad Read Status Register 1 (RDSR1 05h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
1
0
IO5
IO6-IO7
Phase
9.3.2
Instruction
Status
Updated Status
Read Status Register 2 (RDSR2 07h)
The Read Status Register 2 (RDSR2) command allows the Status Register 2 contents of Quad SPI-1 to be read from IO1 and Quad
SPI-2 to be read from IO5. The Status Register 2 contents may be read at any time, even while a program, erase, or write operation
is in progress. It is possible to read the Status Register 2 continuously by providing multiples of eight clock cycles. The status is
updated for each eight cycle read. The maximum clock frequency for the RDSR2 command is 133 MHz.
Figure 9-6 Dual-Quad Read Status Register 2 (RDSR2 07h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
IO5
1
0
IO6-IO7
Phase
Instruction
Document Number: 002-00466 Rev. *G
Status
Updated Status
Page 62 of 119
S79FL01GS
9.3.3
Read Configuration Register (RDCR 35h)
The Read Configuration Register (RDCR) command allows the Configuration Register contents of Quad SPI-1 to be read from IO1
and Quad SPI-2 to be read from IO5. It is possible to read the Configuration Register continuously by providing multiples of eight
clock cycles. The Configuration Register contents may be read at any time, even while a program, erase, or write operation is in
progress.
Figure 9-7 Dual-Quad Read Configuration Register (RDCR 35h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
1
0
IO5
IO6-IO7
Phase
9.3.4
Instruction
Register Read
Repeat Register Read
Bank Register Read (BRRD 16h)
The Read the Bank Register (BRRD) command allows the Bank address Register contents to be read from SO. The instruction is
first shifted in from SI. Then the 8-bit Bank Register is shifted out on SO. It is possible to read the Bank Register continuously by
providing multiples of eight clock cycles. The maximum operating clock frequency for the BRRD command is 133 MHz.
Figure 9-8 Read Bank Register (BRRD 16h) Command
CS#
SCK
IO0
7
6
5
4
3
2
1
0
IO1
IO4
7
6
5
4
3
IO5
Phase
Instruction
Document Number: 002-00466 Rev. *G
2
1
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
0
Register Read
Repeat Register Read
Page 63 of 119
S79FL01GS
9.3.5
Bank Register Write (BRWR 17h)
The Bank Register Write (BRWR) command is used to write address bits above A23, into the Bank Address Register (BAR). The
command is also used to write the Extended address control bit (EXTADD) that is also in BAR[7]. BAR provides the high order
addresses needed by devices having more than 128 Mbits (16 Mbytes), when using 3-byte address commands without extended
addressing enabled (BAR[7] EXTADD = 0). Because this command is part of the addressing method and is not changing data in the
flash memory, this command does not require the WREN command to precede it.
The BRWR instruction is entered, followed by the data byte on SI. The Bank Register is one data byte in length.
The BRWR command has no effect on the P_ERR, E_ERR or WIP bits of the Status and Configuration Registers. Any bank address
bit reserved for the future should always be written as a 0.
Figure 9-9 Bank Register Write (BRWR 17h) Command
CS#
SCK
SI_IO0
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
SO_IO1-IO3
IO4
IO5-IO7
Phase
9.3.6
Instruction
Input Data
Bank Register Access (BRAC B9h)
The Bank Register Read and Write commands provide full access to the Bank Address Register (BAR) but they are both commands
that are not present in legacy SPI memory devices. Host system SPI memory controller interfaces may not be able to easily support
such new commands. The Bank Register Access (BRAC) command uses the same command code and format as the Deep Power
Down (DPD) command that is available in legacy SPI memories. The FL-S family does not support a DPD feature but assigns this
legacy command code to the BRAC command to enable write access to the Bank Address Register for legacy systems that are able
to send the legacy DPD (B9h) command.
When the BRAC command is sent, the S79FL-S family device will then interpret an immediately following Write Register (WRR)
command as a write to the lower address bits of the BAR. A WREN command is not used between the BRAC and WRR commands.
Only the lower two bits of the first data byte following the WRR command code are used to load BAR[1:0]. The upper bits of that byte
and the content of the optional WRR command second data byte are ignored. Following the WRR command the access to BAR is
closed and the device interface returns to the standby state. The combined BRAC followed by WRR command sequence has no
affect on the value of the ExtAdd bit (BAR[7]).
Commands other than WRR may immediately follow BRAC and execute normally. However, any command other than WRR, or any
other sequence in which CS# goes low and returns high, following a BRAC command, will close the access to BAR and return to the
normal interpretation of a WRR command as a write to Status Register 1 and the Configuration Register.
The BRAC + WRR sequence is allowed only when the device is in standby, program suspend, or erase suspend states. This
command sequence is illegal when the device is performing an embedded algorithm or when the program (P_ERR) or erase
(E_ERR) status bits are set to 1.
Figure 9-10 BRAC (B9h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO 3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Page 64 of 119
S79FL01GS
9.3.7
Write Registers (WRR 01h)
The Write Registers (WRR) command allows new values to be written to both the Status Register 1 and Configuration Register.
Before the Write Registers (WRR) command can be accepted by the device, a Write Enable (WREN) command must be received.
After the Write Enable (WREN) command has been decoded successfully, the device will set the Write Enable Latch (WEL) in the
Status Register to enable any write operations.
The Write Registers (WRR) command is entered by shifting the instruction and the data bytes for Quad SPI-1 on IO0 and for Quad
SPI-2 on IO4. The Status Register is one data byte in length.
The Write Registers (WRR) command will set the P_ERR or E_ERR bits if there is a failure in the WRR operation. Any Status or
Configuration Register bit reserved for the future must be written as a 0.
CS# must be driven to the logic high state after the eighth or sixteenth bit of data has been latched. If not, the Write Registers (WRR)
command is not executed. If CS# is driven high after the eighth cycle then only the Status Register 1 is written; otherwise, after the
sixteenth cycle both the Status and Configuration Registers are written. When the configuration register QUAD bit CR[1] is 1, only
the WRR command format with 16 data bits may be used.
As soon as CS# is driven to the logic high state, the self-timed Write Registers (WRR) operation is initiated. While the Write
Registers (WRR) 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 Write Registers (WRR) operation, and is a 0 when it is completed. When
the Write Registers (WRR) operation is completed, the Write Enable Latch (WEL) is set to a 0. The maximum clock frequency for the
WRR command is 133 MHz.
Figure 9-11 Dual-Quad Write Registers
CS#
SCK
IO0
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
SO_IO1-IO3
IO4
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
IO5-IO7
Phase
Instruction
Input Status Register-1
Figure 9-12 Dual-Quad Write Registers (WRR 01h) Command Sequence
CS#
SCK
IO0
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
SO_IO1-IO3
IO4
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
IO5-IO7
Phase
Instruction
Input Status Register-1
Input Conf Register-1
The Write Registers (WRR) command allows the user to change the values of the Block Protect (BP2, BP1, and BP0) bits to define
the size of the area that is to be treated as read-only. The Write Registers (WRR) command also allows the user to set the Status
Register Write Disable (SRWD) bit to a 1 or a 0. The Status Register Write Disable (SRWD) bit allows the BP bits to be hardware
protected.
When the Status Register Write Disable (SRWD) bit of the Status Register is a 0 (its initial delivery state), it is possible to write to the
Status Register provided that the Write Enable Latch (WEL) bit has previously been set by a Write Enable (WREN) command.
The WRR command has an alternate function of loading the Bank Address Register if the command immediately follows a BRAC
command. See Bank Register Access (BRAC B9h) on page 64.
Document Number: 002-00466 Rev. *G
Page 65 of 119
S79FL01GS
9.3.8
Write Enable (WREN 06h)
The Write Enable (WREN) command sets the Write Enable Latch (WEL) bit of the Status Register 1 (SR1[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 IO0 for Quad SPI-1 and
IO4 for Quad SPI-2. Without CS# being driven to the logic high state after the eighth bit of the instruction byte has been latched in on
IO0 for Quad SPI-1 and IO4 for Quad SPI-2, the write enable operation will not be executed.
Figure 9-13 Dual-Quad Write Enable (WREN 06h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
9.3.9
Instruction
Write Disable (WRDI 04h)
The Write Disable (WRDI) command sets the Write Enable Latch (WEL) bit of the Status Register 1 (SR1[1]) to a 0.
The Write Enable Latch (WEL) bit may be set to a 0 by issuing the Write Disable (WRDI) command to disable Page Program (PP),
Sector Erase (SE), Bulk Erase (BE), Write Registers (WRR), 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 IO0 for Quad SPI-1 and
IO4 for Quad SPI-2. Without CS# being driven to the logic high state after the eighth bit of the instruction byte has been latched in on
IO0 for Quad SPI-1 and IO4 for Quad SPI-2, the write disable operation will not be executed.
Figure 9-14 Dual-Quad Write Disable (WRDI 04h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Page 66 of 119
S79FL01GS
9.3.10
Clear Status Register (CLSR 30h)
The Clear Status Register command resets bit SR1[5] (Erase Fail Flag) and bit SR1[6] (Program Fail Flag). It is not necessary to set
the WEL bit before the Clear SR command is executed. The Clear SR 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.
Figure 9-15 Dual-Quad Clear Status Register (CLSR 30h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
9.3.11
Instruction
ECC Status Register Read (ECCRD 18h)
To read the ECC Status Register, the command is followed by the ECC unit (32 bit) address, the four least significant bits (LSB) of
address must be set to zero. This is followed by eight dummy cycles. 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, this continues until CS# goes high. The maximum operating clock
frequency for the ECC READ command is 133 MHz. See Automatic ECC on page 78 for details on ECC unit.
Figure 9-16 ECC Status Register Read Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0 31
1
0
IO1
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO2-IO3
IO4
7
6
5
4
3
2
1
0 31
1
0
IO5
IO6-IO7
Phase
Instruction
Address
Dummy Cycles
Data Out
Note:
1. Data Out for Quad SPI-1 is IO1, Quad SPI-2 is IO5.
Document Number: 002-00466 Rev. *G
Page 67 of 119
S79FL01GS
9.3.12
AutoBoot
SPI devices normally require 32 or more cycles of command and address shifting to initiate a read command. And, in order to read
boot code from an SPI device, the host memory controller or processor must supply the read command from a hardwired state
machine or from some host processor internal ROM code.
Parallel NOR devices need only an initial address, supplied in parallel in a single cycle, and initial access time to start reading boot
code.
The AutoBoot feature allows the host memory controller to take boot code from a S79FL01GS device immediately after the end of
reset, without having to send a read command. This saves 32 or more cycles and simplifies the logic needed to initiate the reading
of boot code.
As part of the power up reset, hardware reset, or command reset process the AutoBoot feature automatically starts a read
access from a prespecified address. At the time the reset process is completed, the device is ready to deliver code from the
starting address. The host memory controller only needs to drive CS# signal from high to low and begin toggling the SCK
signal. The S79FL01GS device will delay code output for a prespecified number of clock cycles before code streams out.
– The Auto Boot Start Delay (ABSD) field of the AutoBoot register specifies the initial delay if any is needed by the host.
– The host cannot send commands during this time.
– If ABSD = 0, the maximum SCK frequency is 50 MHz.
– If ABSD > 0, the maximum SCK frequency is 133 MHz if the QUAD bit CR1[1] is 0 or 104 MHz if the QUAD bit is 1.
The starting address of the boot code is selected by the value programmed into the AutoBoot Start Address (ABSA) field of
the AutoBoot Register which specifies a 512 byte boundary aligned location; the default address is 00000000h.
– Data will continuously shift out until CS# returns high.
At any point after the first data byte is transferred, when CS# returns high, the SPI device will reset to standard SPI mode;
able to accept normal command operations.
– A minimum of one byte must be transferred.
– AutoBoot mode will not initiate again until another power cycle or a reset occurs.
An AutoBoot Enable bit (ABE) is set to enable the AutoBoot feature.
The AutoBoot register bits are nonvolatile and provide:
The starting address (512-byte boundary), set by the AutoBoot Start Address (ABSA). The size of the ABSA field is 23 bits
for devices up to 32-Gbit.
The number of initial delay cycles, set by the AutoBoot Start Delay (ABSD) 8-bit count value.
The AutoBoot Enable.
With the configuration register QUAD bit CR1[1] is set to 1, the boot code will be provided 4 bits per cycle in the same manner as a
Read Quad Out command.
Figure 9-17 AutoBoot Sequence (CR1[1]=1)
CS#
SCK
IO0
0 4 0 4 0 4 0 4
IO1
1 5 1 5 1 5 1 5
IO2
2 6 2 6 2 6 2 6
IO3
3 7 3 7 3 7 3 7
IO4
4 0 4 0 4 0 4 0
IO5
5 1 5 1 5 1 5 1
IO6
6 2 6 2 6 2 6 2
IO7
Phase
Document Number: 002-00466 Rev. *G
7 3 7 3 7 3 7 3
Wait States (ABSD)
D1 D2 D3 D4 D5 D6 D7 ...
Page 68 of 119
S79FL01GS
9.3.13
AutoBoot Register Read (ABRD 14h)
The AutoBoot Register Read command is shifted into SI. Then the 32-bit AutoBoot Register is shifted out on SO, least significant
byte first, most significant bit of each byte first. It is possible to read the AutoBoot Register continuously by providing multiples of 32
clock cycles. The maximum operating clock frequency for ABRD command is 104 MHz.
Figure 9-18 AutoBoot Register Read (ABRD 14h) Command
CS#
SCK
SI_IO0
7
6
5
4
3
2
1
0
SO_IO1
IO4
7
6
5
4
3
2
1
9.3.14
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
0
IO5
Phase
7
Instruction
Data 1
Data N
AutoBoot Register Write (ABWR 15h)
Before the ABWR command can be accepted, 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 ABWR command is entered by shifting the instruction and the data bytes on SI, least significant byte first, most significant bit of
each byte first. The ABWR data is 32 bits in length.
The ABWR command has status reported in Status Register 1 as both an erase and a programming operation. An E_ERR or a
P_ERR may be set depending on whether the erase or programming phase of updating the register fails.
CS# must be driven to the logic high state after the 32nd bit of data has been latched. If not, the ABWR command is not executed.
As soon as CS# is driven to the logic high state, the self-timed ABWR operation is initiated. While the ABWR operation is in
progress, Status Register 1 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 ABWR operation, and is a 0. when it is completed. When the ABWR cycle is completed, the Write Enable Latch
(WEL) is set to a 0. The maximum clock frequency for the ABWR command is 133 MHz.
Figure 9-19 AutoBoot Register Write (ABWR) Command
CS#
SCK
SI_IO0
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
SO_IO1-IO3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Input Data 1
Page 69 of 119
S79FL01GS
9.3.15
Program NVDLR (PNVDLR 43h)
Before the Program NVDLR (PNVDLR) 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 the PNVDLR operation.
The PNVDLR command is entered by shifting the instruction and the data byte on SI-IO0 for Quad SPI-1 and IO4 for Quad SPI-2.
CS# must be driven to the logic high state after the eighth (8th) bit of data has been latched. If not, the PNVDLR command is not
executed. As soon as CS# is driven to the logic high state, the self-timed PNVDLR operation is initiated. While the PNVDLR
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 PNVDLR cycle, and is a 0. when it is completed. The PNVDLR operation can report a
program error in the P_ERR bit of the status register. When the PNVDLR operation is completed, the Write Enable Latch (WEL) is
set to a 0 The maximum clock frequency for the PNVDLR command is 133 MHz.
Figure 9-20 Program NVDLR (PNVDLR 43h) Command Sequence
CS#
SCK
SI_IO0
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
SO_IO1-IO3
IO4
IO5-IO7
Phase
9.3.16
Instruction
Input Data
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-IO0 for Quad SPI-1 and IO4 for Quad SPI-2.
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.
Figure 9-21 Write VDLR (WVDLR 4Ah) Command Sequence
CS#
SCK
SI_IO0
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
SO_IO1-IO3
IO4
IO5-IO 7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Input Data
Page 70 of 119
S79FL01GS
9.3.17
Data Learning Pattern Read (DLPRD 41h)
The instruction is shifted on SI_IO0, then the 8-bit DLP is shifted out on SO_IO1 and IO5. 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.
Figure 9-22 Dual-Quad DLP Read (DLPRD 41h) Command Sequence
CS#
SCK
SI_IO0
7
6
5
4
3
2
1
0
SO_IO1
IO4
7
6
5
4
3
IO5
Phase
9.4
2
1
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
0
Instruction
Data 1
Data N
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 Single Data Rate commands
(SDR).
Some SDR commands transfer address one bit per rising edge of SCK and return data 2, or 8 bits of data per rising edge of
SCK. These are called Read or Fast Read for 2-bit data; Quad Output for 8-bit data.
Some SDR commands transfer both address and data 8 bits per rising edge of SCK. These are called Quad I/O for 8 bit.
Some commands transfer address and data on both the rising edge and falling edge of SCK. These are called Double Data
Rate (DDR) commands.
There are DDR commands for 1, or 4 bits of address per each die or 8 bit data per SCK edge. These are called Fast DDR
for 1-bit, and Quad I/O DDR for 8-bit per edge transfer.
All of these commands begin with an instruction code that is transferred one bit 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 4-bits per clock edge per die are
called Multiple I/O (MIO) commands. For FL-S devices at 256 Mbits or higher density, the traditional SPI 3-byte addresses are
unable to directly address all locations in the memory array. These device have a bank address register that is used with 3-byte
address commands to supply the high order address bits beyond the address from the host system. The default bank address is
zero. Commands are provided to load and read the bank address register. These devices may also 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 External Address (EXTADD) bit in the bank address register to 1.
The Quad I/O 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 I/O read accesses.
Some commands require delay cycles following the address or mode bits to allow time to access the memory array. The delay
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 1 (CR1) Latency Code (LC). 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.
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.
Document Number: 002-00466 Rev. *G
Page 71 of 119
S79FL01GS
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 enhanced high performance read mode.
9.4.1
Read (Read 03h or 4READ 13h)
The instruction
03h (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
03h (ExtAdd=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 IO1 and IO5. 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.
Figure 9-23 Dual-Quad Read Command Sequence (READ 03h or 13h)
CS#
SCK
IO0
7
6
5
4
3
2
1
0
A
1
0
IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
1
0
A
1
0
IO5
IO6-IO7
Phase
Instruction
Address
Data 1
Data N
Note:
1. A = MSB of address = 23 for command 03h, or 31 for command 13h.
9.4.2
Fast Read (FAST_READ 0Bh or 4FAST_READ 0Ch)
The instruction
0Bh (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
0Bh (ExtAdd=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 zero or eight dummy cycles depending on the latency code set in the Configuration Register. The dummy
cycles allow the device internal circuits additional time for accessing the initial address location. During the dummy cycles the data
value on IO1 and IO5 is ‘don’t care’ and may be high impedance. Then the memory contents, at the address given, are shifted out
on IO1 and IO5.
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.
Document Number: 002-00466 Rev. *G
Page 72 of 119
S79FL01GS
Figure 9-24 Dual-Quad SPI Fast Read (FAST_READ) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0 31
1
0
IO1
3
2
1
0
3
2
1
0
7
6
5
4
7
6
5
4
IO2-IO3
IO4
7
6
5
4
3
2
1
0 31
1
0
IO5
IO6-IO7
Phase
9.4.3
Instruction
Address
Dummy Cycles
Data 1
Data 2
Quad Output Read (QOR 6Bh or 4QOR 6Ch)
The instruction
6Bh (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
6Bh (ExtAdd=1) is followed by a 4-byte address (A31-A0) or
6Ch is followed by a 4-byte address (A31-A0)
Then the memory contents, at the address given, is shifted out eight bits at a time through IO0-IO7. Each nibble (4 bits) is shifted out
at the SCK frequency by the falling edge of the SCK signal.
The maximum operating clock frequency for Quad Output Read command is 104 MHz. For Quad Output Read Mode, there may be
dummy cycles required after the last address bit is shifted into SI before data begins shifting out of IO0-IO3. This latency period (i.e.,
dummy cycles) allows the device’s internal circuitry enough time to set up for the initial address. During the dummy cycles, the data
value on IO0-IO7 is ‘don’t care’ and may be high impedance. The number of dummy cycles is determined by the frequency of SCK
(refer to Table 7-6 on page 40).
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.
Figure 9-25 Dual-Quad, Quad Output Read (QOR 6Bh or 4QOR 6Ch) Command Sequence
CS#
SCK
IO0
0
0
0
0
0
IO1
1
1
1
1
1
IO2
2
2
2
2
2
IO3
3
3
3
3
3
4
4
4
4
4
IO5
5
5
5
5
5
IO6
6
6
6
6
6
IO7
7
7
7
7
7
IO4
Phase
7
7
6
6
5
4
5
4
3
3
2
2
Instruction
1
1
0
0
A
1
A
1
Address
0
0
Dummy
D1 D2 D3 D4 D5
Note:
1. A = MSB of address = 23 for command 6Bh, or 31 for command 6Ch.
Document Number: 002-00466 Rev. *G
Page 73 of 119
S79FL01GS
9.4.4
Quad I/O Read (QIOR EBh or 4QIOR ECh)
The instruction
EBh (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
EBh (ExtAdd=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 eight I/O signals — IO0–IO7. It is similar to the Quad Output Read
command but allows input of the address bits eight bits per serial SCK clock. In some applications, the reduced instruction overhead
might allow for code execution (XIP) directly from the S79FL01GS device.
The maximum operating clock frequency for Quad I/O Read is 104 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–IO7. 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-IO7 are ‘don’t care’ and may be high impedance. The number of dummy
cycles is determined by the frequency of SCK and the latency code table (refer to Table 7-6 on page 40). The number of dummy
cycles is set by the LC bits in the Configuration Register (CR1). However, both latency code tables use the same latency values for
the Quad I/O Read command.
Following the latency period, the memory contents at the address given, is shifted out eight bits at a time through IO0–IO7. Each
byte (8 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.
Address jumps can be done without the need for additional Quad I/O Read instructions. This is controlled through the setting of the
Mode bits (after the address sequence, as shown in Figure 9-26 on page 75 or Figure 9-27 on page 75). This added feature
removes the need for the instruction sequence and greatly improves code execution (XIP). The upper nibble (bits 7-4) of the Mode
bits control the length of the next Quad I/O instruction through the inclusion or exclusion of the first byte instruction code. The lower
nibble (bits 3-0) of the Mode bits are ‘don’t care’ (x). If the Mode bits equal Axh, then the device remains in Quad I/O High
Performance Read Mode and the next address can be entered (after CS# is raised high and then asserted low) without requiring the
EBh or ECh instruction, as shown in Figure 9-26 on page 75; thus, eliminating eight cycles for the command sequence. The
following sequences will release the device from Quad I/O High Performance Read mode; after which, the device can accept
standard SPI commands:
1. During the Quad I/O Read Command Sequence, if the Mode bits are any value other than Axh, then the next time CS# is
raised high the device will be released from Quad I/O High Performance Read mode.
During any operation, if CS# toggles high to low to high for eight cycles (or less) and data input (IO0-IO3) are not set for a valid
instruction sequence, then the device will be released from Quad I/O High Performance Read mode. Note that the two mode bit
clock cycles and 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–IO7 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–IO7 signal contention, for the host system to turn off the IO0-IO7 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.
Document Number: 002-00466 Rev. *G
Page 74 of 119
S79FL01GS
Figure 9-26 Dual-Quad I/O Read Command Sequence (3-Byte Address, EBh [ExtAdd=0], LC=00b)
CS#
SCK
IO0
7
0 A-3
4
0
4
0
0
0
0
0
IO1
A-2
5
1
5
1
1
1
1
1
IO2
A-1
6
2
6
2
2
2
2
2
IO3
A
7
3
7
3
3
3
3
3
0 A-3
4
0
4
0
4
4
4
4
IO5
A-2
5
1
5
1
5
5
5
5
IO6
A-1
6
2
6
2
6
6
6
6
IO7
A
7
3
7
3
7
7
7
7
IO4
7
6
6
Phase
5
5
4
4
3
2
3
2
1
1
Instruction
Address
Mode
Dummy
D1 D2 D3 D4
Note:
1. A = MSB of address = 23 for command EBh, or 31 for command ECh.
Figure 9-27 Dual-Quad Continuous Quad I/O Read Command Sequence (3-Byte Address), LC=00b
CS#
SCK
IO0
0
0
A-3
4
0
4
0
0
0
0
0
IO1
1
1
A-2
5
1
5
1
1
1
1
1
IO2
2
2
A-1
6
2
6
2
2
2
2
2
IO3
3
3
A
7
3
7
3
3
3
3
3
IO4
4
4
A-3
4
0
4
0
4
4
4
4
IO5
5
5
A-2
5
1
5
1
5
5
5
5
IO6
6
6
A-1
6
2
6
2
6
6
6
6
IO7
7
7
A
7
3
7
3
7
7
7
7
D1
D2
D3
D4
Phase
DN-1 DN
Address
Mode
Dummy
Note:
1. A = MSB of address = 23 for command EBh, or 31 for command ECh.
Document Number: 002-00466 Rev. *G
Page 75 of 119
S79FL01GS
9.4.5
DDR Quad I/O Read (EDh, EEh)
The Read DDR Quad I/O command 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 the
S79FL01GS device. The QUAD bit of the Configuration Register is set (CR[1]=1) to enable the Quad capability in the S79FL01GS
device.
The instruction
EDh (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
EDh (ExtAdd=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-IO7.
The maximum operating clock frequency for Read DDR Quad I/O command is 80 MHz.
For Read DDR Quad I/O, there is a latency required after the last address and mode bits are shifted into the IO0-IO7 signals before
data begins shifting out of IO0-IO7. 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-IO7 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 number of dummy cycles is set by the LC bits in the
Configuration Register (CR1).
Both latency tables provide cycles for mode bits so a series of Quad I/O DDR commands may eliminate the 8-bit instruction after the
first command sends a complementary mode bit pattern, as shown in Figure 9-28. This feature removes the need for the eight bit
SDR instruction sequence and dramatically reduces initial access times (improves XIP performance). The Mode bits control the
length of the next Read DDR Quad I/O operation through the inclusion or exclusion of the first byte instruction code. If the upper
nibble (IO[7:4]) and lower nibble (IO[3:0]) of the Mode bits are complementary (i.e. 5h and Ah) the device transitions to Continuous
Read DDR Quad I/O Mode and the next address can be entered (after CS# is raised high and then asserted low) without requiring
the EDh or EEh instruction, as shown in Figure 9-29 thus, eliminating eight cycles from the command sequence. The following
sequences will release the device from Continuous Read DDR Quad I/O mode; after which, the device can accept standard SPI
commands:
1. During the Read DDR Quad I/O Command Sequence, if the Mode bits are not complementary the next time CS# is raised
high and then asserted low the device will be released from Read DDR Quad I/O mode.
2. During any operation, if CS# toggles high to low to high for eight cycles (or less) and data input (IO0 - IO7) are not set for
a valid instruction sequence, then the device will be released from Read DDR Quad I/O 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. The HOLD function is not
valid during Quad I/O DDR commands.
Note that the memory devices drive the IOs with a preamble prior to the first data value. The preamble is a pattern 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 eight IOs). 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 46 for more details.
Document Number: 002-00466 Rev. *G
Page 76 of 119
S79FL01GS
Figure 9-28 Dual-Quad SPI DDR Quad I/O Read Initial Access
CS#
SCK
IO0
A-3
8 4 0 4 0
7 6 5 4 3 2 1 0 0 0
IO1
A-2
9 5 1 5 1
7 6 5 4 3 2 1 0 1 1
IO2
A-1
10 6 2 6 2
7 6 5 4 3 2 1 0 2 2
IO3
A
11 7 3 7 3
7 6 5 4 3 2 1 0 3 3
IO4
7
6
7
6
5
4
5
3
3
1
2
1
0
A-3
8 4 0 4 0
7 6 5 4 3 2 1 0 4 4
IO5
A-2
9 5 1 5 1
7 6 5 4 3 2 1 0 5 5
IO6
A-1
10 6 2 6 2
7 6 5 4 3 2 1 0 6 6
IO7
A
3 7 3 7 3
7 6 5 4 3 2 1 0 7 7
Phase
4
2
Instruction
0
Address
Mode
Dummy
DLP
D1 D2
Notes:
1. A = MSB of address = 23 for command EDh, or 31 for command EEh.
2. Example DLP of 34h (or 00110100).
Figure 9-29 Dual-Quad Continuous DDR Quad I/O Read Subsequent Access
CS#
SCK
IO0
A-3
8
4
0
4
0
7
6
5
4
3
2
1
0
0
0
IO1
A-2
9
5
1
5
1
7
6
5
4
3
2
1
0
1
1
IO2
A-1
10
6
2
6
2
7
6
5
4
3
2
1
0
2
2
IO3
A
11
7
3
7
3
7
6
5
4
3
2
1
0
3
3
IO4
A-3
8
4
0
4
0
7
6
5
4
3
2
1
0
4
4
IO5
A-2
9
5
1
5
1
7
6
5
4
3
2
1
0
5
5
IO6
A-1
10
6
2
6
2
7
6
5
4
3
2
1
0
6
6
IO7
A
11
7
3
7
3
7
6
5
4
3
2
1
0
7
7
Phase
Address
Mode
Dummy
DLP
D1 D2
Notes:
1. A = MSB of address = 23 for command EDh, or 31 for command EEh.
2. Example DLP of 34h (or 00110100).
Document Number: 002-00466 Rev. *G
Page 77 of 119
S79FL01GS
9.5
Program Flash Array Commands
9.5.1
9.5.1.1
Program Granularity
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 Error Detection and
Correction (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-S family of products by 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 (See ECC Status Register (ECCSR) on page 44.)The ECC Status Register Read
(ECCRD) command is used to read the ECC status on any ECC unit.
EDC is applied to all parts of the Flash address spaces other than registers. An 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 bits and 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 a programming operation. 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.
ECC protects the OTP region - however a second program operation on the same ECC unit will disable ECC permanently
on that ECC unit (OTP is one time programmable, hence an erase operation to re-enable the ECC enable/indicator bit is
prohibited).
9.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 (1024 bytes) to be programmed in one operation. 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. 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.
9.5.1.3
Single Byte Programming
Single Byte Programming allows full backward compatibility to the standard SPI Page Programming (PP) command by allowing a
single byte to be programmed anywhere in the memory array.
Document Number: 002-00466 Rev. *G
Page 78 of 119
S79FL01GS
9.5.2
Page Program (PP 02h or 4PP 12h)
The Page Program (PP) commands 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 (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
02h (ExtAdd=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 IO0 and IO4. Up to a page can be provided on IO0 and IO4 after the 3-byte address with instruction
02h or 4-byte address with instruction 12h has been provided. If the 9 least significant address bits (A8-A0) are not all zero, all
transmitted data that goes beyond the end of the current page are programmed from the start address of the same page (from the
address whose 9 least significant bits (A8-A0) are all zero) i.e. the address wraps within the page aligned address boundaries. This
is a result of only requiring the user to enter one single page address to cover the entire page boundary.
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.
For optimized timings, using the Page Program (PP) command to load the entire page size program buffer within the page boundary
will save overall programming time versus loading less than a page size 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 (SR1[0]) will indicate
when the programming operation is completed. The P_ERR bit (SR1[6]) will indicate if an error occurs in the programming operation
that prevents successful completion of programming.
Figure 9-30 Dual-Quad Page Program (PP 02h or 4PP 12h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
A
5
4
3
2
1
0
3
2
1
0
3
2
1
0
7
6
5
4
3
2
1
0
A
5
4
3
2
1
0
7
6
5
4
7
6
5
4
IO1-IO3
IO4
IO5-IO7
Phase
9.5.3
Instruction
Address
Input Data1
Input Data 2
Quad Page Program (QPP 32h or 38h, or 4QPP 34h)
The Quad-input Page Program (QPP) command allows bytes to be programmed in the memory (changing bits from 1 to 0). The
Quad-input Page Program (QPP) command allows up to a page size (512 bytes) of data to be loaded into the Page Buffer using
eight signals: IO0-IO7. QPP can improve performance for PROM Programmer and applications that have slower clock speeds (< 12
MHz) by loading 8 bits of data per clock cycle. Systems with faster clock speeds do not realize as much benefit for the QPP
command since the inherent page program time becomes greater than the time it takes to clock-in the data. The maximum
frequency for the QPP command is 80 MHz.
To use Quad Page Program the Quad Enable Bit in the Configuration Register must be set (QUAD=1). A Write Enable command
must be executed before the device will accept the QPP command (Status Register-1, WEL=1).
The instruction
32h (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
32h (ExtAdd=1) is followed by a 4-byte address (A31-A0) or
38h (ExtAdd=0) is followed by a 3-byte address (A23-A0) or
38h (ExtAdd=1) is followed by a 4-byte address (A31-A0) or
34h is followed by a 4-byte address (A31-A0)
and at least two data bytes, into the IO signals. Data must be programmed at previously erased (FFh) memory locations.
QPP requires programming to be done one full page at a time. While less than a full page of data may be loaded for programming,
the entire page is considered programmed, any locations not filled with data will be left as ones, the same page must not be
programmed more than once.
Document Number: 002-00466 Rev. *G
Page 79 of 119
S79FL01GS
All other functions of QPP are identical to Page Program. The QPP command sequence is shown in the Figure 9-31.
Figure 9-31 Dual-Quad, Quad Page Program Command Sequence
CS#
SCK
IO0
0
0
0
0
0
IO1
7
6
5
4
3
2
1
0
A
1
0
1
1
1
1
1
IO2
2
2
2
2
2
3
3
3
3
3
4
4
4
4
4
IO5
5
5
5
5
5
IO6
6
6
6
6
6
IO3
IO4
7
6
5
4
3
2
1
0
A
1
0
IO7
Phase
Instruction
Address
7
7
7
7
7
D1
D2
D3
D4
...
Note:
1. A = MSB of address = A23 for PP 02h, or A31 for PP 02h, or for 4PP 12h.
9.5.4
Program Suspend (PGSP 85h) and Resume (PGRS 8Ah)
The Program Suspend command allows the system to interrupt a programming operation and then read from any other non-erasesuspended sector or non-program-suspended-page. Program Suspend is valid only during a programming operation.
Commands allowed after the Program Suspend command is issued:
Read Status Register 1 (RDSR1 05h)
Read Status Register 2 (RDSR2 07h)
The Write in Progress (WIP) bit in Status Register 1 (SR1[0]) must be checked to know when the programming 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 time required for the suspend operation to complete is
tPSL, see Table 9-6 on page 93.
See Table 9-4 on page 84 for the commands allowed while programming is suspend.
The Program Resume command 8Ah must be written to resume the programming operation after a Program Suspend. If the
programming operation was completed during the suspend operation, a resume command is not needed and has no effect if issued.
Program Resume commands will be ignored unless a Program operation is suspended.
After a 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. Program 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 operation to progress to completion there must be some periods of
time between resume and the next suspend command greater than or equal to tPRS. See Table 9-6 on page 93.
Document Number: 002-00466 Rev. *G
Page 80 of 119
S79FL01GS
Figure 9-32 Dual-Quad Program Suspend Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Instruction
Figure 9-33 Dual_Quad Program Resume Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Page 81 of 119
S79FL01GS
9.6
Erase Flash Array Commands
9.6.1
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 [ExtAdd=0] is followed by a 3-byte address (A23-A0), or
D8h [ExtAdd=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 IO0 and
IO4. 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 a0 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.
ASP has a PPB and a DYB protection bit for each sector.
Figure 9-34 Dual-Quad Sector Erase (SE 20h or 4SE 21h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
A
1
0
IO1-IO3
IO4
IO5-IO7
Phase
9.6.2
Instruction
Address
Bulk Erase (BE 60h or C7h)
The Bulk Erase (BE) command sets all bits to 1 (all bytes are FFh) inside the entire flash memory array. Before the BE 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 eighth bit of the instruction byte has been latched in on IO0 AND IO4. This will
initiate the erase cycle, which involves the pre-programming and erase of the entire flash memory array. If CS# is not driven high
after the last bit of instruction, the BE 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 BE command can be executed only when the Block Protection (BP2, BP1, BP0) bits are set to 0’s. If the BP bits are not zero, the
BE command is not executed and E_ERR is not set. The BE command will skip any sectors protected by the DYB or PPB and the
E_ERR status will not be set.
Figure 9-35 Bulk Erase Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Page 82 of 119
S79FL01GS
9.6.3
Erase Suspend and Resume Commands (ERSP 75h or ERRS 7Ah)
The Erase Suspend command, allows the system to interrupt a sector erase operation and then read from or program data to, any
other sector. Erase Suspend is valid only during a sector erase operation. The Erase Suspend command is ignored if written during
the Bulk Erase operation.
When the Erase Suspend command is written during the sector erase operation, the device requires a maximum of tESL (erase
suspend latency) to suspend the erase operation and update the status bits. See Table 9-7 on page 93.
Commands allowed after the Erase Suspend command is issued:
Read Status Register 1 (RDSR1 05h)
Read Status Register 2 (RDSR2 07h)
The Write in Progress (WIP) bit in Status Register 1 (SR1[0]) must be checked to know when the erase operation has stopped. The
Erase Suspend bit in 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.
If the erase operation was completed during the suspend operation, a resume command is not needed and has no effect if issued.
Erase Resume commands will be ignored unless an Erase operation is suspended.
See Table 9-4 on page 84 for the commands allowed while erase is suspend.
After the erase operation has been suspended, the sector enters the erase-suspend mode. The system can read data from or
program data to the device. Reading at any address within an erase-suspended sector produces undetermined data.
A WREN command is required before any command that will change nonvolatile data, even during erase suspend.
The WRR and PPB Erase commands are not allowed during Erase 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. However, WRR is allowed immediately following the BRAC
command; in this special case the WRR is interpreted as a write to the Bank Address Register, not a write to SR1 or CR1.
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.
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.
The Erase Resume command 7Ah must be written to resume the erase operation if an Erase is suspend. Erase Resume commands
will be ignored unless an Erase is Suspend.
After an Erase Resume command is sent, the WIP bit in the status register will be set to a 1 and the erase operation will continue.
Further Resume commands are ignored.
Erase operations may be interrupted as often as necessary e.g. an erase suspend command could immediately follow an erase
resume command but, in order for an 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 tERS. See Table 9-7 on page 93.
Figure 9-36 Dual-Quad Erase Suspend Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Instruction
Figure 9-37 Dual-Quad Erase Resume Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Page 83 of 119
S79FL01GS
Table 9-4 Commands Allowed During Program or Erase Suspend
Instruction
Name
Instruction
Code
(Hex)
Allowed
During Erase
Suspend
Allowed During
Program
Suspend
Comment
BRAC
B9
X
X
Bank address register may need to be changed during a suspend
to reach a sector for read or program.
BRRD
16
X
X
Bank address register may need to be changed during a suspend
to reach a sector for read or program.
BRWR
17
X
X
Bank address register may need to be changed during a suspend
to reach a sector for read or program.
CLSR
30
X
–
Clear status may be used if a program operation fails during erase
suspend.
DYBRD
E0
X
–
It may be necessary to remove and restore dynamic protection
during erase suspend to allow programming during erase
suspend.
DYBWR
E1
X
–
It may be necessary to remove and restore dynamic protection
during erase suspend to allow programming during erase
suspend.
ERRS
7A
X
FAST_READ
0B
X
X
All array reads allowed in suspend.
Required to resume from erase suspend.
4FAST_READ
0C
X
X
All array reads allowed in suspend.
MBR
FF
X
X
May need to reset a read operation during suspend.
PGRS
8A
X
X
Needed to resume a program operation. A program resume may
also be used during nested program suspend within an erase
suspend.
PGSP
85
X
–
Program suspend allowed during erase suspend.
PP
02
X
–
Required for array program during erase suspend.
4PP
12
X
–
Required for array program during erase suspend.
PPBRD
E2
X
–
Allowed for checking persistent protection before attempting a
program command during erase suspend.
QPP
32, 38
X
–
Required for array program during erase suspend.
4QPP
34
X
–
Required for array program during erase suspend.
4READ
13
X
X
All array reads allowed in suspend.
RDCR
35
X
X
–
DDRQIOR
ED
X
X
All array reads allowed in suspend.
DDRQIOR4
EE
X
X
All array reads allowed in suspend.
QIOR
EB
X
X
All array reads allowed in suspend.
4QIOR
EC
X
X
All array reads allowed in suspend.
QOR
6B
X
X
All array reads allowed in suspend.
4QOR
6C
X
X
All array reads allowed in suspend.
RDSR1
05
X
X
Needed to read WIP to determine end of suspend process.
RDSR2
07
X
X
Needed to read suspend status to determine whether the
operation is suspended or complete.
READ
03
X
X
All array reads allowed in suspend.
RESET
F0
X
X
WREN
06
X
WRR
01
X
Document Number: 002-00466 Rev. *G
Reset allowed anytime.
Required for program command within erase suspend.
X
Bank register may need to be changed during a suspend to reach
a sector needed for read or program. WRR is allowed when
following BRAC.
Page 84 of 119
S79FL01GS
9.7
9.7.1
One Time Program Array Commands
OTP Program (OTPP 42h)
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 2048 bytes so, the address bits from A25 to A10 must be zero for this command. Refer to OTP
Address Space on page 35 for details on the OTP region. The protocol of the OTP Program command is the same as the Page
Program command. 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.
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 SR1 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). 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 79 for the command sequence.
9.7.2
OTP Read (OTPR 4Bh)
The OTP Read command reads data from the OTP region. The OTP region is 2048 bytes so, the address bits from A25 to A10 must
be zero for this command. Refer to OTP Address Space on page 35 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. Also, the OTP Read command is not affected by
the latency code. The OTP read command always has one dummy byte of latency as shown in Figure 9-38.
Figure 9-38 Read OTP (OTPR 4Bh) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0 31
1
0
IO1
3
2
1
0
3
2
1
0
7
6
5
4
7
6
5
4
IO2-IO3
IO4
7
6
5
4
3
2
1
0 31
1
0
IO5
IO6-IO7
Phase
Instruction
Document Number: 002-00466 Rev. *G
Address
Dummy Cycles
Data 1
Data 2
Page 85 of 119
S79FL01GS
9.8
9.8.1
Advanced Sector Protection Commands
ASP Read (ASPRD 2Bh)
The ASP Read instruction 2Bh is shifted into SI by the rising edge of the SCK signal. Then the 16-bit ASP register contents is 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.
Figure 9-39 Dual-Quad SPI ASPRD Command Sequence
CS#
SCK
SI_IO0
7
6
5
4
3
2
1
0
SO_IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
1
0
IO5
IO6-IO7
Phase
9.8.2
Instruction
Register Read
Repeat Register Read
ASP Program (ASPP 2Fh)
Before the ASP Program (ASPP) 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 ASPP command is entered by driving CS# to the logic low state, followed by the instruction and two data bytes on SI, least
significant byte first. The ASP Register is two data bytes in length.
The ASPP command affects the P_ERR and WIP bits of the Status and Configuration Registers in the same manner as any other
programming operation.
CS# input must be driven to the logic high state after the sixteenth bit of data has been latched in. If not, the ASPP command is not
executed. As soon as CS# is driven to the logic high state, the self-timed ASPP operation is initiated. While the ASPP 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 ASPP operation, and is a 0 when it is completed. When the ASPP operation is completed, the Write Enable
Latch (WEL) is set to a 0.
Figure 9-40 ASPP (2Fh) Command
CS#
SCK
IO0
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
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Instruction
Document Number: 002-00466 Rev. *G
Input ASPR Low Byt e
Input IRP High Byte
Page 86 of 119
S79FL01GS
9.8.3
DYB Read (DYBRD E0h)
The instruction E0h is latched into SI by the rising edge of the SCK signal. Followed by the 32-bit address 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.
Figure 9-41 DYBRD Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
A
1
0
IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
1
0
A
1
0
IO5
IO6-IO7
Phase
9.8.4
Instruction
Register
Address
Repeat Register
DYB Write (DYBWR 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, the 32-bit address 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 DYBWR command affects the P_ERR and WIP bits of the Status and 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. If not, the DYBWR
command is not executed. 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 WriteIn 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.
Figure 9-42 DYBWR (E1h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
A
5
4
3
2
1
0
3
2
1
0
3
2
1
0
7
6
5
4
3
2
1
0
A
5
4
3
2
1
0
7
6
5
4
7
6
5
4
IO1-IO3
IO4
IO5-IO7
Phase
Instruction
Document Number: 002-00466 Rev. *G
Address
Input Data1
Input Data 2
Page 87 of 119
S79FL01GS
9.8.5
PPB Read (PPBRD E2h)
The instruction E2h is shifted into SI by the rising edges of the SCK signal, followed by the 32-bit address 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.
Figure 9-43 PPBRD (E2h) Command Sequence
CS#
SCK
SI_IO0
7
6
5
4
3
2
1
0
SO_IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
1
0
IO5
IO6-IO7
Phase
9.8.6
Instruction
DY
Register Read
Repeat Register Read
PPB Program (PPBP 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 32-bit address
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 and 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.
Figure 9-44 PPBP (E3h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
A
1
0
7
6
5
4
3
2
1
0
A
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Address
Page 88 of 119
S79FL01GS
9.8.7
PPB Erase (PPBE E4h)
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.
Figure 9-45 PPB Erase (PPBE E4h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
9.8.8
Instruction
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.
Figure 9-46 PPB Lock Register Read Command Sequence
CS#
SCK
SI_IO0
7
6
5
4
3
2
1
0
SO_IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
1
0
IO5
IO6-IO7
Phase
Instruction
Document Number: 002-00466 Rev. *G
DY
Register Read
Repeat Register Read
Page 89 of 119
S79FL01GS
9.8.9
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.
Figure 9-47 PPB Lock Bit Write (PLBWR A6h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
9.8.10
Instruction
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 PASSRD command is ignored.
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.
Figure 9-48 Password Read (PASSRD E7h) Command Sequence
CS#
SCK
SI_IO0
7
6
5
4
3
2
1
0
SO_IO1
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
IO2-IO3
IO4
7
6
5
4
3
2
IO5
1
0
IO6-IO7
Phase
Instruction
Document Number: 002-00466 Rev. *G
Data 1
Data 8
Page 90 of 119
S79FL01GS
9.8.11
Password Program (PASSP E8h)
Before the Password Program (PASSP) 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, the device sets the Write Enable
Latch (WEL) to enable the PASSP operation.
The password can only be programmed before the Password Mode is selected by programming the Password Protection Mode bit
to 0 in the ASP Register (ASP[2]). After the Password Protection Mode is selected the PASSP command is ignored.
The PASSP 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 PASSP command is not
executed. As soon as CS# is driven to the logic high state, the self-timed PASSP operation is initiated. While the PASSP 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 PASSP cycle, and is a 0 when it is completed. The PASSP command can report a program error in the
P_ERR bit of the status register. When the PASSP operation is completed, the Write Enable Latch (WEL) is set to a 0. The
maximum clock frequency for the PASSP command is 133 MHz.
Figure 9-49 Password Program (PASSP E8h) Command Sequence
CS#
SCK
IO0
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
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
9.8.12
Instruction
Password Byte 1
Password Byte 8
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.
Figure 9-50 Password Unlock (PASSU E9h) Command Sequence
CS#
SCK
IO0
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
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Instruction
Document Number: 002-00466 Rev. *G
Password Byte 1
Password Byte 8
Page 91 of 119
S79FL01GS
9.9
9.9.1
Reset Commands
Software Reset Command (RESET F0h)
The Software Reset command (RESET) restores the device to its initial power up state, except for the volatile FREEZE bit in the
Configuration register CR1[1] and the volatile PPB Lock bit in the PPB Lock Register. 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. Note that the nonvolatile bits in the
configuration register, TBPROT, TBPARM, and BPNV, retain their previous state after a Software Reset. The Block Protection bits
BP2, BP1, and BP0, in the status register will only be reset if they are configured as volatile via the BPNV bit in the Configuration
Register (CR1[3]) and FREEZE is cleared to zero. The software reset cannot be used to circumvent the FREEZE or PPB Lock bit
protection mechanisms for the other security configuration bits. The reset command is executed when CS# is brought to high state
and requires tRPH time to execute.
Figure 9-51 Dual-Quad Software Reset (RESET F0h) Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
9.9.2
Instruction
Mode Bit Reset (MBR FFh)
The Mode Bit Reset (MBR) command can be 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 IO0 and IO4 for 8 SCK cycles. IO1 - IO3 and IO5 - IO7 are ‘don’t care’ during these cycles.
Figure 9-52 Dual-Quad SPI Mode Bit (MBR FFh) Reset Command Sequence
CS#
SCK
IO0
7
6
5
4
3
2
1
0
7
6
5
4
3
2
1
0
IO1-IO3
IO4
IO5-IO7
Phase
Document Number: 002-00466 Rev. *G
Instruction
Page 92 of 119
S79FL01GS
9.10
Embedded Algorithm Performance Tables
Table 9-5 Program and Erase Performance
Symbol
tW
Parameter
WRR Write Time
Min
Typ (1)
Max (2)
Unit
–
560
2000
ms
(3) (4)
tPP
Page Programming (1024 bytes)
–
340
750/1300
µs
tSE
Sector Erase Time (512-kB logical sectors = 4 x 128-kB physical
sectors)
–
520
2600
ms
tBE
Bulk Erase Time
–
103
460
sec
Notes:
1. Typical program and erase times assume the following conditions: 25°C, VCC = 3.0V; random data pattern.
2. Under worst case conditions of 90°C; 100,000 cycles max.
3. Industrial temperature range / Industrial Plus temperature range.
4. Maximum value also applies to OTPP, PPBP, ASPP, PASSP, ABWR, and PNVDLR programming commands.
Table 9-6 Program Suspend AC Parameters
Parameter
Program Suspend Latency (tPSL)
Program Resume to next Program Suspend
(tPRS)
Min
Typic
al
Max
Unit
Comments
–
–
40
µs
The time from Program Suspend command until the
WIP bit is 0
0.06
100
–
µs
Minimum is the time needed to issue the next
Program Suspend command but ≥ typical periods are
needed for Program to progress to completion
Table 9-7 Erase Suspend AC Parameters
Parameter
Erase Suspend Latency (tESL)
Erase Resume to next Erase Suspend
(tERS)
Document Number: 002-00466 Rev. *G
Min
Typica
Max Unit
l
Comments
–
–
45
µs
The time from Erase Suspend command until the WIP bit is
0.
0.06
100
–
µs
Minimum is the time needed to issue the next Erase
Suspend command but ≥ typical periods are needed for the
Erase to progress to completion
Page 93 of 119
S79FL01GS
10. Data Integrity
10.1
Erase Endurance
Table 10-1 Erase Endurance
Parameter
Program/Erase cycles per main Flash array sectors
Program/Erase cycles per PPB array or nonvolatile register array
(1)
Minimum
Unit
100K
P/E cycle
100K
P/E cycle
Note:
1. Each write command to a nonvolatile register causes a P/E cycle on the entire nonvolatile register array. OTP bits and registers internally reside in a separate array
that is not P/E cycled.
10.2
Data Retention
Table 10-2 Data Retention
Minimum
Time
Unit
10K Program/Erase Cycles
20
Years
100K Program/Erase Cycles
2
Years
Parameter
Data Retention Time
Test Conditions
Contact Cypress Sales and FAE for further information on the data integrity. An application note is available at: www.cypress.com/
appnotes.
Document Number: 002-00466 Rev. *G
Page 94 of 119
S79FL01GS
11. Software Interface Reference
11.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 Basic Flash parameter is mandated by the JEDEC JESD216B standard. Two optional parameter tables for
Sector Map and 4 Byte Address Instructions follow the Basic Flash table. 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 parameter tables portion of
the SFDP data structure are 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 11-1 SFDP Overview Map
Byte Address
0000h
,,,
1000h
...
1120h
...
11.1.1
Description
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 which is also one of the CFI parameter tables
Remainder of SFDP parameter tables followed by either more CFI parameters or undefined space
Field Definitions
Table 11-2 SFDP Header
Relative Byte
Address
SFDP Dword
Address
00h
01h
02h
SFDP Header
1st DWORD
03h
Data
Description
53h
This is the entry point for Read SFDP (5Ah) command i.e. location zero within
SFDP space ASCII “S”
46h
ASCII “F”
44h
ASCII “D”
50h
ASCII “P”
06h
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.
05h
01h
SFDP Major Revision This is the original major revision. This major revision is
compatible with all SFDP reading and parsing software.
06h
05h
Number of Parameter Headers (zero based, 05h = 6 parameters)
07h
FFh
Unused
04h
SFDP Header
2nd DWORD
Document Number: 002-00466 Rev. *G
Page 95 of 119
S79FL01GS
Table 11-2 SFDP Header (Continued)
Relative Byte
Address
SFDP Dword
Address
08h
Data
Description
00h
Parameter ID LSB (00h = JEDEC SFDP Basic SPI Flash Parameter)
00h
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.
0Ah
01h
Parameter Major Revision (01h = The original major revision — all SFDP software
is compatible with this major revision.
0Bh
09h
Parameter Table Length (in double words = Dwords = 4 byte units) 09h = 9
Dwords
0Ch
20h
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned) JEDEC Basic SPI Flash
parameter byte offset = 1120h
11h
Parameter Table Pointer Byte 1
00h
Parameter Table Pointer Byte 2
09h
0Dh
0Eh
Parameter
Header 0 1st
DWORD
Parameter
Header 0 2nd
DWORD
0Fh
FFh
Parameter ID MSB (FFh = JEDEC defined legacy Parameter ID)
10h
00h
Parameter ID LSB (00h = JEDEC SFDP Basic SPI Flash Parameter)
05h
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.
12h
01h
Parameter Major Revision (01h = The original major revision — all SFDP software
is compatible with this major revision.
13h
10h
Parameter Table Length (in double words = Dwords = 4 byte units) 10h = 16
Dwords
14h
20h
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned) JEDEC Basic SPI Flash
parameter byte offset = 1120h address
11h
15h
Parameter
Header 1 1st
DWORD
Parameter
Header 1 2nd
DWORD
11h
Parameter Table Pointer Byte 1
00h
Parameter Table Pointer Byte 2
17h
FFh
Parameter ID MSB (FFh = JEDEC defined Parameter)
18h
00h
Parameter ID LSB (00h = JEDEC SFDP Basic SPI Flash Parameter)
16h
19h
06h
Parameter Minor Revision (06h = JESD216 Revision B)
01h
Parameter Major Revision (01h = The original major revision - all SFDP software
is compatible with this major revision.
1Bh
10h
Parameter Table Length (in double words = Dwords = 4 byte units) 10h = 16
Dwords
1Ch
20h
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned) JEDEC Basic SPI Flash
parameter byte offset = 1120h address
11h
Parameter Table Pointer Byte 1
00h
Parameter Table Pointer Byte 2
FFh
Parameter ID MSB (FFh = JEDEC defined Parameter)
1Ah
1Dh
1Eh
1Fh
Parameter
Header 2 1st
DWORD
Parameter
Header 2 2nd
DWORD
Document Number: 002-00466 Rev. *G
Page 96 of 119
S79FL01GS
Table 11-2 SFDP Header (Continued)
Relative Byte
Address
SFDP Dword
Address
20h
Data
Description
81h
Parameter ID LSB (81h = SFDP Sector Map Parameter)
00h
Parameter Minor Revision (00h = Initial version as defined in JESD216 Revision
B)
01h
Parameter Major Revision (01h = The original major revision — all SFDP software
that recognizes this parameter’s ID is compatible with this major revision.
23h
02h
Parameter Table Length (in double words = Dwords = 4 byte units) 02h = 2
Dwords
24h
60h
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned) JEDEC parameter byte
offset = 1160h
11h
Parameter Table Pointer Byte 1
00h
Parameter Table Pointer Byte 2
21h
22h
25h
26h
Parameter
Header 3 1st
DWORD
Parameter
Header 3 2nd
DWORD
27h
FFh
Parameter ID MSB (FFh = JEDEC defined Parameter)
28h
84h
Parameter ID LSB (00h = SFDP 4 Byte Address Instructions Parameter)
00h
Parameter Minor Revision (00h = Initial version as defined in JESD216 Revision
B)
01h
Parameter Major Revision (01h = The original major revision - all SFDP software
that recognizes this parameter’s ID is compatible with this major revision.
2Bh
02h
Parameter Table Length (in double words = Dwords = 4 byte units) (2h = 2
Dwords)
2Ch
68h
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned) JEDEC parameter byte
offset = 1168h
11h
Parameter Table Pointer Byte 1
00h
Parameter Table Pointer Byte 2
29h
2Ah
2Dh
2Eh
Parameter
Header 4 1st
DWORD
Parameter
Header 4 2nd
DWORD
2Fh
FFh
Parameter ID MSB (FFh = JEDEC defined Parameter)
01h
Parameter ID LSB (Cypress Vendor Specific ID-CFI parameter) Legacy
Manufacturer ID 01h = AMD / Cypress
01h
Parameter Minor Revision (01h = ID-CFI updated with SFDP Rev B table)
01h
Parameter Major Revision (01h = The original major revision - all SFDP software
that recognizes this parameter’s ID is compatible with this major revision.
33h
5Ch
Parameter Table Length (in double words = Dwords = 4 byte units) CFI starts at
1000h, the final SFDP parameter (CFI ID = A5) starts at 111Eh (SFDP starting
point of 1120h -2hB of CFI parameter header), for a length of 11EhB excluding the
CFI A5 parameter. The final CFI A5 parameter adds an additional 52hB for a total
of 11Eh + 82h = 170hB. 170hB/4 = 5Ch Dwords.
34h
00h
Parameter Table Pointer Byte 0 (Dword = 4 byte aligned) Entry point for ID-CFI
parameter is byte offset = 1000h relative to SFDP location zero.
10h
Parameter Table Pointer Byte 1
00h
Parameter Table Pointer Byte 2
01h
Parameter ID MSB (01h = JEDEC JEP106 Bank Number 1)
30h
31h
32h
35h
36h
37h
Parameter
Header 5 1st
DWORD
Parameter
Header 5 2nd
DWORD
Document Number: 002-00466 Rev. *G
Page 97 of 119
S79FL01GS
11.2
Device ID and Common Flash Interface (ID-CFI) Address Map
11.2.1
Field Definitions
Table 11-3 Manufacturer and Device ID
Byte Address
Data
00h
01h
Description
Manufacturer ID for Cypress
01h
79h
Device ID Most Significant Byte — Memory Interface Type
02h
21h
Device ID Least Significant Byte — Density
03h
4Eh
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 address
map. A value of 00h indicates the entire 512-byte ID-CFI space must be read
because the actual length of the ID-CFI information is longer than can be
indicated by this legacy single byte field. The value is OPN dependent.
04h
00h (Uniform 512-kB
sectors)
05h
80h (FL-S Family)
06h
xxh
07h
xxh
ASCII characters for Model
Refer to Ordering Information on page 115 for the model number definitions.
08h
xxh
Reserved
09h
xxh
Reserved
0Ah
xxh
Reserved
Sector Architecture
Family ID
0Bh
xxh
Reserved
0Ch
xxh
Reserved
0Dh
xxh
Reserved
0Eh
xxh
Reserved
0Fh
xxh
Reserved
Table 11-4 CFI Query Identification String
Byte Address
Data
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
Document Number: 002-00466 Rev. *G
Description
Page 98 of 119
S79FL01GS
Table 11-5 CFI System Interface String
Byte Address
Data
Description
1Bh
27h
VCC Min. (erase/program): 100 millivolts
1Ch
36h
VCC Max. (erase/program): 100 millivolts
1Dh
00h
VPP Min. voltage (00h = no VPP present)
1Eh
00h
VPP Max. voltage (00h = no VPP present)
1Fh
06h
Typical timeout per single byte program 2N µs
20h
09h (512B page)
21h
09h (512 kB)
22h
11h (1024 Mb)
23h
02h
Max. timeout for byte program 2N times typical
24h
02h
Max. timeout for page program 2N times typical
25h
03h
Max. timeout per individual sector erase 2N times typical
26h
03h
Max. timeout for full chip erase 2N times typical (00h = not
supported)
Typical timeout for Min. size Page program 2N µs (00h = not
supported)
Typical timeout per individual sector erase 2N ms
Typical timeout for full chip erase 2N ms (00h = not supported)
Table 11-6 Device Geometry Definition for 1024-Mbit Device
Byte Address
Data
27h
1Bh (1024 Mb)
28h
03h
29h
01h
2Ah
0Ah
2Bh
00h
2Ch
01h
2Dh
FFh
2Eh
00h
2Fh
00h
30h
08h
31h thru 3Fh
FFh
Document Number: 002-00466 Rev. *G
Description
N
Device Size = 2 bytes;
Flash Device Interface Description;
0000h = x8 only
0001h = x16 only
0002h = x8/x16 capable
0003h = x32 only
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
0103h = Dual-Quad SPI, 3 or 4-byte address
Max. number of bytes in multi-byte write = 2N
(0000 = not supported
0009h = 512B page
000Ah = 1024B page)
Number of Erase Block Regions within device
1 = Uniform Device, 2 = Boot Device
Erase Block Region 1 Information (refer to JEDEC JEP137)
256 sectors = 256-1 = 00FFh
512-kB sectors = 256 bytes x 0800h
RFU
Page 99 of 119
S79FL01GS
Table 11-7 CFI Primary Vendor-Specific Extended Query
Byte Address
Data
40h
50h
41h
52h
42h
49h
43h
31h
Major version number = 1, ASCII
44h
33h
Minor version number = 3, ASCII
21h
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
46h
02h
Erase Suspend
0 = Not Supported
1 = Read Only
2 = Read and Program
47h
01h
Sector Protect
00 = Not Supported
X = Number of sectors in group
48h
00h
Temporary Sector Unprotect
00 = Not Supported
01 = Supported
49h
08h
Sector Protect/Unprotect Scheme
04 = High Voltage Method
05 = Software Command Locking Method
08 = Advanced Sector Protection Method
09 = Secure
4Ah
00h
Simultaneous Operation
00 = Not Supported
X = Number of Sectors
4Bh
01h
Burst Mode (Synchronous sequential read) support
00 = Not Supported
01 = Supported
4Ch
05h
Page Mode Type, model dependent
00 = Not Supported
01 = 4 Word Read Page
02 = 8 Read Word Page
03 = 256-Byte Program Page
04 = 512-Byte Program Page
05 = 1024-Byte Program Page
4Dh
00h
ACC (Acceleration) Supply Minimum
00 = Not Supported, 100 mV
45h
Document Number: 002-00466 Rev. *G
Description
Query-unique ASCII string “PRI”
Page 100 of 119
S79FL01GS
Table 11-7 CFI Primary Vendor-Specific Extended Query (Continued)
Byte Address
Data
Description
4Eh
00h
ACC (Acceleration) Supply Maximum
00 = Not Supported, 100 mV
4Fh
00h
WP# Protection
00 = None
01 = Whole Chip
04 = Uniform Device with Bottom WP Protect
05 = Uniform Device with Top WP Protect
07 = Uniform Device with Top or Bottom Write Protect (user select)
50h
01h
Program Suspend
00 = Not Supported
01 = Supported
The Alternate Vendor-Specific Extended Query provides information related to the expanded command set provided by the
S79FL-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 11-8 CFI Alternate Vendor-Specific Extended Query Header
Byte Address
Data
Description
51h
41h
52h
4Ch
53h
54h
54h
32h
Major version number = 2, ASCII
55h
30h
Minor version number = 0, ASCII
Query-unique ASCII string “ALT”
Table 11-9 CFI Alternate Vendor-Specific Extended Query Parameter 0
Parameter Relative
Byte Address
Offset
Data
00h
00h
Parameter ID (Ordering Part Number)
01h
10h
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)
02h
53h
ASCII “S” for manufacturer (Cypress)
03h
37h
04h
39h
05h
46h
06h
4Ch
07h
30h (1 Gb)
08h
31h (1 Gb)
09h
47h (1 Gb)
0Ah
53h
Document Number: 002-00466 Rev. *G
Description
ASCII “79” for Product Characters (Dual-Quad SPI)
ASCII “FL” for Interface Characters (SPI 3 Volt)
ASCII characters for density
ASCII “S” for Technology (65 nm MirrorBit)
Page 101 of 119
S79FL01GS
Table 11-9 CFI Alternate Vendor-Specific Extended Query Parameter 0
Parameter Relative
Byte Address
Offset
Data
0Bh
xxh
0Ch
xxh
0Dh
xxh
0Eh
xxh
0Fh
xxh
10h
xxh
11h
xxh
Description
Reserved for Future Use (RFU)
Table 11-10 CFI Alternate Vendor-Specific Extended Query Parameter 80h Address Options
Parameter Relative
Byte Address
Offset
Data
00h
80h
Parameter ID (Ordering Part Number)
01h
01h
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)
F0h
Bits 7:4 - Reserved = 1111b
Bit 3 - AutoBoot support - Yes= 0b, No = 1b
Bit 2 - 4-byte address instructions supported - Yes = 0b, No = 1b
Bit 1 - Bank address + 3-byte address instructions supported - Yes = 0b, No = 1b
Bit 0 - 3-byte address instructions supported - Yes = 0b, No = 1b
02h
Description
Table 11-11 CFI Alternate Vendor-Specific Extended Query Parameter 84h Suspend Commands
Parameter Relative
Byte Address
Offset
Data
00h
84h
Parameter ID (Suspend Commands
01h
08h
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)
02h
85h
Program suspend instruction code
03h
28h
Program suspend latency maximum (µs)
04h
8Ah
Program resume instruction code
05h
64h
Program resume to next suspend typical (µs)
06h
75h
Erase suspend instruction code
07h
2Dh
Erase suspend latency maximum (µs)
08h
7Ah
Erase resume instruction code
09h
64h
Erase resume to next suspend typical (µs)
Document Number: 002-00466 Rev. *G
Description
Page 102 of 119
S79FL01GS
Table 11-12 CFI Alternate Vendor-Specific Extended Query Parameter 88h Data Protection
Parameter Relative
Byte Address
Offset
Data
00h
88h
Parameter ID (Data Protection)
01h
04h
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)
02h
0Bh
OTP size 2N bytes, FFh = not supported
03h
01h
OTP address map format, 01h = FL-S format, FFh = not supported
04h
xxh
Block Protect Type, model dependent
00h = FL-P, FL-S, FFh = not supported
05h
01h
Advanced Sector Protection type, model dependent
01h = FL-S ASP
Description
Table 11-13 CFI Alternate Vendor-Specific Extended Query Parameter 8Ch Reset Timing
Parameter Relative
Byte Address
Offset
Data
00h
8Ch
Parameter ID (Reset Timing)
01h
06h
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)
02h
96h
POR maximum value
03h
01h
POR maximum exponent 2N µs
04h
23h
Hardware Reset maximum value, FFh = not supported
05h
00h
Hardware Reset maximum exponent 2N µs
06h
23h
Software Reset maximum value, FFh = not supported
07h
00h
Software Reset maximum exponent 2N µs
Description
Table 11-14 CFI Alternate Vendor-Specific Extended Query Parameter 90h — EHPLC (SDR)
Parameter Relative
Byte Address
Offset
Data
00h
90h
Parameter ID (Latency Code Table)
01h
56h
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)
02h
06h
Number of rows
03h
0Eh
Row length in bytes
04h
46h
Start of header (row 1), ASCII “F” for frequency column header
05h
43h
ASCII “C” for Code column header
06h
03h
Read 3-byte address instruction
Description
07h
13h
Read 4-byte address instruction
08h
0Bh
Read Fast 3-byte address instruction
09h
0Ch
Read Fast 4-byte address instruction
Document Number: 002-00466 Rev. *G
Page 103 of 119
S79FL01GS
Table 11-14 CFI Alternate Vendor-Specific Extended Query Parameter 90h — EHPLC (SDR) (Continued)
Parameter Relative
Byte Address
Offset
Data
0Ah
FFh
Description
Read Dual Out 3-byte address instruction
0Bh
FFh
Read Dual Out 3-byte address instruction
0Ch
6Bh
Read Quad Out 3-byte address instruction
0Dh
6Ch
Read Quad Out 4-byte address instruction
0Eh
FFh
Dual I/O Read 3-byte address instruction
0Fh
FFh
Dual I/O Read 4-byte address instruction
10h
EBh
Quad I/O Read 3-byte address instruction
11h
ECh
Quad I/O Read 4-byte address instruction
12h
32h
Start of row 2, SCK frequency limit for this row (50 MHz)
13h
03h
Latency Code for this row (11b)
14h
00h
Read mode cycles
15h
00h
Read latency cycles
16h
00h
Read Fast mode cycles
17h
00h
Read Fast latency cycles
18h
FFh
Read Dual Out mode cycles
19h
FFh
Read Dual Out mode cycles
1Ah
00h
Read Quad Out mode cycles
1Bh
00h
Read Quad Out latency cycles
1Ch
FFh
Dual I/O Read mode cycles
1Dh
FFh
Dual I/O Read latency cycles
1Eh
02h
Quad I/O Read mode cycles
1Fh
01h
Quad I/O Read latency cycles
20h
50h
Start of row 3, SCK frequency limit for this row (80 MHz)
21h
00h
Latency Code for this row (00b)
22h
FFh
Read mode cycles (FFh = command not supported at this frequency)
23h
FFh
Read latency cycles
24h
00h
Read Fast mode cycles
25h
08h
Read Fast latency cycles
26h
FFh
Read Dual Out mode cycles
27h
FFh
Read Dual Out latency cycles
28h
00h
Read Quad Out mode cycles
29h
08h
Read Quad Out latency cycles
2Ah
FFh
Dual I/O Read mode cycles
2Bh
FFh
Dual I/O Read latency cycles
2Ch
02h
Quad I/O Read mode cycles
2Dh
04h
Quad I/O Read latency cycles
2Eh
5Ah
Start of row 4, SCK frequency limit for this row (90 MHz)
2Fh
01h
Latency Code for this row (01b)
Document Number: 002-00466 Rev. *G
Page 104 of 119
S79FL01GS
Table 11-14 CFI Alternate Vendor-Specific Extended Query Parameter 90h — EHPLC (SDR) (Continued)
Parameter Relative
Byte Address
Offset
Data
30h
FFh
31h
FFh
Read latency cycles
32h
00h
Read Fast mode cycles
33h
08h
Read Fast latency cycles
34h
FFh
Read Dual Out mode cycles
35h
FFh
Read Dual Out latency cycles
36h
00h
Read Quad Out mode cycles
37h
08h
Read Quad Out latency cycles
38h
FFh
Dual I/O Read mode cycles
Description
Read mode cycles (FFh = command not supported at this frequency)
39h
FFh
Dual I/O Read latency cycles
3Ah
02h
Quad I/O Read mode cycles
3Bh
04h
Quad I/O Read latency cycles
3Ch
68h
Start of row 5, SCK frequency limit for this row (104 MHz)
3Dh
02h
Latency Code for this row (10b)
3Eh
FFh
Read mode cycles (FFh = command not supported at this frequency)
3Fh
FFh
Read latency cycles
40h
00h
Read Fast mode cycles
41h
08h
Read Fast latency cycles
42h
FFh
Read Dual Out mode cycles
43h
FFh
Read Dual Out latency cycles
44h
00h
Read Quad Out mode cycles
45h
08h
Read Quad Out latency cycles
46h
FFh
Dual I/O Read mode cycles
47h
FFh
Dual I/O Read latency cycles
48h
02h
Quad I/O Read mode cycles
49h
05h
Quad I/O Read latency cycles
4Ah
85h
Start of row 6, SCK frequency limit for this row (133 MHz)
4Bh
02h
Latency Code for this row (10b)
4Ch
FFh
Read mode cycles (FFh = command not supported at this frequency)
4Dh
FFh
Read latency cycles
4Eh
00h
Read Fast mode cycles
4Fh
08h
Read Fast latency cycles
50h
FFh
Read Dual Out mode cycles
51h
FFh
Read Dual Out latency cycles
52h
FFh
Read Quad Out mode cycles
53h
FFh
Read Quad Out latency cycles
54h
FFh
Dual I/O Read mode cycles
55h
FFh
Dual I/O Read latency cycles
Document Number: 002-00466 Rev. *G
Page 105 of 119
S79FL01GS
Table 11-14 CFI Alternate Vendor-Specific Extended Query Parameter 90h — EHPLC (SDR) (Continued)
Parameter Relative
Byte Address
Offset
Data
56h
FFh
Quad I/O Read mode cycles
57h
FFh
Quad I/O Read latency cycles
Description
Note:
FFh = Not Supported.
Table 11-15 CFI Alternate Vendor-Specific Extended Query Parameter 9Ah — EHPLC (DDR)
Parameter Relative
Byte Address
Offset
Data
00h
9Ah
Parameter ID (Latency Code Table)
01h
2Ah
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)
Description
02h
05h
Number of rows
03h
08h
Row length in bytes
04h
46h
Start of header (row 1), ASCII “F” for frequency column header
05h
43h
ASCII “C” for Code column header
06h
FFh
Read Fast DDR 3-byte address instruction
07h
FFh
Read Fast DDR 4-byte address instruction
08h
FFh
DDR Dual I/O Read 3-byte address instruction
09h
FFh
DDR Dual I/O Read 4-byte address instruction
0Ah
EDh
Read DDR Quad I/O 3-byte address instruction
0Bh
EEh
Read DDR Quad I/O 4-byte address instruction
0Ch
32h
Start of row 2, SCK frequency limit for this row (50 MHz)
0Dh
03h
Latency Code for this row (11b)
0Eh
FFh
Read Fast DDR mode cycles
0Fh
FFh
Read Fast DDR latency cycles
10h
FFh
DDR Dual I/O Read mode cycles
11h
FFh
DDR Dual I/O Read latency cycles
12h
01h
Read DDR Quad I/O mode cycles
13h
03h
Read DDR Quad I/O latency cycles
14h
50h
Start of row 3, SCK frequency limit for this row (80 MHz)
15h
00h
Latency Code for this row (00b)
16h
FFh
Read Fast DDR mode cycles
17h
FFh
Read Fast DDR latency cycles
18h
FFh
DDR Dual I/O Read mode cycles
19h
FFh
DDR Dual I/O Read latency cycles
1Ah
01h
Read DDR Quad I/O mode cycles
1Bh
06h
Read DDR Quad I/O latency cycles
1Ch
FFh
Start of row 4, SCK frequency limit for this row (66 MHz)
Document Number: 002-00466 Rev. *G
Page 106 of 119
S79FL01GS
Table 11-15 CFI Alternate Vendor-Specific Extended Query Parameter 9Ah — EHPLC (DDR) (Continued)
Parameter Relative
Byte Address
Offset
Data
1Dh
FFh
Latency Code for this row (01b)
1Eh
FFh
Read Fast DDR mode cycles
1Fh
FFh
Read Fast DDR latency cycles
20h
FFh
DDR Dual I/O Read mode cycles
21h
FFh
DDR Dual I/O Read latency cycles
22h
FFh
Read DDR Quad I/O mode cycles
23h
FFh
Read DDR Quad I/O latency cycles
24h
FFh
Start of row 5, SCK frequency limit for this row (66 MHz)
25h
FFh
Latency Code for this row (10b)
26h
FFh
Read Fast DDR mode cycles
27h
FFh
Read Fast DDR latency cycles
28h
FFh
DDR Dual I/O Read mode cycles
29h
FFh
DDR Dual I/O Read latency cycles
2Ah
FFh
Read DDR Quad I/O mode cycles
2Bh
FFh
Read DDR Quad I/O latency cycles
Description
Note:
FFh = Not Supported.
Table 11-16 CFI Alternate Vendor-Specific Extended Query Parameter F0h RFU
Parameter Relative
Byte Address
Offset
Data
00h
F0h
Parameter ID (RFU)
01h
0Fh
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)
02h
FFh
RFU
Description
...
FFh
RFU
10h
FFh
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.
Document Number: 002-00466 Rev. *G
Page 107 of 119
S79FL01GS
Table 11-17 CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B
CFI
Parameter
Relative
Byte
Address
Offset
SFDP
Parameter
Relative
Byte
Address
Offset
SFDP Dword
Name
Data
00h
—
N/A
A5h
CFI Parameter ID (JEDEC SFDP)
01h
—
N/A
50h
CFI 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)
E7h
Start of SFDP JEDEC parameter, located at 1120h in the overall SFDP
address space.
Bits 7:5 = unused = 111b
Bits 4:3 = 06h is status register write instruction and status register is
default nonvolatile = 00b
Bit 2 = Program Buffer > 64 bytes = 1
Bits 1:0 = Uniform 4-kB erase unavailable = 11b
FFh
Bits 15:8 = Uniform 4-kB erase opcode = not supported = FFh
02h
00h
03h
01h
JEDEC Basic
Flash
Parameter
Dword-1
Description
04h
02h
EAh
Bit 23 = Unused = 1b
Bit 22 = Supports Quad Out Read = Yes = 1b
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
Bits 18:17 = Number of Address Bytes, 3 or 4 = 01b
Bit 16 = Supports Dual Out Read = Yes = 1b
05h
03h
FFh
Bits 31:24 = unused = FFh
06h
04h
07h
05h
08h
06h
09h
07h
0Ah
08h
0Bh
09h
0Ch
0Ah
0Dh
JEDEC Basic
Flash
Parameter
Dword-2
FFh
FFh
FFh
Density in bits, zero based, 1 Gb = 3FFFFFFFh
3Fh
44h
Bits 7:5 = number of Quad I/O Mode cycles = 010b
Bits 4:0 = number of Quad I/O Dummy cycles = 00100b for default
latency code 00b
EBh
Quad I/O instruction code
08h
Bits 23:21 = number of Quad Out Mode cycles = 000b
Bits 20:16 = number of Quad Out Dummy cycles = 01000b
0Bh
6Bh
Quad Out instruction code
0Eh
0Ch
00h
Bits 7:5 = number of Dual Out Mode cycles (not supported) = 000b
Bits 4:0 = number of Dual Out Dummy cycles (not supported) =
00000b for default latency code
0Fh
0Dh
FFh
Dual Out instruction code (not supported) = FFh
00h
Bits 23:21 = number of Dual I/O Mode cycles (not supported) = 000b
for HPLC
Bits 20:16 = number of Dual I/O Dummy cycles (not supported) =
00000b for EHPLC or 00100b for HPLC Default Latency code = 00b
(not supported)
FFh
Dual I/O instruction code (not supported) = FFh
10h
0Eh
11h
0Fh
JEDEC Basic
Flash
Parameter
Dword-3
JEDEC Basic
Flash
Parameter
Dword-4
Document Number: 002-00466 Rev. *G
Page 108 of 119
S79FL01GS
Table 11-17 CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B (Continued)
CFI
Parameter
Relative
Byte
Address
Offset
12h
SFDP
Parameter
Relative
Byte
Address
Offset
10h
SFDP Dword
Name
JEDEC Basic
Flash
Parameter
Dword-5
Data
Description
EEh
Bits 7:5 RFU = 111b
Bit 4 = QPI (supported) = No = 0b
Bits 3:1 RFU = 111b
Bit 0 = Dual All (not supported) = 0b
FFh
Bits 15:8 = RFU = FFh
FFh
Bits 23:16 = RFU = FFh
13h
11h
14h
12h
15h
13h
FFh
Bits 31:24 = RFU = FFh
16h
14h
FFh
Bits 7:0 = RFU = FFh
17h
15h
18h
16h
19h
17h
1Ah
18h
1Bh
19h
1Ch
1Ah
1Dh
1Bh
1Eh
1Ch
1Fh
1Dh
20h
1Eh
21h
1Fh
22h
20h
23h
21h
24h
22h
25h
23h
JEDEC Basic
Flash
Parameter
Dword-6
JEDEC Basic
Flash
Parameter
Dword-7
JEDEC Basic
Flash
Parameter
Dword-8
JEDEC Basic
Flash
Parameter
Dword-9
Document Number: 002-00466 Rev. *G
FFh
Bits 15:8 = RFU = FFh
00h
Bits 23:21 = number of Dual All Mode cycles (not supported) = 000b
Bits 20:16 = number of Dual All Dummy cycles (not supported) =
00000b
FFh
Dual All instruction code (not supported) = FFh
FFh
Bits 7:0 = RFU = FFh
FFh
Bits 15:8 = RFU = FFh
00h
Bits 23:21 = number of QPI cycles (not supported) = 000b
Bits 20:16 = number of QPI Dummy cycles (not supported) = 00000b
FFh
Bits 31:24 (4-4-4) (not supported) = FFh
00h
Erase type 1 size 2N bytes (not supported) = 00h
FFh
Erase type 1 instruction (not supported) = FFh
00h
Erase type 2 size 2N bytes (not supported) = 00h
FFh
Erase type 2 instruction (not supported) = FFh
13h
Erase type 3 size 2N bytes = 512 kB = 13h
D8h
Erase type 3 instruction
00h
Erase type 4 size 2N bytes (not supported) = 00h
FFh
Erase type 4 instruction (not supported) = FFh
Page 109 of 119
S79FL01GS
Table 11-17 CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B (Continued)
CFI
Parameter
Relative
Byte
Address
Offset
SFDP
Parameter
Relative
Byte
Address
Offset
26h
SFDP Dword
Name
Data
Description
24h
F2h
27h
25h
FFh
28h
26h
0Fh
Bits 31:30 = Erase type 4 Erase, Typical time units (00b: 1 ms, 01b: 16
ms, 10b: 128 ms, 11b: 1 s) = RFU = 11b
Bits 29:25 = Erase type 4 Erase, Typical time count = RFU = 11111b
(typical erase time = (count +1) * units = RFU)
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 = 00011b (typical
erase time = (count +1) * units = 4*128 ms = 512 ms)
Bits 17:16 = Erase type 2 Erase, Typical time units (00b: 1 ms, 01b: 16
ms, 10b: 128 ms, 11b: 1 s) = RFU = 11b
Bits 15:11 = Erase type 2 Erase, Typical time count = RFU = 11111b
(typical erase time = (count +1) * units = RFU)
Bits 10:9 = Erase type 1 Erase, Typical time units (00b: 1 ms, 01b: 16
ms, 10b: 128 ms, 11b: 1 s) = RFU = 11b
Bits 8:4 = Erase type 1 Erase, Typical time count = RFU = 11111b
(typical erase time = (count +1) * units = RFU)
Bits 3:0 = Multiplier from typical erase time to maximum erase time =
2*(N+1), N=2h = 6x multiplier Binary Fields: 11-11111-10-00011-1111111-11-11111-0010 Nibble Format:
1111_1111_0000_1111_1111_1111_1111_0010 Hex Format:
FF_0F_FF_F2
JEDEC Basic
Flash
Parameter
Dword-10
29h
27h
2Ah
28h
A1h
2Bh
29h
25h
2Ch
2Ah
07h
2Dh
2Bh
JEDEC Basic
Flash
Parameter
Dword-11
Document Number: 002-00466 Rev. *G
FFh
D9h
Bit 31 Reserved = 1b
Bits 30:29 = Chip Erase, Typical time units (00b: 16 ms, 01b: 256 ms,
10b: 4 s, 11b: 64 s) = 4s = 10b
Bits 28:24 = Chip Erase, Typical time count, (count+1)*units, count =
11001b, (typical program time = (count +1) * units = 26*.4 µs = 104s
Bit 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, (typical program time = (count +1) *
units =
1*1 µs = 1 µs
Bit 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, (typical program time = (count +1) *
units = 13*8 µs = 104 µs
Bit 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 =
00101b, (typical program time = (count +1) * units =6*64 µs = 384 µ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 Binary Fields: 1-10-11001-00000-1-1100-1-00101-1001-0001 Nibble Format:
1101_1001_0000_0111_0010_0101_1001_0001 Hex Format:
D9_07_25_91
Page 110 of 119
S79FL01GS
Table 11-17 CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B (Continued)
CFI
Parameter
Relative
Byte
Address
Offset
SFDP
Parameter
Relative
Byte
Address
Offset
2Eh
SFDP Dword
Name
Data
Description
2Ch
ECh
2Fh
2Dh
83h
30h
2Eh
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 = 00101b,
max erase suspend latency = (count +1) * units = 6*8 µs = 48 µ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) +
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 + 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-00101-0001-1000100-0001-1-1110-1100 Nibble Format:
0100_0101_0001_1000_1000_0011_1110_1100 Hex Format:
45_18_83_EC
31h
2Fh
JEDEC Basic
Flash
Parameter
Dword-12
45h
8Ah
32h
30h
33h
31h
34h
32h
35h
33h
36h
34h
F7h
37h
35h
FFh
38h
36h
FFh
JEDEC Basic
Flash
Parameter
Dword-13
85h
7Ah
75h
JEDEC Basic
Flash
Parameter
Dword-14
39h
37h
Document Number: 002-00466 Rev. *G
FFh
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 (not supported) = 1
Bits 30:23 = Enter Deep Power Down Instruction (not supported) =
FFh
Bits 22:15 = Exit Deep Power Down Instruction (not supported) = FFh
Bits 14:13 = Exit Deep Power Down to next operation delay units =
(00b: 128 ns, 01b: 1 µs, 10b: 8 µs, 11b: 64 µs) = 64 µs = 11b
Bits 12:8 = Exit Deep Power Down to next operation delay count =
11111b, Exit Deep Power Down to next operation delay =
(count+1)*units (not supported)
Bits 7:4 = RFU = Fh
Bits 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).
Bits 1:0 = RFU = 11b Binary Fields: 1-11111111-11111111-11-111111111-01-11 Nibble Format:
1111_1111_1111_1111_1111_1111_1111_0111 Hex Format:
FF_FF_FF_F7
Page 111 of 119
S79FL01GS
Table 11-17 CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B (Continued)
CFI
Parameter
Relative
Byte
Address
Offset
SFDP
Parameter
Relative
Byte
Address
Offset
3Ah
SFDP Dword
Name
Data
Description
38h
00h
3Bh
39h
F6h
3Ch
3Ah
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 Bits[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. + x1_xxxxb: Mode
Bit[7:0] != Axh + 1x_x1xx: RFU
JEDEC Basic
Flash
Parameter
Dword-15
3Dh
3Bh
3Eh
3Ch
F0h
3Fh
3Dh
28h
40h
3Eh
FAh
41h
3Fh
42h
40h
43h
41h
44h
42h
45h
43h
JEDEC Basic
Flash
Parameter
Dword-16
JEDEC Sector
Map
Parameter
Dword-1
Config-0
Header
Document Number: 002-00466 Rev. *G
FFh
A8h
FFh
00h
00h
FFh
Bits 31:24 = Enter 4-byte Addressing = xxxx_1xxxb: 8-bit volatile bank
register used to define A[30:A24] bits. MSB (bit[7]) is used to enable/
disable 4-byte address mode. When MSB is set to ‘1’, 4-byte address
mode is active and A[30:24] bits are don’t care. Read with instruction
16h. Write instruction is 17h with 1 byte of data. When MSB is cleared
to ‘0’, select the active 128-Mbit segment by setting the appropriate
A[30:24] bits and use 3-byte addressing. + xx1x_xxxxb: Supports
dedicated 4-byte address instruction set. Consult vendor data sheet
for the instruction set definition or look for 4 byte Address Parameter
Table. + 1xxx_xxxxb: Reserved = 10101000b
Bits 23:14 = Exit 4-byte Addressing = xx_xxxx_1xxxb: 8-bit volatile
bank register used to define A[30:A24] bits. MSB (bit[7]) is used to
enable/disable 4-byte address mode. When MSB is cleared to ‘0’, 3byte address mode is active and A30:A24 are used to select the active
128-Mbit memory segment. Read with instruction 16h. Write
instruction is 17h, data length is 1 byte. + 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 = 1111101000b
Bits 13:8 = Soft Reset and Rescue Sequence Support = x0_1xxxb:
issue instruction F0h + 1x_xxxxb: exit 0-4-4 mode is required prior to
other reset sequences above if the device may be operating in this
mode. = 101000b
Bit 7 = RFU = 1
Bits 6:0 = Volatile or Nonvolatile Register and Write Enable Instruction
for Status Register 1 = xx1_xxxxb: Status Register 1 contains a mix of
volatile and nonvolatile bits. The 06h instruction is used to enable
writing of the register. + x1x_xxxxb: Reserved + 1xx_xxxxb: Reserved
= 1110000b Binary Fields: 10101000-1111101000-101000-1-1110000
Nibble Format: 1010_1000_1111_1010_0010_1000_1111_0000 Hex
Format: A8_FA_28_F0
Bits 31:24 = RFU = FFh
Bits 23:16 = Region count (Dwords -1) = 00h: One region
Bits 15:8 = Configuration ID = 00h: Uniform 256 kB sectors
Bits 7:2 = RFU = 111111b
Bit 1 = Map Descriptor = 1
Bit 0 = The end descriptor = 1
Page 112 of 119
S79FL01GS
Table 11-17 CFI Alternate Vendor-Specific Extended Query Parameter A5h, JEDEC SFDP Rev B (Continued)
CFI
Parameter
Relative
Byte
Address
Offset
SFDP
Parameter
Relative
Byte
Address
Offset
46h
44h
47h
45h
48h
46h
49h
47h
4Ah
48h
F3h
4Bh
49h
88h
4Ch
4Ah
FFh
4Dh
4Bh
4Eh
4Ch
4Fh
4Dh
50h
4Eh
51h
4Fh
SFDP Dword
Name
JEDEC Sector
Map
Parameter
Dword-2
Config-0
Region-0
JEDEC 4 Byte
Address
Instructions
Parameter
Dword-1
JEDEC 4 Byte
Address
Instructions
Parameter
Dword-2
Document Number: 002-00466 Rev. *G
Data
Description
F4h
Bits 31:8 = Region size = 00FFFFh: Region size as count-1 of 256
byte units = 64 MB/256 = 256K Count = 262144, value = count -1 =
262144 -1 = 262143 = 3FFFFh
Bits 4:7 = RFU = Fh 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 512 kB erase and
is supported in the 512-kB sector region
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
FFh
FFh
7Fh
FFh
FFh
FFh
DCh
FFh
Supported = 1, Not Supported = 0
Bits 31:20 = RFU = FFFh
Bit 19 = Support for nonvolatile individual sector lock write command,
Instruction=E3h = 1
Bit 18 = Support for nonvolatile 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 =
1
Bit 13 = Support for (1-1-1) DTR_Read Command, Instruction=0Eh = 1
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 = 0
Bit 9 = Support for Erase Command — Type 1 = 0
Bit 8 = Support for (1-4-4) Page Program Command, Instruction=3Eh
=0
Bit 7 = Support for (1-1-4) Page Program Command, Instruction=34h =
1
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 =
1
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 =
1
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
Bits 31:24 = FFh = Instruction for Erase Type 4: RFU
Bits 23:16 = DCh = Instruction for Erase Type 3
Bits 15:8 = FFh = Instruction for Erase Type 2: RFU
Bits 7:0 = FFh = Instruction for Erase Type 1: RFU
Page 113 of 119
S79FL01GS
11.3
Device ID and Common Flash Interface (ID-CFI) ASO Map — Automotive Only
The CFI Primary Vendor-Specific Extended Query is extended to include Electronic Marking information for device traceability.
Address
Data Field
# of
bytes
Data
Format
Example of
Actual
Data
(SA) + 0180h
Size of Electronic
Marking
1
Hex
20
14h
(SA) + 0181h
Revision of Electronic
Marking
1
Hex
1
01h
(SA) + 0182h
Fab Lot #
8
ASCII
LD87270
Hex Read Out of Example Data
4Ch, 44h, 38h, 37h, 32h, 37h, 30h, FFh
(SA) + 018Ah
Wafer #
1
Hex
23
17h
(SA) + 018Bh
Die X Coordinate
1
Hex
10
0Ah
(SA) + 018Ch
Die Y Coordinate
1
Hex
15
0Fh
(SA) + 018Dh
Class Lot #
7
ASCII
BR33150
(SA) + 0194h
Reserved for Future
12
N/A
N/A
42h, 52h, 33h, 33h, 31h, 35h, 30h
FFh, FFh, FFh, FFh, FFh, FFh, FFh, FFh, FFh,
FFh, FFh, FFh
Fab Lot # + Wafer # + Die X Coordinate + Die Y Coordinate gives a unique ID for each device.
11.4
Initial Delivery State
The device is shipped from Cypress with nonvolatile 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 contains 00h (all SR1 bits are cleared to 0’s).
The Configuration Register 1 contains 02h.
The Autoboot register contains 00h.
The Password Register contains FFFFFFFF-FFFFFFFFh.
All PPB bits are 1.
The ASP Register contents are shown here.
Table 11-18 ASP Register Content
Ordering Part Number Model
ASPR Default Value
C1
FE7Fh
Document Number: 002-00466 Rev. *G
Page 114 of 119
S79FL01GS
Ordering Information
12. Ordering Information S79FL01GS
The ordering part number is formed by a valid combination of the following:
S79F
L
01G
S
D
S
B
H
V
C
0
1
Packing Type
0 = Tray
3 = 13” Tape and Reel
Model Number (Sector Type)
1 = Uniform 512-kB sectors
Model Number (Latency Type, Package Details, RESET#)
C = EHPLC, 5 x 5 ball BGA footprint with RESET#
Temperature Range / Grade
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)
Package Materials
H = Low-Halogen, Lead (Pb)-free
Package Type
B = 24-ball BGA 6 x 8 mm package, 1.00 mm pitch
Speed
DS = 80 MHz
AG = 133 MHz
Device Technology
S = 65 nm MirrorBit Process Technology
Density
01G = 1024 Mbit
Device Family
S79FL
Cypress Memory 3.0 V-Only, Dual-Quad Serial Peripheral Interface (SPI) Flash Memory
Notes:
1. EHPLC = Enhanced High Performance Latency Code table.
2. Uniform 512-kB sectors = All sectors are uniform 512-kB with a 1024B programming buffer.
Valid Combinations — Standard
Valid Combinations list configurations planned to be supported in volume for this device. Consult your local sales office to confirm
availability of specific valid combinations and to check on newly released combinations.
Valid Combinations — Standard
Base Ordering
Part Number
Speed
Option
Package and
Temperature
Model Number
Packing Type
Package Marking (1)
S79FL01GS
DS
BHV
C1
0, 3
79FL01GS + S + (Temp) + H + (Model Number)
Note:
1. Example, S79FL01GSDSBHVC10 package marking would be 79FL01GSSVHC1.
Document Number: 002-00466 Rev. *G
Page 115 of 119
S79FL01GS
Valid Combinations — Automotive Grade / AEC-Q100
Table 12-1 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. Consult your local sales representative to confirm availability of specific
combinations and to check on newly released combinations.
Production 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 12-1 Valid Combinations — Automotive Grade / AEC-Q100
Valid Combinations — Automotive Grade / AEC-Q100
Base
Package
Speed
Ordering
and
Option
Part Number
Temperature
S79FL01GS
DS
BHA, BHB
Document Number: 002-00466 Rev. *G
Model
Number
Packing
Type
C1
0, 3
Package Marking
79FL01GS + S + (Temp) + H + (Model Number)
Page 116 of 119
S79FL01GS
13. Revision History
Document History Page
Document Title: S79FL01GS, 1-Gbit (128 MB) Dual-Quad MirrorBit® Flash NVM CMOS 3.0 V Core SPI with Multi-I/O
Document Number: 002-00466
Rev.
ECN No.
Orig. of
Change
Submission
Date
Description of Change
**
-
-
10/15/2014
Initial release.
*A
-
-
02/04/2015
Global: Promoted data sheet from Advance Information to Preliminary
Command Set Summary: S79FL01GS Command Set (sorted by function)
table: corrected ‘Maximum Frequency (MHz)’ for DDRQIOR and 4DDRQIOR
Serial Flash Discoverable Parameters (SFDP) Address Map: Updated
paragraph
Updated SFDP Overview Map table
Updated SFDP Header table
Device ID and Common Flash Interface (ID-CFI) Address Map: Manufacturer
and Device ID table: corrected 03h Data
CFI Alternate Vendor-Specific Extended Query Parameter 84h Suspend
Commands table: corrected 07h Data
Added table: CFI Alternate Vendor-Specific Extended Query Parameter A5h,
JEDEC SFDP Rev B
*B
5120122
BWHA
02/01/2016
Changed maximum value of “SCK Clock Frequency for DDR READ” from
80 MHz to 93 MHz in all instances across the document.
Updated to Cypress template.
*C
5519084
CPHX
01/05/2017
Changed maximum value of “SCK Clock Frequency for DDR READ” from
93 MHz to 80 MHz in all instances across the document.
Added Automotive Temperature Range related information in all instances
across the document.
Updated Electrical Specifications:
Added Thermal Resistance.
Updated Address Space Maps:
Updated Registers:
Added ECC Status Register (ECCSR).
Updated Commands:
Updated Register Access Commands:
Added ECC Status Register Read (ECCRD 18h).
Updated Program Flash Array Commands:
Updated Program Granularity:
Added Automatic ECC.
Added Data Integrity.
Updated Software Interface Reference:
Added Device ID and Common Flash Interface (ID-CFI) ASO Map — Automotive Only.
Updated Ordering Information S79FL01GS:
Added Automotive Grade Temperature Range related information.
Added Valid Combinations — Automotive Grade / AEC-Q100.
Updated to new template.
*D
5662192
ECAO
03/22/2017
Updated Timing Specifications:
Updated SDR AC Characteristics:
Updated Table 5-4:
Changed minimum value of tSU parameter from 3 ns to 1.5 ns.
Updated to new template.
Document Number: 002-00466 Rev. *G
Page 117 of 119
S79FL01GS
Document History Page (Continued)
Document Title: S79FL01GS, 1-Gbit (128 MB) Dual-Quad MirrorBit® Flash NVM CMOS 3.0 V Core SPI with Multi-I/O
Document Number: 002-00466
Rev.
ECN No.
Orig. of
Change
Submission
Date
*E
5767680
ECAO
06/08/2017
Replaced “FAB024” with “ZSA024” in all instances across the document.
Updated Address Space Maps on page 34:
Updated Registers on page 37:
Updated Configuration Register 1 (CR1) on page 40:
Updated details corresponding to Bit 4 (Replaced “RFU” with “DNU”).
Updated PDF properties data.
*F
6049406
BWHA
01/29/2018
Updated to new template.
Completing Sunset Review.
*G
6104454
BWHA
03/21/2018
Table 5-4: Removed the Typ value for tCSH and updated the Typ value for tSU
as “3000”.
Document Number: 002-00466 Rev. *G
Description of Change
Page 118 of 119
S79FL01GS
Sales, Solutions, and Legal Information
Worldwide Sales and Design Support
Cypress maintains a worldwide network of offices, solution centers, manufacturer’s representatives, and distributors. To find the office
closest to you, visit us at Cypress Locations.
PSoC® Solutions
Products
Arm® Cortex® Microcontrollers
Automotive
cypress.com/arm
cypress.com/automotive
Clocks & Buffers
Interface
cypress.com/clocks
cypress.com/interface
Internet of Things
Memory
cypress.com/iot
cypress.com/memory
Microcontrollers
cypress.com/mcu
PSoC
cypress.com/psoc
Power Management ICs
cypress.com/pmic
Touch Sensing
Cypress Developer Community
Community | Projects | Video | Blogs | Training | Components
Technical Support
cypress.com/support
cypress.com/touch
USB Controllers
Wireless Connectivity
PSoC 1 | PSoC 3 | PSoC 4 | PSoC 5LP | PSoC 6 MCU
cypress.com/usb
cypress.com/wireless
© Cypress Semiconductor Corporation, 2014-2018. This document is the property of Cypress Semiconductor Corporation and its subsidiaries, including Spansion LLC (“Cypress”). This document,
including any software or firmware included or referenced in this document (“Software”), is owned by Cypress under the intellectual property laws and treaties of the United States and other countries
worldwide. Cypress reserves all rights under such laws and treaties and does not, except as specifically stated in this paragraph, grant any license under its patents, copyrights, trademarks, or other
intellectual property rights. If the Software is not accompanied by a license agreement and you do not otherwise have a written agreement with Cypress governing the use of the Software, then Cypress
hereby grants you a personal, non-exclusive, nontransferable license (without the right to sublicense) (1) under its copyright rights in the Software (a) for Software provided in source code form, to
modify and reproduce the Software solely for use with Cypress hardware products, only internally within your organization, and (b) to distribute the Software in binary code form externally to end users
(either directly or indirectly through resellers and distributors), solely for use on Cypress hardware product units, and (2) under those claims of Cypress's patents that are infringed by the Software (as
provided by Cypress, unmodified) to make, use, distribute, and import the Software solely for use with Cypress hardware products. Any other use, reproduction, modification, translation, or compilation
of the Software is prohibited.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CYPRESS MAKES NO WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, WITH REGARD TO THIS DOCUMENT OR ANY SOFTWARE
OR ACCOMPANYING HARDWARE, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. No computing
device can be absolutely secure. Therefore, despite security measures implemented in Cypress hardware or software products, Cypress does not assume any liability arising out of any security breach,
such as unauthorized access to or use of a Cypress product. In addition, the products described in these materials may contain design defects or errors known as errata which may cause the product
to deviate from published specifications. To the extent permitted by applicable law, Cypress reserves the right to make changes to this document without further notice. Cypress does not assume any
liability arising out of the application or use of any product or circuit described in this document. Any information provided in this document, including any sample design information or programming
code, is provided only for reference purposes. It is the responsibility of the user of this document to properly design, program, and test the functionality and safety of any application made of this
information and any resulting product. Cypress products are not designed, intended, or authorized for use as critical components in systems designed or intended for the operation of weapons, weapons
systems, nuclear installations, life-support devices or systems, other medical devices or systems (including resuscitation equipment and surgical implants), pollution control or hazardous substances
management, or other uses where the failure of the device or system could cause personal injury, death, or property damage ("Unintended Uses"). A critical component is any component of a device
or system whose failure to perform can be reasonably expected to cause the failure of the device or system, or to affect its safety or effectiveness. Cypress is not liable, in whole or in part, and you
shall and hereby do release Cypress from any claim, damage, or other liability arising from or related to all Unintended Uses of Cypress products. You shall indemnify and hold Cypress harmless from
and against all claims, costs, damages, and other liabilities, including claims for personal injury or death, arising from or related to any Unintended Uses of Cypress products.
Cypress, the Cypress logo, Spansion, the Spansion logo, and combinations thereof, WICED, PSoC, CapSense, EZ-USB, F-RAM, and Traveo are trademarks or registered trademarks of Cypress in
the United States and other countries. For a more complete list of Cypress trademarks, visit cypress.com. Other names and brands may be claimed as property of their respective owners.
Document Number: 002-00466 Rev. *G
Revised March 20, 2018
Page 119 of 119
工商网监
湘ICP备2023018690号
