MBM29QM96DF80PBT_技术文档

MBM29QM96DF-65/80

Data Sheet

July 2003

The following document specifies Spansion memory products that are now offered by both Advanced Micro Devices

and Fujitsu. Although the document is marked with the name of the company that originally developed the specifi-

cation, these products will be offered to customers of both AMD and Fujitsu.

Continuity of Specifications

There is no change to this datasheet as a result of offering the device as a Spansion product. Any changes that

have been made are the result of normal datasheet improvement and are noted in the document revision summary,

where supported. Future routine revisions will occur when appropriate, and changes will be noted in a revision sum-

mary.

Continuity of Ordering Part Numbers

AMD and Fujitsu continue to support existing part numbers beginning with “Am” and “MBM”. To order these prod-

ucts, please use only the Ordering Part Numbers listed in this document.

For More Information

Please contact your local AMD or Fujitsu sales office for additional information about Spansion memory solutions.

Publication Number 26829 Revision A Amendment 0 Issue Date October 25, 2002

FUJITSU SEMICONDUCTOR

DATA SHEET

DS05-20900-1E

PAGE MODE FLASH MEMORY

CMOS

96M (6M × 16) BIT

MBM29QM96DF-65/80

■ GENERAL DESCRIPTION

The MBM29QM96DF is 96M-bit, 3.0 V-only Page mode and dual operation Flash memory organized as 6M words

by 16 bits. The device is offered in a 80-ball FBGA package. This device is designed to be programmed in-system

with the standard system 3.0 V Vcc supply. 12.0 V Vpp and 5.0 V Vcc are not required for program or erase

operations. The device can also be reprogrammed in standard EPROM programmers.

(Continued)

■ PRODUCT LINEUP

Part No.

Ordering Part Number Suffix

V^CC(V)

MBM29QM96DF

65

2.7 to 3.1

VCC

80

2.7 to 3.1

1.65 to VCC

80

VCCQ (V)

Max Random Address Access Time (ns)

Max Page Address Access Time (ns)

Max CE Access Time (ns)

Max OE Access Time (ns)

65

25

30

65

80

25

30

■ PACKAGE

80-ball plastic FBGA

(BGA-80P-M03)

MBM29QM96DF-65/80

(Continued)

The device provides truly high performance non-volatile Flash memory solution. The device offers fast page

access times of 25 ns with random access times of 65 ns , allowing operation of high-speed microprocessors

without wait states. To eliminate bus contention the device has separate chip enable (CE), write enable (WE),

and output enable (OE) controls. The page size is 8 words.

The dual operation function provides simultaneous operation by dividing the memory space into four banks. The

device can improve overall system performance by allowing a host system to program or erase in one bank,

then immediately and simultaneously read from the other bank with zero latency. This releases the system from

waiting for the completion of program or erase operations.

The device is command set compatible with JEDEC standard E²PROMs. Commands are written to the command

register using standard microprocessor write timings. Register contents serve as input to an internal state-

machine which controls the erase and programming circuitry. Write cycles also internally latch addresses and

data needed for the program and erase operations. Reading data out of the device is similar to reading from 5.0

V and 12.0 V Flash or EPROM devices.

The device is programmed by executing the program command sequence. This will invoke the Embedded

Program Algorithm^TMwhich is an internal algorithm that automatically times the program pulse widths and verifies

proper cell margins. Typically, each 32K words sector can be programmed and verified in about 0.3 seconds.

Erase is accomplished by executing the erase command sequence. This will invoke the Embedded Erase

Algorithm^TMwhich is an internal algorithm that automatically preprograms the array if it is not already programmed

before executing the erase operation. During erase, the device automatically times the erase pulse widths and

verifies proper cell margins.

Any individual sector is typically erased and verified in 0.5 second. (If already preprogrammed.)

The device also features a sector erase architecture. The sector mode allows each sector to be erased and

reprogrammed without affecting other sectors. The device is erased when shipped from the factory.

The Enhanced V^I/O(VCCQ) feature allows the output voltage generated on the device to be determined based on

the VI/O level. This feature allows this device to operate in the 1.8 V I/O environment, driving and receiving signals

to and from other 1.8 V devices on the same bus.

The device features single 3.0 V power supply operation for both read and write functions. Internally generated

and regulated voltages are provided for the program and erase operations. A low VCC detector automatically

inhibits program and erase operations on the loss of power. The end of program or erase is detected by Data

Polling of DQ7, by the Toggle Bit feature on DQ6, output pin. Once the end of a program or erase cycle has been

completed, the device internally resets to the read mode.

Fujitsu’s Flash technology combines years of Flash memory manufacturing experience to produce the highest

levels of quality, reliability, and cost effectiveness. The device memory electrically erases all bits within a sector

simultaneously via Fowler-Nordhiem tunneling. The words are programmed one word at a time using the EPROM

programming mechanism of hot electron injection.

2

MBM29QM96DF-65/80

■ FEATURES

• 0.17 µm Process Technology

• Single 3.0 V Read, Program and Erase

Minimized system level power requirements

• Simultaneous Read/Write (Program and Erase) Operations (Dual Bank)

• FlexBank^TM*¹

Bank A: 12 Mbit (4K words × 8 and 32K words × 23)

Bank B: 36 Mbit (32K words × 72)

Bank C: 36 Mbit (32K words × 72)

Bank D: 12 Mbit (4K words × 8 and 32K words × 23)

• Enhanced V^I/O(V^CCQ) Feature

Input/Output voltage generated on the device is determined based on the V^I/Olevel

• High Performance Page Mode

25 ns maximum page access time (65 ns random access time)

• 8 Words Page Size

• Compatible with JEDEC-Standard Commands

Uses same software commands as E²PROMs

• Minimum 100,000 Program/Erase Cycles

• Sector Erase Architecture

Eight 4K words, a hundred ninety 32K words, eight 4K words sectors

Any combination of sectors can be concurrently erased. Also supports full chip erase

• Dual Boot Block

16 by 4K words bootblock sectors, 8 at the top of the address range and 8 at the bottom of the address range

• HiddenROM Region

256 byte of HiddenROM, accessible through a new “HiddenROM Enable” command sequence

Factory serialized and protected to provide a secure electronic serial number (ESN)

• WP/ACC Input Pin

At V^IL, allows protection of “outermost” 2 × 4K words on both ends of boot sectors, regardless of sector

protection/unprotection status

At V^IH, allows removal of boot sector protection

At VACC, increases program performance

• Embedded Erase^TM*²Algorithms

Automatically preprograms and erases the chip or any sector

• Embedded Program^TM*²Algorithms

Automatically programs and verifies data at specified address

• Data Polling and Toggle Bit Feature for detection of program or erase cycle completion

• Ready/Busy Output (RY/BY)

Hardware method for detection of program or erase cycle completion

• Automatic Sleep Mode

When addresses remain stable, the device automatically switches itself to low power mode.

• Low V^CCWrite Inhibit ≤ V^LKO

• Program Suspend/Resume

Suspends the program operation to allow a read in another word

• Erase Suspend/Resume

Suspends the erase operation to allow a read data and/or program in another sector within the same device

(Continued)

*1 : FlexBank^TMis a trademark of Fujitsu Limited.

*2 : Embedded Erase^TMand Embedded Program^TMare trademarks of Advanced Micro Devices, Inc.

3

MBM29QM96DF-65/80

(Continued)

• In accordance with CFI (Common Flash Memory Interface)

• Hardware Reset Pin (RESET)

Hardware method to reset the device for reading array data

• New Sector Protection

Persistent Sector Protection

Password Sector Protection

4

MBM29QM96DF-65/80

■ PIN ASSIGNMENT

FBGA

(TOP VIEW)

(Marking Side)

A8

B8

L8

N.C. N.C.

L7 M7

N.C. N.C.

M8

C8

D8

E8

F8

G8

H8

J8

K8

A22

N.C. VCCQ VSSQ N.C. N.C.

N.C. N.C.

A7 B7

N.C. N.C.

N.C.

C7

D7

E7

F7

G7

H7

J7

K7

A13

A12

A14

A15

A16

DQ15 VSS

N.C.

C6

A9

D6

A8

E6

F6

G6

H6

J6

K6

A10

A11

DQ7

DQ14 DQ13 DQ6

C5

D5

E5

F5

G5

H5

J5

K5

WE RESET A21

C4 D4 E4

RY/BYWP/ACC A18

A19

DQ5 DQ12

VCC

DQ4

F4

G4 H4

J4

K4

A20

DQ2 DQ10 DQ11 DQ3

C3

A7

D3

E3

A6

F3

A5

G3

H3

J3

K3

A17

DQ0

DQ8

DQ9

DQ1

A2

N.C. N.C.

A1 B1

B2

C2

A3

D2

A4

E2

A2

F2

A1

G2

A0

H2

CE

J2

K2

L2

N.C. N.C.

L1 M1

N.C. N.C.

M2

OE

VSS

C1

D1

E1

F1

G1

H1

J1

K1

N.C. N.C. N.C.

VCC

N.C.

N.C. VCCQ VSSQ N.C.

N.C.

(BGA-80P-M03)

■ PIN DESCRIPTIONS

MBM29QM96DF Pin Configuration

Function

A²²to A0

DQ15 to DQ0

CE

Address Inputs

Data Inputs/Outputs

Chip Enable

OE

Output Enable

Write Enable

WE

RESET

WP/ACC

RY/BY

N.C.

Hardware Reset

Hardware Write Protection/Program Acceleration

Ready/Busy Output

Pin Not Connected Internally

Device Ground

V^SS

VCC

Device Power Supply

V^SSQ

Output Buffer Ground

V^CCQ

Output Buffer Power Supply

5

MBM29QM96DF-65/80

■ BLOCK DIAGRAM

VCC

VSS

VCCQ

VSSQ

Bank A

address

Cell Matrix

12 Mbit

Cell Matrix

36 Mbit

A22 to A0

(Bank A)

(Bank B)

X-Decoder

Bank B Address

State

Control

&

Command

Register

RESET

RY/BY

WE

CE

OE

DQ15

to

DQ0

Status

Control

WP/ACC

DQ15 to DQ0

Bank C Address

X-Decoder

Cell Matrix

12 Mbit

Cell Matrix

36 Mbit

(Bank D)

(Bank C)

Bank D

address

■ LOGIC SYMBOL

23

A22 to A0

16

DQ15 to DQ0

RESET

CE

OE

WE

RY/BY

WP/ACC

6

MBM29QM96DF-65/80

■ DEVICE BUS OPERATION

MBM29QM96DF User Bus Operations Table

DQ¹⁵to

DQ⁰

WP/

ACC

Operation

CE OE WE

A⁰

A¹

A²

A³

A⁴

A⁵

A⁶

A⁹

RESET

Autoselect Manufacturer

Code *¹

L

H

X

L

X

L

VID

Code

H

Autoselect Device Code *¹

L

H

L

H

X

H

L

X

H

L

H

A1

X

L

H

A2

X

L

H

A3

X

L

VID

V^ID

A9

X

Code

DOUT

H

Extended Autoselect Device

Code *¹

L

H

A0

X

L

Read *³

L

A4

X

A5

X

A6

X

Standby

X

H

High-Z

DIN

Output Disable

Write (Program/Erase)

X

A⁰

A1

A2

A3

A4

A5

A6

A9

Enable Sector Group

Protection *^2,*⁴

L

X

VID

L

X

H

L

X

H

X

L

X

H

X

H

X

H

X

L

X

VID

X

Code

X

H

Verify Sector Group

Protection *^2,*⁴

H

X

Boot Block Sector Write

Protection *⁵

X

Temporary Sector Group

Unprotection *⁶

X

H

X

VID

Reset

High-Z

L

Legend: L = V^IL, H = VIH, X = VIL or VIH,

= Pulse input. See "DC CHARACTERISTICS" for voltage levels.

*1 : Manufacturer and device codes may also be accessed via a command register write sequence.

See “MBM29QM96DF Command Definitions Table” in “■ DEVICE BUS OPERASTION”.

*2 : Refer to section on "Sector Group Protection".

*3 : WE can be VIL if OE is VIL, OE at VIH initiates the program and erase operations.

*4 : VCC = 2.7 V to 3.1 V.

*5 : Protects “outermost” 2x 4K words on both end of the boot block sectors. (SA0, SA1, SA204, and SA205)

*6 : Also used for "Extended Sector Group Protection".

7

MBM29QM96DF-65/80

MBM29QM96DF Command Definitions Table

Fourth

Bus

Read/

Write

Cycle

Second

Bus

Write

Cycle

Seventh

Bus

Write

Cycle

First Bus

Write

Cycle

Third Bus

Write

Cycle

Fifth Bus Sixth Bus

Bus

Write

Cy-

Write

Cycle

Write

Cycle

Command

Sequence

cles

Req’d

Da

ta

Da

Addr.

Da

ta

Da

Addr.

Da

Addr.

ta

—

ta

—

ta

Read/Reset *¹

2

4

F0h RA RD

2AAh

—

XXXh

555h AAh

55h 555h F0h RA RD

(BA)

2AAh

Autoselect

3

55h

90h

—

555h

2AAh

Program

4

6

555h AAh

55h 555h A0h PA PD

55h 555h 80h 555h AAh

—

2AAh

Chip Erase

Sector Erase

55h 555h 10h

55h SA 30h

Program/Erase

Suspend

1

BA B0h

BA 30h

—

Program/Erase

Resume

—

2AAh

Set to Fast Mode

Fast Program *²

3

2

555h AAh

XXXh

55h 555h 20h

—

A0h PA PD

F0h

—

Reset from

Fast Mode *²

XXXh

2

BA 90h

—

6

*

Extended

XXXh

Sector Group

Protection*³

4

60h SGA 60h SGA 40h SGA SD

—

(BA)

55h

Query *⁴

1

3

4

98h

—

HiddenROM En-

try

2AAh

555h AAh

55h 555h 88h

HiddenROM

Program *⁵

(HRA)

PA

55h 555h A0h

(HR-

PD

HiddenROM

Exit *⁵

2AAh

BA)

555h

XXXh

4

6

555h AAh

55h

90h

00h

—

HiddenROM

Protect *⁵

RD

(0)

555h AAh 2AAh 55h 555h 60h OPBP 68h OPBP 48h XXXh

XX0h PD0

—

PD1

PD2

PD3

XX1h

XX2h

XX3h

Password

Program *⁷

4

555h AAh 2AAh 55h 555h 38h

Password

Unlock

2AAh 55h 555h 28h XX0h PD0 XX1h PD1 XX2h PD2 XX3h PD3

7

4

555h AAh

PWD

Password Verify

555h AAh 2AAh 55h 555h C8h PWA

—

(Continued)

8

MBM29QM96DF-65/80

(Continued)

Fourth

Bus

Read/

Write

Cycle

Second

Bus

Write

Cycle

Seventh

Bus

Write

Cycle

Bus

Write

Cy-

cles

Req’d

First Bus

Write

Cycle

Third Bus

Write

Cycle

Fifth Bus Sixth Bus

Write

Cycle

Write

Cycle

Command

Sequence

Addr. Data

Addr. Data Addr. Data Addr. Data Addr. Data Addr. Data Addr. Data

Password Mode

Locking Bit

Program

RD

(0)

2AAh

6

555h AAh

55h 555h 60h PL 68h PL 48h XXh

—

Persistent

Protection Mode

Locking Bit

Program

RD

(0)

SPML

555h AAh

55h 555h 60h

68h

48h XXh

SA+

WP

SA+

WP

RD

(0)

2AAh

PPB Program

PPB Verify

6

4

555h AAh

55h 555h 60h

55h 555h 90h

—

SA+ RD

x02 (0)

—

SA+

60h

WP

SA+

WP

RD

(0)

All PPB Erase *⁸

PPB Lock Bit Set

6

3

4

555h AAh

40h XXh

—

2AAh 55h 555h 60h

2AAh 55h 555h 78h

—

PPB Lock Bit

Verify

RD

(1)

555h AAh 2AAh 55h 555h 58h SA

—

2AAh 55h 555h 48h SA X1h

555h AAh

—

DPB Write

DPB Erase

4

555h AAh 2AAh 55h 555h 48h SA X0h

RD

2AAh 55h 555h 58h SA

555h AAh

—

DPB Verify

4

(0)

Legend:

RA

PA

= Address of the memory location to be read

= Address of the memory location to be programmed

Addresses are latched on the falling edge of the write pulse.

= Address of the sector

SA

BA

= Bank Address

RD

PD

SGA

= Data read from location RA during read operation.

= Data to be programmed at location PA. Data is latched on the rising edge of write pulse.

= Sector group address to be protected. Set sector group address and (A⁶, A5, A4, A3, A2, A1, A0) =

(0, 1, 1, 1, 0, 1, 0)

SD

= Sector group protection verify data. Output 01h at protected sector group addresses and output

00h at unprotected sector group addresses.

HRA

= Address of the HiddenROM area (000000h to 00007Fh)

HRBA

RD (0)

= Bank Address of the HiddenROM area (A²²= A21 = A20 = A19 = A18 = VIL)

= DQ0 data, RD (1) = DQ1 data. PPB Lock bit is read on DQ1 and PPB or DPB are read on DQ0.

If set, DQ0/DQ1 = 1. If cleared, DQ0/DQ1 = 0.

OPBP

SLA

= (A⁶, A5, A4, A3, A2, A1, A0) is (X, 0, 1, 1, 0, 1, 0)

= Address of the sector to be locked. Set sector address (SA) and either A6 = 1 for unlocked or A6 = 0

for locked

PWA/PWD = Password Address/Password Data

PL

SPML

WP

= (A⁶, A5, A4, A3, A2, A1, A0) is (X, 0, 0, 1, 0, 1, 0)

= (A6, A5, A4, A3, A2, A1, A0) is (X, 0, 1, 0, 0, 1, 0)

= (A6, A5, A4, A3, A2, A1, A0) is (X, 1, 1, 1, 0, 1, 0)

9

MBM29QM96DF-65/80

*1 : Both of these reset commands are equivalent.

*2 : This command is valid during Fast Mode.

*3 : This command is valid while RESET = VID.

*4 : The valid addresses are A⁶to A0.

*5 : This command is valid during HiddenROM mode.

*6 : The data “00h” is also acceptable.

*7 : Data before fourth cycle also need to be programmed repearting from first cycle to third cycle.

*8 : RD(0) of the sixth cycle shows PPB erase status. When RD(0) is "1", programming must be repeated

from the beginning of first cycle to the fourth cycle; both fifth and the sixth validate full completion of erase.

Notes : • Address bits A²²to A11 = X = “H” or “L” for all address commands except for

PA, SA, BA, SGA, OPBP, SLA, PWA, PL, SPML, WP.

• Bus operations are defined in “MBM29QM96DF User Bus Operation Table” in “■ DEVICE BUS

OPERASTION”.

• The system should generate the following address patterns:

555h or 2AAh to addresses A¹⁰to A0

• Both Read/Reset commands are functionally equivalent, resetting the device to the read mode.

• Command combinations not described in Command Definitions table are illegal.

10

MBM29QM96DF-65/80

MBM29QM96DF Autoselect Codes

Type

Manufacture’s Code

Device Code

A²²to A¹²

BA*²

A⁶

VIL

A⁵

x

A⁴

x

A³

VIL

VIH

A²

VIL

VIH

A¹

VIL

VIH

A⁰

VIL

VIH

VIL

VIH

Code (HEX)

04h

BA*²

x

227Eh

2217h

BA*²

x

Extended Device Code*³

BA*²

x

2201h

Sector

Group

Sector Group Protection*¹

VIL

VIH

VIL

VIH

VIL

01h*¹

Addresses

*1 : Sector Group can be protected by "Sector Group Protection", "Extended Sector Group Protection" and " New

Sector Protection(PPB Protection)". Outputs 01h at protected sector group addresses and outputs 00h at

unprotected sector group addresses.

*2 : When V^IDis applied to A9, both Bank 1 and Bank 2 are put into Autoselect mode, which makes simtaneous

operation unable to be executed. Consequently, specifying the bank address is not required. However, the

bank address needs to be indicated when Autoselect mode is read out at command mode, because then it

enables to activate simultaneous operation.

*3 : A read cycle at address (BA) 01h outputs device code. When 227Eh is output, it indicates that two additional

codes, called Extended Device Codes, will be required. Therefore the system may continue reading out these

Extended Device Codes at the address of (BA) 0Eh, as well as at (BA) 0Fh

Exteneded Auteselect Code Table

Type

Code DQ¹⁵DQ¹⁴DQ¹³DQ¹²DQ¹¹DQ¹⁰DQ⁹DQ⁸DQ⁷DQ⁶DQ⁵DQ⁴DQ³DQ²DQ¹DQ⁰

Manufacturer’s

Code

04h

0

1

0

Device Code

227Eh

2217h

2201h

01h

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

Extended Device

Code

PPB Protection

PPB Unprotection

00h

11

MBM29QM96DF-65/80

■ FLEXIBLE SECTOR-ERASE ARCHITECTURE

Sector Address Table (Bank A)

Sector Address

Bank Address

A²²A²¹A²⁰A¹⁹A¹⁸A¹⁷A¹⁶A¹⁵A¹⁴A¹³A¹²

Sector Size

(Kwords)

Bank

Sector

Address Range

SA0

SA1

SA2

SA3

SA4

SA5

SA6

SA7

SA8

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

4

000000h to 000FFFh

001000h to 001FFFh

002000h to 002FFFh

003000h to 003FFFh

004000h to 004FFFh

005000h to 005FFFh

006000h to 006FFFh

007000h to 007FFFh

008000h to 00FFFFh

010000h to 017FFFh

018000h to 01FFFFh

020000h to 027FFFh

028000h to 02FFFFh

030000h to 037FFFh

038000h to 03FFFFh

040000h to 047FFFh

048000h to 04FFFFh

050000h to 057FFFh

058000h to 05FFFFh

060000h to 067FFFh

068000h to 06FFFFh

070000h to 077FFFh

078000h to 07FFFFh

080000h to 087FFFh

088000h to 08FFFFh

090000h to 097FFFh

098000h to 09FFFFh

0A0000h to 0A7FFFh

0A8000h to 0AFFFFh

0B0000h to 0B7FFFh

0B8000h to 0BFFFFh

X

32

SA9

SA10

SA11

SA12

SA13

SA14

SA15

SA16

SA17

SA18

SA19

SA20

SA21

SA22

SA23

SA24

SA25

SA26

SA27

SA28

SA29

SA30

Bank A

12

MBM29QM96DF-65/80

Sector Address Table (Bank B)

Sector Address

Bank Address

A²²A²¹A²⁰A¹⁹A¹⁸A¹⁷A¹⁶A¹⁵A¹⁴A¹³A¹²

Sector Size

(Kwords)

Bank

Sector

Address Range

SA31

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

SA64

SA65

SA66

SA67

SA68

SA69

SA70

SA71

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

X

32

0C0000h to 0C7FFFh

0C8000h to 0CFFFFh

0D0000h to 0D7FFFh

0D8000h to 0DFFFFh

0E0000h to 0E7FFFh

0E8000h to 0EFFFFh

0F0000h to 0F7FFFh

0F8000h to 0FFFFFh

100000h to 107FFFh

108000h to 10FFFFh

110000h to 117FFFh

118000h to 11FFFFh

120000h to 127FFFh

128000h to 12FFFFh

130000h to 137FFFh

138000h to 13FFFFh

140000h to 147FFFh

148000h to 14FFFFh

150000h to 157FFFh

158000h to 15FFFFh

160000h to 167FFFh

168000h to 16FFFFh

170000h to 177FFFh

178000h to 17FFFFh

180000h to 187FFFh

188000h to 18FFFFh

190000h to 197FFFh

198000h to 19FFFFh

1A0000h to 1A7FFFh

1A8000h to 1AFFFFh

1B0000h to 1B7FFFh

1B8000h to 1BFFFFh

1C0000h to 1C7FFFh

1C8000h to 1CFFFFh

1D0000h to 1D7FFFh

1D8000h to 1DFFFFh

1E0000h to 1E7FFFh

1E8000h to 1EFFFFh

1F0000h to 1F7FFFh

1F8000h to 1FFFFFh

200000h to 207FFFh

(Continued)

Bank B

13

MBM29QM96DF-65/80

(Continued)

Sector Address

Bank Address

A²²A²¹A²⁰A¹⁹A¹⁸A¹⁷A¹⁶A¹⁵A¹⁴A¹³A¹²

Sector Size

(Kwords)

Bank

Sector

Address Range

SA72

SA73

SA74

SA75

SA76

SA77

SA78

SA79

SA80

SA81

SA82

SA83

SA84

SA85

SA86

SA87

SA88

SA89

SA90

SA91

SA92

SA93

SA94

SA95

SA96

SA97

SA98

SA99

SA100

SA101

SA102

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

X

32

208000h to 20FFFFh

210000h to 217FFFh

218000h to 21FFFFh

220000h to 227FFFh

228000h to 22FFFFh

230000h to 237FFFh

238000h to 23FFFFh

240000h to 247FFFh

248000h to 24FFFFh

250000h to 257FFFh

258000h to 25FFFFh

260000h to 267FFFh

268000h to 26FFFFh

270000h to 277FFFh

278000h to 27FFFFh

280000h to 287FFFh

288000h to 28FFFFh

290000h to 297FFFh

298000h to 29FFFFh

2A0000h to 2A7FFFh

2A8000h to 2AFFFFh

2B0000h to 2B7FFFh

2B8000h to 2BFFFFh

2C0000h to 2C7FFFh

2C8000h to 2CFFFFh

2D0000h to 2D7FFFh

2D8000h to 2DFFFFh

2E0000h to 2E7FFFh

2E8000h to 2EFFFFh

2F0000h to 2F7FFFh

2F8000h to 2FFFFFh

Bank B

14

MBM29QM96DF-65/80

Sector Address Table (Bank C)

Sector Address

Bank Address

A²²A²¹A²⁰A¹⁹A¹⁸A¹⁷A¹⁶A¹⁵A¹⁴A¹³A¹²

Sector Size

(Kwords)

Bank

Sector

Address Range

SA103

SA104

SA105

SA106

SA107

SA108

SA109

SA110

SA111

SA112

SA113

SA114

SA115

SA116

SA117

SA118

SA119

SA120

SA121

SA122

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

X

32

300000h to 307FFFh

308000h to 30FFFFh

310000h to 317FFFh

318000h to 31FFFFh

320000h to 327FFFh

328000h to 32FFFFh

330000h to 337FFFh

338000h to 33FFFFh

340000h to 347FFFh

348000h to 34FFFFh

350000h to 357FFFh

358000h to 35FFFFh

360000h to 367FFFh

368000h to 36FFFFh

370000h to 377FFFh

378000h to 37FFFFh

380000h to 387FFFh

388000h to 38FFFFh

390000h to 397FFFh

398000h to 39FFFFh

3A0000h to 3A7FFFh

3A8000h to 3AFFFFh

3B0000h to 3B7FFFh

3B8000h to 3BFFFFh

3C0000h to 3C7FFFh

3C8000h to 3CFFFFh

3D0000h to 3D7FFFh

3D8000h to 3DFFFFh

3E0000h to 3E7FFFh

3E8000h to 3EFFFFh

3F0000h to 3F7FFFh

3F8000h to 3FFFFFh

400000h to 407FFFh

408000h to 40FFFFh

410000h to 417FFFh

418000h to 41FFFFh

420000h to 427FFFh

428000h to 42FFFFh

430000h to 437FFFh

438000h to 43FFFFh

440000h to 447FFFh

(Continued)

Bank C SA123

SA124

SA125

SA126

SA127

SA128

SA129

SA130

SA131

SA132

SA133

SA134

SA135

SA136

SA137

SA138

SA139

SA140

SA141

SA142

SA143

15

MBM29QM96DF-65/80

(Continued)

Sector Address

Bank Address

A²²A²¹A²⁰A¹⁹A¹⁸A¹⁷A¹⁶A¹⁵A¹⁴A¹³A¹²

Sector Size

(Kwords)

Bank

Sector

Address Range

SA144

SA145

SA146

SA147

SA148

SA149

SA150

SA151

SA152

SA153

SA154

SA155

SA156

SA157

SA158

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

X

32

448000h to 44FFFFh

450000h to 457FFFh

458000h to 45FFFFh

460000h to 467FFFh

468000h to 46FFFFh

470000h to 477FFFh

478000h to 47FFFFh

480000h to 487FFFh

488000h to 48FFFFh

490000h to 497FFFh

498000h to 49FFFFh

4A0000h to 4A7FFFh

4A8000h to 4AFFFFh

4B0000h to 4B7FFFh

4B8000h to 4BFFFFh

4C0000h to 4C7FFFh

4C8000h to 4CFFFFh

4D0000h to 4D7FFFh

4D8000h to 4DFFFFh

4E0000h to 4E7FFFh

4E8000h to 4EFFFFh

4F0000h to 4F7FFFh

4F8000h to 4FFFFFh

500000h to 507FFFh

508000h to 50FFFFh

510000h to 517FFFh

518000h to 51FFFFh

520000h to 527FFFh

528000h to 52FFFFh

530000h to 537FFFh

538000h to 53FFFFh

Bank C SA159

SA160

SA161

SA162

SA163

SA164

SA165

SA166

SA167

SA168

SA169

SA170

SA171

SA172

SA173

SA174

16

MBM29QM96DF-65/80

Sector Address Table (Bank D)

Sector Address

Bank Address

A²²A²¹A²⁰A¹⁹A¹⁸A¹⁷A¹⁶A¹⁵A¹⁴A¹³A¹²

Sector Size

(Kwords)

Bank

Sector

Address Range

SA175

SA176

SA177

SA178

SA179

SA180

SA181

SA182

SA183

SA184

SA185

SA186

SA187

SA188

SA189

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

X

0

X

0

X

0

32

4

540000h to 547FFFh

548000h to 54FFFFh

550000h to 557FFFh

558000h to 55FFFFh

560000h to 567FFFh

568000h to 56FFFFh

570000h to 577FFFh

578000h to 57FFFFh

580000h to 587FFFh

588000h to 58FFFFh

590000h to 597FFFh

598000h to 59FFFFh

5A0000h to 5A7FFFh

5A8000h to 5AFFFFh

5B0000h to 5B7FFFh

5B8000h to 5BFFFFh

5C0000h to 5C7FFFh

5C8000h to 5CFFFFh

6D0000h to 5D7FFFh

6D8000h to 5DFFFFh

5E0000h to 5E7FFFh

5E8000h to 5EFFFFh

5F0000h to 5F7FFFh

5F8000h to 5F8FFFh

5F9000h to 5F9FFFh

5FA000h to 5FAFFFh

5FB000h to 5FBFFFh

5FC000h to 5FCFFFh

5FD000h to 5FDFFFh

5FE000h to 5FEFFFh

5FF000h to 5FFFFFh

Bank D SA190

SA191

SA192

SA193

SA194

SA195

SA196

SA197

SA198

SA199

SA200

SA201

SA202

SA203

SA204

SA205

0

1

0

1

0

1

0

1

0

1

0

1

4

17

MBM29QM96DF-65/80

Sector Group Address Table

Sector Group

SGA0

A²²

0

A²¹

0

A²⁰

0

A¹⁹

0

A¹⁸

0

A¹⁷

0

A¹⁶

0

A¹⁵

0

A¹⁴

0

A¹³

0

A¹²

0

Sectors

SA0

SGA1

0

1

SA1

SGA2

0

1

0

SA2

SGA3

0

1

SA3

SGA4

0

1

0

SA4

SGA5

0

1

0

1

SA5

SGA6

0

1

0

SA6

SGA7

0

1

SA7

0

1

SGA8

0

1

0

X

SA8 to SA10

1

SGA9

SGA10

SGA11

SGA12

SGA13

SGA14

SGA15

SGA16

SGA17

SGA18

SGA19

SGA20

SGA21

SGA22

SGA23

SGA24

SGA25

SGA26

SGA27

SGA28

SGA29

SGA30

SGA31

SGA32

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

X

SA11 to SA14

SA15 to SA18

SA19 to SA22

SA23 to SA26

SA27 to SA30

SA31 to SA34

SA35 to SA38

SA39 to SA42

SA43 to SA46

SA47 to SA50

SA51 to SA54

SA55 to SA58

SA59 to SA62

SA63 to SA66

SA67 to SA70

SA71 to SA74

SA75 to SA78

SA79 to SA82

SA83 to SA86

SA87 to SA90

SA91 to SA94

SA95 to SA98

SA99 to SA102

SA103 to SA106

(Continued)

18

MBM29QM96DF-65/80

(Continued)

Sector Group

A²²

0

1

A²¹

1

0

A²⁰

1

0

1

A¹⁹

0

1

0

1

0

1

A¹⁸

0

1

0

1

0

1

0

1

0

1

0

1

A¹⁷

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

A¹⁶

X

0

A¹⁵

X

0

A¹⁴

X

A¹³

X

A¹²

X

Sectors

SGA33

SGA34

SGA35

SGA36

SGA37

SGA38

SGA39

SGA40

SGA41

SGA42

SGA43

SGA44

SGA45

SGA46

SGA47

SGA48

SGA49

SGA50

SGA51

SGA52

SGA53

SGA54

SA107 to SA110

SA111 to SA114

SA115 to SA118

SA119 to SA122

SA123 to SA126

SA127 to SA130

SA131 to SA134

SA135 to SA138

SA139 to SA142

SA143 to SA146

SA147 to SA150

SA151 to SA154

SA155 to SA158

SA159 to SA162

SA163 to SA166

SA167 to SA170

SA171 to SA174

SA175 to SA178

SA179 to SA182

SA183 to SA186

SA187 to SA190

SA191 to SA194

SGA55

1

0

1

0

1

X

SA195 to SA197

1

0

SGA56

SGA57

SGA58

SGA59

SGA60

SGA61

SGA62

SGA63

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

SA198

SA199

SA200

SA201

SA202

SA203

SA204

SA205

1

19

MBM29QM96DF-65/80

Common Flash Memory Interface Code Table

Description

A⁶to A⁰

DQ¹⁵to DQ⁰

10h

11h

12h

0051h

0052h

0059h

Query-unique ASCII string “QRY”

Primary OEM Command Set

02h: AMD/FJ standard type

13h

14h

0002h

0000h

15h

16h

0040h

0000h

Address for Primary Extended Table

17h

18h

0000h

Alternate OEM Command Set (00h = not applicable)

Address for Alternate OEM Extended Table

19h

1Ah

0000h

V^CCMin (write/erase) DQ7 to DQ4: 1V, DQ3 to DQ0: 100 mV

V^CCMax (write/erase) DQ7 to DQ4: 1V, DQ3 to DQ0: 100 mV

V^PPMin voltage

1Bh

1Ch

1Dh

1Eh

1Fh

20h

21h

22h

23h

24h

25h

26h

27h

0027h

0031h

0000h

0004h

0000h

0009h

0000h

0005h

0000h

0004h

0000h

0018h

V^PPMax voltage

Typical timeout per single byte/word write 2^Nµs

Typical timeout for Min size buffer write 2^Nµs

Typical timeout per individual block erase 2^Nms

Typical timeout for full chip erase 2^Nms

Max timeout for byte/word write 2^Ntimes typical µs

Max timeout for buffer write 2^Ntimes typical µs

Max timeout per individual block erase 2^Ntimes typical ms

Max timeout for full chip erase 2^Ntimes typical ms

Device Size = 2^Nbyte

Flash Device Interface description

01h: x16

28h

29h

0001h

0000h

2Ah

2Bh

0000h

Max number of byte in multi-byte write = 2^N

Number of Erase Block Regions within device

2Ch

0003h

2Dh

2Eh

2Fh

30h

0007h

0000h

0020h

0000h

Erase Block Region 1 Information

Erase Block Region 2 Information

Erase Block Region 3 Information

Erase Block Region 4 Information

31h

32h

33h

34h

00BDh

0000h

0001h

35h

36h

37h

38h

00BDh

0000h

0020h

0000h

39h

3Ah

3Bh

3Ch

0000h

(Continued)

20

MBM29QM96DF-65/80

(Continued)

Description

A⁶to A⁰

DQ¹⁵to DQ⁰

40h

41h

42h

0050h

0052h

0049h

Query-unique ASCII string “PRI”

Major version number, ASCII

Minor version number, ASCII

43h

44h

0031h

0033h

Address Sensitive Unlock

04h = Required and 0.17µm technology

45h

46h

0004h

0002h

Erase Suspend

02h = To Read & Write

Sector Protection

00h = Not Supported

47h

0001h

X = Number of sectors in per group

Sector Temporary Unprotection

01h = Supported

48h

49h

0001h

0007h

Sector Protection Algorithm

Simultaneous Operation

00h = Not Supported,

4Ah

00AFh

X = Total number of sectors in all Banks except Bank A

Burst Mode Type

00h = Not Supported

4Bh

4Ch

0000h

0002h

Page Mode Type

02h = 8 Word Page

V^ACC(Acceleration) Supply Minimum

00h = Not Supported

DQ7 to DQ4: 1V, DQ3 to DQ0: 100 mV

4Dh

4Eh

0085h

0095h

V^ACC(Acceleration) Supply Maximum

00h = Not Supported

DQ7 to DQ4: 1V, DQ3 to DQ0: 100 mV

Boot Type

4Fh

50h

0001h

Program Suspend

01h = Supported

Bank Organization

X = Number of Banks

57h

0004h

Bank A Region Information

Bank B Region Information

Bank C Region Information

Bank D Region Information

58h

59h

5Ah

5Bh

001Fh

0048h

001Fh

21

MBM29QM96DF-65/80

■ FUNCTIONAL DESCRIPTION

Simultaneous Operation

The device features functions that enable data reading from one memory bank while a program or erase operation

is in progress in the other memory bank (simultaneous operation) , in addition to conventional features (read,

program, erase, erase-suspend read, and erase-suspend program) . The bank is selected by bank address (

A²², A21, A20 , A19, A18 ) with zero latency. The device consists of the following four banks :

Bank A : 8 × 4KW and 23 × 32KW; Bank B : 72 × 32 KW; Bank C : 72 × 32KW; Bank D : 8 × 4KW and 23 × 32KW.

The device can execute simultaneous operations between Bank 1, a bank chosen from among the four banks,

and Bank 2, a bank consisting of the three remaining banks. See “FlexBank^TMArchitecture Table” in “■ FUNC-

TIONAL DESCRIPTION” below. This is what we call “FlexBank”, for example the rest of banks B, C and D to let

the system read while Bank A is in the process of program (or erase) operation. However the different types of

operations for the three banks are not allowed, e.g. Bank A programming, Bank B erasing, and Bank C reading

out. With this “FlexBank”, as described in “Example of Virtual Banks Combination Table” in “■ FUNCTIONAL

DESCRIPTION”, the system gets to select from four combinations of data volume for Bank 1 and Bank 2, which

works well to meet the system requirement. The simultaneous operation cannot execute multi-function mode in

the same bank. Refer to “Bank-to-Bank Read/Write(Program and Erase) Timing Diagram” in “■ TIMING DIA-

GRAM”.

FlexBank^TMArchitecture

Bank 1

Bank 2

Combination

Bank

Splits

Bank Size

12 Mbit

36 Mbit

12 Mbit

Combination

Bank Size

84 Mbit

60 Mbit

84 Mbit

1

2

3

4

Bank A

Bank B

Bank C

Bank D

Bank B, C, D

Bank A, C, D

Bank A, B, D

Bank A, B, C

Example of Virtual Banks Combination

Bank 1

Bank Combination of

Bank 2

Bank

Bank Combination of

Sector Sizes

Splits

Size

Memory Bank

Size

Memory Bank

Bank B

+

Bank C

+

Eight 4K words,

One hundred

sixty-seven

Eight 4K words,

Twenty-three

32K words

1

2

3

4

12 Mbit

Bank A

84 Mbit

32K words

Bank D

Bank B

+

Bank C

Sixteen 4K words,

Forty-six 32K words

One hundred

forty-four 32K words

24 Mbit Bank A +Bank D

72 Mbit

60 Mbit

48 Mbit

Bank A

+

Bank C

+

Sixteen 4K words,

One hundred

eighteen

Seventy-two

32K words

36 Mbit

Bank B

32K words

Bank D

Bank C

+

Bank D

Eight 4K words,

Ninety-five 32Kwords

Eight 4K words,

Ninety-five 32Kwords

48 Mbit Bank A + Bank B

Note : When multiple sector erase over several banks is operated, the system cannot read out of the bank to which

a sector being erased belongs. For example, suppose that erasing is taking place at both Bank A and Bank B,

neither Bank A nor Bank B is read out they output the sequence flag once they are selected.

Meanwhile the system would get to read from either Bank C or Bank D.

22

MBM29QM96DF-65/80

Simultaneous Operation

Bank 1 Status

Case

Bank 2 Status

Read mode

1

2

3

4

5

6

7

Read mode

Autoselect mode

Program mode

Erase mode

Read mode

Autoselect mode

Program mode

Erase mode

Read mode

Note : Bank 1 and Bank 2 are divided for the sake of convenience at Simultaneous Operation. The Bank consists

of 4 banks, Bank A, Bank B, BankC and Bank D. Bank Address (BA) means to specify each of the Banks.

Read Mode

The device has two control functions required to obtain data at the outputs. CE is the power control and used

for a device selection. OE is the output control and used to gate data to the output pins if a device is selected.

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 stable addresses and stable CE to valid data at the output pins. The output

enable access time is the delay from the falling edge of OE to valid data at the output pins. Assuming the

addresses have been stable for at least tACC − tOE time. When reading out a data without changing addresses

after power-up, input hardware reset or to change CE pin from “H” or “L”.

Page Mode Read

The device is capable of fast Page mode read and are compatible with the Page mode Mask ROM read operation.

This mode provides faster read access speed for random locations within a page. The Page size of the device

is 8 words, within the appropriate Page being selected by the higher address bits A²²to A3 and the LSB bits A2

to A0 determining the specific word within that page. This is an asynchronous operation with the microprocessor

supplying the specific word location.

The random or initial page access is equal to t^ACCand subsequent Page read access (as long as the locations

specified by the microprocessor fall within that Page) is equivalent to tPACC. Here again, CE selects the device

and OE is the output control and used to gate data to the output pins if the device is selected. Fast Page mode

accesses are obtained by keeping A22 to A3 constant and changing A2 to A0 to select the specific word, within

that page.

Standby Mode

There are two ways to implement the standby mode on the device, one using both the CE and RESET pins, and

the other via the RESET pin only.

When using both pins, CMOS standby mode is achieved with CE and RESET input held at VCC±0.3 V. Under

this condition the current consumed is less than 5 µA Max. During Embedded Algorithm operation, VCC active

current (ICC2) is required even when CE = “H”. The device can be read with standard access time (tCE) from either

of these standby modes.

When using the RESET pin only, CMOS standby mode is achieved with RESET input held at VSS±0.3 V (CE =

“H” or “L”) . Under this condition the current consumed is less than 5 µA Max. Once the RESET pin is set high,

the device requires tRH as a wake-up time for output to be valid for read access.

During standby mode, the output is in the high impedance state regardless of OE input.

23

MBM29QM96DF-65/80

Automatic Sleep Mode

Automatic sleep mode works to restrain power consumption during read-out of the device data. This is useful

in the application such as a handy terminal which requires low power consumption.

To activate this mode, the device automatically switches itself to low power mode when addresses remain stable

during access time of 150 ns. It is not necessary to control CE, WE, and OE on this mode. The current consumed

is typically 1 µA (CMOS Level).

During simultaneous operation, V^CCactive current (ICC2) is required.

Since the data are latched during this mode, the data are continuously read out. When the addresses are

changed, the mode is automatically canceled and the device reads the data for changed addresses.

Output Disable

With the OE input is at logic high level (VIH), output from the device is disabled. This causes the output pins to

be in a high impedance state.

Autoselect

Autoselect mode allows reading out of a binary code and identifies its manufacturer and type. It is intended for

use by programming equipment for the purpose of automatically matching the device to be programmed with

itscorrespondingprogrammingalgorithm. Thismodeisfunctionalovertheentiretemperaturerangeofthedevice.

To activate this mode, the programming equipment must force V^IDon address pin A9. Three identifier bytes may

then be sequenced from the device outputs by toggling addresses. All addresses are DON’T CARES except A6,

A3, A2, A1 and A0. See “MBM29QM96DF User Bus Operation Table” in “■ DEVICE BUS OPERASTION”.

The manufacturer and device codes may also be read via the command register, for instances when the device

is erased or programmed in a system without access to high voltage on the A9 pin. The command sequence is

illustrated in “MBM29QM96DF Command Definitions Table” in “■ DEVICE BUS OPERASTION”.

In the command Autoselect mode, the bank addresses BA (A²², A21, A20, A19, A18) must point to a specific bank

during the third write bus cycle of the Autoselect command. Then the Autoselect data are read from that bank

while array data can be read from the other bank.

A read cycle from address 00h returns the manufacturer’s code (Fujitsu = 04h) . A read cycle at address 01h

outputs device code. When 227Eh is output, it indicates that two additional codes, called Extended Device Codes

is required. Therefore the system may continue reading out these Extended Device Codes at addresses of 0Eh

and 0Fh. Refer to “MBM29QM96DF Autoselect Codes Table” and “Extended Autoselect Codes Table” in

“■ DEVICE BUS OPERASTION”.

In the case of applying V^IDon A9, because both Bank 1 and Bank 2 enter Autoselect mode, simultanous operation

cannot be executed.

Write

Device erase and programming are accomplished via the command register. The contents of the register serve

as input to the internal state machine. The state machine output dictates the device function.

The command register itself does not occupy any addressable memory location. The register is a latch used to

store the commands, along with the address and data information needed to execute the command. The com-

mand register is written by bringing WE to VIL, while CE is at VIL and OE is at VIH. Addresses are latched on the

falling edge of WE or CE, whichever starts later, while data is latched on the rising edge of WE or CE, whichever

starts first. Standard microprocessor write timings are used.

Refer to AC Write Characteristics and the Erase/Programming Waveforms for specific timing parameters.

Accelerated Program Operation

The device offers accelerated program operation which enables the programming in high speed. If the system

asserts V^ACCto the WP/ACC pin, the device automatically enters the acceleration mode and the time required

for program operation will reduce to about 60%. This function is primarily intended to allow high speed program,

so caution is needed as the sector group becomes temporarily unprotected.

24

MBM29QM96DF-65/80

The system uses fast program command sequence when programming during acceleration mode. Set command

to fast mode and reset command from fast mode are not necessary. When the device enters the acceleration

mode, the device automatically set to fast mode. Therefore the present sequence is used for programming and

detection of completion during acceleration mode.

Removing V^ACCfrom the WP/ACC pin returns the device to normal operation. Do not remove V^ACCfrom WP/

ACC pin while programming. See “Accelerated Program Timing Diagram” in “■ TIMING DIAGRAM”.

HiddenROM Region

Unlike previous flash memory devices, the MBM29QM96DF allows simultaneous operation while the Hidden-

ROM is enabled. However, there are a number of restrictions associated with simultaneous operation and device

operation when the HiddenROM is enabled:

(1) The HiddenROM is not available for reading while the Password Unlock, any PPB program/erase operation,

or Password programming are in progress. Reading to any location in the Bank D will return the status of

these operations until these operations have completed execution.

(2) Writing the corresponding Sector Protect latch associated with the overlaid bootblock sector results in the

Sector Protect latch NOT being updated. This is only accomplished when the HiddenROM is not enabled.

(3) Reading the corresponding DPB associated with the overlaid bootblock sector results in reading invalid data

whenthePPBLock/DPBVerifycommandisissued. ThisfunctionisonlyaccomplishedwhentheHiddenROM

is not enabled.

(4) All commands are available for execution when the HiddenROM is enabled except the following list. Issuing

the following commands while the HiddenROM is enabled results in the command being ignored.

— CFI

— Set to Fast Mode

— Fast Program

— Reset from Fast Mode

— Program and Sector Erase Suspend

— Program and Sector Erase Resume

(5) Executing the Sector Erase command is permitted when the HiddenROM is enabled, however, there is no

provision for erasing the HiddenROM with the Sector Erase command, regardless of the protection status.

The Sector Erase command will erase all other sectors when the HiddenROM is enabled. Erasing the

HiddenROM with the Embedded Algorithm is accomplished by issuing the Chip Erase command. If the

HiddenROM is the only sector requiring erasure, set the Sector Protect latches for the remaining sectors

prior to issuing the Chip Erase command.

