Skip to content

Patent drawings

Drawing 1 of 4

US 7,080,192

Drawing 1 of 4

Expanded drawing 1 of 4 from US 7,080,192, File storage and erasure in flash memory
High-resolution patent drawing

US 7,080,192

File storage and erasure in flash memory

Filed
October 2, 2003
Granted
July 18, 2006
Assignee
Samsung
Inventors
Sau C. Wong

Abstract

A non-volatile, multi-bit-per-cell, Flash memory uses a storage process and/or architecture that is not sector-based. A data block can be stored without unused storage cells remaining in the last sector that stores part of the data block. For an operation erasing one or more data blocks, data blocks to be saved are read from an array and stored temporarily in a storage device. The entire array is then erased, after which the saved data blocks are rewritten in the memory with the amount of storage originally allocated to the erased data now being available for new data. This data arrangement does not subject any memory cells to a large accumulated cell disturbance because all data is read from the array and freshly re-written back into the array every time a record operation occurs. Additionally, the separate sectors in the memory device do not have different endurance histories that must be accounted for to extend the life of the memory. A single erase count for an array can be used in selection of operating parameters such as voltages used during accesses of memory cells in the array.

View on Google Patents ↗
View Full PatentComplete archived record · 4 figures · 50 description paragraphs · 1 tables · 20 claims

Patent record

Source
Google Patents
Publication
US7080192B1
Application
US10/678,885
Priority
March 3, 2000
Prior art date
March 3, 2000
Publication date
July 18, 2006
Legal status
Expired - Lifetime
Original assignee
Samsung Electronics Co Ltd
Current assignee
Samsung Electronics Co Ltd
Prior art keywords
array, data, memory, erasing, data blocks
Source retrieved
July 20, 2026

Classifications

  • 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/34Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
  • G11C16/349Arrangements for evaluating degradation, retention or wearout, e.g. by counting erase cycles
  • G06COMPUTING OR CALCULATING; COUNTING
  • G06FELECTRIC DIGITAL DATA PROCESSING
  • G06F12/00Accessing, addressing or allocating within memory systems or architectures
  • G06F12/02Addressing or allocation; Relocation
  • G06F12/0223User address space allocation, e.g. contiguous or non contiguous base addressing
  • G06F12/023Free address space management
  • G06F12/0238Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
  • G06F12/0246Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
  • G11C11/00Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor
  • G11C11/56Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor using storage elements with more than two stable states represented by steps, e.g. of voltage, current, phase, frequency
  • G11C11/5621Digital stores characterised by the use of particular electric or magnetic storage elements; Storage elements therefor using storage elements with more than two stable states represented by steps, e.g. of voltage, current, phase, frequency using charge storage in a floating gate
  • G11C5/00Details of stores covered by group G11C11/00
  • G11C5/02Disposition of storage elements, e.g. in the form of a matrix array
  • G11C5/025Geometric lay-out considerations of storage- and peripheral-blocks in a semiconductor storage device
  • G11C8/00Arrangements for selecting an address in a digital store
  • G11C8/18Address timing or clocking circuits; Address control signal generation or management, e.g. for row address strobe [RAS] or column address strobe [CAS] signals

Figures

4 plates

Figure 1 of 4 from US 7,080,192, File storage and erasure in flash memory
Figure 01Full resolution ↗
Figure 2 of 4 from US 7,080,192, File storage and erasure in flash memory
Figure 02Full resolution ↗
Figure 3 of 4 from US 7,080,192, File storage and erasure in flash memory
Figure 03Full resolution ↗
Figure 4 of 4 from US 7,080,192, File storage and erasure in flash memory
Figure 04Full resolution ↗

Description

This patent document is a continuation and claims benefit of the earlier filing date of U.S. patent application Ser. No. 09/518,608, filed Mar. 3, 2000, now U.S. Pat. No. 6,662,263 which is hereby incorporated by reference in its entirety.

BACKGROUND

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 cells and has 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 1.15 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.

SUMMARY

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.

BRIEF DESCRIPTION OF THE DRAWINGS

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.

DETAILED DESCRIPTION

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. 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.

TABLE 1Effective Write or Read Bandwidth @ 4 Bits/Cell
Cells Written
or ReadWrite or Read Time to Achieve 25 mV Vt Resolution
in Parallel1 μs2 μs3 μs4 μs5 μs
14Mbps2Mbps1.3Mbps1Mbps0.8Mbps
416Mbps8Mbps5.3Mbps4Mbps3.2Mbps
832Mbps16Mbps10.6Mbps8Mbps6.4Mbps
1248Mbps24Mbps16.0Mbps12Mbps9.6Mbps
1664Mbps32Mbps21.3Mbps16Mbps12.8Mbps
2496Mbps48Mbps31.9Mbps24Mbps19.2Mbps
32128Mbps64Mbps42.6Mbps32Mbps25.6Mbps
48192Mbps96Mbps63.8Mbps48Mbps38.4Mbps
64256Mbps128Mbps85.1Mbps64Mbps51.2Mbps

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.

Claims (20)

  1. A method for operating a semiconductor memory, comprising: storing at least a portion of each of a plurality of data blocks in a physical array in the memory; selecting one or more of the data blocks for erasure; reading first data from the physical array, wherein the first data comprises all data from blocks other than the data blocks selected for erasure; erasing the entire physical array, wherein erasing begins after reading the first data; and writing the first data back into the physical array after erasing the entire physical array.
  2. The method of claim 1, further comprising storing the first data in temporary storage while erasing the physical array, wherein the temporary storage is external to the semiconductor memory.
  3. The method of claim 1, wherein erasing the physical array comprises simultaneously erasing all memory cells in the physical array.
  4. The method of claim 1, wherein the physical array is partitioned into a plurality of separately erasable sectors, and erasing the entire physical array comprises erasing all of the sectors.
  5. The method of claim 4, wherein the sectors are sequentially erased.
  6. The method of claim 4, wherein the writing comprises writing data from different data blocks at consecutive addresses in the physical array, without regard for boundaries between sectors.
  7. The method of claim 1, wherein further comprises writing data from one or more new data blocks into the erased physical array.
  8. The method of claim 1, wherein the memory is a Flash memory.
  9. The method of claim 1, wherein the physical array contains multi-bit-per-cell memory cells.
  10. The method of claim 1, wherein reading data from at least a portion of the physical array, comprises reading all data stored in the physical array, including second data that is the one or more data blocks selected for erasure.
  11. The method of claim 1, further comprising: maintaining a count indicating a number of erase operations performed on the physical array; and selecting parameters for operation of the physical array, the parameters being selected according to the count.
  12. A system for storage of data blocks, comprising: a first memory that is a non-volatile semiconductor memory; and a computer system connected to the first memory, the computer system comprising a storage device, and a processor that executes file management procedure, wherein execution of the file management procedure comprises: identifying a plurality of data blocks at least partly stored in an array in the first memory; selecting one or more of the data blocks for erasure; reading from the array data corresponding to all of the data blocks that are not selected for erasure; storing in the storage device, the data read from the array; erasing the array in entirety; and writing into the first memory, the data from the storage device.
  13. The system of claim 12, wherein the data blocks are files representing music, and the first memory is a memory of a player of the music.
  14. The system of claim 13, wherein the computer system is a personal computer.
  15. The system of claim 12, wherein the file management procedure writes the data blocks from the storage device into the erased array.
  16. The system of claim 15, wherein the file management procedure further comprises writing new data into the erased array.
  17. The system of claim 12, wherein erasing the array comprises simultaneously erasing all memory cells in the array.
  18. The system of claim 12, wherein the array is partitioned into a plurality of separately erasable sectors, and erasing the array comprises erasing all of the sectors.
  19. The system of claim 18, wherein the sectors are sequentially erased.
  20. The system of claim 18, wherein the writing comprises writing data from different data blocks at consecutive addresses in the array, without regard for boundaries between sectors.

Publications

Related applications (7)

  1. US10/678,885

    Priority application

  2. US09/518,608

    Claims priority

  3. US10/678,885

    Claims priority

  4. US09/518,608

    Parent application

    Sectorless flash memory architecture

    Continuation · Filed March 3, 2000

  5. US09/518,608

    Patent family

  6. US10/678,885

    Patent family

  7. US09/518,608

    Earlier family application

Record timeline

  1. Application filed by Samsung Electronics Co Ltd

  2. Priority to US10/678,885

  3. Assigned to MULTI LEVEL MEMORY TECHNOLOGY (NEVADA)

  4. Assigned to INTERNATIONAL DEVELOPMENT AND LICENSING

  5. Assigned to SAMSUNG ELECTRONICS CO., LTD.

  6. Application granted

  7. Publication of US7080192B1

  8. Anticipated expiration

  9. Expired - LifetimeCurrent

Legal events

  1. 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

  2. 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

  3. FEPP

    Fee payment procedure

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

  4. 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

  5. STCF

    Information on status: patent grant

    Free format text: PATENTED CASE

  6. FEPP

    Fee payment procedure

    Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

  7. FEPP

    Fee payment procedure

    Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

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

  8. FPAY

    Fee payment

    Year of fee payment: 4

  9. FPAY

    Fee payment

    Year of fee payment: 8

  10. MAFP

    Maintenance fee payment

    Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553)

    Year of fee payment: 12

Patent citations (87)

  1. US4558431A

    Memory system for storing analog information

    Nec Corporation · December 10, 1985

  2. US4964079A

    Electrically programmable memory with several information bits per cell

    Sgs-Thomson Microelectronics · October 16, 1990

  3. US5909390A

    Techniques of programming and erasing an array of multi-state flash EEPROM cells including comparing the states of the cells to desired values

    Harari; Eliyahou · June 1, 1999

  4. US5043940A

    Flash EEPROM memory systems having multistate storage cells

    Eliyahou Harari · August 27, 1991

  5. US5095344A

    Highly compact eprom and flash eeprom devices

    Eliyahou Harari · March 10, 1992

  6. US5642312A

    Flash EEPROM system cell array with more than two storage states per memory cell

    Harari; Eliyahou · June 24, 1997

  7. US5583812A

    Flash EEPROM system cell array with more than two storage states per memory cell

    Harari; Eliyahou · December 10, 1996

  8. US5293560A

    Multi-state flash EEPROM system using incremental programing and erasing methods

    Eliyahou Harari · March 8, 1994

  9. US5031147A

    Semiconductor memory

    Kabushiki Kaisha Toshiba · July 9, 1991

  10. US5293563A

    Multi-level memory cell with increased read-out margin

    Sharp Kabushiki Kaisha · March 8, 1994

  11. US5418752A

    Flash EEPROM system with erase sector select

    Sundisk Corporation · May 23, 1995

  12. US5999446A

    Multi-state flash EEprom system with selective multi-sector erase

    Sandisk Corporation · December 7, 1999

  13. US6149316A

    Flash EEprom system

    Sandisk Corporation · November 21, 2000

  14. US5172338A

    Multi-state EEprom read and write circuits and techniques

    Sundisk Corporation · December 15, 1992

  15. US5172338B1

    Multi-state eeprom read and write circuits and techniques

    Sandisk Corp · July 8, 1997

  16. US5303198A

    Method of recording data in memory card having EEPROM and memory card system using the same

    Fuji Photo Film Co., Ltd. · April 12, 1994

  17. US5343063A

    Dense vertical programmable read only memory cell structure and processes for making them

    Sundisk Corporation · August 30, 1994

  18. US5239505A

    Floating gate non-volatile memory with blocks and memory refresh

    Intel Corporation · August 24, 1993

  19. US5592669A

    File structure for a non-volatile block-erasable semiconductor flash memory

    Intel Corporation · January 7, 1997

  20. US6002614A

    Memory apparatus including programmable non-volatile multi-bit memory cell, and apparatus and method for demarcating memory states of the cell

    Btg International Inc. · December 14, 1999

  21. US5249158A

    Flash memory blocking architecture

    Intel Corporation · September 28, 1993

  22. US6317363B1

    Multi-state memory

    Sandisk Corporation · November 13, 2001

  23. US5399891A

    Floating gate or flash EPROM transistor array having contactless source and drain diffusions

    Macronix International Co., Ltd. · March 21, 1995

  24. US5691938A

    Non-volatile memory cell and array architecture

    Macronix International Co., Ltd. · November 25, 1997

  25. US5526307A

    Flash EPROM integrated circuit architecture

    Macronix International Co., Ltd. · June 11, 1996

  26. US5371702A

    Block erasable nonvolatile memory device

    Kabushiki Kaisha Toshiba · December 6, 1994

  27. US5379413A

    User selectable word/byte input architecture for flash EEPROM memory write and erase operations

    Intel Corporation · January 3, 1995

  28. US5822781A

    Sector-based storage device emulator having variable-sized sector

    Intel Corporation · October 13, 1998

  29. US5835933A

    Method and apparatus for updating flash memory resident firmware through a standard disk drive interface

    Intel Corporation · November 10, 1998 · Examiner cited

  30. US5682497A

    Managing file structures for a flash memory file system in a computer

    Intel Corporation · October 28, 1997

  31. US6097637A

    Dynamic single bit per cell to multiple bit per cell memory

    Intel Corporation · August 1, 2000

  32. US5638320A

    High resolution analog storage EPROM and flash EPROM

    Invoice Technology, Inc. · June 10, 1997

  33. US5905993A

    Flash memory card with block memory address arrangement

    Mitsubishi Denki Kabushiki Kaisha · May 18, 1999

  34. US5712740A

    Method for reducing wasted storage space when storing multiple data blocks on a storage medium

    Sony Corporation · January 27, 1998

  35. US5748528A

    EEPROM memory device with simultaneous read and write sector capabilities

    Sgs-Thomson Microelectronics S.R.L. · May 5, 1998

  36. US5717636A

    EEPROM memory with contactless memory cells

    Sgs-Thomson Microelectronics S.R.L. · February 10, 1998

  37. US5751634A

    Non-volatile semiconductor memory device for storing multivalue data and readout/write-in method therefor

    Kabushiki Kaisha Toshiba · May 12, 1998

  38. US5694357A

    Nonvolatile semiconductor memory device for storing multi-value data

    Kabushiki Kaisha Toshiba · December 2, 1997

  39. US6130841A

    Semiconductor nonvolatile memory apparatus and computer system using the same

    Hitachi, Ltd. · October 10, 2000

  40. US5742934A

    Flash solid state disk card with selective use of an address conversion table depending on logical and physical sector numbers

    Mitsubishi Denki Kabushiki Kaisha · April 21, 1998

  41. US5745409A

    Non-volatile memory with analog and digital interface and storage

    Invox Technology · April 28, 1998

  42. US5987478A

    Virtual small block file manager for flash memory array

    Intel Corporation · November 16, 1999

  43. US6055181A

    Nonvolatile semiconductor memory device capable of storing multi-value data of more than one bit in a memory cell

    Kabushiki Kaisha Toshiba · April 25, 2000

  44. US5802553A

    File system configured to support variable density storage and data compression within a nonvolatile memory

    Intel Corporation · September 1, 1998

  45. US5680341A

    Pipelined record and playback for analog non-volatile memory

    Invoice Technology · October 21, 1997

  46. US5781921A

    Method and apparatus to effect firmware upgrades using a removable memory device under software control

    Ohmeda Inc. · July 14, 1998

  47. US5896393A

    Simplified file management scheme for flash memory

    Advanced Micro Devices, Inc. · April 20, 1999

  48. US5768192A

    Non-volatile semiconductor memory cell utilizing asymmetrical charge trapping

    Saifun Semiconductors, Ltd. · June 16, 1998

  49. US5892715A

    Non-volatile semiconductor memory device with variable source voltage

    Nec Corporation · April 6, 1999

  50. US5936887A

    Non-volatile memory device with NAND type cell structure

    Samsung Electronics Co., Ltd. · August 10, 1999

  51. US5999445A

    Multilevel non-volatile memory devices

    Sgs-Thomson Microelectronics S.R.L. · December 7, 1999

  52. US5962890A

    Non-volatile semiconductor memory

    Sharp Kabushiki Kaisha · October 5, 1999

  53. US5880993A

    Method and circuit for checking multilevel programming of floating-gate nonvolatile memory cells particularly flash cells

    Sgs-Thomson Microelectronics, S.R.L. · March 9, 1999

  54. US5970012A

    Non-volatile semiconductor memory device having a memory cell capable of establishing multi-level information and data writing method thereof

    Nec Corporation · October 19, 1999

  55. US5946714A

    Semiconductor storage device utilizing address management tables and table state maps for managing data storage and retrieval

    Mitsubishi Denki Kabushiki Kaisha · August 31, 1999

  56. US5717632A

    Apparatus and method for multiple-level storage in non-volatile memories

    Advanced Micro Devices, Inc. · February 10, 1998

  57. US6418506B1

    Integrated circuit memory and method for transferring data using a volatile memory to buffer data for a nonvolatile memory array

    Intel Corporation · July 9, 2002 · Examiner cited

  58. US5909387A

    Memory architecture for recording of multiple messages

    Invox Technology · June 1, 1999

  59. US5896340A

    Multiple array architecture for analog or multi-bit-cell memory

    Invox Technology · April 20, 1999

  60. US5801994A

    Non-volatile memory array architecture

    Programmable Microelectronics Corporation · September 1, 1998

  61. US5848019A

    Pass gate decoder for a multiport memory dEvice that uses a single ported memory cell array structure

    Integrated Device Technology, Inc. · December 8, 1998

  62. US6151246A

    Multi-bit-per-cell flash EEPROM memory with refresh

    Sandisk Corporation · November 21, 2000

  63. US5909449A

    Multibit-per-cell non-volatile memory with error detection and correction

    Invox Technology · June 1, 1999

  64. US6292392B1

    Non-volatile semiconductor device

    Sharp Kabushiki Kaisha · September 18, 2001

  65. US6166407A

    Non-volatile semiconductor memory device

    Sharp Kabushiki Kaisha · December 26, 2000

  66. US5886923A

    Local row decoder for sector-erase fowler-nordheim tunneling based flash memory

    Integrated Silicon Solution Inc. · March 23, 1999

  67. US6240032B1

    Non-volatile semiconductor memory allowing user to enter various refresh commands

    Sharp Kabushiki Kaisha · May 29, 2001 · Examiner cited

  68. US5963465A

    Symmetric segmented memory array architecture

    Saifun Semiconductors, Ltd. · October 5, 1999

  69. US6285574B1

    Symmetric segmented memory array architecture

    Saifun Semiconductors Ltd. · September 4, 2001

  70. US6088264A

    Flash memory partitioning for read-while-write operation

    Intel Corporation · July 11, 2000

  71. US6038636A

    Method and apparatus for reclaiming and defragmenting a flash memory device

    Lexmark International, Inc. · March 14, 2000

  72. US6122193A

    Non-volatile semiconductor memory capable of storing 1-bit data or multi-bit data

    Kabushiki Kaisha Toshiba · September 19, 2000

  73. US6134145A

    High data rate write process for non-volatile flash memories

    Sandisk Corporation · October 17, 2000

  74. US5973958A

    Interlaced storage and sense technique for flash multi-level devices

    Advanced Micro Devices, Inc. · October 26, 1999

  75. US6232632B1

    Double density non-volatile memory cells

    Advanced Micro Devices, Inc. · May 15, 2001

  76. US6166959A

    Flash memory array with internal refresh

    Atmel Corporation · December 26, 2000

  77. US6005803A

    Memory address decoding circuit for a simultaneous operation flash memory device with a flexible bank partition architecture

    Advanced Micro Devices, Inc. · December 21, 1999

  78. US6198648B1

    Semiconductor memory device with hierarchical bit line architecture

    Sharp Kabushiki Kaisha · March 6, 2001

  79. US6212121B1

    Semiconductor memory device with multiple sub-arrays of different sizes

    Samsung Electronics Co., Ltd. · April 3, 2001

  80. US6181597B1

    EEPROM array using 2-bit non-volatile memory cells with serial read operations

    Tower Semiconductor Ltd. · January 30, 2001

  81. US6256231B1

    EEPROM array using 2-bit non-volatile memory cells and method of implementing same

    Tower Semiconductor Ltd. · July 3, 2001

  82. US6229734B1

    Nonvolatile semiconductor storage device having controlled cell threshold voltage distribution

    Nec Corporation · May 8, 2001

  83. US6301154B1

    Semiconductor memory device having floating gate type transistors programmed to have differing threshold voltages

    Sharp Kabushiki Kaisha · October 9, 2001

  84. US6137719A

    Nonvolatile semiconductor memory device storing multi-bit data

    Mitsubishi Denki Kabushiki Kaisha · October 24, 2000

  85. US6091633A

    Memory array architecture utilizing global bit lines shared by multiple cells

    Sandisk Corporation · July 18, 2000

  86. US6330185B1

    High bandwidth multi-level flash memory using dummy memory accesses to improve precision when writing or reading a data stream

    Multi Level Memory Technology · December 11, 2001

  87. US6259627B1

    Read and write operations using constant row line voltage and variable column line load

    Multi Level Memory Technology · July 10, 2001

Cited by (31)

  1. US7975119B2

    Device for prioritized erasure of flash memory

    Sandisk Il Ltd · July 5, 2011 · Examiner cited

  2. US20080056012A1

    Method for prioritized erasure of flash memory

    Sandisk Il Ltd. · March 6, 2008 · Examiner cited

  3. US20080059692A1

    Device for prioritized erasure of flash memory

    Sandisk Il Ltd. · March 6, 2008 · Examiner cited

  4. US8117414B2

    Method for prioritized erasure of flash memory

    Sandisk Il Ltd. · February 14, 2012 · Examiner cited

  5. US8560762B2

    Limited memory power

    Microsoft Corporation · October 15, 2013

  6. US20090327579A1

    Limited memory power

    Microsoft Corporation · December 31, 2009 · Examiner cited

  7. US8854884B2

    NAND flash architecture with multi-level row decoding

    Conversant Intellectual Property Management Inc. · October 7, 2014 · Examiner cited

  8. US20120218829A1

    Nand flash architecture with multi-level row decoding

    Mosaid Technologies Incorporated · August 30, 2012 · Examiner cited

  9. US8341501B2

    Adaptive endurance coding of non-volatile memories

    International Business Machines Corporation · December 25, 2012

  10. US20100281340A1

    Adaptive endurance coding of non-volatile memories

    International Business Machines Corporation · November 4, 2010 · Examiner cited

  11. US8499221B2

    Accessing coded data stored in a non-volatile memory

    International Business Machines Corporation · July 30, 2013

  12. US9767913B2

    Memory system performing read of nonvolatile semiconductor memory device

    Toshiba Memory Corporation · September 19, 2017

  13. US20120268994A1

    Memory system

    Hiroyuki Nagashima · October 25, 2012 · Examiner cited

  14. US10020063B2

    Memory system performing read of nonvolatile semiconductor memory device

    Toshiba Memory Corporation · July 10, 2018

  15. US10916312B2

    Memory system performing read of nonvolatile semiconductor memory device

    Toshiba Memory Corporation · February 9, 2021

  16. US11475962B2

    Memory system performing read operation with read voltage

    Kioxia Corporation · October 18, 2022

  17. US11984167B2

    Memory system performing read operation with read voltage

    Kioxia Corporation · May 14, 2024

  18. US9524786B2

    Memory system changing a memory cell read voltage upon detecting a memory cell read error

    Kabushiki Kaisha Toshiba · December 20, 2016

  19. US10373692B2

    Memory system performing read of nonvolatile semiconductor memory device

    Toshiba Memory Corporation · August 6, 2019

  20. US8929140B2

    Memory system in which a read level is changed based on standing time and at least one of a read, write or erase count

    Kabushiki Kaisha Toshiba · January 6, 2015 · Examiner cited

  21. US20110138105A1

    Non-volatile memories with enhanced write performance and endurance

    International Business Machines Corporation · June 9, 2011 · Examiner cited

  22. US20110138104A1

    Multi-write coding of non-volatile memories

    International Business Machines Corporation · June 9, 2011 · Examiner cited

  23. US8176234B2

    Multi-write coding of non-volatile memories

    International Business Machines Corporation · May 8, 2012

  24. US8176235B2

    Non-volatile memories with enhanced write performance and endurance

    International Business Machines Corporation · May 8, 2012

  25. US8769374B2

    Multi-write endurance and error control coding of non-volatile memories

    International Business Machines Corporation · July 1, 2014

  26. US8621328B2

    Wear-focusing of non-volatile memories for improved endurance

    International Business Machines Corporation · December 31, 2013

  27. US9164893B2

    Nonvolatile semiconductor memory device

    Kabushiki Kaisha Toshiba · October 20, 2015 · Examiner cited

  28. US20140082266A1

    Nonvolatile semiconductor memory device

    Kabushiki Kaisha Toshiba · March 20, 2014 · Examiner cited

  29. US9911499B2

    Semiconductor memory device and memory system

    Toshiba Memory Corporation · March 6, 2018

  30. US9704570B2

    Semiconductor memory device and memory system

    Kabushiki Kaisha Toshiba · July 11, 2017

  31. US11797230B2

    Bios variables storage

    Hewlett-Packard Development Company, L.P. · October 24, 2023

Related Patents