JEDEC JESD68 01-2003 Common Flash Interface (CFI)《通用动画界面(CFI)》.pdf

《JEDEC JESD68 01-2003 Common Flash Interface (CFI)《通用动画界面(CFI)》.pdf》由会员分享，可在线阅读，更多相关《JEDEC JESD68 01-2003 Common Flash Interface (CFI)《通用动画界面(CFI)》.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、JEDEC STANDARD Common Flash Interface (CFI) JESD68.01 (Minor Revision to JESD68, September 1999) SEPTEMBER 2003 JEDEC SOLID STATE TECHNOLOGY ASSOCIATION NOTICE JEDEC standards and publications contain material that has been prepared, reviewed, and approved through the JEDEC Board of Directors level

2、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 pur

3、chaser 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 paten

4、ts 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 approac

5、h 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/EIA standard. No claims to be in conformance w

6、ith 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 call (703) 907-7559 or www.jedec.org Published by JEDEC Solid

7、 State Technology Association 2003 2500 Wilson Boulevard Arlington, VA 22201-3834 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. PRICE: Please ref

8、er to the current Catalog of JEDEC Engineering Standards and Publications online at http:/www.jedec.org/Catalog/catalog.cfm Printed in the U.S.A. All rights reserved PLEASE! DONT VIOLATE THE LAW! This document is copyrighted by the JEDEC Solid State Technology Association and may not be reproduced w

9、ithout permission. Organizations may obtain permission to reproduce a limited number of copies through entering into a license agreement. For information, contact: JEDEC Solid State Technology Association 2500 Wilson Boulevard Arlington, Virginia 22201-3834 or call (703) 907-7559 JEDEC Standard No.

10、68.01 -i- COMMON FLASH INTERFACE (CFI) Contents PageIntroduction ii1 Scope 12 Overview 12.1 Operational summary 13 Hardware interface 13.1 Query command interface 13.2 Query structure output 43.3 Query structure 63.3.1 Query structure overview 63.3.2 Query identification string 73.3.3 Query system i

11、nterface information 83.3.4 Device geomtry definition 93.3.5 Optional algorithm-specific extended 103.3.5.1 Query tables 104 Extensibility 10Annex A 11Tables 1 Command write cycles for query select and deselect 32 Summary of command sequence as a function of device and mode 43 Example of query comma

12、nd sequence of a x8/x16 capable device with an address sensitive query command 44 Summary of query structure output as a function of device and mode 45 Example of query structure output of a x8/x16 capable device 66 Identification string 77 Device-system interface 88 Flash geometry 99 Primary algori

13、thm-specific extended query 1010 Alternate algorithm-specific extended query 10JEDEC Standard No. 68.01 -ii- Introduction 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 f

14、amilies 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. JEDEC Standard No. 68.01 Page 1 COMMO

15、N FLASH INTERFACE (CFI) (From JEDEC Board Ballots JCB-98-81 and JCB-03-42, formulated under the cognizance of the JC-42.4 Subcommittee on Novolatile Memories) 1 Scope This release of the specification defines the basic Query interface for CFI-compliant devices. This allows parameterization of known

16、and future flash Read/Write/Program/Erase control interfaces. This Query structure attempts to define all the critical parameters relevant to a broad base of flash memory devices. The CFI specification will not specify detail command sets, status polling methods, and software algorithms of individua

17、l flash vendors. A 16-bit ID code is assigned to specific algorithm interfaces, and it is up to the algorithm manufacturers to provide these detailed specifications. 2 Overview 2.1 Operational summary After the Query command code has been issued, the device enters the Query mode, allowing reads out

18、of the CFI Query data structure. The CFI Query data structure contains a 16-bit Command Set and Control Interface ID code that specifies an algorithm-specific control interface for a family of flash devices. Query also contains general, common flash memory parameters and algorithm-specified data are

19、as. These provide all the necessary information for controlling Read/Write/Program/Erase operations of a particular family of flash devices according to a algorithm-specified interface. Any additional information not covered in the common CFI Query data structure is located in algorithm-specific ext

20、ended Query Table 9 and Table 10, the address location(s) of which is (are) contained in the general CFI Query structure. 3 Hardware interface 3.1 Query command interface The CFI Query structure is accessed similar to the existing “ID Mode” or “JEDEC ID” access for nonvolatile memories, but uses a d

21、ifferent, non-conflicting command code. The Query access command is 98h, while the JEDEC ID mode access mode is 90h. The Query addressing is always relative to the device word (largest supported) with data always presented on the lowest order byte (D7 - D0 outputs). JEDEC Standard No. 68.01 Page 2 3

22、 Hardware interface (contd) 3.1 Query command interface (contd) Nonvolatile memory devices are assumed to power up in a read-only state. Independent of that assumption, the Query structure contents must be able to be read at the specific address locations following a single system write cycle where:

23、 1) a 98h Query command code is written to 55h address location within the devices address space (in maximum device buswidth), and 2) the device is in any valid read state, such as “Read Array” or “Read ID Data”. Other device states may exist within a long sequence of commands or data input; such se

24、quences must first be completed or terminated before the writing of the 98h Query command code will result in valid Query data structure output. NOTE For devices wider than 8 bits, the valid Query access code has all zeroes (0s) in upper bytes of the data bus. Thus the 16-bit Query command code is 0

25、098h and the 32-bit Query command code is 00000098h. A CFI-compliant device must allow selection and deselection of the Query output mode to and from normal read array operation with a single command write cycle so that the desired data are accessible in the second of two active bus cycles, i.e., bu

26、s cycles in which the devices Chip Enable(s) are active. Table 1 Command write cycles for query select and deselect # of First Bus Cycle Second Bus Cycle Command Cycles Oper Address Data Oper Address Data Read Array 2 Write X FFh/F0h Read AA AD Query 2 Write 55h 98H Read QA QD NOTE 1 “Address” is th

27、e location in maximum device buswidth NOTE 2 Flash devices may or may not have address sensitive query commands. Device drivers should always supply 55h on the address bus and 98h on the data bus to enter query mode; however Flash devices may choose to ignore the address bus and enter query mode if

28、98h is seen on the data bus only NOTE 3 A flash vendor must define other command sequences for other mode accesses as part of the -specific Algorithm and Control Interface specification referenced by the appropriate CFI ID code. Access to and from Query and Read Array modes from any other mode may r

29、equire additional command sequences. NOTE 4 Abbreviations for inputs and outputs of the second cycle refer to address/data for the normal flash array (AA, AD) and Query structure (QA, QD), which may be accessed in random order. JEDEC Standard No. 68.01 Page 3 3 Hardware interface (contd) 3.1 Query c

30、ommand interface (contd) Table 2 Summary of command sequence as a function of device and mode Device type/ mode Command location in maximum device buswidth addresses Command data Command address location in bytes Command data with byte addressing x8 device / x8 mode 55h 98h 55h 98h x16 device / x16

31、mode 55h 0098h AAh AAh: 98h ABh: 00h x16 device / x8 mode N/A * N/A * AAh AAh: 98h x32 device / x32 mode 55h 00000098h 154h 154h: 98h 155h: 00h 156h: 00h 157h: 00h x32 device / x8 mode N/A * N/A * 154h 154h: 98h * The system must drive the lowest order addresses to access all the devices array data

32、when the device is configured in x8 mode. Therefore, word addressing where these lower addresses are not toggled by the system is “Not Applicable” for x8-configured devices. NOTE Flash devices may or may not have address sensitive query commands. Device drivers should always supply 55h on the addres

33、s bus and 98h on the data bus to enter query mode; however Flash devices may choose to ignore the address bus and enter query mode if 98h is seen on the data bus only. Table 3 Example of query command sequence of a x8/x16 capable device with an address sensitive query command Binary Address - x16 Mo

34、de (BYTE#=1) Address : Data Binary Address - x8 Mode (BYTE#=0) Address : Data A8A7A6A5A4A3A2A1A16- A1: D15- D0A7A6A5A4A3A2A1A0A15- A0: D7- D0A7A6A5A4A3A2A1A0A15- A0: D15- D0A6A5A4A3A2A1A0A-1A14- A-1: D7- D00 1 0 1 0 1 0 1 0055h : 0098h 1 0 1 0 1 0 1 0 00Aah : 98h NOTE Address examples provided for d

35、evices with least significant byte address of A0or A-1. JEDEC Standard No. 68.01 Page 4 3 Hardware interface (contd) 3.2 Query structure output Query data are always presented on the lowest-order data outputs (D7 - D0) only. The numerical offset value is the address relative to the maximum bus width

36、 supported by the device. The Query table device starting address is 10h byte address for a byte-wide (x8) device, 10h word address for word-wide (x16) device, 10h “dword” address for a x32 device, etc. Thus for the bytewide (x8) device, the first 2 bytes of the Query structure, “Q” and ”R” in ASCII

37、, appear at device addresses 10h and 11h, which is the same as the absolute byte address. These same data appear on the low byte at word addresses 10h and 11h in a wordwide (x16) device. A CFI-compliant device must output 00H data on upper bytes. Thus, a x16 device outputs ASCII “Q” in the low byte

38、(D7-D0) and 00h in the high byte (D15-D8). The same logic extends to x32 and larger devices, such that: 1) the data are presented in the lowest byte, 2) the data are addressed in maximum-buswidth-relative addresses, and 3) the upper bytes in each data word are filled with 00h data. Thus outputs D31