(6) Executing the HiddenROM Entry command during program or erase suspend mode is allowed. Since the

Sector Erase/Program Resume command is disabled while the HiddenROM is enabled, the user cannot

resume programming or erase of the HiddenROM in place of the overlaid bootblock sector.

HiddenROM Protection Bit

The HiddenROM Protection Bit prevents programming of the HiddenROM memory area. Once set, the Hidden-

ROM memory area contents are non-modifiable.

The MBM29QM96DF features several levels of sector protection, which can disable both the program and erase

operations in certain sectors or sector groups:

(1) Write Protect (WP/ACC)[Hardware Protection]

The device features a hardware protection option using a write protect pin that prevents programming or erasing,

regardless of the state of the sector’s Persistent or Dynamic Protection Bits. The WP/ACC pin is associated with

the “outermost” 2 × 4K words on both ends of boot sectors. The WP/ACC pin has no effect on any other sector.

When WP/ACC is taken to VIL, programming and erase operations of the “outermost” 2 × 4K words sectors on

both end are disabled. By taking WP/ACC back to VIH, the “outermost” 2 × 4K words sectors are enabled for

25

MBM29QM96DF-65/80

program and erase operations, depending upon the status of the individual sector Persistent or Dynamic Pro-

tection Bits. If either of the two outermost sectors Persistent or Dynamic Protection Bits are programmed, program

or erase operations are inhibited. If the sector Persistent or Dynamic Protection Bits are both erased, the two

sectors are available for programming or erasing as long as WP/ACC remains at VIH. The user must hold the

WP/ACC pin at either VIH or VIL during the entire program or erase operation of the “outermost” two sectors on

both end of boot sectors.

(2)Sector Group Protection [Software Protection]

The device features hardware sector protection. This feature disables both program and erase operations in any

number of sector groups. The sector protection feature is enabled using programming equipment at the user’s

site. The device is shipped with all sectors unprotected.

To activate this mode, the programming equipment must force V^IDon address pin A9 and control pin OE, CE =

VIL, (A6, A5, A4, A3, A2, A1,A0) = (0, 1, 1, 1, 0, 1, 0). The sector addresses pins (A22, A21, A20, A19, A18, A17, A16, A15,

A14, A13, and A12) should be set to the sector to be protected. Programming of the protection circuitry begins on

the falling edge of the WE pulse and is terminated with the rising edge of the same. Sector addresses must be

held constant during the WE pulse. See “Sector Group Protection Timing Diagram” in “■ TIMING DIAGRAM”

and “Sector Group Protection Algorithm” in “■ FLOW CHART” for sector protection waveforms and algorithms.

To verify programming of the protection circuitry, the programming equipment must force VID on address pin A9

with CE and OE at VIL and WE at VIH. Scanning the sector addresses (A22, A21, A20, A19, A18, A17, A16, A15, A14,

A13, and A12) while (A6, A5, A4, A3, A2, A1,A0) = (0, 1, 1, 1, 0, 1, 0) produces logic “1” at device output DQ0 for a

protected sector. Otherwise the device produces logic "0" for an unprotected sector. In this mode, the lower order

addresses, except for A0, A1, and A6 are DON’T CARES. Address locations with A1 = VIL are reserved for

Autoselect manufacturer code.

It is also possible to determine if a sector is protected in the system by writing an Autoselect command. Performing

a read operation at the address location XX02h, where the higher order addresses pins (A²², A21, A20, A19, A18,

A17, A16, A15, A14, A13, and A12) represents the sector address will produce a logical “1” at DQ0 for a protected

sector. See “MBM29QM96DF Autoselect Codes Table” and “Extended Autoselect Codes Table” in “■ DEVICE

BUS OPERASTION”.

(3) Extended Sector Group Protection [Software Protection]

In addition to normal sector group protection, the device has Extended Sector Group Protection as extended

function. This function enables protection of the sector group by forcing V^IDon RESET pin and writes a command

sequence. Unlike conventional procedures, it is not necessary to force VID and control timing for control pins.

The only RESET pin requires VID for sector group protection in this mode. The extended sector group protection

requires VID on RESET pin. With this condition the operation is initiated by writing the set-up command (60h) in

the command register. Then the sector group addresses pins (A22, A21, A20, A19, A18, A17, A16, A15, A14, A13 and

A12) and (A6, A5, A4, A3, A2, A1, A0) = (0, 1, 1, 1, 0, 1, 0) should be set to the sector group to be protected (setting

VIL for the other addresses pins is recommended) , and an extended sector group protection command (60h)

should be written. A sector group is typically protected in 250 µs. To verify programming of the protection circuitry,

the sector group addresses pins (A²², A21, A20, A19, A18, A17, A16, A15, A14, A13 and A12) and (A6, A5, A4, A3, A2, A1,

A0) = (0, 1, 1, 1, 0, 1, 0) should be set a command (40h) should be written. Following the command write, logic

“1” at device output DQ0 produces a protected sector in the read operation. If the output is logic “0”, write the

extended sector group protection command (60h) again. To terminate the operation, it is necessary to set RESET

pin to VIH. Refer to “Extended Sector Group Protection Timing Diagram” in “■ TIMING DIAGRAM” and “Extended

Sector Group Protection Algorithm” in “■ FLOW CHART”.

(4) New Sector Protection [Software Protection]

A command sector protection method that replaces the old V^IDcontrolled protection method in future. However

MBM29QM96DF supports both VID protection and Persistent Sector Protection. Both Protect supported as a

shift period.

The persistent Sector Protection and the old V^IDcontrolled protection can go back each other until Persistent

Protection Lock Bit is settled.

26

MBM29QM96DF-65/80

a) Persistent Protection Bit (PPB)

A single Persistent (non-volatile) Protection Bit is assigned to a maximum four sectors (see the sector address

tables for specific sector protection groupings). All 4 K words boot-block sectors have individual sector Persistent

ProtectionBits(PPBs)forgreaterflexibility. EachPPBisindividuallymodifiablethroughthePPBWriteCommand.

Note: If a PPB requires erasure, all of the sector PPBs must first be preprogrammed prior to PPB erasing. All

PPBs erase in parallel, unlike programming where individual PPBs are programmable. It is the

responsibility of the user to perform the preprogramming operation. Otherwise, an already erased sector

PPBs has the potential of being over-erased. There is no hardware mechanism to prevent sector PPBs

over-erasure.

b) Dynamic Protection Bit (DPB)

A volatile protection bit is assigned for each sector. After power-up or hardware reset, the contents of all DPBs

is “0”. Each DPB is individually modifiable through the DPB Write Command.

When the parts are first shipped, the PPBs are cleared, the DPBs are cleared, and PPB Lock is defaulted to

power up in the cleared state-meaning the PPBs are changeable.

When the device is first powered on the DPBs power up cleared (sectors not protected). The Protection State

for each sector is determined by the logical OR of the PPB and the DPB related to that sector. For the sectors

that have the PPBs cleared, the DPBs control whether or not the sector is protected or unprotected. By issuing

the DPB Write/Erase command sequences, the DPBs will be set or cleared, thus placing each sector in the

protected or unprotected state. These are the so-called Dynamic Locked or Unlocked states. They are called

dynamicstatesbecauseitisveryeasytoswitchbackandforthbetweentheprotectedandunprotectedconditions.

This allows software to easily protect sectors against inadvertent changes yet does not prevent the easy removal

of protection when changes are needed. The DPBs maybe set or cleared as often as needed.

PPB vs DPB

The PPBs allow for a more static, and difficult to change, level of protection. The PPBs retain their state across

power cycles because they are Non-Volatile. Individual PPBs are set with a command but must all be cleared

as a group through a complex sequence of program and erasing commands. The PPBs are also limited to 100

erase cycles.

The PBB Lock bit adds an additional level of protection. Once all PPBs are programmed to the desired settings,

the PPB Lock may be set to “1”. Setting the PPB Lock disables all program and erase commands to the Non-

Volatile PPBs. In effect, the PPB Lock Bit locks the PPBs into their current state. The only way to clear the PPB

Lock is to go through a power cycle. 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 set the PBB

Lock to disable any further changes to the PBBs during system operation.

The WP/ACC write protect pin adds a final level of hardware protection to the two outermost 4K words sectors.

When this pin is low it is not possible to change the contents of these two sectors. These sectors generally hold

system boot code. So, the WP/ACC pin can prevent any changes to the boot code that could override the choices

made while setting up sector protection during system initialization.

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 DPB

Write command sequence is all that is necessary. The DPB write/erase command for the dynamic sectors switch

the DPBs to signify protected and unprotected, respectively. 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 disabled 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/ACC = VIL.

27

MBM29QM96DF-65/80

DPB

PPB

PPB Lock

Sector State

0

1

0

1

0

1

0

Unprotected—PPB and DPB are changeable

Protected—PPB and DPB and DPB are changeable

Unprotected—PPB not changeable, DPB is

changeable

0

1

0

1

0

1

Protected—PPB not changeable, DPB is changeable

The above table contains all possible combinations of the DPB, PPB, and PPB lock relating to the status of the

sector.

In summary, if the PPB is set, and the PPB lock is set, the sector is protected and the protection can not be

removed until the next power cycle clears the PBB lock. If the PPB is cleared, the sector can be dynamically

locked or unlocked. The DPB 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 command to a protected sector enables status polling for approximately 1 µs before the device

returns to read mode without having modified the contents of the protected sector. An erase command to a

protected sector enables status polling for approximately 50 µs after which the device returns to read mode

without having erased the protected sector.

The programming of the DPB, PPB, and PPB lock for a given sector can be verified by writing a DPB/PPB/PPB

lock verify command to the device.

–DPB Status

The programming of the DPB for a given sector can be verified by writing a DPB status verify command to the

device.

–PPB Status

The programming of the PPB for a given sector can be verified by writing a PPB status verify command to the

device.

–PPB Lock Bit Status

The programming of the PPB Lock Bit for a given sector can be verified by writing a PPB Lock Bit status verify

command to the device.

c) Persistent Protection Bit Lock (PPB Lock)

• PPB Locked

• PPB Locked with Password

A highly sophisticated protection method that requires a password before changes to certain sectors or sector

groups are permitted.

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. If the customer decides to continue using the

Persistent Sector Protection method, they must set the Persistent Sector Protection Mode Locking Bit. This will

permanently set the part to operate only using Persistent Sector Protection. If the customer decides to use the

password method, they must set the Password Mode Locking Bit. This will permanently set the part to operate

only using password sector protection.

28

MBM29QM96DF-65/80

It is important to remember that setting either the Persistent Sector Protection Mode Locking Bit or the Password

Mode Locking 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 selected when the device is first

programmed, rather than relying on the default mode alone. This is so that it is not possible for a system program

or virus to later set the Password Mode Locking Bit, which would cause an unexpected shift from the default

Persistent Sector Protection Mode into the Password Protection Mode.

The WP/ACC Hardware Protection feature is always available, independent of the software managed protection

method chosen.

A global volatile bit. When set to “1”, the PPBs cannot be changed. When cleared (“0”), the PPBs are changeable.

There is only one PPB Lock bit per device. The PPB Lock is cleared after power-up or hardware reset. There is

no command sequence to unlock the PPB Lock.

The Persistent Protection Bit (PPB) Lock is a volatile bit that reflects the state of the Password Mode Locking

Bit after power-up reset. If the Password Mode Locking Bit is set, which indicates the device is in Password

Protection Mode, the PPB 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 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 back to a “1”.

If the Password Mode Locking Bit is not set, indicating Persistent Sector Protection Mode, the PPB Lock Bit is

cleared after power-up or hardware reset. The PPB Lock Bit is set by issuing the PPB Lock Bit Set command.

Once set the only means for clearing the PPB Lock Bit is by issuing a hardware or power-up reset. The Password

Unlock command is ignored in Persistent Sector Protection Mode.

-Password and Password Mode Locking Bit

In order to select the Password sector protection scheme, the customer must first program the password. Fujitsu

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:

(1) It permanently sets the device to operate using the Password Protection Mode. It is not possible to reverse

this function.

(2) 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 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 disabled, there is no means to verify what the password is

afterwards. If the password is lost after setting the Password Mode Locking Bit, there will be no way to clear the

PPB Lock bit.

The Password Mode Locking Bit, once set, prevents reading the 64-bit password on the DQ bus and further

password programming. The Password Mode Locking Bit is not erasable. Once Password Mode Locking Bit is

programmed, the Persistent Sector Protection Locking Bit is disabled from programming, guaranteeing that no

changes to the protection scheme are allowed.

64-bit Password

The 64-bit Password is located in its own memory space and is accessible through the use of the Password

Program and Verify commands (see “Password Verify Command”). The password function works in conjunction

with the Password Mode Locking Bit, which when set, prevents the Password Verify command from reading the

contents of the password on the pins of the device.

29

MBM29QM96DF-65/80

-Persistent Sector Protection Mode Locking Bit

Like the password mode locking bit, a Persistent Sector Protection mode locking bit exists to guarantee that the

device remain in software sector protection. Once set, the Persistent Sector Protection locking bit prevents

programming of the password protection mode locking bit. This guarantees that a hacker could not place the

device in password protection mode.

(5) Temporary Sector Group Unprotection

This feature allows temporary unprotection of previously protected sectors of the device in order to change data.

The Sector Unprotection mode is activated by setting the RESET pin to high voltage (VID). During this mode,

formerly protected sector groups can be programmed or erased by selecting the sector group addresses. Once

the VID is taken away from the RESET pin, all the previously protected sector groups will be protected again.

While PPB Lock is set, this device cannot enter the Temporary Sector Unprotection mode.

30

MBM29QM96DF-65/80

■ COMMAND DEFINITIONS

Device operations are selected by writing specific address and data sequences into the command register. Some

commands require Bank Address (BA) input. When command sequences are input into bank reading, the

commands have priority over the reading. “MBM29QM96DF Command Definitions Table” in “■ DEVICE BUS

OPERASTION” shows the valid register command sequences. Note that the Erase Suspend (B0h) and Erase

Resume (30h) commands are valid only while the Sector Erase operation is in progress. Also the Program

Suspend (B0h) and Program Resume (30h) commands are valid only while the Program operation is in progress.

Moreover, Read/Reset commands are functionally equivalent, resetting the device to the read mode. Please

note that commands are always written at DQ7 to DQ0 and DQ15 to DQ8 bits are ignored.

Read/Reset Command

In order to return from Autoselect mode or Exceeded Timing Limits (DQ⁵= 1) to Read/Reset mode, verify mode

of secter protect commands, the Read/Reset operation is initiated by writing the Read/Reset command sequence

into the command register. Microprocessor read cycles retrieve array data from the memory. The device remains

enabled for reads until the command register contents are altered.

The device automatically powers-up in the Read/Reset state. In this case, a command sequence is not required

toreaddata. Standardmicroprocessorreadcyclesretrieve arraydata. Thisdefaultvalueensuresthatnospurious

alteration of the memory content occurs during the power transition. Refer to the AC Read Characteristics and

Waveforms for specific timing parameters.

Autoselect Command

Flash memories are intended for use in applications where the local CPU alters memory contents. Therefore

manufacture and device codes must be accessible while the device resides in the target system. PROM pro-

grammers typically access the signature codes by raising A⁹to a higher voltage. However multiplexing high

voltage onto the address lines is not generally desired system design practice.

Thedevicecontains AutoselectcommandoperationtosupplementtraditionalPROMprogrammingmethodology.

The operation is initiated by writing the Autoselect command sequence into the command register.

The Autoselect command sequence is initiated first by writing two unlock cycles. This is followed by a third write

cycle that contains the bank address (BA) and the Autoselect command. Then the manufacture and device

codes can be read from the bank, and actual data from the memory cell can be read from another bank. The

higher order address (A²², A21, A20, A19, A18) required for reading out the manufacture and device codes demands

the bank address (BA) set at the third write cycle.

Following the command write, a read cycle from address (BA) 00h returns the manufacturer’s code (Fujitsu =

04h). And a read cycle at address (BA) 01h outputs device code. When 227Eh is output, this indicates that two

additional codes, called Extended Device Codes will be required. Therefore the system may continue reading

out these Extended Device Codes at the address of (BA) 0Eh, as well as at (BA) 0Fh. Refer to “MBM29QM96DF

Autoselect Codes Table” and “Extended Autoselect Codes Table” in “■ DEVICE BUS OPERASTION”.

