HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 512Mb NAND FLASH HY27US(08/16)12(1/2)B HY27US0812(1/2)B HY27US1612(1/2)B This document is a general product description and is subject to change without notice. Hynix does not assume any responsibility for use of circuits described. No patent licenses are implied. Rev 0.5 / Jul. 2007 1 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Document Title 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Memory Revision History Revision No. History Draft Date Remark Preliminary 0.0 Initial Draft. Oct. 19. 2006 0.1 1) Correct Figure 14 & 15 Mar. 07. 2007 1) Add AC Characteristics 0.2 - tRB : Last RE High to busy (at sequential read) - tCRY : CE High to Ready (in case of interception by CE at read) Mar. 26. 2007 - tCEH : CE High Hold Time (at the last serial read) 0.3 1) Add sequential row read feature and figure 2) Modify Block Replacement Apr. 27. 2007 1) Add x16 Characteristics 0.4 2) Modify read2 operation (sequential row read) 3) Add AC Characteristics May. 29. 2007 - tOH : RE or CE High to Output Hold 1) Correct Read ID Table 16 0.5 2) Correct System Interface Using CE don't care operation Jul. 20. 2007 3) Correct Command Set Table 5 Rev 0.5 / Jul. 2007 2 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash FEATURES SUMMARY HIGH DENSITY NAND FLASH MEMORIES - Cost effective solutions for mass storage applications NAND INTERFACE - x8 or x16 bus width. - Multiplexed Address/ Data - Pinout compatibility for all densities FAST BLOCK ERASE - Block erase time: 2ms (Typ.) STATUS REGISTER ELECTRONIC SIGNATURE - 1st cycle: Manufacturer Code - 2nd cycle: Device Code SUPPLY VOLTAGE - VCC = 2.7 to 3.6V : HY27US(08/16)12(1/2)B CHIP ENABLE DON'T CARE - Simple interface with microcontroller Memory Cell Array x8 : (512+16) Bytes x 32 Pages x 4,096 Blocks x16 : (256+8) Words x 32 Pages x 4,096 Blocks PAGE SIZE HARDWARE DATA PROTECTION - Program/Erase locked during Power transitions CE DON't CARD OPTION ONLY - x8 device : (512+16) Bytes : HY27US0812(1/2)B - x16 device : (256+8) Words : HY27US1612(1/2)B BLOCK SIZE - x8 device: (16K + 512 spare) Bytes - x16 device: (8K + 256 spare) Words DATA RETENTION - 100,000 Program/Erase cycles (with 1bit/512byte ECC) - 10 years Data Retention PACKAGE - HY27US(08/16)12(1/2)B-T(P) : 48-Pin TSOP1 (12 x 20 x 1.2 mm) - HY27US(08/16)12(1/2)B-T (Lead) - HY27US(08/16)12(1/2)B-TP (Lead Free) PAGE READ / PROGRAM - Random access: 12us (max.) - Sequential access: 30ns (min.) - Page program time: 200us (typ.) - HY27US0812(1/2)B-S(P) : 48-Pin USOP1 (12 x 17 x 0.65 mm) - HY27US0812(1/2)B-S (Lead) - HY27US0812(1/2)B-SP (Lead Free) COPY BACK PROGRAM MODE - Fast page copy without external buffering - HY27US0812(1/2)B-F(P) : 63-Ball FBGA (9 x 11 x 1.0 mm) - HY27US0812(1/2)B-F (Lead) - HY27US0812(1/2)B-FP (Lead Free) Rev 0.5 / Jul. 2007 3 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 1. SUMMARY DESCRIPTION The Hynix HY27US(08/16)12(1/2)B series is a 64Mx8bit with spare 2Mx8 bit capacity. The device is offered in 3.3V Vcc Power Supply. Their NAND cell provides the most cost-effective solution for the solid state mass storage market. The memory is divided into blocks that can be erased independently so it is possible to preserve valid data while old data is erased. The memory contains 4096 blocks, composed by 32 pages consisting in two NAND structures of 16 series connected Flash cells. A program operation allows to write the 512-byte (x8 device) or 256-word (x16 device) page in typical 200us and an erase operation can be performed in typical 2ms on a 16K-byte (X8 device) block. Data in the page can be read out at 30ns cycle time (3.3V device) per byte. The I/O pins serve as the ports for address and data input/output as well as command input. This interface allows a reduced pin count and easy migration towards different densities, without any rearrangement of footprint. Commands, Data and Addresses are synchronously introduced using CE, WE, ALE and CLE input pin. The on-chip Program/Erase Controller automates all program and erase functions including pulse repetition, where required, and internal verification and margining of data. The modify operations can be locked using the WP input pin . The output pin R/B (open drain buffer) signals the status of the device during each operation. In a system with multiple memories the R/B pins can be connected all together to provide a global status signal. Even the write-intensive systems can take advantage of the HY27US(08/16)12(1/2)B extended reliability of 100K program/erase cycles by providing ECC (Error Correcting Code) with real time mapping-out algorithm. The chip is offered with the CE don't care function. This option allows the direct download of the code from the NAND Flash memory device by a microcontroller, since the CE transitions do not stop the read operation. The copy back function allows the optimization of defective blocks management: when a page program operation fails the data can be directly programmed in another page inside the same array section without the time consuming serial data insertion phase. This device includes also extra features like OTP/Unique ID area, Read ID2 extension. The HY27US(08/16)12(1/2)B is available in 48 - TSOP1 12 x 20 mm package, 48 - USOP1 12 x 17 mm, FBGA 9 x 11 mm. 1.1 Product List PART NUMBER ORIZATION HY27US0812(1/2)B x8 HY27US1612(1/2)B x16 Rev 0.5 / Jul. 2007 VCC RANGE 2.7V - 3.6 Volt PACKAGE 48TSOP1/ 48USOP1/ 63FBGA 48TSOP1 4 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 9&& ,2a,2 &( ,2a,2 [RQO\ :( 5% 5( $/( &/( :3 966 Figure1: Logic Diagram IO15 - IO8 Data Input / Outputs (x16 only) IO7 - IO0 Data Inputs / Outputs CLE Command latch enable ALE Address latch enable CE Chip Enable RE Read Enable WE Write Enable WP Write Protect R/B Ready / Busy Vcc Power Supply Vss Ground NC No Connection Table 1: Signal Names Rev 0.5 / Jul. 2007 5 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 1& 1& 1& 1& 1& 1& 5% 5( &( 1& 1& 9FF 9VV 1& 1& &/( $/( :( :3 1& 1& 1& 1& 1& 1$1')ODVK 7623 [ 1& 1& 1& 1& 1& 1& 5% 5( &( 1& 1& 9FF 9VV 1& 1& &/( $/( :( :3 1& 1& 1& 1& 1& 1& 1& 1& 1& ,2 ,2 ,2 ,2 1& 1& 1& 9FF 9VV 1& 1& 1& ,2 ,2 ,2 ,2 1& 1& 1& 1& 1$1')ODVK 7623 [ 9VV ,2 ,2 ,2 ,2 ,2 ,2 ,2 ,2 1& 1& 9FF 1& 1& 1& ,2 ,2 ,2 ,2 ,2 ,2 ,2 ,2 9VV Figure 2. 48TSOP1 Contactions, x8 and x16 Device 1& 1& 1& 1& 1& 1& 5% 5( &( 1& 1& 9FF 9VV 1& 1& &/( $/( :( :3 1& 1& 1& 1& 1& 1$1')ODVK 8623 [ 1& 1& 1& 1& ,2 ,2 ,2 ,2 1& 1& 1& 9FF 9VV 1& 1& 1& ,2 ,2 ,2 ,2 1& 1& 1& 1& Figure 3. 48USOP1 Contactions, x8 Rev 0.5 / Jul. 2007 6 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash $ 1& % 1& 1& & :3 $/( 9VV &( :( 5% ' 1& 5( &/( 1& 1& 1& ( 1& 1& 1& 1& 1& 1& ) 1& 1& 1& 1& 1& 1& * 1& 1& 1& 1& 1& 1& + 1& ,2 1& 1& 1& 9FF - 1& ,2 1& 9FF ,2 ,2 . 9VV ,2 ,2 ,2 ,2 9VV 1& 1& 1& 1& / 1& 1& 1& 1& 0 1& 1& 1& 1& Figure 4. 63FBGA Contactions, x8 Device (Top view through package) Rev 0.5 / Jul. 2007 7 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 1.2 PIN DESCRIPTION Pin Name IO0-IO7 IO8-IO15(1) CLE ALE CE WE RE WP R/B VCC VSS NC Description DATA INPUTS/OUTPUTS The IO pins allow to input command, address and data and to output data during read / program operations. The inputs are latched on the rising edge of Write Enable (WE). The I/O buffer float to High-Z when the device is deselected or the outputs are disabled. COMMAND LATCH ENABLE This input activates the latching of the IO inputs inside the Command Register on the Rising edge of Write Enable (WE). ADDRESS LATCH ENABLE This input activates the latching of the IO inputs inside the Address Register on the Rising edge of Write Enable (WE). CHIP ENABLE This input controls the selection of the device. When the device is busy CE low does not deselect the memory. WRITE ENABLE This input acts as clock to latch Command, Address and Data. The IO inputs are latched on the rise edge of WE. READ ENABLE The RE input is the serial data-out control, and when active drives the data onto the I/O bus. Data is valid tREA after the falling edge of RE which also increments the internal column address counter by one. WRITE PROTECT The WP pin, when Low, provides an Hardware protection against undesired modify (program / erase) operations. READY BUSY The Ready/Busy output is an Open Drain pin that signals the state of the memory. SUPPLY VOLTAGE The VCC supplies the power for all the operations (Read, Write, Erase). GROUND NO CONNECTION Table 2: Pin Description NOTE: 1. For x16 Version Only 2. A 0.1uF capacitor should be connected between the Vcc Supply Voltage pin and the Vss Ground pin to decouple the current surges from the power supply. The PCB track widths must be sufficient to carry the currents required during program and erase operations. Rev 0.5 / Jul. 2007 8 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash IO0 IO1 IO2 IO3 IO4 IO5 IO6 IO7 1st Cycle A0 A1 A2 A3 A4 A5 A6 A7 2nd Cycle A9 A10 A11 A12 A13 A14 A15 A16 3rd Cycle A17 A18 A19 A20 A21 A22 A23 A24 4th Cycle A25 (1) (1) (1) (1) (1) (1) L(1) L L L L L L Table 3: Address Cycle Map(x8) NOTE: 1. L must be set to Low. 2. A8 is set to LOW or High by the 00h or 01h Command. IO0 IO1 IO2 IO3 IO4 IO5 IO6 IO7 IO8-IO15 1st Cycle A0 A1 A2 A3 A4 A5 A6 A7 L(1) 2nd Cycle A9 A10 A11 A12 A13 A14 A15 A16 L(1) 3rd Cycle A17 A18 A19 A20 A21 A22 A23 A24 L(1) 4th Cycle A25 L(1) L(1) L(1) L(1) L(1) L(1) L(1) L(1) Table 4: Address Cycle Map(x16) NOTE: 1. L must be set to Low. FUNCTION 1st CYCLE 2nd CYCLE 3rd CYCLE 4th CYCLE READ 1 00h/01h - - - READ 2 50h - - - READ ID 90h - - - RESET FFh - - - PAGE PROGRAM (start) 80h 10h - - COPY BACK PGM (start) 00h 8Ah - - BLOCK ERASE 60h D0h - - READ STATUS REGISTER 70h - - - Acceptable command during busy Yes Yes Table 5: Command Set Rev 0.5 / Jul. 2007 9 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash CLE ALE CE WE RE WP MODE H L L Rising H X L H L Rising H X H L L Rising H H L H L Rising H H L L L Rising H H Data Input L L L(1) H Falling X Sequential Read and Data Output L L L H H X During Read (Busy) X X X X X H During Program (Busy) X X X X X H During Erase (Busy) X X X X X L Write Protect X X H X X 0V/Vcc Read Mode Write Mode Command Input Address Input(4 cycles) Command Input Address Input(4 cycles) Stand By Table 6: Mode Selection NOTE: 1. With the CE high during latency time does not stop the read operation Rev 0.5 / Jul. 2007 10 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 2. BUS OPERATION There are six standard bus operations that control the device. These are Command Input, Address Input, Data Input, Data Output, Write Protect, and Standby. Typically glitches less than 5 ns on Chip Enable, Write Enable and Read Enable are ignored by the memory and do not affect bus operations. 2.1 Command Input. Command Input bus operation is used to give a command to the memory device. Command are accepted with Chip Enable low, Command Latch Enable High, Address Latch Enable low and Read Enable High and latched on the rising edge of Write Enable. Moreover for commands that starts a modify operation (write/erase) the Write Protect pin must be high. See figure 6 and table 13 for details of the timings requirements. Command codes are always applied on IO7:0, disregarding the bus configuration (X8/X16). 2.2 Address Input. Address Input bus operation allows the insertion of the memory address. To insert the 25 addresses needed to access the 512Mbit 4 clock cycles (x8 version) are needed. Addresses are accepted with Chip Enable low, Address Latch Enable High, Command Latch Enable low and Read Enable High and latched on the rising edge of Write Enable. Moreover for commands that starts a modify operation (write/erase) the Write Protect pin must be high. See figure 7 and table 13 for details of the timings requirements. Addresses are always applied on IO7:0, disregarding the bus configuration (X8/X16). 2.3 Data Input. Data Input bus operation allows to feed to the device the data to be programmed. The data insertion is serially and timed by the Write Enable cycles. Data are accepted only with Chip Enable low, Address Latch Enable low, Command Latch Enable low, Read Enable High, and Write Protect High and latched on the rising edge of Write Enable. See figure 8 and table 13 for details of the timings requirements. 2.4 Data Output. Data Output bus operation allows to read data from the memory array and to check the status register content, the lock status and the ID data. Data can be serially shifted out toggling the Read Enable pin with Chip Enable low, Write Enable High, Address Latch Enable low, and Command Latch Enable low. See figures 9 to 15 and table 13 for details of the timings requirements. 2.5 Write Protect. Hardware Write Protection is activated when the Write Protect pin is low. In this condition modify operation do not start and the content of the memory is not altered. Write Protect pin is not latched by Write Enable to ensure the protection even during the power up. 2.6 Standby. In Standby mode the device is deselected, outputs are disabled and Power Consumption is reduced. Rev 0.5 / Jul. 2007 11 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 3. DEVICE OPERATION 3.1 Page Read. Three types of operations are available: random read, serial page read and sequential row read. The random read mode is enabled when the page address is changed. The 528 bytes (x8 device) or 264 words (x16 device) of data within the selected page are transferred to the data registers in less than access random read time tR (12us). The system controller can detect the completion of this data transfer tR (12us) by analyzing the output of R/B pin. Once the data in a page is loaded into the registers, they may be read out in 30ns cycle time by sequentially pulsing RE. High to low transitions of the RE clock output the data stating from the selected column address up to the last column address. After the data of last column address is clocked out, the next page is automatically selected for sequential row read. Waiting tR again allows reading the selected page. The sequential row read operation is terminated by bringing CE high. The way the Read1 and Read2 commands work is like a pointer set to either the main area or the spare area. Writing the Read2 command user may selectively access the spare area of bytes 512 to 527 (x8 device) or words 256 to 263 (x16 device). Addresses A0 to A3 set the starting address of the spare area while addresses A4 to A7 are ignored. Unless the operation is aborted, the page address is automatically incremented for sequential row Read as in Read1 operation and spare sixteen bytes of each page (x8 device) or eight words of each page (x16 device) may be sequentially read. The Read1 command (00h/01h) is needed to move the pointer back to the main area. The Read2 command (50h) is needed to move the pointer back to the spare area. Figure_11 to 14 show typical sequence and timings for each read operation. 3.2 Page Program. The device is programmed basically on a page basis, but it does allow multiple partial page programming of a byte or consecutive bytes up to 528 (x8 device), in a single page program cycle. The number of consecutive partial page programming operations within the same page without an intervening erase operation must not exceed 1 for main array and 2 for spare array. The addressing may be done in any random order in a block. A page program cycle consists of a serial data loading period in which up to 528 bytes (x8 device) or 264 word (x16 device) of data may be loaded into the page register, followed by a non-volatile programming period where the loaded data is programmed into the appropriate cell. Serial data loading can be started from 2nd half array by moving pointer. About the pointer operation, please refer to Figure 24 The data-loading sequence begins by inputting the Serial Data Input command (80h), followed by the four address input cycles and then serial data loading. The Page Program confirm command (10h) starts the programming process. Writing 10h alone without previously entering the serial data will not initiate the programming process. The internal Program Erase Controller automatically executes the algorithms and timings necessary for program and verify, thereby freeing the system controller for other tasks. Once the program process starts, the Read Status Register command may be entered, with RE and CE low, to read the status register. The system controller can detect the completion of a program cycle by monitoring the R/B output, or the Status bit (I/O 6) of the Status Register. Only the Read Status command and Reset command are valid while programming is in progress. When the Page Program is complete, the Write Status Bit (I/O 0) may be checked in Figure 15 The internal write verify detects only errors for "1"s that are not successfully programmed to "0"s. The command register remains in Read Status command mode until another valid command is written to the command register. Rev 0.5 / Jul. 2007 12 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 3.3 Block Erase. The Erase operation is done on a block (16K Byte) basis. It consists of an Erase Setup command (60h), a Block address loading and an Erase Confirm Command (D0h). The Erase Confirm command (D0h) following the block address loading initiates the internal erasing process. This two-step sequence of setup followed by execution command ensures that memory contents are not accidentally erased due to external noise conditions. The block address loading is accomplished three cycles. Only block addresses (A14 to A25 , highest address depending on the device density) are needed while A9 to A13 is ignored. At the rising edge of WE after the erase confirm command input, the internal Program Erase Controller handles erase and erase-verify. When the erase operation is completed, the Write Status Bit (I/O 0) may be checked. Figure 17 details the sequence. 3.4 Copy-Back Program. The copy-back program is provided to quickly and efficiently rewrite data stored in one page within the plane to another page within the same plane without using an external memory. Since the time-consuming sequential reading and its reloading cycles are removed, the system performance is improved. The benefit is especially obvious when a portion of a block is updated and the rest of the block also need to be copied to the newly assigned free block. The operation for performing a copy-back program is a sequential execution of page-read without burstreading cycle and copying-program with the address of destination page. A normal read operation with "00h" command and the address of the source page moves the whole 528byte data into the internal buffer. As soon as the device returns to Ready state, Page-Copy Data-input command (8Ah) with the address cycles of destination page followed may be written. The Program Confirm command (10h) is not needed to actually begin the programming operation. For backward-compatibility, issuing Program Confirm command during copy-back does not affect correct device operation. Copy-Back Program operation is allowed only within the same memory plane. Once the Copy-Back Program is finished, any additional partial page programming into the copied pages is prohibited before erase. Plane address must be the same between source and target page. "When there is a program-failure at Copy-Back operation, error is reported by pass/fail status. But, if Copy-Back operations are accumulated over time, bit error due to charge loss is not checked by external error detection/correction scheme. For this reason, two bit error correction is recommended for the use of Copy-Back operation." Figure 16 shows the command sequence for the copy-back operation. The Copy Back Program operation requires three steps: 1. The source page must be read using the Read A command (one bus write cycle to setup the command and then 4 bus write cycles to input the source page address). This operation copies all 2KBytes from the page into the Page Buffer. 2. When the device returns to the ready state (Ready/Busy High), the second bus write cycle of the command is given with the 4bus cycles to input the target page address. The value for A25 from second to the last page address must be same as the value given to A25 in first address. 3. Then the confirm command is issued to start the P/E/R Controller. Rev 0.5 / Jul. 2007 13 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 3.5 Read Status Register. The device contains a Status Register which may be read to find out whether read, program or erase operatio is completed, and whether the read, program or erase operation is completed successfully. After writing 70h command to the command register, a read cycle outputs the content of the Status Register to the I/O pins on the falling edge of CE or RE, whichever occurs last. This two-line control allows the system to poll the progress of each device in multiple memory connections even when R/B pins are common-wired. RE or CE does not need to be toggled for updated status. Refer to Table 14 for specific Status Register definitions. The command register remains in Status Read mode until further commands are issued to it. Therefore, if the status register is read during a random read cycle, a read command (00h or 50h) should be given before sequential page read cycle. 3.6 Read ID. The device contains a product identification mode, initiated by writing 90h to the command register, followed by an address input of 00h. Four read cycles sequentially output the 1st cycle (ADh), and 2nd cycle (the device code) and 3rd cycle ID, 4th cycle ID, respectively. The command register remains in Read ID mode until further commands are issued to it. Figure 18 shows the operation sequence, while Tables 16 explain the byte meaning. 3.7 Reset. The device offers a reset feature, executed by writing FFh to the command register. When the device is in Busy state during random read, program or erase mode, the reset operation will abort these operations. The contents of memory cells being altered are no longer valid, as the data will be partially programmed or erased. The command register is cleared to wait for the next command, and the Status Register is cleared to value C0h when WP is high. Refer to table 14 for device status after reset operation. If the device is already in reset state a new reset command will not be accepted by the command register. The R/B pin transitions to low for tRST after the Reset command is written. Refer to Figure 21 below. Rev 0.5 / Jul. 2007 14 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 4. OTHER FEATURES 4.1 Data Protection for Power on/off Sequence The device is designed to offer protection from any involuntary program/erase during power-transitions. An internal voltage detector disables all functions whenever Vcc is below about 2.0V(3.0V device). WP pin provides hardware protection and is recommended to be kept at VIL during power-up and power-down. A recovery time of minimum 10us is required before internal circuit gets ready for any command sequences as shown in Figure 22. The two-step command sequence for program/erase provides additional software protection. 4.2 Ready/Busy. The device has a Ready/Busy output that provides method of indicating the completion of a page program, erase, copy-back and random read completion. The R/B pin is normally high and goes to low when the device is busy (after a reset, read, program, erase operation). It returns to high when the internal controller has finished the operation. The pin is an open-drain driver thereby allowing two or more R/B outputs to be Or-tied. Because pull-up resistor value is related to tr(R/B) and current drain during busy (Ibusy), an appropriate value can be obtained with the following reference chart in Figure 23. Its value can be determined by the following guidance. Rev 0.5 / Jul. 2007 15 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Parameter Symbol Min Valid Block Number NVB 4016 Typ Max Unit 4096 Blocks Table 7: Valid Blocks Number NOTE: 1. The 1st block is guaranteed to be a valid block up to 1K cycles with ECC. (1bit/528bytes) Symbol Parameter Value 3.3V Unit Ambient Operating Temperature (Temperature Range Option 1) 0 to 70 Ambient Operating Temperature (Industrial Temperature Range) -40 to 85 TBIAS Temperature Under Bias -50 to 125 TSTG Storage Temperature -65 to 150 V VIO(2) Input or Output Voltage -0.6 to 4.6 V Supply Voltage -0.6 to 4.6 V TA Vcc Table 8: Absolute maximum ratings NOTE: 1. Except for the rating "Operating Temperature Range", stresses above those listed in the Table "Absolute Maximum Ratings" may cause permanent damage to the device. These are stress ratings only and operation of the device at these or any other conditions above those indicated in the Operating sections of this specification is not implied. Exposure to Absolute Maximum Rating conditions for extended periods may affect device reliability. 2. Minimum Voltage may undershoot to -2V during transition and for less than 20ns during transitions. Rev 0.5 / Jul. 2007 16 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash $a$ $''5(66 5(*,67(5 &2817(5 352*5$0 (5$6( &21752//(5 +9*(1(5$7,21 $/( &/( :( &( :3 5( ; 0ELW 0ELW 1$1')ODVK 0(025<$55$< ' ( & 2 ' ( 5 &200$1' ,17(5)$&( /2*,& 3$*(%8))(5 &200$1' 5(*,67(5 <'(&2'(5 '$7$ 5(*,67(5 %8))(56 ,2 Figure 5: Block Diagram Rev 0.5 / Jul. 2007 17 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Parameter Symbol Test Conditions Sequential Read ICC1 Program Erase 3.3Volt Unit Min Typ Max tRC=30ns CE=VIL, IOUT=0mA - 15 30 mA ICC2 - - 15 30 mA ICC3 - - 15 30 mA Stand-by Current (TTL) ICC4 CE=VIH, WP=0V/Vcc - - 1 mA Stand-by Current (CMOS) ICC5 CE=Vcc-0.2, WP=0V/Vcc - 10 50 uA Input Leakage Current ILI VIN=0 to Vcc (max) - - 10 uA Output Leakage Current ILO VOUT =0 to Vcc (max) - - 10 uA Input High Voltage VIH - Vccx0.8 - Vcc+0.3 V Input Low Voltage VIL - -0.3 - Vccx0.2 V Output High Voltage Level VOH IOH=-400uA 2.4 - - V Output Low Voltage Leve VOL IOL=2.1mA - 0.4 V Output Low Current (R/B) IOL (R/B) VOL=0.4V 8 - mA Operating Current 10 Table 9: DC and Operating Characteristics Value Parameter 3.3Volt Input Pulse Levels 0V to Vcc Input Rise and Fall Times 5ns Input and Output Timing Levels Vcc / 2 Output Load (2.7V - 3.6V) 1 TTL GATE and CL=50pF Table 10: AC Conditions Rev 0.5 / Jul. 2007 18 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Item Symbol Test Condition Min Max Unit Input / Output Capacitance CI/O VIL=0V - 10 pF Input Capacitance CIN VIN=0V - 10 pF Table 11: Pin Capacitance (TA=25C, F=1.0MHz) Parameter Symbol Min Typ Max Unit tPROG - 200 700 us Main Array NOP - - 1 Cycles Spare Array NOP - - 2 Cycles tBERS - 2 3 ms Program Time Number of partial Program Cycles in the same page Block Erase Time Table 12: Program / Erase Characteristics Rev 0.5 / Jul. 2007 19 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Parameter Symbol 3.3Volt Min Max Unit CLE Setup time tCLS 15 ns CLE Hold time tCLH 5 ns CE setup time tCS 20 ns CE hold time tCH 5 ns WE pulse width tWP 15 ns ALE setup time tALS 15 ns ALE hold time tALH 5 ns Data setup time tDS 15 ns Data hold time tDH 5 ns Write Cycle time tWC 30 ns WE High hold time tWH 10 ns Data Transfer from Cell to register 12 tR us ALE to RE Delay tAR 10 ns CLE to RE Delay tCLR 10 ns Ready to RE Low tRR 20 ns RE Pulse Width tRP 15 ns WE High to Busy tWB Read Cycle Time tRC RE Access Time tREA 18 ns RE High to Output High Z tRHZ 50 ns CE High to Output High Z tCHZ 50 ns RE or CE high to Output hold tOH 10 ns RE High Hold Time tREH 10 ns tIR 0 ns Output High Z to RE low CE Access Time tCEA WE High to RE low tWHR 100 30 ns ns 25 60 ns ns Last RE High to busy (at sequential read) tRB 100 ns CE High to Ready (in case of interception by CE at read) tCRY 60+tr(R/B#)(4) ns CE High Hold Time (at the last serial read)(3) tCEH Device Resetting Time (Read / Program / Erase) tRST Write Protection time (5) tWW 100 ns 5/10/500(1,2) 100 us ns Table 13: AC Timing Characteristics NOTE: 1. 2. 3. 4. 5. If Reset Command (FFh) is written at Ready state, the device goes into Busy for maximum 5us The time to Ready depends on the value of the pull-up resistor tied R/B pin.ting time. To break the sequential read cycle, CE must be held for longer time than tCEH. The time to Ready depends on the value of the pull-up resistor tied R/B pin. Program / Erase Enable Operation : WP high to WE High. Program / Erase Disable Operation : WP Low to WE High. Rev 0.5 / Jul. 2007 20 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash IO Pagae Program Block Erase Read Cache Read 0 Pass / Fail Pass / Fail NA Pass: `0' Fail: `1' 1 NA NA NA Pass: `0' Fail: `1' (Only for Cache Program, else Don't care) 2 NA NA NA - 3 NA NA NA - 4 NA NA NA - 5 Ready/Busy Ready/Busy Ready/Busy P/E/R Controller Bit Active: `0' Idle: `1' 6 Ready/Busy Ready/Busy Ready/Busy Ready/Busy Busy: `0' Ready': `1' 7 Write Protect Write Protect Write Protect CODING Protected: `0' Not Protected: `1' Table 14: Status Register Coding DEVIIDENTIFIER CYCLE DESCRIPTION 1st Manufacturer Code 2nd Device Identifier Table 15: Device Identifier Coding Part Number Voltage Bus Width 1st cycle (Manufacture Code) 2nd cycle (Device Code) HY27US0812(1/2)B 3.3V x8 ADh 76h HY27US1612(1/2)B 3.3V x16 ADh 56h Table 16: Read ID Data Table Rev 0.5 / Jul. 2007 21 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash &/( W&/6 W&/+ W&6 W&+ &( W:3 :( W$/6 W$/+ $/( W'6 ,2[ W'+ &RPPDQG Figure 6: Command Latch Cycle W&/6 &/( W&6 W:& &( :( W:& W:3 W:3 W:3 W:+ W$/6 W:& W$/+ W:3 W:+ W$/6 W$/+ W:+ W$/6 W$/+ W$/6 W$/+ $/( ,2[ W'+ W'+ W'+ W'6 W'6 &RO$GG &RO$GG W'6 5RZ$GG W'+ W'6 5RZ$GG Figure 7: Address Latch Cycle Rev 0.5 / Jul. 2007 22 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash W&/+ &/( W&+ &( W:& $/( W$/6 W:3 W:3 :( W:3 W:+ W'6 ,2[ W'+ W'6 ',1 W'+ W'6 ',1 W'+ ',1ILQDO Figure 8. Input Data Latch Cycle tCEA CE tREA tREH tRP tCHZ* tREA tREA tOH RE tRHZ tRHZ* tOH I/Ox Dout tRR Dout Dout tRC R/B Notes : Transition is measured 200mV from steady state voltage with load. This parameter is sampled and not 100% tested. Figure 9: Sequential Out Cycle after Read (CLE=L, WE=H, ALE=L) Rev 0.5 / Jul. 2007 23 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash tCLR CLE t CLS tCLH tCS CE tCH tWP WE tCEA t2H tCHZ tWHR RE tDH tDS I/Ox t2H tREA tIR tRH= Status Output 70h Figure 10: Status Read Cycle &/( W&(+ &( W&+= W:& :( W:% W&5< W$5 $/( W5+= W5 W5& 5( W53 ,2[ KRUK &RO$GG &ROXPQ $GGUHVV 5% 5RZ$GG 5RZ$GG 5RZ$GG 'RXW1 'RXW1 'RXW1 'RXW W5% 3DJH 5RZ $GGUHVV %XV\ Figure 11: Read1 Operation (Read One Page) Rev 0.5 / Jul. 2007 24 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash &/( &( :( W:% W&+= W$5 $/( W5 W5& 5( W55 ,2[ KRUK &RO$GG 5RZ$GG 5RZ$GG 5RZ$GG &RO$GG 'RXW1 'RXW1 'RXW1 5RZ$GG 5% %XV\ Figure 12: Read1 Operation intercepted by CE &/( &( :( $/( 5( ,2[ K 'RXW 1 &RO$GG 5RZ$GG 5RZ$GG 5RZ$GG 'RXW 1 'RXW 'RXW 5HDG\ 5% %XV\ %XV\ 0 0 1 2XWSXW 2XWSXW Figure 13: Read2 Operation (Sequential Row Read) Rev 0.5 / Jul. 2007 25 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash &/( &( :( $/( 5( ,2[ K 'RXW 1 &RO$GG 5RZ$GG 5RZ$GG 5RZ$GG 'RXW 1 'RXW 'RXW 'RXW 'RXW 5HDG\ 5% %XV\ %XV\ 0 0 2XWSXW 1 2XWSXW Figure 14: Sequential Row Read Operation Within a Block &/( &( W:& W:& W:& :( W:% W352* $/( 5( ,2[ K 6HULDO'DWD ,QSXW&RPPDQG 5% &RO$GG 5RZ$GG 5RZ$GG 5RZ$GG &ROXPQ $GGUHVV 5RZ$GGUHVV 'LQ 1 'LQ 0 [XSWR%\WH [XSWS:RUG 6HULDO,QSXW K 3URJUDP &RPPDQG K ,2R 5HDG6WDWXV &RPPDQG ,2R 6XFFHVVIXO3URJUDP ,2R (UURULQ3URJUDP Figure 15: Page Program Operation Rev 0.5 / Jul. 2007 26 Rev 0.5 / Jul. 2007 5% ,2[ 5( $/( :( &( &/( K W:& &ROPQ $GGUHVV 5RZ$GGUHVV &RO$GG 5RZ$GG 5RZ$GG 5RZ$GG W:% %XV\ W5 &ROPQ $GGUHVV 5RZ$GGUHVV ,2 ,2 (UURULQ3URJUDP 5HDG6WDWXV &RPPDQG K %XV\ ,2 6XFFHVVIXO3URJUDP KZULWHF\FOHQRPRUH &RO$GG 5RZ$GG 5RZ$GG 5RZ$GG &RS\%DFN'DWD ,QSXW&RPPDQG $K W352* HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Figure 16 : Copy Back Program 27 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash &/( &( W:& :( W:% W%(56 $/( 5( ,2[ K 5RZ$GG 5RZ$GG 5RZ$GG 'K K ,2 5RZ$GGUHVV 5% %86< $XWR%ORFN(UDVH6HWXS&RPPDQG 5HDG6WDWXV &RPPDQG (UDVH&RPPDQG ,2 6XFFHVVIXO(UDVH ,2 (UURULQ(UDVH Figure 17: Block Erase Operation (Erase One Block) CLE CE WE tAR ALE RE tREA 90h 00h Read ID Command Address 1 cycle I/O x ADh K Maker Code Device Code Figure 18: Read ID Operation Rev 0.5 / Jul. 2007 28 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash System Interface Using CE don't care To simplify system interface, CE may be deasserted during data loading or sequential data-reading as shown below. So, it is possible to connect NAND Flash to a microporcessor. The only function that was removed from standard NAND Flash to make CE don't care read operation was disabling of the automatic sequential read function. (HY27US(08/16)122B) &/( &(GRQWFDUH &( :( $/( ,2[ K 6WDUW$GG &\FOH 'DWD,QSXW 'DWD,QSXW K Figure 19: Program Operation with CE don't-care. &/( ,IVHTXHQWLDOURZUHDGHQDEOHG &(PXVWEHKHOGORZGXULQJW5 &(GRQWFDUH &( 5( $/( 5% W5 :( ,2[ K 6WDUW$GG &\FOH K 'DWD2XWSXW VHTXHQWLDO Figure 20: Read Operation with CE don't-care. Rev 0.5 / Jul. 2007 29 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash :( $/( &/( 5( ,2 ))K W567 5% Figure 21: Reset Operation 9FF 97+ W :3 :( XV Figure 22: Power On and Data Protection Timing VTH = 2.5 Volt for 3.3 Volt Supply devices Rev 0.5 / Jul. 2007 30 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash 5S LEXV\ 9FF 5HDG\ 9FF 5% RSHQGUDLQRXWSXW 92+ 92/ 992+9 92/ %XV\ WI WU *1' 'HYLFH )LJ5SYVWUWI 5SYVLEXV\ #9FF 97D &&/ S) LEXV\ Q Q Q P P WI N N N N LEXV\>$@ WUWI>V@ P 5S RKP 5SYDOXHJXLGHQFH 5S PLQ 9FF 0D[ 92/ 0D[ 9 ,2/,/ P$,/ ZKHUH,/LVWKHVXPRIWKHLQSXWFXUUQWVRIDOOGHYLFHVWLHGWRWKH5%SLQ 5S PD[ LVGHWHUPLQHGE\PD[LPXPSHUPLVVLEOHOLPLWRIWU Figure 23: Ready/Busy Pin electrical specifications Rev 0.5 / Jul. 2007 31 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash ['HYLFHV ['HYLFHV $UHD$ K $UHD% K $UHD& K $UHD$ K $UHD& K %\WHV %\WHV %\WHV %\WHV %\WHV $ % & $ & 3DJH%XIIHU 3DJH%XIIHU 3RLQWHU KK 3RLQWHU KKK Figure 24: Pointer operations $5($$ ,2 K K $GGUHVV ,QSXWV 'DWD,QSXW K K K $GGUHVV ,QSXWV 'DWD,QSXW K $UHDV$%&FDQEHSURJUDPPHGGHSHQGLQJRQKRZPXFKGDWDLVLQSXW6XEVHTXHQWKFRPPDQGVFDQEHRPLWWHG $5($% ,2 K K $GGUHVV ,QSXWV 'DWD,QSXW K K K $GGUHVV ,QSXWV 'DWD,QSXW K $UHDV%&FDQEHSURJUDPPHGGHSHQGLQJRQKRZPXFKGDWDLVLQSXW7KHKFRPPDQGPXVWEHUHLVVXHGEHIRUHHDFKSURJUDP $5($& ,2 K K $GGUHVV ,QSXWV 'DWD,QSXW K K K $GGUHVV ,QSXWV 'DWD,QSXW K 2QO\$UHDV&FDQEHSURJUDPPHG6XEVHTXHQWKFRPPDQGFDQEHRPLWWHG Figure 25: Pointer Operations for porgramming Rev 0.5 / Jul. 2007 32 HY27US(08/16)12(1/2)B Series 512Mbit (64Mx8bit / 32Mx16bit) NAND Flash Bad Block Management Devices with Bad Blocks have the same quality level and the same AC and DC characteristics as devices where all the blocks are valid. A Bad Block does not affect the performance of valid blocks because it is isolated from the bit line and common source line by a select transistor. The devices are supplied with all the locations inside valid blocks erased(FFh). The Bad Block Information is written prior to shipping. Any block where the 6th Byte/ 3rd Word in the spare area of the 1st or 2nd page (if the 1st page is Bad) does not contain FFh is a Bad Block. The Bad Block Information must be read before any erase is attempted as the Bad Block Information may be erased. For the system to be able to recognize the Bad Blocks based on the original information it is recommended to create a Bad Block table following the flowchart shown in Figure 26. The 1st block, which is placed on 00h block address is guaranteed to be a valid block. Block Replacement Over the lifetime of the device additional Bad Blocks may develop. In this case the block has to be replaced by copying the data to a valid block. These additional Bad Blocks can be identified as attempts to program or erase them will give errors in the Status Register. As the failure of a page program operation does not affect the data in other pages in the same block, the block can be replaced by re-programming the current data and copying the rest of the replaced block to an available valid block. The Copy Back Program command can be used to copy the data to a valid block. See the "Copy Back Program" section for more details. Refer to Table 18 for the recommended procedure to follow if an error occurs during an operation. Operation Recommended Procedure Erase Block Replacement Program Block Replacement Read ECC (with 1bit/528byte) Table 18: Block Failure 67$57 %ORFN$GGUHVV %ORFN ,QFUHPHQW %ORFN$GGUHVV 'DWD ))K" 1R 8SGDWH %DG%ORFNWDEOH