WO2007056651A1 - Memory with retargetable memory cell redundancy - Google Patents

Memory with retargetable memory cell redundancy Download PDF

Info

Publication number
WO2007056651A1
WO2007056651A1 PCT/US2006/060453 US2006060453W WO2007056651A1 WO 2007056651 A1 WO2007056651 A1 WO 2007056651A1 US 2006060453 W US2006060453 W US 2006060453W WO 2007056651 A1 WO2007056651 A1 WO 2007056651A1
Authority
WO
WIPO (PCT)
Prior art keywords
column
defective
cells
cell
redundant
Prior art date
Application number
PCT/US2006/060453
Other languages
French (fr)
Inventor
Kevin M. Conley
Yoram Cedar
Original Assignee
Sandisk Corporation
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 Sandisk Corporation filed Critical Sandisk Corporation
Priority to EP06839668A priority Critical patent/EP1946326A1/en
Priority to JP2008540301A priority patent/JP5297195B2/en
Publication of WO2007056651A1 publication Critical patent/WO2007056651A1/en

Links

Classifications

    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C29/00Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/70Masking faults in memories by using spares or by reconfiguring
    • G11C29/78Masking faults in memories by using spares or by reconfiguring using programmable devices
    • G11C29/80Masking faults in memories by using spares or by reconfiguring using programmable devices with improved layout
    • G11C29/81Masking faults in memories by using spares or by reconfiguring using programmable devices with improved layout using a hierarchical redundancy scheme
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C16/00Erasable programmable read-only memories
    • G11C16/02Erasable programmable read-only memories electrically programmable
    • G11C16/04Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS
    • G11C16/0483Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS comprising cells having several storage transistors connected in series
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C16/00Erasable programmable read-only memories
    • G11C16/02Erasable programmable read-only memories electrically programmable
    • G11C16/06Auxiliary circuits, e.g. for writing into memory
    • G11C16/10Programming or data input circuits
    • G11C16/14Circuits for erasing electrically, e.g. erase voltage switching circuits
    • G11C16/16Circuits for erasing electrically, e.g. erase voltage switching circuits for erasing blocks, e.g. arrays, words, groups
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C29/00Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/70Masking faults in memories by using spares or by reconfiguring
    • G11C29/78Masking faults in memories by using spares or by reconfiguring using programmable devices
    • G11C29/785Masking faults in memories by using spares or by reconfiguring using programmable devices with redundancy programming schemes
    • G11C29/787Masking faults in memories by using spares or by reconfiguring using programmable devices with redundancy programming schemes using a fuse hierarchy
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C29/00Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/70Masking faults in memories by using spares or by reconfiguring
    • G11C29/78Masking faults in memories by using spares or by reconfiguring using programmable devices
    • G11C29/80Masking faults in memories by using spares or by reconfiguring using programmable devices with improved layout
    • G11C29/808Masking faults in memories by using spares or by reconfiguring using programmable devices with improved layout using a flexible replacement scheme
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C29/00Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/70Masking faults in memories by using spares or by reconfiguring
    • G11C29/78Masking faults in memories by using spares or by reconfiguring using programmable devices
    • G11C29/80Masking faults in memories by using spares or by reconfiguring using programmable devices with improved layout
    • G11C29/816Masking faults in memories by using spares or by reconfiguring using programmable devices with improved layout for an application-specific layout
    • G11C29/82Masking faults in memories by using spares or by reconfiguring using programmable devices with improved layout for an application-specific layout for EEPROMs
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C2229/00Indexing scheme relating to checking stores for correct operation, subsequent repair or testing stores during standby or offline operation
    • G11C2229/70Indexing scheme relating to G11C29/70, for implementation aspects of redundancy repair
    • G11C2229/76Storage technology used for the repair
    • G11C2229/763E-fuses, e.g. electric fuses or antifuses, floating gate transistors

Definitions

  • This invention relates to nonvolatile memories and in particular, the use of redundant data storage units in flash memories to replace defective data storage units.
  • Non-volatile memory products are used today, particularly in the form of small form factor cards, which employ an array of flash EEPROM (Electrically Erasable and Programmable Read Only Memory) cells formed on one or more integrated circuit chips.
  • a memory controller usually but not necessarily on a separate integrated circuit chip, interfaces with a host to which the card is removably connected and controls operation of the memory array within the card.
  • Such a controller typically includes a microprocessor, some nonvolatile read-only-memory (ROM), a volatile random-access-memory (RAM) and one or more special circuits such as one that calculates an error-correction-code (ECC) from data as they pass through the controller during the programming and reading of data.
  • ECC error-correction-code
  • CF CompactFlashTM
  • MMC MultiMedia cards
  • SD Secure Digital
  • Smart Media cards Smart Media cards
  • P-Tag personnel tags
  • Memory Stick cards Some of the commercially available cards are CompactFlashTM (CF) cards, MultiMedia cards (MMC), Secure Digital (SD) cards, Smart Media cards, personnel tags (P-Tag) and Memory Stick cards.
  • Hosts include personal computers, notebook computers, personal digital assistants (PDAs), various data communication devices, digital cameras, cellular telephones, portable audio players, automobile sound systems, and similar types of equipment.
  • PDAs personal digital assistants
  • this type of memory can alternatively be embedded into various types of host systems.
  • NOR and NAND Two general memory array architectures have found commercial application, NOR and NAND.
  • memory cells are connected between adjacent bit line source and drain diffusions that extend in a column direction with control gates connected to word lines extending along rows of cells.
  • a memory cell includes at least one storage element positioned over at least a portion of the cell channel region between the source and drain.
  • a programmed level of charge on the storage elements thus controls an operating characteristic of the cells, which can then be read by applying appropriate voltages to the addressed memory cells. Examples of such cells, their uses in memory systems and methods of manufacturing them are given in United States Patent Nos. 5,070,032, 5,095,344, 5,313,421, 5,315,541, 5,343,063, 5,661,053 and 6,222,762.
  • the NAND array utilizes series strings of more than two memory cells, such as 16 or 32, connected along with one or more select transistors between individual bit lines and a reference potential to form columns of cells. Word lines extend across cells within a large number of these columns. An individual cell within a column is read and verified during programming by causing the remaining cells in the string to be turned on hard so that the current flowing through a string is dependent upon the level of charge stored in the addressed cell. Examples of NAND architecture arrays and their operation as part of a memory system arc found in United States Patent Nos. 5,570,315, 5,774,397, 6,046,935, and 6,522,580.
  • the charge storage elements of current flash EEPROM arrays are most commonly electrically conductive floating gates, typically formed from conductivcly doped polysilicon material.
  • An alternate type of memory cell useful in flash EEPROM systems utilizes a non-conductive dielectric material in place of the conductive floating gate to store charge in a nonvolatile manner.
  • a triple layer dielectric formed of silicon oxide, silicon nitride and silicon oxide (ONO) is sandwiched between a conductive control gate and a surface of a semi -conductive substrate above the memory cell channel.
  • the cell is programmed by injecting electrons from the cell channel into the nitride, where they are trapped and stored in a limited region, and erased by injecting hot holes into the nitride.
  • flash EEPROM memory arrays As in most integrated circuit applications, the pressure to shrink the silicon substrate area required to implement some integrated circuit functions also exists with flash EEPROM memory arrays. It is continually desired to increase the amount of digital data that can be stored in a given area of a silicon substrate, in order to increase the storage capacity of a given size memory card and other types of packages, or to both increase capacity and decrease size.
  • One way to increase the storage density of data is to store more than one bit of data per memory cell and/or per storage unit or element. This is accomplished by dividing a window of a storage element charge level voltage range into more than two states. The use of four such states allows each cell to store two bits of data, eight states stores three bits of data per storage element, and so on.
  • Memory cells of a typical flash EEPROM array are divided into discrete blocks of cells that arc erased together. That is, the block is the erase unit, a minimum number of cells that are simultaneously erasable.
  • Each block typically stores one or more pages of data, the page being the minimum unit of programming and reading, although more than one page may be programmed or read in parallel in different sub- arrays or planes.
  • Each page typically stores one or more sectors of data, the size of the sector being defined by the host system.
  • An example sector includes 512 bytes of user data, following a standard established with magnetic disk drives, plus some number of bytes of overhead information about the user data and/or the block in which they are stored.
  • Such memories are typically configured with many pages in each block, and each page storing multiple host sectors of data.
  • the array is typically divided into sub-arrays, commonly referred to as planes, which contain their own data registers and other circuits to allow parallel operation such that sectors of data may be programmed to or read from each of several or all the planes simultaneously.
  • An array on a single integrated circuit may be physically divided into planes, or each plane may be formed from a separate one or more integrated circuit chips. Examples of such a memory implementation are described in United States Patent Nos. 5,798,968 and 5,890,192.
  • blocks may be linked together to form virtual blocks or metablocks. That is, each metablock is defined to include one block from each plane.
  • the metablock is identified by a host logical block address as a destination for programming and reading data. Similarly, all blocks of a metablock are erased together.
  • the controller in a memory system operated with such large blocks and/or metablocks performs a number of functions including the translation between logical block addresses (LBAs) received from a host, and physical block numbers (PBNs) within the memory array. Individual pages within the blocks are typically identified by offsets within the block address. Address translation often involves use of intermediate terms of a logical block number (LBN) and logical page.
  • LBAs logical block addresses
  • PBNs physical block numbers
  • the physical memory cells arc also grouped into two or more zones.
  • a zone may be any partitioned subset of the physical memory or memory system into which a specified range of logical block addresses is mapped.
  • a memory system capable of storing 64 Megabytes of data may be partitioned into four zones that store 16 Megabytes of data per zone.
  • the range of logical block addresses is then also divided into four groups, one group being assigned to the physical blocks of each of the four zones.
  • Logical block addresses are constrained, in a typical implementation, such that the data of each are never written outside of a single physical zone into which the logical block addresses are mapped.
  • each, zone preferably includes blocks from multiple planes, typically the same number of blocks from each of the planes. Zones are primarily used to simplify address management such as logical to physical translation, resulting in smaller translation tables, less RAM memory needed to hold these tables, and faster access times to address the currently active region of memory, but because of their restrictive nature can result in less than optimum, wear leveling.
  • Individual flash EEPROM cells store an amount of charge in a charge storage element or unit that is representative of one or more bits of data.
  • the charge level of a storage element controls the threshold voltage (commonly referenced as VT) of its memory cell, which is used as a basis of reading the storage state of the cell.
  • VT threshold voltage
  • a threshold voltage window is commonly divided into a number of ranges, one for each of the two or more storage states of the memory cell. In this way, a cell can hold one bit of data or can hold two or more bits of data depending on the number of voltage ranges. These ranges are separated by guardbands that include a nominal sensing level that allows determining the storage states of the individual cells.
  • Error correcting codes are therefore typically calculated by the controller and stored along with the host data being programmed and used during reading to verify the data and perform some level of data correction if necessary. Also, shifting charge levels can be restored back to the centers of their state ranges from, time-to-time, before disturbing operations cause them to shift completely out of their defined ranges and thus cause erroneous data to be read. This process, termed data refresh or scrub, is described in United States Patent Nos. 5,532,962 and 5,909,449, which patents are hereby incorporated by reference in their entirety.
  • Memory cells in a memory array may sometimes be defective.
  • Cells may be defective in a new memory chip because of a manufacturing defect or may become defective during use of the chip. Where a cell become defective during use, the defect may be detected by failure to erase, write to or read from, the cell.
  • One way to deal with such defects is to store data that would be stored in a defective portion of the memory at another location. Such remapping of data from a defective location to a replacement location is described in U.S. Patent ]Slo. 5,535,328, entitled “Non-volatile memory system card with flash erasable sectors of EEPROM cells including a mechanism for substituting defective cells," which patent is hereby incorporated by reference in its entirety.
  • the defective cell may be remapped to a different location or an entire sector may be remapped to another location.
  • Another scheme for relocating data away from defective cells is described in U.S. Patent No. 5,200,959, entitled “Device and method for defect handling in semi-conductor memory,” which patent is hereby incorporated by reference in its entirety. The data of an entire block may also be relocated in this way when a defective cell is found in one block of the memory array.
  • Yet another scheme for managing defective cells is described in U.S. Patent No. 5,438,573, entitled “Flash EEPROM array data and header file structure,” which patent is hereby incorporated by reference in its entirety. This scheme relocates a bit of data corresponding to a defective memory cell to the next cell in the row. The bit corresponding to the next cell is relocated to its neighbor and so on, so that the bits in the row are pushed over by one bit. Redundant bits are provided in each row so that the data still fits in the row.
  • Defective cells may be detected in several ways either during a testing procedure, typically done at the factory prior to use of the memory chip by a user, or during normal use where defects are generally found by the memory controller.
  • Factory testing generally finds physical defects resulting from manufacturing. Such testing uses dedicated test equipment that is connected to the memory system for testing but is disconnected after testing is complete. The defective area is remapped in a permanent manner. Defects may be found by attempting to program, read and erase portions of the memory array to see if any cells fail to perform within specified limits.
  • Latent defects may also be detected as described in U.S. Patent No. 5,428,621, entitled “Latent defect handling in EEPROM devices," which patent is hereby incorporated by reference in its entirety.
  • redundant columns of cells are provided to replace defective columns in the memory array. Such redundant columns do not store any data if there are no defects in the memory array.
  • Figure 1 shows an example of the use of redundant columns according to the prior art. During testing of a memory array, it is found that a memory cell is defective. The defect may be the result of contamination, misprocessing or some other cause. When defective cell 101 is encountered in column 1, column 1 is considered defective and is mapped to redundant column A. This mapping is recorded in some way so that column 1 is not used. Typically, the mapping is recorded by burning fuses that indicate the column that is defective. Any data that would have been sent to column 1 if it were not for the remapping is now sent to redundant column A.
  • FIG. 1 shows a simplified illustration of a memory system 200 for carrying out column replacement illustrated in Figure 1.
  • a flash fuse is burned to indicate the location of a defective column.
  • a flash fuse is a flash cell or group of cells that is treated as a fuse, but unlike conventional fuses may be reprogrammable. There may be one fuse for each non-redundant column of flash memory cell array 221.
  • flash fuses 220 are read into column redundancy control registers 222 so that the location of the defective column and its replacement are indicated by the contents of the registers.
  • column redundancy control registers 222 provide a replacement column address to Y-address decode circuitry 224 so that the defective column is not accessed. More than one defective column may be replaced in this way. Typically, a number of replacement columns 226 are provided so that a number of columns may be replaced.
  • Figure 1 shows N+l non-redundant columns (columns 0 to N) and four redundant columns (columns A to D). Word lines extend across the array at right angles to the columns, extending over both redundant and non-redundant columns.
  • a defective cell is not always a completely unusable cell, it may simply operate outside specified performance limits. For example, a cell that is not programmed after a certain number of voltage pulses may be considered defective even though it is capable of programming if additional pulses are provided.
  • the performance limits that are chosen determine the number of defective cells that are found. By setting high performance limits, overall performance may be improved (e.g. program time may be reduced) but the number of defects will increase. Setting low performance limits reduces the number of defects at the expense of performance.
  • mapping defective cells there is a need for a more space efficient way of mapping defective cells.
  • memory systems that include circuitry for more efficiently carrying out such mapping.
  • a retargetable memory cell redundancy scheme allows individual mapping of defective cells to redundant cells in a redundant column instead of mapping entire columns to redundant columns when they contain defective cells. Defective cells in multiple columns may be mapped to the same redundant column in this way. An entire column is not necessarily considered defective just because one or more cells in the column arc defective. This allows much more efficient use of the space available in the redundant column.
  • Defect mapping data records the locations of defective columns or cells in the memory array and is generated and stored during initial test and configuration. Defect mapping data may be stored in a portion of the flash memory or in a dedicated memory.
  • Both individual cell replacement and column replacement may be implemented in the same memory system at the same time. Generally, the column replacement is done first for any column in which all the memory cells are defective or more than a threshold number are defective. Subsequently, individual cells in remaining non-redundant columns may be mapped to redundant columns that were not needed for replacement of entire columns. Cells may also be replaced in intermediate sized groups of more than one cell, but less than an entire column. One example of such an intermediate sized group is the group formed by the memory cells in a NAND string that arc connected together in pivots
  • a cell replacement scheme may be implemented using circuits that are located adjacent to the memory array and are on the same chip as the memory array. Such circuits are similar to certain circuits of the prior art but contain additional circuitry to allow comparison of row addresses to the row addresses of defective cells that have been remapped.
  • a cell replacement scheme may be implemented using the memory controller to compare addresses to be accessed with the addresses from the defect mapping data. Such a scheme may be implemented without hardware changes and requires only a change to the memory controller firmware.
  • Flash memories are block erasable so that cells are not erased individually, but in units of a block. Blocks generally extend across multiple columns. A block may extend across both redundant columns and non-redundant columns and defective cells within the block are mapped to redundant cells in the same block. Thus, the redundant cells and non-redundant cells containing logically sequential data are erased together.
  • Figure 1 shows a column replacement scheme of the prior art.
  • Figure 2 shows a prior art memory array and peripheral circuitry for carrying out the column replacement scheme of Figure 1.
  • Figure 3 shows a memory system supporting aspects of the present invention.
  • Figure 4 illustrates the block structure of the memory array of the memory system of Figure 3.
  • Figure 5A shows the structure of a block 100 of Figure 4 having multiple NAND strings connected by word lines and bit lines.
  • Figure 5B shows a more detailed view of a NAND string of Figure 5 A.
  • Figure 6 shows an example of redundant cell and redundant column remapping according to an embodiment of the present invention.
  • Figure 7 shows a flowchart for a test and configuration operation to carry out a redundant cell and redundant column-remapping scheme such as that shown in Figure 6.
  • Figure 8 shows a block diagram of circuitry used to carry out a redundant cell and redundant column-remapping scheme such as that of Figure 6.
  • Figure 9 shows a block diagram of an alternative hardware used to carry out a redundant cell and redundant column remapping scheme such as that of Figure 6.
  • FIG. 3 shows a memory system 330 that includes aspects of the present invention.
  • Memory system 330 is connected to a host (not shown) and is in communication with the host. Typically, this communication between host and memory system takes place through a standard interface.
  • a memory system such as memory system 330 is part of a removable memory card that has a standard interface so that it can be connected to a variety of hosts according to standards such as those previously listed.
  • a memory system such as memory system 330 may be embedded in a host system so that it is permanently connected to the host system.
  • Memory system 330 includes a controller 20 that controls operation of memory array 1 in response to commands received from the host.
  • Controller 20 may contain a microprocessor, RAM, flash, buffers, registers, Error Correction Code (ECC) circuits and other circuits to manage memory system 330.
  • Data received from the host is stored in memory array 1 under the direction of controller 20 when a host write command is received. For example, the physical locations at which such data are written are generally determined by the controller.
  • Controller 20 operates according to firmware that may be loaded into controller 20 during initial configuration. Data is read from memory array 1 under the direction of controller 20 when a read command is received from the host.
  • controller 20 maintains a record of logical-to-physical mapping of host data so that when data are identified by the host by a logical address, the data may be accessed in the correct physical address in memory array 1.
  • Controller 20 communicates with memory array 1 through peripheral circuits between controller 20 and memory array 1.
  • Peripheral circuits include row control circuits 3, column control circuits 2, data input/output circuits 6, a state machine 8 and command circuits 7. Additional peripheral circuits may also be used, but are not shown in Figure 3 for clarity.
  • state machine 8 When a particular command is sent from controller 20 to command circuits 7, state machine 8 is configured to execute the command by issuing the appropriate signals to row control circuits 3 and column control circuits 2. When state machine 8 completes an operation, it returns a signal to command circuits 7, which in turn indicate to controller 20 that the operation is complete.
  • Controller 20, memory array 1 and peripheral circuits may all be formed together on a single chip. Alternatively, the memory array and peripheral circuits are formed on one chip and the controller is formed on another chip as shown by the broken line dividing memory system 330 between controller chip 21 and memory array chip 22.
  • Memory array 1 is made up of erasable units of blocks. Programming of charge storage memory devices can only result in adding more charge to its charge storage elements. Therefore, prior to a program operation, existing charge in a charge storage element must be removed (or erased). Erase circuits (not shown) are provided to erase one or more blocks of memory cells.
  • a non-volatile memory such as EEPROM is referred to as a "Flash" EEPROM when an entire array of cells, or significant groups of cells of the array, is electrically erased together (i.e., in a flash). Once erased, the group of cells can then be reprogrammed. The group of cells erasable together may consist one or more addressable erase unit.
  • the erase unit or block typically stores one or more pages of data, the page being the unit of programming and reading, although more than one page may be programmed or read in a single operation.
  • Each page typically stores one or more sectors of data, the size of the sector being defined by the host system.
  • An example is a sector of 512 bytes of user data, following a standard established with magnetic disk drives, plus some number of bytes of overhead information about the user data and/or the block in with it is stored.
  • Figure 4 shows the structure of memory array 1 comprising multiple blocks, a block being the minimum unit of erase.
  • the memory array has 1024 blocks (blocks 0 to 1023), including block 100, which is described in more detail below.
  • Blocks may also be linked to form metablocks that are erased together and so are treated as a single large block.
  • blocks may be arranged in planes, where a plane is a group of blocks that share certain read/write circuits.
  • FIG. 5 A and 5B show an example of the structure of the NAND memory array 1 that uses aspects of the present invention.
  • Block 100 is comprised of multiple NAND strings 5Oa 5 50b...50c with each string having multiple floating gate cells in series. Additional strings that are not shown in Figure 5 A are located between string 50b and 50c.
  • Figure 5A shows how strings 50a, 50b...5Oc are linked together to form a portion of an array (block 100).
  • Bit lines 51a, 5 Ib...5Ic run vertically and have multiple strings connected to them.
  • the NAND strings connected to a single bit line form a column.
  • strings 50a, 50d...5Ox connected to bit line 51a form column 55a
  • a block such as block 100, may extend across multiple columns as shown. Columns may extend in the vertical direction through multiple blocks. Redundant columns are columns that do not normally contain data unless there are defects. Non-redundant columns normally contain data when the portion of the memory where they are located is not erased. Data stored in a memory array may be host data, ECC data, some form of header data, control data stored by the controller or some other data. In the horizontal direction, word lines extend across the block. Source lines also extend across the block and connect to ends of the NAND strings.
  • Block 100 is made up of NAND strings 50a, 50b... 50c, connected by word lines. The cells of block 100 are erased together and are not separately erasable.
  • Figure 5B illustrates schematically string 50a of memory cells organized into a NAND string.
  • a pair of select transistors Sl, S2 controls the connection of string 50a to the remainder of the memory array via the NAJSID string's source terminal 54 and drain terminal 56.
  • each memory transistor in the chain has a charge storage clement to store a given amount of charge so as to represent an intended memory state.
  • a control gate of each memory transistor provides control over read and write operations.
  • a control gate of each of the select transistors Sl, S2 provides control access to the NAND cell via its source terminal 54 and drain terminal 56 respectively.
  • Block 100 extends across both redundant and non-redundant columns of the memory array. Defective cells within block 100 can be mapped to redundant cells that are also within block 100.
  • Figure 6 shows redundant column mapping according to an embodiment of the present invention.
  • redundant column B of Figure 6 contains data mapped from more than one non-redundant column (columns 2 and 3) of memory array 600.
  • a first defective cell 602 in column 2 is mapped to a redundant cell 604 in redundant column B.
  • a second defective cell 606 in column 3 is mapped to another redundant cell 608 in redundant column B.
  • one redundant column (column B) is used for storing data from two different non-redundant columns (column 2 and column 3) in memory array 600.
  • one redundant column can be used to repair multiple defects in the memory array. This is much more efficient than prior art schemes that used an entire redundant column for each defect in the memory array.
  • cells are mapped on a row-by-row basis, instead of mapping all the cells of a column when a defect is found in the column.
  • only defective cells 602, 606 may be mapped to redundant column B.
  • Other cells in columns 2 and 3 that are not defective are not mapped to redundant column B.
  • Defective cells are mapped to the cell in a redundant column that is in the same row. This means that the defective cell and the redundant cell that replaces it share a word line. In this scheme, only one defective cell along a word line can be mapped to a redundant column. However, where more than one redundant column is available, each, defect along a row may be mapped to a different redundant column, so the number of tolerable defects in a row can be as many as the number of redundant columns available.
  • Figure 6 shows a defective cell 610 in column 1. Defective cell 610 and defective cell 602 in column 2 are both in row 612. Because cell 604 in redundant column B is used for the data from cell 602, defective cell 610 is mapped to redundant cell 614 in redundant column C.
  • the redundant column mapping scheme of Figure 6 may be carried out in a memory array having a NAND structure such as that shown in Figure 5A and 5B or having a NOR structure or having another structure.
  • redundant columns that have data mapped from multiple columns
  • additional redundant columns that operate in the conventional manner. These columns replace entire non-redundant columns so that every cell of the non-redundant column is replaced by a cell of the redundant column. This may be done when the non-redundant column is considered defective. This could be because all the cells in the column are defective (unreadable) or because more than a threshold number of cells in the column are defective.
  • Figure 6 shows defective, non-redundant column 0 mapped to redundant column A, which becomes a replacement column.
  • Mapping defective cells to redundant cells may either be done as part of an initial test and configuration operation or may be done at a later time after user data has already been stored in the memory system.
  • redundant columns are only used for remapping during the initial test and configuration operation that is typically performed at the factory before the memory system is sold or used. Defects that occur later, or are discovered later, may be dealt with in other ways. Remapping during initial test and configuration is permanent and so the remapping is recorded in an irreversible manner such as by using fLLSes.
  • Figure 7 shows a flowchart of an initial test and configuration operation on a memory array according to an embodiment of the present invention.
  • This test and configuration shown may be carried out using test equipment that is connected to the memory array after it is manufactured but before it is used with a host.
  • the memory array is generally tested in isolation from the controller and other circuits. Card level testing may also be performed but generally docs not indicate defects in the memory array.
  • a test is done to determine if there are defective cells in the memory array 720. This may be done by programming test data to the memory array and then reading it back. If data cannot be programmed within a predetermined time, then a cell may be considered to be defective. If the data read back from a cell is not the same as that written to it, the cell may be considered defective.
  • Tf a cell does not reach the erased state within, a predetermined time during an erase operation, the cell may also be considered defective. Alternatively, leakage current may be measured to identify defective cells, or some other means of identifying defective cells may be used.
  • the entire memory array may be tested for defective cells to determine the locations of all defective cells in the memory array. Next, it is determined if any column of the memory array has more than a threshold number of defective cells 722. If a column has more than, the threshold number of defective cells, then the entire column is replaced by a redundant column 724. This is similar to the column replacement of the prior art. In one example, the threshold number is equal to the number of cells in the column. In this case, an entire column, is replaced only if all cells in the column are defective.
  • Tf fewer than all cells in the column are defective, then they are individually replaced.
  • individual defective cells are mapped to redundant cells in one or more defective columns 726.
  • One redundant column may contain data mapped from multiple non-redundant columns in this way.
  • the mapping of defective cells to redundant cells is recorded in a permanent manner 728 so that the information remains with the memory array for future use.
  • One way to permanently record such defect mapping data is to use fuses or antifuses indicating the locations of the defective memory cells and their replacements.
  • Another way to permanently record the defect mapping data is to store it in a portion of the nonvolatile memory that is dedicated to storage of such data and is configured so that it is not later erased. This may be done through hardware or software. Other methods of permanently storing defect mapping data may also be used.
  • FIG. 8 shows an example of a memory system 841, including flash memory cell array 843, that includes aspects of the present invention.
  • Flash fuses 840 are present as in certain prior art systems (laser fuses or some equivalent structure may also be used).
  • the defect mapping data stored in flash fuses 840 is first loaded into row redundancy control registers 842.
  • Row redundancy control registers 842 have an input from a row address register 844. This input allows the row address of the next row that is to be read to be transferred to row redundancy control registers 842.
  • the row address is compared with the row addresses in the row redundancy control registers 842 (loaded from flash fuses) to determine if there are any defects in the row.
  • row address is not the same as a row address in row redundancy control register 842, then there is no defective cell in the addressed row and the row may be accessed using the default column addresses without accessing redundant columns 844. If the row address from row address register 844 matches a row address in row redundancy control registers 842, then this is signaled to column redundancy control registers 846 which determines the redundant column to be accessed instead of the non-redundant column that contains the defect in the addressed row.
  • the column addresses provided to Y-addrcss decode circuits 848 for this row indicate the redundant column and not the non-redundant column that contains the defective cell.
  • the hardware needed to carry out the replacement scheme described may be included in peripheral circuits that are formed on the same chip as the memory array.
  • Examples of hardware used to carry out column redundancy schemes are provided in U.S. Patent No. 6,560,146 and U.S. Patent Publication No 2005/0141387A1, entitled “Flexible and area efficient column redundancy for flash memories,” which are hereby incorporated by reference in their entirety.
  • the circuits shown in Patent Application Publication No. 2005/0141387A1 may be adapted to carry out a retargetable memory cell redundancy scheme such as that of memory system 841 by adding circuitry that receives a row address and compares the row address to stored addresses of rows having cells that are remapped.
  • FIG. 9 shows another example of a memory system 960 according to the present invention.
  • An external memory system controller 962 is shown connected to a flash memory device 964. This is similar to the example shown in Figure 3.
  • external memory system controller 962 is connected to flash memory device 964 by an external flash memory bus 966.
  • external memory system controller 962 and flash memory device 964 are formed on separate chips.
  • External memory system controller 962 includes a Central Processing Unit (CPU) or microprocessor 968 and a controller memory 970, which may be a Random Access Memory (RAM).
  • Defect mapping data may be loaded into controller memory 970 when external memory system controller 962 is turned on.
  • a nonvolatile RAM may be used to keep the defect mapping data.
  • controller memory 970 is loaded with the defect mapping data from flash fuses 970.
  • the defect mapping data may be stored in any other suitable location.
  • External memory system controller 962 compares the locations of defects with the physical addresses of the data that is being accessed. When a match occurs between both the row and column addresses of data being accessed and a defect location, external memory system controller 962 sends an access command to flash memory device 964 indicating one of redundant columns 972 instead of the column with the defective cell. State machine 974 then causes column redundancy control registers 976 to indicate the redundant column to Y-address decode circuits 978 in place of the column with the defective cell.
  • a bit (or bits) of data for a defective cell is relocated to a redundant cell that is in the same row (connected to the same word line).
  • a block extends along one or more word lines. Thus, the cells of a row, or of a group of rows are erased together.
  • a block extends to include non-redundant and redundant cells connected by a word line. Any defective cells in the block are remapped to redundant cells within the same block. Thus, when the non-redundant cells are erased, the data that was remapped from the non-redundant cells to redundant cells in redundant columns is also erased. This means that no separate data management structures are required for tracking when data in redundant cells becomes obsolete. Because both non-redundant and redundant cells are erased together, they are both returned to the erased state and are ready to receive new data without any separate operation.

Abstract

In a memory array having redundant columns, a scheme allows defective cells to be individually remapped to redundant cells in a redundant column. Redundant cells in one redundant column replace defective cells in multiple non-redundant columns. Remapping is done as part of initial test and configuration. Specific hardware can be used for the scheme or firmware in the memory controller can implement the scheme.

Description

MEMORY WITH RETARGETABLE MEMORY CELL REDUNDANCY
BACKGROUND
10001] This invention relates to nonvolatile memories and in particular, the use of redundant data storage units in flash memories to replace defective data storage units.
[0002] There are many commercially successful non-volatile memory products being used today, particularly in the form of small form factor cards, which employ an array of flash EEPROM (Electrically Erasable and Programmable Read Only Memory) cells formed on one or more integrated circuit chips. A memory controller, usually but not necessarily on a separate integrated circuit chip, interfaces with a host to which the card is removably connected and controls operation of the memory array within the card. Such a controller typically includes a microprocessor, some nonvolatile read-only-memory (ROM), a volatile random-access-memory (RAM) and one or more special circuits such as one that calculates an error-correction-code (ECC) from data as they pass through the controller during the programming and reading of data. Some of the commercially available cards are CompactFlash™ (CF) cards, MultiMedia cards (MMC), Secure Digital (SD) cards, Smart Media cards, personnel tags (P-Tag) and Memory Stick cards. Hosts include personal computers, notebook computers, personal digital assistants (PDAs), various data communication devices, digital cameras, cellular telephones, portable audio players, automobile sound systems, and similar types of equipment. Besides the memory card implementation, this type of memory can alternatively be embedded into various types of host systems.
[0003] Two general memory array architectures have found commercial application, NOR and NAND. In a typical NOR array, memory cells are connected between adjacent bit line source and drain diffusions that extend in a column direction with control gates connected to word lines extending along rows of cells. A memory cell includes at least one storage element positioned over at least a portion of the cell channel region between the source and drain. A programmed level of charge on the storage elements thus controls an operating characteristic of the cells, which can then be read by applying appropriate voltages to the addressed memory cells. Examples of such cells, their uses in memory systems and methods of manufacturing them are given in United States Patent Nos. 5,070,032, 5,095,344, 5,313,421, 5,315,541, 5,343,063, 5,661,053 and 6,222,762. These patents, along with all other patents, patent applications and other publications cited in this application are hereby incorporated by reference in their entirety.
[0004] The NAND array utilizes series strings of more than two memory cells, such as 16 or 32, connected along with one or more select transistors between individual bit lines and a reference potential to form columns of cells. Word lines extend across cells within a large number of these columns. An individual cell within a column is read and verified during programming by causing the remaining cells in the string to be turned on hard so that the current flowing through a string is dependent upon the level of charge stored in the addressed cell. Examples of NAND architecture arrays and their operation as part of a memory system arc found in United States Patent Nos. 5,570,315, 5,774,397, 6,046,935, and 6,522,580.
[0005] The charge storage elements of current flash EEPROM arrays, as discussed in the foregoing referenced patents, are most commonly electrically conductive floating gates, typically formed from conductivcly doped polysilicon material. An alternate type of memory cell useful in flash EEPROM systems utilizes a non-conductive dielectric material in place of the conductive floating gate to store charge in a nonvolatile manner. A triple layer dielectric formed of silicon oxide, silicon nitride and silicon oxide (ONO) is sandwiched between a conductive control gate and a surface of a semi -conductive substrate above the memory cell channel. The cell is programmed by injecting electrons from the cell channel into the nitride, where they are trapped and stored in a limited region, and erased by injecting hot holes into the nitride. Several specific cell structures and arrays employing dielectric storage elements and are described in United States Patent Application Publication No. 2003/0109093 of Harari et al.
[0006] As in most integrated circuit applications, the pressure to shrink the silicon substrate area required to implement some integrated circuit functions also exists with flash EEPROM memory arrays. It is continually desired to increase the amount of digital data that can be stored in a given area of a silicon substrate, in order to increase the storage capacity of a given size memory card and other types of packages, or to both increase capacity and decrease size. One way to increase the storage density of data is to store more than one bit of data per memory cell and/or per storage unit or element. This is accomplished by dividing a window of a storage element charge level voltage range into more than two states. The use of four such states allows each cell to store two bits of data, eight states stores three bits of data per storage element, and so on. Multiple state flash EEPROM structures using floating gates and their operation are described in United States Patent Nos. 5,043,940 and 5,172,338, and for structures using dielectric floating gates in aforementioned United States Patent Application Publication No. 2003/0109093. Selected portions of a multi-state memory array may also be operated in two states (binary) for various reasons, in a manner described in United States Patent Nos. 5,930,167 and 6,456,528.
[0007] Memory cells of a typical flash EEPROM array are divided into discrete blocks of cells that arc erased together. That is, the block is the erase unit, a minimum number of cells that are simultaneously erasable. Each block typically stores one or more pages of data, the page being the minimum unit of programming and reading, although more than one page may be programmed or read in parallel in different sub- arrays or planes. Each page typically stores one or more sectors of data, the size of the sector being defined by the host system. An example sector includes 512 bytes of user data, following a standard established with magnetic disk drives, plus some number of bytes of overhead information about the user data and/or the block in which they are stored. Such memories are typically configured with many pages in each block, and each page storing multiple host sectors of data.
[0008] In order to increase the degree of parallelism during programming user data into the memory array and read user data from it, the array is typically divided into sub-arrays, commonly referred to as planes, which contain their own data registers and other circuits to allow parallel operation such that sectors of data may be programmed to or read from each of several or all the planes simultaneously. An array on a single integrated circuit may be physically divided into planes, or each plane may be formed from a separate one or more integrated circuit chips. Examples of such a memory implementation are described in United States Patent Nos. 5,798,968 and 5,890,192. [0009] To further efficiently manage the memory, blocks may be linked together to form virtual blocks or metablocks. That is, each metablock is defined to include one block from each plane. Use of the metablock is described in U.S. Patent No. 6,763,424 which patent is hereby incorporated by reference in its entirety. The metablock is identified by a host logical block address as a destination for programming and reading data. Similarly, all blocks of a metablock are erased together. The controller in a memory system operated with such large blocks and/or metablocks performs a number of functions including the translation between logical block addresses (LBAs) received from a host, and physical block numbers (PBNs) within the memory array. Individual pages within the blocks are typically identified by offsets within the block address. Address translation often involves use of intermediate terms of a logical block number (LBN) and logical page.
[0010] In some memory systems, the physical memory cells arc also grouped into two or more zones. A zone may be any partitioned subset of the physical memory or memory system into which a specified range of logical block addresses is mapped. For example, a memory system capable of storing 64 Megabytes of data may be partitioned into four zones that store 16 Megabytes of data per zone. The range of logical block addresses is then also divided into four groups, one group being assigned to the physical blocks of each of the four zones. Logical block addresses are constrained, in a typical implementation, such that the data of each are never written outside of a single physical zone into which the logical block addresses are mapped. In a memory array divided into planes (sub-arrays), which each have their own addressing, programming and reading circuits, each, zone preferably includes blocks from multiple planes, typically the same number of blocks from each of the planes. Zones are primarily used to simplify address management such as logical to physical translation, resulting in smaller translation tables, less RAM memory needed to hold these tables, and faster access times to address the currently active region of memory, but because of their restrictive nature can result in less than optimum, wear leveling.
[0011] Individual flash EEPROM cells store an amount of charge in a charge storage element or unit that is representative of one or more bits of data. The charge level of a storage element controls the threshold voltage (commonly referenced as VT) of its memory cell, which is used as a basis of reading the storage state of the cell. A threshold voltage window is commonly divided into a number of ranges, one for each of the two or more storage states of the memory cell. In this way, a cell can hold one bit of data or can hold two or more bits of data depending on the number of voltage ranges. These ranges are separated by guardbands that include a nominal sensing level that allows determining the storage states of the individual cells. These storage levels often shift as a result of charge disturbing programming, reading or erasing operations performed in neighboring or other related memory cells, pages or blocks. Error correcting codes (ECCs) are therefore typically calculated by the controller and stored along with the host data being programmed and used during reading to verify the data and perform some level of data correction if necessary. Also, shifting charge levels can be restored back to the centers of their state ranges from, time-to-time, before disturbing operations cause them to shift completely out of their defined ranges and thus cause erroneous data to be read. This process, termed data refresh or scrub, is described in United States Patent Nos. 5,532,962 and 5,909,449, which patents are hereby incorporated by reference in their entirety.
[0012] Memory cells in a memory array may sometimes be defective. Cells may be defective in a new memory chip because of a manufacturing defect or may become defective during use of the chip. Where a cell become defective during use, the defect may be detected by failure to erase, write to or read from, the cell. One way to deal with such defects is to store data that would be stored in a defective portion of the memory at another location. Such remapping of data from a defective location to a replacement location is described in U.S. Patent ]Slo. 5,535,328, entitled "Non-volatile memory system card with flash erasable sectors of EEPROM cells including a mechanism for substituting defective cells," which patent is hereby incorporated by reference in its entirety. The defective cell may be remapped to a different location or an entire sector may be remapped to another location. Another scheme for relocating data away from defective cells is described in U.S. Patent No. 5,200,959, entitled "Device and method for defect handling in semi-conductor memory," which patent is hereby incorporated by reference in its entirety. The data of an entire block may also be relocated in this way when a defective cell is found in one block of the memory array. [0013] Yet another scheme for managing defective cells is described in U.S. Patent No. 5,438,573, entitled "Flash EEPROM array data and header file structure," which patent is hereby incorporated by reference in its entirety. This scheme relocates a bit of data corresponding to a defective memory cell to the next cell in the row. The bit corresponding to the next cell is relocated to its neighbor and so on, so that the bits in the row are pushed over by one bit. Redundant bits are provided in each row so that the data still fits in the row.
[0014] Defective cells may be detected in several ways either during a testing procedure, typically done at the factory prior to use of the memory chip by a user, or during normal use where defects are generally found by the memory controller. Factory testing generally finds physical defects resulting from manufacturing. Such testing uses dedicated test equipment that is connected to the memory system for testing but is disconnected after testing is complete. The defective area is remapped in a permanent manner. Defects may be found by attempting to program, read and erase portions of the memory array to see if any cells fail to perform within specified limits. Latent defects may also be detected as described in U.S. Patent No. 5,428,621, entitled "Latent defect handling in EEPROM devices," which patent is hereby incorporated by reference in its entirety.
[0015] In some prior art designs, redundant columns of cells are provided to replace defective columns in the memory array. Such redundant columns do not store any data if there are no defects in the memory array. Figure 1 shows an example of the use of redundant columns according to the prior art. During testing of a memory array, it is found that a memory cell is defective. The defect may be the result of contamination, misprocessing or some other cause. When defective cell 101 is encountered in column 1, column 1 is considered defective and is mapped to redundant column A. This mapping is recorded in some way so that column 1 is not used. Typically, the mapping is recorded by burning fuses that indicate the column that is defective. Any data that would have been sent to column 1 if it were not for the remapping is now sent to redundant column A. Defective cell 101 is replaced by replacement cell 103. In addition, all the other cells of column 1, which are not defective, are also replaced by cells in redundant column A. [0016] Figure 2 shows a simplified illustration of a memory system 200 for carrying out column replacement illustrated in Figure 1. During testing, a flash fuse is burned to indicate the location of a defective column. A flash fuse is a flash cell or group of cells that is treated as a fuse, but unlike conventional fuses may be reprogrammable. There may be one fuse for each non-redundant column of flash memory cell array 221. When memory system 200 starts up, flash fuses 220 are read into column redundancy control registers 222 so that the location of the defective column and its replacement are indicated by the contents of the registers. When the host sends a memory access command, the physical address to be accessed is compared with the column addresses in column redundancy control registers 222. If a defective column is indicated, then instead of trying to access the defective column, the replacement column is accessed. Thus, column redundancy control registers 222 provide a replacement column address to Y-address decode circuitry 224 so that the defective column is not accessed. More than one defective column may be replaced in this way. Typically, a number of replacement columns 226 are provided so that a number of columns may be replaced. Figure 1 shows N+l non-redundant columns (columns 0 to N) and four redundant columns (columns A to D). Word lines extend across the array at right angles to the columns, extending over both redundant and non-redundant columns.
[00171 A defective cell is not always a completely unusable cell, it may simply operate outside specified performance limits. For example, a cell that is not programmed after a certain number of voltage pulses may be considered defective even though it is capable of programming if additional pulses are provided. The performance limits that are chosen determine the number of defective cells that are found. By setting high performance limits, overall performance may be improved (e.g. program time may be reduced) but the number of defects will increase. Setting low performance limits reduces the number of defects at the expense of performance.
[0018] While the prior art column replacement scheme of Figures 1 and 2 described above allows a memory array to be operated with, one or more defective cells, it has several drawbacks. This scheme requires as many redundant columns as there are non-redundant columns with defective cells, generally one redundant column per defect. Redundant columns occupy valuable space on a chip and add to the cost of producing a chip. The more redundant columns are provided, the greater the cost. However, if too few redundant columns are provided, there may not be enough redundant columns to repair some chips so that the chip is unusable. Thus, yield may suffer if too few redundant columns are provided. Newer memory arrays have more memory cells and smaller feature sizes, which tend to increase the number of defects in a memory array. Also, as more cells are programmed together in large pages, programming time tends to be limited by a few slow cells if they are not replaced. Thus, replacement of defective cells is important for newer memory systems.
[0019] Therefore, there is a need for a more space efficient way of mapping defective cells. There is also a need for memory systems that include circuitry for more efficiently carrying out such mapping.
SUMMARY
[0020] A retargetable memory cell redundancy scheme allows individual mapping of defective cells to redundant cells in a redundant column instead of mapping entire columns to redundant columns when they contain defective cells. Defective cells in multiple columns may be mapped to the same redundant column in this way. An entire column is not necessarily considered defective just because one or more cells in the column arc defective. This allows much more efficient use of the space available in the redundant column.
[0021] Detecting defective cells and mapping them to redundant cells in redundant columns takes place as part of an initial test and configuration operation before a memory system is used to store user data. The mapping is generally permanent so that any defective cells remain unused for the lifetime of the memory system. Defect mapping data records the locations of defective columns or cells in the memory array and is generated and stored during initial test and configuration. Defect mapping data may be stored in a portion of the flash memory or in a dedicated memory.
[0022] During normal operation of the memory system (after initial test and configuration), any attempt to access a defective cell is redirected and the replacement cell is accessed instead. Both column and row addresses must match those of a defective cell address for such redirection to occur, whereas only column addresses had to match in prior art schemes. [0023] Both individual cell replacement and column replacement may be implemented in the same memory system at the same time. Generally, the column replacement is done first for any column in which all the memory cells are defective or more than a threshold number are defective. Subsequently, individual cells in remaining non-redundant columns may be mapped to redundant columns that were not needed for replacement of entire columns. Cells may also be replaced in intermediate sized groups of more than one cell, but less than an entire column. One example of such an intermediate sized group is the group formed by the memory cells in a NAND string that arc connected together in scries
[0024] A cell replacement scheme may be implemented using circuits that are located adjacent to the memory array and are on the same chip as the memory array. Such circuits are similar to certain circuits of the prior art but contain additional circuitry to allow comparison of row addresses to the row addresses of defective cells that have been remapped. Alternatively, a cell replacement scheme may be implemented using the memory controller to compare addresses to be accessed with the addresses from the defect mapping data. Such a scheme may be implemented without hardware changes and requires only a change to the memory controller firmware.
[0025] Flash memories are block erasable so that cells are not erased individually, but in units of a block. Blocks generally extend across multiple columns. A block may extend across both redundant columns and non-redundant columns and defective cells within the block are mapped to redundant cells in the same block. Thus, the redundant cells and non-redundant cells containing logically sequential data are erased together.
BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 shows a column replacement scheme of the prior art.
[0027] Figure 2 shows a prior art memory array and peripheral circuitry for carrying out the column replacement scheme of Figure 1.
[0028] Figure 3 shows a memory system supporting aspects of the present invention.
[0029] Figure 4 illustrates the block structure of the memory array of the memory system of Figure 3. [0030] Figure 5A shows the structure of a block 100 of Figure 4 having multiple NAND strings connected by word lines and bit lines.
[0031] Figure 5B shows a more detailed view of a NAND string of Figure 5 A.
[0032] Figure 6 shows an example of redundant cell and redundant column remapping according to an embodiment of the present invention.
[0033] Figure 7 shows a flowchart for a test and configuration operation to carry out a redundant cell and redundant column-remapping scheme such as that shown in Figure 6.
[0034] Figure 8 shows a block diagram of circuitry used to carry out a redundant cell and redundant column-remapping scheme such as that of Figure 6.
[0035] Figure 9 shows a block diagram of an alternative hardware used to carry out a redundant cell and redundant column remapping scheme such as that of Figure 6.
DESCRIPTION OF EMBODIMENTS
[0036] Figure 3 shows a memory system 330 that includes aspects of the present invention. Memory system 330 is connected to a host (not shown) and is in communication with the host. Typically, this communication between host and memory system takes place through a standard interface. In some examples, a memory system such as memory system 330 is part of a removable memory card that has a standard interface so that it can be connected to a variety of hosts according to standards such as those previously listed. In an alternative arrangement, a memory system such as memory system 330 may be embedded in a host system so that it is permanently connected to the host system.
[0037] Memory system 330 includes a controller 20 that controls operation of memory array 1 in response to commands received from the host. Controller 20 may contain a microprocessor, RAM, flash, buffers, registers, Error Correction Code (ECC) circuits and other circuits to manage memory system 330. Data received from the host is stored in memory array 1 under the direction of controller 20 when a host write command is received. For example, the physical locations at which such data are written are generally determined by the controller. Controller 20 operates according to firmware that may be loaded into controller 20 during initial configuration. Data is read from memory array 1 under the direction of controller 20 when a read command is received from the host. Typically, controller 20 maintains a record of logical-to-physical mapping of host data so that when data are identified by the host by a logical address, the data may be accessed in the correct physical address in memory array 1.
[0038] Controller 20 communicates with memory array 1 through peripheral circuits between controller 20 and memory array 1. Peripheral circuits include row control circuits 3, column control circuits 2, data input/output circuits 6, a state machine 8 and command circuits 7. Additional peripheral circuits may also be used, but are not shown in Figure 3 for clarity. When a particular command is sent from controller 20 to command circuits 7, state machine 8 is configured to execute the command by issuing the appropriate signals to row control circuits 3 and column control circuits 2. When state machine 8 completes an operation, it returns a signal to command circuits 7, which in turn indicate to controller 20 that the operation is complete. Controller 20, memory array 1 and peripheral circuits may all be formed together on a single chip. Alternatively, the memory array and peripheral circuits are formed on one chip and the controller is formed on another chip as shown by the broken line dividing memory system 330 between controller chip 21 and memory array chip 22.
[0039] Memory array 1 is made up of erasable units of blocks. Programming of charge storage memory devices can only result in adding more charge to its charge storage elements. Therefore, prior to a program operation, existing charge in a charge storage element must be removed (or erased). Erase circuits (not shown) are provided to erase one or more blocks of memory cells. A non-volatile memory such as EEPROM is referred to as a "Flash" EEPROM when an entire array of cells, or significant groups of cells of the array, is electrically erased together (i.e., in a flash). Once erased, the group of cells can then be reprogrammed. The group of cells erasable together may consist one or more addressable erase unit. The erase unit or block typically stores one or more pages of data, the page being the unit of programming and reading, although more than one page may be programmed or read in a single operation. Each page typically stores one or more sectors of data, the size of the sector being defined by the host system. An example is a sector of 512 bytes of user data, following a standard established with magnetic disk drives, plus some number of bytes of overhead information about the user data and/or the block in with it is stored.
[0040] Figure 4 shows the structure of memory array 1 comprising multiple blocks, a block being the minimum unit of erase. In this example, the memory array has 1024 blocks (blocks 0 to 1023), including block 100, which is described in more detail below. However, some memory arrays may have many more blocks. Blocks may also be linked to form metablocks that are erased together and so are treated as a single large block. In some memories, blocks may be arranged in planes, where a plane is a group of blocks that share certain read/write circuits.
[0041] Figure 5 A and 5B show an example of the structure of the NAND memory array 1 that uses aspects of the present invention. Block 100 is comprised of multiple NAND strings 5Oa5 50b...50c with each string having multiple floating gate cells in series. Additional strings that are not shown in Figure 5 A are located between string 50b and 50c. Figure 5A shows how strings 50a, 50b...5Oc are linked together to form a portion of an array (block 100). Bit lines 51a, 5 Ib...5Ic run vertically and have multiple strings connected to them. The NAND strings connected to a single bit line form a column. For example, strings 50a, 50d...5Ox connected to bit line 51a form column 55a, strings 50b, 5Oe... 5Oy connected to bit line 51b form column 55b. Columns 55a and 55b are non-redundant columns. Strings 50c, 5Of...5Oz form redundant column 55c. A block, such as block 100, may extend across multiple columns as shown. Columns may extend in the vertical direction through multiple blocks. Redundant columns are columns that do not normally contain data unless there are defects. Non-redundant columns normally contain data when the portion of the memory where they are located is not erased. Data stored in a memory array may be host data, ECC data, some form of header data, control data stored by the controller or some other data. In the horizontal direction, word lines extend across the block. Source lines also extend across the block and connect to ends of the NAND strings. A set of cells connected by a word line may be considered a row of the memory array. Block 100 is made up of NAND strings 50a, 50b... 50c, connected by word lines. The cells of block 100 are erased together and are not separately erasable. [0042] Figure 5B illustrates schematically string 50a of memory cells organized into a NAND string. NAND string 50a consists of a series of memory transistors Ml, M2, ... Mn (n= 4, 8, 16 or higher) daisy-chained by their sources and drains. A pair of select transistors Sl, S2 controls the connection of string 50a to the remainder of the memory array via the NAJSID string's source terminal 54 and drain terminal 56. In a memory array, when the source select transistor Sl is turned on, the source terminal is coupled to a source line. Similarly, when the drain select transistor S2 is turned on, the drain terminal of the NAND string is coupled to a bit line of the memory array. Each memory transistor in the chain has a charge storage clement to store a given amount of charge so as to represent an intended memory state. A control gate of each memory transistor provides control over read and write operations. A control gate of each of the select transistors Sl, S2 provides control access to the NAND cell via its source terminal 54 and drain terminal 56 respectively.
[0043] When an addressed memory transistor within a NAND string is read and verified during programming, its control gate is supplied with an appropriate voltage. At the same time, the rest of the non-addressed memory transistors in the NAND string 50 are fully turned on by application of sufficient voltage on their control gates. Tn this way, a conductive path is effectively created from the source of the individual memory transistor to the source terminal 54 of the NAND string and likewise for the drain of the individual memory transistor to the drain terminal 56 of the string. Block 100 extends across both redundant and non-redundant columns of the memory array. Defective cells within block 100 can be mapped to redundant cells that are also within block 100.
[0044] Figure 6 shows redundant column mapping according to an embodiment of the present invention. Unlike the prior art redundant columns, redundant column B of Figure 6 contains data mapped from more than one non-redundant column (columns 2 and 3) of memory array 600. A first defective cell 602 in column 2 is mapped to a redundant cell 604 in redundant column B. A second defective cell 606 in column 3, is mapped to another redundant cell 608 in redundant column B. Thus, one redundant column (column B) is used for storing data from two different non-redundant columns (column 2 and column 3) in memory array 600. In this way, one redundant column can be used to repair multiple defects in the memory array. This is much more efficient than prior art schemes that used an entire redundant column for each defect in the memory array. In the embodiment shown, cells are mapped on a row-by-row basis, instead of mapping all the cells of a column when a defect is found in the column. Thus, only defective cells 602, 606 may be mapped to redundant column B. Other cells in columns 2 and 3 that are not defective are not mapped to redundant column B.
[0045] Defective cells are mapped to the cell in a redundant column that is in the same row. This means that the defective cell and the redundant cell that replaces it share a word line. In this scheme, only one defective cell along a word line can be mapped to a redundant column. However, where more than one redundant column is available, each, defect along a row may be mapped to a different redundant column, so the number of tolerable defects in a row can be as many as the number of redundant columns available. For example, Figure 6 shows a defective cell 610 in column 1. Defective cell 610 and defective cell 602 in column 2 are both in row 612. Because cell 604 in redundant column B is used for the data from cell 602, defective cell 610 is mapped to redundant cell 614 in redundant column C. The redundant column mapping scheme of Figure 6 may be carried out in a memory array having a NAND structure such as that shown in Figure 5A and 5B or having a NOR structure or having another structure.
[0046] In addition to the redundant columns that have data mapped from multiple columns, there are additional redundant columns that operate in the conventional manner. These columns replace entire non-redundant columns so that every cell of the non-redundant column is replaced by a cell of the redundant column. This may be done when the non-redundant column is considered defective. This could be because all the cells in the column are defective (unreadable) or because more than a threshold number of cells in the column are defective. For example, Figure 6 shows defective, non-redundant column 0 mapped to redundant column A, which becomes a replacement column.
[0047] Mapping defective cells to redundant cells (and mapping of defective columns to redundant columns) may either be done as part of an initial test and configuration operation or may be done at a later time after user data has already been stored in the memory system. In some examples, redundant columns are only used for remapping during the initial test and configuration operation that is typically performed at the factory before the memory system is sold or used. Defects that occur later, or are discovered later, may be dealt with in other ways. Remapping during initial test and configuration is permanent and so the remapping is recorded in an irreversible manner such as by using fLLSes.
[0048] While the relocation shown in Figure 6 is either a single bit or an entire column, other units of replacement are also possible. For example, in NAND memories such as shown in Figures 5A and 5B, it may be convenient to replace a string of cells where the string contains a defective memory cell. Thus, for example. If string 50a of Figure 5A includes a defective cell it may be replaced by string 50c without mapping other string such as string 50d that are connected to bit line 51a.
[0049] Figure 7 shows a flowchart of an initial test and configuration operation on a memory array according to an embodiment of the present invention. This test and configuration shown may be carried out using test equipment that is connected to the memory array after it is manufactured but before it is used with a host. The memory array is generally tested in isolation from the controller and other circuits. Card level testing may also be performed but generally docs not indicate defects in the memory array. First, a test is done to determine if there are defective cells in the memory array 720. This may be done by programming test data to the memory array and then reading it back. If data cannot be programmed within a predetermined time, then a cell may be considered to be defective. If the data read back from a cell is not the same as that written to it, the cell may be considered defective. Tf a cell does not reach the erased state within, a predetermined time during an erase operation, the cell may also be considered defective. Alternatively, leakage current may be measured to identify defective cells, or some other means of identifying defective cells may be used. The entire memory array may be tested for defective cells to determine the locations of all defective cells in the memory array. Next, it is determined if any column of the memory array has more than a threshold number of defective cells 722. If a column has more than, the threshold number of defective cells, then the entire column is replaced by a redundant column 724. This is similar to the column replacement of the prior art. In one example, the threshold number is equal to the number of cells in the column. In this case, an entire column, is replaced only if all cells in the column are defective. Tf fewer than all cells in the column are defective, then they are individually replaced. After mapping defective columns, individual defective cells are mapped to redundant cells in one or more defective columns 726. One redundant column may contain data mapped from multiple non-redundant columns in this way. The mapping of defective cells to redundant cells is recorded in a permanent manner 728 so that the information remains with the memory array for future use. One way to permanently record such defect mapping data is to use fuses or antifuses indicating the locations of the defective memory cells and their replacements. Another way to permanently record the defect mapping data is to store it in a portion of the nonvolatile memory that is dedicated to storage of such data and is configured so that it is not later erased. This may be done through hardware or software. Other methods of permanently storing defect mapping data may also be used.
[0050] Figure 8 shows an example of a memory system 841, including flash memory cell array 843, that includes aspects of the present invention. Flash fuses 840 are present as in certain prior art systems (laser fuses or some equivalent structure may also be used). The defect mapping data stored in flash fuses 840 is first loaded into row redundancy control registers 842. Row redundancy control registers 842 have an input from a row address register 844. This input allows the row address of the next row that is to be read to be transferred to row redundancy control registers 842. The row address is compared with the row addresses in the row redundancy control registers 842 (loaded from flash fuses) to determine if there are any defects in the row. If the row address is not the same as a row address in row redundancy control register 842, then there is no defective cell in the addressed row and the row may be accessed using the default column addresses without accessing redundant columns 844. If the row address from row address register 844 matches a row address in row redundancy control registers 842, then this is signaled to column redundancy control registers 846 which determines the redundant column to be accessed instead of the non-redundant column that contains the defect in the addressed row. The column addresses provided to Y-addrcss decode circuits 848 for this row indicate the redundant column and not the non-redundant column that contains the defective cell. Thus, redundant columns are accessed on a row-by-row basis, whereas in the prior art, access was independent of the row address. Here, both row and column addresses must match a recorded defect location, where in the prior art only a column address match was needed. This row-by-row mapping scheme may be done as the only replacement scheme or may be done in conjunction with a column replacement scheme as shown in Figure 6. These schemes may also be combined with other schemes for replacing portions of the memory array, such as replacement of entire blocks where the number of defective cells or defective columns is more than a predetermined number.
[0051] The hardware needed to carry out the replacement scheme described may be included in peripheral circuits that are formed on the same chip as the memory array. Examples of hardware used to carry out column redundancy schemes are provided in U.S. Patent No. 6,560,146 and U.S. Patent Publication No 2005/0141387A1, entitled "Flexible and area efficient column redundancy for flash memories," which are hereby incorporated by reference in their entirety. The circuits shown in Patent Application Publication No. 2005/0141387A1 may be adapted to carry out a retargetable memory cell redundancy scheme such as that of memory system 841 by adding circuitry that receives a row address and compares the row address to stored addresses of rows having cells that are remapped.
[0052] Figure 9 shows another example of a memory system 960 according to the present invention. An external memory system controller 962 is shown connected to a flash memory device 964. This is similar to the example shown in Figure 3. Here, external memory system controller 962 is connected to flash memory device 964 by an external flash memory bus 966. Typically, external memory system controller 962 and flash memory device 964 are formed on separate chips. External memory system controller 962 includes a Central Processing Unit (CPU) or microprocessor 968 and a controller memory 970, which may be a Random Access Memory (RAM). Defect mapping data may be loaded into controller memory 970 when external memory system controller 962 is turned on. Alternatively, a nonvolatile RAM may be used to keep the defect mapping data. In memory system 960, controller memory 970 is loaded with the defect mapping data from flash fuses 970. Alternatively, the defect mapping data may be stored in any other suitable location. External memory system controller 962 compares the locations of defects with the physical addresses of the data that is being accessed. When a match occurs between both the row and column addresses of data being accessed and a defect location, external memory system controller 962 sends an access command to flash memory device 964 indicating one of redundant columns 972 instead of the column with the defective cell. State machine 974 then causes column redundancy control registers 976 to indicate the redundant column to Y-address decode circuits 978 in place of the column with the defective cell. Thus, the functions carried out by the dedicated hardware in memory system 841 of Figure 8 are carried out by external memory system controller 962 in Figure 9. This example has the advantage that it is easier to implement because it does not require hardware changes as an external memory system controller is already provided in most memory systems to manage the memory system. However, this method may be slower and places additional burdens on external memory system controller 962 and on external flash memory bus 966 which may cause memory system 960 to run slower than if these functions are carried out by dedicated circuitry on the memory array chip.
[0053] In the schemes described above, a bit (or bits) of data for a defective cell is relocated to a redundant cell that is in the same row (connected to the same word line). In many memory designs, a block extends along one or more word lines. Thus, the cells of a row, or of a group of rows are erased together. In an embodiment of the present invention, a block extends to include non-redundant and redundant cells connected by a word line. Any defective cells in the block are remapped to redundant cells within the same block. Thus, when the non-redundant cells are erased, the data that was remapped from the non-redundant cells to redundant cells in redundant columns is also erased. This means that no separate data management structures are required for tracking when data in redundant cells becomes obsolete. Because both non-redundant and redundant cells are erased together, they are both returned to the erased state and are ready to receive new data without any separate operation.
[0054J Although various aspects of the present invention have been described with respect to particular embodiments, it will be understood that the invention is entitled to protection within the full scope of the appended claims.

Claims

CLAIMS:
1. A nonvolatile memory array, comprising: a first column of memory cells that contains a defective cell and nondefective cells; a second column of memory cells that is a redundant column that contains only data relocated from elsewhere in the memory array; and the defective cell individually mapped to a redundant cell in the second column such that data to be stored in the defective cell is stored in the redundant cell, the defective cell and the redundant cell in the same row, the second column containing no data mapped from the nondefective cells of the first column.
2. The memory array of claim 1 further comprising a third column that is considered defective and does not store data, all data for the third column stored in a fourth column that is a redundant column.
3. The memory array of claim 2 wherein the third column is considered defective because it has a number of defective cells that exceeds a threshold number.
4. The memory array of claim 1 wherein the defective cell and the redundant cell are in the same block and are not separately erasable.
5. The memory array of claim 4 wherein the mapping of the defective cell to the redundant cell is recorded in another block of the memory array.
6. The memory array of claim 1 wherein the second column contains additional data that is mapped from defective cells in columns other than the first column.
7. The memory array of claim 1 wherein the mapping of the defective cell to the redundant cell is recorded outside the nonvolatile memory array.
8. The memory array of claim 1 wherein the mapping of the defective cell to the redundant cell is permanently recorded using a fuse or antifuse.
9. The memory array of claim 1 wherein the memory array has a NAND structure.
10. The memory array of claim 1 wherein an individual cell of the first or second column contains two or more bits of data.
11. The memory array of claim 1 wherein, subsequently, when access to the defective cell is attempted, the redundant cell is accessed instead.
12. The memory array of claim 11 wherein, when, access to the defective cell is attempted, both the row and column of the defective cell are compared to a defect map to determine that the defective cell is defective.
13. The memory array of claim 12 wherein the row and column are compared to the defect map by a dedicated state machine connected to the memory array.
14. The memory array of claim 12 wherein the row and column are compared to the defect map by a controller that also performs other memory management functions.
15. A method of testing and repairing a nonvolatile memory array having one or more defective cells and one or more redundant columns of redundant cells during an initialization procedure for a new memory chip, comprising: detecting one or more defective cells in the memory array; and individually assigning a replacement cell in a redundant column to replace a defective cell in a first column without assigning any other replacement cells in the redundant column to cells of the first column that are not defective, the defective ceil and the replacement cell connected by a word line.
16. The method of claim 15 further comprising determining that a second column is defective by comparing the number of defective cells in the second column with a threshold number and assigning an entire additional redundant column to replace the second column.
17. The -method of claim 15 further comprising recording the assignment of the replacement cell by causing a permanent change in a fuse or antifuse.
18. The method of claim 15 further comprising recording the assignment of the replacement cell in a nonvolatile memory.
19. A method of replacing a string of memory cells in a nonvolatile NAND type flash memory array, a string of NAND cells connected in series between two select gates, comprising: determining that a first string of memory cells in a first column is a defective string; and mapping the first string of memory cells to a second string of memory cells in a redundant column without mapping other strings of the first column to the redundant column.
20. The method of claim 19 wherein the first string of memory cells is determined to be a defective string because it contains at least one defective cell.
21. The method of claim 19 wherein the first string of memory cells is determined to be a defective string because it contains only defective cells.
22. The method of claim 19 wherein the first string and the second string are both in the same block.
23. The method of claim 19 wherein the first string and the second string share common word lines.
PCT/US2006/060453 2005-11-08 2006-11-01 Memory with retargetable memory cell redundancy WO2007056651A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP06839668A EP1946326A1 (en) 2005-11-08 2006-11-01 Memory with retargetable memory cell redundancy
JP2008540301A JP5297195B2 (en) 2005-11-08 2006-11-01 Memory with re-targetable memory cell redundancy

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/270,198 US7379330B2 (en) 2005-11-08 2005-11-08 Retargetable memory cell redundancy methods
US11/270,410 US7447066B2 (en) 2005-11-08 2005-11-08 Memory with retargetable memory cell redundancy
US11/270,198 2005-11-08
US11/270,410 2005-11-08

Publications (1)

Publication Number Publication Date
WO2007056651A1 true WO2007056651A1 (en) 2007-05-18

Family

ID=38023610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/060453 WO2007056651A1 (en) 2005-11-08 2006-11-01 Memory with retargetable memory cell redundancy

Country Status (6)

Country Link
US (2) US7447066B2 (en)
EP (1) EP1946326A1 (en)
JP (1) JP5297195B2 (en)
KR (1) KR101021165B1 (en)
TW (1) TWI354992B (en)
WO (1) WO2007056651A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7379330B2 (en) 2005-11-08 2008-05-27 Sandisk Corporation Retargetable memory cell redundancy methods
JP2009123250A (en) * 2007-11-09 2009-06-04 Spansion Llc Semiconductor device and its control method

Families Citing this family (133)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7631245B2 (en) * 2005-09-26 2009-12-08 Sandisk Il Ltd. NAND flash memory controller exporting a NAND interface
US8291295B2 (en) 2005-09-26 2012-10-16 Sandisk Il Ltd. NAND flash memory controller exporting a NAND interface
KR101202537B1 (en) 2006-05-12 2012-11-19 애플 인크. Combined distortion estimation and error correction coding for memory devices
CN103280239B (en) 2006-05-12 2016-04-06 苹果公司 Distortion estimation in memory device and elimination
WO2007132456A2 (en) 2006-05-12 2007-11-22 Anobit Technologies Ltd. Memory device with adaptive capacity
US7697326B2 (en) 2006-05-12 2010-04-13 Anobit Technologies Ltd. Reducing programming error in memory devices
KR100733952B1 (en) * 2006-06-12 2007-06-29 삼성전자주식회사 Multi-bit flash memory device capable of minimizing coupling between flag cells and program method thereof
US20080046641A1 (en) * 2006-08-21 2008-02-21 Sandisk Il Ltd. NAND flash memory controller exporting a logical sector-based interface
US20080046630A1 (en) * 2006-08-21 2008-02-21 Sandisk Il Ltd. NAND flash memory controller exporting a logical sector-based interface
US8060806B2 (en) 2006-08-27 2011-11-15 Anobit Technologies Ltd. Estimation of non-linear distortion in memory devices
US7821826B2 (en) 2006-10-30 2010-10-26 Anobit Technologies, Ltd. Memory cell readout using successive approximation
US7975192B2 (en) 2006-10-30 2011-07-05 Anobit Technologies Ltd. Reading memory cells using multiple thresholds
US7924648B2 (en) 2006-11-28 2011-04-12 Anobit Technologies Ltd. Memory power and performance management
WO2008068747A2 (en) 2006-12-03 2008-06-12 Anobit Technologies Ltd. Automatic defect management in memory devices
US7900102B2 (en) 2006-12-17 2011-03-01 Anobit Technologies Ltd. High-speed programming of memory devices
US7751240B2 (en) 2007-01-24 2010-07-06 Anobit Technologies Ltd. Memory device with negative thresholds
US8151166B2 (en) 2007-01-24 2012-04-03 Anobit Technologies Ltd. Reduction of back pattern dependency effects in memory devices
US8369141B2 (en) 2007-03-12 2013-02-05 Apple Inc. Adaptive estimation of memory cell read thresholds
US8001320B2 (en) 2007-04-22 2011-08-16 Anobit Technologies Ltd. Command interface for memory devices
JP5497631B2 (en) * 2007-04-26 2014-05-21 アギア システムズ インコーポレーテッド Built-in memory repair method based on fuse burn-in state machine and fuse download state machine
WO2008139441A2 (en) 2007-05-12 2008-11-20 Anobit Technologies Ltd. Memory device with internal signal processing unit
US8234545B2 (en) 2007-05-12 2012-07-31 Apple Inc. Data storage with incremental redundancy
US7925936B1 (en) 2007-07-13 2011-04-12 Anobit Technologies Ltd. Memory device with non-uniform programming levels
US8259497B2 (en) 2007-08-06 2012-09-04 Apple Inc. Programming schemes for multi-level analog memory cells
US8174905B2 (en) 2007-09-19 2012-05-08 Anobit Technologies Ltd. Programming orders for reducing distortion in arrays of multi-level analog memory cells
US7773413B2 (en) 2007-10-08 2010-08-10 Anobit Technologies Ltd. Reliable data storage in analog memory cells in the presence of temperature variations
US8000141B1 (en) 2007-10-19 2011-08-16 Anobit Technologies Ltd. Compensation for voltage drifts in analog memory cells
US8527819B2 (en) 2007-10-19 2013-09-03 Apple Inc. Data storage in analog memory cell arrays having erase failures
US8068360B2 (en) 2007-10-19 2011-11-29 Anobit Technologies Ltd. Reading analog memory cells using built-in multi-threshold commands
WO2009063450A2 (en) 2007-11-13 2009-05-22 Anobit Technologies Optimized selection of memory units in multi-unit memory devices
TW200921691A (en) * 2007-11-14 2009-05-16 Etron Technology Inc Method for controlling a dram
US8225181B2 (en) 2007-11-30 2012-07-17 Apple Inc. Efficient re-read operations from memory devices
US8209588B2 (en) 2007-12-12 2012-06-26 Anobit Technologies Ltd. Efficient interference cancellation in analog memory cell arrays
US8456905B2 (en) 2007-12-16 2013-06-04 Apple Inc. Efficient data storage in multi-plane memory devices
US8085586B2 (en) 2007-12-27 2011-12-27 Anobit Technologies Ltd. Wear level estimation in analog memory cells
US8156398B2 (en) 2008-02-05 2012-04-10 Anobit Technologies Ltd. Parameter estimation based on error correction code parity check equations
US7924587B2 (en) 2008-02-21 2011-04-12 Anobit Technologies Ltd. Programming of analog memory cells using a single programming pulse per state transition
US7864573B2 (en) 2008-02-24 2011-01-04 Anobit Technologies Ltd. Programming analog memory cells for reduced variance after retention
US8230300B2 (en) 2008-03-07 2012-07-24 Apple Inc. Efficient readout from analog memory cells using data compression
US8400858B2 (en) 2008-03-18 2013-03-19 Apple Inc. Memory device with reduced sense time readout
US8059457B2 (en) 2008-03-18 2011-11-15 Anobit Technologies Ltd. Memory device with multiple-accuracy read commands
US8068380B2 (en) * 2008-05-15 2011-11-29 Micron Technology, Inc. Block repair scheme
US8498151B1 (en) 2008-08-05 2013-07-30 Apple Inc. Data storage in analog memory cells using modified pass voltages
US7924613B1 (en) 2008-08-05 2011-04-12 Anobit Technologies Ltd. Data storage in analog memory cells with protection against programming interruption
US8169825B1 (en) 2008-09-02 2012-05-01 Anobit Technologies Ltd. Reliable data storage in analog memory cells subjected to long retention periods
US8949684B1 (en) 2008-09-02 2015-02-03 Apple Inc. Segmented data storage
US8000135B1 (en) 2008-09-14 2011-08-16 Anobit Technologies Ltd. Estimation of memory cell read thresholds by sampling inside programming level distribution intervals
US8482978B1 (en) 2008-09-14 2013-07-09 Apple Inc. Estimation of memory cell read thresholds by sampling inside programming level distribution intervals
JP4746658B2 (en) * 2008-09-29 2011-08-10 株式会社東芝 Semiconductor memory system
US8239734B1 (en) 2008-10-15 2012-08-07 Apple Inc. Efficient data storage in storage device arrays
US7996736B2 (en) * 2008-10-26 2011-08-09 Sandisk 3D Llc Bad page marking strategy for fast readout in memory
US8713330B1 (en) 2008-10-30 2014-04-29 Apple Inc. Data scrambling in memory devices
US8208304B2 (en) 2008-11-16 2012-06-26 Anobit Technologies Ltd. Storage at M bits/cell density in N bits/cell analog memory cell devices, M>N
US7881134B2 (en) * 2008-11-17 2011-02-01 Micron Technology, Inc. Replacing defective columns of memory cells in response to external addresses
US8316201B2 (en) 2008-12-18 2012-11-20 Sandisk Il Ltd. Methods for executing a command to write data from a source location to a destination location in a memory device
US8397131B1 (en) 2008-12-31 2013-03-12 Apple Inc. Efficient readout schemes for analog memory cell devices
US8248831B2 (en) 2008-12-31 2012-08-21 Apple Inc. Rejuvenation of analog memory cells
US8924661B1 (en) 2009-01-18 2014-12-30 Apple Inc. Memory system including a controller and processors associated with memory devices
US8228701B2 (en) 2009-03-01 2012-07-24 Apple Inc. Selective activation of programming schemes in analog memory cell arrays
US8259506B1 (en) 2009-03-25 2012-09-04 Apple Inc. Database of memory read thresholds
US8832354B2 (en) 2009-03-25 2014-09-09 Apple Inc. Use of host system resources by memory controller
US8238157B1 (en) 2009-04-12 2012-08-07 Apple Inc. Selective re-programming of analog memory cells
US8027195B2 (en) * 2009-06-05 2011-09-27 SanDisk Technologies, Inc. Folding data stored in binary format into multi-state format within non-volatile memory devices
US8102705B2 (en) 2009-06-05 2012-01-24 Sandisk Technologies Inc. Structure and method for shuffling data within non-volatile memory devices
US20110002169A1 (en) 2009-07-06 2011-01-06 Yan Li Bad Column Management with Bit Information in Non-Volatile Memory Systems
US8479080B1 (en) 2009-07-12 2013-07-02 Apple Inc. Adaptive over-provisioning in memory systems
US20110040924A1 (en) * 2009-08-11 2011-02-17 Selinger Robert D Controller and Method for Detecting a Transmission Error Over a NAND Interface Using Error Detection Code
US20110041039A1 (en) * 2009-08-11 2011-02-17 Eliyahou Harari Controller and Method for Interfacing Between a Host Controller in a Host and a Flash Memory Device
US20110041005A1 (en) 2009-08-11 2011-02-17 Selinger Robert D Controller and Method for Providing Read Status and Spare Block Management Information in a Flash Memory System
US8495465B1 (en) 2009-10-15 2013-07-23 Apple Inc. Error correction coding over multiple memory pages
US8677054B1 (en) 2009-12-16 2014-03-18 Apple Inc. Memory management schemes for non-volatile memory devices
US20110153912A1 (en) * 2009-12-18 2011-06-23 Sergey Anatolievich Gorobets Maintaining Updates of Multi-Level Non-Volatile Memory in Binary Non-Volatile Memory
US8468294B2 (en) 2009-12-18 2013-06-18 Sandisk Technologies Inc. Non-volatile memory with multi-gear control using on-chip folding of data
US8144512B2 (en) 2009-12-18 2012-03-27 Sandisk Technologies Inc. Data transfer flows for on-chip folding
US8725935B2 (en) 2009-12-18 2014-05-13 Sandisk Technologies Inc. Balanced performance for on-chip folding of non-volatile memories
US8595411B2 (en) 2009-12-30 2013-11-26 Sandisk Technologies Inc. Method and controller for performing a sequence of commands
US8443263B2 (en) 2009-12-30 2013-05-14 Sandisk Technologies Inc. Method and controller for performing a copy-back operation
US8694814B1 (en) 2010-01-10 2014-04-08 Apple Inc. Reuse of host hibernation storage space by memory controller
US8572311B1 (en) 2010-01-11 2013-10-29 Apple Inc. Redundant data storage in multi-die memory systems
US8694853B1 (en) 2010-05-04 2014-04-08 Apple Inc. Read commands for reading interfering memory cells
JP5559616B2 (en) * 2010-06-17 2014-07-23 ラピスセミコンダクタ株式会社 Semiconductor memory device
US8572423B1 (en) 2010-06-22 2013-10-29 Apple Inc. Reducing peak current in memory systems
KR101660985B1 (en) * 2010-07-09 2016-10-10 에스케이하이닉스 주식회사 Semiconductor memory device and method of operation the same
US8595591B1 (en) 2010-07-11 2013-11-26 Apple Inc. Interference-aware assignment of programming levels in analog memory cells
US9104580B1 (en) 2010-07-27 2015-08-11 Apple Inc. Cache memory for hybrid disk drives
US8767459B1 (en) 2010-07-31 2014-07-01 Apple Inc. Data storage in analog memory cells across word lines using a non-integer number of bits per cell
US8856475B1 (en) 2010-08-01 2014-10-07 Apple Inc. Efficient selection of memory blocks for compaction
US8694854B1 (en) 2010-08-17 2014-04-08 Apple Inc. Read threshold setting based on soft readout statistics
US9021181B1 (en) 2010-09-27 2015-04-28 Apple Inc. Memory management for unifying memory cell conditions by using maximum time intervals
US8819328B2 (en) 2010-12-30 2014-08-26 Sandisk Technologies Inc. Controller and method for performing background operations
US9342446B2 (en) 2011-03-29 2016-05-17 SanDisk Technologies, Inc. Non-volatile memory system allowing reverse eviction of data updates to non-volatile binary cache
US8694719B2 (en) 2011-06-24 2014-04-08 Sandisk Technologies Inc. Controller, storage device, and method for power throttling memory operations
US8842473B2 (en) 2012-03-15 2014-09-23 Sandisk Technologies Inc. Techniques for accessing column selecting shift register with skipped entries in non-volatile memories
US9727417B2 (en) 2012-03-29 2017-08-08 Intel Corporation Chunk redundancy architecture for memory
US11024352B2 (en) 2012-04-10 2021-06-01 Samsung Electronics Co., Ltd. Memory system for access concentration decrease management and access concentration decrease method
US8681548B2 (en) 2012-05-03 2014-03-25 Sandisk Technologies Inc. Column redundancy circuitry for non-volatile memory
US9043661B2 (en) 2012-05-30 2015-05-26 Micron Technology, Inc. Memories and methods for performing column repair
JP2013254538A (en) * 2012-06-06 2013-12-19 Toshiba Corp Nonvolatile semiconductor memory device
US9076506B2 (en) 2012-09-28 2015-07-07 Sandisk Technologies Inc. Variable rate parallel to serial shift register
TWI502600B (en) * 2012-09-28 2015-10-01 Leadconn Technology Co Ltd Device for fixing identifier of memory
US9490035B2 (en) 2012-09-28 2016-11-08 SanDisk Technologies, Inc. Centralized variable rate serializer and deserializer for bad column management
US8897080B2 (en) 2012-09-28 2014-11-25 Sandisk Technologies Inc. Variable rate serial to parallel shift register
US8741714B2 (en) * 2012-10-03 2014-06-03 Sandisk 3D Llc Support lines to prevent line collapse in arrays
US8972649B2 (en) * 2012-10-05 2015-03-03 Microsoft Technology Licensing, Llc Writing memory blocks using codewords
US9032244B2 (en) * 2012-11-16 2015-05-12 Microsoft Technology Licensing, Llc Memory segment remapping to address fragmentation
US9146807B2 (en) 2012-12-04 2015-09-29 Sandisk Technologies Inc. Bad column handling in flash memory
KR102049076B1 (en) 2012-12-06 2020-01-09 삼성전자주식회사 non- volatile memory device and operating method thereof
KR20140075949A (en) * 2012-12-11 2014-06-20 삼성전자주식회사 NONVOLATILE MEMORY DEVICE AND MEMORy SYSTEM
US9229848B2 (en) 2013-01-21 2016-01-05 Micron Technology, Inc. Determining soft data for fractional digit memory cells
US8990614B2 (en) * 2013-03-14 2015-03-24 Apple Inc. Performance of a system having non-volatile memory
US9343185B2 (en) 2013-09-26 2016-05-17 International Business Machines Corporation Electronic circuit for fitting a virtual address range to a physical memory containing faulty address
KR102154499B1 (en) * 2013-12-23 2020-09-10 삼성전자주식회사 Nonvolatile memory device and driving method of the same
US9934872B2 (en) 2014-10-30 2018-04-03 Sandisk Technologies Llc Erase stress and delta erase loop count methods for various fail modes in non-volatile memory
US20160124664A1 (en) * 2014-10-30 2016-05-05 Sandisk Technologies Inc. Block Level Local Column Redundancy Methods for Higher Yield
US9224502B1 (en) 2015-01-14 2015-12-29 Sandisk Technologies Inc. Techniques for detection and treating memory hole to local interconnect marginality defects
US10032524B2 (en) 2015-02-09 2018-07-24 Sandisk Technologies Llc Techniques for determining local interconnect defects
US9269446B1 (en) 2015-04-08 2016-02-23 Sandisk Technologies Inc. Methods to improve programming of slow cells
US9564219B2 (en) 2015-04-08 2017-02-07 Sandisk Technologies Llc Current based detection and recording of memory hole-interconnect spacing defects
KR102294848B1 (en) * 2015-06-30 2021-08-31 삼성전자주식회사 Storage device including nonvolatile memory device and controller
US9659666B2 (en) * 2015-08-31 2017-05-23 Sandisk Technologies Llc Dynamic memory recovery at the sub-block level
US9792175B2 (en) * 2015-10-21 2017-10-17 Sandisk Technologies Llc Bad column management in nonvolatile memory
KR101716865B1 (en) * 2016-04-29 2017-03-15 고려대학교 산학협력단 Stack and heap management apparatus for avoiding using fault cells in main memory and method thereof
US10353769B2 (en) 2017-07-25 2019-07-16 Apple Inc. Recovering from addressing fault in a non-volatile memory
US10726939B2 (en) * 2017-09-27 2020-07-28 SK Hynix Inc. Memory devices having spare column remap storages
US10671497B2 (en) * 2018-01-19 2020-06-02 International Business Machines Corporation Efficient and selective sparing of bits in memory systems
US10832793B2 (en) * 2018-08-21 2020-11-10 Micron Technology, Inc. Defective memory cell detection circuitry including use in automotive control systems
CN110970121B (en) * 2018-09-29 2023-04-18 浙江悦讯信息科技有限公司 Operation transferring and tracing system and operation transferring and tracing method based on block chain
US10942799B1 (en) 2019-09-06 2021-03-09 Intel Corporation Defective bit line management in connection with a memory access
US11314588B2 (en) * 2019-11-11 2022-04-26 Winbond Electronics Corp. Memory device and multi physical cells error correction method thereof
TW202133177A (en) * 2020-02-24 2021-09-01 聯華電子股份有限公司 Non-volatile memory and operation method thereof
US11556416B2 (en) 2021-05-05 2023-01-17 Apple Inc. Controlling memory readout reliability and throughput by adjusting distance between read thresholds
US11847342B2 (en) 2021-07-28 2023-12-19 Apple Inc. Efficient transfer of hard data and confidence levels in reading a nonvolatile memory
CN116612801B (en) * 2023-07-19 2023-10-13 芯天下技术股份有限公司 Erasing method and decoding circuit of small-capacity storage array

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5485425A (en) * 1992-06-30 1996-01-16 Hitachi, Ltd. Semiconductor memory device having redundant column and operation method thereof
EP0797145A1 (en) * 1996-03-22 1997-09-24 STMicroelectronics S.r.l. Sectorized electrically erasable and programmable non-volatile memory device with redundancy
US5808945A (en) * 1996-02-21 1998-09-15 Sony Corporation Semiconductor memory having redundant memory array
US6484277B1 (en) * 1999-05-19 2002-11-19 Infineon Technologies Ag Integrated memory having a redundancy function

Family Cites Families (82)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3895360A (en) * 1974-01-29 1975-07-15 Westinghouse Electric Corp Block oriented random access memory
JPS61265798A (en) * 1985-05-20 1986-11-25 Fujitsu Ltd Semiconductor memory device
JPS62287497A (en) 1986-06-06 1987-12-14 Fujitsu Ltd Semiconductor memory unit
JPH0677400B2 (en) 1987-11-12 1994-09-28 シャープ株式会社 Semiconductor integrated circuit device
US5095344A (en) * 1988-06-08 1992-03-10 Eliyahou Harari Highly compact eprom and flash eeprom devices
US5043940A (en) * 1988-06-08 1991-08-27 Eliyahou Harari Flash EEPROM memory systems having multistate storage cells
US5268870A (en) * 1988-06-08 1993-12-07 Eliyahou Harari Flash EEPROM system and intelligent programming and erasing methods therefor
US5265055A (en) * 1988-10-07 1993-11-23 Hitachi, Ltd. Semiconductor memory having redundancy circuit
JP2993684B2 (en) * 1988-10-07 1999-12-20 株式会社日立製作所 Semiconductor memory device with defect relieve circuit
US5070032A (en) * 1989-03-15 1991-12-03 Sundisk Corporation Method of making dense flash eeprom semiconductor memory structures
US5535328A (en) 1989-04-13 1996-07-09 Sandisk Corporation Non-volatile memory system card with flash erasable sectors of EEprom cells including a mechanism for substituting defective cells
US5172338B1 (en) 1989-04-13 1997-07-08 Sandisk Corp Multi-state eeprom read and write circuits and techniques
EP1031992B1 (en) 1989-04-13 2006-06-21 SanDisk Corporation Flash EEPROM system
US5200959A (en) 1989-10-17 1993-04-06 Sundisk Corporation Device and method for defect handling in semi-conductor memory
US5343063A (en) * 1990-12-18 1994-08-30 Sundisk Corporation Dense vertical programmable read only memory cell structure and processes for making them
JPH0831279B2 (en) 1990-12-20 1996-03-27 インターナショナル・ビジネス・マシーンズ・コーポレイション Redundant system
US5270979A (en) * 1991-03-15 1993-12-14 Sundisk Corporation Method for optimum erasing of EEPROM
US5663901A (en) * 1991-04-11 1997-09-02 Sandisk Corporation Computer memory cards using flash EEPROM integrated circuit chips and memory-controller systems
US5430859A (en) 1991-07-26 1995-07-04 Sundisk Corporation Solid state memory system including plural memory chips and a serialized bus
US6230233B1 (en) 1991-09-13 2001-05-08 Sandisk Corporation Wear leveling techniques for flash EEPROM systems
US5438573A (en) 1991-09-13 1995-08-01 Sundisk Corporation Flash EEPROM array data and header file structure
US6222762B1 (en) * 1992-01-14 2001-04-24 Sandisk Corporation Multi-state memory
US5313421A (en) 1992-01-14 1994-05-17 Sundisk Corporation EEPROM with split gate source side injection
US5712180A (en) 1992-01-14 1998-01-27 Sundisk Corporation EEPROM with split gate source side injection
JP2554816B2 (en) 1992-02-20 1996-11-20 株式会社東芝 Semiconductor memory device
JP2741825B2 (en) 1992-04-28 1998-04-22 三菱電機株式会社 Semiconductor storage device
US5657332A (en) * 1992-05-20 1997-08-12 Sandisk Corporation Soft errors handling in EEPROM devices
US5532962A (en) * 1992-05-20 1996-07-02 Sandisk Corporation Soft errors handling in EEPROM devices
US5315541A (en) * 1992-07-24 1994-05-24 Sundisk Corporation Segmented column memory array
US5428621A (en) 1992-09-21 1995-06-27 Sundisk Corporation Latent defect handling in EEPROM devices
US5555204A (en) 1993-06-29 1996-09-10 Kabushiki Kaisha Toshiba Non-volatile semiconductor memory device
KR0169267B1 (en) 1993-09-21 1999-02-01 사토 후미오 Nonvolatile semiconductor memory device
US5442748A (en) 1993-10-29 1995-08-15 Sun Microsystems, Inc. Architecture of output switching circuitry for frame buffer
US5661053A (en) * 1994-05-25 1997-08-26 Sandisk Corporation Method of making dense flash EEPROM cell array and peripheral supporting circuits formed in deposited field oxide with the use of spacers
JPH0883497A (en) * 1994-09-12 1996-03-26 Hitachi Ltd Semiconductor integrated circuit device
US5783958A (en) * 1996-01-19 1998-07-21 Sgs-Thomson Microelectronics, Inc. Switching master slave circuit
US5682352A (en) * 1996-02-08 1997-10-28 Invoice Technology, Inc. Digital testing of analog memory devices
JP3845889B2 (en) * 1996-02-21 2006-11-15 ソニー株式会社 Semiconductor memory device
US5903495A (en) * 1996-03-18 1999-05-11 Kabushiki Kaisha Toshiba Semiconductor device and memory system
US5798968A (en) 1996-09-24 1998-08-25 Sandisk Corporation Plane decode/virtual sector architecture
US6091666A (en) 1996-10-04 2000-07-18 Sony Corporation Nonvolatile flash memory with fast data programming operation
KR100205006B1 (en) * 1996-10-08 1999-06-15 윤종용 Semiconductor memory device having an automatic falut block mapping function
US5890192A (en) * 1996-11-05 1999-03-30 Sandisk Corporation Concurrent write of multiple chunks of data into multiple subarrays of flash EEPROM
JP3317187B2 (en) * 1997-04-25 2002-08-26 日本電気株式会社 Semiconductor storage device
US5930167A (en) 1997-07-30 1999-07-27 Sandisk Corporation Multi-state non-volatile flash memory capable of being its own two state write cache
US5909449A (en) 1997-09-08 1999-06-01 Invox Technology Multibit-per-cell non-volatile memory with error detection and correction
US6138254A (en) * 1998-01-22 2000-10-24 Micron Technology, Inc. Method and apparatus for redundant location addressing using data compression
US6295231B1 (en) * 1998-07-17 2001-09-25 Kabushiki Kaisha Toshiba High-speed cycle clock-synchronous memory device
JP3730423B2 (en) 1998-11-24 2006-01-05 富士通株式会社 Semiconductor memory device
US6141267A (en) 1999-02-03 2000-10-31 International Business Machines Corporation Defect management engine for semiconductor memories and memory systems
US6151248A (en) * 1999-06-30 2000-11-21 Sandisk Corporation Dual floating gate EEPROM cell array with steering gates shared by adjacent cells
DE19957621C2 (en) 1999-11-30 2001-11-29 Schleifring Und Appbau Gmbh Arrangement for the transmission of electrical signals between moving parts with a reduced number of paths
US6426893B1 (en) 2000-02-17 2002-07-30 Sandisk Corporation Flash eeprom system with simultaneous multiple data sector programming and storage of physical block characteristics in other designated blocks
US6243306B1 (en) 2000-07-19 2001-06-05 International Business Machines Corporation Defect management engine for generating a unified address to access memory cells in a primary and a redundancy memory array
US6496425B1 (en) * 2000-08-21 2002-12-17 Micron Technology, Inc Multiple bit line column redundancy
US6512263B1 (en) 2000-09-22 2003-01-28 Sandisk Corporation Non-volatile memory cell array having discontinuous source and drain diffusions contacted by continuous bit line conductors and methods of forming
JP3916862B2 (en) * 2000-10-03 2007-05-23 株式会社東芝 Nonvolatile semiconductor memory device
JP2002208294A (en) 2001-01-12 2002-07-26 Toshiba Corp Semiconductor memory having redundancy system
US6763424B2 (en) * 2001-01-19 2004-07-13 Sandisk Corporation Partial block data programming and reading operations in a non-volatile memory
KR100385957B1 (en) * 2001-02-14 2003-06-02 삼성전자주식회사 Semiconductor memory device having effective column redundancy scheme
US6522580B2 (en) * 2001-06-27 2003-02-18 Sandisk Corporation Operating techniques for reducing effects of coupling between storage elements of a non-volatile memory operated in multiple data states
US6563732B2 (en) 2001-08-02 2003-05-13 Stmicroelectronics, Inc. Redundancy circuit and method for flash memory devices
US6594177B2 (en) * 2001-08-02 2003-07-15 Stmicroelectronics, Inc. Redundancy circuit and method for replacing defective memory cells in a flash memory device
US7170802B2 (en) 2003-12-31 2007-01-30 Sandisk Corporation Flexible and area efficient column redundancy for non-volatile memories
US6560146B2 (en) 2001-09-17 2003-05-06 Sandisk Corporation Dynamic column block selection
US6456528B1 (en) 2001-09-17 2002-09-24 Sandisk Corporation Selective operation of a multi-state non-volatile memory system in a binary mode
US6925007B2 (en) * 2001-10-31 2005-08-02 Sandisk Corporation Multi-state non-volatile integrated circuit memory systems that employ dielectric storage elements
JP2003187591A (en) 2001-12-14 2003-07-04 Toshiba Corp Semiconductor memory
KR100437461B1 (en) 2002-01-12 2004-06-23 삼성전자주식회사 Nand-type flash memory device and erase, program, and copy-back program methods thereof
US6771536B2 (en) * 2002-02-27 2004-08-03 Sandisk Corporation Operating techniques for reducing program and read disturbs of a non-volatile memory
JP4175852B2 (en) * 2002-09-13 2008-11-05 スパンション エルエルシー Semiconductor memory that replaces redundant cell array normally
JP4040405B2 (en) 2002-09-20 2008-01-30 富士通株式会社 Nonvolatile semiconductor memory cell control method and nonvolatile semiconductor memory device
US7196931B2 (en) * 2002-09-24 2007-03-27 Sandisk Corporation Non-volatile memory and method with reduced source line bias errors
US6983428B2 (en) * 2002-09-24 2006-01-03 Sandisk Corporation Highly compact non-volatile memory and method thereof
JP4314057B2 (en) * 2003-04-18 2009-08-12 サンディスク コーポレイション Nonvolatile semiconductor memory device and electronic device
US6975542B2 (en) 2003-05-08 2005-12-13 Micron Technology, Inc. NAND flash memory with improved read and verification threshold uniformity
JP2005182900A (en) * 2003-12-18 2005-07-07 Sony Corp Semiconductor memory
US7057939B2 (en) 2004-04-23 2006-06-06 Sandisk Corporation Non-volatile memory and control with improved partial page program capability
KR100530930B1 (en) * 2004-05-11 2005-11-23 주식회사 하이닉스반도체 A method for multi-i/o repair of nand flash memory device and a nand flash memory device thereof
JP4102338B2 (en) * 2004-07-20 2008-06-18 株式会社東芝 Semiconductor memory device
US7116590B2 (en) * 2004-08-23 2006-10-03 Micron Technology, Inc. Memory address repair without enable fuses
US7447066B2 (en) 2005-11-08 2008-11-04 Sandisk Corporation Memory with retargetable memory cell redundancy

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5485425A (en) * 1992-06-30 1996-01-16 Hitachi, Ltd. Semiconductor memory device having redundant column and operation method thereof
US5808945A (en) * 1996-02-21 1998-09-15 Sony Corporation Semiconductor memory having redundant memory array
EP0797145A1 (en) * 1996-03-22 1997-09-24 STMicroelectronics S.r.l. Sectorized electrically erasable and programmable non-volatile memory device with redundancy
US6484277B1 (en) * 1999-05-19 2002-11-19 Infineon Technologies Ag Integrated memory having a redundancy function

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1946326A1 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7379330B2 (en) 2005-11-08 2008-05-27 Sandisk Corporation Retargetable memory cell redundancy methods
US7447066B2 (en) 2005-11-08 2008-11-04 Sandisk Corporation Memory with retargetable memory cell redundancy
JP2009123250A (en) * 2007-11-09 2009-06-04 Spansion Llc Semiconductor device and its control method

Also Published As

Publication number Publication date
JP5297195B2 (en) 2013-09-25
US7379330B2 (en) 2008-05-27
KR101021165B1 (en) 2011-03-15
TWI354992B (en) 2011-12-21
US20070103977A1 (en) 2007-05-10
JP2009515289A (en) 2009-04-09
US7447066B2 (en) 2008-11-04
TW200733115A (en) 2007-09-01
KR20080076918A (en) 2008-08-20
EP1946326A1 (en) 2008-07-23
US20070103978A1 (en) 2007-05-10

Similar Documents

Publication Publication Date Title
US7379330B2 (en) Retargetable memory cell redundancy methods
EP1829047B1 (en) System and method for use of on-chip non-volatile memory write cache
US7477547B2 (en) Flash memory refresh techniques triggered by controlled scrub data reads
US7573773B2 (en) Flash memory with data refresh triggered by controlled scrub data reads
US7451264B2 (en) Cycle count storage methods
US7467253B2 (en) Cycle count storage systems
US7315916B2 (en) Scratch pad block
US7395404B2 (en) Cluster auto-alignment for storing addressable data packets in a non-volatile memory array
CN101331554A (en) Memory with retargetable memory cell redundancy
EP2135251B1 (en) Flash memory refresh techniques triggered by controlled scrub data reads
WO2007121025A1 (en) Cycle count storage methods and systems
JP4332108B2 (en) Memory controller, flash memory system, and flash memory control method

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680046747.4

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2006839668

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2008540301

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 1020087013050

Country of ref document: KR