16mb Burst cr1 0 p23z PDF

Products and specifications discussed herein are subject to change by Micron without notice.
16Mb: 1 Meg x 16 Async/Page/Burst CellularRAM 1.0 Memory

Features
PDF: 09005aef81cb58ed/Source: 09005aef81c7a667 Micron Technology, Inc., reserves the right to change products or specifications without notice.
16mb_burst_cr1_0_p23z_1.fm - Rev. H 4/08 EN 1 2005 Micron Technology, Inc. All rights reserved.
Async/Page/Burst CellularRAM Memory
MT45W1MW16BDGB
Features
Single device supports asynchronous, page, and
burst operations
Random access time: 70ns
VCC, VCCQ voltages:
1.71.95V VCC
1.73.6V
1
VCCQ
Page mode read access
Sixteen-word page size
Interpage read access: 70ns
Intrapage read access: 20ns
Burst mode write access: continuous burst
Burst mode read access:
4, 8, or 16 words, or continuous burst
MAX clock rate: 104 MHz (
t
CLK = 9.62ns)
Burst initial latency: 39ns (4 clocks) @ 104 MHz
t
ACLK: 7ns @ 104 MHz
Low power consumption
Asynchronous read: <20mA
Intrapage read: <15mA
Intrapage read initial access, burst read:
(39ns [4 clocks] @ 104 MHz) < 35mA
Continuous burst read: <28mA
Standby: 70A
Deep power-down: <10A (TYP @ 25C)
Low-power features
Temperature-compensated refresh (TCR)
On-chip temperature sensor
Partial-array refresh (PAR)
Deep power-down (DPD) mode
Options Designator
Configuration
1 Meg x 16 MT45W1MW16BD
Package
54-ball VFBGA (green) GB
Access time
70ns access -70
Frequency
80 MHz 8
104 MHz 1
Figure 1: 54-Ball VFBGA
Notes: 1. 3.6V I/O and 30C exceed the CellularRAM
Workgroup 1.0 specifications.
2. Contact factory.
Part Number Example:
MT45W1MW16BDGB-701WT
Options (continued) Designator
Standby power
Standard None
Operating temperature range
Wireless (30C to +85C) WT
1
Industrial (40C to +85C) IT
2
A
B
C
D
E
F
G
H
J
1 2 3 4 5 6
Top View
(Ball Down)
LB#
DQ8
DQ9
VSSQ
VCCQ
DQ14
DQ15
A18
WAIT
OE#
UB#
DQ10
DQ11
DQ12
DQ13
A19
A8
CLK
A0
A3
A5
A17
NC
A14
A12
A9
ADV#
A2
CE#
DQ1
DQ3
DQ4
DQ5
WE#
A11
NC
CRE
DQ0
DQ2
VCC
VSS
DQ6
DQ7
NC
NC
A1
A4
A6
A7
A16
A15
A13
A10
NC
16mb_burst_cr1_0_p23zTOC.fm - Rev. H 4/08 EN 2 2005 Micron Technology, Inc. All rights reserved.
Table of Contents
Table of Contents
Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Functional Block Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Ball Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Bus Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Part Numbering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Valid Part Number Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Device Marking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Power-Up Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Bus Operating Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Asynchronous Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Page Mode READ Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Burst Mode Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Mixed-Mode Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
WAIT Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
LB#/UB# Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Low-Power Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Standby Mode Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Temperature-Compensated Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Partial-Array Refresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Deep Power-Down Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Configuration Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Access Using CRE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Software Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Bus Configuration Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Burst Length (BCR[2:0]) Default = Continuous Burst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Burst Wrap (BCR[3]) Default = Burst No Wrap (Within Burst Length) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Output Impedance (BCR[5]) Default = Outputs Use Full Drive Strength . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
WAIT Configuration (BCR[8]) Default = WAIT Transitions One Clock Before Data Valid/Invalid . . . . . . . . .25
WAIT Polarity (BCR[10]) Default = WAIT Active HIGH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Latency Counter (BCR[13:11]) Default = Three-Clock Latency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Operating Mode (BCR[15]) Default = Asynchronous Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Refresh Configuration Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Partial-Array Refresh (RCR[2:0]) Default = Full Array Refresh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Deep Power-Down (RCR[4]) Default = DPDDisabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Temperature-Compensated Refresh (RCR[6:5]) Default = On-Chip Temperature Sensor. . . . . . . . . . . . . . . .28
Page Mode Operation (RCR[7]) Default = Disabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Maximum and Typical Standby Currents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Timing Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Timing Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Package Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
Revision History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58
16mb_burst_cr1_0_p23zLOF.fm - Rev. H 4/08 EN 3 2005 Micron Technology, Inc. All rights reserved.
List of Figures
List of Figures
Figure 1: 54-Ball VFBGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1
Figure 2: Functional Block Diagram 1 Meg x 16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Figure 3: Part Number Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Figure 4: Power-Up Initialization Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Figure 5: READ Operation (ADV = LOW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Figure 6: WRITE Operation (ADV = LOW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Figure 7: Page Mode READ Operation (ADV = LOW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Figure 8: Burst Mode READ (4-word Burst) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Figure 9: Burst Mode WRITE (4-word Burst) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Figure 10: Wired-OR WAIT Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Figure 11: Refresh Collision During READ Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16
Figure 12: Refresh Collision During WRITE Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17
Figure 13: Configuration Register WRITE in Asynchronous Mode Followed by READ ARRAY Operation . . . .19
Figure 14: Configuration Register WRITE in Synchronous Mode Followed by READ ARRAY Operation . . . . .20
Figure 15: Load Configuration Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Figure 16: Read Configuration Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Figure 17: Bus Configuration Register Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Figure 18: WAIT Configuration (BCR[8] = 0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Figure 19: WAIT Configuration (BCR[8] = 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Figure 20: WAIT Configuration During Burst Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Figure 21: Latency Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Figure 22: Refresh Configuration Register Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Figure 23: Typical Refresh Current vs. Temperature (ITCR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Figure 24: AC Input/Output Reference Waveform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Figure 25: Output Load Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Figure 26: Initialization Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Figure 27: Asynchronous READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Figure 28: Asynchronous READ Using ADV# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Figure 29: Page Mode READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Figure 30: Single-Access Burst READ Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
Figure 31: 4-Word Burst READ Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Figure 32: READ Burst Suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Figure 33: Continuous Burst READ Showing an Output Delay with BCR[8] = 0 for End-of-Row Condition . .43
Figure 34: CE#-Controlled Asynchronous WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Figure 35: LB#/UB#-Controlled Asynchronous WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Figure 36: WE#-Controlled Asynchronous WRITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Figure 37: Asynchronous WRITE Using ADV# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Figure 38: Burst WRITE Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Figure 39: Continuous Burst WRITE Showing an Output Delay with BCR[8] = 0 for End-of-Row Condition .49
Figure 40: Burst WRITE Followed by Burst READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
Figure 41: Asynchronous WRITE Followed by Burst READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Figure 42: Asynchronous WRITE Followed by Burst READ ADV# LOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Figure 43: Burst READ Followed by Asynchronous WRITE (WE#-Controlled) . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Figure 44: Burst READ Followed by Asynchronous WRITE Using ADV# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Figure 45: Asynchronous WRITE Followed by Asynchronous READ ADV# LOW . . . . . . . . . . . . . . . . . . . . . . . .55
Figure 46: Asynchronous WRITE Followed by Asynchronous READ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Figure 47: 54-Ball VFBGA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57
16mb_burst_cr1_0_p23zLOT.fm - Rev. H 4/08 EN 4 2005 Micron Technology, Inc. All rights reserved.
List of Tables
List of Tables
Table 1: VFBGA Ball Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Table 2: Bus Operations Asynchronous Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Table 3: Bus Operations Burst Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8
Table 4: Sequence and Burst Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24
Table 5: Latency Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Table 6: 16Mb Address Patterns for PAR (RCR[4] = 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Table 7: Absolute Maximum Ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Table 8: Electrical Characteristics and Operating Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
Table 9: Maximum Standby Currents for Applying PAR and TCR Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Table 10: Deep Power-Down Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Table 11: Capacitance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32
Table 12: Asynchronous READ Cycle Timing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Table 13: Burst READ Cycle Timing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Table 14: Asynchronous WRITE Cycle Timing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Table 15: Burst WRITE Cycle Timing Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Table 16: Initialization Timing Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
General Description
General Description
Micron
CellularRAM is a high-speed, CMOS PSRAM memory device developed for

low-power, portable applications. The MT45W1MW16BDGB is a 16Mb DRAM core
device organized as 1 Meg x 16 bits. This device includes an industry-standard
burst mode Flash interface that dramatically increases read/write bandwidth compared
with other low-power SRAM or Pseudo SRAM offerings.
For seamless operation on a burst Flash bus, CellularRAM products incorporate a trans-
parent self-refresh mechanism. The hidden refresh requires no additional support from
the system memory controller and has no significant impact on device read/write
performance.
Two user-accessible control registers define device operation. The bus configuration
register (BCR) defines how the CellularRAM device interacts with the system memory
bus and is nearly identical to its counterpart on burst mode Flash devices. The refresh
configuration register (RCR) is used to control how refresh is performed on the DRAM
array. These registers are automatically loaded with default settings during power-up
and can be updated anytime during normal operation.
Special attention has been focused on standby current consumption during self refresh.
CellularRAM products include three system-accessible mechanisms to minimize
standby current. Partial-array refresh (PAR) limits refresh to only that part of the DRAM
array that contains essential data. Temperature-compensated refresh (TCR) uses an on-
chip sensor to adjust the refresh rate to match the device temperature. The refresh rate
decreases at lower temperatures to minimize current consumption during standby. TCR
can also be set by the system for maximum device temperatures of +85C, +45C, and
+15C. Deep power-down (DPD) halts the REFRESH operation altogether and is used
when no vital information is stored in the device. These three refresh mechanisms are
accessed through the RCR.
Functional Block Diagrams
Functional Block Diagrams
Figure 2: Functional Block Diagram 1 Meg x 16

Note: Functional block diagrams illustrate simplified device operation. See truth table, ball
descriptions, and timing diagrams for detailed information.
A[19:0]
Input/
Output
MUX
and
Buffers
Control
Logic
1,024K x 16
DRAM
MEMORY
ARRAY
CE#
WE#
OE#
CLK
ADV#
CRE
WAIT
LB#
UB#
DQ[7:0]
DQ[15:8]
Refresh Configuration
Register (RCR)
Bus Configuration
Register (BCR)
Address Decode
Logic
Ball Descriptions
Ball Descriptions
Note: The CLK and ADV# inputs can be tied to VSS if the device is always operating in asynchro-
nous or page mode. WAIT will be asserted but should be ignored during asynchronous and
page mode operations.
Table 1: VFBGA Ball Descriptions
VFBGA
Assignment Symbol Type Description
G2, H1, D3, E4,
F4, F3, G4, G3,
H5, H4, H3, H2,
D4, C4, C3, B4,
B3, A5, A4, A3
A[19:0] Input Address inputs: Inputs for addresses during READ and WRITE operations.
Addresses are internally latched during READ and WRITE cycles. The address lines
are also used to define the value to be loaded into the bus configuration register
or the refresh configuration register.
J2 CLK Input Clock: Synchronizes the memory to the system operating frequency during
synchronous operations. When configured for synchronous operation, the address
is latched on the first rising CLK edge when ADV# is active. CLK is static LOW or
HIGH during asynchronous access READ and WRITE operations and during PAGE
READ ACCESS operations.
J3 ADV# Input Address valid: Indicates that a valid address is present on the address inputs.
Addresses can be latched on the rising edge of ADV# during asynchronous READ
and WRITE operations. ADV# can be held LOW during asynchronous READ and
WRITE operations.
A6 CRE Input Configuration register enable: When CRE is HIGH, WRITE operations load the
refresh configuration register or bus configuration register.
B5 CE# Input Chip enable: Activates the device when LOW. When CE# is HIGH, the device is
disabled and goes into standby or deep power-down mode.
A2 OE# Input Output enable: Enables the output buffers when LOW. When OE# is HIGH, the
output buffers are disabled.
G5 WE# Input Write enable: Determines if a given cycle is a WRITE cycle. If WE# is LOW, the cycle
is a WRITE to either a configuration register or to the memory array.
A1 LB# Input Lower byte enable: DQ[7:0].
B2 UB# Input Upper byte enable: DQ[15:8].
G1, F1, F2, E2,
D2, C2, C1, B1,
G6, F6, F5, E5,
D5, C6, C5, B6
DQ[15:0] Input/
Output
Data inputs/outputs.
J1 WAIT Output Wait: Provides data-valid feedback during burst READ and WRITE operations. The
signal is gated by CE#. WAIT is used to arbitrate collisions between REFRESH and
READ/WRITE operations. WAIT is asserted when a burst crosses a row boundary.
WAIT is also used to mask the delay associated with opening a new internal page.
WAIT is asserted and should be ignored during asynchronous and page mode
operations. WAIT is High-Z when CE# is HIGH.
E3, H6, J4, J5, J6 NC Not internally connected.
D6 VCC Supply Device power supply (1.71.95V): Power supply for device core operation.
E1 VCCQ Supply I/O power supply (1.73.6V): Power supply for input/output buffers.
E6 VSS Supply VSS must be connected to ground.
D1 VSSQ Supply VSSQ must be connected to ground.
Bus Operations
Bus Operations
Notes: 1. CLK must be LOW during async read and async write modes, and to achieve standby power
during standby and DPD modes. CLK must be static (HIGH or LOW) during burst suspend.
2. The WAIT polarity is configured through the bus configuration register (BCR[10]).
3. When LB# and UB# are in select mode (LOW), DQ[15:0] are affected. When only LB# is in
select mode, DQ[7:0] are affected. When only UB# is in the select mode, DQ[15:8] are
affected.
4. The device will consume active power in this mode whenever addresses are changed.
5. When the device is in standby mode, address inputs and data inputs/outputs are internally
isolated from any external influence.
6. VIN

= VCCQ or 0V; all device balls must be static (unswitched) in order to achieve standby cur-
rent.
7. DPD is maintained until RCR is reconfigured.
8. Burst mode operation is initialized through the bus configuration register (BCR[15]).
Table 2: Bus Operations Asynchronous Mode
Mode Power CLK
1
ADV# CE# OE# WE# CRE
LB#/
UB# WAIT
2
DQ[15:0]
3
Notes
Read Active L L L L H L L Low-Z Data-Out 4
Write Active L L L X L L L Low-Z Data-In 4
Standby Standby L X H X X L X High-Z High-Z 5, 6
No operation Idle L X L X X L X Low-Z X 4, 6
Configuration
Register
Active L L L H L H X Low-Z High-Z
DPD Deep
power-down
L X H X X X X High-Z High-Z 7
Table 3: Bus Operations Burst Mode
Mode Power CLK
1
ADV# CE# OE# WE# CRE
LB#/
UB# WAIT
2
DQ[15:0]
3
Notes
Async read Active L L L L H L L Low-Z Data-Out 4
Async write Active L L L X L L L Low-Z Data-In 4
Standby Standby L X H X X L X High-Z High-Z 5, 6
No operation Idle L X L X X L X Low-Z X 4, 6
Initial burst
read
Active L L X H L L Low-Z X 4, 8
Initial burst
write
Active L L H L L X Low-Z X 4, 8
Burst
continue
Active H L X X X L Low-Z Data-In or
Data-Out
4, 8
Burst suspend Active X X L H X L X Low-Z High-Z 4, 8
Configuration
register
Active L L H L H X Low-Z High-Z 8
DPD Deep
power-down
L X H X X X X High-Z High-Z 7
Part Numbering Information
Part Numbering Information
Micron CellularRAM devices are available in several different configurations and densi-
ties (see Figure 3).
Figure 3: Part Number Chart
Notes: 1. 3.6V I/O and 30C exceed the CellularRAM Workgroup 1.0 specifications.
Valid Part Number Combinations
After building the part number from the part numbering chart above, visit to the Micron
Part Marking Decoder Web site at www.micron.com/partsearch to verify that the part
number is offered and valid. If the device required is not on this list, contact the factory.
Device Marking
Due to the size of the package, the Micron standard part number is not printed on the
top of the device. Instead, an abbreviated device mark comprised of a five-digit alphanu-
meric code is used. The abbreviated device marks are cross-referenced to the Micron
part numbers at www.micron.com/partsearch. To view the location of the abbreviated
mark on the device, refer to customer service note, CSN-11, Product Mark/Label at
www.micron.com/csn.
MT 45 W 1M W 16 BD GB -70 8 WT ES
Micron Technology
Product Family
45 = PSRAM/CellularRAM Memory
Operating Core Voltage
W = 1.71.95V
Address Locations
M = Megabits
Operating Voltage
W = 1.73.6V (see Note 1)
Bus Configuration
16 = x16
READ/WRITE Operation Mode
BD = Asynchronous/Page/Burst
Package Codes
GB = VFBGA green (6 x 9 grid, 0.75mm pitch, 6.0mm x 8.0mm x 1.0mm) 54-ball

Production Status
Blank = Production
ES = Engineering Sample
MS = Mechanical Sample
Operating Temperature
WT = 30C to +85C (see Note 1)
IT = 40C to +85C (contact factory)
Standby Power Options
Blank = Standard
Frequency
8 = 80 MHz
1 = 104 MHz
Access/Cycle Time
70 = 70ns
Functional Description
Functional Description
In general, the MT45W1MW16BDGB devices are high-density alternatives to SRAM and
Pseudo SRAM products, popular in low-power, portable applications.
The MT45W1MW16BDGB contains a 16,777,216-bit DRAM core organized as 1,048,576
addresses by 16 bits. This device implements the same high-speed bus interface found
on burst mode Flash products.
The CellularRAM bus interface supports both asynchronous and burst mode transfers.
Page mode accesses are also included as a bandwidth-enhancing extension to the asyn-
chronous read protocol.
Power-Up Initialization
CellularRAM products include an on-chip voltage sensor used to launch the power-up
initialization process. Initialization will configure the BCR and the RCR with their default
settings (see Figure 17 on page 23 and Figure 22 on page 27). VCC and VCCQ must be
applied simultaneously. When they reach a stable level at or above 1.7V, the device will
require 150s to complete its self-initialization process. During the initialization period,
CE# should remain HIGH. When initialization is complete, the device is ready for
normal operation.
Figure 4: Power-Up Initialization Timing

Bus Operating Modes
The MT45W1MW16BDGB CellularRAM products incorporate a burst mode interface
found on Flash products targeting low-power, wireless applications. This bus interface
supports asynchronous, page mode, and burst mode read and write transfers. The
specific interface supported is defined by the value loaded into the bus configuration
register. Page mode is controlled by the refresh configuration register (RCR[7]).
Asynchronous Mode
CellularRAM products power up in the asynchronous operating mode. This mode uses
the industry-standard SRAM control bus (CE#, OE#, WE#, LB#/UB#). READ operations
(Figure 5) are initiated by bringing CE#, OE#, and LB#/UB# LOW while keeping WE#
HIGH. Valid data will be driven out of the I/Os after the specified access time has
elapsed. WRITE operations (Figure 6 on page 11) occur when CE#, WE#, and LB#/UB#
are driven LOW. During asynchronous WRITE operations, the OE# level is a Don't
Care, and WE# will override OE#. The data to be written is latched on the rising edge of
CE#, WE#, or LB#/UB# (whichever occurs first). Asynchronous operations (page mode
disabled) can either use the ADV input to latch the address, or ADV can be driven LOW
during the entire READ/WRITE operation.
During asynchronous operation, the CLK input must be held static LOW or HIGH. WAIT
will be driven while the device is enabled and its state should be ignored. WE# LOW time
must be limited to
t
CEM.
Vcc
VccQ
Device Initialization
Vcc = 1.7V
Device ready for
normal operation
t
PU
>
150s
Bus Operating Modes
Figure 5: READ Operation (ADV = LOW)
Note: ADV must remain LOW for page mode operation.
Figure 6: WRITE Operation (ADV = LOW)

Page Mode READ Operation
Page mode is a performance-enhancing extension to the legacy asynchronous READ
operation. In page-mode-capable products, an initial asynchronous read access is
performed, then adjacent addresses can be read quickly by simply changing the low-
order address. Addresses A[3:0] are used to determine the members of the 16-address
CellularRAM page. Any change in addresses A[4] or higher will initiate a new
t
AA access
time. Figure 7 shows the timing for a page mode access. Page mode takes advantage of
the fact that adjacent addresses can be read in a shorter period of time than random
addresses. WRITE operations do not include comparable page mode functionality.
During asynchronous page mode operation, the CLK input must be held static LOW or
HIGH. CE# must be driven HIGH upon completion of a page mode access. WAIT will be
driven while the device is enabled and its state should be ignored. Page mode is enabled
by setting RCR[7] to HIGH. ADV must be driven LOW during all page mode read
accesses.
ADDRESS VALID
DATA
CE#
DATA VALID
OE#
WE#
LB#/UB#
t
RC = READ Cycle Time
ADDRESS
ADDRESS VALID
DATA
CE#
DONT CARE
DATA VALID
OE#
WE#
LB#/UB#
t
WC = WRITE Cycle Time
ADDRESS
<
t
CEM
Bus Operating Modes
The CE# LOW time is limited by refresh considerations. CE# must not stay LOW longer
than
t
CEM.
Figure 7: Page Mode READ Operation (ADV = LOW)
Burst Mode Operation
Burst mode operations enable high-speed synchronous READ and WRITE operations.
Burst operations consist of a multi-clock sequence that must be performed in an
ordered fashion. After CE# goes LOW, the address to access is latched on the next rising
edge of CLK that ADV# is LOW. During this first clock rising edge, WE# indicates whether
the operation is going to be a READ (WE# = HIGH, Figure 8 on page 13) or WRITE (WE#
= LOW, Figure 9 on page 14).
The size of a burst can be specified in the BCR as either fixed-length or continuous.
Fixed-length bursts consist of four, eight, or sixteen words. Continuous bursts have the
ability to start at a specified address and burst through the entire memory. The latency
count stored in the BCR defines the number of clock cycles that elapse before the initial
data value is transferred between the processor and CellularRAM device.
The WAIT output will be asserted as soon as CE# goes LOW and will be de-asserted to
indicate when data is to be transferred into (or out of ) the memory. WAIT will again be
asserted if the burst crosses the boundary between 128-word rows. Once the Cellu-
larRAM device has restored the previous rows data and accessed the next row, WAIT will
be de-asserted and the burst can continue (see Figure 33 on page 43).
The processor can access other devices without incurring the timing penalty of the
initial latency for a new burst by suspending burst mode. Bursts are suspended by stop-
ping CLK. CLK can be stopped HIGH or LOW. If another device will use the data bus
while the burst is suspended, OE# should be taken HIGH to disable the CellularRAM
outputs; otherwise, OE# can remain LOW. Note that the WAIT output will continue to be
active, and as a result no other devices should directly share the WAIT connection to the
controller. To continue the burst sequence, OE# is taken LOW, then CLK is restarted after
valid data is available on the bus.
DATA
CE#
DONT CARE
OE#
WE#
LB#/UB#
ADDRESS ADDRESS[0]
ADDRESS
[1]
ADDRESS
[2]
ADDRESS
[3]
D[1] D[2] D[3]
t
AA
t
APA
<
t
CEM
t
APA
t
APA
D[0]
Bus Operating Modes
The CE# LOW time is limited by refresh considerations. CE# must not stay LOW longer
than
t
CEM unless row boundaries are crossed at least every
t
CEM. If a burst suspension
will cause CE# to remain LOW for longer than
t
CEM, CE# should be taken HIGH and the
burst restarted with a new CE# LOW/ADV# LOW cycle.
Figure 8: Burst Mode READ (4-word Burst)
Note: Non-default BCR settings: Latency code two (three clocks); WAIT active LOW; WAIT
asserted during delay.
A[19:0]
D[0]
ADV#
CE#
OE#
D[1] D[2] D[3]
WE#
WAIT
DQ[15:0]
LB#/UB#
Latency Code 2 (3 clocks)
CLK
UNDEFINED DONT CARE
READ Burst Identified
(WE# = HIGH)
ADDRESS
VALID
Bus Operating Modes
Figure 9: Burst Mode WRITE (4-word Burst)
A[19:0]
D[0]
ADV#
CE#
OE#
D[1] D[2] D[3]
WE#
WAIT
DQ[15:0]
LB#/UB#
ADDRESS
VALID
Latency Code 2 (3 clocks)
CLK
DONT CARE
WRITE Burst Identified
(WE# = LOW)
Bus Operating Modes
Mixed-Mode Operation
The device can support a combination of synchronous READ and asynchronous WRITE
operations when the BCR is configured for synchronous operation. The asynchronous
WRITE operation requires that the clock (CLK) be held static LOW or HIGH during the
entire sequence. The ADV# signal can be used to latch the target address, or it can
remain LOW during the entire WRITE operation. CE# must return HIGH when transi-
tioning between mixed-mode operations. Note that the
t
CKA period is the same as a
READ or WRITE cycle. This time is required to ensure adequate refresh. Mixed-mode
operation facilitates a seamless interface to legacy burst mode Flash memory control-
lers. See Figure 41 on page 51.
WAIT Operation
The WAIT output on a CellularRAM device is typically connected to a shared, system-
level WAIT signal (see Figure 10). The shared WAIT signal is used by the processor to
coordinate transactions with multiple memories on the synchronous bus.
Figure 10: Wired-OR WAIT Configuration

Once a READ or WRITE operation has been initiated, WAIT goes active to indicate that
the CellularRAM device requires additional time before data can be transferred. For
READ operations, WAIT will remain active until valid data is output from the device. For
WRITE operations, WAIT will indicate to the memory controller when data will be
accepted into the CellularRAM device. When WAIT transitions to an inactive state, the
data burst will progress on successive clock edges.
During a Burst cycle, CE# must remain asserted until the first data is valid. Bringing CE#
HIGH during this initial latency may cause data corruption.
The WAIT output also performs an arbitration role when a READ or WRITE operation is
launched while an on-chip refresh is in progress. If a collision occurs, WAIT is asserted
for additional clock cycles until the refresh has completed (see Figures 11 and 12 on
page 17). When the refresh operation has completed, the READ or WRITE operation will
continue normally.
WAIT is also asserted when a continuous READ or WRITE burst crosses a row boundary.
The WAIT assertion allows time for the new row to be accessed and permits any pending
refresh operations to be performed.
LB#/UB# Operation
The LB# enable and UB# enable signals support byte-wide data transfers. During READ
operations, the enabled byte(s) are driven onto the DQ. The DQ associated with a
disabled byte are put into a High-Z state during a READ operation. During WRITE opera-
CellularRAM
External
Pull-Up/
Pull-Down
Resistor
Processor
READY
Other
Device
WAIT
Other
Device
WAIT
WAIT
Bus Operating Modes
tions, any disabled bytes will not be transferred to the RAM array and the internal value
will remain unchanged. During an asynchronous WRITE cycle, the data to be written is
latched on the rising edge of CE#, WE#, LB#, or UB#, whichever occurs first.
When both the LB# and UB# are disabled (HIGH) during an operation, the device will
disable the data bus from receiving or transmitting data. Although the device will seem
to be deselected, it remains in an active mode as long as CE# remains LOW.
Figure 11: Refresh Collision During READ Operation
A[19:0]
ADV#
CE#
OE#
WE#
WAIT
DQ[15:0]
CLK
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
VOH
VOL
D[2] D[1] D[3]
VALID
ADDRESS
Additional WAIT states inserted to allow refresh completion.
LB#/UB#
UNDEFINED DONT CARE
D[0]
High-Z
Bus Operating Modes
Figure 12: Refresh Collision During WRITE Operation
A[19:0]
ADV#
CE#
OE#
WE#
WAIT
DQ[15:0]
CLK
D[1] D[0] D[3] D[2]
VALID
ADDRESS
Additional WAIT states inserted to allow refresh completion.
LB#/UB#
DONT CARE
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
VOH
VOL
High-Z
Low-Power Operation
Low-Power Operation
Standby Mode Operation
During standby, the device current consumption is reduced to the level necessary to
perform the DRAM refresh operation. Standby operation occurs when CE# is HIGH.
The device will enter a reduced power state upon completion of a READ or WRITE oper-
ation or when the address and control inputs remain static for an extended period of
time. This mode will continue until a change occurs to the address or control inputs.
Temperature-Compensated Refresh
Temperature-compensated refresh (TCR) allows for adequate refresh at different
temperatures. This CellularRAM device includes an on-chip temperature sensor. When
the sensor is enabled, it continually adjusts the refresh rate according to the operating
temperature. The on-chip sensor is enabled by default.
Three fixed refresh rates are also available, corresponding to temperature thresholds of
+15C, +45C, and +85C. The setting selected must be for a temperature higher than the
case temperature of the CellularRAM device. If the case temperature is +35C, the system
can minimize self refresh current consumption by selecting the +45C setting. The +15C
setting would result in inadequate refreshing and cause data corruption.
Partial-Array Refresh
Partial-array refresh (PAR) restricts refresh operation to a portion of the total memory
array. This feature enables the device to reduce standby current by refreshing only that
part of the memory array required by the host system. The refresh options are full array,
one-half array, one-quarter array, one-eighth array, or none of the array. The mapping of
these partitions can start at either the beginning or the end of the address map (see
Table 6 on page 28). READ and WRITE operations to address ranges receiving refresh will
not be affected. Data stored in addresses not receiving refresh will become corrupted.
When re-enabling additional portions of the array, the new portions are available imme-
diately upon writing to the RCR.
Deep Power-Down Operation
Deep power-down (DPD) operation disables all refresh-related activity. This mode is
used if the system does not require the storage provided by the CellularRAM device. Any
stored data will become corrupted when DPD is enabled. When refresh activity has been
re-enabled by rewriting the RCR, the CellularRAM device will require 150s to perform
an initialization procedure before normal operations can resume. During this 150s
period, the current consumption will be higher than the specified standby levels, but
considerably lower than the active current specification.
DPD cannot be enabled or disabled by writing to the RCR using the software access
sequence; the RCR should be accessed using CRE instead.
Configuration Registers
Two user-accessible configuration registers define the device operation. The bus config-
uration register (BCR) defines how the CellularRAM interacts with the system memory bus
and is nearly identical to its counterpart on burst mode Flash devices. The refresh configu-
ration register (RCR) is used to control how refresh is performed on the DRAM array.
These registers are automatically loaded with default settings during power-up and can
be updated any time the devices are operating in a standby state.
Access Using CRE
The configuration registers are loaded using either a synchronous or an asynchronous
WRITE operation when the configuration register enable (CRE) input is HIGH (see
Figure 13 on page 19 and Figure 14 on page 20). When CRE is LOW, a READ or WRITE
operation will access the memory array. The register values are placed on address pins
A[19:0]. In an asynchronous WRITE, the values are latched into the configuration
register on the rising edge of ADV#, CE#, or WE#, whichever occurs first; LB# and UB#
are Dont Care. Access using CRE is WRITE only. The BCR is accessed when A[19] is
HIGH; the RCR is accessed when A[19] is LOW.
Figure 13: Configuration Register WRITE in Asynchronous Mode Followed by READ ARRAY
Operation
Note: A[19] = LOW to load RCR; A[19] = HIGH to load BCR.
A[18:0]
CLK
OPCODE ADDRESS
ADDRESS
DATA VALID
A19
1
ADV#
CE#
OE#
WE#
LB#/UB#
DQ[15:0]
Initiate Control Register Access
Write Address Bus Value
to Control Register
CRE
t
AVS
t
AVH
t
AVH
t
AVS
t
VP
t
VPH
t
CPH
t
WP
t
CW
DONT CARE
Select Control Register
Figure 14: Configuration Register WRITE in Synchronous Mode Followed by READ ARRAY
Operation
Notes: 1. Non-default BCR settings for CR WRITE in synchronous mode followed by READ ARRAY
operation: Latency code two (three clocks); WAIT active LOW; WAIT asserted during delay.
2. A[19] = LOW to load RCR; A[19] = HIGH to load BCR.
3. CE# must remain LOW to complete a burst-of-one WRITE. WAIT must be monitoredaddi-
tional WAIT cycles caused by refresh collisions require a corresponding number of addi-
tional CE# LOW cycles.
CLK
A[18:0]
A19
2
CRE
ADV#
CE#
OE#
WE#
LB#/UB#
WAIT
DQ[15:0]
t
SP
t
SP
t
SP
t
HD
t
HD
t
HD
t
CSP
t
SP
t
HD
High-Z
OPCODE ADDRESS
High-Z
t
CEW
Latch Control Register Value
Latch Control Register Address
t
CBPH
3
DATA
VALID
ADDRESS
DONT CARE
Software Access
Software access of the configuration registers uses a sequence of asynchronous READ
and asynchronous WRITE operations. The contents of the configuration registers can be
read or modified using the software sequence.
The configuration registers are loaded using a four-step sequence consisting of two
asynchronous READ operations followed by two asynchronous WRITE operations (see
Figure 15). The read sequence is virtually identical except that an asynchronous READ is
performed during the fourth operation (see Figure 16). Note that a third READ cycle of
the highest address will cancel the access sequence until a different address is read.
The address used during all READ and WRITE operations is the highest address of the
CellularRAM device being accessed (FFFFFh for 16Mb); the content at this address is not
changed by using this sequence.
The data value presented during the third operation (WRITE) in the sequence defines
whether the BCR or the RCR is to be accessed. If the data is 0000h, the sequence will
access the RCR; if the data is 0001h, the sequence will access the BCR. During the fourth
operation, DQ[15:0] transfer data into or out of bits 150 of the configuration registers.
The use of the software sequence does not affect the ability to perform the standard
(CRE-controlled) method of loading the configuration registers. However, the software
nature of this access mechanism eliminates the need for the control register enable
(CRE) pin. If the software mechanism is used, the CRE pin can simply be tied to VSS. The
port line often used for CRE control purposes is no longer required.
Software access of the RCR should not be used to enter or exit DPD.
Figure 15: Load Configuration Register
Note: If the data present when WE# falls is not 0000h or 0001h, it is possible that the maximum
address will be overwritten.
ADDRESS
(MAX)
ADDRESS
(MAX)
ADDRESS
(MAX)
XXXXh XXXXh
CR VALUE
IN
ADDRESS
CE#
OE#
WE#
LB#/UB#
DATA
DON'T CARE
READ READ WRITE

WRITE
ADDRESS
(MAX)
Note 0ns (Min)
RCR: 0000h
BCR: 0001h
Figure 16: Read Configuration Register
Note: If the data present when WE# falls is not 0000h or 0001h, it is possible that the maximum
address will be overwritten.
ADDRESS
(MAX)
ADDRESS
(MAX)
ADDRESS
(MAX)
XXXXh XXXXh
CR VALUE
OUT
ADDRESS
CE#
OE#
WE#
LB#/UB#
DATA
DON'T CARE
READ READ WRITE

READ
ADDRESS
(MAX)
Note: 0ns (Min)
RCR: 0000h
BCR: 0001h
Bus Configuration Register
The BCR defines how the CellularRAM device interacts with the system memory bus.
Page mode operation is enabled by a bit contained in the RCR. Figure 17 describes the
control bits in the BCR. At power-up, the BCR is set to 9D4Fh.
The BCR is accessed using CRE and A[19] HIGH or through the configuration register
software sequence with DQ = 0001h on the third cycle.
Figure 17: Bus Configuration Register Definition
Note: All burst WRITEs are continuous.
A13
13 12 11 0
Latency
Counter
3 2 1
WAIT
Polarity
4 5
WAIT
Configuration (WC)
Clock
Configuration (CC)
6 7 8
Output
Impedance
Burst
Wrap (BW)*
14
A12A11 A10 A9 A8 A7 A6 A5 A4 A3 A2 A1 A0
0
1
Operation Mode
Synchronous burst access mode
Asynchronous access mode (default)
BCR[12] BCR[11] Latency Counter BCR[13]
0
0
0
0
1
1
1
1
0
0
1
1
0
0
1
1
0
1
0
1
0
1
0
1
Code 0Reserved
Code 1Reserved
Code 2
Code 3 (Default)
Code 4Reserved
Code 5Reserved
Code 6Reserved
Code 7Reserved
0
1
WAIT Polarity
Active LOW
Active HIGH (default)
BCR[10]
0
1
WAIT Configuration
Asserted during delay
Asserted one data cycle before delay (default)
0
1
Output Impedance
Full Drive (default)
1/4 Drive
BCR[5]
Burst Wrap (Note 1)
Burst wraps within the burst length
Burst no wrap (default)
BCR[3]
BCR[1] BCR[0] Burst Length (Note 1) BCR[2]
15
Burst
Length (BL)*
Reserved Reserved
9 10
Reserved
Operating
Mode
Reserved
A14 A15 A[18:16]
0
1
Register Select
Select RCR
Select BCR
Must be set to "0"
19 1816
Register
Select
A19
Reserved
Must be set to "0" Must be set to "0" Must be set to "0" Must be set to "0"
BCR[8]
0
1
Clock Configuration
Not supported
Rising edge (default)
BCR[6]
BCR[15]
BCR[19]
0
1
0
0
0
1
0
1
1
1
1
0
1
1
4 words
8 words
16 words
Continuous burst (default)
Burst Length (BCR[2:0]) Default = Continuous Burst
Burst lengths define the number of words the device outputs during a burst READ oper-
ation. The device supports a burst length of 4, 8, or 16 words. The device can also be set
in continuous burst mode where data is output sequentially without regard to address
boundaries; the internal address wraps to 000000h if the device is read past the last
address. WRITE bursts are always performed using continuous burst mode.
Burst Wrap (BCR[3]) Default = Burst No Wrap (Within Burst Length)
The burst wrap option determines if a 4-, 8-, or 16-word burst READ wraps within the
burst length or steps through sequential addresses. If the wrap option is not enabled, the
device outputs data from sequential addresses without regard to burst boundaries; the
internal address wraps to 000000h if the device is read past the last address.
Table 4: Sequence and Burst Length
Burst Wrap
Starting
Address
4-Word
Burst
Length
8-Word
Burst Length 16-Word Burst length Continuous Burst
BCR[3] Wrap (Decimal) Linear Linear Linear Linear
0 Yes
0 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2-3-4-5-6-7-8-9-10-11-12-13-14-15 0-1-2-3-4-5-6-
1 1-2-3-0 1-2-3-4-5-6-7-0 1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-0 1-2-3-4-5-6-7-
2 2-3-0-1 2-3-4-5-6-7-0-1 2-3-4-5-6-7-8-9-10-11-12-13-14-15-0-1 2-3-4-5-6-7-8-
3 3-0-1-2 3-4-5-6-7-0-1-2 3-4-5-6-7-8-9-10-11-12-13-14-15-0-1-2 3-4-5-6-7-8-9-
4 4-5-6-7-0-1-2-3 4-5-6-7-8-9-10-11-12-13-14-15-0-1-2-3 4-5-6-7-8-9-10-
5 5-6-7-0-1-2-3-4 5-6-7-8-9-10-11-12-13-14-15-0-1-2-3-4 5-6-7-8-9-10-11-
6 6-7-0-1-2-3-4-5 6-7-8-9-10-11-12-13-14-15-0-1-2-3-4-5 6-7-8-9-10-11-12-
7 7-0-1-2-3-4-5-6 7-8-9-10-11-12-13-14-15-0-1-2-3-4-5-6 7-8-9-10-11-12-13-
... ... ...
14 14-15-0-1-2-3-4-5-6-7-8-9-10-11-12-13 14-15-16-17-18-19-20-
...
15 15-0-1-2-3-4-5-6-7-8-9-10-11-12-13-14 15-16-17-18-19-20-
21...
1 No
0 0-1-2-3 0-1-2-3-4-5-6-7 0-1-2-3-4-5-6-7-8-9-10-11-12-13-14-15 0-1-2-3-4-5-6-
1 1-2-3-4 1-2-3-4-5-6-7-8 1-2-3-4-5-6-7-8-9-10-11-12-13-14-15-16 1-2-3-4-5-6-7-
2 2-3-4-5 2-3-4-5-6-7-8-9 2-3-4-5-6-7-8-9-10-11-12-13-14-15-16-
17
2-3-4-5-6-7-8-
3 3-4-5-6 3-4-5-6-7-8-9-10 3-4-5-6-7-8-9-10-11-12-13-14-15-16-17-
18
3-4-5-6-7-8-9-
4 4-5-6-7-8-9-10-11 4-5-6-7-8-9-10-11-12-13-14-15-16-17-
18-19
4-5-6-7-8-9-10-
5 5-6-7-8-9-10-11-12 5-6-7-8-9-10-11-12-13-...-15-16-17-18-
19-20
5-6-7-8-9-10-11
6 6-7-8-9-10-11-12-
13
6-7-8-9-10-11-12-13-14-...-16-17-18-19-
20-21
6-7-8-9-10-11-12
7 7-8-9-10-11-12-13-
14
7-8-9-10-11-12-13-14-...-17-18-19-20-
21-22
7-8-9-10-11-12-13
... ... ...
14 14-15-16-17-18-19-...-23-24-25-26-27-
28-29
14-15-16-17-18-19-20-
15 15-16-17-18-19-20-...-24-25-26-27-28-
29-30
15-16-17-18-19-20-21-
Output Impedance (BCR[5]) Default = Outputs Use Full Drive Strength
The output driver strength can be altered to adjust for different data bus loading
scenarios. The reduced-strength option should be more than adequate in stacked chip
(Flash + CellularRAM) environments when there is a dedicated memory bus. The reduced-
drive-strength option is included to minimize noise generated on the data bus during
READ operations. Normal output impedance should be selected when using a discrete
CellularRAM device in a more heavily loaded data bus environment. Partial drive is
approximately one-quarter full drive strength. Outputs are configured at full drive
strength during testing.
WAIT Configuration (BCR[8]) Default = WAIT Transitions One Clock Before Data Valid/Invalid
The WAIT configuration bit is used to determine when WAIT transitions between the
asserted and the de-asserted state with respect to valid data presented on the data bus.
The memory controller will use the WAIT signal to coordinate data transfer during
synchronous READ and WRITE operations. When BCR[8] = 0, data will be valid or invalid
on the clock edge immediately after WAIT transitions to the de-asserted or asserted
state, respectively (see Figures 18 and 20). When BCR[8] = 1, the WAIT signal transitions
one clock period prior to the data bus going valid or invalid (see Figures 19 and 20).
WAIT Polarity (BCR[10]) Default = WAIT Active HIGH
The WAIT polarity bit indicates whether an asserted WAIT output should be HIGH or
LOW. This bit will determine whether the WAIT signal requires a pull-up or pull-down
resistor to maintain the de-asserted state.
Figure 18: WAIT Configuration (BCR[8] = 0)
Note: Data valid/invalid immediately after WAIT transitions (BCR[8] = 0). See Figure 20 on
page 26.
Figure 19: WAIT Configuration (BCR[8] = 1)
Note: Valid/invalid data delayed for one clock after WAIT transitions (BCR[8] = 1). See Figure 20
on page 26.
WAIT
DQ[15:0]
CLK
Data[0] Data[1]
Data immediately valid (or invalid)
High-Z
WAIT
D[15:0]
CLK
Data[0]
Data valid (or invalid) after one clock delay
High-Z
Figure 20: WAIT Configuration During Burst Operation

Note: Non-default BCR setting for WAIT during BURST operation: WAIT active LOW.
Latency Counter (BCR[13:11]) Default = Three-Clock Latency
The latency counter bits determine how many clocks occur between the beginning of a
READ or WRITE operation and the first data value transferred. Only latency code two
(three clocks) or latency code three (four clocks) is allowed (see Table 5 and Figure 21).
Operating Mode (BCR[15]) Default = Asynchronous Operation
The operating mode bit selects either synchronous BURST operation or the default
asynchronous mode of operation.
Figure 21: Latency Counter
Table 5: Latency Configuration
Latency Configuration Code
Max Input CLK Frequency (MHz)
104 MHz 80 MHz
2 (3 clocks) 66 (15ns) 53

(18.75ns)
3 (4 clocks) default 104 (9.62ns) 80 (12.50ns)
WAIT
WAIT
DQ[15:0]
CLK
D[0] D[1]
BCR[8] = 0
Data valid in current cycle.
BCR[8] = 1
Data valid in next cycle.
DONT CARE
D[2] D[3] D[4]
A[19:0]
ADV#
DQ[15:0]
CLK
Code 2
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
Code 3 (Default)
DQ[15:0]
DONT CARE UNDEFINED
V
IH
V
IL
V
IH
V
IL
V
IH
V
IL
V
OH
V
OL
V
OH
V
OL
VALID
ADDRESS
Refresh Configuration Register
The refresh configuration register (RCR) defines how the CellularRAM device performs
its transparent self refresh. Altering the refresh parameters can dramatically reduce
current consumption during standby mode. Page mode control is also embedded into
the RCR. Figure 22 describes the control bits used in the RCR. At power-up, the RCR is set
to 0010h.
The RCR is accessed using CRE and A[19] LOW; or through the configuration register
software access sequence with DQ = 0000h on the third cycle (see Configuration Regis-
ters on page 19.)
Partial-Array Refresh (RCR[2:0]) Default = Full Array Refresh
The PAR bits restrict refresh operation to a portion of the total memory array. This
feature allows the device to reduce standby current by refreshing only that part of the
memory array required by the host system. The refresh options are full array, one-half
array, one-quarter array, one-eighth array, or none of the array. The mapping of these
partitions can start at either the beginning or the end of the address map (see Table 6 on
page 28).
Figure 22: Refresh Configuration Register Mapping

PAR
A4 A3 A2 A1 A0 Address Bus
4 5 1 2 3 0
RESERVED RESERVED
6
A5
0
1
Deep Power-Down
DPD Enable
DPD Disable (default)
RCR[4]
TCR
RCR[6] RCR[5]
1 1
1
1
0 0
0
0
Maximum Case Temp.
+85C
Internal sensor (default)
+45C
+15C
A6
All must be set to "0"
A[18:8]
188 19
Register
Select
A19
0
1
Register Select
Select RCR
Select BCR
RCR[19]
RCR[1]
0
0
1
1
RCR[0]
0
1
0
1
Refresh Coverage
Full array (default)
Bottom 1/2 array
Bottom 1/4 array
Bottom 1/8 array
RCR[2]
0
0
0
0
0 0 1
0
1 1
1 0 1
1 1 1
None of array
Top 1/2 array
Top 1/4 array
Top 1/8 array
DPD
Must be set to "0"
A7
7
PAGE
0
1
Page Mode Enable/Disable
Page Mode Disabled (default)
Page Mode Enable
RCR[7]
Deep Power-Down (RCR[4]) Default = DPD Disabled
The deep power-down bit enables and disables all refresh-related activity. This mode is
used if the system does not require the storage provided by the CellularRAM device. Any
stored data will become corrupted when DPD is enabled. When refresh activity has been
re-enabled, the CellularRAM device will require 150s to perform an initialization proce-
dure before normal operations can resume.
Deep power-down is enabled when RCR[4] = 0, and remains enabled until RCR[4] is set to
1. DPD should not be enabled or disabled with the software access sequence; instead,
use CRE to access the RCR.
Temperature-Compensated Refresh (RCR[6:5]) Default = On-Chip Temperature Sensor
This CellularRAM device includes an on-chip temperature sensor that automatically
adjusts the refresh rate according to the operating temperature. The on-chip TCR is
enabled by clearing both of the TCR bits in the refresh configuration register (RCR[6:5] =
00b). Any other TCR setting enables a fixed refresh rate. When the on-chip temperature
sensor is enabled, the device continually adjusts the refresh rate according to the oper-
ating temperature.
The TCR bits also allow for adequate fixed-rate refresh at three different temperature
thresholds (+15C, +45C, and +85C). The setting selected must be for a temperature
higher than the case temperature of the CellularRAM device. If the case temperature
is +35C, the system can minimize self refresh current consumption by selecting the
+45C setting. The +15C setting would result in inadequate refreshing and cause
data corruption.
Page Mode Operation (RCR[7]) Default = Disabled
The page mode operation bit determines whether page mode is enabled for asynchro-
nous READ operations. In the power-up default state, page mode is disabled.
Table 6: 16Mb Address Patterns for PAR (RCR[4] = 1)
RCR[2] RCR[1] RCR[0] Active Section Address Space Size Density
0 0 0 Full die 000000h0FFFFFh 1 Meg x 16 16Mb
0 0 1 One-half of die 000000h07FFFFh 512K x 16 8Mb
0 1 0 One-quarter of die 000000h03FFFFh 256K x 16 4Mb
0 1 1 One-eighth of die 000000h01FFFFh 128K x 16 2Mb
1 0 0 None of die 0 0 Meg x 16 0Mb
1 0 1 One-half of die 80000h0FFFFFh 512K x 16 8Mb
1 1 0 One-quarter of die C0000h0FFFFFh 256K x 16 4Mb
1 1 1 One-eighth of die E0000h0FFFFFh 128K x 16 2Mb
Electrical Characteristics
Notes: 1. 30C exceeds the CellularRAM Workgroup 1.0 specification of 25C.
Stresses greater than those listed may cause permanent damage to the device. This is a
stress rating only, and functional operation of the device at these or any other conditions
above those indicated in the operational sections of this specification is not implied.
Exposure to absolute maximum rating conditions for extended periods may affect reli-
ability.
Table 7: Absolute Maximum Ratings
Parameter Rating
Voltage to any ball except VCC, VCCQ relative
to VSS
0.5V to (4.0V or VCCQ + 0.3V, whichever is
less)
Voltage on VCC supply relative to VSS 0.2V to +2.45V
Voltage on VCCQ supply relative to VSS 0.2V to +4.0V
Storage temperature (plastic) 55C to +150C
Operating temperature (case)
Wireless
1
Industrial
30C to +85C
40C to +85C
Soldering temperature and time
10 seconds (solder ball only)
+260C
Notes: 1. 30C and 3.6V I/O exceed the CellularRAM Workgroup 1.0 specifications.
2. Input signals may overshoot to VCCQ + 1.0V for periods less than 2ns during transitions.
3. VIH (MIN) value is not aligned with CellularRAM work group 1.0 specification of VCCQ - 0.4V.
4. Input signals may undershoot to VSS - 1.0V for periods less than 2ns during transitions.
5. BCR[5] = 0b.
6. This parameter is specified with the outputs disabled to avoid external loading effects. The
user must add the current required to drive output capacitance expected in the actual sys-
tem.
7. ISB (MAX) values measured with PAR set to FULL ARRAY and TCR set to +85C. In order to
achieve low standby current, all inputs must be driven to either VCCQ or VSS. ISB might be
slightly higher for up to 500ms after power-up, after changes to the PAR array partition, or
when entering standby mode.
Table 8: Electrical Characteristics and Operating Conditions
Wireless temperature
1
(30C < T
C
< +85C); Industrial temperature (40C < T
C
< +85C)
Description Conditions Symbol Min Max Units Notes
Supply voltage VCC 1.7 1.95 V
I/O supply voltage VCCQ 1.7 3.6 V 1
Input high voltage VIH 1.4 VCCQ + 0.2 V 2, 3
Input low voltage VIL 0.2 0.4 V 4
Output high voltage IOH = 0.2mA VOH 0.8 VCCQ V 5
Output low voltage IOL = +0.2mA VOL 0.2 VCCQ V 5
Input leakage current VIN = 0 to VCCQ ILI 1 A
Output leakage current OE# = VIH or
Chip disabled
ILO 1 A
Operating Current
Asynchronous random READ/
WRITE
VIN = VCCQ or 0V
Chip enabled,
IOUT = 0
ICC1 70 20 mA 6
Asynchronous page READ ICC1P 70 15 mA 6
Initial access, burst READ/WRITE ICC2 104 MHz 35 mA 6
80 MHz 30
Continuous burst READ ICC3R 104 MHz 28 mA 6
80 MHz 22
Continuous burst WRITE ICC3W 104 MHz 33 mA 6
80 MHz 25
Standby current VIN = VCCQ or 0V
CE# = VCCQ
ISB Standard 70 A 7
Maximum and Typical Standby Currents
The following table and figure refer to the maximum and typical standby currents for the
MT45W1MW16BDGB device. The typical values shown in Figure 23 are measured with
the default on-chip temperature sensor control enabled. The maximum values shown in
Table 9 are measured with the relevant TCR bits set in the configuration register.
Notes: 1. For RCR[6:5] = 00b (default) refer to Figure 23, Typical Refresh Current vs. Temperature
(ITCR) for typical values.
2. In order to achieve low standby current, all inputs must be driven to VCCQ or VSS. ISB might
be slightly higher for up to 500ms after power-up, after changes to the PAR array portion,
or when entering standby mode.
3. TCR values for 85C are 100 percent tested. TCR values for 15C and 45C are sampled only.
4. Typical ISB currents for each PAR setting with the appropriate TCR selected, or temperature
sensor enabled.
Figure 23: Typical Refresh Current vs. Temperature (ITCR)
Note: Typical ISB currents for each PAR setting with the appropriate TCR selected, or temperature
sensor enabled.
Table 9: Maximum Standby Currents for Applying PAR and TCR Settings
PAR
TCR
Units +15C (RCR[6:5] = 10b) +45C (RCR[6:5] = 01b) +85C (RCR[6:5] = 11b)
Full array 45 60 70 A
1/2 array 40 55 65 A
1/4 array 37 50 60 A
1/8 array 37 50 60 A
0 array 35 45 55 A
0
5
10
15
20
25
30
35
40
45
50
-
4
5
C
-
3
5
C
-
2
5
C
-
1
5
C
-
0
5
C

0
5
C

1
5
C

2
5
C

3
5
C

4
5
C

5
5
C

6
5
C

7
5
C

8
5
C
Temperature (C)
I
S
B

(
A
)
PAR FULL
PAR 1/2
PAR 1/4
PAR 0
Notes: 1. These parameters are verified in device characterization and are not 100 percent tested.
Figure 24: AC Input/Output Reference Waveform

Notes: 1. AC test inputs are driven at VCCQ for a logic 1 and VSSQ for a logic 0. Input rise and fall
times (10% to 90%) < 1.6ns.
2. Input timing begins at VCC/2. Due to the possibility of a difference between VCC and VCCQ,
the input test point may not be shown to scale.
3. Output timing ends at VCCQ/2.
Figure 25: Output Load Circuit
Notes: 1. All tests are performed with the outputs configured for full drive strength (BCR[5] = 0b).
Table 10: Deep Power-Down Specifications
Description Conditions Symbol Typ Units
Deep power-down VIN = VCCQ or 0V; +25C IZZ 10 A
Table 11: Capacitance
Description Conditions Symbol Min Max Units Notes
Input capacitance T
C
= +25C; f = 1 MHz;
VIN = 0V
CIN 2.0 6.5 pF 1
Input/output capacitance (DQ) CIO 3.0 6.5 pF 1
Output Test Points Input
1
VCCQ
VSSQ
VCCQ/2
3
VCC/2
2
DUT VccQ/2
30pF
Test Point
50
Timing Requirements
Timing Requirements
2. Low-Z to High-Z timings are tested with the circuit shown in Figure 25 on page 32. The
High-Z timings measure a 100mV transition from either VOH or VOL toward VCCQ/2.
3. High-Z to Low-Z timings are tested with the circuit shown in Figure 25 on page 32. The Low-
Z timings measure a 100mV transition away from the High-Z (VCCQ/2) level toward either
VOH or VOL.
4. Page mode enabled only.
Table 12: Asynchronous READ Cycle Timing Requirements
Parameter
1
Symbol
70ns
Units Notes Min Max
Address access time
t
AA 70 ns
ADV# access time
t
AADV 70 ns
Page access time
t
APA 20 ns
Address hold from ADV# HIGH
t
AVH 5 ns
Address setup to ADV# HIGH
t
AVS 10 ns
LB#/UB# access time
t
BA 70 ns
LB#/UB# disable to DQ High-Z output
t
BHZ 8 ns 4
LB#/UB# enable to Low-Z output
t
BLZ 10 ns 3
Maximum CE# pulse width
t
CEM 8 s 2
CE# LOW to WAIT valid
t
CEW 1 7.5 ns
Chip select access time
t
CO 70 ns
CE# LOW to ADV# HIGH
t
CVS 10 ns
Chip disable to DQ and WAIT High-Z output
t
HZ 8 ns 4
Chip enable to Low-Z output
t
LZ 10 ns 3
Output enable to valid output
t
OE 20 ns
Output hold from address change
t
OH 5 ns
Output disable to DQ High-Z output
t
OHZ 8 ns 4
Output enable to Low-Z output
t
OLZ 3 ns 3
Page cycle time
t
PC 20 ns
READ cycle time
t
RC 70 ns
ADV# pulse width LOW
t
VP 10 ns
ADV# pulse width HIGH
t
VPH 10 ns
Timing Requirements
2. When configured for synchronous mode (BCR[15] = 0), a refresh opportunity must be pro-
vided every
t
CEM. A refresh opportunity is satisfied by either of the following two condi-
tions: a) clocked CE# HIGH, or b) CE# HIGH for greater than 15ns.
High-Z timings measure a 100mV transition from either VOH or VOL toward VCCQ/2.
4. High-Z to Low-Z timings are tested with the circuit shown in Figure 25 on page 32. The Low-
VOH or VOL.
Table 13: Burst READ Cycle Timing Requirements
Parameter
1
Symbol
104 MHz 80 MHz
Units Notes Min Max Min Max
Burst to READ access time
t
ABA 35 46.5 ns
CLK to output delay
t
ACLK 7 9 ns
Burst OE# LOW to output delay
t
BOE 20 20 ns
CE# HIGH between subsequent burst and
mixed-mode operations
t
CBPH 5 5 ns 2
t
CEM 8 8 s
t
CEW 1 7.5 1 7.5 ns
CLK period
t
CLK 9.62 20 12.5 20 ns
CE# setup time to active CLK edge
t
CSP 3 20 4.5 20 ns
Hold time from active CLK edge
t
HD 2 2 ns
Chip disable to DQ and WAIT High-Z output
t
HZ 8 8 ns 3
CLK rise or fall time
t
KHKL 1.6 1.8 ns
CLK to WAIT valid
t
KHTL 7 9 ns
Output HOLD from CLK
t
KOH 2 2 ns
CLK HIGH or LOW time
t
KP 3 4 ns
Output disable to DQ High-Z output
t
OHZ 8 8 ns 3
Output enable to Low-Z output
t
OLZ 3 3 ns 4
Setup time to active CLK edge
t
SP 3 3 ns
Timing Requirements
Notes: 1. High-Z to Low-Z timings are tested with the circuit shown in Figure 25 on page 32. The Low-
VOH or VOL.
High-Z timings measure a 100mV transition from either VOH or VOL

toward VCCQ/2.
3. WE# LOW time must be limited to
t
CEM (8s).
Table 14: Asynchronous WRITE Cycle Timing Requirements
Parameter Symbol
70ns
Units Notes Min Max
Address and ADV# LOW setup time
t
AS 0 ns
Address hold from ADV# going HIGH
t
AVH 5 ns
Address setup to ADV# going HIGH
t
AVS 10 ns
Address valid to end of WRITE
t
AW 70 ns
LB#/UB# select to end of WRITE
t
BW 70 ns
t
CEW 1 7.5 ns
Async address-to-burst transition time
t
CKA 70 ns
CE# HIGH between subsequent asynchronous operations
t
CPH 5 ns
CE# LOW to ADV# HIGH
t
CVS 10 ns
Chip enable to end of WRITE
t
CW 70 ns
Data hold from WRITE time
t
DH 0 ns
Data WRITE setup time
t
DW 23 ns
Chip disable to WAIT High-Z output
t
HZ 8 ns
Chip enable to Low-Z output
t
LZ 10 ns 1
End WRITE to Low-Z output
t
OW 5 ns 1
ADV# pulse width
t
VP 10 ns
ADV# pulse width HIGH
t
VPH 10 ns
ADV# setup to End of WRITE
t
VS 70 ns
WRITE cycle time
t
WC 70 ns
WRITE to DQ High-Z output
t
WHZ 8 ns 2
WRITE pulse width
t
WP 46 ns 3
WRITE pulse width HIGH
t
WPH 10 ns
WRITE recovery time
t
WR 0 ns
Timing Requirements
Notes: 1. When configured for synchronous mode (BCR[15] = 0), a refresh opportunity must be pro-
vided every
t
tions: a) clocked CE# HIGH, or b) CE# HIGH for greater than 15ns.
Figure 26: Initialization Period

Table 15: Burst WRITE Cycle Timing Requirements
Parameter Symbol
104 MHz 80 MHz
Units Notes Min Max Min Max
CE# HIGH between subsequent burst and
mixed-mode operations
t
CBPH 5 5 ns 1
t
CEM 8 8 s 1
t
CEW 1 7.5 1 7.5 ns
Clock period
t
CLK 9.62 20 12.5 20 ns
CE# setup to CLK active edge
t
CSP 3 20 4.5 20 ns
Hold time from active CLK edge
t
HD 2 2 ns
Chip disable to WAIT High-Z output
t
HZ 8 8 ns
CLK rise or fall time
t
KHKL 1.6 1.8 ns
Clock to WAIT valid
t
KHTL 7 9 ns
CLK HIGH or LOW time
t
KP 3 4 ns
Setup time to active CLK edge
t
SP 3 3 ns
Table 16: Initialization Timing Parameters
Parameter Symbol
-70
Units Min Max
Initialization period (required before normal operations)
t
PU 150 s
t
PU
Vcc, VccQ = 1.7V
Vcc (MIN)
Device ready for
normal operation
Timing Diagrams
Timing Diagrams
Figure 27: Asynchronous READ
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
VOH
VOL
A[19:0]
ADV#
CE#
LB#/UB#
OE#
WE#
WAIT
DQ[15:0]
VALID ADDRESS
t
AA
t
HZ
t
BA
High-Z High-Z
t
RC
t
CO
t
BHZ
t
OHZ
t
OE
t
CEW t
HZ
VALID OUTPUT
High-Z
UNDEFINED DONT CARE
t
BLZ
t
LZ
t
OLZ
Timing Diagrams
Figure 28: Asynchronous READ Using ADV#
A[19:0]
ADV#
CE#
LB#/UB#
OE#
WE#
WAIT
DQ[15:0]
VALID ADDRESS
t
VPH
t
AADV
t
AA
t
VP
t
HZ
t
BA
High-Z High-Z
t
CVS
t
CO
t
BLZ
t
BHZ
t
OHZ
t
LZ
t
OE
t
OLZ
VALID OUTPUT
t
AVH
t
AVS
High-Z
UNDEFINED DONT CARE
t
CEW t
HZ
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
VOH
VOL
Timing Diagrams
Figure 29: Page Mode READ

A[3:0]
ADV#
CE#
LB#/UB#
OE#
WE#
WAIT
DQ[15:0]
VALID ADDRESS
t
AA
t
HZ
t
BA
High-Z High-Z
t
CO
t
CEM
t
BLZ
t
BHZ
t
OHZ
t
LZ
t
OE
t
OLZ
t
CEW t
HZ
High-Z
UNDEFINED DONT CARE
A[19:4]
VALID ADDRESS
VALID
ADDRESS
VALID
ADDRESS
VALID
ADDRESS
t
RC
VALID
OUTPUT
t
APA
t
PC
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
VOH
VOL
t
OH
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
Timing Diagrams
Figure 30: Single-Access Burst READ Operation
Notes: 1. Non-default BCR settings for single-access burst READ operation: Latency code two (three
clocks); WAIT active LOW; WAIT asserted during delay.
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VOH
VOL
t
SP
t
CLK
t
ACLK
t
CEW
t
HD
t
ABA
VALID
OUTPUT
VALID
ADDRESS
High-Z
t
KOH
t
OHZ
t
SP
t
HD
LB#/UB#
VIH
VIL
t
CSP
t
CEM
High-Z
t
OLZ
High-Z
t
HD
t
HZ
t
KP
t
KP
t
KHKL
t
HD
t
SP
UNDEFINED DONT CARE
(WE# = HIGH)
t
KHTL
t
BOE
Timing Diagrams
Figure 31: 4-Word Burst READ Operation

Note: Non-default BCR settings for 4-word burst READ operation: Latency code two (three
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VOH
VOL
t
SP
t
CLK
t
KHKL
t
HD
t
ABA
VALID
ADDRESS
High-Z
t
KOH
t
HZ
t
HD
t
SP
t
HD
LB#/UB#
VIH
VIL
High-Z
t
OLZ
t
CBPH
t
CSP
t
CEM
t
SP
t
HD
t
OHZ
t
KP
t
KP
UNDEFINED DONT CARE
(WE# = HIGH)
t
CEW
t
ACLK
t
KHTL
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
t
BOE
High-Z
Timing Diagrams
Figure 32: READ Burst Suspend

Note: Non-default BCR settings for READ burst suspend: Latency code two (three clocks); WAIT
active LOW; WAIT asserted during delay.
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VOH
VOL
t
SP
t
HD
High-Z
t
OLZ
t
ACLK
LB#/UB#
VIH
VIL
t
CLK
t
SP
t
HD
t
CSP
t
CEM
t
SP
t
HD
t
KOH
VALID
OUTPUT
VALID
OUTPUT
VALID
ADDRESS
High-Z
t
CBPH
t
HZ
t
OHZ
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
t
BOE
t
OHZ
t
BOE
t
OLZ
VALID
ADDRESS
High-Z
DONT CARE UNDEFINED
Timing Diagrams
Figure 33: Continuous Burst READ Showing an Output Delay with BCR[8] = 0 for End-of-Row
Condition

Notes: 1. Non-default BCR settings for continuous burst READ showing an output delay, BCR[8] = 0
for end-of-row condition: Latency code two (three clocks); WAIT active LOW; WAIT asserted
during delay.
2. WAIT will be asserted a maximum of (2 LC) cycles (BCR[8] = 0; WAIT asserted during delay).
LC = latency code (BCR[13:11]).
3. CE# must not remain LOW longer than
t
CEM.
t
ACLK
t
KOH
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VOH
VOL
t
KHTL
t
KHTL
t
CLK
LB#/UB#
VIH
VIL
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
Note 2
Note 3
DONT CARE
Timing Diagrams
Figure 34: CE#-Controlled Asynchronous WRITE

A[19:0]
ADV#
CE#
LB#/UB#
OE#
WE#
WAIT
DQ[15:0]
IN
VALID ADDRESS
High-Z High-Z
t
WC
t
CEW t
HZ
VALID INPUT
t
AW
DONT CARE
t
WR
t
CW
t
DW
DQ[15:0]
OUT
t
WHZ
t
BW
t
LZ
t
DH
t
AS
t
WP
t
WPH
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
VOH
VOL
High-Z
t
CPH
Timing Diagrams
Figure 35: LB#/UB#-Controlled Asynchronous WRITE

VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
A[19:0]
ADV#
CE#
LB#/UB#
OE#
WE#
WAIT
DQ[15:0]
IN
VIH
VIL
VALID ADDRESS
High-Z
t
WC
t
CEW
t
HZ
VALID INPUT
t
AW
DONT CARE
t
WR
t
CW
t
DW
DQ[15:0]
OUT
VOH
VOL
t
WHZ
t
BW
t
LZ
t
DH
t
AS
t
WP
t
WPH
High-Z
High-Z
Timing Diagrams
Figure 36: WE#-Controlled Asynchronous WRITE

VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
A[19:0]
ADV#
CE#
LB#/UB#
OE#
WE#
WAIT
DQ[15:0]
IN
VIH
VIL
VALID ADDRESS
t
WC
t
CEW
t
HZ
VALID INPUT
t
AW
DONT CARE
t
WR
t
DW
DQ[15:0]
OUT
VOH
VOL
t
WHZ
t
BW
t
CW
t
LZ
t
WP
t
DH
t
OW
t
AS
t
WPH
High-Z
High-Z
High-Z
Timing Diagrams
Figure 37: Asynchronous WRITE Using ADV#

VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VOH
VOL
A[19:0]
ADV#
CE#
LB#/UB#
OE#
WE#
WAIT
DQ[15:0]
IN
VIH
VIL
VALID ADDRESS
High-Z High-Z
t
CEW
t
HZ
VALID INPUT
t
VS
DONT CARE
t
CW
t
DW
DQ[15:0]
OUT
VOH
VOL
t
WHZ
t
BW
t
LZ
t
WP
t
DH
t
OW
t
AS
t
WPH
t
AS
t
VPH
t
AVH t
AVS
t
VP
t
AW
High-Z
Timing Diagrams
Figure 38: Burst WRITE Operation

Note: Non-default BCR settings for burst WRITE operation: Latency code two (three clocks);
WAIT active LOW; WAIT asserted.
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VIH
VIL
t
CLK
t
KP
t
SP
t
HD
t
CSP
t
CEM
D[3] D[2] D[1] D[0]
VALID
ADDRESS
t
HD
t
SP
t
HD
t
SP
t
HD
t
SP
High-Z High-Z
LB#/UB#
VIH
VIL
t
SP
t
HD
t
HD
DONT CARE
WRITE Burst Identified
(WE# = LOW)
t
CBPH
t
KHTL t
HZ
t
CEW
t
KP
t
KHKL
Timing Diagrams
Figure 39: Continuous Burst WRITE Showing an Output Delay with BCR[8] = 0 for End-of-Row
Condition

Notes: 1. Non-default BCR settings for continuous burst WRITE, BCR[8] = 0; WAIT active LOW; WAIT
asserted during delay. Do not cross row boundaries with fixed latency.
2. CE# must not remain LOW longer than
t
CEM.
3. WAIT asserts for anywhere from LC to 2LC cycles. LC = latency code (BCR[13:11]).
4. Taking CE# HIGH or ADV# LOW on the start-of-row cycle will abort the burst and not write
the start-of-row data. Devices from different CellularRAM vendors can assert WAIT so that
the start-of-row data is input just before (as shown), or just after WAIT asserts. This differ-
ence in behavior will not be noticed by controllers that monitor WAIT, or that use WAIT to
abort on the start-of-row input cycle.
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VIH
VIL
t
KHTL
t
KHTL
t
CLK
t
SP
t
HD
VALID INPUT VALID INPUT
Start of row
(A[6:0] = 00h)
(NOTE 4)
End of row
(A[6:0] = 7Fh)
Note 3
Note 4
VALID INPUT VALID INPUT
DONT CARE
VIH
VIL
LB#/UB#
Timing Diagrams
Figure 40: Burst WRITE Followed by Burst READ

Notes: 1. Non-default BCR settings for burst WRITE followed by burst READ: Latency code two (three
vided every
t
tions: a) clocked CE# HIGH, or b) CE# HIGH for greater than 15ns. Note that the CellularRAM
Workgroup 1.0 specification requires CE# to be clocked HIGH to terminate the burst.
3. Clock rates below 50 MHz (
t
CLK > 20ns) are allowed as long as
t
CSP specifications are met.
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
IN/OUT
VOH
VOL
CLK
VIH
VIL
VIH
VIL
t
CLK
t
SP
t
SP
t
HD
t
CSP
D[3] D[2] D[1] D[0]
VALID
ADDRESS
t
HD
t
SP
t
HD
t
SP
t
SP
t
HD
VALID
ADDRESS
t
ABA
t
CSP t
OHZ
t
KOH
t
ACLK
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
High-Z High-Z
VOH
VOL
LB#/UB#
VIH
VIL
t
HD
t
SP
t
HD
t
SP
t
HD
t
HD
High-Z
UNDEFINED DONT CARE
t
BOE
tCBPH
2
High-Z
t
SP
t
HD
Timing Diagrams
Figure 41: Asynchronous WRITE Followed by Burst READ

Notes: 1. Non-default BCR settings for asynchronous WRITE followed by burst READ: Latency code
two (three clocks); WAIT active LOW; WAIT asserted during delay.
vided every
t
tions: a) clocked CE# HIGH, or b) CE# HIGH for greater than 15ns. Note that the CellularRAM
Workgroup 1.0 specification requires CE# to be clocked HIGH to terminate the burst.
t
t
t
CLK
t
SP t
HD
t
SP
t
HD
VALID
ADDRESS
t
OHZ
t
KOH
t
ACLK
High-Z
High-Z
VALID ADDRESS VALID ADDRESS
t
AVS
t
AVH
t
AW
t
WR
t
VP
t
VS
t
CKA
A[19:0]
VIH
VIL
ADV#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
IN/OUT
VOH
VOL
CLK
VIH
VIL
VIH
VIL
VOH
VOL
CE#
VIH
VIL
LB#/UB#
VIH
VIL
t
CW
t
WPH
t
AS
t
AS
t
WP
t
WC
t
DH t
DW
DATA DATA High-Z
t
CVS
t
HD
t
SP
t
CEW
t
SP
t
HD
t
CSP
t
WC
t
WC
t
BW
t
WHZ
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
DONT CARE UNDEFINED
t
ABA
t
BOE
t
CBPH
2
t
VPH
Timing Diagrams
Figure 42: Asynchronous WRITE Followed by Burst READ ADV# LOW

Notes: 1. Non-default BCR settings for asynchronous WRITE followed by burst READ: Latency code
two (three clocks); WAIT active LOW; WAIT asserted during delay.
vided every
t
CEM. A refresh opportunity is satisfied by either of these conditions: a) clocked
CE# HIGH, or b) CE# HIGH for greater than 15ns. Note that the CellularRAM Workgroup 1.0
specification requires CE# to be clocked HIGH to terminate the burst.
t
t
t
CLK
t
SP t
HD
t
SP
t
HD
VALID
ADDRESS
t
OHZ
t
KOH
t
ACLK
High-Z
High-Z
t
AVS
t
AVH
t
AW
t
WR
t
VP
t
VS
t
CKA
A[19:0]
VIH
VIL
ADV#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
IN/OUT
VOH
VOL
CLK
VIH
VIL
VIH
VIL
VOH
VOL
CE#
VIH
VIL
LB#/UB#
VIH
VIL
t
CW
t
WPH
t
AS
t
AS
t
WP
t
WC
t
DH t
DW
DATA DATA High-Z
t
CVS
t
HD
t
SP
t
CEW
t
SP
t
HD
t
CSP
t
WC
t
WC
t
BW
t
WHZ
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
VALID
OUTPUT
DONT CARE UNDEFINED
t
ABA
t
BOE
t
CBPH
2
t
VPH
Timing Diagrams
Figure 43: Burst READ Followed by Asynchronous WRITE (WE#-Controlled)
vided every
t
tions: a) clocked CE# HIGH, or b) CE# HIGH for greater than 15ns. Note that CellularRAM
Workgroup specification 1.0 requires CE# to be clocked HIGH to terminate the burst.

A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VOH
VOL
t
SP
t
CLK
t
ACLK
t
CEW
t
HD
t
ABA
t
AW
t
CW
t
WR
VALID
OUTPUT
VALID
ADDRESS
High-Z
t
KOH
t
DW
t
OHZ
t
SP
t
HD
LB#/UB#
VIH
VIL
t
CSP
High-Z
t
OLZ
t
HD
t
WP
t
WPH
t
AS
t
DH
t
HZ
t
HD
t
BW
t
SP
t
HZ
t
HD
t
SP
(WE# = HIGH)
t
WC
t
KHTL
t
BOE
VALID
ADDRESS
VALID
INPUT
High-Z
t
CEW
t
CBPH
1
DONT CARE UNDEFINED
Timing Diagrams
Figure 44: Burst READ Followed by Asynchronous WRITE Using ADV#

vided every
t
tions: a) clocked CE# HIGH, or b) CE# HIGH for greater than 15ns. Note that CellularRAM
Workgroup specification 1.0 requires CE# to be clocked HIGH to terminate the burst.
A[19:0]
VIH
VIL
ADV#
VIH
VIL
CE#
VIH
VIL
OE#
VIH
VIL
WE#
VIH
VIL
WAIT
DQ[15:0]
VOH
VOL
CLK
VIH
VIL
VOH
VOL
t
SP
t
CLK
t
CEW
t
HD
t
ABA
t
VPH
t
VS
t
AVS
t
AVH
t
AW
t
CW
VALID
OUTPUT
VALID
ADDRESS
High-Z
t
KOH
t
DW
t
OHZ
t
SP
t
HD
t
VP
LB#/UB#
VIH
VIL
t
CSP
High-Z
t
OLZ
t
HD
t
WP
t
WPH
t
AS
t
DH
t
HD t
BW
t
SP
t
HZ
t
HD
t
SP
UNDEFINED DONT CARE
(WE# = HIGH)
t
KHTL
VALID
ADDRESS
VALID
INPUT
High-Z
t
CEW t
HZ
t
CBPH
1
t
ACLK
t
BOE
t
AS
Timing Diagrams
Figure 45: Asynchronous WRITE Followed by Asynchronous READ ADV# LOW

Notes: 1. When configured for synchronous mode (BCR[15] = 0), CE# must remain HIGH for at least
5ns (
t
CPH) to schedule the appropriate internal refresh operation. Otherwise,
t
CPH is only
required after CE#-controlled WRITEs.
A[19:0]
VIH
VIL
ADV#
VIH
VIL
OE#
WE#
WAIT
DQ[15:0]
IN/OUT
VOH
VOL
VIH
VIL
VOH
VOL
CE#
LB#/UB#
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
t
CW
t
WPH
t
WP
t
WC
t
DH
t
DW
t
HZ
DATA
t
HZ
High-Z
VALID ADDRESS
t
AA
t
BHZ
t
CPH
1 t
CO
VALID
OUTPUT
High-Z
t
OE
t
OLZ
t
LZ
t
BLZ
t
OHZ
t
HZ
t
AW
t
WR
t
BW
DONT CARE UNDEFINED
DATA
Timing Diagrams
Figure 46: Asynchronous WRITE Followed by Asynchronous READ
Notes: 1. When configured for synchronous mode (BCR[15] = 0), CE# must remain HIGH for at least
5ns (
t
CPH) to schedule the appropriate internal refresh operation. Otherwise,
t
CPH is only
required after CE#-controlled WRITEs.
t
AVS
t
AVH
t
VPH
t
VP
t
VS
A[19:0]
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
VIH
VIL
ADV#
OE#
WE#
WAIT
DQ[15:0]
IN/OUT
VOH
VOL
VIH
VIL
VOH
VOL
CE#
LB#/UB#
t
VP
t
AVH
t
CW
t
WPH
t
AS
t
WP
t
WC
t
DH
t
DW
DATA DATA
High-Z
VALID ADDRESS
t
AA
t
BHZ
t
AADV
t
CPH
1
t
CO
VALID
OUTPUT
High-Z
t
CVS
t
OLZ
t
LZ
t
AS
t
BLZ
t
OHZ
t
HZ
t
AW
t
WR
t
BW
UNDEFINED DONT CARE
t
OE
t
AVS
t
CVS
8000 S. Federal Way, P.O. Box 6, Boise, ID 83707-0006, Tel: 208-368-3900

[email protected] www.micron.com Customer Comment Line: 800-932-4992
Micron, the M logo, and the Micron logo are trademarks of Micron Technology, Inc. CellularRAM is a trademark of Micron Technology, Inc.
inside the U.S. and a trademark of Qimonda AG outside the U.S. All other trademarks are the property of their respective owners. This data
sheet contains minimum and maximum limits specified over the complete power supply and temperature range for production devices.
Although considered final, these specifications are subject to change, as further product development and data characterization some-
times occur.
Package Dimensions
Package Dimensions
Figure 47: 54-Ball VFBGA

Notes: 1. All dimensions in millimeters; MAX/MIN or typical, as noted.
2. Package width and length do not include mold protrusion; allowable mold protrusion is
0.25mm per side.
3. The MT45W1MW16BDGB uses green packaging.
BALL A1 ID
0.70 0.05
SEATING
PLANE
0.10 A
A
1.00 MAX
BALL A6
BALL A1
BALL A1 ID
0.75
TYP
0.75 TYP
1.875
3.75
6.00 0.10
3.00 0.05
DIMENSIONS APPLY
TO SOLDER BALLS
POST REFLOW.
PRE-REFLOW BALL
DIAMETER IS 0.35
ON A 0.30 SMD
BALL PAD.
54X 0.37
SOLDER BALL MATERIAL:
96.5% Sn, 3% Ag, 0.5% Cu
MOLD COMPOUND:
EPOXY NOVOLAC
SUBSTRATE MATERIAL:
PLASTIC LAMINATE
6.00
3.00
4.00 0.05
8.00 0.10
Revision History
Revision History
Rev. H, Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .04/08
Updated the MAX I/O voltage from 3.3V to 3.6V.
Updated Figure 15 on page 21 and Figure 16 on page 22 to include the 0ns MIN spec.
Changed
t
PU in Table 16 on page 36 from a MIN to a MAX value.
Updated Figure 42 on page 52 to include the correct drawing.
Rev. G, Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11/07
Table 15, Burst WRITE Cycle Timing Requirements, on page 36: Corrected
t
CEM
parameter label from minimum to maximum.
Rev. F, Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11/06
Updated Rev. letter to F
Rev. F, Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .06/06
Changed the title of Figure 10 to Wired-OR Wait Configuration
Updated wording in the third paragraph of WAIT Operation on page 15 to the
following: During a Burst cycle, CE# must remain asserted until the first data is valid.
Bringing CE# HIGH during this initial latency may cause data corruption.
Changed WAIT from
t
CW to
t
CEW in Figure 14
Changed Min/Max columns from -701 and -708, to 104 MHz and 80 MHz in
Table 5
Changed Output enable to Low-Z output MIN value from 5 to 3 in Table 12
Changed Min/Max columns from -70 to 70ns in Table 12
Removed CLK to DQ High-Z Output and CLK to Low-Z Output rows from Table 13
Changed Output enable to Low-Z output MIN value from 5 to 3 in Table 13
Table 13
Table 15
Removed
t
WHZ lines and arrows in Figure 42
Removed
t
Removed
t
Rev. E, Production. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .02/06
Changed document status to Production.
Rev. D, Preliminary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .01/06
Changed VIH and VIL to VOH and VOL in Figure 27, 28, 29, 34, 35, 36, 37
Updated Continuous burst READ and Standby specifications in Features section
Updated document designator to Preliminary
Deleted Tables 1743.
Rev. C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12/05
Deleted 4-Word Burst READ Operation (with LB#/UB#) timing diagram
Changed file name to new standard: p23z16_b_cr1-0 to 16mb_burst_cr1_0_p23z
Rev. B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10/05
Fixed exceptions to template (primarily minor formatting on page 1)
Revision History
Page 1, Figure 1: changed E3 ball color to white
Page 1: changed multiple - to for negative numbers (per style)
Eliminated holdover references to dual parts (pgs. 10 and 30)
Updated to state that CLK must be held static LOW or HIGH during async READ and
WRITE (pgs. 7, 10, 11, 14)
Updated note 4 in Table 8 to eliminate reference to dual part (was BCR[5:4] = 00b)
Rev. A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .08/05
Initial release with Advance designation.

16mb Burst cr1 0 p23z PDF

Uploaded by

Copyright:

Available Formats

16mb Burst cr1 0 p23z PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

16mb Burst cr1 0 p23z PDF

Uploaded by

Copyright:

Available Formats

Products and specifications discussed herein are subject to change by Micron without notice.

16Mb: 1 Meg x 16 Async/Page/Burst CellularRAM 1.0 Memory

CellularRAM is a high-speed, CMOS PSRAM memory device developed for

8000 S. Federal Way, P.O. Box 6, Boise, ID 83707-0006, Tel: 208-368-3900

You might also like