|Publication number||US6662263 B1|
|Application number||US 09/518,608|
|Publication date||Dec 9, 2003|
|Filing date||Mar 3, 2000|
|Priority date||Mar 3, 2000|
|Also published as||US7080192|
|Publication number||09518608, 518608, US 6662263 B1, US 6662263B1, US-B1-6662263, US6662263 B1, US6662263B1|
|Inventors||Sau C. Wong|
|Original Assignee||Multi Level Memory Technology|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (84), Referenced by (33), Classifications (28), Legal Events (7)|
|External Links: USPTO, USPTO Assignment, Espacenet|
1. Field of the Invention
This invention relates to non-volatile memory and to systems for storage of blocks of information.
2. Description of Related Art
A conventional non-volatile semiconductor memory such as a Flash memory includes one or more arrays of memory cells. FIG. 1A shows a conventional architecture for a Flash memory 100 including an array 110. The memory cells in array 110 are arranged in rows and columns and connected together by row lines 112 and column lines 113 (also referred to as word lines 112 and bit lines 113). Each row line 112 connects to the control gates of memory cells in an associated row, and each column line 113 connects to the drains of memory cells in an associated column. Flash memory array 110 is further divided into multiple sectors 115. Each sector 115 contains one or more columns of memory cells and has an associated source line 114 connected to the sources of the memory cells in the sector 115. Further associated with each memory array 110 are a row decoder 120, a column decoder 130, and a source decoder 140 that respectively connect to row lines 112, column lines 113, and source lines 114 of the array 110. Drivers (not shown) associated with row decoder 120, column decoder 130, and source decoder 140 bias row lines 112, column lines 113, and source lines 114 as required for erase, write, and read operations.
FIG. 1B shows another architecture for a Flash memory array 110′. Array 110 ′ is similar to array 110 (FIG. 1A) but has row-based sectors 115′, instead of column based sectors. Each sector 115′ includes one or more rows of memory cell a source line 114′ connected to the sources of the memory cells in the sector 115′. A source decoder 140′ connects to and controls the voltage levels on source lines 114′ for erase, write, and read operations.
The memory arrays 110 and 110′ commonly store blocks of data. For example, a digitally encoded music player such as an MP3 music player can employ array 110 or 110′ to store data representing music or songs. The data for each song is stored in one or more sectors 115 or 115′, and each sector 115 or 115′ only stores data from one song. This arrangement permits a user to erase one song by erasing the sector or sectors associated with the song. The data associated with other songs, being stored in separate sectors, is not erased. A user can thus keep a favorite song while changing other songs. One drawback of this data arrangement is the wasted storage capacity resulting when data for a song only partly fills a sector so that some memory cells store no data. Sectors can be made smaller to reduce the average amount of wasted data storage. But, smaller sectors require a Flash memory to include more sectors for the same amount of storage, and the increase in the number of sectors increases circuit overhead. Accordingly, providing the greatest possible effective storage capacity per integrated circuit area requires balancing wasted memory cells in large sectors against increased overhead for small sectors.
Another concern or drawback of the conventional Flash memory architectures is the accumulation of disturbances of the threshold voltages of memory cells. With either array 110 or 110′, row decoder 120 and column decoder 130 respectively apply signals to a selected row line and a selected column line to write to or read from a selected memory cell. For a write operation, the voltages on the selected row and column lines are high and combine to change the threshold voltage of the selected memory cell, thereby writing a data value. The high row and column voltages can disturb the threshold voltages of unselected memory cells connected to the selected row line or the selected column line. These disturbances of the threshold voltages (i.e., write disturbs) can accumulate over time.
For an erase operation, source decoder 140 or 140′ and row decoder 120 establish in a selected sector a voltage difference between the control gates and the sources of the memory cells while the drains float. The voltage difference causes Fowler-Nordheim tunneling that lowers the threshold voltages of the memory cells in the selected sector, to an erased state. Typically, the source decoder applies a positive voltage to the source line 114 or 114′ for a selected sector, and row decoder 120 applies ground or a negative voltage to the row lines associated with the selected sector. For array 110, row lines 112 connect to memory cells in sectors 115 not being erased. Accordingly, erasing the selected sector can disturb the threshold voltages of memory cells in other sectors of the array 110. These disturbances of the threshold voltages (i.e., erase disturbs) can accumulate over time.
Particular problems arise if data remains in some sectors while other sectors of the array are repeatedly erased and programmed. In this case, the accumulated write and erase disturb can change the threshold voltages of memory cells in sectors storing long term data. Such disturbance can become intolerable in a multi-bit-per-cell memory. In a multi-bit-per-cell memory, each memory cell stores N bits of information and requires 2N distinguishable threshold voltage windows corresponding to the possible N-bit values. As N increases, the threshold voltage windows narrow, and the disturbance of the threshold voltages becomes more difficult to accommodate.
Another problem arises because the memory cells in sectors that are erased frequently age differently from memory cells in sectors that are rarely erased. To compensate for aging or endurance effects, a memory can include circuits that adjust erase, write, or read voltages to compensate for the effects of aging. Different types of compensation can be required for different sectors because the memory cells in different sectors have different histories and have aged differently. Some memories incorporate complex circuitry that monitors the number of erase operations for each sector and operates each sector according to its history. U.S. Pat. Nos. 5,172,338 and 5,163,021, entitled “Multi-State EEPROM Read and Write Circuits and Techniques”, describe Flash memory including circuitry that compensates for differences in aging in different sectors. Such circuitry requires extra overhead, increases circuit complexity, and therefore can increase the cost of a Flash memory.
In accordance with the invention, a non-volatile memory uses a data management process or arrangement that is not sector-based. This improves storage efficiency because data blocks can be stored without unused storage cells between data blocks. To erase one or more data block from an array, data blocks from the array that are to be saved are read and stored temporarily in a storage device, such as a main memory or a hard disk drive of a computer system connected to the non-volatile memory. The entire memory array is then erased, and the data blocks from the storage device are rewritten in the memory, with the amount of storage originally allocated to the erased data blocks now being available for new data blocks. This data arrangement does not subject any memory cells to a large accumulated write or erase disturbances because all data is read from the array and freshly re-written back after other data blocks in the array are erased. Thus, the accumulated program disturb is limited to only that accumulated from filling the array with data at most once. Additionally, the separate sectors do not have different endurance histories that must be accounted for to extend the life of the memory. A single count of the number of erase operation performed on an array can control voltages used during erase, write, or read operation to extend the usable life of the memory.
One embodiment of the invention is a method for operating a semiconductor memory such as a multi-bit-per-cell Flash memory. The method includes: storing portions of a plurality of data blocks in an array in the memory; selecting one or more of the data blocks for erasure; reading from the array data from data blocks that are not selected for erasure; erasing the array; and writing into the memory the data read from the array. The data that were read from the array can be stored while erasing the array so that writing into the memory writes at least a portion of the data blocks back into the erased array. The array can be sectorless for simultaneously erasing all memory cells in the array or can be partitioned into separately erasable sectors that are erased in a sequential, parallel, or pipelined manner. To maximize storage utilization, the data blocks are written at consecutive addresses in the array, without regard for boundaries between sectors.
Another embodiment of the invention is a system for storage of data blocks. The system includes a first memory that is a non-volatile semiconductor memory such as a multi-bit-per-cell Flash memory and a computer system connected to the first memory. The computer system can be a personal computer that includes a storage device such as a disk drive and a processor that executes file management procedure. Executing the file management procedure includes: identifying a plurality of data blocks at least partially stored in an array in the first memory; selecting one or more of the data blocks for erasure; reading from the array data from data blocks that are not selected for erasure; storing in the storage device the data read from the array; erasing the array; and writing into the first memory the data from the storage device. In an example application, the data blocks represent music, and the first memory is the memory of a portable player of digitally-encoded music. The file management procedure can write the data from the storage device and data from new data blocks into the erased array. When writing, the data blocks are stored at consecutive physical addresses in the array, without regard for boundaries between sectors.
Yet another embodiment of the invention is a non-volatile memory that includes arrays of memory cells, local circuits, and global circuits. Each array includes row lines, column lines, and a source line, wherein the row lines, the column lines, and the source line of each array are isolated from the row lines, the column lines, and the source line of the other arrays. Each local circuit is associated with and coupled to a corresponding one of the arrays. The local circuits implement erase, write, and read operations in the corresponding array, wherein the erase operation erases all memory cells in the corresponding array. Each local circuit can maintain a single count of the number of erasures of the associated array and can use the count to select voltages used during erase, write, or read operations.
The global circuits connect to and coordinate the local circuits for input and output of data from the memory. To achieve a high bandwidth, the global circuits coordinate the local circuit to simultaneously write a plurality of multi-bit values in a plurality of the arrays and/or coordinate the local circuit to simultaneously read a plurality of multi-bit values from a plurality of the arrays.
FIGS. 1A and 1B are block diagrams of standard architectures for Flash memories.
FIGS. 2A and 2B are block diagrams of embodiments of multi-bit-per-cell Flash memories in accordance with the invention.
FIG. 3 is a block diagram of a storage system in accordance with an embodiment of the invention.
FIG. 4 is a block diagram of a multi-bit-per-cell Flash memory illustrating memory areas storing data files in accordance with an embodiment of the invention.
FIG. 5 is a floor plan for specific multi-bit-per-cell memories in accordance with the invention.
Use of the same reference symbols in different figures indicates similar or identical items.
In accordance with an aspect of the invention, a storage system employing non-volatile Flash memory, erases an entire array instead of individual sectors, and writes back into the memory any data to be retained after the erase. This avoids the possible large accumulated threshold voltage disturbances that are difficult to accommodate in a multi-bit-per-cell memory. The system also maintains a more uniform endurance history for memory cells in the array. Accordingly, the memory can provide higher storage density by permitting smaller margins for threshold voltage disturbances and disparities in aging effects. Additionally, storing data independent of sector boundaries reduces storage inefficiency resulting from unused memory cells between the end of one data block in one sector and the start of the next data block in a following sector.
FIG. 2A shows a multi-bit-per-cell Flash memory 200 in accordance with an embodiment of the invention. Memory 200 includes two memory arrays, a left array 210L and a right array 210R, which share a global row decoder 220. Each array 210L or 210R contains rows and columns of memory cells 216 connected together by row lines 212L or 212R and column lines 213L and 213R. In array 210L, row lines 212L connect to the control gates of memory cells in associated rows, and column lines 213L connect to the drains of memory cells in associated columns. In array 210R, row lines 212R connect to the control gates of memory cells in associated rows, and column lines 213R connect to the drains of memory cells in associated columns. Each memory cell 216 is a non-volatile memory cell and can be implemented, for example, as a floating gate transistor having a control gate coupled to an associated row line 212L or 212R and a drain coupled to an associated column line 213L or 213R.
Global row decoder 220 is between arrays 210L and 210R so that each row line 212R is isolated from the row line 212L corresponding to the same row address. Global row decoder 220 decodes a portion of an address signal to select the array 210L or 210R and the row line 212L or 212R corresponding to the address. A global column decoder 230 decodes another portion of the address signal. Arrays 210L and 210R have respective local column select circuits 232L and 232R that select a column line according to global selection signals from global column decoder 230. Local erase/write/read (E/W/R) circuits 234L and 234R and the isolation of array 210L from array 210R permit each array 210L or 210R to conduct an erase, write, or read operation without affecting the other array 210R or 210L.
In the following, reference numbers 210, 212, 213, 222, 232, and 234 (i.e., without a suffix such as “L” or “R”) generically refer to an array, a row line, a column line, a driver, a local column select circuit, and an E/W/R circuit.
FIG. 2A does not show source lines or divisions of either array 210 into sectors. In one embodiment of the invention, the sources of all memory cells 216 in each array 210 are connected together, and an erase operation simultaneously erases all memory cells in an array 210. Alternatively, if the erase voltage drivers used during an erase operation are insufficient for erasing all of the memory cells in an array 210, each array 210 can be divided into sectors for sequential or pipelined erase operations. As described above, continuous row lines or continuous column lines, depending on whether sectors are column-based or row-based, can extend across the sector of the array. In the embodiment including sectors, the entire array is erased in a series of sector erase processes.
For an exemplary erase operation, global row decoder 220 activates all of the drivers 222 associated with the array 210 being erased. Drivers 222 activated for the erase either ground the attached row lines 212 or bias the attached row lines 212 at a negative voltage, depending on the erase method employed. The source line connected to the memory cells in the array 210 being erased is raised to a positive voltage so that the total voltage difference between the control gates and the sources of the memory cells being erased is between about 10 volts and about 15 volts. The voltage difference or another parameter of the erase operation (e.g., the duration of the erase operation) can be selected according to an erase count 242 that indicates the number times the array was previously erased. The local column select circuit 232 for the array 210 being erased disconnects the associated column lines 213 from any bias voltage, thereby allowing column lines 213 to float during the erase operation. The voltage difference between the control gate and the source of each memory cell being erased causes Fowler-Nordheim tunneling that lowers the threshold voltage of the memory cell to an erased state. While one array 210L or 210R is being erased, the other array 210R or 210L can be independently accessed since there is no continuity between the row, column, or source lines of the separate arrays.
Endurance cycle counters 242L and 242R are incremented every time an erase (or write) operation occurs for corresponding arrays 210L and 210R. The output or content of counters 242L and 242R can be stored in a non-volatile Flash memory that is constantly being updated. One-bit-per-cell storage can be used to ensure reliability, and a portion of the arrays 210L and 210R can be dedicated for this purpose. The cycle counts are read out to a register next to counter 242L and 242R upon every power-up. As described further below, the usable life of the memory 100 can be increased if local E/W/R circuits 234L and 234R use erase, write, and/or read voltages that depend on the count for corresponding arrays 210L and 210R. The overhead required for this improvement in usable life is less than required in a Flash memory in which each individual sector has to maintain an independent endurance history.
After an array 210 has been erased, a write operation can program any selected memory cell in the array, to a threshold voltage level corresponding to a multi-bit value being written. Many different methods for writing a multi-bit value to a memory cell are known and can be implemented in memory 200. The following describes one particular example of a write operation to illustrate some of the issues relevant in the memory architecture of FIG. 2A. Many alternative types of write operations and write circuits could be employed.
To write to a selected memory cell, global row decoder 220 selects and activates a driver 222 connected to a selected row line 212 that is coupled to the control gate of the selected memory cell. The other drivers 222 for the selected array 210 ground the unselected row lines 212. In an exemplary embodiment, the local write/read circuit 234 associated with the selected memory cell receives a data signal representing the multi-bit value being written and provides to the selected driver 222 a programming voltage Vpp (typically between 8 volts and 12 volts) and a verify voltage Vvfy (typically between 2 volts and 6 volts). The levels of programming voltage Vpp and verify voltage Vvfy depend on the multi-bit value being written.
During each of a series of program cycles during the write operation, the activated driver 222 applies programming voltage Vpp to the selected row line 212. The associated local write/read circuit 234 directs the local column select circuit 232 to apply a programming voltage Vw (typically 5 to 6 volts) to the column line that global column decoder 230 identifies. In one embodiment of the invention, the programming voltage Vw is from a variable voltage supply 240 and has a voltage level that depends on the erase count 242 for the array. Unselected column lines 213 in the selected array 210 are grounded, as is the source line for the selected memory cell. The combination of programming voltages Vpp and Vw on the control gate and drain of the selected memory cell causes channel hot electron injection that raises the threshold voltage of the selected memory cell.
During a series of verify cycles, which are between the program cycles during of the write operation, the activated driver 222 applies verify voltage Vvfy to the selected row line 212. The associated local write/read circuit 234 directs the local column select circuit 232 to apply a read voltage Vr (typically about 1 to 1.5 volt) to the selected column line. A sense amplifier (not shown) in the write/read circuit 234L or 234R senses the conductivity of the selected memory cell to determine whether the selected memory cell has reached the target threshold voltage. After the memory cell has reached the target threshold voltage, further program cycles are stopped and the write operation is complete.
As with the write operation, memory 200 can use many alternative methods for reading a multi-bit value from a memory cell. For illustrative purposes, one such read method is addressed. In the exemplary embodiment, the local write/read circuit 234 of the selected array 210 uses a driver 222 that global row decoder 220 activates to vary a voltage on the selected row line. While the voltage on the selected row line 212 varies, a sense amplifier senses the conductivity of the selected memory cell. The row line voltage when the selected memory cell changes conductivity indicates the threshold voltage of the selected memory cell. That row line voltage can then be converted into a multi-bit digital value, which is the result of the read operation.
In general, endurance cycling affects the operation of a conventional non-volatile Flash memory cell such as a stacked-gate cell with ONO (Oxide-Nitride-Oxide) insulator using channel-hot electron injection for writing and Fowler-Nordheim tunneling for erasing. As noted above, electrical erasure is usually done with the control gate biased to either ground or a negative-potential, and the source biased to more than 10 V or to about 5 V, respectively. This creates a large electric field across the tunnel oxide in a direction that causes electrons stored in the floating-gate to tunnel through the thin tunnel oxide to the source. However, depending on the electric field across the source-substrate junction, the source junction profile, and the doping concentration and gradient, band-to-band tunneling current can occur, which causes current to flow from the source to the substrate. This current is undesirable and can generate hot-hole injection directed towards the floating gate. Some of these holes can be trapped in the tunnel oxide. These trapped charges could cause a built-in potential field across the tunnel oxide, which degrades the tunnel oxide and adversely affects the tunneling (erase) process. In other words, as the memory cell ages, the erase time usually stretches out (or increases) if the erase voltage remains the same. This effect combined with the programming degradation as described below causes the well-known, endurance-cycle-induced Vt window closure phenomenon.
One way to achieve the same erased threshold voltage Vt without increasing the erase time is to increase the erase voltage slightly as the count of erase operations increases. Negative-gate erase is preferred over grounded-gate erase, primarily because a negative-gate erase causes less band-to-band tunneling current with a lower source-to-substrate voltage. A negative-gate erase also helps to reduce the need for a large charge-pump to supply the erase current from a greater than 10 V supply. With the negative-gate erase scheme that is commonly used today, the negative-erase voltage on the control gate can be varied as a function of endurance cycle (erase count 242). Conventional voltage regulation and voltage trimming techniques can achieve the necessary voltage variation.
Endurance cycling affects writing in a similar way. During channel-hot electron injection, some of the hot-holes generated by impact ionization near the drain junction can be injected across the oxide barrier and some could be trapped in the tunnel oxide. This slows down the channel-hot electron injection process. Ideally, charge trapping can be avoided by making certain that the memory cell being programmed is biased in a desired operating region so that the drain and gate voltages are optimal (i.e., not too high and not too low) for minimizing hot-hole injection. One way to compensate for charge trapping is to adjust and increase the drain voltage Vw gradually as erase count 242 of endurance cycle increases.
Reading may also be affected by the endurance cycling. As the memory cell ages, the charge-trapping effect can cause the Vt of the memory cell to change, which could be a concern depending on the exact read scheme used. For example, slowly ramping the row line voltage to the threshold voltage of the memory cell and then converting that analog voltage to an N-bit wide data with an A/D converter, without the use of any reference cells, can potentially cause an erroneous read-out as the device ages. This problem can be taken care of by using a read method that employs 2N reference cells and a CAM for comparisons that determine the N-bit wide digital representation of the Vt read from a memory cell. U.S. Pat. No. 6,094,368, entitled “Auto-Tracking Write and Read Processes For Multi-Bit-Per-Cell Non-Volatile Memories”, describes such read methods and is hereby incorporated by reference in its entirety. The concern for errors during a read, may not be as problematic as erase and write errors, since the read process requires lower voltages except for the control gate, and the read operation can use a compensation scheme, for example, using multiple reference cells and a CAM for accurate read-out.
FIG. 2B is a block diagram of multi-bit-per-cell memory 250 in accordance with another embodiment of the invention. Memory 250 contains N memory banks where each bank contains left and right arrays as described above in regard to FIG. 2A. Each memory bank includes elements similar or identical to those described in regard to FIG. 2A. Those elements have the same base reference number as used in FIG. 2A but different suffixes (1L) to (NL) or (1R) to (NR) to identify the associated bank 1 to N and side left (L) or right (R).
Global I/O lines 248 connect to local E/W/R circuits 234(1L) to 234(NL) and 234(1R) to 234 (NR) for data input and output from any of the arrays 210. Global column decoder 230 connects to local column select circuits 232(1L) to 232(NL) and 232(1R) to 232(NR) via global column select lines 238, but the local column lines 213(1) to 213(N) are isolated from each other. Each array 210 has its own E/W/R circuit 234 and row and column lines 212 and 213 that are isolated from other arrays 210 to permit erase, write, or read operations that do not interfere with the operation of the other arrays. Accordingly, each of the arrays 210 can perform write or read operations in parallel. Assuming that arrays 210 are identical, performing write or read operations in parallel can increase the bandwidth of memory 250 by a factor up to 2N (where 2N is the number of independent arrays in N banks) times the bandwidth of a similar memory that writes to or reads from one memory array at a time. The parallel write operations typically result in data from a data block being simultaneously written into multiple memory banks. When multiple arrays are simultaneously written to and erased, a single erase count is sufficient for selection of parameters for erase, write, and read operations as the arrays age.
FIG. 3 is a block diagram of a data storage system 300 in accordance with the invention. The data storage system 300 includes a non-volatile semiconductor memory device 200 such as disclosed in reference to FIG. 2 and a computer system 310. In an exemplary embodiment of data storage system 300, memory device 200 is the memory of a music player that stores a number of songs in a digital format such as MP3 or AC3. When a user decides to change the songs stored in memory device 200, the user connects memory device 200 to computer system 310 using a suitable computer interface or port such as a universal serial bus (USB). The computer system 310 can be any system having a processor (CPU) 320 and a storage device 330 adequate for execution of file management software 340 and storage of data files. In an exemplary embodiment, computer system 310 is a personal computer, and storage device 330 includes the main memory of the personal computer, a hard disk drive, or other media for storage of digital data.
After connecting memory device 200 to computer system 310, the user starts and uses file management software 340 interactively via I/O devices such as the monitor, mouse, and keyboard of computer system 310. In particular, the user selects from the data files in memory device 200, any data files (e.g., songs) that the user wants to delete. File management software 340 then identifies the array or arrays containing data files to be deleted, reads any old data files that are not being deleted, and saves old data files 332 in storage device 330. Alternatively, file management software 340 can read the entire array or arrays, including the data blocks to be erased, and then separate the data to be erased from the data to be saved. As another alternative, the data to be saved can be directly stored elsewhere in memory device 200, for example, in other arrays that have available storage or in an on-chip buffer (not shown).
After the data to be saved has been read from the array, file management software 340 directs memory device 200 to erase each array containing at least a portion of a deleted data file. As noted above, all of the memory cells in an array can be simultaneously erased, or the entire array can be erased a sector at a time. File management software 340 permits the user to select new data files for storage in memory device 200. For example, a user can select an MP3 file from a library in storage device 330 or download a new MP3 file from the Internet into storage device 330. Storage device 330 stores new data files 334 and old data files 332, and the user selects which of the old and new data files to transfer to memory device 200.
When memory device 200 has space available for an old data file 332 and/or a new data file 334 (e.g., after erasing an array), file management software 340 can write one or more data files to the available space. Each data file can be written into the freshly erased array or into other available storage space in memory device 200. The data files can be stored without regard for sector boundaries (if any) in memory device 200. Storage for one data file can start at a physical address immediately following the last address used for another data file. Accordingly, data storage is not wasted by memory cells that remain unused in a last sector storing part of a data file. A directory can record information regarding the data files including, for example, a start address and a file length or stop address for each data file.
For a music player, the time for transferring the content of entire arrays between memory 200 and computer system 310 is relatively insignificant when compared to the time required for other operations involved in the manipulation of music files. For a data rate of 12 Mbits/sec, which is the maximum USB 1.1 data rate, memory 200 requires about 44 seconds to transfer 64 Mbytes of data (the equivalent of one hour of music represented in MP3 format). This data rate can be achieved using multiple banks of memory cells such as illustrated in FIG. 2B. For example, if each array 210 stores four bits per memory cell, the programming or setting of a threshold voltage must be accurate to within about 25 mV, and a worst case write or read time between 1 μs and 5 μs can be achieved. Table 1 indicates the effective bandwidth with different numbers of banks operating in parallel and different worst-case write times.
Effective Write or Read Bandwidth @ 4 Bits/Cell
Write or Read Time to Achieve 25 mV Vt Resolution
For example, with a 2-μs, worst-case access time and four bits per cell, accessing eight memory cells in parallel proves a 16.0 Mbit/sec bandwidth (which is greater than the maximum USB 1.1 data rate.
FIG. 4 shows a layout of a 256-Mbit memory 400 in accordance with a specific example of the architecture illustrated in FIG. 2B. Memory 400 includes eight banks including left arrays 210(1L) to 210(8L) and right arrays 210(1R) to 210(8R). Each of 16 arrays 210(1L) to 210(8L) and 210(1R) to 210(8R) contains 4 Meg cells (4×1024×1024 cells), and each memory cell stores 4-bits of data. In memory 400, an erase operation can simultaneously erase a selected number of arrays or an entire array of memory cells. A write operation simultaneously writes eight 4-bit values (i.e., 32 bits of data) or one memory cell in each of the eight arrays associated with either the first four banks 1 to 4 or the second four banks 5 to 8. Similarly, a read operation simultaneously reads eight 4-bit values (i.e., 32 bits of data) or one memory cell in each of the eight arrays associated with either the first four banks 1 to 4 or the second four banks 5 to 8.
For memory 400, all or the arrays 210 in the four banks are erased together (serially, in pipelined manner, or in parallel), and two erase counts (one for banks 1 to 4 and one for banks 5 to 8) are sufficient to indicate the endurance state of memory 400. Accordingly, variation of erase, program, and read parameters can be on a large scale that requires less overhead than required for known Flash memories.
FIG. 4 further illustrates the allocation of available storage when storing eleven files of different lengths F1 to F11 in memory 400. The first file F1 is stored beginning at an address 0 which is associated with a 32-bit value stored in eight memory cells, one in each of arrays 210(1L) to 210(4L) and 210(1R) to 210(4R). Storage for file F2 begins with an address immediately following the last address used for file F1. Accordingly, there are no unused memory cells between the end of file F1 and the start of file F2. The other files F3 to F11 are stored in the same manner at consecutive addresses so that no unused memory cells are left between files. The boundaries of files are independent of sector boundaries (if any) within arrays 210. The boundaries between files F3 and F4, files F7 and F8, files F8 and F9, and files F10 and F11 particularly illustrate that the end of a file and the start of a next file can be in the middle of a column line. Unused memory cells remain at addresses following the last file F11 but can be used for another file if the file is small enough to fit in the available space.
FIG. 5 illustrates a layout of a 256-Mbit memory 500 in accordance with an embodiment of the invention including more than one global row decoder 520A and 520B. Memory 500 includes 32 arrays (1,1) through (8,4) arranged in eight rows and four columns. The first two columns of arrays share global row decoder 520A and the second two columns share the second global row decoder 520B. Each array contains 2 Meg cells and stores four bits of data per memory cell. In memory 500, an erase operation can simultaneously erase a selected number of arrays or an entire array of memory cells. A write operation simultaneously writes eight 4-bit values (i.e., 32 bits of data) in the eight arrays associated with two banks of four arrays each. A read operation simultaneously reads eight 4-bit values (i.e., 32 bits of data) in the eight arrays. Memory 500 can implement an endurance enhancement scheme using four erase counts to characterize the endurance state of memory 500.
Although the invention has been described with reference to particular embodiments, the description is only an example of the invention's application and should not be taken as a limitation. In particular, although the above described embodiments concentrated on multi-bit-per-cell memories, the invention can also employ conventional binary memory that store only a single bit in each memory cell. Additionally, the array arrangements in the memories disclosed above are merely examples of possible arrangements. More generally, a memory can employ any number of rows and columns of arrays with suitable global and local circuits. Further, the preceding discussion was aimed at conventional N-channel non-volatile memory devices and described operations and threshold voltages appropriate for N-channel non-volatile memory devices. Alternative embodiments of this invention include other types of device such as P-channel non-volatile memory devices to the extent that those devices are suitable for non-volatile memory. Various other adaptations and combinations of features of the embodiments disclosed are within the scope of the invention as defined by the following claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4558431||Dec 12, 1983||Dec 10, 1985||Nec Corporation||Memory system for storing analog information|
|US4964079||Apr 24, 1989||Oct 16, 1990||Sgs-Thomson Microelectronics||Electrically programmable memory with several information bits per cell|
|US5031147||Jul 17, 1989||Jul 9, 1991||Kabushiki Kaisha Toshiba||Semiconductor memory|
|US5043940||Jul 17, 1989||Aug 27, 1991||Eliyahou Harari||Flash EEPROM memory systems having multistate storage cells|
|US5095344||Jun 8, 1988||Mar 10, 1992||Eliyahou Harari||Highly compact eprom and flash eeprom devices|
|US5172338||Apr 11, 1990||Dec 15, 1992||Sundisk Corporation||Multi-state EEprom read and write circuits and techniques|
|US5239505||Dec 28, 1990||Aug 24, 1993||Intel Corporation||Floating gate non-volatile memory with blocks and memory refresh|
|US5249158||Feb 11, 1991||Sep 28, 1993||Intel Corporation||Flash memory blocking architecture|
|US5293560||Nov 3, 1992||Mar 8, 1994||Eliyahou Harari||Multi-state flash EEPROM system using incremental programing and erasing methods|
|US5293563||Dec 12, 1991||Mar 8, 1994||Sharp Kabushiki Kaisha||Multi-level memory cell with increased read-out margin|
|US5303198 *||Jul 5, 1991||Apr 12, 1994||Fuji Photo Film Co., Ltd.||Method of recording data in memory card having EEPROM and memory card system using the same|
|US5343063||Dec 18, 1990||Aug 30, 1994||Sundisk Corporation||Dense vertical programmable read only memory cell structure and processes for making them|
|US5371702||Mar 5, 1993||Dec 6, 1994||Kabushiki Kaisha Toshiba||Block erasable nonvolatile memory device|
|US5379413 *||Jun 19, 1992||Jan 3, 1995||Intel Corporation||User selectable word/byte input architecture for flash EEPROM memory write and erase operations|
|US5399891||Jan 25, 1994||Mar 21, 1995||Macronix International Co., Ltd.||Floating gate or flash EPROM transistor array having contactless source and drain diffusions|
|US5418752||Oct 20, 1992||May 23, 1995||Sundisk Corporation||Flash EEPROM system with erase sector select|
|US5526307||Sep 13, 1994||Jun 11, 1996||Macronix International Co., Ltd.||Flash EPROM integrated circuit architecture|
|US5583812||Feb 16, 1995||Dec 10, 1996||Harari; Eliyahou||Flash EEPROM system cell array with more than two storage states per memory cell|
|US5592669||Dec 1, 1995||Jan 7, 1997||Intel Corporation||File structure for a non-volatile block-erasable semiconductor flash memory|
|US5638320||Jan 11, 1996||Jun 10, 1997||Invoice Technology, Inc.||High resolution analog storage EPROM and flash EPROM|
|US5642312||May 22, 1996||Jun 24, 1997||Harari; Eliyahou||Flash EEPROM system cell array with more than two storage states per memory cell|
|US5680341||Jan 16, 1996||Oct 21, 1997||Invoice Technology||Pipelined record and playback for analog non-volatile memory|
|US5682497||Apr 8, 1996||Oct 28, 1997||Intel Corporation||Managing file structures for a flash memory file system in a computer|
|US5691938||May 3, 1994||Nov 25, 1997||Macronix International Co., Ltd.||Non-volatile memory cell and array architecture|
|US5694357||May 15, 1996||Dec 2, 1997||Kabushiki Kaisha Toshiba||Nonvolatile semiconductor memory device for storing multi-value data|
|US5712740||Feb 26, 1996||Jan 27, 1998||Sony Corporation||Method for reducing wasted storage space when storing multiple data blocks on a storage medium|
|US5717632||Nov 27, 1996||Feb 10, 1998||Advanced Micro Devices, Inc.||Apparatus and method for multiple-level storage in non-volatile memories|
|US5717636 *||May 3, 1996||Feb 10, 1998||Sgs-Thomson Microelectronics S.R.L.||EEPROM memory with contactless memory cells|
|US5742934||Mar 11, 1996||Apr 21, 1998||Mitsubishi Denki Kabushiki Kaisha||Flash solid state disk card with selective use of an address conversion table depending on logical and physical sector numbers|
|US5745409||Sep 28, 1995||Apr 28, 1998||Invox Technology||Non-volatile memory with analog and digital interface and storage|
|US5748528||May 3, 1996||May 5, 1998||Sgs-Thomson Microelectronics S.R.L.||EEPROM memory device with simultaneous read and write sector capabilities|
|US5751634||May 15, 1996||May 12, 1998||Kabushiki Kaisha Toshiba||Non-volatile semiconductor memory device for storing multivalue data and readout/write-in method therefor|
|US5768192||Jul 23, 1996||Jun 16, 1998||Saifun Semiconductors, Ltd.||Non-volatile semiconductor memory cell utilizing asymmetrical charge trapping|
|US5781921 *||May 6, 1996||Jul 14, 1998||Ohmeda Inc.||Method and apparatus to effect firmware upgrades using a removable memory device under software control|
|US5801994||Aug 15, 1997||Sep 1, 1998||Programmable Microelectronics Corporation||Non-volatile memory array architecture|
|US5802553||Dec 19, 1995||Sep 1, 1998||Intel Corporation||File system configured to support variable density storage and data compression within a nonvolatile memory|
|US5822781||Oct 30, 1992||Oct 13, 1998||Intel Corporation||Sector-based storage device emulator having variable-sized sector|
|US5848019 *||Aug 29, 1997||Dec 8, 1998||Integrated Device Technology, Inc.||Pass gate decoder for a multiport memory dEvice that uses a single ported memory cell array structure|
|US5880993||Sep 30, 1997||Mar 9, 1999||Sgs-Thomson Microelectronics, S.R.L.||Method and circuit for checking multilevel programming of floating-gate nonvolatile memory cells particularly flash cells|
|US5886923 *||Oct 27, 1997||Mar 23, 1999||Integrated Silicon Solution Inc.||Local row decoder for sector-erase fowler-nordheim tunneling based flash memory|
|US5892715 *||Jul 7, 1997||Apr 6, 1999||Nec Corporation||Non-volatile semiconductor memory device with variable source voltage|
|US5896340||Jul 7, 1997||Apr 20, 1999||Invox Technology||Multiple array architecture for analog or multi-bit-cell memory|
|US5896393 *||May 23, 1996||Apr 20, 1999||Advanced Micro Devices, Inc.||Simplified file management scheme for flash memory|
|US5905993||Apr 9, 1997||May 18, 1999||Mitsubishi Denki Kabushiki Kaisha||Flash memory card with block memory address arrangement|
|US5909387||Jun 2, 1997||Jun 1, 1999||Invox Technology||Memory architecture for recording of multiple messages|
|US5909390||Dec 16, 1997||Jun 1, 1999||Harari; Eliyahou||Techniques of programming and erasing an array of multi-state flash EEPROM cells including comparing the states of the cells to desired values|
|US5909449||Sep 8, 1997||Jun 1, 1999||Invox Technology||Multibit-per-cell non-volatile memory with error detection and correction|
|US5936887||Aug 12, 1997||Aug 10, 1999||Samsung Electronics Co., Ltd.||Non-volatile memory device with NAND type cell structure|
|US5946714||Apr 16, 1997||Aug 31, 1999||Mitsubishi Denki Kabushiki Kaisha||Semiconductor storage device utilizing address management tables and table state maps for managing data storage and retrieval|
|US5962890||Apr 30, 1997||Oct 5, 1999||Sharp Kabushiki Kaisha||Non-volatile semiconductor memory|
|US5963465||Dec 12, 1997||Oct 5, 1999||Saifun Semiconductors, Ltd.||Symmetric segmented memory array architecture|
|US5970012||Sep 30, 1997||Oct 19, 1999||Nec Corporation||Non-volatile semiconductor memory device having a memory cell capable of establishing multi-level information and data writing method thereof|
|US5973958||Jun 23, 1998||Oct 26, 1999||Advanced Micro Devices, Inc.||Interlaced storage and sense technique for flash multi-level devices|
|US5987478||Oct 31, 1995||Nov 16, 1999||Intel Corporation||Virtual small block file manager for flash memory array|
|US5999445||Aug 22, 1997||Dec 7, 1999||Sgs-Thomson Microelectronics S.R.L.||Multilevel non-volatile memory devices|
|US5999446||Dec 29, 1997||Dec 7, 1999||Sandisk Corporation||Multi-state flash EEprom system with selective multi-sector erase|
|US6002614||Nov 21, 1997||Dec 14, 1999||Btg International Inc.||Memory apparatus including programmable non-volatile multi-bit memory cell, and apparatus and method for demarcating memory states of the cell|
|US6005803||Sep 23, 1998||Dec 21, 1999||Advanced Micro Devices, Inc.||Memory address decoding circuit for a simultaneous operation flash memory device with a flexible bank partition architecture|
|US6038636 *||Apr 27, 1998||Mar 14, 2000||Lexmark International, Inc.||Method and apparatus for reclaiming and defragmenting a flash memory device|
|US6055181||Aug 7, 1998||Apr 25, 2000||Kabushiki Kaisha Toshiba||Nonvolatile semiconductor memory device capable of storing multi-value data of more than one bit in a memory cell|
|US6088264||Jan 5, 1998||Jul 11, 2000||Intel Corporation||Flash memory partitioning for read-while-write operation|
|US6091633||Aug 9, 1999||Jul 18, 2000||Sandisk Corporation||Memory array architecture utilizing global bit lines shared by multiple cells|
|US6097637||Sep 10, 1996||Aug 1, 2000||Intel Corporation||Dynamic single bit per cell to multiple bit per cell memory|
|US6122193||Jun 1, 1999||Sep 19, 2000||Kabushiki Kaisha Toshiba||Non-volatile semiconductor memory capable of storing 1-bit data or multi-bit data|
|US6130841||Nov 2, 1999||Oct 10, 2000||Hitachi, Ltd.||Semiconductor nonvolatile memory apparatus and computer system using the same|
|US6134145||Aug 3, 1998||Oct 17, 2000||Sandisk Corporation||High data rate write process for non-volatile flash memories|
|US6137719||Nov 1, 1999||Oct 24, 2000||Mitsubishi Denki Kabushiki Kaisha||Nonvolatile semiconductor memory device storing multi-bit data|
|US6149316||Jan 29, 1997||Nov 21, 2000||Sandisk Corporation||Flash EEprom system|
|US6151246 *||Nov 25, 1998||Nov 21, 2000||Sandisk Corporation||Multi-bit-per-cell flash EEPROM memory with refresh|
|US6166407||Aug 24, 1998||Dec 26, 2000||Sharp Kabushiki Kaisha||Non-volatile semiconductor memory device|
|US6166959||Apr 13, 2000||Dec 26, 2000||Atmel Corporation||Flash memory array with internal refresh|
|US6181597||Feb 4, 1999||Jan 30, 2001||Tower Semiconductor Ltd.||EEPROM array using 2-bit non-volatile memory cells with serial read operations|
|US6198648||Nov 29, 1999||Mar 6, 2001||Sharp Kabushiki Kaisha||Semiconductor memory device with hierarchical bit line architecture|
|US6212121||Nov 30, 1999||Apr 3, 2001||Samsung Electronics Co., Ltd.||Semiconductor memory device with multiple sub-arrays of different sizes|
|US6229734||Mar 20, 2000||May 8, 2001||Nec Corporation||Nonvolatile semiconductor storage device having controlled cell threshold voltage distribution|
|US6232632||Nov 9, 1999||May 15, 2001||Advanced Micro Devices, Inc.||Double density non-volatile memory cells|
|US6240032||Nov 25, 1998||May 29, 2001||Sharp Kabushiki Kaisha||Non-volatile semiconductor memory allowing user to enter various refresh commands|
|US6256231||Feb 4, 1999||Jul 3, 2001||Tower Semiconductor Ltd.||EEPROM array using 2-bit non-volatile memory cells and method of implementing same|
|US6259627||Jan 27, 2000||Jul 10, 2001||Multi Level Memory Technology||Read and write operations using constant row line voltage and variable column line load|
|US6285574||Jul 6, 1999||Sep 4, 2001||Saifun Semiconductors Ltd.||Symmetric segmented memory array architecture|
|US6292392||Sep 30, 1998||Sep 18, 2001||Sharp Kabushiki Kaisha||Non-volatile semiconductor device|
|US6301154||Feb 3, 2000||Oct 9, 2001||Sharp Kabushiki Kaisha||Semiconductor memory device having floating gate type transistors programmed to have differing threshold voltages|
|US6317363||Oct 13, 2000||Nov 13, 2001||Sandisk Corporation||Multi-state memory|
|US6330185||Jan 23, 2001||Dec 11, 2001||Multi Level Memory Technology||High bandwidth multi-level flash memory using dummy memory accesses to improve precision when writing or reading a data stream|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7512015||Jul 17, 2006||Mar 31, 2009||Lattice Semiconductor Corporation||Negative voltage blocking for embedded memories|
|US7636259||Jul 17, 2006||Dec 22, 2009||Lallice Semiconductor Corporation||Flash memory array with independently erasable sectors|
|US7640389 *||Feb 28, 2006||Dec 29, 2009||Freescale Semiconductor, Inc.||Non-volatile memory having a multiple block erase mode and method therefor|
|US7643341 *||Feb 28, 2007||Jan 5, 2010||Infineon Technologies Ag||Integrated circuit having a memory arrangement|
|US7817469 *||Aug 18, 2005||Oct 19, 2010||Sandisk Il Ltd.||Drift compensation in a flash memory|
|US7843951 *||Nov 11, 2003||Nov 30, 2010||Rambus Inc.||Packet storage system for traffic handling|
|US7936610||Aug 3, 2009||May 3, 2011||Micron Technology, Inc.||Selective refresh of single bit memory cells|
|US7957189||Nov 2, 2006||Jun 7, 2011||Sandisk Il Ltd.||Drift compensation in a flash memory|
|US7961506||Feb 5, 2008||Jun 14, 2011||Micron Technology, Inc.||Multiple memory cells with rectifying device|
|US8332696 *||Dec 27, 2007||Dec 11, 2012||Industrial Technology Research Institute||Defect management method for storage medium and system thereof|
|US8363447 *||Dec 11, 2008||Jan 29, 2013||Sony Corporation||Storage device and information recording and verification method|
|US8472457||Nov 29, 2010||Jun 25, 2013||Rambus Inc.||Method and apparatus for queuing variable size data packets in a communication system|
|US8601202||Aug 26, 2009||Dec 3, 2013||Micron Technology, Inc.||Full chip wear leveling in memory device|
|US8625346||Aug 19, 2011||Jan 7, 2014||Round Rock Research, Llc||Multiple level cell memory device with single bit per cell, re-mappable memory block|
|US8665645||Mar 28, 2011||Mar 4, 2014||Sandisk Il Ltd.||Drift compensation in a flash memory|
|US8854884 *||May 9, 2012||Oct 7, 2014||Conversant Intellectual Property Management Inc.||NAND flash architecture with multi-level row decoding|
|US8947923||Jun 13, 2011||Feb 3, 2015||Micro Technology, Inc.||Memory cells with rectifying device|
|US9201730||Dec 24, 2013||Dec 1, 2015||Round Rock Research, Llc||Multiple level cell memory device with single bit per cell, re-mappable memory block|
|US20050243829 *||Nov 11, 2003||Nov 3, 2005||Clearspeed Technology Pic||Traffic management architecture|
|US20050265368 *||Nov 11, 2003||Dec 1, 2005||Anthony Spencer||Packet storage system for traffic handling|
|US20060028875 *||Aug 18, 2005||Feb 9, 2006||M-Systems Flash Disk Pioneers, Ltd.||Drift compensation in a flash memory|
|US20070070696 *||Nov 2, 2006||Mar 29, 2007||Msystems Ltd||Drift compensation in a flash memory|
|US20070204098 *||Feb 28, 2006||Aug 30, 2007||Eguchi Richard K||Non-volatile memory having a multiple block erase mode and method therefor|
|US20070223284 *||Feb 28, 2007||Sep 27, 2007||Infineon Technologies Ag||Integrated circuit having a memory arrangement|
|US20090044085 *||Dec 27, 2007||Feb 12, 2009||Industrial Technology Research Institute||Defect management method for storage medium and system thereof|
|US20090073769 *||Jun 29, 2008||Mar 19, 2009||Sandisk Il Ltd.||Method and system for optimizing reliability and performance of programming data in non-volatile memory devices|
|US20090196095 *||Feb 5, 2008||Aug 6, 2009||Micron Technology, Inc.||Multiple memory cells and method|
|US20100254178 *||Dec 11, 2008||Oct 7, 2010||Sony Corporation||Storage device and information re-recording method|
|US20110069716 *||Mar 24, 2011||Anthony Spencer||Method and apparatus for queuing variable size data packets in a communication system|
|US20110170349 *||Jul 14, 2011||Meir Avraham||Drift compensation in a flash memory|
|US20120057406 *||Sep 2, 2010||Mar 8, 2012||Eon Silicon Solution Inc.||Flash memory apparatus|
|US20120218829 *||May 9, 2012||Aug 30, 2012||Mosaid Technologies Incorporated||Nand flash architecture with multi-level row decoding|
|WO2006048860A2 *||Oct 26, 2005||May 11, 2006||Meir Avraham||Drift compensation in a flash memory|
|U.S. Classification||711/103, 365/185.33, 365/185.29, 711/E12.008, 365/189.04, 365/230.03, 365/185.11, 711/165, 365/185.13, 365/230.06|
|International Classification||G11C5/02, G11C16/34, G06F12/00, G11C11/56, G11C8/18, G06F12/02|
|Cooperative Classification||G11C11/5621, G11C16/349, G11C11/56, G06F12/0246, G11C5/025, G11C8/18|
|European Classification||G11C11/56D, G11C16/34W, G11C5/02S, G11C8/18, G06F12/02D2E2, G11C11/56|
|Mar 3, 2000||AS||Assignment|
Owner name: MULTI LEVEL MEMORY TECHNOLOGY, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WONG, SAU C.;REEL/FRAME:010664/0426
Effective date: 20000302
|Jul 28, 2005||AS||Assignment|
Owner name: MULTI LEVEL MEMORY TECHNOLOGY (NEVADA), NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MULTI LEVEL MEMORY TECHNOLOGY (CALIFORNIA);REEL/FRAME:016800/0640
Effective date: 20050720
|Aug 24, 2005||AS||Assignment|
Owner name: INTERNATIONAL DEVELOPMENT AND LICENSING, CALIFORNI
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MULTI LEVEL MEMORY TECHNOLOGY;REEL/FRAME:017176/0517
Effective date: 20050802
|Feb 3, 2006||AS||Assignment|
Owner name: SAMSUNG ELECTRONICS CO., LTD., KOREA, REPUBLIC OF
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTERNATIONAL DEVELOPMENT AND LICENSING;REEL/FRAME:017230/0319
Effective date: 20050804
|May 18, 2007||FPAY||Fee payment|
Year of fee payment: 4
|May 31, 2011||FPAY||Fee payment|
Year of fee payment: 8
|May 29, 2015||FPAY||Fee payment|
Year of fee payment: 12