W29N01GV - Winbond

W29N01GV
W29N01GV
1G-BIT 3.3V
NAND FLASH MEMORY
1
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Table of Contents
1.
2.
3.
GENERAL DESCRIPTION ............................................................................................................... 7
FEATURES ....................................................................................................................................... 7
PACKAGE TYPES AND PIN CONFIGURATIONS .......................................................................... 8
3.1
Pin assignment 48-pin TSOP1 ............................................................................................. 8
3.2
Pin assignment 48 ball VFBGA ............................................................................................ 9
3.3
Pin Descriptions.................................................................................................................. 10
4.
PIN DESCRIPTIONS ...................................................................................................................... 11
4.1
Chip Enable (#CE).............................................................................................................. 11
4.2
Write Enable (#WE) ............................................................................................................ 11
4.3
Read Enable (#RE) ............................................................................................................ 11
4.4
Address Latch Enable (ALE) .............................................................................................. 11
4.5
Command Latch Enable (CLE) .......................................................................................... 11
4.6
Write Protect (#WP)............................................................................................................ 11
4.7
Ready/Busy (RY/#BY) ........................................................................................................ 11
4.8
Input and Output (I/Ox) ....................................................................................................... 11
5.
6.
BLOCK DIAGRAM .......................................................................................................................... 12
MEMORY ARRAY ORGANIZATION .............................................................................................. 13
6.1
Array Organization.............................................................................................................. 13
7.
8.
9.
MODE SELECTION TABLE ........................................................................................................... 14
COMMAND TABLE ........................................................................................................................ 15
DEVICE OPERATIONS .................................................................................................................. 16
9.1
READ operation.................................................................................................................. 16
9.2
9.3
9.4
9.1.1
PAGE READ (00h-30h)......................................................................................................... 16
9.1.2
CACHE READ OPERATIONS .............................................................................................. 17
9.1.3
RANDOM DATA OUTPUT (05h-E0h) ................................................................................... 21
9.1.4
READ ID (90h) ...................................................................................................................... 22
9.1.5
READ PARAMETER PAGE (ECh) ....................................................................................... 23
9.1.6
READ STATUS (70h) ........................................................................................................... 25
9.1.7
READ UNIQUE ID (EDh) ...................................................................................................... 27
PROGRAM operation ......................................................................................................... 28
9.2.1
PAGE PROGRAM (80h-10h) ................................................................................................ 28
9.2.2
SERIAL DATA INPUT (80h).................................................................................................. 28
9.2.3
RANDOM DATA INPUT (85h) .............................................................................................. 29
9.2.4
CACHE PROGRAM (80h-15h) ............................................................................................. 29
COPY BACK operation....................................................................................................... 31
9.3.1
READ for COPY BACK (00h-35h) ........................................................................................ 31
9.3.2
PROGRAM for COPY BACK (85h-10h) ................................................................................ 31
BLOCK ERASE operation .................................................................................................. 33
9.4.1
9.5
RESET operation................................................................................................................ 34
9.5.1
9.6
BLOCK ERASE (60h-D0h).................................................................................................... 33
RESET (FFh) ........................................................................................................................ 34
FEATURE OPERATION..................................................................................................... 35
Publication Release Date: June 5, 2014
2
Revision D
W29N01GV
9.7
9.8
9.9
9.6.1
GET FEATURES (EEh) ........................................................................................................ 38
9.6.2
SET FEATURES (EFh) ......................................................................................................... 39
ONE TIME PROGRAMMABLE (OTP) area ....................................................................... 40
9.7.1
OTP DATA PROGRAM (A0h-10h) ........................................................................................ 40
9.7.2
OTP DATA PROTECT (A5h-10h) ......................................................................................... 42
9.7.3
OTP DATA READ (AFh-30h) ................................................................................................ 43
WRITE PROTECT .............................................................................................................. 44
BLOCK LOCK..................................................................................................................... 46
10.
ELECTRICAL CHARACTERISTICS............................................................................................... 47
10.1 Absolute Maximum Ratings ................................................................................................ 47
10.2 Operating Ranges .............................................................................................................. 47
10.3 Device power-up timing ...................................................................................................... 48
10.4 DC Electrical Characteristics .............................................................................................. 49
10.5 AC Measurement Conditions ............................................................................................. 50
10.6 AC timing characteristics for Command, Address and Data Input ..................................... 50
10.7 AC timing characteristics for Operation .............................................................................. 51
10.8 Program and Erase Characteristics ................................................................................... 52
11.
12.
TIMING DIAGRAMS ....................................................................................................................... 53
INVALID BLOCK MANAGEMENT .................................................................................................. 62
12.1 Invalid blocks ...................................................................................................................... 62
12.2 Initial invalid blocks ............................................................................................................. 62
12.3 Error in operation ................................................................................................................ 63
12.4 Addressing in program operation ....................................................................................... 63
13.
PACKAGE DIMENSIONS............................................................................................................... 64
13.1 TSOP 48-pin 12x20 ............................................................................................................ 64
13.2 VFBGA48Ball (8X6.5 MM2, Ball pitch:0.8mm, Ø =0.45mm) ............................................... 65
14.
15.
16.
ORDERING INFORMATION .......................................................................................................... 66
VALID PART NUMBERS ................................................................................................................ 67
REVISION HISTORY ...................................................................................................................... 68
3
Publication Release Date: June 5, 2014
Revision D
W29N01GV
List of Tables
Table 3.1 Pin Descriptions .......................................................................................................................... 10
Table 6.1 Addressing .................................................................................................................................. 13
Table 7.1 Mode Selection ........................................................................................................................... 14
Table 8.1 Command Table.......................................................................................................................... 15
Table 9.1 Device ID and configuration codes for Address 00h................................................................... 22
Table 9.2 ONFI identifying codes for Address 20h ..................................................................................... 22
Table 10.1 Absolute Maximum Ratings ...................................................................................................... 47
Table 10.2 Operating Ranges ..................................................................................................................... 47
Table 10.3 DC Electrical Characteristics .................................................................................................... 49
Table 10.4 AC Measurement Conditions .................................................................................................... 50
Table 10.5 AC timing characteristics for Command, Address and Data Input ........................................... 50
Table 10.6 AC timing characteristics for Operation .................................................................................... 51
Table 10.7 Program and Erase Characteristics .......................................................................................... 52
Table 12.1 Valid Block Number .................................................................................................................. 62
Table 12.2 Block failure............................................................................................................................... 63
Table 15.1 Part Numbers for Commercial Temperature ............................................................................. 67
Table 15.2 Part Numbers for Industrial Temperature ................................................................................. 67
Table 16.1 History Table ............................................................................................................................. 68
4
Publication Release Date: June 5, 2014
Revision D
W29N01GV
List of Figures
Figure 3-1 Pin Assignment 48-pin TSOP1 (Package code S) ...................................................................... 8
Figure 3-2 Pin Assignment 48-ball VFBGA (Package Code D) .................................................................... 9
Figure 5-1 NAND Flash Memory Block Diagram ........................................................................................ 12
Figure 6-1 Array Organization ..................................................................................................................... 13
Figure 9-1Page Read Operations ............................................................................................................... 16
Figure 9-2 Sequential Cache Read Operations .......................................................................................... 18
Figure 9-3 Random Cache Read Operation ............................................................................................... 19
Figure 9-4 Last Address Cache Read Operation ........................................................................................ 20
Figure 9-5 Random Data Output ................................................................................................................. 21
Figure 9-6 Read ID...................................................................................................................................... 22
Figure 9-7 Read Parameter Page ............................................................................................................... 23
Figure 9-8 Read Status Operation .............................................................................................................. 25
Figure 9-9 Read Unique ID ......................................................................................................................... 27
Figure 9-10 Page Program.......................................................................................................................... 28
Figure 9-11 Random Data Input ................................................................................................................. 29
Figure 9-12 Cache Program Start ............................................................................................................... 30
Figure 9-13 Cache Program End ................................................................................................................ 30
Figure 9-14 Copy Back Program Operation................................................................................................ 32
Figure 9-15 Copy Back Operation with Random Data Input....................................................................... 32
Figure 9-16 Block Erase Operation ............................................................................................................. 33
Figure 9-17 Reset Operation....................................................................................................................... 34
Figure 9-18 Get Feature Operation ............................................................................................................. 38
Figure 9-19 Set Feature Operation ............................................................................................................. 39
Figure 9-20 OTP Data Program .................................................................................................................. 41
Figure 9-21 OTP Data Protect .................................................................................................................... 42
Figure 9-22 OTP Data Read ....................................................................................................................... 43
Figure 9-23 Erase Enable ........................................................................................................................... 44
Figure 9-24 Erase Disable .......................................................................................................................... 44
Figure 9-25 Program Enable ....................................................................................................................... 44
Figure 9-26 Program Disable ...................................................................................................................... 45
Figure 9-27 Program for Copy Back Enable ............................................................................................... 45
Figure 9-28 Program for Copy Back Disable .............................................................................................. 45
Figure 10-1 RY/#BY Behavior During Power-On ........................................................................................ 48
Figure 11-1 Command Latch Cycle ............................................................................................................ 53
Figure 11-2 Address Latch Cycle ................................................................................................................ 53
Figure 11-3 Data Latch Cycle ..................................................................................................................... 54
Figure 11-4 Serial Access Cycle after Read ............................................................................................... 54
Figure 11-5 Serial Access Cycle after Read (EDO) .................................................................................... 54
Figure 11-6 Read Status Operation ............................................................................................................ 55
Figure 11-7 Page Read Operation .............................................................................................................. 55
Figure 11-8 #CE Don't Care Read Operation ............................................................................................. 56
Figure 11-9 Random Data Output Operation .............................................................................................. 56
Figure 11-10 Cache Read Operation (1/2) ................................................................................................. 57
5
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-11 Cache Read Operation (2/2) ................................................................................................. 57
Figure 11-12 Read ID.................................................................................................................................. 58
Figure 11-13 Page Program........................................................................................................................ 58
Figure 11-14 #CE Don't Care Page Program Operation ............................................................................ 59
Figure 11-15 Page Program with Random Data Input ................................................................................ 59
Figure 11-16 Copy Back ............................................................................................................................. 60
Figure 11-17 Cache Program...................................................................................................................... 60
Figure 11-18 Block Erase............................................................................................................................ 61
Figure 11-19 Reset ..................................................................................................................................... 61
Figure 12-1 flow chart of create initial invalid block table ........................................................................... 62
Figure 12-2 Bad block Replacement........................................................................................................... 63
Figure 13-1 TSOP 48-PIN 12X20mm ......................................................................................................... 64
Figure 13-2 Fine-Pitch Ball Grid Array 48-Ball (8x6.5mm) ......................................................................... 65
Figure 14-1 Ordering Part Number Description .......................................................................................... 66
6
Publication Release Date: June 5, 2014
Revision D
W29N01GV
1. GENERAL DESCRIPTION
The W29N01GV (1G-bit) NAND Flash memory provides a storage solution for embedded systems with
limited space, pins and power. It is ideal for code shadowing to RAM, solid state applications and storing
media data such as, voice, video, text and photos. The device operates on a single 2.7V to 3.6V power
supply with active current consumption as low as 25mA and 10uA for CMOS standby current.
The memory array totals 138,412,032 bytes, and organized into 1,024 erasable blocks of 135,168 bytes.
Each block consists of 64 programmable pages of 2,112-bytes each. Each page consists of 2,048-bytes
for the main data storage area and 64-bytes for the spare data area (The spare area is typically used for
error management functions).
The W29N01GV supports the standard NAND flash memory interface using the multiplexed 8-bit bus to
transfer data, addresses, and command instructions. The five control signals, CLE, ALE, #CE, #RE and
#WE handle the bus interface protocol. Also, the device has two other signal pins, the #WP (Write
Protect) and the RY/#BY (Ready/Busy) for monitoring the device status.
2. FEATURES
 Basic Features
– Density : 1Gbit (Single chip solution)
– Vcc : 2.7V to 3.6V
– Bus width : x8
– Operating temperature
 Commercial: 0°C to 70°C
 Industrial: -40°C to 85°C
 Single-Level Cell (SLC) technology.
 Organization
– Density: 1G-bit/128M-byte
– Page size
 2,112 bytes (2048 + 64 bytes)
– Block size
 64 pages (128K + 4K bytes)
 Highest Performance
– Read performance (Max.)
 Random read: 25us
 Sequential read cycle: 25ns
– Write Erase performance
 Page program time: 250us(typ.)
 Block erase time: 2ms(typ.)
– Endurance 100,000 Erase/Program
Cycles(1)
– 10-years data retention
 Command set
– Standard NAND command set
– Additional command support
 Sequential Cache Read
 Random Cache Read
 Cache Program
 Copy Back
 OTP Data Program
 OTP Data Lock by Page
 OTP Data Read
– Contact Winbond for block Lock feature
 Lowest power consumption
– Read: 25mA(typ.)
– Program/Erase: 25mA(typ.)
– CMOS standby: 10uA(typ.)
 Space Efficient Packaging
– 48-pin standard TSOP1
– 48-ball VFBGA
– Contact Winbond for stacked
packages/KGD
Note:
1.
Endurance specification is based on 1bit/528 byte ECC (Error Correcting Code).
7
Publication Release Date: June 5, 2014
Revision D
W29N01GV
3. PACKAGE TYPES AND PIN CONFIGURATIONS
W29N01GV is offered in a 48-pin TSOP1 package (Code S) and 48-ball VFBGA package (Code S) as
shown in Figure 3-1 and 3-2, respectively. Package diagrams and dimensions are illustrated in Section:
Package Dimensions.
3.1
Pin assignment 48-pin TSOP1
Top View
X8
N.C
N.C
N.C
N.C
N.C
N.C
RY/#BY
#RE
#CE
N.C
N.C
Vcc
Vss
N.C
N.C
CLE
ALE
#WE
#WP
DNU
N.C
N.C
N.C
N.C
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
X8
48-pin TSOP1
Standard package
12mm x 20mm
48
47
46
45
44
43
42
41
40
39
38
37
36
35
34
33
32
31
30
29
28
27
26
25
Vss1
N.C
N.C
N.C
IO7
IO6
IO5
IO4
N.C
Vcc1
DNU
Vcc
Vss
N.C
Vcc1
N.C
IO3
IO2
IO1
IO0
N.C
N.C
N.C
Vss1
Figure 3-1 Pin Assignment 48-pin TSOP1 (Package code S)
Note:
1.
These pins might not be connected in the package. Winbond recommends connecting these pins to the designed
external sources for ONFI compatibility.
8
Publication Release Date: June 5, 2014
Revision D
W29N01GV
3.2
Pin assignment 48 ball VFBGA
Top View, ball down
1
2
3
4
5
6
A
#WP
ALE
Vss
#CE
#WE
RY/#BY
B
N.C
#RE
CLE
N.C
N.C
N.C
C
N.C
N.C
N.C
N.C
N.C
N.C
D
N.C
N.C
N.C
N.C
N.C
N.C
E
DNU
N.C
N.C
N.C
N.C
N.C
F
N.C
IO0
N.C
N.C
N.C
Vcc
G
N.C
IO1
N.C
Vcc
IO5
IO7
H
Vss
IO2
IO3
IO4
IO6
Vss
Figure 3-2 Pin Assignment 48-ball VFBGA (Package Code D)
9
Publication Release Date: June 5, 2014
Revision D
W29N01GV
3.3
Pin Descriptions
PIN NAME
I/O
FUNCTION
#WP
I
Write Protect
ALE
I
Address Latch Enable
#CE
I
Chip Enable
#WE
I
Write Enable
RY/#BY
O
Ready/Busy
#RE
I
Read Enable
CLE
I
Command Latch Enable
I/O[0-7]
I/O
Vcc
Supply
Power supply
Vss
Supply
Ground
DNU
-
Do Not Use: This pins are unconnected pins.
N.C
-
No Connect
Data Input/Output (x8)
Table 3.1 Pin Descriptions
Note:
1.
Connect all Vcc and Vss pins to power supply or ground. Do not leave Vcc or Vss disconnected.
10
Publication Release Date: June 5, 2014
Revision D
W29N01GV
4. PIN DESCRIPTIONS
4.1 Chip Enable (#CE)
#CE pin enables and disables device operation. When #CE is high the device is disabled and the I/O pins
are set to high impedance and enters into standby mode if not busy. When #CE is set low the device will
be enabled, power consumption will increase to active levels and the device is ready for Read and Write
operations.
4.2 Write Enable (#WE)
#WE pin enables the device to control write operations to input pins of the device. Such as, command
instructions, addresses and data that are latched on the rising edge of #WE.
4.3 Read Enable (#RE)
#RE pin controls serial data output from the pre-loaded Data Register. Valid data is present on the I/O
bus after the tREA period from the falling edge of #RE. Column addresses are incremented for each #RE
pulse.
4.4
Address Latch Enable (ALE)
ALE pin controls address input to the address register of the device. When ALE is active high, addresses
are latched via the I/O pins on the rising edge of #WE.
4.5 Command Latch Enable (CLE)
CLE pin controls command input to the command register of the device. When CLE is active high,
commands are latched into the command register via I/O pins on the rising edge of #WE.
4.6 Write Protect (#WP)
#WP pin can be used to prevent the inadvertent program/erase to the device. When #WP pin is active
low, all program/erase operations are disabled.
4.7 Ready/Busy (RY/#BY)
RY/#BY pin indicates the device status. When RY/#BY output is low, it indicates that the device is
processing either a program, erase or read operations. When it returns to high, those operations have
completed. RY/#BY pin is an open drain.
4.8 Input and Output (I/Ox)
I/Ox bi-directional pins are used for the following; command, address and data operations.
11
Publication Release Date: June 5, 2014
Revision D
W29N01GV
5. BLOCK DIAGRAM
Status
Register
#CE
ALE
CLE
#RE
#WE
#WP
Command
Resister
Column Decoder
Cache Register
Data Register
I/O
Control
I/Ox
Address
Register
NAND Flash
Array
Logic
Control
High Voltage
Generator
Row Decoder
RY/#BY
Figure 5-1 NAND Flash Memory Block Diagram
12
Publication Release Date: June 5, 2014
Revision D
W29N01GV
6. MEMORY ARRAY ORGANIZATION
6.1
Array Organization
Total
1024 blocks
IO0 ~ IO7
1 block
2048
Data register
64
2048
Cache register
64
1 page
= 2048+64 bytes
1 block
= 64 pages
= (128K+4K) bytes
1 device
=1024 blocks
= (128M + 4M) bytes
2112 bytes
Figure 6-1 Array Organization
I/O7
I/O6
I/O5
I/O4
I/O3
I/O2
I/O1
I/O0
A7
A6
A5
A4
A3
A2
A1
A0
2 cycle
L
L
L
L
A11
A10
A9
A8
3rd cycle
A19
A18
A17
A16
A15
A14
A13
A12
A27
A26
A25
A24
A23
A22
A21
A20
1st cycle
nd
th
4 cycle
Table 6.1 Addressing
Notes:
1.
“L” indicates a low condition, which must be held during the address cycle to insure correct processing.
2.
A0 to A11 during the 1st and 2nd cycles are column addresses. A12 to A27 during the 3rd and 4th cycles are row
addresses.
3.
The device ignores any additional address inputs that exceed the device’s requirement.
13
Publication Release Date: June 5, 2014
Revision D
W29N01GV
7. MODE SELECTION TABLE
MODE
CLE
ALE
#CE
#WE
#RE
#WP
Read
mode
Command input
H
L
L
H
X
Address input
L
H
L
H
X
Write
mode
Command input
H
L
L
H
H
Address input
L
H
L
H
H
Data input
L
L
L
H
H
Sequential Read and Data output
L
L
L
H
During read (busy)
X
X
X
X
H
X
During program (busy)
X
X
X
X
X
H
During erase (busy)
X
X
X
X
X
H
Write protect
X
X
X
X
X
L
Standby
X
X
H
X
X
0V/Vcc
X
Table 7.1 Mode Selection
Notes:
1.
“H” indicates a HIGH input level, “L” indicates a LOW input level, and “X” indicates a Don’t Care Level.
2.
#WP should be biased to CMOS HIGH or LOW for standby.
14
Publication Release Date: June 5, 2014
Revision D
W29N01GV
8. COMMAND TABLE
1st CYCLE
2nd CYCLE
PAGE READ
00h
30h
READ for COPY BACK
00h
35h
SEQUENTIAL CACHE READ
31h
RANDOM CACHE READ
00h
LAST ADDRESS CACHE READ
3Fh
READ ID
90h
READ STATUS
70h
Yes
RESET
FFh
Yes
PAGE PROGRAM
80h
10h
PROGRAM for COPY BACK
85h
10h
CACHE PROGRAM
80h
15h
60h
D0h
COMMAND
BLOCK ERASE
RANDOM DATA INPUT
(1)
Acceptable during
busy
31h
85h
RANDOM DATA OUTPUT(1)
05h
READ PARAMETER PAGE
ECh
READ UNIQUE ID
EDh
GET FEATURES
EEh
SET FEATURES
EFh
OTP DATA PROTECT
A5h
10h
OTP DATA PROGRAM
A0h
10h
OTP DATA READ
AFh
30h
E0h
Table 8.1 Command Table
Notes:
1.
RANDOM DATA INPUT and RANDOM DATA OUTPUT command is only to be used within a page.
2.
Any commands that are not in the above table are considered as undefined and are prohibited as inputs.
15
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9. DEVICE OPERATIONS
9.1 READ operation
9.1.1 PAGE READ (00h-30h)
When the device powers on, the default is READ mode. This operation can also be entered by writing 00h
command to the command register, and then write four address cycles, followed by writing 30h command.
After writing 30h command, the data is transferred from NAND array to Data Register during tR. Data
transfer progress can be done by monitoring the status of the RY/#BY signal output. RY/#BY signal will
be LOW during data transfer. Also, there is an alternate method by using the READ STATUS (70h)
command. If the READ STATUS command is issued during read operation, the Read (00h) command
must be re-issued to read out the data from Data Register. When the data transfer is complete, RY/#BY
signal goes HIGH, and the data can be read from Data Register by toggling #RE. Read is sequential from
initial column address to the end of the page. (See Figure 9-1)
Figure 9-1Page Read Operations
16
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.2 CACHE READ OPERATIONS
To obtain a higher degree of performance read operations, the device’s Cache and Data Register can be
used independent of each other. Data can be read out from the Cache Register, while array data is
transferred from the NAND Array to the Data Register.
The CACHE READ mode starts with issuing a PAGE READ command (00h-30h) to transfer a page of
data from NAND array to the Cache Register. RY/#BY signal will go LOW during data transfer indicating a
busy status. Copying the next page of data from the NAND array to the Data Register while making the
Cache Register page data available is done by issuing either a SEQUENTIAL CACHE READ (31h) or
RANDOM CACHE READ (00h-31h) command. The SEQUENTIAL CACHE READ mode will copy the
next page of data in sequence from the NAND array to the Data Register or use the RANDOM CACHE
READ mode (00h-31h) to copy a random page of data from NAND array to the Data Register. The
RY/#BY signal goes LOW for a period of tRCBSY during the page data transfer from NAND array to the
Data Register. When RY/#BY goes HIGH, this means that the Cache Register data is available and can
be read out of the Cache Register by toggling #RE, which starts at address column 0. If it is desired to
start at a different column address, a RANDOM DATA OUTPUT (05h-E0h) command can be used to
change the column address to read out the data.
At this point in the procedure when completing the read of the desired number of bytes, one of two things
can be chosen. Continue CACHE READ (31h or 00h-31h) operations or end the CACHE READ mode
with a LAST ADDRESS CACHE READ (3Fh) command.
To continue with the read operations, execute the CACHE READ (31h or 00h-31h) command. The
RY/#BY signal goes LOW for the period of tRCBSY while data is copied from Data Register to the Cache
Register and the next page of data starts being copied from the NAND array to the Data Register. When
RY/#BY signal goes HIGH signifying that the Cache Register data is available, at this time #RE can start
toggling to output the desired data starting at column 0 address or using the RANDOM DATA OUPUT
command for random column address access.
To terminate the CACHE READ operations a LAST ADDRESS CACHE READ (3Fh) command is issued,
RY/#BY signal goes LOW and the Data Register contents is copied to the Cache Register. At the
completion of the Data Register to Cache Register transfer, RY/#BY goes HIGH indicating data is
available at the output of the Cache Register. At this point Data can be read by toggling #RE starting at
column address 0 or using the RANDOM DATA OUPUT command for random column address access.
The device NAND array is ready for next command set.
17
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.2.1. SEQUENTIAL CACHE READ (31h)
The SEQUENTIAL CACHE READ (31h) copies the next page of data in sequence within block to the
Data Register while the previous page of data in the Cache Register is available for output. This is done
by issuing the command (31h), RY/#BY signal goes LOW and the STATUS REGISTER bits 6 and 5 =
“00” for the period of tRCBSY. When RY/#BY signal goes HIGH and STATUS REGISTER bits 6 and 5 =
“10”, data at the Cache Register is available. The data can be read out from the Cache Register by
toggling #RE, starting address is column 0 or by using the RANDOM DATA OUPUT command for random
column address access.
Figure 9-2 Sequential Cache Read Operations
18
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.2.2. RANDOM CACHE READ (00h-31h)
The RANDOM CACHE READ (00h-31h) will copy a particular page from NAND array to the Data Register
while the previous page of data is available at the Cache Register output. Perform this function by first
issuing the 00h command to the Command Register, then writing the four address cycles for the desired
page of data to the Address Register. Then write the 31h command to the Command Register. Note; the
column address bits are ignored.
After the RANDOM CACHE READ command is issued, RY/#BY signal goes LOW and STATUS
REGISTER bits 6 and 5 equal “00” for the period of tRCBSY. When RY/#BY signal goes HIGH and
STATUS REGISTER bits 6 and 5 equal “10”, the page data in the Cache Register is available. The data
can read out from the Cache Register by toggling #RE, the starting column address will be 0 or use the
RANDOM DATA OUTPUT (05h-E0h) command change the column address to start reading out the data.
Figure 9-3 Random Cache Read Operation
19
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.2.3. LAST ADDRESS CACHE READ (3Fh)
The LAST ADDRESS CACHE READ (3Fh) copies a page of data from the Data Register to the Cache
Register without starting the another cache read. After writing the 3Fh command, RY/#BY signal goes
LOW and STATUS REGISTER bits 6 and 5 equals “00” for the period of tRCBSY. When RY/#BY signal
goes HIGH and STATUS REGISTER bits 6 and 5 equals “11”, the Cache Register data is available, and
the device NAND array is in ready state. The data can read out from the Cache Register by toggling #RE,
starting at address column 0 or RANDOM DATA OUTPUT (05h-E0h) command to change the column
address to read out the data.
Figure 9-4 Last Address Cache Read Operation
20
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.3 RANDOM DATA OUTPUT (05h-E0h)
The RANDOM DATA OUTPUT allows the selection of random column addresses to read out data from a
single or multiple of addresses. The use of the RANDOM DATA OUTPUT command is available after the
PAGE READ (00h-30h) sequence by writing the 05h command following by the 2 cycle column address
and then the E0h command. Toggling #RE will output data sequentially. The RANDOM DATA OUTPUT
command can be issued multiple times, but limited to the current loaded page.
Figure 9-5 Random Data Output
21
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.4 READ ID (90h)
READ ID command is comprised of two modes determined by the input address, device (00h) or ONFI
(20h) identification information. To enter the READ ID mode, write 90h to the Command Register followed
by a 00h address cycle, then toggle #RE for 5 single byte cycles, the W29N01GV pre-programmed code
includes the Manufacturer ID, Device ID, and Product-Specific Information (see Table 9.1). If the READ
ID command is followed by 20h address, the output code includes 4 single byte cycles of ONFI identifying
information (see Table 9.2). The device remains in the READ ID mode until the next valid command is
issued.
Figure 9-6 Read ID
# of
Byte/Cycles
1st
Byte/Cycle
2nd
Byte/Cycle
3rd
Byte/Cycle
4th
Byte/Cycle
5th
Byte/Cycle
Code
EFh
F1h
80h
95h
00h
Device ID
Cache
Programming
Supported
Page Size:2KB
Spare Area Size:64b
BLK Size w/o Spare:128KB
Organized:X8
Serial Access:25ns
Description
MFR ID
Table 9.1 Device ID and configuration codes for Address 00h
# of Byte/Cycles
1st
Byte/Cycle
2nd
Byte/Cycle
3rd
Byte/Cycle
4th
Byte/Cycle
Code
4Fh
4Eh
46h
49h
Table 9.2 ONFI identifying codes for Address 20h
22
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.5 READ PARAMETER PAGE (ECh)
READ PARAMETER PAGE can read out the device’s parameter data structure, such as, manufacturer
information, device organization, timing parameters, key features, and other pertinent device parameters.
The data structure is stored with at least three copies in the device’s parameter page. Figure 9-7 shows
the READ PARAMETER PAGE timing. The RANDOM DATA OUTPUT (05h-E0h) command is supported
during data output.
Figure 9-7 Read Parameter Page
Byte
Description
Value
0-3
Parameter page signature
4Fh, 4Eh, 46h, 49h
4-5
Revision number
02h, 00h
6-7
Features
supported
8-9
Optional commands supported
37h, 00h
10-31
Reserved
00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h,
00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h
32-43
Device manufacturer
57h, 49h, 4Eh, 42h, 4Fh, 4Eh, 44h, 20h, 20h, 20h, 20h,
20h
44-63
Device model
57h,32h,39h,4Eh,30h,31h,47h,56h,20h,20h,20h,20h,20
h,20h,20h,20h,20h,20h,20h,20h
64
W29N01GV (x8)
10h, 00h
W29N01GV (x8)
Manufacturer ID
EFh
65-66
Date code
00h, 00h
67-79
Reserved
00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h,
00h, 00h
80-83
# of data bytes per page
00h, 08h, 00h, 00h
84-85
# of spare bytes per page
40h, 00h
86-89
# of data bytes per partial page
00h, 02h, 00h, 00h
90-91
# of spare bytes per partial page
10h, 00h
92-95
# of pages per block
40h, 00h, 00h, 00h
23
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Byte
96-99
Description
Value
# of blocks per unit
00h, 04h, 00h, 00h
100
# of logical units
01h
101
# of address cycles
22h
102
# of bits per cell
01h
103-104
Bad blocks maximum per unit
14h, 00h
105-106
Block endurance
01h, 05h
Guaranteed valid blocks at beginning of
target
01h
Block endurance for guaranteed valid
blocks
00h, 00h
110
# of programs per page
04h
111
Partial programming attributes
00h
112
# of ECC bits
01h
113
# of interleaved address bits
00h
114
Interleaved operation attributes
00h
Reserved
00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h,
00h, 00h
I/O pin capacitance
0Ah
129-130
Timing mode support
1Fh, 00h
131-132
Program cache timing
1Fh, 00h
133-134
Maximum page program time
BCh, 02h
135-136
Maximum block erase time
10h, 27h
137-138
Maximum random read time
19h, 00h
139-140
tCCS minimum
46h, 00h
141-163
Reserved
00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h,
00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h, 00h,
00h
164-165
Vendor specific revision #
01h,00h
166-253
Vendor specific
00h
254-255
Integrity CRC
Set at shipment
256-511
Value of bytes 0-255
512-767
Value of bytes 0-255
107
108-109
115-127
128
>767
Additional redundant parameter pages
Table 9.3 Parameter Page Output Value
24
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.6 READ STATUS (70h)
The W29N01GV has an 8-bit Status Register which can be read during device operation. Refer to Table
9.3 for specific Status Register definitions. After writing 70h command to the Command Register, read
cycles will only read from the Status Register. The status can be read from I/O[7:0] outputs, as long as
#CE and #RE are LOW. Note; #RE does not need to be toggled for Status Register read. The Command
Register remains in status read mode until another command is issued. To change to normal read mode,
issue the PAGE READ (00h) command. After the PAGE READ command is issued, data output starts
from the initial column address.
Figure 9-8 Read Status Operation
25
Publication Release Date: June 5, 2014
Revision D
W29N01GV
SR bit
I/O 0
Page Read
Cache Read
Page Program
Cache
Program
Block Erase
Definition
0=Successful
Program/Erase
Not Use
Not Use
Pass/Fail
Pass/Fail(N)
Pass/Fail
1=Error
in Program/Erase
I/O 1
Not Use
Not Use
Not Use
Pass/Fail(N-1)
Not Use
0=Successful
Program
1=Error in Program
I/O 2
Not Use
Not Use
Not Use
Not Use
Not Use
0
I/O 3
Not Use
Not Use
Not Use
Not Use
Not Use
0
I/O 4
Not Use
Not Use
Not Use
Not Use
Not Use
0
I/O 5
Ready/Busy
Ready/Busy1
Ready/Busy
Ready/Busy
Ready/Busy
I/O 6
Ready/Busy
Cache
Ready/Busy2
Ready/Busy
Cache
Ready/Busy
Ready/Busy
I/O 7
Write Protect
Write Protect
Write Protect
Write Protect
Write Protect
Ready = 1
Busy = 0
Ready = 1
Busy = 0
Unprotected = 1
Protected = 0
Table 9.4 Status Register Bit Definition
Notes:
1.
SR bit 5 is 0 during the actual programming operation. If cache mode is used, this bit will be 1 when all internal
operations are complete.
2.
SR bit 6 is 1 when the Cache Register is ready to accept new data. RY/#BY follows bit 6.
26
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.1.7 READ UNIQUE ID (EDh)
The W29N01GV NAND Flash device has a method to uniquely identify each NAND Flash device by using
the READ UNIQUE ID command. The format of the ID is limitless, but the ID for every NAND Flash
device manufactured, will be guaranteed to be unique.
Numerous NAND controllers typically use proprietary error correction code (ECC) schemes. In these
cases Winbond cannot protect unique ID data with factory programmed ECC. However, to ensure data
reliability, Winbond will program the NAND Flash devices with 16 bytes of unique ID code, starting at byte
0 on the page, immediately followed by 16 bytes of the complement of that unique ID. The combination of
these two actions is then repeated 16 times. This means the final copy of the unique ID will resides at
location byte 511. At this point an XOR or exclusive operation can be performed on the first copy of the
unique ID and its complement. If the unique ID is good, the results should yield all the bits as 1s. In the
event that any of the bits are 0 after the XOR operation, the procedure can be repeated on a subsequent
copy of the unique ID data.
Figure 9-9 Read Unique ID
27
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.2 PROGRAM operation
9.2.1 PAGE PROGRAM (80h-10h)
The W29N01GV Page Program command will program pages sequentially within a block, from the lower
order page address to higher order page address. Programming pages out of sequence is prohibited. The
W29N01GV supports partial-page programming operations up to 4 times before an erase is required if
partitioning a page. Note; programming a single bit more than once without first erasing it is not
supported.
9.2.2 SERIAL DATA INPUT (80h)
Page Program operation starts with the execution of the Serial Data Input command (80h) to the
Command Register, following next by inputting four address cycles and then the data is loaded. Serial
data is loaded to Cache Register with each #WE cycle. The Program command (10h) is written to the
Command Register after the serial data input is finished. At this time the internal write state controller
automatically executes the algorithms for program and verifies operations. Once the programming starts,
determining the completion of the program process can be done by monitoring the RY/#BY output or the
Status Register Bit 6, which will follow the RY/#BY signal. RY/#BY will stay LOW during the internal array
programming operation during the period of (tPROG). During page program operation, only two
commands are available, READ STATUS (70h) and RESET (FFh). When the device status goes to the
ready state, Status Register Bit 0 (I/O0) indicates whether the program operation passed (Bit0=0) or failed
(Bit0=1), (see Figure 9-10). The Command Register remains in read status mode until the next command
is issued.
Figure 9-10 Page Program
28
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.2.3 RANDOM DATA INPUT (85h)
After the Page Program (80h) execution of the initial data has been loaded into the Cache Register, if the
need for additional writing of data is required, using the RANDOM DATA INPUT (85h) command can
perform this function to a new column address prior to the Program (10h) command. The RANDOM Data
INPUT command can be issued multiple times in the same page (See Figure 9-11).
Figure 9-11 Random Data Input
9.2.4 CACHE PROGRAM (80h-15h)
CACHE PROGEAM (80h) command is started by writing the command to the Command Register. The
next writes should be four cycles of address, and then either writing a full or partial page of input data into
the Cache Register. Issuing the CACHE PROGRAM (15h) command to the Command Register, starting
transferring data from the Cache Register to the Data Register on the rising edge of #WE and RY/#BY will
go LOW. Programming to the array starts after the data has been copied into the Data Register and
RY/#BY returns to HIGH.
When RY/#BY returns to HIGH, the next input data can be written to the Cache Register by issuing
another CACHE PROGRAM command series. The time RY/#BY goes LOW, is typical controlled by the
actual programming time. The time for the first programming pass equals the time it takes to transfer the
data from the Cache Register to the Data Register. On the second and subsequent programming passes,
data transfer from the Cache Register to the Data Register is held until Data Register content is
programming into the NAND array.
The CACHE PROGRAM command can cross block address boundaries. RANDOM DATA INPUT (85h)
commands are permitted with CACHE PROGRAM operations. Status Register’s Cache RY/#BY Bit 6
(I/O6) can be read after issuing the READ STATUS (70h) command for confirming when the Cache
Register is ready or busy. RY/#BY, always follows Status Register Bit 6 (I/O6). Status Register’s RY/#BY
Bit 5 (I/O5) can be polled to determine whether the array programming is in progress or completed for the
current programming cycle.
If only RY/#BY is used for detecting programming status, the last page of the program sequence must
use the PAGE PROGRAM (10h) command instead of the CACHE PROGRAM (15h) command. If the
29
Publication Release Date: June 5, 2014
Revision D
W29N01GV
CACHE PROGRAM (15h) command is used every time, including the last page programming, Status
Register’s Bit 5 (I/O5) must be used to determine when programming is complete.
Status Register’s Pass/Fail, Bit 0 (I/O0) returns the pass/fail status for the previous page when Status
Register’s Bit 6 (I/O6) equals a “1” (ready state). The pass/fail status of the current PROGRAM operation
is returned with Status Register’s Bit 0 (I/O0) when Bit 5 (I/O5) of the Status Register equals a “1” (ready
state) as shown in Figure 9-12 and 9-13.
Note: The CACHE PROGRAM command cannot be used on blocks 0-3 if used as boot blocks.
Figure 9-12 Cache Program Start
Figure 9-13 Cache Program End
30
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.3
COPY BACK operation
Copy Back operations require two command sets. Issue a READ for COPY BACK (00h-35h) command
first, then the PROGRAM for COPY BACK (85h-10h) command.
9.3.1 READ for COPY BACK (00h-35h)
The READ for COPY BACK command is used together with the PROGRAM for COPY BACK (85h-10h)
command. To start execution, READ for COPY BACK (00h) command is written to the Command
Register, followed by the four cycles of the source page address. To start the transfer of the selected
page data from the memory array to the Cache Register, write the 35h command to the Command
Register.
After execution of the READ for COPY BACK command sequence and RY/#BY returns to HIGH marking
the completion of the operation, the transferred data from the source page into the Cache Register may
be read out by toggling #RE. Data is output sequentially from the column address that was originally
specified with the READ for COPY BACK command. RANDOM DATA OUTPUT (05h-E0h) commands
can be issued multiple times without any limitation after READ for COPY BACK command has been
executed (see Figures 9-14 and 9-15).
At this point the device is in ready state to accept the PROGRAM for COPY BACK command.
9.3.2 PROGRAM for COPY BACK (85h-10h)
After the READ for COPY BACK command operation has been completed and RY/#BY goes HIGH, the
PROGRAM for COPY BACK command can be written to the Command Register. The command results in
the transfer of data from the Cache Register to the Data Register, then internal operations start
programming of the new destination page. The sequence would be, write 85h to the Command Register,
followed by the four cycle destination page address to the NAND array. Next write the 10h command to
the Command Register; this will signal the internal controller to automatically start to program the data to
new destination page. During this programming time, RY/#BY will go LOW. The READ STATUS
command can be used instead of the RY/#BY signal to determine when the program is complete. When
Status Register Bit 6 (I/O6) equals to “1”, Status Register Bit 0 (I/O0) will indicate if the operation was
successful or not.
The RANDOM DATA INPUT (85h) command can be used during the PROGRAM for COPY BACK
command for modifying the original data. Once the data is copied into the Cache Register using the
READ for COPY BACK (00h-35h) command, follow by writing the RANDOM DATA INPUT (85h)
command, along with the address of the data to be changed. The data to be changed is placed on the
external data pins. This operation copies the data into the Cache Register. Once the 10h command is
written to the Command Register, the original data and the modified data are transferred to the Data
Register, and programming of the new page commences. The RANDOM DATA INPUT command can be
issued numerous times without limitation, as necessary before starting the programming sequence with
10h command.
Since COPY BACK operations do not use external memory and the data of source page might include a
bit errors, a competent ECC scheme should be developed to check the data before programming data to
a new destination page.
31
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 9-14 Copy Back Program Operation
Figure 9-15 Copy Back Operation with Random Data Input
32
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.4 BLOCK ERASE operation
9.4.1
BLOCK ERASE (60h-D0h)
Erase operations happen at the architectural block unit. This W29N01GV has 1024 erase blocks. Each
block is organized into 64 pages (2112 bytes/page), 132K bytes (128K + 4K bytes)/block. The BLOCK
ERASE command operates on a block by block basis.
Erase Setup command (60h) is written to the Command Register. Next, the two cycle block address is
written to the device. The page address bits are loaded during address block address cycle, but are
ignored. The Erase Confirm command (D0h) is written to the Command Register at the rising edge of
#WE, RY/#BY goes LOW and the internal controller automatically handles the block erase sequence of
operation. RY/#BY goes LOW during Block Erase internal operations for a period of tBERS,
The READ STATUS (70h) command can be used for confirm block erase status. When Status Register
Bit6 (I/O6) becomes to “1”, block erase operation is finished. Status Register Bit0 (I/O0) will indicate a
pass/fail condition (see Figure 9-16).
Figure 9-16 Block Erase Operation
33
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.5
RESET operation
9.5.1 RESET (FFh)
READ, PROGRAM, and ERASE commands can be aborted by the RESET (FFh) command during the
time the W29N01GV is in the busy state. The Reset operation puts the device into a known status. The
data that is processed in either the programming or erasing operations are no longer valid. This means
the data can be partially programmed or erased and therefore data is invalid. The Command Register is
cleared and is ready to accept next command. The Data Register and Cache Register contents are
marked invalid.
The Status Register indicates a value of E0h when #WP is HIGH; otherwise a value of 60h when #WP is
LOW. After RESET command is written to the command register, RY/#BY goes LOW for a period of tRST
(see Figure 9-17).
Figure 9-17 Reset Operation
34
Publication Release Date: June 5, 2014
Revision D
W29N01GV
FEATURE OPERATION
9.6
The GET FEATURES (EEh) and SET FEATURES (EFh) commands are used to change the NAND Flash
device behavior from the default power on settings. These commands use a one-byte feature address to
determine which feature is to be read or modified. A range of 0 to 255 defines all features; each is
described in the features table (see Table 9.4 thru 9.7). The GET FEATURES (EEh) command reads 4Byte parameter in the features table (See GET FEATURES function). The SET FEATURES (EFh)
command places the 4-Byte parameter in the features table (See SET FEATURES function).
When a feature set is volatile, meaning it remains active by default until the device is powered off. The set
feature remains the set even if a RESET (FFh) command is issued.
Feature address
Description
00h
N.A
01h
Timing mode
02h-7Fh
Reserved
80h
Vendor specific parameter : Programmable I/O drive strength
81h
Vendor specific parameter : Programmable RY/#BY pull-down strength
82h-FFh
Reserved
Table 9.5 Features
Feature Address 01h: Timing Mode
Sub feature
Options
I/O7
I/O6
I/O5
I/O4
I/O3
I/O2
I/O1
I/O0
Value
Notes
parameter
P1
Timing mode
Mode 0 (default)
Reserved (0)
0
0
0
00h
1
Mode 1
Reserved (0)
0
0
1
01h
1
Mode 2
Reserved (0)
0
1
0
02h
1
Mode 3
Reserved (0)
0
1
1
03h
1
Mode 4
Reserved (0)
1
0
0
04h
1
Mode 5
Reserved (0)
1
0
1
05h
2
P2
Reserved (0)
00h
Reserved (0)
00h
Reserved (0)
00h
P3
P4
Table 9.6 Feature Address 01h
Notes:
1.
2.
Timing mode is set to mode 0 by default. The timing mode should be selected to indicate the maximum speed at
which the device will receive addresses, commands, and data cycles. The five supported settings for the timing
mode are shown. The device returns to mode 0 when a power cycle has occurred. Supported timing modes are
reported in the parameter page.
Not supported.
35
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Feature Address 80h: Programmable I/O Drive Strength
Sub feature
Options
I/O7
I/O6
I/O5
I/O4
I/O3
I/O2
I/O1
I/O0
Value
Notes
1
parameter
P1
I/O
Full (default)
Reserved (0)
0
0
00h
drive strength
Three-quarters
Reserved (0)
0
1
01h
One-half
Reserved (0)
1
0
02h
One-quarter
Reserved (0)
1
1
03h
P2
Reserved (0)
00h
Reserved (0)
00h
Reserved (0)
00h
P3
P4
Table 9.7 Feature Address 80h
Note:
1.
The default drive strength setting is Full strength. The Programmable I/O Drive Strength mode is used to change
from the default I/O drive strength. Drive strength should be selected based on expected loading of the memory
bus. This table shows the four supported output drive-strength settings. The device returns to the default drive
strength mode when a power cycle has occurred. AC timing parameters may need to be relaxed if I/O drive
strength is not set to full.
36
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Feature Address 81h: Programmable RY/#BY Pull-down Strength
Sub feature
Options
I/O7
I/O6
I/O5
I/O4
I/O3
I/O2
I/O1
I/O0
Value
Notes
1
parameter
P1
RY/#BY
Full (default)
Reserved (0)
0
0
00h
pull-down
Three-quarters
Reserved (0)
0
1
01h
One-half
Reserved (0)
1
0
02h
One-quarter
Reserved (0)
1
1
03h
strength
P2
Reserved (0)
00h
Reserved (0)
00h
Reserved (0)
00h
P3
P4
Table 9.8 Feature Address 81h
Note:
1.
The default programmable RY/#BY pull-down strength is set to Full strength. The pull-down strength is used to
change the RY/#BY pull-down strength. RY/#BY pull-down strength should be selected based on expected
loading of RY/#BY. The four supported pull-down strength settings are shown. The device returns to the default
pull-down strength when a power cycle has occurred.
37
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.6.1 GET FEATURES (EEh)
The GET FEATURES command returns the device feature settings including those previously set by the
SET FEATURES command. To use the Get Feature mode write the command (EEh) to the Command
Register followed by the single cycle byte Feature Address. RY/#BY will goes LOW for the period of
tFEAT. If Read Status (70h) command is issued for monitoring the process completion status, Read
Command (00h) has to be executed to re-establish data output mode. Once, RY/#BY goes HIGH, the
device feature settings can be read by toggling #RE. The device remains in Feature Mode until another
valid command is issued to Command Register. See Figure 9-18.
Figure 9-18 Get Feature Operation
38
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.6.2 SET FEATURES (EFh)
The SET FEATURES command sets the behavior parameters by selecting a specified feature address.
To change device behavioral parameters, execute Set Feature command by writing EFh to the Command
Register, followed by the single cycle feature address. Each feature parameter (P0-P3) is latched at the
rising edge of each #WE. The RY/#BY signal will go LOW during the period of tFEAT while the four
feature parameters are stored. The Read Status (70h) command can be issued for monitoring the
progress status of this operation. The parameters are stored in device until the device goes through a
power on cycle. The device remains in feature mode until another valid command is issued to Command
Register.
Figure 9-19 Set Feature Operation
39
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.7 ONE TIME PROGRAMMABLE (OTP) area
The device has One-Time Programmable (OTP) memory area comprised of ten pages (2112 bytes/page).
This entire range of pages is functionally guaranteed. Only the OTP commands can access the OTP
area. When the device ships from Winbond, the OTP area is in an erase state (all bits equal “1”). In the
OTP area, programming or partial-page programming is done only by programming “0” bits. The OTP
area cannot be erased, therefore protecting the area only prevent further programming.
OTP area programming and protection have two separate commands. The OTP DATA PROGRAM (A0h10h) command is used to program an OTP page. Programming an entire page as one operation or up to
four partial-page programming sequences is available. Programming other OTP pages can be done in the
same way. The OTP DATA PROTECT (A5h-10h) command will permanently protected the OTP area
from further programming operations. The OTP DATA READ command (AFh-30h) can read the OTP area
with or without protection set. Note; there is no erase command for OTP area.
9.7.1 OTP DATA PROGRAM (A0h-10h)
Programming the OTP area can be done using the OTP DATA PROGRAM (A0h-10h) command. An
entire page can be programmed at once or up to four partial page programming sequences per page.
This command enables programming into the offset of an OTP page by using the two bytes of Column
Address [11:0]. If OTP area is protected by OTP DATA PROTECT command, the programming the OTP
area will not be executed, and RY/#BY goes LOW for a period of tOBSY.
To use this command sequence, the A0h command is written to Command Register. Then issue the four
address cycles that are column address of first two cycles and range page address[0B:02] of the two
remaining cycles. Then write 1 to 2112 bytes of data, followed by program confirmation command (10h) is
written to Command Register. At this point the internal controller automatically executes the algorithms for
program and verify. The RY/#BY will go LOW during the program execution for the period of (tPROG).
Program verification only detects 1’s that are not successfully programmed to 0’s.
If OTP area is not protected, RANDOM DATA INPUT commands can be used during OTP program
operations.
READ STATUS (70h) command is valid during the OTP program operation. For this operation, Status
Register Bit5 and Bit6 (I/O5 and I/O6, respectively) will follow same state as RY/#BY. If the OTP area is
protected, Status Register Bit7 (I/O7) will equal “0”; otherwise it is a “1”. After the device is in the ready
state, Status Register Bit0 (I/O0) indicates whether the operation passed or failed.
40
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 9-20 OTP Data Program
41
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.7.2 OTP DATA PROTECT (A5h-10h)
To protect the data in OTP area used the OTP DATA PROTECT (A5h-10h) command. After the OTP
area is protected, the OTP area cannot be unprotected and no additional data can be programmed to the
OTP area.
To use this command, A5h is written to the Command Register. Then issues the four address cycles with
the following address code: 00h-00h-01h-00h. Finalized by writing the protect confirmation command
(10h) to the Command Register. The RY/#BY signal will go LOW during this protection process, a period
similar with page program time (tPROG).
READ STATUS (70h) command is valid during the OTP protect operation. For this operation, Status
Register Bit5 and Bit6 (I/O5 and I/O6, respectively) will indicate same state as the RY/#BY. After the
device go to the ready state, Status Register Bit0 (I/O0) indicates whether the operation passed or failed.
Figure 9-21 OTP Data Protect
42
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.7.3 OTP DATA READ (AFh-30h)
This command can read the data from OTP pages. The read capability from OTP area is available with or
without OTP area protection.
To use this command sequence, AFh command is written to Command Register. Then issue four address
cycles comprised of the column address (first two cycles) and the range page address [0B:02] for the
remaining two cycles. Once the address is written, perform the read confirmation command (30h) to the
Command Register. The RY/#BY signal will go LOW while the OTP data is transferred from OTP area to
Data Register during the period of (tR). The RANDOM DATA OUTPUT command can use during OTP
data read operations. Read timing of OTP data read is the same as the typical PAGE READ timing.
READ STATUS and RESET command are valid during OTP data read operation. For this operation,
Status Register Bit5 and Bit6 (I/O5 and I/O6, respectively) indicate the same as the RY/#BY signal.
Additional OTP pages can be read by repeating OTP DATA READ command.
If OTP DATA READ command is followed by CACHE READ operation, the RESET command has to be
executed prior to issuing the CACHE READ commands. RESET time can be up to 5µs.
Figure 9-22 OTP Data Read
43
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.8 WRITE PROTECT
#WP pin can enable or disable program and erase commands preventing or allowing program and erase
operations. Figure 9-23 to 9-28 shows the enabling or disabling timing with #WP setup time (tWW) that is
from rising or falling edge of #WP to latch the first commands. After first command is latched, #WP pin
must not toggle until the command operation is complete and the device is in the ready state. (Status
Register Bit5 (I/O5) equal 1.
Figure 9-23 Erase Enable
Figure 9-24 Erase Disable
Figure 9-25 Program Enable
44
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 9-26 Program Disable
Figure 9-27 Program for Copy Back Enable
#WE
tWW
I/Ox
10h
85h
#WP
RY/#BY
Figure 9-28 Program for Copy Back Disable
45
Publication Release Date: June 5, 2014
Revision D
W29N01GV
9.9
BLOCK LOCK
The device has block lock feature that can protect the entire device or user can indicate a ranges of
blocks from program and erase operations. Using this feature offers increased functionality and flexibility
data protection to prevent unexpected program and erase operations. Contact to Winbond for using this
feature.
46
Publication Release Date: June 5, 2014
Revision D
W29N01GV
10. ELECTRICAL CHARACTERISTICS
10.1 Absolute Maximum Ratings
PARAMETERS
SYMBOL
Supply Voltage
CONDITIONS
VCC
Voltage Applied to Any Pin
VIN
Storage Temperature
Relative to Ground
TSTG
RANGE
UNIT
–0.6 to +4.6
V
–0.6 to +4.6
V
–65 to +150
°C
5
mA
Short circuit output current, I/Os
Table 10.1 Absolute Maximum Ratings
Notes:
1.
Specification for W29N01GV is preliminary. See preliminary designation at the end of this document.
2.
This device has been designed and tested for the specified operation ranges. Proper operation outside of these
levels is not guaranteed. Exposure to absolute maximum ratings may affect device reliability. Exposure beyond
absolute maximum ratings may cause permanent damage.
10.2 Operating Ranges
SPEC
PARAMETER
Supply Voltage
Ambient Temperature,
Operating
SYMBOL
CONDITIONS
MIN
MAX
2.7
3.6
Commercial
0
+70
Industrial
-40
+85
VCC
TA
UNIT
V
°C
Table 10.2 Operating Ranges
47
Publication Release Date: June 5, 2014
Revision D
W29N01GV
10.3 Device power-up timing
The device is designed to avoid unexpected program/erase operations during power transitions. When
the device is powered on, the system has to wait until the ready state. #WP is recommended to VIL for
preventing unexpected Program and Erase operations during power-transition until Vcc is stable. The
RY/#BY will become valid after 50µs from the Vcc ramp start, and at least 10µs after Vcc reaches
minimum Vcc level. The first command has to be a RESET command after the device is powered on.
Before issuing RESET command, the system has to wait until the RY/#BY goes HIGH, or wait at least
100µs after Vcc reaches minimum Vcc. After issuing the RESET command, the busy time is 1ms
maximum. RY/#BY polling or READ STATUS command can monitor the reset busy period. After
completing this procedure, the device is initialized and ready for the operation (See Figure 10-1).
Figure 10-1 RY/#BY Behavior During Power-On
48
Publication Release Date: June 5, 2014
Revision D
W29N01GV
10.4 DC Electrical Characteristics
SPEC
PARAMETER
SYMBOL
CONDITIONS
UNIT
MIN
TYP
MAX
-
25
35
mA
tRC= tRC MIN
Sequential Read current
Icc1
#CE=VIL
IOUT=0mA
Program current
Icc2
-
-
25
35
mA
Erase current
Icc3
-
-
25
35
mA
Standby current (TTL)
ISB1
-
-
1
mA
Standby current (CMOS)
ISB2
-
10
50
µA
#CE=VIH
#WP=0V/Vcc
#CE=Vcc – 0.2V
#WP=0V/Vcc
Input leakage current
ILI
VIN= 0 V to Vcc
-
-
±10
µA
Output leakage current
ILO
VOUT=0V to Vcc
-
-
±10
µA
Input high voltage
VIH
I/O7~0, #CE,#WE,#RE,
#WP,CLE,ALE,RY/#BY,
0.8 x Vcc
-
Vcc + 0.3
V
Input low voltage
VIL
-
-0.3
-
0.2 x Vcc
V
Output high voltage(1)
VOH
IOH=-400µA
2.4
-
-
V
Output low voltage(1)
VOL
IOL=2.1mA
-
-
0.4
V
IOL(RY/#BY)
VOL=0.4V
8
10
Output low current
mA
Table 10.3 DC Electrical Characteristics
Note:
1.
VOH and VOL may need to be relaxed if I/O drive strength is not set to full.
2.
IOL (RY/#BY) may need to be relaxed if RY/#BY pull-down strength is not set to full
49
Publication Release Date: June 5, 2014
Revision D
W29N01GV
10.5 AC Measurement Conditions
PARAMETER
SYMBOL
Input Capacitance(1), (2)
SPEC
UNIT
MIN
MAX
CIN
-
10
pF
Input/Output Capacitance(1), (2)
CIO
-
10
pF
Input Rise and Fall Times
TR/TF
-
5
ns
Input Pulse Voltages
-
0 to VCC
V
Input/Output timing Voltage
-
Vcc/2
V
Output load (1)
CL
1TTL GATE and CL=30pF
-
Table 10.4 AC Measurement Conditions
Notes:
1.
Verified on device characterization , not 100% tested
2.
Test conditions TA=25’C, f=1MHz, VIN=0V
10.6 AC timing characteristics for Command, Address and Data Input
SPEC
PARAMETER
SYMBOL
UNIT
MIN
MAX
ALE to Data Loading Time
tADL
70
-
ns
ALE Hold Time
tALH
5
-
ns
ALE setup Time
tALS
10
-
ns
#CE Hold Time
tCH
5
-
ns
CLE Hold Time
tCLH
5
-
ns
CLE setup Time
tCLS
10
-
ns
#CE setup Time
tCS
15
-
ns
Data Hold Time
tDH
5
-
ns
Data setup Time
tDS
10
-
ns
Write Cycle Time
tWC
25
-
ns
#WE High Hold Time
tWH
10
-
ns
#WE Pulse Width
tWP
12
-
ns
#WP setup Time
tWW
100
-
ns
Table 10.5 AC timing characteristics for Command, Address and Data Input
Note:
1.
tADL is the time from the #WE rising edge of final address cycle to the #WE rising edge of first data cycle.
50
Publication Release Date: June 5, 2014
Revision D
W29N01GV
10.7 AC timing characteristics for Operation
SPEC
PARAMETER
SYMBOL
UNIT
MIN
MAX
tAR
10
-
ns
tCEA
-
25
ns
tCHZ
-
30
ns
CLE to #RE Delay
tCLR
10
-
ns
#CE HIGH to Output Hold
tCOH
15
-
ns
tRCBSY
3
25
µs
Output High-Z to #RE LOW
tIR
0
-
ns
Data Transfer from Cell to Data Register
tR
-
25
µs
READ Cycle Time
tRC
25
-
ns
#RE Access Time
tREA
-
20
ns
#RE HIGH Hold Time
tREH
10
-
ns
#RE HIGH to Output Hold
tRHOH
15
-
ns
#RE HIGH to #WE LOW
tRHW
100
-
ns
#RE HIGH to Output High-Z(1)
tRHZ
-
100
ns
tRLOH
5
-
ns
#RE Pulse Width
tRP
12
-
ns
Ready to #RE LOW
tRR
20
-
ns
Reset Time (READ/PROGRAM/ERASE)(2)
tRST
-
5/10/500
µs
tWB
-
100
ns
tWHR
60
-
ns
ALE to #RE Delay
#CE Access Time
#CE HIGH to Output High-Z
(1)
Cache Busy in Cache Read mode
#RE LOW to output hold
(3)
#WE HIGH to Busy
#WE HIGH to #RE LOW
Table 10.6 AC timing characteristics for Operation
Notes:
1.
AC characteristics may need to be relaxed if I/O drive strength is not set to “full.”
Transition is measured ±200mV from steady-state voltage with load. This parameter is sampled and not 100 %
tested
2.
The first time the RESET (FFh) command is issued while the device is idle, the device will go busy for a maximum
of 1ms. Thereafter, the device goes busy for a maximum of 5μs.
3.
Do not issue new command during tWB, even if RY/#BY is ready.
51
Publication Release Date: June 5, 2014
Revision D
W29N01GV
10.8 Program and Erase Characteristics
SPEC
PARAMETER
SYMBOL
UNIT
TYP
MAX
NoP
-
4
cycles
tPROG
250
700
µs
tCBSY
3
700
µs
Busy Time for SET FEATURES /GET FEATURES
tFEAT
-
1
µs
Busy Time for program/erase at locked block
tLBSY
-
3
µs
Busy Time for OTP program when OTP is protected
tOBSY
-
30
µs
Block Erase Time
tBERS
2
10
ms
tLPROG
-
-
-
Number of partial page programs
Page Program time
Busy Time for Cache program
(1)
Last Page Program time (2)
Table 10.7 Program and Erase Characteristics
Note:
1.
tCBSY maximum time depends on timing between internal program complete and data-in.
2.
tLPROG = Last Page program time (tPROG) + Last -1 Page program time (tPROG) – Last page Address,
Command and Data load time.
52
Publication Release Date: June 5, 2014
Revision D
W29N01GV
11. TIMING DIAGRAMS
Figure 11-1 Command Latch Cycle
Figure 11-2 Address Latch Cycle
53
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-3 Data Latch Cycle
Note:
1.
Din Final = 2,111(x8)
Figure 11-4 Serial Access Cycle after Read
Figure 11-5 Serial Access Cycle after Read (EDO)
54
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-6 Read Status Operation
Figure 11-7 Page Read Operation
55
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-8 #CE Don't Care Read Operation
Figure 11-9 Random Data Output Operation
56
Publication Release Date: June 5, 2014
Revision D
W29N01GV
CLE
tCLS tCLH
tCS tCH
#CE
tWC
#WE
tCEA
ALE
tRC
#RE
tDS tDH
tWB
Col
Col
add 1
add 2
Column address
00h
00h
I/Ox
Row
add 1
Row
add 2
tR
tREA
tRR
30h
31h
Page address
m
Dout
0
tRCBSY
Dout
1
31h
Dout
Page address m
RY/#BY
Column address 0
1
Don’t care
Figure 11-10 Cache Read Operation (1/2)
CLE
tCLS tCLH
tCS tCH
#CE
#WE
tCEA
tRHW
ALE
tRC
#RE
tRR
tDS tDH
I/Ox
Dout
tREA
Dout
0
31h
tRCBSY
Dout
1
Page address
m+1
Dout
Dout
0
3Fh
tRCBSY
Dout
1
Page address
m+2
Dout
RY/#BY
Column address 0
Column address 0
Don’t care
1
Figure 11-11 Cache Read Operation (2/2)
Note:
1.
See Table 9.1 for actual value.
57
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-12 Read ID
Figure 11-13 Page Program
58
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-14 #CE Don't Care Page Program Operation
Figure 11-15 Page Program with Random Data Input
59
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-16 Copy Back
Figure 11-17 Cache Program
60
Publication Release Date: June 5, 2014
Revision D
W29N01GV
Figure 11-18 Block Erase
Figure 11-19 Reset
61
Publication Release Date: June 5, 2014
Revision D
W29N01GV
12. INVALID BLOCK MANAGEMENT
12.1 Invalid blocks
The W29N01GV may have initial invalid blocks when it ships from factory. Also, additional invalid blocks
may develop during the use of the device. Nvb represents the minimum number of valid blocks in the total
number of available blocks (See Table 12.1). An invalid block is defined as blocks that contain one or
more bad bits. Block 0, block address 00h is guaranteed to be a valid block at the time of shipment.
Parameter
Valid block number
Symbol
Min
Max
Unit
Nvb
1004
1024
blocks
Table 12.1 Valid Block Number
12.2 Initial invalid blocks
Initial invalid blocks are defined as blocks that contain one or more invalid bits when shipped from factory.
Although the device contains initial invalid blocks, a valid block of the device is of the same quality and
reliability as all valid blocks in the device with reference to AC and DC specifications. The W29N01GV
has internal circuits to isolate each block from other blocks and therefore, the invalid blocks will not affect
the performance of the entire device.
Before the device is shipped from the factory, it will be erased and invalid blocks are marked. All initial
invalid blocks are marked with non-FFh at the first byte of spare area on the 1st or 2nd page. The initial
invalid block information cannot be recovered if inadvertently erased. Therefore, software should be
created to initially check for invalid blocks by reading the marked locations before performing any program
or erase operation, and create a table of initial invalid blocks as following flow chart
Figure 12-1 flow chart of create initial invalid block table
62
Publication Release Date: June 5, 2014
Revision D
W29N01GV
12.3 Error in operation
Additional invalid blocks may develop in the device during its life cycle. Following the procedures herein is
required to guarantee reliable data in the device.
After each program and erase operation, check the status read to determine if the operation failed. In
case of failure, a block replacement should be done with a bad-block management algorithm. The system
has to use a minimum 1-bit ECC per 528 bytes of data to ensure data recovery.
Operation
Detection and recommended procedure
Erase
Status read after erase  Block Replacement
Program
Status read after program  Block Replacement
Read
Verify ECC  ECC correction
Table 12.2 Block failure
Figure 12-2 Bad block Replacement
Note:
1.
An error happens in the nth page of block A during program or erase operation.
2.
Copy the data in block A to the same location of block B which is valid block.
3.
Copy the nth page data of block A in the buffer memory to the nth page of block B
4.
Creating or updating bad block table for preventing further program or erase to block A
12.4 Addressing in program operation
The pages within the block have to be programmed sequentially from the lower order page address to the
higher order page address within the block. The lower order page is defined as the start page to program,
does not need to be page 0 in the block. Random page programming is prohibited.
63
Publication Release Date: June 5, 2014
Revision D
W29N01GV
13. PACKAGE DIMENSIONS
13.1 TSOP 48-pin 12x20
1
48
e
E
b
c
D
HD
A2
A
 L
L1
A1
Symbol
A
A1
A2
D
HD
E
b
c
e
L
L1
Y

MILLIMETER
MIN. NOM. MAX.
1.20
0.05
0.95
1.00
1.05
18.5
18.4
18.3
19.8
20.0
20.2
11.9
12.1
12.0
INCH
MIN. NOM. MAX.
0.047
0.002
0.037 0.039 0.041
0.720 0.724 0.728
0.780 0.787
0.795
0.468 0.472 0.476
0.17
0.10
0.007
0.004
0.22
0.27
0.21
0.60
0.80
0.70
0.020
5
0.024
0.031
0.028
0.004
0.10
0
0.011
0.008
0.020
0.50
0.50
0.009
Y
0
5
Figure 13-1 TSOP 48-PIN 12X20mm
64
Publication Release Date: June 5, 2014
Revision D
W29N01GV
13.2 VFBGA48Ball (8X6.5 MM2, Ball pitch:0.8mm, Ø =0.45mm)
Figure 13-2 Fine-Pitch Ball Grid Array 48-Ball (8x6.5mm)
65
Publication Release Date: June 5, 2014
Revision D
W29N01GV
14. ORDERING INFORMATION
Figure 14-1 Ordering Part Number Description
66
Publication Release Date: June 5, 2014
Revision D
W29N01GV
15. VALID PART NUMBERS
The following table provides the valid part numbers for the W29N01GV NAND Flash Memory. Please
contact Winbond for specific availability by density and package type. Winbond NAND Flash memories
use a 12-digit Product Number for ordering.
Part Numbers for Commercial Temperature:
PACKAGE TYPE
DENSITY
PRODUCT NUMBER
TOP SIDE MARKING
S
TSOP-48
1G-bit
W29N01GVSCAA
W29N01GVSCAA
D
VFBGA-48
1G-bit
W29N01GVDCAA
W29N01GVDCAA
Table 15.1 Part Numbers for Commercial Temperature
Part Numbers for Extended Temperature:
PACKAGE TYPE
DENSITY
PRODUCT NUMBER
TOP SIDE MARKING
S
TSOP-48
1G-bit
W29N01GVSIAA
W29N01GVSIAA
D
VFBGA-48
1G-bit
W29N01GVDIAA
W29N01GVDIAA
Table 15.2 Part Numbers for Industrial Temperature
Note:
1.
For Extended Temperature shipments, please contact Winbond for availability.
67
Publication Release Date: June 5, 2014
Revision D
W29N01GV
16. REVISION HISTORY
VERSION
DATE
PAGE
DESCRIPTION
A
03/04/2013
New Create Preliminary
B
7/19/2013
Modified 10.3 Device Power-up Timing
C
10/31/2013
Add VFBGA48 and remove VFBGA63
Update 15. Valid Parts Numbers
D
06/05/2014
Remove Advanced information
Table 16.1 History Table
Trademarks
Winbond is trademark of Winbond Electronics Corporation.
All other marks are the property of their respective owner.
Important Notice
Winbond products are not designed, intended, authorized or warranted for use as components in systems
or equipment intended for surgical implantation, atomic energy control instruments, airplane or spaceship
instruments, transportation instruments, traffic signal instruments, combustion control instruments, or for
other applications intended to support or sustain life. Furthermore, Winbond products are not intended for
applications wherein failure of Winbond products could result or lead to a situation where in personal
injury, death or severe property or environmental damage could occur.
Winbond customers using or selling these products for use in such applications do so at their own risk
and agree to fully indemnify Winbond for any damages resulting from such improper use or sales.
68
Publication Release Date: June 5, 2014
Revision D