US20020036941A1 - Protection after brown out in a synchronous memory - Google Patents

Protection after brown out in a synchronous memory Download PDF

Info

Publication number
US20020036941A1
US20020036941A1 US09/862,868 US86286801A US2002036941A1 US 20020036941 A1 US20020036941 A1 US 20020036941A1 US 86286801 A US86286801 A US 86286801A US 2002036941 A1 US2002036941 A1 US 2002036941A1
Authority
US
United States
Prior art keywords
memory device
supply voltage
latch
memory
register
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US09/862,868
Other versions
US6366521B1 (en
Inventor
Frankie Roohparvar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
US Bank NA
Original Assignee
Micron Technology Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Micron Technology Inc filed Critical Micron Technology Inc
Priority to US09/862,868 priority Critical patent/US6366521B1/en
Publication of US20020036941A1 publication Critical patent/US20020036941A1/en
Application granted granted Critical
Publication of US6366521B1 publication Critical patent/US6366521B1/en
Assigned to U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT reassignment U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICRON TECHNOLOGY, INC.
Assigned to MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT reassignment MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT PATENT SECURITY AGREEMENT Assignors: MICRON TECHNOLOGY, INC.
Assigned to U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT reassignment U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT CORRECTIVE ASSIGNMENT TO CORRECT THE REPLACE ERRONEOUSLY FILED PATENT #7358718 WITH THE CORRECT PATENT #7358178 PREVIOUSLY RECORDED ON REEL 038669 FRAME 0001. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST. Assignors: MICRON TECHNOLOGY, INC.
Assigned to JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT reassignment JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MICRON SEMICONDUCTOR PRODUCTS, INC., MICRON TECHNOLOGY, INC.
Assigned to MICRON TECHNOLOGY, INC. reassignment MICRON TECHNOLOGY, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Assigned to MICRON TECHNOLOGY, INC. reassignment MICRON TECHNOLOGY, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Assigned to MICRON TECHNOLOGY, INC., MICRON SEMICONDUCTOR PRODUCTS, INC. reassignment MICRON TECHNOLOGY, INC. RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C7/00—Arrangements for writing information into, or reading information out from, a digital store
    • G11C7/10—Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers
    • G11C7/1015—Read-write modes for single port memories, i.e. having either a random port or a serial port
    • G11C7/1045—Read-write mode select circuits
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C16/00—Erasable programmable read-only memories
    • G11C16/02—Erasable programmable read-only memories electrically programmable
    • G11C16/06—Auxiliary circuits, e.g. for writing into memory
    • G11C16/22—Safety or protection circuits preventing unauthorised or accidental access to memory cells
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C16/00—Erasable programmable read-only memories
    • G11C16/02—Erasable programmable read-only memories electrically programmable
    • G11C16/06—Auxiliary circuits, e.g. for writing into memory
    • G11C16/22—Safety or protection circuits preventing unauthorised or accidental access to memory cells
    • G11C16/225—Preventing erasure, programming or reading when power supply voltages are outside the required ranges
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C16/00—Erasable programmable read-only memories
    • G11C16/02—Erasable programmable read-only memories electrically programmable
    • G11C16/06—Auxiliary circuits, e.g. for writing into memory
    • G11C16/30—Power supply circuits
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C7/00—Arrangements for writing information into, or reading information out from, a digital store
    • G11C7/24—Memory cell safety or protection circuits, e.g. arrangements for preventing inadvertent reading or writing; Status cells; Test cells

Definitions

  • the present invention relates generally to non-volatile memory devices and in particular the present invention relates to a synchronous non-volatile flash memory.
  • RAM random-access memory
  • ROM read-only memory
  • ROM read-only memory
  • An EEPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • RAM random access memory
  • EEPROM electrically isolated programmable read-only memory
  • EEPROM electrically isolated programmable read-only memory
  • EEPROM electrically isolated gates
  • Flash memory is a type of EEPROM that can be erased and reprogrammed in blocks instead of one byte at a time.
  • BIOS stored on a flash memory chip so that it can easily be updated if necessary. Such a BIOS is sometimes called a flash BIOS. Flash memory is also popular in modems because it enables the modem manufacturer to support new protocols as they become standardized.
  • a typical Flash memory comprises a memory array that includes a large number of memory cells arranged in row and column fashion.
  • Each of the memory cells includes a floating gate field-effect transistor capable of holding a charge.
  • the cells are usually grouped into blocks.
  • Each of the cells within a block can be electrically programmed in a random basis by charging the floating gate.
  • the charge can be removed from the floating gate by a block erase operation.
  • the data in a cell is determined by the presence or absence of the charge in the floating gate.
  • SDRAM synchronous DRAM
  • FPM Full Page Mode
  • BEDO Extended Data Output
  • SDRAM's can be accessed quickly, but are volatile. Many computer systems are designed to operate using SDRAM, but would benefit from non-volatile memory.
  • a memory device comprises a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a predetermined value, and a latch coupled to the voltage detection circuit.
  • the latch can be programmed to indicate if the supply voltage drops below the predetermined value.
  • a memory device comprises a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a s predetermined value, a volatile register to store operating data, and a brown-out latch circuit programmed to a first data state after an initialization operation is performed to load the volatile register.
  • the brown-out latch is programmed to a second state in response to the voltage detection circuit if the supply voltage drops below the predetermined value.
  • a system comprises a power supply, and a memory device coupled to the power supply to receive a supply voltage.
  • the memory device comprises a voltage detection circuit to monitor the supply voltage and provide a signal if the supply voltage drops below a predetermined value, and a latch coupled to the voltage detection circuit.
  • a method of operating a memory device comprising performing a first initialization operation on the memory device, changing a data state of a latch circuit from a default state to a second state after the first initialization operation, monitoring a supply voltage of the memory device, and setting the latch circuit to the default data state if the supply voltage is below a predetermined voltage.
  • FIG. 1A is a block diagram of a synchronous flash memory of the present invention
  • FIG. 1B is an integrated circuit pin interconnect diagram of one embodiment of the present invention.
  • FIG. 1C is an integrated circuit interconnect bump grid array diagram of one embodiment of the present invention.
  • FIG. 2 illustrates a mode register of one embodiment of the present invention
  • FIG. 3 is a flow chart of a self-timed write sequence according to one embodiment of the present invention.
  • FIG. 4 is a flow chart of a complete write status-check sequence according to one embodiment of the present invention.
  • FIG. 5 is a flow chart of a self-timed block erase sequence according to one embodiment of the present invention.
  • FIG. 6 is a flow chart of a complete block erase status-check sequence according to one embodiment of the present invention.
  • FIG. 7 is a flow chart of a block protect sequence according to one embodiment of the present invention.
  • FIG. 8 is a flow chart of a complete block status-check sequence according to one embodiment of the present invention.
  • FIG. 9 is a flow chart of a device protect sequence according to one embodiment of the present invention.
  • FIG. 10 is a flow chart of a block unprotect sequence according to one embodiment of the present invention.
  • FIG. 11 illustrates the timing of an initialize and load mode register operation
  • FIG. 12 illustrates the timing of a clock suspend mode operation
  • FIG. 13 illustrates the timing of a burst read operation
  • FIG. 14 illustrates the timing of alternating bank read accesses
  • FIG. 15 illustrates the timing of a full-page burst read operation
  • FIG. 16 illustrates the timing of a burst read operation using a data mask signal
  • FIG. 17 illustrates the timing of a write operation followed by a read to a different bank
  • FIG. 18 illustrates the timing of a write operation followed by a read to the same bank
  • FIG. 19 is a block diagram of a system of one embodiment of the invention.
  • the following detailed description is divided into two major sections.
  • the first section is an Interface Functional Description that details compatibility with an SDRAM memory.
  • the second major section is a Functional Description that specifies flash architecture functional commands.
  • the memory device 100 includes an array of non-volatile flash memory cells 102 .
  • the array is arranged in a plurality of addressable banks.
  • the memory contains four memory banks 104 , 106 , 108 and 110 .
  • Each memory bank contains addressable sectors of memory cells.
  • the data stored in the memory can be accessed using externally provided location addresses received by address register 112 .
  • the addresses are decoded using row address multiplexer circuitry 114 .
  • the addresses are also decoded using bank control logic 116 and row address latch and decode circuitry 118 .
  • column address counter and latch circuitry 120 couples the received addresses to column decode circuitry 122 .
  • Circuit 124 provides input/output gating, data mask logic, read data latch circuitry and write driver circuitry. Data is input through data input registers 126 and output through data output registers 128 .
  • Command execution logic 130 is provided to control the basic operations of the memory device.
  • a state machine 132 is also provided to control specific operations performed on the memory arrays and cells.
  • a status register 134 and an identification register 136 can also be provided to output data.
  • the command circuit 130 and/or state machine 132 can be generally referred to as control circuitry to control read, write, erase and other memory operations.
  • FIG. 1B illustrates an interconnect pin assignment of one embodiment of the present invention.
  • the memory package 150 has 54 interconnect pins.
  • the pin configuration is substantially similar to available SDRAM packages.
  • Two interconnects specific to the present invention are RP# 152 and Vccp 154 .
  • the present invention may share interconnect labels that are appear the same as SDRAM's, the function of the signals provided on the interconnects are described herein and should not be equated to SDRAM's unless set forth herein.
  • FIG. 1C illustrates one embodiment of a memory package 160 that has bump connections instead of the pin connections of FIG. 1C.
  • the present invention therefore, is not limited to a specific package configuration.
  • the input clock connection is used to provide a clock signal (CLK).
  • CLK clock signal
  • the clock signal can be driven by a system clock, and all synchronous flash memory input signals are sampled on the positive edge of CLK.
  • CLK also increments an internal burst counter and controls the output registers.
  • the input clock enable (CKE) connection is used to activate (HIGH state) and deactivates (LOW state) the CLK signal input. Deactivating the clock input provides POWER-DOWN and STANDBY operation (where all memory banks are idle), ACTIVE POWER-DOWN (a memory row is ACTIVE in either bank) or CLOCK SUSPEND operation (burst/access in progress).
  • CKE is synchronous except after the device enters power-down modes, where CKE becomes asynchronous until after exiting the same mode.
  • the input buffers, including CLK are disabled during power-down modes to provide low standby power. CKE may be tied HIGH in systems where power-down modes (other than RP# deep power-down) are not required.
  • the chip select (CS#) input connection provides a signal to enable (registered LOW) and disable (registered HIGH) a command decoder provided in the command execution logic. All commands are masked when CS# is registered HIGH. Further, CS# provides for external bank selection on systems with multiple banks, and CS# can be considered part of the command code; but may not be necessary.
  • the input command input connections for RAS#, CAS#, and WE# (along with CAS#, CS#) define a command that is to be executed by the memory, as described in detail below.
  • the input/output mask (DQM) connections are used to provide input mask signals for write accesses and an output enable signal for read accesses. Input data is masked when DQM is sampled HIGH during a WRITE cycle.
  • the output buffers are placed in a high impedance (High-Z) state (after a two-clock latency) when DQM is sampled HIGH during a READ cycle.
  • DQML corresponds to data connections DQ0-DQ7 and DQMH corresponds to data connections DQ8-DQ15. DQML and DQMH are considered to be the same state when referenced as DQM.
  • Address inputs 133 are primarily used to provide address signals.
  • the memory has 12 lines (A0-A11). Other signals can be provided on the address connections, as described below.
  • the address inputs are sampled during an ACTIVE command (row-address A0-A11) and a READ/WRITE command (column-address A0-A7) to select one location in a respective memory bank.
  • the address inputs are also used to provide an operating code (OpCode) during a LOAD COMMAND REGISTER operation, explained below.
  • Address lines A0-A11 are also used to input mode settings during a LOAD MODE REGISTER operation.
  • An input reset/power-down (RP#) connection 140 is used for reset and power-down operations.
  • RP# Upon initial device power-up, a 100 ⁇ s delay after RP# has transitioned from LOW to HIGH is required in one embodiment for internal device initialization, prior to issuing an executable command.
  • the RP# signal clears the status register, sets the internal state machine (ISM) 132 to an array read mode, and places the device in a deep power-down mode when LOW.
  • ISM internal state machine
  • all input connections, including CS# 142 are “Don't Care” and all outputs are placed in a High-Z state.
  • VHH voltage 5V
  • the RP# signal also allows a device protect bit to be set to 1 (protected) and allows block protect bits of a 16 bit register, at locations 0 and 15 to be set to 0 (unprotected) when brought to VHH.
  • the protect bits are described in more detail below.
  • RP# is held HIGH during all other modes of operation.
  • Bank address input connections, BA0 and BA1 define which bank an ACTIVE, READ, WRITE, or BLOCK PROTECT command is being applied.
  • the DQ0-DQ15 connections 143 are data bus connections used for bi-directional data communication.
  • a VCCQ connection is used to provide isolated power to the DQ connections to improved noise immunity.
  • VCCQ Vcc or 1.8V ⁇ 15V.
  • the VSSQ connection is used to isolated ground to DQs for improved noise immunity.
  • the VCC connection provides a power supply, such as 3V.
  • a ground connection is provided through the Vss connection.
  • Another optional voltage is provided on the VCCP connection 144 .
  • the VCCP connection can be tied externally to VCC, and sources current during device initialization, WRITE and ERASE operations. That is, writing or erasing to the memory device can be performed using a VCCP voltage, while all other operations can be performed with a VCC voltage.
  • the Vccp connection is coupled to a high voltage switch/pump circuit 145 .
  • One embodiment of the present invention is a nonvolatile, electrically sector-erasable (Flash), programmable read-only memory containing 67,108,864 bits organized as 4,194,304 words by 16 bits. Other population densities are contemplated, and the present invention is not limited to the example density.
  • Flash electrically sector-erasable
  • Each memory bank is organized into four independently erasable blocks (16 total). To ensure that critical firmware is protected from accidental erasure or overwrite, the memory can include sixteen 256K-word hardware and software lockable blocks.
  • the memory's four-bank architecture supports true concurrent operations.
  • a read access to any bank can occur simultaneously with a background WRITE or ERASE operation to any other bank.
  • the synchronous flash memory has a synchronous interface (all signals are registered on the positive edge of the clock signal, CLK).
  • Read accesses to the memory can be burst oriented. That is, memory accesses start at a selected location and continue for a programmed number of locations in a programmed sequence. Read accesses begin with the registration of an ACTIVE command, followed by a READ command. The address bits registered coincident with the ACTIVE command are used to select the bank and row to be accessed. The address bits registered coincident with the READ command are used to select the starting column location and bank for the burst access.
  • the synchronous flash memory provides for programmable read burst lengths of 1, 2, 4 or 8 locations, or the full page, with a burst terminate option. Further, the synchronous flash memory uses an internal pipelined architecture to achieve high-speed operation.
  • the synchronous flash memory can operate in low-power memory systems, such as systems operating on three volts. A deep power-down mode is provided, along with a power-saving standby mode. All inputs and outputs are low voltage transistor-transistor logic (LVTTL) compatible.
  • the synchronous flash memory offers substantial advances in Flash operating performance, including the ability to synchronously burst data at a high data rate with automatic column address generation and the capability to randomly change column addresses on each clock cycle during a burst access.
  • the synchronous flash memory is configured similar to a multi-bank DRAM that operates at low voltage and includes a synchronous interface. Each of the banks is organized into rows and columns. Prior to normal operation, the synchronous flash memory is initialized.
  • the following sections provide detailed information covering device initialization; register definition, command descriptions and device operation.
  • the synchronous flash is powered up and initialized in a predefined manner. After power is applied to VCC, VCCQ and VCCP (simultaneously), and the clock signal is stable, RP# 140 is brought from a LOW state to a HIGH state. A delay, such as a 100 ⁇ s delay, is needed after RP# transitions HIGH in order to complete internal device initialization. After the delay time has passed, the memory is placed in an array read mode and is ready for Mode Register programming or an executable command. After initial programming of a non-volatile mode register 147 (NVMode Register), the contents are automatically loaded into a volatile Mode Register 148 during the initialization. The device will power up in a programmed state and will not require reloading of the non-volatile mode register 147 prior to issuing operational commands. This is explained in greater detail below.
  • the Mode Register 148 is used to define the specific mode of operation of the synchronous flash memory. This definition includes the selection of a burst length, a burst type, a CAS latency, and an operating mode, as shown in FIG. 2.
  • the Mode Register is programmed via a LOAD MODE REGISTER command and retains stored information until it is reprogrammed. The contents of the Mode Register may be copied into the NVMode Register 147 .
  • the NVMode Register settings automatically load the Mode Register 148 during initialization. Details on ERASE NVMODE REGISTER and WRITE NVMODE REGISTER command sequences are provided below. Those skilled in the art will recognize that an SDRAM requires that a mode register must be externally loaded during each initialization operation.
  • the present invention allows a default mode to be stored in the NV mode register 147 .
  • the contents of the NV mode register are then copied into a volatile mode register 148 for access during memory operations.
  • Mode Register bits M0-M2 specify a burst length
  • M3 specifies a burst type (sequential or interleaved)
  • M4-M6 specify a CAS latency
  • M7 and M8 specify a operating mode
  • M9 is set to one
  • M10 and M11 are reserved in this embodiment. Because WRITE bursts are not currently implemented; M9 is set to a logic one and write accesses are single location (non-burst) accesses.
  • the Mode Register must be loaded when all banks are idle, and the controller must wait the specified time before initiating a subsequent operation.
  • Read accesses to the synchronous flash memory can be burst oriented, with the burst length being programmable, as shown in Table 1.
  • the burst length determines the maximum number of column locations that can be automatically accessed for a given READ command. Burst lengths of 1, 2, 4, or 8 locations are available for both sequential and the interleaved burst types, and a full-page burst is available for the sequential type.
  • the full-page burst can be used in conjunction with the BURST TERMINATE command to generate arbitrary burst lengths that is, a burst can be selectively terminated to provide custom length bursts. When a READ command is issued, a block of columns equal to the burst length is effectively selected.
  • All accesses for that burst take place within this block, meaning that the burst will wrap within the block if a boundary is reached.
  • the block is uniquely selected by A1-A7 when the burst length is set to two, by A2-A7 when the burst length is set to four, and by A3-A7 when the burst length is set to eight.
  • the remaining (least significant) address bit(s) are used to select the starting location within the block. Full-page bursts wrap within the page if the boundary is reached.
  • Accesses within a given burst may be programmed to be either sequential or interleaved; this is referred to as the burst type and is selected via bit M3.
  • the ordering of accesses within a burst is determined by the burst length, the burst type and the starting column address, as shown in Table 1.
  • the synchronous flash memory incorporates a number of features to make it ideally suited for code storage and execute-in-place applications on an SDRAM bus.
  • the memory array is segmented into individual erase blocks. Each block may be erased without affecting data stored in other blocks. These memory blocks are read, written and erased by issuing commands to the command execution logic 130 (CEL).
  • the CEL controls the operation of the Internal State Machine 132 (ISM), which completely controls all ERASE NVMODE REGISTER, WRITE NVMODE REGISTER, WRITE, BLOCK ERASE, BLOCK PROTECT, DEVICE PROTECT, UNPROTECT ALL BLOCKS and VERIFY operations.
  • the ISM 132 protects each memory location from over-erasure and optimizes each memory location for maximum data retention. In addition, the ISM greatly simplifies the control necessary for writing the device in-system or in an external programmer.
  • the synchronous flash memory is organized into 16 independently erasable memory blocks that allow portions of the memory to be erased without affecting the rest of the memory data. Any block may be hardware-protected against inadvertent erasure or writes. A protected block requires that the RP# pin be driven to VHH (a relatively high voltage) before being modified.
  • VHH a relatively high voltage
  • the 256K-word blocks at locations 0 and 15 can have additional hardware protection.
  • an UNPROTECT ALL BLOCKS command will unlock all blocks except the blocks at locations 0 and 15, unless the RP# pin is at VHH. This provides additional security for critical code during in-system firmware updates, should an unintentional power disruption or system reset occur.
  • ISM Power-up initialization, ERASE, WRITE and PROTECT timings are simplified by using an ISM to control all programming algorithms in the memory array.
  • the ISM ensures protection against over-erasure and optimizes write margin to each cell.
  • the ISM automatically increments and monitors WRITE attempts, verifies write margin on each memory cell and updates the ISM Status Register.
  • the ISM automatically Overwrites the entire addressed block (eliminates over-erasure), increments and monitors ERASE attempts and sets bits in the ISM Status Register.
  • the 8-bit ISM Status Register 134 allows an external processor 200 to monitor the status of the ISM during WRITE, ERASE and PROTECT operations.
  • One bit of the 8-bit Status Register (SR7) is set and cleared entirely by the ISM. This bit indicates whether the ISM is busy with an ERASE, WRITE or PROTECT task. Additional error information is set in three other bits (SR3, SR4 and SR5): write and protect block error, erase and unprotect all blocks error, and device protection error.
  • Status register bits SRO, SR1 and SR2 provide details on the ISM operation underway. The user can monitor whether a device-level or bank-level ISM operation (including which bank is under ISM control) is underway.
  • Table 2 illustrates one embodiment of the status register.
  • SR7 ISM STATUS
  • the controlling logic polls this bit to determine when the erase and write status bits are valid.
  • SR6 RESERVED Reserved for future use.
  • SR2 and SR3 can be decoded to determine which bank is under ISM control.
  • the synchronous flash features a very low current, deep power-down mode.
  • the RP# pin 140 reset/power-down
  • VSS ⁇ 0.2V.
  • RP# must be held at Vss for 100 ns prior to the device entering the reset mode. With RP# held at Vss, the device will enter the deep power-down mode. After the device enters the deep power-down mode, a transition from LOW to HIGH on RP# will result in a device power-up initialize sequence as outlined herein.
  • Transitioning RP# from LOW to HIGH after entering the reset mode but prior to entering deep power-down mode requires a 1 ⁇ s delay prior to issuing an executable command.
  • all buffers excluding the RP# buffer are disabled and the current draw is low, for example, a maximum of 50 ⁇ A at 3.3V VCC.
  • the input to RP# must remain at Vss during deep power-down. Entering the RESET mode clears the Status Register 134 and sets the ISM 132 to the array read mode.
  • the synchronous flash memory array architecture is designed to allow sectors to be erased without disturbing the rest of the array.
  • the array is divided into 16 addressable “blocks” that are independently erasable. By erasing blocks rather than the entire array, the total device endurance is enhanced, as is system flexibility. Only the ERASE and BLOCK PROTECT functions are block oriented.
  • the 16 addressable blocks are equally divided into four banks 104 , 106 , 108 and 110 of four blocks each.
  • the four banks have simultaneous read-while-write functionality.
  • An ISM WRITE or ERASE operation to any bank can occur simultaneously to a READ operation to any other bank.
  • the Status Register 134 maybe polled to determine which bank is under ISM operation.
  • the synchronous flash memory has a single background operation ISM to control power-up initialization, ERASE, WRITE, and PROTECT operations. Only one ISM operation can occur at any time; however, certain other commands, including READ operations, can be performed while the ISM operation is taking place.
  • An operational command controlled by the ISM is defined as either a bank-level operation or a device-level operation.
  • WRITE and ERASE are bank-level ISM operations.
  • a READ to any location in the bank may output invalid data, whereas a READ to any other bank will read the array.
  • a READ STATUS REGISTER command will output the contents of the Status Register 134 .
  • the bank will automatically enter the array read mode.
  • ERASE NVMODE REGISTER, WRITE NVMODE REGISTER, BLOCK PROTECT, DEVICE PROTECT, and UNPROTECT ALL BLOCKS are device-level ISM operations. Once an ISM device-level operation has been initiated, a READ to any bank will output the contents of the array.
  • a READ STATUS REGISTER command may be issued to determine completion of the ISM operation.
  • Any block may be protected from unintentional ERASE or WRITE with a hardware circuit that requires the RP# pin be driven to VHH before a WRITE or ERASE is commenced, as explained below.
  • Any block may be hardware-protected to provide extra security for the most sensitive portions of the firmware.
  • the protection status of any block may be checked by reading its block protect bit with a READ STATUS REGISTER command. Further, to protect a block, a three-cycle command sequence must be issued with the block address.
  • the device protection status and block protect status can be read by issuing a READ DEVICE CONFIGURATION (90H) command.
  • a specific address must be asserted. While in this mode, specific addresses are issued to read the desired information.
  • the device protect bit is read at 000003H, and each of the block protect bits is read at the third address location within each block (xx0002H).
  • the device and block protect bits are output on DQ0. See Table 3 for more details on some of the various device configuration registers 136 .
  • the ISM status bit (SR7) is set to a logic 1, the WRITE has been completed, and the bank will be in the array read mode and ready for an executable command.
  • Writing to hardware-protected blocks also requires that the RP# pin be set to VHH prior to the third cycle (WRITE), and RP# must be held at VHH until the ISM WRITE operation is complete.
  • the write and erase status bits (SR4 and SR5) will be set if the LCR-ACTIVE-WRITE command sequence is not completed on consecutive cycles or the bank address changes for any of the three cycles. After the ISM has initiated the WRITE, it cannot be aborted except by a RESET or by powering down the part. Doing either during a WRITE may corrupt the data being written.
  • Executing an ERASE sequence will set all bits within a block to logic 1.
  • the command sequence necessary to execute an ERASE is similar to that of a WRITE.
  • three consecutive command sequences on consecutive clock edges are required to initiate an ERASE of a block.
  • LOAD COMMAND REGISTER is given with ERASE SETUP (20H) on A0-A7, and the bank address of the block to be erased is issued on BA0, BA1.
  • the next command is ACTIVE, where A10, A11, BA0, BA1 provide the address of the block to be erased.
  • the third cycle is WRITE, during which ERASE CONFRIM (DOH) is given on DQ0-DQ7 and the bank address is reissued.
  • the ISM status bit will be set on the following clock edge (subject to CAS latencies).
  • ERASE CONFIRM D0H
  • the ISM will start the ERASE of the addressed block. Any READ operation to the bank where the addressed block resides may output invalid data.
  • the write and erase status bits (SR4 and SR5) will be set and the operation is prohibited.
  • the memory includes a 16-bit register that has one bit corresponding to the 16 protectable blocks.
  • the memory also has a register to provide a device bit used to protect the entire device from write and erase operations.
  • the command sequence necessary to execute a BLOCK PROTECT is similar to that of a WRITE.
  • three consecutive command cycles are required to initiate a BLOCK PROTECT.
  • a LOAD COMMAND REGISTER is issued with a PROTECT SETUP (60H) command on A0-A7, and the bank address of the block to be protected is issued on BA0, BA1.
  • the next command is ACTIVE, which activates a row in the block to be protected and confirms the bank address.
  • the third cycle is WRITE, during which BLOCK PROTECT CONFIRM (01H) is issued on DQ0-DQ7, and the bank address is reissued.
  • the ISM status bit will be set on the following clock edge (subject to CAS latencies). The ISM will then begin the PROTECT operation. If the LCR-ACTIVE-WRITE is not completed on consecutive cycles (NOPs and COMMAND INHIBITs are permitted between cycles) or the bank address changes, the write and erase status bits (SR4 and SR5) will be set and the operation is prohibited.
  • the ISM status bit (SR7) is set to a logic 1
  • the PROTECT has been completed, and the bank will be in the array read mode and ready for an executable command.
  • a block protect bit Once a block protect bit has been set to a 1 (protected), it can only be reset to a 0 if the UNPROTECT ALL BLOCKS command.
  • the UNPROTECT ALL BLOCKS command sequence is similar to the BLOCK PROTECT command; however, in the third cycle, a WRITE is issued with a UNPROTECT ALL BLOCKS CONFIRM (DOH) command and addresses are “Don't Care.”
  • Executing a DEVICE PROTECT sequence sets the device protect bit to a 1 and prevents a block protect bit modification.
  • the command sequence necessary to execute a DEVICE PROTECT is similar to that of a WRITE. Three consecutive command cycles are required to initiate a DEVICE PROTECT sequence. In the first cycle, LOAD COMMAND REGISTER is issued with a PROTECT SETUP (60H) on A0-A7, and a bank address is issued on BA0, BA1. The bank address is “Don't Care” but the same bank address must be used for all three cycles. The next command is ACTIVE.
  • the third cycle is WRITE, during which a DEVICE PROTECT (F 1 H) command is issued on DQ0-DQ7, and RP# is brought to VHH.
  • the ISM status bit will be set on the following clock edge (subject to CAS latencies).
  • An executable command can be issued to the device.
  • a new WRITE operation will not be permitted until the current ISM operation is complete.
  • the device protect bit does not affect WRITE or ERASE operations.
  • SR7 state machine status register bit
  • SRO state machine status register bit
  • SR3 device/bank
  • SR1 bankA0
  • SR2 bankA1
  • SR4 write/protect block
  • SR5 erase/unprotect
  • the sequence includes loading the command register (code 40H), receiving an active command and a row address, and receiving a write command and a column address.
  • the sequence then provides for a status register polling to determine if the write is complete.
  • the polling monitors status register bit 7 (SR7) to determine if it is set to a 1.
  • SR7 status register bit 7
  • An optional status check can be included.
  • FIG. 4 a flow chart of a complete write status-check sequence according to one embodiment of the present invention is provided.
  • the sequence looks for status register bit 4 (SR4) to determine if it is set to a 0. If SR4 is a 1, there was an error in the write operation.
  • the sequence also looks for status register bit 3 (SR3) to determine if it is set to a 0. If SR3 is a 1, there was an invalid write error during the write operation.
  • SR4 status register bit 4
  • SR3 status register bit 3
  • FIG. 5 a flow chart of a self-timed block erase sequence according to one embodiment of the present invention is provided.
  • the sequence includes loading the command register (code 20H), and receiving an active command and a row address.
  • the memory determines if the block is protected. If it is not protected, the memory performs a write operation (D0H) to the block and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode. If the block is protected, the erase is not allowed unless the RP# signal is at an elevated voltage (VHH).
  • VHH elevated voltage
  • FIG. 6 illustrates a flow chart of a complete block erase status-check sequence according to one embodiment of the present invention.
  • FIG. 7 is a flow chart of a block protect sequence according to one embodiment of the present invention.
  • the sequence includes loading the command register (code 60H), and receiving an active command and a row address.
  • the memory determines if the block is protected. If it is not protected, the memory performs a write operation (01H) to the block and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode. If the block is protected, the erase is not allowed unless the RP# signal is at an elevated voltage (VHH).
  • VHH elevated voltage
  • FIG. 8 a flow chart of a complete block status-check sequence according to one embodiment of the present invention is provided.
  • the sequence monitors the status register bits 3, 4 and 5 to determine of errors were detected.
  • FIG. 9 is a flow chart of a device protect sequence according to one embodiment of the present invention.
  • the sequence includes loading the command register (code 60H), and receiving an active command and a row address.
  • the memory determines if RP# is at VHH.
  • the memory performs a write operation (F1H) and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode.
  • FIG. 10 is a flow chart of a block unprotect sequence according to one embodiment of the present invention.
  • the sequence includes loading the command register (code 60H), and receiving an active command and a row address.
  • the memory determines if the memory device is protected. If it is not protected, the memory determines if the boot locations (blocks 0 and 15) are protected. If none of the blocks are protected the memory performs a write operation (DOH) to the block and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode. If the device is protected, the erase is not allowed unless the RP# signal is at an elevated voltage (VHH). Likewise, if the boot locations are protected, the memory detennines if all blocks should be unprotected.
  • DOH write operation
  • FIG. 11 illustrates the timing of an initialize and load mode register operation.
  • the mode register is programmed by providing a load mode register command and providing operation code (opcode) on the address lines.
  • the opcode is loaded into the mode register.
  • the contents of the non-volatile mode register are automatically loaded into the mode register upon power-up and the load mode register operation may not be needed.
  • FIG. 12 illustrates the timing of a clock suspend mode operation
  • FIG. 13 illustrates the timing of another burst read operation
  • FIG. 14 illustrates the timing of alternating bank read accesses. Here active commands are needed to change bank addresses.
  • a full page burst read operation is illustrated in FIG. 15. Note that the full page burst does not self terminate, but requires a terminate command.
  • FIG. 16 illustrates the timing of a read operation using a data mask signal.
  • the DQM signal is used to mask the data output so that Dout m+1 is not provided on the DQ connections.
  • FIG. 17 the timing of a write operation followed by a read to a different bank is illustrated.
  • a write is performed to bank a and a subsequent read is performed to bank b.
  • the same row is accessed in each bank.
  • FIG. 18 the timing of a write operation followed by a read to the same bank is illustrated.
  • a write is performed to bank a and a subsequent read is performed to bank a.
  • a different row is accessed for the read operation, and the memory must wait for the prior write operation to be completed. This is different from the read of FIG. 17 where the read was not delayed due to the write operation.
  • a loss of power is very serious during the operation of a memory device. Data corruption could occur if the device is busy writing.
  • One embodiment of the present invention has a protection register 149 that prevents any program or erase operation from being performed on selected blocks.
  • This register can have a volatile and a non-volatile component. The contents of the non-volatile register include default protection settings and are transferred to the volatile register during power-up.
  • a low Vcc detection circuit 125 (FIG. 1) is also provided that sets the volatile portion of this protection register 149 to protect all blocks during a low voltage situation.
  • Command logic 130 can program register 149 in response to circuit 125 .
  • the non-volatile protection register is programmed to protect selected memory locations. This data is then loaded into the volatile shadow register and accessed during operations. If the low Vcc detection circuit determines that the Vcc voltage dropped below a preset level, the volatile register is set to protect all sectors of the memory. In one embodiment, the detection circuit indicates if the Vcc level drops below 2 volts with a supply voltage of about 3 to 3.6 volts. This provides a level of safety to protect the memory during supply voltage variations. If a controller then attempts to write to a memory location, the memory will indicate that the location is protected. The controller can then check the status of the memory, and perform a reset/initialization of the memory.
  • the low Vcc detection circuit can also set a latch 127 when the power returns to a good level.
  • This latch can also be read through the status register 134 . Performing an initialization of the memory will reset the brown out latch.
  • the register can be read to determine if an initialization operation was performed. That is, the latch is set to a first state after an initialization is performed, and the latch is set to a second state if the Vcc level drops.
  • the addition of the brown out detection allows the system to check status register 134 to see if the device is ready to communicate. This also allows the processor 200 to determine if initialization has occurred. Thus, the brown out latch 127 can be read to determine if a brown out has occurred and a reset is needed.
  • a synchronous flash memory includes an array of non-volatile memory cells.
  • the memory device has a package configuration that is compatible with an SDRAM.
  • the memory device can detect a brown-out of a supply voltage.
  • the memory device comprises a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a predetermined value.
  • a latch is coupled to the voltage detection circuit and can be programmed to indicate if the supply voltage dropped below the predetermined value.
  • An external controller can read a status of the latch. The memory, therefore, can provide an indication to an external controller that a reset, or initialization, operation is needed.

Abstract

A synchronous flash memory includes an array of non-volatile memory cells. The memory device has a package configuration that is compatible with an SDRAM. The memory device can detect a brown-out of a supply voltage. The memory device comprises a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a predetermined value. A latch is coupled to the voltage detection circuit and can be programmed to indicate if the supply voltage dropped below the predetermined value. An external controller can read a status of the latch. The memory, therefore, can provide an indication to an external controller that a reset, or initialization, operation is needed.

Description

    TECHNICAL FIELD OF THE INVENTION
  • The present invention relates generally to non-volatile memory devices and in particular the present invention relates to a synchronous non-volatile flash memory. [0001]
    • BACKGROUND OF THE INVENTION
  • Memory devices are typically provided as internal storage areas in the computer. The term memory identifies data storage that comes in the form of integrated circuit chips. There are several different types of memory. One type is RAM (random-access memory). This is typically used as main memory in a computer environment. RAM refers to read and write memory; that is, you can both write data into RAM and read data from RAM. This is in contrast to ROM, which permits you only to read data. Most RAM is volatile, which means that it requires a steady flow of electricity to maintain its contents. As soon as the power is turned off, whatever data was in RAM is lost. [0002]
  • Computers almost always contain a small amount of read-only memory (ROM) that holds instructions for starting up the computer. Unlike RAM, ROM cannot be written to. An EEPROM (electrically erasable programmable read-only memory) is a special type non-volatile ROM that can be erased by exposing it to an electrical charge. Like other types of ROM, EEPROM is traditionally not as fast as RAM. EEPROM comprise a large number of memory cells having electrically isolated gates (floating gates). Data is stored in the memory cells in the form of charge on the floating gates. Charge is transported to or removed from the floating gates by programming and erase operations, respectively. [0003]
  • Yet another type of non-volatile memory is a Flash memory. A Flash memory is a type of EEPROM that can be erased and reprogrammed in blocks instead of one byte at a time. Many modem PCS have their BIOS stored on a flash memory chip so that it can easily be updated if necessary. Such a BIOS is sometimes called a flash BIOS. Flash memory is also popular in modems because it enables the modem manufacturer to support new protocols as they become standardized. [0004]
  • A typical Flash memory comprises a memory array that includes a large number of memory cells arranged in row and column fashion. Each of the memory cells includes a floating gate field-effect transistor capable of holding a charge. The cells are usually grouped into blocks. Each of the cells within a block can be electrically programmed in a random basis by charging the floating gate. The charge can be removed from the floating gate by a block erase operation. The data in a cell is determined by the presence or absence of the charge in the floating gate. [0005]
  • A synchronous DRAM (SDRAM) is a type of DRAM that can run at much higher clock speeds than conventional DRAM memory. SDRAM synchronizes itself with a CPU's bus and is capable of running at 100 MHZ, about three times faster than conventional FPM (Fast Page Mode) RAM, and about twice as fast EDO (Extended Data Output) DRAM and BEDO (Burst Extended Data Output) DRAM. SDRAM's can be accessed quickly, but are volatile. Many computer systems are designed to operate using SDRAM, but would benefit from non-volatile memory. [0006]
  • For the reasons stated above, and for other reasons stated below which will become apparent to those skilled in the art upon reading and understanding the present specification, there is a need in the art for a non-volatile memory device that can operate in a manner similar to SDRAM operation. [0007]
    • SUMMARY OF THE INVENTION
  • The above-mentioned problems with memory devices and other problems are addressed by the present invention and will be understood by reading and studying the following specification. [0008]
  • In one embodiment, a memory device comprises a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a predetermined value, and a latch coupled to the voltage detection circuit. The latch can be programmed to indicate if the supply voltage drops below the predetermined value. [0009]
  • In another embodiment, a memory device comprises a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a s predetermined value, a volatile register to store operating data, and a brown-out latch circuit programmed to a first data state after an initialization operation is performed to load the volatile register. The brown-out latch is programmed to a second state in response to the voltage detection circuit if the supply voltage drops below the predetermined value. [0010]
  • In yet another embodiment, a system comprises a power supply, and a memory device coupled to the power supply to receive a supply voltage. The memory device comprises a voltage detection circuit to monitor the supply voltage and provide a signal if the supply voltage drops below a predetermined value, and a latch coupled to the voltage detection circuit. [0011]
  • A method of operating a memory device comprising performing a first initialization operation on the memory device, changing a data state of a latch circuit from a default state to a second state after the first initialization operation, monitoring a supply voltage of the memory device, and setting the latch circuit to the default data state if the supply voltage is below a predetermined voltage.[0012]
    • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1A is a block diagram of a synchronous flash memory of the present invention; [0013]
  • FIG. 1B is an integrated circuit pin interconnect diagram of one embodiment of the present invention; [0014]
  • FIG. 1C is an integrated circuit interconnect bump grid array diagram of one embodiment of the present invention; [0015]
  • FIG. 2 illustrates a mode register of one embodiment of the present invention; [0016]
  • FIG. 3 is a flow chart of a self-timed write sequence according to one embodiment of the present invention; [0017]
  • FIG. 4 is a flow chart of a complete write status-check sequence according to one embodiment of the present invention; [0018]
  • FIG. 5 is a flow chart of a self-timed block erase sequence according to one embodiment of the present invention; [0019]
  • FIG. 6 is a flow chart of a complete block erase status-check sequence according to one embodiment of the present invention; [0020]
  • FIG. 7 is a flow chart of a block protect sequence according to one embodiment of the present invention; [0021]
  • FIG. 8 is a flow chart of a complete block status-check sequence according to one embodiment of the present invention; [0022]
  • FIG. 9 is a flow chart of a device protect sequence according to one embodiment of the present invention; [0023]
  • FIG. 10 is a flow chart of a block unprotect sequence according to one embodiment of the present invention; [0024]
  • FIG. 11 illustrates the timing of an initialize and load mode register operation; [0025]
  • FIG. 12 illustrates the timing of a clock suspend mode operation; [0026]
  • FIG. 13 illustrates the timing of a burst read operation; [0027]
  • FIG. 14 illustrates the timing of alternating bank read accesses; [0028]
  • FIG. 15 illustrates the timing of a full-page burst read operation; [0029]
  • FIG. 16 illustrates the timing of a burst read operation using a data mask signal; [0030]
  • FIG. 17 illustrates the timing of a write operation followed by a read to a different bank; [0031]
  • FIG. 18 illustrates the timing of a write operation followed by a read to the same bank; and [0032]
  • FIG. 19 is a block diagram of a system of one embodiment of the invention. [0033]
    • DETAILED DESCRIPTION OF THE INVENTION
  • In the following detailed description of present embodiments, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments in which the inventions may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical and electrical changes may be made without departing from the spirit and scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the claims. [0034]
  • The following detailed description is divided into two major sections. The first section is an Interface Functional Description that details compatibility with an SDRAM memory. The second major section is a Functional Description that specifies flash architecture functional commands. [0035]
    • Interface Functional Description
  • Referring to FIG. 1A, a block diagram of one embodiment of the present invention is described. The [0036] memory device 100 includes an array of non-volatile flash memory cells 102. The array is arranged in a plurality of addressable banks. In one embodiment, the memory contains four memory banks 104, 106, 108 and 110. Each memory bank contains addressable sectors of memory cells. The data stored in the memory can be accessed using externally provided location addresses received by address register 112. The addresses are decoded using row address multiplexer circuitry 114. The addresses are also decoded using bank control logic 116 and row address latch and decode circuitry 118. To access an appropriate column of the memory, column address counter and latch circuitry 120 couples the received addresses to column decode circuitry 122. Circuit 124 provides input/output gating, data mask logic, read data latch circuitry and write driver circuitry. Data is input through data input registers 126 and output through data output registers 128. Command execution logic 130 is provided to control the basic operations of the memory device. A state machine 132 is also provided to control specific operations performed on the memory arrays and cells. A status register 134 and an identification register 136 can also be provided to output data. The command circuit 130 and/or state machine 132 can be generally referred to as control circuitry to control read, write, erase and other memory operations.
  • FIG. 1B illustrates an interconnect pin assignment of one embodiment of the present invention. The [0037] memory package 150 has 54 interconnect pins. The pin configuration is substantially similar to available SDRAM packages. Two interconnects specific to the present invention are RP# 152 and Vccp 154. Although the present invention may share interconnect labels that are appear the same as SDRAM's, the function of the signals provided on the interconnects are described herein and should not be equated to SDRAM's unless set forth herein. FIG. 1C illustrates one embodiment of a memory package 160 that has bump connections instead of the pin connections of FIG. 1C. The present invention, therefore, is not limited to a specific package configuration.
  • Prior to describing the operational features of the memory device, a more detailed description of the interconnect pins and their respective signals is provided. The input clock connection is used to provide a clock signal (CLK). The clock signal can be driven by a system clock, and all synchronous flash memory input signals are sampled on the positive edge of CLK. CLK also increments an internal burst counter and controls the output registers. [0038]
  • The input clock enable (CKE) connection is used to activate (HIGH state) and deactivates (LOW state) the CLK signal input. Deactivating the clock input provides POWER-DOWN and STANDBY operation (where all memory banks are idle), ACTIVE POWER-DOWN (a memory row is ACTIVE in either bank) or CLOCK SUSPEND operation (burst/access in progress). CKE is synchronous except after the device enters power-down modes, where CKE becomes asynchronous until after exiting the same mode. The input buffers, including CLK, are disabled during power-down modes to provide low standby power. CKE may be tied HIGH in systems where power-down modes (other than RP# deep power-down) are not required. [0039]
  • The chip select (CS#) input connection provides a signal to enable (registered LOW) and disable (registered HIGH) a command decoder provided in the command execution logic. All commands are masked when CS# is registered HIGH. Further, CS# provides for external bank selection on systems with multiple banks, and CS# can be considered part of the command code; but may not be necessary. [0040]
  • The input command input connections for RAS#, CAS#, and WE# (along with CAS#, CS#) define a command that is to be executed by the memory, as described in detail below. The input/output mask (DQM) connections are used to provide input mask signals for write accesses and an output enable signal for read accesses. Input data is masked when DQM is sampled HIGH during a WRITE cycle. The output buffers are placed in a high impedance (High-Z) state (after a two-clock latency) when DQM is sampled HIGH during a READ cycle. DQML corresponds to data connections DQ0-DQ7 and DQMH corresponds to data connections DQ8-DQ15. DQML and DQMH are considered to be the same state when referenced as DQM. [0041]
  • [0042] Address inputs 133 are primarily used to provide address signals. In the illustrated embodiment the memory has 12 lines (A0-A11). Other signals can be provided on the address connections, as described below. The address inputs are sampled during an ACTIVE command (row-address A0-A11) and a READ/WRITE command (column-address A0-A7) to select one location in a respective memory bank. The address inputs are also used to provide an operating code (OpCode) during a LOAD COMMAND REGISTER operation, explained below. Address lines A0-A11 are also used to input mode settings during a LOAD MODE REGISTER operation.
  • An input reset/power-down (RP#) [0043] connection 140 is used for reset and power-down operations. Upon initial device power-up, a 100 μs delay after RP# has transitioned from LOW to HIGH is required in one embodiment for internal device initialization, prior to issuing an executable command. The RP# signal clears the status register, sets the internal state machine (ISM) 132 to an array read mode, and places the device in a deep power-down mode when LOW. During power down, all input connections, including CS# 142, are “Don't Care” and all outputs are placed in a High-Z state. When the RP# signal is equal to a VHH voltage (5V), all protection modes are ignored during WRITE and ERASE. The RP# signal also allows a device protect bit to be set to 1 (protected) and allows block protect bits of a 16 bit register, at locations 0 and 15 to be set to 0 (unprotected) when brought to VHH. The protect bits are described in more detail below. RP# is held HIGH during all other modes of operation.
  • Bank address input connections, BA0 and BA1 define which bank an ACTIVE, READ, WRITE, or BLOCK PROTECT command is being applied. The DQ0-[0044] DQ15 connections 143 are data bus connections used for bi-directional data communication. Referring to FIG. 1B, a VCCQ connection is used to provide isolated power to the DQ connections to improved noise immunity. In one embodiment, VCCQ=Vcc or 1.8V±15V. The VSSQ connection is used to isolated ground to DQs for improved noise immunity. The VCC connection provides a power supply, such as 3V. A ground connection is provided through the Vss connection. Another optional voltage is provided on the VCCP connection 144. The VCCP connection can be tied externally to VCC, and sources current during device initialization, WRITE and ERASE operations. That is, writing or erasing to the memory device can be performed using a VCCP voltage, while all other operations can be performed with a VCC voltage. The Vccp connection is coupled to a high voltage switch/pump circuit 145.
  • The following sections provide a more detailed description of the operation of the synchronous flash memory. One embodiment of the present invention is a nonvolatile, electrically sector-erasable (Flash), programmable read-only memory containing 67,108,864 bits organized as 4,194,304 words by 16 bits. Other population densities are contemplated, and the present invention is not limited to the example density. Each memory bank is organized into four independently erasable blocks (16 total). To ensure that critical firmware is protected from accidental erasure or overwrite, the memory can include sixteen 256K-word hardware and software lockable blocks. The memory's four-bank architecture supports true concurrent operations. [0045]
  • A read access to any bank can occur simultaneously with a background WRITE or ERASE operation to any other bank. The synchronous flash memory has a synchronous interface (all signals are registered on the positive edge of the clock signal, CLK). Read accesses to the memory can be burst oriented. That is, memory accesses start at a selected location and continue for a programmed number of locations in a programmed sequence. Read accesses begin with the registration of an ACTIVE command, followed by a READ command. The address bits registered coincident with the ACTIVE command are used to select the bank and row to be accessed. The address bits registered coincident with the READ command are used to select the starting column location and bank for the burst access. [0046]
  • The synchronous flash memory provides for programmable read burst lengths of 1, 2, 4 or 8 locations, or the full page, with a burst terminate option. Further, the synchronous flash memory uses an internal pipelined architecture to achieve high-speed operation. [0047]
  • The synchronous flash memory can operate in low-power memory systems, such as systems operating on three volts. A deep power-down mode is provided, along with a power-saving standby mode. All inputs and outputs are low voltage transistor-transistor logic (LVTTL) compatible. The synchronous flash memory offers substantial advances in Flash operating performance, including the ability to synchronously burst data at a high data rate with automatic column address generation and the capability to randomly change column addresses on each clock cycle during a burst access. [0048]
  • In general, the synchronous flash memory is configured similar to a multi-bank DRAM that operates at low voltage and includes a synchronous interface. Each of the banks is organized into rows and columns. Prior to normal operation, the synchronous flash memory is initialized. The following sections provide detailed information covering device initialization; register definition, command descriptions and device operation. [0049]
  • The synchronous flash is powered up and initialized in a predefined manner. After power is applied to VCC, VCCQ and VCCP (simultaneously), and the clock signal is stable, [0050] RP# 140 is brought from a LOW state to a HIGH state. A delay, such as a 100 μs delay, is needed after RP# transitions HIGH in order to complete internal device initialization. After the delay time has passed, the memory is placed in an array read mode and is ready for Mode Register programming or an executable command. After initial programming of a non-volatile mode register 147 (NVMode Register), the contents are automatically loaded into a volatile Mode Register 148 during the initialization. The device will power up in a programmed state and will not require reloading of the non-volatile mode register 147 prior to issuing operational commands. This is explained in greater detail below.
  • The [0051] Mode Register 148 is used to define the specific mode of operation of the synchronous flash memory. This definition includes the selection of a burst length, a burst type, a CAS latency, and an operating mode, as shown in FIG. 2. The Mode Register is programmed via a LOAD MODE REGISTER command and retains stored information until it is reprogrammed. The contents of the Mode Register may be copied into the NVMode Register 147. The NVMode Register settings automatically load the Mode Register 148 during initialization. Details on ERASE NVMODE REGISTER and WRITE NVMODE REGISTER command sequences are provided below. Those skilled in the art will recognize that an SDRAM requires that a mode register must be externally loaded during each initialization operation. The present invention allows a default mode to be stored in the NV mode register 147. The contents of the NV mode register are then copied into a volatile mode register 148 for access during memory operations.
  • Mode Register bits M0-M2 specify a burst length, M3 specifies a burst type (sequential or interleaved), M4-M6 specify a CAS latency, M7 and M8 specify a operating mode, M9 is set to one, and M10 and M11 are reserved in this embodiment. Because WRITE bursts are not currently implemented; M9 is set to a logic one and write accesses are single location (non-burst) accesses. The Mode Register must be loaded when all banks are idle, and the controller must wait the specified time before initiating a subsequent operation. [0052]
  • Read accesses to the synchronous flash memory can be burst oriented, with the burst length being programmable, as shown in Table 1. The burst length determines the maximum number of column locations that can be automatically accessed for a given READ command. Burst lengths of 1, 2, 4, or 8 locations are available for both sequential and the interleaved burst types, and a full-page burst is available for the sequential type. The full-page burst can be used in conjunction with the BURST TERMINATE command to generate arbitrary burst lengths that is, a burst can be selectively terminated to provide custom length bursts. When a READ command is issued, a block of columns equal to the burst length is effectively selected. All accesses for that burst take place within this block, meaning that the burst will wrap within the block if a boundary is reached. The block is uniquely selected by A1-A7 when the burst length is set to two, by A2-A7 when the burst length is set to four, and by A3-A7 when the burst length is set to eight. The remaining (least significant) address bit(s) are used to select the starting location within the block. Full-page bursts wrap within the page if the boundary is reached. [0053]
  • Accesses within a given burst may be programmed to be either sequential or interleaved; this is referred to as the burst type and is selected via bit M3. The ordering of accesses within a burst is determined by the burst length, the burst type and the starting column address, as shown in Table 1. [0054]
    TABLE 1
    BURST DEFINITION
    Order of Accesses Within a Burst
    Burst Type = Type =
    Length Starting Column Address Sequential Interleaved
    2 A0 0-1 0-1
    0 1-0 1-0
    1
    4 A1 A0
    0 0 0-1-2-3 0-1-2-3
    0 1 1-2-3-0 1-0-3-2
    1 0 2-3-0-1 2-3-0-1
    1 1 3-0-1-2 3-2-1-0
    8 A1 A1 A0
    0 0 0 0-1-2-3-4-5-6-7 0-1-2-3-4-5-6-7
    0 0 1 1-2-3-4-5-6-7-0 1-0-3-2-5-4-7-6
    0 1 0 2-3-4-5-6-7-0-1 2-3-0-1-6-7-4-5
    0 1 1 3-4-5-6-7-0-1-2 3-2-1-0-7-6-5-4
    1 0 0 4-5-6-7-0-1-2-3 4-5-6-7-0-1-2-3
    1 0 1 5-6-7-0-1-0-3-2 5-4-7-6-1-0-3-2
    1 1 0 6-7-0-1-2-3-4-5 6-7-4-5-2-3-0-1
    1 1 1 7-0-1-2-3-4-5-6 7-6-5-4-3-2-1-0
    Full n = A0-A7 Cn, Cn + 1, Cn + 2 Not supported
    Page (location 0-255) Cn + 3, Cn + 4
    256 . . . Cn − 1,
    Cn . . .
  • The following truth table provides more detail of some operation commands relating to protection of the memory array according to an embodiment of the memory of the present invention. [0055]
    TABLE 1
    TRUTH
    Flash Memory Command Sequences
    1st CYCLE 2nd CYCLE 3rd CYCLE
    Operation C A A D R C A A D R C A A D R
    M D D Q P M D D Q P M D D Q P
    D D D # D D D # D D D #
    R R R R R R
    Protect L 6 B X H AC R B X H W X B 0 H
    Block/ C 0 an TI o an RI an 1 /
    Confirm R H k VE w k T k H V
    E HH
    Protect L 6 B X H AC X B X H W X B F V
    Device/ C 0 an TI an RI an 1 HH
    Confirm R H k VE k T k H
    E
    Unprotect L 6 B X H AC X B X H W X B D H
    Blocks/ C 0 an TI an RI an 0 /
    Confirm R H k VE k T k H V
    E HH
    • Function Description
  • The synchronous flash memory incorporates a number of features to make it ideally suited for code storage and execute-in-place applications on an SDRAM bus. The memory array is segmented into individual erase blocks. Each block may be erased without affecting data stored in other blocks. These memory blocks are read, written and erased by issuing commands to the command execution logic [0056] 130 (CEL). The CEL controls the operation of the Internal State Machine 132 (ISM), which completely controls all ERASE NVMODE REGISTER, WRITE NVMODE REGISTER, WRITE, BLOCK ERASE, BLOCK PROTECT, DEVICE PROTECT, UNPROTECT ALL BLOCKS and VERIFY operations. The ISM 132 protects each memory location from over-erasure and optimizes each memory location for maximum data retention. In addition, the ISM greatly simplifies the control necessary for writing the device in-system or in an external programmer.
  • The synchronous flash memory is organized into 16 independently erasable memory blocks that allow portions of the memory to be erased without affecting the rest of the memory data. Any block may be hardware-protected against inadvertent erasure or writes. A protected block requires that the RP# pin be driven to VHH (a relatively high voltage) before being modified. The 256K-word blocks at [0057] locations 0 and 15 can have additional hardware protection. Once a PROTECT BLOCK command has been executed to these blocks, an UNPROTECT ALL BLOCKS command will unlock all blocks except the blocks at locations 0 and 15, unless the RP# pin is at VHH. This provides additional security for critical code during in-system firmware updates, should an unintentional power disruption or system reset occur.
  • Power-up initialization, ERASE, WRITE and PROTECT timings are simplified by using an ISM to control all programming algorithms in the memory array. The ISM ensures protection against over-erasure and optimizes write margin to each cell. During WRITE operations, the ISM automatically increments and monitors WRITE attempts, verifies write margin on each memory cell and updates the ISM Status Register. When a BLOCK ERASE operation is performed, the ISM automatically Overwrites the entire addressed block (eliminates over-erasure), increments and monitors ERASE attempts and sets bits in the ISM Status Register. [0058]
  • The 8-bit [0059] ISM Status Register 134 allows an external processor 200 to monitor the status of the ISM during WRITE, ERASE and PROTECT operations. One bit of the 8-bit Status Register (SR7) is set and cleared entirely by the ISM. This bit indicates whether the ISM is busy with an ERASE, WRITE or PROTECT task. Additional error information is set in three other bits (SR3, SR4 and SR5): write and protect block error, erase and unprotect all blocks error, and device protection error. Status register bits SRO, SR1 and SR2 provide details on the ISM operation underway. The user can monitor whether a device-level or bank-level ISM operation (including which bank is under ISM control) is underway. These six bits (SR3-SR5) must be cleared by the host system. Table 2 illustrates one embodiment of the status register.
    TABLE 2
    STATUS REGISTER
    STATUS
    BIT# STATUS REGISTER BIT DESCRIPTION
    SR7 ISM STATUS The ISMS bit displays the active
    1 = Ready status of the state machine when
    0 = Busy performing WRITE or BLOCK
    ERASE. The controlling logic polls
    this bit to determine when the erase
    and write status bits are valid.
    SR6 RESERVED Reserved for future use.
    SR5 ERASE/UNPROTECT BLOCK ES is set to 1 after the maximum
    STATUS number of ERASE cycles is
    1 = BLOCK ERASE or executed by the ISM without a
    BLOCK UNPROTECT error successful verify. This bit is also set
    0 = Successful BLOCK ERASE to 1 if a BLOCK UNPROTECT
    or UNPROTECT operation is unsuccessful. ES is only
    cleared by a CLEAR STATUS
    REGISTER command or by a
    RESET.
    SR4 WRITE/PROTECT BLOCK WS is set to 1 after the maximum
    STATUS number of WRITE cycles is
    1 = WRITE or BLOCK executed by the ISM without a
    PROTECT error successful verify. This bit is also set
    0 = Successful WRITE or to 1 if a BLOCK or DEVICE
    BLOCK PROTECT PROTECT operation is
    unsuccessful. WS is only cleared by
    a CLEAR STATUS REGISTER
    command or by a RESET.
    SR2 BANKA1 ISM STATUS When SR0 = 0, the bank under ISM
    SR1 BANKA0 ISM STATUS control can be decoded from BA0,
    BA1: [0,0] Bank0; [0,1] Bank1;
    [1,0] Bank2; [1,1] Bank3.
    SR3 DEVICE PROTECT STATUS DPS is set to 1 if an invalid WRITE,
    1 = Device protected, invalid ERASE, PROTECT BLOCK,
    operation attempted PROTECT DEVICE or
    0 = Device unprotected or RP# UNPROTECT ALL BLOCKS is
    condition met attempted. After one of these
    commands is issued, the condition of
    RP#, the block protect bit and the
    device protect bit are compared to
    determine if the desired operation is
    allowed. Must be cleared by
    CLEAR STATUS REGISTER or by
    a RESET.
    SR0 DEVICE/BANK ISM STATUS DBS is set to 1 if the ISM operation
    1 = Device level ISM operation is a device-level operation. A valid
    0 = Bank level ISM operation READ to any bank of the array can
    immediately follow the registration
    of a device-level ISM WRITE
    operation. When DBS is set to 0, the
    ISM operation is a bank-level
    operation. A READ to the bank
    under ISM control may result in
    invalid data. SR2 and SR3 can be
    decoded to determine which bank is
    under ISM control.
  • To allow for maximum power conservation, the synchronous flash features a very low current, deep power-down mode. To enter this mode, the RP# pin [0060] 140 (reset/power-down) is taken to VSS ±0.2V. To prevent an inadvertent RESET, RP# must be held at Vss for 100 ns prior to the device entering the reset mode. With RP# held at Vss, the device will enter the deep power-down mode. After the device enters the deep power-down mode, a transition from LOW to HIGH on RP# will result in a device power-up initialize sequence as outlined herein. Transitioning RP# from LOW to HIGH after entering the reset mode but prior to entering deep power-down mode requires a 1 μs delay prior to issuing an executable command. When the device enters the deep power-down mode, all buffers excluding the RP# buffer are disabled and the current draw is low, for example, a maximum of 50 μA at 3.3V VCC. The input to RP# must remain at Vss during deep power-down. Entering the RESET mode clears the Status Register 134 and sets the ISM 132 to the array read mode.
  • The synchronous flash memory array architecture is designed to allow sectors to be erased without disturbing the rest of the array. The array is divided into 16 addressable “blocks” that are independently erasable. By erasing blocks rather than the entire array, the total device endurance is enhanced, as is system flexibility. Only the ERASE and BLOCK PROTECT functions are block oriented. The 16 addressable blocks are equally divided into four [0061] banks 104, 106, 108 and 110 of four blocks each.
  • The four banks have simultaneous read-while-write functionality. An ISM WRITE or ERASE operation to any bank can occur simultaneously to a READ operation to any other bank. The [0062] Status Register 134 maybe polled to determine which bank is under ISM operation. The synchronous flash memory has a single background operation ISM to control power-up initialization, ERASE, WRITE, and PROTECT operations. Only one ISM operation can occur at any time; however, certain other commands, including READ operations, can be performed while the ISM operation is taking place. An operational command controlled by the ISM is defined as either a bank-level operation or a device-level operation. WRITE and ERASE are bank-level ISM operations. After an ISM bank operation has been initiated, a READ to any location in the bank may output invalid data, whereas a READ to any other bank will read the array. A READ STATUS REGISTER command will output the contents of the Status Register 134. The ISM status bit will indicate when the ISM operation is complete (SR7=1). When the ISM operation is complete, the bank will automatically enter the array read mode. ERASE NVMODE REGISTER, WRITE NVMODE REGISTER, BLOCK PROTECT, DEVICE PROTECT, and UNPROTECT ALL BLOCKS are device-level ISM operations. Once an ISM device-level operation has been initiated, a READ to any bank will output the contents of the array. A READ STATUS REGISTER command may be issued to determine completion of the ISM operation. When SR7=1, the ISM operation will be complete and a subsequent ISM operation may be initiated. Any block may be protected from unintentional ERASE or WRITE with a hardware circuit that requires the RP# pin be driven to VHH before a WRITE or ERASE is commenced, as explained below.
  • Any block may be hardware-protected to provide extra security for the most sensitive portions of the firmware. During a WRITE or ERASE of a hardware protected block, the RP# pin must be held at VHH until the WRITE or ERASE is completed. Any WRITE or ERASE attempt on a protected block without RP# =VHH will be prevented and will result in a write or erase error. The blocks at [0063] locations 0 and 15 can have additional hardware protection to prevent an inadvertent WRITE or ERASE operation. In this embodiment, these blocks cannot be software-unlocked through an UNPROTECT ALL BLOCKS command unless RP# =VHH. The protection status of any block may be checked by reading its block protect bit with a READ STATUS REGISTER command. Further, to protect a block, a three-cycle command sequence must be issued with the block address.
  • The device protection status and block protect status can be read by issuing a READ DEVICE CONFIGURATION (90H) command. To read the desired register, a specific address must be asserted. While in this mode, specific addresses are issued to read the desired information. The device protect bit is read at 000003H, and each of the block protect bits is read at the third address location within each block (xx0002H). The device and block protect bits are output on DQ0. See Table 3 for more details on some of the various device configuration registers [0064] 136.
    TABLE 3
    DEVICE CONFIGURATION
    Device
    Configuration Address Data CONDITION
    Block Protect Bit xx0002H DQ0 = 1 Block protected
    xx0002H DQ0 = 0 Block unprotected
    Device Protect Bit 000003H DQ0 = 1 Block protect modification
    prevented
    000003H DQ0 = 0 Block protect modification
    enabled
  • Three consecutive commands on consecutive clock edges are needed to input data to the array (NOPs and Command Inhibits are permitted between cycles). In the first cycle, a LOAD COMMAND REGISTER command is given with WRITE SETUP (40H) on A0-A7, and the bank address is issued on BA0, BA1. The next command is ACTIVE, which activates the row address and confirms the bank address. The third cycle is WRITE, during which the starting column, the bank address, and data are issued. The ISM status bit will be set on the following clock edge (subject to CAS latencies). While the ISM executes the WRITE, the ISM status bit (SR7) will be at 0. A READ operation to the bank under ISM control may produce invalid data. When the ISM status bit (SR7) is set to a [0065] logic 1, the WRITE has been completed, and the bank will be in the array read mode and ready for an executable command. Writing to hardware-protected blocks also requires that the RP# pin be set to VHH prior to the third cycle (WRITE), and RP# must be held at VHH until the ISM WRITE operation is complete. The write and erase status bits (SR4 and SR5) will be set if the LCR-ACTIVE-WRITE command sequence is not completed on consecutive cycles or the bank address changes for any of the three cycles. After the ISM has initiated the WRITE, it cannot be aborted except by a RESET or by powering down the part. Doing either during a WRITE may corrupt the data being written.
  • Executing an ERASE sequence will set all bits within a block to [0066] logic 1. The command sequence necessary to execute an ERASE is similar to that of a WRITE. To provide added security against accidental block erasure, three consecutive command sequences on consecutive clock edges are required to initiate an ERASE of a block. In the first cycle, LOAD COMMAND REGISTER is given with ERASE SETUP (20H) on A0-A7, and the bank address of the block to be erased is issued on BA0, BA1. The next command is ACTIVE, where A10, A11, BA0, BA1 provide the address of the block to be erased. The third cycle is WRITE, during which ERASE CONFRIM (DOH) is given on DQ0-DQ7 and the bank address is reissued. The ISM status bit will be set on the following clock edge (subject to CAS latencies). After ERASE CONFIRM (D0H) is issued, the ISM will start the ERASE of the addressed block. Any READ operation to the bank where the addressed block resides may output invalid data. When the ERASE operation is complete, the bank will be in the array read mode and ready for an executable command. Erasing hardware-protected blocks also requires that the RP# pin be set to VHH prior to the third cycle (WRITE), and RP# must be held at VHH until the ERASE is completed (SR7=1). If the LCR-ACTIVE-WRITE command sequence is not completed on consecutive cycles (NOPs and COMMAND INHIBITs are permitted between cycles) or the bank address changes for one or more of the command cycles, the write and erase status bits (SR4 and SR5) will be set and the operation is prohibited.
  • Executing a BLOCK PROTECT sequence enables the first level of software/hardware protection for a given block. The memory includes a 16-bit register that has one bit corresponding to the 16 protectable blocks. The memory also has a register to provide a device bit used to protect the entire device from write and erase operations. The command sequence necessary to execute a BLOCK PROTECT is similar to that of a WRITE. To provide added security against accidental block protection, three consecutive command cycles are required to initiate a BLOCK PROTECT. In the first cycle, a LOAD COMMAND REGISTER is issued with a PROTECT SETUP (60H) command on A0-A7, and the bank address of the block to be protected is issued on BA0, BA1. The next command is ACTIVE, which activates a row in the block to be protected and confirms the bank address. The third cycle is WRITE, during which BLOCK PROTECT CONFIRM (01H) is issued on DQ0-DQ7, and the bank address is reissued. The ISM status bit will be set on the following clock edge (subject to CAS latencies). The ISM will then begin the PROTECT operation. If the LCR-ACTIVE-WRITE is not completed on consecutive cycles (NOPs and COMMAND INHIBITs are permitted between cycles) or the bank address changes, the write and erase status bits (SR4 and SR5) will be set and the operation is prohibited. When the ISM status bit (SR7) is set to a [0067] logic 1, the PROTECT has been completed, and the bank will be in the array read mode and ready for an executable command. Once a block protect bit has been set to a 1 (protected), it can only be reset to a 0 if the UNPROTECT ALL BLOCKS command. The UNPROTECT ALL BLOCKS command sequence is similar to the BLOCK PROTECT command; however, in the third cycle, a WRITE is issued with a UNPROTECT ALL BLOCKS CONFIRM (DOH) command and addresses are “Don't Care.”
  • The blocks at [0068] locations 0 and 15 have additional security. Once the block protect bits at locations 0 and 15 have been set to a 1 (protected), each bit can only be reset to a 0 if RP# is brought to VHH prior to the third cycle of the UNPROTECT operation, and held at VHH until the operation is complete (SR7=1). Further, if the device protect bit is set, RP# must be brought to VHH prior to the third cycle and held at VHH until the BLOCK PROTECT or UNPROTECT ALL BLOCKS operation is complete. To check a block's protect status, a READ DEVICE CON FIGURATION (90H) command may be issued.
  • Executing a DEVICE PROTECT sequence sets the device protect bit to a 1 and prevents a block protect bit modification. The command sequence necessary to execute a DEVICE PROTECT is similar to that of a WRITE. Three consecutive command cycles are required to initiate a DEVICE PROTECT sequence. In the first cycle, LOAD COMMAND REGISTER is issued with a PROTECT SETUP (60H) on A0-A7, and a bank address is issued on BA0, BA1. The bank address is “Don't Care” but the same bank address must be used for all three cycles. The next command is ACTIVE. The third cycle is WRITE, during which a DEVICE PROTECT (F 1 H) command is issued on DQ0-DQ7, and RP# is brought to VHH. The ISM status bit will be set on the following clock edge (subject to CAS latencies). An executable command can be issued to the device. RP# must be held at VHH until the WRITE is completed (SR7=1). A new WRITE operation will not be permitted until the current ISM operation is complete. Once the device protect bit is set, it cannot be reset to a 0. With the device protect bit set to a 1, BLOCK PROTECT or BLOCK UNPROTECT is prevented unless RP# is at VHH during either operation. The device protect bit does not affect WRITE or ERASE operations. Refer to Table 4 for more information on block and device protect operations. [0069]
    TABLE 4
    PROTECT OPERATIONS TRUTH TABLE
    FUNCTION RP # CS # DQM WE # Address Vccp DQ0-DQ7
    DEVICE UNPROTECTED
    PROTECT SETUP H L H L 60H X X
    PROTECT BLOCK H L H L BA H 01H
    PROTECT DEVICE VHH L H L X X F1H
    UNPROTECT H/VHH H X H D0H
    ALL BLOCKS
    DEVICE PROTECTED
    PROTECT H or VHH H 60H X X
    SETUP
    PROTECT VHH H BA H 01H
    BLOCK
    UNPROTECT VHH H X H D0H
    ALL BLOCKS
  • After the state machine status register bit (SR7) has been set, the device/bank (SRO), device protect (SR3), bankA0 (SR1), bankA1 (SR2), write/protect block (SR4) and erase/unprotect (SR5) status bits may be checked. If one or a combination of SR3, SR4, SR5 status bits has been set, an error has occurred during operation. The ISM cannot reset the SR3, SR4 or SR5 bits. To clear these bits, a CLEAR STATUS REGISTER (50H) command must be given. Table 5 lists some combinations of errors. [0070]
    TABLE 5
    STATUS REGISTER ERROR DECODE
    STATUS BITS
    SR5 SR4 SR3 ERROR DESCRIPTION
    0 0 0 No errors
    0 1 0 WRITE, BLOCK PROTECT or DEVICE PROTECT error
    0 1 1 Invalid BLOCK PROTECT or DEVICE PROTECT, RP# not
    valid (VHH)
    0 1 1 Invalid BLOCK or DEVICE PROTECT, RP# not valid
    1 0 0 ERASE or ALL BLOCK UNPROTECT error
    1 0 1 Invalid ALL BLOCK UNPROTECT, RP# not valid (VHH)
    1 1 0 Command sequencing error
  • Referring to FIG. 3, a flow chart of a self-timed write sequence according to one embodiment of the present invention is described. The sequence includes loading the command register ([0071] code 40H), receiving an active command and a row address, and receiving a write command and a column address. The sequence then provides for a status register polling to determine if the write is complete. The polling monitors status register bit 7 (SR7) to determine if it is set to a 1. An optional status check can be included. When the write is completed, the array is placed in the array read mode.
  • Referring to FIG. 4, a flow chart of a complete write status-check sequence according to one embodiment of the present invention is provided. The sequence looks for status register bit 4 (SR4) to determine if it is set to a 0. If SR4 is a 1, there was an error in the write operation. The sequence also looks for status register bit 3 (SR3) to determine if it is set to a 0. If SR3 is a 1, there was an invalid write error during the write operation. [0072]
  • Referring to FIG. 5, a flow chart of a self-timed block erase sequence according to one embodiment of the present invention is provided. The sequence includes loading the command register (code 20H), and receiving an active command and a row address. The memory then determines if the block is protected. If it is not protected, the memory performs a write operation (D0H) to the block and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode. If the block is protected, the erase is not allowed unless the RP# signal is at an elevated voltage (VHH). [0073]
  • FIG. 6 illustrates a flow chart of a complete block erase status-check sequence according to one embodiment of the present invention. The sequence monitors the status register to determine if a command sequence error occurred (SR4 or SR5=1). If SR3 is set to a 1, an invalid erase or unprotect error occurred. Finally, a block erase or unprotect error happened if SR5 is set to a 1. [0074]
  • FIG. 7 is a flow chart of a block protect sequence according to one embodiment of the present invention. The sequence includes loading the command register ([0075] code 60H), and receiving an active command and a row address. The memory then determines if the block is protected. If it is not protected, the memory performs a write operation (01H) to the block and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode. If the block is protected, the erase is not allowed unless the RP# signal is at an elevated voltage (VHH).
  • Referring to FIG. 8, a flow chart of a complete block status-check sequence according to one embodiment of the present invention is provided. The sequence monitors the [0076] status register bits 3, 4 and 5 to determine of errors were detected.
  • FIG. 9 is a flow chart of a device protect sequence according to one embodiment of the present invention. The sequence includes loading the command register ([0077] code 60H), and receiving an active command and a row address. The memory then determines if RP# is at VHH. The memory performs a write operation (F1H) and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode.
  • FIG. 10 is a flow chart of a block unprotect sequence according to one embodiment of the present invention. The sequence includes loading the command register ([0078] code 60H), and receiving an active command and a row address. The memory then determines if the memory device is protected. If it is not protected, the memory determines if the boot locations (blocks 0 and 15) are protected. If none of the blocks are protected the memory performs a write operation (DOH) to the block and monitors the status register for completion. An optional status check can be performed and the memory is placed in an array read mode. If the device is protected, the erase is not allowed unless the RP# signal is at an elevated voltage (VHH). Likewise, if the boot locations are protected, the memory detennines if all blocks should be unprotected.
  • FIG. 11 illustrates the timing of an initialize and load mode register operation. The mode register is programmed by providing a load mode register command and providing operation code (opcode) on the address lines. The opcode is loaded into the mode register. As explained above, the contents of the non-volatile mode register are automatically loaded into the mode register upon power-up and the load mode register operation may not be needed. [0079]
  • FIG. 12 illustrates the timing of a clock suspend mode operation, and FIG. 13 illustrates the timing of another burst read operation. FIG. 14 illustrates the timing of alternating bank read accesses. Here active commands are needed to change bank addresses. A full page burst read operation is illustrated in FIG. 15. Note that the full page burst does not self terminate, but requires a terminate command. [0080]
  • FIG. 16 illustrates the timing of a read operation using a data mask signal. The DQM signal is used to mask the data output so that Dout m+1 is not provided on the DQ connections. [0081]
  • Referring to FIG. 17, the timing of a write operation followed by a read to a different bank is illustrated. In this operation, a write is performed to bank a and a subsequent read is performed to bank b. The same row is accessed in each bank. [0082]
  • Referring to FIG. 18, the timing of a write operation followed by a read to the same bank is illustrated. In this operation, a write is performed to bank a and a subsequent read is performed to bank a. A different row is accessed for the read operation, and the memory must wait for the prior write operation to be completed. This is different from the read of FIG. 17 where the read was not delayed due to the write operation. [0083]
    • Brown Out Protection
  • A loss of power is very serious during the operation of a memory device. Data corruption could occur if the device is busy writing. [0084]
  • One embodiment of the present invention has a [0085] protection register 149 that prevents any program or erase operation from being performed on selected blocks. This register can have a volatile and a non-volatile component. The contents of the non-volatile register include default protection settings and are transferred to the volatile register during power-up. A low Vcc detection circuit 125 (FIG. 1) is also provided that sets the volatile portion of this protection register 149 to protect all blocks during a low voltage situation. Command logic 130 can program register 149 in response to circuit 125.
  • Upon power up and during initialization a lot of internal registers need to be set properly for the memory device to work properly. With that in mind, a brown out, or a glitch in power, may not be noticed by the system controller and could impact all the settings of the device. Any subsequent attempt to communicate with this device would result in unpredictable behavior. [0086]
  • In operation, the non-volatile protection register is programmed to protect selected memory locations. This data is then loaded into the volatile shadow register and accessed during operations. If the low Vcc detection circuit determines that the Vcc voltage dropped below a preset level, the volatile register is set to protect all sectors of the memory. In one embodiment, the detection circuit indicates if the Vcc level drops below 2 volts with a supply voltage of about 3 to 3.6 volts. This provides a level of safety to protect the memory during supply voltage variations. If a controller then attempts to write to a memory location, the memory will indicate that the location is protected. The controller can then check the status of the memory, and perform a reset/initialization of the memory. [0087]
  • Referring to FIG. 19, a block diagram of a system of one embodiment is provided. The low Vcc detection circuit can also set a [0088] latch 127 when the power returns to a good level. This latch can also be read through the status register 134. Performing an initialization of the memory will reset the brown out latch. Thus, the register can be read to determine if an initialization operation was performed. That is, the latch is set to a first state after an initialization is performed, and the latch is set to a second state if the Vcc level drops.
  • The addition of the brown out detection allows the system to check [0089] status register 134 to see if the device is ready to communicate. This also allows the processor 200 to determine if initialization has occurred. Thus, the brown out latch 127 can be read to determine if a brown out has occurred and a reset is needed.
    • Conclusion
  • A synchronous flash memory includes an array of non-volatile memory cells. The memory device has a package configuration that is compatible with an SDRAM. The memory device can detect a brown-out of a supply voltage. The memory device comprises a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a predetermined value. A latch is coupled to the voltage detection circuit and can be programmed to indicate if the supply voltage dropped below the predetermined value. An external controller can read a status of the latch. The memory, therefore, can provide an indication to an external controller that a reset, or initialization, operation is needed. [0090]

Claims (21)

What is claimed is:
1. A memory device comprising:
a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a predetermined value; and
a latch coupled to the voltage detection circuit, wherein the latch can be programmed to indicate if the supply voltage dropped below the predetermined value.
2. The memory device of claim 1 further comprises an externally accessible status register to provide data indicating a programmed state of the latch to an external controller.
3. The memory device of claim 1 wherein the latch is programmed to a first data state after the memory device is initialized, and the latch is programmed to a second data state when the supply voltage drops below the predetermined value.
4. The memory device of claim 1 further comprising an array of non-volatile memory cells.
5. The memory device of claim 1 wherein the predetermined value is about one volt below a normal supply voltage, Vcc.
6. A memory device comprising:
a voltage detection circuit to monitor a supply voltage and provide a signal if the supply voltage drops below a predetermined value;
a volatile register to store operating data;
a brown-out latch circuit programmed to a first data state after an initialization operation is performed to load the volatile register, the brown-out latch is programmed to a second state in response to the voltage detection circuit if the supply voltage drops below the predetermined value.
7. The memory device of claim 6 further comprises an externally accessible status register to provide data indicating a programmed state of the latch to an external controller.
8. The memory device of claim 6 further comprising an array of non-volatile memory cells.
9. The memory device of claim 6 wherein the predetermined value is about one volt below a normal supply voltage, Vcc.
10. A system comprising:
a power supply; and
a memory device coupled to the power supply to receive a supply voltage, the memory device comprises,
a voltage detection circuit to monitor the supply voltage and provide a signal if the supply voltage drops below a predetermined value, and
a latch coupled to the voltage detection circuit, wherein the latch can be programmed to indicate if the supply voltage dropped below the predetermined value.
11. The system of claim 10 further comprising a memory controller coupled to the memory device, and wherein the memory device comprises an externally accessible status register to provide data indicating a programmed state of the latch to the memory controller.
12. The system of claim 10 wherein the latch is programmed to a first data state after the memory device is initialized, and the latch is programmed to a second data state when the supply voltage drops below the predetermined value
13. The system of claim 10 wherein the memory device is a flash memory having an array of non-volatile memory cells.
14. A system comprising:
a power supply to provide a supply voltage;
a memory controller; and
a synchronous flash memory device coupled to the memory controller and the power supply, the synchronous flash memory device comprises,
an array of non-volatile memory cells,
a voltage detection circuit to monitor the supply voltage and provide a signal if the supply voltage drops below a predetermined value, and
a latch coupled to the voltage detection circuit, wherein the latch can be programmed to indicate if the supply voltage dropped below the predetermined value.
15. A method of operating a memory device comprising:
performing a first initialization operation on the memory device;
changing a data state of a latch circuit from a default state to a second state after the first initialization operation;
monitoring a supply voltage of the memory device; and
setting the latch circuit to the default data state-if the supply voltage is below a predetermined voltage.
16. The method of claim 15 further comprising:
reading the data state of the latch circuit using a controller located external from the memory device.
17. The method of claim 15 further comprising:
performing a second initialization operation after the latch circuit is set to the default data state.
18. The method of claim 15 wherein performing the initialization operation comprises:
reading data stored in a non-volatile register; and
storing the data read from the non-volatile elements in at least one volatile register.
19. A method of operating a memory device comprising:
using an external memory controller, reading a data state of a latch circuit located in the memory device; and
performing an initialization operation on the memory device in response to the data state of the latch circuit.
20. The method of claim 19 further comprising:
monitoring a supply voltage of the memory device; and
setting the latch circuit to a default data state if the supply voltage is below a predetermined voltage.
21. The method of claim 19 wherein performing the initialization operation comprises:
reading data stored in a non-volatile register; and
storing the data read from the non-volatile elements in at least one volatile register.
US09/862,868 2000-07-28 2001-05-22 Protection after brown out in a synchronous memory Expired - Lifetime US6366521B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/862,868 US6366521B1 (en) 2000-07-28 2001-05-22 Protection after brown out in a synchronous memory

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/628,183 US6246626B1 (en) 2000-07-28 2000-07-28 Protection after brown out in a synchronous memory
US09/862,868 US6366521B1 (en) 2000-07-28 2001-05-22 Protection after brown out in a synchronous memory

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/628,183 Continuation US6246626B1 (en) 2000-07-28 2000-07-28 Protection after brown out in a synchronous memory

Publications (2)

Publication Number Publication Date
US20020036941A1 true US20020036941A1 (en) 2002-03-28
US6366521B1 US6366521B1 (en) 2002-04-02

Family

ID=24517822

Family Applications (2)

Application Number Title Priority Date Filing Date
US09/628,183 Expired - Lifetime US6246626B1 (en) 2000-07-28 2000-07-28 Protection after brown out in a synchronous memory
US09/862,868 Expired - Lifetime US6366521B1 (en) 2000-07-28 2001-05-22 Protection after brown out in a synchronous memory

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/628,183 Expired - Lifetime US6246626B1 (en) 2000-07-28 2000-07-28 Protection after brown out in a synchronous memory

Country Status (1)

Country Link
US (2) US6246626B1 (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6618312B2 (en) * 2001-05-04 2003-09-09 Texas Instruments Incorporated Method and device for providing a multiple phase power on reset
KR101815136B1 (en) 2009-11-27 2018-01-05 삼성전자주식회사 Method and apparatus for protecting data of flash memory
KR20200131749A (en) * 2019-05-13 2020-11-24 윈본드 일렉트로닉스 코포레이션 Semiconductor device
US11169587B2 (en) * 2020-01-10 2021-11-09 Micron Technology, Inc. Feedback for power management of a memory die using a dedicated pin

Families Citing this family (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6330679B1 (en) * 1997-12-31 2001-12-11 Intel Corporation Input buffer circuit with dual power down functions
US6246626B1 (en) * 2000-07-28 2001-06-12 Micron Technology, Inc. Protection after brown out in a synchronous memory
US6751740B1 (en) * 2000-08-11 2004-06-15 Sun Microsystems, Inc. Method and system for using a combined power detect and presence detect signal to determine if a memory module is connected and receiving power
US6711701B1 (en) * 2000-08-25 2004-03-23 Micron Technology, Inc. Write and erase protection in a synchronous memory
JP2002175689A (en) * 2000-09-29 2002-06-21 Mitsubishi Electric Corp Semiconductor integrated circuit device
DE10101971A1 (en) * 2001-01-17 2002-07-25 Siemens Ag An electronic state storage device for monitoring the availability of power supply voltages from an electrical system for monitoring the power supply to motor vehicle safety critical devices, while the engine is not running
US6549975B2 (en) * 2001-03-08 2003-04-15 Micron Technology, Inc. Tri-stating output buffer during initialization of synchronous memory
US6865702B2 (en) * 2001-04-09 2005-03-08 Micron Technology, Inc. Synchronous flash memory with test code input
US7036004B2 (en) * 2001-07-25 2006-04-25 Micron Technology, Inc. Power up initialization for memory
US6625081B2 (en) 2001-08-13 2003-09-23 Micron Technology, Inc. Synchronous flash memory with virtual segment architecture
US6560161B1 (en) 2001-08-30 2003-05-06 Micron Technology, Inc. Synchronous flash memory command sequence
US6529409B1 (en) * 2001-09-10 2003-03-04 Silicon Storage Technology, Inc. Integrated circuit for concurrent flash memory with uneven array architecture
US6870770B2 (en) 2001-12-12 2005-03-22 Micron Technology, Inc. Method and architecture to calibrate read operations in synchronous flash memory
KR100415092B1 (en) * 2002-05-13 2004-01-13 주식회사 하이닉스반도체 A semiconductor memory device with a mode register, and method for controlling deep power down mode thereof
US6751139B2 (en) 2002-05-29 2004-06-15 Micron Technology, Inc. Integrated circuit reset circuitry
KR100452326B1 (en) * 2002-07-04 2004-10-12 삼성전자주식회사 Method and circuit for selecting mode of operation voltage in semiconductor memory device thereof
JP4679036B2 (en) * 2002-09-12 2011-04-27 ルネサスエレクトロニクス株式会社 Storage device
US6879517B2 (en) * 2002-09-18 2005-04-12 Motorola, Inc. Battery circuit with three-terminal memory device
US7272709B2 (en) * 2002-12-26 2007-09-18 Micron Technology, Inc. Using chip select to specify boot memory
US6944064B2 (en) * 2003-12-22 2005-09-13 Silicon Storage Technology, Inc. Memory unit having programmable device ID
US20060095622A1 (en) * 2004-10-28 2006-05-04 Spansion, Llc System and method for improved memory performance in a mobile device
US7693669B2 (en) * 2005-04-12 2010-04-06 Atmel Corporation Method and circuit for detecting a brown out condition
KR100702310B1 (en) * 2005-07-21 2007-03-30 주식회사 하이닉스반도체 Non-volatile latch circuit and system on chip with the same
US7512507B2 (en) * 2006-03-23 2009-03-31 Micron Technology, Inc. Die based trimming
US7292487B1 (en) 2006-05-10 2007-11-06 Micron Technology, Inc. Independent polling for multi-page programming
KR101364443B1 (en) * 2007-01-31 2014-02-17 삼성전자주식회사 Memory system, memory controller and memory for the same, and method of constructing signal of the same
US7609562B2 (en) * 2007-01-31 2009-10-27 Intel Corporation Configurable device ID in non-volatile memory
CN101802923B (en) * 2007-08-06 2014-09-03 桑迪士克科技股份有限公司 Enhanced write abort mechanism for non-volatile memory
US7599241B2 (en) * 2007-08-06 2009-10-06 Sandisk Corporation Enhanced write abort mechanism for non-volatile memory
KR101031519B1 (en) * 2007-12-20 2011-04-29 주식회사 하이닉스반도체 Semiconductor memory input/output device
US8832353B2 (en) * 2009-04-07 2014-09-09 Sandisk Technologies Inc. Host stop-transmission handling
US8228100B2 (en) 2010-01-26 2012-07-24 Freescale Semiconductor, Inc. Data processing system having brown-out detection circuit
US8253453B2 (en) 2010-10-28 2012-08-28 Freescale Semiconductor, Inc. Brown-out detection circuit
US9037902B2 (en) 2013-03-15 2015-05-19 Sandisk Technologies Inc. Flash memory techniques for recovering from write interrupt resulting from voltage fault
US9355674B2 (en) 2013-07-19 2016-05-31 Seagate Technology Llc Data storage device and system having adaptive brownout detection
CN109427399A (en) * 2017-08-31 2019-03-05 北京兆易创新科技股份有限公司 A kind of programmed method and programmer of NOR Flash
US10770119B2 (en) * 2018-12-06 2020-09-08 Macronix International Co., Ltd. Memory circuit

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR940006094B1 (en) 1989-08-17 1994-07-06 삼성전자 주식회사 Nonvolatile semiconductor memory device and fabricating method thereof
US5414671A (en) * 1990-05-01 1995-05-09 Sharp Kabushimi Kaisha Semiconductor memory device having operation control means with data judging function
JPH04341997A (en) * 1991-05-20 1992-11-27 Mitsubishi Electric Corp Semiconductor memory device
JP3319105B2 (en) 1993-12-15 2002-08-26 富士通株式会社 Synchronous memory
US5696917A (en) 1994-06-03 1997-12-09 Intel Corporation Method and apparatus for performing burst read operations in an asynchronous nonvolatile memory
US5537065A (en) * 1994-09-15 1996-07-16 Lsi Logic Corporation Programmable voltage detection system
US5526364A (en) 1995-02-10 1996-06-11 Micron Quantum Devices, Inc. Apparatus for entering and executing test mode operations for memory
US5661054A (en) 1995-05-19 1997-08-26 Micron Technology, Inc. Method of forming a non-volatile memory array
US5600605A (en) 1995-06-07 1997-02-04 Micron Technology, Inc. Auto-activate on synchronous dynamic random access memory
US5557579A (en) * 1995-06-26 1996-09-17 Micron Technology, Inc. Power-up circuit responsive to supply voltage transients with signal delay
US5666321A (en) 1995-09-01 1997-09-09 Micron Technology, Inc. Synchronous DRAM memory with asynchronous column decode
US5793775A (en) 1996-01-26 1998-08-11 Micron Quantum Devices, Inc. Low voltage test mode operation enable scheme with hardware safeguard
US5787457A (en) 1996-10-18 1998-07-28 International Business Machines Corporation Cached synchronous DRAM architecture allowing concurrent DRAM operations
US5943263A (en) 1997-01-08 1999-08-24 Micron Technology, Inc. Apparatus and method for programming voltage protection in a non-volatile memory system
US5825710A (en) 1997-02-26 1998-10-20 Powerchip Semiconductor Corp. Synchronous semiconductor memory device
US5898634A (en) * 1997-06-17 1999-04-27 Micron Technology, Inc. Integrated circuit with supply voltage detector
US6141247A (en) 1997-10-24 2000-10-31 Micron Technology, Inc. Non-volatile data storage unit and method of controlling same
US6246626B1 (en) * 2000-07-28 2001-06-12 Micron Technology, Inc. Protection after brown out in a synchronous memory

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6618312B2 (en) * 2001-05-04 2003-09-09 Texas Instruments Incorporated Method and device for providing a multiple phase power on reset
KR101815136B1 (en) 2009-11-27 2018-01-05 삼성전자주식회사 Method and apparatus for protecting data of flash memory
KR20200131749A (en) * 2019-05-13 2020-11-24 윈본드 일렉트로닉스 코포레이션 Semiconductor device
KR102345226B1 (en) 2019-05-13 2021-12-29 윈본드 일렉트로닉스 코포레이션 Semiconductor device
US11169587B2 (en) * 2020-01-10 2021-11-09 Micron Technology, Inc. Feedback for power management of a memory die using a dedicated pin
US20220035432A1 (en) * 2020-01-10 2022-02-03 Micron Technology, Inc. Feedback for power management of a memory die using a dedicated pin
US11726541B2 (en) * 2020-01-10 2023-08-15 Micron Technology, Inc. Feedback for power management of a memory die using a dedicated pin

Also Published As

Publication number Publication date
US6366521B1 (en) 2002-04-02
US6246626B1 (en) 2001-06-12

Similar Documents

Publication Publication Date Title
US6246626B1 (en) Protection after brown out in a synchronous memory
US6711701B1 (en) Write and erase protection in a synchronous memory
US7010643B2 (en) Status register to improve initialization of a synchronous memory
US6459617B1 (en) Method and circuitry for bank tracking in write command sequence
US6304497B1 (en) Synchronous memory status register
US6580659B1 (en) Burst read addressing in a non-volatile memory device
US6278654B1 (en) Active terminate command in synchronous flash memory
US7409493B2 (en) Top/bottom symmetrical protection scheme for flash
US7278004B2 (en) Burst write in a non-volatile memory device
US6496444B2 (en) Elimination of precharge operation in synchronous flash memory
US6920522B2 (en) Synchronous flash memory with accessible page during write
US7073014B1 (en) Synchronous non-volatile memory system
US20070133312A1 (en) Flash with consistent latency for read operations
US7054992B2 (en) Synchronous flash memory with non-volatile mode register
US6675255B1 (en) Device initialize command for a synchronous memory
US6697907B1 (en) Hardware initialization of a synchronous memory
US20050135180A1 (en) Interface command architecture for synchronous flash memory
EP1269474B1 (en) Symmetrical protection scheme for first and last sectors of synchronous flash memory

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12

AS Assignment

Owner name: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT, CALIFORNIA

Free format text: SECURITY INTEREST;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:038669/0001

Effective date: 20160426

Owner name: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGEN

Free format text: SECURITY INTEREST;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:038669/0001

Effective date: 20160426

AS Assignment

Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT, MARYLAND

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:038954/0001

Effective date: 20160426

Owner name: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL

Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:038954/0001

Effective date: 20160426

AS Assignment

Owner name: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT, CALIFORNIA

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE REPLACE ERRONEOUSLY FILED PATENT #7358718 WITH THE CORRECT PATENT #7358178 PREVIOUSLY RECORDED ON REEL 038669 FRAME 0001. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:043079/0001

Effective date: 20160426

Owner name: U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGEN

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE REPLACE ERRONEOUSLY FILED PATENT #7358718 WITH THE CORRECT PATENT #7358178 PREVIOUSLY RECORDED ON REEL 038669 FRAME 0001. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST;ASSIGNOR:MICRON TECHNOLOGY, INC.;REEL/FRAME:043079/0001

Effective date: 20160426

AS Assignment

Owner name: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT, ILLINOIS

Free format text: SECURITY INTEREST;ASSIGNORS:MICRON TECHNOLOGY, INC.;MICRON SEMICONDUCTOR PRODUCTS, INC.;REEL/FRAME:047540/0001

Effective date: 20180703

Owner name: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT, IL

Free format text: SECURITY INTEREST;ASSIGNORS:MICRON TECHNOLOGY, INC.;MICRON SEMICONDUCTOR PRODUCTS, INC.;REEL/FRAME:047540/0001

Effective date: 20180703

AS Assignment

Owner name: MICRON TECHNOLOGY, INC., IDAHO

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:U.S. BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT;REEL/FRAME:047243/0001

Effective date: 20180629

AS Assignment

Owner name: MICRON TECHNOLOGY, INC., IDAHO

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT;REEL/FRAME:050937/0001

Effective date: 20190731

AS Assignment

Owner name: MICRON TECHNOLOGY, INC., IDAHO

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:051028/0001

Effective date: 20190731

Owner name: MICRON SEMICONDUCTOR PRODUCTS, INC., IDAHO

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT;REEL/FRAME:051028/0001

Effective date: 20190731