MX26LV400 Macronix NBit TM Memory Family 4M-BIT [512Kx8/256Kx16] CMOS SINGLE VOLTAGE 3V ONLY BOOT SECTOR HIGH SPEED eLiteFlashTM MEMORY FEATURES • Extended single - supply voltage range 3.0V to 3.6V • 524,288 x 8/262,144 x 16 switchable • Single power supply operation - 3.0V only operation for read, erase and program operation • Fast access time: 55/70ns • Low power consumption - 30mA maximum active current - 30uA typical standby current • Command register architecture - Byte/word Programming (typical) - Sector Erase (Sector structure 16K-Bytex1, 8K-Bytex2, 32K-Bytex1, and 64K-Byte x7) • Auto Erase (chip & sector) and Auto Program - Automatically erase any combination of sectors with Erase verify capability. - Automatically program and verify data at specified address • Status Reply - Data# polling & Toggle bit for detection of program and erase operation completion. • Ready/Busy# pin (RY/BY#) - Provides a hardware method of detecting program or erase operation completion. • 2,000 minimum erase/program cycles • Latch-up protected to 100mA from -1V to VCC+1V • Boot Sector Architecture - T = Top Boot Sector - B = Bottom Boot Sector • Package type: - 48-pin TSOP - 48-ball CSP • Compatibility with JEDEC standard - Pinout and software compatible with single-power supply Flash • 20 years data retention GENERAL DESCRIPTION The MX26LV400 is a 4-mega bit high speed Flash memory organized as 512K bytes of 8 bits or 256K words of 16 bits. MXIC's high speed Flash memories offer the most cost-effective and reliable read/write non-volatile random access memory. The MX26LV400 is packaged in 48-pin TSOP, and 48-ball CSP. It is designed to be reprogrammed and erased in system or in standard EPROM programmers. for 100% TTL level control inputs and fixed power supply levels during erase and programming, while maintaining maximum EPROM compatibility. MXIC high speed Flash technology reliably stores memory contents even after 2,000 erase and program cycles. The MXIC cell is designed to optimize the erase and programming mechanisms. In addition, the combination of advanced tunnel oxide processing and low internal electric fields for erase and program operations produces reliable cycling. The MX26LV400 uses a 3.0V~3.6V VCC supply to perform the High Reliability Erase and auto Program/Erase algorithms. The standard MX26LV400 offers access time as fast as 55ns, allowing operation of high-speed microprocessors without wait states. To eliminate bus contention, the MX26LV400 has separate chip enable (CE#) and output enable (OE#) controls. The highest degree of latch-up protection is achieved with MXIC's proprietary non-epi process. Latch-up protection is proved for stresses up to 100 milliamperes on address and data pin from -1V to VCC + 1V. MXIC's high speed Flash memories augment EPROM functionality with in-circuit electrical erasure and programming. The MX26LV400 uses a command register to manage this functionality. The command register allows P/N:PM1094 REV. 1.0, NOV. 08, 2004 1 MX26LV400 PIN CONFIGURATIONS PIN DESCRIPTION 48 TSOP (Standard Type) (12mm x 20mm) A15 A14 A13 A12 A11 A10 A9 A8 NC NC WE# RESET# NC NC RY/BY# NC A17 A7 A6 A5 A4 A3 A2 A1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 MX26LV400 SYMBOL PIN NAME A16 BYTE# GND Q15/A-1 Q7 Q14 Q6 Q13 Q5 Q12 Q4 VCC Q11 Q3 Q10 Q2 Q9 Q1 Q8 Q0 OE# GND CE# A0 A0~A17 Address Input Q0~Q14 Data Input/Output Q15/A-1 Q15(Word mode)/LSB addr(Byte mode) CE# Chip Enable Input WE# Write Enable Input BYTE# Word/Byte Selection input RESET# Hardware Reset Pin OE# Output Enable Input RY/BY# Ready/Busy Output VCC Power Supply Pin (3.0V~3.6V) GND Ground Pin 48-Ball CSP Ball Pitch = 0.8 mm, Top View, Balls Facing Down A B C D E F G 6 A13 A12 A14 A15 A16 5 A9 A8 A10 A11 Q7 Q14 Q13 Q6 4 WE# RESET# NC NC Q5 Q12 Vcc Q4 3 RY/BY# NC NC NC Q2 Q10 Q11 Q3 2 A7 A17 A6 A5 Q0 Q8 Q9 Q1 1 A3 A4 A2 A1 A0 CE# OE# GND BYTE# Q15/A-1 P/N:PM1094 H GND REV. 1.0, NOV. 08, 2004 2 MX26LV400 BLOCK STRUCTURE Table 1: MX26LV400T SECTOR ARCHITECTURE Sector Sector Size Byte Mode Word Mode Address range Byte Mode (x8) Word Mode (x16) Sector Address A17 A16 A15 A14 A13 A12 SA0 64Kbytes 32Kwords 00000-0FFFF 00000-07FFF 0 0 0 X X X SA1 64Kbytes 32Kwords 10000-1FFFF 08000-0FFFF 0 0 1 X X X SA2 64Kbytes 32Kwords 20000-2FFFF 10000-17FFF 0 1 0 X X X SA3 64Kbytes 32Kwords 30000-3FFFF 18000-1FFFF 0 1 1 X X X SA4 64Kbytes 32Kwords 40000-4FFFF 20000-27FFF 1 0 0 X X X SA5 64Kbytes 32Kwords 50000-5FFFF 28000-2FFFF 1 0 1 X X X SA6 64Kbytes 32Kwords 60000-6FFFF 30000-37FFF 1 1 0 X X X SA7 32Kbytes 16Kwords 70000-77FFF 38000-3BFFF 1 1 1 0 X X SA8 8Kbytes 4Kwords 78000-79FFF 3C000-3CFFF 1 1 1 1 0 0 SA9 8Kbytes 4Kwords 7A000-7BFFF 3D000-3DFFF 1 1 1 1 0 1 SA10 16Kbytes 8Kwords 7C000-7FFFF 3E000-3FFFF 1 1 1 1 1 X Note: Byte mode:address range A17:A-1, word mode:address range A17:A0. Table 2: MX26LV400B SECTOR ARCHITECTURE Sector Sector Size Byte Mode Word Mode Address range Byte Mode (x8) Word Mode (x16) Sector Address A17 A16 A15 A14 A13 A12 SA0 16Kbytes 8Kwords 00000-03FFF 00000-01FFF 0 0 0 0 0 X SA1 8Kbytes 4Kwords 04000-05FFF 02000-02FFF 0 0 0 0 1 0 SA2 8Kbytes 4Kwords 06000-07FFF 03000-03FFF 0 0 0 0 1 1 SA3 32Kbytes 16Kwords 08000-0FFFF 04000-07FFF 0 0 0 1 X X SA4 64Kbytes 32Kwords 10000-1FFFF 08000-0FFFF 0 0 1 X X X SA5 64Kbytes 32Kwords 20000-2FFFF 10000-17FFF 0 1 0 X X X SA6 64Kbytes 32Kwords 30000-3FFFF 18000-1FFFF 0 1 1 X X X SA7 64Kbytes 32Kwords 40000-4FFFF 20000-27FFF 1 0 0 X X X SA8 64Kbytes 32Kwords 50000-5FFFF 28000-2FFFF 1 0 1 X X X SA9 64Kbytes 32Kwords 60000-6FFFF 30000-37FFF 1 1 0 X X X SA10 64Kbytes 32Kwords 70000-7FFFF 38000-3FFFF 1 1 1 X X X Note: Byte mode:address range A17:A-1, word mode:address range A17:A0. P/N:PM1094 REV. 1.0, NOV. 08, 2004 3 MX26LV400 BLOCK DIAGRAM CE# OE# WE# RESET# CONTROL INPUT HIGH VOLTAGE LOGIC LATCH BUFFER Y-DECODER AND X-DECODER ADDRESS A0-A17 PROGRAM/ERASE WRITE STATE MACHINE (WSM) STATE REGISTER FLASH ARRAY Y-PASS GATE SENSE AMPLIFIER PGM DATA HV ARRAY SOURCE HV COMMAND DATA DECODER COMMAND DATA LATCH PROGRAM DATA LATCH Q0-Q15/A-1 I/O BUFFER P/N:PM1094 REV. 1.0, NOV. 08, 2004 4 MX26LV400 the device automatically times the erase pulse width, provides the erase verification, and counts the number of sequences. A status bit toggling between consecutive read cycles provides feedback to the user as to the status of the erasing operation. AUTOMATIC PROGRAMMING The MX26LV400 is word/byte programmable using the Automatic Programming algorithm. The Automatic Programming 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 statemachine which controls the erase and programming circuitry. During write cycles, the command register internally latches address and data needed for the programming 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# or CE#, whichever happens first. AUTOMATIC PROGRAMMING ALGORITHM MXIC's Automatic Programming algorithm requires the user to only write program set-up commands (including 2 unlock write cycle and A0H) and a program command (program data and address). The device automatically times the programming pulse width, provides the program verification, and counts the number of sequences. A status bit similar to DATA# polling and a status bit toggling between consecutive read cycles, provide feedback to the user as to the status of the programming operation. Refer to write operation status, table 7, for more information on these status bits. MXIC's high speed Flash technology combines years of EPROM experience to produce the highest levels of quality, reliability, and cost effectiveness. The MX26LV400 electrically erases all bits simultaneously using FowlerNordheim tunneling. The bytes are programmed by using the EPROM programming mechanism of hot electron injection. During a program cycle, the state-machine will control the program sequences and command register will not respond to any command set. After the state machine has completed its task, it will allow the command register to respond to its full command set. AUTOMATIC CHIP ERASE The entire chip is bulk erased using 10 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 verification of electrical erase are controlled internally within the device. AUTOMATIC SELECT The auto select mode provides manufacturer and device identification, through identifier codes output on Q7~Q0. This mode is mainly adapted for programming equipment on the device to be programmed with its programming algorithm. When programming by high voltage method, automatic select mode requires VID (11V to 12V) on address pin A9 and other address pin A6, A1 and A0 as referring to Table 3. In addition, to access the automatic select codes in-system, the host can issue the automatic select command through the command register without requiring VID, as shown in table 4. AUTOMATIC SECTOR ERASE The MX26LV400 is sector(s) erasable using MXIC's Auto Sector Erase algorithm. The Automatic Sector Erase algorithm automatically programs the specified sector(s) prior to electrical erase. The timing and verification of electrical erase are controlled internally within the device. An erase operation can erase one sector, multiple sectors, or the entire device. AUTOMATIC ERASE ALGORITHM MXIC's Automatic Erase algorithm requires the user to write commands to the command register using standard microprocessor write timings. The device will automatically pre-program and verify the entire array. Then P/N:PM1094 REV. 1.0, NOV. 08, 2004 5 MX26LV400 TABLE 3. MX26LV400 AUTO SELECT MODE OPERATION A17 A11 Description Mode CE# OE# WE# | A9 | A12 A10 Manufacturer Code A8 A6 A5 A1 A0 | | A7 A2 Q15~Q0 L L H X X VID X L X L L C2H Word L L H X X VID X L X L H 22B9H Silicon (Top Boot Block) Byte L L H X X VID X L X L H XXB9H ID Device ID Word L L H X X VID X L X L H 22BAH (Bottom Boot Block) Byte L L H X X VID X L X L H XXBAH Read Device ID NOTE:SA=Sector Address, X=Don't Care, L=Logic Low, H=Logic High P/N:PM1094 REV. 1.0, NOV. 08, 2004 6 MX26LV400 TABLE 4. MX26LV400 COMMAND DEFINITIONS Command Bus First Bus Cycle Cycle Addr Second Bus Cycle Data Addr Third Bus Cycle Fourth Bus Cycle Data Addr Data Addr Data Fifth Bus Cycle Addr Sixth Bus Cycle Data Addr Data Reset 1 XXXH F0H Read 1 RA Word 4 555H AAH 2AAH 55H 555H 90H ADI DDI Byte 4 AAAH AAH 555H 55H AAAH 90H ADI DDI Word 4 555H AAH 2AAH 55H 555H A0H PA PD Byte 4 AAAH AAH 555H 55H AAAH A0H PA PD Word 6 555H AAH 2AAH 55H 555H 80H 555H AAH 2AAH 55H 555H 10H Byte 6 AAAH AAH 555H 55H AAAH 80H AAAH AAH 555H 55H AAAH 10H Word 6 555H AAH 2AAH 55H 555H 80H 555H AAH 2AAH 55H SA 30H Byte 6 AAAH AAH 555H 55H AAAH 80H AAAH AAH 555H 55H SA 30H Read Silicon ID Program Chip Erase Sector Erase RD Note: 1. ADI = Address of Device identifier; A1=0, A0 = 0 for manufacturer code,A1=0, A0 = 1 for device code. A2-A17=do not care. (Refer to table 3) DDI = Data of Device identifier : C2H for manufacture code, 22B9/B9(Top), and 22BA/BA(Bottom) for device code. X = X can be VIL or VIH RA=Address of memory location to be read. RD=Data to be read at location RA. 2. PA = Address of memory location to be programmed. PD = Data to be programmed at location PA. SA = Address of the sector. 3. The system should generate the following address patterns: 555H or 2AAH to Address A10~A0 in word mode/AAAH or 555H to Address A10~A-1 in byte mode. Address bit A11~A17=X=Don't care for all address commands except for Program Address (PA) and Sector Address (SA). Write Sequence may be initiated with A11~A17 in either state. P/N:PM1094 REV. 1.0, NOV. 08, 2004 7 MX26LV400 COMMAND DEFINITIONS Device operations are selected by writing specific address 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 5 defines the valid register command sequences. TABLE 5. MX26LV400 BUS OPERATION ADDRESS DESCRIPTION CE# OE# WE# RESET# A17 A10 A9 A8 A6 A5 A1 A0 A12 A11 Read L L Q8~Q15 H H A7 AIN Q0~Q7 A2 Dout BYTE BYTE =VIH =VIL Dout Q8~Q14 =High Z Q15=A-1 Write L H L H AIN DIN(3) DIN Reset X X X L X High Z High Z High Z Output Disable L H H H X High Z High Z High Z Vcc± X X Vcc± X High Z High Z High Z Standby 0.3V 0.3V NOTES: 1. Manufacturer and device codes may also be accessed via a command register write sequence. Refer to Table 4. 2. VID is the Silicon-ID-Read high voltage, 11V to 12V. 3. Refer to Table 5 for valid Data-In during a write operation. 4. X can be VIL or VIH. P/N:PM1094 REV. 1.0, NOV. 08, 2004 8 MX26LV400 Characteristics" section contains timing specification table and timing diagrams for write operations. 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 remain at VIH. STANDBY MODE When using both pins of CE# and RESET#, the device enter CMOS Standby with both pins held at Vcc ± 0.3V. If CE# and RESET# are held at VIH, but not within the range of VCC ± 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 internal state machine is set for reading array data upon device power-up, or after a hardware reset. This ensures that no spurious alteration of the memory content occurs during the power transition. 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 device data outputs. The device remains enabled for read access until the command register contents are altered. 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. WRITE COMMANDS/COMMAND SEQUENCES To program data to the device or erase sectors of memory , the system must drive WE# and CE# to VIL, and OE# to VIH. RESET# OPERATION The "word/byte Program Command Sequence" section has details on programming data to the device. 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 An erase operation can erase one sector, multiple sectors , 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 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. 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 at VIL but not within VSS±0.3V, the standby current will be greater. After the system writes the autoselect command sequence, the device enters the autoselect mode. The system can then read autoselect 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 Autoselect Mode and Autoselect Command Sequence section for more information. The RESET# pin may be tied to system reset circuitry. A system reset would that also reset the high speed Flash, enabling the system to read the boot-up firmware from the high speed Flash. ICC2 in the DC Characteristics table represents the active current specification for the write mode. The "AC If RESET# is asserted during a program or erase operation, the RY/BY# pin remains a "0" (busy) until the inter- P/N:PM1094 REV. 1.0, NOV. 08, 2004 9 MX26LV400 nal 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. SET-UP AUTOMATIC CHIP/SECTOR ERASE COMMANDS Refer to the AC Characteristics tables for RESET# parameters and to Figure 14 for the timing diagram. The read or reset operation is initiated by writing the read/reset command sequence into the command register. Microprocessor read cycles retrieve array data. The device remains enabled for reads until the command register contents are altered. The Automatic Chip Erase does not require the device to be entirely pre-programmed prior to executing the Automatic Chip Erase. Upon executing the Automatic Chip Erase, the device will automatically program and verify the entire memory for an all-zero data pattern. When the device is automatically verified to contain an all-zero pattern, a self-timed chip erase and verify begin. The erase and verify operations are completed when the data on Q7 is "1" at which time the device returns to the Read mode. The system is not required to provide any control or timing during these operations. If program-fail or erase-fail happen, the write of F0H will reset the device to abort the operation. A valid command must then be written to place the device in the desired state. When using the Automatic Chip 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). SILICON-ID READ COMMAND If the Erase operation was unsuccessful, the data on Q5 is "1" (see Table 7), indicating the erase operation exceed internal timing limit. 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 sector erase command 30H. READ/RESET COMMAND High speed Flash memories are intended for use in applications where the local CPU alters memory contents. As such, manufacturer and device codes must be accessible while the device resides in the target system. PROM programmers typically access signature codes by raising A9 to a high voltage (VID). However, multiplexing high voltage onto address lines is not generally desired system design practice. The automatic erase begins on the rising edge of the last WE# or CE# pulse, whichever happens first in the command sequence and terminates when the data on Q7 is "1" at which time the device returns to the Read mode, or the data on Q6 stops toggling for two consecutive read cycles at which time the device returns to the Read mode. The MX26LV400 contains a Silicon-ID-Read operation to supple traditional PROM programming methodology. The operation is initiated by writing the read silicon ID command sequence into the command register. Following the command write, a read cycle with A1=VIL, A0=VIL retrieves the manufacturer code of C2H/00C2H. P/N:PM1094 REV. 1.0, NOV. 08, 2004 10 MX26LV400 TABLE 6. SILICON ID CODE Pins A1 Q15~Q8 Q7 Q6 Q5 Q4 Q3 Q2 Q1 Q0 Code (Hex) Word VIL VIL 00H 1 1 0 0 0 0 1 0 00C2H Byte VIL VIL X 1 1 0 0 0 0 1 0 C2H Device code Word VIH VIL 22H 1 0 1 1 1 0 0 1 22B9H for MX26LV400T Byte VIH VIL X 1 0 1 1 1 0 0 1 B9H Device code Word VIH VIL 22H 1 0 1 1 1 0 1 0 22BAH for MX26LV400B Byte VIL X 1 0 1 1 1 0 1 0 BAH Manufacture code A0 VIH READING ARRAY DATA RESET COMMAND The device is automatically set to reading array data after device power-up. No commands are required to retrieve data. The device is also ready to read array data after completing an Automatic Program or Automatic Erase algorithm. Writing the reset command to the device resets the device to reading array data. Address bits are don't care for this command. The reset command may be written between the sequence 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. The system must issue the reset command to re-enable the device for reading array data if Q5 goes high, or while in the autoselect mode. See the "Reset Command" section, next. The reset command may be written between the sequence cycles in a program command sequence before programming begins. This resets the device to reading array data. Once programming begins, however, the device ignores reset commands until the operation is complete. The reset command may be written between the sequence cycles in an SILICON ID READ command sequence. Once in the SILICON ID READ mode, the reset command must be written to return to reading array data. If Q5 goes high during a program or erase operation, writing the reset command returns the device to reading array data. P/N:PM1094 REV. 1.0, NOV. 08, 2004 11 MX26LV400 followed by the program set-up command. The program address and data are written next, which in turn initiate the Embedded Program algorithm. The system is not required to provide further controls or timings. The device automatically generates the program pulses and verifies the programmed cell margin. Table 1 shows the address and data requirements for the word/byte program command sequence. SECTOR ERASE COMMANDS The Automatic Sector Erase does not require the device to be entirely pre-programmed prior to executing the Automatic Sector Erase Set-up 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 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. 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 either the data on Q7 is "1" at which time the device returns to the Read mode, or 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. Any commands written to the device during the Em-bedded Program Algorithm are ignored. Note that a hardware reset immediately terminates the programming operation. The word/byte Program command sequence should be reinitiated once the device has reset to reading array data, to ensure data integrity. 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 command 80H. Two more "unlock" write cycles are then followed 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 preceding WE# 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 Erase Timer.) Any command other than Sector Erase (30H) during the time-out period resets the device to read mode. 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 operation and set Q5 to "1" , or cause the Data# Polling algorithm to indicate the operation was successful. However, a succeeding read will show that the data is still "0". Only erase operations can convert a "0" to a "1". 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 7 and the following subsections describe the functions of these bits. Q7, RY/BY#, and Q6 each offer a method for determining whether a program or erase operation is complete or in progress. These three bits are discussed first. WORD/BYTE PROGRAM COMMAND SEQUENCE The device programs one byte of data for each program operation. The command sequence requires four bus cycles, and is initiated by writing two unlock write cycles, P/N:PM1094 REV. 1.0, NOV. 08, 2004 12 MX26LV400 Q7: Data# Polling Q6:Toggle BIT I The Data# Polling bit, Q7, indicates to the host system whether an Automatic Algorithm is in progress or completed. Data# Polling is valid after the rising edge of the final WE# pulse in the program or erase command sequence. Toggle Bit I on Q6 indicates whether an Automatic Program or Erase algorithm is in progress or complete. Toggle Bit I may be read at any address, and is valid after the rising edge of the final WE# or CE#, whichever happens first, in the command sequence (prior to the program or erase operation), and during the sector time-out. During the Automatic Program algorithm, the device outputs on Q7 the complement of the datum programmed to Q7. When the Automatic Program algorithm is complete, the device outputs the datum programmed to Q7. The system must provide the program address to read valid status information on Q7. During an Automatic Program or Erase algorithm operation, 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. When the device is actively erasing (that is, the Automatic Erase algorithm is in progress), Q6 toggling. However, the system must also use Q2 to determine which sectors are erasing. Alternatively, the system can use Q7. During the Automatic Erase algorithm, Data# Polling produces a "0" on Q7. When the Automatic Erase algorithm is complete, Data# Polling produces a "1" on Q7. This is analogous to the complement/true datum out-put 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. Q6 stops toggling once the Automatic Program algorithm is complete. Table 7 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). Toggle Bit II is valid after the rising edge of the final WE# or CE#, whichever happens first, in the command sequence. RY/BY# : Ready/Busy 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 when the sector is actively erasing. Q6, by comparison, indicates when the device is actively erasing, but cannot distinguish which sectors are selected for erasure. Thus, both status bits are required for sectors and mode information. Refer to Table 8 to compare outputs for Q2 and Q6. The RY/BY# is a dedicated, open-drain output pin that indicates whether an Automatic Erase/Program algorithm is in progress or complete. The RY/BY# status is valid after the rising edge of the final WE# or CE#, whichever happens first, 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. If the output is high (Ready), the device is ready to read array data, or is in the standby mode. Reading Toggle Bits Q6/ Q2 Table 7 shows the outputs for RY/BY# during write operation. 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 P/N:PM1094 REV. 1.0, NOV. 08, 2004 13 MX26LV400 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. operation, it specifies that the entire chip is bad or combination of sectors are bad. If this time-out condition occurs during the word/byte programming operation, it specifies that the entire sector containing 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 system 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 operation. If it is still toggling, the device did not complete the operation successfully, and the system must write the reset command to return to reading array data. The time-out condition will not appear if a user tries to program a non blank location without erasing. Please note that this is not a device failure condition since the device was incorrectly used. 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 status as described in the previous paragraph. Alternatively, it may choose to perform other system tasks. In this case, the system must start at the beginning of the algorithm when it returns to determine the status of the operation. Q5 Exceeded Timing Limits 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 successfully completed. Data# Polling and Toggle Bit are the only operating functions of the device under this condition. If this time-out condition occurs during sector erase operation, it specifies that a particular sector is bad and it may not be reused. However, other sectors are still functional and may be used for the program or erase operation. 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. If this time-out condition occurs during the chip erase P/N:PM1094 REV. 1.0, NOV. 08, 2004 14 MX26LV400 TABLE 7. WRITE OPERATION STATUS Status Q7 Q6 (Note1) In Progress Word/Byte Program in Auto Program Algorithm Q7# Q5 Q3 Q2 RY/BY# N/A No 0 (Note2) Toggle 0 Toggle Auto Erase Algorithm Exceeded Word/Byte Program in Auto Program Algorithm 0 Toggle 0 1 Toggle 0 Q7# Toggle 1 N/A No 0 Time Limits Toggle Auto Erase Algorithm 0 Toggle 1 1 Toggle 0 Note: 1. Q7 and Q2 require a valid address when reading status information. Refer to the appropriate subsection for further details. 2. Q5 switches to '1' when an Auto Program or Auto Erase operation has exceeded the maximum timing limits. See "Q5 : Exceeded Timing Limits" for more information. P/N:PM1094 REV. 1.0, NOV. 08, 2004 15 MX26LV400 Q3 Sector Erase Timer POWER SUPPLY DECOUPLING In order to reduce power switching effect, each device should have a 0.1uF ceramic capacitor connected between its VCC and GND. 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 and Toggle Bit are valid after the initial sector erase command sequence. POWER-UP SEQUENCE The MX26LV400 powers up in the Read only mode. In addition, the memory contents may only be altered after successful completion of the predefined command sequences. 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 additional 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. DATA PROTECTION The MX26LV400 is designed to offer protection against accidental erasure or programming caused by spurious system level signals that may exist during power transition. 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 specific command sequences. The device also incorporates several features to prevent inadvertent write cycles resulting from VCC power-up and power-down transition or system noise. 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. P/N:PM1094 REV. 1.0, NOV. 08, 2004 16 MX26LV400 ABSOLUTE MAXIMUM RATINGS OPERATING RATINGS Storage Temperature Plastic Packages . . . . . . . . . . . . . ..... -65oC to +150oC Ambient Temperature with Power Applied. . . . . . . . . . . . . .... -65oC to +125oC Voltage with Respect to Ground VCC (Note 1) . . . . . . . . . . . . . . . . . -0.5 V to +4.0 V A9, OE#, and RESET# (Note 2) . . . . . . . . . . . . . . . . -0.5 V to +12 V All other pins (Note 1) . . . . . . . -0.5 V to VCC +0.5 V Output Short Circuit Current (Note 3) . . . . . . 200 mA Commercial (C) Devices Ambient Temperature (TA ). . . . . . . . . . . . 0° C to +70° C VCC Supply Voltages VCC for full voltage range. . . . . . . . . . . +3.0 V to 3.6 V Operating ranges define those limits between which the functionality of the device is guaranteed. Notes: 1. Minimum DC voltage on input or I/O pins is -0.5 V. During voltage transitions, input or I/O pins may overshoot VSS to -2.0 V for periods of up to 20 ns. Maximum DC voltage on input or I/O pins is VCC +0.5 V. During voltage transitions, input or I/O pins may overshoot to VCC +2.0 V for periods up to 20 ns. 2. Minimum DC input voltage on pins A9, OE#, and RESET# is -0.5 V. During voltage transitions, A9, OE#, and RESET# may overshoot VSS to -2.0 V for periods of up to 20 ns. Maximum DC input voltage on pin A9 is +12 V which may overshoot to 13.5V for periods up to 20 ns. 3. No more than one output may be shorted to ground at a time. Duration of the short circuit should not be greater than one second. Stresses above those listed under "Absolute Maximum Ratings" may cause permanent damage to the device. This is a stress rating only; functional operation of the device at these or any other conditions above those indicated in the operational sections of this data sheet is not implied. Exposure of the device to absolute maximum rating conditions for extended periods may affect device reliability. P/N:PM1094 REV. 1.0, NOV. 08, 2004 17 MX26LV400 CAPACITANCE TA = 25oC, f = 1.0 MHz SYMBOL CIN1 CIN2 COUT PARAMETER Input Capacitance Control Pin Capacitance Output Capacitance MIN. TYP MAX. 8 12 12 UNIT pF pF pF CONDITIONS VIN = 0V VIN = 0V VOUT = 0V TABLE 8. DC CHARACTERISTICS TA = 0oC to 70oC, VCC = 3.0V~3.6V MX26LV400 Symbol PARAMETER ILI ILIT MIN. TYP MAX. UNIT CONDITIONS Input Leakage Current ±1 ±3 uA VIN = VSS to VCC A9 Input Leakage Current 35 200 uA VCC=VCC max; A9=12V ILO ±1 Output Leakage Current uA VOUT = VSS to VCC, VCC=VCC max ICC1 VCC Active Read Current 20 30 mA CE#=VIL, @5MHz 8 14 mA OE#=VIH @1MHz ICC2 VCC Active write Current 26 30 mA CE#=VIL, OE#=VIH ICC3 VCC Standby Current 30 100 uA CE#; RESET#=VCC ± 0.3V ICC4 VCC Standby Current 30 100 uA RESET#=VSS ± 0.3V -0.5 0.8 V 0.7xVCC VCC+0.3 V 11 12 V VCC=3.3V 0.45 V IOL = 4.0mA, During Reset VIL Input Low Voltage (Note 1) VIH Input High Voltage VID Voltage for Automatic Select VOL Output Low Voltage VCC= VCC min VOH1 Output High Voltage (TTL) 0.85xVCC IOH = -2mA, VCC=VCC min VOH2 Output High Voltage VCC-0.4 IOH = -100uA, VCC min (CMOS) NOTES: 1. VIL min. = -1.0V for pulse width is equal to or less than 50 ns. VIL min. = -2.0V for pulse width is equal to or less than 20 ns. 2. VIH max. = VCC + 1.5V for pulse width is equal to or less than 20 ns If VIH is over the specified maximum value, read operation cannot be guaranteed. 3. Automatic sleep mode enable the low power mode when addresses remain stable for tACC +30ns. P/N:PM1094 REV. 1.0, NOV. 08, 2004 18 MX26LV400 AC CHARACTERISTICS TA = 0oC to 70oC, VCC = 3.0V~3.6V TABLE 9. READ OPERATIONS 26LV400-55 26LV400-70 SYMBOLPARAMETER MIN. MIN. tRC Read Cycle Time (Note 1) 55 tACC Address to Output Delay 55 70 ns CE#=OE#=VIL tCE CE# to Output Delay 55 70 ns OE#=VIL tOE OE# to Output Delay 25 30 ns CE#=VIL tDF OE# High to Output Float (Note1) 0 25 ns CE#=VIL tOEH Output Read 0 0 ns Enable Toggle and 10 10 ns Hold Time Data# Polling 0 0 ns tOH Address to Output hold MAX. MAX. UNIT 70 25 0 CONDITIONS ns CE#=OE#=VIL NOTE: TEST CONDITIONS: 1. Not 100% tested. 2. tDF is defined as the time at which the output achieves the open circuit condition and data is no longer driven. • Input pulse levels: 0V/3.0V. • Input rise and fall times is equal to or less than 5ns. • Output load: 1 TTL gate + 100pF (Including scope and jig), for 26LV400-70. 1 TTL gate + 30pF (Including scope and jig) for 26LV400-55. • Reference levels for measuring timing: 1.5V. P/N:PM1094 REV. 1.0, NOV. 08, 2004 19 MX26LV400 SWITCHING TEST CIRCUITS DEVICE UNDER 2.7K ohm +3.3V TEST CL 6.2K ohm DIODES=IN3064 OR EQUIVALENT CL= 100pF Including jig capacitance for MX26LV400T/B-70 (30pF for MX26LV400T/B-55) SWITCHING TEST WAVEFORMS 3.0V TEST POINTS 0V INPUT OUTPUT AC TESTING: Inputs are driven at 3.0V for a logic "1" and 0V for a logic "0". Input pulse rise and fall times are < 5ns. P/N:PM1094 REV. 1.0, NOV. 08, 2004 20 MX26LV400 FIGURE 1. READ TIMING WAVEFORMS tRC VIH Addresses ADD Valid VIL tACC tCE CE# VIH VIL WE# VIH VIL tOE tOEH tDF VIH OE# VIL tACC Outputs VOH HIGH Z tOH DATA Valid HIGH Z VOL VIH RESET# VIL P/N:PM1094 REV. 1.0, NOV. 08, 2004 21 MX26LV400 AC CHARACTERISTICS TA = 0oC to 70oC, VCC = 3.0V~3.6V TABLE 10. Erase/Program Operations 26LV400-55 26LV400-70 SYM- MIN. UNIT BOL PARAMETER MIN. MAX. MAX. tWC Write Cycle Time (Note 1) 55 70 ns tAS Address Setup Time 0 0 ns tAH Address Hold Time 45 45 ns tDS Data Setup Time 35 35 ns tDH Data Hold Time 0 0 ns tOES Output Enable Setup Time 0 0 ns tGHWL Read Recovery Time Before Write 0 0 ns (OE# High to WE# Low) tCS CE# Setup Time 0 0 ns tCH CE# Hold Time 0 0 ns tWP Write Pulse Width 35 35 ns tWPH Write Pulse Width High 30 30 ns tWHWH1 Programming Operation (Note 2) 55/70(TYP.) 55/70(TYP.) us (Byte/Word program time) tWHWH2 Sector Erase Operation (Note 2) 2.4(TYP.) 2.4(TYP.) sec tVCS VCC Setup Time (Note 1) 50 50 us tRB Recovery Time from RY/BY# 0 0 ns tBUSY Program/Erase Valid to RY/BY# Delay 90 90 ns tBAL Sector Address Load Time 50 50 us NOTES: 1. Not 100% tested. 2. See the "Erase and Programming Performance" section for more information. P/N:PM1094 REV. 1.0, NOV. 08, 2004 22 MX26LV400 AC CHARACTERISTICS TA = 0oC to 70oC, VCC = 3.0V~3.6V TABLE 11. Alternate CE# Controlled Erase/Program Operations 26LV400-55 26LV400-70 MIN. SYMBOL PARAMETER MIN. tWC Write Cycle Time (Note 1) 55 70 ns tAS Address Setup Time 0 0 ns tAH Address Hold Time 45 45 ns tDS Data Setup Time 35 35 ns tDH Data Hold Time 0 0 ns tOES Output Enable Setup Time 0 0 ns tGHEL Read Recovery Time Before Write 0 0 ns tWS WE# Setup Time 0 0 ns tWH WE# Hold Time 0 0 ns tCP CE# Pulse Width 35 35 ns tCPH CE# Pulse Width High 30 30 ns tWHWH1 Programming Byte 55(Typ.) 55(Typ.) us Operation(note2) Word 70(Typ.) 70(Typ.) us 2.4(Typ.) 2.4(Typ.) sec tWHWH2 Sector Erase Operation (note2) MAX. MAX. UNIT NOTE: 1. Not 100% tested. 2. See the "Erase and Programming Performance" section for more information. P/N:PM1094 REV. 1.0, NOV. 08, 2004 23 MX26LV400 FIGURE 2. COMMAND WRITE TIMING WAVEFORM VCC Addresses 3V VIH ADD Valid VIL tAH tAS WE# VIH VIL tOES tWPH tWP tCWC CE# VIH VIL tCS OE# tCH VIH VIL tDS tDH VIH Data DIN VIL P/N:PM1094 REV. 1.0, NOV. 08, 2004 24 MX26LV400 AUTOMATIC PROGRAMMING TIMING WAVEFORM ing after automatic programming starts. Device outputs DATA# during programming and DATA# after programming on Q7. (Q6 is for toggle bit; see toggle bit, DATA# polling, timing waveform) One byte data is programmed. Verify in fast algorithm and additional verification by external control are not required because these operations are executed automatically by internal control circuit. Programming completion can be verified by DATA# polling and toggle bit check- FIGURE 3. AUTOMATIC PROGRAMMING TIMING WAVEFORM Program Command Sequence(last two cycle) tWC 555h Address Read Status Data (last two cycle) tAS PA PA PA tAH CE# tCH tGHWL OE# tWHWH1 tWP WE# tCS tWPH tDS tDH A0h Status 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 P/N:PM1094 REV. 1.0, NOV. 08, 2004 25 MX26LV400 FIGURE 4. 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 from system Increment Address No Verify Byte Ok ? YES No Last Address ? YES Auto Program Completed P/N:PM1094 REV. 1.0, NOV. 08, 2004 26 MX26LV400 FIGURE 5. CE# CONTROLLED PROGRAM TIMING WAVEFORM 555 for program 2AA for erase PA for program SA for sector erase 555 for chip erase Data# Polling Address PA tWC tAS tAH tWH WE# tGHEL OE# tCP tWHWH1 or 2 CE# tWS tCPH tDS tBUSY tDH DQ7 DOUT Data tRH A0 for program 55 for erase PD for program 30 for sector erase 10 for chip erase RESET# RY/BY# NOTES: 1.PA=Program Address, PD=Program Data, DOUT=Data Out, DQ7=complement of data written to device. 2.Figure indicates the last two bus cycles of the command sequence. P/N:PM1094 REV. 1.0, NOV. 08, 2004 27 MX26LV400 AUTOMATIC CHIP ERASE TIMING WAVEFORM All data in chip are erased. External erase verification is not required because data is verified automatically by internal control circuit. Erasure completion can be verified by DATA# polling and toggle bit checking after auto- matic erase starts. Device outputs 0 during erasure and 1 after erasure on Q7. (Q6 is for toggle bit; see toggle bit, DATA# polling, timing waveform) FIGURE 6. AUTOMATIC CHIP ERASE TIMING WAVEFORM Erase Command Sequence(last two cycle) tWC 2AAh Address Read Status Data tAS VA 555h VA tAH CE# tCH tGHWL OE# tWHWH2 tWP WE# tCS tWPH tDS tDH 55h In Progress Complete 10h Data tBUSY tRB RY/BY# tVCS VCC NOTES: SA=sector address(for Sector Erase), VA=Valid Address for reading status data(see "Write Operation Status"). P/N:PM1094 REV. 1.0, NOV. 08, 2004 28 MX26LV400 FIGURE 7. 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 Pall from System NO Data=FFh ? YES Auto Chip Erase Completed P/N:PM1094 REV. 1.0, NOV. 08, 2004 29 MX26LV400 AUTOMATIC SECTOR ERASE TIMING WAVEFORM Sector indicated by A12 to A17 are erased. External erase verify is not required because data are verified automatically by internal control circuit. Erasure completion can be verified by DATA# polling and toggle bit check- ing after automatic erase starts. Device outputs 0 during erasure and 1 after erasure on Q7. (Q6 is for toggle bit; see toggle bit, DATA# polling, timing waveform) FIGURE 8. AUTOMATIC SECTOR ERASE TIMING WAVEFORM Erase Command Sequence(last two cycle) tWC Sector Address 0 2AAh Address Read Status Data tAS Sector Address 1 Sector Address n VA VA tAH CE# tCH tGHWL OE# WE# tCS tWHWH2 tBAL tWP tWPH tDS tDH 55h 30h 30h 30h In Progress Complete Data tBUSY tRB RY/BY# tVCS VCC NOTES: SA=sector address(for Sector Erase), VA=Valid Address for reading status data(see "Write Operation Status"). P/N:PM1094 REV. 1.0, NOV. 08, 2004 30 MX26LV400 FIGURE 9. 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 Last Sector to Erase NO YES Data Poll from System Data=FFh NO YES Auto Sector Erase Completed P/N:PM1094 REV. 1.0, NOV. 08, 2004 31 MX26LV400 WRITE OPERATION STATUS FIGURE 10. DATA# POLLING ALGORITHM Start Read Q7~Q0 Add.=VA(1) Yes Q7 = Data ? No No Q5 = 1 ? Yes Read Q7~Q0 Add.=VA Yes Q7 = Data ? (2) No FAIL Pass NOTE : 1.VA=Valid address for programming 2.Q7 should be re-checked even Q5="1" because Q7 may change simultaneously with Q5. P/N:PM1094 REV. 1.0, NOV. 08, 2004 32 MX26LV400 FIGURE 11. TOGGLE BIT ALGORITHM Start Read Q7-Q0 Read Q7-Q0 Toggle Bit Q6 = Toggle ? (Note 1) NO YES NO Q5= 1? YES Read Q7~Q0 Twice (Note 1,2) Toggle bit Q6= Toggle? NO YES Program/Erase Operation Not Complete,Write Reset Command Program/Erase operation Complete 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 change to "1". P/N:PM1094 REV. 1.0, NOV. 08, 2004 33 MX26LV400 FIGURE 12. Data# Polling Timings (During Automatic Algorithms) tRC Address VA VA VA tACC tCE CE# tCH tOE OE# tOEH tDF WE# tOH Q7 Complement Complement True Valid Data Q0-Q6 Status Data Status Data True Valid Data High Z High Z tBUSY RY/BY# NOTES: 1. VA=Valid address. Figure shows are first status cycle after command sequence, last status read cycle, and array data read cycle. 2. CE# must be toggled when DATA# polling. P/N:PM1094 REV. 1.0, NOV. 08, 2004 34 MX26LV400 FIGURE 13. Toggle Bit Timings (During Automatic Algorithms) tRC VA VA Address VA VA tACC tCE CE# tCH tOE OE# tDF tOEH WE# tOH High Z Q6/Q2 Valid Status (first raed) Valid Status Valid Data (second read) (stops toggling) Valid Data tBUSY RY/BY# NOTES: 1. 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. 2. CE# must be toggled when toggle bit toggling. P/N:PM1094 REV. 1.0, NOV. 08, 2004 35 MX26LV400 TABLE 12. AC CHARACTERISTICS Parameter Std Description Test Setup All Speed Options Unit tREADY1 RESET# PIN Low (During Automatic Algorithms) MAX 20 us MAX 500 ns to Read or Write (See Note) tREADY2 RESET# PIN Low (NOT During Automatic Algorithms) to Read or Write (See Note) tRP RESET# Pulse Width (During Automatic Algorithms) MIN 500 ns tRH RESET# High Time Before Read (See Note) MIN 50 ns tRB RY/BY# Recovery Time (to CE#, OE# go low) MIN 0 ns Note: Not 100% tested FIGURE 14. 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:PM1094 REV. 1.0, NOV. 08, 2004 36 MX26LV400 AC CHARACTERISTICS TABLE 13. WORD/BYTE CONFIGURATION (BYTE#) Parameter JEDEC Description Speed Options Std -55 Unit -70 tELFL/tELFH CE# to BYTE# Switching Low or High Max tFLQZ BYTE# Switching Low to Output HIGH Z Max 25 25 ns tFHQV BYTE# Switching High to Output Active Min 55 70 ns FIGURE 15. 5 ns BYTE# TIMING WAVEFORM FOR READ OPERATIONS (BYTE# switching from byte mode to word mode) CE# OE# tELFH BYTE# Q0~Q14 DOUT (Q0-Q7) Q15/A-1 VA DOUT (Q0-Q14) DOUT (Q15) tFHQV P/N:PM1094 REV. 1.0, NOV. 08, 2004 37 MX26LV400 FIGURE 16. BYTE# TIMING WAVEFORM FOR READ OPERATIONS (BYTE# switching from word mode to byte mode) CE# OE# tELFH BYTE# DOUT (Q0-Q14) Q0~Q14 DOUT (Q15) Q15/A-1 DOUT (Q0-Q7) VA tFLQZ FIGURE 17. BYTE# TIMING WAVEFORM FOR PROGRAM OPERATIONS CE# The falling edge of the last WE# signal WE# BYTE# tAS P/N:PM1094 tAH REV. 1.0, NOV. 08, 2004 38 MX26LV400 FIGURE 18. ID CODE READ TIMING WAVEFORM VCC 3V VID VIH VIL ADD A9 ADD A0 VIH VIL tACC tACC VIH A1 VIL ADD A2-A8 A10-A17 CE# VIH VIL VIH VIL WE# VIH tCE VIL OE# VIH tOE VIL tDF tOH tOH VIH DATA Q0-Q15 DATA OUT DATA OUT VIL C2H/00C2H B9H/BAH (Byte) 22B9H/22BAH (Word) P/N:PM1094 REV. 1.0, NOV. 08, 2004 39 MX26LV400 TABLE 14. ERASE AND PROGRAMMING PERFORMANCE (1) LIMITS PARAMETER TYP. (2) MAX. (3) UNITS Sector Erase Time 2.4 15 sec Chip Erase Time 20 120 sec Byte Programming Time 55 220 us Word Programming Time 70 280 us Chip Programming Time (Word/Byte Mode) 18 36 sec Erase/Program Cycles MIN. 2K (6) Cycles Note: 1. Not 100% tested. 2. Typical program and erase times assume the following conditions : 25° C, 3.3V VCC. Programming spec. assume that all bits are programmed to checkerboard pattern. 3. Maximum values are measured at VCC=3.0V, worst case temperature. Maximum values are up to including 2K program/erase cycles. 4. System-level overhead is the time required to execute the command sequences for the all program command. 5. Excludes 00H programming prior to erasure. (In the pre-programming step of the embedded erase algorithm, all bits are programmed to 00H before erasure) 6. Min. erase/program cycles is under : 3.3V VCC, 25° C, checkerboard pattern conditions, and without baking process. TABLE 15. LATCH-UP CHARACTERISTICS MIN. MAX. Input Voltage with respect to GND on ACC, OE#, RESET#, A9 -1.0V 12V Input Voltage with respect to GND on all power pins, Address pins, CE# and WE# -1.0V VCC + 1.0V -1.0V VCC + 1.0V -100mA +100mA Input Voltage with respect to GND on all I/O pins Current Includes all pins except VCC. Test conditions: VCC = 3.0V, one pin at a time. P/N:PM1094 REV. 1.0, NOV. 08, 2004 40 MX26LV400 ORDERING INFORMATION PLASTIC PACKAGE PART NO. MX26LV400TTC-55 ACCESS TIME (ns) 55 OPERATING Current MAX. (mA) 30 STANDBY Current MAX. (uA) 100 MX26LV400BTC-55 55 30 100 MX26LV400TTC-70 70 30 100 MX26LV400BTC-70 70 30 100 MX26LV400TXBC-55 55 30 100 MX26LV400BXBC-55 55 30 100 MX26LV400TXBC-70 70 30 100 MX26LV400BXBC-70 70 30 100 MX26LV400TXEC-55 55 30 100 MX26LV400BXEC-55 55 30 100 MX26LV400TXEC-70 70 30 100 MX26LV400BXEC-70 70 30 100 MX26LV400TTC-55G 55 30 100 MX26LV400BTC-55G 55 30 100 MX26LV400TTC-70G 70 30 100 MX26LV400BTC-70G 70 30 100 MX26LV400TXBC-55G 55 30 100 MX26LV400BXBC-55G 55 30 100 MX26LV400TXBC-70G 70 30 100 MX26LV400BXBC-70G 70 30 100 MX26LV400TXEC-55G 55 30 100 MX26LV400BXEC-55G 55 30 100 MX26LV400TXEC-70G 70 30 100 MX26LV400BXEC-70G 70 30 100 P/N:PM1094 PACKAGE Remark 48 Pin TSOP (Normal Type) 48 Pin TSOP (Normal Type) 48 Pin TSOP (Normal Type) 48 Pin TSOP (Normal Type) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.4mm) 48 Ball CSP (Ball size:0.4mm) 48 Ball CSP (Ball size:0.4mm) 48 Ball CSP (Ball size:0.4mm) 48 Pin TSOP (Normal Type) 48 Pin TSOP (Normal Type) 48 Pin TSOP (Normal Type) 48 Pin TSOP (Normal Type) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.3mm) 48 Ball CSP (Ball size:0.4mm) 48 Ball CSP (Ball size:0.4mm) 48 Ball CSP (Ball size:0.4mm) 48 Ball CSP (Ball size:0.4mm) Pb-free Pb-free Pb-free Pb-free Pb-free Pb-free Pb-free Pb-free Pb-free Pb-free Pb-free Pb-free REV. 1.0, NOV. 08, 2004 41 MX26LV400 PACKAGE INFORMATION P/N:PM1094 REV. 1.0, NOV. 08, 2004 42 MX26LV400 48-Ball CSP (for MX26LV400ATXBC/ATXBI/ABXBC/ABXBI) P/N:PM1094 REV. 1.0, NOV. 08, 2004 43 MX26LV400 48-Ball CSP (for MX26LV400ATXEC/ATXEI/ABXEC/ABXEI) P/N:PM1094 REV. 1.0, NOV. 08, 2004 44 MX26LV400 REVISION HISTORY Revision No. Description 1.0 1. Removed "Preliminary" Page P1 P/N:PM1094 Date NOV/08/2004 REV. 1.0, NOV. 08, 2004 45 MX26LV400 MACRONIX INTERNATIONAL CO., 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.