This document is a general product descriptio n and is subject to change wit hout noti ce. Hyni x does no t assume an y respon sibilit y for
use of circuits described. No patent licenses are implied.
Rev 0.4 / Mar. 2007 1
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
2Gb NAND FLASH
HY27UF082G2A
HY27UF162G2A
Rev 0.4 / Mar. 2007 2
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Document Title
2Gbit (256Mx8bit/128Mx16bit) NAND Flash Memory
Revision History
Revision
No. History Draft Date Remark
0.01 Initial Draft. Jan. 24. 2006 Preliminary
0.1 1) Change NOP
2) Correct 5th Read ID
3) Chnage AC Timing Characteristics
May. 18. 2006 Preliminary
0.2 1) Add x16 features. Sep. 07. 2006 Preliminary
0.3
1) Chnage AC Timing Characteristics
2) Add AC Timing Characteristics
- tCOH = 15ns (min)
3) Correct copy back function
4) Delet Preliminary.
Nov. 21. 2006
0.4 1) Delete cache read function in x16 product Mar. 21. 2007
tR tCRRH tRHOH tRLOH
Before 25 50 100 15
After 20 100 15 5
Rev 0.4 / Mar. 2007 3
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) 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
SUPPLY VOLTAGE
- VCC = 2.7 to 3.6V : HY27UFxx2G2A
Memory Cell Array
= (2K+64) Bytes x 64 Pages x 2,048 Blocks
= (1K+32) Words x 64pages x 1,024 Blocks
PAGE SIZE
- x8 device : (2K+64 spare) Bytes
: HY27UF082G2A
- x16 device : (1K+32 spare) Words
: HY27UF162G2A
BLOCK SIZE
- x8 device: (128K + 4K spare) Bytes
- x16 device : (64K + 2K spare) Words
PAGE READ / PROGRAM
- Random access: 25us (max.)
- Sequential access: 30ns (min.)
- Page program time: 200us (typ.)
COPY BACK PROGRAM MODE
- Fast page copy without external buffering
CACHE PROGRAM
- Internal (2048+64) By te buffer to improv e the program
throughput
FAST BLOCK ERASE
- Block erase time: 2ms (Typ.)
STATUS REGISTER
ELECTRONIC SIGNATURE
- 1st cycle: Manufacturer Code
- 2nd cycle: Device Code
- 3rd cycle: Internal chip number, Cell Type, Number of
Simultaneously Programmed Pages.
- 4th cycle: Page size, Block size, Organization, Spare
size
- 5th cycle: Plane Number, Plane Size
CHIP ENABLE DON’T CARE
- Simple interface sith microcontroller
SERIAL NUMBER OPTION
DATA RETENTION
- 100,000 Program/Erase cycles (with 1bit/528byte ECC)
- 10 years Data Retention
PACKAGE
- HY27UF(08/16)2G2A-T(P)
: 48-pin TSOP1(12 x 20 x 1.2 mm)
- HY27UF(08/16)2G2A-T (Lead)
- HY27UF(08/16)2G2A-TP (Lead Free)
- HY27UF082G2A-UP
: 52-ULGA (12 x 17 x 0.65 mm)
- HY27UF082G2A-UP (Lead Free)
Rev 0.4 / Mar. 2007 4
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
1. SUMMARY DESCRIPTION
The Hynix HY27UF(08/16)2G2A series is a 25 6Mx8b it with spa re 16Mx8 bit capacity. The device is offered in 3.3V Vcc
Power Supply.
Its NAND cell provides the most cost-e ff ective solution for the solid state mass stor age mark et. 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 device contains 2048 blocks, composed by 64 pages consisting in two NAND structures of 32 series connected
Flash cells.
A program operation allows to write the 2112-byte page in typical 200us and an erase operation can be performed in
typical 2ms on a 128K-byte(X8 device) block.
Data in the page can be read out at 30ns cycle time 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 diff erent
densities, without any rearrangement of footprint.
Commands, Data and Addresses ar e synchronously introduced using CE, WE, ALE and CLE input pin. The on-chip Pro-
gram/Er ase Cont roller automates all progr am and er ase f unctions including pulse repetiti on, where required, and inter-
nal verification and margin ing of data.
The modify operations can be locked using the WP input pin or using the extended lock block feature described later.
The output pin R/B (open drain buffer) signals the status of the device during each operation. In a system with multi-
ple 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 HY27UF(08/16)2G2A extended reliability of 100K pro-
gram/erase cycles by providing ECC (Error Correcting Code) with real time mapping-out algorithm.
The chip could be offered with the CE don’t care function. This function 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: whe n a page progr am operat ion fails
the data can be directly programmed in another page inside the same arr ay s ection without the time consuming serial
data insertion phase.
The cache program feature allows the data insertion in the cache register while the data register is copied into the
flash array. This pipelined program operation improves the program throughput when long files are written inside the
memory. A cache read feature (x8 ) is also implemented. This feature allows to dramatically improve the read through-
put when consecutive pages have to be streamed out.
The HYNIX HY27UF(08/16)2G2A series is available in 48 - TSOP1 12 x 20 mm, 52-ULGA 12 x 17 mm.
1.1 Product List
PART NUMBER ORIZATION VCC RANGE PACKAGE
HY27UF082G2A x8 2.7V - 3.6 Volt 48TSOP1 / 52-ULGA
HY27UF162G2A x16 48TSOP1
Rev 0.4 / Mar. 2007 5
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
9&&
966
:3
&/(
$/(
5(
:(
&( ,2a,2
,2a,2[2QO\
5%
Figure1: Logic Diagram
IO15 - IO8 Data Inputs / 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 / Bus y
Vcc Power Supply
Vss Ground
NC No Connection
Table 1: Signal Names
Rev 0.4 / Mar. 2007 6
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
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&
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
[
1&
1&
1&
1&
1&
1&
5%
5(
&(
1&
1&
9FF
9VV
1&
1&
&/(
$/(
:(
:3
1&
1&
1&
1&
1&
9VV
,2
,2
,2
,2
,2
,2
,2
,2
1&
1&
9FF
1&
1&
1&
,2
,2
,2
,2
,2
,2
,2
,2
9VV







1$1')ODVK
7623
[
Rev 0.4 / Mar. 2007 7
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
1&
1&
1&
1&
1&
1&
1&
1&
1&
1&
1&
1&
:(
:3 966
,2
,2
,2 ,2
,2
,2
,2
966
,2
5%
1&
1& 1&
1&
1&
1&
1& 1&
1&
966
966
9&&
9&&
1& &/(
$/(
&(
5(
1&
1& 1&
1&
1&
1&
1&
1&
1&
$
%
&
'
(
)
*
+
-
.
/
0
1

Figure 3. 52-ULGA Contactions, x8 Device
(Top view through package)
Rev 0.4 / Mar. 2007 8
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
1.2 PIN DESCRIPTION
Pin Name Description
IO0-IO7
IO8-IO15(1)
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.
CLE COMMAND LATCH ENABLE
This input activates the latching of the IO inputs inside the Command Register on the Rising edge of
Wri te Enable (WE).
ALE ADDRESS LATCH ENABLE
This input activates the latching of the IO inputs inside the Address Register on the Rising edge of
Wri te Enable (WE).
CE CHIP ENABLE
This input cont r ols the sele c tion of the device. When the d evice is busy CE low does not deselect the
memory.
WE WRITE ENABLE
This input acts as clock to latch Command, Address and Data. The IO inputs are latched on the rise
edge of WE.
RE 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 theocolumn address counter by one.
WP WRITE PROTECT
The WP pin, when Low, provides an Ha rdwar e protection against undesired modif y (progr am / er ase)
operations.
R/B READY BUSY
The Ready/Busy output is an Open Drain pin that signals the state of the memory.
VCC SUPPLY VOLTAGE
The VCC supplies the power for all the oper a tions (Read, Write, Erase).
VSS GROUND
NC 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 s upply. The PCB tr ack widths must be sufficient to carry the currents required
during program and erase operations.
3. An internal voltage detector disables all functions whenever VCC is below 2.0V (3.3V version)
version to protect the device from any involuntary program/erase buring power transitions.
Rev 0.4 / Mar. 2007 9
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
IO0 IO1 IO2 IO3 IO4 IO5 IO6 IO7
1st Cycle A0 A1 A2 A3 A4 A5 A6 A7
2nd Cycle A8 A9 A10 A11 L(1) L(1) L(1) L(1)
3rd Cycle A12 A13 A14 A15 A16 A17 A18 A19
4th Cycle A20 A21 A22 A23 A24 A25 A26 A27
5th Cycle A28 L(1) L(1) L(1) L(1) L(1) L(1) L(1)
Table 3: Address Cycle Map(x8)
NOTE:
1. L must be set to Low.
IO0 IO1 IO2 IO3 IO4 IO5 IO6 IO7 IO8-IO15
1st Cycle A0 A1 A2 A3 A4 A5 A6 A7 L(1)
2nd Cycle A8 A9 A10 L(1) L(1) L(1) L(1) L(1) L(1)
3rd Cycle A11 A12 A13 A14 A15 A16 A17 A18 L(1)
4th Cycle A19 A20 A21 A22 A23 A24 A25 A26 L(1)
5th Cycle A27 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 Acceptable command
during busy
READ 1 00h 30h - -
READ FOR COPY-BACK 00h 35h - -
READ ID 90h - - -
RESET FFh - - - Yes
PAGE PROGRAM 80h 10h - -
COPY BACK PGM 85h 10h - -
BLOCK ERASE 60h D0h - -
READ STATUS REGISTER 70h - - - Yes
CACHE PROGRAM 80h 15h - -
RANDOM DATA INPUT 85h - - -
RAMDOM DATA OUTPUT 05h E0h - -
CACHE READ START (1) 00h 31h - -
CACHE READ EXIT (1) 34h - - -
Table 5: Command Set
NOTE:
1. Only for x8 product
Rev 0.4 / Mar. 2007 10
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
CLE ALE CE WE RE WP MODE
H L L Rising H X Read Mode Command Input
L H L Rising H X Address Input(5 cycles)
H L L Rising H H Write Mode Command Input
L H L Rising H H Address Input(5 cycles)
LLLRisingHHData Input
LL
L(1) H Falling X Sequential Read and Data Output
L L L H H X During Read (Busy)
XXXXXHDuring Program (Busy)
XXXXXHDuring Erase (Busy)
XXXXXLWrite Protect
XXHXX0V/VccStand By
Table 6: Mode Selection
NOTE:
1. With the CE high during latency time does not stop the read operation
Rev 0.4 / Mar. 2007 11
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) 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 le ss than 5 ns o n Chip Enable, W rite Enab le and R ead Ena ble are ig nore d by the memo ry 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 modif y ope r ation (wr ite/er ase) the Write Protect pin must
be high. See figure 5 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 op er ation allows the ins ertion of the memory addr ess. To insert the 29 addresses needed to access
the 2Gbit 5 clock cycles (x8 version) are needed. Addresses are accepted with Chip Enable low, Address Latch Enable
High, Command Latch Enable low and R ead Enab le High and latched on the rising edge of Write Enable. Moreov er f o r
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. 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
7 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 8,9,1 0,11 and table 13 f or 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 altere d. Write Protect pin is not latched by Write Enable to ensure the pro-
tection 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.4 / Mar. 2007 12
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
3. DEVICE OPERATION
3.1 Page Read.
Upon initial devi ce power up , the device de fault s to R ead mode. This oper ati on is also initi ated by writ ing 00h and 30h
to the command register along with five addr ess cycles. In two consecutive r ead operations, the second one does need
00h command, which five address cycles and 30h command initiates that operation. Second read operation always
requires setup command if first read operation was executed using also random data out command.
Two types of operations are available: random read. The random read mode is enabled when the page address is
changed. The 2112bytes (X8 device) or 1056words (x16 device) of data within the selected page are tr ansferred to the
data registers in less than 25us(tR). The system contr oller may dete ct the completion of this data transfer (tR) by ana-
lyzing the output of R/B pin. Once the data in a page is loaded into the data registers, they may be read out in 30ns
cycle time (3.3V version) by sequentially pulsing RE. The repetitive high to low transitions of the RE clock make the
device output the data starting from the selected column address up to the last column address.
The device may output random data in a page instead of the consecutive sequential data by writing random
data output command. The column address of next data, which is going to be out, may be changed to the address
which follows random data output command.
Random data output can be operated multiple times regardless of how many times it is done in a page.
Random data output is not available in cache read (x8).
3.2 Page Program.
The device is progr ammed basically by pa ge, but it does allow multiple par tial page pr ogr amming of a word or consec-
utive bytes up to 2112 (X8 device) or 1056 (x16 device), in a single page program cycle.
The number of consecutive partial page programming operation within the same page without an intervening erase
operation must not exceed 4 times for main array (X8 device:1time/512byte, x16 device:1time/256word) and 4 times
for spare array (X8 device:1time/16byte, x16 device:1tme/8word).
The addressing should be done in sequential order in a block. A page program cycle consists of a serial data loading
period in which up to 2112bytes (X8 device) or 1056words (x16 device) of data may be loaded into the data register,
followed by a non-volatile programming period where the loaded data is programmed into the appropriate cell.
The serial data loading period begins by inputting the Serial Data Input command (80h), followed by the five cycle
address inputs and then serial data. The words other than those to be programmed do not need to be loaded. The
device supports random data input in a page. The column address of next data, which will be entered, may be
changed to the address which follows random data input command (85h). Random data input may be opera ted multi-
ple times regardless of how many times it is done in a page.
The Page Program confirm command (10h) initiates the programming process. Writing 10h alone without previously
entering the serial data will not initiate the programming process. The P/E/R controller automatically executes the
algorithms and timings necessary for program and verify, thereby freeing the system controller for other tasks. Once
the progr am process starts, the Read Status R egister command may be entered to read the status re gister. 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 Reg ister. Only the Read Status command and Reset comm and are valid while pr ogramming is in progress. When
the Page Program is complete, the Write Status Bit (I/O 0) may be checked. The internal write verify detects only
errors for "1"s that are not successfully progr ammed to "0"s. The command register remains in Read Status command
mode until another valid command is written to the command register. Figure 13 details the sequence.
Rev 0.4 / Mar. 2007 13
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
3.3 Block Erase.
The Erase operation is done on a block basis. Block address loading is accomplished in two cycles initiated by an Erase
Setup command (60h). Only addr ess A18 to A28 (X8) or A17 to A27 (x16) is valid while A12 to A17 (X8) or A11 to A16
(x16) are ignored. 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 acci-
dentally erased due to external noise conditions. At the rising edge of WE after the erase confirm command input, the
P/E/R controller handles erase and erase-verify.
Once the erase process starts, the Read Status Register command may be entered to read the status register.
The system controller can detect the completion of an erase 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 erasing is in progress. 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 configured to quickly and efficiently rewrite data stored in one page without utilizing an
external memory. Since the time-consuming cycles of serial access and re-loading cycles are removed, the system per-
formance 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 serial access and copying-p rogram with the address of destination page.
A read operation with "35h" command and the address of the source page moves the whole 2112byte (X8 device) or
1056word (x16 device) data into the internal data buffer. As soon as the device returns to Ready state, Copy Back com-
mand (85h) with the address cycles of destination page may be written. The Program Confirm command (10h) is
required to actually begin the programming operation. Data input cycle for modifying a portion or multiple distant por-
tions of the source page is allowed as shown in Figure 15.
"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 15 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
5 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 5bus cycles to input the target page address. The value for A28 from second to the last page address
must be same as the value given to A28 in first address.
3. Then the confirm command is issued to start the P/E/R Controller.
Note:
1. Copy-Back Program operation is allowed only within the same memory plane.
2. On the same plane, It’s prohibited to operate copy-back program from an odd address page (source page) to an
even address page (target page) or from an ev en address page (source page) to an odd address page (target page).
Therefore, the copy-back program is permitted just between odd address pages or even address pages.
Rev 0.4 / Mar. 2007 14
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
3.5 Read Status Register.
The device contains a Status Register which ma y be read to find out whether rea d, progra m or erase oper ation is com-
pleted, and whether the progr am or er as e oper a tion is c omplet ed successf u lly. After writ ing 70h c ommand to t he com-
mand 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.
Re fer to table 14 fo r specific Status R egis ter definitions . The command register remains in Status R ead mode until fur-
ther commands are iss ued to it. Therefore, if the status register is read during a r andom read cycle, the read command
(00h) should be given before starting read cycles. See figure 9 for details of the Read Status operation.
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. Five read cycles sequentially output the manufacturer code (ADh), and the device code and 3rd
cycle ID, 4th cycle ID, 5th cycle ID respectively. The command register remains in Read ID mode until further com-
mands 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 re gis ter. When the device is in Busy state
during random read, pr ogr am or er ase mode, the res et 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 E0h 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 com-
mand is written. Re fer to figure 23.
Rev 0.4 / Mar. 2007 15
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
3.8 Cache program
Cache Program is an extension of Page Program, which is executed with 2112byte (X8 device) or 1056word (x16)
data registers, and is available only within a block. Since the device has 1 page of cache memory, serial data input
may be executed while
data stored in data register are programmed into memory cell. After writing the first set of data up to 2112byte (X8
device) or 1056word (x16 device) into the selected cache r egisters, Cache Pr ogr am command (15h) instead of actual
Page Program (10h) is
input to make cache registers free and to start internal program operation. To transfer data from cache registers to
data registers, the device remains in Busy state for a short period of time (tCBSY) and has its cache registers ready
for the next data-input while the internal programming gets started with the data loaded into data registers. Read
Status command (70h) may be issued to find out when cache registers become ready by polling the Cache-Busy sta-
tus bit (I/ O6). Pass/fail status of only the previous page is available upon the return to Ready state. When the next
set of data is input with the Cache Program command, tCBSY is affected by the progress of pending internal program-
ming. The programming of the cache registers is initiated only when the pending program cycle is finished and the
data registers are av ailable for the tr ansfer of data from ca che registers. The status bit (I/O5 ) for internal R eady/Busy
may be polled to identify the completion of internal programming.
If the system monitors the progress of progr amming only with R/B, the last page of the target progr amming sequence
must be programmed with actual Page Program command (10h). If the Cache Program command (15h) is used
instead, status bit (I/O5) must be polled to find out when the last programming is actually finished before starting
other operations such as read. Pass/fail status is available in two steps. I/O 1 returns with the status of the previous
page upon Ready or I/O6 status bit changing to "1", and later I/O 0 with the status of current page upon true Ready
(returning fro m intern al pr ogramming) or I/O 5 status bit changing to "1". I/O 1 may be read together when I/O 0 is
checked. See figure 16 for more details.
NO TE : Since progr amming the last page does not employ caching, the progr am time has to be that of P age Progr am.
However, if the previous program cycle with the cache data has not finished, the actual program cycle of the
last page is initiated only after completion of the previous cycle, which can be expressed as the following
formula.
tPROG= Program time for the last page+ Program time for the ( last -1 ) page
- (Program command cycle time + Last page data loading time)
The value for A28 from second to the last page address must be same as the value given to A28 in first address.
Rev 0.4 / Mar. 2007 16
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
3.9 Cache Read (x8)
Cache read operation allows automatic download of consecut ive pages, up to the whole device. Immediately after 1st
latency end, while user can start reading out data, device internally starts reading following page.
Start address of 1st page is at page start (A<10:0>=00h), aft er 1st latency time (tr) , automatic data download wi ll
be uninterrupted. In fact latency time is 25us, while download of a page require at least 100us for x8 device. Cache
read operation command is like standard read, except for confirm code (30h for standard read, 31h for cache read)
user can check operation status using :
- R/B ( “0” means latency ongoing, download not possible, “1” means download of n page possible, even if device
internally is active on n+1 page)
- Status register (SR<6> behave like R/B, SR<5 > is “0” w hen devic e is int ernally reading a nd “1” when devi ce is idl e)
To exit cache read operation a cache read exit command (34h) must be issued. this command can be given any time
(both device idle and reading).
If device is active (SR<5>=0) it will go idle within 5us, while if it is not active, device itself will go busy for a time
shorter then tRBSY before becoming again idle and ready to accept any further commands.
If user arrives reading last byte/word of the memory array, then has to stop by giving a cache read exit command.
Random data output is not available in cache read.
Cache read operation must be done only block by block if system needs to avoid reading also from invalid blocks.
Rev 0.4 / Mar. 2007 17
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
4. OTHER FEATURES
4.1 Data Protection & 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.3V version). 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 24. The two-step com-
mand sequence for program/erase provides additional software protection.
If the power is dropped during the ready read/write/erase operation, Power protection function may not guaranteed
the data. Power protection function is only available during the power on/off sequence.
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, cache progr am 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 P/E/R 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 (Figure 25). Its value can be determined by the following guidance.
Rev 0.4 / Mar. 2007 18
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Parameter Symbol Min Typ Max Unit
Valid Block Number NVB 2008 2048 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 Unit
3.3V
TAAmbient 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
VIO(2) Input or Output Voltage -0.6 to 4.6 V
Vcc Supply Voltage -0.6 to 4.6 V
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 the se or an y other conditions abov e those indicat ed in t he Ope rat ing se ctions o f this specifi cation 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.4 / Mar. 2007 19
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
$''5(66
5(*,67(5
&2817(5
352*5$0
(5$6(
&21752//(5
+9*(1(5$7,21
&200$1'
,17(5)$&(
/2*,&
&200$1'
5(*,67(5
'$7$
5(*,67(5
,2
5(
%8))(56
<'(&2'(5
3$*(%8))(5
;
'
(
&
2
'
(
5
0ELW0ELW
1$1')ODVK
0(025<$55$<
:3
&(
:(
&/(
$/(
$a$
Figure 4: Block Diagram
Rev 0.4 / Mar. 2007 20
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Parameter Symbol Test Conditions 3.3Volt Unit
Min Typ Max
Operating
Current
Sequential
Read ICC1 tRC=30ns
CE=VIL,
IOUT=0mA -1530mA
Program ICC2 - - 15 30 mA
Erase ICC3 - - 15 30 mA
Stand-by Current (TTL) ICC4 CE=VIH,
WP=0V/Vcc -1mA
Stand-by Current (CMOS) ICC5 CE=Vcc-0.2,
WP=0V/Vcc -1050uA
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 - 0.2xVcc 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 10 - mA
Table 9: DC and Operating Characteristics
Parameter Value
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.4 / Mar. 2007 21
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) 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
Program Time tPROG - 200 700 us
Dummy Busy Time for Cache Program tCBSY - 3 700 us
Number of partial Program Cycles in the same page Main Array NOP - - 4 Cycles
Spare Array NOP - - 4 Cycles
Block Erase Time tBERS -23ms
Table 12: Program / Erase Characteristics
Rev 0.4 / Mar. 2007 22
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Parameter Symbol 3.3Volt Unit
Min Max
CLE Setup time tCLS 15 ns
CLE Hold time tCLH 5 ns
CE setup time tCS 25 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
Address t o Data Loading time tADL(2) 100 ns
Data Transfer from Cell to register tR 20 us
ALE to RE Delay tAR 15 ns
CLE to RE Delay tCLR 15 ns
Ready t o RE Low tRR 20 ns
RE Pulse Width tRP 15 ns
WE High to Busy tWB 100 ns
Read Cycle Time tRC 30 ns
RE Access Time tREA 25 ns
RE High to Output High Z tRHZ 50 ns
CE High to Output High Z tCHZ 50 ns
Cache Read RE high tCRRH 100 ns
RE High to Output hold tRHOH 15 ns
RE Low to Output hold tRLOH 5 ns
CE High to Output Hold tCOH 15 ns
RE High Hold Time tREH 10 ns
Output High Z to RE low tIR 0 ns
CE Access Time tCEA 30 ns
WE High to RE lo w tWHR 60 ns
Device Resetting Time (Read / Program / Erase) tRST 5/10/500(1) us
Write Protection time tWW(3) 100 ns
Table 13: AC Timing Characteristics
NOTE:
1. If Reset Command (FFh) is written at Re ady state, the device go es into Busy for maximum 5us
2. tADL is the time from the WE rising edge of final address cycle to the WE rising of first data cycle.
3. Program / Erase Enable Operation : WP high to WE High.
Program / Erase Disable Operation : WP Low to WE High.
Rev 0.4 / Mar. 2007 23
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
IO Pagae
Program Block
Erase Read CODING
0 Pass / Fail Pass / Fail NA Pass: ‘0’ Fail: ‘1’
1 NA NA NA Pass: ‘0’ Fail: ‘1’
2NA NA NA -
3NA NA NA -
4NA NA NA -
5 Ready/Busy Ready/Busy Ready/Busy Active: ‘0’ Idle: ‘1’
6 Ready/Busy Ready/Busy Ready/Busy Busy: ‘0’ Ready’: ‘1’
7 Write Protect Write Protect Write Protect Protected: ‘0’ Not
Protected: ‘1’
Table 14: Status Register Coding
DEVIIDENTIFIER CYCLE DESCRIPTION
1st Manufacturer Code
2nd Device Identifier
3rd Internal chip number, cell Type, Number of Simultaneously Programmed
pages.
4th Page size, spare size, Block size, Organization
5th Plane Number, Plane Size
Table 15: Device Identifier Coding
Part Number Voltage Bus
Width 1st cycle
(Manufacture Code) 2nd cycle
(Device Code) 3rd cycle 4th cycle 5th cycle
HY27UF082G2A 3.3V x8 ADh DAh 80h 1Dh 00h
HY27UF162G2A 3.3V x16 ADh CAh 80h 5Dh 00h
Table 16: Read ID Data Table
Rev 0.4 / Mar. 2007 24
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Description IO7 IO6 IO5 IO4 IO3 IO2 IO1 IO0
Die / Package
1
2
4
Reserved
0 0
0 1
1 0
1 1
String Type
Single Level
2x Multi-level
Reserved
Reservedl
0 0
0 1
1 0
1 1
Number of
Simultaneously
Programmed Pages
1
2
3
4
0 0
0 1
1 0
1 1
Interl eave Program
Between different dice Not Support
Support 0
1
Wri te Cache Not Support
Support 0
1
Table 17: 3rd Byte of Device Idendifier Description
Description IO7 IO6 IO5-4 IO3 IO2 IO1-0
Page Size
(Without Spare Area)
1KB
2KB
4KB
Reserved
0 0
0 1
1 0
1 1
Spare Area Size
(Byte / 512 Byte) 8
16 0
1
Serial Access Time
50ns
30ns
25ns
Reserved
0
0
1
1
0
1
0
1
Block Size (Without
Spare Area)
64KB
128KB
256KB
512KB
0 0
0 1
1 0
1 1
Organization X8
X16 0
1
Table 18: 4th Byte of Device Identifier Description
Rev 0.4 / Mar. 2007 25
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Description IO7 IO6 IO5-4 IO3 IO2 IO1-0
Plane Number
1
2
3
4
0
0
1
1
1
0
0
1
Plane Size
(Without Redundant
Area)
1Gb
2Gb
4Gb
8Gb
Reserved
Reserved
Reserved
Reserved
0
0
0
0
1
1
1
1
0 0
0 1
1 0
1 1
0 0
0 1
1 0
1 1
Reserved 0 0 0
Table 19: 5th Byte of Device Identifier Description
Rev 0.4 / Mar. 2007 26
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Figure 5: Command Latch Cycle
W&/
6
W&6
W:3
&RPPDQG
&/(
&(
:(
$/(
,2[
W'+W'6
W$/6 W$/+
W&/+
W&+
W&/6
W&6
W:3
W:& W:& W:&
W:3 W:3 W:3
W$/6
W:+W:+W:+W:+
W$/+ W$/6W$/6W$/6W$/6
&RO$GG
W$/+ W$/+ W$/+ W$/+
W'+
&RO$GG 5RZ$GG 5RZ$GG 5RZ$GG
W:&
W'+ W'+ W'+ W'+
W'6 W'6 W'6 W'6
W'6
&/(
&(
:(
$/(
,2[
Figure 6: Address Latch Cycle
Rev 0.4 / Mar. 2007 27
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
W:&
W$/6
W&/+
W&+
W:3
W:+
',1 ',1 ',1ILQDO
W'+ W'+ W'+
W'6 W'6 W'6
W:3 W:3
&/(
$/(
&(
,2[
:(
1RWHV',1ILQDOPHDQV
t
CEA
t
REA
t
RP
t
REA
t
RHZ
t
RHZ*
Dout Dout Dout
t
CHZ*
t
OH
t
OH
t
REA
t
REH
t
RC
t
RR
Notes : Transition is measured ±200mV from steady state voltage with load.
This parameter is sampled and not 100% tested.
CE
RE
R/B
I/Ox
Figure 7. Input Data Latch Cycle
Figure 8: Sequential Out Cycle after Read (CLE=L, WE=H, ALE=L)
Rev 0.4 / Mar. 2007 28
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Figure 9: Status Read Cycle
tCLS
tCLR
tCLH
tCS
tCH
tWP
tWHR
tCEA
tDS tREA
tCHZ
tRH=
t2H
t2H
70h Status Output
tDH tIR
CE
WE
I/O
x
CLE
RE
&/(
$/(
&(
,2[
:(
5(
5'
W
:&
W
&/5
W
55
K K
&RO$GG
&ROXPQ$GGUHVV 5RZ$GGUHVV
&RO$GG
5RZ$GG 5RZ$GG 5RZ$GG
%XV\
'RXW1 'RXW1 'RXW0
W
:%
W
$5
W
5
W
5&
W
5+=
Figure 10: Read1 Operation (Read One Page)
Rev 0.4 / Mar. 2007 29
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
W:%
W$5
W&+=
W&2+
W5&
W5
W55
%XV\
K K 'RXW
1'RXW
1 'RXW
1
&RO
$GG &RO
$GG 5RZ
$GG 5RZ
$GG 5RZ
$GG
&ROXPQ$GGUHVV 5RZ$GGUHVV
&/(
&(
:(
$/(
5(
,2[
5%
Figure 11: Read1 Operation intercepted by CE
Rev 0.4 / Mar. 2007 30
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
&/(
$/(
&(
5(
5%
,2[
:(
W&/5
K
&ROXPQ$GGUHVV 5RZ$GGUHVV
%XV\
K K (K
'RXW1 'RXW0
'RXW1 'RXW0
&RO$GG 5RZ$GG 5RZ$GG 5RZ$GG
&RO$GG
&ROXPQ$GGUHVV
&RO$GG &RO$GG
W5 W5&
W:%
W$5
W55
W:+5
W5($
W5+:
Figure 12 : Random Data output
Rev 0.4 / Mar. 2007 31
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Figure 13: Page Program Operation
&/(
$/(
&(
5(
5%
,2[
:(
W:&
K &RO
$GG
6HULDO'DWD
,QSXW&RPPDQG &ROXPQ$GGUHVV 5RZ$GGUHVV 5HDG6WDWXV
&RPPDQG
3URJUDP
&RPPDQG
,2R 6XFFHVVIXO3URJUDP
,2R (UURULQ3URJUDP
XSWRP%\WH
6HULDO,QSXW
&RO
$GG 5RZ
$GG 5RZ
$GG 5RZ
$GG 'LQ
1'LQ
0K K ,2R
W:&
W:% W352*
W:&
W$'/
Rev 0.4 / Mar. 2007 32
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
&/(
$/(
&(
5(
5%
,2[
:(
W:&
K 'LQ
1'LQ
0'LQ
-'LQ
.
K K K
,2

&RO$GG &RO$GG &RO$GG &RO$GG5ZR$GG 5ZR$GG 5ZR$GG
W:&
W:%
W352*
6HULDO'DWD
,QSXW&RPPDQG 5DQGRP'DWD
,QSXW&RPPDQG
&ROXPQ$GGUHVV &ROXPQ$GGUHVV5RZ$GGUHVV 6HULDO,QSXW 6HULDO,QSXW 3URJUDP
&RPPDQG
5HDG6WDWXV
&RPPDQG
W:&
W$'/ W$'/
Figure 14 : Random Data In
Rev 0.4 / Mar. 2007 33
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
%XV\
W:%
W:%
W$'/
W352*
W:&
&/(
&(
:(
5(
,2[
5%
$/(
&ROXPQ$GGUHVV
K K K 'DWD 'DWD1 K ,2[%KK
&RO
$GG &RO
$GG 5RZ
$GG 5RZ
$GG 5RZ
$GG &RO
$GG &RO
$GG 5RZ
$GG 5RZ
$GG 5RZ
$GG
5RZ$GGUHVV &ROXPQ$GGUHVV 5RZ$GGUHVV
W5
%XV\
&RS\%DFN'DWD
,QSXW&RPPDQG
Figure 15 : Copy Back Program
Rev 0.4 / Mar. 2007 34
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
&/(
$/(
&(
5(
5%
,2[
:(
5%
,2[
([&DFKH3URJUDP
W:&
K K ,2
3URJUDP&RQILUP
&RPPDQG7UXH
/DVW3DJH,QSXW3URJUDP
0D[WLPHVUHSHDWDEOH
W&%6<PD[XV
W&%6<
&RO$GG5RZ$GG'DWD
W&%6< W&%6< W352*
6HULDO'DWD
,QSXW&RPPDQG &ROXPQ$GGUHVV 5RZ$GGUHVV 6HULDO,QSXW 3URJUDP
&RPPDQG
'XPP\
K K
$GGUHVV
'DWD,QSXW $GGUHVV
'DWD,QSXW $GGUHVV
'DWD,QSXW $GGUHVV
'DWD,QSXW
K K K KK K K
K K
'LQ
1'LQ
0'LQ
1'LQ
0
&RO
$GG
K &RO
$GG
5RZ
$GG
5RZ
$GG
5RZ
$GG
W:% W352*
W:% W&%6<
&RO
$GG &RO
$GG
5RZ
$GG
5RZ
$GG
5RZ
$GG
Figure 16 : Cache Program
Rev 0.4 / Mar. 2007 35
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
W:&
&/(
&(
:(
$/(
5(
,2[
5%
W:% W%(56
%86<
K ,2'K
5RZ
$GG 5RZ
$GG 5RZ
$GG
K
$XWR%ORFN(UDVH
6HWXS&RPPDQG
(UDVH&RPPDQG 5HDG6WDWXV
&RPPDQG
,2 6XFFHVVIXO(UDVH
,2 (UURULQ(UDVH
5RZ$GGUHVV
Figure 17: Block Erase Operation (Erase One Block)
K
&/(
&(
:(
$/(
5(
,2[ K
W5($
5HDG,'&RPPDQG $GGUHVVF\FOH 0DNHU&RGH 'HYLFH&RGH
$'K
WK&\FOHUG&\FOH
'$K 'K
WK&\FOH
KK
W$5
Figure 18: Read ID Operation
Rev 0.4 / Mar. 2007 36
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
'K
'
5HDGVWSDJH
5HDGQGSDJH
5HDGUGSDJH 5HDGWKSDJH
,GOH ,GOH
' ' ' ' ' ' ' ' ' '' ' 
$GG $GG $GG $GG $GG K
   
V V V
V
V V V
&/(
$/(
:(
5(
,QWHUQDORSHUDWLRQ
6WDWXV5HJLVWHU
65!
Figure 19: start address at page start :after 1st latency uninterrupted data flow
'
,GOH ,GOH
VW5%6<
  
QSDJH
QSDJH
5HDGQSDJH
' ' K' ' ' ' 
&/(
$/(
:(
5(
5%
,QWHUQDO
RSHUDWLRQ
6WDWXV5HJLVWHU
65!
8VHUFDQ
KHUHILQLVK
UHDGLQJ1
SDJH
1SDJH
FDQQRWEH
UHDG
V
V
,QWHUUXSWHG
5HDG
QSDJH
Figure 20: exit from cache read in 5us when device internally is reading (x8)
Rev 0.4 / Mar. 2007 37
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) 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 conn ect NAND Flash t o a microporc essor. 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.
&(GRQ¶WFDUH
K 6WDUW$GG&\FOH 'DWD,QSXW K'DWD,QSXW
&/(
&(
:(
$/(
,2[
Figure 21: Program Operation with CE don’t-care.
,IVHTXHQWLDOURZUHDGHQDEOHG
&(PXVWEHKHOGORZGXULQJW5 &(GRQ¶WFDUH
K K
&/(
&(
5(
$/(
5%
:(
,2[
6WDUW$GG&\FOH 'DWD2XWSXWVHTXHQWLDO
W5
Figure 22: Read Operation with CE don’t-care.
Rev 0.4 / Mar. 2007 38
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Figure 23: Reset Operation
))K
W567
:(
$/(
&/(
5(
,2[
5%
:3
:(
9FF
XV
W
97+
Figure 24: Power On and Data Protection Timing
VTH = 2.5 Volt for 3.3 Volt Supply devices
Rev 0.4 / Mar. 2007 39
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
5SYDOXHJXLGHQFH
5SPLQ9SDUW
ZKHUH,/LVWKHVXPRIWKHLQSXWFXUUQWVRIDOOGHYLFHVWLHGWRWKH5%SLQ
5SPD[LVGHWHUPLQHGE\PD[LPXPSHUPLVVLEOHOLPLWRIWU
#9FF 97D &&
/
S)
9FF0D[9
2/0D[ 9
P$,/,2/,/
5S LEXV\
&
/
5SRKP
LEXV\
LEXV\>$@
WUWI>V@
WI
 



 

   
%XV\
5HDG\ 9FF
92+
WUWI
92/
9FF
Q P
N N N N
Q P
Q P
*1'
'HYLFH
RSHQGUDLQRXWSXW
5%
Figure 25: Ready/Busy Pin electrical specifications
Rev 0.4 / Mar. 2007 40
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Bad Block Management
Devices wit h Bad Blocks ha ve the same qualit y level and the s ame 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 isol ated from the bit line and common sourc e lin e by a
select transistor. The devices are supplied with all the locations inside valid blocks erased(FFh).
The Bad Block Inform ation is written prior to shipping. Any bl ock where the 1st Byte / 1st 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 p laced
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 copyi ng the d at a to a
valid block. These additional Bad Blocks can be identified as attempts to program or erase them will give errors in the Status Regis-
ter.
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-programmin g t h e current data and copying the rest of the repl a ced 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 20 for the recommended procedure to follow if an error occurs during an operation.
Operation Recommended Procedure
Erase Block Replacement
Program Block Replacement or ECC (with 1bit/528byte)
Read ECC (with 1bit/528byte)
Table 20: Block Failure
Figure 26: Bad Block Management Flowchart
<HV
<HV
1R
1R
67$57
%ORFN$GGUHVV
%ORFN
'DWD
))K"
/DVW
EORFN"
(1'
,QFUHPHQW
%ORFN$GGUHVV
8SGDWH
%DG%ORFNWDEOH
Rev 0.4 / Mar. 2007 41
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Write Protect Operation
The Erase and Program Operations are automatically reset when WP goes Low (tWW = 100ns, min). The operations
are enabled and disabled as follows (Figure 27~30)
::
W
K K
:(
,2[
:3
5%
K K
W::
:(
,2[
:3
5%
Figure 27: Enable Programming
Figure 28: Disable Programming
Rev 0.4 / Mar. 2007 42
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
K
W
'K
::
:(
,2[
:3
5%
K
W::
'K
:(
,2[
:3
5%
Figure 29: Enable Erasing
Figure 30: Disable Erasing
Rev 0.4 / Mar. 2007 43
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Table 21: 48pin-TSOP1, 12 x 20mm, Package Mechanical Data
Symbol millimeters
Min Typ Max
A1.200
A1 0.050 0.150
A2 0.980 1.030
B 0.170 0.250
C 0.100 0.200
CP 0.100
D 11.910 12.000 12.120
E 19.900 20.000 20.100
E1 18.300 18.400 18.500
e 0.500
L 0.500 0.680
alpha 0 5



'
$
',(
$
H
%
/
Į
(
(
&
&3
$
Figure 31: 48pin-TSOP1, 12 x 20mm, Package Outline
Rev 0.4 / Mar. 2007 44
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
Symbol millimeters
Min Typ Max
A 16.90 17.00 17.10
A1 13.00
A2 12.00
B 11.90 12.00 12.10
B1 10.00
B2 6.00
C1.00
C1 1.50
C2 2.00
D1.00
D1 1.00
E 0.55 0.60 0.65
CP1 0.65 0.70 0.75
CP2 0.95 1.00 1.05
Figure 32. 52-ULGA, 12 x 17mm, Package Outline
(Top view through package)
%
$$$
FS
(
FS
&
&
&
%
%
''

0
&$%

0
&$%
Table 22: 52-ULGA, 12 x 17mm, Package Mechanical Data
Rev 0.4 / Mar. 2007 45
HY27UF(08/16)2G2A Series
2Gbit (256Mx8bit/128Mx16bit) NAND Flash
MARKING INFORMATION - TSOP1/ULGA
Packag M arking Exam ple
TSOP1
/
ULGA
K O R
H Y 2 7 U F x x 2 G 2 A
x x x x Y W W x x
- hynix
- K O R
- H Y27UFxx2G2A xxxx
HY : Hynix
2 7 : NAND Flash
U: Pow er Supply
F: Classification
xx: B it O rg a n iza tio n
2G: Density
2: Mode
A: Version
x : Package Type
x : Package M aterial
x : O perating Tem perature
x : Bad Block
- Y : Year (ex: 5= year 2005, 06= year 2006)
- w w: W ork W eek (ex: 12= w ork w eek 12)
- xx : Proce ss Co de
Note
- C ap ita l Le tter
- Small Lette r
: H yn ix S ymbo l
: Orig in C o u n tr y
: U (2.7V~ 3.6V)
: S in g le L e v e l C e ll+S in g le D ie +La r g e Blo c k
: 08(x8), 16(x16)
: 2G bit
: 1 n C E & 1 R /n B ; Se q u e ntia l Ro w R e ad Disa b le
: 2n d G e ne ra tion
: T(48-TSO P1), U(52-ULGA)
: Blank(Norm al), P(Lead Free)
: C (0~70) I(-4 0~85)
: B(Included Bad Block), S(1~5 Bad Block),
P(All G ood Block)
: Fixe d Item
: N o n-fix ed Item
: Part N u m b er