JESD216
JESD216
JESD216
STANDARD
JESD216
APRIL 2011
JEDEC standards and publications contain material that has been prepared, reviewed, and
approved through the JEDEC Board of Directors level and subsequently reviewed and approved
by the JEDEC legal counsel.
JEDEC standards and publications are designed to serve the public interest through eliminating
misunderstandings between manufacturers and purchasers, facilitating interchangeability and
improvement of products, and assisting the purchaser in selecting and obtaining with minimum
delay the proper product for use by those other than JEDEC members, whether the standard is to
be used either domestically or internationally.
JEDEC standards and publications are adopted without regard to whether or not their adoption
may involve patents or articles, materials, or processes. By such action JEDEC does not assume
any liability to any patent owner, nor does it assume any obligation whatever to parties adopting
the JEDEC standards or publications.
The information included in JEDEC standards and publications represents a sound approach to
product specification and application, principally from the solid state device manufacturer
viewpoint. Within the JEDEC organization there are procedures whereby a JEDEC standard or
publication may be further processed and ultimately become an ANSI standard.
No claims to be in conformance with this standard may be made unless all requirements stated in
the standard are met.
Inquiries, comments, and suggestions relative to the content of this JEDEC standard or
publication should be addressed to JEDEC at the address below, or refer to www.jedec.org under
Standards and Documents for alternative contact information.
Published by
©JEDEC Solid State Technology Association 2011
3103 North 10th Street
Suite 240 South
Arlington, VA 22201-2107
This document may be downloaded free of charge; however JEDEC retains the
copyright on this material. By downloading this file the individual agrees not to
charge for or resell the resulting material.
DON’T VIOLATE
THE
LAW!
Contents
Page
Foreword Iii
Introduction iii
1 Scope 1
2 Normative references 1
6 SFDP Database 6
6.1 SFDP Overall Header Structure 6
6.2 SFDP Header 6
6.2.1 SFDP Header: 1st DWORD 6
6.2.2 SFDP Header: 2nd DWORD 7
6.3 Parameter Headers 7
6.3.1 Parameter Header: 1st DWORD 8
6.3.2 Parameter Header: 2nd DWORD 8
6.3.3 Example of an SFDP Header 9
6.4 JEDEC Flash Parameter Tables 10
-i-
JEDEC Standard No. 216
Contents (cont’d)
Page
8 Legacy Compatibility 17
Figures
1 Read SFDP (1-1-1) Mode Timing Diagram 3
2 Read SFDP (2-2-2) Mode Timing Diagram 3
3 Read SFDP (4-4-4) Mode Timing Diagram 4
4 Overall Header Structure 6
5 Example of an SFDP Header 9
Tables
1 JEDEC Flash Parameter Table: 1st DWORD 10
2 JEDEC Flash Parameter Table: 2nd DWORD 12
3 JEDEC Flash Parameter Table: 3rd DWORD 12
4 JEDEC Flash Parameter Table: 4th DWORD 13
5 JEDEC Flash Parameter Table: 5th DWORD 14
6 JEDEC Flash Parameter Table: 6th DWORD 14
7 JEDEC Flash Parameter Table: 7th DWORD 15
8 JEDEC Flash Parameter Table: 8th DWORD 15
9 JEDEC Flash Parameter Table: 9th DWORD 16
-ii-
JEDEC Standard No. 216
Foreword
This document was prepared by the JEDEC SFDP Task Group authorized by the JC-42.4
Committee Chairman.
The intended audience is serial NOR flash vendors and engineers writing device drivers for
SFDP compliant serial flash devices.
Introduction
The Serial Flash Discoverable Parameter (SFDP) standard provides a consistent method of
describing the functional and feature capabilities of serial flash devices in a standard set of
internal parameter tables. These parameter tables can be interrogated by host system software to
enable adjustments needed to accommodate divergent features from multiple vendors. The
concept is similar to the one found in the Introduction of JEDEC Standard, JESD68 on CFI:
“The Common Flash Interface (CFI) specification outlines a device and host system software
interrogation handshake that allows specific software algorithms to be used for entire families of
devices. This allows device-independent, JEDEC ID-independent, and forward- and backward
compatible software support for the specified flash device families. It allows flash vendors to
standardize their existing interfaces for long-term compatibility”.
The current SFDP document defines a common parameter table describing important device
characteristics and serial access methods used to read the parameter table data. Additional
parameter headers and tables can be specified by flash vendors and are optional.
-iii-
JEDEC Standard No. 216
-iv-
JEDEC Standard No. 216
Page 1
(From JEDEC Board Ballot JCB-11-22, formulated under the cognizance of the JC-42.4
Committee on Nonvolatile Memory).
1 Scope
This standard defines the structure of the SFDP database within the memory device and methods
used to read its data.
The JEDEC-defined header and basic flash parameter table is mandatory. Additional flash
vendor-defined headers and tables are optional.
The read instruction protocol using various I/O modes and standard clock rate are specified. The
device operating voltage is not specified.
2 Normative reference
The following normative documents contain provisions that, through reference in this text,
constitute provisions of this standard. For dated references, subsequent amendments to, or
revisions of, any of these publications do not apply. However, parties to agreements based on
this standard are encouraged to investigate the possibility of applying the most recent editions of
the normative documents indicated below. For undated references, the latest edition of the
normative document referred to applies.
(There are no normative documents at this time, but this space is reserved for future use to be in
compliance with JEDEC document standards)
For the purposes of this standard, the following terms and definitions apply:
00b: The ‘b’ suffix indicates the ‘00’ digits are a binary representation of the number.
DTR: Double Transfer Rate. Opcode, address, and/or data may be input or output on both the
rising and falling edges of the clock.
DWORD: Four consecutive 8-bit bytes used as the basic 32-bit building block for headers and
parameter tables.
JEDEC Standard No. 216
Page 2
Instruction: The combination of the opcode, address, and dummy cycles used to issue a command
to the serial flash.
Mode Bits: Optional control bits that follow the address bits. These bits are driven by the
system controller if they are specified.
Wait States: Required dummy clock cycles after the address bits or optional mode bits.
(x-y-z): I/O mode nomenclature used to indicate the number of active pins used for the opcode
(x), address (y), and data (z). At the present time, the only valid Read SFDP instruction modes
are: (1-1-1), (2-2-2), and (4-4-4)
4.1 Opcode
4.2 Address
Indicates the starting read location in the SFDP area and is always expressed as a 24-bit address.
Following the address, eight dummy clocks (8 wait states) are required before valid data is
clocked out.
SFDP compliant devices must support 50 MHz operation for the Read SFDP instruction
(opcode 0x5A). Devices may support a wider frequency range, but a controller can always run
SFDP cycles at 50 MHz or less and get valid results.
The Read SFDP instruction can be used with device supported modes of (1-1-1), (2-2-2), or
(4-4-4), but the opcode (0x5A), address (24 bits), eight dummy clocks (8 wait states), and
50 MHz requirements remain the same.
JEDEC Standard No. 216
Page 3
S#
0 1 2 3 4 5 6 7 8 9 30 31 39 40 41 42 43 44 45 46
C
DOUT1 DOUT2
High Impedance
DQ1 7 6 5 4 3 2 1 0
S#
0 1 2 3 4 5 14 15 23 24 25 26
C
DQ1 0 0 1 1 23 21 3 1 7 5 3 1
S#
0 1 2 3 6 7 15 16
C
DQ1 0 1 21 17 5 1 5 1
DQ2 1 0 22 18 6 2 6 2
DQ3 0 1 23 19 7 3 7 3
5.1 Security
For security reasons, the SFDP and flash memory address ranges must never overlap.
Addresses beyond the end of the SFDP tables must not alias into the flash memory. Regardless
of the implementation, writes to SFDP tables must be permanently disabled after manufacturing.
Functionality will be available during the Read SFDP instruction if the memory device supports
these features.
Not supported with the Read SFDP instruction, even when a memory device defaults to Read
Wrap mode. Only continuous reads are supported with the Read SFDP instruction.
Device behavior when the Read SFDP instruction crosses the SFDP structure boundary is not
defined except for the security restriction specified in 5.1. There is no requirement for the
address counter to wrap back to the beginning of the structure and the data read after that point is
not specified.
The content of reserved SFDP locations (memory within the SFDP address space that has not yet
been defined or used) is not specified, but recommended to be all 0xFF.
JEDEC Standard No. 216
Page 6
6 SFDP Database
The SFDP Header is located at address 0x000000 of the SFDP data structure. It identifies the
SFDP Signature, the number of parameter headers, and the SFDP revision numbers.
Bits Description
SFDP Signature
Allows a user to know that the information is valid.
31:0
Signature[31:0]: 0x50444653
JEDEC Standard No. 216
Page 7
This number must be revised by a vendor or JEDEC when a new parameter header is
added
SFDP Major Revision Number
This 8-bit field indicates the major revision number.
Major revisions are changes that reorganize or add parameters to locations that are NOT
15:8 currently Reserved. Major revisions would require code (BIOS/firmware) or hardware
change to get previously defined discoverable parameters. Major revisions do not
change the overall structure.
Minor revisions are changes that add parameters in existing Reserved locations, or
7:0
clarifications to existing fields. Minor revisions do NOT change overall structure of
SFDP.
NOTE Minor Revision starts at 0x00 and may only be revised by JEDEC.
Identifies the size, location, revision, and ownership of their associated parameter tables.
Parameter table ownership will be either JEDEC (via this document) or an individual vendor (via
vendor specific documentation).
Multiple parameter headers can be specified with each parameter header being 2 DWORDs
(64-bits). The first parameter header is mandatory, defined by JEDEC, and starts at byte offset
0x08. The total number of parameter headers is specified in the NPH field of the SFDP header
(see 6.2.3). All subsequent parameter headers need to be contiguous and may be specified by
JEDEC or by vendors using the same structure (as shown in 6.1).
JEDEC Standard No. 216
Page 8
Bits Description
Parameter Table Length
This field specifies how many DWORDs are in the Parameter table.
31:24
Note: This field is 1’s based. Therefore, 1 indicates 1 DWORD.
Parameter Table Major Revision Number
This 8-bit field indicates the major revision number.
Major revisions are changes that reorganize or add parameters to locations that are
NOT currently Reserved. Major revisions would require code (BIOS/firmware) or
23:16
hardware change to get previously defined discoverable parameters.
Note: Major Revision starts at 0x01. The JEDEC specified Major Revision can only
be modified by JEDEC. The vendor specified Major Revision can only be modified
by the same vendor.
Parameter Table Minor Revision Number
This 8-bit field indicates the minor revision number.
Minor revisions are changes that add parameters in existing Reserved locations, or
15:8
clarifications. Minor revisions do NOT change overall structure of SFDP.
Note: Minor Revision starts at 0x00. The JEDEC specified Minor Revision can only
be modified by JEDEC. The vendor specified Minor Revision can only be modified
by the same vendor.
ID Number:
7:0 If this field is set to 0x00, it indicates a JEDEC specified header. For vendor
specified headers, this field must be set to the vendor’s Manufacturer ID.
Bits Description
Unused
31:24
Contains 0xFF and can never be changed.
Parameter Table Pointer (PTP)
23:0 This 24-bit address specifies the start of this header’s Parameter Table in the SFDP
structure. The address must be DWORD-aligned.
JEDEC Standard No. 216
Page 9
Figure 5 shows an example of an SFDP Header with SFDP Revision 1.0, one Parameter Header,
Parameter Table length of 9 DWORDs, 1st Parameter Header Revision 1.0, JEDEC ID of 0x00,
and the Parameter Table Pointer pointing to location 0x000010.
Hex Byte
[31:24] [23:16] [15:8] [7:0] Location
SFDP 0x50 0x44 0x46 0x53 < [3:0]
Header
0xFF 0x00 0x01 0x00 < [7:4]
1st Parameter 0x09 0x01 0x00 0x00 < [B:8]
Header
0xFF 0x00 0x00 0x10 < [F:C]
Parameter tables contain coded information describing the features and capabilities of the serial
flash. The first parameter table as defined by JEDEC is mandatory and its starting address is
specified by the PTP field of the 1st Parameter Header. The length of this table is nine
DWORDs. This table identifies some of the basic features of flash memory devices.
NOTE All flash devices under 128 megabits in size should use 00b for this value for 24 bit
addressing. This field refers to the number of address bits/bytes that are clocked in for any
instruction requiring an address in the flash array. This field does not pertain to SFDP Header or
Table accesses; all SFDP accesses use 3-byte addressing.
Examples: Read, Fast Read, Write, 4 kilobyte Erase.
JEDEC Standard No. 216
Page 11
0: 0x50 is the Opcode to enable a status register write when bit 3 is set to 1.
4
1: 0x06 is the Opcode to enable a status register write when bit 3 is set to 1.
NOTE If target flash status register is nonvolatile, then bits 3 and 4 must be set to 00b.
Write Enable Instruction Required for Writing to Volatile Status Register
0: Target flash has nonvolatile status bit and does not require status register to be written
on every power on to allow writes and erases.
3
1: Target flash requires a 0x00 to be written to the status register in order to allow writes
and erases.
NOTE If target flash register is nonvolatile, then bits 3 and 4 must be set to 00b.
Write Granularity
2 0: 1 Byte – Use this setting for single byte programmable devices or buffer
programmable devices when the buffer is less than 64 bytes (32 Words).
1: Use this setting for buffer programmable devices when the buffer size is 64 bytes (32
Words) or larger.
Block/Sector Erase Sizes
Identifies the erase granularity for all Flash Components.
23:21 NOTE This field should be counted in clocks not number of bits received by the serial flash.
The master drives the bus during "mode bits" cycles; the master tri-states the bus during
"dummy" cycles.
Example If 4 mode bits are needed with a single input address phase instruction, this
field would be 100b.
(1-1-4) Fast Read Number of Wait states (dummy clocks) needed before valid
output
This field will be 00000b if wait states/dummy clocks are not supported.
20:16 (The number of dummy clocks should be > 0 to avoid contention on bi-directional pins.)
Example If 8 bits are needed with a single input address phase instruction, this field
would be 01000b.
15:8 (1-4-4) Fast Read Opcode
Opcode for single input opcode, quad input address, and quad output data Fast Read.
Quad Input Address Quad Output (1-4-4) Fast Read Number of Mode Bits
This field will be 000b if Mode bits are not supported,
7:5 NOTE This field should be counted in clocks not number of bits received by the serial flash.
The master drives the bus during "mode bits" cycles; the master tri-states the bus during
"dummy" cycles.
Example If 8 mode bits are needed with a quad input address phase instruction, this
field would be 010b.
(1-4-4) Fast Read Number of Wait states (dummy clocks) needed before valid
output
This field will be 00000b if wait states/dummy clocks are not supported.
4:0 (The number of dummy clocks should be > 0 to avoid contention on bi-directional pins.)
Example If 16 bits are needed with a quad input address phase instruction, this field
would be 00100b.
JEDEC Standard No. 216
Page 13
NOTE This field should be counted in clocks not number of bits received by the serial flash.
23:21 The master drives the bus during "mode bits" cycles; the master tri-states the bus during
"dummy" cycles.
Example If 8 mode bits are needed with a dual input address phase instruction, this
field would be 100b.
(1-2-2) Fast Read Number of Wait states (dummy clocks) needed before valid
output
This field will be 00000b if wait states/dummy clocks are not supported.
20:16 (The number of dummy clocks should be > 0 to avoid contention on bi-directional pins.)
Example If 8 bits are needed with a dual input address phase instruction, this field
would be 00100b.
(1-1-2) Fast Read Opcode
15:8 Opcode for single input opcode& address and dual output data Fast Read.
Note: The industry standard is 0x3B
(1-1-2) Fast Read Number of Mode Bits
This field will be 000b if Mode bits are not supported,
7:5 NOTE This field should be counted in clocks not number of bits received by the serial flash.
Example If 4 mode bits are needed with a single input address phase instruction, this
field would be 100b.
(1-1-2) Fast Read Number of Wait states (dummy clocks) needed before valid
output
This field should be programmed with 01000b for 8 clocks of dummy cycle.
4:0 (The number of dummy clocks should be > 0 to avoid contention on bi-directional pins.)
NOTE For legacy reasons, if dummy clocks for this opcode is not 01000b, then bit 16 of Flash
Basic Properties offset 0 (Supports (1-1-2) Fast Read) must NOT be set to ‘1’.
JEDEC Standard No. 216
Page 14
NOTE This field should be counted in clocks not number of bits received by the serial flash.
23:21 The master drives the bus during "mode bits" cycles; the master tri-states the bus during "dummy"
cycles.
Example If 4 mode bits are needed with a (2-2-2) Fast Read instruction, this field
would be 010b.
(2-2-2) Fast Read Number of Wait states (dummy clocks) needed before valid
output
This field will be 00000b if wait states/dummy clocks are not supported.
20:16 (The number of dummy clocks should be > 0 to avoid contention on bi-directional pins.)
Example If 8 bits are needed with a (2-2-2) Fast Read instruction, this field would be
00100b.
15:0 Reserved. These bits default to all 1’s
JEDEC Standard No. 216
Page 15
NOTE This field should be counted in clocks not number of bits received by the serial flash.
23:21 The master drives the bus during "mode bits" cycles; the master tri-states the bus during "dummy"
cycles.
Example If 8 mode bits are needed with a (4-4-4) Fast Read phase instruction, this
field would be 010b.
(4-4-4) Fast Read Number of Wait states (dummy clocks) needed before valid
output
This field will be 00000b if wait states/dummy clocks are not supported.
20:16 (The number of dummy clocks should be > 0 to avoid contention on bi-directional pins.)
Example If 16 bits are needed with a (4-4-4) Fast Read phase instruction, this field
would be 00100b.
15:0 Reserved. These bits default to all 1’s
7:0 NOTE This field specifies ‘N’ and is used to calculate sector/block size = 2^N bytes
Example If the sector size is 256 kilobytes, this field would 0x12.
Sector Type 3 Opcode
15:8
Opcode used to erase the number of bytes specified by Sector Type 3 Size (bits 7-0).
Sector Type 3 Size
This field will be 0x00 if this sector type does not exist.
7:0
NOTE This field specifies ‘N’ and is used to calculate sector/block size = 2^N bytes
Additional headers and parameter tables can be added by vendors without JEDEC approval.
The first four DWORDs of the 6.4 JEDEC Flash Parameters Table can never be modified.
New headers must be built using exactly two DWORDs and they must immediately follow
the existing header(s).
Minimum parameter table size is one DWORD. The maximum parameter table size is not
specified.
Parameter tables may be located anywhere in the SFDP space. They do not need to
immediately follow the parameter headers.
Overlapping parameter tables are permitted.
8 Legacy Compatibility
Prior to the release of this document, Intel published SFDP guidelines with a four DWORD
parameter table. The first four DWORDs of the JEDEC Parameter Table are identical to the table
in Intel's guidelines. Devices in production prior to the release of JESD216 might only contain
these four DWORDs.
STANDARD IMPROVEMENT FORM JEDEC JESD216
The purpose of this form is to provide the Technical Committees of JEDEC with input from the industry
regarding usage of the subject standard. Individuals or companies are invited to submit comments to
JEDEC. All comments will be collected and dispersed to the appropriate committee(s).
If you can provide input, please complete this form and return to:
JEDEC Fax: 703.907.7583
Attn: Publications Department
3103 North 10th Street
Suite 240 South
Arlington, VA 22201-2107
Other
Submitted by
Name: Phone:
Company: E-mail:
Address:
City/State/Zip: Date: