S71NS064NA0BFWSY3 [SPANSION]
Memory Circuit, 4MX16, CMOS, PBGA44, 9.20 X 8 MM, 1.20 MM HEIGHT, LEAD FREE, FBGA-44;型号: | S71NS064NA0BFWSY3 |
厂家: | SPANSION |
描述: | Memory Circuit, 4MX16, CMOS, PBGA44, 9.20 X 8 MM, 1.20 MM HEIGHT, LEAD FREE, FBGA-44 静态存储器 内存集成电路 |
文件: | 总113页 (文件大小:2198K) |
中文: | 中文翻译 | 下载: | 下载PDF数据表文档文件 |
S71NS128NA0/S71NS064NA0 Based MCPs
Stacked Multi-Chip Product (MCP) MirrorBit™ Flash Memory
and PSRAM 128 Mb (8M x 16-bit) and 64 Mb (4M x 16-Bit),
110 nm CMOS 1.8 Volt-only, Multiplexed, Simultaneous Read/
Write, Burst Mode Flash Memory with
16 Mb (1M x 16-Bit) PSRAM
ADVANCE
INFORMATION
Data Sheet
Notice to Readers: This document states the current technical specifications
regarding the Spansion product(s) described herein. Each product described
herein may be designated as Advance Information, Preliminary, or Full
Production. See Notice On Data Sheet Designations for definitions.
Publication Number S71NS128_064NA0_00 Revision A Amendment 0 Issue Date April 6, 2005
This document contains information on a product under development at Spansion, LLC. The information is intended to help you evaluate this product. Do not design in
this product without contacting the factory. Spansion reserves the right to change or discontinue work on this proposed product without notice.
A d v a n c e I n f o r m a t i o n
Notice On Data Sheet Designations
Spansion LLC issues data sheets with Advance Information or Preliminary designations to advise
readers of product information or intended specifications throughout the product life cycle, in-
cluding development, qualification, initial production, and full production. In all cases, however,
readers are encouraged to verify that they have the latest information before finalizing their de-
sign. The following descriptions of Spansion data sheet designations are presented here to
highlight their presence and definitions.
Advance Information
The Advance Information designation indicates that Spansion LLC is developing one or more spe-
cific products, but has not committed any design to production. Information presented in a
document with this designation is likely to change, and in some cases, development on the prod-
uct may discontinue. Spansion LLC therefore places the following conditions upon Advance
Information content:
“This document contains information on one or more products under development at Spansion LLC. The
information is intended to help you evaluate this product. Do not design in this product without con-
tacting the factory. Spansion LLC reserves the right to change or discontinue work on this proposed
product without notice.”
Preliminary
The Preliminary designation indicates that the product development has progressed such that a
commitment to production has taken place. This designation covers several aspects of the prod-
uct life cycle, including product qualification, initial production, and the subsequent phases in the
manufacturing process that occur before full production is achieved. Changes to the technical
specifications presented in a Preliminary document should be expected while keeping these as-
pects of production under consideration. Spansion places the following conditions upon
Preliminary content:
“This document states the current technical specifications regarding the Spansion product(s) described
herein. The Preliminary status of this document indicates that product qualification has been completed,
and that initial production has begun. Due to the phases of the manufacturing process that require
maintaining efficiency and quality, this document may be revised by subsequent versions or modifica-
tions due to changes in technical specifications.”
Combination
Some data sheets will contain a combination of products with different designations (Advance
Information, Preliminary, or Full Production). This type of document will distinguish these prod-
ucts and their designations wherever necessary, typically on the first page, the ordering
information page, and pages with the DC Characteristics table and the AC Erase and Program
table (in the table notes). The disclaimer on the first page refers the reader to the notice on this
page.
Full Production (No Designation on Document)
When a product has been in production for a period of time such that no changes or only nominal
changes are expected, the Preliminary designation is removed from the data sheet. Nominal
changes may include those affecting the number of ordering part numbers available, such as the
addition or deletion of a speed option, temperature range, package type, or VIO range. Changes
may also include those needed to clarify a description or to correct a typographical error or in-
correct specification. Spansion LLC applies the following conditions to documents in this
category:
“This document states the current technical specifications regarding the Spansion product(s) described
herein. Spansion LLC deems the products to have been in sufficient production volume such that sub-
sequent versions of this document are not expected to change. However, typographical or specification
corrections, or modifications to the valid combinations offered may occur.”
Questions regarding these document designations may be directed to your local AMD or Fujitsu
sales office.
ii
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
S71NS128NA0/S71NS064NA0 Based MCPs
Stacked Multi-Chip Product (MCP) MirrorBit™ Flash Memory
and PSRAM 128 Mb (8M x 16-bit) and 64 Mb (4M x 16-Bit),
110 nm CMOS 1.8 Volt-only, Multiplexed, Simultaneous Read/
Write, Burst Mode Flash Memory with 16 Mb (1M x 16-Bit)
pSRAM
ADVANCE
INFORMATION
Data Sheet
Distinctive Characteristics
MCP Features
Power supply voltage of 1.7 V to 1.95 V
Speed
—
—
Flash = 54 MHz, 66 MHz, 80 MHz
Asynchronous access time
Flash = 70_ns, PSRAM = 70_ns
Packages:
—
—
7.7 x 6.2 x 1.0 mm 44-ball FBGA (S71NS064NA0
9.2 x 8 x 1.0 mm 44-ball FBGA (S71NS128NA0)
Operating Temperature
–25°C to +85°C
—
General Description
The S71NS Series is a product line of stacked Multi-Chip Product (MCP) packages
and consists of
One multiplexed FLASH memory die (NS128N or NS064N)
One PSRAM
The products covered by this document are listed in the table below. For details about their spec-
ifications, please refer to the individual data sheets (included in this document) for further
details.
Flash Density
128 Mb
PSRAM Density
16 Mb 32 Mb
Device
64 Mb
S71NS064NA0
S71NS128NA0
Publication Number S71NS128_064NA0_00 Revision A Amendment 0 Issue Date April 6, 2005
This document contains information on a product under development at Spansion, LLC. The information is intended to help you evaluate this product. Do not design in
this product without contacting the factory. Spansion reserves the right to change or discontinue work on this proposed product without notice.
A d v a n c e I n f o r m a t i o n
Contents
S71NS128NA0/S71NS064NA0 Based MCPs . . . . . . . . . . . . . . . . . . . . . . . . 1
Product Selector Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
MCP Block Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Connection Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
S71NS128NA0, 44-ball Very-Thin FBGA (NLB044) Pinout, NS128N + 16 PSRAM................................................................9
S71NS064NA0, 44-ball Very-Thin FBGA (NLD044) Pinout, NS064N + 16 PSRAM........................................................... 10
Input/Output Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Logic Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Order Number.........................................................................................................................................................................................12
Physical Dimension — S71NS128NA0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
NLB044, 44-Ball Very Thin Fine-Pitch Ball Grid Array (FBGA) 9.2 x 8 mm Package.......................................................13
Physical Dimension — S71NS064NA0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
NLD044, 44-Ball Very Thin Fine-pitch Ball Grid Array (BGA) 7.7 x 6.2 mm....................................................................... 14
S29NSxxxN MirrorBitTM Flash Family . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Distinctive Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Product Selector Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Block Diagram of Simultaneous Operation Circuit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Input/Output Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Logic Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Device Bus Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
VersatileIO™ (VIO) Control.................................................................................................................................................................24
Requirements for Asynchronous Read Operation (Non-Burst)..............................................................................................24
Requirements for Synchronous (Burst) Read Operation...........................................................................................................25
Continuous Burst .........................................................................................................................................................................25
8-, 16-, and 32-Word Linear Burst with Wrap Around ....................................................................................................27
8-, 16-, and 32-Word Linear Burst without Wrap Around .............................................................................................27
Programmable Wait State................................................................................................................................................................... 28
Configuration Register ......................................................................................................................................................................... 28
Handshaking Feature............................................................................................................................................................................. 28
Simultaneous Read/Write Operations with Zero Latency....................................................................................................... 28
Writing Commands/Command Sequences.................................................................................................................................... 28
Accelerated Program and Erase Operations................................................................................................................................. 28
Write Buffer Programming Operation............................................................................................................................................ 29
Autoselect Mode.....................................................................................................................................................................................30
Advanced Sector Protection and Unprotection............................................................................................................................30
Sector Protection.....................................................................................................................................................................................31
Persistent Sector Protection................................................................................................................................................................31
Persistent Protection Bit (PPB) ................................................................................................................................................32
Persistent Protection Bit Lock (PPB Lock Bit) in Persistent Sector Protection Mode ..........................................32
Dynamic Protection Bit (DYB) ................................................................................................................................................32
Persistent Sector Protection Mode Lock Bit..................................................................................................................................34
Password Sector Protection................................................................................................................................................................34
64-bit Password.......................................................................................................................................................................................34
Password Mode Lock Bit......................................................................................................................................................................34
Persistent Protection Bit Lock (PPB Lock Bit) in Password Sector Protection Mode......................................................35
Hardware Data Protection Mode......................................................................................................................................................35
Write Protect (WP#) .................................................................................................................................................................36
WP# Boot Sector Protection .............................................................................................................................................................36
Low VCC Write Inhibit ........................................................................................................................................................................36
2
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Write Pulse “Glitch” Protection........................................................................................................................................................36
Logical Inhibit............................................................................................................................................................................................36
Power-Up Write Inhibit .............................................................................................................................................................36
Lock Register............................................................................................................................................................................................36
Standby Mode .........................................................................................................................................................................................37
Automatic Sleep Mode..........................................................................................................................................................................37
RESET#: Hardware Reset Input .........................................................................................................................................................37
VCC Power-up and Power-down Sequencing .....................................................................................................................37
Output Disable Mode............................................................................................................................................................................37
SecSi™ (Secured Silicon) Sector SectorFlash Memory Region.................................................................................................37
Factory Locked: Factor SecSi Sector Programmed and Protected At the Factory .................................................38
Customer SecSi Sector ...............................................................................................................................................................38
Common Flash Memory Interface (CFI). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Command Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Reading Array Data................................................................................................................................................................................52
Set Configuration Register Command Sequence..........................................................................................................................52
Read Configuration Register Command Sequence......................................................................................................................52
Read Mode Setting .......................................................................................................................................................................53
Programmable Wait State Configuration .............................................................................................................................53
Programmable Wait State .........................................................................................................................................................53
Handshaking ...................................................................................................................................................................................54
Burst Length Configuration .......................................................................................................................................................54
Burst Wrap Around ....................................................................................................................................................................54
RDY Configuration ......................................................................................................................................................................54
RDY Polarity ..................................................................................................................................................................................55
Configuration Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Reset Command......................................................................................................................................................................................56
Autoselect Command Sequence ...................................................................................................................................................... 58
Enter SecSi™ Sector/Exit SecSi Sector Command Sequence.................................................................................................... 58
Unlock Bypass Command Sequence ......................................................................................................................................59
Program Command Sequence ............................................................................................................................................................59
Program Command Sequence ..................................................................................................................................................59
Program Command Sequence (Unlock Bypass Mode) .....................................................................................................59
Accelerated Program.............................................................................................................................................................................59
Write Buffer Programming Command Sequence........................................................................................................................ 60
Chip Erase Command Sequence........................................................................................................................................................62
Chip Erase Command Sequence .............................................................................................................................................62
Sector Erase Command Sequence.....................................................................................................................................................63
Sector Erase Command Sequence ..........................................................................................................................................63
Accelerated Sector Erase ......................................................................................................................................................... 64
Erase Suspend/Erase Resume Commands.......................................................................................................................................65
Program Suspend/Program Resume Commands ..........................................................................................................................65
Lock Register Command Set Definitions ....................................................................................................................................... 66
Password Protection Command Set Definitions.......................................................................................................................... 66
Non-Volatile Sector Protection Command Set Definitions......................................................................................................67
Global Volatile Sector Protection Freeze Command Set.......................................................................................................... 69
Volatile Sector Protection Command Set...................................................................................................................................... 69
Write Operation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
DQ7: Data# Polling................................................................................................................................................................................75
RDY: Ready .............................................................................................................................................................................................77
DQ6: Toggle Bit I....................................................................................................................................................................................77
DQ2: Toggle Bit II...................................................................................................................................................................................77
Reading Toggle Bits DQ6/DQ2..........................................................................................................................................................79
DQ5: Exceeded Timing Limits ............................................................................................................................................................79
DQ3: Sector Erase Start Timeout State Indicator.......................................................................................................................80
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
3
A d v a n c e I n f o r m a t i o n
DQ1: Write to Buffer Abort...............................................................................................................................................................80
Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82
Operating Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
DC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
CMOS Compatible.................................................................................................................................................................................83
Test Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Key to Switching Waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Switching Waveforms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86
VCC Power-up ....................................................................................................................................................................................... 86
Synchronous/Burst Read .................................................................................................................................................................... 87
Asynchronous Read ............................................................................................................................................................................. 89
Hardware Reset (RESET#)........................................................................................................................................... 90
Erase/Program Operations ................................................................................................................................................................. 91
Erase and Programming Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Device History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
S29NSxxxN Revision Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
1 M x 16 Bit Multiplexed Single Transistor RAM. . . . . . . . . . . . . . . . . . 103
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Pad Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
DC Operating Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Capacitance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
DC and Operating Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
AC Operating Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Test Conditions.....................................................................................................................................................................................105
AC Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Device Operation .................................................................................................................................................................................106
Read Access............................................................................................................................................................................................106
Read Access Timing Diagrams..........................................................................................................................................................107
Write Access..........................................................................................................................................................................................107
RMS (Reduced Memory Size)............................................................................................................................................................109
TCSR (Temperature Cotrolled Self Refresh)...............................................................................................................................109
Configuration Register Settings........................................................................................................................................................109
Configuration Register Access Timing Waveforms ...................................................................................................................109
STRAM Revision Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
S71NS128NA0/S71NS064NA0 MCP Revision Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
4
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Tables
Table 1.
Device Bus Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Address Latency for 7, 6, and 5 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Address Latency for 4 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Address Latency for 3 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Address Latency for 2 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Address/Boundary Crossing Latency for 7, 6, and 5 Wait States. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Address/Boundary Crossing Latency for 4 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Address/Boundary Crossing Latency for 3 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Address/Boundary Crossing Latency for 2 Wait States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Burst Address Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Sector Protection Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Lock Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
SecSiTM SectorSecure Sector Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
CFI Query Identification String. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
System Interface String . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Device Geometry Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Primary Vendor-Specific Extended Query. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Sector Address Table, S29NS256N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Sector Address Table, S29NS128N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Sector Address Table, S29NS064N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Programmable Wait State Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Wait States for Handshaking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Burst Length Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Configuration Register. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Device ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
Write Buffer Command Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
Command Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71
DQ6 and DQ2 Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Write Operation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Test Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
Table 13.
Table 14.
Table 15.
Table 16.
Table 17.
Table 18.
Table 19.
Table 20.
Table 21.
Table 22.
Table 23.
Table 24.
Table 25.
Table 26.
Table 27.
Table 28.
Table 29.
Table 30.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
5
A d v a n c e I n f o r m a t i o n
Figures
Figure 1.
Figure 2.
Figure 3.
Figure 4.
Program Operation............................................................................................................................60
Write Buffer Programming Operation ...................................................................................................62
Erase Operation................................................................................................................................64
PPB Program/Erase Algorithm.............................................................................................................68
Data# Polling Algorithm.....................................................................................................................76
Toggle Bit Algorithm..........................................................................................................................78
Maximum Negative Overshoot Waveform .............................................................................................82
Maximum Positive Overshoot Waveform...............................................................................................82
Test Setup .......................................................................................................................................85
Input Waveforms and Measurement Levels...........................................................................................85
VCC Power-up Diagram CLK Characterization.........................................................................................86
CLK Characterization .........................................................................................................................86
Burst Mode Read...............................................................................................................................88
Asynchronous Mode Read...................................................................................................................89
Reset Timings...................................................................................................................................90
Program Operation Timings ................................................................................................................92
Chip/Sector Erase Operations .............................................................................................................93
Accelerated Unlock Bypass Programming Timing ...................................................................................94
Data# Polling Timings (During Embedded Algorithm).............................................................................95
Toggle Bit Timings (During Embedded Algorithm)..................................................................................95
8-, 16-, and 32-Word Linear Burst Address Wrap Around........................................................................96
Latency with Boundary Crossing..........................................................................................................96
Back-to-Back Read/Write Cycle Timings ...............................................................................................97
Read Cycle Timing Waveform (1) (WE# = VIH)....................................................................................107
Read Cycle Timing Waveform (2) (WE# = VIH)....................................................................................107
Write Cycle Timing Waveform (1) (OE# = VIH)....................................................................................108
Write Cycle Timing Waveform (2) (OE# = VIH)....................................................................................108
Power Up Timing Waveform..............................................................................................................109
Configuration Register Access Timing Waveforms—Read Cycle ..............................................................109
Configuration Register Access Timing Waveforms—Write Cycle..............................................................110
Figure 5.
Figure 6.
Figure 7.
Figure 8.
Figure 9.
Figure 10.
Figure 11.
Figure 12.
Figure 13.
Figure 14.
Figure 15.
Figure 16.
Figure 17.
Figure 18.
Figure 19.
Figure 20.
Figure 21.
Figure 22.
Figure 23.
Figure 24.
Figure 25.
Figure 26.
Figure 27.
Figure 28.
Figure 29.
Figure 30.
6
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Product Selector Guide
Device/
Model#
Flash
Density
pSRAM
Density
Flash Speed
(MHz)
PSRAM Speed
(ns)
Supplier
Package
S71NS064NA0-MF
S71NS064NA0-ME
S71NS064NA0-MD
S71NS064NA0-MZ
S71NS064NA0-MY
S71NS064NA0-MW
S71NS064NA0-MP
S71NS064NA0-MN
S71NS064NA0-MM
S71NS128NA0-SF
S71NS128NA0-SE
S71NS128NA0-SD
S71NS128NA0-SZ
S71NS128NA0-SY
S71NS128NA0-SW
S71NS128NA0-SP
S71NS128NA0-SN
S71NS128NA0-SM
54
66
80
54
66
80
54
66
80
54
66
80
54
66
80
54
66
80
PSRAM Type 1
64 Mb
16 Mb
70
PSRAM Type 2
PSRAM Type 3
PSRAM Type 1
PSRAM Type 2
PSRAM Type 3
NLD044
128 Mb
16 Mb
70
NLB044
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
7
A d v a n c e I n f o r m a t i o n
MCP Block Diagrams
RDY
CLK
RESET#
F-WP#
ACC
Flash
Memory
CE#
(S29NS128J
or
OE#
WE#
S29NS064J)
AVD#
A19 – A16
A20
A/DQ15 – A/DQ0
A21
A22
16 Mb
LB#
UB#
A21/LB#
(Note 1) A22/UB#
pSRAM
CS#
Notes:
1. A22 available for 128 Mb Flash only
2. A15 – A0 are multiplexed with DQ15 – DQ0.
3. indicates the highest order address bit.
A
MAX
8
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Connection Diagrams
S71NS128NA0, 44-ball Very-Thin FBGA (NLB044) Pinout, NS128N + 16 PSRAM
Top View, Balls Facing Down
NC
NC
A1
A2
A3
A4
A5
VCC WE# ACC A19 A17 UB#
B5 B6 B7 B8 B9 B10
A20 AVD# NC RESET# CS# A18 CE# GND
C3 C4 C5 C6 C7 C8 C9 C10
A6
A7
A8
A9
A10
RDY A21/LB#GND CLK
B1
B2
B3
B4
VCC
A16
C1
C2
GND A/DQ7 A/DQ6 A/DQ13A/DQ12A/DQ3 A/DQ2 A/DQ9 A/DQ8 OE#
D1 D2 D3 D4 D5 D6 D7 D8 D9 D10
A/DQ15 A/DQ14 GND A/DQ5 A/DQ4A/DQ11A/DQ10 VCC A/DQ1 A/DQ0
NC
NC
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
9
A d v a n c e I n f o r m a t i o n
S71NS064NA0, 44-ball Very-Thin FBGA (NLD044) Pinout, NS064N + 16 PSRAM
Top View, Balls Facing Down
NC
NC
NC
NC
A1
A2
A3
A4
A5
A6
A7
A8
A9
A17 A22/UB#
B9 B10
CE# GND
C9 C10
A10
RDY A21/LB# GND CLK
VCC WE# ACC A19
B1
B2
B3
A20 AVD# NC RESET# CS#
C3 C4 C5 C6 C7
B4
B5
B6
B7
B8
VCC
A16
A18
C1
C2
C8
GND A/DQ7 A/DQ6 A/DQ13 A/DQ12 A/DQ3 A/DQ2 A/DQ9 A/DQ8 OE#
D1 D2 D3 D4 D5 D6 D7 D8 D9 D10
A/DQ15 A/DQ14 GND A/DQ5 A/DQ4 A/DQ11 A/DQ10 VCC A/DQ1 A/DQ0
NC
NC
NC
NC
10
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Input/Output Descriptions
A22/UB# = Address Inputs, pSRAM Upper Byte Control (A22 available for 128 Mb Flash)
A21/LB# = Address Inputs, pSRAM Lower Byte Control
A20–A16 = Address Inputs
A/DQ15–A/DQ0 = Multiplexed Address/Data input/output
CE# = Chip Enable Input. Asynchronous relative to CLK for the Burst mode.
OE# = Output Enable Input. Asynchronous relative to CLK for the Burst mode.
WE# = Write Enable Input.
V
=
=
=
=
Device Power Supply (1.70 V – 1.95 V).
Input/Output Power Supply (1.70 V – 1.95 V)
Ground
CC
V
CCQ
V
SS
V
Input/Output Ground
SSQ
NC = No Connect; not connected internally
RDY
Ready output; indicates the status of the Burst read.
=
V
V
= data invalid
= data valid
OL
OH
CLK
The first rising edge of CLK in conjunction with AVD# low latches address input and activates burst mode
operation. After the initial word is output, subsequent rising edges of CLK increment the internal address
counter. CLK should remain low during asynchronous access.
=
=
AVD#
Address Valid input. Indicates to device that the valid address is present on the address inputs (address
bits A15 – A0 are multiplexed, address bits Amax – A16 are address only).
V
= for asynchronous mode, indicates valid address; for burst mode, causes starting address to be
IL
latched on rising edge of CLK.
V
= device ignores address inputs
IH
RESET# = Hardware reset input. V = device resets and returns to reading array data
IL
WP#
Hardware write protect input. V = disables writes to SA258 – SA257 (S29NS256N),
IL
=
=
SA130 – SA129 (S29NS128N) or SA66– SA65 (S29NS064N). Should be at V for all other conditions.
IH
ACC
At 9 V, accelerates programming; automatically places device in unlock bypass mode. At V , disables
IL
program and erase functions. Should be at V for all other conditions.
IH
Logic Symbol
*A22/UB#
A21/LB#
A20–A16
16
A/DQ15 – A/DQ0
CLK
CE#
CS#
OE#
RDY
WE#
RESET#
AVD#
WP#
ACC
Note: *A22 available for 128Mb Flash only
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
11
A d v a n c e I n f o r m a t i o n
Ordering Information
The order number (Valid Combination) is formed by the following:
Order Number
S71NS
128
N
A0
BF
W
A
B
0
Packing Type
0
2
3
=
=
=
Tray
7” Tape and Reel
13” Tape and Reel
Model Number
F
E
D
Z
Y
W
P
=
=
=
=
=
=
=
=
=
PSRAM Type 1, 54MHz Flash
PSRAM Type 1, 66MHz Flash
PSRAM Type 1, 80MHz Flash
PSRAM Type 2, 54MHz Flash
PSRAM Type 2, 66MHz Flash
PSRAM Type 2, 80MHz Flash
PSRAM Type 3, 54MHz Flash
PSRAM Type 3, 66MHz Flash
PSRAM Type 3, 80MHz Flash
N
M
Package Modifier
S
=
44-ball, 8 x 9.2 x 1.2 mm,
FBGA MCP Multi-Chip Package (S71NS128NA0)
44-ball, 6.2 x 7.7 x 1.2 mm,
M
=
FBGA MCP Multi-Chip Package (S71NS064NA0)
Temperature Range
W
= Wireless (–25°C to +85°C)
Package Type
BF = Very Fine-pitch BGA Pb-free package
pSRAM Density
A0 = 16 Mb (1M x 16-bit)
Process Technology
N
=
110 nm, MirrorBit•M Technology
Code Flash Density
128= 128 Mb
064= 65 Mb
Product Family
S71NS Multi-chip Product (MCP)
1.8 V Multiplexed, SRW, Burst Mode Code Flash
Please use the standard format for the Ordering Information with the above data — this for-
mat is only for the purpose of identifying the variable parameters.
Valid Combinations
S71NS
Notes:
128, 64
N
A0
BF
W
S, M
F, E, D, Z, Y, W, P, N, M
0, 2, 3
1. Type 0 is standard. Specify other options as required.
2. BGA package marking omits leading “S” and packing type designator from ordering part number.
Valid Combinations
Valid Combinations list configurations planned to be supported in volume for this device. Consult
your local sales office to confirm availability of specific valid combinations and to check on newly
released combinations.
12
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Physical Dimension — S71NS128NA0
NLB044, 44-Ball Very Thin Fine-Pitch Ball Grid Array (FBGA) 9.2 x 8 mm Package
A
D
A1 CORNER
INDEX MARK
D1
A1 CORNER
10
10
9
8
7
6
5
4
3
2
1
NF2
NF1
e
A
B
C
D
E1
E
SE
7
1.00
NF4
NF3
B
1.00
SD
7
φb
6
0.10
C
A2
C
A
φ0.05
φ0.15
M
M
C
C
A B
A1
0.08
C
SEATING PLANE
NOTES:
1. DIMENSIONING AND TOLERANCING PER ASME Y14.5M-1994.
2. ALL DIMENSIONS ARE IN MILLIMETERS.
PACKAGE
JEDEC
NLB 044
N/A
3. BALL POSITION DESIGNATION PER JESD 95-1, SPP-010 (EXCEPT
AS NOTED).
8.00 mm x 9.20 mm NOM
PACKAGE
NOTE
4.
e REPRESENTS THE SOLDER BALL GRID PITCH.
SYMBOL
MIN
1.05
0.20
0.85
7.90
9.10
NOM
---
MAX
1.20
---
5. SYMBOL "MD" IS THE BALL ROW MATRIX SIZE IN THE
"D" DIRECTION.
A
A1
A2
D
OVERALL THICKNESS
BALL HEIGHT
SYMBOL "ME" IS THE BALL COLUMN MATRIX SIZE IN THE
"E" DIRECTION.
---
0.91
0.97
8.10
9.30
BODY THICKNESS
BODY SIZE
N IS THE TOTAL NUMBER OF SOLDER BALLS.
8.00
6
7
DIMENSION "b" IS MEASURED AT THE MAXIMUM BALL
DIAMETER IN A PLANE PARALLEL TO DATUM C.
E
9.20
BODY SIZE
D1
E1
MD
ME
N
4.50 BSC.
1.50 BSC.
10
BALL FOOTPRINT
BALL FOOTPRINT
SD AND SE ARE MEASURED WITH RESPECT TO DATUMS
A AND B AND DEFINE THE POSITION OF THE CENTER
SOLDER BALL IN THE OUTER ROW.
ROW MATRIX SIZE D DIRECTION
ROW MATRIX SIZE E DIRECTION
TOTAL BALL COUNT
WHEN THERE IS AN ODD NUMBER OF SOLDER BALLS IN
THE OUTER ROW PARALLEL TO THE D OR E DIMENSION,
RESPECTIVELY, SD OR SE = 0.000.
4
44
WHEN THERE IS AN EVEN NUMBER OF SOLDER BALLS IN
THE OUTER ROW, SD OR SE = e/2
φb
0.25
0.30
0.35
BALL DIAMETER
e
0.50 BSC.
0.25 BSC.
---
BALL PITCH
8. NOT USED.
SD / SE
SOLDER BALL PLACEMENT
DEPOPULATED SOLDER BALLS
9. "+" INDICATES THE THEORETICAL CENTER OF DEPOPULATED
BALLS.
10 A1 CORNER TO BE IDENTIFIED BY CHAMFER, LASER OR INK
MARK, METALLIZED MARK INDENTATION OR OTHER MEANS.
3298 \ 16-038.22a1
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
13
A d v a n c e I n f o r m a t i o n
Physical Dimension — S71NS064NA0
NLD044, 44-Ball Very Thin Fine-pitch Ball Grid Array (BGA) 7.7 x 6.2 mm
A
D
D1
+0.20
-0.50
A1 CORNER
1.00
C
A1 ID.
10
9
8
7
6
5
4
3
2
1
0.10
2X
0.50 REF
NF2
NF1
e
0.50 REF
A
B
C
D
E
B
E1
SE
1.00
7
NF4
NF3
1.00
SD
B
7
ƒÓb
6
0.10 C
2X
φ 0.05
φ 0.15
M
C
TOP VIEW
M
C A
BOTTOM VIEW
0.10
C
A2
A
0.08 C
A1
SEATING PLANE
C
SIDE VIEW
NOTES:
PACKAGE
JEDEC
NLD 044
N/A
1. DIMENSIONING AND TOLERANCING METHODS PER
ASME Y14.5M-1994.
2. ALL DIMENSIONS ARE IN MILLIMETERS.
D x E
7.70 mm x 6.20 mm
PACKAGE
3. BALL POSITION DESIGNATION PER JEP95, SECTION 4.3,
SPP-010.
SYMBOL
A
MIN
1.05
NOM
---
MAX
NOTE
4.
e REPRESENTS THE SOLDER BALL GRID PITCH.
1.20
---
PROFILE
5. SYMBOL "MD" IS THE BALL MATRIX SIZE IN THE "D"
DIRECTION.
A1
A2
D
0.20
0.85
---
BALL HEIGHT
0.91
0.97
BODY THICKNESS
BODY SIZE
SYMBOL "ME" IS THE BALL MATRIX SIZE IN THE
"E" DIRECTION.
7.70 BSC.
6.20 BSC.
4.50 BSC.
1.50 BSC.
10
E
BODY SIZE
n IS THE NUMBER OF POPULTED SOLDER BALL POSITIONS
FOR MATRIX SIZE MD X ME.
D1
E1
MD
ME
n
MATRIX FOOTPRINT
MATRIX FOOTPRINT
MATRIX SIZE D DIRECTION
MATRIX SIZE E DIRECTION
BALL COUNT
6
7
DIMENSION "b" IS MEASURED AT THE MAXIMUM BALL
DIAMETER IN A PLANE PARALLEL TO DATUM C.
SD AND SE ARE MEASURED WITH RESPECT TO DATUMS A
AND B AND DEFINE THE POSITION OF THE CENTER SOLDER
BALL IN THE OUTER ROW.
4
44
WHEN THERE IS AN ODD NUMBER OF SOLDER BALLS IN THE
OUTER ROW SD OR SE = 0.000.
Øb
eE
eD
SE
0.25
0.30
0.35
BALL DIAMETER
BALL PITCH
0.50 BSC.
0.50 BSC
0.25 BSC.
WHEN THERE IS AN EVEN NUMBER OF SOLDER BALLS IN THE
OUTER ROW, SD OR SE = e/2
BALL PITCH
SOLDER BALL PLACEMENT
8. "+" INDICATES THE THEORETICAL CENTER OF DEPOPULATED
BALLS.
DEPOPULATED SOLDER BALLS
9. A1 CORNER TO BE IDENTIFIED BY CHAMFER, LASER OR INK
MARK, METALLIZED MARK INDENTATION OR OTHER MEANS.
10. OUTLINE AND DIMENSIONS PER CUSTOMER REQUIREMENT.
3488 \ 16-038.22 \ 3.28.5
14
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
S29NSxxxN MirrorBitTM Flash Family
S29NS256N, S29NS128N, S29NS064N
256/128/64 Megabit (16/8/4M x 16-bit), CMOS 1.8 Volt-only
Simultaneous Read/Write, Multiplexed, Burst Mode
Flash Memory
ADVANCE
INFORMATION
Data Sheet
Distinctive Characteristics
—
—
Typical effective word programming time of 6 µs
utilizing a 32-Word Write Buffer at ACC (VPP) Level
Typical sector erase time of 350 ms for 16 Kword
sectors and 800 ms sector erase time for 64 Kword
sectors
Single 1.8 volt read, program and erase (1.70
to 1.95 volt)
VersatileIO™ Feature
—
Device generates data output voltages and tolerates
data input voltages as determined by the voltage on
the VCCQ pin
Security features
—
1.8 V compatible I/O signals
Multiplexed Data and Address for reduced
Persistent Sector Protection
—
A command sector protection method to lock
combinations of individual sectors to prevent
program or erase operations within that sector
Sectors can be locked and unlocked in-system at VCC
level
I/O count
—
—
A15–A0 multiplexed as DQ15–DQ0
Addresses are latched by AVD# control input when
CE# low
—
Simultaneous Read/Write operation
Password Sector Protection
—
Data can be continuously read from one bank while
executing erase/program functions in other bank
Zero latency between read and write operations
—
A sophisticated sector protection method to lock
combinations of individual sectors to prevent
program or erase operations within that sector using
a user-defined 64-bit password
—
Read access times at 80/66/54 MHz
—
—
—
Burst access times of 9/11/13.5 ns
at industrial temperature range
Asynchronous random access times
of 80/80/80 ns
Synchronous random access times
of 80/80/80 ns
Hardware Sector Protection
—
—
WP# protects the two highest sectors
All sectors locked when ACC (VPP) = VIL
Handshaking feature
—
Provides host system with minimum possible latency
by monitoring RDY
Burst length
Supports Common Flash Memory
Interface (CFI)
Software command set compatible with
JEDEC 42.4 standards
—
—
Continuous linear burst
8/16/32 word linear burst with wrap around
—
8/16/32 word linear burst without wrap around
SecSiTM (Secured Silicon) Sector region
—
Backwards compatible with Am29F and Am29LV
families
—
256 words accessible through a command sequence,
128 words for the Factory SecSi Sector and 128
words for the Customer SecSi Sector.
Manufactured on 110 nm MirrorBitTM process
technology
Power dissipation (typical values, 8 bits
Cycling endurance: 100,000 cycles per sector
switching, CL = 30 pF) @80 MHz
typical
—
—
—
—
Continuous Burst Mode Read: 35 mA
Simultaneous Operation: 50 mA
Program/Erase: 19 mA
Data retention: 20 years typical
Data# Polling and toggle bits
—
Provides a software method of detecting program
and erase operation completion
Standby mode: 20 µA
Sector Architecture
Erase Suspend/Resume
—
—
Four 16 K word sectors in upper-most address range
—
Suspends an erase operation to read data from, or
program data to, a sector that is not being erased,
then resumes the erase operation
Two-hundred-fifty-five 64Kword sectors
(S29NS256N), One-hundred-twenty-seven 64
Kword sectors (S29NS128N), or Sixty-three 64
Kword sectors (S29NS064N)
Program Suspend/Resume
—
Suspends a programming operation to read data
from a sector other than the one being programmed,
then resume the programming operation
—
—
Sixteen banks (S29NS128N and S29NS256N)
Eight banks (S29NS064N)
Unlock Bypass Program command
Typical word programming time of 40 µs
—
Reduces overall programming time when issuing
multiple program command sequences
Publication Number S71NS128_064NA0_00 Revision A Amendment 0 Issue Date April 6, 2005
This document contains information on one or more products under development at Spansion LLC. The information is intended to help you evaluate this product. Do not
design in this product without contacting the factory. Spansion LLC reserves the right to change or discontinue work on this proposed product without notice.
A d v a n c e I n f o r m a t i o n
General Description
The S29NS256N, S29NS128N, and S29NS064N are 256 Mb, 128 Mb, and 64 Mb (respectively)
1.8 Volt-only, Simultaneous Read/Write, Burst Mode Flash memory devices, organized as
16,777,216, 8,388,608, and 4,194,304 words of 16 bits each. These devices use a single VCC of
1.70 to 1.95 V to read, program, and erase the memory array. A 9.0-volt ACC, also referred to
as VPP in older documents, may be used for faster program performance if desired. These devices
can also be programmed in standard EPROM programmers.
The devices are offered at the following speeds:
Clock Speed
80 MHz
Burst Access (ns)
Synch. Initial Access (ns)
Asynch. Initial Access (ns)
Output Loading
9
80
80
80
80
80
80
66 MHz
11.0
13.5
30 pF
54 MHz
The devices operate within the temperature range of –25 °C to +85 °C, and are offered in Very
Thin FBGA packages.
Simultaneous Read/Write Operations with Zero Latency
The Simultaneous Read/Write architecture provides simultaneous operation by dividing the
memory space into either sixteen banks (NS256N or NS128N) or eight banks (NS064N). The de-
vice allows a host system to program or erase in one bank, then immediately and simultaneously
read from another bank, with zero latency. This releases the system from waiting for the comple-
tion of program or erase operations.The devices are structured as shown in the following tables:
S29NS256N
Bank 0-14 Sectors Bank 15 Sectors
S29NS128N
Bank 0-14 Sectors Bank 15 Sectors
Quantity
Size
Quantity
Size
Quantity
Size
Quantity
Size
4
16 Kwords
64 Kwords
4
7
16 Kwords
64 Kwords
240
64 Kwords
120
64 Kwords
15
240 Mb total
16 Mb total
120 Mb total
8 Mb total
16
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
S29NS064N
Bank 0-6 Sectors
Bank 7 Sectors
Quantity
Size
Quantity
Size
4
7
16 Kwords
64 Kwords
56
64 Kwords
56 Mb total
8 Mb total
The VersatileIO™ (VIO) control allows the host system to set the voltage levels that the device
generates at its data outputs and the voltages tolerated at its data inputs to the same voltage
level that is asserted on the VCCQ pin.
The devices use Chip Enable (CE#), Write Enable (WE#), Address Valid (AVD#) and Output En-
able (OE#) to control asynchronous read and write operations. For burst operations, the devices
additionally require Ready (RDY) and Clock (CLK). This implementation allows easy interface with
minimal glue logic to microprocessors/microcontrollers for high performance read operations.
The devices offer complete compatibility with the JEDEC 42.4 single-power-supply Flash
command set standard. Commands are written to the command register using standard mi-
croprocessor write timings. Reading data out of the device are similar to reading from other Flash
or EPROM devices.
The host system can detect whether a program or erase operation is complete by using the device
status bit DQ7 (Data# Polling) and DQ6/DQ2 (toggle bits). After a program or erase cycle has
been completed, the device automatically returns to reading array data.
The sector erase architecture allows memory sectors to be erased and reprogrammed without
affecting the data contents of other sectors. The devices are fully erased when shipped from the
factory.
Hardware data protection measures include a low VCC detector that automatically inhibits write
operations during power transitions. The devices also offer three types of data protection at the
sector level. Persistent Sector Protection provides in-system, command-enabled protection of
any combination of sectors using a single power supply at VCC. Password Sector Protection
prevents unauthorized write and erase operations in any combination of sectors through a user-
defined 64-bit password. When at VIL, WP# locks the highest two sectors. Finally, when ACC is
at VIL, all sectors are locked.
The devices offer two power-saving features. When addresses have been stable for a specified
amount of time, the device enters the automatic sleep mode. The system can also place the
device into the standby mode. Power consumption is greatly reduced in both modes.
Device programming occurs by executing the program command sequence. This initiates the Em-
bedded Program algorithm - an internal algorithm that automatically times the program pulse
widths and verifies proper cell margin. The Unlock Bypass mode facilitates faster program times
by requiring only two write cycles to program data instead of four. Additionally, Write Buffer Pro-
gramming is available on this family of devices. This feature provides superior programming
performance by grouping locations being programmed.
Device erasure occurs by executing the erase command sequence. This initiates the Embedded
Erase algorithm - an internal algorithm that automatically preprograms the array (if it is not al-
ready fully programmed) before executing the erase operation. During erase, the device
automatically times the erase pulse widths and verifies proper cell margin.
The Program Suspend/Program Resume feature enables the user to put program on hold to
read data from any sector that is not selected for programming. If a read is needed from the Per-
sistent Protection area, Dynamic Protection area, or the CFI area, after an program suspend, then
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
17
A d v a n c e I n f o r m a t i o n
the user must use the proper command sequence to enter and exit this region. The program sus-
pend/resume functionality is also available when programming in erase suspend (1 level depth
only).
The Erase Suspend/Erase Resume feature enables the user to put erase on hold to read data
from, or program data to, any sector that is not selected for erasure. True background erase can
thus be achieved. If a read is needed from the Persistent Protection area, Dynamic Protection
area, or the CFI area, after an erase suspend, then the user must use the proper command se-
quence to enter and exit this region.
The hardware RESET# pin terminates any operation in progress and resets the internal state
machine to reading array data. The RESET# pin may be tied to the system reset circuitry. A sys-
tem reset would thus also reset the device, enabling the system microprocessor to read boot-up
firmware from the Flash memory device.
The host system can detect whether a memory array program or erase operation is complete by
using the device status bit DQ7 (Data# Polling), DQ6/DQ2 (toggle bits), DQ5 (exceeded timing
limit), DQ3 (sector erase start timeout state indicator), and DQ1 (write to buffer abort). After a
program or erase cycle has been completed, the device automatically returns to reading array
data.
The sector erase architecture allows memory sectors to be erased and reprogrammed without
affecting the data contents of other sectors. The device is fully erased when shipped from
the factory.
Hardware data protection measures include a low VCC detector that automatically inhibits write
operations during power transitions. The device also offers two types of data protection at the
sector level. When at VIL, WP# locks the two outermost boot sectors at the top of memory.
When the ACC pin = VIL, the entire flash memory array is protected.
Spansion LLC Flash technology combines years of Flash memory manufacturing experience to
produce the highest levels of quality, reliability and cost effectiveness. The device electrically
erases all bits within a sector. The data is programmed using hot electron injection.
18
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Product Selector Guide
Description
S29NS256N, S29NS128N, S29NS064N
Burst Frequency
80 MHz
66 MHz
80
54 MHz
80
Max Initial Synchronous Access Time, ns (TIACC
)
80
9
Max Burst Access Time, ns (TBACC
Max Asynchronous Access Time, ns (TACC
Max CE# Access Time, ns (TCE
)
11.0
13.5
)
80
9
80
80
)
Max OE# Access Time, ns (TOE
)
11.0
13.5
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
19
A d v a n c e I n f o r m a t i o n
Block Diagram
VCCQ
VCC
VSS
A/DQ15–A/DQ0
RDY
Buffer
RDY
Erase Voltage
Generator
Input/Output
Buffers
State
WE#
RESET#
ACC(Note 2)
Control
Command
Register
PGM Voltage
Generator
WP#
Data
Latch
Chip Enable
Output Enable
Logic
CE#
OE#
Y-Decoder
Y-Gating
VCC
Detector
Timer
Cell Matrix
X-Decoder
Burst
State
Control
Burst
Address
Counter
AVD#
CLK
Amax–A0
A/DQ15–A/DQ0
Amax–A16
Notes:
1. Amax indicates the highest order address bit. Amax equals A23 for NS256N, A22 for NS128N and A21 for
NS064N.
2. ACC is the same pin as the pin referred to as VPP in older documentation.
20
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Block Diagram of Simultaneous Operation Circuit
V
CCQ
V
V
CC
SS
V
ssq
Bank Address
DQ15–DQ0
Bank 0
A
–A0
max
X-Decoder
OE#
Bank Address
DQ15–DQ0
Bank 1
(Note 4)
A
CC
X-Decoder
A
–A0
max
RESET#
WE#
OE#
STATE
DQ15–
DQ0
CONTROL
&
COMMAND
REGISTER
CE#
Status
AVD#
CLK
RDY
Control
WP#
A
–A0
DQ15–DQ0
max
OE#
X-Decoder
Bank n-1
DQ15–DQ0
Bank Address
A
–A0
max
A
–A0
max
OE#
X-Decoder
Bank n
Bank Address
DQ15–DQ0
Notes:
1. A15–A0 are multiplexed with DQ15–DQ0.
2. Amax indicates the highest order address bit. A23 (NS256N), A22 (NS128N), A21 (NS064N).
3. n = 15 for NS256N, NS128N, and n = 7 for NS064N.
4. ACC is the same pin as the pin referred to as VPP in older documentation.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
21
A d v a n c e I n f o r m a t i o n
Input/Output Descriptions
A23–A16
=
=
=
=
Address Inputs, S29NS256N
Address Inputs, S29NS128N
Address Inputs, S29NS064N
Multiplexed Address/Data input/output
A22–A16
A21–A16
A/DQ15–A/DQ0
CE#
OE#
=
=
Chip Enable Input. Asynchronous relative to CLK for
the Burst mode.
Output Enable Input. Asynchronous relative to CLK
for the Burst mode.
WE#
VCC
=
=
=
Write Enable Input.
Device Power Supply (1.70 V–1.95 V).
VCCQ
Input/Output Power Supply
(1.70 V–1.95 V).
VSS
VSSQ
NC
=
=
=
=
Ground
Input/Output Ground
No Connect; not connected internally
RDY
Ready output; indicates the status of the Burst read.
VOL= data invalid.
VOH = data valid.
CLK
=
The first rising edge of CLK in conjunction with AVD#
low latches address input and activates burst mode
operation. After the initial word is output,
subsequent rising edges of CLK increment the
internal address counter. CLK should remain low
during asynchronous access.
AVD#
=
Address Valid input. Indicates to device that the valid
address is present on the address inputs (address
bits A15–A0 are multiplexed, address bits Amax–A16
are address only).
VIL = for asynchronous mode, indicates valid
address; for burst mode, causes starting address to
be latched on rising edge of CLK.
VIH= device ignores address inputs
RESET#
WP#
=
=
Hardware reset input. VIL= device resets and returns
to reading array data
Hardware write protect input. VIL = disables writes to
SA257–258 (S29NS256N), SA129–130
(S29NS128N) or SA65–66 (S29NS064N). Should be
at VIH for all other conditions.
ACC (VPP
)
=
At 9 V, accelerates programming; automatically
places device in unlock bypass mode. At VIL, disables
program and erase functions. Should be at VIH for all
other conditions.
22
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Logic Symbol
5 to 8
A
–A16
16
max
A/DQ15–
A/DQ0
CLK
CE#
OE#
WE#
RESET#
AVD#
WP#
RDY
ACC
A
indicates the highest order address bit.
max
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
23
A d v a n c e I n f o r m a t i o n
Device Bus Operations
This section describes the requirements and use of the device bus operations, which are initiated
through the internal command register. The command register itself does not occupy any addres-
sable memory location. The register is composed of latches that store the commands, along with
the address and data information needed to execute the command. The contents of the register
serve as inputs to the internal state machine. The state machine outputs dictate the function of
the device. Table 1 lists the device bus operations, the inputs and control levels they require, and
the resulting output. The following subsections describe each of these operations in further detail.
Table 1. Device Bus Operations
A/DQ15–
Operation
CE#
OE#
WE#
A
–16
0
RESET#
CLK
L
AVD#
max
Asynchronous Read
Write
L
L
L
H
X
X
H
L
Addr In
I/O
H
H
H
L
Addr In
I/O
H/L
H/L
X
Standby (CE#)
H
X
X
X
X
X
HIGH Z
HIGH Z
X
X
Hardware Reset
Burst Read Operations
Load Starting Burst Address
L
L
H
L
H
H
Addr In
X
Addr In
H
H
Advance Burst to next address with
appropriate Data presented on the Data Bus
Burst
Data Out
H
Terminate current Burst read cycle
H
X
X
X
H
H
X
X
HIGH Z
HIGH Z
H
L
X
X
Terminate current Burst read cycle via RESET#
X
Terminate current Burst read cycle and start
new Burst read cycle
L
H
H
X
I/O
H
Legend: L = Logic 0, H = Logic 1, X = Don’t Care.
VersatileIO™ (V ) Control
IO
The VersatileIO (VIO) control allows the host system to set the voltage levels that the device gen-
erates at its data outputs and the voltages tolerated at its data inputs to the same voltage level
that is asserted on the VCCQ pin.
Requirements for Asynchronous Read Operation (Non-Burst)
To read data from the memory array, the system must assert a valid address on Amax–A16 and
A/DQ15–A/DQ0 while AVD# and CE# are at VIL. WE# should remain at VIH. Note that CLK must
remain at VIL during asynchronous read operations. The rising edge of AVD# latches the address,
after which the system can drive OE# to VIL. The data will appear on A/DQ15–A/DQ0. (See Figure
14, on page 74.) Since the memory array is divided into banks, each bank remains enabled for
read access until the command register contents are altered.
Address access time (tACC) is equal to the delay from stable addresses to valid output data. The
chip enable access time (tCE) is the delay from the stable addresses and stable CE# to valid data
at the outputs. The output enable access time (tOE) is the delay from the falling edge of OE# to
valid data at the output.
The internal state machine is set for reading array data upon device power-up, or after a hardware
reset. This ensures that no spurious alteration of the memory content occurs during the power
transition.
24
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Requirements for Synchronous (Burst) Read Operation
The device is capable of seven different burst read modes: continuous burst read; 8-, 16-, and
32-word linear burst reads with wrap around; and 8-, 16-, and 32-word linear burst reads without
wrap around.
Continuous Burst
When the device first powers up, it is enabled for asynchronous read operation. The device is au-
tomatically enabled for burst mode and addresses are latched on the first rising edge of CLK input,
while AVD# is held low for one clock cycle.
Prior to activating the clock signal, the system should determine how many wait states are desired
for the initial word (tIACC) of each burst session. The system would then write the Set Configura-
tion Register command sequence.
The initial word is output tIACC after the rising edge of the first CLK cycle. Subsequent words are
output tBACC after the rising edge of each successive clock cycle, which automatically increments
the internal address counter. Note that the device has a fixed internal address boundary
that occurs every 128 words, starting at address 00007Fh. The transition from the
highest address 7FFFFFh to 000000h is also a boundary crossing. During a boundary
crossing, there is a no additional latency between the valid read at address 00007F and the valid
read at address 000080 (or between addresses offset from these values by the same multiple of
128 words) for frequencies equal to or lower than 66 Mhz. For frequencies higher than 66 Mhz,
there is a latency of 1 cycle.
During the time the device is outputting data with the starting burst address not divisible by four,
additional waits are required. The RDY output indicates this condition to the system by
deasserting.
Table 2 through Table 5 shows the address latency as a function of variable wait states.
Table 2. Address Latency for 7, 6, and 5 Wait States
Word
0
1
2
3
D0
D1
D2
D3
D1
D2
D2
D3
D3
D4
D4
D4
D4
D5
D5
D5
D5
D6
D6
D6
D6
D7
D7
D7
D7
D8
D8
D8
D8
7, 6, and 5
ws
1 ws
1 ws
1 ws
D3
1 ws
1 ws
1 ws
Table 3. Address Latency for 4 Wait States
Word
0
1
2
3
D0
D1
D2
D3
D1
D2
D2
D3
D3
D4
D4
D4
D4
D5
D5
D5
D5
D6
D6
D6
D6
D7
D7
D7
D7
D8
D8
D8
D8
D9
D9
D9
4 ws
D3
1 ws
1 ws
1 ws
Table 4. Address Latency for 3 Wait States
Word
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
25
A d v a n c e I n f o r m a t i o n
0
1
2
3
D0
D1
D2
D3
D1
D2
D2
D3
D4
D4
D3
D4
D5
D5
D4
D5
D6
D6
D5
D6
D7
D7
D6
D7
D8
D8
D7
D8
D9
D9
D8
D9
3 ws
D3
D10
D10
1 ws
Table 5. Address Latency for 2 Wait States
Word
0
1
2
3
D0
D1
D2
D3
D1
D2
D3
D4
D2
D3
D4
D5
D3
D4
D5
D6
D4
D5
D6
D7
D5
D6
D7
D8
D6
D7
D8
D9
D7
D8
D8
D9
2 ws
D9
D10
D11
D10
Table 6 through Table 9 show the address/boundary crossing latency for variable wait state if a
boundary crossing occurs during initial access
Table 6. Address/Boundary Crossing Latency for 7, 6, and 5 Wait States
Word
0
1
2
3
D0
D1
D2
D3
D1
D2
D2
D3
D3
1 ws
1 ws
1 ws
1 ws
D4
D4
D4
D4
D5
D5
D5
D5
D6
D6
D6
D6
D7
D7
D7
D7
7, 6, and 5
ws
1 ws
1 ws
1 ws
D3
1 ws
1 ws
1 ws
Table 7. Address/Boundary Crossing Latency for 4 Wait States
Word
0
1
2
3
D0
D1
D2
D3
D1
D2
D2
D3
D3
D4
D4
D4
D4
D5
D5
D5
D5
D6
D6
D6
D6
D7
D7
D7
D7
D8
D8
D8
D8
1 ws
1 ws
1 ws
4 ws
D3
1 ws
1 ws
1 ws
Table 8. Address/Boundary Crossing Latency for 3 Wait States
Word
0
1
2
3
D0
D1
D2
D3
D1
D2
D2
D3
D3
D4
D4
D4
D4
D5
D5
D5
D5
D6
D6
D6
D6
D7
D7
D7
D7
D8
D8
D8
D8
D9
D9
D9
3 ws
D3
1 ws
1 ws
1 ws
26
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 9. Address/Boundary Crossing Latency for 2 Wait States
Word
0
1
2
3
D0
D1
D2
D3
D1
D2
D2
D3
D4
D4
D3
D4
D5
D5
D4
D5
D6
D6
D5
D6
D7
D7
D6
D7
D8
D8
D7
D8
D9
D9
D8
D9
2 ws
D3
D10
D10
1 ws
The device will continue to output continuous, sequential burst data, wrapping around to address
000000h after it reaches the highest addressable memory location, until the system asserts CE#
high, RESET# low, or AVD# low in conjunction with a new address. See Table 1 on page 10. The
reset command does not terminate the burst read operation.
If the host system crosses a 128 word line boundary while reading in burst mode, and the device
is not programming or erasing, no additional latency will occur as described above. If the host
system crosses the bank boundary while the device is programming or erasing, the device will
provide asynchronous read status information. The clock will be ignored. After the host has com-
pleted status reads, or the device has completed the program or erase operation, the host can
restart a burst operation using a new address and AVD# pulse.
8-, 16-, and 32-Word Linear Burst with Wrap Around
These three modes are of the linear wrap around design, in which a fixed number of words are
read from consecutive addresses. In each of these modes, the burst addresses read are deter-
mined by the group within which the starting address falls. The groups are sized according to the
number of words read in a single burst sequence for a given mode (see Table 10.)
Table 10. Burst Address Groups
Mode Group Size Group Address Ranges
8-word
8 words
0-7h, 8-Fh, 10-17h, 18-1Fh...
0-Fh, 10-1Fh, 20-2Fh, 30-3Fh...
16-word
16 words
00-1Fh, 20-3Fh, 40-5Fh, 60-
7Fh...
32-word
32 words
As an example: if the starting address in the 8-word mode is 3Ah, and the burst sequence would
be 3A-3B-3C-3D-3E-3F-38-39h. The burst sequence begins with the starting address written to
the device, but wraps back to the first address in the selected group. In a similar fashion, the 16-
word and 32-word Linear Wrap modes begin their burst sequence on the starting address written
to the device, and then wraps back to the first address in the selected address group and termi-
nates the burst read. Note that in these three burst read modes the address pointer does
not cross the boundary that occurs every 128 words; thus, no wait states are inserted
(except during the initial access).
8-, 16-, and 32-Word Linear Burst without Wrap Around
In these modes, a fixed number of words (predefined as 8, 16, or 32 words) are read from con-
secutive addresses starting with the initial word, which is written to the device. When the address
is at the end of the group address range (see Burst Address Groups Table), the burst read oper-
ation stops and the RDY output goes low. There is no group limitation and is different from the
Linear Burst with Wrap Around.
As an example, for 8-word length Burst Read, if the starting address written to the device is 3A,
the burst sequence would be 3A-3B-3C-3D-3E-3F-40-41h, and the read operation will be termi-
nated after all eight words. The 16-word and 32-word modes would operate in a similar fashion
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
27
A d v a n c e I n f o r m a t i o n
and continuously read to the predefined 16 or 32 words accordingly. Note: In this burst read
mode, the address pointer may cross the boundary that occurs every 128 words.
Programmable Wait State
The programmable wait state feature indicates to the device the number of additional clock cycles
that must elapse after AVD# is driven active before data will be available. Upon power up, the
device defaults to the maximum of seven total cycles. The total number of wait states is program-
mable from two to seven cycles. For further details, see “Set Configuration Register Command
Sequence”.
Configuration Register
The device uses a configuration register to set the various burst parameters: number of wait
states, burst read mode, burst length, RDY configuration, and synchronous mode active.
Handshaking Feature
The handshaking feature allows the host system to simply monitor the RDY signal from the device
to determine when the initial word of burst data is ready to be read. The host system should use
the configuration register to set the number of wait states for optimal burst mode operation. The
initial word of burst data is indicated by the rising edge of RDY after OE# goes low.
Simultaneous Read/Write Operations with Zero Latency
This device is capable of reading data from one bank of memory while programming or erasing
in one of the other banks of memory. An erase operation may also be suspended to read from or
program to another location within the same bank (except the sector being erased). Figure 23,
on page 82 shows how read and write cycles may be initiated for simultaneous operation with
zero latency. Refer to the DC Characteristics table for read-while-program and read-while-erase
current specifications.
Writing Commands/Command Sequences
The device has inputs/outputs that accept both address and data information. To write a com-
mand or command sequence (which includes programming data to the device and erasing sectors
of memory), the system must drive AVD# and CE# to VIL, and OE# to VIH when providing an
address to the device, and drive WE# and CE# to VIL, and OE# to VIH. when writing commands
or data.
The device features an Unlock Bypass mode to facilitate faster programming. Once the device
enters the Unlock Bypass mode, only two write cycles are required to program a word, instead of
four.
An erase operation can erase one sector, multiple sectors, or the entire device. Table 14-17 indi-
cates the address space that each sector occupies. The device address space is divided into
multiple banks. A “bank address” is the address bits required to uniquely select a bank. Similarly,
a “sector address” is the address bits required to uniquely select a sector.
Refer to the DC Characteristics table for write mode current specifications. The AC Characteristics
section contains timing specification tables and timing diagrams for write operations.
Accelerated Program and Erase Operations
The device offers accelerated program and erase operation through the ACC function. ACC is pri-
marily intended to allow faster manufacturing throughput at the factory and not to be used in
system operations.
If the system asserts VHH on this input, the device automatically enters the aforementioned Un-
lock Bypass mode and uses the higher voltage on the input to reduce the time required for
program and erase operations. The system can then use the abbreviated Embedded Programming
28
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
command and Write Buffer Load command sequence provided by the Unlock Bypass mode. Note
that if a “Write-to-Buffer-Abort Reset” is required while in Unlock Bypass mode, the full 3-cycle
RESET command sequence must be used to reset the device. Removing VHH from the ACC
input, upon completion of the embedded program or erase operation, returns the device to nor-
mal operation. Note that sectors must be unlocked prior to raising ACC to VHH. Note that the ACC
pin must not be at VHH for operations other than accelerated programming, or device damage
may result. In addition, the ACC pin must not be left floating or unconnected; inconsistent behav-
ior of the device may result.
When at VIL, ACC locks all sectors. ACC should be at VIH for all other conditions.
Write Buffer Programming Operation
Write Buffer Programming allows the system to write a maximum of 32 words in one program-
ming operation. This results in a faster effective word programming time than the standard
“word” programming algorithms. The Write Buffer Programming command sequence is initiated
by first writing two unlock cycles. This is followed by a third write cycle containing the Write Buffer
Load command written at the Sector Address in which programming will occur. At this point, the
system writes the number of “word locations minus 1” that will be loaded into the page buffer
at the Sector Address in which programming will occur. This tells the device how many write buffer
addresses will be loaded with data and therefore when to expect the “Program Buffer to Flash”
confirm command. The number of locations to program cannot exceed the size of the write buffer
or the operation will abort. (NOTE: The number loaded = the number of locations to program
minus 1. For example, if the system will program 6 address locations, then 05h should be written
to the device.)
The system then writes the starting address/data combination. This starting address is the first
address/data pair to be programmed, and selects the “write-buffer-page” address. All subsequent
address/data pairs must fall within the “selected-write-buffer-page”, and be loaded in sequential
order.
The “write-buffer-page” is selected by using the addresses AMAX-A5 where AMAX is A23 for
S29NS256N, A22 for S29NS128N, and A21 for S29NS064N.
The “write-buffer-page” addresses must be the same for all address/data pairs loaded into
the write buffer. (This means Write Buffer Programming cannot be performed across multiple
“write-buffer-pages”. This also means that Write Buffer Programming cannot be performed
across multiple sectors. If the system attempts to load programming data outside of the selected
“write-buffer-page”, the operation will ABORT.)
After writing the Starting Address/Data pair, the system then writes the remaining address/data
pairs into the write buffer. Write buffer locations must be loaded in sequential order.
Note that if a Write Buffer address location is loaded multiple times, the “address/data pair”
counter will be decremented for every data load operation. Also, the last data loaded at
a location before the “Program Buffer to Flash” confirm command will be programmed into the
device. It is the software’s responsibility to comprehend ramifications of loading a write-buffer
location more than once. The counter decrements for each data load operation, NOT for each
unique write-buffer-address location.
Once the specified number of write buffer locations have been loaded, the system must then write
the “Program Buffer to Flash” command at the Sector Address. Any other address/data write com-
binations will abort the Write Buffer Programming operation. The device will then “go busy”. The
Data Bar polling techniques should be used while monitoring the last address location loaded
into the write buffer. This eliminates the need to store an address in memory because the sys-
tem can load the last address location, issue the program confirm command at the last loaded
address location, and then data bar poll at that same address. DQ7, DQ6, DQ5, DQ2, and DQ1
should be monitored to determine the device status during Write Buffer Programming.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
29
A d v a n c e I n f o r m a t i o n
The write-buffer “embedded” programming operation can be suspended using the standard sus-
pend/resume commands. Upon successful completion of the Write Buffer Programming operation,
the device will return to READ mode.
The Write Buffer Programming Sequence can be ABORTED under any of the following conditions:
Load a value that is greater than the page buffer size during the “Number of
Locations to Program” step.
Write to an address in a sector different than the one specified during the
“Write-Buffer-Load” command.
Write an Address/Data pair to a different write-buffer-page than the one se-
lected by the “Starting Address” during the “write buffer data loading” stage
of the operation.
Write data other than the “Confirm Command” after the specified number of
“data load” cycles.
The ABORT condition is indicated by DQ1 = 1, DQ7 = DATA# (for the “last address location
loaded”), DQ6 = TOGGLE, DQ5 = 0. This indicates that the Write Buffer Programming Operation
was ABORTED. A “Write-to-Buffer-Abort reset” command sequence is required when using the
Write-Buffer-Programming features in Unlock Bypass mode. Note: The SecSITM sector, autose-
lect, and CFI functions are unavailable when a program operation is in progress.
Use of the write buffer is strongly recommended for programming when multiple words
are to be programmed. Write buffer programming is allowed in any sequence of memory (or
address) locations. These flash devices are capable of handling multiple write buffer programming
operations on the same write buffer address range without intervening erases. However, pro-
gramming the same word address multiple times without intervening erases requires a modified
programming method. Please contact your local SpansionTM representative for details.
Autoselect Mode
The autoselect mode provides manufacturer and device identification, and sector protection ver-
ification, through identifier codes output from the internal register (which is separate from the
memory array) on DQ15–DQ0. This mode is primarily intended for programming equipment to
automatically match a device to be programmed with its corresponding programming algorithm.
The autoselect codes can also be accessed in-system.
When verifying sector protection, the sector address must appear on the appropriate highest
order address bits. The remaining address bits are don’t care. When all necessary bits have been
set as required, the programming equipment may then read the corresponding identifier code on
DQ15–DQ0. The autoselect codes can also be accessed in-system through the command register.
The command sequence is illustrated in Table , “,” on page 56. Note that if a Bank Address (BA)
on address bits A23, A22, A21, and A20 for the NS256N, A22, A21, A20, and A19 for the NS128N,
A21, A20, and A19 for the NS064N, is asserted during the third write cycle of the autoselect com-
mand, the host system can read autoselect data that bank and then immediately read array data
from the other bank, without exiting the autoselect mode.
To access the autoselect codes, the host system must issue the autoselect command via the com-
mand register, as shown in Table , “,” on page 56.
Advanced Sector Protection and Unprotection
This advanced security feature provides an additional level of protection to all sectors against in-
advertent program or erase operations.
The advanced sector protection feature disables both programming and erase operations in any
sector while the advanced sector unprotection feature re-enables both program and erase oper-
ations in previously protected sectors. Sector protection/unprotection can be implemented using
either of the two methods
30
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Hardware method
Software method
Persistent/Password Sector Protection is achieved by using the software method while the sector
protection with WP# pin is achieved by using the hardware method.
All parts default to operate in the Persistent Sector Protection mode. The customer must then
choose if the Persistent or Password Protection method is most desirable. There are two one-time
programmable non-volatile bits that define which sector protection method will be used.
Persistent Mode Lock Bit
Password Mode Lock Bit
If the customer decides to continue using the Persistent Sector Protection method, they must set
the Persistent Mode Lock Bit. This will permanently set the part to operate only using Persistent
Sector Protection. However, if the customer decides to use the Password Sector Protection
method, they must set the Password Mode Lock Bit. This will permanently set the part to op-
erate only using Password Sector Protection.
It is important to remember that setting either the Persistent Mode Lock Bit or the Password
Mode Lock Bit permanently selects the protection mode. It is not possible to switch between the
two methods once a locking bit has been set. It is important that one mode is explicitly se-
lected when the device is first programmed, rather than relying on the default mode
alone. If both are selected to be set at the same time, the operation will abort. This is
done so that it is not possible for a system program or virus to later set the Password Mode Lock-
ing Bit, which would cause an unexpected shift from the default Persistent Sector Protection Mode
into the Password Sector Protection Mode.
The device is shipped with all sectors unprotected. Spansion offers the option of programming
and protecting sectors at the factory prior to shipping the device through Spansion programming
services. Contact an Spansion representative for details.
Sector Protection
The device features several levels of sector protection, which can disable both the program and
erase operations in certain sectors.
Persistent Sector Protection
A software enabled command sector protection method that replaces the old 12 V controlled pro-
tection method.
Password Sector Protection
A highly sophisticated software enabled protection method that requires a password before
changes to certain sectors or sector groups are permitted
WP# Hardware Protection
A write protect pin (WP#) can prevent program or erase operations in the outermost sectors.The
WP# Hardware Protection feature is always available, independent of the software managed pro-
tection method chosen.
Persistent Sector Protection
The Persistent Sector Protection method replaces the old 12 V controlled protection method while
at the same time enhancing flexibility by providing three different sector protection states:
Persistently Locked—A sector is protected and cannot be changed.
Dynamically Locked—The sector is protected and can be changed by a sim-
ple command
Unlocked—The sector is unprotected and can be changed by a simple com-
mand
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
31
A d v a n c e I n f o r m a t i o n
In order to achieve these states, three types of “bits” namely Persistent Protection Bit (PPB), Dy-
namic Protection Bit (DYB), and Persistent Protection Bit Lock (PPB Lock) are used to achieve the
desired sector protection scheme:
Persistent Protection Bit (PPB)
PPB is used to as an advanced security feature to protect individual sectors from being pro-
grammed or erased thereby providing additional level of protection. Every sector is assigned a
Persistent Protection Bit.
Each PPB is individually programmed through the PPB Program Command. However all PPBs
are erased in parallel through the All PPB Erase Command. Prior to erasing, these bits don’t
have to be pre programmed. The Embedded Erase algorithm automatically preprograms and ver-
ifies prior to an electrical erase. The system is not required to provide any controls or timings
during these operations.
The PPBs retain their state across power cycles because they are Non-Volatile. The PPBs has the
same endurance as the flash memory.
Persistent Protection Bit Lock (PPB Lock Bit) in Persistent Sector
Protection Mode
PPB Lock Bit is a global volatile bit and provides an additional level of protection to the sectors.
When programmed (set to “0”), all the PPBs are locked and hence none of them can be
changed. When erased (cleared to “1”), the PPBs are changeable. There is only one PPB Lock
Bit in every device. Only a hardware reset or a power-up clears the PPB Lock Bit. It is to be noted
that there is no software solution, i.e. command sequence to unlock the PPB Lock Bit.
Once all PPBs are configured to the desired settings, the PPB Lock Bit may be set (programmed
to “0”). The PPB Lock Bit is set by issuing the PPB Lock Bit Set Command. Programming or setting
the PPB Lock Bit disables program and erase commands to all the PPBs. In effect, the PPB Lock
Bit locks the PPBs into their current state. The only way to clear the PPB Lock Bit is to go through
a hardware or powerup reset. System boot code can determine if any changes to the PPB are
needed e.g. to allow new system code to be downloaded. If no changes are needed then the boot
code can disable the PPB Lock Bit to prevent any further changes to the PPBs during system
operation.
Dynamic Protection Bit (DYB)
DYB is a security feature used to protect individual sectors from being programmed or erased in-
advertently. It is a volatile protection bit and is assigned to each sector. Upon power-up or a
hardware reset, the contents of all DYBs are set (programmed to “0”). Each DYB can be individ-
ually modified through the DYB Set Command or the DYB Clear Command.
The Protection Status for a particular sector is determined by the status of the PPB and the DYB
relative to that sector. For the sectors that have the PPBs cleared (erased to “1”), the DYBs control
whether or not the sector is protected or unprotected. By issuing the DYB Set or Clear command
sequences, the DYBs will be set (programmed to “0”) or cleared (erased to “1”), thus placing each
sector in the protected or unprotected state respectively. These states are the so-called Dynamic
Locked or Unlocked states due to the fact that they can switch back and forth between the pro-
tected and unprotected states. This feature allows software to easily protect sectors against
inadvertent changes yet does not prevent the easy removal of protection when changes are
needed. The DYBs maybe set (programmed to “0”) or cleared (erased to “1”) as often as needed.
When the parts are first shipped, the PPBs are cleared (erased to “1”) and upon power up or reset,
the DYBs are set (programmed to “0”). The PPB Lock Bit defaults to the cleared state (erased to
“1”) after power up and the PPBs retain their previous state as they are non-volatile.
32
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
It is possible to have sectors that have been persistently locked, and sectors that are left in the
dynamic state. The sectors in the dynamic state are all unprotected. If there is a need to protect
some of them, a simple DYB Set command sequence is all that is necessary. The DYB Set or Clear
command for the dynamic sectors signify protected or unprotected state of the sectors respec-
tively. However, if there is a need to change the status of the persistently locked sectors, a few
more steps are required. First, the PPB Lock Bit must be cleared by either putting the device
through a power-cycle, or hardware reset. The PPBs can then be changed to reflect the desired
settings. Setting the PPB Lock Bit once again will lock the PPBs, and the device operates normally
again.
Note: to achieve the best protection, it’s recommended to execute the PPB Lock Bit Set command
early in the boot code, and protect the boot code by holding WP# = VIL. Note that the PPB and
DYB bits have the same function when ACC = VHH as they do when ACC = VIH
.
Table 11. Sector Protection Schemes
PPB
DYB
PPB
Lock
Sector State
1
0
1
1
1
0
1
1
1
Sector Unprotected
Sector Protected through DYB
Sector Protected through PPB
Sector Protected through PPB
and DYB
0
0
1
1
0
1
1
1
0
0
0
0
Sector Unprotected
Sector Protected through DYB
Sector Protected through PPB
Sector Protected through PPB
and DYB
0
0
0
Table 11 contains all possible combinations of the DYB, PPB, and PPB Lock relating to the status
of the sector.
In summary, if the PPB is set (programmed to “0”), and the PPB Lock is set (programmed to “0”),
the sector is protected and the protection can not be removed until the next power cycle clears
(erase to “1”) the PPB Lock Bit. Once the PPB Lock Bit is cleared (erased to “1”), the sector can
be persistently locked or unlocked. Likewise, if both PPB Lock Bit or PPB is cleared (erased to “1”)
the sector can then be dynamically locked or unlocked. The DYB then controls whether or not the
sector is protected or unprotected.
If the user attempts to program or erase a protected sector, the device ignores the command and
returns to read mode. A program or erase command to a protected sector enables status polling
and returns to read mode without having modified the contents of the protected sector.
The programming of the DYB, PPB, and PPB Lock for a given sector can be verified by writing in-
dividual status read commands DYB Status, PPB Status, and PPB Lock Status to the device.
Persistent Sector Protection Mode Lock Bit
A Persistent Mode Lock Bit exists to guarantee that the device remain in software sector protec-
tion. Once programmed (set to “0”), the Persistent Mode Lock Bit prevents programming of the
Password Mode Lock Bit. This guarantees that now, a hacker cannot place the device in Password
Sector Protection Mode.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
33
A d v a n c e I n f o r m a t i o n
Password Sector Protection
The Password Sector Protection Mode method allows an even higher level of security than the Per-
sistent Sector Protection Mode. There are two main differences between the Persistent Sector
Protection Mode and the Password Sector Protection Mode:
When the device is first powered up, or comes out of a reset cycle, the PPB
Lock Bit is set to the locked state, rather than cleared to the unlocked
state.
The only means to clear the PPB Lock Bit is by writing a unique 64-bit Pass-
word to the device.
The Password Sector Protection method is otherwise identical to the Persistent Sector Protection
method.
A 64-bit password is the only additional tool utilized in this method.
The password is stored in a one-time programmable (OTP) region of the flash memory. Once
the Password Mode Lock Bit is set, the password is permanently set with no means to read, pro-
gram, or erase it. The password is used to clear the PPB Lock Bit. The Password Unlock command
must be written to the flash, along with a password. The flash device internally compares the
given password with the pre-programmed password. If they match, the PPB Lock Bit is cleared,
and the PPBs can be altered. If they do not match, the flash device does nothing. There is a built-
in 1 µs delay for each “password check.” This delay is intended to thwart any efforts to run a pro-
gram that tries all possible combinations in order to crack the password.
64-bit Password
The 64-bit Password is located in a non-erasable region of the FLash and is accessible through
the use of the Password Program and Verify commands (see “Password Protection Command Set
Definitions” section on page 51). The password function works in conjunction with the Password
Mode Locking Bit, which when set, prevents the Password Verify command from reading the con-
tents of the password on the pins of the device.
Password Mode Lock Bit
In order to select the Password Sector Protection scheme, the customer must first program the
password. Spansion LLC recommends that the password be somehow correlated to the unique
Electronic Serial Number (ESN) of the particular flash device. Each ESN is different for every flash
device; therefore each password should be different for every flash device. While programming
in the password region, the customer may perform Password Verify operations.
Once the desired password is programmed in, the customer must then set the Password Mode
Locking Bit. This operation achieves two objectives:
It permanently sets the device to operate using the Password Sector Protec-
tion Mode. It is not possible to reverse this function.
It also disables all further commands to the password region. All program and
read operations are ignored.
Both of these objectives are important, and if not carefully considered, may lead to unrecoverable
errors. The user must be sure that the Password Sector Protection method is desired when setting
the Password Mode Locking Bit. More importantly, the user must be sure that the password is
correct when the Password Mode Locking Bit is set. Due to the fact that read operations are dis-
abled, there is no means to verify what the password is afterwards. If the password is lost after
setting the Password Mode Lock Bit, there will be no way to clear the PPB Lock Bit.
The Password Mode Lock Bit, once set, prevents reading the 64-bit password on the DQ bus and
further password programming. The Password Mode Lock Bit is not erasable. Once Password
Mode Lock Bit is programmed, the Persistent Mode Lock Bit is disabled from programming, guar-
anteeing that no changes to the protection scheme are allowed.
34
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Persistent Protection Bit Lock (PPB Lock Bit) in Password Sector
Protection Mode
The Persistent Protection Bit Lock (PPB Lock Bit) is a volatile bit that reflects the state of the Pass-
word Mode Lock Bit after power-up reset. If the Password Mode Lock Bit is also set, after a
hardware reset (RESET# asserted) or a power-up reset, the ONLY means for clearing the PPB Lock
Bit in Password Protection Mode is to issue the Password Unlock command. Successful execution
of the Password Unlock command to enter the entire password clears the PPB Lock Bit, allowing
for sector PPBs modifications. Asserting RESET#, taking the device through a power-on reset, or
issuing the PPB Lock Bit Set command sets the PPB Lock Bit to a “1”.
If the Password Mode Lock Bit is not set (device is operating in the default Persistent Protection
Mode). The Password Unlock command is ignored in Persistent Sector Protection Mode.
Hardware Data Protection Mode
The device offers two types of data protection at the sector level:
When WP# is at VIL, the two outermost sectors at the top are locked (device
specific).
When ACC is at VIL, all sectors are locked.
SA257 and SA258 are locked (S29NS256N)
SA129 and SA130 are locked (S29NS128N)
SA65 and SA66 are locked (S29NS064N)
The write protect pin (WP#) adds a final level of hardware program and erase protection to the
boot sectors. The boot sectors are the two sectors containing the highest set of addresses in these
top-boot-configured devices. For the none boot option, the WP# hardware feature is not available.
When this pin is low it is not possible to change the contents of these top sectors. These
sectors generally hold system boot code. So, the WP# pin can prevent any changes to the boot
code that could override the choices made while setting up sector protection during system
initialization.
The following hardware data protection measures prevent accidental erasure or programming,
which might otherwise be caused by spurious system level signals during VCC power-up and
power-down transitions, or from system noise.
Write Protect (WP#)
The Write Protect feature provides a hardware method of protecting the two outermost sectors.
This function is provided by the WP# pin and overrides the previously discussed Sector Protec-
tion/Unprotection method.
If the system asserts VIL on the WP# pin, the device disables program and erase functions in the
“top” boot sectors. If the system asserts VIH on the WP# pin, the device reverts to whether the
boot sectors were last set to be protected or unprotected. That is, sector protection or unprotec-
tion for these sectors depends on whether they were last protected or unprotected.
WP# Boot Sector Protection
The WP# signal will be latched at a specific time in the embedded program or erase sequence. To
prevent a write to the top two sectors, WP# must be asserted (WP#=VIL) on the last write cycle
of the embedded sequence (i.e., 4th write cycle in embedded program, 6th write cycle in embed-
ded erase).
If selecting multiple sectors for erasure: The WP# protection status is latched only on the 6th
write cycle of the embedded sector erase command sequence when the first sector is selected. If
additional sectors are selected for erasure, they are subject to the WP# status that was latched
on the 6th write cycle of the command sequence.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
35
A d v a n c e I n f o r m a t i o n
Note that the WP# pin must not be left floating or unconnected; inconsistent behavior of the de-
vice may result.
Low VCC Write Inhibit
When VCC is less than VLKO, the device does not accept any write cycles. This protects data during
CC power-up and power-down. The command register and all internal program/erase circuits are
V
disabled, and the device resets to reading array data. Subsequent writes are ignored until VCC is
greater than VLKO. The system must provide the proper signals to the control inputs to prevent
unintentional writes when VCC is greater than VLKO.
Write Pulse “Glitch” Protection
Noise pulses of less than tWEP on WE# do not initiate a write cycle.
Logical Inhibit
Write cycles are inhibited by holding any one of OE# = VIL, CE# = VIH or WE# = VIH. To initiate
a write cycle, CE# and WE# must be a logical zero while OE# is a logical one.
Power-Up Write Inhibit
If WE# = CE# = RESET# = VIL and OE# = VIH during power up, the device does not accept com-
mands on the rising edge of WE#. The internal state machine is automatically reset to the read
mode on power-up
Lock Register
The Lock Register consists of 3 bits. Each of these bits are non-volatile and read-only. DQ15-DQ3
are reserved and are undefined.
Table 12. Lock Register
DQ15-3
DQ2
DQ1
DQ0
Undefined
Password Protection Mode Lock Bit Persistent Protection Mode Lock Bit SecSi Sector Protection Bit
36
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Standby Mode
When the system is not reading or writing to the device, it can place the device in the standby
mode. In this mode, current consumption is greatly reduced, and the outputs are placed in the
high impedance state, independent of the OE# input.
The device enters the CMOS standby mode when the CE# and RESET# inputs are both held at
VCC. The device requires standard access time (tCE) for read access when the device is in either
of these standby modes, before it is ready to read data.
If the device is deselected during erasure or programming, the device draws active current until
the operation is completed.
ICC3 in the DC Characteristics table represents the standby current specification.
Automatic Sleep Mode
The automatic sleep mode minimizes Flash device energy consumption. The device automatically
enters this mode when addresses and clock remain stable for tACC + 20 ns. The automatic sleep
mode is independent of the CE#, WE#, and OE# control signals. Standard address access timings
provide new data when addresses are changed. While in sleep mode, output data is latched and
always available to the system. ICC4 in the DC Characteristics table represents the automatic
sleep mode current specification.
RESET#: Hardware Reset Input
The RESET# input provides a hardware method of resetting the device to reading array data.
When RESET# is driven low for at least a period of tRP, the device immediately terminates any
operation in progress, tristates all outputs, and ignores all read/write commands for the duration
of the RESET# pulse. The device also resets the internal state machine to reading array data. The
operation that was interrupted should be reinitiated once the device is ready to accept another
command sequence, to ensure data integrity.
Current is reduced for the duration of the RESET# pulse. When RESET# is held at VSS, the device
draws CMOS standby current (ICC4). If RESET# is held at VIL but not within VSS, the standby cur-
rent will be greater.
RESET# may be tied to the system reset circuitry. A system reset would thus also reset the Flash
memory, enabling the system to read the boot-up firmware from the Flash memory.
Refer to the AC Characteristics tables for RESET# parameters and to Figure 15 for the timing
diagram.
V
Power-up and Power-down Sequencing
CC
The device imposes no restrictions on VCC power-up or power-down sequencing. Asserting RE-
SET# to VIL is required during the entire VCC power sequence until the respective supplies reach
their operating voltages. Once VCC attains its operating voltage, de-assertion of RESET# to VIH is
permitted.
Output Disable Mode
When the OE# input is at VIH, output from the device is disabled. The outputs are placed in the
high impedance state.
SecSi™ (Secured Silicon) Sector Flash Memory Region
The SecSi (Secured Silicon) Sector feature provides a Flash memory region that enables perma-
nent part identification through an Electronic Serial Number (ESN). The SecSi Sector is 256 words
in length. All reads outside of the 256 word address range will return non-valid data. The Factory
Indicator Bit (DQ7) is used to indicate whether or not the Factory SecSi Sector is locked when
shipped from the factory. The Customer Indicator Bit (DQ6) is used to indicate whether or not the
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
37
A d v a n c e I n f o r m a t i o n
Customer SecSi Sector is locked when shipped from the factory. The Factory SecSi bits are per-
manently set at the factory and cannot be changed, which prevents cloning of a factory locked
part. This ensures the security of the ESN and customer code once the product is shipped to the
field.
Spansion offers the device with a Factory SecSi Sector that is locked and a Customer SecSi Sector
that is either locked or is lockable. The Factory SecSi Sector is always protected when shipped
from the factory, and has the Factory Indicator Bit (DQ7) permanently set to a “1”. The Customer
SecSi Sector is shipped unprotected, allowing customers to utilize that sector in any manner they
choose. Once the Customer SecSi Sector area is protected, the Customer Indicator Bit will be per-
manently set to “1.”
The system accesses the SecSi Sector through a command sequence (see “Enter SecSi™ Sector/
Exit SecSi Sector Command Sequence” section on page 43). After the system has written the
Enter SecSi Sector command sequence, it may read the SecSi Sector by using the addresses nor-
mally occupied by sector SA0 of the memory array. This mode of operation continues until the
system issues the Exit SecSi Sector command sequence, or until power is removed from the de-
vice. While SecSi Sector access is enabled, Memory Array read access, program operations, and
erase operations to all sectors other than SA0 are also available. On power-up, or following a
hardware reset, the device reverts to sending commands to the normal address space.
Factory Locked: Factor SecSi Sector Programmed and Protected
At the Factory
In a factory sector locked device, the Factory SecSi Sector is protected when the device is shipped
from the factory. The Factory SecSi Sector cannot be modified in any way. The device is pre pro-
grammed with both a random number and a secure ESN. The Factory SecSi Sector is located at
addresses 000000h–00007Fh.
The device is available pre programmed with one of the following:
A random, secure ESN only within the Factor SecSi Sector
Customer code within the Customer SecSi Sector through the SpansionTM pro-
gramming services
Both a random, secure ESN and customer code through the SpansionTM pro-
gramming services.
Table 13. SecSiTM Sector Addresses
Sector
Customer
Factory
Sector Size
128 words
Address Range
000080h-0000FFh
000000h-00007Fh
128 words
Customers may opt to have their code programmed by Spansion through the SpansionTM program-
ming services. Spansion programs the customer’s code, with or without the random ESN. The
devices are then shipped from Spansion’s factory with the Factory SecSi Sector and Customer
SecSi Sector permanently locked. Contact an Spansion representative for details on using Span-
sion’s SpansionTM programming services.
Customer SecSi Sector
If the security feature is not required, the Customer SecSi Sector can be treated as an additional
Flash memory space. The Customer SecSi Sector can be read any number of times, but can be
programmed and locked only once. Note that the accelerated programming (ACC) and unlock by-
pass functions are not available when programming the Customer SecSi Sector, but reading the
first Bank through the last bank is available. The Customer SecSi Sector is located at addresses
000080h–0000FFh.
38
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
The Customer SecSi Sector area can be protected by writing the SecSi Sector Protection Bit Lock
command sequence.
Once the Customer SecSi Sector is locked and verified, the system must write the Exit SecSi Sec-
tor Region command sequence to return to reading and writing SA0 in the memory array.
The Customer SecSi Sector lock must be used with caution since, once locked, there is no proce-
dure available for unlocking the Customer SecSi Sector area and none of the bits in the Customer
SecSi Sector memory space can be modified in any way.
Common Flash Memory Interface (CFI)
The Common Flash Interface (CFI) specification outlines device and host system software inter-
rogation handshake, which allows specific vendor-specified software algorithms to be used for
entire families of devices. Software support can then be device-independent, JEDEC ID-indepen-
dent, and forward- and backward-compatible for the specified flash device families. Flash vendors
can standardize their existing interfaces for long-term compatibility.
This device enters the CFI Query mode when the system writes the CFI Query command, 98h, to
address 55h any time the device is ready to read array data. The system can read CFI information
at the addresses given in Tables 14–17. To terminate reading CFI data, the system must write the
reset command.
For further information, please refer to the CFI Specification and CFI Publication 100, available
via the World Wide Web at http://www.amd.com/flash/cfi. Alternatively, contact the local sales
representative for copies of these documents.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
39
A d v a n c e I n f o r m a t i o n
Table 14. CFI Query Identification String
Data
Addresses S29NS256N S29NS128N S29NS064N
Description
10h
11h
12h
0051h
0052h
0059h
Query Unique ASCII string “QRY”
13h
14h
0002h
0000h
Primary OEM Command Set
15h
16h
0040h
0000h
Address for Primary Extended Table
17h
18h
0000h
0000h
Alternate OEM Command Set (00h = none
exists)
19h
1Ah
0000h
0000h
Address for Alternate OEM Extended Table
(00h = none exists)
Table 15. System Interface String
Data
Addresses S29NS256N S29NS128N S29NS064N
Description
VCC Min. (write/erase)
1Bh
1Ch
1Dh
1Eh
1Fh
20h
21h
22h
0017h
0019h
0000h
0000h
0006h
0009h
000Ah
0000h
D7–D4: volt, D3–D0: 100 millivolt
VCC Max. (write/erase)
D7–D4: volt, D3–D0: 100 millivolt
ACC Min. voltage (00h = no ACC pin present)
Refer to 4Dh
ACC Max. voltage (00h = no ACC pin
present) Refer to 4Eh
Typical timeout per single byte/word write 2N
µs
Typical timeout for Min. size buffer write 2N
µ
s (00h = not supported)
Typical timeout per individual block erase 2N
ms
Typical timeout for full chip erase 2N ms (00h
= not supported)
Max. timeout for byte/word write 2N times
typical
23h
24h
25h
0003h
0001h
0002h
Max. timeout for buffer write 2N times typical
Max. timeout per individual block erase 2N
times typical
Max. timeout for full chip erase 2N times
typical (00h = not supported)
26h
0000h
40
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 16. Device Geometry Definition
Data
Addresses S29NS256N S29NS128H S29NS064N
Description
Device Size = 2N byte
27h
0019h
0018h
0017h
28h
29h
0001h
0000h
Flash Device Interface description (refer to
CFI publication 100)
Max. number of bytes in multi-byte write =
2Ah
2Bh
0006h
0000h
2N
(00h = not supported)
2Ch
0002h
Number of Erase Block Regions within device
2Dh
2Eh
2Fh
30h
00FEh
0000h
0000h
0002h
007Eh
0000h
0000h
0002h
003Eh
0000h
0000h
0002h
Erase Block Region 1 Information
(refer to the CFI specification or CFI
publication 100)
31h
32h
33h
34h
0003h
0000h
0080h
0000h
Erase Block Region 2 Information
Erase Block Region 3 Information
Erase Block Region 4 Information
35h
36h
37h
38h
0000h
0000h
0000h
0000h
39h
3Ah
3Bh
3Ch
0000h
0000h
0000h
0000h
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
41
A d v a n c e I n f o r m a t i o n
Table 17. Primary Vendor-Specific Extended Query
Data
Addresses S29NS256N S29NS128N S29NS064N
Description
40h
41h
42h
0050h
0052h
0049h
Query-unique ASCII string “PRI”
43h
44h
0031h
0034h
Major version number, ASCII
Minor version number, ASCII
Address Sensitive Unlock (Bits 1-0)
0 = Required, 1 = Not Required
45h
0010h
Silicon Revision Number (Bits 7-2)
Erase Suspend
46h
47h
0002h
0001h
0 = Not Supported, 1 = To Read Only, 2 = To
Read & Write
Sector Protect
0 = Not Supported, X = Number of sectors in
per group
Sector Temporary Unprotect
00 = Not Supported, 01 = Supported
48h
49h
0000h
0008h
Sector Protect/Unprotect scheme
08 = Advanced Sector Protection
Simultaneous Operation
4Ah
4Bh
4Ch
00F0h
0078h
0001h
0000h
0038h
Number of Sectors in all banks except boot
bank
Burst Mode Type
00 = Not Supported, 01 = Supported
Page Mode Type
00 = Not Supported, 01 = 4 Word Page, 02
= 8 Word Page
ACC (Acceleration) Supply Minimum
4Dh
4Eh
0085h
0095h
00h = Not Supported, D7-D4: Volt, D3-D0:
100 mV
ACC (Acceleration) Supply Maximum
00h = Not Supported, D7-D4: Volt, D3-D0:
100 mV
Top/Bottom Boot Sector Flag
0001h = Top/Middle Boot Device,
0002h = Bottom Boot Device, 03h = Top
Boot Device
4Fh
0003h
50h
51h
0001h
0001h
Program Suspend. 00h = not supported
Unlock Bypass
00 = Not Supported, 01=Supported
SecSi Sector (Customer OTP Area) Size 2N
bytes
52h
0008h
42
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Data
Addresses S29NS256N S29NS128N S29NS064N
Description
Hardware Reset Low Time-out during an
embedded algorithm to read mode Maximum
2N ns
53h
54h
0008h
0008h
Hardware Reset Low Time-out not during an
embedded algorithm to read mode Maximum
2N ns
55h
56h
57h
0005h
0005h
0010h
Erase Suspend Time-out Maximum 2N ns
Program Suspend Time-out Maximum 2N ns
Bank Organization: X = Number of banks
0010h
0010h
0008h
0008h
Bank 0 Region Information. X = Number of
sectors in bank
58h
59h
5Ah
5Bh
5Ch
5Dh
5Eh
5Fh
60h
61h
62h
63h
64h
65h
66h
67h
68h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
0008h
000Bh
0002h
Bank 1 Region Information. X = Number of
sectors in bank
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0010h
0013h
0008h
0008h
0008h
0008h
0008h
0008h
000Bh
0000h
0000h
0000h
0000h
0000h
0000h
0000h
0000h
Bank 2 Region Information. X = Number of
sectors in bank
Bank 3 Region Information. X = Number of
sectors in bank
Bank 4 Region Information. X = Number of
sectors in bank
Bank 5 Region Information. X = Number of
sectors in bank
Bank 6 Region Information. X = Number of
sectors in bank
Bank 7 Region Information. X = Number of
sectors in bank
Bank 8 Region Information. X = Number of
sectors in bank
Bank 9 Region Information. X = Number of
sectors in bank
Bank 10 Region Information. X = Number of
sectors in bank
Bank 11 Region Information. X = Number of
sectors in bank
Bank 12 Region Information. X = Number of
sectors in bank
Bank 13 Region Information. X = Number of
sectors in bank
Bank 14 Region Information. X = Number of
sectors in bank
Bank 15 Region Information. X = Number of
sectors in bank
Process Technology. 00h = 230 nm, 01h =
170 nm, 02h = 130 nm/110 nm
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
43
A d v a n c e I n f o r m a t i o n
\
Table 18. Sector Address Table, S29NS256N (Sheet 1 of 4)
Bank
Sector
SA0
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
000000h–00FFFFh
010000h–01FFFFh
020000h–02FFFFh
030000h–03FFFFh
040000h–04FFFFh
050000h–05FFFFh
060000h–06FFFFh
070000h–07FFFFh
080000h–08FFFFh
090000h–09FFFFh
0A0000h–0AFFFFh
0B0000h–0BFFFFh
0C0000h–0CFFFFh
0D0000h–0DFFFFh
0E0000h–0EFFFFh
0F0000h–0FFFFFh
100000h–10FFFFh
110000h–11FFFFh
120000h–12FFFFh
130000h–13FFFFh
140000h–14FFFFh
150000h–15FFFFh
160000h–16FFFFh
170000h–17FFFFh
180000h–18FFFFh
190000h–19FFFFh
1A0000h–1AFFFFh
1B0000h–1BFFFFh
1C0000h–1CFFFFh
1D0000h–1DFFFFh
1E0000h–1EFFFFh
1F0000h–1FFFFFh
Bank
Sector
SA32
SA33
SA34
SA35
SA36
SA37
SA38
SA39
SA40
SA41
SA42
SA43
SA44
SA45
SA46
SA47
SA48
SA49
SA50
SA51
SA52
SA53
SA54
SA55
SA56
SA57
SA58
SA59
SA60
SA61
SA62
SA63
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
200000h–20FFFFh
210000h–21FFFFh
220000h–22FFFFh
230000h–23FFFFh
240000h–24FFFFh
250000h–25FFFFh
260000h–26FFFFh
270000h–27FFFFh
280000h–28FFFFh
290000h–29FFFFh
2A0000h–2AFFFFh
2B0000h–2BFFFFh
2C0000h–2CFFFFh
2D0000h–2DFFFFh
2E0000h–2EFFFFh
2F0000h–2FFFFFh
300000h–30FFFFh
310000h–31FFFFh
320000h–32FFFFh
330000h–33FFFFh
340000h–34FFFFh
350000h–35FFFFh
360000h–36FFFFh
370000h–37FFFFh
380000h–38FFFFh
390000h–39FFFFh
3A0000h–3AFFFFh
3B0000h–3BFFFFh
3C0000h–3CFFFFh
3D0000h–3DFFFFh
3E0000h–3EFFFFh
3F0000h–3FFFFFh
SA1
SA2
SA3
SA4
SA5
SA6
SA7
SA8
SA9
SA10
SA11
SA12
SA13
SA14
SA15
SA16
SA17
SA18
SA19
SA20
SA21
SA22
SA23
SA24
SA25
SA26
SA27
SA28
SA29
SA30
SA31
44
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 18. Sector Address Table, S29NS256N (Sheet 2 of 4)
Bank
Sector
SA64
SA65
SA66
SA67
SA68
SA69
SA70
SA71
SA72
SA73
SA74
SA75
SA76
SA77
SA78
SA79
SA80
SA81
SA82
SA83
SA84
SA85
SA86
SA87
SA88
SA89
SA90
SA91
SA92
SA93
SA94
SA95
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
400000h–40FFFFh
410000h–41FFFFh
420000h–42FFFFh
430000h–43FFFFh
440000h–44FFFFh
450000h–45FFFFh
460000h–46FFFFh
470000h–47FFFFh
480000h–48FFFFh
490000h–49FFFFh
4A0000h–4AFFFFh
4B0000h–4BFFFFh
4C0000h–4CFFFFh
4D0000h–4DFFFFh
4E0000h–4EFFFFh
4F0000h–4FFFFFh
500000h–50FFFFh
510000h–51FFFFh
520000h–52FFFFh
530000h–53FFFFh
540000h–54FFFFh
550000h–55FFFFh
560000h–56FFFFh
570000h–57FFFFh
580000h–58FFFFh
590000h–59FFFFh
5A0000h–5AFFFFh
5B0000h–5BFFFFh
5C0000h–5CFFFFh
5D0000h–5DFFFFh
5E0000h–5EFFFFh
5F0000h–5FFFFFh
Bank
Sector
SA96
Sector Size
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
Address Range
600000h–60FFFFh
610000h–61FFFFh
620000h–62FFFFh
630000h–63FFFFh
640000h–64FFFFh
650000h–65FFFFh
660000h–66FFFFh
670000h–67FFFFh
680000h–68FFFFh
690000h–69FFFFh
6A0000h–6AFFFFh
6B0000h–6BFFFFh
6C0000h–6CFFFFh
6D0000h–6DFFFFh
6E0000h–6EFFFFh
6F0000h–6FFFFFh
700000h–70FFFFh
710000h–71FFFFh
720000h–72FFFFh
730000h–73FFFFh
740000h–74FFFFh
750000h–75FFFFh
760000h–76FFFFh
770000h–77FFFFh
780000h–78FFFFh
790000h–79FFFFh
7A0000h–7AFFFFh
7B0000h–7BFFFFh
7C0000h–7CFFFFh
7D0000h–7DFFFFh
7E0000h–7EFFFFh
7F0000h–7FFFFFh
SA97
SA98
SA99
SA100
SA101
SA102
SA103
SA104
SA105
SA106
SA107
SA108
SA109
SA110
SA111
SA112
SA113
SA114
SA115
SA116
SA117
SA118
SA119
SA120
SA121
SA122
SA123
SA124
SA125
SA126
SA127
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
45
A d v a n c e I n f o r m a t i o n
Table 18. Sector Address Table, S29NS256N (Sheet 3 of 4)
Bank
Sector
SA128
SA129
SA130
SA131
SA132
SA133
SA134
SA135
SA136
SA137
SA138
SA139
SA140
SA141
SA142
SA143
SA144
SA145
SA146
SA147
SA148
SA149
SA150
SA151
SA152
SA153
SA154
SA155
SA156
SA157
SA158
SA159
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
800000h–80FFFFh
810000h–81FFFFh
820000h–82FFFFh
830000h–83FFFFh
840000h–84FFFFh
850000h–85FFFFh
860000h–86FFFFh
870000h–87FFFFh
880000h–88FFFFh
890000h–89FFFFh
8A0000h–8AFFFFh
8B0000h–8BFFFFh
8C0000h–8CFFFFh
8D0000h–8DFFFFh
8E0000h–8EFFFFh
8F0000h–8FFFFFh
900000h–90FFFFh
910000h–91FFFFh
920000h–92FFFFh
930000h–93FFFFh
940000h–94FFFFh
950000h–95FFFFh
960000h–96FFFFh
970000h–97FFFFh
980000h–98FFFFh
990000h–99FFFFh
9A0000h–9AFFFFh
9B0000h–9BFFFFh
9C0000h–9CFFFFh
9D0000h–9DFFFFh
9E0000h–9EFFFFh
9F0000h–9FFFFFh
Bank
Sector
SA160
SA161
SA162
SA163
SA164
SA165
SA166
SA167
SA168
SA169
SA170
SA171
SA172
SA173
SA174
SA175
SA176
SA177
SA178
SA179
SA180
SA181
SA182
SA183
SA184
SA185
SA186
SA187
SA188
SA189
SA190
SA191
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
A00000h–A0FFFFh
A10000h–A1FFFFh
A20000h–A2FFFFh
A30000h–A3FFFFh
A40000h–A4FFFFh
A50000h–A5FFFFh
A60000h–A6FFFFh
A70000h–A7FFFFh
A80000h–A8FFFFh
A90000h–A9FFFFh
AA0000h–AAFFFFh
AB0000h–ABFFFFh
AC0000h–ACFFFFh
AD0000h–ADFFFFh
AE0000h–AEFFFFh
AF0000h–AFFFFFh
B00000h–B0FFFFh
B10000h–B1FFFFh
B20000h–B2FFFFh
B30000h–B3FFFFh
B40000h–B4FFFFh
B50000h–B5FFFFh
B60000h–B6FFFFh
B70000h–B7FFFFh
B80000h–B8FFFFh
B90000h–B9FFFFh
BA0000h–BAFFFFh
BB0000h–BBFFFFh
BC0000h–BCFFFFh
BD0000h–BDFFFFh
BE0000h–BEFFFFh
BF0000h–BFFFFFh
46
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 18. Sector Address Table, S29NS256N (Sheet 4 of 4)
Bank
Sector
SA192
SA193
SA194
SA195
SA196
SA197
SA198
SA199
SA200
SA201
SA202
SA203
SA204
SA205
SA206
SA207
SA208
SA209
SA210
SA211
SA212
SA213
SA214
SA215
SA216
SA217
SA218
SA219
SA220
SA221
SA222
SA223
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
C00000h–C0FFFFh
C10000h–C1FFFFh
C20000h–C2FFFFh
C30000h–C3FFFFh
C40000h–C4FFFFh
C50000h–C5FFFFh
C60000h–C6FFFFh
C70000h–C7FFFFh
C80000h–C8FFFFh
C90000h–C9FFFFh
CA0000h–CAFFFFh
CB0000h–CBFFFFh
CC0000h–CCFFFFh
CD0000h–CDFFFFh
CE0000h–CEFFFFh
CF0000h–CFFFFFh
D00000h–D0FFFFh
D10000h–D1FFFFh
D20000h–D2FFFFh
D30000h–D3FFFFh
D40000h–D4FFFFh
D50000h–D5FFFFh
D60000h–D6FFFFh
D70000h–D7FFFFh
D80000h–D8FFFFh
D90000h–D9FFFFh
DA0000h–DAFFFFh
DB0000h–DBFFFFh
DC0000h–DCFFFFh
DD0000h–DDFFFFh
DE0000h–DEFFFFh
DF0000h–DFFFFFh
Bank
Sector
SA224
SA225
SA226
SA227
SA228
SA229
SA230
SA231
SA232
SA233
SA234
SA235
SA236
SA237
SA238
SA239
SA240
SA241
SA242
SA243
SA244
SA245
SA246
SA247
SA248
SA249
SA250
SA251
SA252
SA253
SA254
SA255
SA256
SA257
SA258
Sector Size
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
16 K words
16 K words
16 K words
16 K words
Address Range
E00000h–E0FFFFh
E10000h–E1FFFFh
E20000h–E2FFFFh
E30000h–E3FFFFh
E40000h–E4FFFFh
E50000h–E5FFFFh
E60000h–E6FFFFh
E70000h–E7FFFFh
E80000h–E8FFFFh
E90000h–E9FFFFh
EA0000h–EAFFFFh
EB0000h–EBFFFFh
EC0000h–ECFFFFh
ED0000h–EDFFFFh
EE0000h–EEFFFFh
EF0000h–EFFFFFh
F00000h–F0FFFFh
F10000h–F1FFFFh
F20000h–F2FFFFh
F30000h–F3FFFFh
F40000h–F4FFFFh
F50000h–F5FFFFh
F60000h–F6FFFFh
F70000h–F7FFFFh
F80000h–F8FFFFh
F90000h–F9FFFFh
FA0000h–FAFFFFh
FB0000h–FBFFFFh
FC0000h–FCFFFFh
FD0000h–FDFFFFh
FE0000h–FEFFFFh
FF0000h–FF3FFFh
FF4000h–FF7FFFh
FF8000h–FFBFFFh
FFC000h–FFFFFFh
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
47
A d v a n c e I n f o r m a t i o n
\
Table 19. Sector Address Table, S29NS128N (Sheet 1 of 2)
Bank
Sector
SA0
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
000000h–00FFFFh
010000h–01FFFFh
020000h–02FFFFh
030000h–03FFFFh
040000h–04FFFFh
050000h–05FFFFh
060000h–06FFFFh
070000h–07FFFFh
080000h–08FFFFh
090000h–09FFFFh
0A0000h–0AFFFFh
0B0000h–0BFFFFh
0C0000h–0CFFFFh
0D0000h–0DFFFFh
0E0000h–0EFFFFh
0F0000h–0FFFFFh
100000h–10FFFFh
110000h–11FFFFh
120000h–12FFFFh
130000h–13FFFFh
140000h–14FFFFh
150000h–15FFFFh
160000h–16FFFFh
170000h–17FFFFh
180000h–18FFFFh
190000h–19FFFFh
1A0000h–1AFFFFh
1B0000h–1BFFFFh
1C0000h–1CFFFFh
1D0000h–1DFFFFh
1E0000h–1EFFFFh
1F0000h–1FFFFFh
Bank
Sector
SA32
SA33
SA34
SA35
SA36
SA37
SA38
SA39
SA40
SA41
SA42
SA43
SA44
SA45
SA46
SA47
SA48
SA49
SA50
SA51
SA52
SA53
SA54
SA55
SA56
SA57
SA58
SA59
SA60
SA61
SA62
SA63
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
200000h–20FFFFh
210000h–21FFFFh
220000h–22FFFFh
230000h–23FFFFh
240000h–24FFFFh
250000h–25FFFFh
260000h–26FFFFh
270000h–27FFFFh
280000h–28FFFFh
290000h–29FFFFh
2A0000h–2AFFFFh
2B0000h–2BFFFFh
2C0000h–2CFFFFh
2D0000h–2DFFFFh
2E0000h–2EFFFFh
2F0000h–2FFFFFh
300000h–30FFFFh
310000h–31FFFFh
320000h–32FFFFh
330000h–33FFFFh
340000h–34FFFFh
350000h–35FFFFh
360000h–36FFFFh
370000h–37FFFFh
380000h–38FFFFh
390000h–39FFFFh
3A0000h–3AFFFFh
3B0000h–3BFFFFh
3C0000h–3CFFFFh
3D0000h–3DFFFFh
3E0000h–3EFFFFh
3F0000h–3FFFFFh
SA1
SA2
SA3
SA4
SA5
SA6
SA7
SA8
SA9
SA10
SA11
SA12
SA13
SA14
SA15
SA16
SA17
SA18
SA19
SA20
SA21
SA22
SA23
SA24
SA25
SA26
SA27
SA28
SA29
SA30
SA31
48
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 19. Sector Address Table, S29NS128N (Sheet 2 of 2)
Bank
Sector
SA64
SA65
SA66
SA67
SA68
SA69
SA70
SA71
SA72
SA73
SA74
SA75
SA76
SA77
SA78
SA79
SA80
SA81
SA82
SA83
SA84
SA85
SA86
SA87
SA88
SA89
SA90
SA91
SA92
SA93
SA94
SA95
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
400000h–40FFFFh
410000h–41FFFFh
420000h–42FFFFh
430000h–43FFFFh
440000h–44FFFFh
450000h–45FFFFh
460000h–46FFFFh
470000h–47FFFFh
480000h–48FFFFh
490000h–49FFFFh
4A0000h–4AFFFFh
4B0000h–4BFFFFh
4C0000h–4CFFFFh
4D0000h–4DFFFFh
4E0000h–4EFFFFh
4F0000h–4FFFFFh
500000h–50FFFFh
510000h–51FFFFh
520000h–52FFFFh
530000h–53FFFFh
540000h–54FFFFh
550000h–55FFFFh
560000h–56FFFFh
570000h–57FFFFh
580000h–58FFFFh
590000h–59FFFFh
5A0000h–5AFFFFh
5B0000h–5BFFFFh
5C0000h–5CFFFFh
5D0000h–5DFFFFh
5E0000h–5EFFFFh
5F0000h–5FFFFFh
Bank
Sector
SA96
Sector Size
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
64 K words
16 K words
16 K words
16 K words
16 K words
Address Range
600000h–60FFFFh
610000h–61FFFFh
620000h–62FFFFh
630000h–63FFFFh
640000h–64FFFFh
650000h–65FFFFh
660000h–66FFFFh
670000h–67FFFFh
680000h–68FFFFh
690000h–69FFFFh
6A0000h–6AFFFFh
6B0000h–6BFFFFh
6C0000h–6CFFFFh
6D0000h–6DFFFFh
6E0000h–6EFFFFh
6F0000h–6FFFFFh
700000h–70FFFFh
710000h–71FFFFh
720000h–72FFFFh
730000h–73FFFFh
740000h–74FFFFh
750000h–75FFFFh
760000h–76FFFFh
770000h–77FFFFh
780000h–78FFFFh
790000h–79FFFFh
7A0000h–7AFFFFh
7B0000h–7BFFFFh
7C0000h–7CFFFFh
7D0000h–7DFFFFh
7E0000h–7EFFFFh
7F0000h–7F3FFFh
7F4000h–7F7FFFh
7F8000h–7FBFFFh
7FC000h–7FFFFFh
SA97
SA98
SA99
SA100
SA101
SA102
SA103
SA104
SA105
SA106
SA107
SA108
SA109
SA110
SA111
SA112
SA113
SA114
SA115
SA116
SA117
SA118
SA119
SA120
SA121
SA122
SA123
SA124
SA125
SA126
SA127
SA128
SA129
SA130
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
49
A d v a n c e I n f o r m a t i o n
\
Table 20. Sector Address Table, S29NS064N
Bank
Sector
SA0
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
000000h–00FFFFh
010000h–01FFFFh
020000h–02FFFFh
030000h–03FFFFh
040000h–04FFFFh
050000h–05FFFFh
060000h–06FFFFh
070000h–07FFFFh
080000h–08FFFFh
090000h–09FFFFh
0A0000h–0AFFFFh
0B0000h–0BFFFFh
0C0000h–0CFFFFh
0D0000h–0DFFFFh
0E0000h–0EFFFFh
0F0000h–0FFFFFh
100000h–10FFFFh
110000h–11FFFFh
120000h–12FFFFh
130000h–13FFFFh
140000h–14FFFFh
Bank
Sector
SA32
SA33
SA34
SA35
SA36
SA37
SA38
SA39
SA40
SA41
SA42
SA43
SA44
SA45
SA46
SA47
SA48
SA49
SA50
SA51
SA52
Sector Size
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
Address Range
200000h–20FFFFh
210000h–21FFFFh
220000h–22FFFFh
230000h–23FFFFh
240000h–24FFFFh
250000h–25FFFFh
260000h–26FFFFh
270000h–27FFFFh
280000h–28FFFFh
290000h–29FFFFh
2A0000h–2AFFFFh
2B0000h–2BFFFFh
2C0000h–2CFFFFh
2D0000h–2DFFFFh
2E0000h–2EFFFFh
2F0000h–2FFFFFh
300000h–30FFFFh
310000h–31FFFFh
320000h–32FFFFh
330000h–33FFFFh
340000h–34FFFFh
SA1
SA2
SA3
SA4
SA5
SA6
SA7
SA8
SA9
SA10
SA11
SA12
SA13
SA14
SA15
SA16
SA17
SA18
SA19
SA20
SA21
SA22
SA23
SA24
SA25
SA26
SA27
SA28
SA29
SA30
SA31
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
150000h–15FFFFh
160000h–16FFFFh
170000h–17FFFFh
180000h–18FFFFh
190000h–19FFFFh
1A0000h–1AFFFFh
1B0000h–1BFFFFh
1C0000h–1CFFFFh
1D0000h–1DFFFFh
1E0000h–1EFFFFh
1F0000h–1FFFFFh
SA53
SA54
SA55
SA56
SA57
SA58
SA59
SA60
SA61
SA62
SA63
SA64
SA65
SA66
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
64 Kwords
16 K words
16 K words
16 K words
16 K words
350000h–35FFFFh
360000h–36FFFFh
370000h–37FFFFh
380000h–38FFFFh
390000h–39FFFFh
3A0000h–3AFFFFh
3B0000h–3BFFFFh
3C0000h–3CFFFFh
3D0000h–3DFFFFh
3E0000h–3EFFFFh
3F0000h–3F3FFFh
3F4000h–3F7FFFh
3F8000h–3FBFFFh
3FC000h–3FFFFFh
50
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Command Definitions
Writing specific address and data commands or sequences into the command register initiates
device operations. Table on page 56 defines the valid register command sequences. Writing in-
correct address and data values or writing them in the improper sequence resets the device
to reading array data.
All addresses are latched on the rising edge of AVD#. All data is latched on the rising edge of
WE#. Refer to the AC Characteristics section for timing diagrams.
Reading Array Data
The device is automatically set to reading array data after device power-up. No commands are
required to retrieve data in asynchronous mode. Each bank is ready to read array data after com-
pleting an Embedded Program or Embedded Erase algorithm.
After the device accepts an Erase Suspend command, the corresponding bank enters the erase-
suspend-read mode, after which the system can read data from any non-erase-suspended sector.
After completing a programming operation in the Erase Suspend mode, the system may once
again read array data with the same exception. See the Erase Suspend/Erase Resume Commands
section for more information.
After the device accepts a Program Suspend command, the corresponding bank enters the pro-
gram-suspend-read mode, after which the system can read data from any non-program-
suspended sector within the same bank.
The system must issue the reset command to return a bank to the read (or erase-suspend-read)
mode if DQ5 goes high during an active program or erase operation, or if the bank is in the au-
toselect mode.
See also VersatileIO™ (VIO) Control and Requirements for Synchronous (Burst) Read Operation
in the Device Bus Operations section for more information. The Asynchronous Read and Synchro-
nous/Burst Read tables provide the read parameters, and Figure 13, on page 73 and Figure 14,
on page 74 show the timings.
Set Configuration Register Command Sequence
The device uses a configuration register to set the various burst parameters: number of wait
states, burst read mode, RDY configuration, and synchronous mode active. The configuration reg-
ister must be set before the device will enter burst mode.
The configuration register is loaded with a four-cycle command sequence. The first two cycles are
standard unlock sequences. On the third cycle, the data should be D0h and address bits should
be 555h. During the fourth cycle, the configuration code should be entered onto the data bus with
the address bus set to address 000h. Once the data has been programmed into the configuration
register, a software reset command is required to set the device into the correct state. The device
will power up or after a hardware reset with the default setting, which is in asynchronous mode.
The register must be set before the device can enter synchronous mode. The configuration reg-
ister can not be changed during device operations (program, erase, or sector lock).
Read Configuration Register Command Sequence
The configuration register can be read with a four-cycle command sequence. The first two cycles
are standard unlock sequences. On the third cycle, the data should be C6h and address bits
should be 555h. During the fourth cycle, the configuration code should be read out of the data
bus with the address bus set to address 000h. Once the data has been read from the configuration
register, a software reset command is required to set the device into the correct set mode.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
51
A d v a n c e I n f o r m a t i o n
Read Mode Setting
On power-up or hardware reset, the device is set to be in asynchronous read mode. This setting
allows the system to enable or disable burst mode during system operations.
Programmable Wait State Configuration
The programmable wait state feature informs the device of the number of clock cycles that must
elapse after AVD# is driven active before data will be available. This value is determined by the
input frequency of the device. Configuration Bit CR13–CR11 determine the setting (see Table
21).
The wait state command sequence instructs the device to set a particular number of clock cycles
for the initial access in burst mode. The number of wait states that should be programmed into
the device is directly related to the clock frequency.
Table 21. Programmable Wait State Settings
TotalInitialAccess
CR13
CR12
CR11
Cycles
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
2
3
4
5
6
7 (default)
Reserved
Reserved
Notes:
1. Upon power-up or hardware reset, the default setting is seven wait states.
2. RDY will default to being active with data when the Wait State Setting is set to a
total initial access cycle of 2.
It is recommended that the wait state command sequence be written, even if the default wait
state value is desired, to ensure the device is set as expected. A hardware reset will set the wait
state to the default setting.
Programmable Wait State
The host system should set CR13-CR11 to 101/100/011 for a clock frequency of 80/66/54 MHz
for the system/device to execute at maximum speed.
Table 22 on page 39 describes the typical number of clock cycles (wait states) for various
conditions.
52
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 22. Wait States for Handshaking
Typical No. of Clock Cycles after AVD# Low
Conditions at Address
80 MHz
66 MHz
54 MHz
Initial address (VCCQ = 1.8 V)
7
6
5
Handshaking
For optimal burst mode performance, the host system must set the appropriate number of wait
states in the flash device depending on the clock frequency.
The autoselect function allows the host system to determine whether the flash device is enabled
for handshaking.
Burst Length Configuration
The device supports four different read modes: continuous mode, and 8, 16, and 32 word linear
with or without wrap around modes. A continuous sequence (default) begins at the starting ad-
dress and advances the address pointer until the burst operation is complete. If the highest
address in the device is reached during the continuous burst read mode, the address pointer
wraps around to the lowest address.
For example, an eight-word linear read with wrap around begins on the starting address written
to the device and then advances to the next 8 word boundary. The address pointer then returns
to the 1st word after the previous eight word boundary, wrapping through the starting location.
The sixteen- and thirty-two linear wrap around modes operate in a fashion similar to the eight-
word mode.
Table 23 shows the CR2-CR0 and settings for the four read modes.
Table 23. Burst Length Configuration
Address Bits
Burst Modes
Continuous
CR2
CR1
CR0
0
0
0
1
0
1
1
0
0
0
1
0
8-word linear
16-word linear
32-word linear
Notes:
1. Upon power-up or hardware reset the default setting is continuous.
2. All other conditions are reserved.
Burst Wrap Around
By default, the device will perform burst wrap around with CR3 set to a ‘1’. Changing the CR3 to
a ‘0’ disables burst wrap around.
RDY Configuration
By default, the device is set so that the RDY pin will output VOH whenever there is valid data on
the outputs. The device can be set so that RDY goes active one data cycle before active data. CR8
determines this setting; “1” for RDY active (default) with data, “0” for RDY active one clock cycle
before valid data.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
53
A d v a n c e I n f o r m a t i o n
RDY Polarity
By default, the RDY pin will always indicate that the device is ready to handle a new transaction
with CR10 set to a ‘1’. In this case, the RDY pin is active high. Changing the CR10 to a ‘0’ sets
the RDY pin to be active low. In this case, the RDY pin will always indicate that the device is ready
to handle a new transaction when low.
54
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Configuration Register
Table 24 shows the address bits that determine the configuration register settings
for various device functions.
Table 24. Configuration Register
CR BIt
CR15
CR14
CR13
Function
Reserved
Reserved
Settings (Binary)
0 = Default
0 = Default
000 = Data is valid on the 2nd active CLK edge after AVD# transition to VIH
001 = Data is valid on the 3rd active CLK edge after AVD# transition to VIH
010 = Data is valid on the 4th active CLK edge after AVD# transition to VIH
011 = Data is valid on the 5th active CLK edge after AVD# transition to VIH
100 = Data is valid on the 6th active CLK edge after AVD# transition to VIH
101 = Data is valid on the 7th active CLK edge after AVD# transition to VIH (default)
CR12
Programmable
Wait State
110 = Reserved
111 = Reserved
CR11
CR10
0 = RDY signal is active low
RDY Polarity
1 = RDY signal is active high (default)
CR9
CR8
Reserved
RDY
1 = Default
0 = RDY active one clock cycle before data
1 = RDY active with data (default)
CR7
CR6
CR5
CR4
Reserved
Reserved
Reserved
Reserved
1 = default
1 = default
0 = default
0 = default
0 = No Wrap Around Burst
Burst Wrap
Around
CR3
CR2
1 = Wrap Around Burst (default)
000 = Continuous (default)
010 = 8-Word Linear Burst
CR1
Burst Length 011 = 16-Word Linear Burst
100 = 32-Word Linear Burst
(All other bit settings are reserved)
CR0
Note:Device will be in the default state upon power-up or hardware reset.
Reset Command
Writing the reset command resets the banks to the read or erase-suspend-read mode. Address
bits are don’t cares for this command.
The reset command may be written between the sequence cycles in an erase command sequence
before erasing begins. This resets the bank to which the system was writing to the read mode.
Once erasure begins, however, the device ignores reset commands until the operation
is complete.
The reset command may be written between the sequence cycles in a program command se-
quence before programming begins. This resets the bank to which the system was writing to the
read mode. If the program command sequence is written to a bank that is in the Erase Suspend
mode, writing the reset command returns that bank to the erase-suspend-read mode. Once pro-
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
55
A d v a n c e I n f o r m a t i o n
gramming begins, however, the device ignores reset commands until the operation is
complete.
The reset command may be written between the sequence cycles in an autoselect command se-
quence. Once in the autoselect mode, the reset command must be written to return to the read
mode. If a bank entered the autoselect mode while in the Erase Suspend mode, writing the reset
command returns that bank to the erase-suspend-read mode.
If DQ5 goes high during a program or erase operation, writing the reset command returns the
banks to the read mode (or erase-suspend-read mode if that bank was in Erase Suspend).
Note: If DQ1 goes high during a Write Buffer Programming operation, the system must
write the “Write to Buffer Abort Reset” command sequence to RESET the device to
reading array data. The standard RESET command will not work. See Table 17 on
page 28 for details on this command sequence.
56
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Autoselect Command Sequence
The autoselect command sequence allows the host system to access the manufacturer and device
codes, and determine whether or not a sector is protected. Table on page 56 shows the address
and data requirements. The autoselect command sequence may be written to an address within
a bank that is either in the read or erase-suspend-read mode. The autoselect command may not
be written while the device is actively programming or erasing in the other bank. Autoselect does
not support simultaneous operations or burst mode.
Table 25. Device ID
Description
Address
Read Data
128N
256N
0001h
2D7E
2D2F
2D00
064N
0001h
2B7Eh
2B33h
2B00h
Manufacturer ID
(BA) + 00h
0001h
2C7Eh
2C35h
2C00h
TBD
Device ID, Word 1 (BA) + 01h
Device ID, Word 2 (BA) + 0Eh
Device ID, Word 3 (BA) + 0Fh
Revision ID
(BA) + 03h
(SA) = 02h
Sector Block
Lock/Unlock
0001 - Locked
0000 - Unlocked
DQ15 - DQ8 = Reserved
DQ7 - Factory Lock Bit
1 = Locked, 0 = Not Locked
DQ6 - Customer Lock Bit
1 = Locked, 0 = Not Locked
Indicator Bits
(BA) + 07h DQ5 Handshake Bit
1 = Reserved
0 = Standard Handshake
DQ4 & DQ3 - WP# Protections Boot Code
01 = WP# Protects only the Top Boot Sectors
DQ2-DQ0 = Reserved
The autoselect command sequence is initiated by first writing two unlock cycles. This is followed
by a third write cycle that contains the bank address and the autoselect command. The bank then
enters the autoselect mode. The system may read at any address within the same bank any num-
ber of times without initiating another autoselect command sequence. The following table
describes the address requirements for the various autoselect functions, and the resulting data.
BA represents the bank address. The device ID is read in three cycles. During this time, other
banks are still available to read the data from the memory.
The system must write the reset command to return to the read mode (or erase-suspend-read
mode if the bank was previously in Erase Suspend).
Enter SecSi™ Sector/Exit SecSi Sector Command Sequence
The SecSi Sector region provides a secured data area containing a random, eight word electronic
serial number (ESN). The system can access the SecSi Sector region by issuing the three-cycle
Enter SecSi Sector command sequence. The device continues to access the SecSi Sector region
until the system issues the four-cycle Exit SecSi Sector command sequence. The Exit SecSi Sector
command sequence returns the device to normal operation. The SecSi Sector is not accessible
when the device is executing an Embedded Program or embedded Erase algorithm. Table , “,” on
page 56 shows the address and data requirements for both command sequences.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
57
A d v a n c e I n f o r m a t i o n
Unlock Bypass Command Sequence
The unlock bypass feature allows the system to program faster than the standard program com-
mand sequence. The unlock bypass command sequence is initiated by first writing two unlock
cycles. This is followed by a third write cycle containing the unlock bypass command, 20h. That
bank then enters the unlock bypass mode.
During the unlock bypass mode only the command is valid. To exit the unlock bypass mode, the
system must issue the two-cycle unlock bypass reset command sequence. The first cycle must
contain the bank address and the data 90h. The second cycle need only contain the data 00h. The
bank then returns to the read mode.
Program Command Sequence
Program Command Sequence
Programming is a four-bus-cycle operation. The program command sequence is initiated by writ-
ing two unlock write cycles, followed by the program set-up command. The program address and
data are written next, which in turn initiate the Embedded Program algorithm. The system is not
required to provide further controls or timings. The device automatically provides internally gen-
erated program pulses and verifies the programmed cell margin. Table on page 56 shows the
address and data requirements for the program command sequence.
When the Embedded Program algorithm is complete, that bank then returns to the read mode
and addresses are no longer latched. The system can determine the status of the program oper-
ation by monitoring DQ7 or DQ6/DQ2. Refer to the Write Operation Status section for information
on these status bits.
Any commands written to the device during the Embedded Program Algorithm are ignored. Note
that a hardware reset immediately terminates the program operation. The program command
sequence should be reinitiated once that bank has returned to the read mode, to ensure data
integrity.
Programming is allowed in any sequence and across sector boundaries. A bit cannot be pro-
grammed from “0” back to a “1.” Attempting to do so may causes that bank to set DQ5 = 1
(change-up condition). However, a succeeding read will show that the data is still “0.” Only erase
operations can convert a “0” to a “1.”
Program Command Sequence (Unlock Bypass Mode)
Once the device enters the unlock bypass mode, then a two-cycle unlock bypass program com-
mand sequence is all that is required to program in this mode. The first cycle in this sequence
contains the unlock bypass program command, A0h; the second cycle contains the program ad-
dress and data. Additional data is programmed in the same manner. This mode dispenses with
the initial two unlock cycles required in the standard program command sequence, resulting in
faster total programming time. Table on page 56 shows the requirements for the unlock bypass
command sequences.
Accelerated Program
The device offers accelerated program operations through the ACC input. When the system as-
serts ACC on this input, the device automatically enters the Unlock Bypass mode. The system
may then write the two-cycle Unlock Bypass program command sequence. The device uses the
higher voltage on the ACC input to accelerate the operation.
Figure 1 illustrates the algorithm for the program operation. Refer to the Erase/Program Opera-
tions table in the AC Characteristics section for parameters, and Figure 16, on page 77 for timing
diagrams.
58
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
START
Write Program
Command Sequence
Data Poll
from System
Embedded
Program
algorithm
in progress
Verify Data?
Yes
No
No
Increment Address
Last Address?
Yes
Programming
Completed
Note: See Table for program command sequence.
Figure 1. Program Operation
Write Buffer Programming Command Sequence
Write Buffer Programming Sequence allows for faster programming as compared to the standard
Program Command Sequence. See Table 26 on page 46 for the program command sequence.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
59
A d v a n c e I n f o r m a t i o n
Table 26. Write Buffer Command Sequence
Sequence
Unlock Command 1
Unlock Command 2
Address
555
Data
00AA
0055
Comment
Not required in the Unlock Bypass mode
Same as above
2AA
Starting
Address
Write Buffer Load
0025h
Specify the Number of Program
Locations
Starting
Address
Word
Count
Number of locations to program minus 1
Starting
Address
Program All addresses must be within write-buffer-page boundaries, but
Load 1st data word
Data
do not have to be loaded in any order
Write
Buffer
Location
Program
Data
Load next data word
...
Same as above
...
...
Same as above
Write
Buffer
Location
Program
Data
Load last data word
Same as above
Sector
Address
This command must follow the last write buffer location loaded,
or the operation will ABORT
Write Buffer Program Confirm
Device goes busy
0029h
Status monitoring through DQ
pins (Perform Data Bar Polling
on the Last Loaded Address
)
Notes:
1. Write buffer addresses must be loaded in sequential order.
60
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Write “Write to Buffer”
command and
Sector Address
Part of “Write to Buffer”
Command Sequence
Write number of addresses
to program minus 1(WC)
and Sector Address
Write first address/data
Yes
WC = 0 ?
No
Write to a different
sector address
Abort Write to
Buffer Operation?
Yes
Write to buffer ABORTED.
Must write “Write-to-buffer
Abort Reset” command
sequence to return
No
Write next address/data pair
to read mode.
WC = WC - 1
Write program buffer to
flash sector address
Read DQ15 - DQ0 at
Last Loaded Address
Yes
DQ7 and DQ15 = Data?
No
No
No
DQ1 = 1?
Yes
DQ5 and DQ13 = 1?
Yes
Read DQ15 - DQ0 with
address = Last Loaded
Address
Yes
DQ7 and DQ15 = Data?
No
FAIL or ABORT
PASS
Figure 2. Write Buffer Programming Operation
Chip Erase Command Sequence
Chip Erase Command Sequence
Chip erase is a six bus cycle operation. The chip erase command sequence is initiated by writing
two unlock cycles, followed by a set-up command. Two additional unlock write cycles are then
followed by the chip erase command, which in turn invokes the Embedded Erase algorithm. The
device does not require the system to preprogram prior to erase. The Embedded Erase algorithm
automatically preprograms and verifies the entire memory for an all zero data pattern prior to
electrical erase. The system is not required to provide any controls or timings during these oper-
ations. Table on page 56 shows the address and data requirements for the chip erase command
sequence.
When the Embedded Erase algorithm is complete, that bank returns to the read mode and ad-
dresses are no longer latched. The system can determine the status of the erase operation by
using DQ7 or DQ6/DQ2. Refer to the Write Operation Status section for information on these sta-
tus bits.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
61
A d v a n c e I n f o r m a t i o n
Any commands written during the chip erase operation are ignored. However, note that a hard-
ware reset immediately terminates the erase operation. If that occurs, the chip erase command
sequence should be reinitiated once that bank has returned to reading array data, to ensure data
integrity.
Sector Erase Command Sequence
Sector Erase Command Sequence
Sector erase in normal mode is a six bus cycle operation. The sector erase command sequence is
initiated by writing two unlock cycles, followed by a set-up command. Two additional unlock cycles
are written, and are then followed by the address of the sector to be erased, and the sector erase
command. Table shows the address and data requirements for the sector erase command
sequence.
The device does not require the system to preprogram prior to erase. The Embedded Erase algo-
rithm automatically programs and verifies the entire memory for an all zero data pattern prior to
electrical erase. The system is not required to provide any controls or timings during these
operations.
After the command sequence is written, a sector erase time-out of no less than tSEA, sector erase
accept, occurs. During the time-out period, additional sector addresses and sector erase com-
mands may be written. Loading the sector erase buffer may be done in any sequence, and the
number of sectors may be from one sector to all sectors. The time between these additional cycles
must be less than tSEA. Any sector erase address and command following the exceeded time-out
may or may not be accepted. Any command other than Sector Erase or Erase Suspend dur-
ing the time-out period resets that bank to the read mode.
The system can monitor DQ3 to determine if the sector erase timer has timed out (See the section
on DQ3: Sector Erase start timeout state indicator.). The time-out begins from the rising edge of
the final WE# pulse in the command sequence.
When the Embedded Erase algorithm is complete, the bank returns to reading array data and ad-
dresses are no longer latched. Note that while the Embedded Erase operation is in progress, the
system can read data from the non-erasing banks. The system can determine the status of the
erase operation by reading DQ7 or DQ6/ DQ2 in the erasing bank. Refer to the Write Operation
Status section for information on these status bits.
Once the sector erase operation has begun, only the Erase Suspend command is valid. All other
commands are ignored. However, note that a hardware reset immediately terminates the erase
operation. If that occurs, the sector erase command sequence should be reinitiated once that
bank has returned to reading array data, to ensure data integrity.
62
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Accelerated Sector Erase
The device offers accelerated sector erase operation through the ACC function. This method of
erasing sectors is faster than the standard sector erase command sequence. The accelerated
sector erase function must not be used more than 100 times per sector. In addition, ac-
celerated sector erase should be performed at room temperature (30°C +-10°C).
The following procedure is used to perform accelerated sector erase:
1.
Sectors to be erased must be PPB and DYB cleared. All sectors that remain locked will not be
erased.
2.
3.
4.
Apply 9 V to the ACC input. This voltage must be applied at least 1 µs before executing step 3.
Issue the standard chip erase command.
Monitor status bits DQ2/DQ6 or DQ7 to determine when erasure is complete, just as in the
standard erase operation. See Write Operation Status for further details.
5.
Lower ACC from 9 V to V
.
CC
START
Write Erase
Command Sequence
Data Poll
from System
Embedded
Erase
algorithm
in progress
No
Data = FFh?
Yes
Erasure Completed
Figure 3. Erase Operation
Note: See the section on DQ3 for information on the sector erase start timeout state indicator.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
63
A d v a n c e I n f o r m a t i o n
Erase Suspend/Erase Resume Commands
The Erase Suspend command, B0h, allows the system to interrupt a sector erase operation and
then read data from, program data to, any sector not selected for erasure. The system may also
lock or unlock any sector while the erase operation is suspended. The system must not write
the sector lock/unlock command to sectors selected for erasure. The bank address is re-
quired when writing this command. This command is valid only during the sector erase operation,
including the minimum tSEA time-out period during the sector erase command sequence. The
Erase Suspend command is ignored if written during the chip erase operation or Embedded Pro-
gram algorithm.
When the Erase Suspend command is written during the sector erase operation, the device re-
quires a maximum of tESL, erase suspend latency, to suspend the erase operation. However, when
the Erase Suspend command is written during the sector erase time-out, the device immediately
terminates the time-out period and suspends the erase operation.
After the erase operation has been suspended, the bank enters the erase-suspend-read mode.
The system can read data from or program data to any sector not selected for erasure. (The de-
vice “erase suspends” all sectors selected for erasure.) The system may also lock or unlock any
sector while in the erase-suspend-read mode. Reading at any address within erase-suspended
sectors produces status information on DQ7–DQ0. The system can use DQ7, or DQ6 and DQ2
together, to determine if a sector is actively erasing or is erase-suspended. Refer to the Write Op-
eration Status section for information on these status bits.
After an erase-suspended program operation is complete, the bank returns to the erase-suspend-
read mode. The system can determine the status of the program operation using the DQ7 or DQ6
status bits, just as in the standard program operation. Refer to the Write Operation Status section
for more information.
In the erase-suspend-read mode, the system can also issue the autoselect command sequence.
Refer to the Autoselect Functions and Autoselect Command Sequence sections for details.
To resume the sector erase operation, the system must write the Erase Resume command. The
bank address of the erase-suspended bank is required when writing this command. Further writes
of the Resume command are ignored. Another Erase Suspend command can be written after the
chip has resumed erasing.
Program Suspend/Program Resume Commands
The Program Suspend command allows the system to interrupt a embedded programming oper-
ation or a “Write to Buffer” programming operation so that data can read from any non-suspended
sector. When the Program Suspend command is written during a programming process, the de-
vice halts the programming operation within tPSL, program suspend latency, and updates the
status bits. Addresses are defined when writing the Program Suspend command.
After the programming operation has been suspended, the system can read array data from any
non-suspended sector. The Program Suspend command may also be issued during a program-
ming operation while an erase is suspended. In this case, data may be read from any addresses
not in Erase Suspend or Program Suspend. If a read is needed from the SecSi Sector area (One
Time Program area), then user must use the proper command sequences to enter and exit this
region.
The system may also write the autoselect command sequence when the device is in Program Sus-
pend mode. The device allows reading autoselect codes in the suspended sectors, since the codes
are not stored in the memory array. When the device exits the autoselect mode, the device re-
verts to Program Suspend mode, and is ready for another valid operation. See “Autoselect
Command Sequence” for more information.
64
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
After the Program Resume command is written, the device reverts to programming. The system
can determine the status of the program operation using the DQ7 or DQ6 status bits, just as in
the standard program operation. See “Write Operation Status” for more information.
The system must write the Program Resume command (address bits are “don’t care”) to exit the
Program Suspend mode and continue the programming operation. Further writes of the Program
Resume command are ignored. Another Program Suspend command can be written after the de-
vice has resume programming.
Lock Register Command Set Definitions
The Lock Register Command Set permits the user to one-time program the Persistent Protection
Mode Lock Bit or Password Protection Mode Lock Bit. The Lock Command Set also allows for the
reading of the Persistent Protection Mode Lock Bit or Password Protection Mode Lock Bit.
The Lock Register Command Set Entry command sequence must be issued prior to any of the
commands listed following to enable proper command execution.
Note that issuing the Lock Register Command Set Entry command disables reads and writes
for Bank 0. Reads from other banks excluding Bank 0 are allowed.
Lock Register Program Command
Lock Register Read Command
Lock Register Exit Command
The Lock Register Command Set Exit command must be issued after the execution of the
commands to reset the device to read mode, and re-enables reads and writes for Bank 0.
For the device to be permanently set to the Persistent Protection Mode or the Password Protection
Mode, the sequence of a Lock Register Command Set Exit command, must be initiated after is-
suing the Persistent Protection Mode Lock Bit Program and the Password Protection
Mode Lock Bit Program commands. Note that if the Persistent Protection Mode Lock Bit
and the Password Protection Mode Lock Bit are programmed at the same time, neither will
be programmed.
Password Protection Command Set Definitions
The Password Protection Command Set permits the user to program the 64-bit password, verify
the programming of the 64-bit password, and then later unlock the device by issuing the valid
64-bit password.
The Password Protection Command Set Entry command sequence must be issued prior to
any of the commands listed following to enable proper command execution.
Note that issuing the Password Protection Command Set Entry command disables reads and
writes for Bank 0. Reads for other banks excluding Bank 0 are allowed. However Writes to any
bank are not allowed.
Password Program Command
Password Read Command
Password Unlock Command
The Password Program Command permits programming the password that is used as part of the
hardware protection scheme. The actual password is 64-bits long. There is no special addressing
order required for programming the password.
Once the Password is written and verified, the Password Mode Locking Bit must be set in order to
prevent verification. The Password Program Command is only capable of programming “0”s. Pro-
gramming a “1” after a cell is programmed as a “0” results in a time-out by the Embedded
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
65
A d v a n c e I n f o r m a t i o n
Program Algorithm with the cell remaining as a “0”. The password is all 1’s when shipped from
the factory. All 64-bit password combinations are valid as a password.
The Password Verify Command is used to verify the Password. The Password is verifiable only
when the Password Mode Lock Bit is not programmed. If the Password Mode Lock Bit is pro-
grammed and the user attempts to verify the Password, the device will always drive all 1’s onto
the DQ data bus.
The lower two address bits (A1–A0) are valid during the Password Read, Password Program, and
Password Unlock.
The Password Unlock command is used to clear the PPB Lock Bit so that the PPBs can be unlocked
for modification, thereby allowing the PPBs to become accessible for modification. The exact pass-
word must be entered in order for the unlocking function to occur. This command cannot be issued
any faster than 1 µs at a time to prevent a hacker from running through the all 64-bit combina-
tions in an attempt to correctly match a password. If the command is issued before the 1 µs
execution window for each portion of the unlock, the command will be ignored.
The Password Unlock function is accomplished by writing Password Unlock command and data to
the device to perform the clearing of the PPB Lock Bit. The password is 64 bits long. A1 and A0
are used for matching. Writing the Password Unlock command does not need to be address order
specific. An example sequence is starting with the lower address A1–A0= 00, followed by A1–A0=
01, A1–A0= 10, and A1–A0= 11.
Approximately 1 uSec is required for unlocking the device after the valid 64-bit password is given
to the device. It is the responsibility of the microprocessor to keep track of the entering the por-
tions of the 64-bit password with the Password Unlock command, the order, and when to read the
PPB Lock bit to confirm successful password unlock. In order to re-lock the device into the Pass-
word Mode, the PPB Lock Bit Set command can be re-issued.
The Password Protection Command Set Exit command must be issued after the execution of
the commands listed previously to reset the device to read mode, otherwise the device will hang.
Note that issuing the Password Protection Command Set Exit command re-enables reads and
writes for Bank 0.
Non-Volatile Sector Protection Command Set Definitions
The Non-Volatile Sector Protection Command Set permits the user to program the Persistent Pro-
tection Bits (PPBs), erase all of the Persistent Protection Bits (PPBs), and read the logic state of
the Persistent Protection Bits (PPBs).
The Non-Volatile Sector Protection Command Set Entry command sequence must be issued
prior to any of the commands listed following to enable proper command execution.
Note that issuing the Non-Volatile Sector Protection Command Set Entry command disables
reads and writes for Active Bank. Reads from other banks excluding Active Bank are allowed.
PPB Program Command
All PPB Erase Command
PPB Status Read Command
The PPB Program command is used to program, or set, a given PPB. Each PPB is individually pro-
grammed (but is bulk erased with the other PPBs). The specific sector addresses (AMAX–A14) are
written at the same time as the program command. If the PPB Lock Bit is set, the PPB Program
command will not execute and the command will time-out without programming the PPB.
The All PPB Erase command is used to erase all PPBs in bulk. There is no means for individually
erasing a specific PPB. Unlike the PPB program, no specific sector address is required. However,
when the PPB erase command is written, all Sector PPBs are erased in parallel. If the PPB Lock
Bit is set the ALL PPB Erase command will not execute and the command will time-out without
erasing the PPBs.
66
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
The device will preprogram all PPBs prior to erasing when issuing the All PPB Erase command.
Also note that the total number of PPB program/erase cycles has the same endurance as the flash
memory array.
The programming state of the PPB for a given sector can be verified by writing a PPB Status Read
Command to the device. See Figure 4, on page 53 for the PPB program/erase algorithm.
Enter PPB
Command Set.
Addr = BA
Program PPB Bit.
Addr = SA
Read Byte.
Addr = SA0
Read Byte.
Addr = SA0
No
DQ6 =
Toggle?
Yes
DQ5 = 1?
Yes
Read Byte Twice.
Addr = SA0
No
Read Byte.
Addr = SA
DQ6 =
Toggle?
Yes
DQ0 =
No
'1' (Erase)
'0' (Pgm.)?
FAIL
Yes
Issue Reset
Command
PASS
Exit PPB
Command Set
Figure 4. PPB Program/Erase Algorithm
Note: The bank entered during entry is the active bank. Take for example the active bank is
BA0. Any reads in BA0 will result in status reads of the PPB bit. If the user wants to set (pro-
grammed to “0”) in a different bank other than the active bank, say for example BA5, then the
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
67
A d v a n c e I n f o r m a t i o n
active bank switches from BA0 to BA5. Reading in BA5 will result in status read of the bit whereas
reading in BA0 will result in true data.
The Non-Volatile Sector Protection Command Set Exit command must be issued after the
execution of the commands listed previously to reset the device to read mode. Note that issuing
the Non-Volatile Sector Protection Command Set Exit command re-enables reads and writes
for Active Bank.
After entering the PPB Mode
The PPB Status Read (BA) is the Mode entry (BA)
If PPB Program command is given, the new PPB Status Read (BA) will be the
same (BA) as given in the PPB Program.
If PPB Erase command is given, the new PPB Status Read (BA) is the same
(BA) as given in the PPB Program or PPB Set Entry, whichever was last.
During PPB Program or Erase Operation, PPB status read is not available. Only
polling data is available in Bank0 and no other bank. Reading from all other
banks will give core data.
Global Volatile Sector Protection Freeze Command Set
The Global Volatile Sector Protection Freeze Command Set permits the user to set the PPB Lock
Bit and reading the logic state of the PPB Lock Bit.
The Volatile Sector Protection Freeze Command Set Entry command sequence must be is-
sued prior to any of the commands listed following to enable proper command execution.
Reads from all banks excluding mode entry bank are allowed.
PPB Lock Bit Set Command
PPB Lock Bit Status Read Command
The PPB Lock Bit Set command is used to set the PPB Lock bit if it is cleared either at reset or if
the Password Unlock command was successfully executed. There is no PPB Lock Bit Clear com-
mand. Once the PPB Lock Bit is set, it cannot be cleared unless the device is taken through a
power-on clear (for Persistent Sector Protection Mode) or the Password Unlock command is exe-
cuted (for Password Sector Protection Mode). If the Password Mode Locking Bit is set, the PPB
Lock Bit status is reflected as set, even after a power-on reset cycle.
The programming state of the PPB Lock Bit can be verified by executing a PPB Lock Bit Status
Read Command to the device.
The Global Volatile Sector Protection Freeze Command Set Exit command must be issued
after the execution of the commands listed previously to reset the device to read mode.
Volatile Sector Protection Command Set
The Volatile Sector Protection Command Set permits the user to set the Dynamic Protection Bit
(DYB), clear the Dynamic Protection Bit (DYB), and read the logic state of the Dynamic Protection
Bit (DYB).
The Volatile Sector Protection Command Set Entry command sequence must be issued prior
to any of the commands listed following to enable proper command execution.
Note that issuing the Volatile Sector Protection Command Set Entry command disables reads
and writes for the bank selected with the command. Reads for other banks excluding the selected
bank are allowed.
DYB Set Command
DYB Clear Command
DYB Status Read Command
68
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
The DYB Set/Clear command is used to set or clear a DYB for a given sector. The high order ad-
dress bits (A23–A14 for the NS256N, A22–A14 for the NS128N, A21–A14 for the NS064N) are
issued at the same time as the code 00h or 01h on DQ7-DQ0. All other DQ data bus pins are
ignored during the data write cycle. The DYBs are modifiable at any time, regardless of the state
of the PPB or PPB Lock Bit. The DYBs are set at power-up or hardware reset.
The programming state of the DYB for a given sector can be verified by writing a DYB Status Read
Command to the device.
Note: The bank entered during entry is the active bank. Take for example the active bank is
BA0. Any reads in BA0 will result in status reads of the DYB bit. If the user wants to set (pro-
grammed to “0”) in a different bank other than the active bank, say for example BA5, then the
active bank switches from BA0 to BA5. Reading in BA5 will result in status read of the bit
whereas reading in BA0 will result in true data.
The Volatile Sector Protection Command Set Exit command must be issued after the execu-
tion of the commands listed previously to reset the device to read mode.
Note that issuing the Volatile Sector Protection Command Set Exit command re-enables
reads and writes for the bank selected.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
69
A d v a n c e I n f o r m a t i o n
Table 27. Command Definitions (Sheet 1 of 3)
Bus Cycles (Notes 1–6)
Command Sequence
(Notes)
First
Second
Third
Fourth
Fifth
Sixth
Seventh
Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data
Asynchronous Read (7)
Reset (8)
1
1
RA
RD
F0
XXX
(BA)
555
(BA)
X00
Manufacturer ID
Device ID
4
6
4
4
555
555
555
555
AA
AA
AA
AA
2AA
2AA
2AA
2AA
55
55
55
55
90
90
90
0001
(BA)
555
(BA) (Note (BA) (Note (BA) (Note
X01
10)
X0E
10)
X0F
10)
Indicator Bits
(11)
(BA)
555
(BA) (Note
X0D
11)
(BA)
555
(BA)
X03
Revision ID
90
20
Mode Entry
3
2
555
XXX
AA
A0
2AA
PA
55
PD
555
Program (12)
Reset (13)
2
BA
90
XXX
00
CFI
1
4
6
1
55
555
555
SA
98
AA
AA
29
Program
2AA
2AA
55
55
555
SA
A0
25
PA
SA
PD
Write to Buffer (17)
Program Buffer to Flash
WC
PA
PD
WBL
PD
Write to Buffer Abort Reset
(20)
3
555
AA
2AA
55
555
F0
Chip Erase
6
6
555
555
AA
AA
2AA
2AA
55
55
555
555
80
80
555
555
AA
AA
2AA
2AA
55
55
555
SA
10
30
Sector Erase
Erase Suspend / Program
Suspend (14)
1
1
4
4
BA
BA
B0
30
AA
AA
Erase Resume / Program
Resume (15)
Set Config. Register (28)
555
555
2AA
2AA
55
55
555
555
D0
C6
X00
X00
CR
CR
Read Configuration Register
Lock Register Command Set Definitions
Lock Register
Command Set
Entry
3
555
XX
AA
2AA
00
55
555
40
Lock Register
Bits Program
(Note 23)
2
1
2
A0
data
90
data
Lock
Lock Register
Bits Read
(BA0)
00
Lock Register
Command Set
Exit (note 24)
XX
XX
00
70
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 27. Command Definitions (Sheet 2 of 3)
Bus Cycles (Notes 1–6)
Command Sequence
(Notes)
First
Second
Third
Fourth
Fifth
Sixth
Seventh
Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data
Password Protection Command Set Definitions
Password
Protection
Command Set
Entry
3
2
555
AA
2AA
55
555
60
PWD
0/
PWD
1/
PWD
2/
PWD
3
00/
01/
02/
03
Password
Program (note
24, 26)
XX
A0
Password
Password Read
(note 27)
PWD
0
PWD
1
PWD
2
PWD
3
4
7
00
00
01
00
02
00
03
01
Password Unlock
(note 26)
PWD
0
PWD
1
PWD
2
PWD
3
25
90
03
00
02
03
00
29
Password
Protection
Command Set
Exit
2
3
XX
XX
Non-Volatile Sector Protection Command Set Definitions
Non-Volatile
SectorProtection
Command Set
Entry
(BA)
555
555
AA
2AA
55
C0
(BA)
SA
PPB Program
(29)
2
2
1
XX
XX
A0
80
00
30
All PPB Erase
(Notes 19) (29)
PPB
00
(BA)
SA
RD
(0)
PPB Status Read
Non-Volatile
SectorProtection
Command Set
Exit
2
XX
90
XX
00
Global Volatile Sector Protection Command Set Definitions
Global Volatile
SectorProtection
Freeze
Command Set
Entry
(BA)
555
3
555
AA
2AA
XX
55
00
50
PPB Lock Bit Set
2
1
XX
A0
PPB Lock
Bit
PPB Lock Bit
Status Read
(BA)
XX
RD
(0)
Global Volatile
SectorProtection
Freeze
2
XX
90
XX
00
Command Set
Exit
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
71
A d v a n c e I n f o r m a t i o n
Table 27. Command Definitions (Sheet 3 of 3)
Bus Cycles (Notes 1–6)
Command Sequence
(Notes)
First
Second
Third
Fourth
Fifth
Sixth
Seventh
Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data Addr Data
SecSi Sector Command Definitions
SecSi Sector
Entry (Note
21)
3
555
AA
2AA
00
55
555
88
SecSi Sector
Program
2
1
4
XX
00
A0
data
AA
data
SecSi
Sector
SecSi Sector
Read
SecSi Sector
Exit (note 24)
555
2AA
55
555
90
XX
00
Volatile Sector Protection Command Set Definitions
Volatile Sector
Protection
Command Set
Entry (Note 21)
(BA)
555
3
555
AA
2AA
55
E0
(BA)
SA
DYB Set
2
2
1
XX
XX
A0
A0
00
01
(BA)
SA
DYB
DYB Clear
(BA)
SA
DYB Status Read
RD(0)
Volatile Sector
Protection
Command Set
Exit (note 24)
2
XX
90
XX
00
Legend:
X = Don’t care
RA = Address of the memory location to be read.
RD = Data read from location RA during read operation.
PA = Address of the memory location to be programmed. Addresses latch on the falling edge of the WE# or CE# pulse, whichever
happens later.
PD = Data to be programmed at location PA. Data latches on the rising edge of WE# or CE# pulse, whichever happens first.
PD(0) = SecSi Sector Lock Bit. PD(0), or bit[0].
PD(1) = Persistent Protection Mode Lock Bit. PD(1), or bit[1], must be set to ‘0’ for protection while PD(2), bit[2] must be left as
‘1’.
PD(2) = Password Protection Mode Lock Bit. PD(2), or bit[2], must be set to ‘0’ for protection while PD(1), bit[1] must be left as ‘1’.
PD(3) = Protection Mode OTP Bit. PD(3) or bit[3].
SA = Address of the sector to be verified (in autoselect mode) or erased. SA includes BA. Address bits Amax–A13 uniquely select
any sector.
BA = Address of the bank (A23–A21 for S29NS256N, A22–A20 for S29NS128N, A21–A19 for S29NS064N) that is being switched to
autoselect mode, is in bypass mode, or is being erased.
CR = Configuration Register set by data bits D15-D0.
PWD3–PWD0 = Password Data. PD3–PD0 present four 16 bit combinations that represent the 64-bit Password
PWA = Password Address. Address bits A1 and A0 are used to select each 16-bit portion of the 64-bit entity.
PWD = Password Data.
RD(0) = DQ0 protection indicator bit. If protected, DQ0 = 0, if unprotected, DQ0 = 1.
72
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
RD(1) = DQ1 protection indicator bit. If protected, DQ1 = 0, if unprotected, DQ1 = 1.
RD(2) = DQ2 protection indicator bit. If protected, DQ2 = 0, if unprotected, DQ2 = 1.
RD(4) = DQ4 protection indicator bit. If protected, DQ4 = 0, if unprotected, DQ4 = 1.
WBL = Write Buffer Location. Address must be within the same write buffer page as PA.
WC = Word Count. Number of write buffer locations to load minus 1.
Notes:
1. See Table 1 for description of bus operations.
2. All values are in hexadecimal.
3. Except for the read cycle and the fourth cycle of the autoselect command sequence, all bus cycles are write cycles.
4. Data bits DQ15–DQ8 are don’t care in command sequences, except for RD and PD.
5. Unless otherwise noted, address bits Amax–A12 are don’t cares.
6. Writing incorrect address and data values or writing them in the improper sequence may place the device in an unknown
state. The system must write the reset command to return the device to reading array data.
7. No unlock or command cycles required when bank is reading array data.
8. The Reset command is required to return to reading array data (or to the erase-suspend-read mode if previously in Erase
Suspend) when a bank is in the autoselect mode, or if DQ5 goes high (while the bank is providing status information).
9. The fourth cycle of the autoselect command sequence is a read cycle. The system must read device IDs across the 4th, 5th,
and 6th cycles, The system must provide the bank address. See the Autoselect Command Sequence section for more
information.
10. See Table 25 for description of bus operations.
11. See the “Autoselect Command Sequence” section on page 43.
12. The Unlock Bypass command sequence is required prior to this command sequence.
13. The Unlock Bypass Reset command is required to return to reading array data when the bank is in the unlock bypass mode.
14. The system may read and program in non-erasing sectors, or enter the autoselect mode, when in the Erase Suspend mode.
The Erase Suspend command is valid only during a sector erase operation, and requires the bank address.
15. The Erase Resume command is valid only during the Erase Suspend mode, and requires the bank address.
16. Command is valid when device is ready to read array data or when device is in autoselect mode.
17. The total number of cycles in the command sequence is determined by the number of words written to the write buffer. The
maximum number of cycles in the command sequence is 37.
18. The entire four bus-cycle sequence must be entered for which portion of the password.
19. The ALL PPB ERASE command will pre-program all PPBs before erasure to prevent over-erasure of PPBs.
20. Command sequence resets device for next command after write-to-buffer operation.
21. Entry commands are needed to enter a specific mode to enable instructions only available within that mode.
22. Write Buffer Programming can be initiated after Unlock Bypass Entry.
23. If both the Persistent Protection Mode Locking Bit and the password Protection Mode Locking Bit are set a the same time, the
command operation will abort and return the device to the default Persistent Sector Protection Mode.
24. The Exit command must be issued to reset the device into read mode. Otherwise the device will hang.
25. Note: Autoselect, CFI, OTP, Unlock Bypass Mode and all ASP modes cannot be nested with each other.
26. Only A7 - A0 (lower address bits) are used
27. Amax–A0 (all address bits) are used.
28. Requires the RESET# command to configure the configuration register.
29. See Figure 4 for details.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
73
A d v a n c e I n f o r m a t i o n
Write Operation Status
The device provides several bits to determine the status of a program or erase operation: DQ2,
DQ3, DQ5, DQ6, and DQ7. Table 29 on page 66 and the following subsections describe the func-
tion of these bits. DQ7 and DQ6 each offers a method for determining whether a program or erase
operation is complete or in progress.
DQ7: Data# Polling
The Data# Polling bit, DQ7, indicates to the host system whether an Embedded Program or Erase
algorithm is in progress or completed, or whether a bank is in Erase Suspend. Data# Polling is
valid after the rising edge of the final WE# pulse in the command sequence. Note that the
Data# Polling is valid only for the last word being programmed in the write-buffer-page
during Write Buffer Programming. Reading Data# Polling status on any word other
than the last word to be programmed in the write-buffer-page will return false status
information.
During the Embedded Program algorithm, the device outputs on DQ7 the complement of the
datum programmed to DQ7. This DQ7 status also applies to programming during Erase Suspend.
When the Embedded Program algorithm is complete, the device outputs the datum programmed
to DQ7. The system must provide the program address to read valid status information on DQ7.
If a program address falls within a protected sector, Data# Polling on DQ7 is active for approxi-
mately tPSP, then that bank returns to the read mode.
During the Embedded Erase algorithm, Data# Polling produces a “0” on DQ7. When the Embed-
ded Erase algorithm is complete, or if the bank enters the Erase Suspend mode, Data# Polling
produces a “1” on DQ7. The system must provide an address within any of the sectors selected
for erasure to read valid status information on DQ7.
After an erase command sequence is written, if all sectors selected for erasing are protected,
Data# Polling on DQ7 is active for approximately tASP, then the bank returns to the read mode.
If not all selected sectors are protected, the Embedded Erase algorithm erases the unprotected
sectors, and ignores the selected sectors that are protected. However, if the system reads DQ7
at an address within a protected sector, the status may not be valid.
Just prior to the completion of an Embedded Program or Erase operation, DQ7 may change asyn-
chronously with DQ6–DQ0 while Output Enable (OE#) is asserted low. That is, the device may
change from providing status information to valid data on DQ7. Depending on when the system
samples the DQ7 output, it may read the status or valid data. Even if the device has completed
the program or erase operation and DQ7 has valid data, the data outputs on DQ6–DQ0 may be
still invalid. Valid data on DQ7–DQ0 will appear on successive read cycles.
Table 29 on page 66 shows the outputs for Data# Polling on DQ7. Figure 5, on page 61 shows the
Data# Polling algorithm. Figure 19, on page 80 in the AC Characteristics section shows the Data#
Polling timing diagram.
74
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
START
Read DQ7–DQ0
Addr = VA
Yes
DQ7 = Data?
No
No
DQ5 = 1?
Yes
Read DQ7–DQ0
Addr = VA
Yes
DQ7 = Data?
No
PASS
FAIL
Notes:
1. VA = Valid address for programming. During a
sector erase operation, a valid address is any sector
address within the sector being erased. During chip
erase, a valid address is any non-protected sector
address.
2. DQ7 should be rechecked even if DQ5 = “1” because
DQ7 may change simultaneously with DQ5.
Figure 5. Data# Polling Algorithm
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
75
A d v a n c e I n f o r m a t i o n
RDY: Ready
The RDY pin is a dedicated status output that indicates valid output data on A/DQ15–A/DQ0 dur-
ing burst (synchronous) reads. When RDY is asserted (RDY = VOH), the output data is valid and
can be read. When RDY is de-asserted (RDY = VOL), the system should wait until RDY is re-as-
serted before expecting the next word of data.
In synchronous (burst) mode with CE# = OE# = VIL, RDY is de-asserted under the following con-
ditions: during the initial access; after crossing the internal boundary between addresses 7Eh and
7Fh (and addresses offset from these by a multiple of 64). The RDY pin will also switch during
status reads when a clock signal drives the CLK input. In addition, RDY = VOH when CE# = VIL
and OE# = VIH, and RDY is Hi-Z when CE# = VIH
In asynchronous (non-burst) mode, the RDY pin does not indicate valid or invalid output data.
Instead, RDY = VOH when CE# = VIL, and RDY is Hi-Z when CE# = VIH
.
.
DQ6: Toggle Bit I
Toggle Bit I on DQ6 indicates whether an Embedded Program or Erase algorithm is in progress or
complete, or whether the device has entered the Erase Suspend mode. Toggle Bit I may be read
at any address in the same bank, and is valid after the rising edge of the final WE# pulse in the
command sequence (prior to the program or erase operation), and during the sector erase time-
out.
During an Embedded Program or Erase algorithm operation, successive read cycles to any ad-
dress cause DQ6 to toggle. Note that OE# must be low during toggle bit status reads. When the
operation is complete, DQ6 stops toggling.
After an erase command sequence is written, if all sectors selected for erasing are protected, DQ6
toggles for approximately tASP, all sectors protected toggle time, then returns to reading array
data. If not all selected sectors are protected, the Embedded Erase algorithm erases the unpro-
tected sectors, and ignores the selected sectors that are protected.
The system can use DQ6 and DQ2 together to determine whether a sector is actively erasing or
is erase-suspended. When the device is actively erasing (that is, the Embedded Erase algorithm
is in progress), DQ6 toggles. When the device enters the Erase Suspend mode, DQ6 stops tog-
gling. However, the system must also use DQ2 to determine which sectors are erasing or erase-
suspended. Alternatively, the system can use DQ7 (see the subsection on DQ7: Data# Polling).
If a program address falls within a protected sector, DQ6 toggles for approximately tPSP after the
program command sequence is written, then returns to reading array data.
DQ6 also toggles during the erase-suspend-program mode, and stops toggling once the Embed-
ded Program algorithm is complete.
See the following for additional information: (toggle bit flowchart), DQ6: Toggle Bit I (descrip-
tion), 20 (toggle bit timing diagram), and Table 28 on page 64 (compares DQ2 and DQ6).
DQ2: Toggle Bit II
The “Toggle Bit II” on DQ2, when used with DQ6, indicates whether a particular sector is actively
erasing (that is, the Embedded Erase algorithm is in progress), or whether that sector is erase-
suspended. Toggle Bit II is valid after the rising edge of the final WE# pulse in the command
sequence.
DQ2 toggles when the system reads at addresses within those sectors that have been selected
for erasure. Note that OE# must be low during toggle bit status reads. But DQ2 cannot distinguish
whether the sector is actively erasing or is erase-suspended. DQ6, by comparison, indicates
whether the device is actively erasing, or is in Erase Suspend, but cannot distinguish which sec-
76
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
tors are selected for erasure. Thus, both status bits are required for sector and mode information.
Refer to Table 29 on page 66 to compare outputs for DQ2 and DQ6.
See the following for additional information: (toggle bit flowchart), DQ6: Toggle Bit I (descrip-
tion), 20 (toggle bit timing diagram), and Table 28 on page 64 (compares DQ2 and DQ6).
START
Read Byte
DQ7-DQ0
Address = VA
Read Byte
DQ7-DQ0
Address = VA
No
DQ6 = Toggle?
Yes
No
DQ5 = 1?
Yes
Read Byte Twice
DQ7-DQ0
Adrdess = VA
No
DQ6 = Toggle?
Yes
FAIL
PASS
Note:
The system should recheck the toggle bit even if DQ5 =
“1” because the toggle bit may stop toggling as DQ5
changes to “1.” See the subsections on DQ6 and DQ2
for more information.
Figure 6. Toggle Bit Algorithm
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
77
A d v a n c e I n f o r m a t i o n
Table 28. DQ6 and DQ2 Indications
If device is
and the system reads
then DQ6
and DQ2
programming,
at any address,
toggles,
does not toggle.
at an address within a sector
selected for erasure,
toggles,
toggles,
also toggles.
does not toggle.
toggles.
actively erasing,
erase suspended,
at an address within sectors not
selected for erasure,
at an address within a sector
selected for erasure,
does not toggle,
returns array data,
toggles,
at an address within sectors not
returns array data. The system can read
from any sector not selected for erasure.
selected for erasure,
programming in
erase suspend
at any address,
is not applicable.
Reading Toggle Bits DQ6/DQ2
Whenever the system initially begins reading toggle bit status, it must read DQ7–DQ0 at least
twice in a row to determine whether a toggle bit is toggling. Typically, the system would note and
store the value of the toggle bit after the first read. After the second read, the system would com-
pare the new value of the toggle bit with the first. If the toggle bit is not toggling, the device has
completed the program or erase operation. The system can read array data on DQ7–DQ0 on the
following read cycle.
However, if after the initial two read cycles, the system determines that the toggle bit is still tog-
gling, the system also should note whether the value of DQ5 is high (see the section on DQ5). If
it is, the system should then determine again whether the toggle bit is toggling, since the toggle
bit may have stopped toggling just as DQ5 went high. If the toggle bit is no longer toggling, the
device has successfully completed the program or erase operation. If it is still toggling, the device
did not completed the operation successfully, and the system must write the reset command to
return to reading array data.
The remaining scenario is that the system initially determines that the toggle bit is toggling and
DQ5 has not gone high. The system may continue to monitor the toggle bit and DQ5 through suc-
cessive read cycles, determining the status as described in the previous paragraph. Alternatively,
it may choose to perform other system tasks. In this case, the system must start at the beginning
of the algorithm when it returns to determine the status of the operation.
DQ5: Exceeded Timing Limits
DQ5 indicates whether the program or erase time has exceeded a specified internal pulse count
limit. Under these conditions DQ5 produces a “1,” indicating that the program or erase cycle was
not successfully completed.
The device may output a “1” on DQ5 if the system tries to program a “1” to a location that was
previously programmed to “0.” Only an erase operation can change a “0” back to a “1.”
Under this condition, the device halts the operation, and when the timing limit has been exceeded,
DQ5 produces a “1.”
Under both these conditions, the system must write the reset command to return to the read
mode (or to the erase-suspend-read mode if a bank was previously in the erase-suspend-program
mode).
78
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
DQ3: Sector Erase Start Timeout State Indicator
After writing a sector erase command sequence, the system may read DQ3 to determine whether
or not erasure has begun. (The sector erase timer does not apply to the chip erase command.) If
additional sectors are selected for erasure, the entire time-out also applies after each additional
sector erase command. When the time-out period is complete, DQ3 switches from a “0” to a “1.”
If the time between additional sector erase commands from the system can be assumed to be
less than tSEA, the system need not monitor DQ3. See also the Sector Erase Command Sequence
section.
After the sector erase command is written, the system should read the status of DQ7 (Data# Poll-
ing) or DQ6 (Toggle Bit I) to ensure that the device has accepted the command sequence, and
then read DQ3. If DQ3 is “1,” the Embedded Erase algorithm has begun; all further commands
(except Erase Suspend) are ignored until the erase operation is complete. If DQ3 is “0,” the device
will accept additional sector erase commands. To ensure the command has been accepted, the
system software should check the status of DQ3 prior to and following each subsequent sector
erase command. If DQ3 is high on the second status check, the last command might not have
been accepted.
Table 29 on page 66 shows the status of DQ3 relative to the other status bits.
DQ1: Write to Buffer Abort
DQ1 indicates whether a Write to Buffer operation was aborted. Under these conditions DQ1 pro-
duces a ‘1’. The system must issue the Write to Buffer Abort Reset command sequence to return
the device to reading array data. See “Write Buffer Programming Operation” on page 15 for more
details.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
79
A d v a n c e I n f o r m a t i o n
Table 29. Write Operation Status
DQ7
DQ5
DQ2
DQ1
Status
(Note 2)
DQ6
Toggle
Toggle
(Note 1)
DQ3
N/A
1
(Note 2) (Note 4)
Embedded Program Algorithm
Embedded Erase Algorithm
DQ7#
0
0
0
No toggle
Toggle
0
Standard
Mode
N/A
Reading within Program Suspended
Sector
Valid data for all address except the address being programed, which
will return invalid data
Program
Suspend
Mode
Reading within Non-Program
Suspended Sector
Data
(Note 3)
Erase
Suspended Sector
1
No toggle
Data
0
N/A
Toggle
Data
N/A
Erase-Suspend-
Erase
Suspend
Mode
Read
Non-Erase
Data
Data
Data
Data
Suspended Sector
Erase-Suspend-Program
BUSY State
DQ7#
DQ7#
DQ7#
DQ7#
Toggle
Toggle
Toggle
Toggle
0
0
1
0
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0
Write to
Buffer
(Note 5)
Exceeded Timing Limits
ABORT State
0
1
Notes:
1. DQ5 switches to ‘1’ when an Embedded Program or Embedded Erase operation has exceeded the maximum timing limits.
Refer to the section on DQ5 for more information.
2. DQ7 and DQ2 require a valid address when reading status information. Refer to the appropriate subsection for
further details.
3. Data are invalid for addresses in a Program Suspended sector.
4. DQ1 indicates the Write to Buffer ABORT status during Write Buffer Programming operations.
5. The data-bar polling algorithm should be used for Write Buffer Programming operations. Note that DQ7# during
Write Buffer Programming indicates the data-bar for DQ7 data for the LAST LOADED WRITE-BUFFER ADDRESS
location.
80
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Absolute Maximum Ratings
Storage Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . –65°C to +150°C
Ambient Temperature with Power Applied . . . . . . . . . . . . . . –65°C to +125°C
Voltage with Respect to Ground, All Inputs and I/Os
except ACC (Note 1) . . . . . . . . . . . . . . . . . . . . . . . . . –0.5 V to VCC + 0.5 V
VCC (Note 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .–0.5 V to +2.5 V
ACC (Note 2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . –0.5 V to + 9.5 V
Output Short Circuit Current (Note 3). . . . . . . . . . . . . . . . . . . . . . . . 100 mA
Notes:
1. Minimum DC voltage on input or I/Os is –0.5 V. During voltage transitions, input at I/Os may undershoot VSS to –2.0 V for
periods of up to 20 ns during voltage transitions inputs might overshooot to VCC +0.5 V for periods up to 20 ns. See Figure
7. Maximum DC voltage on output and I/Os is VCC + 0.5 V. During voltage transitions outputs may overshoot to VCC + 2.0 V
for periods up to 20 ns. See Figure 8.
2. Minimum DC input voltage on ACC is –0.5 V. During voltage transitions, ACC may undershoot VSS to –2.0 V for periods of up
to 20 ns. See Figure 7. Maximum DC input voltage on ACC is +9.5 V which may overshoot to +10.5 V for periods up to 20 ns.
3. No more than one output may be shorted to ground at a time. Duration of the short circuit should not be greater than one
second.
4. Stresses above those listed under “Absolute Maximum Ratings” may cause permanent damage to the device. This is a stress
rating only; functional operation of the device at these or any other conditions above those indicated in the operational
sections of this data sheet is not implied. Exposure of the device to absolute maximum rating conditions for extended periods
may affect device reliability.
20 ns
20 ns
20 ns
+0.9 V
–2.0 V
V
CC
+2.0 V
2.0 V
20 ns
20 ns
20 ns
Figure 7. Maximum Negative Overshoot
Waveform
Figure 8. Maximum Positive Overshoot
Waveform
Operating Ranges
Ambient Temperature (TA) . . . . . . . . . . . . . . . . . . . . . . . . . –25°C to +85°C
Ambient Temperature (TA) during Accelerated Sector Erase . . +20°C to +40°C
VCC Supply Voltages
VCC min . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .+1.70 V
VCC max . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .+1.95 V
Operating ranges define those limits between which the functionality of the device is guaranteed.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
81
A d v a n c e I n f o r m a t i o n
DC Characteristics
CMOS Compatible
Parameter Description
Test Conditions (Note 1)
VIN = VSS to VCC, VCC = VCC max
VOUT = VSS to VCC, VCC = VCC max
80 MHz
Min
Typ
Max
±1
±1
36
33
30
38
35
32
40
37
34
42
39
36
18
4
Unit
µA
ILI
Input Load Current
ILO
Output Leakage Current
µA
26
24
22
26
24
22
28
26
24
30
28
26
15
3
CE# = VIL, OE# = VIL
burst length = 8
,
66 MHz
54 MHz
80 MHZ
66 MHz
54 MHz
80 MHZ
66 MHz
54 MHz
80 MHZ
66 MHz
54 MHz
5 MHz
mA
mA
mA
mA
CE# = VIL, OE# = VIL
burst length = 16
,
VCC Active Burst Read Current
(Note 5)
ICCB
CE# = VIL, OE# = VIL
,
burst length = 32
CE# = VIL, OE# = VIL
burst length =
continuous
,
mA
mA
mA
VCC Active Asynchronous Read
Current (Note 2)
ICC1
CE# = VIL, OE# = VIH
1 MHz
ICC2
ICC3
ICC4
VCC Active Write Current (Note 3) CE# = VIL, OE# = VIH, ACC = VIH
19
52.5
CE# = VIH, RESET# = VIH
VCC Standby Current (Note 4)
(Note 8)
20
80
40
µA
µA
VCC Reset Current
RESET# = VIL, CLK = VIL (Note 8)
150
CE# = VIL, OE# = VIL (Note 8)
(Note 9)
VCC Active Current
(Read While Write)
ICC5
50
60
mA
ICC6
IPPW
VCC Sleep Current
CE# = VIL, OE# = VIH
ACC = 9 V
20
20
40
30
µA
Accelerated Program Current
(Note 6)
mA
Accelerated Erase Current
(Note 6)
IPPE
ACC = 9 V
20
30
mA
VIL
VIH
Input Low Voltage
–0.5
0.4
VIO + 0.2
0.1
V
V
V
V
V
V
V
V
– 0.4
Input High Voltage
IO
VOL
VOH
VID
Output Low Voltage
IOL = 100 µA, VCC = VCC min
IOH = –100 µA, VCC = VCC min
– 0.1
Output High Voltage
IO
Voltage for Accelerated Program
Low VCC Lock-out Voltage
8.5
1.0
9.5
1.4
VLKO
82
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Note:
1. Maximum ICC specifications are tested with VCC = VCCmax.
2. The ICC current listed is typically less than 2 mA/MHz, with OE# at VIH
.
3. ICC active while Embedded Erase or Embedded Program is in progress.
4. Device enters automatic sleep mode when addresses are stable for tACC + 20 ns. Typical sleep mode current
is equal to ICC3
.
5. Specifications assume 8 I/Os switching.
6. Not 100% tested. ACC is not a power supply pin.
7. While measuring Output Leakage Current, CE# should be at VIH
8. VIH = VCC ± -0.2 V and VIL > -0.1V.
.
9. Clock Frequency 66 MHz and in Continuous Mode.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
83
A d v a n c e I n f o r m a t i o n
Test Conditions
Device
Under
Test
C
L
Figure 9. Te st S e tup
Table 30. Test Specifications
Test Condition
All Speeds
Unit
Output Load Capacitance, CL
(including jig capacitance)
30
pF
Input Rise and Fall Times
Input Pulse Levels
2.5 @ 80 MHz, 3 @ 54, 66 MHz
0.0–VCC
ns
V
Input timing measurement
reference levels
VIO/2
VIO/2
V
V
Output timing measurement
reference levels
Key to Switching Waveforms
WAVEFORM
INPUTS
OUTPUTS
Steady
Changing from H to L
Changing from L to H
Don’t Care, Any Change Permitted
Does Not Apply
Changing, State Unknown
Center Line is High Impedance State (High Z)
Switching Waveforms
VIO
VIO/2
VIO/2
In
Measurement Level
Output
0.0 V
Figure 10. Input Waveforms and Measurement Levels
84
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
AC Characteristics
V
Power-up
CC
Parameter
Description
Test Setup
Speed
Unit
tVCS
VCC Setup Time
Min
1
ms
Notes:
1. VCC >+ VCCQ - 100mV and VCC ramp rate is >1V/100µs
2. VCC ramp rate <1V/100µs, Hardware Reset will be required
tVCS
VCC
VCCQ
RESET#
Figure 11.
V
Power-up Diagram CLK Characterization
CC
Parameter
fCLK
Description
CLK Frequency
CLK Period
(80 MHz) (66 MHz) (54 MHz)
Unit
MHz
ns
Max
Min
80
66
54
tCLK
12.5
15.0
18.5
tCH
CLK High Time
CLK Low Time
CLK Rise Time
CLK Fall Time
Min
5
6.1
3
7.4
3
ns
ns
tCL
tCR (Note)
tCF (Note)
Max
2.5
Notes:
1. Not 100% tested.
t
CLK
t
t
CL
CH
CLK
t
t
CF
CR
Figure 12. CLK Characterization
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
85
A d v a n c e I n f o r m a t i o n
AC Characteristics
Synchronous/Burst Read
Parameter
JEDEC Standard Description
(80 MHz)
(66 MHz)
(54 MHz)
Unit
tIACC
tBACC
Initial Access Time
Max
Max
80
ns
Burst Access Time Valid Clock to
Output Delay
9
11.0
13.5
ns
tAVDS
tAVDH
tAVDO
tACS
AVD# Setup Time to CLK
Min
Min
Min
Min
Min
Min
Max
Max
Max
Min
Min
Max
4
6
4
6
5
7
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
AVD# Hold Time from CLK
AVD# High to OE# Low
0
Address Setup Time to CLK
Address Hold Time from CLK
Data Hold Time from Next Clock Cycle
Output Enable to Data, or RDY Valid
Chip Enable to High Z (Note)
Output Enable to High Z (Note)
CE# Setup Time to CLK
4
6
3
9
8
8
4
5
7
tACH
tBDH
tOE
6
3
4
11.0
10
10
4
13.5
10
10
tCEZ
tOEZ
tCES
tRDYS
tRACC
RDY Setup Time to CLK
3.5
9
4
5
Ready access time from CLK
11.0
13.5
Note: Not 100% tested.
86
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
5 cycles for initial access shown.
tCEZ
tCES
15.2 ns typ. (66 MHz)
12.5 ns typ. (80 MHz)
CE#
CLK
1
2
3
4
5
6
7
tAVDS
AVD#
tAVDH
tAVDO
tACS
Amax-A16
Aa
tBACC
tACH
Hi-Z
Aa
A/DQ15-
A/DQ0 (n)
tIACC
Da
Da + 1
Da + n
Da + 2
Da + 3
tOEZ
tBDH
OE#
tRACC
tOE
Hi-Z
Hi-Z
Hi-Z
Hi-Z
Hi-Z
RDY (n)
tCR
tRDYS
Hi-Z
Hi-Z
A/DQ15-
A/DQ0 (n + 1)
Da
Da
Da
Da + 1
Da + 1
Da
Da + 2
Da + 1
Da
Da + n
Da + n
Da + n
Da + 2
Da + 1
Da
RDY (n + 1)
Hi-Z
Hi-Z
A/DQ15-
A/DQ0 (n + 2)
RDY (n + 2)
Hi-Z
Hi-Z
A/DQ15-
A/DQ0 (n + 3)
RDY (n + 3)
Notes:
1. Figure shows total number of clock set to five. The 54 MHz is able to operate using 5 clocks.
2. If any burst address occurs at “address + 1”, “address + 2”, or “address +3”, additional clock delays are
inserted, and are indicated by RDY.
Figure 13. Burst Mode Read
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
87
A d v a n c e I n f o r m a t i o n
AC Characteristics
Asynchronous Read
Parameter
JEDEC
Standard
tCE
Description
(80 MHz) (66 MHz) (54 MHz)
Unit
ns
Access Time from CE# Low
Asynchronous Access Time
AVD# Low Time
Max
Max
Min
80
80
8
tACC
ns
tAVDP
ns
Address Setup Time to Rising Edge of
AVD
tAAVDS
Min
Min
4
4
6
5
ns
ns
Address Hold Time from Rising Edge of
AVD
tAAVDH
tOE
6
9
7
Output Enable to Output Valid
Max
Min
11.0
0
13.5
ns
ns
Read
Output Enable Hold
tOEH
Toggle and Data#
Polling
Time
Min
10
10
ns
ns
tOEZ
Output Enable to High Z (See Note)
Max
Note: Not 100% tested.
CE#
tOE
OE#
WE#
tOEH
tCE
tOEZ
A/DQ15–
A/DQ0
RA
tACC
Valid RD
RA
Amax–A16
AVD#
tAAVDH
tAVDP
tAAVDS
Note: RA = Read Address, RD = Read Data.
Figure 14. Asynchronous Mode Read
88
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
AC Characteristics
Hardware Reset (RESET#)
Parameter
JEDEC
Std
tRP
Description
All Speed Options
Unit
ns
RESET# Pulse Width
Reset High Time Before Read
Min
Min
200
10
tRH
µs
Note: Not 100% tested.
CE#, OE#
tRH
RESET#
tRP
Figure 15. Reset Timings
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
89
A d v a n c e I n f o r m a t i o n
AC Characteristics
Erase/Program Operations
Parameter
JEDEC
tAVAV
Standard Description
tWC Write Cycle Time (Note 1)
tAS
(80 MHz)
(66 MHz)
(54 MHz)
Unit
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
Min
Min
Min
Min
Min
Min
Typ
Typ
Typ
Typ
Typ
45
4
45
4
80
5
tAVWL
tWLAX
Address Setup Time
Address Hold Time
AVD# Low Time
tAH
6
6
7
tAVDP
tDS
8
tDVWH
tWHDX
tGHWL
tELWL
Data Setup Time
20
4
25
0
45
0
tDH
Data Hold Time
tGHWL
tCS
Read Recovery Time Before Write
CE# Setup Time
0
0
tWHEH
tWLWH
tWHWL
tCH
CE# Hold Time
0
tWP/tWRL
tWPH
Write Pulse Width
Write Pulse Width High
30
20
Latency Between Read and Write
Operations
tSR/W
tVPP
Min
Min
Min
0
500
1
ns
ns
µs
ACC Rise and Fall Time
ACC Setup Time (During
Accelerated Programming)
tVPS
tVCS
tSEA
tESL
tPSL
VCC Setup Time
Min
Max
Max
Max
50
50
35
35
µs
µs
µs
µs
Sector Erase Accept Time-out
Erase Suspend Latency
Program Suspend Latency
Toggle Time During Programming
Within a Protected Sector
tPSP
Typ
1
µs
Toggle Time During Sector
Protection
tASP
Typ
100
3
µs
ns
tWEP
Noise Pulse Margin on WE#
Max
Notes:
1. Not 100% tested.
2. See the “Erase and Programming Performance” section for more information.
3. Does not include the preprogramming time.
90
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
AC Characteristics
Program Command Sequence (last two cycles)
Read Status Data
tAS
AVD
tAH
tAVDP
Amax–A16
PA
PA
VA
VA
VA
In
A/DQ15
–
555h
Complete
A0h
PD
tDS
tDH
VA
Progress
A/DQ0
CE#
tCH
OE#
WE#
tWP
tWHWH1
tCS
tWPH
tWC
V
IH
CLK
VCC
V
IL
tVCS
Notes:
1. PA = Program Address, PD = Program Data, VA = Valid Address for reading status bits.
2. “In progress” and “complete” refer to status of program operation.
3. Amax–A16 are don’t care during command sequence unlock cycles.
Figure 16. Program Operation Timings
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
91
A d v a n c e I n f o r m a t i o n
AC Characteristics
Erase Command Sequence (last two cycles)
Read Status Data
tAS
AVD
tAH
tAVDP
SA
555h for
chip erase
VA
VA
VA
Amax–A16
10h for
chip erase
In
A/DQ15
–
2AAh
Complete
55h
SA
30h
VA
Progress
A/DQ0
tDS
tDH
CE#
tCH
OE#
WE#
tWP
tWHWH2
tCS
tWPH
tWC
V
IH
CLK
VCC
V
IL
tVCS
Notes:
1. SA is the sector address for Sector Erase.
2. Address bits Amax–A16 are don’t cares during unlock cycles in the command sequence.
Figure 17. Chip/Sector Erase Operations
92
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
AC Characteristics
CE#
AVD#
WE#
Amax
–A16
PA
PA
A/DQ15
–
Don't Care
A0h
PD
Don't Care
A/DQ0
CE#
tVPS
V
V
ID
ACC
tVPP
or V
IL
IH
Notes:
1. ACC can be left high for subsequent programming pulses.
2. Use setup and hold times from conventional program operation.
Figure 18. Accelerated Unlock Bypass Programming Timing
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
93
A d v a n c e I n f o r m a t i o n
AC Characteristics
AVD#
tCEZ
tCE
CE#
tOEZ
tCH
tOE
OE#
tOEH
WE#
tACC
VA
High Z
High Z
A
–A16
max
VA
A/DQ15
A/DQ0
–
Status Data
Status Data
VA
VA
Notes:
1. All status reads are asynchronous.
2. VA = Valid Address. Two read cycles are required to determine status. When the Embedded Algorithm operation is
complete, and Data# Polling will output true data.
Figure 19. Data# Polling Timings (During Embedded Algorithm)
AVD#
tCEZ
tCE
CE#
tOEZ
tCH
tOE
OE#
WE#
tOEH
tACC
High Z
High Z
A
–A16
max
VA
VA
VA
A/DQ15
–
Status Data
Status Data
VA
A/DQ0
Notes:
1. All status reads are asynchronous.
2. VA = Valid Address. Two read cycles are required to determine status. When the Embedded Algorithm operation is
complete, the toggle bits will stop toggling.
Figure 20. Toggle Bit Timings (During Embedded Algorithm)
94
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
AC Characteristics
Address wraps back to beginning of address group.
Initial Access
39
CLK
39
3A
3B
3C
3D
3E
3F
38
Address (hex)
A/DQ15
–
D0
D1
D2
D3
D4
D5
D6
D7
A/DQ0
AVD#
OE#
V
IH
V
IL
V
IH
(stays low)
(stays low)
V
IL
V
CE#
IL
Note: 8-word linear burst mode shown. 16- and 32-word linear burst read modes behave similarly.
D0 represents the first word of the linear burst.
Figure 21. 8-, 16-, and 32-Word Linear Burst Address Wrap Around
Address boundary occurs every 128 words, beginning at address
00007Fh: (0000FFh, 00017Fh, etc.) Address 000000h is also a boundary crossing.
C124
C125
7D
C126
7E
C127
7F
C127
7F
C128
80
C129
81
C130
82
C131
CLK
7C
83
Address (hex)
(stays high)
AVD#
RDY(1)
RDY(2)
tRACC
tRACC
latency
tRACC
tRACC
latency
Data
D124
D125
D126
D127
D128
D129
D130
OE#,
CE#
(stays low)
Notes:
1. Cxx indicates the clock that triggers data Dxx on the outputs; for example, C60 triggers D60.
2. At frequencies less than or equal to 66 Mhz, there is no latency.
Figure 22. Latency with Boundary Crossing
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
95
A d v a n c e I n f o r m a t i o n
AC Characteristics
Last Cycle in
Program or
Sector Erase
Read status (at least two cycles) in same bank
and/or array data from other bank
Begin another
write or program
command sequence
Command Sequence
tWC
tRC
tRC
tWC
CE#
OE#
tOE
tOEH
tGHWL
WE#
tWPH
tOEZ
tWP
tDS
tACC
tOEH
tDH
RA
A/DQ15
A/DQ0
–
RA
RA
PA/SA
PD/30h
RD
RD
555h
AAh
tSR/W
RA
Amax–A16
PA/SA
tAS
AVD#
tAH
Note:Breakpoints in waveforms indicate that system may alternately read array data from the “non-busy bank”
while checking the status of the program or erase operation in the “busy” bank. The system should read status
twice to ensure valid information.
Figure 23. Back-to-Back Read/Write Cycle Timings
96
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Erase and Programming Performance
Parameter
Typ (Note 1)
Max (Note 2)
Unit
Comments
64 Kword
16 Kword
VCC
VCC
0.8
3.5
2
Sector Erase Time
s
<0.15
154 (NS256N)
77 (NS128N)
39 (NS064N)
308 (NS256N)
154 (NS128N)
78 (NS064N)
Excludes 00h
programming prior to
erasure (Note 5)
VCC
Chip Erase Time
s
131 (NS256N)
66 (NS128N)
33 (NS064N)
262 (NS256N)
132 (NS128N)
66 (NS064N)
ACC
VCC
ACC
VCC
ACC
VCC
ACC
40
24
400
240
94
Single Word Programming Time
µs
µs
µs
9.4
6
Effective Word Programming Time
utilizing Program Write Buffer
60
300
192
3000
1920
Total 32-Word Buffer
Programming Time
157.3 (NS256N)
78.6 (NS128N)
39.3 (NS064N)
314.6 (NS256N)
157.3 (NS128N)
78.6 (NS064N)
VCC
Excludes system level
overhead (Note 6)
Chip Programming Time (Note 4)
s
100.7 (NS256N)
50.3 (NS128N)
25.2 (NS064N)
201.3 (NS256N)
100.7 (NS128N)
50.3 (NS064N)
ACC
Notes:
1. Typical program and erase times assume the following conditions: 25°C, 1.8 V VCC, 10,000 cycles typical. Additionally,
programming typicals assume checkerboard pattern.
2. Under worst case conditions of 90°C, VCC = 1.70 V, 100,000 cycles.
3. Effective write buffer specification is based upon a 32-word write buffer operation.
4. The typical chip programming time is considerably less than the maximum chip programming time listed, since most words
program faster than the maximum program times listed.
5. In the pre-programming step of the Embedded Erase algorithm, all words are programmed to 00h before erasure.
6. System-level overhead is the time required to execute the two- or four-bus-cycle sequence for the program command. See
Table 27 for further information on command definitions.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
97
A d v a n c e I n f o r m a t i o n
Device History
Device
Revision
Extended Code (Hex)
0x012Eh
Major Reason(s) for Change
ES1
ES2
Initial release.
Errata Fix
NS256N
0x012Dh
ES1
0x012Eh
Initial release, 66 MHz
Initial Release, 54 MHz
Initial release
NS128N
NS064N
ES1
0x011Eh
Initial
TBD
98
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
S29NSxxxN Revision Summary
The revision history for the flash documented in this MCP datasheet reflects the revision history
for the discrete flash datasheet, S29NS256/128/64N_00_A3a, April 5, 2005.
Revision A (April 16, 2004)
Initial Release.
Revision A1 (June 28, 2004)
General Description
Corrected the effective temperature range to -25°C to +85°C.
Connection Diagram
Corrected pin B5 on the S29NS256N to A23.
Corrected pin B1 on the S29NS256N to VCC
Corrected pin B1 on the S29NS128N to VCC
Corrected pin B1 on the S29NS064N to VCC
.
.
.
Created separate illustrations for S29NS128N and S29NS064N.
Ordering Information
Corrected the Package Type offerings.
Valid Combinations table
Included package type description for S29NS064N device.
Completely revised format and layout.
8-, 16-, and 32-Word Linear Burst without Wrap Around
Corrected information in this section.
Lock Register
Section and table were substantially revised.
Programmable Wait State
Corrected information in this section.
Handshaking Feature
Corrected information in this section.
Autoselect Command Sequence
Corrected information in this section.
Physical Dimensions
Corrected the drawing for the S29NS064N device.
Write Buffer Command Sequence
Corrected the address for the Write Buffer Load sequence.
Revision A2 (September 9, 2004)
Connection Diagrams
Updated pin labels.
Ordering Information
Completely updated the OPN table.
Valid Combinations table
Updated this table.
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
99
A d v a n c e I n f o r m a t i o n
Continuous Burst
Added information to this section.
Lock Register
Updated the lock register table.
Configuration Register
Updated the settings for CR15.
Device ID table
Updated the indicator bits information.
Figure 7
Updated the waveform.
Figure 21
Updated the waveform.
Revision A3 (November 16, 2004)
Table 17. ”Primary Vendor-Specific Extended Query”
Updated the data values for addresses 45h, 53h, and 54h.
Global
Updated the synchronous and asynchronous access times.
Programmable Wait State
Updated this section.
Write Buffer Programming Command Sequence
Added a note to the table.
Revision A3a (April 5, 2005)
Global
Updated reference links.
Distinctive Characteristics
Added note to ACC is represented as VPP in older documentation.
General Description
Added note regarding ACC and VPP.
Block Diagram
Added same note regarding ACC and VPP.
Added WP# term and arrow to State Control and Command Register block.
Block Diagram of Simultaneous Operation Circuit
Changed VPP to Vssq.
Added WP# term and arrow to State Control and Command Register block.
Added ACC term and arrow to State Control and Command Register block.
Added note to ACC is represented as VPP in older documentation.
Input/Output Description
Added VPP term adjacent to ACC term.
Tables 2, 3, 4, 5, 6, 7, 8, and 9
Change Wait State titles and columns in these tables.
100
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
A d v a n c e I n f o r m a t i o n
Table 24
Changed Function column and Settings to represent Reserved CR Bits.
Table 27
Removed several bold lines between columns.
DC Characteristics
Reduced Typ and Max values for ICCB
.
Added note for clock frequency in continuous mode.
Erase & Programming Performance Table
Corrected Sector Erase Time Typ. Value for 64 Kword from 0.6 to 0.8 in Erase and Programming
Performance table
Physical Dimensions (S29NS046N)
Replaced VDE044 with new package drawing.
Device History
Updated Device History table
April 6, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
101
1 M x 16 Bit Multiplexed Single
Transistor RAM
ADVANCE
INFORMATION
Features
Process Technology: 0.13 µm CMOS
Organization: 1M x16 bit
Power Supply Voltage: 1.7V – 1.9V
Multiplexed address and data bus
Three State Outputs
RMS and Auto TCSR for power saving
Block Diagram
AVD#
Self-Refresh
Control
CS#
UB#
LB#
WE#
OE#
Column Select
Control
Logic
Memory Array
1M X 16
Address
Decoder
A19–A16
Address/Data
Multiplexer
ADQ15–ADQ0
DIN/DOUT Buffer
I/O Circuit
Pad Description
Name
CS#
Function
Chip select inputs
Output enable input
Write enable input
Address valid input
Address/Data In-out
Address inputs
Name
LB#
Function
Lower byte (ADQ7–ADQ0
OE#
UB#
Upper byte (ADQ15–ADQ8)
Power supply
WE#
AVD#
V
CC
V
I/O Power supply
Ground
CCQ
ADQ
V
I
SS(Q)
NC
A
No connection
I
Publication Number S71NS128_064NA0_00 Revision A Amendment 0 Issue Date April 5, 2005
A d v a n c e I n f o r m a t i o n
Absolute Maximum Ratings
Parameter
Symbol
Minimum
Unit
Voltage on Any Pin Relative to V
V
, V
–0.2 to V
+0.3V
V
SS
IN
OUT
CCQ
-0.2 to 2.5V
(Note 2)
Voltage on Vcc supply relative to V
V
, V
CCQ
V
SS
CC
Power Dissipation
P
1.0
W
°C
°C
D
Storage Temperature
Operating Temperature
T
-65 to 150
-25 to 85
STG
T
A
Notes:
1. Stresses greater than those listed above Absolute Maximum Ratingss can cause permanent damage to the device.
Functional operation should be restricted to recommended operating condition. Exposure to absolute maximum rating
conditions for extended periods may affect reliability.
2. Undershoot at power-off : –1.0V in case of pulse width < 20ns
Functional Description
CS# OE# WE# LB# UB# AVD#
ADQ15 – ADQ0
High-Z
A19 – A16
Mode
Power
Stand by
Active
H
L
X
H
X
X
H
X
X
X
H
X
X
H
X
H
X
X
X
X
Deselected
High-Z
Output Disabled
Output Disabled
L
High-Z
Active
Configuration Register
Write Access
L
L
H
L
L
H
H
H
H
H
H
Data In
X
X
Active
Active
Configuration Register
Read Access
H
Data Out
L
L
L
L
L
L
L
H
L
H
H
H
H
L
H
L
H
H
L
L
Add. Input
Data Out
Data Out
Data Out
Data In
Add. Input
Address Input
Lower Byte Read
Upper Byte Read
Word Read
Active
Active
Active
Active
Active
Active
Active
H
H
H
H
H
H
X
X
X
X
X
X
L
H
L
L
L
H
H
H
L
H
L
Lower Byte Write
Upper Byte Write
Word Write
L
H
L
Data In
L
L
Data In
Note:
X means don’t care. (Must be low or high state).
DC Operating Conditions
Parameter
Symbol
Min
1.7
1.7
0
Typ
1.8
1.8
0
Max
1.9
1.9
0
Unit
V
V
CC
Supply voltage
V
V
CCQ
Ground
V
V
V
SS, SSQ
V
+ 0.2
CCQ
Input high voltage
V
V
– 0.4
-
-
V
V
IH
CCQ
(Note 2)
-0.2
(Note 3)
Input low voltage
V
IL
0.4
Notes:
1. T = -25 to 85°C, otherwise specified.
A
2. Overshoot: V +1.0 V in case of pulse width < 20ns
CC
3. Undershoot: –1.0 V in case of pulse width < 20ns
4
.
O
v
e
r
s
h
o
o
t
a
n
d
u
n
d
e
r
s
h
o
o
t
a
r
e
s
a
m
p
l
e
d
,
n
o
t
1
0
0
%
t
e
s
t
e
d
.
Capacitance
f =1MHz, TA=25°C
Item
Symbol
Test Condition
Min
Max
8
Unit
pF
Input Capacitance
C
C
V
V
=0 V
=0 V
-
-
IN
IO
IN
IO
Input/Output Capacitance
10
pF
Capacitance is sampled, not 100% tested
104
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 5, 2005
A d v a n c e I n f o r m a t i o n
DC and Operating Characteristics
Parameter
Symbol
Test Conditions
, V =V
Min
Typ
Max Unit
Input leakage current
I
V
=V to V
–1
1
µA
LI
IN
SS
CCQ
CC
CCmax
CS#=V or OE=V or WE=V
,
IH
IH
IL
, V =V
CCQ CC CCmax
Output leakage current
I
–1
1
µA
LO
V
=V to V
IO
SS
Cycle time=1µs, 100% duty, I =0 mA,
IO
I
I
3
mA
mA
CC1
CC2
CS#<0.2 V, V <0.2V or V >V -0.2 V
IN
IN
CCQ
Average operating current
Cycle time = Min, I =0mA, 100% duty,
IO
CS#=VIL, VIN=VIL or VIH
25
Output low voltage
Output high voltage
V
I
I
= 0.1 mA, V =V
CCmin
0.1
V
V
OL
OL
CC
V
= –0.1 mA, V =V
V
-0.1
OH
OH
CC
CCmin
CCQ
CS#>V
–0.2 V Other inputs = 0 – V
CCQ
CCQ
(Typical condition: V =1.8 V @ 25°C)
Standby Current (CMOS)
I
LL
60
µA
CC
SB1
(Maximum condition: V =1.9 V @ 85°C)
CC
Note: Maximum ICC specifications are tested with VCC = VCCmax
.
AC Operating Conditions
Test Conditions
(Test Load and Test Input/Output Reference)
Input Pulse Level : 0.2 V to VCCQ – 0.2V
Input Rise and Fall Time : 5 ns
DOU T
Input and Output reference Voltage : VCCQ/2
CL
Output Load (See right) : CL = 30pF
(Including scope and Jig capacitance)
April 5, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
105
A d v a n c e I n f o r m a t i o n
AC Characteristics
VCC = 1.7 V – 1.9 V, Gnd = 0 V, TA = -25°C to +85°C
Speed
Max
Parameter
Symbol
Unit
Min
15
15
5
AVD# Low pulse
t
1000
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
ns
AVD
Address setup to AVD# rising edge
Address hold from AVD# rising edge
Chip enable setup to AVD# rising edge
AVD# low to data valid time
Address access time
t
AVDS
AVDH
Common
t
t
7
CSS
t
t
t
70
70
70
ACC1
ACC2
ACC3
ADOE
Chip enable to data output
Address disable to output enable
Output enable to valid output
UB#, LB# enable to data output
UB#, LB# enable to low-Z output
Output enable to low-Z output
Chip disable to high-Z output
UB#, LB# disable to high-Z output
Output disable to high-Z output
AVD# low to end of write
t
0
t
25
25
OE
Read
t
UBLBA
t
5
5
BLZ
OLZ
t
t
15
15
15
HZ
t
BHZ
OHZ
t
t
70
70
70
45
50
25
0
ACW1
ACW2
ACW3
Address valid to end of write
Chip enable to end of write
Write pulse low
t
t
Write
t
WRL
UB#, LB# valid to end of write
Data to write time overlap
t
BW
DW
t
Data hold from write time
t
DH
Device Operation
The access is performed in two stages. The first stage is address latching. The first stage take
place between point A and B in timing diagram. At this stage, the Chip Select (CS#) to the device
is asserted. The random access is enabled either from the point the address becomes stable,
the falling edge of the AVD# signal or from the falling edge of the last chip select signal. The
second stage is the read or write access. This takes place between points B and C in timing di-
agram. In case of a read access, the multiplexed address/data bus (ADQ15 – ADQ0) changes
its direction. Note that tOE, when it is dominant, the device goes into the read cycle because the
address is available long before the device output is enabled.
Read Access
The read access is initiated by applying the address to the multiplexed address/data bus or to
the address bus over A15 (A16 -> Axx). When the address is stable, the device chip select (CS#)
is set active low. At point A, the AVD# signal is taken low and the latch becomes transparent.
This allows the address to be propagated to the memory array. The address is stable at the rising
edge of the AVD# signal. The AVD# signal goes high at point B in which the address latch is
completed. At this point the read cycle is entered. The OE# signal is set active low. This changes
the direction of the bus. The status of control signals UB# and LB# are set according to the
access. Data is read at point C.
106
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 5, 2005
A d v a n c e I n f o r m a t i o n
Read Access Timing Diagrams
C
A
B
tAVD
AVD#
tACC1
tAVDH
tAVDS
Address/Data
Address Valid
Data Valid
tACC2
tOHZ
tADOE
tOLZ
tOE
OE#
CS#
tCSS
tHZ
tACC3
tBLZ
tUBLBA
tBHZ
UB#, LB#
Figure 1. Read Cycle Timing Waveform (1) (WE# = V
)
IH
C
A
B
t
AVD
AVD#
t
t
AVDS
AVDH
Address/Data
Address Valid
Data Valid
t
ACC2
t
OHZ
t
OLZ
t
OE
OE#
CS#
t
CSS
t
HZ
t
t
BLZ
t
BHZ
UBLBA
UB#, LB#
Note: tHZ and tBHZ and tOHZ are defined as the time at which the outputs achieve the open circuit conditions and are not referenced
to output voltage levels.
Figure 2. Read Cycle Timing Waveform (2) (WE# = V
)
IH
Write Access
The write access is initiated by applying the address to the multiplexed address/data bus or to
the address bus over A15 (A16 -> Axx). When the address is stable, the device chip select (CS#)
is set active low. At point A, the AVD# signal is taken low and the latch becomes transparent.
This allows the address to be propagated to the memory array. The address is stable at the rising
edge of the AVD# signal. The AVD# signal goes high at point B in which the address latch is
completed. At this point, the second stage of the write process is entered. Data is input to the
multiplexed address/data bus. The WE# signal is set low and control signal UB# and LB# are set
according to the access.
April 5, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
107
A d v a n c e I n f o r m a t i o n
C
A
B
tAVD
AVD#
tACW1
tAVDS
tAVDH
Data Valid
Address/Data
Address Valid
tACW2
tDH
tDW
tWRL
WE#
CS#
tCSS
tACW3
tBW
UB#, LB#
Figure 3. Write Cycle Timing Waveform (1) (OE# = V
)
IH
C
A
B
tAVD
AVD#
tAVDS
tAVDH
Data Valid
Address/Data
Address Valid
tACW2
tDH
tDW
tWRL
WE#
CS#
tCSS
tBW
UB#, LB#
Note: Write Cycle. A write occurs during the overlap(tWRL) of low CS#, low WE# and low UB# or LB#. A write begins at the
last transition among low CS# and low WE# with asserting UB# or LB# low for single byte operation or simultaneously asserting
UB and LB low for word operation. A write ends at the earliest transition among high CS# and high WE#. The tWRL is measured
from the beginning and to the end of write.
Figure 4. Write Cycle Timing Waveform (2) (OE# = V
)
IH
108
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 5, 2005
A d v a n c e I n f o r m a t i o n
200us
V
(Min.)
CC
V
CC
CS#
Power Up Mode
Normal Operation
Note: Power Up. After VCC reaches VCC(Min.) , wait 200 µs with CS high, then normal operation begins.
Figure 5. Power Up Timing Waveform
RMS (Reduced Memory Size)
The 16M STRAM can be operated as a 2M, 4M, 8M or 16M device. The mode is set according to
configuration register access timings, and the array size is set by configuration register bit 2 and
3. While operating in the RMS mode, the unselected memory array may not be used.
TCSR (Temperature Cotrolled Self Refresh)
The 16M STRAM can be operated with temperature controlled self-refresh. The device internal
self-refresh period is controlled according as temperature change automatically.
Configuration Register Settings
Bit Number
15 – 8
Definition
Comments
Do not use in normal mode
Reserved for future use
7 – 4
Bit 3
Bit 2
Memory Size
Using Addresses
ADQ0–15 , A16–A19
ADQ0–15 , A16–A18
ADQ0–15 , A16–A17
ADQ0–15 , A16
0
0
Full Array
1/2 Array
3 – 2
Reduced Memory Size
0
1
1
0
1/4 Array
1
1
1/8 Array (Default)
Bit 1
0
Bit 0
0
Temperature Range
Auto TCSR
1 – 0
Temperature
Configuration Register Access Timing Waveforms
Data Valid
A/DQ15 – A/DQ0
tOLZ
tOE
OE#
tOHZ
tACC3
CS#
tHZ
High
UB#, LB#, WE#
Note: AVD# signal is fixed High
Figure 6. Configuration Register Access Timing Waveforms—Read Cycle
April 5, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
109
A d v a n c e I n f o r m a t i o n
A/DQ15 – A/DQ0
Data Valid
tDW
tDH
tWRL
WE#
tACC3
CS#
High
UB#, LB#, OE#
Note: AVD# signal is fixed High
Figure 7. Configuration Register Access Timing Waveforms—Write Cycle
110
S71NS128NA0/S71NS064NA0 Based MCPs
S71NS128_064NA0_00_A0 April 5, 2005
A d v a n c e I n f o r m a t i o n
STRAM Revision Summary
Revision A0 (April 6, 2005)
Initial release.
April 5, 2005 S71NS128_064NA0_00_A0
S71NS128NA0/S71NS064NA0 Based MCPs
111
A d v a n c e I n f o r m a t i o n
S71NS128NA0/S71NS064NA0 MCP Revision Summary
Revision A0 (April 6, 2005)
Initial release.
Colophon
The products described in this document are designed, developed and manufactured as contemplated for general use, including without limitation, ordinary
industrial use, general office use, personal use, and household use, but are not designed, developed and manufactured as contemplated (1) for any use that
includes fatal risks or dangers that, unless extremely high safety is secured, could have a serious effect to the public, and could lead directly to death, personal
injury, severe physical damage or other loss (i.e., nuclear reaction control in nuclear facility, aircraft flight control, air traffic control, mass transport control,
medical life support system, missile launch control in weapon system), or (2) for any use where chance of failure is intolerable (i.e., submersible repeater and
artificial satellite). Please note that Spansion will not be liable to you and/or any third party for any claims or damages arising in connection with above-men-
tioned uses of the products. Any semiconductor devices have an inherent chance of failure. You must protect against injury, damage or loss from such failures
by incorporating safety design measures into your facility and equipment such as redundancy, fire protection, and prevention of over-current levels and other
abnormal operating conditions. If any products described in this document represent goods or technologies subject to certain restrictions on export under
the Foreign Exchange and Foreign Trade Law of Japan, the US Export Administration Regulations or the applicable laws of any other country, the prior au-
thorization by the respective government entity will be required for export of those products.
Trademarks and Notice
The contents of this document are subject to change without notice. This document may contain information on a Spansion product under development by
Spansion. Spansion reserves the right to change or discontinue work on any product without notice. The information in this document is provided as is with-
out warranty or guarantee of any kind as to its accuracy, completeness, operability, fitness for particular purpose, merchantability, non-infringement of third-
party rights, or any other warranty, express, implied, or statutory. Spansion assumes no liability for any damages of any kind arising out of the use of the
information in this document.
Copyright © 2004 Spansion. All rights reserved. Spansion, the Spansion logo, MirrorBit, combinations thereof, and ExpressFlash are trademarks of Spansion.
Other company and product names used in this publication are for identification purposes only and may be trademarks of their respective companies.
112
S71NS128NA0/S71NS064NA0 based MCPs
S71NS128_064NA0_00_A0 April 6, 2005
相关型号:
S71NS064NA0BFWSZ2
Memory Circuit, 4MX16, CMOS, PBGA44, 9.20 X 8 MM, 1.20 MM HEIGHT, LEAD FREE, FBGA-44
SPANSION
S71NS064NA0BHWRA0
Memory Circuit, 4MX16, CMOS, PBGA56, 8 X 9.20 MM, 1.20 MM HEIGHT, LEAD AND HALOGEN FREE, VFBGA-56
SPANSION
S71NS064NA0BHWRA3
Memory Circuit, 4MX16, CMOS, PBGA56, 8 X 9.20 MM, 1.20 MM HEIGHT, LEAD AND HALOGEN FREE, VFBGA-56
SPANSION
S71NS064NA0BHWRN0
Memory Circuit, 4MX16, CMOS, PBGA56, 8 X 9.20 MM, 1.20 MM HEIGHT, LEAD AND HALOGEN FREE, VFBGA-56
SPANSION
S71NS064NA0BJWRA0
Memory Circuit, 4MX16, CMOS, PBGA56, 8 X 9.20 MM, 1.20 MM HEIGHT, LEAD FREE, VFBGA-56
SPANSION
S71NS064NA0BJWRN0
MirrorBit 1.8 Volt-only Simultaneous Read/Write, Burst-mode Multiplexed Flash Memory
SPANSION
S71NS064NA0BJWRN2
MirrorBit 1.8 Volt-only Simultaneous Read/Write, Burst-mode Multiplexed Flash Memory
SPANSION
S71NS064NA0BJWRN3
MirrorBit 1.8 Volt-only Simultaneous Read/Write, Burst-mode Multiplexed Flash Memory
SPANSION
S71NS064NA0BJWRT0
MirrorBit 1.8 Volt-only Simultaneous Read/Write, Burst-mode Multiplexed Flash Memory
SPANSION
S71NS064NA0BJWRT2
MirrorBit 1.8 Volt-only Simultaneous Read/Write, Burst-mode Multiplexed Flash Memory
SPANSION
S71NS064NA0BJWRT3
MirrorBit 1.8 Volt-only Simultaneous Read/Write, Burst-mode Multiplexed Flash Memory
SPANSION
S71NS064NA0BJWVN0
MirrorBit 1.8 Volt-only Simultaneous Read/Write, Burst-mode Multiplexed Flash Memory
SPANSION
©2020 ICPDF网 联系我们和版权申明