The sector state (PPB protection or PPB unprotection) is informed by address (SA) XX02h . Scanning the sector

group addresses (A²², A21, A20, A19, A18, A17, A16, A15, A14, A13, and A12) while(A6, A5, A4, A3, A2, A1,A0) = (0, 1, 1,

1, 0, 1, 0) produces logic “1” at device output DQ0 for a protected sector group. The programming verification

should be performed by verifying sector group protection on the protected sector. See “MBM29QM96DF User

Bus Operation Table” in “■ DEVICE BUS OPERASTION”.

The manufacture and device codes can be read from the selected bank. To read the manufacture and device

codes and sector protection status from a non-selected bank, it is necessary to write the Read/Reset command

sequence into the register. Autoselect command should then be written into the bank to be read.

If the software (program code) for Autoselect command is stored in the Flash memory, the device and manu-

facture codes should be read from the other bank, which does not contain the software.

To terminate the operation, it is necessary to write the Read/Reset command sequence into the register. To

execute the Autoselect command during the operation, Read/Reset command sequence must be written before

the Autoselect command.

31

MBM29QM96DF-65/80

Word Programming Command

The device is programmed on word-by-word basis. Programming is a four bus cycle operation. There are two

“unlock” write cycles. These are followed by the program set-up command and data write cycles. Addresses are

latched on the falling edge of CE or WE, whichever happens later, and the data is latched on the rising edge of

CE or WE, whichever happens first. The rising edge of CE or WE (whichever happens first) starts programming.

Upon executing the Embedded Program Algorithm command sequence, the system is not required to provide

further controls or timings. The device automatically provides adequate internally generated program pulses

and verify programmed cell margin.

The system can determine the status of the program operation by using DQ7 (Data Polling) , DQ6 (Toggle Bit)

or RY/BY. The Data Polling and Toggle Bit must be performed at the memory location being programmed.

The automatic programming operation is completed when the data on DQ⁷is equivalent to data written to this

bit at which device returns to the read mode and addresses are no longer latched. See “Hardware Sequence

Flags Table” in “■ COMMAND DEFINITIONS”. Therefore the device requires that a valid address to the device

be supplied by the system in this particular instance. Hence Data Polling must be performed at the memory

location being programmed.

If hardware reset occurs during the programming operation, the data being written is not guaranteed.

Programming is allowed in any sequence and across sector boundaries. Beware that a data “0” cannot be

programmed back to a “1”. Attempting to do so may either hang up the device or result in an apparent success

according to the data polling algorithm but a read from Read/Reset mode will show that the data is still “0”. Only

erase operations can convert from “0”s to “1”s.

“Embedde Program^TMAlgorithm” in “■ FLOW CHART” illustrates the Embedded Program^TMAlgorithm using

typical command strings and bus operations.

Program Suspend/Resume Command

The Program Suspend command allows the system to interrupt a program operation so that data can be read

from any address. Writing the Program Suspend command (B0h) during the Embedded Program operation

immediately suspends the programming. The Program Suspend command may also be issued during a pro-

gramming operation while an erase is suspended. The bank addresses of sector being programmed should be

set when writing the Program Suspend command.

When the Program Suspend command is written during a programming process, the device halts the program

operation within 1 µs and updates the status bits.

After the program operation has been suspended, the system can read data from any address. The data at

program-suspended address is not valid. Normal read timing and command definitions apply.

After the Program Resume command (30h) is written, the device reverts to programming. The bank addresses

of sectors being suspended should be set when writing the Program Resume command. The system can

determine the program operation status using the DQ⁷or DQ6 status bits, just as in the standard program

operation. See “Write Operation Status” for more information.

The system may also write the Autoselect command sequence in the Program Suspend mode. The device allows

reading Autoselect codes at the addresses within programming sectors, since the codes are not stored in the

memory. When the device exits from the Autoselect mode, the device reverts to the Program Suspend mode,

and is ready for another valid operation. See “Autoselect Command Sequence” for more information.

The system must write the Program Resume command (address bits are “Bank Address”) to exit from the

Program Suspend mode and continue programming operation. Further writes of the Resume command are

ignored. Another Program Suspend command can be written after the device resumes programming.

32

MBM29QM96DF-65/80

Chip Erase Command

Chip erase is a six-bus cycle operation. There are two “unlock” write cycles. These are followed by writing the

“set-up” command. Two more “unlock” write cycles are then followed by the chip erase command.

Chip erase does not require the user to program prior to erase. Upon executing the Embedded Erase Algorithm

command sequence the device automatically programs and verifies the entire memory for an all zero data pattern

prior to electrical erase. (Preprogram Function) The system is not required to provide any controls or timings

during these operations.

The system can determine the erase operation status by using DQ⁷(Data Polling), or DQ6 (Toggle Bit). The chip

erase begins on the rising edge of the last CE or WE, whichever happens first in the command sequence and

terminates when the data on DQ7 is “1” (See Write Operation Status section.) at which the device returns to

read the mode.

Chip Erase Time; Sector Erase Time × All sectors + Chip Program Time (Preprogramming)

“Embedde Erase^TMAlgorithm” in “■ FLOW CHART” illustrates the Embedded Erase^TMAlgorithm for typical

command strings and bus operations.

Sector Erase Command

Sector erase is a six bus cycle operation. There are two “unlock” write cycles. These are followed by writing the

“set-up” command. Two more “unlock” write cycles are then followed by the Sector Erase command. The sector

address (any address location within the desired sector) is latched on the falling edge of CE or WE whichever

starts later, while the command (Data = 30h) is latched on the rising edge of CE or WE whichever starts first.

Aftertime-outof“tTOW”fromtherisingedgeofthelastsectorerasecommand, thesectoreraseoperationwillbegin.

Multiple sectors are erased concurrently by writing the six bus cycle operations on “MBM29QM96DF Command

Definitions Table” in “■ DEVICE BUS OPERATION”. This sequence is followed with writes of the Sector Erase

command to addresses in other sectors desired to be concurrently erased. The time between writes must be

less than “t^TOW” otherwise that command is not accepted and erasure does not start. It is recommended that

processor interrupts be disabled during this time to guarantee this condition. The interrupts can be re-enabled

after the last Sector Erase command is written. A time-out of “tTOW” from the rising edge of last CEor WE whichever

starts first initiates the execution of the Sector Erase command(s). If another falling edge of CE or WE, whichever

starts first occurs within the “tTOW” time-out window the timer is reset. (Monitor DQ3 to determine if the sector

erase timer window is still open, see section DQ3, Sector Erase Timer.) Any command other than Sector Erase

or Erase Suspend during this time-out period will reset the device to the read mode, ignoring the previous

command string. Resetting the device once execution has begun may corrupt the data in the sector. In that case

restart the erase on those sectors and allow them to complete. Refer to Write Operation Status section for Sector

Erase Timer operation. Loading the sector erase buffer may be done in any sequence and with any number of

sectors.

Sector erase does not require the user to program prior to erase. The device automatically programs all memory

locations in the sector(s) to be erased prior to electrical erase (Preprogram function). When erasing a sector or

sectors the remaining unselected sectors are not affected. The system is not required to provide any controls

or timings during these operations.

The system can determine the status of the erase operation by using DQ⁷(Data Polling), or DQ6 (Toggle Bit).

The sector erase begins after the “t^TOW” time out from the rising edge of CE or WE whichever starts first for the

last sector erase command pulse and terminates when the data on DQ7 is “1”. See Write Operation Status

section. at which time the device returns to the read mode. Data polling and Toggle Bit must be performed at

an address within any of the sectors being erased.

Multiple Sector Erase Time; [Sector Erase Time + Sector Program Time (Preprogramming)] × Number of Sector

Erase.

In case of multiple sector erase across bank boundaries, a read from the bank (read-while-erase) to which

sectors being erased belong cannot be performed.

33

MBM29QM96DF^-65/80

“Embedde Erase^TMAlgorithm” in “■ FLOW CHART” illustrates the Embedded Erase^TMAlgorithm for typical

command strings and bus operations.

Erase Suspend/Resume Command

The Erase Suspend command allows the user to interrupt a Sector Erase operation and then perform data reads

from or programs to a sector not being erased. This command is applicable ONLY during the Sector Erase

operation which includes the time-out period for sector erase. The Erase Suspend command is ignored during

the Chip Erase operation. Writting the Erase Suspend command (B0h) during the Sector Erase time-out results

in immediate termination of the time-out period and suspension of the erase operation.

Writing the Erase Resume command (30h) resumes the erase operation. The addresses are “DON’T CARES”

when writting the Erase Suspend or Erase Resume command.When the Erase Suspend command is written

during the Sector Erase operation, the device takes a maximum of “t^SPD” to suspend the erase operation. When

the device has entered the erase-suspended mode, the DQ7 bit is at logic “1”, and DQ6 stops toggling. The user

must use the address of the erasing sector for reading DQ6 and DQ7 to determine if the erase operation is

suspended. Further writes of the Erase Suspend command are ignored.

When the erase operation is suspended, the device defaults to the erase-suspend-read mode. Reading data in

this mode is the same as reading from the standard read mode except that the data must be read from sectors

that have not been erase-suspended. Successively reading from the erase-suspended sector while the device

is in the erase-suspend-read mode causes DQ2 to toggle. See the section on DQ2.

After entering the erase-suspend-read mode, the user can program the device by writing the appropriate com-

mand sequence for Program. This program mode is known as the erase-suspend-program mode. Again, pro-

gramming in this mode is the same as programming in the regular Program mode except that the data must be

programmed to sectors that are not erase-suspended. Successively reading from the erase-suspended sector

while the device is in the erase-suspend-program mode causes DQ²to toggle. The end of the erase-suspended

Program operation is detected by the Data polling of DQ7 or by the Toggle Bit I (DQ6) which is the same as the

regular Program operation. Note that DQ7 must be read from the Program address while DQ6 can be read from

any address.

To resume the operation of Sector Erase, the Resume command (30h) should be written. Any further writes of

theResumecommandatthispointisignored. AnotherEraseSuspendcommandiswrittenafterthechip resumes

erasing.

Fast Mode

Fast Mode function dispenses with the initial two unlock cycles required in the standard program command

sequence writing Fast Mode command into the command register. In this mode the required bus cycle for

programming is two cycles instead of four bus cycles in standard program command. The read operation is also

executed after exiting this mode. During the Fast mode, do not write any commands other than the Fast program/

Fast mode reset command. To exit this mode, write Fast Mode Reset command into the command register.

Refer to “Embedded Program Algorithm for Fast Mode” in “■ FLOW CHART”. The V^CCactive current is required

even CE = VIH during Fast Mode.

Fast Programming

During Fast Mode, the programming can be executed with two bus cycles operation. The Embedded Program

Algorithm is executed by writing program set-up command (A0h) and data write cycles (PA/PD). Refer to

“Embedded Program Algorithm for Fast Mode” in “■ FLOW CHART”.

Query (CFI:Common Flash Memory Interface)

The CFI (Common Flash Memory Interface) specification outlines device and host system software interrogation

handshake which allows specific vendor-specified software algorithms to be used for entire families of device.

This allows device-independent, JEDEC ID-independent, and forward-and backward-compatible software sup-

port for the specified flash device families. Refer to “Common Flash Memory Interface Code Table” in

“■ FLEXIBLE SECTOR-ERASE ARCHITECTURE” in detail.

The operation is initiated by writing the query command (98h) into the command register. Following the command

write, a read cycle from specific address retrives device information. Please note that output data of upper byte

34

MBM29QM96DF-65/80

(DQ¹⁵to DQ8) is “0”. Refer to “Common Flash Memory Interface Code Table” in “■ FLEXIBLE SECTOR-ERASE

ARCHITECTURE”. To terminate operation, write the Read/Reset command sequence into the register.

HiddenROM Entry Command

The device has a HiddenROM area with One Time Protect function. This area is to enter the security code and

to unable the change of the code once set. Program/erase is possible in this area until it is protected. However

once it is protected, it is impossible to unprotect. Therefore extreme caution is required.

HiddenROM area is 256 byte. This area is normally the “outermost” 8K words boot block area. Therefore, write

the HiddenROM entry command sequence to enter the HiddenROM area. It is called HiddenROM mode when

the HiddenROM area appears.

The following commands are permitted after issuing the HiddenROM Entry command:

1. Autoselect

2. Password Program

3. Password Verify

4. Password Unlock

5. Read/Reset

6. Program

7. Chip and Sector Erase

8. HiddenROM Protection Bit Program

9. PPB Program

10. All PPB Erase

11. PPB Lock Bit Set

12. DPB Write

13. DPB/PPB/PPB Lock Bit Verify

14. HiddenROM Exit

The following commands are unavailable when the HiddenROM is enabled. Issuing the following commands

while the HiddenROM is enabled results in the command being ignored.

1. CFI

2. Set to Fast Mode

3. Fast Program

4. Reset from Fast Mode

5. Program and Sector Erase Suspend

6. Program and Sector Erase Resume

The HiddenROM Entry command is allowed when the device is in either program or erase suspend modes. If

the HiddenROM is enabled, the program or erase suspend command is ignored. This prevents resuming either

programming or erase on the HiddenROM if the overlayed sector is undergoing programming or erase. It is the

responsibility of the software to resume the program or erase of a suspended program or erase after exiting the

HiddenROM.

Executing any of the PPB program/erase commands, or Password Unlock command results in the Bank A

returning the status of these operations while they are in progress, thus making the HiddenROM unavailable for

reading. If the HiddenROM is enabled while the DPB command is issued, the DPB for the overlayed sector is

NOT updated. Reading the DPB status using the PPB Lock Bit/DPB verify command when the HiddenROM is

enabled returns invalid data. Note that any other commands should not be issued other than the HiddenROM

program/protection/reset commands during the HiddenROM mode. When you issue the other commands in-

cluding the suspend resume, send the HiddenROM reset command first to exit the HiddenROM mode and then

issue each command.

HiddenROM^TMProgram Command

To program the data to the HiddenROM area, write the HiddenROM program command sequence during Hid-

denROM mode. This command is the same as the program command in usual except to write the command

during HiddenROM mode. Therefore the detection of completion method is the same as using the DQ⁷data

35

MBM29QM96DF-65/80

polling, and DQ⁶toggle bit. Need to pay attention to the address to be programmed. If the address other than

the HiddenROM area is selected to program, data of the address are changed.

During the write into the HiddenROM region, the program suspend command issuance is prohibited.

HiddenROM^TMProtect Command

The method to protect the HiddenROM is to apply high voltage (V^ID) to A9 and OE, set the sector address in the

HiddenROM area and (A6, A5, A4, A3, A2, A1, A0) = (0, 0, 1, 1, X, 1, 0), and apply the write pulse during the

HiddenROM mode. To verify the protect circuit, apply high voltage (V^ID) to A9, specify (A6, A5, A4, A3, A2, A1,

A0) = (0, 0, 1, 1, X, 1, 0) and the sector address in the HiddenROM area, and read. When “1” appears on DQ0,

the protect setting is completed. “0” appears on DQ0 if it is not protected. Please apply write pulse agian. The

same command sequence could be used for the above method because other than the HiddenROM mode, it is

the same as the sector protect in the past.

And the device has also HiddenROM protect command without V^ID. See “MBM29QM96DF Command Definitions

Table” in “ ■ DEVICE BUS OPERASTION”.

Other sector will be effected if the address other than those for HiddenROM area is selected for the sector

address, so please be carefull. Once it is protected, protection can not be cancelled, so please pay the closest

attention.

Password Program 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. 4 Password Program commands are required to program

the password. The user must enter the unlock cycle, password program command (38h) and the program

address/data for each portion of the password when programming. There are no provisions for entering the 2-

cycle unlock cycle, the password program command, and all the password data. There is no special addressing

order required for programming the password. Also, when the password is undergoing programming, Simulta-

neous Operation is disabled. Read operations to any memory location will return the programming status. Once

programming is complete, the user must issue a Read/Reset command to return the device to normal operation.

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. Programming a “1” after a

cell is programmed as a “0” results in a time-out by the Embedded Program Algorithm with the cell remaining

as a “0”. The password is all F’s when shipped from the factory. All 64-bit password combinations are valid as

a password. Writing the HiddenROM Exit command returns the device back to normal operation.

Password Verify Command