39、- D8 of a x32 device present 00h data during Query read, starting at word address 10h or byte-relative address 40h. In devices that are x8/x16 capable, the x8 data is still presented in word-relative (16-bit) addresses. However, the “fill data” (00h) is not the same as driven by the upper bytes in t

40、he x16 mode. As in x16 mode, the byte address (A0or A-1depending on pinout) is ignored for Query output so that the “odd byte address” (A0or A-1high) repeats the “even byte address” data (A0or A-1low). Therefore, in x8 mode using byte addressing, such devices will output the sequence “Q”, “Q”, “R”,

41、“R”, “Y”, “Y”, and so on, beginning at byte-relative address 20h (which is equivalent to word offset 10h in x16 mode). Again, this is extensible to x32 and wider devices in that byte addresses are ignored during Query output in x8 mode such that: 1) Query data appears to repeat at each byte address

42、within a word, and 2) the Query data starts at the byte address 10h times the number of bytes of maximum device buswidth. JEDEC Standard No. 68.01 Page 5 3 Hardware interface (contd) 3.2 Query structure output (contd) Table 4 Summary of query structure output as a function of device and mode Device

43、type / mode Query start location in maximum device buswidth addresses Query data with maximum device buswidth addressing “x” = ASCII equivalent Query start address in bytes Query data with byte addressing x8 device /x8 mode 10h 10h: 51h “Q” 11h: 52h “R” 12h: 59h “Y” 10h 10h: 51h “Q” 11h: 52h “R” 12h

44、: 59h “Y” x16 device / x16 mode 10h 10h: 0051h “Q” 11h: 0052h “R” 12h: 0059h “Y” 20h 20h: 51h “Q” 21h: 00h null 22h: 52h “R” x16 device / x8 mode N/A * N/A * 20h 20h: 51h “Q” 21h: 51h “Q” 22h: 52h “R” x32 device / x32 mode 10h 10h: 00000051h “Q” 11h: 00000052h “R” 12h: 00000059h “Y” 40h 40h: 51h “Q”

45、 41h: 00h null 42h: 00h null 43h: 00h null 44h: 52h “R” x32 device / x8 mode N/A * N/A * 40h 40h: 51h “Q” 41h: 51h “Q” 42h: 51h “Q” 43h: 51h “Q” 44h: 52h “R” * The system must drive the lowest order addresses to access all the devices array data when the device is configured in x8 mode. Therefore, w

46、ord addressing where these lower addresses are not toggled by the system is “Not Applicable” for x8-configured devices. JEDEC Standard No. 68.01 Page 6 3 Hardware interface (contd) 3.2 Query structure output (contd) Table 5 Example of query structure output of a x8/x16 capable device Binary Address

47、- x16 Mode (BYTE# =1) Address : Data Binary Address - x8 Mode (BYTE# =0) Address : Data A6A5A4A3A2A1A16- A1: D15- D0A5A4A3A2A1A0A7- A0: D7- D0A5A4A3A2A1A0A15- A0: D15- D0 4A3A2A1A0A-1A6- A-1: D7- D00 1 0 0 0 0 0 1 0 0 0 1 0 1 0 0 1 0 0 1 0 0 1 1 0 1 0 1 0 0 0 1 0 1 0 1 0 1 0 1 1 0 0 1 0 1 1 1 0 1 1

48、0 0 0 0010h: 0051h 0011h: 0052h 0012h: 0059h 0013h: P_IDLO0014h: P_IDHI 0015h: P_ADRLO 0016h: P_ADRHI 0017h: A_IDLO 0018h: A_IDHI“Q” “R” “Y” PrAlgo ID# (lo) PrAlgoID# (hi) PrAlgo TblAdr (lo) PrAlgo TblAdr (hi) AltAlgo ID# (lo) AltAlgo ID# (hi) 1 0 0 0 0 0 1 0 0 0 0 1 1 0 0 0 1 0 1 0 0 0 1 1 1 0 0 1

49、0 0 1 0 0 1 0 1 1 0 0 1 1 0 1 0 0 1 1 1 1 0 1 0 0 0 . 20h: 51h “Q” 21h: 51h “Q” 22h: 52h “R” 23h: 52h “R” 24h: 59h “Y” 25h: 59h “Y” 26h: P_IDLOPrAlgo ID# (lo) 27h: P_IDLO PrAlgo ID# (lo) 28h: P_IDHIPrAlgo ID# (hi) . NOTE Address examples provided for devices with least significant byte address of A0or A-1. 3.3 Query structure 3.3.1 Query structure overview The Query command causes the flash component to display the CFI Query structure or “database.” The structure sub-sections and address locations are summarized as follows: