MX29LV065MTI-90_技术文档

MX29LV065M

64M-BIT SINGLE VOLTAGE 3V ONLY

UNIFORM SECTOR FLASH MEMORY

FEATURES

GENERAL FEATURES

• Low Power Consumption

• Single Power Supply Operation

- 2.7 to 3.6 volt for read, erase, and program opera-

tions

- Active read current: 18mA(typ.)

- Active write current: 50mA(typ.)

- Standby current: 20uA(typ.)

• Minimum 100,000 erase/program cycle

• 20-years data retention

• Configuration

- 8,388,608 x 8 byte structure

• Sector structure

- 64KB x 128

SOFTWARE FEATURES

• Sector Protection/Chip Unprotect

- Provides sector group protect function to prevent

program or erase operation in the protected sector

group

• Support Common Flash Interface (CFI)

- Flash device parameters stored on the device and

provide the host system to access.

• Program Suspend/Program Resume

- Suspend program operation to read other sectors

• Erase Suspend/Erase Resume

- Provides chip unprotect function to allow code

changes

- Provides temporary sector group unprotect function

for code changes in previously protected sector groups

• Secured Silicon Sector

- Suspends sector erase operation to read or program

other sectors

• Status Reply

- Provides a 256-byte area for code or data that can be

permanently protected

- Data# polling & Toggle bits provide detection of pro-

gram and erase operation completion

- Once this sector is protected, it is prohibited to pro-

gram or erase within the sector again

• Latch-up protected to 250mA from -1V to Vcc + 1V

• Low Vcc write inhibit is equal to or less than 1.5V

• Compatible with JEDEC standard

- Pin-out and software compatible to single power sup-

ply Flash

HARDWARE FEATURES