ThePasswordVerifyCommandisusedtoverifythePassword. ThePasswordisverifiableonlywhenthePassword

Mode Locking Bit is not programmed. If the Password Mode Locking Bit is programmed and the user attempts

to verify the Password, the device will always drive all F’s onto the DQ data bus.

The Password Verify command is permitted if the HiddenROM is enabled. Also, the device will not operate in

Simultaneous Operation when the Password Verify command is executed. Only the password is returned re-

gardless of the bank address. The lower two address bits (A¹:A0) are valid during the Password Verify. Writing

the HiddenROM Exit command returns the device back to normal operation.

Password Protection Mode Locking Bit Program Command

ThePasswordProtectionModeLockingBitProgramCommandprogramsthePasswordProtectionModeLocking

Bit, which prevents further verifies or updates to the Password. Once programmed, the Password Protection

Mode Locking Bit cannot be erase. Once the Password Protection Mode Locking Bit is programmed, the Per-

sistent Sector Protection Locking Bit program circuitry is disabled, thereby forcing the device to remain in the

Password Protection mode. After issuing "PL/68h" at 4th bus cycle, the device requires approximately 150µs

time out period for programming the Password Protection Mode Locking Bit. Then by writing "PL/48h" at 5th bus

cycle, thedeviceoutputsverifydataatDQ⁰. If DQ0 = 1 then Password Protection Mode Locking Bit is programmed.

If not, then the user needs to repeat this program sequence from the 4th cycle of "PL/68h".Exiting the Mode

Locking Bit Program command is accomplished by writing the HiddenROM Exit command.

36

MBM29QM96DF-65/80

Persistent Sector Protection Mode Locking Bit Program Command

ThePersistentSectorProtectionModeLockingBitProgramCommandprogramsthePersistentSectorProtection

Mode Locking Bit, which prevents the Password Mode Locking Bit from ever being programmed. By disabling

the program circuitry of the Password Mode Locking Bit, the device is forced to remain in the Persistent Sector

Protection mode of operation, once this bit is set. After issuing "SPML/68h" at 4th bus cycle, the device requires

approximately 150µs time out period for programming the Persistent Protection Mode Locking Bit. Then by writing

"SPML/48h" at 5th bus cycle, the device outputs verify data at DQ⁰. If DQ0 = 1 then Persistent Protection Mode

Locking Bit is programmed. If not, then the user needs to repeat this program sequence from the 4th cycle of

"SPML/68h". Exiting the Persistent Protection Mode Locking Bit Program command is accomplished by writing

the HiddenROM Exit command.

PPB Lock Bit Set 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 command. Once the PPB Lock

Bit is set, it cannot be cleared unless the device is taken through a power-on clear or the Password Unlock

command is executed. If the Password Mode Locking Bit is set, the PPB Lock Bit status is reflected as set, even

after a power-on reset cycle. Exiting the PPB Lock Bit Set command is accomplished by writing the HiddenROM

Exit command.

DPB Write(Erase) Command

The DPB Write command is used to set or clear a DPB for a given sector. The high order address bits (A²²to

A12) are issued at the same time as the code 01h or 00h on DQ7 to DQ0. All other DQ data bus pins are ignored

during the data write cycle. The DPBs are modifiable at any time, regardless of the state of the PPB or PPB

Lock Bit. The DPBs are cleared at power-up or hardware reset.Exiting the DPB Write command is accomplished

by writing the HiddenROM Exit command.

DPB Verify command

DPB verify command is used to verify the status of a DPB for given sevtor.

Scanning the sector addresses (SA) will produce a logical "1" at the device output DQ⁰for a protected sector.

Otherwise the device will produce "0" at DQ0 for the sector which is not protected. Writing the HiddenROM Exit

Command returns the device back to normal operation.

PPB Lock Bit Verify command

PPB Lock Bit verify command is used to verify the status of a PPB Lock Bit.

A logical "1" at the device output DQ¹indicates that the PPB Lock Bit is set.

If PPB Lock Bit is not set, DQ1 will output"0". Writing the HiddenROM Exit Command returns the device back to

normal operation.

Password Unlock Command

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 password must be

entered in order for the unlocking function to occur. This command cannot be issued any faster than 2 µs at a

time to prevent a hacker from running through the all 64-bit combinations in an attempt to correctly match a

password. Ifthecommandisissuedbeforethe2µsexecutionwindowforeachportionoftheunlock, thecommand

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. A⁰and A1 are used to determine the 16 bit data quantity is used to

match separated 16 bits. Writing the Password Unlock command is address order specific. In other words, the

lowers address A¹:A0 = 00, the next cycle command is to A1:A0 = 01, then to A1:A0 = 10, and finally to A1:A0 = 11.

Writing out of sequence results in the Password Unlock not returning a match with the password and the PPB

Lock Bit remains set.

37

MBM29QM96DF-65/80

Once the Password Unlock command is entered, the RY/BY pin goes LOW indicating that the device is busy.

Also, reading the Bank A results in the DQ6 pin toggling, indicating that the Password Unlock function is in

progress. Reading the other bank returns actual array data. Approximately 2µs is required for each portion of

the unlock. Once the first portion of the password unlock completes (RY/BY is not driven and DQ6 does not

toggle when read), the next cycle is issued, only this time with the next part of the password. Seven cycles

Password Unlock commands are required to successfully clear the PPB Lock Bit. As with the first Password

Unlock command, the RY/BY signal goes LOW and reading the device results in the DQ6 pin toggling on

successive read operations until complete. It is the responsibility of the microprocessor to keep track of the

number of Password Unlock cycles, the order, and when to read the PPB Lock bit to confirm successful password

unlock. Writing the HiddenROM Exit Command returns the device back to normal operation.

PPB Program Command

The PPB Program command is used to program, or set, a given PPB. Each PPB is individually programmed

(but is bulk erased with the other PPBs). The specific sector address (A22 to A12) are written at the same time

as the program command 60h. If the PPB Lock Bit is set and the corresponding PPB is set for the sector, the

PPB Program command will not execute and the command will time-out without programming the PPB. After

issuing "SGA + WP/68h" at 4th bus cycle, the device requires approximately 150µs time out period for program-

ming the PPB. Then by writing "SGA + WP/48h" at 5th bus cycle, the device outputs verify data at DQ⁰. If DQ0

= 1 then PPB is programmed. If not, then the user needs to repeat this program sequence from the 4th cycle of

"SGA + WP/68h".

The PPB Program command does not follow the Embedded Program algorithm. Writing the HiddenROM Exit

Command returns the device back to normal operation.

All PPB Erase Command

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 (60h), 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. After issuing "WP/60h" at

4th bus cycle, the device requires approximately 1.5ms time out period for programming the PPB. Then by writing

"SGA + WP/40h" at 5th bus cycle, the device outputs verify data at DQ⁰. If DQ0 = 0 then PPB is successfully

erased. If not, then the user needs to repeat this program sequence from the 4th cycle of "WP/60h".

It is the responsibility of the user to preprogram all PPBs prior to issuing the All PPB Erase command. If the user

attempts to erase a cleared PPB, over-erasure may occur making it difficult to program the PPB at a later time.

Also note that the total number of PPB program/erase cycles is limited to 100 cycles. Cycling the PPBs beyond

100 cycles is not guaranteed. Writing the HiddenROM Exit Command returns the device back to normal oper-

ation.

Write Operation Status

Detailed in “Hardware Sequence Flags Table” in “■ COMMAND DEFINITIONS” are all the status flags which

can determine the status of the bank for the current mode operation. The read operation from the bank which

doesn’t operate Embedded Algorithm returns data of memory cells. These bits offer a method for determining

whether an Embedded Algorithm is properly completed. The information on DQ²is address-sensitive. This

means that if an address from an erasing sector is consecutively read, the DQ2 bit will toggle. However, DQ2 will

not toggle if an address from a non-erasing sector is consecutively read. This allows users to determine which

sectors are in erase and which are not.

The status flag is not output from banks (non-busy banks) which do not execute Embedded Algorithms. For

example, a bank (busy bank) is executing an Embedded Algorithm. When the read sequence is [1] < busy bank

>, [2] < non-busy bank >, [3] < busy bank >, the DQ⁶toggles in the case of [1] and [3]. In case of [2], the data of

memory cells are output. In the erase-suspend read mode with the same read sequence, DQ6 will not be toggled

in [1] and [3].

38

MBM29QM96DF-65/80

Hardware Sequence Flafs Table

Status

DQ⁷

DQ7

0

DQ⁶

DQ⁵

0

DQ³

0

DQ²

1

Embedded Program Algorithm

Embedded Erase Algorithm

Toggle

0

1

Toggle*¹

Erase Suspend Read

(Erase Suspended Sector)

1

0

Data

0

Data

0

Toggle

Data

1*²

In Progress

Erase

Erase Suspend Read

Suspended

Data

DQ7

Data

(Non-Erase Suspended Sector)

Mode

Erase Suspend Program

(Non-Erase Suspended Sector)

Toggle

Embedded Program Algorithm

Embedded Erase Algorithm

DQ⁷

0

Toggle

1

0

1

N/A

Exceeded

Erase

Time Limits

Erase Suspend Program

Suspended

DQ⁷

Toggle

1

0

N/A

(Non-Erase Suspended Sector)

Mode

*1 : Successive reads from the erasing or erase-suspend sector will cause DQ²to toggle.

*2 : Reading from non-erase suspend sector address will indicate logic “1” at the DQ2 bit.

Notes: • DQ0 and DQ1 are reserve pins for future use.

• DQ4 is limited to Fujitsu internal use.

DQ⁷

Data Polling

The device features Data Polling as a method to indicate to the host that the Embedded Algorithms are in

progress or completed. During the Embedded Program Algorithm, an attempt to read the device will produce a

complement of data last written to DQ7. Upon completion of the Embedded Program Algorithm, an attempt to

read the device will produce true data last written to DQ7. During the Embedded Erase Algorithm, an attempt to

read the device will produce a “0” at the DQ7 output. Upon completion of the Embedded Erase Algorithm, an

attempt to read device will produce a “1” on DQ7. The flowchart for Data Polling (DQ7) is shown in “Data Polling

Algorithm” in “■ FLOW CHART”.

For programming, the Data Polling is valid after the rising edge of the fourth write pulse in the four write pulse

sequences.

For chip erase and sector erase, the Data Polling is valid after the rising edge of the sixth write pulse in the six

write pulse sequences. Data Polling must be performed at sector addresses of sectors being erased, not pro-

tected sectors. Otherwise the status may become invalid.

If a program address falls within a protected sector, Data Polling on DQ7 is active for approximately 1 µs, then

that bank returns to the read mode. After an erase command sequence is written, if all sectors selected for

erasing are protected, Data Polling on DQ7 is active for approximately 400 µs, then the bank returns to read mode.

Once the Embedded Algorithm operation is close to being completed, the device data pins (DQ7) may change

asynchronously while the output enable (OE) is asserted low. This means that device is driving status information

on DQ7 at one instant, and then that byte’s valid data at the next instant. Depending on when the system samples

the DQ7 output, it may read the status or valid data. Even if device has completed the Embedded Algorithm

operation and DQ7 has a valid data, data outputs on DQ0 to DQ6 may still be invalid. The valid data on DQ0 to

DQ7 will be read on successive read attempts.

TheDataPollingfeatureisactiveonlyduringtheEmbeddedProgrammingAlgorithm, EmbeddedEraseAlgorithm

or sector erase time-out. (See “Toggle Bit Status Table” in “■ COMMAND DEFINITIONS”.)

See “Data Polling during Embedded Algorithm Operation Timing Diagram” in “■ TIMING DIAGRAM” for the Data

Polling timing specifications and diagrams.

39

MBM29QM96DF-65/80

DQ⁶

Toggle Bit I

The device also features the “Toggle Bit I” as a method to indicate to the host system that the Embedded

Algorithms are in progress or completed.

During Embedded Program or Erase Algorithm cycle, successive attempts to read (OE toggling) data from the

busy bank will result in DQ6 toggling between one and zero. Once the Embedded Program or Erase Algorithm

cycle is completed, DQ6 will stop toggling and valid data will be read on the next successive attempts. During

programming, the Toggle Bit I is valid after the rising edge of the fourth write pulse in the four write pulse

sequences. For chip erase and sector erase, the Toggle Bit I is valid after the rising edge of the sixth write pulse

in the six write pulse sequences. The Toggle Bit I is active during the sector time out.

In programming, if the sector being written is protected, the toggle bit will toggle for about 1 µs and then stop

toggling with data unchanged. In erase, the device will erase all selected sectors except for protected ones. If

all selected sectors are protected, the chip will toggle the toggle bit for about 400 µs and then drop back into

read mode, having data kept remained.

Either CE or OE toggling will cause DQ6 to toggle. In addition, an Erase Suspend/Resume command will cause

DQ6 to toggle.

The system can use DQ⁶to determine whether a sector is actively erased or is erase-suspended. When a bank

is actively erased (that is, the Embedded Erase Algorithm is in progress) , DQ6 toggles. When a bank enters the

Erase Suspend mode, DQ6 stops toggling. Successive read cycles during erase-suspend-program cause DQ6

to toggle.

To operate toggle bit function properly, CE or OE must be high when bank address is changed.

See “AC Waveforms for Toggle Bit I during Embedded Algorithm Operations Timing Diagram” in “■ TIMING

DIAGRAM” for the Toggle Bit I timing specifications and diagrams.

DQ⁵

Exceeded Timing Limits

DQ5 will indicate if the program or erase time has exceeded the specified limits (internal pulse count) . Under

these conditions DQ5 will produce “1”. This is a failure condition indicating that the program or erase cycle was

not successfully completed. Data Polling is only operating function of the device under this condition. The CE

circuit will partially power down device under these conditions (to approximately 2 mA) . The OE and WE pins

will control the output disable functions as described in “MBM29QM96DF User Bus Operation Table” in “■

DEVICE BUS OPERASTION”.

The DQ⁵failure condition may also appear if a user tries to program a non-blank location without pre-erase. In

this case the device locks out and never completes the Embedded Algorithm operation. Hence, the system never

reads valid data on DQ⁷bit and DQ6 never stop toggling. Once the device has exceeded timing limits, the DQ5

bit will indicate a “1.” Please note that this is not a device failure condition since the device was incorrectly used.

If this occurs, reset device with the command sequence.

DQ³

Sector Erase Timer

After completion of the initial sector erase command sequence, sector erase time-out begins. DQ3 will remain

low until the time-out is completed. Data Polling and Toggle Bit are valid after the initial sector erase command

sequence.

If Data Polling or the Toggle Bit I indicates that a valid erase command has been written, DQ3 may be used to

determine whether the sector erase timer window is still open. If DQ3 is high (“1”) the internally controlled erase

cycle has begun. If DQ3 is low (“0”) , the device will accept additional sector erase commands. To insure 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 were high on the second status check, the command may not have

been accepted.

See “Hardware Sequence Flags Table” in “■ COMMAND DEFINITIONS” : Hardware Sequence Flags.

40

MBM29QM96DF-65/80

DQ²

Toggle Bit II

This toggle bit II, along with DQ⁶, can be used to determine whether the device is in the Embedded Erase

Algorithm or in Erase Suspend.

Successive reads from the erasing sector will cause DQ2 to toggle during the Embedded Erase Algorithm. If the

device is in the erase-suspended-read mode, successive reads from the erase-suspended sector will cause

DQ2 to toggle. When the device is in the erase-suspended-program mode, successive reads from the non-erase

suspended sector will indicate a logic “1” at the DQ2 bit.

DQ⁶is different from DQ2 in that DQ6 toggles only when the standard program or Erase, or Erase Suspend

Program operation is in progress. The behavior of these two status bits, along with that of DQ7, is summarized

as follows :

For example, DQ²and DQ6 can be used together to determine if the erase-suspend-read mode is in progress.

(DQ2 toggles while DQ6 does not.) See also “Toggle Bit Status Table” in “■ COMMAND DEFINITIONS” and

“DQ2 vs. DQ6” in “■ TIMING DIAGRAM”.

Furthermore DQ2 can also be used to determine which sector is being erased. At the erase mode, DQ2 toggles

if this bit is read from an erasing sector.

To operate toggle bit function properly, CE or OE must be high when bank address is changed.

Reading Toggle Bits DQ⁶/DQ²

Whenever the system initially begins reading toggle bit status, it must read DQ7 to DQ0 at least twice in a row

to determine whether a toggle bit is toggling. Typically a system would note and store the value of the toggle bit

after the first read. After the second read, the system would compare 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 to DQ0 on the following read cycle.

However, if, after the initial two read cycles, the system determines that the toggle bit is still toggling, 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 complete 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 DQ⁵has not

gone high. The system may continue to monitor the toggle bit and DQ5 through successive read cycles, deter-

mining 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. (Refer to “Toggle Bit Algorithm” in “■ FLOW CHART”.)

Toggle Bit Status Table

Mode

DQ⁷

DQ7

0

DQ⁶

DQ²

1

Program

Erase

Toggle

Toggle*

Erase-Suspend Read

(Erase-Suspended Sector)

1

Toggle

1*

Erase-Suspend Program

DQ⁷

Toggle

* : Successive reads from the erasing or erase-suspend sector will cause DQ²to toggle. Reading from

non-erase suspend sector address will indicate logic “1” at the DQ2 bit.

41

MBM29QM96DF-65/80

RY/BY (Ready/Busy Pin)

The device provides a RY/BY open-drain output pin as a way to indicate to the host system that Embedded

Algorithms are either in progress or have been completed. If output is low, the device is busy with either a program

or erase operation. If output is high, the device is ready to accept any read/program or erase operation. If the

device is placed in an Erase Suspend mode, RY/BY output will be high.

During programming, the RY/BY pin is driven low after the rising edge of the fourth write pulse. During an erase

operation, the RY/BY pin is driven low after the rising edge of the sixth write pulse. The RY/BY pin will indicate

a busy condition during RESET pulse. Refer to “RY/BY Timing Diagram during Program/Erase Operation Timing

Diagram” and “RESET, RY/BY Timing Diagram” in “■ TIMING DIAGRAM” for a detailed timing diagram. The

RY/BY pin is pulled high in standby mode.

Since this is an open-drain output, RY/BY pins can be tied together in parallel with a pull-up resistor to VCC.

Data Protection

The device is designed to offer protection against accidental erasure or programming caused by spurious system

level signals that may exist during power transitions. During power up device automatically resets internal state

machine to Read mode. Also, with its control register architecture, alteration of memory contents only occurs

after successful completion of specific multi-bus cycle command sequence.

Device also incorporates several features to prevent inadvertent write cycles resulting from V^CCpower-up and

power-down transitions or system noise.

Low V^CCWrite Inhibit

To avoid initiation of a write cycle during V^CCpower-up and power-down, a write cycle is locked out for VCC less

thanV^LKO(Min).IfVCC <VLKO,thecommandregisterisdisabledandallinternalprogram/erasecircuitsaredisabled.

Under this condition, the device will reset to the read mode. Subsequent writes will be ignored until the V^CClevel

is greater than VLKO. It is the users responsibility to ensure that the control pins are logically correct to prevent

unintentional writes when V^CCis above VLKO (Min).

If the Embedded Erase Algorithm is interrupted, there is possibility that the erasing sector(s) can not be used.

Write Pulse “Glitch” Protection

Noise pulses of less than 5 ns (typical) on OE, CE, or WE will not initiate a write cycle.

Logical Inhibit

Writing is 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

Power-up of the device with WE = CE = VIL and OE = VIH will not accept commands on the rising edge of WE.

The internal state machine is automatically reset to read mode on power-up.

42

MBM29QM96DF-65/80

■ ABSOLUTE MAXIMUM RATINGS

Value

Unit

Parameter

Symbol

Min

−55

−40

Max

+ 125

+ 85

Storage Temperature

Tstg

T^A

°C

Ambient Temperature with Power Applied

Voltage with Respect to Ground. All pins except

A⁹, OE, and RESET *^1,*²

VIN, VOUT

−0.5

VCC + 0.5

V

Power Supply Voltage *^1,*²

A9, OE, and RESET *^1,*³

WP/ACC *^1,*⁴

VCC, VCCQ

VIN

−0.5

+ 4.0

+ 13.0

+ 10.5

V

VACC

*1 : Voltage is defined on the basis of VSS = GND = 0V.

*2 : Minimum DC voltage on input or l/O pins is −0.5 V. During voltage transitions, inputs or I/O pins may undershoot

VSS to −2.0 V for periods of up to 20 ns. Maximum DC voltage on input or l/O pins is VCC + 0.5 V. During voltage

transitions,inputs may overshoot to VCC + 2.0 V for periods of up to 20 ns.

*3 : Minimum DC input voltage on A9, OE, and RESET pins is −0.5 V. During voltage transitions, A9, OE, and RESET

pins may undershoot VSS to −2.0 V for periods of up to 20 ns. Voltage difference between input and supply voltage

(VIN – VCC) does not exceed + 9.0 V. Maximum DC input voltage on A9, OE and RESET pins is + 13.0 V which

may overshoot to + 14.0 V for periods of up to 20 ns.

*4 : Minimum DC input voltage on WP/ACC pins is −0.5 V. During voltage transitions, WP/ACC pin may undershoot

VSS to −2.0 V for periods of up to 20 ns. Maximum DC input voltage on WP/ACC pin is + 10.5 V which may

overshoot to + 12.0 V for periods of up to 20 ns when VCC is applied.

WARNING: Semiconductor devices can be permanently damaged by application of stress (voltage, current,

temperature, etc.) in excess of absolute maximum ratings. Do not exceed these ratings.

■ RECOMMENDED OPERATING RANGES

Value

Parameter

Symbol

Part No.

Unit

Min

−40

Max

+ 85

+ 3.1

VCC

Ambient Temperature

Power Supply Voltage *

T^A

MBM29QM96DF-65/80

MBM29QM96DF-65

MBM29QM96DF-80

°C

V

V^CC

+ 2.7

+ 1.65

V

V^CCQSupply Voltage *

VCCQ

VCC

V

* : Voltage is defined on the basis of VSS = GND = 0 V.

WARNING: The recommended operating conditions are required in order to ensure the normal operation of the

semiconductor device. All of the device’s electrical characteristics are warranted when the device is

operated within these ranges.

Always use semiconductor devices within their recommended operating conditionranges. Operation

outside these ranges may adversely affect reliability and could result in device failure.

No warranty is made with respect to uses, operating conditions, or combinations not represented on

the data sheet. Users considering application outside the listed conditions are advised to contact their

FUJITSU representatives beforehand.

43

MBM29QM96DF-65/80

■ MAXIMUM OVERSHOOT / MAXIMUM UNDERSHOOT

20 ns

+0.8 V

−0.5 V

−2.0 V

20 ns

Figure 1 Maximum Undershoot Waveform

20 ns

VCC + 2.0 V

V^CC+ 0.5 V

+ 2.0 V

20 ns

Figure 2 Maximum Overshoot Waveform 1

20 ns

+ 14.0 V

+ 13.0 V

VCC + 0.5 V

20 ns

Note: This waveform is applied for A⁹, OE, and RESET.

Figure 3 Maximum Overshoot Waveform 2

44

MBM29QM96DF-65/80

■ DC CHARACTERISTICS

Value

Unit

Sym-

bol

Parameter

Conditions

Min

−1.0

Typ

—

Max

+ 1.0

Input Leakage Current

Output Leakage Current

I^LI

VIN = VSSQ to VCCQ, VCC = VCC Max

VOUT = VSSQ to VCCQ, VCC = Vcc Max

µA

I^LO

—

A⁹, OE, RESET Inputs Leakage

Current

VCC = VCC Max,

A9, OE, RESET = 12.5 V

ILIT

ILIA

—

35

20

µA

WP/ACC Accelerated Program

Current

VCC = VCC Max,

WP/ACC = VACC Max

mA

V^CCActive Current *¹

(Initial/Random Read)

CE = VIL, OE = VIH, f = 10 MHz

CE = VIL, OE = VIH, f = 5 MHz

CE = VIL, OE = VIH

—

45

20

25

mA

ICC1

ICC2

V^CCActive Current *²

VCC = VCC Max, CE = VCCQ ±0.3 V,

RESET = VCCQ ±0.3 V,

V^CCCurrent (Standby)

ICC3

—

1

5

µA

WP/ACC = VCCQ ±0.3 V

VCC = VCC Max,

RESET = VSSQ ±0.3 V

V^CCCurrent (Standby,Reset)

V^CCCurrent (Page Mode) *³

ICC4

ICC5

ICC6

—

1

—

1

5

µA

mA

µA

CE = VIL, OE = VIH, f = 40 MHz

V^CCCurrent

(Automatic Sleep Mode) *⁴

VCC = VCC Max, CE = VSS ±0.3 V,

VIN = VCCQ ±0.3 V or VSSQ ±0.3 V

V^CCActive Current*⁵

(Read-While-Program)

V^CCActive Current*⁵

(Read-While-Erase)

ICC7

ICC8

CE = VIL, OE = VIH

—

45

mA

V^CCActive Current*⁵

(Erase-Suspend-Program)

ICC9

V^IL

CE = VIL, OE = VIH

—

25

mA

V

Input Low Voltage

—

−0.5

0.6

VCCQ +

0.3

Input High Voltage

V^IH

VCCQ − 0.2

V

Voltage for Auteselect and Sector

Protection(A⁹, OE, RESET)*⁶

VID

—

11.5

8.5

12.0

9.0

12.5

V

Voltage for WP/ACC Sectoer

Protection/Unprotection and

Program Acceleration

V^ACC

9.5

V^OL1

V^OL2

V^OH1

V^OH2

VLKO

IOL = 4.0 mA, VCC = VCC Min

IOL = 100 µA, VCC = VCC Min

IOH = –2.0 mA, VCC = VCC Min

IOH = –100 µA, VCC = VCC Min

—

0.3

0.1

—

V

Output Low Voltage

VCCQ − 0.3

VCCQ − 0.2

2.3

—

Output High Voltage

—

Low V^CCLock-Out Voltage

2.4

2.5

*1 : lCC current listed includes both the DC operating current and the frequency dependent component.

*2 : lCC active while Embedded Algorithm (Program or Erase) is in progress.

*3 : Addresses except A2, A1, A0 are fixed.

*4 : Automatic sleep mode enables the low power mode when address remain stable for 150 ns.

*5 : Embedded Algorithm (Program or Erase) is in progress.(@5 MHz)

*6 : V^IDis only for Sector Group Protection operation and Autoselect mode.

45

MBM29QM96DF-65/80

■ AC CHARACTERISTICS

• Read Only Operations Characteristics

Value *

Symbol

JEDEC Standard

Parameter

Condition

Unit

65

80

Min

Max

Min

Max

Read Cycle Time

t^AVAV

t^AVQV

—

tRC

tACC

t^PRC

t^PACC

—

65

—

65

—

25

80

—

ns

CE = VIL

OE = VIL

Address to Output Delay

Page Read Cycle Time

—

25

—

30

—

80

—

30

—

CE = VIL

OE = VIL

Page Address to Output Delay

—

Chip Enable to Output Delay

Output Enable to Output Delay

Chip Enable to Output High-Z

Output Enable to Output High-Z

t^ELQV

t^GLQV

t^EHQZ

t^GHQZ

tCE

tOE

tDF

OE = VIL

—

65

25

—

80

30

ns

—

Output Hold Time From Address,

CE or OE,

Whichever Occurs First

tAXQX

tOH

—

4

—

4

—

ns

RESET Pin Low to Read Mode

—

tREADY

—

20

—

20

Note : *Test Conditions:

Output Load: V^CCQ= 1.65 V to 2.7 V :30pF

V^CCQ= 2.7 V to 3.1 V : 1 TTL gate and 30pF (MBM29QM96DF-65)

1 TTL gate and 100pF (MBM29QM96DF-80)

Input rise and fall times: 5 ns

Input pulse levels: 0.0 V or V^CCQ

Timing measurement reference level

Input:

0.5 × VCCQ

Output: 0.5 × VCCQ

46

MBM29QM96DF-65/80

• Write (Erase/Program) Operations

Value

Symbol

JEDEC Standard Min

Parameter

65

Typ

—

80

Typ

—

Unit

Max

—

MIn

80

0

Max

—

Write Cycle Time

t^AVAV

t^AVWL

tWC

tAS

65

0

ns

Address Setup Time

—

Address Setup Time to OE Low

During Toggle Bit Polling

—

tWLAX

—

tASO

tAH

12

45

0

—

12

45

0

—

ns

Address Hold Time

Address Hold Time from CE or OE

High During Toggle Bit Polling

tAHT

Data Setup Time

Data Hold Time

t^DVWH

t^WHDX

tDS

tDH

35

0

—

35

0

—

ns

Read

0

Output

Enable Hold

Time

—

t^OEH

Toggle and Data

Polling

10

—

10

—

ns

CE High During Toggle Bit Polling

OE High During Toggle Bit Polling

Read Recover Time Before Write

CE Setup Time

—

tCEPH

tOEPH

tGHWL

tGHEL

tCS

20

0

—

6

—

20

0

—

6

—

ns

µs

s

tGHWL

t^GHEL

tELWL

tWLEL

tWHEH

tEHWH

t^WLWH

tELEH

tWHWL

tEHEL

t^WHWH1

tWHWH2

—

0

WE Setup Time

tWS

0

CE Hold Time

tCH

0

WE Hold Time

tWH

0

Write Pulse Width

tWP

35

30

—

50

500

4

35

30

—

50

500

4

CE Pulse Width

tCP

Write Pulse Width High

CE Pulse Width High

Word Programming Operation

Sector Erase Operation*¹

VCC Setup Time

tWPH

tCPH

tWHWH1

tWHWH2

tVCS

0.5

—

0.5

—

µs

ns

µs

Rise Time to V^ID*²

—

tVIDR

tVACCR

tVLHT

tWPP

tOESP

tCSP

Rise Time to VACC*³

—

Voltage Transition Time *²

Write Pulse Width*²

—

100

4

100

4

OE Setup Time to WE Active*²

CE Setup Time to WE Active*²

—

4

(Continued)

47

MBM29QM96DF-65/80

(Continued)

Value

Symbol

JEDEC Standard Min

Parameter

65

Typ

—

80

Typ

—

Unit

Max

Min

0

Max

—

Recover Time from RY/BY

RESET Pulse Width

—

tRB

tRP

0

—

ns

500

—

500

—

RESET High Level Period Before

Read

—

tRH

tBUSY

tEOE

200

—

90

65

200

—

90

80

ns

Program/Erase Valid to RY/BY

Delay

Delay Time from Embedded

Output Enable

—

Erase Time-out Time

—

t^TOW

50

—

50

—

µs

Erase Suspend Transition Time

tSPD

20

*1 : This does not include the preprogramming time.

*2 : This timing is for Sector Group Protection operation.

*3 : This timing is limited for Accelerated Program operation only.

48

MBM29QM96DF^-65/80

■ ERASE AND PROGRAMMING PERFORMANCE

Value

Parameter

Unit

Comments

Min

Typ

Max

Excludes programming time

prior to erase

Sector Erase Time

—

0.5

2.0

s

Word Programming Time

Chip Programming Time

Erase/Program Cycle

—

6

100

150

—

µs

s

Excludes system-level overhead

—

37.7

—

100,000

cycle

Note : Typical Erase Conditions: TA = +25 °C, VCC = 2.9 V

Typical Program Conditions: TA = +25 °C, VCC = 2.9 V, Data = Checker

■ FBGA PIN CAPACITANCE

Parameter

Input Capacitance

Symbol

C^IN

Test Setup

Typ

7.0

Max

10.0

12.0

11.0

12.0

Unit

pF

VIN = 0

Output Capacitance

Control Pin Capacitance

WP/ACC Pin Capacitance

C^OUT

C^IN2

VOUT = 0

VIN = 0

6.0

pF

7.5

pF

CIN3

10.0

pF

Note : Test Conditions: TA = +25 °C, f = 1.0 MHz

49

MBM29QM96DF-65/80

■ SWITCHING WAVEFORMS

• Key to Switching Waveforms

WAVEFORM

INPUTS

OUTPUTS

Must Be

Steady

Will Be

Steady

May

Change

from H to L

Will Be

Change

from H to L

May

Change

from L to H

Will Be

Change

from L to H

“H” or “L”:

Any Change

Permitted

Changing,

State

Unknown

Does Not

Apply

Center Line is

High-

Impedance

“Off” State

tRC

