NumonyxTM Advanced+ Boot Block Flash Memory (C3) 28F800C3, 28F160C3, 28F320C3 (x16) Datasheet Product Features Flexible SmartVoltage Technology -- 2.7 V- 3.6 V read/program/erase -- 12 V for fast production programming 1.65 V to 2.5 V or 2.7 V to 3.6 V I/O Option -- Reduces overall system power High Performance -- 2.7 V- 3.6 V: 70 ns max access time Optimized Architecture for Code Plus Data Storage -- Eight 4 Kword blocks, top or bottom parameter boot -- Up to 127 x 32 Kword blocks -- Fast program suspend capability -- Fast erase suspend capability Flexible Block Locking -- Lock/unlock any block -- Full protection on power-up -- Write Protect (WP#) pin for hardware block protection Low Power Consumption -- 9 mA typical read -- 7 uA typical standby with Automatic Power Savings feature Extended Temperature Operation -- -40 C to +85 C 128-bit Protection Register -- 64 bit unique device identifier -- 64 bit user programmable OTP cells Extended Cycling Capability -- Minimum 100,000 block erase cycles Software -- Supported by Numonyx Advanced Flash File Managers -- NumonyxTM VFM, NumonyxTM FDI, etc. -- Code and data storage in the same memory device -- Robust Power Loss Recovery for Data Loss Prevention -- Common Flash Interface Standard Surface Mount Packaging -- 48-Ball BGA*/VFBGA -- 64-Ball Easy BGA packages -- 48-TSOP package Intel ETOX* VIII (0.13 m) Flash Technology -- 8, 16, 32 Mbit Intel ETOX* VII (0.18 m) Flash Technology -- 16, 32 Mbit Intel ETOX* VI (0.25 m) Flash Technology -- 8, 16 and 32 Mbit 290645-24 March 2008 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH NUMONYXTM PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN NUMONYX'S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS, NUMONYX ASSUMES NO LIABILITY WHATSOEVER, AND NUMONYX DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF NUMONYX PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY PATENT, COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT. Numonyx products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. Legal Lines and Disclaimers Numonyx B.V. may make changes to specifications and product descriptions at any time, without notice. Numonyx B.V. may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Numonyx reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. Contact your local Numonyx sales office or your distributor to obtain the latest specifications and before placing your product order. Copies of documents which have an order number and are referenced in this document, or other Numonyx literature may be obtained by visiting the Numonyx website at http://www.numonyx.com. Numonyx, the Numonyx logo, and StrataFlash are trademarks or registered trademarks of Numonyx B.V. or its subsidiaries in other countries. *Other names and brands may be claimed as the property of others. Copyright (c) 2008, Numonyx B.V., All Rights Reserved. Datasheet 2 March 2008 290645-24 C3 Discrete Contents 1.0 Introduction .............................................................................................................. 7 1.1 Nomenclature ..................................................................................................... 7 1.2 Conventions ....................................................................................................... 8 2.0 Functional Overview .................................................................................................. 9 2.1 Product Overview ................................................................................................ 9 2.2 Block Diagram .................................................................................................. 10 2.3 Memory Map..................................................................................................... 10 3.0 Package Information ............................................................................................... 13 3.1 mBGA* and VF BGA Package .............................................................................. 13 3.2 TSOP Package................................................................................................... 14 3.3 Easy BGA Package............................................................................................. 15 4.0 Ballout and Signal Descriptions ............................................................................... 16 4.1 48-Lead TSOP Package ...................................................................................... 16 4.2 64-Ball Easy BGA Package .................................................................................. 19 4.3 Signal Descriptions ............................................................................................ 19 5.0 Maximum Ratings and Operating Conditions............................................................ 21 5.1 Absolute Maximum Ratings................................................................................. 21 5.2 Operating Conditions ......................................................................................... 21 6.0 Electrical Specifications ........................................................................................... 23 6.1 Current Characteristics....................................................................................... 23 6.2 DC Voltage Characteristics.................................................................................. 24 7.0 AC Characteristics ................................................................................................... 26 7.1 AC Read Characteristics ..................................................................................... 26 7.2 AC Write Characteristics ..................................................................................... 30 7.3 Erase and Program Timings ................................................................................ 34 7.4 AC I/O Test Conditions....................................................................................... 34 7.5 Device Capacitance ........................................................................................... 35 8.0 Power and Reset Specifications ............................................................................... 36 8.1 Active Power (Program/Erase/Read) .................................................................... 36 8.2 Automatic Power Savings (APS) .......................................................................... 36 8.3 Standby Power.................................................................................................. 36 8.4 Deep Power-Down Mode..................................................................................... 36 8.5 Power and Reset Considerations .......................................................................... 37 8.5.1 Power-Up/Down Characteristics................................................................ 37 8.5.2 RP# Connected to System Reset .............................................................. 37 8.5.3 VCC, VPP and RP# Transitions.................................................................. 37 8.5.4 Reset Specifications................................................................................ 37 8.6 Power Supply Decoupling ................................................................................... 38 9.0 Device Operations ................................................................................................... 39 9.1 Bus Operations ................................................................................................. 39 9.1.1 Read .................................................................................................... 39 9.1.2 Write .................................................................................................... 39 9.1.3 Output Disable ....................................................................................... 39 9.1.4 Standby ................................................................................................ 39 9.1.5 Reset.................................................................................................... 40 10.0 Modes of Operation ................................................................................................. 41 March 2008 290645-24 Datasheet 3 C3 Discrete 10.1 10.2 10.3 Read Mode........................................................................................................41 10.1.1 Read Array ............................................................................................41 10.1.2 Read Identifier .......................................................................................41 10.1.3 CFI Query ..............................................................................................42 10.1.4 Read Status Register...............................................................................42 10.1.4.1 Clear Status Register .................................................................43 Program Mode...................................................................................................43 10.2.1 12-Volt Production Programming ..............................................................43 10.2.2 Suspending and Resuming Program ..........................................................44 Erase Mode .......................................................................................................44 10.3.1 Suspending and Resuming Erase ..............................................................44 11.0 Security Modes ........................................................................................................48 11.1 Flexible Block Locking.........................................................................................48 11.1.1 Locking Operation...................................................................................48 11.1.1.1 Locked State ............................................................................49 11.1.1.2 Unlocked State .........................................................................49 11.1.1.3 Lock-Down State.......................................................................49 11.2 Reading Block-Lock Status ..................................................................................49 11.3 Locking Operations during Erase Suspend .............................................................49 11.4 Status Register Error Checking ............................................................................50 11.5 128-Bit Protection Register .................................................................................50 11.5.1 Reading the Protection Register ................................................................50 11.5.2 Programming the Protection Register.........................................................51 11.5.3 Locking the Protection Register.................................................................51 11.6 VPP Program and Erase Voltages ..........................................................................51 11.6.1 Program Protection .................................................................................51 Datasheet 4 March 2008 290645-24 C3 Discrete Revision History Date of Revision Version 05/12/98 -001 Original version -002 48-Lead TSOP package diagram change BGA package diagrams change 32-Mbit ordering information change (Section 6) CFI Query Structure Output Table Change (Table C2) CFI Primary-Vendor Specific Extended Query Table Change for Optional Features and Command Support change (Table C8) Protection Register Address Change IPPD test conditions clarification (Section 4.3) BGA package top side mark information clarification (Section 6) 10/03/98 -003 Byte-Wide Protection Register Address change VIH Specification change (Section 4.3) VIL Maximum Specification change (Section 4.3) ICCS test conditions clarification (Section 4.3) Added Command Sequence Error Note (Table 7) Datasheet renamed from 3 Volt Advanced Boot Block, 8-, 16-, 32-Mbit Flash Memory Family. 12/04/98 -004 Added tBHWH/tBHEH and tQVBL (Section 4.6) Programming the Protection Register clarification (Section 3.4.2) 12/31/98 -005 Removed all references to x8 configurations 02/24/99 -006 Removed reference to 40-Lead TSOP from front page 06/10/99 -007 Added Easy BGA package (Section 1.2) Removed 1.8 V I/O references Locking Operations Flowchart changed (Appendix B) Added tWHGL (Section 4.6) CFI Primary Vendor-Specific Extended Query changed (Appendix C) 03/20/00 -008 Max ICCD changed to 25 A Table 10, added note indicating VCCMax = 3.3 V for 32-Mbit device 04/24/00 -009 Added specifications for 0.18 micron product offerings throughout document Added 64Mbit density -010 Changed references of 32Mbit 80ns devices to 70ns devices to reflect the faster product offering. Changed VccMax=3.3V reference to indicate that the affected product is the 0.25m 32Mbit device. Minor text edits throughout document. 7/20/01 -011 Added 1.8v I/O operation documentation where applicable Added TSOP PCN `Pin-1' indicator information Changed references in 8 x 8 BGA pinout diagrams from `GND' to `Vssq' Added `Vssq' to Pin Descriptions Information Removed 0.4 m references in DC characteristics table Corrected 64Mb package Ordering Information from 48-uBGA to 48-VFBGA Corrected `bottom' parameter block sizes to on 8Mb device to 8 x 4KWords Minor text edits throughout document 10/02/01 -012 Added specifications for 0.13 micron product offerings throughout document -013 Corrected Iccw / Ippw / Icces /Ippes values. Added mechanicals for 16Mb and 64Mb Minor text edits throughout document. 4/05/02 -014 Updated 64Mb product offerings. Updated 16Mb product offerings. Revised and corrected DC Characteristics Table. Added mechanicals for Easy BGA. Minor text edits throughout document. 3/06/03 -016 Complete technical update. 07/21/98 10/12/00 2/05/02 March 2008 290645-24 Description Datasheet 5 C3 Discrete Date of Revision Version 10/01/03 -017 Corrected information in the Device Geometry Details table, address 0x34. 5/20/04 -018 Updated the layout of the datasheet. 9/1/04 -019 Fixed typo for Standby power on cover page. 9/14/04 -020 Added lead-free line items to Table 38, "Product Information Ordering Matrix" on page 70. 9/27/04 -021 Added specification for 8Mb 0.13 micron device. Added 0.13 micron to Table 38, "Product Information Ordering Matrix" on page 70. 1/26/05 -022 Converted datasheet to new template. Deleted Description in Table 4. Deleted Note in Figure 5. 5/16/05 -023 Removed all 64M ordering information, removed VF BGA 8M ordering information. Removed 64M reference in title page only. Added software verbiage in title page. Corrected Lead Width (b) measurement in Fig 2., uBGA and VF BGA Package Drawing and Dimensions, page 12. March 2008 24 Datasheet 6 Description Applied Numnyx branding. March 2008 290645-24 C3 Discrete 1.0 Introduction This datasheet contains the specifications for the NumonyxTM Advanced+ Boot Block Flash Memory (C3) device family, hereafter called the C3 flash memory device. These flash memories add features such as instant block locking and protection registers that can be used to enhance the security of systems. The NumonyxTM Advanced+ Book Block Flash Memory (C3) device, manufactured on Intel's latest 0.13 m and 0.18 m technologies, represents a feature-rich solution for low-power applications. The C3 device incorporates low-voltage capability (3 V read, program, and erase) with high-speed, low-power operation. Flexible block locking allows any block to be independently locked or unlocked. Add to this the NumonyxTM Flash Data Integrator (NumonyxTM FDI) software and you have a cost-effective, flexible, monolithic code plus data storage solution. NumonyxTM Advanced+ Boot Block Flash Memory (C3) products are available in 48-lead TSOP, 48-ball CSP, and 64-ball Easy BGA packages. Additional information on this product family can be obtained from the NumonyxTM Flash website: http://www.Numonyx.com 1.1 Nomenclature 0x Hexadecimal prefix 0b Binary prefix Byte 8 bits Word 16 bits KW or Kword 1024 words March 2008 290645-24 Mword 1,048,576 words Kb 1024 bits KB 1024 bytes Mb 1,048,576 bits MB 1,048,576 bytes APS Automatic Power Savings CSP Chip Scale Package CUI Command User Interface OTP One Time Programmable PR Protection Register PRD Protection Register Data PLR Protection Lock Register RFU Reserved for Future Use SR Status Register SRD Status Register Data WSM Write State Machine Datasheet 7 C3 Discrete 1.2 Conventions The terms pin and signal are often used interchangeably to refer to the external signal connections on the package; for chip scale package (CSP) the term ball is used. Group Membership Brackets: Square brackets will be used to designate group membership or to define a group of signals with similar function (i.e. A[21:1], SR[4:1]) Set: When referring to registers, the term set means the bit is a logical 1. Clear: When referring to registers, the term clear means the bit is a logical 0. Block: A group of bits (or words) that erase simultaneously with one block erase instruction. Main Block: A block that contains 32 Kwords. Parameter Block: A block that contains 4 Kwords. Datasheet 8 March 2008 290645-24 C3 Discrete 2.0 Functional Overview This section provides an overview of the NumonyxTM Advanced+ Boot Block Flash Memory (C3) device features and architecture. 2.1 Product Overview The C3 flash memory device provides high-performance asynchronous reads in package-compatible densities with a 16 bit data bus. Individually-erasable memory blocks are optimally sized for code and data storage. Eight 4 Kword parameter blocks are located in the boot block at either the top or bottom of the device's memory map. The rest of the memory array is grouped into 32 Kword main blocks. The device supports read-array mode operations at various I/O voltages (1.8 V and 3 V) and erase and program operations at 3 V or 12 V VPP. With the 3 V I/O option, VCC and VPP can be tied together for a simple, ultra-low-power design. In addition to I/O voltage flexibility, the dedicated VPP input provides complete data protection when VPP VPPLK. The C3 Discrete device features a 128-bit protection register enabling security techniques and data protection schemes through a combination of factory-programmed and user-programmable OTP data registers. Zero-latency locking/unlocking on any memory block provides instant and complete protection for critical system code and data. Additional block lock-down capability provides hardware protection where software commands alone cannot change the block's protection status. A command User Interface (CUI) serves as the interface between the system processor and internal operation of the device. A valid command sequence issued to the CUI initiates device automation. An internal Write State Machine (WSM) automatically executes the algorithms and timings necessary for block erase, program, and lock-bit configuration operations. The device offers three low-power saving features: Automatic Power Savings (APS), standby mode, and deep power-down mode. The device automatically enters APS mode following read cycle completion. Standby mode begins when the system deselects the flash memory by deasserting Chip Enable, CE#. The deep power-down mode begins when Reset Deep Power-Down, RP# is asserted, which deselects the memory and places the outputs in a high-impedance state, producing ultra-low power savings. Combined, these three power-savings features significantly enhanced power consumption flexibility. March 2008 290645-24 Datasheet 9 C3 Discrete 2.2 Figure 1: Block Diagram C3 Flash Memory Device Block Diagram DQ 0-DQ 15 VCCQ Input Buffer Identifier Register Status Register Power Reduction Control Data Comparator Y-Decoder Y-Gating/Sensing Da ta Re gi ster Outp ut M ulti ple xer Output Buffer I/O Logic CE# WE# OE# RP# Command User Interface WP# X-Decoder Address Counter 2.3 32- KWord M ain Blo ck Address Latch 4 -KWor d Para mete r B loc k 32- KWord M ain Blo ck Input Buffer 4 -KWor d Para mete r B loc k A[MAX:MIN] Write State Machine Program/Erase Voltage Switch VPP VCC GND Memory Map The C3 Discrete device is asymmetrically blocked, which enables system code and data integration within a single flash device. The bulk of the array is divided into 32 Kword main blocks that can store code or data, and 4 Kword boot blocks to facilitate storage of boot code or for frequently changing small parameters. See Table 1, "Top Boot Memory Map" on page 11 and Table 2, "Bottom Boot Memory Map" on page 12 for details. Datasheet 10 March 2008 290645-24 C3 Discrete Table 1: Top Boot Memory Map Size (KW ) Blk 8-Mbit Memory Addressin g (Hex) Size (KW ) Blk 16-Mbit Memory Addressing (Hex) Size (KW ) Blk 32-Mbit Memory Addressin g (Hex) Size (KW ) Blk 64-Mbit Memory Addressing (Hex) 4 22 7F0007FFFF 4 38 FF000-FFFFF 4 70 1FF0001FFFFF 4 134 3FF000-3FFFFF 4 21 7E0007EFFF 4 37 FE000-FEFFF 4 69 1FE0001FEFFF 4 133 3FE000-3FEFFF 4 20 7D0007DFFF 4 36 FD000-FDFFF 4 68 1FD0001FDFFF 4 132 3FD000-3FDFFF 4 19 7C0007CFFF 4 35 FC000-FCFFF 4 67 1FC0001FCFFF 4 131 3FC000-3FCFFF 4 18 7B0007BFFF 4 34 FB000-FBFFF 4 66 1FB0001FBFFF 4 130 3FB000-3FBFFF 4 17 7A0007AFFF 4 33 FA000-FAFFF 4 65 1FA0001FAFFF 4 129 3FA000-3FAFFF 4 16 7900079FFF 4 32 F9000-F9FFF 4 64 1F90001F9FFF 4 128 3F9000-3F9FFF 4 15 7800078FFF 4 31 F8000-F8FFF 4 63 1F80001F8FFF 4 127 3F8000-3F8FFF 32 14 7000077FFF 32 30 F0000-F7FFF 32 62 1F00001F7FFF 32 126 3F0000-3F7FFF 32 13 680006FFFF 32 29 E8000-EFFFF 32 61 1E80001EFFFF 32 125 3E8000-3EFFFF 32 12 6000067FFF 32 28 E0000-E7FFF 32 60 1E00001E7FFF 32 124 3E0000-3E7FFF 32 11 580005FFFF 32 27 D8000-DFFFF 32 59 1D80001DFFFF 32 123 3D8000-3DFFFF ... ... ... ... ... ... ... ... ... ... ... ... 32 2 1000017FFF 32 2 10000-17FFF 32 2 1000017FFF 32 2 10000-17FFF 32 1 8000-0FFFF 32 1 08000-0FFFF 32 1 080000FFFF 32 1 08000-0FFFF 32 0 0000-07FFF 32 0 00000-07FFF 32 0 0000007FFF 32 0 00000-07FFF March 2008 290645-24 Datasheet 11 C3 Discrete Table 2: Bottom Boot Memory Map Size (KW ) Blk 8-Mbit Memory Addressin g (Hex) Size (KW ) Blk 16-Mbit Memory Addressing (Hex) Size (KW ) Blk 32-Mbit Memory Addressing (Hex) Size (KW ) Blk 64-Mbit Memory Addressing (Hex) 32 22 780007FFFF 32 38 F8000-FFFFF 32 70 1F80001FFFFF 32 134 3F8000-3FFFFF 32 21 7000077FFF 32 37 F0000-F7FFF 32 69 1F00001F7FFF 32 133 3F0000-3F7FFF 32 20 680006FFFF 32 36 E8000-EFFFF 32 68 1E80001EFFFF 32 132 3E8000-3EFFFF 32 19 6000067FFF 32 35 E0000-E7FFF 32 67 1E00001E7FFF 32 131 3E0000-3E7FFF ... ... ... ... ... ... ... ... ... . ... ... 32 10 180001FFFF 32 10 18000-1FFFF 32 10 18000-1FFFF 32 10 18000-1FFFF 32 9 1000017FFF 32 9 10000-17FFF 32 9 10000-17FFF 32 9 10000-17FFF 32 8 080000FFFF 32 8 08000-0FFFF 32 8 08000-0FFFF 32 8 08000-0FFFF 4 7 0700007FFF 4 7 07000-07FFF 4 7 07000-07FFF 4 7 07000-07FFF 4 6 0600006FFF 4 6 06000-06FFF 4 6 06000-06FFF 4 6 06000-06FFF 4 5 0500005FFF 4 5 05000-05FFF 4 5 05000-05FFF 4 5 05000-05FFF 4 4 0400004FFF 4 4 04000-04FFF 4 4 04000-04FFF 4 4 04000-04FFF 4 3 0300003FFF 4 3 03000-03FFF 4 3 03000-03FFF 4 3 03000-03FFF 4 2 0200002FFF 4 2 02000-02FFF 4 2 02000-02FFF 4 2 02000-02FFF 4 1 0100001FFF 4 1 01000-01FFF 4 1 01000-01FFF 4 1 01000-01FFF 4 0 0000000FFF 4 0 00000-00FFF 4 0 00000-00FFF 4 0 00000-00FFF Datasheet 12 March 2008 290645-24 C3 Discrete 3.0 Package Information 3.1 BGA* and VF BGA Package Figure 2: BGA* and VF BGA Package Drawing and Dimensions C3 Discrete 8/16/32/64M, .25,.18, .13u ubga/VFBGA R0 Ball A1 Corner D 1 E 2 3 4 S1 5 6 7 8 8 A A B B C C D D E E F F 7 6 4 5 3 Ball A1 Corner S2 2 1 e b Bottom View -Bump side up Top View - Bump Side down A 1 A2 A Seating Y Plan Side View Note: Drawing not to scale Dimensions Symbol Package Height A Ball Height A1 Package Body Thickness A2 Ball (Lead) Width b Package Body Length 8M (.25) D Package Body Length 16M (.25/.18/.13) 32M (.25/.18/.13) D Package Body Length 64M (.18) D Package Body Width 8M (.25) E Package Body Width 16M (.25/.18/.13) 32M (.18/.13) E Package Body Width 32M (.25) E Package Body Width 64M (.18) E Pitch e Ball (Lead) Count 8M, 16M N Ball (Lead) Count 32M N Ball (Lead) Count 64M N Seating Plane Coplanarity Y Corner to Ball A1 Distance Along D 8M (.25) S1 Corner to Ball A1 Distance Along D 16M (.25/.18/.13) 32M (.18/.13) S1 Corner to Ball A1 Distance Along D 64M (.18) S1 Corner to Ball A1 Distance Along E 8M (.25) S2 Corner to Ball A1 Distance Along E 16M (.25/.18/.13) 32M (.18/.13) S2 Corner to Ball A1 Distance Along E 32M (.25) S2 Corner to Ball A1 Distance Along E 64M (.18) S2 March 2008 290645-24 Min Millimeters Nom Max 1.000 0.150 0.325 7.810 7.186 7.600 6.400 6.864 10.750 8.900 1.230 0.918 1.125 1.275 1.507 3.450 2.525 Min Inches Nom Max 0.0394 0.0059 0.665 0.375 7.910 7.286 7.700 6.500 6.964 10.850 9.000 0.750 46 47 48 1.330 1.018 1.225 1.375 1.607 3.550 2.625 0.0128 0.0262 0.0148 0.425 8.010 7.386 7.800 6.600 7.064 10.860 9.100 0.2829 0.2992 0.2520 0.2702 0.4232 0.3504 0.2868 0.3031 0.2559 0.2742 0.4272 0.3543 0.0295 46 47 48 0.100 1.430 1.118 1.325 1.475 1.707 3.650 2.725 0.0484 0.0361 0.0443 0.0502 0.0593 0.1358 0.0994 0.0524 0.0401 0.0482 0.0541 0.0633 0.1398 0.1033 0.0167 0.2908 0.3071 0.2598 0.2781 0.4276 0.3583 0.0039 0.0563 0.0440 0.0522 0.0581 0.0672 0.1437 0.1073 Datasheet 13 C3 Discrete 3.2 TSOP Package Figure 3: TSOP Package Drawing and Dimensions Z A2 See Notes 1, 2, 3 and 4 Pin 1 e See Detail B E Y D1 A1 D Seating Plane See Detail A A Detail A Detail B C b 0 L Notes: 1. One dimple on package denotes Pin 1. 2. If two dimples, then the larger dimple denotes Pin 1. 3. Pin 1 will always be in the upper left corner of the package, in reference to the product mark. Table 3: TSOP Package Dimensions Millimeters Parameter Inches Symbol Min Package Height A Nom Max Min Nom 1.200 Standoff A1 0.050 Package Body Thickness A2 0.950 Max 0.047 0.002 1.000 1.050 0.037 0.039 0.041 Lead Width b 0.150 0.200 0.300 0.006 0.008 0.012 Lead Thickness c 0.100 0.150 0.200 0.004 0.006 0.008 Package Body Length D1 18.200 18.400 18.600 0.717 0.724 0.732 Package Body Width E 11.800 12.000 12.200 0.465 0.472 0.480 Lead Pitch e Terminal Dimension D 19.800 20.000 20.200 0.780 0.787 0.795 Lead Tip Length L 0.500 0.600 0.700 0.020 0.024 0.028 Lead Count N Lead Tip Angle Seating Plane Coplanarity Y Lead to Package Offset Z Datasheet 14 0.500 0.0197 48 0 3 48 5 0 3 0.100 0.150 0.250 0.350 5 0.004 0.006 0.010 0.014 March 2008 290645-24 C3 Discrete 3.3 Figure 4: Easy BGA Package Easy BGA Package Drawing and Dimension Ball A1 Corner D 1 E 2 3 4 Ball A1 Corner S1 5 6 7 8 8 A A B B C C D D E E F F G G H H 7 6 5 4 3 2 1 S2 b e Top View - Ball side down Bottom View - Ball Side Up A1 A2 A Seating Y Plane Side View Note: Drawing not to scale Dimensions Table Package Height Ball Height Package Body Thickness Ball (Lead) Width Package Body Width Package Body Length Pitch Ball (Lead) Count Seating Plane Coplanarity Corner to Ball A1 Distance Along D Corner to Ball A1 Distance Along E Symbol A A1 A2 b D E [e] N Y S1 S2 Millimeters Min Nom Max 1.200 Notes 0.250 0.330 9.900 12.900 1.400 2.900 Inches Min Nom Max 0.0472 0.0098 0.780 0.430 10.000 13.000 1.000 64 1.500 3.000 0.530 10.100 13.100 1 1 0.0130 0.3898 0.5079 0.100 1.600 3.100 1 1 0.0551 0.1142 0.0307 0.0169 0.3937 0.5118 0.0394 64 0.0591 0.1181 0.0209 0.3976 0.5157 0.0039 0.0630 0.1220 Note: (1) Package dimensions are for reference only. These dimensions are estimates based on die size, and are subject to change. March 2008 290645-24 Datasheet 15 C3 Discrete 4.0 Ballout and Signal Descriptions The C3 device is available in 48-lead TSOP, 48-ball VF BGA, 48-ball BGA, and Easy BGA packages. See Figure 5 on page 16, Figure 7 on page 18, and Figure 8 on page 19, respectively. 4.1 48-Lead TSOP Package Figure 5: 48-Lead TSOP Package 64 M 32 M 16 M Datasheet 16 A15 A14 A13 A12 A11 A10 A9 A8 A21 A20 WE# RP# VPP WP# A19 A18 A17 A7 A6 A5 A4 A3 A2 A1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 Advanced+ Boot Block 48-Lead TSOP 12 mm x 20 mm TOP VIEW 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 A16 VCCQ GND DQ15 DQ7 DQ14 DQ6 DQ13 DQ5 DQ12 DQ4 VCC DQ11 DQ3 DQ10 DQ2 DQ9 DQ1 DQ8 DQ0 OE# GND CE# A0 March 2008 290645-24 C3 Discrete Figure 6: Mark for Pin-1 Indicator on 48-Lead 8-Mb, 16-Mb and 32-Mb TSOP Current M ark: New M ark: Note: Table 4: The topside marking on 8 Mb, 16 Mb, and 32 Mb NumonyxTM Advanced and Advanced + Boot Block 48L TSOP products will convert to a white ink triangle as a Pin 1 indicator. Products without the white triangle will continue to use a dimple as a Pin 1 indicator. There are no other changes in package size, materials, functionality, customer handling, or manufacturability. Product will continue to meet Numonyx stringent quality requirements. Products affected are Numonyx Ordering Codes shown in Table 4. 48-Lead TSOP Extended 64 Mbit Extended Extended 32 Mbit Extended 16 Mbit TE28F320C3TD70 TE28F320C3BD70 TE28F160C3TD70 TE28F160C3BD70 TE28F800C3TA90 TE28F800C3BA90 TE28F320C3TC70 TE28F320C3BC70 TE28F160C3TC80 TE28F160C3BC80 TE28F800C3TA110 TE28F800C3BA110 TE28F320C3TC90 TE28F320C3BC90 TE28F160C3TA90 TE28F160C3BA90 TE28F320C3TA100 TE28F320C3BA100 TE28F160C3TA110 TE28F160C3BA110 TE28F320C3TA110 TE28F320C3BA110 March 2008 290645-24 Datasheet 17 C3 Discrete Figure 7: 48-Ball BGA* and 48-Ball VF BGA Chip Scale Package (Top View, Ball Down)1,2,3 1 2 3 4 5 6 7 8 16M A A13 A11 A8 VPP WP# A19 A7 A4 B A14 A10 WE# RP# A18 A17 A5 A2 64M 32M C A15 A12 A9 A21 A20 A6 A3 A1 D A16 D14 D5 D11 D2 D8 CE# A0 E VCCQ D15 D6 D12 D3 D9 D0 GND F GND D7 D13 D4 VCC D10 D1 OE# Notes: 1. Shaded connections indicate the upgrade address connections. Numonyx recommends to not use routing in this area. 2. A19 denotes 16 Mbit; A20 denotes 32 Mbit; A21 denotes 64 Mbit. 3. Unused address balls are not populated. Datasheet 18 March 2008 290645-24 C3 Discrete 4.2 64-Ball Easy BGA Package Figure 8: 64-Ball Easy BGA Package1,2 1 2 3 4 5 6 7 8 A 8 7 6 5 4 3 2 1 VPP A18 A A1 A6 A18 VPP VCC GND A10 A15 B A15 A10 GND VCC A6 A1 A14 A11 A20(1) DU RP# A19(1) A17 A2 A13 A12 A21(1) DU WE# WP# A7 A3 A9 A8 A4 B A2 A17 A19(1) RP# DU A20(1) A11 A14 C C A3 A7 WP# WE# DU A21(1) A12 A13 D D A4 A5 DU DU DU DU A8 A9 DQ8 DQ1 DQ9 DQ3 DQ12 DQ6 DU DU E DU DU DU DU A5 E F DU DU DQ6 DQ12 DQ3 DQ9 DQ1 DQ8 DU DU DQ14 DQ5 DQ11 DQ10 DQ0 CE# F CE# DQ0 DQ10 DQ11 DQ5 DQ14 DU DU G G A0 VSSQ DQ2 DQ4 DQ13 DQ15 VSSQ A16 H A16 VSSQ D15 D13 DQ4 DQ2 VSSQ A0 DU VCCQ VSSQ VCC VCCQ OE# A22(2) H A22(2) OE# VCCQ VCC VSSQ DQ7 VCCQ DU Top View- Ball Side D7 Bottom View - Ball Side Notes: 1. A19 denotes 16 Mbit; A20 denotes 32 Mbit; A21 denotes 64 Mbit. 2. Unused address balls are not populated. 4.3 Table 5: Symbol Signal Descriptions Signal Descriptions Type Description A[MAX:0] Input ADDRESS INPUTS for memory addresses. Address are internally latched during a program or erase cycle. 8 Mbit: AMAX= A18 16 Mbit: AMAX = A19 32 Mbit: AMAX = A20 64 Mbit: AMAX = A21 DQ[15:0] Input/ Output DATA INPUTS/OUTPUTS: Inputs data and commands during a write cycle; outputs data during read cycles. Inputs commands to the Command User Interface when CE# and WE# are active. Data is internally latched. The data pins float to tri-state when the chip is de-selected or the outputs are disabled. CE# Input CHIP ENABLE: Active-low input. Activates the internal control logic, input buffers, decoders and sense amplifiers. CE# is active low. CE# high de-selects the memory device and reduces power consumption to standby levels. OE# Input OUTPUT ENABLE: Active-low input. Enables the device's outputs through the data buffers during a Read operation. Input RESET/DEEP POWER-DOWN: Active-low input. When RP# is at logic low, the device is in reset/deep power-down mode, which drives the outputs to High-Z, resets the Write State Machine, and minimizes current levels (ICCD). When RP# is at logic high, the device is in standard operation. When RP# transitions from logic-low to logic-high, the device resets all blocks to locked and defaults to the read array mode. RP# March 2008 290645-24 Datasheet 19 C3 Discrete Table 5: Signal Descriptions Symbol Type Description WE# Input WRITE ENABLE: Active-low input. WE# controls writes to the device. Address and data are latched on the rising edge of the WE# pulse. Input WRITE PROTECT: Active-low input. When WP# is a logic low, the lock-down mechanism is enabled and blocks marked lock-down cannot be unlocked through software. When WP# is logic high, the lock-down mechanism is disabled and blocks previously locked-down are now locked and can be unlocked and locked through software. After WP# goes low, any blocks previously marked lock-down revert to the lock-down state. See Section 11.0, "Security Modes" on page 48 for details on block locking. VPP Input/ Power PROGRAM/ERASE Power Supply: Operates as an input at logic levels to control complete device protection. Supplies power for accelerated Program and Erase operations in 12 V 5% range. Do not leave this pin floating. Lower VPP VPPLK to protect all contents against Program and Erase commands. Set VPP = VCC for in-system Read, Program and Erase operations. In this configuration, VPP can drop as low as 1.65 V to allow for resistor or diode drop from the system supply. Apply VPP to 12 V 5% for faster program and erase in a production environment. Applying 12 V 5% to VPP can only be done for a maximum of 1000 cycles on the main blocks and 2500 cycles on the boot blocks. VPP can be connected to 12 V for a total of 80 hours maximum. See Section 11.6 for details on VPP voltage configurations. VCC Power DEVICE CORE Power Supply: Supplies power for device operations. VCCQ Power OUTPUT Power Supply: Output-driven source voltage. This ball can be tied directly to VCC if operating within VCC range. GND Power Ground: For all internal circuitry. All ground inputs must be connected. DU -- Do Not Use: Do not use this ball. This ball must not be connected to any power supplies, signals or other balls,; it must be left floating. NC -- No Connect WP# Datasheet 20 March 2008 290645-24 C3 Discrete 5.0 Maximum Ratings and Operating Conditions 5.1 Absolute Maximum Ratings Warning: Stressing the device beyond the "Absolute Maximum Ratings" may cause permanent damage. These ratings are stress ratings only. Operation beyond the "Operating Conditions" is not recommended, and extended exposure beyond the "Operating Conditions" may affect device reliability. . NOTICE: Specifications are subject to change without notice. Verify with your local Numonyx Sales office that you have the latest datasheet before finalizing a design. Parameter Maximum Rating Notes Extended Operating Temperature During Read -40 C to +85 C During Block Erase and Program -40 C to +85 C Temperature under Bias -40 C to +85 C Storage Temperature -65 C to +125 C Voltage On Any Pin (except VCC and VPP) with Respect to GND -0.5 V to +3.7 V VPP Voltage (for Block Erase and Program) with Respect to GND -0.5 V to +13.5 V VCC and VCCQ Supply Voltage with Respect to GND -0.2 V to +3.6 V Output Short Circuit Current 100 mA 1 1,2,3 4 Notes: 1. Minimum DC voltage is -0.5 V on input/output pins. During transitions, this level may undershoot to -2.0 V for periods <20 ns. Maximum DC voltage on input/output pins is VCC +0.5 V which, during transitions, may overshoot to VCC +2.0 V for periods <20 ns. 2. Maximum DC voltage on VPP may overshoot to +14.0 V for periods <20 ns. 3. VPP Program voltage is normally 1.65 V-3.6 V. Connection to a 11.4 V-12.6 V supply can be done for a maximum of 1000 cycles on the main blocks and 2500 cycles on the parameter blocks during program/ erase. VPP may be connected to 12 V for a total of 80 hours maximum. 4. Output shorted for no more than one second. No more than one output shorted at a time. 5.2 Table 6: Operating Conditions Temperature and Voltage Operating Conditions Symbol Parameter TA Operating Temperature VCC1 VCC Supply Voltage VCC2 VCCQ1 VCCQ2 Notes Min Max Units -40 +85 C 1, 2 2.7 3.6 Volts 1, 2 3.0 3.6 1 I/O Supply Voltage VCCQ3 VPP1 March 2008 290645-24 Supply Voltage 1 2.7 3.6 1.65 2.5 1.8 2.5 1.65 3.6 Volts Volts Datasheet 21 C3 Discrete Table 6: Symbol Temperature and Voltage Operating Conditions Parameter VPP2 Cycling Block Erase Cycling Notes Min Max 1, 3 11.4 12.6 3 100,000 Units Volts Cycles Notes: 1. VCC and VCCQ must share the same supply when they are in the VCC1 range. 2. VCCMax = 3.3 V for 0.25m 32-Mbit devices. 3. Applying VPP = 11.4 V-12.6 V during a program/erase can only be done for a maximum of 1000 cycles on the main blocks and 2500 cycles on the parameter blocks. VPP may be connected to 12 V for a total of 80 hours maximum. Datasheet 22 March 2008 290645-24 C3 Discrete 6.0 Electrical Specifications 6.1 Current Characteristics Table 7: Sym DC Current Characteristics (Sheet 1 of 2) Parameter VCC 2.7 V-3.6 V 2.7 V-2.85 V 2.7 V-3.3 V VCCQ 2.7 V-3.6 V 1.65 V-2.5 V 1.8 V-2.5 V Note Typ Max Typ Max Typ Unit Test Conditions Max ILI Input Load Current 1,2 1 1 1 A VCC = VCCMax VCCQ = VCCQMax VIN = VCCQ or GND ILO Output Leakage Current 1,2 10 10 10 A VCC = VCCMax VCCQ = VCCQMax VIN = VCCQ or GND ICCS ICCD ICCR IPPD ICCW ICCE ICCES/ ICCWS IPPR VCC Standby Current for 0.13 and 0.18 Micron Product 1 7 15 20 50 150 250 A VCC Standby Current for 0.25 Micron Product 1 10 25 20 50 150 250 A VCC Power-Down Current for 0.13 and 0.18 Micron Product 1,2 7 15 7 20 7 20 A VCC Power-Down Current for 0.25 Product 1,2 7 25 7 25 7 25 A VCC Read Current for 0.13 and 0.18 Micron Product 1,2,3 9 18 8 15 9 15 mA VCC Read Current for 0.25 Micron Product 1,2,3 10 18 8 15 9 15 mA 1 0.2 5 0.2 5 0.2 5 A RP# = GND 0.2 V VPP VCC 18 55 18 55 18 55 mA VPP =VPP1, Program in Progress 8 22 10 30 10 30 mA VPP = VPP2 (12v) Program in Progress 16 45 21 45 21 45 mA VPP = VPP1, Erase in Progress 8 15 16 45 16 45 mA VPP = VPP2 (12v) , Erase in Progress 7 15 50 200 50 200 A VPP Deep Power-Down Current VCC Program Current VCC Erase Current VCC Erase Suspend Current for 0.13 and 0.18 Micron Product VCC Erase Suspend Current for 0.25 Micron Product VPP Read Current March 2008 290645-24 1,4 1,4 VCC = VCCMax VCCQ = VCCQMax VIN = VCCQ or GND RP# = GND 0.2 V VCC = VCCMax VCCQ = VCCQMax OE# = VIH, CE# =VIL f = 5 MHz, IOUT=0 mA Inputs = VIL or VIH CE# = VIH, Erase Suspend in Progress 1,4,5 1,4 VCC = VCCMax CE# = RP# = VCCQ or during Program/ Erase Suspend WP# = VCCQ or GND 10 25 50 200 50 200 A 2 15 2 15 2 15 A VPP VCC 50 200 50 200 50 200 A VPP > VCC Datasheet 23 C3 Discrete Table 7: Sym IPPW IPPE IPPES/ IPPWS DC Current Characteristics (Sheet 2 of 2) Parameter VPP Program Current VPP Erase Current VCC 2.7 V-3.6 V 2.7 V-2.85 V 2.7 V-3.3 V VCCQ 2.7 V-3.6 V 1.65 V-2.5 V 1.8 V-2.5 V Note Typ Max Typ Max Typ Max 0.05 0.1 0.05 0.1 0.05 0.1 mA VPP =VPP1, Program in Progress 8 22 8 22 8 22 mA VPP = VPP2 (12v) Program in Progress 0.05 0.1 0.05 0.1 0.05 0.1 mA VPP = VPP1, Erase in Progress 8 22 16 45 16 45 mA VPP = VPP2 (12v) , Erase in Progress 0.2 5 0.2 5 0.2 5 A VPP = VPP1, Program or Erase Suspend in Progress 50 200 50 200 50 200 A VPP = VPP2 (12v) , Program or Erase Suspend in Progress Unit 1,4 1,4 VCC Erase Suspend Current 1,4 Test Conditions Notes: 1. All currents are in RMS unless otherwise noted. Typical values at nominal VCC, TA = +25 C. 2. The test conditions VCCMax, VCCQMax, VCCMin, and VCCQMin refer to the maximum or minimum VCC or VCCQ voltage listed at the top of each column. VCCMax = 3.3 V for 0.25m 32-Mbit devices. 3. Automatic Power Savings (APS) reduces ICCR to approximately standby levels in static operation (CMOS inputs). 4. Sampled, not 100% tested. 5. ICCES or ICCWS is specified with device de-selected. If device is read while in erase suspend, current draw is sum of ICCES and ICCR. If the device is read while in program suspend, current draw is the sum of ICCWS and ICCR. 6.2 DC Voltage Characteristics Table 8: Sym DC Voltage Characteristics (Sheet 1 of 2) Parameter VCC 2.7 V-3.6 V 2.7 V-2.85 V 2.7 V-3.3 V VCCQ 2.7 V-3.6 V 1.65 V-2.5 V 1.8 V-2.5 V Note Min Max Min Max Min Max Unit Test Conditions VIL Input Low Voltage -0.4 VCC * 0.22 V -0.4 0.4 -0.4 0.4 V VIH Input High Voltage 2.0 VCCQ +0.3V VCCQ - 0.4V VCCQ +0.3V VCCQ - 0.4V VCCQ +0.3V V VOL Output Low Voltage -0.1 0.1 -0.1 0.1 -0.1 0.1 V VCC = VCCMin VCCQ = VCCQMin IOL = 100 A VOH Output High Voltage VCCQ -0.1V V VCC = VCCMin VCCQ = VCCQMin IOH = -100 A VPPLK VPP LockOut Voltage 1.0 V Complete Write Protection VPP1 VPP2 Datasheet 24 VPP during Program / Erase Operations 1 VCCQ - 0.1V 1.0 VCCQ - 0.1V 1.0 1 1.65 3.6 1.65 3.6 1.65 3.6 V 1,2 11.4 12.6 11.4 12.6 11.4 12.6 V March 2008 290645-24 C3 Discrete Table 8: Sym DC Voltage Characteristics (Sheet 2 of 2) Parameter VCC 2.7 V-3.6 V 2.7 V-2.85 V 2.7 V-3.3 V VCCQ 2.7 V-3.6 V 1.65 V-2.5 V 1.8 V-2.5 V Note Min Max Min Max Min Max Unit VIL Input Low Voltage -0.4 VCC * 0.22 V -0.4 0.4 -0.4 0.4 V VIH Input High Voltage 2.0 VCCQ +0.3V VCCQ - 0.4V VCCQ +0.3V VCCQ - 0.4V VCCQ +0.3V V VOL Output Low Voltage -0.1 0.1 -0.1 0.1 -0.1 0.1 V VLKO VCC Prog/ Erase Lock Voltage 1.5 1.5 1.5 V VLKO2 VCCQ Prog/ Erase Lock Voltage 1.2 1.2 1.2 V Test Conditions VCC = VCCMin VCCQ = VCCQMin IOL = 100 A Notes: 1. Erase and Program are inhibited when VPP < VPPLK and not guaranteed outside the valid VPP ranges of VPP1 and VPP2. 2. Applying VPP = 11.4 V-12.6 V during program/erase can only be done for a maximum of 1000 cycles on the main blocks and 2500 cycles on the parameter blocks. VPP may be connected to 12 V for a total of 80 hours maximum. March 2008 290645-24 Datasheet 25 C3 Discrete 7.0 AC Characteristics 7.1 AC Read Characteristics Table 9: Read Operations--8-Mbit Density Density # Sym 8 Mbit Product 70 ns VCC 2.7 V - 3.6 V 3.0 V - 3.6 V 2.7 V - 3.6 V 3.0 V - 3.6 V 2.7 V - 3.6 V Note Min (ns) Min (ns) Min (ns) Min (ns) Min (ns) 70 Paramete r 90 ns Max (ns) Max (ns) Max (ns) 3,4 R2 tAVQV Address to Output Delay 3,4 70 80 90 100 110 R3 tELQV CE# to Output Delay 1,3,4 70 80 90 100 110 R4 tGLQV OE# to Output Delay 1,3,4 20 30 30 30 30 R5 tPHQV RP# to Output Delay 3,4 150 150 150 150 150 R6 tELQX CE# to Output in Low Z 2,3,4 0 0 0 0 0 R7 tGLQX OE# to Output in Low Z 2,3,4 0 0 0 0 0 R8 tEHQZ CE# to Output in High Z 2,3,4 20 20 20 20 20 R9 tGHQZ OE# to Output in High Z 2,3,4 20 20 20 20 20 tOH Output Hold from Address, CE#, or OE# Change, Whichever Occurs First 2,3,4 Notes: 1. 2. 3. 4. 0 0 0 100 Max (ns) Read Cycle Time R10 90 Max (ns) tAVAV R1 80 110 ns 0 110 0 OE# may be delayed up to tELQV-tGLQV after the falling edge of CE# without impact on tELQV. Sampled, but not 100% tested. See Figure 9, "Read Operation Waveform" on page 29. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. Datasheet 26 March 2008 290645-24 C3 Discrete Table 10: Read Operations--16-Mbit Density Densit y # Sym 16 Mbit Produ ct 70 ns 80 ns VCC 2.7 V-3.6 V 2.7 V-3.6 V Paramet er Min (ns) Max (ns) Max (ns) Min (ns) Max (ns) Min (ns) Max (ns) Min (ns ) Ma x (ns ) Min (ns ) Ma x (ns ) tAVQV 70 80 80 90 100 110 3,4 R3 tELQV CE# to Output Delay 70 80 80 90 100 110 1,3,4 R4 tGLQV OE# to Output Delay 20 20 30 30 30 30 1,3,4 R5 tPHQV RP# to Output Delay 150 150 150 150 150 150 3,4 R6 tELQX CE# to Output in Low Z 0 0 0 0 0 0 2,3,4 R7 tGLQX OE# to Output in Low Z 0 0 0 0 0 0 2,3,4 R8 tEHQZ CE# to Output in High Z 20 20 20 20 20 20 2,3,4 R9 tGHQZ OE# to Output in High Z 20 20 20 20 20 20 2,3,4 tOH Output Hold from Address, CE#, or OE# Change, Whichever Occurs First Notes: 1. 2. 3. 4. 0 0 100 Note s 2.7 V- 3.6V R2 0 90 3.0 V- 3.6V Address to Output Delay 0 80 2.7 V-3.6 V Read Cycle Time R10 80 3.0 V-3.6 V 110 ns tAVAV R1 70 Min (ns) 90 ns 0 110 0 3,4 2,3,4 OE# may be delayed up to tELQV-tGLQV after the falling edge of CE# without impact on tELQV. Sampled, but not 100% tested. See Figure 9, "Read Operation Waveform" on page 29. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. March 2008 290645-24 Datasheet 27 C3 Discrete Table 11: Read Operations--32-Mbit Density Densit y # Sym Paramet er 32 Mbit Produc t 70 ns 90 ns VCC 2.7 V-3.6 V 2.7 V-3.6 V Min (ns) R1 R2 Max (ns) 70 Min (ns) Max (ns) 90 100 ns 3.0 V-3.3 V Min (ns) Max (ns) 90 110 ns 2.7 V-3.3 V Min (ns) Max (ns) 100 3.0 V-3.3 V 2.7 V-3.3 V Min (ns ) Min (ns) Max (ns ) 100 Note s Max (ns) tAVAV Read Cycle Time tAVQV Address to Output Delay 110 3,4 70 90 90 100 100 110 3,4 R3 tELQV CE# to Output Delay 70 90 90 100 100 110 1,3,4 R4 tGLQV OE# to Output Delay 20 20 30 30 30 30 1,3,4 R5 tPHQV RP# to Output Delay 150 150 150 150 150 150 3,4 R6 tELQX CE# to Output in Low Z 0 0 0 0 0 0 2,3,4 R7 tGLQX OE# to Output in Low Z 0 0 0 0 0 0 2,3,4 R8 tEHQZ CE# to Output in High Z 20 20 20 20 20 20 2,3,4 R9 tGHQZ OE# to Output in High Z 20 20 20 20 20 20 2,3,4 tOH Output Hold from Address, CE#, or OE# Change, Whichever Occurs First R10 Notes: 1. 2. 3. 4. 0 0 0 0 0 0 2,3,4 OE# may be delayed up to tELQV-tGLQV after the falling edge of CE# without impact on tELQV. Sampled, but not 100% tested. See Figure 9, "Read Operation Waveform" on page 29. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. Datasheet 28 March 2008 290645-24 C3 Discrete Table 12: Read Operations -- 64-Mbit Density Density # Sym 64 Mbit Product 70 ns 80 ns VCC 2.7 V-3.6 V 2.7 V-3.6 V Note Min Min 70 Parameter Unit Max Max R1 tAVAV Read Cycle Time 3,4 R2 tAVQV Address to Output Delay 3,4 R3 tELQV CE# to Output Delay 1,3,4 70 80 ns R4 tGLQV OE# to Output Delay 1,3,4 20 20 ns R5 tPHQV RP# to Output Delay R6 tELQX CE# to Output in Low Z 2,3,4 0 R7 tGLQX OE# to Output in Low Z 2,3,4 0 R8 tEHQZ CE# to Output in High Z 2,3,4 20 20 ns R9 tGHQZ OE# to Output in High Z 2,3,4 20 20 ns Output Hold from Address, CE#, or OE# Change, Whichever Occurs First 2,3,4 R10 Notes: 1. 2. 3. 4. tOH 80 ns 70 3,4 80 150 0 150 0 ns ns ns 0 ns 0 ns OE# may be delayed up to tELQV-tGLQV after the falling edge of CE# without impact on tELQV. Sampled, but not 100% tested. See Figure 9, "Read Operation Waveform" on page 29. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. Figure 9: Read Operation Waveform R1 R2 Address [A] R3 R8 CE# [E] R4 R9 OE# [G] WE# [W] R7 R6 R10 Data [D/Q] R5 RST# [P] March 2008 290645-24 Datasheet 29 C3 Discrete 7.2 Table 13: AC Write Characteristics Write Operations--8-Mbit Density Density 8 Mbit Product # Sym Parameter 70ns 3.0 V - 3.6 V VCC 2.7 V - 3.6 V 90 ns 110 ns 80 70 100 90 110 Note Min (ns) Min (ns) Min (ns) Min (ns) Min (ns) W1 tPHWL / tPHEL RP# High Recovery to WE# (CE#) Going Low 4,5 150 150 150 150 150 W2 tELWL / tWLEL CE# (WE#) Setup to WE# (CE#) Going Low 4,5 0 0 0 0 0 W3 tWLWH / tELEH WE# (CE#) Pulse Width 4,5 45 50 60 70 70 W4 tDVWH / tDVEH Data Setup to WE# (CE#) Going High 2,4,5 40 50 50 60 60 W5 tAVWH / tAVEH Address Setup to WE# (CE#) Going High 2,4,5 50 50 60 70 70 W6 tWHEH / tEHWH CE# (WE#) Hold Time from WE# (CE#) High 4,5 0 0 0 0 0 W7 tWHDX / tEHDX Data Hold Time from WE# (CE#) High 2,4,5 0 0 0 0 0 W8 tWHAX / tEHAX Address Hold Time from WE# (CE#) High 2,4,5 0 0 0 0 0 W9 tWHWL / tEHEL WE# (CE#) Pulse Width High 2,4,5 25 30 30 30 30 W10 tVPWH / tVPEH VPP Setup to WE# (CE#) Going High 3,4,5 200 200 200 200 200 W11 tQVVL VPP Hold from Valid SRD 3,4 0 0 0 0 0 W12 tBHWH / tBHEH WP# Setup to WE# (CE#) Going High 3,4 0 0 0 0 0 W13 tQVBL WP# Hold from Valid SRD 3,4 0 0 0 0 0 W14 tWHGL WE# High to OE# Going Low 3,4 30 30 30 30 30 Notes: 1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high (whichever goes high first). Hence, tWP = tWLWH = tELEH = tWLEH = tELWH. Similarly, write pulse width high (tWPH) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low (whichever goes low last). Hence, tWPH = tWHWL = tEHEL = tWHEL = tEHWL. 2. Refer to Table 23, "Command Bus Operations" on page 45 for valid AIN or DIN. 3. Sampled, but not 100% tested. 4. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. 5. See Figure 10, "Write Operations Waveform" on page 33. Datasheet 30 March 2008 290645-24 C3 Discrete Table 14: Write Operations--16-Mbit Density Density 16 Mbit Product # Sym Parameter 70 ns 80 ns 3.0 V - 3.6 V VCC 2.7 V - 3.6 V 90 ns 80 110 ns 100 90 Unit 70 80 110 Not e Min Min Min Min Min Min W1 tPHWL / tPHEL RP# High Recovery to WE# (CE#) Going Low 4,5 150 150 150 150 150 150 ns W2 tELWL / tWLEL CE# (WE#) Setup to WE# (CE#) Going Low 4,5 0 0 0 0 0 0 ns W3 tWLWH / tELEH WE# (CE#) Pulse Width 1,4, 5 45 50 50 60 70 70 ns W4 tDVWH / tDVEH Data Setup to WE# (CE#) Going High 2,4, 5 40 40 50 50 60 60 ns W5 tAVWH / tAVEH Address Setup to WE# (CE#) Going High 2,4, 5 50 50 50 60 70 70 ns W6 tWHEH / tEHWH CE# (WE#) Hold Time from WE# (CE#) High 4,5 0 0 0 0 0 0 ns W7 tWHDX / tEHDX Data Hold Time from WE# (CE#) High 2,4, 5 0 0 0 0 0 0 ns W8 tWHAX / tEHAX Address Hold Time from WE# (CE#) High 2,4, 5 0 0 0 0 0 0 ns W9 tWHWL / tEHEL WE# (CE#) Pulse Width High 1,4, 5 25 30 30 30 30 30 ns W10 tVPWH / tVPEH VPP Setup to WE# (CE#) Going High 3,4, 5 200 200 200 200 200 200 ns W11 tQVVL VPP Hold from Valid SRD 3,4 0 0 0 0 0 0 ns W12 tBHWH / tBHEH WP# Setup to WE# (CE#) Going High 3,4 0 0 0 0 0 0 ns W13 tQVBL WP# Hold from Valid SRD 3,4 0 0 0 0 0 0 ns W14 tWHGL WE# High to OE# Going Low 3,4 30 30 30 30 30 30 ns Notes: 1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high (whichever goes high first). Hence, tWP = tWLWH = tELEH = tWLEH = tELWH. Similarly, write pulse width high (tWPH) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low (whichever goes low last). Hence, tWPH = tWHWL = tEHEL = tWHEL = tEHWL. 2. Refer to Table 23, "Command Bus Operations" on page 45 for valid AIN or DIN. 3. Sampled, but not 100% tested. 4. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. 5. See Figure 10, "Write Operations Waveform" on page 33. March 2008 290645-24 Datasheet 31 C3 Discrete Table 15: Write Operations--32-Mbit Density Density 32 Mbit Product # Sym 70 ns 90 ns 3.0 V - 3.6 V6 Parameter VCC 2.7 V - 3.6 V 100 ns 110 ns 90 100 100 Unit 70 90 110 Note Min Min Min Min Min Min W1 tPHWL / tPHEL RP# High Recovery to WE# (CE#) Going Low 4,5 150 150 150 150 150 150 ns W2 tELWL / tWLEL CE# (WE#) Setup to WE# (CE#) Going Low 4,5 0 0 0 0 0 0 ns W3 tWLWH / tELEH WE# (CE#) Pulse Width 1,4,5 45 60 60 70 70 70 ns W4 tDVWH / tDVEH Data Setup to WE# (CE#) Going High 2,4,5 40 40 50 60 60 60 ns W5 tAVWH / tAVEH Address Setup to WE# (CE#) Going High 2,4,5 50 60 60 70 70 70 ns W6 tWHEH / tEHWH CE# (WE#) Hold Time from WE# (CE#) High 4,5 0 0 0 0 0 0 ns W7 tWHDX / tEHDX Data Hold Time from WE# (CE#) High 2,4,5 0 0 0 0 0 0 ns W8 tWHAX / tEHAX Address Hold Time from WE# (CE#) High 2,4,5 0 0 0 0 0 0 ns W9 tWHWL / tEHEL WE# (CE#) Pulse Width High 1,4,5 25 30 30 30 30 30 ns W10 tVPWH / tVPEH VPP Setup to WE# (CE#) Going High 3,4,5 200 200 200 200 200 200 ns W11 tQVVL VPP Hold from Valid SRD 3,4 0 0 0 0 0 0 ns W12 tBHWH / tBHEH WP# Setup to WE# (CE#) Going High 3,4 0 0 0 0 0 0 ns W13 tQVBL WP# Hold from Valid SRD 3,4 0 0 0 0 0 0 ns W14 tWHGL WE# High to OE# Going Low 3,4 30 30 30 30 30 30 ns Notes: 1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high (whichever goes high first). Hence, tWP = tWLWH = tELEH = tWLEH = tELWH. Similarly, write pulse width high (tWPH) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low (whichever goes low last). Hence, tWPH = tWHWL = tEHEL = tWHEL = tEHWL. 2. Refer to Table 23, "Command Bus Operations" on page 45 for valid AIN or DIN. 3. Sampled, but not 100% tested. 4. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. 5. See Figure 10, "Write Operations Waveform" on page 33. 6. VCCMax = 3.3 V for 32-Mbit 0.25 Micron product. Datasheet 32 March 2008 290645-24 C3 Discrete Table 16: Write Operations--64-Mbit Density # Symbol Parameter 64 Mbit Product 80 ns 2.7 V - 3.6 V VCC W1 Density Unit Note Min 4,5 150 ns tPHWL / tPHEL RP# High Recovery to WE# (CE#) Going Low W2 tELWL / tWLEL CE# (WE#) Setup to WE# (CE#) Going Low 4,5 0 ns W3 tWLWH / tELEH WE# (CE#) Pulse Width 1,4,5 60 ns W4 tDVWH / tDVEH Data Setup to WE# (CE#) Going High 2,4,5 40 ns W5 tAVWH / tAVEH Address Setup to WE# (CE#) Going High 2,4,5 60 ns W6 tWHEH / tEHWH CE# (WE#) Hold Time from WE# (CE#) High 4,5 0 ns W7 tWHDX / tEHDX Data Hold Time from WE# (CE#) High 2,4,5 0 ns W8 tWHAX / tEHAX Address Hold Time from WE# (CE#) High 2,4,5 0 ns W9 tWHWL / tEHEL WE# (CE#) Pulse Width High 1,4,5 30 ns VPP Setup to WE# (CE#) Going High W10 tVPWH / tVPEH W11 tQVVL 3,4,5 200 ns VPP Hold from Valid SRD 3,4 0 ns W12 tBHWH / tBHEH WP# Setup to WE# (CE#) Going High 3,4 0 ns W13 tQVBL WP# Hold from Valid SRD 3,4 0 ns W14 tWHGL WE# High to OE# Going Low 3,4 30 ns Notes: 1. Write pulse width (tWP) is defined from CE# or WE# going low (whichever goes low last) to CE# or WE# going high (whichever goes high first). Hence, tWP = tWLWH = tELEH = tWLEH = tELWH. Similarly, write pulse width high (tWPH) is defined from CE# or WE# going high (whichever goes high first) to CE# or WE# going low (whichever goes low last). Hence, tWPH = tWHWL = tEHEL = tWHEL = tEHWL. 2. Refer to Table 23, "Command Bus Operations" on page 45 for valid AIN or DIN. 3. Sampled, but not 100% tested. 4. See Figure 11, "AC Input/Output Reference Waveform" on page 34 for timing measurements and maximum allowable input slew rate. 5. See Figure 10, "Write Operations Waveform" on page 33. Figure 10: Write Operations Waveform W5 W8 Address [A] W6 CE# [E] W3 W2 W9 WE# [W] OE# [G] W4 W7 Data [D/Q] W1 RP# [P] W10 Vpp [V] March 2008 290645-24 Datasheet 33 C3 Discrete 7.3 Erase and Program Timings Table 17: Erase and Program Timings Symbol 1.65 V-3.6 V VPP Parameter 11.4 V-12.6 V Unit Note Typ Max Typ Max tBWPB 4-KW Parameter Block Word Program Time 1, 2, 3 0.10 0.30 0.03 0.12 s tBWMB 32-KW Main Block Word Program Time 1, 2, 3 0.8 2.4 0.24 1 s Word Program Time for 0.13 and 0.18 Micron Product 1, 2, 3 12 200 8 185 s Word Program Time for 0.25 Micron Product 1, 2, 3 22 200 8 185 s tWHQV2 / tEHQV2 4-KW Parameter Block Erase Time 1, 2, 3 0.5 4 0.4 4 s tWHQV3 / tEHQV3 32-KW Main Block Erase Time 1, 2, 3 1 5 0.6 5 s tWHRH1 / tEHRH1 Program Suspend Latency 1,3 5 10 5 10 s tWHRH2 / tEHRH2 Erase Suspend Latency 1,3 5 20 5 20 s tWHQV1 / tEHQV1 Notes: 1. Typical values measured at TA= +25 C and nominal voltages. 2. Excludes external system-level overhead. 3. Sampled, but not 100% tested. 7.4 AC I/O Test Conditions Figure 11: AC Input/Output Reference Waveform VCCQ Input VCCQ/2 Test Points VCCQ/2 Output 0V Note: Input timing begins, and output timing ends, at VCCQ/2. Input rise and fall times (10% to 90%) < 5 ns. Worst-case speed conditions are when VCC = VCCMin. Datasheet 34 March 2008 290645-24 C3 Discrete Figure 12: Transient Equivalent Testing Load Circuit VCCQ R1 Device Under Test Out CL Note: R2 See Table 17 for component values. Table 18: Test Configuration Component Values for Worst-Case Speed Conditions Test Configuration VCCQMin Standard Test Note: CL (pF) R1 (k) R2 (k) 50 25 25 CL includes jig capacitance. 7.5 Device Capacitance TA = 25 C, f = 1 MHz Table 19: Device Capacitance Parameter Typ Input Capacitance Output Capacitance Symbol CIN COUT Max Unit Condition 6 8 pF VIN = 0.0 V 8 12 pF VOUT = 0.0 V Sampled, not 100% tested. March 2008 290645-24 Datasheet 35 C3 Discrete 8.0 Power and Reset Specifications NumonyxTM flash devices have a tiered approach to power savings that can significantly reduce overall system power consumption. The Automatic Power Savings (APS) feature reduces power consumption when the device is selected but idle. If CE# is deasserted, the flash enters its standby mode, where current consumption is even lower. If RP# is deasserted, the flash enter deep power-down mode for ultra-low current consumption. The combination of these features can minimize memory power consumption, and therefore, overall system power consumption. 8.1 Active Power (Program/Erase/Read) With CE# at a logic-low level and RP# at a logic-high level, the device is in the active mode. Refer to the DC Characteristic tables for ICC current values. Active power is the largest contributor to overall system power consumption. Minimizing the active current could have a profound effect on system power consumption, especially for batteryoperated devices. 8.2 Automatic Power Savings (APS) Automatic Power Savings provides low-power operation during read mode. After data is read from the memory array and the address lines are idle, APS circuitry places the device in a mode where typical current is comparable to ICCS. The flash stays in this static state with outputs valid until a new location is read. 8.3 Standby Power When CE# is at a logic-high level (VIH), the flash memory is in standby mode, which disables much of the device's circuitry and substantially reduces power consumption. Outputs are placed in a high-impedance state independent of the status of the OE# signal. If CE# transitions to a logic-high level during Erase or Program operations, the device will continue to perform the operation and consume corresponding active power until the operation is completed. System engineers should analyze the breakdown of standby time versus active time and quantify the respective power consumption in each mode for their specific application. This approach will provide a more accurate measure of application-specific power and energy requirements. 8.4 Deep Power-Down Mode The deep power-down mode is activated when RP# = VIL. During read modes, RP# going low de-selects the memory and places the outputs in a high-impedance state. Recovery from deep power-down requires a minimum time of tPHQV for read operations, and tPHWL/tPHEL for write operations. During program or erase modes, RP# transitioning low aborts the in-progress operation. The memory contents of the address being programmed or the block being erased are no longer valid as the data integrity has been compromised by the abort. During deep power-down, all internal circuits are switched to a low-power savings mode (RP# transitioning to VIL or turning off power to the device clears the Status Register). Datasheet 36 March 2008 290645-24 C3 Discrete 8.5 Power and Reset Considerations 8.5.1 Power-Up/Down Characteristics To prevent any condition that may result in a spurious write or erase operation, Numonyx recommends to power-up VCC and VCCQ together. Conversely, VCC and VCCQ must power-down together. Numonyx also recommends that you power-up VPP with or after VCC has reached VCCmin. Conversely, VPP must powerdown with or slightly before VCC. If VCCQ and/or VPP are not connected to the VCC supply, then VCC must attain VCCmin before applying VCCQ and VPP. Device inputs must not be driven before supply voltage reaches VCCmin. Power supply transitions must only occur when RP# is low. 8.5.2 RP# Connected to System Reset The use of RP# during system reset is important with automated program/erase devices since the system reads from the flash memory when it comes out of reset. If a CPU reset occurs without a flash memory reset, proper CPU initialization will not occur because the flash memory may be providing status information instead of array data. Numonyx recommends connecting RP# to the system CPU RESET# signal to allow proper CPU/flash initialization following system reset. System designers must guard against spurious writes when VCC voltages are above VLKO. Because both WE# and CE# must be low for a command write, driving either signal to VIH will inhibit writes to the device. The CUI architecture provides additional protection since alteration of memory contents can only occur after successful completion of the two-step command sequences. The device is also disabled until RP# is brought to VIH, regardless of the state of its control inputs. By holding the device in reset during power-up/down, invalid bus conditions during power-up can be masked, providing yet another level of memory protection. 8.5.3 VCC, VPP and RP# Transitions The CUI latches commands as issued by system software and is not altered by VPP or CE# transitions or WSM actions. Its default state upon power-up, after exit from reset mode or after VCC transitions above VLKO (Lockout voltage), is read-array mode. After any program or Block-Erase operation is complete (even after VPP transitions down to VPPLK), the CUI must be reset to read-array mode by the Read Array command if access to the flash-memory array is desired. 8.5.4 Reset Specifications Table 20: Reset Specifications Symbol Parameter VCC 2.7 V - 3.6 V Min tPLPH March 2008 290645-24 RP# Low to Reset during Read (If RP# is tied to VCC, this specification is not applicable) 100 Unit Notes ns 1, 2 Max Datasheet 37 C3 Discrete Table 20: Reset Specifications Symbol VCC 2.7 V - 3.6 V Parameter Min Unit Notes Max tPLRH1 RP# Low to Reset during Block Erase 22 s 3 tPLRH2 RP# Low to Reset during Program 12 s 3 Notes: 1. If tPLPH is < 100 ns the device may still reset but this is not guaranteed. 2. If RP# is asserted while a Block Erase or Word Program operation is not executing, the reset will complete within 100 ns. 3. Sampled, but not 100% tested. Figure 13: Reset Operations Waveforms R P # (P ) V IH V IL t PLPH (A ) R e s e t d u rin g R e a d M o d e tPHQV tPHW L tPHEL A b o rt C o m p le te t PLR H R P # (P ) V IH t PHQV t PHW L t PHEL V IL t PLP H (B ) R e s e t d u rin g P ro g ra m o r B lo c k E ra s e , t P L P H < t P L R H A b o rt D e e p C o m p le te P o w e rD ow n R P # (P ) V IH t PLR H V IL t PHQV t PHW L t PHEL t PLPH (C ) R e s e t P ro g ra m o r B lo c k E ra s e , t P L P H > t P L R H 8.6 Power Supply Decoupling Flash memory power-switching characteristics require careful device decoupling. System designers should consider the following three supply current issues: * Standby current levels (ICCS) * Read current levels (ICCR) * Transient peaks produced by falling and rising edges of CE#. Transient current magnitudes depend on the device outputs' capacitive and inductive loading. Two-line control and proper decoupling capacitor selection will suppress these transient voltage peaks. Each flash device should have a 0.1 F ceramic capacitor connected between each VCC and GND, and between its VPP and VSS. These highfrequency, inherently low-inductance capacitors should be placed as close as possible to the package leads. Datasheet 38 March 2008 290645-24 C3 Discrete 9.0 Device Operations The C3 Discrete device uses a CUI and automated algorithms to simplify Program and Erase operations. The CUI allows for 100% CMOS-level control inputs and fixed power supplies during erasure and programming. The internal WSM completely automates Program and Erase operations while the CUI signals the start of an operation and the Status Register reports device status. The CUI handles the WE# interface to the data and address latches as well as system status requests during WSM operation. 9.1 Bus Operations The C3 Discrete device performs read, program, and erase operations in-system through the local CPU or microcontroller. Four control pins (CE#, OE#, WE#, and RP#) manage the data flow in and out of the flash device. Table 21 on page 39 summarizes these bus operations. Table 21: Bus Operations Mode RP# CE# OE# WE# DQ[15:0] Read VIH Write VIH VIL VIL VIH DOUT VIL VIH VIL DIN Output Disable VIH VIL VIH VIH High-Z Standby VIH VIH X X High-Z VIL X X X High-Z Reset Note: X = Don't Care (VIL or VIH) 9.1.1 Read When performing a read cycle, CE# and OE# must be asserted; WE# and RP# must be deasserted. CE# is the device selection control; when active low, it enables the flash memory device. OE# is the data output control; when low, data is output on DQ[15:0]. See Figure 9, "Read Operation Waveform" on page 29. 9.1.2 Write A write cycle occurs when both CE# and WE# are low; RP# and OE# are high. Commands are issued to the Command User Interface (CUI). The CUI does not occupy an addressable memory location. Address and data are latched on the rising edge of the WE# or CE# pulse, whichever occurs first. See Figure 10, "Write Operations Waveform" on page 33. 9.1.3 Output Disable With OE# at a logic-high level (VIH), the device outputs are disabled. DQ[15:0] are placed in a high-impedance state. 9.1.4 Standby Deselecting the device by bringing CE# to a logic-high level (VIH) places the device in standby mode, which substantially reduces device power consumption without any latency for subsequent read accesses. In standby, outputs are placed in a high- March 2008 290645-24 Datasheet 39 C3 Discrete impedance state independent of OE#. If deselected during a Program or Erase operation, the device continues to consume active power until the Program or Erase operation is complete. 9.1.5 Reset From read mode, RP# at VIL for time tPLPH deselects the memory, places output drivers in a high-impedance state, and turns off all internal circuits. After return from reset, a time tPHQV is required until the initial read-access outputs are valid. A delay (tPHWL or tPHEL) is required after return from reset before a write cycle can be initiated. After this wake-up interval, normal operation is restored. The CUI resets to read-array mode, the Status Register is set to 0x80, and all blocks are locked. See Figure 13, "Reset Operations Waveforms" on page 38. If RP# is taken low for time tPLPH during a Program or Erase operation, the operation will be aborted; the memory contents at the aborted location (for a program) or block (for an erase) are no longer valid, since the data may be partially erased or written. The abort process goes through the following sequence: 1. When RP# goes low, the device shuts down the operation in progress, a process which takes time tPLRH to complete. 2. After time tPLRH, the part will either reset to read-array mode (if RP# is asserted during tPLRH) or enter reset mode (if RP# is deasserted after tPLRH). See Figure 13, "Reset Operations Waveforms" on page 38. In both cases, after returning from an aborted operation, the relevant time tPHQV or tPHWL/tPHEL must be observed before a Read or Write operation is initiated, as discussed in the previous paragraph. However, in this case, these delays are referenced to the end of tPLRH rather than when RP# goes high. As with any automated device, it is important to assert RP# during a system reset. When the system comes out of reset, the processor reads from the flash memory. Automated flash memories provide status information when read during Program or Block-Erase operations. If a CPU reset occurs with no flash memory reset, proper CPU initialization may not occur because the flash memory may be providing status information instead of array data. NumonyxTM flash memories allow proper CPU initialization following a system reset through the use of the RP# input. In this application, RP# is controlled by the same RESET# signal that resets the system CPU. Datasheet 40 March 2008 290645-24 C3 Discrete 10.0 Modes of Operation 10.1 Read Mode The flash memory has four read modes (read array, read identifier, read status, and CFI query) and two write modes (program and erase). Three additional modes (erase suspend to program, erase suspend to read, and program suspend to read) are available only during suspended operations. Table 23, "Command Bus Operations" on page 45 and Table 24, "Command Codes and Descriptions" on page 46 summarize the commands used for these modes. Appendix A, "Write State Machine States" on page 53 is a comprehensive chart showing the state transitions. 10.1.1 Read Array When RP# transitions from VIL (reset) to VIH, the device defaults to read-array mode and will respond to the read-control inputs (CE#, address inputs, and OE#) without any additional CUI commands. When the device is in read array mode, four control signals control data output. * WE# must be logic high (VIH) * CE# must be logic low (VIL) * OE# must be logic low (VIL) * RP# must be logic high (VIH) In addition, the address of the desired location must be applied to the address pins. If the device is not in read-array mode, as would be the case after a Program or Erase operation, the Read Array command (0xFF) must be issued to the CUI before array reads can occur. 10.1.2 Read Identifier The read-identifier mode outputs three types of information: the manufacturer/device identifier, the block locking status, and the protection register. The device is switched to this mode by issuing the Read Identifier command (0x90). Once in this mode, read cycles from addresses shown in Table 22 retrieve the specified information. To return to read-array mode, issue the Read Array command (0xFF). March 2008 290645-24 Datasheet 41 C3 Discrete Table 22: Device Identification Codes Address1 Item Manufacturer ID Device ID Data Base Offset Block 0x00 Block 0x01 0x0089 0x88C0 8-Mbit Top Boot Device 0x88C1 8-Mbit Bottom Boot Device 0x88C2 16-Mbit Top Boot Device 0x88C3 16-Mbit Bottom Boot Device 0x88C4 32-Mbit Top Boot Device 0x88C5 32-Mbit Bottom Boot Device 0x88CC 64-Mbit Top Boot Device 0x88CD Block Lock Status2 Block 0x02 Description DQ0 = 0b0 64-Mbit Bottom Boot Device Block is unlocked DQ0 = 0b1 Block is locked DQ1 = 0b0 Block is not locked-down DQ1 = 0b1 Block is locked down Block Lock-Down Status2 Block 0x02 Protection Register Lock Status Block 0x80 Lock Data Protection Register Block 0x81 - 0x88 Register Data Multiple reads required to read the entire 128-bit Protection Register. Notes: 1. The address is constructed from a base address plus an offset. For example, to read the Block Lock Status for block number 38 in a bottom boot device, set the address to 0x0F8000 plus the offset (0x02), i.e. 0x0F8002. Then examine DQ0 of the data to determine if the block is locked. 2. See Section 11.2, "Reading Block-Lock Status" on page 49 for valid lock status. 10.1.3 CFI Query The CFI query mode outputs Common Flash Interface (CFI) data after issuing the Read Query Command (0x98). The CFI data structure contains information such as block size, density, command set, and electrical specifications. Once in this mode, read cycles from addresses shown in Appendix C, "Common Flash Interface," retrieve the specified information. To return to read-array mode, issue the Read Array command (0xFF). 10.1.4 Read Status Register The Status Register indicates the status of device operations and the success/failure of that operation. The Read Status Register (0x70) command causes subsequent reads to output data from the Status Register until another command is issued. To return to reading from the array, issue a Read Array (0xFF) command. The Status Register bits are output on DQ[7:0]. The upper byte, DQ[15:8], outputs 0x00 when a Read Status Register command is issued. The contents of the Status Register are latched on the falling edge of OE# or CE# (whichever occurs last) which prevents possible bus errors that might occur if Status Register contents change while being read. CE# or OE# must be toggled with each subsequent status read, or the Status Register will not indicate completion of a Program or Erase operation. Datasheet 42 March 2008 290645-24 C3 Discrete When the WSM is active, SR[7] will indicate the status of the WSM; the remaining bits in the Status Register indicate whether the WSM was successful in performing the preferred operation See Table 25, "Status Register Bit Definition" on page 47. 10.1.4.1 Clear Status Register The WSM can set Status Register bits 1 through 7 and can clear bits 2, 6, and 7, but the WSM cannot clear Status Register bits 1, 3, 4 or 5. Because bits 1, 3, 4, and 5 indicate various error conditions, these bits can be cleared only through the Clear Status Register (0x50) command. By allowing the system software to control the resetting of these bits, several operations may be performed (such as cumulatively programming several addresses or erasing multiple blocks in sequence) before reading the Status Register to determine if an error occurred during that series. Clear the Status Register before beginning another command or sequence. The Read Array command must be issued before data can be read from the memory array. Resetting the device also clears the Status Register. 10.2 Program Mode Programming is executed using a two-write cycle sequence. The Program Setup command (0x40) is issued to the CUI, followed by a second write that specifies the address and data to be programmed. The WSM will execute a sequence of internally timed events to program preferred bits of the addressed location, then verify the bits are sufficiently programmed. Programming the memory results in specific bits within an address location being changed to a "0." If users attempt to program "1"s, the memory cell contents do not change and no error occurs. The Status Register indicates programming status. While the program sequence executes, status bit 7 is "0." The Status Register can be polled by toggling either CE# or OE#. While programming, the only valid commands are Read Status Register, Program Suspend, and Program Resume. When programming is complete, the program-status bits must be checked. If the programming operation was unsuccessful, SR[4] is set to indicate a program failure. If SR[3] is set, then VPP was not within acceptable limits, and the WSM did not execute the program command. If SR[1] is set, a program operation was attempted on a locked block and the operation was aborted. The Status Register should be cleared before attempting the next operation. Any CUI instruction can follow after programming is completed; however, to prevent inadvertent Status Register reads, be sure to reset the CUI to read-array mode. 10.2.1 12-Volt Production Programming When VPP is between 1.65 V and 3.6 V, all program and erase current is drawn through the VCC pin. Note: If VPP is driven by a logic signal, VIH min = 1.65 V. That is, VPP must remain above 1.65 V to perform in-system flash modifications. When VPP is connected to a 12 V power supply, the device draws program and erase current directly from the VPP pin. This eliminates the need for an external switching transistor to control VPP. Figure 16 on page 52 shows examples of how the flash power supplies can be configured for various usage models. The 12 V VPP mode enhances programming performance during the short period of time typically found in manufacturing processes; however, it is not intended for extended use. You cna apply 12 V to VPP during Program and Erase operations for a March 2008 290645-24 Datasheet 43 C3 Discrete maximum of 1000 cycles on the main blocks and 2500 cycles on the parameter blocks. VPP may be connected to 12 V for a total of 80 hours maximum. Stressing the device beyond these limits may cause permanent damage. 10.2.2 Suspending and Resuming Program The Program Suspend command halts an in-progress program operation so that data can be read from other locations of memory. Once the programming process starts, issuing the Program Suspend command to the CUI requests that the WSM suspend the program sequence at predetermined points in the program algorithm. The device continues to output Status Register data after the Program Suspend command is issued. Polling SR[7] and SR[2] will determine when the program operation has been suspended (both will be set to "1"). The program-suspend latency is specified with tWHRH1/tEHRH1. A Read-Array command can now be issued to the CUI to read data from blocks other than that which is suspended. The only other valid commands while program is suspended are Read Status Register, Read Identifier, CFI Query, and Program Resume. After the Program Resume command is issued to the flash memory, the WSM will continue with the programming process and SR[2] and SR[7] will automatically be cleared. The device automatically outputs Status Register data when read (see Figure 18, "Program Suspend / Resume Flowchart" on page 57) after the Program Resume command is issued. VPP must remain at the same VPP level used for program while in program-suspend mode. RP# must also remain at VIH. 10.3 Erase Mode To erase a block, issue the Erase Set-up and Erase Confirm commands to the CUI, along with an address identifying the block to be erased. This address is latched internally when the Erase Confirm command is issued. Block erasure results in all bits within the block being set to "1." Only one block can be erased at a time. The WSM will execute a sequence of internally timed events to program all bits within the block to "0," erase all bits within the block to "1," then verify that all bits within the block are sufficiently erased. While the erase executes, status bit 7 is a "0." When the Status Register indicates that erasure is complete, check the erase-status bit to verify that the Erase operation was successful. If the Erase operation was unsuccessful, SR[5] of the Status Register will be set to a "1," indicating an erase failure. If VPP is not within acceptable limits after the Erase Confirm command was issued, the WSM will not execute the erase sequence; instead, SR[5] of the Status Register is set to indicate an erase error, and SR[3] is set to a "1" to identify that VPP supply voltage is not within acceptable limits. After an Erase operation, clear the Status Register (0x50) before attempting the next operation. Any CUI instruction can follow after erasure is completed; however, to prevent inadvertent status- register reads, Numonyx recommends that you place the flash in read-array mode after the erase is complete. 10.3.1 Suspending and Resuming Erase Since an Erase operation requires on the order of seconds to complete, an Erase Suspend command is provided to allow erase-sequence interruption to read data from--or program data to-- another block in memory. Once the erase sequence is started, issuing the Erase Suspend command to the CUI suspends the erase sequence at a predetermined point in the erase algorithm. The Status Register indicates if/when the Erase operation has been suspended. Erase-suspend latency is specified by tWHRH2/ tEHRH2. Datasheet 44 March 2008 290645-24 C3 Discrete A Read Array or Program command can now be issued to the CUI to read/program data from/to blocks other than that which is suspended. This nested Program command can subsequently be suspended to read yet another location. The only valid commands while Erase is suspended are Read Status Register, Read Identifier, CFI Query, Program Setup, Program Resume, Erase Resume, Lock Block, Unlock Block, and Lock-Down Block. During erase-suspend mode, the device can be placed in a pseudo-standby mode by taking CE# to VIH, which reduces active current consumption. Erase Resume continues the erase sequence when CE# = VIL. Similar to the end of a standard Erase operation, the Status Register must be read and cleared before the next instruction is issued. Table 23: Command Bus Operations First Bus Cycle Command Second Bus Cycle Notes Oper Addr Data Oper Addr Data ID Read Array 1,3 Write X 0xFF Read Identifier 1,3 Write X 0x90 Read IA CFI Query 1,3 Write X 0x98 Read QA QD Read Status Register 1,3 Write X 0x70 Read X SRD Clear Status Register 1,3 Write X 0x50 Program 2,3 Write X 0x40/0x10 Write PA PD Block Erase/Confirm 1,3 Write X 0x20 Write BA D0H Program/Erase Suspend 1,3 Write X 0xB0 Write BA 0x01 Program/Erase Resume 1,3 Write X 0xD0 Lock Block 1,3 Write X 0x60 Unlock Block 1,3 Write X 0x60 Write BA 0xD0 Lock-Down Block 1,3 Write X 0x60 Write BA 0x2F Protection Program 1,3 Write X 0xC0 Write PA PD X = "Don't Care" PA = Prog Addr SRD = Status Reg. Data PD = Prog Data BA = Block Addr IA = Identifier Addr. QA = Query Addr. ID = Identifier Data QD = Query Data Notes: 1. Following the Read Identifier or CFI Query commands, read operations output device identification data or CFI query information, respectively. See Section 10.1.2 and Section 10.1.3. 2. Either 0x40 or 0x10 command is valid, but the Numonyx standard is 0x40. 3. When writing commands, the upper data bus [DQ8-DQ15] should be either VIL or VIH, to minimize current draw. Bus operations are defined in Table 21, "Bus Operations" on page 39. March 2008 290645-24 Datasheet 45 C3 Discrete Table 24: Command Codes and Descriptions Code (HEX) Device Mode FF Command Description Read Array This command places the device in read-array mode, which outputs array data on the data pins. 40 Program Set-Up This is a two-cycle command. The first cycle prepares the CUI for a program operation. The second cycle latches addresses and data information and initiates the WSM to execute the Program algorithm. The flash outputs Status Register data when CE# or OE# is toggled. A Read Array command is required after programming to read array data. See Section 10.2, "Program Mode" on page 43. 20 Erase Set-Up This is a two-cycle command. It prepares the CUI for the Erase Confirm command. If the next command is not an Erase Confirm command, then the CUI will (a) set both SR.4 and SR.5 to "1," (b) place the device into the read-Status Register mode, and (c) wait for another command. See Section 10.3, "Erase Mode" on page 44. Erase Confirm Program/Erase Resume D0 Unlock Block If the previous command was an Erase Set-Up command, then the CUI will close the address and data latches and begin erasing the block indicated on the address pins. During program/erase, the device will respond only to the Read Status Register, Program Suspend and Erase Suspend commands, and will output Status Register data when CE# or OE# is toggled. If a Program or Erase operation was previously suspended, this command will resume that operation. If the previous command was Block Unlock Set-Up, the CUI will latch the address and unlock the block indicated on the address pins. If the block had been previously set to Lock-Down, this operation will have no effect. (See Section 11.1) B0 Program Suspend Erase Suspend Issuing this command will begin to suspend the currently executing Program/Erase operation. The Status Register will indicate when the operation has been successfully suspended by setting either the program-suspend SR[2] or erase-suspend SR[6] and the WSM status bit SR[7] to a "1" (ready). The WSM will continue to idle in the SUSPEND state, regardless of the state of all inputcontrol pins except RP#, which will immediately shut down the WSM and the remainder of the chip if RP# is driven to VIL. See Sections 3.2.5.1 and 3.2.6.1. 70 Read Status Register This command places the device into read-Status Register mode. Reading the device will output the contents of the Status Register, regardless of the address presented to the device. The device automatically enters this mode after a Program or Erase operation has been initiated. See Section 10.1.4, "Read Status Register" on page 42. 50 Clear Status Register The WSM can set the block-lock status SR[1], VPP Status SR[3], program status SR[4], and erasestatus SR[5] bits in the Status Register to "1," but it cannot clear them to "0." Issuing this command clears those bits to "0." 90 Read Identifier This command puts the device into the read-identifier mode so that reading the device will output the manufacturer/device codes or block-lock status. See Section 10.1.2, "Read Identifier" on page 41. 60 Block Lock, Block Unlock, Block Lock-Down Set-Up This command prepares the CUI for block-locking changes. If the next command is not Block Unlock, Block Lock, or Block Lock-Down, then the CUI will set both the program and erase-Status Register bits to indicate a command-sequence error. See Section 11.0, "Security Modes" on page 48. 01 Lock-Block If the previous command was Lock Set-Up, the CUI will latch the address and lock the block indicated on the address pins. (See Section 11.1) 2F Lock-Down If the previous command was a Lock-Down Set-Up command, the CUI will latch the address and lock-down the block indicated on the address pins. (See Section 11.1) 98 CFI Query This command puts the device into the CFI-Query mode so that reading the device will output Common Flash Interface information. See Section 10.1.3 and Appendix C, "Common Flash Interface". C0 Protection Program Set-Up This is a two-cycle command. The first cycle prepares the CUI for a program operation to the protection register. The second cycle latches addresses and data information and initiates the WSM to execute the Protection Program algorithm to the protection register. The flash outputs Status Register data when CE# or OE# is toggled. A Read Array command is required after programming to read array data. See Section 11.5. 10 Alt. Prog Set-Up Operates the same as Program Set-up command. (See 0x40/Program Set-Up) 00 Invalid/ Reserved Unassigned commands should not be used. Numonyx reserves the right to redefine these codes for future functions. Note: See Datasheet 46 Appendix A, "Write State Machine States" for mode transition information. March 2008 290645-24 C3 Discrete Table 25: Status Register Bit Definition WSMS ESS ES PS VPPS PSS BLS R 7 6 5 4 3 2 1 0 NOTES: SR[7] WRITE STATE MACHINE STATUS (WSMS) 1 = Ready 0 = Busy Before checking program or erase- status bits, check the Write State Machine bit first to determine Word Program or Block Erase completion. SR[6] = ERASE-SUSPEND STATUS (ESS) 1 = Erase Suspended 0 = Erase In Progress/Completed When Erase Suspend is issued, WSM halts execution and sets both WSMS and ESS bits to "1." ESS bit remains set to "1" until an Erase Resume command is issued. SR[5] = ERASE STATUS (ES) 1 = Error In Block Erase 0 = Successful Block Erase When this bit is set to "1," WSM has applied the maximum number of erase pulses to the block and is still unable to verify successful block erasure. SR[4] = PROGRAM STATUS (PS) 1 = Error in Programming 0 = Successful Programming When this bit is set to "1," WSM has attempted but failed to program a word/byte. SR[3] = VPP STATUS (VPPS) 1 = VPP Low Detect, Operation Abort 0 = VPP OK The VPP status bit does not provide continuous indication of VPP level. The WSM interrogates VPP level only after the Program or Erase command sequences have been entered and informs the system if VPP has not been switched on. The VPP is also checked before the operation is verified by the WSM. The VPP status bit is not guaranteed to report accurate feedback between VPPLK and VPP1Min. SR[2] = PROGRAM SUSPEND STATUS (PSS) 1 = Program Suspended 0 = Program in Progress/Completed When Program Suspend is issued, WSM halts execution and sets both WSMS and PSS bits to "1." PSS bit remains set to "1" until a Program Resume command is issued. SR[1] = BLOCK LOCK STATUS 1 = Prog/Erase attempted on a locked block; Operation aborted. 0 = No operation to locked blocks If a Program or Erase operation is attempted to one of the locked blocks, this bit is set by the WSM. The operation specified is aborted and the device is returned to read status mode. SR[0] = RESERVED FOR FUTURE ENHANCEMENTS (R) This bit is reserved for future use and should be masked out when polling the Status Register. Note: A Command-Sequence Error is indicated when SR[4], SR[5], and SR[7] are set. March 2008 290645-24 Datasheet 47 C3 Discrete 11.0 Security Modes 11.1 Flexible Block Locking The C3 Discrete device offers an instant, individual block-locking scheme that allows any block to be locked or unlocked with no latency, enabling instant code and data protection. This locking scheme offers two levels of protection. The first level allows software-only control of block locking (useful for data blocks that change frequently), while the second level requires hardware interaction before locking can be changed (useful for code blocks that change infrequently). The following sections will discuss the operation of the locking system. The term "state [abc]" will be used to specify locking states; for example, "state [001]," where a = value of WP#, b = bit D1 of the Block Lock Status Register, and c = bit D0 of the Block Lock Status Register. Figure 14, "Block Locking State Diagram" on page 48 displays all of the possible locking states. Figure 14: Block Locking State Diagram Power-Up/Reset Locked [X01] LockedDown4,5 [011] Hardware Locked5 [011] WP# Hardware Control Unlocked [X00] Software Locked [111] Unlocked [110] Software Block Lock (0x60/0x01) or Software Block Unlock (0x60/0xD0) Software Block Lock-Down (0x60/0x2F) WP# hardware control Notes: 11.1.1 1. [a,b,c] represents [WP#, D1, D0]. X = Don't Care. 2. D1 indicates block Lock-down status. D1 = `0', Lock-down has not been issued to this block. D1 = `1', Lock-down has been issued to this block. 3. D0 indicates block lock status. D0 = `0', block is unlocked. D0 = `1', block is locked. 4. Locked-down = Hardware + Software locked. 5. [011] states should be tracked by system software to determine difference between Hardware Locked and Locked-Down states. Locking Operation The locking status of each block can be set to Locked, Unlocked, or Lock-Down, each of which will be described in the following sections. See Figure 14, "Block Locking State Diagram" on page 48 and Figure 21, "Locking Operations Flowchart" on page 60. Datasheet 48 March 2008 290645-24 C3 Discrete The following paragraph concisely summarizes the locking functionality. 11.1.1.1 Locked State The default state of all blocks upon power-up or reset is locked (states [001] or [101]). Locked blocks are fully protected from alteration. Any Program or Erase operations attempted on a locked block will return an error on bit SR[1]. The state of a locked block can be changed to Unlocked or Lock Down using the appropriate software commands. An Unlocked block can be locked by writing the Lock command sequence, 0x60 followed by 0x01. 11.1.1.2 Unlocked State Unlocked blocks (states [000], [100], [110]) can be programmed or erased. All unlocked blocks return to the Locked state when the device is reset or powered down. The status of an unlocked block can be changed to Locked or Locked Down using the appropriate software commands. A Locked block can be unlocked by writing the Unlock command sequence, 0x60 followed by 0xD0. 11.1.1.3 Lock-Down State Blocks that are Locked-Down (state [011]) are protected from Program and Erase operations (just like Locked blocks), but their protection status cannot be changed using software commands alone. A Locked or Unlocked block can be Locked Down by writing the Lock-Down command sequence, 0x60 followed by 0x2F. Locked-Down blocks revert to the Locked state when the device is reset or powered down. The Lock-Down function depends on the WP# input pin. When WP# = 0, blocks in Lock Down [011] are protected from program, erase, and lock status changes. When WP# = 1, the Lock-Down function is disabled ([111]), and Locked-Down blocks can be individually unlocked by software command to the [110] state, where they can be erased and programmed. These blocks can then be relocked [111] and unlocked [110] as required while WP# remains high. When WP# goes low, blocks that were previously Locked Down return to the Lock-Down state [011], regardless of any changes made while WP# was high. Device reset or power-down resets all blocks, including those in Lock-Down, to Locked state. 11.2 Reading Block-Lock Status The Lock status of each block can be read in read-identifier mode of the device by issuing the read-identifier command (0x90). Subsequent reads at Block Address + 0x00002 will output the Lock status of that block. The Lock status is represented by DQ0 and DQ1: * DQ0 indicates the Block Lock/Unlock status and is set by the Lock command and cleared by the Unlock command. It is also automatically set when entering Lock Down. * DQ1 indicates Lock-Down status and is set by the Lock-Down command. It cannot be cleared by software--only by device reset or power-down. See Table 22, "Device Identification Codes" on page 42 for block-status information. 11.3 Locking Operations during Erase Suspend Changes to block-lock status can be performed during an erase-suspend by using the standard locking command sequences to Unlock, Lock, or Lock Down a block. This operation is useful in the case when another block needs to be updated while an Erase operation is in progress. March 2008 290645-24 Datasheet 49 C3 Discrete To change block locking during an Erase operation, first issue the Erase Suspend command (0xB0), and then check the Status Register until it indicates that the Erase operation has been suspended. Next, write the preferred Lock command sequence to a block and the Lock status will be changed. After completing any preferred Lock, Read, or Program operations, resume the Erase operation with the Erase Resume command (0xD0). If a block is Locked or Locked Down during a Suspended Erase of the same block, the locking status bits will be changed immediately. But when the Erase is resumed, the Erase operation will complete. Locking operations cannot be performed during a Program Suspend. Refer to Appendix A, "Write State Machine States" on page 53 for detailed information on which commands are valid during Erase Suspend. 11.4 Status Register Error Checking Using nested-locking or program-command sequences during Erase Suspend can introduce ambiguity into Status Register results. Since locking changes are performed using a two-cycle command sequence, for example, 0x60 followed by 0x01 to lock a block. Following the Block Lock, Block Unlock, or Block Lock-Down Setup command (0x60) with an invalid command will produce a Lock-Command error (SR[4] and SR[5] will be set to 1) in the Status Register. If a Lock-Command error occurs during an Erase Suspend, SR[4] and SR[5] will be set to 1 and will remain at 1 after the Erase is resumed. When Erase is complete, any possible error during the Erase cannot be detected by the Status Register because of the previous Lock-Command error. A similar situation happens if an error occurs during a Program-Operation error nested within an Erase Suspend. 11.5 128-Bit Protection Register The C3 device architecture includes a 128-bit protection register than can be used to increase the security of a system design. For example, the number contained in the protection register can be used to "match" the flash component with other system components, such as the CPU or ASIC, preventing device substitution. Application note, AP-657 Designing with the Advanced+ Boot Block Flash Memory Architecture, contains additional application information. The 128 bits of the protection register are divided into two 64-bit segments. One of the segments is programmed at the Numonyx factory with a unique 64-bit number, which is unchangeable. The other segment is left blank for customer designs to program, as preferred. Once the customer segment is programmed, it can be locked to prevent further programming. 11.5.1 Reading the Protection Register The protection register is read in the Read-Identifier mode. The device is switched to this mode by issuing the Read Identifier command (0x90). Once in this mode, read cycles from addresses shown in Figure 15, "Protection Register Mapping" retrieve the specified information. To return to Read-Array mode, issue the Read Array command (0xFF). Datasheet 50 March 2008 290645-24 C3 Discrete 11.5.2 Programming the Protection Register The protection register bits are programmed using the two-cycle Protection Program command. The 64-bit number is programmed 16 bits at a time. First, issue the Protection Program Setup command, 0xC0. The next write to the device will latch in address and data and program the specified location. The allowable addresses are listed in Table 22, "Device Identification Codes" on page 42. See Figure 22, "Protection Register Programming Flowchart" on page 61. Attempting to program to a previously locked protection register segment will result in a Status Register error (Program Error bit SR[4] and Lock Error bit SR[1] will be set to 1). Note: Do not attempt to address Protection Program commands outside the defined protection register address space; status register can be indeterminate. 11.5.3 Locking the Protection Register The user-programmable segment of the protection register is lockable by programming bit 1 of the PR-LOCK location to 0. Bit 0 of this location is programmed to 0 at the Numonyx factory to protect the unique device number. This bit is set using the Protection Program command to program 0xFFFD to the PR-LOCK location. After these bits have been programmed, no further changes can be made to the values stored in the protection register. Protection Program commands to a locked section will result in a Status Register error (Program Error bit SR[4] and Lock Error bit SR[1] will be set to 1). Protection register lockout state is not reversible. Figure 15: Protection Register Mapping 0x88 64-bit Segment (User-Programmable) 0x85 0x84 128-Bit Protection Register 0 64-bit Segment (Intel Factory-Programmed) 0x81 PR Lock Register 0 0x80 11.6 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 VPP Program and Erase Voltages The C3 device provides in-system programming and erase in the 1.65 V-3.6 V range. For fast production programming, 12 V programming can be used. 11.6.1 Program Protection In addition to the flexible block locking, the VPP programming voltage can be held low for absolute hardware write protection of all blocks in the flash device. When VPP is below or equal to VPPLK, any Program or Erase operation will result in an error, prompting the corresponding Status Register bit (SR[3]) to be set. March 2008 290645-24 Datasheet 51 C3 Discrete Figure 16: Example Power Supply Configurations System Supply System Supply 12 V Supply VPP 10 K 12 V Fast Programming Absolute Write Protection With V Prot# (Logic Signal) VPP Low-Voltage Programming PP VPPLK System Supply (Note 1) VCC VCC Absolute Write Protection via Logic Signal System Supply VCC VCC VPP VPP 12 V Supply Low Voltage and 12 V Fast Programming Note: 1. Low-Voltage Programming A resistor can be used if the VCC supply can sink adequate current based on resistor value. See AP-657 Designing with the Advanced+ Boot Block Flash Memory Architecture for details. Datasheet 52 March 2008 290645-24 C3 Discrete Appendix A Write State Machine States Table 26 and Table 27 show the Write State Machine command state transitions based on incoming commands. Table 26: Write State Machine States (Sheet 1 of 2) Command Input (and Next State) Current State SR. 7 Data When Read Read Array (FFH) Program Setup (10/ 40H) Erase Setup (20H) Read Array "1" Array Read Array Prog. Setup Ers. Setup Read Status "1" Status Read Array Prog. Setup Read Config. "1" Config Read Array Read Query "1" CFI Read Array Lock Setup "1" Status Lock Cmd. Error "1" Status Read Array Prog. Setup Ers. Setup Read Array Read Sts. Read Array Lock Oper. (Done) "1" Status Read Array Prog. Setup Ers. Setup Read Array Read Sts. Read Array Prot. Prog. Setup "1" Status Protection Register Program Prot. Prog. (Not Done) "0" Status Protection Register Program (Not Done) Prot. Prog. (Done) "1" Status Read Sts. Read Array Prog. Setup "1" Status Program (Not Done) "0" Status Prog. Susp. Status "1" Status Prog. Sus. Read Array Program Suspend Read Array Prog. (Not Done) Prog. Sus. Rd. Array Program (Not Done) Prog. Sus. Status Prog. Sus. Rd. Array Prog. Susp. Read Array "1" Array Prog. Sus. Read Array Program Suspend Read Array Prog. (Not Done) Prog. Sus. Rd. Array Program (Not Done) Prog. Sus. Status Prog. Sus. Rd. Array Prog. Susp. Read Config "1" Config Prog. Sus. Read Array Program Suspend Read Array Prog. (Not Done) Prog. Sus. Rd. Array Program (Not Done) Prog. Sus. Status Prog. Sus. Rd. Array Prog. Susp. Read Query "1" CFI Prog. Sus. Read Array Program Suspend Read Array Prog. (Not Done) Prog. Sus. Rd. Array Program (Not Done) Prog. Sus. Status Prog. Sus. Rd. Array Program (Done) "1" Status Read Array Prog. Setup Read Status Read Array Erase Setup "1" Status March 2008 290645-24 Prog/Ers Suspend (B0H) Prog/ Ers Resume (D0) Read Status (70H) Clear Status (50H) Read Array Read Sts. Read Array Ers. Setup Read Array Read Sts. Read Array Prog. Setup Ers. Setup Read Array Read Sts. Read Array Prog. Setup Ers. Setup Read Array Read Sts. Read Array Lock Command Error Read Array Erase Confirm (D0H) Prog. Setup Lock (Done) Ers. Setup Lock Cmd. Error Lock (Done) Read Array Lock Cmd. Error Program Prog. Sus. Status Program (Not Done) Ers. Setup Erase Command Error Program (Not Done) Read Array Erase (Not Done) Erase Cmd. Error Erase (Not Done) Erase Command Error Datasheet 53 C3 Discrete Table 26: Write State Machine States (Sheet 2 of 2) Read Array Prog. Setup Ers. Setup Read Array Read Status Read Array Erase Sus. Status Erase (Not Done) Erase Cmd. Error "1" Status Erase (Not Done) "0" Status Ers. Susp. Status "1" Status Erase Sus. Read Array Prog. Setup Ers. Sus. Rd. Array Erase Ers. Sus. Rd. Array Erase Erase Sus. Status Ers. Sus. Rd. Array Erase Susp. Array "1" Array Erase Sus. Read Array Prog. Setup Ers. Sus. Rd. Array Erase Ers. Sus. Rd. Array Erase Erase Sus. Status Ers. Sus. Rd. Array Ers. Susp. Read Config "1" Config Erase Sus. Read Array Prog. Setup Ers. Sus. Rd. Array Erase Ers. Sus. Rd. Array Erase Erase Sus. Status Ers. Sus. Rd. Array Ers. Susp. Read Query "1" CFI Erase Sus. Read Array Prog. Setup Ers. Sus. Rd. Array Erase Ers. Sus. Rd. Array Erase Erase Sus. Status Ers. Sus. Rd. Array Erase (Done) "1" Status Read Array Prog. Setup Ers. Setup Read Sts. Read Array Erase (Not Done) Read Array Table 27: Write State Machine States, Continued Command Input (and Next State) Lock Setup (60H) Lock Confirm (01H) Lock Down Confirm (2FH) Current State Read Config (90H) Read Query (98H) Read Array Read Config. Read Query Lock Setup Prot. Prog. Setup Read Array Read Status Read Config. Read Query Lock Setup Prot. Prog. Setup Read Array Read Config. Read Config. Read Query Lock Setup Prot. Prog. Setup Read Array Read Query Read Config. Read Query Lock Setup Prot. Prog. Setup Read Array Lock Setup Prot. Prog. Setup (C0H) Locking Command Error Lock Cmd. Error Read Config. Read Query Lock Oper. (Done) Read Config. Read Query Lock Operation (Done) Lock Setup Prot. Prog. Setup Read Array Lock Setup Prot. Prog. Setup Read Array Prot. Prog. Setup Protection Register Program Prot. Prog. (Not Done) Protection Register Program (Not Done) Prot. Prog. (Done) Read Config. Read Query Lock Setup Prot. Prog. Setup Prog. Setup Program Program (Not Done) Program (Not Done) Prog. Susp. Status Datasheet 54 Prog. Susp. Read Config. Prog. Susp. Read Query Unlock Confirm (D0H) Program Suspend Read Array Read Array Program (Not Done) March 2008 290645-24 C3 Discrete Table 27: Write State Machine States, Continued Prog. Susp. Read Array Prog. Susp. Read Config. Prog. Susp. Read Query Program Suspend Read Array Program (Not Done) Prog. Susp. Read Config. Prog. Susp. Read Config. Prog. Susp. Read Query Program Suspend Read Array Program (Not Done) Prog. Susp. Read Query. Prog. Susp. Read Config. Prog. Susp. Read Query Program Suspend Read Array Program (Not Done) Program (Done) Read Config. Read Query Erase Setup Erase Cmd. Error Lock Setup Prot. Prog. Setup Read Array Erase (Not Done) Erase Command Error Read Config. Read Query Lock Setup Erase (Not Done) Prot. Prog. Setup Read Array Erase (Not Done) Erase Susp. Status Ers. Susp. Read Config. Erase Suspend Read Query Lock Setup Erase Suspend Read Array Erase (Not Done) Erase Suspend Array Ers. Susp. Read Config. Erase Suspend Read Query Lock Setup Erase Suspend Read Array Erase (Not Done) Eras Sus. Read Config Erase Suspend Read Config. Erase Suspend Read Query Lock Setup Erase Suspend Read Array Erase (Not Done) Eras Sus. Read Query Erase Suspend Read Config. Erase Suspend Read Query Lock Setup Erase Suspend Read Array Erase (Not Done) Ers.(Done) Read Config. Read Query Lock Setup March 2008 290645-24 Prot. Prog. Setup Read Array Datasheet 55 C3 Discrete Appendix B Flow Charts Figure 17: Word Program Flowchart WORD PROGRAM PROCEDURE Bus Operation Command Start Write Write 0x40, Word Address (Setup) Write Data, Word Address Program Data = 0x40 Setup Addr = Location to program Write Data Data = Data to program Addr = Location to program Read None Status register data: Toggle CE# or OE# to update Status Register Idle None Check SR[7] 1 = WSM Ready 0 = WSM Busy (Confirm) Program Suspend Loop Read Status Register No SR[7] = Comments 0 Suspend? Yes Repeat for subsequent Word Program operations. Full Status Register check can be done after each program, or after a sequence of program operations. 1 Full Status Check (if desired) Write 0xFF after the last operation to set to the Read Array state. Program Complete FULL STATUS CHECK PROCEDURE Read Status Register SR[3] = Bus Command Operation 1 SR[4] = Idle None Check SR[3]: 1 = VP P Error Idle None Check SR[4]: 1 = Data Program Error Idle None Check SR[1]: 1 = Block locked; operation aborted VP P Range Error 0 1 Program Error 1 Device Protect Error Comments 0 SR[1] = 0 Program Successful Datasheet 56 SR[3] MUST be cleared before the Write State Machine will allow further program attempts. If an error is detected, clear the Status Register before continuing operations - only the Clear Staus Register command clears the Status Register error bits. March 2008 290645-24 C3 Discrete Figure 18: Program Suspend / Resume Flowchart PROGRAM SUSPEND / RESUME PROCEDURE Bus Command Operation Start Write 0xB0 Any Address Write (Program Suspend) Write Write 0x70 Any Address Program Data = 0xB0 Suspend Addr = Any address 0 Read None Status register data Toggle CE# or OE# to update Status register Addr = Any address Idle None Check SR[7]: 1 = WSM ready 0 = WSM busy Idle None Check SR[2]: 1 = Program suspended 0 = Program completed Write Read Array Data = 0xFF Addr = Any address Read None Read array data from block other than the one being programmed 1 SR[2] = 0 Program Completed 1 Write 0xFF (Read Array) Read Array Data Done Reading Data = 0x70 Addr = Any address (Read Status) Read Status Register SR[7] = Read Status Comments Write 0xFF No (Read Array) Write Program Data = 0xD0 Resume Addr = Any address Read Array Data Yes Write 0xD0 Any Address (Program Resume) Program Resumed March 2008 290645-24 Datasheet 57 C3 Discrete Figure 19: Erase Suspend / Resume Flowchart ERASE SUSPEND / RESUME PROCEDURE Bus Operation Command Start Write 0xB0, Any Address Write 0x70, Any Address Write Read Status Data = 0x70 Addr = Any address Write Erase Suspend Data = 0xB0 Addr = Any address Read None Status Register data. Toggle CE# or OE# to update Status register; Addr = Any Address Idle None Check SR[7]: 1 = WSM ready 0 = WSM busy Idle None Check SR[6]: 1 = Erase suspended 0 = Erase completed (Erase Suspend) (Read Status) Read Status Register SR[7] = 0 1 SR[6] = 0 Erase Completed Write 1 Write 0xFF (Read Array) Read or Write Read Array Data Done Reading Comments Write Read Array Data = 0xFF or 0x40 or Program Addr = Any address None Read array or program data from/to block other than the one being erased Program Data = 0xD0 Resume Addr = Any address 0 1 (Erase Resume) Datasheet 58 Write 0xD0, Any Address Write 0xFF Erase Resumed Read Array Data (Read Array) March 2008 290645-24 C3 Discrete Figure 20: Block Erase Flowchart BLOCK ERASE PROCEDURE Bus Comments Operation Command Block Data = 0x20 Write Erase Addr = Block to be erased (BA) Setup Start Write 0x20, Block Address (Block Erase) Write Erase Confirm Read None Status Register data. Toggle CE# or OE# to update Status register data Idle None Check SR[7]: 1 = WSM ready 0 = WSM busy Write 0xD0, (Erase Confirm) Block Address Suspend Erase Loop Read Status Register No 0 SR[7] = Suspend Erase 1 Data = 0xD0 Addr = Block to be erased (BA) Yes Repeat for subsequent block erasures. Full Status register check can be done after each block erase or after a sequence of block erasures. Full Erase Status Check (if desired) Write 0xFF after the last operation to enter read array mode. Block Erase Complete FULL ERASE STATUS CHECK PROCEDURE Read Status Register SR[3] = Bus Command Operation 1 VP P Range Error 0 SR[4,5] = 1,1 Command Sequence Error 0 SR[5] = 1 Block Erase Error 1 Block Locked Error 0 SR[1] = 0 Block Erase Successful March 2008 290645-24 Comments Idle None Check SR[3]: 1 = VP P Range Error Idle None Check SR[4,5]: Both 1 = Command Sequence Error Idle None Check SR[5]: 1 = Block Erase Error Check SR[1]: 1 = Attempted erase of locked block; erase aborted. SR[1,3] must be cleared before the Write State Machine will allow further erase attempts. Idle None Only the Clear Status Register command clears SR[1, 3, 4, 5]. If an error is detected, clear the Status register before attempting an erase retry or other error recovery. Datasheet 59 C3 Discrete Figure 21: Locking Operations Flowchart LOCKING OPERATIONS PROCEDURE Start Write 0x60, Block Address (Lock Setup) Write Write either 0x01/0xD0/0x2F, Block Address (Lock Confirm) Write Write 0x90 O ptional Bus Operation Command (Read Device ID) No Yes Write 0xFF Any Address Data = 0x60 Addr = Any Address Lock, Data = Unlock, or Lock-Down Confirm Addr = 0x01 (Block Lock) 0xD0 (Block Unlock) 0x2F (Lock-Down Block) Block to lock/unlock/lock-down Write Read Data = 0x90 (Optional) Device ID Addr = Any Address Read Block Lock Block Lock status data (Optional) Status Addr = Block address + offset 2 Read Block Lock Status Locking Change? Lock Setup Comments Idle (Optional) None Confirm locking change on D[1,0] . Write Read Array Data = 0xFF Addr = Any address (Read Array) Lock Change Complete Datasheet 60 March 2008 290645-24 C3 Discrete Figure 22: Protection Register Programming Flowchart PROTECTION REGISTER PROGRAMMING PROCEDURE Bus Operation Command Start Write 0xC0, PR Address Program Data = 0xC0 PR Setup Addr = First Location to Program Write Protection Data = Data to Program Program Addr = Location to Program (Confirm Data) Read Status Register SR[7] = Write (Program Setup) Write PR Address & Data Comments Read None Status Register Data. Toggle CE# or OE# to Update Status Register Data Idle None Check SR[7]: 1 = WSM Ready 0 = WSM Busy Program Protection Register operation addresses must be within the Protection Register address space. Addresses outside this space will return an error. 0 1 Repeat for subsequent programming operations. Full Status Check (if desired) Full Status Register check can be done after each program, or after a sequence of program operations. Write 0xFF after the last operation to set Read Array state. Program Complete FULL STATUS CHECK PROCEDURE Read Status Register Data SR[3], SR[4] = Bus Command Operation 1 Comments Idle None Check SR[1], SR[3], SR[4]: 0,1,1 = VP P Range Error Idle None Check SR[1], SR[3], SR[4]: 0,0,1 = Programming Error Idle None Check SR[1], SR[3], SR[4]: 1,0,1 = Block locked; operation aborted VP P Range Error 0 SR[3], SR[4] = 1 Program Error SR[3] must be cleared before the Write State Machine will allow further program attempts. 0 Only the Clear Staus Register command clears SR[1, 3, 4]. SR[3], SR[4] = 1 Register Locked; Program Aborted If an error is detected, clear the Status register before attempting a program retry or other error recovery. 0 Program Successful March 2008 290645-24 Datasheet 61 C3 Discrete Appendix C Common Flash Interface This appendix defines the data structure or "database" returned by the Common Flash Interface (CFI) Query command. System software should parse this structure to gain critical information such as block size, density, x8/x16, and electrical specifications. Once this information has been obtained, the software detects which command sets to use to enable flash writes, block erases, and otherwise control the flash component. The Query is part of an overall specification for multiple command set and control interface descriptions called Common Flash Interface, or CFI. C.1 Query Structure Output The Query database allows system software to obtain information for controlling the flash device. This section describes the device's CFI-compliant interface that allows access to Query data. Query data are presented on the lowest-order data outputs (DQ0-DQ7) only. The numerical offset value is the address relative to the maximum bus width supported by the device. On this family of devices, the Query table device starting address is a 0x10, which is a word address for x16 devices. For a word-wide (x16) device, the first two Query-structure bytes, ASCII "Q" and "R," appear on the low byte at word addresses 0x10 and 0x11. This CFI-compliant device outputs 0x00 data on upper bytes. The device outputs ASCII "Q" in the low byte (DQ0DQ7) and 0x00 in the high byte (DQ8-DQ15). At Query addresses containing two or more bytes of information, the least-significant data byte is presented at the lower address, and the most-significant data byte is presented at the higher address. For tables in this appendix, addresses and data are represented in hexadecimal notation, so the "h" suffix has been dropped. In addition, since the upper byte of wordwide devices is always "0x00," the leading "00" has been dropped from the table notation and only the lower byte value is shown. Any x16 device outputs can be assumed to have 0x00 on the upper byte in this mode. Table 28: Summary of Query Structure Output as a Function of Device and Mode Device Device Addresses Datasheet 62 Hex Offset Hex Code ASCII Value 00010: 51 "Q" 00011: 52 "R" 00012: 59 "Y" March 2008 290645-24 C3 Discrete Table 29: Example of Query Structure Output of x16 Devices Word Addressing: Offset Hex Code A[X-0] Value DQ[16:0] 0x00010 0051 "Q" 0x00011 0052 "R" 0x00012 0059 "Y" 0x00013 P_IDLO PrVendor 0x00014 P_IDHI ID # 0x00015 PLO PrVendor 0x00016 PHI TblAdr 0x00017 A_IDLO AltVendor 0x00018 A_IDHI ID # ... C.2 ... ... Query Structure Overview The Query command causes the flash component to display the Common Flash Interface (CFI) Query structure or "database." Table 30 summarizes the structure subsections and address locations. Table 30: Query Structure Offset 0x00000 Manufacturer Code 0x00001 0x(BA+2) Description1 Sub-Section Name Device Code 2 0x00004-0xF Block Status register Block-specific information Reserved Reserved for vendor-specific information 0x00010 CFI query identification string Command set ID and vendor data offset 0x0001B System interface information Device timing & voltage information 0x00027 Device geometry definition Flash device layout P3 Primary Numonyx-specific Extended Query Table Vendor-defined additional information specific to the Primary Vendor Algorithm Notes: 1. Refer to the Query Structure Output section and offset 0x28 for the detailed definition of offset address as a function of device bus width and mode. 2. BA = Block Address beginning location (i.e., 0x08000 is block 1's beginning location when the block size is 32K-word). 3. Offset 15 defines "P" which points to the Primary Numonyx-specific Extended Query Table. C.3 Block Status Register The Block Status Register indicates whether an erase operation completed successfully or whether a given block is locked or can be accessed for flash program/erase operations. See Table 31. Block Erase Status (BSR[1]) allows system software to determine the success of the last block erase operation. BSR[1] can be used just after power-up to verify that the VCC supply was not accidentally removed during an erase operation. March 2008 290645-24 Datasheet 63 C3 Discrete Table 31: Block Status Register Offset Length 0x(BA+2)1 1 Description Add. Value Block Lock Status Register BA+2 --00 or --01 BSR[0] Block lock status 0 = Unlocked 1 = Locked BA+2 (bit 0): 0 or 1 BSR[1] Block lock-down status 0 = Not locked down 1 = Locked down BA+2 (bit 1): 0 or 1 BSR[7:2]: Reserved for future use BA+2 (bit 2-7): 0 Notes: 1. BA = Block Address beginning location (i.e., 0x08000 is block 1's beginning location when the block size is 32K-word). C.4 CFI Query Identification String The Identification String provides verification that the component supports the Common Flash Interface specification. It also indicates the specification version and supported vendor-specified command set(s). See Table 32. Table 32: CFI Identification Offset Length 0x10 3 0x13 Description Add. Hex Code Value Query-unique ASCII string "QRY" 10: 11: 12: --51 --52 --59 "Q" "R" "Y" 2 Primary vendor command set and control interface ID code 16-bit ID code for vendor-specified algorithms 13: 14: --03 --00 0x15 2 Extended Query Table primary algorithm address 15: 16: --35 --00 0x17 2 Alternate vendor command set and control interface ID code 0x0000 means no second vendor-specified algorithm exists 17: 18: --00 --00 0x19 2 Secondary algorithm Extended Query Table address 0x0000 means none exists 19: 1A: --00 --00 Add. Hex Code Value Table 33: System Interface Information Offset Length 0x1B 1 VCC logic supply minimum program/erase voltage bits 0-3 BCD 100 mV bits 4-7 BCD volts 1B: --27 2.7 V 0x1C 1 VCC logic supply maximum program/erase voltage bits 0-3 BCD 100 mV bits 4-7 BCD volts 1C: --36 3.6 V 0x1D 1 VPP [programming] supply minimum program/erase voltage bits 0-3 BCD 100 mV bits 4-7 HEX volts 1D: --B4 11.4 V 0x1E 1 VPP [programming] supply maximum program/erase voltage bits 0-3 BCD 100 mV bits 4-7 HEX volts 1E: --C6 12.6 V 0x1F 1 "n" such that typical single word program time-out =2n s 1F: --05 32 s Datasheet 64 Description March 2008 290645-24 C3 Discrete Table 33: System Interface Information Offset Length Description Add. 2n Value 0x20 1 "n" such that typical max. buffer write time-out = 20: --00 NA 0x21 1 "n" such that typical block erase time-out = 2n ms 21: --0A 1s 0x22 1 "n" such that typical full chip erase time-out = 2n ms 22: --00 NA 0x23 1 "n" such that maximum word program time-out = 2n times typical 23: --04 512s 0x24 1 "n" such that maximum buffer write time-out = 2n times typical 24: --00 NA 0x25 1 "n" such that maximum block erase time-out = 2n times typical 25: --03 8s 26: --00 NA 0x26 1 C.5 "n" such that maximum chip erase time-out = 2n s Hex Code times typical Device Geometry Definition Table 34: Device Geometry Definition Offset Length Description Add. Hex Code Value 27 Table 35, "Device Geometry Details" on page 66 28: 29: --01 --00 x16 "n" such that maximum number of bytes in write buffer = 2n 2A: 2B: --00 --00 0 1 Number of erase block regions within device: 1. x = 0 means no erase blocking; the device erases in "bulk" 2. x specifies the number of device or partition regions with one or more contiguous same-size erase blocks. 3. Symmetrically blocked partitions have one blocking region 4. Partition size = (total blocks) x (individual block size) 2C: --02 2 2D: 2E: 2F: 30: See 4 Erase Block Region 1 Information bits 0-15 = y, y+1 = number of identical-size erase blocks bits 16-31 = z, region erase block(s) size are z x 256 bytes 31: 32: 33: 34: See 14 Erase Block Region 2 Information bits 0-15 = y, y+1 = number of identical-size erase blocks bits 16-31 = z, region erase block(s) size are z x 256 bytes See n 0x27 1 "n" such that device size = 2 in number of bytes 0x28 2 Flash device interface: 0x2A 2 0x2C 0x2D 0x2D March 2008 290645-24 x8 async 28:00,29:0 0 x16 async 28:01,29:00 x8/x16 async 28:02,29:00 Table 35, "Device Geometry Details" on page 66 Table 35, "Device Geometry Details" on page 66 Datasheet 65 C3 Discrete Table 35: Device Geometry Details 16 Mbit 32 Mbit 64 Mbit Address 0x27 -B -T -B -T -B -T --15 -15 --16 -16 --17 --17 0x28 --01 --01 --01 --01 --01 --01 0x29 --00 --00 --00 -00 -00 -00 0x2A --00 --00 --00 -00 -00 -00 0x2B --00 --00 --00 -00 -00 -00 0x2C --02 --02 --02 --02 --02 --02 0x2D --07 --1E --07 --3E --07 --7E 0x2E --00 --00 --00 -00 -00 -00 0x2F --20 --00 --20 -00 --20 --00 0x30 --00 --01 --00 --01 --00 --01 0x31 --1E --07 --3E --07 --7E --07 0x32 --00 --00 --00 -00 -00 -00 0x33 --00 --20 --00 --20 --00 --20 0x34 --01 --00 --01 --00 --01 --00 C.6 Numonyx-Specific Extended Query Table Certain flash features and commands are optional as shown in Table 36, "PrimaryVendor Specific Extended Query" on page 66. The Numonyx-specific Extended Query table specifies these features as well as other similar types of information. Table 36: Primary-Vendor Specific Extended Query (Sheet 1 of 2) Offset1 P = 0x15 Length 0x(P+0) 0x(P+1) 0x(P+2) 3 Description (Optional Flash Features and Commands) Primary extended query table Unique ASCII string "PRI" Address Hex Code Value 35: 36: 37: --50 --52 --49 "P" "R" "I" 0x(P+3) 1 Major version number, ASCII 38: --31 "1" 0x(P+4) 1 Minor version number, ASCII 39: --30 "0" Optional feature and command support (1=yes, 0=no) bits 9-31 are reserved; undefined bits are "0." If bit 31 is "1" then another 31 bit field of optional features follows at the end of the bit-30 field. 3A: 3B: 3C: 3D: --66 --00 --00 --00 0x(P+5) 0x(P+6) 0x(P+7) 0x(P+8) Datasheet 66 4 bit bit bit bit bit bit bit bit bit 0 1 2 3 4 5 6 7 8 Chip erase supported Suspend erase supported Suspend program supported Legacy lock/unlock supported Queued erase supported Instant individual block locking supported Protection bits supported Page mode read supported Synchronous read supported bit bit bit bit bit bit bit bit bit 0 1 2 3 4 5 6 7 8 = = = = = = = = = 0 1 1 0 0 1 1 0 0 No Yes Yes No No Yes Yes No No March 2008 290645-24 C3 Discrete Table 36: Primary-Vendor Specific Extended Query (Sheet 2 of 2) Offset1 P = 0x15 Length 0x(P+9) 1 Description (Optional Flash Features and Commands) Supported functions after suspend: Read Array, Status, Query Other supported operations are: bits 1-7 reserved; undefined bits are "0" Address Hex Code 3E: --01 bit 0 Program supported after erase suspend 0x(P+A) 0x(P+B) 2 Block Status Register mask bits 2-15 are Reserved; undefined bits are "0" bit 0 Block Lock-Bit Status Register active bit 1 Block Lock-Down Bit Status active bit 0 = 1 Value Yes 3F: --03 40: --00 bit 0 = 1 Yes bit 1 = 1 Yes 0x(P+C) 1 VCC logic supply highest performance program/ erase voltage bits 0-3 BCD value in 100 mV bits 4-7 BCD value in volts 41: --33 3.3 V 0x(P+D) 1 VPP optimum program/erase supply voltage bits 0-3 BCD value in 100 mV bits 4-7 HEX value in volts 42: --C0 12.0 V Notes: 1. The variable P is a pointer which is defined at CFI offset 0x15. Table 37: Protection Register Information Offset1 P = 0x35 Length 0x(P+E) 1 Description (Optional Flash Features and Commands) Address Hex Code Value 43: --01 01 44: 45: 46: --80 --00 --03 80h 00h 8 byte 0x(P+12) Protection Field 1: Protection Description This field describes user-available One Time Programmable (OTP) Protection register bytes. Some are pre-programmed with deviceunique serial numbers. Others are user programmable. Bits 0-15 point to the Protection register Lock byte, the section's first byte. The following bytes are factory pre-programmed and userprogrammable. bits 0-7 = Lock/bytes JEDEC-plane physical low address bits 8-15 = Lock/bytes JEDEC -plane physical high address bits 16-23 = "n" such that 2n = factory pre-programmed bytes bits 24-31 = "n" such that 2n = user programmable bytes 47: --03 8 byte 0x(P+13) Reserved for future use 48: Number of Protection register fields in JEDEC ID space. "00h," indicates that 256 protection bytes are available 0x(P+F) 0x(P+10) (0xP+11) 4 Notes: 1. The variable P is a pointer which is defined at CFI offset 0x15. March 2008 290645-24 Datasheet 67 C3 Discrete Appendix D Additional Information Order Number Document/Tool 297938 3 Volt Advanced+ Boot Block Flash Memory Specification Update 292216 AP-658 Designing for Upgrade to the Advanced+ Boot Block Flash Memory 292215 AP-657 Designing with the Advanced+ Boot Block Flash Memory Architecture Contact your Numonyx Representative NumonyxTM Flash Data Integrator (NumonyxTM FDI) Software Developer's Kit 297874 IFDI Interactive: Play with NumonyxTM Flash Data Integrator on Your PC Notes: 1. To request Numonyx documentation or tools, contact your local Numonyx or distribution sales office. Datasheet 68 March 2008 290645-24 C3 Discrete Appendix E Ordering Information Figure 23: Component Ordering Information T E2 8 F 3 2 0 C3 T C7 0 Package TE = 48- Lead TSOP GT = 48- Ball BGA * CSP GE = VF BGA CSP RC = Easy BGA PC = Pb Free Easy BGA PH = Pb Free VFBGA JS = Pb Free TSOP Product line designator (R) for all Intel Flash products Device Density 640 = x16 (64 Mbit) 320 = x16 (32 Mbit) 160 = x16 (16 Mbit) 800 = x16 (8 Mbit) March 2008 290645-24 Access Speed (ns) (70, 80 , 90, 100 , 110 ) Lithography A = 0.25 m C = 0.18 m D = 0.13 m T = Top Blocking B = Bottom Blocking Product Family C3 = 3 Volt Advanced+ Boot Block VCC = 2.7 V-3.6 V VPP = 2 .7 V-3 .6 V or 11 . 4 V-12 .6 V Datasheet 69 C3 Discrete Table 38: Product Information Ordering Matrix VALID COMBINATIONS (All Extended Temperature) 48-Lead TSOP 48-Ball BGA* CSP 48-Ball VF BGA Easy BGA Extended 64 Mbit Extended 32 Mbit Extended 16 Mbit Extended 8 Mbit Note: TE28F320C3TD70 TE28F320C3BD70 TE28F320C3TC70 TE28F320C3BC70 TE28F320C3TC90 TE28F320C3BC90 TE28F320C3TA100 TE28F320C3BA100 TE28F320C3TA110 TE28F320C3BA110 JS28F320C3BD70 JS28F320C3TD70 JS28F320C3BD90 JS28F320C3TD90 TE28F160C3TD70 TE28F160C3BD70 TE28F160C3TC70 TE28F160C3BC70 TE28F160C3TC80 TE28F160C3BC80 TE28F160C3TC90 TE28F160C3BC90 TE28F160C3TA90 TE28F160C3BA90 TE28F160C3TA110 TE28F160C3BA110 JS28F160C3BD70 JS28F160C3TD70 TE28F800C3TD70 TE28F800C3BD70 TE28F800C3TA90 TE28F800C3BA90 TE28F800C3TA110 TE28F800C3BA110 JS28F800C3BD70 JS28F800C3TD70 GT28F320C3TA100 GT28F320C3BA100 GT28F320C3TA110 GT28F320C3BA110 GT28F160C3TA90 GT28F160C3BA90 GT28F160C3TA110 GT28F160C3BA110 GE28F320C3TD70 GE28F320C3BD70 GE28F320C3TC70 GE28F320C3BC70 GE28F320C3TC90 GE28F320C3BC90 PH28F320C3BD70 PH28F320C3TD70 PH28F320C3BD90 PH28F320C3TD90 GE28F160C3TD70 GE28F160C3BD70 GE28F160C3TC70 GE28F160C3BC70 GE28F160C3TC80 GE28F160C3BC80 GE28F160C3TC90 GE28F160C3BC90 PH28F160C3BD70 PH28F160C3TD70 RC28F320C3TD70 RC28F320C3BD70 RC28F320C3TD90 RC28F320C3BD90 RC28F320C3TC90 RC28F320C3BC90 RC28F320C3TA100 RC28F320C3BA100 RC28F320C3TA110 RC28F320C3BA110 PC28F320C3BD70 PC28F320C3TD70 PC28F320C3BD90 PC28F320C3TD90 RC28F160C3TD70 RC28F160C3BD70 RC28F160C3TC70 RC28F160C3BC70 RC28F160C3TC80 RC28F160C3BC80 RC28F160C3TC90 RC28F160C3BC90 RC28F160C3TA90 RC28F160C3BA90 RC28F160C3TA110 RC28F160C3BA110 PC28F160C3BD70 PC28F160C3TD70 RC28F800C3TD70 RC28F800C3BD70 RC28F800C3TA90 RC28F800C3BA90 RC28F800C3TA110 RC28F800C3BA110 PC28F800C3BD70 PC28F800C3TD70 The second line of the 48-ball BGA package top side mark specifies assembly codes. For samples only, the first character signifies either "E" for engineering samples or "S" for silicon daisy chain samples. All other assembly codes without an "E" or "S" as the first character are production units. Datasheet 70 March 2008 290645-24