System and method which compares data preread from memory cells to data to be written to the cells
Claim Score by NHIP
Abstract
A memory system which includes one or more arrays of memory cells (e.g., flash memory cells) organized into sets of cells, wherein each set of cells is indicative of a set of stored data, and wherein the system also includes circuitry which compares new data (to be written to a set of cells) with stored data (preread from a corresponding set of cells) and prevents a write of the new data to the array if the new data is identical to the stored data, a computer system including such a memory system, and a method implemented by such a computer system. In preferred embodiments, the system includes a controller which includes logic circuitry which performs the comparison. In response to the comparison determining that the new data to be written is identical to the previously stored data, the controller generates a confirmation signal indicating that the new data has been written to the array, rather than actually writing the new data to the array. Preferably, the system emulates a magnetic disk drive and each of the sets of cells has sufficient capacity to store the same amount of data as can a set of a conventional magnetic disk drive. Preferably, each array of flash memory cells is organized into rows and columns of the cells, and each of the rows is a set of cells capable of storing a sector of data.

Term
Term ended
Projected expiry passed 22 July 2018, 8.2 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
55 claims: 11 independent, 44 dependent
- 1A memory circuit, including:an array of memory cells organized into sets, each of said sets having capacity to store a set of data;a buffer memory which stores a first set of data to be written to the array to replace a second set of data stored in a first one of the sets of the cells;interface circuitry coupled to the array and operable to read the second set of data from said first one of the sets of the cells;a comparator coupled to the buffer memory to receive the first set of data and coupled to the interface circuitry to receive the second set of data which has been read from the first one of the sets of the cells, the comparator being operable to compare at least a portion of the first set of data with at least a portion of the second set of data and to generate a control signal having a first state if the first set of data matches the second set of data;and a control engine coupled to the comparator to receive the control signal, and operable to prevent a write of the first set of data to the array in response to the control signal having the first state.
- 10A memory system for use with a host device, said memory system including:an array of memory cells organized into sets of said cells;a host interface coupled to receive memory commands and data from the host device, and operable to generate control signals in response to the memory commands;a buffer memory coupled to the host interface and configured to receive and store a first set of the data from the host interface, said first set of data to be written to the array to replace a second set of data stored in a first one of the sets of the cells;array interface circuitry coupled to the array and operable to read the second set of data from said first one of the sets;a comparator coupled to the buffer memory to receive the first set of data and coupled to the array interface circuitry to receive the second set of data which has been read from the first one of the sets, the comparator being operable to compare at least a portion of the first set of data with at least a portion of the second set of data and to assert a first signal with a first state in response to determining that the first set of data matches the second set of data;and a control engine coupled to the comparator to receive the first signal, coupled to the host interface to receive the control signals, and coupled to the array interface circuit, the control engine being operable to prevent a write of the first set of data to the array in response to reception of both the first signal having the first state and a first one of the control signals, wherein the first one of the control signals is indicative of a memory command from the host device which would otherwise cause the memory circuit to write said first set of data to the array.
- 15A method for operating a memory circuit in response to a command to write a first set of data to an array of memory cells of said memory circuit to replace a second set of data stored in the array, wherein the array is organized into sets of the cells and the second set of data is stored in a first one of the sets of the cells, said method including the steps of:(a) reading at least a portion of the second set of data from said first one of the sets of the cells;(b) comparing each portion of the second set of data which has been read from the array with a corresponding portion of the first set of data, and generating a control signal having a first state upon determining that the first set of data matches the second set of data;and (c) in response to said control signal having the first state, generating a confirmation signal which indicates that the first set of data has been written to the array rather than writing said first set of data to the array.
- 20A method for operating a memory circuit including an array of memory cells organized into sets of the cells, said method including the steps of:(a) receiving a command from a host device, said command indicating that a first set of data is to be written to the array to replace a second set of data previously stored in a first one of the sets of the cells, (b) reading the second set of data from said first one of the sets of the cells;(b) comparing at least a portion of the second set of data which has been read from the array with at least a portion of the first set of data;(c) in response to a determination in step (b) that the first set of data matches the second set of data, asserting to the host device a confirmation signal indicating that the first set of data has been written to the array rather than writing said first set of data to the array, and in response to a determination in step (b) that the first set of data does not match the second set of data, writing the first set of data to a second one of the sets of the cells.
- 24Broadest claimClaim Score 71, broad(NHIP)A method for writing data to an array of memory cells, said method including the steps of:writing a first set of data into a first set of the cells;comparing at least a portion of a second set of data with a corresponding portion of the first set of data;and writing the second set of data to the array only upon determining as a result of the step of comparing that the second set of data differs from the first set of data.
- 31A memory system, including:an array of memory cells organized into sets of the cells, each of said sets having capacity to store a set of data;a buffer memory which stores a first set of data, wherein the first set of data is to be written to the array to replace a second set of data stored in a first one of the sets of the cells;interface circuitry coupled to the array and operable to read the second set of data from said first one of the sets of the cells;a comparator coupled to the buffer memory to receive the first set of data and coupled to the interface circuitry to receive the second set of data which has been read from the first one of the sets of the cells, wherein the comparator is operable to perform a comparison of at least a portion of the first set of data with at least a portion of the second set of data, in which it generates a control signal having a first state if the first set of data matches the second set of data, and in which it generates the control signal with a second state and aborts the comparison upon determining that the first set of data does not match the second set of data;and a control engine coupled to the comparator to receive the control signal, wherein the control engine is operable to prevent a write of the first set of data to the array in response to the control signal having the first state.
- 32A nonvolatile memory circuit, comprising:a group of nonvolatile memory cells;a buffer sized to retain data to be written to said group of nonvolatile memory cells;and comparison circuitry coupled to the buffer and to the group of nonvolatile memory cells, and configured to compare a first set of data in the buffer with a second set of data in the group of nonvolatile memory cells and to generate a signal functionally indicative of a match between the first set of data and the second set of data.
- 36A nonvolatile memory circuit, comprising:a first group of nonvolatile memory cells;a second group of memory cells sized to retain data to be written to said first group of nonvolatile memory cells;and comparison circuitry coupled to the second group of memory cells and to the first group of nonvolatile memory cells, and configured to compare a first set of data stored in the second group of memory cells with a second set of data stored in the first group of nonvolatile memory cells and to generate a signal functionally indicative of a match between the first set of data and the second set of data.
- 41A computer system, including:a processor;and a memory subsystem, wherein said memory subsystem includes: an array of memory cells organized into sets of said cells;a processor interface coupled to receive memory commands and data from the processor, and operable to generate control signals in response to the memory commands;a buffer memory coupled to the processor interface and configured to receive and store a first set of the data from the processor interface, said first set of data to be written to the array to replace a second set of data stored in a first one of the sets of the cells;array interface circuitry coupled to the array and operable to read the second set of data from said first one of the sets;a comparator coupled to the buffer memory to receive the first set of data and coupled to the array interface circuitry to receive the second set of data which has been read from the first one of the sets, the comparator being operable to compare at least a portion of the first set of data with at least a portion of the second set of data and to assert a first signal with a first state in response to determining that the first set of data matches the second set of data;and a control engine coupled to the comparator to receive the first signal, coupled to the processor interface to receive the control signals, and coupled to the array interface circuit, the control engine being operable to prevent a write of the first set of data to the array in response to reception of both the first signal having the first state and a first one of the control signals, wherein the first one of the control signals is indicative of a memory command from the processor which would otherwise cause the memory circuit to write said first set of data to the array.
- 48A computer system, including:a processor;and a memory subsystem, wherein said memory subsystem includes: a group of nonvolatile memory cells;a processor interface coupled to receive memory commands and data from the processor, and operable to generate control signals in response to the memory commands;a buffer coupled to the processor interface and sized to retain data to be written to said group of nonvolatile memory cells;and comparison circuitry coupled to the buffer and to the group of nonvolatile memory cells, and configured to compare a first set of data in the buffer with a second set of data in the group of nonvolatile memory cells in response to a first one of the control signals, and to generate a signal functionally indicative of a match between the first set of data and the second set of data as a result of said;and write circuitry coupled to the buffer and to the group of nonvolatile memory cells, and configured to prevent a write of the first set of data to the group of nonvolatile memory cells in response to the signal, wherein the first one of the control signals is indicative of a memory command from the processor which would otherwise cause the memory circuit to write said first set of data to the group of nonvolatile memory cells.
- 52A computer system, including:a processor;and a memory subsystem, wherein said memory subsystem includes: a first group of nonvolatile memory cells;a processor interface coupled to receive memory commands and data from the processor, and operable to generate control signals in response to the memory commands;a second group of memory cells coupled to the processor interface and sized to retain data to be written to said first group of nonvolatile memory cells;and comparison circuitry coupled to the second group of memory cells and to the first group of nonvolatile memory cells, and configured to compare a first set of data in the second group of memory cells with a second set of data in the first group of nonvolatile memory cells in response to a first one of the control signals, and to generate a signal functionally indicative of a match between the first set of data and the second set of data as a result of said;and write circuitry coupled to the second group of memory cells and to the first group of nonvolatile memory cells, and configured to prevent a write of the first set of data to the first group of nonvolatile memory cells in response to the signal, wherein the first one of the control signals is indicative of a memory command from the processor which would otherwise cause the memory circuit to write said first set of data to the first group of nonvolatile memory cells.
Independent claims11
83 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
[0001] 1. Field of the Invention
[0002] The invention is a memory system which includes at least one array of memory cells (e.g., flash memory cells) and circuitry which compares new data to be written to a set of the cells with data already stored in a corresponding set of the cells and writes the new data to the array only if the new data is not identical to the previously stored data, and a computer system which includes such a memory system, and method performed by such a computer system. In preferred embodiments, the memory system is designed to emulate a magnetic disk drive.
[0003] 2. Description of Related Art
[0004] It is conventional to implement a memory system as an integrated circuit including an array of flash memory cells and circuitry for independently erasing selected blocks of the cells. FIG. 1 is a simplified block diagram of such an integrated circuit (flash memory chip <b>103</b>). An integrated flash memory chip such as memory chip <b>103</b> of FIG. 1 (or a memory system including such a memory chip) can be modified in accordance with the present invention to avoid unnecessary writes of data to sectors of flash memory array circuit <b>16</b>.
[0005] Flash memory array circuit <b>16</b> of memory chip <b>103</b> comprises rows and columns of nonvolatile flash memory cells. Memory chip <b>103</b> also includes I/O pins DQ<b>0</b>-DQ<b>15</b> (for asserting output data to an external device or receiving input data from an external device), input buffer circuits <b>122</b>, <b>122</b>A, and <b>122</b>B, output buffer circuits <b>128</b>, <b>128</b>A, and <b>128</b>B, address buffer <b>17</b> for receiving address bits A<b>0</b> through A<b>17</b> from an external device, row decoder circuit (X address decoder) <b>12</b>, column multiplexer circuit (Y multiplexer) <b>14</b>, and control unit <b>29</b> (also denoted herein as “controller” <b>29</b>).
[0006] Each of the cells (storage locations) of memory array circuit <b>16</b> is indexed by a row index (an “X” index determined by decoder circuit <b>12</b>) and a column index (a “Y” index determined by Y decoder circuit <b>13</b> of circuit <b>14</b>). Each column of cells of memory array <b>16</b> comprises “n” memory cells, each cell implemented by a floating-gate N-channel transistor. The drains of all transistors of a column are connected to a bitline, and the gate of each of the transistors is connected to a different wordline, and the sources of the transistors are held at a source potential (which is usually ground potential for the chip during a read or programming operation). Each memory cell is a nonvolatile memory cell since the transistor of each cell has a floating gate capable of semipermanent charge storage. The current drawn by each cell (i.e., by each of the N-channel transistors) depends on the amount of charge stored on the cell's floating gate. Thus, the charge stored on each floating gate determines a data value that is stored “semipermanently” in the corresponding cell. In cases in which each of the N-channel transistors is a flash memory device, the charge stored on the floating gate of each is erasable (and thus the data value stored by each cell is erasable) by appropriately changing the voltage applied to the gate and source (in a well known manner).
[0007] The individual memory cells (not depicted) are addressed by eighteen address bits (A<b>0</b>-A<b>17</b>), with nine bits being used by X decoder circuit <b>12</b> to select the row of array <b>16</b> in which the target cell (or cells) is (or are) located and the remaining nine bits being used by Y decoder circuit <b>13</b> (of Y-multiplexer <b>14</b>) to select the appropriate column (or columns) of array <b>16</b>. Typically, a set of eight or sixteen target cells (or 256 target cells) in a single row of the array are selected by a single set of eighteen address bits A<b>0</b>-A<b>17</b>, with Y decoder circuit <b>13</b> determining the column addresses of such cells in response to a nine-bit subset of the set of address bits. In response to the other nine address bits A<b>0</b>-A<b>17</b>, X decoder circuit <b>12</b> determines a row address which selects one cell in the selected column.
[0008] In a normal operating mode, chip <b>103</b> executes a write operation as follows. Address buffer <b>17</b> asserts appropriate ones of address bits A<b>0</b>-A<b>17</b> to circuit <b>14</b> and decoder circuit <b>12</b>. In response to these address bits, circuit <b>14</b> determines a column address (which selects one of the columns of memory cells of array <b>16</b>), and circuit <b>12</b> determines a row address (which selects one cell in the selected column). In response to a write command supplied from controller <b>29</b>, a signal (indicative of data) present at the output of input buffer <b>122</b>, <b>122</b>A, and/or <b>122</b>B is asserted through circuit <b>14</b> to the cell of array <b>16</b> determined by the row and column address (e.g., to the drain of such cell). During such write operation, output buffers <b>128</b>, <b>128</b>A, and <b>128</b>B are disabled.
[0009] In the normal operating mode, chip <b>103</b> executes a read operation as follows. Address buffer <b>17</b> asserts appropriate ones of address bits A<b>0</b>-A<b>17</b> to circuit <b>14</b> and address decoder circuit <b>12</b>. In response to these address bits, circuit <b>14</b> asserts a column address to memory array <b>16</b> (which selects one of the columns of memory cells), and circuit <b>12</b> asserts a row address to memory array <b>16</b> (which selects one cell in the selected column). In response to a read command supplied from control unit <b>29</b>, a current signal indicative of a data value stored in the cell of array <b>16</b> (a “data signal”) determined by the row and column address is supplied from the drain of the selected cell through the bitline of the selected cell and then through circuit <b>14</b> to sense amplifier circuitry <b>33</b>. This data signal is processed in amplifier circuitry <b>33</b>, buffered in output buffers <b>128</b>, <b>128</b>A, and/or <b>128</b>B, and finally asserted at pins DQ<b>0</b>-DQ<b>15</b>. During such read operation, input buffers <b>122</b>, <b>122</b>A, and <b>122</b>B are disabled.
[0010] Chip <b>103</b> also includes a pad which receives a high voltage V<sub>pp </sub>from an external device, and a switch <b>121</b> connected to this pad. During some steps of a typical erase or program sequence (in which the cells of array <b>16</b> are erased or programmed), control unit <b>29</b> sends a control signal to switch <b>121</b> to cause switch <b>121</b> to close and thereby assert the high voltage V<sub>pp </sub>to various components of the chip including X decoder <b>12</b>. Voltage V<sub>pp </sub>is higher (typically V<sub>pp</sub>=12 volts) than the normal operating mode supply voltage (typically V<sub>cc</sub>=5 volts or V<sub>cc</sub>=5.5 volts) for the MOS transistors of chip <b>103</b>.
[0011] When reading a selected cell of array <b>16</b>, if the cell is in an erased state, the cell will conduct a first current which is converted to a first voltage in sense amplifier circuitry <b>33</b>. If the cell is in a programmed state, it will conduct a second current which is converted to a second voltage in sense amplifier circuitry <b>33</b>. Sense amplifier circuitry <b>33</b> determines the state of the cell (i.e., whether it is programmed or erased corresponding to a binary value of 0 or 1, respectively) by comparing the voltage indicative of the cell state to a reference voltage. The outcome of this comparison is an output which is either high or low (corresponding to a digital value of one or zero) which sense amplifier circuitry <b>33</b> sends to output buffers <b>128</b> and <b>128</b>B (and through multiplexer <b>124</b> to output buffer <b>128</b>A). One or more of the output buffers in turn asserts a corresponding data signal to corresponding ones of pins DQ<b>0</b>-DQ<b>15</b> (from which it can be accessed by an external device).
[0012] It is important during a write operation to provide the wordline of the selected cell with the proper voltage and the drain of the selected cell with the appropriate voltage level (the voltage determined by the output of each input buffer, asserted through latch/multiplexer <b>130</b> to circuit <b>14</b>), in order to successfully write data to the cell without damaging the cell.
[0013] Internal state machine <b>120</b> of control unit <b>29</b> of chip <b>103</b> controls detailed operations of chip <b>103</b> such as the various individual steps necessary for carrying out programming, reading and erasing operations. State machine <b>120</b> thus functions to reduce the overhead required of a processor (not depicted) typically used in association with chip <b>103</b>.
[0014] Memory operations, including programming, reading, and erasing can be initiated in various ways. For all operations, the chip enable signal {overscore (CE)} must be made active (low). To perform a read operation, write enable signal {overscore (WE)} must be made inactive (high). For a write operation, signal {overscore (WE)} must be made active (low). In order to reduce the likelihood of accidental modification of data, erase and program operations require receipt of two consecutive commands that are processed by command execution logic unit <b>124</b>. The program and erase commands are provided by the associated processor to data I/O pins DQ<b>0</b>-DQ<b>7</b>, forwarded to input buffer <b>122</b>, and then forwarded to the command execution logic unit <b>124</b> for processing.
[0015] If memory array <b>16</b> is to be erased (typically, all or large blocks of cells are erased at the same time), the processor causes the Output Enable {overscore (OE)} pin to be inactive (high), and the Chip Enable {overscore (CE)} and Write Enable {overscore (WE)} pins to be active (low). The processor then issues an 8 bit command <b>20</b>H (0010 0000) on data I/O pins DQ<b>0</b>-DQ<b>7</b>, typically called an Erase Setup command (each of I/O pins DQ<b>0</b>-DQ<b>7</b> corresponds to an I/O pad). This is followed by issuance of a second eight bit command D<b>0</b>H (1101 0000), typically called an Erase Confirm command. Two separate commands are used to reduce the possibility of an inadvertent erase operation.
[0016] The commands are transferred to data input buffer <b>122</b>, and the commands are then transferred to command execution logic unit <b>124</b> of control unit <b>29</b>. Logic unit <b>124</b> then instructs state machine <b>120</b> to perform all the numerous and well known steps for erasing array <b>16</b>.
[0017] Once an erase sequence is completed, state machine <b>120</b> updates an 8 bit status register <b>126</b>, the contents of which are transferred to data output buffer <b>128</b>A which is connected to data I/O pins DQ<b>0</b>-DQ<b>7</b> of the memory system. The processor periodically polls the data I/O pins to read the contents of status register <b>126</b> in order to determine whether an erase sequence has been completed and whether it has been completed successfully.
[0018] During a typical erase operation, it is desired to erase all the cells of array <b>16</b> (or an erase block of the cells) so that the threshold voltages are all within a specified voltage range. That range is typically a small positive voltage range such as from +1.5 to +3.0 volts. If the erased cells fall within this range, the cell to be read (the “selected” or “target”) cell will produce a cell current in a read operation. The presence of cell current flow indicates that the cell is in an erased state (logic “1”) rather than a programmed state (logic “0”). Cell current is produced in a selected erased cell if the voltage applied to the control gate of the cell, by way of the wordline connected to X decoder <b>12</b>, exceeds the threshold voltage of the erased cell. In addition, cells which are not being read (“deselected” cells) are prevented from producing a cell current even if such cells have been erased to a low threshold voltage state. By way of example, for cells located in the same row as the selected cell, by definition, share the same wordline as the selected cell. However, the drains of the deselected cells will be floating thereby preventing a cell current from being generated. Deselected cells in the same column will not conduct cell current because the wordlines of such deselected cells are typically grounded. Thus, the gate-source voltage of these cells will be insufficient to turn on these deselected cells even if they are in an erased state.
[0019] An example of a flash memory array which can be employed as memory array <b>16</b> of chip <b>103</b> is described in U.S. patent application Ser. No. 08/606,246, entitled “Segmented Non-Volatile Memory Array with Multiple Sources with Improved Word Line Control Circuitry,” filed on Feb. 23, 1996 and assigned to the assignee of the present application.
[0020] The present invention is useful as an improvement to flash memory systems of the type designed to emulate magnetic disk drive systems. This type of flash memory system is typically implemented as a card (for insertion into a computer system) with a chip set mounted thereon, where the chip set includes an onboard controller and several memory chips controlled by the controller. Each memory chip implements an array of flash memory cells organized into independently erasable blocks. A conventional flash memory system of this type can be modified in accordance with the invention to avoid unnecessary writes of data to sectors of the flash memory array.
[0021] In the past, magnetic hard disk systems have been the dominant storage media for computers and related systems. The low cost and high capacity Es offered by this technology has made magnetic hard disk systems the mainstay in the computer industry. Because of the dominance of this technology, virtually all computer systems use and support this technology. The support of magnetic disk systems is evident by the software associated with the disk drives. The dominant computer operating system known as “DOS” (Disk Operating System) is essentially a software package used to manage a disk system. The DOS software has been developed by IBM Corporation, Microsoft Corporation, and Novell as the heart of widely used computer software. The first generation of Microsoft Corporation's “Windows” operating system software was essentially a continuation of the original DOS software with a user friendly shell added for ease of use.
[0022] The DOS software was developed to support the physical characteristics of hard drive structures, supporting file structures based on heads, cylinders and sectors. The DOS software stores and retrieves data based on these physical attributes. Magnetic hard disk drives operate by storing polarities on magnetic material. This material is able to be rewritten quickly and as often as desired. These characteristics has allowed DOS to develop a file structure that stores files at a given location which is updated by a rewrite of that location as information is changed. Essentially all locations in DOS are viewed as fixed and do not change over the life of the disk drive being used therewith, and are easily updated by rewrites of the smallest supported block of this structure. A sector (of a magnetic disk drive) is the smallest unit of storage that the DOS operating system will support. In particular, a sector has come to mean 512 bytes (each byte consisting of eight bits) of information for DOS and most other operating systems in existence. DOS also uses clusters as a storage unit. Clusters, however, are nothing more than the logical grouping of sectors to form a more efficient way of storing files and tracking them with less overhead.
[0023] The development of flash memory integrated circuits has enabled a new technology to offer competition to magnetic hard drives and offer advantages and capabilities that are hard to support by disk drive characteristics and features. The low power, high ruggedness, and small sizes offered by a solid state flash memory system make such a flash memory system attractive and able to compete with a magnetic hard disk drive system. Although a memory implemented with flash memory technology may be more costly than a hard disk drive system, computers and other processing systems are being developed that require (or benefit greatly from) use of flash memory features.
[0024] Thus, flash memory systems have been developed that emulate the storage characteristics of hard disk drives. Such a flash memory system is preferably structured to support storage in 512 byte blocks along with additional storage for overhead associated with mass storage, such as ECC (error correction code) bits and/or redundant bits. A key to this development is to make the flash memory array respond to a host processor in a manner that looks like a magnetic disk assembly so the operating system can store and retrieve data in a known manner and be easily integrated into a computer system including the host processor.
[0025] To make a flash memory easily integratable into a host computer, two basic approaches have been developed. One approach is to configure the flash memory as a storage array, and to load special software into the host to translate conventional operating system (e.g., DOS) commands into flash commands and procedures for assertion to the flash memory. This approach uses the host computing power to act as a controller for the utility that manages the flash memory (rather than including such a controller in the flash memory itself).
[0026] Another approach is to make the interface to the flash memory identical to a conventional interface to a conventional magnetic hard disk drive. This approach has been adopted by the PCMCIA standardization committee, which committee has promulgated a standard for supporting flash memory systems with a hard disk drive protocol. A flash memory card (including one or more flash memory array chips) whose interface meets this standard can be plugged into a host system having a standard DOS operating system with a PCMCIA-ATA (or standard ATA) interface. Such a flash memory card is designed to match the latter standard interfaces, but must include an onboard controller which manages each flash memory array independent of the host system. This approach has several advantages, including the following: there are no special system requirements for the host system (so ease of host system design is assured); no extra memory is required in the host, allowing for better use of the host memory; and the flash memory system runs independently of the host, freeing the host computer to do other tasks while the flash memory is storing or retrieving data from a flash memory array. However, the approach requires a controller onboard the flash memory to implement the equivalent of an operating system behind the PCMCIA interface.
[0027] An example of a flash memory array for use in a flash memory system that emulates a magnetic disk drive will be described with reference to FIG. 2. The flash memory array structure shown in FIG. 2 may be suitable for low cost applications of .the type commonly implemented using low cost magnetic disk drives. Memory array <b>16</b> of FIG. 2 has 544 bytes per row of cells (each byte consisting of eight bits, where each memory cell is capable of storing one bit). Thus, each row of cells is equivalent to a magnetic disk sector (512 bytes of data plus 32 bytes of “overhead”).
[0028] Memory array <b>16</b> of FIG. 2 is partitioned into large “decode” blocks of cells (e.g., eight large decode blocks as shown in FIG. 2) that are physically isolated from one another. This partitioning of blocks allows defects in one decode block (e.g., decode block <b>16</b>A) to be isolated from the other decode blocks in the array, allows defective decode blocks to be bypassed by a controller, and allows for high usage of die and enhances overall yield of silicon produced (driving down the cost of flash mass storage systems).
[0029] The expression “decode block” is used to denote a block of cells of a memory array which are sufficiently physically isolated from the other cells of the array that the disturb effect on the cells in the decode block (due to high voltage application to the other cells of the array, e.g., during erasing or programming of the other cells) is negligible. In one case, an entire memory array is a single decode block. More typically, a memory array includes two or more decode blocks.
[0030] In the array of FIG. 2, each decode block is subdivided into eight independently erasable blocks, sometimes referred to herein as “erase blocks.” In the FIG. 2 example, each erase block (e.g., erase block <b>16</b>B) consists of rows of flash memory cells, with each row being capable of storing seventeen “packets” of bits, and each packet consisting of 32 bytes (each byte consisting of eight bits). Thus, each row (capable of storing 544 bytes) corresponds to one conventional disk sector (comprising 544 bytes), and each row can store 512 bytes of user data as well as a field of 32 ECC bytes for use in error detection and correction and other bits associated with sector management. In the FIG. 2 example, each erase block corresponds to two “cylinders” of data (in the sense that this expression is used in a conventional magnetic disk drive), with each cylinder consisting of 256K bits of data organized into 64 sectors. Thus, each erase block in the FIG. 2 example consists of 128 sectors of data.
[0031] Still with reference to FIG. 2, each erase block (e.g., erase block <b>16</b>B) can be independently erased in response to signals from the controller. All flash memory cells in each erase block are erased at the same (or substantially the same) time, so that erasure of an erase block amounts to erasure of a large portion of array <b>16</b> at a single time.
[0032] In many normal usages of flash memory systems (other than disk emulation systems), an entire memory is written (or erased) or entire decode blocks are written (or erased) at one time. However, in a disk emulation system this is typically not done, as the data is typically very dynamic with small portions (e.g., individual rows of flash memory cells) being rewritten many times while other small portions remain unchanged. To accomplish the latter type of data updating, the controller will write data to free locations (e.g., rows) and when the memory is to be updated it will write the new (updated) data to other free rows (not previously written), marking the previously written rows as old (obsolete, and ready to be erased). The system will keep track of these obsolete rows and will erase an entire erase block when it becomes filled or almost filled with obsolete rows. Updated data (to replace data in one row of one erase block) may be placed in another erase block or even another decode block or possibly even a different flash memory chip. The constant rewriting and moving of files will result in erase blocks being constantly programmed and erased. In DOS it is typical for new files to be updated heavily and unused files to be not updated or never changed once generated. This typical use of files will result in portions of memory being updated frequently while other areas will remain stagnant and unchanged.
[0033] In flash memory systems, writes of data to flash memory cells are slow and they cause wear on the cells. This wear limits the useful life of conventional flash memory systems and reduces their overall reliability. The present invention overcomes these limitations (by applying data discrimination to avoid unnecessary writes to flash memory cells).
[0034] A file of data to be written to cells of a disk emulation system (a flash memory system which emulates a magnetic disk drive) typically consists of sectors of data. During writing of a file to cells of such a system, each of the sectors of data is typically written to a different row of cells (or to another distinct set of cells which has capacity to store a sector of data, and which is thus sometimes denoted herein as a “sector” of cells). The inventor has recognized that in many cases, a file of new data to be written to the cells corresponds to a previously written file of “old” data, with many sectors of the new data being identical to corresponding sectors of the old data.
[0035] It would be desirable to reduce the number of writes to an array (of flash memory cells) that must be performed in order to keep the array updated. Doing so would result in less stress on the cells, and would thus increase the operating life of the array and achieve better system reliability. In addition, system performance would be greatly improved, by reducing the time spent by system in writing data to cells and reducing overall command overhead. However, until the present invention, it had not been known how to achieve such write reduction in flash memory systems which emulate magnetic disk drives or in other types of flash memory systems.
SUMMARY OF THE INVENTION
[0036] In preferred embodiments, the invention is a memory system including one or more arrays of memory cells (e.g., flash memory cells or other nonvolatile memory cells), and each array is organized into sectors of cells, either physically (e.g., with each row of cells corresponding to a sector) or logically (with no specific correspondence between each sector and the physical position of the cells comprising the sector). Each cell is indicative of a stored data bit (whether the cell is in an erased or programmed state), and each sector of cells is indicative of a sector of stored data. The system includes circuitry which compares new data (to be written to the array) with stored data that has been “preread” from a selected sector (or other set) of the cells, where the selected sector (or other set) is to be updated with the new data. The system prevents a write of the new data to the array if the new data is identical to the stored data. If the new data is not identical to the stored data the system writes the new data to a second one of the sectors (or other sets) of the cells, where the second one of the sectors (or sets) corresponds to the selected sector (or set) in the following sense: the system marks the selected sector (or set) as “old” (or “obsolete”) and keeps track of the fact that the second one of the sectors (or sets) contains updated data which replaces data in the obsolete selected sector (or set).
[0037] In preferred embodiments, the memory system is designed to emulate a magnetic disk drive, the cells of the array are organized into sectors, and each of the sectors of cells can store the same amount of data as can a sector of a conventional magnetic disk drive supported by the DOS operating system (i.e., 512 bytes of data). In some of such preferred embodiments, each array of nonvolatile memory cells is organized into rows and columns of the cells, and each of the rows is a sector of cells capable of storing a sector of data.
[0038] Preferably, the system includes a controller which includes logic circuitry for performing the comparison. In response to the comparison determining that the new data is identical to the previously stored data, the controller preferably generates a confirmation signal indicating that the new data has been written to the array (rather than actually writing the new data to the array). Typically, the memory system communicates with a host processor (host) and the confirmation signal is sent to the host (in response to a command from the host that the new data be written to the array).
[0039] Other aspects of the invention are the method implemented by any of the described embodiments of the memory system of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
0040[0040]FIG. 1 is block diagram of a conventional nonvolatile (flash) memory circuit (implemented as an integrated circuit), including a conventional controller for controlling memory operations of the circuit.
0041[0041]FIG. 2 is a diagram of the manner in which cells of a flash memory array are organized in one flash memory system which emulates a magnetic disk drive.
0042[0042]FIG. 3 is a block diagram of a computer system including a processor and an embodiment of the integrated flash memory system of the invention.
0043[0043]FIG. 4 is a block diagram of another embodiment of the flash memory system of the invention, including several flash memory arrays (each implemented as a separate integrated circuit) and a controller for controlling memory operations of any selected one of the arrays and for implementing the invention.
0044[0044]FIG. 5 is a block diagram of another embodiment of the flash memory system of the invention.
0045[0045]FIG. 6 is a schematic diagram of a preferred embodiment of comparator circuit <b>110</b> of FIG. 3.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
0046[0046] Preferred embodiments of the invention will be described with reference to FIGS. 3, 4, <b>5</b>, and <b>6</b>. One such embodiment is the computer system shown in FIG. 3. This computer system includes processor <b>2</b> (sometimes referred to herein as a host processor), input device <b>1</b> (which can be a keyboard) which can be manipulated by a human user to enter data and/or commands to processor <b>2</b>, and flash memory chip <b>3</b>. Flash memory chip <b>3</b>, which is a memory subsystem of the computer system of FIG. 3, replaces a conventional magnetic disk drive system (or other, memory subsystem) . Variations on the system of FIG. 3 include both a flash memory chip (such as chip <b>3</b> of FIG. 3) and at least one other memory subsystem (such as a conventional magnetic disk drive system). Of course, it is contemplated that the computer system of FIG. 3 can also include other peripheral devices, such as a display device.
0047[0047] Flash memory chip <b>3</b> shown in FIG. 3 includes controller <b>129</b> and array <b>216</b> of nonvolatile memory cells (which are preferably nonvolatile flash memory cells). Memory chip <b>3</b> of FIG. 3 can be identical to chip <b>103</b> of FIG. 1, except in that chip <b>3</b> includes controller <b>129</b> which is designed and programmed in accordance with the invention (rather than controller <b>29</b> of FIG. 1), and in that controller <b>129</b> includes host interface <b>102</b>, multiplexer <b>130</b>, error detection and correction circuit <b>132</b>, and flash interface <b>114</b>. In preferred implementations, interface <b>102</b> receives binary data and address bits from host processor <b>2</b> (and sends binary data bits from memory array <b>216</b> to processor <b>2</b>). Preferably, processor <b>2</b> is programmed with a standard DOS operating system and includes a PCMCIA-ATA interface (of the type discussed above), and interface <b>102</b> complies with the PCMCIA-ATA standard and thus can communicate with the standard PCMCIA-ATA interface of processor <b>2</b>.
0048[0048] Flash memory array <b>216</b> of FIG. 3 preferably includes a cell array identical to array <b>116</b> of FIG. 2 (which can be identical to array <b>16</b> of FIG. 1) and circuitry which performs the functions of elements <b>12</b>, <b>14</b>, and <b>33</b> of FIG. 1. Flash interface <b>114</b> receives data (to be written to array <b>114</b>) and address bits from other elements of chip <b>3</b> and asserts corresponding data and address bits with appropriate timing and format to array <b>216</b>. Flash interface <b>114</b> also reads data bits from cells of array <b>216</b> (e.g., from any selected sector of cells of array <b>216</b>) and asserts the data bits which it reads with appropriate timing and format to other elements of chip <b>3</b> (including to comparator circuit <b>110</b>). The description of those components of FIG. 3 which correspond to components of FIG. 1 has been provided above with reference to FIG. 1, and will not be repeated below.
0049[0049] The cells of flash memory array <b>216</b> of FIG. 3 (and the cells of array <b>16</b> of FIG. 1) are organized into decode blocks. Each decode block is organized into independently erasable erase blocks (as is each decode block of array <b>116</b> shown in FIG. 2). In some implementations of the FIG. 3 embodiment, memory array <b>216</b> is an array of nonvolatile memory cells other than flash memory cells. Preferably however, each cell of array <b>216</b> is implemented as a flash memory cell.
0050[0050] With reference to FIG. 3, in response to control signals and address bits from processor <b>2</b> (or another external host), interface <b>102</b> sends the address bits (including bits identifying cylinder, head, and sector addresses) to control engine <b>130</b> of controller <b>129</b>, and asserts internal control signals to appropriate components of controller <b>129</b> (including control engine <b>130</b>) as required to implement each memory operation specified by each control signal from host processor <b>2</b> (e.g., a read of some or all cells of array <b>216</b>, an erase of one or more erase blocks of array <b>216</b>, or a write of data to some or all cells of array <b>216</b>). In response to the address bits, control engine <b>130</b> generates translated address bits and sends the translated address bits to flash interface <b>114</b>. Among the internal control signals asserted by interface <b>102</b> are enable/disable signals (as well as presets) which are asserted (from control engine <b>130</b>) to comparator circuit <b>110</b> at appropriate times. FIG. 6 is a preferred embodiment of circuit <b>110</b>.
0051[0051] In the FIG. 6 embodiment, comparator circuit <b>110</b> includes an array of XNOR (exclusive NOR) gates <b>400</b>-<b>406</b> whose outputs are all connected to NAND gate <b>408</b>. The output of NAND gate <b>408</b> is presented to the input of JK register <b>410</b> at the J input, with the K input connected to ground (logic low). During preread checks (i.e., during the inventive preread and compare operations), the controller (controller <b>129</b> of FIG. 3) will first issue a control signal (Reset Compare Register) that will force register <b>410</b> to the clear (reset) state. The controller will then fetch a byte of data from flash memory array <b>216</b> and a corresponding byte of data from buffer memory <b>104</b>. The corresponding bits of each byte will be input to the XNOR gates <b>400</b>-<b>406</b> resulting in a positive output from each of the XNOR gates if the inputs thereto are the same (1,1 or 0,0) or a negative output from each XNOR gate whose inputs are different (0,1 or 1,0). if all bits of each byte match each other (i.e., the byte read from flash array <b>216</b> is identical to that read from buffer memory <b>104</b>), the eight XNOR outputs will be all logic high and will drive the output of NAND <b>408</b> low. The low output of NAND <b>408</b> is presented to the J input of JK register <b>410</b>. The controller will then generate a clock sampling the compare condition, as determined by the logic level of the J input. If the J is low (the two bytes match each other), the JK register will remain clear indicating that the data has compared. The controller will then fetch the next sequential byte of data from flash memory array <b>216</b> and the next byte of data from buffer memory <b>104</b>, again repeating the compare and sample operation. If any of the bytes of data read from flash memory <b>216</b> miscompares with a corresponding one of the bytes of write data in buffer <b>104</b>, the J input of circuit <b>410</b> will be driven to a logic high and the JK register will toggle to the set state when sampled by the compare clock. Once the JK register becomes set, it will remain set indicating a miscompare has occurred, regardless of any further clocking. The controller will monitor this JK register output and will abort the compare operation as soon as the miscompare status is detected. Aborting the operation when a miscompare is detected will result in saved overhead time (avoiding wasted time in clocking to the end of the sector). This translates to performance savings to the system. If a miscompare is detected, the controller will then generate the necessary control signals to write the new set of data in buffer memory <b>104</b> to a new (erased) sector of flash memory array <b>216</b>. It will also mark the sector just read from flash memory array <b>216</b>, which has been found to miscompare, to an “obsolete” state.
0052[0052] If the compare operation has compared all bytes of the sector and found no miscompare (between any byte read from array <b>216</b> and a corresponding byte read from memory <b>104</b>), the two sectors (stored in array <b>216</b> and memory <b>104</b>) are of identical value, resulting in no need to write the new sector to array <b>216</b>. In this case, the sector residing in array <b>216</b> is left untouched and the host is notified that the sector write is complete. This bypass of a write operation results in a big time savings, since flash writes are slow compared to reads. A flash write of a sector can take 1 to 5 milliseconds while a read compare will take approximately 50 microseconds. Thus, a large savings is gained when a sector is not required to be written to array <b>216</b>. If all the data in a file is changing (i.e., each compare operation performed on a sector in array <b>216</b> and a new sector of the file in memory <b>104</b> determines that the two sectors are not identical), the compare operation will result in unnecessary overhead that degrades system performance. To avoid this problem, the controller preferably has two ways of preventing this overhead from occurring (or reducing its magnitude).
0053[0053] The simplest feature to prevent the preread comparisons from adding to the overall overhead is to design the controller to be operable in a mode in which it does not perform the compare operation (i.e., in response to a command from the host). This capability is preferably supported by a vendor unique command from the host that tells the controller not to perform the read compares when issued a write command.
0054[0054] With reference again to FIG. 6, circuit <b>110</b> preferably also includes an arithmetic logic unit (ALU) <b>412</b> which performs desired arithmetic operations on either or both of the bit streams received at the “A” and “B” inputs of circuit <b>110</b>. In response to control signals from control engine <b>130</b>, ALU <b>412</b> can pass through unaltered either the data received at its “A” input (from buffer memory <b>104</b> via the “A” input of circuit <b>110</b>) or the data received at its “B” input (from array <b>216</b>, via interface <b>114</b> and the “B” input of circuit <b>110</b>), at appropriate times during system operation.
0055[0055] When the controller is operating in a mode in which read compares are allowed (and performed), some typical considerations of file usage are preferably taken into account to allow the controller not to do a read compare of all write files. In a computer that is storing a file in a group of sectors, the file tends to change toward the end of the file, as the end of the file is typically the most recently worked on portion. In a file with a change (relative to a previously stored version of the file), many times a small change will result in data being shifted, resulting in everything after the change looking like a change since it will be bit/byte shifted. Noting this characteristic, the controller is preferably programmed to start a write operation by doing a preread and compare on each successive sector. As soon as a miscompare is detected, the controller preferably aborts the process of performing preread and compares, and instead enters a mode in which it automatically writes each succeeding new sector to memory cells of the array and obsoletes each older sector corresponding to (and replaced by) each succeeding new sector, without any further comparisons.
0056[0056] Typically, the control signals and address bits received at interface <b>102</b> from the external host (processor <b>2</b>) indicate one or more sectors of array <b>216</b> which are to be updated with new data (also received from the host or from a memory controlled by the host). In response to the internal control signals and address bits asserted by interface <b>102</b> (in response to the control signals and address bits received from host processor <b>2</b>), controller <b>129</b> writes each sector of the data to a “free” sector (e.g., row) of array <b>216</b> which corresponds to the sector (and cylinder and head) specified by the host (or controller <b>129</b> determines that there is no need to perform such write, in accordance with the invention). When controller <b>129</b> determines that a previously written sector of array <b>216</b> needs to be updated with new data received from host processor <b>2</b>, controller <b>129</b> causes chip <b>3</b> to execute the following operations: controller <b>129</b> causes flash interface to write the new data to a “free” sector of array <b>216</b>, which is an erased sector other than the previously written sector (i.e., an erased sector of array <b>216</b> to which data has not been written since the last erase of the entire erase block containing the erased sector); controller <b>129</b> marks the previously written sector as old (obsolete, and ready to be erased); and typically also controller <b>129</b> asserts a confirmation signal to interface <b>102</b> (to be relayed to the host to confirm that the requested write operation has been performed). As will be explained below, control engine <b>130</b> of controller <b>129</b> is preferably programmed in accordance with the invention to assert such a confirmation signal even when it has prevented a write of the updating data to array <b>216</b> (after controller <b>129</b> has determined that there is no need for such a write, because the updating data is identical to previously written data which the updating data is intended to replace). Controller <b>129</b> is programmed to keep track of the obsolete sectors of array <b>216</b> (typically, each sector is a row of cells of array <b>216</b>) and to cause the erasing of an entire erase block when it becomes filled or almost filled with obsolete sectors. Controller <b>129</b> can cause the new data (updating data) from the host to be written to another erase block (an erase block other than the erase block containing the previously written sector to be updated) or even another decode block or possibly even a different flash memory chip.
0057[0057] With reference again to FIG. 3, control engine <b>130</b> asserts control signals to the other elements of controller <b>129</b> (including elements <b>106</b> and <b>110</b>) and to flash interface <b>114</b> in response to the internal control signals it receives from interface <b>102</b>, to cause controller <b>129</b> and interface <b>114</b> to execute operations in accordance with the present invention. Control engine <b>130</b> determines which set of suboperations or functions need to be performed to implement the memory operation specified by processor <b>2</b> (e.g., a write of data in buffer memory <b>104</b> to array <b>216</b>, or a read of data from array <b>216</b> to buffer memory <b>104</b>). In a typical implementation of control engine <b>130</b>, control engine <b>130</b> includes a microcontroller which performs the high level operations, such as command and status handshaking with the host via interface <b>102</b>. This microcontroller is responsible for locating the proper memory location (within array <b>216</b>) from a given cylinder, head and sector address from the host. This microcontroller will handle error correction (ECC) calculations and will also correct errant data bits found by the ECC calculations. While such a microcontroller can be programmed to efficiently handle these activities, it will typically be too slow to control the real time operations of managing the data flow and flash interface gating. Because of the performance limitations, a specially designed sequencer will often be included in control engine <b>130</b> to control the real time functions of the flash data gating and flash interface control. In an implementation using a microcontroller and a specially designed sequencer, the microcontroller will typically act as the master to the slave sequencer. This is done by having the microcontroller activate the sequencer to do specific functions in response to the microcontroller's commands. In this environment, the sequencer will be given commands such as “read sector,” “write enable,”<b>0</b> or “erase a block.” The locations of the cells of array on which to do these operations are given to the sequencer from the microcontroller.
0058[0058] Typically, the sequencer would perform the specified operation by managing the DMA circuit <b>120</b> and the bad location hardware (error detection circuitry), as well as handling the address and command handshaking with the flash port logic (flash interface <b>114</b>).
0059[0059] Various structures of microcontroller and sequencer logic are possible, but the overall methodology will preferably resemble the structures used by conventional magnetic hard disk drives.
0060[0060] An alternate design approach that may be used to implement control engine <b>130</b> is to replace the microcontroller and sequencer by a single RISC processor or DSP (digital signal processor). Use of such processor cores provides the speed required (which otherwise would be provided by a sequencer) as well as the high level intelligence required. This approach would simplify the design and would shift the development burden more to firmware design. This approach would also give better flexibility for design changes, through firmware, and would possibly reduce cost where a small core would replace large blocks of logic.
0061[0061] Data to be written to array <b>216</b> are received at interface <b>102</b>, and written from interface <b>102</b> to buffer memory <b>104</b>. Buffer memory <b>104</b> is preferably an SRAM circuit, but it can alternatively be an array of nonvolatile memory cells or some other memory circuit. Memory <b>104</b> has capacity to store a set of data. This set can be a “sector” of the data, and such a sector of data can consist of a number (e.g., sixteen) of “packets” of the data (where “sector” and “packet” have been explained above). In accordance with the invention, comparator circuit <b>110</b> operates in a mode in which it compares a set (e.g., a sector) of new data temporarily stored in buffer <b>104</b> to be later written to flash memory array <b>216</b> (e.g., to a sector of array <b>216</b>), with a previously stored set (e.g., sector) of data. The previously stored set of data is data, stored in cells of flash memory array <b>216</b> (e.g., in a sector of array <b>216</b> to which a sector of data in buffer <b>104</b> is to be written), which is to be replaced by the new data in buffer memory <b>104</b>. The previously stored set of data is preread from array <b>216</b> and asserted to comparator <b>110</b> in accordance with the invention.
0062[0062] For specificity, the rest of the detailed description will describe embodiments in which a “sector” of new data in a buffer memory is to be written to a “sector” of cells of a flash memory array. However, it is contemplated that in other embodiments, a set of new data (not necessarily a “sector” of new data) in a buffer memory is to be written to memory cells of a flash memory array (not necessarily to a “sector” of such cells).
0063[0063] With reference again to FIG. 3, in accordance with another aspect of the invention, control engine <b>130</b> is programmed to prevent a write of the new data from memory <b>104</b> to array <b>216</b> when comparator <b>110</b> has determined that the new data in buffer <b>104</b> is identical to the previously stored data (in array <b>216</b>) which the new data is intended to replace.
0064[0064] In preferred implementations of the FIG. 3 system, array <b>216</b> is organized into erase blocks of cells, and each row of each erase block stores a quantity of bits which corresponds to a sector of a magnetic disk drive (and thus each row is denoted as a sector of cells). In one such implementation, memory <b>104</b> receives from interface <b>102</b> (and stores) a burst of 512 eight-bit bytes of new data (4096 bits) and each row of array <b>216</b> consists of 4352 cells (and thus each row can store the 4096 bits of new data plus an additional 256-bit packet of “overhead” bits). In variations on the single chip embodiment of FIG. 3, array <b>216</b> and controller <b>129</b> are implemented in two or more separate chips. Array <b>216</b> can itself be replaced by an array implemented in two or more chips.
0065[0065] With reference to FIG. 3, memory system <b>3</b> operates as follows when a sector of new data to be written to a sector of array <b>216</b> has been stored in buffer memory <b>104</b>. Control engine <b>130</b> (e.g., a sequencer within control engine <b>130</b>) sends a control signal to direct memory access circuit <b>120</b> (“DMA unit” <b>120</b>) to set the DMA pointer to the start of a sector, sets comparator logic circuit <b>110</b> to a mode of operation in which it compares the data value asserted to its “A” input to the data value asserted to its “B” input and asserts to control engine <b>130</b> a status bit indicative of whether each pair of a sequence of pairs of data values simultaneously asserted to circuit <b>110</b> match (or alternatively, a sequence of status bits, each indicative of whether each pair of data values simultaneously asserted to circuit <b>110</b> match), sets DMA <b>120</b> to a mode of operation in which it sequentially asserts the 8-bit bytes of one sector of data from memory <b>104</b> to multiplexer <b>106</b>, causes multiplexer <b>106</b> to enter a mode of operation in which multiplexer <b>106</b> passes the data it receives from memory <b>104</b> to the “A” input of circuit <b>110</b>, and causes a sequence of eight-bit bytes of a corresponding sector of stored data to be read from array <b>216</b> and passed through interface <b>114</b> to the “B” input of circuit <b>110</b>. Multiplexer <b>106</b> can be controlled to select either eight bits of data received in parallel from shift register <b>118</b>, or eight bits of data received in parallel from buffer memory <b>4</b>, and asserting each set of selected bits to circuit <b>110</b>.
0066[0066] Preferably, circuit <b>110</b> includes a register for an interim status bit indicative of whether all pairs of data values already asserted to circuit <b>110</b> (in parallel to the “A” and “B” inputs of circuit <b>110</b>) are matching pairs. E.g., circuit <b>110</b> can add a “zero” bit to the contents of the register each time a matching pair of data values is received at the “A” and “B” inputs of circuit <b>110</b>, and circuit <b>110</b> can add a “one” bit to the contents of the register each time a non-matching pair of data values is received at the “A” and “B” inputs of circuit <b>110</b>. The “one” bit will be held and will not be reset to zero. Preferably, circuit <b>110</b> includes logic circuitry for asserting a first status signal (e.g., a single “one” bit) to control engine <b>130</b> when the contents of the status register within circuit <b>110</b> changes from a “zero” bit to a “one” bit, and for asserting a second status signal (e.g., a single “zero” bit) to control engine <b>130</b> if the status register (within circuit <b>110</b>) still contains a “zero” bit after an entire sector of data has been received at each of the “A” and “B” inputs of circuit <b>110</b> and been processed by comparator <b>110</b>.
0067[0067] In response to such a “first” status signal from comparator circuit <b>110</b> (indicating that the new sector of data in buffer <b>104</b> does not match the previously stored sector of data read from array <b>216</b>), the comparison operation (which had been performed by circuit <b>110</b>) is aborted, and control engine <b>130</b> sets circuit <b>110</b> to operate in a mode in which it does not alter data received at its “A” input (and instead passes the data through to its output terminal), and control engine <b>130</b> puts flash interface <b>114</b> into a mode in which it receives the output of circuit <b>110</b>. Control engine <b>130</b> also causes DMA unit <b>120</b> to set the DMA address back by one sector, and DMA unit <b>120</b> causes the same sector of data bits to be reread from memory <b>104</b> to multiplexer <b>106</b> (as a sequence of eight-bit bytes). Multiplexer <b>106</b> then asserts the sector of data from buffer memory <b>104</b> to circuit <b>110</b>, circuit <b>110</b> passes the data through (unaltered) to its output terminal, and the data asserted at circuit <b>110</b>'s output terminal is received by flash interface <b>114</b> and written by flash interface <b>114</b> to a sector of cells (a “free” sector of erased cells) of flash memory array <b>216</b> in a well known manner. In preferred implementations, multiple streams of the bits from buffer memory <b>104</b> are written to array <b>216</b> in parallel, so that at any one time, bits are being written to two or more cells of array <b>216</b>. In one preferred implementation, two hundred fifty six (<b>256</b>) streams of bits are written to array <b>216</b> in parallel (so that a packet of 32 eight-bit bytes of the data is written to array <b>216</b> during a single write operation). Control engine <b>130</b> keeps track of the sector of array <b>216</b> to which the new data has been written, generates a confirmation signal indicating that the new sector of data has been written to the sector of cells specified by the host (processor <b>2</b>), and asserts the confirmation signal to host interface <b>102</b>. In response, interface <b>102</b> relays the confirmation signal (or asserts a corresponding confirmation signal) to the host. Typically, control engine <b>130</b> does not keep track of the status of each packet of a sector, and it confirms the writing of a sector of data but not a subset (e.g., a packet) of a sector of data.
0068[0068] In response to the described “second” status signal from comparator circuit <b>110</b> (indicating that the new sector of data in buffer <b>104</b> matches the previously stored sector of data read from array <b>216</b>), control engine <b>130</b> prevents a write of the new sector of data to array <b>216</b>. In the preferred embodiments, control engine <b>130</b> instead generates a confirmation signal indicating that the new sector of data has been written to the sector of cells of array <b>216</b> in which the matching sector of data has previously been stored (rather than actually writing the new data to array <b>216</b>), and asserts the confirmation signal to host interface <b>102</b>. In response, interface <b>102</b> relays the confirmation signal (or asserts a corresponding confirmation signal) to the host (processor <b>2</b>).
0069[0069] Shift register <b>118</b> is optionally employed to store temporarily one or more overhead bits, to be written to array <b>216</b> for use in subsequent processing of data bits to be written from buffer memory <b>104</b> to array <b>216</b>. Also, overhead bits read from array <b>216</b> can be stored in register <b>118</b> for use at appropriate times during processing of corresponding data read from array <b>216</b>. Preferably, control engine <b>130</b> is capable of monitoring the contents of shift register <b>118</b> and shifting the contents of register <b>118</b> by sequencer control to assert from register <b>118</b> selected overhead bits corresponding to any selected packet of a sector of data (read from array <b>216</b> or to be written to array <b>216</b>).
0070[0070] Also preferably, control engine <b>130</b> can alter the length of each DMA transfer to fit the desired volume of data to be written to array <b>216</b> (i.e., the size of each sector, packet, or other quantity of data asserted from buffer memory <b>104</b> is preferably controllable). Preferably, control engine <b>130</b> can alter the DMA address to allow multiple reads (rereads) of the same quantity of data from buffer <b>104</b> during a DMA transfer operation.
0071[0071] After an entire sector of data in buffer memory <b>104</b> has been processed in accordance with the invention (by performing a comparison in circuit <b>110</b> and writing the sector of data to array <b>216</b>), the sequencer within control engine <b>130</b> selects shift register <b>118</b> as a data source. At this point, shift register <b>118</b> contains overhead bits corresponding to the sector of data written to array <b>216</b>, typically because controller <b>129</b> has caused ECC check bits (e.g., from circuit <b>132</b> discussed below), defect bits, and system flags for the sector of data to be written to register <b>118</b> as a set of overhead bits for the sector. The overhead bits are sequentially asserted (as a sequence of eight-bit words) from shift register <b>118</b> through multiplexer <b>106</b> and circuit <b>110</b> to flash interface <b>114</b>, and are then written to cells of array <b>216</b>. In the above-mentioned implementation of array <b>216</b> in which each row of array <b>216</b> consists of 4352 cells (and can store sixteen 256-bit packets of data plus an additional 256-bit packet of overhead bits), a sector of data (4096 bits of data stored in buffer <b>104</b>) is written to a single row of array <b>216</b>, and a packet of <b>256</b> overhead bits from register <b>118</b> are also written to the same row of array <b>216</b>.
0072[0072] To read a sector of data from array <b>216</b>, the FIG. 3 system operates as follows. The sequencer within control engine <b>130</b> causes flash interface <b>114</b> to read the overhead bits for the sector from array <b>216</b>. The overhead bits that are read from array <b>216</b> are asserted through circuit <b>110</b> to shift register <b>118</b> (and/or to circuit <b>132</b> discussed below). Control engine <b>130</b> (e.g., the sequencer within control engine <b>130</b>) then sets the DMA address to the start of the sector, and causes DMA unit <b>120</b> and flash interface <b>114</b> to execute a DMA operation in which the first packet of bits (e.g., the first 32 eight-bit bytes of bits) is read from array <b>216</b>, asserted from interface <b>114</b> to circuit <b>110</b>, and written from the output of circuit <b>110</b> to buffer memory <b>104</b> (and optionally through multiplexer <b>130</b> to circuit <b>132</b>). Control engine <b>130</b> (e.g., the sequencer within control engine <b>130</b>) monitors the DMA operation for completion of the packet transfer to memory <b>104</b>.
0073[0073] Upon completion of the packet transfer, control engine <b>130</b> causes another DMA operation to be performed to read the next packet from array <b>216</b> and write the packet to buffer memory <b>104</b>. This sequence of steps is repeated for each packet of the sector to be read from array <b>216</b>, until all packets of the sector have been read from array <b>216</b> and written to buffer memory <b>104</b>.
0074[0074] The error correction code for the sector (error correction code bits which are a subset of the overhead bits previously read from array <b>216</b> and stored in register <b>118</b>) is preferably also checked, under control of control engine <b>130</b>, to determine if there is any detectible error in the data in buffer memory <b>104</b>. If no error is detected, the data are transferred from buffer memory <b>104</b> through host interface <b>102</b> to host processor <b>2</b>.
0075[0075] More specifically, circuit <b>3</b> preferably includes multiplexer circuit <b>130</b> and error detection and correction circuit <b>132</b> (ECC <b>132</b>) connected as shown in FIG. 3 (with the input of ECC <b>132</b> connected to the output of multiplexer <b>130</b>). When circuit <b>3</b> operates in a write mode in which it writes data from buffer memory <b>104</b> to array <b>216</b>, the data being written (or to be written) to array <b>216</b> is asserted from buffer memory <b>104</b> through multiplexer <b>106</b>, circuit <b>110</b>, and multiplexer <b>130</b> to ECC <b>132</b>. In this mode, ECC <b>132</b> processes the data to calculate check bits. ECC <b>132</b> asserts the check bits to flash interface <b>114</b>, and flash interface <b>114</b> causes the check bits to be written to array <b>216</b>.
0076[0076] When circuit <b>3</b> operates in a read mode in which it reads data from array <b>216</b>, flash interface <b>114</b> asserts the data (and corresponding check bits) which it reads from array <b>216</b> through circuit <b>110</b> and multiplexer <b>130</b> to ECC <b>132</b>. In this mode, ECC <b>132</b> processes the check bits and data to identify errors in the data, and ECC <b>132</b> asserts appropriate signals to control engine <b>130</b> (e.g., signals indicative of syndrome bits) as a result of this operation. ECC <b>132</b> thus performs error detection on the data read from array <b>216</b>. Control engine <b>130</b> reads the syndrome bits from ECC <b>132</b> and calculates a correction vector based thereon (e.g., in a well known manner). Once the correction vector and displacement are known, control engine <b>130</b> alters the data in buffer memory <b>104</b> to correct at least one detected error therein. The corrected data will then be sent to the host (via host interface <b>102</b>).
0077[0077] In some embodiments, to read a set of data bits (and any corresponding overhead bits for the set) from a location (e.g., a sector) of a flash memory array, the controller of the inventive flash memory system identifies the location where the set of data is stored and reads any corresponding overhead bits (typically stored in a sublocation distinct from that where the data of interest is stored). The controller stores and/or processes the overhead bits. Then, the first subset of the set of data is then DMA gated from the flash memory array and written into an internal data buffer. The next subset of the set of data is then DMA gated from the flash memory array and written into the internal data buffer, and this process repeats until all subsets of the set of data have been read from the array and written to the internal data buffer. After the entire set of data has been stored in the internal data buffer, the controller preferably performs error detection (using ECC check bits read from the flash memory array), and if the data is found correct the controller causes the data to be sent from the internal data buffer to a host over a controller interface. Reads of different locations (e.g., sectors) of the flash memory proceed with this same procedure until data from all desired locations has been sent to the host. When all the data has been sent to the host, the read operation is complete.
0078[0078] Control engine <b>130</b> is preferably programmed with software for implementing the invention as described with reference to FIG. 3. Throughout the specification, including in the claims, the expression that a device is “programmed with software” for performing an operation in accordance with the invention is used in a broad sense to denote that the device includes software, firmware, or dedicated hardware which gives the device the capability of performing the operation. Also throughout the specification, including in the claims, the term “circuitry” is used to denote any hardware comprising active and/or passive electrical components (e.g., semiconductor devices, tubes, resistors, etc.) whether or not such hardware is programmed with software (unless the term “circuitry” is qualified to refer to a narrower class of such hardware). A general purpose processor which includes transistors or other electrical components and which is programmed with software causing the processor to process electrical signals (indicative of binary data) that it receives in accordance with an algorithm is an example of “circuitry” within the scope of this definition.
0079[0079] In the FIG. 3 circuit, controller <b>129</b> includes hardware as specified (including comparator <b>110</b> which is implemented by hardwired logic circuitry). It is contemplated that in alternative embodiments, controller <b>129</b> can be a general purpose processor (including a memory) which is programmed with software enabling the processor to perform an operation in accordance with the invention (e.g., in response to external signals from host processor <b>2</b> specifying operations on memory array <b>216</b>).
0080[0080] It should be understood that although controller <b>129</b> is a component of the same integrated circuit (chip <b>3</b>) as is flash memory array <b>216</b> in the FIG. 3 embodiment of the invention, in other embodiments of the invention the controller and flash memory array will be implemented in distinct chips. For example, it is contemplated that the invention can be embodied in a chip set (such as that shown in FIG. 4) which includes a controller chip and two or more memory array chips, each of which operates under control of the controller chip. Such a chip set can be implemented to emulate a magnetic disk drive (with the controller chip operating in response to commands received from a remote host). It is contemplated that the controller would be capable of performing a memory operation on any selected one of the memory array chips. For example, when instructed to write a sector of data to non-volatile memory cells of a selected one of the memory array chips, it would compare the sector to a previously stored sector of data read from the selected memory array chip in accordance with the invention, and either write the sector of data to the selected memory array chip or generate a confirmation signal indicating that the sector has been written to selected memory array chip without actually writing the sector to the chip (depending on the outcome of the comparison).
0081[0081]FIG. 4 is a block diagram of a multi-chip embodiment of the inventive flash memory system, including identical nonvolatile memory arrays <b>316</b>, <b>416</b>, and <b>516</b> (each implemented as a separate integrated circuit) and controller <b>129</b>'. Each cell of each of arrays <b>316</b>, <b>416</b>, and <b>516</b> is preferably a flash memory cell. Also preferably, each of arrays <b>316</b>, <b>416</b>, and <b>516</b> comprises at least one decode block of flash memory cells (and preferably several such decode blocks), each decode block includes at least one erase block of cells, and each of the erase blocks includes at least one row of cells. Controller <b>129</b>' is programmed to control memory operations of any selected one of arrays <b>316</b>, <b>416</b>, and <b>516</b>, and to process a sector of data to be written to any selected one of arrays <b>316</b>, <b>416</b>, and <b>516</b> in accordance with the invention. Controller <b>129</b>' can differ from controller <b>129</b> of FIG. 3 only in that controller <b>129</b>' includes hardware and/or software for selecting one of the flash memory arrays (whereas controller <b>129</b> need not have such a capability).
0082[0082] Another embodiment of the flash memory system of the invention is shown in FIG. 5. In the FIG. 5 embodiment, flash memory chip <b>300</b> is controlled by an external controller chip <b>229</b>. Flash memory chip <b>300</b> includes an array <b>16</b> of flash memory cells, and array <b>16</b> consists of decode blocks of cells (such as decode block <b>16</b>E). Controller <b>229</b> operates with microcontroller chip <b>200</b>. In FIG. 5, chips <b>200</b> and <b>229</b> together perform the functions of controller <b>129</b> of the FIG. 3 embodiment. Flash memory chip <b>300</b> of FIG. 5 need not include control logic circuitry (of the type included in control unit <b>29</b> of memory chip <b>103</b> of FIG. 1), and instead controller <b>229</b> of FIG. 5 includes hardware and software for controlling memory operations of chip <b>300</b> (and for implementing the present invention).
0083[0083] Several embodiments of the method and apparatus of the invention have been described with reference to FIGS. 3, 4, <b>5</b>, and <b>6</b>. Although these embodiments have been described in some detail, it is contemplated that changes from these embodiments can be made without departing from the spirit and scope of the invention as defined by the appended claims.
Contents4
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2007159880A1 | Cited by | United States of America | Pre-grant |
| US6578126B1 | Cited by | United States of America | Search report |
| US2009262574A1 | Cited by | United States of America | Pre-grant |
| US2006036803A1 | Cited by | United States of America | Pre-grant |
| US9575835B2 | Cited by | United States of America | Search report |
| US2006034122A1 | Cited by | United States of America | Pre-grant |
| US2007032016A1 | Cited by | United States of America | Pre-grant |
| US7281114B2 | Cited by | United States of America | Search report |
| US8078793B1 | Cited by | United States of America | Applicant |
| US8185713B2 | Cited by | United States of America | Search report |
| US2006056240A1 | Cited by | United States of America | Pre-grant |
| US2007260845A1 | Cited by | United States of America | Pre-grant |
| US2006126382A1 | Cited by | United States of America | Pre-grant |
| US2015234707A1 | Cited by | United States of America | Pre-grant |
| US2007255889A1 | Cited by | United States of America | Pre-grant |
| US7894232B2 | Cited by | United States of America | Search report |
| US12292403B2 | Cited by | United States of America | Applicant |
| US2009032862A1 | Cited by | United States of America | Pre-grant |
| US2007233940A1 | Cited by | United States of America | Pre-grant |
| US2007171717A1 | Cited by | United States of America | Pre-grant |
| KR101507975B1 | Cited by | Republic of Korea | Search report |
| US2009077305A1 | Cited by | United States of America | Pre-grant |
| US2006152975A1 | Cited by | United States of America | Pre-grant |
| US2006143426A1 | Cited by | United States of America | Pre-grant |
| US6522950B1 | Cited by | United States of America | Search report |
| US7755938B2 | Cited by | United States of America | Applicant |
| US2013138867A1 | Cited by | United States of America | Pre-grant |
| US7353323B2 | Cited by | United States of America | Search report |
| US2003145188A1 | Cited by | United States of America | Pre-grant |
| US2010250885A1 | Cited by | United States of America | Pre-grant |
| US11366596B2 | Cited by | United States of America | Search report |
| US2007195607A1 | Cited by | United States of America | Pre-grant |
| US8130575B2 | Cited by | United States of America | Applicant |
| US7035993B2 | Cited by | United States of America | Search report |
| US8681570B2 | Cited by | United States of America | Search report |
| US2004186962A1 | Cited by | United States of America | Pre-grant |
| US11060994B2 | Cited by | United States of America | Applicant |
| US2023267974A1 | Cited by | United States of America | Search report |
| US2008094127A1 | Cited by | United States of America | Pre-grant |
| US2008111177A1 | Cited by | United States of America | Pre-grant |
| US9164676B2 | Cited by | United States of America | Search report |
| US2007036007A1 | Cited by | United States of America | Pre-grant |
| US8626995B1 | Cited by | United States of America | Search report |
| US2003135688A1 | Cited by | United States of America | Pre-grant |
| US11253852B2 | Cited by | United States of America | Search report |
| US7904636B2 | Cited by | United States of America | Applicant |
| US8482997B2 | Cited by | United States of America | Applicant |
| US12038403B2 | Cited by | United States of America | Applicant |
| US7711891B1 | Cited by | United States of America | Applicant |
| US9437312B2 | Cited by | United States of America | Search report |
| US7779226B2 | Cited by | United States of America | Search report |
| US11887687B2 | Cited by | United States of America | Search report |
| US2006285386A1 | Cited by | United States of America | Pre-grant |
| US2005144418A1 | Cited by | United States of America | Pre-grant |
| US2006158940A1 | Cited by | United States of America | Pre-grant |
| US2004153620A1 | Cited by | United States of America | Pre-grant |
| US2010173464A1 | Cited by | United States of America | Pre-grant |
| US2005144416A1 | Cited by | United States of America | Pre-grant |
| US2006068551A1 | Cited by | United States of America | Pre-grant |
| US6963505B2 | Cited by | United States of America | Applicant |
| US6928527B2 | Cited by | United States of America | Search report |
| US2005232024A1 | Cited by | United States of America | Pre-grant |
| US2015081973A1 | Cited by | United States of America | Pre-grant |
| US2006146624A1 | Cited by | United States of America | Pre-grant |
| US9348536B1 | Cited by | United States of America | Search report |
| US2006211188A1 | Cited by | United States of America | Pre-grant |
| US2006245274A1 | Cited by | United States of America | Pre-grant |
| US9405705B2 | Cited by | United States of America | Search report |
| US2007141788A1 | Cited by | United States of America | Pre-grant |
| US7257025B2 | Cited by | United States of America | Applicant |
| US2010217917A1 | Cited by | United States of America | Pre-grant |
| US2007173017A1 | Cited by | United States of America | Pre-grant |
| US2006285408A1 | Cited by | United States of America | Pre-grant |
| US2007253248A1 | Cited by | United States of America | Pre-grant |
| US2006126396A1 | Cited by | United States of America | Pre-grant |
| US8788781B2 | Cited by | United States of America | Applicant |
| US2007096199A1 | Cited by | United States of America | Pre-grant |
| US2007168637A1 | Cited by | United States of America | Pre-grant |
| US11067526B2 | Cited by | United States of America | Applicant |
| US2004218426A1 | Cited by | United States of America | Pre-grant |
| US2007196982A1 | Cited by | United States of America | Pre-grant |
| US2007051982A1 | Cited by | United States of America | Pre-grant |
| US2008239599A1 | Cited by | United States of America | Pre-grant |
| US2007133276A1 | Cited by | United States of America | Pre-grant |
| US2007120180A1 | Cited by | United States of America | Pre-grant |
| US2007153575A1 | Cited by | United States of America | Pre-grant |
3 members in 1 office
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 68936996 | United States of America | A | |
| 68936996 | United States of America | A | |
| 12101598 | United States of America | A | |
| 08689369 | – | – | – |
| US19960689369 | – | – | – |
| US19980121015 | – | – | – |
Members3
| Document | Office | Kind | |
|---|---|---|---|
| US5787484A | United States of America | A | |
| US2002004878A1 | United States of America | A1 | |
| US6438665B2 | United States of America | B2 |
12 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF |
Numbers
- Publication, DOCDB
- 2002004878
- Publication, EPODOC
- US2002004878
- Application
- 9121015
- Application, DOCDB
- 12101598
- Application, EPODOC
- US19980121015
Titles
- English
- SYSTEM AND METHOD WHICH COMPARES DATA PREREAD FROM MEMORY CELLS TO DATA TO BE WRITTEN TO THE CELLS
Classification
- CPC, 5
- G06F3/0616
- G06F3/0658
- G06F3/0664
- G06F3/0679
- G11C16/10
- IPC, 2
- G06F3 06
- G11C16 10
- USPC, 3
- 711103000
- 711154000
- 711156000