Address

Address Stable

tACC

CE

OE

tOE

tDF

tOEH

WE

tCE

tOH

High-Z

Outputs

Output Valid

Read Operation Timing Diagram

50

MBM29QM96DF-65/80

Same page Addresses

A22 to A3

A2 to A0

Aa

Ab

Ac

Ad

Ae

Af

Ag

Ah

tRC

t^PRC

tPRC

tACC

tCE

CE

tOEH

tOE

OE

WE

t^DF

tPACC

tOH

tPACC

tOH

tPACC

tOH

tPACC

tOH

tPACC

tOH

tPACC

tOH

t^OH

Da

tOH

High-Z

Db

Dc

Dd

De

Df

Dg

Dh

Output

Page Read Operation Timing Diagram

tRC

Address

Address Stable

tACC

CE

tRH

tRP

tRH

tCE

RESET

Outputs

tOH

High-Z

Outputs Valid

Hardware Reset/Read Operation Timing Diagram

51

MBM29QM96DF-65/80

3rd Bus Cycle

Data Polling

555h

PA

Address

tWC

tRC

tAS

tAH

CE

tCH

tCS

tCE

OE

tOE

tWP

tWPH

tGHWL

tWHWH1

WE

tDF

tOH

tDS

tDH

PD

DOUT

A0h

DQ7

Data

Notes : • PA is address of the memory location to be programmed.

• PD is data to be programmed at word address.

• DQ7 is the output of the complement of the data written to the device.

• DOUT is the output of the data written to the device.

• Figure indicates last two bus cycles out of four bus cycle sequence.

Alternate WE Controlled Program Operation Timing Diagram

52

MBM29QM96DF-65/80

3rd Bus Cycle

Data Polling

PA

555h

Address

WE

tWC

tAH

tAS

tWS

tWH

OE

CE

tCP

tCPH

tWHWH1

tGHEL

tDS

tDH

PD

D^OUT

DQ7

A0h

Data

Notes : • PA is address of the memory location to be programmed.

• PD is data to be programmed at word address.

• DQ7 is the output of the complement of the data written to the device.

• DOUT is the output of the data written to the device.

• Figure indicates last two bus cycles out of four bus cycle sequence.

Alternate CE Controlled Program Operation Timing Diagram

53

MBM29QM96DF-65/80

2AAh

555h

SA*

2AAh

Address

555h

tWC

tAS

tAH

CE

tCS

tCH

OE

tWP

tWPH

tGHWL

WE

tDS

tDH

10h for Chip Erase

10h/

30h

AAh

55h

80h

55h

Data

tVCS

VCC

* : SA is the sector address for Sector Erase. Address = 555h for Chip Erase.

Chip/Sector Erase Operation Timing Diagram

54

MBM29QM96DF-65/80

CE

tCH

tOE

tDF

OE

tOEH

WE

tCE

*

High-Z

DQ7 =

Data

DQ7

Valid Data

tWHWH1 or 2

High-Z

DQ6 to DQ0

DQ⁶to DQ0 = Output Flag

Valid Data

tEOE

* : DQ7 = Valid Data (The device has completed the Embedded operation.)

Data Polling during Embedded Algorithm Operation Timing Diagram

55

MBM29QM96DF-65/80

Address

CE

tAHT tASO

tAHT tAS

tCEPH

WE

tOEPH

tOEH

OE

tOE

tCE

tDH

*

Stop

Output

Valid

Toggle

Data

Toggle

Data

Toggle

Data

DQ 6/DQ2

RY/BY

Data

Toggling

tBUSY

* : DQ6 stops toggling (The device has completed the Embedded operation.)

AC Waveforms for Toggle Bit I during Embedded Algorithm Operations

56

MBM29QM96DF-65/80

Read

Command

Read

Command

Read

tRC

tWC

tRC

tWC

tRC

BA2

(PA)

BA2

(PA)

Address

CE

BA1

(555h)

tACC

tCE

tAS

tAH

tAHT

tOE

tCEPH

OE

WE

DQ

tDF

tGHWL

tOEH

tWP

tDS

tDH

tDF

Valid

Output

Valid

Output

Valid

Output

Status

Intput

(A0H)

(PD)

Note : This is example of Read for Bank 1 and Embedded Algorithm (program) for Bank 2.

BA1 : Address corresponding to Bank 1

BA2 : Address corresponding to Bank 2

Bank-to-Bank Read / Write(Program and Erase) Timing Diagram

Enter

Embedded

Erase

Suspend

Enter Erase

Suspend Program

Erase

Resume

Erase Suspend

Read

Erase Suspend

Read

WE

Erase

Suspend

Program

Erase

Complete

DQ6

DQ2 *

Toggle

DQ2 and DQ6

with OE or CE

* : DQ2 is read from the erase-suspended sector.

DQ²vs. DQ6

57

MBM29QM96DF-65/80

CE

Rising edge of the last WE signal

WE

Entire program or

erase operations

RY/BY

tBUSY

RY/BY Timing Diagram during Program/Erase Operation Timing Diagram

WE

RESET

tRP

tRB

RY/BY

tREADY

RESET, RY/BY Timing Diagram

58

MBM29QM96DF-65/80

Address

SPAX

SPAY

(A22 to

A12)

A6, A2, A0

A5, A4, A3, A1

V

ID

IH

A

9

t

VLHT

V

ID

IH

OE

t

VLHT

t

VLHT

t

WPP

WE

t

OESP

t

CSP

CE

01h

Data

t

OE

t

VCS

V

CC

SPAX : Sector Group Address to be protected

SPAY : Next Sector Group Address to be protected

Sector Group Protection Timing Diagram

59

MBM29QM96DF-65/80

VCC

tVIDR

tVCS

tVLHT

VID

VIH

RESET

CE

WE

tVLHT

Program or Erase Command Sequence

Unprotection period

RY/BY

Temporary Sector Group Unprotection Timing Diagram

60

MBM29QM96DF-65/80

VCC

tVCS

VID

VIH

tVLHT

RESET

tWC

tVIDR

Address

SGAX

SGAY

A6, A2, A0

A5, A4,

A3, A1

CE

OE

TIME-OUT

tWP

WE

60h

40h

01h

60h

Data

tOE

SGAX : Sector Group Address to be protected

SGAY : Next Sector Group Address to be protected

TIME-OUT : Time-Out window = 250 µs (Min)

Extended Sector Group Protection Timing Diagram

61

MBM29QM96DF-65/80

VCC

tVACCR

tVCS

tVLHT

VACC

VIH

WP/ACC

CE

WE

tVLHT

Program Command Sequence

Acceleration period

Accelerated Program Timing Diagram

62

MBM29QM96DF-65/80

EMBEDDED ALGORITHM

Start

Write Program Command

Sequence

(See Below)

Data Polling Device

Embedded

Program

Algorithm

in progress

No

Verify Data

?

Yes

No

Increment Address

Last Address

?

Yes

Programming Completed

Program Command Sequence (Address/Command):

555h/AAh

2AAh/55h

555h/A0h

Program Address/Program Data

Embedded Program^TMAlgorithm

63

MBM29QM96DF-65/80

EMBEDDED ALGORITHM

Start

Write Erase Command

Sequence

(See Below)

Data Polling or Toggle Bit

from Device

Embedded

Erase

Algorithm

in progress

No

Data = FFh

?

Yes

Erasure Completed

Individual Sector/Multiple Sector

Erase Command Sequence

(Address/Command):

Chip Erase Command Sequence

(Address/Command):

555h/AAh

2AAh/55h

555h/80h

555h/AAh

2AAh/55h

555h/10h

555h/AAh

2AAh/55h

555h/80h

555h/AAh

2AAh/55h

Sector Address/30h

Additional sector

erase commands

are optional.

Sector Address/30h

Embedded Erase^TMAlgorithm

64

MBM29QM96DF-65/80

VA = Address for programming

= Any of the sector addresses

within the sector being erased

during sector erase or multiple

sector erase operation.

Start

Read

DQ⁷to DQ0

Addr. = VA

= Any of the sector addresses

within the sector not being

protected during chip erase

operation.

Yes

DQ7 = Data?

No

DQ5 = 1?

Yes

Read

DQ⁷to DQ0

Addr. = VA

Yes

DQ7 = Data?

*

No

Fail

Pass

* : DQ7 is rechecked even if DQ5 = “1” because DQ7 may change simultaneously with DQ5.

Data Polling Algorithm

65

MBM29QM96DF^-65/80

VA = Bank address being excuted

Start

Embeded Algorithm

Read

DQ7 to DQ0

Addr. = VA

1

*

Read

DQ7 to DQ0

Addr. = VA

DQ6 =

No

Toggle?

Yes

No

DQ5 = 1?

Yes

*1, *2

*^1,*2

Read DQ7 to DQ0

Addr. = VA

Read DQ7 to DQ0

Addr. = VA

No

DQ6 =

Toggle?

Yes

Program/Erase

Operation Not

Complete, Write

Reset Command

Program/Erase

Operation Complete

*1 : Read toggle bit twice to determine whether it is toggling.

*2 : Recheck toggle bit because it may stop toggling as DQ5 changes to “1”.

Toggle Bit Algorithm

66

MBM29QM96DF-65/80

Start

Setup Sector Group Addr.

(A22, A21, A20, A19, A18, A17,

A16, A15, A14, A13, A12)

PLSCNT = 1

OE

CE

=

VID, A9

=

VID,

VIH

=

VIL, RESET

=

A6 = A2 = A0 = VIL,

A⁵= A4 = A3 = A1 = VIH

Activate WE Pulse

Time out 100 µs

Increment PLSCNT

WE = V IH, CE = OE = V IL

(A9 should remain VID)

Read from Sector Group

(Addr. = SPA,

A⁶= A2 = A0 = VIL,

A5 = A4 = A3 = A1 = VIH )

No

PLSCNT = 25?

Yes

Data = 01h?

Yes

Remove VID from A9

Write Reset Command

Protect Another Sector

Group ?

No

Device Failed

Remove VID from A9

Write Reset Command

Sector Group Protection

Completed

Sector Group Protection Algorithm

67

MBM29QM96DF-65/80

Start

RESET = VID

*1

Perform Erase or

Program Operation

RESET = VIH

Temporary Sector Group

Unprotection Completed

*2

*1 : All protected sector groups are unprotected.

*2 : All previously protected sector groups are reprotected once again.

Temporary Sector Group Unprotection Algorithm

68

MBM29QM96DF-65/80

Start

RESET = VID

Wait to 4 µs

Device is Operating in

Temporary Sector Group

Unprotection Mode

No

Extended Sector Group

Protection Entry?

Yes

To Setup Sector Group Protection

Write XXXh/60h

PLSCNT = 1

To Protect Sector Group

Write 60h to SGA

A

6

= A

4

2

= A

0

= VIL

,

(

)

A

5

= A = A

3

= A

1

=VIH

Time out 250 µs

To Verify Sector Group Protection

Write 40h to SGA

Increment PLSCNT

A

6

= A

2

= A

0

= VIL

,

(

)

A5

= A4 = A

3

= A

1=VIH

Read from Sector Group Address

(Addr. = SGA,

No

A5

=⁶A

4

3

=⁰A

1

=^ILVIH

)

A

= A

2

= A

= A = V

,

Setup Next SGA

No

Data = 01h?

PLSCNT = 25?

Yes

Protect Other Sector

Group?

Remove VID from RESET

Write Reset Command

No

Remove VID from RESET

Write Reset Command

Device Failed

Sector Group Protection

Completed

Extended Sector Group Protection Algorithm

69

MBM29QM96DF-65/80

FAST MODE ALGORITHM

Start

555h/AAh

2AAh/55h

Set Fast Mode

555h/20h

XXXh/A0h

Program Address/Program Data

Data Polling Device

In Fast Program

No

Verify Data?

Yes

No

Last Address

?

Increment Address

Yes

Programming Completed

BA/90h

Reset Fast Mode

XXXh/F0h

Embedded Program Algorithm for Fast Mode

70

MBM29QM96DF-65/80

Password Mode Choice Method

Start

Password Program

Password Verify

Password Protection

Mode

DQ⁰= 1?

Reset Command

Bit Program

No (Time out)

Reset Command

DQ⁰= 0?

Yes

Reset Command

Program Complete

Password Sector Protect Algorithm

71

MBM29QM96DF-65/80

PPB Lock Clear in Password Mode

Start

Password Unlock

No (Time out)

RY/BY = H?

Yes

No

DPB/PPB/PPB Lock

Bit Status

DQ⁰= 1?

Reset Command

Password/Unlock

Complete

All PPB Erase

Reset Command

No (Time out)

DQ⁰= 0?

Yes

Program Complete

PPB Lock Bit Clear in Password Mode

72

MBM29QM96DF-65/80

■ ORDERING INFORMATION

Part Number

Package

Access Time (ns)

Remarks

MBM29QM96DF65PBT

MBM29QM96DF80PBT

65

80

80-ball plastic FBGA

(BGA-80P-M03)

MBM29QM96D

F

65

PBT

PACKAGE TYPE

PBT = 80-Ball Fine Pitch Ball Grid Array

Package (FBGA)

SPEED OPTION

See "Product Selector Guide".

DEVICE REVISION

DEVICE NUMBER/DESCRIPTION

MBM29QM96D

96Mega-bit (6M × 16-Bit) Page Mode Flash Memory

3.0V-only Read, Program, and Erase, Dual Boot

73

MBM29QM96DF-65/80

■ PACKAGE DIMENSIONS

80-ball plastic FBGA

(BGA-80P-M03)

1.08 –⁺0⁰.^.1¹3²

.043 –⁺.^.0⁰0⁰5⁵

12.00±0.10(.472±.004)

(Mounting height)

(Stand off)

B

0.38±0.10

(.015±.004)

0.40(.016)

REF

0.80(.031)

REF

8

7

6

5

4

3

2

1

A

9.00±0.10

(.354±.004)

0.10(.004)

S

(INDEX AREA)

D C B A

M

L

K

J

H

G

F

E

INDEX AREA

S

80-ø0.45±0.05

M

0.08(.003)

S A B

(80-ø.018±.002)

C

2003 FUJITSU LIMITED B80003S-c-1-1

Dimensions in mm (inches) .

Note : The values in parentheses are reference values.

74

MBM29QM96DF^-65/80

FUJITSU LIMITED

The contents of this document are subject to change without notice.

Customers are advised to consult with FUJITSU sales

representatives before ordering.

The information, such as descriptions of function and application

circuit examples, in this document are presented solely for the

purpose of reference to show examples of operations and uses of

Fujitsu semiconductor device; Fujitsu does not warrant proper

operation of the device with respect to use based on such

information. When you develop equipment incorporating the

device based on such information, you must assume any

responsibility arising out of such use of the information. Fujitsu

assumes no liability for any damages whatsoever arising out of

the use of the information.

Any information in this document, including descriptions of

function and schematic diagrams, shall not be construed as license

of the use or exercise of any intellectual property right, such as

patent right or copyright, or any other right of Fujitsu or any third

party or does Fujitsu warrant non-infringement of any third-party’s

intellectual property right or other right by using such information.

Fujitsu assumes no liability for any infringement of the intellectual

property rights or other rights of third parties which would result

from the use of information contained herein.

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 use accompanying 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 use requiring

extremely high reliability (i.e., submersible repeater and artificial

satellite).

Please note that Fujitsu will not be liable against you and/or any

third party for any claims or damages arising in connection with

above-mentioned 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 prior

authorization by Japanese government will be required for export

of those products from Japan.

F0306

FUJITSU LIMITED Printed in Japan


型号：	MBM29QM96DF80PBT
厂家：	SPANSION
描述：	Flash, 6MX16, 80ns, PBGA80, PLASTIC, FBGA-80 内存集成电路闪存
文件：	总76页 (文件大小：1024K)
中文：	中文翻译
下载：	下载PDF数据表文档文件

MBM29QM96DF80PBT [SPANSION]

相关型号：

MBM29QM96DF80PBT-E1

MBM29SL160BD

MBM29SL160BD-10

MBM29SL160BD-10PBT

MBM29SL160BD-10PFTN

MBM29SL160BD-10PFTR

MBM29SL160BD-12

MBM29SL160BD-12PBT

MBM29SL160BD-12PFTN

MBM29SL160BD-12PFTR

MBM29SL160TD

MBM29SL160TD-10