• Ready/Busy (RY/BY#) Output

- Provides a hardware method of detecting program

and erase operation completion

• Hardware Reset (RESET#) Input

- Provides a hardware method to reset the internal

state machine to read mode

PERFORMANCE

• High Performance

• ACC input

- ACC (high voltage) accelerates programming time

for higher throughput during system

- Fast access time: 90ns

- Page read time:25ns

- Sector erase time: 0.5s (typ.)

- Effective write buffer byte programming time: 11us

- 8 byte page read buffer

- 32 byte write buffer: reduces programming time for

multiple-byte updates

PACKAGE

• 48-pinTSOP

• All Pb-free devices are RoHS Compliant

GENERAL DESCRIPTION

The MX29LV065M is a 64-mega bit Flash memory orga-

nized as 8M bytes of 8 bits. MXIC's Flash memories

offer the most cost-effective and reliable read/write non-

volatile random access memory. The MX29LV065M is

packaged in 48-pinTSOP, 63-ball CSP. It is designed to

be reprogrammed and erased in system or in standard

EPROM programmers.

The standard MX29LV065M offers access time as fast

as 90ns, allowing operation of high-speed microproces-

sors without wait states. To eliminate bus contention,

the MX29LV065M has separate chip enable (CE#) and

P/N:PM1100

REV. 1.1, AUG. 15, 2005

1

MX29LV065M

output enable (OE#) controls.

fication of electrical erase are controlled internally within

the device.

MXIC's Flash memories augment EPROM functionality

with in-circuit electrical erasure and programming. The

MX29LV065M uses a command register to manage this

functionality.

AUTOMATIC SECTOR ERASE

The MX29LV065M is sector(s) erasable using MXIC's

Auto Sector Erase algorithm. Sector erase modes allow

sectors of the array to be erased in one erase cycle. The

Automatic Sector Erase algorithm automatically programs

the specified sector(s) prior to electrical erase. The tim-

ing and verification of electrical erase are controlled inter-

nally within the device.

MXIC Flash technology reliably stores memory contents

even after 100,000 erase and program cycles. The MXIC

cell is designed to optimize the erase and program

mechanisms. In addition, the combination of advanced

tunnel oxide processing and low internal electric fields

for erase and programming operations produces reliable

cycling. The MX29LV065M uses a 2.7V to 3.6V VCC

supply to perform the High Reliability Erase and auto

Program/Erase algorithms.

AUTOMATIC ERASE ALGORITHM

The highest degree of latch-up protection is achieved

with MXIC's proprietary non-epi process. Latch-up pro-

tection is proved for stresses up to 100 milliamperes on

address and data pin from -1V to VCC + 1V.

MXIC's Automatic Erase algorithm requires the user to

write commands to the command register using stan-

dard microprocessor write timings. The device will auto-

matically pre-program and verify the entire array. Then

the device automatically times the erase pulse width,

provides the erase verification, and counts the number

of sequences. A status bit toggling between consecu-

tive read cycles provides feedback to the user as to the

status of the programming operation.

AUTOMATIC PROGRAMMING

The MX29LV065M is byte/page programmable using the

Automatic Programming algorithm. The Automatic Pro-

gramming algorithm makes the external system do not

need to have time out sequence nor to verify the data

programmed.

Register contents serve as inputs to an internal state-

machine which controls the erase and programming cir-

cuitry. During write cycles, the command register inter-

nally latches address and data needed for the program-

ming and erase operations. During a system write cycle,

addresses are latched on the falling edge, and data are

latched on the rising edge of WE# .

AUTOMATIC PROGRAMMING ALGORITHM

MXIC's Automatic Programming algorithm require the user

to only write program set-up commands (including 2 un-

lock write cycle and A0H) and a program command (pro-

gram data and address). The device automatically times

the programming pulse width, provides the program veri-

fication, and counts the number of sequences. A status

bit similar to DATA# polling and a status bit toggling be-

tween consecutive read cycles, provide feedback to the

user as to the status of the programming operation.

MXIC's Flash technology combines years of EPROM

experience to produce the highest levels of quality, reli-

ability, and cost effectiveness. The MX29LV065M elec-

trically erases all bits simultaneously using Fowler-

Nordheim tunneling. The bytes are programmed by us-

ing the EPROM programming mechanism of hot elec-

tron injection.

During a program cycle, the state-machine will control

the program sequences and command register will not

respond to any command set. During a Sector Erase

cycle, the command register will only respond to Erase

Suspend command. After Erase Suspend is completed,

the device stays in read mode. After the state machine

has completed its task, it will allow the command regis-

ter to respond to its full command set.

AUTOMATIC CHIP ERASE

The entire chip is bulk erased using 50 ms erase pulses

according to MXIC's Automatic Chip Erase algorithm. The

Automatic Erase algorithm automatically programs the

entire array prior to electrical erase. The timing and veri-

P/N:PM1100

REV. 1.1, AUG. 15, 2005

2

MX29LV065M

PIN CONFIGURATION

48TSOP

NC

A22

A16

A15

A14

A13

A12

A11

A9

1

48

47

46

45

44

43

42

41

40

39

38

37

36

35

34

33

32

31

30

29

28

27

26

25

NC

2

NC

3

A17

GND

A20

A19

A10

Q7

4

5

6

7

8

9

Q6

A8

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

Q5

WE#

RESET#

ACC

RY/BY#

A18

A7

Q4

V

CC

MX29LV065M

VI/O

A21

Q3

Q2

A6

Q1

A5

Q0

A4

OE#

GND

CE#

A0

A3

A2

A1

NC

LOGIC SYMBOL

PIN DESCRIPTION

SYMBOL PIN NAME

23

8

A0~A22

Q0~Q7

CE#

Address Input

A0-A22

Data Inputs/Outputs

Q0-Q7

Chip Enable Input

WE#

Write Enable Input

OE#

Output Enable Input

CE#

RESET#

ACC

Hardware Reset Pin, Active Low

Programming Acceleration input

Read/Busy Output

OE#

RY/BY#

VCC

WE#

RESET#

ACC

+3.0V single power supply

Output Buffer Power

VI/O

RY/BY#

GND

Device Ground

NC

Pin Not Connected Internally

VI/O

P/N:PM1100

REV. 1.1, AUG. 15, 2005

3

MX29LV065M

BLOCK DIAGRAM

WRITE

STATE

CE#

OE#

CONTROL

INPUT

PROGRAM/ERASE

HIGH VOLTAGE

WE#

MACHINE

(WSM)

LOGIC

RESET#

STATE

FLASH

ARRAY

ADDRESS

LATCH

REGISTER

ARRAY

A0-A22

AND

SOURCE

HV

BUFFER

Y-PASS GATE

COMMAND

DATA

DECODER

PGM

SENSE

DATA

HV

AMPLIFIER

COMMAND

DATA LATCH

PROGRAM

DATA LATCH

Q0-Q7

I/O BUFFER

P/N:PM1100

REV. 1.1, AUG. 15, 2005

4

MX29LV065M

SECTOR (GROUP) STRUCTURE

Sector

A22

A21

A20

A19

A18

A17

A16

8-bit Address Range

(in hexadecimal)

000000-00FFFF

010000-01FFFF

020000-02FFFF

030000-03FFFF

040000-04FFFF

050000-05FFFF

060000-06FFFF

070000-07FFFF

080000-08FFFF

090000-09FFFF

0A0000-0AFFFF

0B0000-0BFFFF

0C0000-0CFFFF

0D0000-0DFFFF

0E0000-0EFFFF

0F0000-0FFFFF

100000-10FFFF

110000-11FFFF

120000-12FFFF

130000-13FFFF

140000-14FFFF

150000-15FFFF

160000-16FFFF

170000-17FFFF

180000-18FFFF

190000-19FFFF

1A0000-1AFFFF

1B0000-1BFFFF

1C0000-1CFFFF

1D0000-1DFFFF

1E0000-1EFFFF

1F0000-1FFFFF

200000-20FFFF

210000-21FFFF

220000-22FFFF

230000-23FFFF

240000-24FFFF

250000-25FFFF

SA0

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

SA1

SA2

SA3

SA4

SA5

SA6

SA7

SA8

SA9

SA10

SA11

SA12

SA13

SA14

SA15

SA16

SA17

SA18

SA19

SA20

SA21

SA22

SA23

SA24

SA25

SA26

SA27

SA28

SA29

SA30

SA31

SA32

SA33

SA34

SA35

SA36

SA37

P/N:PM1100

REV. 1.1, AUG. 15, 2005

5

MX29LV065M

Sector

A22

A21

A20

A19

A18

A17

A16

8-bit Address Range

(in hexadecimal)

260000-26FFFF

270000-27FFFF

280000-28FFFF

290000-29FFFF

2A0000-2AFFFF

2B0000-2BFFFF

2C0000-2CFFFF

2D0000-2DFFFF

2E0000-2EFFFF

2F0000-2FFFFF

300000-30FFFF

310000-31FFFF

320000-32FFFF

330000-33FFFF

340000-34FFFF

350000-35FFFF

360000-36FFFF

370000-37FFFF

380000-38FFFF

390000-39FFFF

3A0000-3AFFFF

3B0000-3BFFFF

3C0000-3CFFFF

3D0000-3DFFFF

3E0000-3EFFFF

3F0000-3FFFFF

400000-40FFFF

410000-41FFFF

420000-42FFFF

430000-43FFFF

440000-44FFFF

450000-45FFFF

460000-46FFFF

470000-47FFFF

480000-48FFFF

490000-49FFFF

4A0000-4AFFFF

4B0000-4BFFFF

4C0000-4CFFFF

4D0000-4DFFFF

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

SA72

SA73

SA74

SA75

SA76

SA77

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

P/N:PM1100

REV. 1.1, AUG. 15, 2005

6

MX29LV065M

Sector

A22

A21

A20

A19

A18

A17

A16

8-bit Address Range

(in hexadecimal)

4E0000-4EFFFF

4F0000-4FFFFF

500000-50FFFF

510000-51FFFF

520000-52FFFF

530000-53FFFF

540000-54FFFF

550000-55FFFF

560000-56FFFF

570000-57FFFF

580000-58FFFF

590000-59FFFF

5A0000-5AFFFF

5B0000-5BFFFF

5C0000-5CFFFF

5D0000-5DFFFF

5E0000-5EFFFF

5F0000-5FFFFF

600000-60FFFF

610000-60FFFF

620000-62FFFF

630000-63FFFF

640000-64FFFF

650000-65FFFF

660000-66FFFF

670000-67FFFF

680000-68FFFF

690000-69FFFF

6A0000-6AFFFF

6B0000-6BFFFF

6C0000-6CFFFF

6D8000-6DFFFF

6E0000-6EFFFF

6F8000-6FFFFF

700000-70FFFF

710000-71FFFF

720000-72FFFF

730000-73FFFF

740000-74FFFF

750000-75FFFF

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

SA103

SA104

SA105

SA106

SA107

SA108

SA109

SA110

SA111

SA112

SA113

SA114

SA115

SA116

SA117

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

P/N:PM1100

REV. 1.1, AUG. 15, 2005

7

MX29LV065M

Sectpr

A22

A21

A20

A19

A18

A17

A16

8-bit Address Range

(in hexadecimal)

760000-76FFFF

770000-77FFFF

780000-78FFFF

790000-79FFFF

7A0000-7AFFFF

7B0000-7BFFFF

7C0000-7CFFFF

7D0000-7DFFFF

7E0000-7EFFFF

7F0000-7FFFFF

SA118

SA119

SA120

SA121

SA122

SA123

SA124

SA125

SA126

SA127

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

0

1

Note: All sector groups are 64K bytes in size.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

8

MX29LV065M

MX29LV065M Sector Group Protection Address Table

Sector Group

SA0-SA3

A22-A18

00000

00001

00010

00011

00100

00101

00110

00111

01000

01001

01010

01011

01100

01101

01110

01111

10000

10001

10010

10011

10100

10101

10110

10111

11000

11001

11010

11011

11100

11101

11110

11111

SA4-SA7

SA8-SA11

SA12-SA15

SA16-SA19

SA20-SA23

SA24-SA27

SA28-SA31

SA32-SA35

SA36-SA39

SA40-SA43

SA44-SA47

SA48-SA51

SA52-SA55

SA56-SA59

SA60-SA63

SA64-SA67

SA68-SA71

SA72-SA75

SA76-SA79

SA80-SA83

SA84-SA87

SA88-SA91

SA92-SA95

SA96-SA99

SA100-SA103

SA104-SA107

SA108-SA111

SA112-SA115

SA116-SA119

SA120-SA123

SA124-SA127

P/N:PM1100

REV. 1.1, AUG. 15, 2005

9

MX29LV065M

Table 1. BUS OPERATION (1)

Operation

CE#

OE#

L

WE#

H

RESET#

ACC

X

Address

Q0~Q7

D_OUT

Read

L

H

A_IN

Write (Program/Erase)

Accelerated Program

Standby

L

H

L

H

X

A_IN

(Note 3)

High-Z

(Note 3)

L

H

L

H

V_HH

H

A_IN

VCC±0.3V

X

VCC±0.3V

X

Output Disable

Reset

L

X

L

H

L

X

Sector Group Protect

(Note 2)

H

L

V_ID

X

Sector Addresses,

A6=L,A3=L, A2=L,

A1=H,A0=L

Sector Addresses,

A6=H, A3=L, A2=L,

A1=H, A0=L

A_IN

Chip unprotect

(Note 2)

L

H

X

L

V_ID

X

(Note 3)

Temporary Sector

Group Unprotect

X

V_ID

Legend:

L=Logic LOW=V_IL, H=Logic High=V_IH, V_ID=12.0 ±0.5V, V_HH=12.0 ±0.5V, X=Don't Care, A_IN=Address IN, D_IN=Data

IN, D_OUT=Data OUT

Notes:

1. Address are A22:A0.Sector addresses are A22:A16.

2. The sector group protect and chip unprotect functions may also be implemented via programming equipment.See

the "Sector Group Protection and Chip Unprotect" section.

3. D_INor D_OUTas required by command sequence, Data# polling or sector protect algorithm (see Figure 15).

P/N:PM1100

REV. 1.1, AUG. 15, 2005

10

MX29LV065M

Table 2. AUTOSELECT CODES (High Voltage Method)

A22 A14

to to

A15 A10

A8

to

A5

to

A3

Description

CE# OE# WE#

A9

VID

A6

L

to A1

A2

A0

Q7 to Q0

A7

X

A4

X

Manufacturer ID

Cycle 1

L

H

X

L

H

L

C2h

7Eh

Cycle 2

X

L

X

H

L

H

13h

Cycle 3

H

L

00h

Sector Protection

Verification

Secured Silicon

Sector Indicator

Bit (Q7)

SA

L

01h (protected),

00h (unprotected)

90h

L

H

X

VID

X

L

X

L

H

(factory locked),

10h

(not factory locked)

Legend: L = Logic Low = VIL, H = Logic High = VIH, SA = Sector Address, X = Don't care.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

11

MX29LV065M

or sequences into the command register initiates device

operations. Table 1 defines the valid register command

sequences.Writing incorrect address and data values or

writing them in the improper sequence resets the device

to reading array data. Section has details on erasing a

sector or the entire chip, or suspending/resuming the erase

operation.

REQUIREMENTS FOR READING ARRAY

DATA

To read array data from the outputs, the system must

drive the CE# and OE# pins to VIL. CE# is the power

control and selects the device. OE# is the output control

and gates array data to the output pins.WE# should re-

main at VIH.

After the system writes the Automatic Select command

sequence, the device enters the Automatic Select mode.

The system can then read Automatic Select codes from

the internal register (which is separate from the memory

array) on Q7-Q0. Standard read cycle timings apply in

this mode. Refer to the Automatic Select Mode and Au-

tomatic Select Command Sequence section for more

information.

The internal state machine is set for reading array data

upon device power-up, or after a hardware reset. This

ensures that no spurious alteration of the memory con-

tent occurs during the power transition. No command is

necessary in this mode to obtain array data. Standard

microprocessor read cycles that assert valid address on

the device address inputs produce valid data on the de-

vice data outputs. The device remains enabled for read

access until the command register contents are altered.

ICC2 in the DC Characteristics table represents the ac-

tive current specification for the write mode. The "AC

Characteristics" section contains timing specification

table and timing diagrams for write operations.

PAGE MODE READ

The MX29LV065M offers "fast page mode read" func-

tion. This mode provides faster read access speed for

random locations within a page. The page size of the

device is 8 bytes. The appropriate page is selected by

the higher address bits A-1~A1.This is an asynchronous

operation;the microprocessor supplies the specific word

location.

WRITE BUFFER

Write Buffer Programming allows the system to write a

maximum of 32 bytes in one programming operation.This

results in faster effective programming time than the stan-

dard programming algorithms.See "Write Buffer" for more

information.

The system performance could be enhanced by initiating

1 normal read and 7 fast page read. When CE# is

deasserted and reasserted for a subsequent access, the

access time is tACC or tCE. Fast page mode accesses

are obtained by keeping the "read-page addresses" con-

stant and changing the "intra-read page" addresses.

ACCELERATED PROGRAM OPERATION

The device offers accelerated program operations through

the ACC function. This is one of two functions provided

by the ACC pin. This function is primarily intended to

allow faster manufacturing throughput at the factory.

WRITING COMMANDS/COMMAND SE-

QUENCES

If the system asserts VHH on this pin, the device auto-

matically enters the aforementioned Unlock Bypass

mode, temporarily unprotects any protected sectors, and

uses the higher voltage on the pin to reduce the time

required for program operations. The system would use

a two-cycle program command sequence as required by

the Unlock Bypass mode. RemovingVHH from the ACC

pin must not be at VHH for operations other than accel-

erated programming, or device damage may result.

To program data to the device or erase sectors of memory,

the system must driveWE# and CE# toVIL, and OE# to

VIH.

An erase operation can erase one sector, multiple sec-

tors, or the entire device. Table indicates the address

space that each sector occupies. A "sector address"

consists of the address bits required to uniquely select a

sector.The "Writing specific address and data commands

P/N:PM1100

REV. 1.1, AUG. 15, 2005

12

MX29LV065M

but not within VSS±0.3V, the standby current will be

greater.

STANDBY MODE

When using both pins of CE# and RESET#, the device

enter CMOS Standby with both pins held atVCC ±0.3V.

If CE# and RESET# are held at VIH, but not within the

range ofVCC ±0.3V, the device will still be in the standby

mode, but the standby current will be larger.During Auto

Algorithm operation,Vcc active current (ICC2) is required

even CE# = "H" until the operation is completed. The

device can be read with standard access time (tCE) from

either of these standby modes, before it is ready to read

data.

The RESET# pin may be tied to system reset circuitry.

A system reset would that also reset the Flash memory,

enabling the system to read the boot-up firmware from

the Flash memory.

If RESET# is asserted during a program or erase

operation, the RY/BY# pin remains a "0" (busy) until the

internal reset operation is complete, which requires a time

of tREADY (during Embedded Algorithms).The system

can thus monitor RY/BY# to determine whether the reset

operation is complete. If RESET# is asserted when a

program or erase operation is completed within a time of

tREADY (not during Embedded Algorithms).The system

can read data tRH after the RESET# pin returns to VIH.

AUTOMATIC SLEEP MODE

The automatic sleep mode minimizes Flash device en-

ergy consumption.The device automatically enables this

mode when address remain stable for tACC+30ns. The

automatic sleep mode is independent of the CE#, WE#,

and OE# control signals. Standard address access tim-

ings provide new data when addresses are changed.While

in sleep mode, output data is latched and always avail-

able to the system. ICC4 in the DC Characteristics table

represents the automatic sleep mode current specifica-

tion.

Refer to the AC Characteristics tables for RESET#

parameters and to Figure 3 for the timing diagram.

SECTOR GROUP PROTECT OPERATION

The MX29LV065M features hardware sector group pro-

tection. This feature will disable both program and erase

operations for these sector group protected. In this de-

vice, a sector group consists of four adjacent sectors

which are protected or unprotected at the same time.To

activate this mode, the programming equipment must force

VID on address pin A9 and control pin OE#, (suggest

VID = 12V) A6 = VIL and CE# = VIL. (see Table 2) Pro-

gramming of the protection circuitry begins on the falling

edge of the WE# pulse and is terminated on the rising

edge. Please refer to sector group protect algorithm and

waveform.

OUTPUT DISABLE

With the OE# input at a logic high level (VIH), output

from the devices are disabled.This will cause the output

pins to be in a high impedance state.

RESET# OPERATION

MX29LV065M also provides another method.Which re-

quiresVID on the RESET# only.This method can be imple-

mented either in-system or via programming equipment.

This method uses standard microprocessor bus cycle tim-

ing.

The RESET# pin provides a hardware method of resetting

the device to reading array data.When the RESET# pin

is driven low for at least a period of tRP, the device

immediately terminates any operation in progress,

tristates all output pins, and ignores all read/write

commands for the duration of the RESET# pulse. The

device also resets the internal state machine to reading

array data.The operation that was interrupted should be

reinitiated once the device is ready to accept another

command sequence, to ensure data integrity

To verify programming of the protection circuitry, the pro-

gramming equipment must forceVID on address pin A9

( with CE# and OE# at VIL and WE# at VIH). When

A1=1, it will produce a logical "1" code at device output

Q0 for a protected sector. Otherwise the device will pro-

duce 00H for the unprotected sector. In this mode, the

addresses, except for A1, are don't care. Address loca-

tions with A1 = VIL are reserved to read manufacturer

and device codes. (Read Silicon ID)

Current is reduced for the duration of the RESET# pulse.

When RESET# is held at VSS±0.3V, the device draws

CMOS standby current (ICC4).If RESET# is held atVIL

P/N:PM1100

REV. 1.1, AUG. 15, 2005

13

MX29LV065M

It is also possible to determine if the group is protected

in the system by writing a Read Silicon ID command.

Performing a read operation with A1=VIH, it will produce

a logical "1" at Q0 for the protected sector.

the local CPU alters memory contents. As such, manu-

facturer and device codes must be accessible while the

device resides in the target system. PROM program-

mers typically access signature codes by raising A9 to

a high voltage. However, multiplexing high voltage onto

address lines is not generally desired system design prac-

tice.

CHIP UNPROTECT OPERATION

The MX29LV065M also features the chip unprotect mode,

so that all sectors are unprotected after chip unprotect

is completed to incorporate any changes in the code.It is

recommended to protect all sectors before activating chip

unprotect mode.

MX29LV065M provides hardware method to access the

silicon ID read operation.Which method requiresVID on

A9 pin, VIL on CE#, OE#, A6, and A1 pins.Which apply

VIL on A0 pin, the device will output MXIC's manufac-

ture code. Which apply VIH on A0 pin, the device will

output MX29LV065M device code.

To activate this mode, the programming equipment must

force VID on control pin OE# and address pin A9. The

CE# pins must be set at VIL. Pins A6 must be set to

VIH.(seeTable 2) Refer to chip unprotect algorithm and

waveform for the chip unprotect algorithm. The unprotect

mechanism begins on the falling edge of the WE# pulse

and is terminated on the rising edge.

VERIFY SECTOR GROUP PROTECT STATUS

OPERATION

MX29LV065M provides hardware method for sector group

protect status verify. Which method requires VID on A9

pin, VIH on WE# and A1 pins, VIL on CE#, OE#, A6, and

A0 pins, and sector address on A16 to A22 pins. Which

the identified sector is protected, the device will output

01H.Which the identified sector is not protect, the device

will output 00H.

MX29LV065M also provides another method.Which re-

quiresVID on the RESET# only.This method can be imple-

mented either in-system or via programming equipment.

This method uses standard microprocessor bus cycle tim-

ing.

It is also possible to determine if the chip is unprotect in

the system by writing the Read Silicon ID command.

Performing a read operation with A1=VIH, it will produce

00H at data outputs (Q0-Q7) for an unprotect sector.It is

noted that all sectors are unprotected after the chip

unprotect algorithm is completed.

DATA PROTECTION

The MX29LV065M is designed to offer protection against

accidental erasure or programming caused by spurious

system level signals that may exist during power transi-

tion. During power up the device automatically resets

the state machine in the Read mode. In addition, with its

control register architecture, alteration of the memory

contents only occurs after successful completion of spe-

cific command sequences. The device also incorporates

several features to prevent inadvertent write cycles re-

sulting fromVCC power-up and power-down transition or

system noise.

TEMPORARY SECTOR GROUP UNPROTECT

OPERATION

This feature allows temporary unprotect of previously

protected sector to change data in-system.The Tempo-

rary Sector Unprotect mode is activated by setting the

RESET# pin toVID(11.5V-12.5V). During this mode, for-

merly protected sectors can be programmed or erased

as unprotect sector. Once VID is remove from the RE-

SET# pin, all the previously protected sectors are pro-

tected again.

SECURED SILICON SECTOR

The MX29LV065M features a OTP memory region where

the system may access through a command sequence

to create a permanent part identification as so called

Electronic Serial Number (ESN) in the device.Once this

region is programmed, any further modification on the re-

gion is impossible. The secured silicon sector is a 256

bytes in length, and uses a Secured Silicon Sector Indi-

SILICON ID READ OPERATION

Flash memories are intended for use in applications where

P/N:PM1100

REV. 1.1, AUG. 15, 2005

14

MX29LV065M

cator Bit (Q7) to indicate whether or not the Secured Sili-

con Sector is locked when shipped from the factory.This

bit is permanently set at the factory and cannot be

changed, which prevent duplication of a factory locked

part.This ensures the security of the ESN once the prod-

uct is shipped to the field.

way.A factory locked device has an 16-byte random ESN

at address 000000h-00000Fh.

CUSTOMER LOCKABLE:Secured Silicon

Sector NOT Programmed or Protected At the

Factory

The MX29LV065M offers the device with Secured Sili-

con Sector either factory locked or customer lockable.

The factory-locked version is always protected when

shipped from the factory , and has the Secured Silicon

Sector Indicator Bit permanently set to a "1". The cus-

tomer-lockable version is shipped with the Secured Sili-

con Sector unprotected, allowing customers to utilize that

sector in any form they prefer. The customer-lockable

version has the secured sector Indicator Bit permanently

set to a "0". Therefore, the Secured Silicon Sector Indi-

cator Bit prevents customer, lockable device from being

used to replace devices that are factory locked.

As an alternative to the factory-locked version, the device

may be ordered such that the customer may program

and protect the 256 bytes Secured Silicon Sector.

Programming and protecting the Secured Silicon Sector

must be used with caution since, once protected, there

is no procedure available for unprotected the Secured

Silicon Sector area and none of the bits in the Secured

Silicon Sector memory space can be modified in any way.

The Secured Silicon Sector area can be protected using

one of the following procedures:

The system access the Secured Silicon Sector through

a command sequence (refer to "Enter Secured Silicon/

Exit Secured Silicon Sector command Sequence). After

the system has written the Enter Secured Silicon Sector

command sequence, it may read the Secured Silicon

Sector by using the address normally occupied by the

first sector SA0. Once entry the Secured Silicon Sector

the operation of boot sectors is disabled but the operation

of main sectors is as normally. This mode of operation

continues until the system issues the Exit Secured Sili-

con Sector command sequence, or until power is removed

from the device. On power-up, or following a hardware

reset, the device reverts to sending command to sector

SA0.

Write the three-cycle Enter Secured Silicon Sector Region

command sequence, and then follow the in-system

sector protect algorithm as shown in Figure 15, except

that RESET# may be at eitherVIH orVID.This allows in-

system protection of the Secured Silicon Sector without

raising any device pin to a high voltage. Note that method

is only applicable to the Secured Silicon Sector.

Write the three-cycle Enter Secured Silicon Sector Region

command sequence, and then alternate method of sector

protection described in the :Sector Group Protection and

Unprotect" section.

Once the Secured Silicon Sector is programmed, locked

and verified, the system must write the Exit Secured

Silicon Sector Region command sequence to return to

reading and writing the remainder of the array.

Secured Silicon ESN factory

Customer

lockable

Sector address

range

locked

LOW VCC WRITE INHIBIT

000000h-00000Fh

ESN

Determined by

Customer

000010h-0000FFh Unavailable

When VCC is less than VLKO the device does not ac-

cept any write cycles. This protects data during VCC

power-up and power-down.The command register and

all internal program/erase circuits are disabled, and the

device resets. Subsequent writes are ignored until VCC

is greater thanVLKO. The system must provide the proper

signals to the control pins to prevent unintentional write

whenVCC is greater thanVLKO.

FACTORY LOCKED:Secured Silicon Sector

Programmed and Protected At the Factory

In device with an ESN, the Secured Silicon Sector is

protected when the device is shipped from the factory.

The Secured Silicon Sector cannot be modified in any

P/N:PM1100

REV. 1.1, AUG. 15, 2005

15

MX29LV065M

WRITE PULSE "GLITCH" PROTECTION

Noise pulses of less than 5ns (typical) on 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 SEQUENCE

The MX29LV065M powers up in the Read only mode.

In addition, the memory contents may only be altered

after successful completion of the predefined command

sequences.

POWER-UP WRITE INHIBIT

If WE#=CE#=VIL and OE#=VIH during power up, the

device does not accept commands on the rising edge of

WE#. The internal state machine is automatically reset

to the read mode on power-up.

POWER SUPPLY DE COUPLING

In order to reduce power switching effect, each device

should have a 0.1uF ceramic capacitor connected be-

tween itsVCC and GND.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

16

MX29LV065M

Erase Resume (30H) commands are valid only while the

Sector Erase operation is in progress. Either of the two

reset command sequences will reset the device (when

applicable).

SOFTWARE COMMAND DEFINITIONS

Device operations are selected by writing specific ad-

dress and data sequences into the command register.

Writing incorrect address and data values or writing them

in the improper sequence will reset the device to the

read mode. Table 3 defines the valid register command

sequences. Note that the Erase Suspend (B0H) and

All addresses are latched on the falling edge of WE# or

CE#, whichever happens later. All data are latched on

rising edge of WE# or CE#, whichever happens first.

TABLE 3. MX29LV065M COMMAND DEFINITIONS

First Bus

Cycle

Second Bus Third Bus Fourth Bus

Cycle Cycle Cycle

Fifth Bus Sixth Bus

Cycle Cycle

Addr Data Addr Data

Command

Bus

Cycles Addr Data Addr Data Addr Data Addr

Data

Read (Note 5)

1

RA

RD

Reset (Note 6)

XXX F0

XXX AA

Automatic Select (Note 7)

Manufacturer ID

4

3

4

XXX 55

XXX 90 X00

XXX 90 X01

XXX 90 X03

C2H

7E

Device ID

X0E 13

X0F 00

(Note 8)

Secured Sector Factory

Protect

Sector Group Protect

Verify (Note 9)

XXX 90 (SA)X02 00/01

XXX 88

Enter Secured Silicon

Sector

Exit Secured Silicon

Sector

XXX 90 XXX

00

Program

4

6

1

3

XXX AA

XXX 55

XXX A0 PA

SA 25 SA

PD

BC

Write to Buffer (Note 10)

Program Buffer to Flash

Write to Buffer Abort

Reset (Note 11)

Chip Erase

PA PD WBL PD

SA

29

XXX AA

XXX 55

XXX F0

6

1

XXX AA

XXX B0

XXX 55

XXX 80 XXX

AA

XXX 55

XXX 10

SA 30

Sector Erase

Program/Erase Suspend

(Note 12)

Program/Erase Resume

(Note 13)

1

XXX 30

CFI Query (Note 14)

AA

98

P/N:PM1100

REV. 1.1, AUG. 15, 2005

17

MX29LV065M

Legend:

X=Don't care

PD=Data to be programmed at location PA. Data is

latched on the rising edge of WE# or CE# pulse.

SA=Address of the sector to be erase or verified (in

autoselect mode).

Address bits A22-A12 uniquely select any sector.

WBL=Write Buffer Location. Address must be within the

same write buffer page as PA.

RA=Address of the memory location to be read.

RD=Data read from location RA during read operation.

PA=Address of the memory location to be programmed.

Addresses are latched on the falling edge of the WE# or

CE# pulse, whichever happen later.

DDI=Data of device identifier

C2H for manufacture code

BC=Byte Count.Number of write buffer locations to load

minus 1.

Notes:

1. See Table 1 for descriptions of bus operations.

2. All values are in hexadecimal.

3. Except when reading array or automatic select data, all bus cycles are write operation.

4. Address bits are don't care for unlock and command cycles, except when PA or SA is required.

5. No unlock or command cycles required when device is in read mode.

6. The Reset command is required to return to the read mode when the device is in the automatic select mode or if

Q5 goes high.

7. The fourth cycle of the automatic select command sequence is a read cycle.

8. The device ID must be read in three cycles.

9. The data is 00h for an unprotected sector/sector block and 01h for a protected sector/sector block.

10.The total number of cycles in the command sequence is determined by the number of words written to the write

buffer.The maximum number of cycles in the command sequence is 37.

11.Command sequence resets device for next command after aborted write-to-buffer operation.

12. The system may read and program functions in non-erasing sectors, or enter the automatic select mode, when in

the erase Suspend mode.The Erase Suspend command is valid only during a sector erase operation.

13. The Erase Resume command is valid only during the Erase Suspend mode.

14. Command is valid when device is ready to read array data or when device is in automatic select mode.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

18

MX29LV065M

array data (also applies during Erase Suspend).

READING ARRAY DATA

The device is automatically set to reading array data

after device power-up. No commands are required to re-

trieve data. The device is also ready to read array data

after completing an Automatic Program or Automatic

Erase algorithm.

SILICON ID READ COMMAND SEQUENCE

The SILICON ID READ command sequence allows the

host system to access the manufacturer and devices

codes, and determine whether or not a sector is pro-

tected.Table 2 shows the address and data requirements.

This method is an alternative to that shown in Table 1,

which is intended for PROM programmers and requires

VID on address bit A9.

After the device accepts an Erase Suspend command,

the device enters the Erase Suspend mode. The sys-

tem can read array data using the standard read tim-

ings, except that if it reads at an address within erase-

suspended sectors, the device outputs status data. Af-

ter completing a programming operation in the Erase

Suspend mode, the system may once again read array

data with the same exception. See Erase Suspend/Erase

Resume Commands for more information on this mode.

The system must issue the reset command to re-en-

able the device for reading array data if Q5 goes high, or

while in the automatic select mode. See the "Reset Com-

mand" section, next.

The SILICON ID READ command sequence is initiated

by writing two unlock cycles, followed by the SILICON

ID READ command. The device then enters the SILI-

CON ID READ mode, and the system may read at any

address any number of times, without initiating another

command sequence. A read cycle at address XX00h

retrieves the manufacturer code. A read cycle at address

XX01h returns the device code. A read cycle containing

a sector address (SA) and the address 02h returns 01h if

that sector is protected, or 00h if it is unprotected. Refer

to Table for valid sector addresses.

RESET COMMAND

Writing the reset command to the device resets the de-

vice to reading array data. Address bits are don't care for

this command.

The system must write the reset command to exit the

automatic select mode and return to reading array data.

The reset command may be written between the se-

quence cycles in an erase command sequence before

erasing begins. This resets the device to reading array

data.Once erasure begins, however, the device ignores

reset commands until the operation is complete.

BYTE PROGRAM COMMAND SEQUENCE

The command sequence requires four bus cycles, and

is initiated by writing two unlock write cycles, followed

by the program set-up command.The program address

and data are written next, which in turn initiate the Em-

bedded Program algorithm. The system is not required

to provide further controls or timings. The device auto-

matically generates the program pulses and verifies the

programmed cell margin.Table 3 shows the address and

data requirements for the byte program command se-

quence.

The reset command may be written between the se-

quence cycles in a program command sequence before

programming begins. This resets the device to reading

array data (also applies to programming in Erase Sus-

pend mode). Once programming begins, however, the

device ignores reset commands until the operation is

complete.

When the Embedded Program algorithm is complete, the

device then returns to reading array data and addresses

are no longer latched. The system can determine the

status of the program operation by using Q7, Q6, or RY/

BY#. See "Write Operation Status" for information on

these status bits.

The reset command may be written between the se-

quence cycles in an SILICON ID READ command se-

quence. Once in the SILICON ID READ mode, the reset

command must be written to return to reading array data

(also applies to SILICON ID READ during Erase Sus-

pend).

Any commands written to the device during the Embed-

ded Program Algorithm are ignored. Note that a hard-

ware reset immediately terminates the programming op-

If Q5 goes high during a program or erase operation,

writing the reset command returns the device to reading

P/N:PM1100

REV. 1.1, AUG. 15, 2005

19

MX29LV065M

eration. The Byte Program command sequence should

be reinitiated once the device has reset to reading array

data, to ensure data integrity.

decremented for every data load operation.The host sys-

tem must therefore account for loading a write-buffer lo-

cation more than once.The counter decrements for each

data load operation, not for each unique write-buffer-ad-

dress location. Note also that if an address location is

loaded more than once into the buffer, the final data loaded

for that address will be programmed.

Programming is allowed in any sequence and across

sector boundaries. A bit cannot be programmed from a

"0" back to a "1". Attempting to do so may halt the op-

eration and set Q5 to "1", or cause the Data# Polling

algorithm to indicate the operation was successful. How-

ever, a succeeding read will show that the data is still

"0". Only erase operations can convert a "0" to a "1".

Once the specified number of write buffer locations have

been loaded, the system must then write the Program

Buffer to Flash command at the sector address. Any

other address and data combination aborts the Write

Buffer Programming operation. The device then begins

programming. Data polling should be used while monitor-

ing the last address location loaded into the write buffer.

Q7, Q6, Q5, and Q1 should be monitored to determine

the device status during Write Buffer Programming.

Write Buffer Programming

Write Buffer Programming allows the system write to a

maximum of 32 bytes in one programming operation.This

results in faster effective programming time than the stan-

dard programming algorithms.TheWrite Buffer Program-

ming command sequence is initiated by first writing two

unlock cycles.This is followed by a third write cycle con-

taining the Write Buffer Load command written at the

Sector Address in which programming will occur. The

fourth cycle writes the sector address and the number of

word locations, minus one, to be programmed. For ex-

ample, if the system will program 6 unique address loca-

tions, then 05h should be written to the device.This tells

the device how many write buffer addresses will be loaded

with data and therefore when to expect the Program Buffer

to Flash command.The number of locations to program

cannot exceed the size of the write buffer or the operation

will abort.

The write-buffer programming operation can be suspended

using the standard program suspend/resume commands.

Upon successful completion of the Write Buffer Program-

ming operation, the device is ready to execute the next

command.

TheWrite Buffer Programming Sequence can be aborted

in the following ways:

•

Load a value that is greater than the page buffer size

during the Number of Locations to Program step.

Write to an address in a sector different than the one

specified during the Write-Buffer-Load command.

Write an Address/Data pair to a different write-buffer-

page than the one selected by the Starting Address

during the write buffer data loading stage of the op-

eration.

The fifth cycle writes the first address location and data

to be programmed.The write-buffer-page is selected by

address bits A_MAX-4. All subsequent address/data pairs

must fall within the selected-write-buffer-page.The sys-

tem then writes the remaining address/data pairs into

the write buffer. Write buffer locations may be loaded in

any order.

•

Write data other than the Confirm Command after the

specified number of data load cycles.

The abort condition is indicated by Q1 = 1, Q7 = DATA#

(for the last address location loaded), Q6 = toggle, and

Q5=0.AWrite-to-Buffer-Abort Reset command sequence

must be written to reset the device for the next opera-

tion. Note that the full 3-cycle Write-to-Buffer-Abort Re-

set command sequence is required when using Write-

Buffer-Programming features in Unlock Bypass mode.

The write-buffer-page address must be the same for all

address/data pairs loaded into the write buffer. (This

means Write Buffer Programming cannot be performed

across multiple write-buffer pages.This also means that

Write Buffer Programming cannot be performed across

multiple sectors. If the system attempts to load program-

ming data outside of the selected write-buffer page, the

operation will abort.

Program Suspend/Program Resume Command

Sequence

The Program Suspend command allows the system to

interrupt a programming operation or a Write to Buffer

programming operation so that data can be read from any

Note that if a Write Buffer address location is loaded

multiple times, the address/data pair counter will be

P/N:PM1100

REV. 1.1, AUG. 15, 2005

20

MX29LV065M

non-suspended sector.When the Program Suspend com-

mand is written during a programming process, the de-

vice halts the program operation within 15us maximum

(5 us typical) and updates the status bits. Addresses are

not required when writing the Program Suspend com-

mand.

AUTOMATIC CHIP/SECTOR ERASE COM-

MAND

The device does not require the system to preprogram

prior to erase.The Automatic Erase algorithm automati-

cally pre-program and verifies the entire memory for an

all zero data pattern prior to electrical erase.The system

is not required to provide any controls or timings during

these operations. Table 3 shows the address and data

requirements for the chip erase command sequence.

After the programming operation has been suspended,

the system can read array data from any non-suspended

sector. The Program Suspend command may also be

issued during a programming operation while an erase is

suspended. In this case, data may be read from any

addresses not in Erase Suspend or Program Suspend. If

a read is needed from the Secured Silicon Sector area

(One-time Program area), then user must use the proper

command sequences to enter and exit this region.

Any commands written to the chip during the Automatic

Erase algorithm are ignored. Note that a hardware reset

during the chip erase operation immediately terminates

the operation.The Chip Erase command sequence should

be reinitiated once the device has returned to reading

array data, to ensure data integrity.

The system may also write the autoselect command

sequence when the device is in the Program Suspend

mode. The system can read as many autoselect codes

as required.When the device exits the autoselect mode,

the device reverts to the Program Suspend mode, and

is ready for another valid operation. See Autoselect Com-

mand Sequence for more information.

The system can determine the status of the erase op-

eration by using Q7, Q6, Q2, or RY/BY#.See "Write Op-

eration Status" for information on these status bits.When

the Automatic Erase algorithm is complete, the device

returns to reading array data and addresses are no longer

latched.

After the Program Resume command is written, the de-

vice reverts to programming.The system can determine

the status of the program operation using the Q7 or Q6

status bits, just as in the standard program operation.

See Write Operation Status for more information.

Figure 10 illustrates the algorithm for the erase opera-

tion. See the Erase/Program Operations tables in "AC

Characteristics" for parameters, and to Figure 9 for tim-

ing diagrams.

SETUP AUTOMATIC CHIP/SECTOR ERASE

Chip erase is a six-bus cycle operation. There are two

"unlock" write cycles. These are followed by writing the

"set-up" command 80H. Two more "unlock" write cycles

are then followed by the chip erase command 10H, or

the sector erase command 30H.

The MX29LV065M contains a Silicon-ID-Read operation

to supplement traditional PROM programming methodol-

ogy. The operation is initiated by writing the read silicon

ID command sequence into the command register. Fol-

lowing the command write, a read cycle with

A1=VIL,A0=VIL retrieves the manufacturer code.A read

cycle with A1=VIL,A0=VIH retrieves the device code.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

21

MX29LV065M

device requires a maximum 20us to suspend the sector

erase operation.However,When the Erase Suspend com-

mand is written during the sector erase time-out, the

device immediately terminates the time-out period and

suspends the erase operation. After this command has

been executed, the command register will initiate erase

suspend mode. The state machine will return to read

mode automatically after suspend is ready. At this time,

state machine only allows the command register to re-

spond to the Erase Resume, program data to, or read

data from any sector not selected for erasure.

SECTOR ERASE COMMANDS

The Automatic Sector Erase does not require the device

to be entirely pre-programmed prior to executing the Au-

tomatic Set-up Sector Erase command and Automatic

Sector Erase command. Upon executing the Automatic

Sector Erase command, the device will automatically

program and verify the sector(s) memory for an all-zero

data pattern. The system is not required to provide any

control or timing during these operations.

When the sector(s) is automatically verified to contain

an all-zero pattern, a self-timed sector erase and verify

begin. The erase and verify operations are complete

when the data on Q7 is "1" and the data on Q6 stops

toggling for two consecutive read cycles, at which time

the device returns to the Read mode. The system is not

required to provide any control or timing during these

operations.

The system can determine the status of the program

operation using the Q7 or Q6 status bits, just as in the

standard program operation. After an erase-suspend pro-

gram operation is complete, the system can once again

read array data within non-suspended blocks.

ERASE RESUME

When using the Automatic Sector Erase algorithm, note

that the erase automatically terminates when adequate

erase margin has been achieved for the memory array

(no erase verification command is required). Sector erase

is a six-bus cycle operation. There are two "unlock" write

cycles. These are followed by writing the set-up com-

mand 80H. Two more "unlock" write cycles are then fol-

lowed by the sector erase command 30H. The sector

address is latched on the falling edge of WE# or CE#,

whichever happens later , while the command (data) is

latched on the rising edge of WE# or CE#, whichever

happens first. Sector addresses selected are loaded

into internal register on the sixth falling edge of WE# or

CE#, whichever happens later. Each successive sector

load cycle started by the falling edge of WE# or CE#,

whichever happens later must begin within 50us from

the rising edge of the precedingWE# or CE#, whichever

happens first. Otherwise, the loading period ends and

internal auto sector erase cycle starts. (Monitor Q3 to

determine if the sector erase timer window is still open,

see section Q3, Sector EraseTimer.) Any command other

than Sector Erase(30H) or Erase Suspend(B0H) during

the time-out period resets the device to read mode.

This command will cause the command register to clear

the suspend state and return back to Sector Erase mode

but only if an Erase Suspend command was previously

issued. Erase Resume will not have any effect in all

other conditions. Another Erase Suspend command can

be written after the chip has resumed erasing.

ERASE SUSPEND

This command only has meaning while the state ma-

chine is executing Automatic Sector Erase operation,

and therefore will only be responded during Automatic

Sector Erase operation. When the Erase Suspend com-

mand is issued during the sector erase operation, the

P/N:PM1100

REV. 1.1, AUG. 15, 2005

22

MX29LV065M

The single cycle Query command is valid only when the

device is in the Read mode, including Erase Suspend,

Standby mode, and Read ID mode;however, it is ignored

otherwise.

QUERY COMMAND AND COMMON FLASH

INTERFACE (CFI) MODE

MX29LV065M is capable of operating in the CFI mode.

This mode all the host system to determine the manu-

facturer of the device such as operating parameters and

configuration.Two commands are required in CFI mode.

Query command of CFI mode is placed first, then the

Reset command exits CFI mode.These are described in

Table 4.

The Reset command exits from the CFI mode to the

Read mode, or Erase Suspend mode, or read ID mode.

The command is valid only when the device is in the CFI

mode.

Table 4-1. CFI mode: Identification Data Values

(All values in these tables are in hexadecimal)

Description

Addressh Addressh

Datah

(x16)

10

(x8)

20

22

24

26

28

2A

2C

2E

30

32

34

Query-unique ASCII string "QRY"

51

52

59

02

00

40

00

11

12

Primary vendor command set and control interface ID code

Address for primary algorithm extended query table

13

14

15

16

Alternate vendor command set and control interface ID code (none)

Address for secondary algorithm extended query table (none)

17

18

19

1A

Table 4-2. CFI Mode: System Interface Data Values

Description

Addressh Addressh

Datah

(x16)

1B

1C

1D

1E

1F

20

(x8)

36

VCC supply, minimum (2.7V)

27

36

00

07

0A

00

01

05

04

00

VCC supply, maximum (3.6V)

38

VPP supply, minimum (none)

3A

3C

3E

40

VPP supply, maximum (none)

Typical timeout for single word/byte write (2^Nus)

Typical timeout for maximum size buffer write (2^Nus)

Typical timeout for individual block erase (2^Nms)

Typical timeout for full chip erase (2^Nms)

Maximum timeout for single word/byte write times (2^NX Typ)

Maximum timeout for maximum size buffer write times (2^NX Typ)

Maximum timeout for individual block erase times (2^NX Typ)

Maximum timeout for full chip erase times (not supported)

21

42

22

44

23

46

24

48

25

4A

4C

26

P/N:PM1100

REV. 1.1, AUG. 15, 2005

23

MX29LV065M

Table 4-3. CFI Mode: Device Geometry Data Values

Description

Addressh Addressh

Datah

(x16)

27

(x8)

4E

50

52

54

56

58

5A

5C

5E

60

62

64

66

68

6A

6C

6E

70

72

74

76

78

Device size (2ⁿbytes)

17

00

05

00

01

7F

00

01

00

Flash device interface code

28

29

Maximum number of bytes in multi-byte write (not supported)

2A

2B

2C

2D

2E

2F

30

Number of erase block regions (01h=uniform device)

Erase block region 1 information

[2E,2D] = # of blocks in region -1

[30, 2F] = size in multiples of 256-bytes

31

Erase Block Region 2 Information (refer to CFI publication 100)

Erase Block Region 3 Information (refer to CFI publication 100)

Erase Block Region 4 Information (refer to CFI publication 100)

32

33

34

35

36

37

38

39

3A

3B

3C

P/N:PM1100

REV. 1.1, AUG. 15, 2005

24

MX29LV065M

Table 4-4. CFI Mode: Primary Vendor-Specific Extended Query Data Values

Description

Addressh Addressh

Datah

(x16)

40

(x8)

80

82

84

86

88

8A

8C

8E

90

92

94

96

98

9A

Query-unique ASCII string "PRI"

50

52

49

31

33

01

02

04

01

04

00

01

B5

41

42

Major version number, ASCII

43

Minor version number, ASCII

44

Address sensitive unlock (0=required, 1= not required)

Erase suspend (2= to read and write)

Sector protect (N= # of sectors/group)

Temporarysectorunprotect(1=supported)

Sector protect/unprotect scheme

45

46

47

48

49

SimultaneousR/Woperation(0=notsupported)

Burst mode type (0=not supported)

Page mode type (1=8 byte page)

4A

4B

4C

4D

ACC (Acceleration) Supply Minimum

00h=NotSupported,D7-D4:Volt,D3-D0:100mV

ACC (Acceleration) Supply Maximum

00h=NotSupported,D7-D4:Volt,D3-D0:100mV

Top/Bottom Boot Sector Flag

4E

4F

9C

9E

C5

00

00h=Uniform Device without WP# support

02h=Bottom Boot Device, 03h=Top Boot Device

04h=uniform sectors bottom WP# protect,

05h=uniform sectors top WP# protect

ProgramSuspend

50

A0

01

00h=NotSupported,01h=Supported

P/N:PM1100

REV. 1.1, AUG. 15, 2005

25

MX29LV065M

WRITE OPERATION STATUS

The device provides several bits to determine the status

of a write operation: Q2, Q3, Q5, Q6, Q7, and RY/BY#.

Table 5 and the following subsections describe the func-

tions of these bits. Q7, RY/BY#, and Q6 each offer a

method for determining whether a program or erase op-

eration is complete or in progress. These three bits are

discussed first.

Table 5. Write Operation Status

Status

Q7

Q6

Q5

Q3

Q2

No

Q1

RY/BY#

Byte Program in Auto Program Algorithm

Q7# Toggle

0

N/A

0

Toggle

Auto Erase Algorithm

Erase Suspend Read

0

1

Toggle

No

0

1

Toggle N/A

0

1

N/A Toggle N/A

Erase

(Erase Suspended Sector)

Erase Suspend Read

Toggle

Suspended

Mode

Data

Data Data

Data Data Data

1

(Non-Erase Suspended Sector)

Erase Suspend Program

Q7# Toggle

0

N/A

0

1

Program-SuspendedRead

(Program-SuspendedSector)

Program-SuspendedRead

(Non-Program-SuspendedSector)

Invalid (not allowed)

Program

Suspend

Data

1

Write-to-Buffer Busy

Abort

Q7# Toggle

0

N/A

0

1

0

Notes:

1.Q5 switches to "1" when an Byte Program, Erase, or Write-to-Buffer operation has exceeded the maximum timing

limits. Refer to the section on Q5 for more information.

2.Q7 and Q2 require a valid address when reading status information.Refer to the appropriate subsection for further

details.

3.The Data# Polling algorithm should be used to monitor the last loaded write-buffer address location.

4. Q1 switches to "1" when the device has aborted the write-to-buffer operation.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

26

MX29LV065M

happens first pulse in the command sequence (prior to

the program or erase operation), and during the sector

time-out.

Q7: Data# Polling

The Data# Polling bit, Q7, indicates to the host system

whether an Automatic Algorithm is in progress or com-

pleted, or whether the device is in Erase Suspend. Data#

Polling is valid after the rising edge of the finalWE# pulse

in the program or erase command sequence.

During an Automatic Program or Erase algorithm opera-

tion, successive read cycles to any address cause Q6

to toggle. The system may use either OE# or CE# to

control the read cycles.When the operation is complete,

Q6 stops toggling.

During the Automatic Program algorithm, the device out-

puts on Q7 the complement of the datum programmed

to Q7.This Q7 status also applies to programming dur-

ing Erase Suspend.When the Automatic Program algo-

rithm is complete, the device outputs the datum pro-

grammed to Q7.The system must provide the program

address to read valid status information on Q7. If a pro-

gram address falls within a protected sector, Data# Poll-

ing on Q7 is active for approximately 1 us, then the de-

vice returns to reading array data.

After an erase command sequence is written, if all sec-

tors selected for erasing are protected, Q6 toggles for

100us and returns to reading array data. If not all se-

lected sectors are protected, the Automatic Erase algo-

rithm erases the unprotected sectors, and ignores the

selected sectors that are protected.

The system can use Q6 and Q2 together to determine

whether a sector is actively erasing or is erase suspended.

When the device is actively erasing (that is, the Auto-

matic Erase algorithm is in progress), Q6 toggling.When

the device enters the Erase Suspend mode, Q6 stops

toggling. However, the system must also use Q2 to de-

termine which sectors are erasing or erase-suspended.

Alternatively, the system can use Q7.

During the Automatic Erase algorithm, Data# Polling pro-

duces a "0" on Q7.When the Automatic Erase algorithm

is complete, or if the device enters the Erase Suspend

mode, Data# Polling produces a "1" on Q7.This is analo-

gous to the complement/true datum output described for

the Automatic Program algorithm: the erase function

changes all the bits in a sector to "1" prior to this, the

device outputs the "complement," or "0".The system must

provide an address within any of the sectors selected for

erasure to read valid status information on Q7.

If a program address falls within a protected sector, Q6

toggles for approximately 2us after the program com-

mand sequence is written, then returns to reading array

data.

After an erase command sequence is written, if all sec-

tors selected for erasing are protected, Data# Polling on

Q7 is active for approximately 100 us, then the device

returns to reading array data. If not all selected sectors

are protected, the Automatic Erase algorithm erases the

unprotected sectors, and ignores the selected sectors

that are protected.

Q6 also toggles during the erase-suspend-program mode,

and stops toggling once the Automatic Program algo-

rithm is complete.

Table 5 shows the outputs for Toggle Bit I on Q6.

When the system detects Q7 has changed from the

complement to true data, it can read valid data at Q7-Q0

on the following read cycles. This is because Q7 may

change asynchronously with Q0-Q6 while Output Enable

(OE#) is asserted low.

Q2:Toggle Bit II

The "Toggle Bit II" on Q2, when used with Q6, indicates

whether a particular sector is actively erasing (that is,

the Automatic Erase algorithm is in process), or whether

that sector is erase-suspended. Toggle Bit II is valid

after the rising edge of the final WE# or CE#, whichever

happens first pulse in the command sequence.

Q6:Toggle BIT I

Toggle Bit I on Q6 indicates whether an Automatic Pro-

gram or Erase algorithm is in progress or complete, or

whether the device has entered the Erase Suspend mode.

Toggle Bit I may be read at any address, and is valid

after the rising edge of the final WE# or CE#, whichever

Q2 toggles when the system reads at addresses within

those sectors that have been selected for erasure. (The

system may use either OE# or CE# to control the read

cycles.) But Q2 cannot distinguish whether the sector

is actively erasing or is erase-suspended. Q6, by com-

P/N:PM1100

REV. 1.1, AUG. 15, 2005

27

MX29LV065M

parison, indicates whether the device is actively eras-

ing, or is in Erase Suspend, but cannot distinguish which

sectors are selected for erasure. Thus, both status bits

are required for sectors and mode information. Refer to

Table 5 to compare outputs for Q2 and Q6.

If this time-out condition occurs during sector erase op-

eration, it specifies that a particular sector is bad and it

may not be reused. However, other sectors are still func-

tional and may be used for the program or erase opera-

tion. The device must be reset to use other sectors.

Write the Reset command sequence to the device, and

then execute program or erase command sequence. This

allows the system to continue to use the other active

sectors in the device.

Reading Toggle Bits Q6/ Q2

Whenever the system initially begins reading toggle bit

status, it must read Q7-Q0 at least twice in a row to

determine whether a toggle bit is toggling. Typically, the

system would note and store the value of the toggle bit

after the first read. After the second read, the system

would 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 Q7-Q0 on the following read cycle.

If this time-out condition occurs during the chip erase

operation, it specifies that the entire chip is bad or com-

bination of sectors are bad.

If this time-out condition occurs during the byte program-

ming operation, it specifies that the entire sector contain-

ing that byte is bad and this sector may not be reused,

(other sectors are still functional and can be reused).

However, if after the initial two read cycles, the system

determines that the toggle bit is still toggling, the sys-

tem also should note whether the value of Q5 is high

(see the section on Q5). 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 Q5 went

high. If the toggle bit is no longer toggling, the device

has successfully completed the program or erase opera-

tion. 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 time-out condition may also appear if a user tries to

program a non blank location without erasing. In this

case the device locks out and never completes the Au-

tomatic Algorithm operation. Hence, the system never

reads a valid data on Q7 bit and Q6 never stops toggling.

Once the Device has exceeded timing limits, the Q5 bit

will indicate a "1". Please note that this is not a device

failure condition since the device was incorrectly used.

The Q5 failure condition may appear if the system tries

to program a to a "1" location that is previously pro-

grammed to "0". Only an erase operation can change a

"0" back to a "1". Under this condition, the device halts

the operation, and when the operation has exceeded the

timing limits, Q5 produces a "1".

The remaining scenario is that system initially determines

that the toggle bit is toggling and Q5 has not gone high.

The system may continue to monitor the toggle bit and

Q5 through successive read cycles, determining the sta-

tus 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 al-

gorithm when it returns to determine the status of the

operation.

Q3:Sector Erase Timer

After the completion of the initial sector erase command

sequence, the sector erase time-out will begin. Q3 will

remain low until the time-out is complete. Data# Polling

andToggle Bit are valid after the initial sector erase com-

mand sequence.

Q5:Program/Erase Timing

Q5 will indicate if the program or erase time has exceeded

the specified limits (internal pulse count). Under these

conditions Q5 will produce a "1". This time-out condition

indicates that the program or erase cycle was not suc-

cessfully completed. Data# Polling and Toggle Bit are

the only operating functions of the device under this con-

dition.

If Data# Polling or the Toggle Bit indicates the device

has been written with a valid erase command, Q3 may

be used to determine if the sector erase timer window is

still open. If Q3 is high ("1") the internally controlled

erase cycle has begun; attempts to write subsequent

commands to the device will be ignored until the erase

operation is completed as indicated by Data# Polling or

Toggle Bit. If Q3 is low ("0"), the device will accept addi-

P/N:PM1100

REV. 1.1, AUG. 15, 2005

28

MX29LV065M

tional sector erase commands. To insure the command

has been accepted, the system software should check

the status of Q3 prior to and following each subsequent

sector erase command. If Q3 were high on the second

status check, the command may not have been accepted.

If the time between additional erase commands from the

system can be less than 50us, the system need not to

monitor Q3.

Q1: Write-to-Buffer Abort

Q1 indicates whether a Write-to-Buffer operation was

aborted.Under these conditions Q1 produces a "1".The

system must issue theWrite-to-Buffer-Abort-Reset com-

mand sequence to return the device to reading array data.

See Write Buffer section for more details.

RY/BY#:READY/BUSY OUTPUT

The RY/BY# is a dedicated, open-drain output pin that

indicates whether an Embedded Algorithm is in progress

or complete. The RY/BY# status is valid after the rising

edge of the final WE# pulse in the command sequence.

Since RY/BY# is an open-drain output, several RY/BY#

pins can be tied together in parallel with a pull-up resistor

to VCC .

If the output is low (Busy), the device is actively erasing

or programming. (This includes programming in the Erase

Suspend mode.) If the output is high (Ready), the device

is ready to read array data (including during the Erase

Suspend mode), or is in the standby mode.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

29

MX29LV065M

OPERATING RATINGS

ABSOLUTE MAXIMUM RATINGS

StorageTemperature

Commercial (C) Devices

Plastic Packages . . . . . . . . . . . . . ..... -65^oC to +150^oC

Ambient Temperature (T^A). . . . . . . . . . . . 0°C to +70°C

Industrial (I) Devices

AmbientTemperature

with Power Applied. . . . . . . . . . . . . .... -65^oC to +125^oC

Voltage with Respect to Ground

Ambient Temperature (T^A). . . . . . . . . . -40°C to +85° C

V^CCSupply Voltages

V^CCfor full voltage range. . . . . . . . . . . +2.7 V to 3.6 V

VCC (Note 1) . . . . . . . . . . . . . . . . . -0.5 V to +4.0 V

A9, OE#, and

Operating ranges define those limits between which the

functionality of the device is guaranteed.

RESET# (Note 2) . . . . . . . . . . . ....-0.5 V to +12.5 V

All other pins (Note 1) . . . . . . . -0.5 V to VCC +0.5 V

Output Short Circuit Current (Note 3) . . . . . . 200 mA

Notes:

1. Minimum DC voltage on input or I/O pins is -0.5 V.

During voltage transitions, input or I/O pins may over-

shoot VSS to -2.0 V for periods of up to 20 ns. Maxi-

mum DC voltage on input or I/O pins is VCC +0.5 V.

During voltage transitions, input or I/O pins may over-

shoot to VCC +2.0 V for periods up to 20ns.

2. Minimum DC input voltage on pins A9, OE#, and

RESET# is -0.5V.During voltage transitions, A9, OE#,

and RESET# may overshoot VSS to -2.0 V for peri-

ods of up to 20 ns. Maximum DC input voltage on pin

A9 is +12.5 V which may overshoot to 14.0 V for peri-

ods up to 20 ns.

3.No more than one output may be shorted to ground at

a time. Duration of the short circuit should not be

greater than one second.

Stresses above those listed under "Absolute Maximum

Ratings" may cause permanent damage to the device.

This is a stress rating only; functional operation of the

device at these or any other conditions above those in-

dicated in the operational sections of this data sheet is

not implied. Exposure of the device to absolute maxi-

mum rating conditions for extended periods may affect

device reliability.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

30

MX29LV065M

DC CHARACTERISTICS

TA=-40°C to 85° C, VCC=2.7V~3.6V

Para-

meter Description

Test Conditions

Min.

Typ.

Max.

Unit

I LI

Input Load Current (Note 1)

VIN = VSS to VCC ,

VCC = VCC max

±1.0

uA

I LIT A9 Input Leakage Current

I LO Output Leakage Current

VCC=VCC max; A9 = 12.5V

VOUT = VSS to VCC ,

VCC=VCC max

35

uA

±1.0

ICC1 VCC Active Read Current

(Notes 2,3)

CE#= VIL,

OE# = VIH

10 MHz

5 MHz

35

18

5

50

25

20

40

60

mA

1 MHz

ICC2 VCC Intra-Page Read

Current (Notes 2,3)

ICC3 VCC ActiveWrite Current

(Notes 2,3)

CE#= VIL ,

OE# = VIH

10 MHz

40 MHz

5

10

50

CE#= VIL , OE# = VIH

CE#,RESET#=VCC±0.3V

RESET#=VSS±0.3V

ICC4 VCC Standby Current

(Note 2)

20

50

uA

ICC5 VCC Reset Current

(Note 2)

ICC6 Automatic Sleep Mode

(Note 2,4)

VIL = V SS ± 0.3 V,

VIH = VCC ±0.3 V,

VIL

Input LowVoltage

-0.5

0.7xVCC

11.5

0.8

VCC+0.5

12.5

V

VIH Input HighVoltage

VHH Voltage for ACC Program

Acceleration

VCC = 2.7V ~ 3.6V

12.0

VID Voltage for Autoselect and

Temporary Sector Unprotect

VOL Output LowVoltage

VOH1 Output HighVoltage

VOH2

VCC = 3.0 V ±10%

11.5

12.5

0.45

V

IOL= 4.0mA,VCC=VCC min

V

IOH=-2.0mA,VCC=VCC min 0.85VCC

IOH=-100uA,VCC=VCC min VCC-0.4

2.3

VLKO LowVCC Lock-OutVoltage

(Note 5)

2.5

Notes:

1. The ICC current listed is typically is less than 2 mA/MHz, with OE# at VIH. Typical specifications are for VCC =

3.0V.

2. Maximum ICC specifications are tested with VCC = VCC max.

3. ICC active while Embedded Erase or Embedded Program is in progress.

4. Automatic sleep mode enables the low power mode when addresses remain stable for t ACC + 30 ns.

5. Not 100% tested.

6.A9=12.5V whenTA=0°C to 85°C, A9=12V when whenTA=-40°C to 0°C.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

31

MX29LV065M

SWITCHING TEST CIRCUITS

TEST SPECIFICATIONS

Test Condition

All Speeds

1 TTL gate

30

Unit

pF

Output Load

DEVICE UNDER

TEST

2.7K ohm

Output Load Capacitance, CL

(including jig capacitance)

Input Rise and Fall Times

Input Pulse Levels

3.3V

5

ns

V

0.0-3.0

1.5

CL

6.2K ohm

DIODES=IN3064

OR EQUIVALENT

Input timing measurement

reference levels

V

Output timing measurement

reference levels

0.5 V_IO

V

Note: If V_IO<VCC, the reference level is 0.5V_IO.

KEY TO SWITCHING WAVEFORMS

WAVEFORM

INPUTS

OUTPUTS

Steady

Changing from H to L

Changing from L to H

Don't Care, Any Change Permitted

Does Not Apply

Changing, State Unknown

Center Line is High Impedance State(High Z)

SWITCHING TEST WAVEFORMS

3.0V

Measurement Level

1.5V

0.5V

V

IO

0.0V

INPUT

OUTPUT

Note: If V_IO<VCC, the input measurement reference level is 0.5V_IO.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

32

MX29LV065M

AC CHARACTERISTICS

Read-Only Operations

Parameter

TA=-40°C to 85°C, VCC=2.7V~3.6V

Speed Options

Std.

tRC

Description

Test Setup

90

25

35

16

0

Unit

ns

Read CycleTime (Note 1)

Address to Output Delay

Min

CE#, OE#=VIL Max

tACC

tCE

Chip Enable to Output Delay

Page Access Time

OE#=VIL

Max

Min

tPACC

tOE

tDF

Output Enable to Output Delay

Chip Enable to Output High Z (Note 1)

Output Enable to Output High Z (Note 1)

Output HoldTime From Address, CE#

or OE#, whichever Occurs First

Read

tDF

tOH

Min

35

10

ns

tOEH

Output Enable HoldTime Toggle and

(Note 1)

Data# Polling

Notes:

1. Not 100% tested.

2. See SWITCHING TEST CIRCUITS and TEST SPECIFICATIONS TABLE for test specifications.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

33

MX29LV065M

Figure 1. READ TIMING WAVEFORMS

tRC

VIH

ADD Valid

Addresses

VIL

tCE

VIH

CE#

tRH

VIL

tRH

VIH

WE#

tDF

VIL

VIH

VIL

tOEH

tOE

OE#

tOH

tACC

HIGH Z

VOH

VOL

Outputs

DATA Valid

VIH

VIL

RESET#

RY/BY#

0V

Figure 2. PAGE READ TIMING WAVEFORMS

Same Page

A2~A22

A0~A2

tACC

CE#

tPACC

OE#

Qa

Qb

Qc

Qd

Qe

Qf

Qg

Qh

Output

P/N:PM1100

REV. 1.1, AUG. 15, 2005

34

MX29LV065M

AC CHARACTERISTICS

Parameter Description

Test Setup All Speed Options Unit

tREADY1

RESET# PIN Low (During Automatic Algorithms)

MAX

20

us

to Read or Write (See Note)

tREADY2

RESET# PIN Low (NOT During Automatic Algorithms)

to Read or Write (See Note)

MAX

500

ns

tRP

RESET# Pulse Width (NOT During Automatic Algorithms)

RESET# HighTime Before Read (See Note)

RY/BY# Recovery Time(to CE#, OE# go low)

RESET# Low to Standby Mode

MIN

500

50

0

ns

us

tRH

tRB

tRPD

20

Note:Not 100% tested

Figure 3. RESET# TIMING WAVEFORM

RY/BY#

CE#, OE#

tRH

RESET#

tRP

tReady2

Reset Timing NOT during Automatic Algorithms

tReady1

RY/BY#

tRB

CE#, OE#

RESET#

tRP

Reset Timing during Automatic Algorithms

P/N:PM1100

REV. 1.1, AUG. 15, 2005

35

MX29LV065M

AC CHARACTERISTICS

Erase and Program Operations

Parameter

TA=-40° C to 85° C, VCC=2.7V~3.6V

Speed Options

Std.

tWC

tAS

Description

90

0

Unit

ns

Write CycleTime (Note 1)

Address SetupTime

Min

ns

tASO

tAH

Address Setup Time to OE# low during toggle bit polling

Address HoldTime

15

45

0

ns

tAHT

Address HoldTime From CE# or OE# high during toggle

bit polling

ns

tDS

Data SetupTime

Min

35

0

ns

tDH

Data HoldTime

tCEPH

tOEPH

tGHWL

CE# High DuringToggle Bit Polling

Output Enable High during toggle bit polling

Read RecoveryTime BeforeWrite

(OE# High to WE# Low)

20

0

tGHEL

tCS

Read RecoveryTime BeforeWrite

CE# SetupTime

Min

Typ

0

ns

us

tCH

CE# HoldTime

0

tWP

Write PulseWidth

35

30

240

60

tWPH

Write PulseWidth High

Write Buffer Program Operation (Note 2,3)

Single Byte Program Operation

(Notes 2,5)

tWHWH1

Accelerated Single Byte

Typ

54

us

Programming Operation (Notes 2,5)

Sector Erase Operation (Note 2)

VCC SetupTime (Note 1)

tWHWH2

tVCS

Typ

Min

Max

0.5

50

0

sec

us

ns

us

tRB

Write RecoveryTime from RY/BY#

Program/EraseValid to RY/BY# Delay

VHH Rise and FallTime (Note 1)

ProgramValid Before Status Polling (Note 6)

tBUSY

tVHH

90

250

4

tPOLL

Notes:

1. Not 100% tested.

2. See the "Erase And Programming Performance" section for more information.

3.For 1-32 bytes programmed.

4. Effective write buffer specification is based upon a 32-byte write buffer operation.

5.Byte programming specification is based upon a single byte programming operation not utilizing the write buffer.

6. When using the program suspend/resume feature, if the suspend command is issued within tPOLL, tPOLL must be

fully re-applied upon resuming the programming operation.If the suspend command is issued after tPOLL, tPOLL is

not required again prior to reading the status bits upon resuming.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

36

MX29LV065M

ERASE/PROGRAM OPERATION

Figure 4. AUTOMATIC PROGRAM TIMING WAVEFORMS

Program Command Sequence(last two cycle)

Read Status Data (last two cycle)

tWC

tAS

PA

XXXh

PA

Address

CE#

tAH

tCH

OE#

WE#

tWP

tWHWH1

tCS

tWPH

tDS tDH

Status

A0h

PD

DOUT

Data

tBUSY

tRB

RY/BY#

tVCS

VCC

NOTES:

1.PA=Program Address, PD=Program Data, DOUT is the true data the program address

Figure 5. ACCELERATED PROGRAM TIMING DIAGRAM

VHH

ACC

VIL or VIH

tVHH

P/N:PM1100

REV. 1.1, AUG. 15, 2005

37

MX29LV065M

Figure 6. AUTOMATIC PROGRAMMING ALGORITHM FLOWCHART

START

Write Data AAH Address 555H

Write Data 55H Address 2AAH

Write Data A0H Address 555H

Write Program Data/Address

Data Poll

Increment

Address

from system

No

Verify Word Ok ?

YES

Last Address ?

YES

Auto Program Completed

P/N:PM1100

REV. 1.1, AUG. 15, 2005

38

MX29LV065M

Figure 7. WRITE BUFFER PROGRAMMING ALGORITHM FLOWCHART

Write "Write to Buffer"

command and

Sector Address

Write number of addresses

to program minus 1(WC)

and Sector Address

Part of "Write to Buffer"

Command Sequence

Write first address/data

Yes

WC = 0 ?

No

Yes

Write to a different

sector address

Abort Write to

Buffer Operation ?

No

Write to buffer ABORTED.

Must write "Write-to-buffer

Abort Reset" command sequence

to return to read mode.

Write next address/data pair

(Note 1)

WC = WC - 1

Write program buffer

to flash sector address

Notes:

1. When Sector Address is specified, any address in

the selected sector is acceptable. However, when

loading Write-Buffer address locations with data, all

addresses must fall within the selected Write-Buffer

Page.

Read Q7~Q0 at Last

Loaded Address

2. Q7 may change simultaneously with Q5.

Therefore, Q7 should be verified.

Yes

Q7 = Data ?

No

3. If this flowchart location was reached because Q5=

"1" then the device FAILED. If this flowchart location

was reached because Q1="1", then the Write to

Buffer operation was ABORTED. In either case, the

proper reset command must be written before the

device can begin another operation. If Q1=1, write

the Write-Buffer-Programming-Abort-Reset com-

mand. If Q5=1, write the Reset command.

4. See Table 3 for command sequences required for

write buffer programming.

No

Q1 = 1 ?

Yes

Q5 = 1 ?

Yes

Read Q7~Q0 with address

= Last Loaded Address

Yes

(Note 2)

(Note 3)

Q7 = Data ?

No

FAIL or ABORT

PASS

P/N:PM1100

REV. 1.1, AUG. 15, 2005

39

MX29LV065M

Figure 8. PROGRAM SUSPEND/RESUME FLOWCHART

Program Operation

or Write-to-Buffer

Sequence in Progress

Write Program Suspend

Command Sequence

Command is also valid for

Erase-suspended-program

operations

Write address/data

XXXh/B0h

Wait 15us

Autoselect and Secured Sector

read operations are also allowed

Data cannot be read from erase-or

program-suspended sectors

Read data as

required

No

Done reading ?

Yes

Write Program Resume

Command Sequence

Write address/data

XXXh/30h

Device reverts to

operation prior to

Program Suspend

P/N:PM1100

REV. 1.1, AUG. 15, 2005

40

MX29LV065M

Figure 9. AUTOMATIC CHIP/SECTOR ERASE TIMING WAVEFORM

Erase Command Sequence(last two cycle)

Read Status Data

VA

tWC

tAS

VA

2AAh

SA

Address

CE#

555h for chip erase

tAH

tCH

OE#

WE#

tWHWH2

tWP

tCS

tWPH

tDS tDH

In

Progress

55h

30h

Complete

Data

10 for Chip Erase

tBUSY

tRB

RY/BY#

tVCS

VCC

NOTES:

1.SA=sector address(for Sector Erase), VA=Valid Address for reading status data(see "Write Operation Status").

P/N:PM1100

REV. 1.1, AUG. 15, 2005

41

MX29LV065M

Figure 10. AUTOMATIC CHIP ERASE ALGORITHM FLOWCHART

START

Write Data AAH Address 555H

Write Data 55H Address 2AAH

Write Data 80H Address 555H

Write Data AAH Address 555H

Write Data 55H Address 2AAH

Write Data 10H Address 555H

Data Poll

from system

YES

No

DATA = FFh ?

YES

Auto Erase Completed

P/N:PM1100

REV. 1.1, AUG. 15, 2005

42

MX29LV065M

Figure 11. AUTOMATIC SECTOR ERASE ALGORITHM FLOWCHART

START

Write Data AAH Address 555H

Write Data 55H Address 2AAH

Write Data 80H Address 555H

Write Data AAH Address 555H

Write Data 55H Address 2AAH

Write Data 30H Sector Address

NO

Last Sector

to Erase ?

YES

Data Poll from System

NO

Data=FFh?

YES

Auto Sector Erase Completed

P/N:PM1100

REV. 1.1, AUG. 15, 2005

43

MX29LV065M

Figure 12. ERASE SUSPEND/RESUME FLOWCHART

START

Write Data B0H

ERASE SUSPEND

NO

Toggle Bit checking Q6

not toggled

YES

Read Array or

Program

Reading or

NO

Programming End

YES

Write Data 30H

Continue Erase

ERASE RESUME

Another

NO

Erase Suspend ?

YES

P/N:PM1100

REV. 1.1, AUG. 15, 2005

44

MX29LV065M

AC CHARACTERISTICS

Alternate CE# Controlled Erase and Program Operations

Parameter

Speed Options

Std.

tWC

tAS

Description

90

0

Unit

ns

Write CycleTime (Note 1)

Address SetupTime

Min

ns

tAH

Address HoldTime

45

35

0

ns

tDS

Data SetupTime

ns

tDH

Data HoldTime

ns

tGHEL

Read RecoveryTime Before Write

(OE# High to WE# Low)

WE# SetupTime

0

ns

tWS

tWH

tCP

Min

Typ

0

ns

us

WE# HoldTime

CE# PulseWidth

35

25

240

60

tCPH

CE# Pulse Width High

Write Buffer Program Operation (Note 2,3)

Single Byte Program Operation

(Notes 2,5)

tWHWH1

Accelerated Single Byte

Programming Operation (Notes 2,5)

Sector Erase Operation (Note 2)

RESET HIGHTime BeforeWrite (Note 1)

Program Valid Before Status Polling (Note 6)

Typ

54

us

tWHWH2

tRH

Typ

Min

Max

0.5

50

4

sec

ns

tPOLL

us

Notes:

1. Not 100% tested.

2. See the "Erase And Programming Performance" section for more information.

3.For 1-32 bytes programmed.

4. Effective write buffer specification is based upon a 32-byte write buffer operation.

5. Byte programming specification is based upon a single byte programming operation not utilizing the write buffer.

6. When using the program suspend/resume feature, if the suspend command is issued within tPOLL, tPOLL must be

fully re-applied upon resuming the programming operation.If the suspend command is issued after tPOLL, tPOLL is

not required again prior to reading the status bits upon resuming.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

45

MX29LV065M

Figure 13. CE# CONTROLLED PROGRAM TIMING WAVEFORM

PA for program

555 for program

2AA for erase

SA for sector erase

555 for chip erase

Data# Polling

Address

PA

tWC

tWH

tAS

tAH

WE#

OE#

tGHEL

tCP

tWHWH1 or 2

CE#

Data

tWS

tDS

tCPH

tBUSY

tDH

Q7

DOUT

PD for program

30 for sector erase

10 for chip erase

A0 for program

55 for erase

tRH

RESET#

RY/BY#

NOTES:

1.PA=Program Address, PD=Program Data, DOUT=Data Out, Q7=complement of data written to device.

2.Figure indicates the last two bus cycles of the command sequence.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

46

MX29LV065M

SECTOR GROUP PROTECT/CHIP UNPROTECT

Figure 14. Sector Group Protect / Chip Unprotect Waveform (RESET# Control)

VID

VIH

RESET#

SA, A6

A1, A0

Valid*

Sector Group Protect or Chip Unprotect

Verify

40h

Status

Data

60h

Sector Group Protect:150us

Chip Unprotect:15ms

1us

CE#

WE#

OE#

Note: For sector group protect A6=0, A1=1, A0=0. For chip unprotect A6=1, A1=1, A0=0

P/N:PM1100

REV. 1.1, AUG. 15, 2005

47

MX29LV065M

Figure 15. IN-SYSTEM SECTOR GROUP PROTECT/CHIP UNPROTECT ALGORITHMS WITH

RESET#=VID

START

Protect all sectors:

PLSCNT=1

The indicated portion of

PLSCNT=1

the sector protect algorithm

must be performed

RESET#=VID

for all unprotected sectors

RESET#=VID

prior to issuing the first

sector unprotect address

Wait 1us

No

First Write

Temporary Sector

Unprotect Mode

Cycle=60h?

First Write

No

Temporary Sector

Unprotect Mode

Cycle=60h?

Yes

Set up sector address

No

All sectors

protected?

Sector Protect:

Write 60h to sector

address with

A6=0, A1=1, A0=0

Yes

Set up first sector address

Wait 150us

Sector Unprotect:

Write 60h to sector

address with

Verify Sector Protect:

Write 40h to sector

address with

Reset

PLSCNT=1

A6=1, A1=1, A0=0

A6=0, A1=1, A0=0

Increment PLSCNT

Wait 15 ms

Read from

sector address

with

A6=0, A1=1, A0=0

Verify Sector Unprotect:

Write 40h to sector

address with

No

Increment PLSCNT

A6=1, A1=1, A0=0

No

Data=01h?

Yes

PLSCNT=25?

Read from

sector address

with

Yes

A6=1, A1=1, A0=0

No

Device failed

Reset

Yes

Protect another

sector?

PLSCNT=1

No

PLSCNT=1000?

Data=00h?

Yes

No

Sector Protect

Algorithm

Yes

Remove VID from RESET#

Device failed

No

Last sector

verified?

Write reset command

Yes

Chip Unprotect

Algorithm

Sector Protect complete

Remove VID from RESET#

Write reset command

Sector Unprotect complete

P/N:PM1100

REV. 1.1, AUG. 15, 2005

48

MX29LV065M

AC CHARACTERISTICS

Parameter

tVLHT

Description

Test Setup

Min.

All Speed Options Unit

Voltage transition time

4

100

4

us

ns

us

tWPP1

Write pulse width for sector group protect

OE# setup time to WE# active

Min.

tOESP

Min.

Figure 16. SECTOR GROUP PROTECT TIMING WAVEFORM (A9, OE# Control)

A1

A6

12V

3V

A9

tVLHT

Verify

12V

3V

OE#

tVLHT

tWPP 1

WE#

tOESP

CE#

Data

01H

F0H

tOE

Sector Address

A22-A16

P/N:PM1100

REV. 1.1, AUG. 15, 2005

49

MX29LV065M

Figure 17. SECTOR GROUP PROTECTION ALGORITHM (A9, OE# Control)

START

Set Up Sector Addr

PLSCNT=1

OE#=VID, A9=VID, CE#=VIL

A6=VIL

Activate WE# Pulse

Time Out 150us

Set WE#=VIH, CE#=OE#=VIL

A9 should remain VID

.

Read from Sector

Addr=SA, A1=1

No

Data=01H?

PLSCNT=32?

Yes

Device Failed

Yes

Protect Another

Sector?

Remove VID from A9

Write Reset Command

Sector Protection

Complete

P/N:PM1100

REV. 1.1, AUG. 15, 2005

50

MX29LV065M

Figure 18. CHIP UNPROTECT TIMING WAVEFORM (A9, OE# Control)

A1

12V

3V

A9

A6

tVLHT

Verify

12V

3V

OE#

tVLHT

tWPP 2

WE#

CE#

tOESP

Data

00H

F0H

tOE

P/N:PM1100

REV. 1.1, AUG. 15, 2005

51

MX29LV065M

Figure 19. CHIP UNPROTECT FLOWCHART (A9, OE# Control)

START

Protect All Sectors

PLSCNT=1

Set OE#=A9=VID

CE#=VIL, A6=1

Activate WE# Pulse

Time Out 15ms

Increment

PLSCNT

Set OE#=CE#=VIL

A9=VID, A1=1

Set Up First Sector Addr

Read Data from Device

No

Data=00H?

Yes

PLSCNT=1000?

Increment

Sector Addr

Yes

Device Failed

No

All sectors have

been verified?

Yes

Remove VID from A9

Write Reset Command

Chip Unprotect

Complete

* It is recommended before unprotect whole chip, all sectors should be protected in advance.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

52

MX29LV065M

AC CHARACTERISTICS

Parameter Description

Test

Setup

Min

All Speed Options Unit

tVIDR

tRSP

tRRB

VID Rise and Fall Time (see Note)

500

4

ns

us

RESET# Setup Time for Temporary Sector Unprotect

RESET# Hold Time from RY/BY# High for Temporary

Sector Group Unprotect

Min

4

Figure 20. TEMPORARY SECTOR GROUP UNPROTECT WAVEFORMS

12V

RESET#

0 or 3V

VIL or VIH

tVIDR

Program or Erase Command Sequence

CE#

WE#

tRSP

tRRB

RY/BY#

P/N:PM1100

REV. 1.1, AUG. 15, 2005

53

MX29LV065M

Figure 21. TEMPORARY SECTOR GROUP UNPROTECT FLOWCHART

Start

RESET# = VID (Note 1)

Perform Erase or Program Operation

Operation Completed

RESET# = VIH

Temporary Sector Unprotect Completed(Note 2)

Note :

1. All protected sectors are temporary unprotected.

VID=11.5V~12.5V

2. All previously protected sectors are protected again.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

54

MX29LV065M

Figure 22. SECURED SILICON SECTOR PROTECTED ALGORITHMS FLOWCHART

START

Enter Secured Silicon Sector

Wait 1us

First Wait Cycle Data=60h

Second Wait Cycle Data=60h

A6=0, A1=1, A0=0

Wait 300us

No

Data = 01h ?

Yes

Device Failed

Write Reset Command

Secured Sector Protect Complete

P/N:PM1100

REV. 1.1, AUG. 15, 2005

55

MX29LV065M

Figure 23. SILICON ID READ TIMING WAVEFORM

VCC

3V

VID

ADD

A9

VIH

VIL

VIH

VIL

ADD

A0

tACC

VIH

VIL

A1

A2

VIH

VIL

VIH

VIL

ADD

CE#

VIH

VIL

tCE

VIH

VIL

WE#

OE#

tOE

VIH

VIL

tDF

tOH

VIH

VIL

DATA

Q0-Q15

DATA OUT

Manufacturer ID

DATA OUT

Device ID

Cycle 1

Device ID

Cycle 2

Device ID

Cycle 3

P/N:PM1100

REV. 1.1, AUG. 15, 2005

56

MX29LV065M

WRITE OPERATION STATUS

Figure 24. DATA# POLLING TIMING WAVEFORMS (DURING AUTOMATIC ALGORITHMS)

tRC

VA

Address

CE#

tACC

tCE

tCH

tOE

OE#

WE#

tOEH

tDF

tOH

High Z

Complement

Status Data

True

Valid Data

Q7

Q0-Q6

True

tBUSY

RY/BY#

NOTES:

VA=Valid address. Figure shows are first status cycle after command sequence, last status read cycle, and array data raed cycle.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

57

MX29LV065M

Figure 25. DATA# POLLING ALGORITHM

Start

Read Q7~Q0

Add.=VA(1)

Yes

Q7 = Data ?

No

Q5 = 1 ?

Yes

Read Q7~Q0

Add.=VA

Yes

Q7 = Data ?

(2)

No

FAIL

Pass

Notes:

1.VA=valid address for programming.

2.Q7 should be rechecked even Q5="1" because Q7 may change simultaneously with Q5.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

58

MX29LV065M

Figure 26. TOGGLE BIT TIMING WAVEFORMS (DURING AUTOMATIC ALGORITHMS)

tRC

VA

Address

CE#

tACC

tCE

tCH

tOE

OE#

tOEH

tDF

WE#

tOH

tDH

Valid Status

(second read)

Valid Status

(first read)

Valid Data

Q6/Q2

Valid Status

(stops toggling)

RY/BY#

NOTES:

VA=Valid address; not required for Q6. Figure shows first two status cycle after command sequence, last status read cycle, and

array data read cycle.

P/N:PM1100

REV. 1.1, AUG. 15, 2005

59

MX29LV065M

Figure 27. TOGGLE BIT ALGORITHM

START

Read Q7~Q0

(Note 1)

NO

Toggle Bit Q6

=Toggle?

YES

NO

Q5=1?

YES

(Note 1,2)

Read Q7~Q0 Twice

Toggle Bit Q6=

Toggle?

YES

Program/Erase Operation Not

Program/Erase Operation Complete

Complete, Write Reset Command

Note:

1. Read toggle bit twice to determine whether or not it is toggling.

2. Recheck toggle bit because it may stop toggling as Q5 changes to "1".

P/N:PM1100

REV. 1.1, AUG. 15, 2005

60

MX29LV065M

Figure 28. Q6 versus Q2

Enter Embedded

Erasing

Erase

Enter Erase

Erase

Suspend

Suspend Program

Resume

Erase

Erase Suspend

Read

Erase

Erase Suspend

Read

Erase

WE#

Q6

Suspend

Program

Complete

Q2

NOTES:

The system can use OE# or CE# to toggle Q2/Q6, Q2 toggles only when read at an address within an erase-suspended

P/N:PM1100

REV. 1.1, AUG. 15, 2005

61

MX29LV065M

ERASE AND PROGRAMMING PERFORMANCE (1)

PARAMETER

Typ (Note 1)

Max (Note 2)

Unit

Comments

Excludes 00h

programming

prior to erasure

Note 6

Sector Erase Time

0.5

3.5

sec

Chip Erase Time

64

128

sec

Total Write Buffer Program Time (Note 4)

Total Accelerated Effective Write Buffer

Program Time (Note 4)

240

200

us

Excludes

system level

overhead

Chip Program Time

63

sec

Note 7

Notes:

1. Typical program and erase times assume the following conditions: 25° C, 3.0 V VCC. Programming specifications

assume checkerboard data pattern.

2. Maximum values are measured at VCC = 3.0 V, worst case temperature. Maximum values are valid up to and

including 100,000 program/erase cycles.

3. Byte programming specification is based upon a single byte programming operation not utilizing the write buffer.

4. For 1-32 bytes programmed in a single write buffer programming operation.

5. Effective write buffer specification is calculated on a per-byte basis for a 32-byte write buffer operation.

6. In the pre-programming step of the Embedded Erase algorithm, all bits are programmed to 00h before erasure.

7. System-level overhead is the time required to execute the command sequence(s) for the program command. See

Tables 3 for further information on command definitions.

8. The device has a minimum erase and program cycle endurance of 100,000 cycles.

LATCH-UP CHARACTERISTICS

MIN.

-1.0V

MAX.

13.5V

Input Voltage with respect to GND on all pins except I/O pins

Input Voltage with respect to GND on all I/O pins

Current

-1.0V

VCC + 1.0V

+100mA

-100mA

Includes all pins except Vcc. Test conditions: VCC = 3.0V, one pin at a time.

DATA RETENTION

Parameter

Min

20

Unit

Minimum Pattern Data Retention Time

Years

P/N:PM1100

REV. 1.1, AUG. 15, 2005

62

MX29LV065M

TSOP PIN AND BGA PACKAGE CAPACITANCE

Parameter Symbol

Parameter Description

Test Set

TYP

6

MAX

7.5

5.0

12

UNIT

pF

CIN

Input Capacitance

VIN=0

TSOP

CSP

4.2

8.5

5.4

7.5

3.9

pF

COUT

CIN2

Output Capacitance

VOUT=0

VIN=0

TSOP

CSP

pF

6.5

9

pF

Control Pin Capacitance

TSOP

CSP

pF

4.7

pF

Notes:

1. Sampled, not 100% tested.

2.Test conditions TA=25°C, f=1.0MHz

P/N:PM1100

REV. 1.1, AUG. 15, 2005

63

MX29LV065M

ORDERING INFORMATION

PART NO.

ACCESS TIME

Ball Pitch/

Ball size

PACKAGE

Remark

(ns)

MX29LV065MTC-90

MX29LV065MTI-90

MX29LV065MTC-90G

MX29LV065MTI-90G

90

48 Pin TSOP

(Normal Type)

48 Pin TSOP

(Normal Type)

48 Pin TSOP

(Normal Type)

48 Pin TSOP

(Normal Type)

90

Pb-free

P/N:PM1100

REV. 1.1, AUG. 15, 2005

64

MX29LV065M

PART NAME DESCRIPTION

MX 29 LV 640 M T T C 90 G

OPTION:

G: Lead-free package

R: Restricted VCC (3.0V~3.6V)

Q: Restricted VCC (3.0V~3.6V) with Lead-free package

blank: normal

SPEED:

70: 70ns

90: 90ns

10:100ns

TEMPERATURE RANGE:

C: Commercial (0˚C to 70˚C)

I: Industrial (-40˚C to 85˚C)

PACKAGE:

M: SOP

T: TSOP

X: FBGA (CSP)

XB - 0.3mm Ball

XE - 0.4mm Ball

XC - 1.0mm Ball

BOOT BLOCK TYPE:

T: Top Boot

B: Bottom Boot

H: Uniform with Highest Sector H/W Protect

L: Uniform with Lowest Sector H/W Protect

U: Uniform Sector

REVISION:

M: NBit Technology

DENSITY & MODE:

033/320/321: 32Mb, Page Mode Flash Device

065/640/641: 64Mb, Page Mode Flash Device

128/129: 128Mb, Page Mode Flash Device

TYPE:

LV/GL: 3V standard

LA: 3V Security

DEVICE:

29:Flash

P/N:PM1100

REV. 1.1, AUG. 15, 2005

65

MX29LV065M

PACKAGE INFORMATION

P/N:PM1100

REV. 1.1, AUG. 15, 2005

66

MX29LV065M

REVISION HISTORY

Revision No. Description

Page

P1

P32

P63

P66

All

Date

APR/12/2005

AUG/15/2005

1.0

1.1

1. Removed "Preliminary"

1. Added description about Pb-free device is RoHS compliant

2.Added note 6 for ILIT parameter in DC Characteristics table

3. Added comments into performance table

4. Added Part Name Description

5. Removed 63-ball CSP package information

P/N:PM1100

REV. 1.1, AUG. 15, 2005

67

MX29LV065M

MACRONIX INTERNATIONALCO., LTD.

Headquarters:

TEL:+886-3-578-6688

FAX:+886-3-563-2888

Europe Office :

TEL:+32-2-456-8020

FAX:+32-2-456-8021

Hong Kong Office :

TEL:+86-755-834-335-79

FAX:+86-755-834-380-78

Japan Office :

Kawasaki Office :

TEL:+81-44-246-9100

FAX:+81-44-246-9105

Osaka Office :

TEL:+81-6-4807-5460

FAX:+81-6-4807-5461

Singapore Office :

TEL:+65-6346-5505

FAX:+65-6348-8096

Taipei Office :

TEL:+886-2-2509-3300

FAX:+886-2-2509-2200

MACRONIX AMERICA, INC.

TEL:+1-408-262-8887

FAX:+1-408-262-8810

http : //www.macronix.com

MACRONIX INTERNATIONAL CO., LTD. reserves the right to change product and specifications without notice.


型号：	MX29LV065MTI-90
厂家：	MACRONIX INTERNATIONAL
描述：	Flash, 8MX8, 90ns, PDSO48, 12 X 20 MM, MO-142, TSOP1-48 光电二极管
文件：	总68页 (文件大小：383K)
中文：	中文翻译
下载：	下载PDF数据表文档文件

MX29LV065MTI-90 [Macronix]

相关型号：

MX29LV065MTI-90G

MX29LV065MTMC-70G

MX29LV065MTMC-70Q

MX29LV065MTMC-90G

MX29LV065MTMC-90Q

MX29LV065MTMI-70G

MX29LV065MTMI-70Q

MX29LV065MTMI-90G

MX29LV065MTMI-90Q

MX29LV065MTTC-70G

MX29LV065MTTC-70Q

MX29LV065MTTC-90G