US20130111113A1 - NAND Flash Memory Controller Exporting a NAND Interface - Google Patents
NAND Flash Memory Controller Exporting a NAND Interface Download PDFInfo
- Publication number
- US20130111113A1 US20130111113A1 US13/596,926 US201213596926A US2013111113A1 US 20130111113 A1 US20130111113 A1 US 20130111113A1 US 201213596926 A US201213596926 A US 201213596926A US 2013111113 A1 US2013111113 A1 US 2013111113A1
- Authority
- US
- United States
- Prior art keywords
- controller
- nand
- nand interface
- host
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
- G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
- G06F11/1008—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices
- G06F11/1068—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices in sector programmable memories, e.g. flash disk
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/08—Error detection or correction by redundancy in data representation, e.g. by using checking codes
- G06F11/10—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's
- G06F11/1008—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices
- G06F11/1072—Adding special bits or symbols to the coded information, e.g. parity check, casting out 9's or 11's in individual solid state devices in multilevel memories
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/04—Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS
- G11C16/0483—Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS comprising cells having several storage transistors connected in series
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2212/00—Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
- G06F2212/72—Details relating to flash memory management
- G06F2212/7201—Logical to physical mapping or translation of blocks or pages
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/04—Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS
Abstract
A NAND controller for interfacing between a host device and a flash memory device (e.g., a NAND flash memory device) fabricated on a flash die is disclosed. In some embodiments, the presently disclosed NAND controller includes electronic circuitry fabricated on a controller die, the controller die being distinct from the flash die, a first interface (e.g. a host-type interface, for example, a NAND interface) for interfacing between the electronic circuitry and the flash memory device, and a second interface (e.g. a flash-type interface) for interfacing between the controller and the host device, wherein the second interface is a NAND interface. According to some embodiments, the first interface is an inter-die interface. According to some embodiments, the first interface is a NAND interface. Systems including the presently disclosed NAND controller are also disclosed. Methods for assembling the aforementioned systems, and for reading and writing data using NAND controllers are also disclosed.
Description
- This patent application is a continuation of U.S. patent application Ser. No. 12/539,417, filed Aug. 11, 2009, which is a continuation-in-part of U.S. patent application Ser. No. 11/326,336, filed Jan. 6, 2006 (now U.S. Pat. No. 7,631,245), which claims the benefit of U.S. Provisional Pat. App. No. 60/720,098, filed Sep. 26, 2005 (now abandoned).
- The present invention relates to NAND flash memory controllers that export to the host computer the same type of interface that is exported by a standard NAND flash memory device.
- Single Bit and Multi-Bit Flash Memory Cells
- Flash memory devices have been known for many years. Typically, each memory cell within a flash memory device stores one bit of information. The traditional way to store a bit in a flash memory cell has been by supporting two states of the memory cell. One state represents a logical “0” and the other state represents a logical “1”.
- In a flash memory cell, the two states are implemented by having a floating gate situated above the cell's channel (the area connecting the source and drain elements of the cell's transistor), and having two valid states for the amount of charge stored within the floating gate. Typically, one state is with zero charge in the floating gate and is the unwritten state of the cell after being erased (commonly defined to represent the “1” state) and the other state is with some amount of negative charge in the floating gate (commonly defined to represent the “0” state). Having negative charge in the gate causes the threshold voltage of the cell's transistor (i.e. the voltage that has to be applied to the transistor's control gate in order to cause the transistor to conduct) to increase. It is possible to read the stored bit by checking the threshold voltage of the cell. If the threshold voltage is in the higher state then the bit value is “0” and if the threshold voltage is in the lower state then the bit value is “1”. Actually there is no need to accurately read the cell's threshold voltage. All that is needed is to correctly identify in which of the two states the cell is currently located. For this purpose it is sufficient to compare the threshold voltage of the cell to a reference voltage that is between the two states, and to determine if the cell's threshold voltage is below or above the reference value.
-
FIG. 1A (prior art) shows graphically how this works. Specifically,FIG. 1A shows a distribution of the threshold voltages of a large population of cells. Because the cells in a flash device are not exactly identical in their characteristics and behavior (due to, for example, small variations in impurity concentrations or defects in the silicon structure), applying the same programming operation to all of the cells does not cause all of the cells to have exactly the same threshold voltage. Instead, the threshold voltage is distributed as shown inFIG. 1A . Cells storing a value of “1” typically have a negative threshold voltage, such that most of the cells have a threshold voltage close to the central voltage value of the left peak (labeled 1) ofFIG. 1A , with fewer cells having threshold voltages lower or higher than the central voltage of the left peak. Similarly, cells storing a value of “0” typically have a positive threshold voltage, such that most of the cells have a threshold voltage close to the central voltage of the right peak (labeled 0) ofFIG. 1A , with fewer cells having threshold voltages lower or higher than the central voltage of the right peak. - In recent years, a new kind of flash device has appeared on the market, using “Multi Level Cells” (MLC). The term “Multi-Level Cell” is misleading because flash memory with a single bit per cell uses multiple i.e. two levels, as described above. Therefore, the term “Single Bit Cell” (SBC) is used hereinafter to refer to a memory cell of two levels and the term “Multi-Bit Cell” (MBC) is used hereinafter to refer to a memory cell of more than two levels, i.e. more than one bit per cell. The most common MBC flash memories at present are ones with two bits per cell, and therefore examples are given below using such MBC memories. It should however be understood that the present invention is equally applicable to flash memory devices that support more than two bits per cell. A single MBC cell storing two bits of information is in one of four different states. As the cell's “state” is represented by the cell's threshold voltage, an MBC cell supports four different valid ranges for the cell's threshold voltage.
FIG. 1B (prior art) shows the threshold voltage distribution for a typical MBC cell of two bits per cell. As expected,FIG. 1B has four peaks, each peak corresponding to one state. As for the SBC, each state is actually a voltage range and not a single voltage. When reading the cell's contents, the cell's threshold voltage must be correctly identified in a definite voltage range. For a prior art example of an MBC flash device see U.S. Pat. No. 5,434,825 to Harari that is included by reference for all purposes as if fully set forth herein. - A cell designed for MBC operation e.g. in four states is typically operable as an SBC cell with two states. For example, Conley et al. in U.S. Pat. No. 6,426,893 incorporated by reference for all purposes as if fully set forth herein, disclosed the use of both MBC and SBC modes within the same device, and selecting certain parts of the device to operate with highest density in MBC mode, while other parts are used in SBC mode to provide better performance.
- MBC devices provide a significant cost advantage. An MBC device with two bits per cell requires about half the area of a silicon wafer than an SBC of similar capacity. However, there are drawbacks to using MBC flash. Average read and write times of MBC memories are longer than of SBC memories, resulting in worse performance. Also, the reliability of MBC is lower than SBC. The differences between the threshold voltage ranges in MBC are much smaller than in SBC. Thus, a disturbance in the threshold voltage (e.g leakage of stored charge causing a threshold voltage drift or interference from operating neighboring cells) that are insignificant in SBC because of the large gap between the two states, may cause an MBC cell to move from one state to another, resulting in an erroneous bit. The end result is a lower performance specification of MBC cells in terms of data retention time or the endurance of the device to many write/erase cycles.
- NAND Flash Memory Devices
- Flash memory devices are typically divided into NOR devices and NAND devices, the names being derived from the way the individual memory cells are interconnected within the cells array. NOR devices are random access—a host computer accessing a NOR flash device can provide the device any address on its address pins and immediately retrieve data stored in that address on the device's data pins. This is much like SRAM or EPROM memories operate. NAND devices, on the other hand, are not random access but serial access. It is not possible to access any random address in the way described above for NOR—instead the host has to write into the device a sequence of bytes which identifies both the type of the requested command (e.g. read, write, erase, etc.) and the address to be used for that command. The address identifies a page (the smallest chunk of flash memory that can we written in a single operation) or a block (the smallest chunk of flash memory that can be erased in a single operation), and not a single byte or word. It is true that the read and write command sequences contain addresses of single bytes or words, but in reality the NAND flash device always reads from the memory cells and writes to the memory cells complete pages. After a page of data is read from the array into a buffer inside the device, the host can access the data bytes or words one by one by serially clocking them out using a strobe signal.
- Because of the non-random access of NAND devices, they cannot be used for running code directly from the flash memory. This is contrary to NOR devices which support direct code execution (typically called “eXecution In Place” or “XIP”). Therefore NOR devices are the ones typically used for code storage. However, NAND devices have advantages that make them very useful for data storage. NAND devices are cheaper than NOR devices of the same bit capacity, or equivalently—NAND devices provide many more bits of storage than NOR devices for the same cost. Also, the write and erase performance of NAND devices is much faster than of NOR devices. These advantages make the NAND flash memory technology the technology of choice for storing data.
- NAND Interface Protocols
- A typical SBC NAND device is Toshiba TC58NVG1S3B that provides 2 Gbit of storage. A typical MBC NAND device is Toshiba TC58NVG2D4B that provides 4 Gbit of storage. The data sheets of both devices are incorporated by reference for all purposes as if fully set forth herein.
- As can be seen from the aforementioned data sheets, those two NAND devices have a similar interface. These NAND devices use the same electrical signals for coordinating commands and data transfer between the NAND flash device and a host device. Those signals include data lines and a few control signals—ALE (Address Latch Enable), CLE (Command Latch Enable), WE\ (Write Enable), and more. The SBC and MBC devices are not fully identical in their behavior—the time it takes to write an MBC page is much longer than time it takes to write an SBC page. However, the electrical signals used in both devices and their functionalities are the same. This type of interface protocol is known in the art as “NAND interface”. Even though the “NAND interface protocol” has not, to date, been formally standardized by a standardization body, the manufacturers of NAND flash devices all follow the same protocol for supporting the basic subset of NAND flash functionality. This is done so that customers using NAND devices within their electronic products could use NAND devices from any manufacturer without having to tailor their hardware or software for operating with the devices of a specific vendor. It is noted that even NAND vendors that provide extra functionality beyond this basic subset of functionality ensure that the basic functionality is provided in order to provide compatibility with the protocol used by the other vendors, at least to some extent.
- In this application the term “NAND Interface protocol” (or “NAND interface” in short) means an interface protocol between an initiating device and a responding device that in general follows the protocol between a host device and a NAND flash device for the basic read, write and erase operations, even if it is not fully compatible with all timing parameters, not fully compatible with respect to other commands supported by NAND devices, or contains additional commands not supported by NAND devices. In other words, the term “NAND interface” refers to any interface protocol that uses sequences of transferred bytes equivalent in functionality to the sequences of bytes used when interfacing with the Toshiba TC58NVG1S3B NAND device for reading (opcode 00H), writing (opcode 80H) and erasing (opcode 60H), and also uses control signals equivalent in functionality to the CLE, ALE, CE, WE and RE signals of the above NAND device.
- It is noted that the “NAND interface protocol” is not symmetric. Thus, it is always the host device which initiates the interaction over a NAND interface, and never the flash device.
- A given device (e.g. a controller, flash device, host device, etc.) is said to comprise, include or have a “NAND interface” if the given device includes elements (e.g. hardware, software, firmware or any combination thereof) necessary for supporting the NAND interface protocol (e.g. for interacting with another device using a NAND interface protocol).
- An interface (e.g. a NAND interface or an interface associated with another protocol) of a given device (e.g. a controller device) may be a “host-side interface” (e.g. the given device is adapted to interact with a host device using the host-side interface) or the interface of the given device may be a “flash memory device-side interface” (e.g. the given device is adapted to interact with a flash memory device using the flash memory device-side interface). The terms “flash memory device-side interface”, “flash device-side interface” and “flash-side interface” are used herein interchangeably.
- These terms (i.e. “host-side interface” and “flash device-side interface”) should not be confused with the terms “host-type interface” and “flash-type interface” which are terminology used herein to differentiate between the two sides of a NAND interface protocol, as this protocol is not symmetric. Furthermore, because it is always the host that initiates the interaction, we note that a given device is said to have a “host-type interface” if the device includes the necessary hardware and/or software for implementing the host side of the NAND interface protocol (i.e. for presenting a NAND host, and initiating the NAND protocol interaction) Similarly, because the flash device never initiates the interaction, we note that a given device is said to have a “flash-type interface” if the device includes the necessary hardware and/or software for implementing the flash side of the NAND protocol (i.e. for presenting a NAND flash device).
- Typically, “host-type interfaces” (i.e. those which play the role of the host) are “flash device-side interfaces” (i.e. they interact with flash devices or with hardware emulating a flash device) while “flash device-type interfaces” (i.e. those which play the role of the flash device) are typically “hosts-side interfaces” (i.e. they interact with host devices or with hardware emulating a host device). In this application the term “host device” (or “host” in short) means any device that has processing power and is capable of interfacing with a flash memory device. A host device may be a personal computer, a PDA, a cellular phone, a game console, etc.
- Typically, NAND devices are relatively difficult to interface and work with. One reason for that is the relatively complex (compared to NOR devices) protocol for accessing them, as described above. Another difficulty is the existence of errors in the data read from NAND devices, In contrast, NOR devices that can be assumed to always return correct data. This inherent non-reliability of NAND devices requires the use of Error Detection Codes (EDC) and Error Correction Codes (ECC).
- Manufacturers of SBC NAND flash devices typically advise users to apply an Error Correction Code capable of correcting 1 bit error in each page of 512 bytes of data. But data sheets of MBC NAND flash devices typically advise applying an ECC capable of correcting 4 bit errors in each page of 512 bytes of data. For pages of size 2048 bytes such as in the case of the NAND devices mentioned above (known as “large block devices”), the suggestion is to apply error correction per each portion of 512 bytes of the page. In this application the term “N-bit ECC” refers to an ECC scheme capable of correcting N bit errors in 512 bytes of data, regardless if the 512 bytes are the size of one page, less than one page, or more than one page.
- NAND Controllers
- Because of those complexities of NAND devices, it is the common practice to use a “NAND controller” for controlling the use of a NAND device in an electronic system. It is true that it is possible to operate and use a NAND device directly by a host device with no intervening NAND controller, and there are systems that actually operate like this. However, this architecture suffers from many disadvantages. First, the host has to individually manipulate each one of the NAND device's control signals (e.g. CLE or ALE), which is cumbersome and time-consuming for the host. Second, the support of EDC and ECC puts a severe burden on the host—parity bits have to be calculated for each page written, and error detection calculations (and sometimes also error correction calculations) must be performed by the host. All this makes such “no controller” architecture relatively slow and inefficient.
- Using a NAND controller significantly simplifies the host's tasks when using the NAND device. The processor interacts with the controller using a protocol that is much more convenient to use—a request for writing a page may be sent as a single command code followed by address and data, instead of having to bother with the complex sequencing of control lines and NAND command codes. The controller then converts the host-controller protocol into the equivalent NAND protocol sequences, while the host is free to do other tasks (or just to wait for the NAND operation to complete, if so desired).
- There are several options in the prior art regarding the location where the NAND controller resides within the system. A first approach is shown in
FIG. 2 . Here theNAND controller 114 is physically located within thehost processor 112A of thehost device 110A. If thehost processor 112A is implemented as a single die, then thecontroller 114 is incorporated on the same die. This is for example the case in some of the OMAP processors manufactured and sold by Texas Instruments. In a system built using this architecture the host processor typically interacts with the NAND controller using some proprietary protocol, as the interaction is internal to the host processor and there is no benefit in using a standard protocol. - A second prior art approach is shown in
FIGS. 3A-3B . Here theNAND controller 116 is a separate physical element, residing between thehost processor 112B of thehost 110B and theNAND device 120A. This is for example the case in portable USB Flash Drives (UFDs), such as the DiskOnKey manufactured and sold by M-Systems Flash Disk Pioneers, where there is aNAND controller 116 packaged inside the UFD and interacting using a deviceside NAND interface 124 with theNAND device 120A on one side and with thehost processor 112B on the other side (using a hostside USB interface 122 which uses the USB protocol). In a system built using this architecture the host processor typically interacts with the NAND controller using a standard protocol such as USB or ATA, as the interaction is external to the processor and it is more convenient to use standard protocols that are already supported by the processor for other purposes. - Note that according to the terminology previously defined,
NAND interface 124 is a “flash memory device side NAND interface” (i.e. adapted to interact withNAND flash device 120A) but at the sametime NAND interface 124 is also a host-type NAND interface (i.e. adapted to initiate the NAND protocol interaction). - A third prior art approach is shown in
FIG. 4 . Here theNAND controller 118 is physically located within theNAND device 120B. The flash device and the controller may even be implemented on the same die. This is for example the case in some of the MDOC storages devices manufactured and sold by M-Systems Flash Disk Pioneers and in the OneNAND devices manufactured and sold by Samsung Electronics. In a system built using this architecture thehost processor 112B typically interacts with the NAND controller using either a standard protocol such as USB or a semi-standard protocol as is the case in the MDOC and OneNAND examples mentioned above. - We can deduce from the above that a prior art stand-alone NAND controller (that is not integrated with neither the NAND device nor the host processor) will typically have some standard interface on its host side, and a NAND interface on its flash memory device side (for example, see
FIG. 3B ). Indeed one can find in the market NAND controllers exporting many interface types—USB, SD (SecureDigital), MMC (MultiMediaCard), and more. However, one cannot currently find a stand-alone NAND controller that exports NAND interface to the host. Indeed, this is reasonable to expect—a host processor that does not have built-in NAND support and requires an external controller for that purpose, typically does not have a NAND interface and cannot directly connect to a device exporting a NAND interface and therefore has no use of a controller with host-side NAND interface. On the other hand, a host processor that has built-in NAND support typically also includes a built-in NAND controller and can connect directly to a NAND device, and therefore has no need for an external NAND controller. - The prior art described above leaves one problem unsolved. Assume that there is a host processor incorporating a built-in NAND controller and a NAND interface as in
FIG. 2 . The built-in controller is designed to work with NAND devices of a certain level of reliability. This is so because a NAND controller provides a certain level of error detection and correction, and therefore cannot support NAND devices with lower reliability. For example, a NAND controller having a 1-bit ECC can work with SBC NAND devices that are specified by their manufacturers to require only this level of error correction. Such controller cannot work with two-bit-per-cell MBC NAND devices because they require 4-bit ECC, and therefore some data might not be read correctly into the processor. Similarly, a NAND controller providing 4-bit ECC can work with current two-bit-per-cell MBC NAND, but will not work with next generation MBC NAND devices that will most probably require a higher level of ECC capability. - This is so because future MBC NAND devices are expected to be less reliable than current MBC devices and to require a much stronger ECC capability. The reasons for the reduced reliability and increased error rate are twofold:
- a. The process used for manufacturing NAND devices is continuously being improved to yield smaller memory cells. While a few years ago NAND devices used 0.4 micron process, currently they use 90 nm and 70 nm technology, and this shrinking trend is expected to continue. With shrinking dimensions of the memory cells comes lower reliability, as the small dimensions make the cells more sensitive to physical effects and phenomena that previously were not important.
- b. When MBC cells with more than two bits per cell will become commercially available, they will necessarily be much less reliable than SBC cells and two-bit-per-cell MBC cells. The larger number of states that have to be represented by the cell's threshold voltage imply that the margins between states are smaller and even smaller disturbances and drifts result in incorrect reading of data. This effect could already be witnessed in the comparison between SLC and two-bit-per-cell MBC, where the ECC requirements increased from 1-bit ECC to 4-bit ECC.
- Returning now to the
host processor 112A with the built-inNAND controller 114, suppose thecontroller 114 supports only 1-bit ECC. Then this processor might not be able to use MBC NAND even though this is highly desirable because of the MBC NAND lower cost. If the MBC NAND is connected to the NAND interface of the built-in controller of the processor, which might be the only way to connect it to the processor, then the MBC NAND generates too many errors for the limited-capability ECC of the built-in controller to correct. - Similarly, if the built-in controller supports 4-bit ECC, it can use both SLC and two-bit-per-cell MBC NAND. But when NAND devices with lower reliability appear in the market, the processor is not able to benefit from their lower price because its built-in controller is not able to provide the required level of error correction.
- Therefore we see that the state of the prior art does not provide a good solution to the problem of benefiting from the cost advantage of a new NAND device, while using a host processor incorporating a built-in NAND controller designed to support a previous generation of NAND devices.
- There is an ongoing need for devices and methods that provide compatibility between a host device having an onboard NAND controller and successive generations of NAND flash memory devices.
- The aforementioned needs are satisfied by several aspects of the present invention.
- It is disclosed a controller for interfacing between a host device and a flash memory device (e.g. a NAND flash memory device) fabricated on a flash die. The presently disclosed controller includes (a) electronic circuitry fabricated on a controller die, the controller die being distinct from the flash die, (b) a first interface (for example, a host-type interface) for interfacing between the electronic circuitry and the flash memory device (e.g. the NAND flash memory device), and (c) a second interface (for example, a flash-type interface) for interfacing between the controller and the host device, wherein the second interface is a NAND interface.
- According to some embodiments, the first interface is an inter-die interface.
- According to some embodiments, the first interface is a NAND interface.
- According to some embodiments, the presently disclosed controller further includes (d) an error correction module for providing error correction for data received through one of the first and second interface.
- According to some embodiments, the presently disclosed controller further includes (d) at least one additional host-side interface for interfacing with the host device.
- It is disclosed a data storage system including (a) a flash memory device fabricated on a flash die, and (b) the presently disclosed NAND controller, where the controller is operative to communicate with the flash memory device through the first interface.
- According to some embodiments, the presently disclosed system further includes (c) a common packaging, wherein the flash memory device and the controller are both provided within the common packaging.
- According to some embodiments, the presently disclosed system further includes (c) separate respective packagings, wherein each of the flash memory device and the controller is provided within a respective packaging.
- According to some embodiments, the presently disclosed system further includes (c) a printed circuit board on which the flash memory device and the controller are mounted, wherein the flash die is directly mounted on the printed circuit board without a package.
- According to some embodiments, the presently disclosed system further includes (c) a printed circuit board on which the flash memory device and the controller are mounted, wherein the controller die is directly mounted on the printed circuit board without a package.
- It is disclosed a data storage system including (a) a host device, (b) a flash memory device fabricated on a flash die, and (c) the presently disclosed NAND controller operative to communicate with both the flash memory device through the first interface and with the host device through the second interface.
- It is disclosed a method of writing data from a host device including the steps of: (a) providing a flash memory device fabricated on a flash die and a controller fabricated on a controller die, the flash die being distinct from the controller die, (b) issuing a write command from the host device to the controller according to a NAND interface protocol, and (c) issuing a write command from the controller to the flash memory device according to a NAND interface protocol.
- According to some embodiments, the presently disclosed method further includes the step of (d) calculating parity bits by the controller.
- It is disclosed a method of reading data to a host device including the steps of: (a) providing a flash memory device fabricated on a flash die and a controller fabricated on a controller die, the flash die being distinct from the controller die, (b) issuing a read command from the host device to the controller according to a NAND interface protocol, and (c) issuing a read command from the controller to the flash memory device according to a NAND interface protocol.
- According to some embodiments, the presently disclosed method further includes the steps of (d) retrieving the data from the flash memory device to the controller, (e) retrieving parity bits associated with the retrieved data from the flash memory device to the controller, (f) correcting the retrieved data according to the retrieved parity bits, thereby generating corrected data, and (g) retrieving the corrected data from the controller to the host device.
- It is disclosed a method of creating a data storage system including the steps of (a) providing a flash memory device fabricated on a flash die, (b) providing the presently disclosed NAND controller, and (c) deploying the flash controller to the flash memory device such that the flash controller is operative to communicate with the flash memory device through the first interface.
- According to some embodiments, the presently disclosed method further includes the step of (d) packaging the flash controller and the flash memory device within a single package.
- According to some embodiments, the flash memory device and the flash controller reside within separate respective packages, and the deploying includes engaging the respective packages to each other.
- According to some embodiments, the presently disclosed method further includes the step of (d) mounting the flash memory device and the controller onto a printed circuit board, wherein the mounting includes directly mounting the flash memory die onto the printed circuit board without a package.
- According to some embodiments, the presently disclosed method further includes the step of (d) mounting the flash memory device and the controller onto a printed circuit board, wherein the mounting includes directly mounting the controller die onto the printed circuit board without a package.
- According to some embodiments, the presently disclosed method further includes the step of (d) deploying the data storage system to a host device such that the flash controller is operative to communicate with the host device through the second interface.
- These and further embodiments will be apparent from the detailed description and examples that follow.
-
FIGS. 1A-1B provide a graphical illustration of distributions of thresholds voltages of a large population of memory cells (prior art). -
FIG. 2 provides a block diagram of a prior art system including a host device and a NAND flash device. -
FIG. 3A provides a block diagram of a prior art system including a host device, a NAND controller and a NAND flash device. -
FIG. 3B provides a block diagram of a prior art NAND controller having a USB interface on the host side and a NAND interface on the flash memory device side. -
FIG. 4 provides a block diagram of a prior art system including a host device and a NAND flash device. -
FIG. 5A provides a block diagram of a NAND controller having a NAND interface on the host side and a NAND interface on the flash memory device side in accordance with exemplary embodiments of the present invention. -
FIG. 5B provides a block diagram of a system including a host device, the NAND controller ofFIG. 5A , and a NAND flash device in accordance with exemplary embodiments of the present invention. -
FIG. 6A illustrates an exemplary die configuration of the exemplary system described inFIG. 5B . -
FIG. 6B illustrates an exemplary configuration of the exemplary system described inFIG. 5B where the NAND controller and the NAND flash device reside within a single multi-chip package. -
FIG. 6C illustrates an exemplary configuration of the exemplary system described inFIG. 5B where the NAND controller and the NAND flash device reside within separate respective packages. -
FIG. 7 shows a flow chart describing a method wherein a host writes data to a NAND storage device via an external NAND controller. -
FIG. 8 shows a flowchart describing a method wherein a host reads data from a NAND storage device 120 via an external NAND controller. -
FIG. 9 is a block diagram of an exemplary controller of an embodiment. -
FIGS. 10A-10D are block diagrams of exemplary controllers of an embodiment. - The present invention will now be described in terms of specific, example embodiments. It is to be understood that the invention is not limited to the example embodiments disclosed. It should also be understood that not every feature of the controllers, systems including controllers, and methods of reading and data described is necessary to implement the invention as claimed in any particular one of the appended claims. Various elements and features of devices are described to fully enable the invention. It should also be understood that throughout this disclosure, where a process or method is shown or described, the steps of the method may be performed in any order or simultaneously, unless it is clear from the context that one step depends on another being performed first.
- U.S. patent application Ser. No. 11/326,336 (now U.S. Patent Application Publication No. US 2007/0074093 A1), which is hereby incorporated by reference, disclosed for the first time a new type of NAND controller, characterized by the fact that the interface it exports to the host side is a NAND interface. In some embodiments, this presently disclosed controller has NAND interfaces on both sides—on the flash memory device side, where the controller plays the role of a host towards the NAND device, and on the host device side, where the controller plays the role of a NAND device towards the host.
- For the purposes of this disclosure, a “NAND flash memory device” is defined as electronic circuitry including a plurality of NAND flash memory cells and any necessary control circuitry (e.g. circuitry for providing a flash-type interface) for storing data within the NAND flash memory cells. It is noted that the “NAND flash memory device” does not necessarily have its own dedicated housing, and may reside with another “device” such as a controller within a single housing. In some embodiments, the “NAND flash memory device” is directly mounted onto a printed circuit board without any packing.
- Furthermore, in some embodiments, the controller includes an error correction capability that is sufficient for correcting the many errors of a lower-reliability NAND device. Because these errors are corrected by the controller, the controller can present to the host a flash device having no errors at all, or having a smaller number of errors—small enough for the error correction capability of the host's built-in NAND controller to handle.
- Attention is now called to
FIG. 5A , which provides a schematic block diagram of a controller in accordance with some embodiments of the present invention.Controller 130 includes a flash memory device-side NAND interface 142 for interfacing to a NAND flash device. Furthermore, it is noted that flash memory device-side NAND interface 142 is also a host-type NAND interface (i.e. adapted to initiate the interaction over the NAND interface, and to present a host device to a NAND flash device). - The
controller 130 also includes a hostside NAND interface 144 for interfacing to a host that supports a NAND interface protocol. This host side NAND interface is also a flash memory-type NAND interface (e.g. thecontroller 130 is adapted to present to the host a NAND flash memory storage device). The controller may optionally include one or more additional host-side interfaces 146, for interfacing the controller to hosts using non-NAND interfaces, such as USB or MMC interfaces. - As shown in
FIG. 5A , the controller further includes anECC module 132 for detecting and correcting all or some of the errors in the data retrieved from the NAND device through device-side interface 142. TheECC module 132 may include hardware, software, firmware or any combination thereof. TheECC module 132 may correct all errors, in which case theNAND controller 130 exports to the host an error-free NAND device. Alternatively, theECC module 132 may correct only some of the errors found in the data retrieved from the NAND device through the flash memory device-side NAND interface 142. - In one example, the NAND device may have a reliability that requires 4-bit ECC, and the
ECC module 142 corrects enough of the errors to increase the data reliability up to the level that enables a 1-bit ECC module in the host's built-in NAND controller to handle the data. - It is noted that
NAND controller 130 may optionally also include one or more modules 134 (e.g. including hardware, software, firmware or any combination thereof) for providing other functionality, such as encryption functionality or address mapping that maps logical flash addresses received from the host into physical flash addresses sent to the flash device. Examples of other types of additional functionality are discussed below. - Attention is now called to
FIG. 5B which shows a schematic block diagram of an exemplary system including the external NAND controller 130 (e.g. a controller separate from the host device) described inFIG. 5A . Through deviceside NAND interface 142 theexternal NAND controller 130 interfaces withNAND flash device 120A. Through hostside NAND interface 144, theNAND controller 130 interfaces withhost device 110A. - One should note that the way
external controller 130 interfaces through the twoNAND interfaces - Using device
side NAND interface 142,external NAND controller 130 acts as the host-type part of the NAND interface protocol and theNAND device 130 acts as the flash-type part of the NAND interface protocol. Usinghost side interface 144,external controller 130 acts as the flash-type part of the NAND interface protocol and host 110A acts as the host-type part of the NAND interface protocol. - Attention is now called to
FIG. 6A which shows an exemplary die configuration of the exemplary system described inFIG. 5A . Thus, it is noted that theNAND controller 130 includeselectronic circuitry 135 fabricated on a controller die 131 while theNAND flash device 120A includeselectronic circuitry 137 fabricated on aflash die 133. The controller die 131 and the flash die 133 are distinct dies. - It is noted that elements within the
NAND controller 130 as described inFIG. 5A (i.e. theECC module 132, the flash-type NAND interface 144, the host-type NAND interfaces) are implemented at least in part by the controllerelectronic circuitry 135 residing on the controller die. - The
interface 142 between the controllerelectronic circuitry 135 and the flashelectronic circuitry 137 is an “inter-die” interface. As used herein, an “inter-die interface” (e.g. an inter-die NAND interface) is operative to interface between two distinct units of electronic circuitry residing on distinct dies (e.g. to provide the necessary physical and logical infrastructure for the distinct units of electronic circuitry to communicate with each other, for example, using one or more specific protocols). Thus, the inter-die interface includes the necessary physical elements (pads, output and input drivers, etc) for interfacing between the two distinct units of electronic circuitry residing on separate dies. - According to some embodiments, an inter-die interface may interface between electronic circuitry fabricated on two distinct dies that are packaged in a common package. This example is illustrated in
FIG. 6B , wherein both theNAND controller 130 and theNAND flash device 120A reside within acommon multi-chip package 139. - Alternatively, the inter-die interface may interface between electronic circuitry fabricated on two distinct dies packaged in distinct packages (for example, where each die is packaged in its own package). This example is illustrated in
FIG. 6C , wherein theNAND controller 130 and theNAND flash device 120A reside in separate respective packages. In particular, theNAND controller 130 resides withincontroller package 141, while theNAND flash device 120A resides withinflash package 143. Thus, as illustrated inFIG. 6C ,interface 142 is an “inter-package interface.” - It is noted that the examples where the dies reside in a common package (for example, as shown in
FIG. 6A ) and where the dies reside in separate packages (for example, as shown inFIG. 6B ) are not the only possible configurations. - Thus, alternatively, in some embodiments, the inter-die interface may interface between electronic circuitry fabricated on two distinct dies, where one or both of these dies has no package at all. For example, in many applications, due to a need to conserve space, memory dies are provided (e.g. mounted, for example, directly mounted) on boards with no packaging at all. Thus, in one example, it is noted that in the new generation of memory cards for phones, memory dies are often mounted on boards with no packaging at all. As used herein, a die which is “directly mounted” onto a printed circuit board is mounted on the printed circuit board without being packaged first.
-
FIG. 7 shows a flow chart describing a method wherein ahost 110A (e.g. a host including aNAND controller 114 within the device) writes data (e.g. a page of data) to aNAND storage device 120A via anexternal NAND controller 130. As shown inFIG. 7 , thehost 110A issues 410 a write command to the external controller 130 (e.g. a write command issued using the NAND interface protocol, including command bytes, address bytes and data bytes). Thehost 110A is not necessarily aware of the fact it is issuing the command to acontroller 130, and may assume it is interfacing with a standard NAND flash storage device of the type it is capable of handling. - The
NAND controller 130 receives the write command issued by the host (e.g. via the host-side NAND interface 144). After receiving the write command, the controller calculates ECC parity bits 420 (e.g. using ECC module 132) corresponding to the data bytes, and issues 430 a write command to the NAND device (e.g. via the flash memory device side interface 142). Again, the command is issued according to the NAND interface protocol, including command bytes, address bytes and data bytes that contain both the host's data bytes and the corresponding ECC parity bits. The NAND flash storage device is not necessarily aware that it received the command indirectly via theNAND controller 130 and not directly from thehost device 110A. Instep 440 the NANDflash storage device 120A stores the data bytes it received into the non-volatile memory cells, thus fulfilling the host's 110A request. -
FIG. 8 shows a flowchart describing a method wherein ahost 110A (e.g. a host including aNAND controller 114 within the device) reads data (e.g. a page of data) from aNAND storage device 120A via anexternal NAND controller 130. Thus, thehost 110A issues 410 a read command to the external controller 130 (e.g. a read command issued using the NAND interface protocol, including command bytes and address bytes). As in the write command above, thehost 110A is not necessarily aware of the fact it is issuing the command to anexternal controller 130, and may assume it is interfacing with a standard NAND device of the type it is capable of handling. - The
external NAND controller 130 receives the read command issued by the host (e.g. via the host-side NAND-interface 144). After receiving the read command, theexternal controller 130 issues 520 a read command (e.g. via the device-side NAND interface 142) to theNAND device 120A. Again, the command is issued according to the NAND interface protocol, including command bytes and address bytes. Instep 530 the NANDflash storage device 120A retrieves the requested data from the non-volatile cells array, where the host data is accompanied by the ECC parity bits calculated when the data had been stored. Instep 540 the data bytes and the accompanying parity bits are sent to the external NAND controller. This sending is done according to the NAND interface protocol by a series of read strobes generated by the controller, each sequentially reading into the controller one byte or one word (depending on whether the NAND interface used is 8 bits wide or 16 bits wide). Instep 550 theexternal NAND controller 130 uses the parity bits for correcting errors in the data bytes (e.g. with the ECC module 132). Instep 560 the corrected data bytes are sent to the host via the hostside NAND interface 144. The sending is again done according to the NAND interface protocol by a series of read strobes generated by the host. Thehost 110A now has the same data bytes it originally stored into the flash memory. - It can now be seen that this invention allows one to benefit from the cost advantage of new NAND devices, while using a host processor incorporating a built-in NAND controller designed to support a previous generation of NAND devices.
- As mentioned above, the NAND controller in these embodiments may include one or more modules (e.g. including hardware, software, firmware or any combination thereof) for providing other functionality, such as encryption functionality or address mapping that maps logical flash addresses received from the host into physical flash addresses sent to the flash device. The following sections provide examples of other types of additional functionality.
- Exemplary NAND Flash Memory Controller Exporting a NAND Interface
- Returning to the drawings,
FIG. 9 is a block diagram of anexemplary controller 300 of an embodiment. As shown inFIG. 9 , thecontroller 300 includes acontrol module 340 for controlling the operation of thecontroller 300 and, optionally, one or moreadditional modules 350 for providing other functions. Examples of other functions include, but are not limited to, data scrambling, column replacement, handling write aborts and/or program failures (via safe zones), read scrubbing, wear leveling, bad block and/or spare block management, error correction code (ECC) functionality, error detection code (EDC) functionality, status functionality, encryption functionality, error recovery, and address mapping (e.g., mapping of logical to physical blocks). The following paragraphs describe some of these functions, and the following section describe others of these functions. - “Data scrambling” or “scrambling” is an invertible transformation of an input bit sequence to an output bit sequence, such that each bit of the output bit sequence is a function of several bits of the input bit sequence and of an auxiliary bit sequence. The data stored in a flash memory device may be scrambled in order to reduce data pattern-dependent sensitivities, disturbance effects, or errors by creating more randomized data patterns. More information about data scrambling can be found in the following patent documents: U.S. patent application Ser. Nos. 11/808,906, 12/209,697, 12/251,820, 12/165,141, and 11/876,789, as well as PCT application no. PCT/US08/88625.
- “Column replacement” refers to various implementations of mapping or replacing entirely bad columns, portions of columns, or even individual cells. Suitable types of column replacement techniques can be found in U.S. Pat. Nos. 7,379,330 and 7,447,066.
- There are several potential problems in writing to flash memory devices where logically or physically adjacent data may be corrupted outside of the location where the data is attempted to be written. One example is when a write to one area (e.g., a cell, page, or block) of memory fails, and the contents of some surrounding memory may be corrupted. This is referred to as a “program failure” or “program disturb.” A similar effect known as “write abort” is when a write (or program) operation is terminated prematurely, for example when power is removed unexpectedly. In both cases, there are algorithms which may be used to pro-actively copy data from a “risk zone” to a “safe zone” to handle write aborts and program failures, as described in U.S. Pat. No. 6,988,175.
- “Read scrubbing” or, more generally, “scrubbing” refers to the techniques of refreshing and correcting data stored in a flash memory device to compensate for disturbs. A scrub operation entails reading data in areas that may have received exposure to potentially disturbing signals and performing some corrective action if this data is determined to have been disturbed. Read scrubbing is further described in U.S. Pat. Nos. 7,012,835, 7,224,607, and 7,477,547.
- Flash memory devices may be written unevenly, and “wear leveling” refers to techniques that attempt to even out the number of times memory cells are written over their lifetime. Exemplary wear leveling techniques are described in U.S. Pat. Nos. 6,230,233 and 6,594,183.
- In general, flash memory devices are manufactured with an excess number of blocks (greater than the defined minimum capacity). Either during factory testing or during use of the device, certain blocks may be discovered as “bad” or “defective,” meaning that they are unable to correctly store data and need to be replaced. Similarly, there may be an excess of “good” blocks (greater than the defined minimum capacity) which may be used as “spares” until another block fails or becomes defective. Keeping track of these extra blocks is known as bad block management and spare block management, respectively. More information about bad block and spare block management can be found in U.S. Pat. No. 7,171,536.
- As mentioned above, additional information about these different functional modules and how they are used in exemplary controller architectures is provided later in this document.
- Returning to the drawings, as also shown in
FIG. 9 , thecontroller 300 includes one or more flash memory device-side NAND interface(s) 335 for interfacing with one or more NAND flash device(s) 330 (e.g., 1-8 memory dies). Furthermore, it is noted that the flash memory device-side NAND interface 335 is also a host-type NAND interface (i.e., that it is adapted to initiate the interaction over the NAND interface and to present a host to a NAND flash device(s) 330). Thecontroller 300 also includes a hostside NAND interface 325 for interfacing to a host 320 (having a host controller 321) that supports a NAND interface protocol. This hostside NAND interface 325 is also a flash memory-type NAND interface (e.g., thecontroller 300 is adapted to present to the host 320 a NAND flash memory storage device). Examples of NAND interfaces include, but are not limited to, Open NAND Flash Interface (ONFI), toggle mode (TM), and a high-performance flash memory interface, such as the one described in U.S. Pat. No. 7,366,029, which is hereby incorporated by reference. Thecontroller 300 may optionally include one or more additional host-side interfaces, for interfacing thecontroller 300 to hosts using non-NAND interfaces, such as SD, USB, SATA, or MMC interfaces. Also, theinterfaces - It should be noted that the
controller 300 and flash memory device(s) 330 can be used in any desired system environment. For example, in one implementation, a product manufactured with one ormore controller 300/flash memory device(s) 330 units is used in a solid-state drive (SSD). As another example, thecontroller 300 can be used in OEM designs that use a Southbridge controller to interface to flash memory devices. - There are several advantages of using a NAND flash memory controller that exports a NAND interface to a host. To appreciate these advantages, first consider the realities of current controller architectures. Today, there are two types of NAND interfaces: a “raw” interface and a “managed” interface. With a raw interface, the basic memory is exposed with primitive commands like read, program, and erase, and the external controller is expected to provide memory management functions, such as ECC, defect management, and flash translation. With a managed interface, through some higher level interface, logical items such as sectors/pages/blocks or files are managed, and the controller manages memory management functions.
- However, the set of firmware required to “manage” the NAND can be divided into two categories. The first category is generic flash software that mostly manages the host interface, objects (and read/modify/write sequences), and caching. This is referred to as the “host management” layer. The second category is flash-specific management functionality that does, for example, the ECC, data scrambling, and specific error recovery and error prevention techniques like pro-active read scrubbing and copying lower-page blocks to prevent data loss due to write aborts, power failures, and write errors. This is referred to as the “device management” layer.
- The first category of software is relatively constant and may be provided by various companies, including OS vendors, chipset and controller vendors, and embedded device vendors. In general, let's assume there are M specific systems/OSes/ASICs that may want to use flash in their designs. The second set is potentially proprietary to individual companies and even specific to certain memory designs and generations. In general, let's assume there are N different memory specific design points. Today, this is an all-or-nothing approach to flash management—either buy raw NAND or managed NAND. This also means that a solution must incorporate one of the M system and host management environments with one of the N memory device management environments. In general, this means that either (1) a flash vendor with the second kind of knowledge must provide all layers of a solution, including ASIC controller and host interface software, and do M different designs for the M different host opportunities, or (2) any independent ASIC and firmware company has little opportunity to customize their solutions to specific memory designs without doing N different designs, or (3) two companies have to work together, potentially exposing valuable trade secrets and IP and/or implement different solutions for each memory design. This can also produce a time-to-market delay if M different host solutions have to be modified to accept any new memory design or vice versa.
- By using a NAND flash memory controller that exports a NAND interface to a host, a new logical interface is provided that uses existing physical NAND interfaces and commands, such as legacy asynchronous, ONFI, or TM, to create a new logical interface above raw or physical NAND and below logical or managed NAND, create “virtual” raw NAND memory with no ECC required in the host controller, and disable host ECC (since 0 ECC is required from the host to protect the NAND memory). This new logical interface also can provide, for example, data scrambling, scrubbing, disturbs, safe zone handling, wear leveling, and bad block management (to only expose the good blocks) “beneath” this interface level.
- This different logical interface provides several advantages over standard flash interfaces or managed NAND interfaces, including ONFI Block Abstraction (BA) or Toshiba LBA. For example, separation of the memory-specific functions that may vary from memory type and generation (e.g., NAND vs. 3D (or NOR) and 5Xnm vs. 4Xnm vs. 3Xnm) allows for different amounts of ECC, vendor-unique and memory-unique schemes for error prevention and correction schemes, such as handling disturbs and safe zones, and allows vendor-unique algorithms to remain “secret” within the controller and firmware. Additionally, there is greater commonality between technology (and vendors) at this logical interface level, which enables quicker time to market. Further, this allows much closer to 1:1 command operation, meaning improved and more-predictable performance versus managed NAND or other higher level interfaces.
- There are additional advantages associated with this controller architecture. For example, it allows for independent development, test, and evolution of memory technology from the host and other parts of the system. It can also allow for easier and faster deployment of next generation memories, since changes to support those memories are more localized. Further, it allows memory manufactures to protect secret algorithms used to manage the raw flash. Also, page management can be integrated with the file system and/or other logical mapping. Thus, combined with standard external interfaces (electrical and command sets), this architecture makes it easier to design in raw flash that is more transparent from generation to generation.
- There is at least one other secondary benefit from the use of this architecture—the
controller 300 only presents a single electrical load on the external interface and drives the raw flash internal to the MCP. This allows for potentially greater system capacity without increasing the number of flash channels, higher speed external interfaces (since fewer loads), and higher-speed internal interfaces to the raw flash devices (since very tightly-controlled internal design (substrate connection) is possible). - Another advantage associated with the controller of this embodiment is that is can be used to provide a “split bus” architecture through the use of different host and memory buses, potentially at different speeds (i.e., the bus between the host and the controller can be different from the bus between the controller and the flash memory device(s)). (As used herein, a “bus” is an electrical connection of multiple devices (e.g., chips or dies) that have the same interface. For example, a point-to-point connection is a bus between two devices, but most interface standards support having multiple devices connected to the same electrical bus.) This architecture is especially desired in solid-state drives (SSDs) that can potentially have hundreds of flash memory devices. In conventional SSD architectures, the current solution is to package N normal flash memory devices in a multi-chip package (MCP), but this still creates N loads on a bus, creating N times the capacitance and inductance. The more loads on a bus, the slower it operates. For example, one current architecture can support a 80 MHz operation with 1-4 devices but can support only a 40 MHz operation with 8-16 devices. This is the opposite of what is desired—higher speeds if more devices are used. Furthermore, more devices imply the need for greater physical separation between the host and the memory MCPs. For example, if 16 packages were used, they will be spread over a relatively large physical distance (e.g., several inches) in an arbitrary topology (e.g., a bus or star-shaped (or arbitrary stub) topology). This also reduces the potential performance of any electrical interface. So, to obtain, for example, 300 MHz of transfers (ignoring bus widths), either four fast buses or eight slow buses can be used. But, the fast buses could only support four flash memory devices each, or 16 total devices, which is not enough for most SSDs today. If the buses run faster, the number of interface connections (pins and analog interfaces) can be reduced, as well as potentially the amount of registers and logic in the host.
- Because the
controller 300 in this embodiment splits the interconnection between the host and the raw flash memory device(s) into a separate host side interface and a flash side interface with a buffer in between, the host bus has fewer loads and can run two to four times faster. Further, since the memory bus is internal to the MCP, it can have lower power, higher speed, and lower voltage because of the short distance and finite loads involved. Further, the two buses can run at different frequencies and different widths (e.g., one side could use an 8-bit bus, and the other side can use a 16-bit bus). - While some architectures may insert standard transceivers to decouple these buses, the
controller 300 of this embodiment can use buffering and can run these interfaces at different speeds. This allows thecontroller 300 to also match two different speed buses, for example, a flash side interface bus running at 140 MB/sec and an ONFI bus that runs at either 132 or 166 MB/sec. A conventional bus transceiver design would have to pick the lower of the two buses and run at 132 MB/sec in this example, while thecontroller 300 of this embodiment can achieve 140 MB/sec by running the ONFI bus at 166 MB/sec and essentially have idle periods. Accordingly, thecontroller 300 of this embodiment provides higher performance at potentially lower cost and/or lower power and interface flexibility between different products (e.g., different speed and width host and memory buses, fewer loads on the host in a typical system (which enables faster operation and aggregation of the memory bus bandwidth to the host interface), and different interfaces on the host and memory side with interface translation). - As mentioned above, a single controller can also have multiple flash side interface(s) 335 to the flash memory device(s), which also enables further parallelism between raw flash memory devices and transfers into the controller, which allows the flash side interface to run slower (as well as faster) than the
host side interface 325. A single controller can also have multiple host side interfaces that may be connected to different host controller interfaces to allow for greater parallelism in accessing the flash memory device(s), to share the controller, or to better match the speed of the flash side interface (which could be faster than the host side interface for the reasons described above). - Another advantage of importing a NAND interface to a host relates to the use of a distributed controller architecture. Today, flash memory devices are typically implemented with a single level of controller. In large solid-state drives (SSDs), there may be tens or even hundreds of flash devices. In high-performance devices, it may be desirable to have parallel operations going on in as many of these flash devices as possible, which may be power constrained. There are interface specs today at 600 MB/sec, and these are still increasing. To reach this level of performance requires very fast controllers, memories, and ECC modules. Today, high performance controllers are built with either one or a small number of ECC modules and one or two microprocessors to handle memory device management. Since some of the functions are very localized to the memory devices themselves, such as ECC, with the
controller 300 of this embodiment, a two-tiered network of devices can be utilized. Specifically, thehost 320 can manage the host interface and high-level mapping of logical contents, and one ormore controllers 300 can manage one or more raw NAND flash memory devices to provide local management of memory device functions (e.g., ECC) and parallelism in the execution of these functions due to parallel execution of thecontroller 300 and thehost 320 and parallel execution ofmultiple controllers 300 handling different operations in parallel ondifferent memories 320. In contrast to conventional controllers in SSDs, which perform memory device management functions in one place, by splitting these functions into two layers, this architecture can take advantage of parallel performance in two ways (e.g., between host and slave, and between many slaves). This enables higher total performance levels (e.g., 600 MB/sec) without having to design a single ECC module or microprocessor that can handle that rate. - Yet another advantage of this architecture is that a higher-level abstraction of the raw memory can be developed, such that system developers do not need to know about error recovery or the low-level details of the memory, such as ECC and data scrambling, since the
controller 300 can be used to perform those functions in addition to handling memory-specific functions such as read, erase, and program disturbs, and safe zones. This level of support is referred to herein as “corrected” flash,” which is logically in between raw flash and managed NAND. On the other hand, this architecture is not fully managed memory in the sense of page or block management at a logical level and may require the host to provide for logical-to-physical mapping of pages and blocks. However, thecontroller 300 can still present some flash memory management restrictions to the host and its firmware, such as: only full pages can be programmed, pages must be written in order within a block, and pages can only be written once before the entire block must be erased. Wear leveling of physical blocks to ensure that they are used approximately evenly can also be performed by thecontroller 300; however, thehost 320 can be responsible for providing this function. Also, thecontroller 300 preferably presents thehost 320 with full page read and write operations into pages and blocks of NAND. The characteristics of logical page size and block size will likely be the same as the underlying NAND (unless partial page operations are supported). The majority of the spare area in each physical page in the raw NAND will be used by thecontroller 300 for ECC and its metadata. Thecontroller 300 can provide for a smaller number of spare bytes that the using system can utilize for metadata management. - Exemplary NAND Flash Memory Controller Embodiment
- This section discusses an exemplary controller architecture and provides more details on some of the various functional modules discussed above. As noted above, a “module” can be implemented in any suitable manner, such as with hardware, software/firmware, or a combination thereof, and the functionality of a “module” can be performed by a single component or distributed among several components in the controller.
- Returning now to the drawings,
FIG. 10A is a diagram of a presently preferred implementation of theNAND controller 300 ofFIG. 9 . It should be understood that any of the components shown in these drawings can be implemented as hardware, software/firmware, or a combination thereof. In this implementation, thefirst NAND Interface 325 inFIG. 9 is implemented by the Host Interface Module (“HIM”) 3010. TheHIM 3010 is a collection of logic that supports the “host side interface” as a “flash device-type interface.” TheHIM 3010 comprises a first-in-first-out (“FIFO”)module 3080, acontrol unit 3090, a cyclic redundancy check (“CRC”) module 3100 (although another type of error detection code (“EDC”) module can be used), acommand register 3110, anaddress register 3120, and a host direct memory access (“HDMA”)unit 3130. In this embodiment, theHIM 3010 takes the form of an ONFI HIM. As will be discussed in more detail below, some HIMs receive a high-level request from a host controller for a relatively-large amount of data that spans several pages, and the NAND controller determines what actions are needed to satisfy the request. In contrast, an ONFI HIM receives several smaller-sized requests (e.g., for individual pages) from a host controller, so the ONFI HIM is required to simultaneously handle multiple (e.g., eight) read and write requests. - Returning to
FIG. 10A , thesecond NAND Interface 335 ofFIG. 9 is implemented here by a Flash Interface Module (“FIM”) 3020. In a current embodiment, theFIM 3020 is implemented as a collection of logic and a low-level programmable sequencer that creates the “device side interface” as a “host-type interface.” In this embodiment, theFIM 3020 comprises acommand register 3140, anaddress register 3150, an ECC encodemodule 3160, anECC decode module 3170, adata scrambler 3180, and a data descrambler 3190. - Internal to the
NAND controller 300 is aprocessor 3040, which has local ROM, code RAM, and data RAM. Acentral bus 3030 connects theprocessor 3040, theHIM 3010, theFIM 3020, and the other modules described below and is used to transfer data between the different modules shown. Thisbi-directional bus 3030 may be either an electrical bus with actual connections to each internal component or an Advanced High-Speed Bus (“AHB”) used in conjunction with an ARC microprocessor, which logically connects the various modules using an interconnect matrix. Thecentral bus 3030 can transmits data, control signals, or both. TheNAND controller 300 also comprises a buffer RAM (“BRAM”) 3050 that is used to temporarily store pages of data that are either being read or written, and anECC correction engine 3060 for correcting errors. TheNAND controller 300 further comprises anencryption module 3070 for perfommiing encryption/decryption functions. - The
NAND controller 300 can further comprise a column replacement module, which is implemented here by either the FIM sequencer, firmware in theprocessor 3040, or preferably in a small amount of logic and a table located in theFIM 3020. The column replacement module allows the flash memory device(s) 330 (FIG. 9 ) to contain information on bad column locations. The bad column address information is contained in the flash memory device(s) 330 and is scanned by firmware prior to any read or write operation. After firmware scans the flash memory device(s) 330, it builds a bad column address table with the bad column location to be used by the column replacement module. On flash write operations, the column replacement module inserts the data (0xFFFF) for the address that is detected in a bad column address table. On flash read operations, data from the bad column address will be discarded. - With the components of the
NAND controller 300 now generally described, exemplary write and read operations of theNAND controller 300 will now be presented. Turning first to a write operation, theFIFO 3080 in theHIM 3010 acts as a buffer for an incoming write command, address, and data from a host controller and synchronizes those elements to the system card domain. TheCRC module 3100 checks the incoming information to determine if any transmission errors are present. (TheCRC module 3100 is an example of the EDC module discussed above.) The CRC module generates or checks an error detection code to check for transmission errors as part of an end-to-end data protection scheme. If no errors are detected, thecontrol unit 3090 decodes the command received from theFIFO 3080 and stores it in thecommand register 3110, and also stores the address in theaddress register 3120. The data received from the host controller is sent through theHDMA AHB interface 3130 to theBRAM 3050 via thecentral bus 3030. Thecontrol unit 3090 sends an interrupt to theprocessor 3040, in response to which theprocessor 3040 reads the command from thecommand register 3080 and theaddress register 3120 and, based on the command, sets up the data path in theFIM 3020 and stores the command in the FIM'scommand register 3140. Theprocessor 3040 also translates the address from theNAND interface 325 into an internal NAND address and stores it in the FIM'saddress register 3150. If logical-to-physical address conversion is to be performed, theprocessor 3040 can use a mapping table to create the correct physical address. Theprocessor 3040 can also perform one or more additional functions described below. Theprocessor 3040 then sets up a data transfer from theBRAM 3050 to theFIM 3020. - The
FIM 3020 takes the value from theaddress register 3150 and formats it in accordance with the standard of theNAND interface 335. The data stored in theBRAM 3050 is sent to theencryption module 3070 for encryption and is then sent through thedata scrambler 3180. Thedata scrambler 3180 scrambles the data and outputs the data to the FIM'sECC encoder 3160, which generates the ECC parity bits to be stored with the data. The data and ECC bits are then transferred over the second NAND interface with the write command to the flash memory device(s) for storage. As an example of an additional function that may occur during writes, if protection for write aborts or program failures is enabled and if the write request is to an upper page address, theprocessor 3040 can send a read command to the flash memory device(s) over the second NAND interface for the corresponding lower page and then send a program command to have it copied into a safe zone (a spare scratchpad area) by writing it back to another location in the flash memory device(s) 330. If an error occurs in writing the upper page, the lower page can still be read back from the safe zone and the error corrected. (This is an example of the module discussed above for handling write aborts and/or program failures via safe zones.) - Turning now to a read operation, the
HIM 3010 receives a read command from a host controller, and theprocessor 3040 reads the command and logical address. If logical-to-physical address conversion is to be performed, the firmware in theprocessor 3040 could use a mapping table to create the correct physical address. (This is an example of the address mapping module discussed above.) The firmware then sends the physical address over thesecond NAND interface 335 to the flash memory device(s) 330. After the read access, the data is transferred over the NAND interface, decoded and used to generate the syndrome data for error correction, descrambled by the data descrambler 3190, and then sent over thecentral bus 3030 to theBRAM 3050. TheECC correction engine 3060 is used to correct any errors that can be corrected using the ECC on the data that is stored in theBRAM 3050. Since the ECC may be computed and stored in portions of a physical page, theprocessor 3040 can be interrupted as each portion of the page is received or corrected, or once when all of the data is transferred. Theencryption module 3070 then performs a decryption operation on the data. The timing described above is flexible since thefirst NAND interface 325 and thesecond NAND interface 335 may operate at different speeds, and the firmware can transfer the data using either store-and-forward techniques or speed-match buffering. When the data is sent back to the host controller, it is sent through theHIM 3010, and the transmission CRC is sent back to the host over thefirst NAND interface 325 to check for transmission error. - As mentioned above, in addition to handling commands sent from the host controller, the
processor 3040 may perform one or more additional functions asynchronously or independent of any specific command sent by the host. For example, if theECC correction engine 3060 detects a correctable soft error, theECC correction engine 3060 can correct the soft error and also interrupt theprocessor 3040 to log the page location so that the corresponding block could be read scrubbed at a later point in time. Other exemplary background tasks that can be performed by theprocessor 3040 are wear leveling and mapping of bad blocks and spare blocks, as described below. - Turning again to the drawings,
FIG. 10B is a block diagram showing a more detailed view of a NAND controller of an embodiment. As with the controller shown inFIG. 10A , the controller in this embodiment contains anONFI HIM 3200 and aFIM 3260 that communicate through a central bus (here, an Advanced Microcontroller Bus Architecture (“AMBA”) High-performance Bus (“AHB”)multi-layer matrix bus 3270 for the data path and an advanced peripheral bus (“APB”) 3330 for the command path). TheONFI HIM 3200 and theFIM 3260 can be associated with any of the processors. For example, theONFI HIM 3200 can be associated with an ARC600 microprocessor 3280 (with a built-in cache 3285) that runs ARC code stored in aMRAM 3290. In general, theARC600 3280 is used to service interrupts from theONFI HIM 3200 and manages the data path setup and transfers information to theflash control RISC 3250. Theflash control RISC 3250 is the microprocessor that can be used with theFIM 3260 and, in general, handles the function of setting up theFIM 3260 by generating micro-control codes to various components in theFIM 3260. More particularly, theflash control RISC 3250 sets up the flash direct memory access (“FDMA”)module 3440 in theFIM 3260, which communicates with theAHB bus 3270 and generates the AHB bus protocol commands to read data from theDRAM 3220. Theflash control RISC 3250 also sets up theEDC module 3450, which contains the ECC encoder and decoder. TheMRAM 3240 stores code used to run theflash control RISC 3250. - The NAND controller in this embodiment also contains a
ROM 3210 that stores instruction code to get the controller running upon boot-up. Additional components of the NAND controller include aDRAM 3220, anECC correction engine 3230, anencrypt module 3300, anAPB bridge 3310, an interruptcontroller 3320, and a clock/reset management module 3340. - The
encryption module 3300 enciphers and deciphers 128 bit blocks of data using either a 128, 192, or 256 bit key according to the Advanced Encryption Standard (AES). For write operations, after data is received from the host and sent to the BRAM 3050 (FIG. 10A ) by the ONFI HIM, theARC600 processor 3280 creates a control block with defined parameters of the encipher operations. Theencryption module 3300 then performs the encipher operations and stores the resulting data toBRAM 3050 and interrupts theARC600 processor 3280 to indicate that the data is ready. For read operations, after the ECC engine completes error correction in theBRAM 3050, theARC600 processor 3280 creates a control block with defined parameters of the decipher operations. Theencryption module 3300 then performs the decipher operations and stores the resulting data to theBRAM 3050 and interrupts theARC600 processor 3280 to indicate data is ready. - Turning now to the
ONFI HIM 3220 and theFIM 3260 in more detail, theONFI HIM 3220 comprises anONFI interface 3350 that operates either in an asynchronous mode or a source synchronous mode, which is part of the ONFI standard. (Asynchronous (or “async”) mode is when data is latched with the WE# signal for writes and the RE# signal for reads. Source synchronous (or “source (src) sync”) is when the strobe (DQS) is forwarded with the data to indicate when the data should be latched.) TheONFI HIM 3200 also contains acommand FIFO 3360, adata FIFO 3370, adata controller 3380, aregister configuration module 3400, a host direct memory access (“HDMA”)module 3380, and aCRC module 3415, which function as described above in conjunction withFIG. 10A . TheONFI HIM 3200 further contains anAPB interface 3390 and anAHB port 3420 for communicating with theAPB bus 3330 and theAHB bus 3270, respectively. TheFIM 3260 comprises anEDC module 3450 that includes an EDC encoder and an EDC decoder, a flash protocol sequencer (“FPS”) 3430, which generates commands to the NAND bus based on micro-control codes provided by theflash control RISC 3250 or theARC600 microprocessor 3280, anFDMA 3440, a data scrambler/de-scrambler 3470 and aNAND interface 3460. - The scrambler/
descrambler 3470 performs a transformation of data during both flash write transfers (scrambling) and flash read transfers (de-scrambling). The data stored in the flash memory device(s) 330 may be scrambled in order to reduce data pattern-dependent sensitivities, disturbance effects, or errors by creating more randomized data patterns. By scrambling the data in a shifting pattern across pages in the memory device(s) 330, the reliability of the memory can be improved significantly. The scrambler/descrambler 3470 processes data on-the-fly and is configured by either theARC600 processor 3280 or theFlash Control RISC 3250 using register accesses. ECC check bit generation is performed after scrambling. ECC error detection is performed prior to de-scrambling, but correction is performed after descrambling. - The NAND controller in this embodiment processes write and read operations generally as described above with respect to
FIG. 10A . For example, for a write operation, thecommand FIFO 3360 and thedata FIFO 3370 store an incoming write command and data, and theCRC module 3415 checks the incoming information to determine if any transmission errors are present. If no errors are detected, thedata controller 3380 decodes the command received from thecommand FIFO 3360 and stores it in a command register in theregister configuration module 3400. The address received from the host controller is stored in the address register in theregister configuration module 3400. The data received from the host controller is sent through theHDMA 3410 to theDRAM 3220. Thedata controller 3380 then sends an interrupt to theARC600 3280 or theFlash Control RISC 3250, which reads the command from the command register, reads the address from the address register, and passes control to theflash control RISC 3250 to set up theFIM 3260 to start reading the data from DRAM 322 and perform ECC and data scrambling operations, the result of which is sent to the flash memory device(s) 330 for storage. TheARC600 microprocessor 3280 and/or theFIM 3260 can perform additional operations. For example, theFIM 3260 can perform column replacement, and the following operations can be performed using theARC600 microprocessor 3280 together with the FIM 360: bad block and spare block management, safe zones, read scrubbing, and wear leveling. These operations are described in more detail below. - For a read operation, the
ONFI HIM 3200 sends an interrupt to theARC600 microprocessor 3280 when a read command is received. TheARC600 microprocessor 3280 then passes the command and address information to theflash control RISC 3250, which sets up theFPS 3430 to generate a read command to the NAND flash memory device(s) 330. Once the data is ready to be read from the NAND flash memory device(s) 330, theFPS 3430 starts sending read commands to the NAND bus. The read data goes through theNAND interface unit 3460 to thedata descrambler 3470 and then through theEDC module 3450, which generates the syndrome bits for ECC correction. The data and syndrome bits are then passed through theFDMA 3440 and stored in theDRAM 3220. Theflash control RISC 3250 then sets up theECC correction engine 3230 to correct any errors. Theencrypt module 3300 can decrypt the data at this time. TheARC600 microprocessor 3280 then receives an interrupt and programs theregister configuration module 3400 in theONFI HIM 3200 to state that the data is ready to be read from theDRAM 3220. Based on this information, theONFI HIM 3200 reads the data from theDRAM 3220 and stores it in thedata FIFO 3370. TheONFI HIM 3200 then sends a ready signal to the host controller to signal that the data is ready to be read. - As mentioned above, unlike other HIMs, an ONFI HIM receives several smaller-sized requests (e.g., for individual pages) from a host controller, so the ONFI HIM is required to simultaneously handle multiple (e.g., eight) read and write requests. In this way, there is more bi-directional communication between the ONFI HIM and the host controller than with other HIMs. Along with this increased frequency in communication comes more parallel processing to handle the multiple read and write requests.
-
FIGS. 10C and 10D illustrate the logical operations of an ONFI HIM for read and write operations, respectively. Turning first toFIG. 10C , theONFI HIM 3480 of this embodiment receives a read command from a host controller through anONFI bus 3490. TheONFI HIM 3480 can operate in an asynch or a source synch mode and communicates the read command to acommand FIFO 3540 viasignal multiplexors ONFI HIM 3480 can be used in an async mode and source sync mode using the Async and ONFIsource sync components ONFI HIM 3480 also stores the address received from the host controller in a logical unit number (“LUN”)address FIFO 3550. (The NAND controller in this embodiment supports multiple logical units, which are treated as independent entities that are addressable by LUN addresses.) The command and address are read from theFIFOs data controller 3560, which synchronizes these items. The command anddata controller 3560 then sends an interrupt to thesystem register controller 3570, which generates an interrupt to the ARC600 microcontroller. The ARC600 microcontroller then reads the LUN address from the register in thesystem register controller 3570, and the process of reading data from the flash memory device(s) is as described above. When all the read data is written to the DRAM, the ARC600 microprocessor program the status register in thesystem register controller 3570 to inform theONFI HIM 3480 that the data is ready to be read. TheONFI HIM 3480 then reads the data through theHDMA 3580 using the readrequest control unit 3585. The read data is stored in theread data FIFO 3590, which is partitioned for eachLUN 3595. Once that is done, a ready indicator is stored in the status register, and the data is streamed to the host controller. - Turning now to
FIG. 10D , in a write operation, a write command is received from a host controller through anONFI 3410 bus. TheONFI HIM 3400 communicates the write command to acommand FIFO 3460 viasignal multiplexors ONFI HIM 3400 can be used in an async mode and source sync mode using the Async and ONFIsource sync components ONFI HIM 3400 also stores the address received from the host controller in a logical unit number (“LUN”)address FIFO 3470. The data received from the host controller is stored in awrite data FIFO 3520. The command and address are read from theFIFOs data controller 3480, which synchronizes these items. The command anddata controller 3480 then sends an interrupt to thesystem register controller 3490, which generates an interrupt to the ARC600 microcontroller. The ARC600 microcontroller then reads the LUN address from the register in thesystem register controller 3490, and the process of setting-up the controller from a write operation is as described above. TheHDMA 3530 has anAHB port 3540 in communication with theAHB bus 3550 and sends the data to the DRAM. TheCRC module 3545 checks for transmission errors in the data. Once the data has been stored in the flash memory device(s) 330 and the flash memory device(s) 330 indicate ready and the status of program operation is successful or fail, a ready indicator is stored in the status register in thesystem register controller 3490, indicating that theONFI HIM 3400 is ready for another command from the host controller. - Returning to
FIG. 10A , theNAND controller 300 can also handle program failures and erase failures. As the NAND flash memory device(s) 330 attached to the flash interface module 3020 (hereafter FIM) are programmed, the NAND memory device(s) 330 report the success or failure of the program operation to the NAND controller 300 (or optionally to the ONFI Host through the host interface module 3010 (hereafter HIM)). The NAND memory device(s) 330 may experience some number of program failures over the expected life of the memory due to defects in the NAND cells or due to the limited endurance the NAND cells have with regard to erase and program cycles. - The NAND memory device(s) 330 will return a FAIL status to the
controller 300 when the program page operation does not complete successfully. The controller processor 3040 (FIG. 10A ) or flash protocol sequencer 3430 (FIG. 10B ) verifies the success or failure of each program page operation. Generally, the failure of any single program page operation will cause the processor 3040 (or optionally the ONFI Host) to regard the entire NAND block (which may contain multiple pages) to be defective. The defective block will be retired from use. Typically, thecontroller 300 will copy the data that was not successfully programmed and any data in preceding pages in the defective block to another replacement block (a spare block). Thecontroller 300 may read preceding pages into theBRAM 3050 using theFIM 3020, the data de-scrambler 3190, and theECC decoder 3170 and applying ECC correction as needed. The data is then written to the replacement block using theFIM 3020 in the normal fashion. - One aspect of program failures is that a failure programming one page may corrupt data in another page that was previously programmed. Typically, this would be possible with MLC NAND memory which is organized physically with upper and lower logical pages sharing a word-line within the memory array. A typical usage would be to program data into a lower page and subsequent data into the upper page. One method to prevent the loss of data in the lower page when a program failure occurs when programming the upper page on the word-line is to read the lower page data prior to programming the upper page. The lower page data could be read into the
controller BRAM 3050 and could additionally be programmed into a scratch pad area in the non-volatile flash memory device(s) 330, sometimes called a “safe zone.” The data thus retained in theBRAM 3050 or safe zone would then be protected from loss due to a programming failure and would be available to be copied to the replacement block, particularly in cases where the data was corrupted in the lower page of the NAND memory device(s) 330 and could no longer be read successfully. - It is possible that some NAND failure modes could similarly corrupt data in other areas of the memory array, such as on adjacent word lines. This method of reading other potentially vulnerable data into the
controller BRAM 3050, and/or saving the data into a scratch pad or safe zone area could also be used to protect data in these circumstances. - As the NAND flash memory device(s) 330 attached to the
FIM 3020 are erased, the NAND memory device(s) 330 report the success or failure of the block erase operation to the NAND controller 300 (or optionally to the ONFI Host through the HIM 3010). The NAND memory device(s) 330 will return a FAIL status to thecontroller 300 when the erase operation does not successfully complete. Thecontroller processor 3040 or circuits in theflash protocol sequencer 3430 verifies the success or failure of each erase operation. Generally, the failure of any erase operation will cause the processor 3040 (or ONFI Host) to regard the entire NAND block to be defective. The defective block will be retired from use and a spare block used in its place. - The
NAND controller 300 can also handle program disturbs, erase disturbs, and read disturbs within the flash memory device. - The internal NAND programming operations could possibly effect, or disturb, other areas of the memory array, causing errors when attempting to read those other areas. One method to prevent failures from program disturb is to perform reads or “read scrubbing” operations on potentially vulnerable areas in conjunction with programming operations, in order to detect disturb effects before they become uncorrectable or unrecoverable errors. Once a disturb condition is detected (by high soft error rates during the read scrubbing operation), the controller processor 3040 (or the external ONFI host) can copy the data to another area in the flash memory device(s) 330.
- The internal NAND erase operations could possibly effect, or disturb other areas of the memory array, causing errors when attempting to read those other areas. One method to prevent failures from erase disturb is to perform reads or “read scrubbing” operations on potentially vulnerable areas in conjunction with erase operations, in order to detect disturb effects before they become uncorrectable or unrecoverable errors. Once a disturb condition is detected, the controller processor 3040 (or the external ONFI host) can copy the data to another area in the flash memory device(s) 330.
- The internal NAND read operations could possibly effect, or disturb other areas of the memory array, causing errors when attempting to read those other areas. The disturb effects can sometimes accumulate over many read operations. One method to prevent failures from program disturb is to perform reads or “read scrubbing” operations on potentially vulnerable areas in conjunction with read operations, in order to detect disturb effects before they become uncorrectable or unrecoverable errors. Once a disturb condition is detected, the controller processor 3040 (or the external ONFI host) can copy the data to another area in the flash memory device(s) 330.
- Referring now to
FIG. 10A , theNAND controller 300 handles read errors in the following manner. Typically, the data that is programmed into the NAND memory device(s) 330 through theFIM 3020 has an error detection or error correction code appended and stored with the data in the NAND array. Thecontroller 300 uses theECC encoder 3160 for this function. When such data is read from the flash array to theBRAM 3050, theECC decoder 3170 re-generates the ECC code from the data and compares it to the ECC code that was appended to the data when programmed into the flash. If the data is identical to the data that was written, the ECC circuits indicate that there is no data error present. If some difference in the read data is detected, and the difference is small enough to be within the capability of the ECC to correct, the read data (typically contained in the BRAM 3050) is “corrected” or modified to restore it to the original value by theECC correction engine 3060, as controlled by theprocessor 3040. If the data errors exceed the ECC correction capability, an “uncorrectable” read error occurs. Typically, an uncorrectable read error would result in an error status being returned to the Host interface when read. - One method to prevent uncorrectable read errors, or to recover when an error is detected, is for the controller 300 (or the external ONFI host) to retry the read operation. The retry may use shifted margin levels or other mechanisms to decrease the errors within the data, perhaps eliminating the errors or reducing the number of errors to a level that is within the ECC correction capability.
- Optionally, when a read error is recovered, or if the amount of ECC correction needed to recover the data meets or exceeds some threshold, the data could be re-written to the same or to another block in order to restore the data to an error-free or improved condition. The original data location may optionally be considered as defective, in which case it could be marked as defective and retired from use.
- Referring again to
FIG. 10A , theNAND controller 300 can also handle write aborts. Write aborts are the unexpected loss of power to thecontroller 300 and NAND memory device(s) 330 while a program or erase operation is in progress. The loss of power can result in incomplete programming or erase conditions in the NAND memory device(s) 330 that could result in uncorrectable read errors. In some cases, such as with MLC NAND, other pages that share a word line (i.e., a lower page) could be corrupted by an aborted program operation on the upper page of a word line, much like the program failure condition described above. - There are several methods to reduce or eliminate write abort errors, or minimize their impact. One method is to use a low voltage detection circuit to notify the
processor 3040 that the power has been interrupted. Theprocessor 3040 can then allow current program or erase operations to finish but not allow new operations to start. Ideally, the current operations would have enough time with sufficient power to complete. - An alternative method, perhaps used in conjunction with the low voltage detection method, is to add capacitance or a battery (or some alternative power supply source) to the power supply circuits to extend the power available to complete program or erase operations.
- Another method is to provide a scratch pad “safe zone” similar to that described above. Any “old” data that exists in lower pages that may be vulnerable during an upper page program could be read and saved in the safe zone before the upper page program is started. That would provide protection for previously-programmed data in case of a power loss event. In some implementations, it may be acceptable to not be able to read data that was corrupted in a write abort situation, but other possibly un-related older data must be protected.
- Another method is to search for potential write abort errors when the controller is powered on. If an error is found that can be determined (or assumed) to be a result of a write abort, the error data may be discarded. In this situation, the
controller 300 effectively reverts back to previous data, and the interrupted operation is as if it did not happen. - Referring again to
FIG. 10A , theNAND controller 300 can also conduct wear leveling on the memory. Wear leveling is a method to increase overall product endurance and lifetime by more evenly distributing block usage amongst all physical blocks than would otherwise occur as a result of normal flash management algorithms. This is done by forcing “cold” blocks to the spare blocks pool, which will in turn be used for host data updates, and, at the same time, moving the data from “cold” blocks, which are not updated by the host, to a “hot” block. This swap will result in mixing up “hot” and “cold” blocks. The swap can be done either randomly or cyclically, choosing blocks for the swap, or choosing them on the basis of a hot count (number of program-erase cycles) analysis. The swap can be done periodically, say in every 100 block cycles, typically calibrated by a system parameter to balance between overall system performance and evening of block usage to balance wear and performance overhead. - An example high level sequence is:
-
- 1. Schedule wear leveling operation
- 2. Identify “hot” and “cold” blocks by either hot count analysis or on random or cyclic basis.
- 3. Copy data from the selected “cold” block to the selected “hot” free block in the free block pool.
- 4. Release the “cold” block to the free block pool. As a result, the free block pool is populated by a cold block instead of hot one.
- Some operations can be skipped, like analysis-based blocks selection. The wear level operation itself can also be skipped if block wear distribution is detected as even.
- The wear level operations and hot count management are performed in firmware by the
processor 3040, such that the host controller 121 (FIG. 9 ) will not be aware of these housekeeping flash block level operations - Referring to
FIG. 10A , thecontroller 300 can also implement read scrubbing on the flash memory device(s) 330 upon detection of a read disturb. Read operations to one area of the NAND memory array within the flash memory device(s) 330 may affect or disturb other areas of the memory array, causing cells to shift from one state to another, and ultimately causing bit errors when attempting to read data previously stored to those other areas. The disturb effects can accumulate over many read operations, eventually leading to a number of bit errors that may exceed the data correction capabilities of the system. The errors that exceed the system correction capabilities are referred to as uncorrectable errors. One method to prevent failures from program disturbs is to perform reads or “scrubbing” operations on potentially vulnerable areas, in order to detect disturb effects before they become uncorrectable or unrecoverable errors. Once a disturb condition is detected, typically by detecting that there are a number of bits in error on the data read, theprocessor 3040 can move the data to another area in the memory generally by copying the data to another area of the NAND memory array in order to “refresh” it. - Read scrub copy is usually triggered by correctable ECC error discovered by the ECC correction engine 3060 (
FIG. 10A ), either in blocks read during the course of a host read operation, an internal system read operation, or by a scheduled read scrub scan. System read operations are those needed by the flash storage system to read firmware, parameters, or mapping information stored in the NAND flash. Read scrub scan is a read of all data in a block to determine whether any data contained therein has been disturbed. Blocks are selected for a read scrub scan typically when they have been partially read during the course of a host read or system read operation, but may also be selected using other criteria, such as randomly, or via deterministic sequencing through the blocks of memory. Because a read scrub scan operation takes time and affects data throughput of the system, the system may select blocks for read scrub scan only periodically or infrequently, by use of a random selection, a counter, or other mechanisms. The frequency of scheduling may be calibrated to balance between the system performance needs, and the frequency require to detect disturbed data before it becomes uncorrectable. Upon detection of a correctable error that has some number of bits in error above a pre-defined threshold, the read scrub copy is scheduled for the block. - Read scrub copy is a method by which data is read from the disturbed block and written to another block, after correction of all data which has correctable ECC error. The original block can then be returned to the common free block pool and eventually erased and written with other data. Read scrub scan and read scrub copy scheduling will be done in the
NAND controller 300 in firmware by theprocessor 3040, such that the host controller 121 will not be aware of these housekeeping flash block level operations. - Finally, the following patent applications, which were filed Aug. 11, 2009 and are hereby incorporated by reference, provide additional embodiments that can be used with the embodiments presented herein: “Controller and Method for Interfacing Between a Host Controller in a Host and a Flash Memory Device,” U.S. patent application Ser. No. 12/539,394; “Controller and Method for Detecting a Transmission Error Over a NAND Interface Using Error Detection Code,” U.S. patent application Ser. No. 12/539,407; and “Controller and Method for Providing Read Status and Spare Block Management Information in a Flash Memory System,” U.S. patent application Ser. No. 12/539,379.
- In the description and claims of the present application, each of the verbs, “comprise” “include” and “have”, and conjugates thereof, are used to indicate that the object or objects of the verb are not necessarily a complete listing of members, components, elements or parts of the subject or subjects of the verb.
- The present invention has been described using detailed descriptions of embodiments thereof that are provided by way of example and are not intended to limit the scope of the invention. The described embodiments comprise different features, not all of which are required in all embodiments of the invention. Some embodiments of the present invention utilize only some of the features or possible combinations of the features. Variations of embodiments of the present invention that are described and embodiments of the present invention comprising different combinations of features noted in the described embodiments will occur to persons of the art.
Claims (45)
1. A controller for interfacing between a host controller in a host device and a flash memory device, the controller comprising:
a first NAND interface configured to transfer data between the host controller and the controller using a NAND interface protocol, wherein the first NAND interface is further configured to receive, from the host controller, (i) one of a read command and a write command and (ii) a logical address;
an address conversion module configured to convert the logical address received from the host controller to a physical address of the flash memory device;
a second NAND interface configured to transfer data between the controller and the flash memory device using a NAND interface protocol in accordance with the one of the read command and the write command received from the host controller;
an error correction code (ECC) module configured to calculate ECC bits for data received through at least one of the first and second NAND interfaces; and
an additional functionality module.
2. The controller of claim 1 , wherein the additional functionality module comprises a data scrambling module.
3. The controller of claim 1 , wherein the additional functionality module comprises a column replacement module.
4. The controller of claim 1 , wherein the additional functionality module comprises a module that handles at least one of a write abort and a program failure.
5. The controller of claim 1 , wherein the additional functionality module comprises a read scrubbing module.
6. The controller of claim 1 , wherein the additional functionality module comprises a wear leveling module.
7. The controller of claim 1 , wherein the additional functionality module comprises a module that manages at least one of bad blocks and spare blocks.
8. The controller of claim 1 , wherein the additional functionality module comprises an encryption module.
9. The controller of claim 1 , wherein the NAND interface protocol used by the first NAND interface is the same as the NAND interface protocol used by the second NAND interface.
10. The controller of claim 1 , wherein the NAND interface protocol used by the first NAND interface is different from the NAND interface protocol used by the second NAND interface.
11. The controller of claim 1 , wherein a bus between the host device and the controller is different from a bus between the controller and the flash memory device.
12. A controller for interfacing between a host controller in a host device and a flash memory device, the controller comprising:
a first NAND interface configured to transfer data between the host controller and the controller using a NAND interface protocol, wherein the first NAND interface is further configured to receive, from the host controller, (i) one of a read command and a write command and (ii) a physical address of the flash memory device;
a second NAND interface configured to transfer data between the controller and the flash memory device using a NAND interface protocol in accordance with the one of the read command and the write command received from the host controller;
an error correction code (ECC) module configured to calculate ECC bits for data received through at least one of the first and second NAND interfaces; and
an additional functionality module.
13. The controller of claim 12 , wherein the additional functionality module comprises a data scrambling module.
14. The controller of claim 12 , wherein the additional functionality module comprises a column replacement module.
15. The controller of claim 12 , wherein the additional functionality module comprises a module that handles at least one of a write abort and a program failure.
16. The controller of claim 12 , wherein the additional functionality module comprises a read scrubbing module.
17. The controller of claim 12 , wherein the additional functionality module comprises a wear leveling module.
18. The controller of claim 12 , wherein the additional functionality module comprises a module that manages at least one of bad blocks and spare blocks.
19. The controller of claim 12 , wherein the additional functionality module comprises an encryption module.
20. The controller of claim 12 , wherein the additional functionality module comprises an address mapping module.
21. The controller of claim 12 , wherein the NAND interface protocol used by the first NAND interface is the same as the NAND interface protocol used by the second NAND interface.
22. The controller of claim 12 , wherein the NAND interface protocol used by the first NAND interface is different from the NAND interface protocol used by the second NAND interface.
23. The controller of claim 12 , wherein a bus between the host device and the controller is different from a bus between the controller and the flash memory device.
24. A method for interfacing between a host controller in a host device and a flash memory device, the method comprising:
performing in a controller in communication with the host controller and the flash memory device:
receiving (i) one of a read command and a write command and (ii) a logical address from the host controller, wherein (i) the one of the read command and the write command and (ii) the logical address are received through a first NAND interface of the controller using a NAND interface protocol;
converting the logical address received from the host controller to a physical address of the flash memory device;
transferring data between the host controller and the controller in accordance with the one of the read command and the write command received from the host controller, wherein the data is transferred through the first NAND interface of the controller using the NAND interface protocol;
transferring data between the controller and the physical address of the flash memory device in accordance with the one of the read command and the write command received from the host controller, wherein the data is transferred through a second NAND interface of the controller using a NAND interface protocol;
calculating error correction code (ECC) bits for the data received through at least one of the first and second NAND interfaces; and
performing an additional function using an additional functionality module of the controller.
25. The method of claim 24 , wherein performing the additional function comprises performing a data scrambling operation.
26. The method of claim 24 , wherein performing the additional function comprises performing a column replacement operation.
27. The method of claim 24 , wherein performing the additional function comprises handling at least one of a write abort and a program failure.
28. The method of claim 24 , wherein performing the additional function comprises performing a read scrubbing operation.
29. The method of claim 24 , wherein performing the additional function comprises performing a wear leveling operation.
30. The method of claim 24 , wherein performing the additional function comprises managing at least one of bad blocks and spare blocks.
31. The method of claim 24 , wherein performing the additional function comprises performing an encryption operation.
32. The method of claim 24 , wherein the NAND interface protocol used by the first NAND interface is the same as the NAND interface protocol used by the second NAND interface.
33. The method of claim 24 , wherein the NAND interface protocol used by the first NAND interface is different from the NAND interface protocol used by the second NAND interface.
34. The method of claim 24 , wherein a bus between the host device and the controller is different from a bus between the controller and the flash memory device.
35. A method for interfacing between a host controller in a host device and a flash memory device, the method comprising:
performing in a controller in communication with the host controller and the flash memory device:
receiving (i) one of a read command and a write command and (ii) a physical address of the flash memory device from the host controller, wherein (i) the one of the read command and the write command and (ii) the physical address are received through a first NAND interface of the controller using a NAND interface protocol;
transferring data between the host controller and the controller in accordance with the one of the read command and the write command received from the host controller, wherein the data is transferred through the first NAND interface of the controller using the NAND interface protocol;
transferring data between the controller and the physical address of the flash memory device in accordance with the one of the read command and the write command received from the host controller, wherein the data is transferred through a second NAND interface of the controller using a NAND interface protocol;
calculating error correction code (ECC) bits for the data received through at least one of the first and second NAND interfaces; and
performing an additional function using an additional functionality module of the controller.
36. The method of claim 35 , wherein performing the additional function comprises performing a data scrambling operation.
37. The method of claim 35 , wherein performing the additional function comprises performing a column replacement operation.
38. The method of claim 35 , wherein performing the additional function comprises handling at least one of a write abort and a program failure.
39. The method of claim 35 , wherein performing the additional function comprises performing a read scrubbing operation.
40. The method of claim 35 , wherein performing the additional function comprises performing a wear leveling operation.
41. The method of claim 35 , wherein performing the additional function comprises managing at least one of bad blocks and spare blocks.
42. The method of claim 35 , wherein performing the additional function comprises performing an encryption operation.
43. The method of claim 35 , wherein the NAND interface protocol used by the first NAND interface is the same as the NAND interface protocol used by the second NAND interface.
44. The method of claim 35 , wherein the NAND interface protocol used by the first NAND interface is different from the NAND interface protocol used by the second NAND interface.
45. The method of claim 35 , wherein a bus between the host device and the controller is different from a bus between the controller and the flash memory device.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/596,926 US20130111113A1 (en) | 2005-09-26 | 2012-08-28 | NAND Flash Memory Controller Exporting a NAND Interface |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US72009805P | 2005-09-26 | 2005-09-26 | |
US11/326,336 US7631245B2 (en) | 2005-09-26 | 2006-01-06 | NAND flash memory controller exporting a NAND interface |
US12/539,417 US8291295B2 (en) | 2005-09-26 | 2009-08-11 | NAND flash memory controller exporting a NAND interface |
US13/596,926 US20130111113A1 (en) | 2005-09-26 | 2012-08-28 | NAND Flash Memory Controller Exporting a NAND Interface |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/539,417 Continuation US8291295B2 (en) | 2005-09-26 | 2009-08-11 | NAND flash memory controller exporting a NAND interface |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130111113A1 true US20130111113A1 (en) | 2013-05-02 |
Family
ID=41569710
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/539,417 Active 2027-01-26 US8291295B2 (en) | 2005-09-26 | 2009-08-11 | NAND flash memory controller exporting a NAND interface |
US13/596,926 Abandoned US20130111113A1 (en) | 2005-09-26 | 2012-08-28 | NAND Flash Memory Controller Exporting a NAND Interface |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/539,417 Active 2027-01-26 US8291295B2 (en) | 2005-09-26 | 2009-08-11 | NAND flash memory controller exporting a NAND interface |
Country Status (1)
Country | Link |
---|---|
US (2) | US8291295B2 (en) |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014193376A1 (en) * | 2013-05-30 | 2014-12-04 | Hewlett-Packard Development Company, L.P. | Separate memory controllers to access data in memory |
WO2014204331A1 (en) * | 2013-06-17 | 2014-12-24 | Llc "Topcon Positioning Systems" | Nand flash memory interface controller with gnss receiver firmware booting capability |
TWI509622B (en) * | 2013-07-09 | 2015-11-21 | Univ Nat Taiwan Science Tech | Fault bits scrambling memory and method thereof |
TWI553641B (en) * | 2013-12-09 | 2016-10-11 | 慧榮科技股份有限公司 | Data storage device and mode detection method thereof |
US9886378B2 (en) | 2014-04-29 | 2018-02-06 | Samsung Electronics Co., Ltd. | Nonvolatile memory system using control signals to transmit varied signals via data pins |
WO2019152192A1 (en) | 2018-02-05 | 2019-08-08 | Micron Technology, Inc. | Memory systems having controllers embedded in packages of integrated circuit memory |
US10489313B2 (en) | 2016-10-31 | 2019-11-26 | Alibaba Group Holding Limited | Flash storage failure rate reduction and hyperscale infrastructure robustness enhancement through the MRAM-NOR flash based cache architecture |
US10552063B2 (en) | 2018-06-21 | 2020-02-04 | International Business Machines Corporation | Background mitigation reads in a non-volatile memory system |
US10699791B2 (en) | 2018-08-24 | 2020-06-30 | International Business Machines Corporation | Adaptive read voltage threshold calibration in non-volatile memory |
WO2020176183A1 (en) * | 2019-02-25 | 2020-09-03 | Micron Technology, Inc. | Storage device operation orchestration |
US10782908B2 (en) | 2018-02-05 | 2020-09-22 | Micron Technology, Inc. | Predictive data orchestration in multi-tier memory systems |
US10824352B2 (en) | 2017-12-06 | 2020-11-03 | International Business Machines Corporation | Reducing unnecessary calibration of a memory unit for which the error count margin has been exceeded |
US10852949B2 (en) | 2019-04-15 | 2020-12-01 | Micron Technology, Inc. | Predictive data pre-fetching in a data storage device |
US10880401B2 (en) | 2018-02-12 | 2020-12-29 | Micron Technology, Inc. | Optimization of data access and communication in memory systems |
US10877892B2 (en) | 2018-07-11 | 2020-12-29 | Micron Technology, Inc. | Predictive paging to accelerate memory access |
US10936205B2 (en) | 2017-10-05 | 2021-03-02 | International Business Machines Corporation | Techniques for retention and read-disturb aware health binning |
US11099789B2 (en) | 2018-02-05 | 2021-08-24 | Micron Technology, Inc. | Remote direct memory access in multi-tier memory systems |
US11184030B2 (en) | 2019-12-11 | 2021-11-23 | Samsung Electronics Co., Ltd. | Storage controller for correcting error, storage device including the same, and operating method thereof |
US11416395B2 (en) | 2018-02-05 | 2022-08-16 | Micron Technology, Inc. | Memory virtualization for accessing heterogeneous memory components |
DE102015105414B4 (en) | 2014-04-15 | 2023-12-07 | Infineon Technologies Ag | Editing a destination storage |
Families Citing this family (155)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8291295B2 (en) | 2005-09-26 | 2012-10-16 | Sandisk Il Ltd. | NAND flash memory controller exporting a NAND interface |
WO2007037757A1 (en) * | 2005-09-29 | 2007-04-05 | Trek 2000 International Ltd | Portable data storage using slc and mlc flash memory |
US8549236B2 (en) * | 2006-12-15 | 2013-10-01 | Siliconsystems, Inc. | Storage subsystem with multiple non-volatile memory arrays to protect against data losses |
JP4994112B2 (en) * | 2007-05-22 | 2012-08-08 | ルネサスエレクトロニクス株式会社 | Semiconductor integrated circuit device and memory control method |
US8051358B2 (en) | 2007-07-06 | 2011-11-01 | Micron Technology, Inc. | Error recovery storage along a nand-flash string |
US8065583B2 (en) | 2007-07-06 | 2011-11-22 | Micron Technology, Inc. | Data storage with an outer block code and a stream-based inner code |
US8103936B2 (en) * | 2007-10-17 | 2012-01-24 | Micron Technology, Inc. | System and method for data read of a synchronous serial interface NAND |
US8046542B2 (en) | 2007-11-21 | 2011-10-25 | Micron Technology, Inc. | Fault-tolerant non-volatile integrated circuit memory |
US8499229B2 (en) | 2007-11-21 | 2013-07-30 | Micro Technology, Inc. | Method and apparatus for reading data from flash memory |
US8120990B2 (en) | 2008-02-04 | 2012-02-21 | Mosaid Technologies Incorporated | Flexible memory operations in NAND flash devices |
US8068365B2 (en) | 2008-02-04 | 2011-11-29 | Mosaid Technologies Incorporated | Non-volatile memory device having configurable page size |
JP5166074B2 (en) * | 2008-02-29 | 2013-03-21 | 株式会社東芝 | Semiconductor memory device, control method thereof, and error correction system |
US8806293B2 (en) * | 2008-10-09 | 2014-08-12 | Micron Technology, Inc. | Controller to execute error correcting code algorithms and manage NAND memories |
US8572443B2 (en) * | 2009-04-08 | 2013-10-29 | International Business Machines Corporation | System, method, and computer program product for determining a retention behavior for at least one block of a memory device having finite endurance and/or retention |
US8112682B2 (en) * | 2009-04-23 | 2012-02-07 | Sandisk Il Ltd | Method and device for bad-block testing |
US8286004B2 (en) * | 2009-10-09 | 2012-10-09 | Lsi Corporation | Saving encryption keys in one-time programmable memory |
US8555141B2 (en) * | 2009-06-04 | 2013-10-08 | Lsi Corporation | Flash memory organization |
US8200857B2 (en) * | 2009-11-30 | 2012-06-12 | Lsi Corporation | Coalescing multiple contexts into a single data transfer in a media controller architecture |
US20100306451A1 (en) * | 2009-06-01 | 2010-12-02 | Joshua Johnson | Architecture for nand flash constraint enforcement |
US8321639B2 (en) * | 2009-12-30 | 2012-11-27 | Lsi Corporation | Command tracking for direct access block storage devices |
US8245112B2 (en) * | 2009-06-04 | 2012-08-14 | Lsi Corporation | Flash memory organization |
US8166258B2 (en) * | 2009-07-24 | 2012-04-24 | Lsi Corporation | Skip operations for solid state disks |
US8219776B2 (en) * | 2009-09-23 | 2012-07-10 | Lsi Corporation | Logical-to-physical address translation for solid state disks |
US8180981B2 (en) * | 2009-05-15 | 2012-05-15 | Oracle America, Inc. | Cache coherent support for flash in a memory hierarchy |
US20110041039A1 (en) * | 2009-08-11 | 2011-02-17 | Eliyahou Harari | Controller and Method for Interfacing Between a Host Controller in a Host and a Flash Memory Device |
US20110041005A1 (en) * | 2009-08-11 | 2011-02-17 | Selinger Robert D | Controller and Method for Providing Read Status and Spare Block Management Information in a Flash Memory System |
US20110040924A1 (en) * | 2009-08-11 | 2011-02-17 | Selinger Robert D | Controller and Method for Detecting a Transmission Error Over a NAND Interface Using Error Detection Code |
KR101678909B1 (en) * | 2009-09-17 | 2016-11-23 | 삼성전자주식회사 | Flash memory system and erase refresh methods for the same |
US20110102997A1 (en) * | 2009-11-02 | 2011-05-05 | Ocz Technology Group, Inc. | Mass storage device and method of accessing memory devices thereof |
EP2507710B1 (en) * | 2009-11-30 | 2018-10-31 | Hewlett-Packard Enterprise Development LP | Remapping for memory wear leveling |
CN102110027A (en) * | 2009-12-23 | 2011-06-29 | 威刚科技(苏州)有限公司 | Storage device with abnormal voltage protection and operating method thereof |
US8595411B2 (en) | 2009-12-30 | 2013-11-26 | Sandisk Technologies Inc. | Method and controller for performing a sequence of commands |
US8443263B2 (en) | 2009-12-30 | 2013-05-14 | Sandisk Technologies Inc. | Method and controller for performing a copy-back operation |
KR101648531B1 (en) * | 2010-02-12 | 2016-08-17 | 삼성전자주식회사 | Nonvolatile memory system and operation method using the same |
US9098430B2 (en) * | 2010-03-22 | 2015-08-04 | Conversant Intellectual Property Management Inc. | Composite semiconductor memory device with error correction |
US8386895B2 (en) | 2010-05-19 | 2013-02-26 | Micron Technology, Inc. | Enhanced multilevel memory |
US8402320B2 (en) * | 2010-05-25 | 2013-03-19 | Oracle International Corporation | Input/output device including a mechanism for error handling in multiple processor and multi-function systems |
US8286027B2 (en) * | 2010-05-25 | 2012-10-09 | Oracle International Corporation | Input/output device including a mechanism for accelerated error handling in multiple processor and multi-function systems |
TWI438777B (en) * | 2010-06-10 | 2014-05-21 | Global Unichip Corp | A hardware module as xor parity control |
US9569320B2 (en) | 2010-12-01 | 2017-02-14 | Seagate Technology Llc | Non-volatile memory program failure recovery via redundant arrays |
US20120167100A1 (en) * | 2010-12-23 | 2012-06-28 | Yan Li | Manual suspend and resume for non-volatile memory |
US8819328B2 (en) | 2010-12-30 | 2014-08-26 | Sandisk Technologies Inc. | Controller and method for performing background operations |
US8570999B1 (en) | 2011-01-19 | 2013-10-29 | Greenvity Communications, Inc. | System and method for communications in a network |
JP5259755B2 (en) * | 2011-02-25 | 2013-08-07 | 株式会社東芝 | MEMORY DEVICE HAVING MULTICHANNEL AND MEMORY ACCESS METHOD IN THE DEVICE |
US8924627B2 (en) | 2011-03-28 | 2014-12-30 | Western Digital Technologies, Inc. | Flash memory device comprising host interface for processing a multi-command descriptor block in order to exploit concurrency |
US9170878B2 (en) * | 2011-04-11 | 2015-10-27 | Inphi Corporation | Memory buffer with data scrambling and error correction |
US20120297248A1 (en) * | 2011-05-17 | 2012-11-22 | Alan David Bennett | Block write handling after corruption |
US9076528B2 (en) * | 2011-05-31 | 2015-07-07 | Micron Technology, Inc. | Apparatus including memory management control circuitry and related methods for allocation of a write block cluster |
US8694719B2 (en) | 2011-06-24 | 2014-04-08 | Sandisk Technologies Inc. | Controller, storage device, and method for power throttling memory operations |
US9406346B2 (en) | 2011-06-30 | 2016-08-02 | Sandisk Technologies Llc | Smart bridge for memory core |
US9003102B2 (en) | 2011-08-26 | 2015-04-07 | Sandisk Technologies Inc. | Controller with extended status register and method of use therewith |
US8700834B2 (en) * | 2011-09-06 | 2014-04-15 | Western Digital Technologies, Inc. | Systems and methods for an enhanced controller architecture in data storage systems |
US9195530B1 (en) | 2011-09-06 | 2015-11-24 | Western Digital Technologies, Inc. | Systems and methods for improved data management in data storage systems |
US8707104B1 (en) | 2011-09-06 | 2014-04-22 | Western Digital Technologies, Inc. | Systems and methods for error injection in data storage systems |
US8713357B1 (en) | 2011-09-06 | 2014-04-29 | Western Digital Technologies, Inc. | Systems and methods for detailed error reporting in data storage systems |
US8839083B2 (en) * | 2011-10-25 | 2014-09-16 | Taejin Info Tech Co., Ltd. | Secure error detection and synchronous data tagging for high-speed data transfer |
US20130124778A1 (en) * | 2011-11-10 | 2013-05-16 | Greenliant Llc | Method of storing host data and meta data in a nand memory, a memory controller and a memory system |
KR20130052971A (en) * | 2011-11-14 | 2013-05-23 | 삼성전자주식회사 | Method of operating non-volatile memory devices |
US8862798B1 (en) * | 2011-12-02 | 2014-10-14 | Altera Corporation | Fast parallel-to-serial memory data transfer system and method |
KR20130070251A (en) * | 2011-12-19 | 2013-06-27 | 에스케이하이닉스 주식회사 | Bridge chipset and data storage system including the same |
US8700961B2 (en) | 2011-12-20 | 2014-04-15 | Sandisk Technologies Inc. | Controller and method for virtual LUN assignment for improved memory bank mapping |
US9208070B2 (en) * | 2011-12-20 | 2015-12-08 | Sandisk Technologies Inc. | Wear leveling of multiple memory devices |
US9141308B2 (en) | 2011-12-30 | 2015-09-22 | Sandisk Technologies Inc. | Controller and method for using a transaction flag for page protection |
US9116620B2 (en) | 2011-12-30 | 2015-08-25 | Sandisk Technologies Inc. | Controller and method for memory aliasing for different flash memory types |
US9213632B1 (en) * | 2012-02-29 | 2015-12-15 | Marvell International Ltd. | Systems and methods for data storage devices to use external resources |
US8862952B1 (en) * | 2012-03-16 | 2014-10-14 | Western Digital Technologies, Inc. | Prioritized memory scanning for data storage systems |
US9053008B1 (en) | 2012-03-26 | 2015-06-09 | Western Digital Technologies, Inc. | Systems and methods for providing inline parameter service in data storage devices |
US8760922B2 (en) | 2012-04-10 | 2014-06-24 | Sandisk Technologies Inc. | System and method for micro-tiering in non-volatile memory |
TWI454916B (en) * | 2012-05-08 | 2014-10-01 | Phison Electronics Corp | Storage unit management method, memory controller and memory storage device using the same |
CN103425586B (en) * | 2012-05-17 | 2016-09-14 | 群联电子股份有限公司 | Storage unit management method, Memory Controller and memorizer memory devices |
US9183085B1 (en) | 2012-05-22 | 2015-11-10 | Pmc-Sierra, Inc. | Systems and methods for adaptively selecting from among a plurality of error correction coding schemes in a flash drive for robustness and low latency |
US8996957B1 (en) * | 2012-05-22 | 2015-03-31 | Pmc-Sierra, Inc. | Systems and methods for initializing regions of a flash drive having diverse error correction coding (ECC) schemes |
US8788910B1 (en) | 2012-05-22 | 2014-07-22 | Pmc-Sierra, Inc. | Systems and methods for low latency, high reliability error correction in a flash drive |
US8972824B1 (en) | 2012-05-22 | 2015-03-03 | Pmc-Sierra, Inc. | Systems and methods for transparently varying error correction code strength in a flash drive |
US9176812B1 (en) | 2012-05-22 | 2015-11-03 | Pmc-Sierra, Inc. | Systems and methods for storing data in page stripes of a flash drive |
US8793556B1 (en) | 2012-05-22 | 2014-07-29 | Pmc-Sierra, Inc. | Systems and methods for reclaiming flash blocks of a flash drive |
US9021337B1 (en) | 2012-05-22 | 2015-04-28 | Pmc-Sierra, Inc. | Systems and methods for adaptively selecting among different error correction coding schemes in a flash drive |
US9021336B1 (en) | 2012-05-22 | 2015-04-28 | Pmc-Sierra, Inc. | Systems and methods for redundantly storing error correction codes in a flash drive with secondary parity information spread out across each page of a group of pages |
US9021333B1 (en) | 2012-05-22 | 2015-04-28 | Pmc-Sierra, Inc. | Systems and methods for recovering data from failed portions of a flash drive |
US9047214B1 (en) | 2012-05-22 | 2015-06-02 | Pmc-Sierra, Inc. | System and method for tolerating a failed page in a flash device |
TWI495998B (en) * | 2012-08-01 | 2015-08-11 | Phison Electronics Corp | Data management method, memory controller and memory storage device |
CN103593255B (en) * | 2012-08-15 | 2016-12-21 | 群联电子股份有限公司 | Data managing method, memory storage and memory storage controller |
US9471484B2 (en) | 2012-09-19 | 2016-10-18 | Novachips Canada Inc. | Flash memory controller having dual mode pin-out |
US8990670B2 (en) * | 2012-09-28 | 2015-03-24 | Intel Corporation | Endurance aware error-correcting code (ECC) protection for non-volatile memories |
US9847139B2 (en) * | 2012-10-01 | 2017-12-19 | Seagate Technology Llp | Flash channel parameter management with read scrub |
KR101979735B1 (en) * | 2012-11-02 | 2019-05-17 | 삼성전자 주식회사 | Non-volatile memory system and host communicating with the same |
US9577673B2 (en) | 2012-11-08 | 2017-02-21 | Micron Technology, Inc. | Error correction methods and apparatuses using first and second decoders |
US9466382B2 (en) | 2012-11-14 | 2016-10-11 | Sandisk Technologies Llc | Compensation for sub-block erase |
US8830717B2 (en) | 2012-11-29 | 2014-09-09 | Sandisk Technologies Inc. | Optimized configurable NAND parameters |
US8988941B2 (en) | 2012-12-18 | 2015-03-24 | SanDisk Tehcnologies Inc. | Select transistor tuning |
US9652376B2 (en) | 2013-01-28 | 2017-05-16 | Radian Memory Systems, Inc. | Cooperative flash memory control |
US9081666B2 (en) | 2013-02-15 | 2015-07-14 | Seagate Technology Llc | Non-volatile memory channel control using a general purpose programmable processor in combination with a low level programmable sequencer |
FR3003051B1 (en) * | 2013-03-08 | 2016-07-29 | Peugeot Citroen Automobiles Sa | METHOD OF VERIFYING DATA INTEGRITY OF AN ONBOARD CALCULATOR |
MY180992A (en) * | 2013-03-13 | 2020-12-15 | Intel Corp | Memory latency management |
US9478271B2 (en) * | 2013-03-14 | 2016-10-25 | Seagate Technology Llc | Nonvolatile memory data recovery after power failure |
US9053012B1 (en) | 2013-03-15 | 2015-06-09 | Pmc-Sierra, Inc. | Systems and methods for storing data for solid-state memory |
US9026867B1 (en) | 2013-03-15 | 2015-05-05 | Pmc-Sierra, Inc. | Systems and methods for adapting to changing characteristics of multi-level cells in solid-state memory |
US9009565B1 (en) | 2013-03-15 | 2015-04-14 | Pmc-Sierra, Inc. | Systems and methods for mapping for solid-state memory |
US9081701B1 (en) | 2013-03-15 | 2015-07-14 | Pmc-Sierra, Inc. | Systems and methods for decoding data for solid-state memory |
US9208018B1 (en) | 2013-03-15 | 2015-12-08 | Pmc-Sierra, Inc. | Systems and methods for reclaiming memory for solid-state memory |
US9218890B2 (en) | 2013-06-03 | 2015-12-22 | Sandisk Technologies Inc. | Adaptive operation of three dimensional memory |
TWI514394B (en) * | 2013-08-27 | 2015-12-21 | Toshiba Kk | Semiconductor memory device and its control method |
US10185515B2 (en) | 2013-09-03 | 2019-01-22 | Qualcomm Incorporated | Unified memory controller for heterogeneous memory on a multi-chip package |
US9142324B2 (en) | 2013-09-03 | 2015-09-22 | Sandisk Technologies Inc. | Bad block reconfiguration in nonvolatile memory |
US9218886B2 (en) * | 2013-12-10 | 2015-12-22 | SanDisk Technologies, Inc. | String dependent parameter setup |
US9798493B2 (en) | 2013-12-16 | 2017-10-24 | International Business Machines Corporation | Firmware bypass for medium-access commands |
US9671973B2 (en) | 2013-12-20 | 2017-06-06 | Empire Technology Development Llc | Data storage in degraded solid state memory |
US9417960B2 (en) * | 2013-12-20 | 2016-08-16 | Seagate Technology Llc | Preventing programming errors from occurring when programming flash memory cells |
US9696920B2 (en) * | 2014-06-02 | 2017-07-04 | Micron Technology, Inc. | Systems and methods for improving efficiencies of a memory system |
US9613715B2 (en) | 2014-06-16 | 2017-04-04 | Sandisk Technologies Llc | Low-test memory stack for non-volatile storage |
US10691838B2 (en) * | 2014-06-20 | 2020-06-23 | Cypress Semiconductor Corporation | Encryption for XIP and MMIO external memories |
US9959203B2 (en) | 2014-06-23 | 2018-05-01 | Google Llc | Managing storage devices |
US9606882B2 (en) * | 2014-07-17 | 2017-03-28 | Sandisk Technologies Llc | Methods and systems for die failure testing |
US9542118B1 (en) | 2014-09-09 | 2017-01-10 | Radian Memory Systems, Inc. | Expositive flash memory control |
US10552085B1 (en) | 2014-09-09 | 2020-02-04 | Radian Memory Systems, Inc. | Techniques for directed data migration |
US9652321B2 (en) * | 2014-09-23 | 2017-05-16 | Intel Corporation | Recovery algorithm in non-volatile memory |
US9529668B2 (en) * | 2014-09-26 | 2016-12-27 | Intel Corporation | Method and system for using NAND page buffers to improve the transfer buffer utilization of a solid state drive |
KR102358053B1 (en) | 2014-10-28 | 2022-02-04 | 삼성전자주식회사 | Storage device including a plurality of nonvolatile memory chips |
US10528410B2 (en) * | 2014-12-16 | 2020-01-07 | Intel Corporation | Apparatus, method and system to exchange error information in a unified protocol communication |
US9722774B2 (en) * | 2015-04-29 | 2017-08-01 | Samsung Electronics Co., Ltd. | Non-leaky helper data: extracting unique cryptographic key from noisy F-PUF fingerprint |
KR102367982B1 (en) | 2015-06-22 | 2022-02-25 | 삼성전자주식회사 | Data storage device and data processing system having the same |
KR102403266B1 (en) | 2015-06-22 | 2022-05-27 | 삼성전자주식회사 | Data storage device and data processing system having the same |
US9577854B1 (en) | 2015-08-20 | 2017-02-21 | Micron Technology, Inc. | Apparatuses and methods for asymmetric bi-directional signaling incorporating multi-level encoding |
US9691473B2 (en) | 2015-09-22 | 2017-06-27 | Sandisk Technologies Llc | Adaptive operation of 3D memory |
US9401216B1 (en) | 2015-09-22 | 2016-07-26 | Sandisk Technologies Llc | Adaptive operation of 3D NAND memory |
US11385797B2 (en) | 2015-10-05 | 2022-07-12 | Micron Technology, Inc. | Solid state storage device with variable logical capacity based on memory lifecycle |
TWI571881B (en) * | 2015-10-23 | 2017-02-21 | 群聯電子股份有限公司 | Valid data merging method, memory controller and memory storage apparatus |
JP6646213B2 (en) * | 2016-01-19 | 2020-02-14 | 富士通株式会社 | Storage control device, storage device, and storage control method |
US10078458B1 (en) * | 2016-03-31 | 2018-09-18 | EMC IP Holding Company LLC | Method and system for adaptively migrating data in solid state memory |
US10783146B2 (en) | 2016-07-19 | 2020-09-22 | Sap Se | Join operations in hybrid main memory systems |
US10698732B2 (en) * | 2016-07-19 | 2020-06-30 | Sap Se | Page ranking in operating system virtual pages in hybrid memory systems |
US11449232B1 (en) * | 2016-07-22 | 2022-09-20 | Pure Storage, Inc. | Optimal scheduling of flash operations |
KR20180023079A (en) | 2016-08-23 | 2018-03-07 | 에스케이하이닉스 주식회사 | Semiconductor system |
KR20180086816A (en) * | 2017-01-23 | 2018-08-01 | 에스케이하이닉스 주식회사 | Memory device and electronic device performing adaptive error correction with pre-checking error rate and method of operating the memory device |
US10164817B2 (en) * | 2017-03-21 | 2018-12-25 | Micron Technology, Inc. | Methods and apparatuses for signal translation in a buffered memory |
US10388392B2 (en) * | 2017-04-08 | 2019-08-20 | Texas Instruments Incorporated | Safe execution in place (XIP) from flash memory |
US10446197B2 (en) | 2017-08-31 | 2019-10-15 | Micron Technology, Inc. | Optimized scan interval |
US10558393B2 (en) * | 2017-10-20 | 2020-02-11 | Qualcomm Incorporated | Controller hardware automation for host-aware performance booster |
US10754580B2 (en) | 2017-10-23 | 2020-08-25 | Micron Technology, Inc. | Virtual partition management in a memory device |
KR102406868B1 (en) | 2017-11-23 | 2022-06-10 | 삼성전자주식회사 | Semiconductor memory device, memory system and method of operating the same |
WO2019113729A1 (en) | 2017-12-11 | 2019-06-20 | Micron Technology, Inc. | Scheme to improve efficiency of garbage collection in cached flash translation layer |
US10564868B2 (en) | 2018-01-24 | 2020-02-18 | Western Digital Technologies, Inc. | Method and apparatus for selecting power states in storage devices |
US11709539B2 (en) | 2018-01-24 | 2023-07-25 | Western Digital Technologies, Inc. | Low power state staging |
CN108170382B (en) * | 2018-02-05 | 2023-12-12 | 力瑞信(深圳)科技有限公司 | Solid state disk and data reading system |
US10365854B1 (en) | 2018-03-19 | 2019-07-30 | Micron Technology, Inc. | Tracking data temperatures of logical block addresses |
US10824568B2 (en) * | 2018-07-25 | 2020-11-03 | Western Digital Technologies, Inc. | Speculative pre-fetching of flash translation layer tables for use with solid state systems |
TWI740187B (en) * | 2019-02-20 | 2021-09-21 | 慧榮科技股份有限公司 | Access method |
US11093164B2 (en) * | 2019-08-27 | 2021-08-17 | Micron Technology, Inc. | Handling bad blocks generated during a block erase operation |
US11467737B2 (en) * | 2020-12-04 | 2022-10-11 | Micron Technology, Inc. | Reducing probabilistic data integrity scan collisions |
US11409599B2 (en) | 2020-12-04 | 2022-08-09 | Micron Technology, Inc. | Managing probabilistic data integrity scans in workloads with localized read patterns |
US11609857B2 (en) | 2020-12-04 | 2023-03-21 | Micron Technology, Inc. | Identification and caching of frequent read disturb aggressors |
US11699498B2 (en) | 2020-12-04 | 2023-07-11 | Micron Technology, Inc. | Managing probabilistic data integrity scan intervals |
CN112700813B (en) * | 2020-12-25 | 2023-12-22 | 北京浪潮数据技术有限公司 | NAND control method, device and equipment based on wear state |
US11556420B2 (en) | 2021-04-06 | 2023-01-17 | Macronix International Co., Ltd. | Managing error correction coding in memory systems |
US20230236753A1 (en) * | 2022-01-21 | 2023-07-27 | Micron Technology, Inc. | Predictive sanitization of an array of memory with capacitive cells and/or ferroelectric cells |
Family Cites Families (165)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5268870A (en) | 1988-06-08 | 1993-12-07 | Eliyahou Harari | Flash EEPROM system and intelligent programming and erasing methods therefor |
US5430859A (en) | 1991-07-26 | 1995-07-04 | Sundisk Corporation | Solid state memory system including plural memory chips and a serialized bus |
GB2259589A (en) | 1991-09-12 | 1993-03-17 | Motorola Inc | Self - timed random access memories |
US6230233B1 (en) | 1991-09-13 | 2001-05-08 | Sandisk Corporation | Wear leveling techniques for flash EEPROM systems |
US5532962A (en) | 1992-05-20 | 1996-07-02 | Sandisk Corporation | Soft errors handling in EEPROM devices |
US5473753A (en) | 1992-10-30 | 1995-12-05 | Intel Corporation | Method of managing defects in flash disk memories |
US5404485A (en) | 1993-03-08 | 1995-04-04 | M-Systems Flash Disk Pioneers Ltd. | Flash file system |
US5799168A (en) | 1996-01-05 | 1998-08-25 | M-Systems Flash Disk Pioneers Ltd. | Standardized flash controller |
US5818757A (en) | 1996-07-22 | 1998-10-06 | Invox Technology | Analog and multi-level memory with reduced program disturb |
JPH10107649A (en) | 1996-09-30 | 1998-04-24 | Sanyo Electric Co Ltd | Code error correction/detection decoder |
US5771346A (en) | 1996-10-24 | 1998-06-23 | Micron Quantum Devices, Inc. | Apparatus and method for detecting over-programming condition in multistate memory device |
US5928370A (en) | 1997-02-05 | 1999-07-27 | Lexar Media, Inc. | Method and apparatus for verifying erasure of memory blocks within a non-volatile memory structure |
JP3565687B2 (en) | 1997-08-06 | 2004-09-15 | 沖電気工業株式会社 | Semiconductor memory device and control method thereof |
US5937425A (en) | 1997-10-16 | 1999-08-10 | M-Systems Flash Disk Pioneers Ltd. | Flash file system optimized for page-mode flash technologies |
JP3638770B2 (en) | 1997-12-05 | 2005-04-13 | 東京エレクトロンデバイス株式会社 | Storage device with test function |
US5943283A (en) | 1997-12-05 | 1999-08-24 | Invox Technology | Address scrambling in a semiconductor memory |
JPH11297066A (en) | 1998-04-10 | 1999-10-29 | Ricoh Co Ltd | Semiconductor device |
US6034882A (en) | 1998-11-16 | 2000-03-07 | Matrix Semiconductor, Inc. | Vertically stacked field programmable nonvolatile memory and method of fabrication |
US6498851B1 (en) | 1998-11-25 | 2002-12-24 | Sandisk Corporation | Data encryption and signal scrambling using programmable data conversion arrays |
US6181599B1 (en) | 1999-04-13 | 2001-01-30 | Sandisk Corporation | Method for applying variable row BIAS to reduce program disturb in a flash memory storage array |
JP3602984B2 (en) | 1999-07-09 | 2004-12-15 | 富士通株式会社 | Memory device |
JP3937214B2 (en) | 1999-09-17 | 2007-06-27 | 株式会社ルネサステクノロジ | Storage device for recording error correction count |
US8341332B2 (en) | 2003-12-02 | 2012-12-25 | Super Talent Electronics, Inc. | Multi-level controller with smart storage transfer manager for interleaving multiple single-chip flash memory devices |
US6426893B1 (en) | 2000-02-17 | 2002-07-30 | Sandisk Corporation | Flash eeprom system with simultaneous multiple data sector programming and storage of physical block characteristics in other designated blocks |
JP2001297038A (en) | 2000-04-11 | 2001-10-26 | Toshiba Corp | Data storage device, recording medium, and recording medium control method |
DE60037877T2 (en) | 2000-04-13 | 2009-01-29 | A-DATA TECHNOLOGY Co., Ltd., Chung Ho City | Multi-interface memory card and adapter module for it |
US6631085B2 (en) | 2000-04-28 | 2003-10-07 | Matrix Semiconductor, Inc. | Three-dimensional memory array incorporating serial chain diode stack |
US6420215B1 (en) | 2000-04-28 | 2002-07-16 | Matrix Semiconductor, Inc. | Three-dimensional memory array and method of fabrication |
US20030120858A1 (en) | 2000-09-15 | 2003-06-26 | Matrix Semiconductor, Inc. | Memory devices and methods for use therewith |
US6738937B1 (en) | 2000-12-01 | 2004-05-18 | Lsi Logic Corporation | Method for nondisruptive testing of device and host attachment to storage subsystems |
US7020739B2 (en) | 2000-12-06 | 2006-03-28 | Tdk Corporation | Memory controller, flash memory system having memory controller and method for controlling flash memory device |
US6523484B2 (en) * | 2000-12-20 | 2003-02-25 | Gunderson, Inc. | Center beam car with depressed cargo-carrying area |
US6754765B1 (en) | 2001-05-14 | 2004-06-22 | Integrated Memory Logic, Inc. | Flash memory controller with updateable microcode |
US6591330B2 (en) | 2001-06-18 | 2003-07-08 | M-Systems Flash Disk Pioneers Ltd. | System and method for flexible flash file |
US6760805B2 (en) | 2001-09-05 | 2004-07-06 | M-Systems Flash Disk Pioneers Ltd. | Flash management system for large page size |
TW516118B (en) | 2001-09-11 | 2003-01-01 | Leadtek Research Inc | Decoding conversion device and method capable of supporting multiple memory chips and their application system |
GB0123412D0 (en) | 2001-09-28 | 2001-11-21 | Memquest Ltd | Memory system sectors |
GB0123415D0 (en) | 2001-09-28 | 2001-11-21 | Memquest Ltd | Method of writing data to non-volatile memory |
GB0123416D0 (en) | 2001-09-28 | 2001-11-21 | Memquest Ltd | Non-volatile memory control |
US6778436B2 (en) | 2001-10-10 | 2004-08-17 | Fong Piau | Apparatus and architecture for a compact flash memory controller |
US6859856B2 (en) | 2001-10-23 | 2005-02-22 | Flex P Industries Sdn. Bhd | Method and system for a compact flash memory controller |
US6704852B2 (en) | 2001-11-16 | 2004-03-09 | Key Technology Corporation | Control device applicable to flash memory card and method for building partial lookup table |
US6977847B2 (en) | 2001-11-23 | 2005-12-20 | M-Systems Flash Disk Pioneers Ltd. | Detecting partially erased units in flash devices |
US7219271B2 (en) | 2001-12-14 | 2007-05-15 | Sandisk 3D Llc | Memory device and method for redundancy/self-repair |
TWI240861B (en) | 2002-01-11 | 2005-10-01 | Integrated Circuit Solution In | Data access method and architecture of flash memory |
US6683817B2 (en) | 2002-02-21 | 2004-01-27 | Qualcomm, Incorporated | Direct memory swapping between NAND flash and SRAM with error correction coding |
US20030206442A1 (en) | 2002-05-02 | 2003-11-06 | Jerry Tang | Flash memory bridiging device, method and application system |
US6721820B2 (en) | 2002-05-15 | 2004-04-13 | M-Systems Flash Disk Pioneers Ltd. | Method for improving performance of a flash-based storage system using specialized flash controllers |
US7081377B2 (en) | 2002-06-27 | 2006-07-25 | Sandisk 3D Llc | Three-dimensional memory |
US6976194B2 (en) | 2002-06-28 | 2005-12-13 | Sun Microsystems, Inc. | Memory/Transmission medium failure handling controller and method |
US6973613B2 (en) | 2002-06-28 | 2005-12-06 | Sun Microsystems, Inc. | Error detection/correction code which detects and corrects component failure and which provides single bit error correction subsequent to component failure |
KR100448905B1 (en) | 2002-07-29 | 2004-09-16 | 삼성전자주식회사 | Computer system with nand flash memory for booting and storagement |
JP4129381B2 (en) | 2002-09-25 | 2008-08-06 | 株式会社ルネサステクノロジ | Nonvolatile semiconductor memory device |
KR101122511B1 (en) | 2002-10-28 | 2012-03-15 | 쌘디스크 코포레이션 | Automated wear leveling in non-volatile storage systems |
US7171536B2 (en) | 2002-10-28 | 2007-01-30 | Sandisk Corporation | Unusable block management within a non-volatile memory system |
US7096313B1 (en) | 2002-10-28 | 2006-08-22 | Sandisk Corporation | Tracking the least frequently erased blocks in non-volatile memory systems |
US20050055479A1 (en) | 2002-11-21 | 2005-03-10 | Aviad Zer | Multi-module circuit card with inter-module direct memory access |
US8037229B2 (en) | 2002-11-21 | 2011-10-11 | Sandisk Technologies Inc. | Combination non-volatile memory and input-output card with direct memory access |
US7225357B2 (en) | 2003-01-21 | 2007-05-29 | Zentek Technology Japan, Inc. | SDIO card development system |
US7069370B2 (en) | 2003-01-31 | 2006-06-27 | Toshiba Corporation | USB memory storage apparatus with integrated circuit in a connector |
JP4550439B2 (en) | 2003-02-28 | 2010-09-22 | 東芝メモリシステムズ株式会社 | ECC controller |
JP2004355163A (en) | 2003-05-28 | 2004-12-16 | Renesas Technology Corp | Data processor, and electronic apparatus |
US6988175B2 (en) | 2003-06-30 | 2006-01-17 | M-Systems Flash Disk Pioneers Ltd. | Flash memory management method that is resistant to data corruption by power loss |
JP3984209B2 (en) | 2003-07-31 | 2007-10-03 | 株式会社東芝 | Semiconductor memory device |
KR100560767B1 (en) | 2003-09-02 | 2006-03-13 | 삼성전자주식회사 | System including insertable and removable storage and control method thereof |
US7191379B2 (en) | 2003-09-10 | 2007-03-13 | Hewlett-Packard Development Company, L.P. | Magnetic memory with error correction coding |
US7012835B2 (en) | 2003-10-03 | 2006-03-14 | Sandisk Corporation | Flash memory data correction and scrub techniques |
US7730368B2 (en) * | 2003-10-31 | 2010-06-01 | Sandisk Il Ltd. | Method, system and computer-readable code for testing of flash memory |
TWI226643B (en) | 2003-10-31 | 2005-01-11 | C One Technology Corp | Simulated SmartMedia/xD-Picture memory card using any nonvolatile memory |
EP1538525A1 (en) * | 2003-12-04 | 2005-06-08 | Texas Instruments Incorporated | ECC computation simultaneously performed while reading or programming a flash memory |
US7350044B2 (en) | 2004-01-30 | 2008-03-25 | Micron Technology, Inc. | Data move method and apparatus |
WO2005076203A1 (en) | 2004-02-03 | 2005-08-18 | Matsushita Electric Industrial Co., Ltd. | Memory card, data processor, memory card control method and memory card setting method |
US7136973B2 (en) | 2004-02-04 | 2006-11-14 | Sandisk Corporation | Dual media storage device |
WO2005076137A1 (en) * | 2004-02-05 | 2005-08-18 | Research In Motion Limited | Memory controller interface |
JP4102313B2 (en) | 2004-02-05 | 2008-06-18 | 株式会社東芝 | Semiconductor integrated circuit device |
US8019928B2 (en) | 2004-02-15 | 2011-09-13 | Sandisk Il Ltd. | Method of managing a multi-bit-cell flash memory |
JP4398750B2 (en) | 2004-02-17 | 2010-01-13 | 株式会社東芝 | NAND flash memory |
JP2005234976A (en) | 2004-02-20 | 2005-09-02 | Renesas Technology Corp | Storage device |
JP2005258851A (en) * | 2004-03-12 | 2005-09-22 | Renesas Technology Corp | Memory card |
KR100648243B1 (en) | 2004-03-19 | 2006-11-24 | 삼성전자주식회사 | Memory card using nand flash memory |
US7177977B2 (en) | 2004-03-19 | 2007-02-13 | Sandisk Corporation | Operating non-volatile memory without read disturb limitations |
JP4357331B2 (en) * | 2004-03-24 | 2009-11-04 | 東芝メモリシステムズ株式会社 | Microprocessor boot-up control device and information processing system |
US7406572B1 (en) | 2004-03-26 | 2008-07-29 | Cypress Semiconductor Corp. | Universal memory circuit architecture supporting multiple memory interface options |
JP4570891B2 (en) | 2004-03-30 | 2010-10-27 | ルネサスエレクトロニクス株式会社 | Storage device |
US7057939B2 (en) | 2004-04-23 | 2006-06-06 | Sandisk Corporation | Non-volatile memory and control with improved partial page program capability |
US7139199B2 (en) | 2004-06-28 | 2006-11-21 | Intel Corporation | Flash memory file system with transacted operations |
JP2006048783A (en) | 2004-08-02 | 2006-02-16 | Renesas Technology Corp | Nonvolatile memory and memory card |
JP2006048777A (en) | 2004-08-02 | 2006-02-16 | Toshiba Corp | Nand flash memory and data writing method |
DK3422583T3 (en) | 2004-08-30 | 2020-09-28 | Google Llc | SYSTEM AND METHOD OF PROVIDING NON-VOLATILE MEMORY ADMINISTRATION IN CORDLESS PHONES |
JP4406339B2 (en) | 2004-09-21 | 2010-01-27 | 株式会社東芝 | Controller, memory card and control method thereof |
US7149119B2 (en) | 2004-09-30 | 2006-12-12 | Matrix Semiconductor, Inc. | System and method of controlling a three-dimensional memory |
JP4828816B2 (en) | 2004-10-25 | 2011-11-30 | 株式会社東芝 | Memory card, semiconductor device, and memory card control method |
US7149111B2 (en) | 2004-12-17 | 2006-12-12 | Msystems Ltd. | Method of handling limitations on the order of writing to a non-volatile memory |
US20060239450A1 (en) | 2004-12-21 | 2006-10-26 | Michael Holtzman | In stream data encryption / decryption and error correction method |
US6980471B1 (en) | 2004-12-23 | 2005-12-27 | Sandisk Corporation | Substrate electron injection techniques for programming non-volatile charge storage memory cells |
US7177191B2 (en) | 2004-12-30 | 2007-02-13 | Sandisk 3D Llc | Integrated circuit including memory array incorporating multiple types of NAND string structures |
US7187583B2 (en) | 2005-01-25 | 2007-03-06 | Phison Electronics Corp. | Method for reducing data error when flash memory storage device using copy back command |
US7657696B2 (en) * | 2005-02-25 | 2010-02-02 | Lsi Corporation | Method to detect NAND-flash parameters by hardware automatically |
KR100759427B1 (en) * | 2005-03-17 | 2007-09-20 | 삼성전자주식회사 | Hard disk drive and information processing system with reduced power consumption and data input and output method thereof |
JP4198124B2 (en) | 2005-04-27 | 2008-12-17 | 株式会社ハギワラシスコム | 1-chip type semiconductor memory device |
JP2006323739A (en) | 2005-05-20 | 2006-11-30 | Renesas Technology Corp | Memory module, memory system and information apparatus |
KR100746289B1 (en) | 2005-07-11 | 2007-08-03 | 삼성전자주식회사 | Non-volatile memory card apparatus and method for updating memory capacity |
US7345907B2 (en) | 2005-07-11 | 2008-03-18 | Sandisk 3D Llc | Apparatus and method for reading an array of nonvolatile memory cells including switchable resistor memory elements |
US7362604B2 (en) | 2005-07-11 | 2008-04-22 | Sandisk 3D Llc | Apparatus and method for programming an array of nonvolatile memory cells including switchable resistor memory elements |
GB2428496A (en) | 2005-07-15 | 2007-01-31 | Global Silicon Ltd | Error correction for flash memory |
US7362611B2 (en) | 2005-08-30 | 2008-04-22 | Micron Technology, Inc. | Non-volatile memory copy back |
US7218552B1 (en) | 2005-09-09 | 2007-05-15 | Sandisk Corporation | Last-first mode and method for programming of non-volatile memory with reduced program disturb |
US7170788B1 (en) | 2005-09-09 | 2007-01-30 | Sandisk Corporation | Last-first mode and apparatus for programming of non-volatile memory with reduced program disturb |
US8291295B2 (en) | 2005-09-26 | 2012-10-16 | Sandisk Il Ltd. | NAND flash memory controller exporting a NAND interface |
US7631245B2 (en) | 2005-09-26 | 2009-12-08 | Sandisk Il Ltd. | NAND flash memory controller exporting a NAND interface |
US20070076478A1 (en) | 2005-09-30 | 2007-04-05 | Sigmatel, Inc. | System and method of memory block management |
US7640424B2 (en) | 2005-10-13 | 2009-12-29 | Sandisk Corporation | Initialization of flash storage via an embedded controller |
KR20050107369A (en) | 2005-10-27 | 2005-11-11 | 서운식 | An apparatus and a means to control storage device with executable in place |
US7447066B2 (en) | 2005-11-08 | 2008-11-04 | Sandisk Corporation | Memory with retargetable memory cell redundancy |
US7262994B2 (en) | 2005-12-06 | 2007-08-28 | Sandisk Corporation | System for reducing read disturb for non-volatile storage |
US7349258B2 (en) | 2005-12-06 | 2008-03-25 | Sandisk Corporation | Reducing read disturb for non-volatile storage |
US7355889B2 (en) | 2005-12-19 | 2008-04-08 | Sandisk Corporation | Method for programming non-volatile memory with reduced program disturb using modified pass voltages |
US7355888B2 (en) | 2005-12-19 | 2008-04-08 | Sandisk Corporation | Apparatus for programming non-volatile memory with reduced program disturb using modified pass voltages |
US7769978B2 (en) * | 2005-12-21 | 2010-08-03 | Sandisk Corporation | Method and system for accessing non-volatile storage devices |
JP2007183844A (en) | 2006-01-10 | 2007-07-19 | Hitachi Global Storage Technologies Netherlands Bv | Auxiliary storage device and record reproduction method |
KR20070076849A (en) | 2006-01-20 | 2007-07-25 | 삼성전자주식회사 | Apparatus and method for accomplishing copy-back operation in memory card |
US7499326B2 (en) | 2006-04-12 | 2009-03-03 | Sandisk Corporation | Apparatus for reducing the impact of program disturb |
US7426137B2 (en) | 2006-04-12 | 2008-09-16 | Sandisk Corporation | Apparatus for reducing the impact of program disturb during read |
US7436713B2 (en) | 2006-04-12 | 2008-10-14 | Sandisk Corporation | Reducing the impact of program disturb |
US7366029B2 (en) | 2006-04-24 | 2008-04-29 | Sandisk Corporation | High-performance flash memory data transfer |
US7852690B2 (en) | 2006-05-15 | 2010-12-14 | Apple Inc. | Multi-chip package for a flash memory |
US7584336B2 (en) | 2006-06-08 | 2009-09-01 | International Business Machines Corporation | Systems and methods for providing data modification operations in memory subsystems |
US20080046630A1 (en) | 2006-08-21 | 2008-02-21 | Sandisk Il Ltd. | NAND flash memory controller exporting a logical sector-based interface |
US20080046641A1 (en) | 2006-08-21 | 2008-02-21 | Sandisk Il Ltd. | NAND flash memory controller exporting a logical sector-based interface |
US7468911B2 (en) | 2006-11-02 | 2008-12-23 | Sandisk Corporation | Non-volatile memory using multiple boosting modes for reduced program disturb |
US7440323B2 (en) | 2006-11-02 | 2008-10-21 | Sandisk Corporation | Reducing program disturb in non-volatile memory using multiple boosting modes |
US8127200B2 (en) | 2006-12-24 | 2012-02-28 | Sandisk Il Ltd. | Flash memory device and system with randomizing for suppressing errors |
US7468918B2 (en) | 2006-12-29 | 2008-12-23 | Sandisk Corporation | Systems for programming non-volatile memory with reduced program disturb by removing pre-charge dependency on word line data |
US7450430B2 (en) | 2006-12-29 | 2008-11-11 | Sandisk Corporation | Programming non-volatile memory with reduced program disturb by using different pre-charge enable voltages |
US7433241B2 (en) | 2006-12-29 | 2008-10-07 | Sandisk Corporation | Programming non-volatile memory with reduced program disturb by removing pre-charge dependency on word line data |
US7463531B2 (en) | 2006-12-29 | 2008-12-09 | Sandisk Corporation | Systems for programming non-volatile memory with reduced program disturb by using different pre-charge enable voltages |
US7984360B2 (en) | 2006-12-31 | 2011-07-19 | Ramot At Tel Aviv University Ltd. | Avoiding errors in a flash memory by using substitution transformations |
US7949931B2 (en) | 2007-01-02 | 2011-05-24 | International Business Machines Corporation | Systems and methods for error detection in a memory system |
US7861139B2 (en) | 2007-01-26 | 2010-12-28 | Micron Technology, Inc. | Programming management data for NAND memories |
JP4498370B2 (en) | 2007-02-14 | 2010-07-07 | 株式会社東芝 | Data writing method |
US7477547B2 (en) | 2007-03-28 | 2009-01-13 | Sandisk Corporation | Flash memory refresh techniques triggered by controlled scrub data reads |
US7865473B2 (en) | 2007-04-02 | 2011-01-04 | International Business Machines Corporation | Generating and indicating incremental backup copies from virtual copies of a data set |
JP5162763B2 (en) | 2007-08-07 | 2013-03-13 | 株式会社メガチップス | Memory access system |
US7584308B2 (en) | 2007-08-31 | 2009-09-01 | International Business Machines Corporation | System for supporting partial cache line write operations to a memory module to reduce write data traffic on a memory channel |
US8086936B2 (en) | 2007-08-31 | 2011-12-27 | International Business Machines Corporation | Performing error correction at a memory device level that is transparent to a memory channel |
US8082482B2 (en) | 2007-08-31 | 2011-12-20 | International Business Machines Corporation | System for performing error correction operations in a memory hub device of a memory module |
US20100269021A1 (en) | 2007-09-05 | 2010-10-21 | Gower Kevin C | Method for Performing Error Correction Operations in a Memory Hub Device of a Memory Module |
JP2009087509A (en) | 2007-10-03 | 2009-04-23 | Toshiba Corp | Semiconductor storage device |
US8103936B2 (en) | 2007-10-17 | 2012-01-24 | Micron Technology, Inc. | System and method for data read of a synchronous serial interface NAND |
US8209465B2 (en) | 2007-10-30 | 2012-06-26 | Hagiwara Sys-Com Co., Ltd. | Data writing method |
JP5019611B2 (en) | 2007-12-27 | 2012-09-05 | 株式会社東芝 | Memory system |
JP4856110B2 (en) | 2008-03-01 | 2012-01-18 | 株式会社東芝 | Chain search apparatus and chain search method |
JP4691122B2 (en) | 2008-03-01 | 2011-06-01 | 株式会社東芝 | Memory system |
JP2009244962A (en) | 2008-03-28 | 2009-10-22 | Toshiba Corp | Memory system |
US8281061B2 (en) | 2008-03-31 | 2012-10-02 | Micron Technology, Inc. | Data conditioning to improve flash memory reliability |
US8059455B2 (en) | 2008-05-09 | 2011-11-15 | Sandisk Il Ltd. | Partial scrambling to reduce correlation |
US8154918B2 (en) | 2008-06-30 | 2012-04-10 | Sandisk Il Ltd. | Method for page- and block based scrambling in non-volatile memory |
US20100332942A1 (en) | 2008-09-10 | 2010-12-30 | Arm Limited | Memory controller for NAND memory using forward error correction |
US8429330B2 (en) | 2008-09-12 | 2013-04-23 | Sandisk Technologies Inc. | Method for scrambling data in which scrambling data and scrambled data are stored in corresponding non-volatile memory locations |
US8806293B2 (en) | 2008-10-09 | 2014-08-12 | Micron Technology, Inc. | Controller to execute error correcting code algorithms and manage NAND memories |
US20100180182A1 (en) | 2009-01-09 | 2010-07-15 | Seagate Technology Llc | Data memory device and controller with interface error detection and handling logic |
WO2010125695A1 (en) | 2009-04-30 | 2010-11-04 | Powerchip Corporation | Programming method for nand flash memory device |
US8250282B2 (en) | 2009-05-14 | 2012-08-21 | Micron Technology, Inc. | PCM memories for storage bus interfaces |
US7898859B2 (en) | 2009-06-15 | 2011-03-01 | Micron Technology, Inc. | Use of emerging non-volatile memory elements with flash memory |
US8495332B2 (en) | 2009-07-24 | 2013-07-23 | Apple Inc. | Controller for optimizing throughput of read operations |
-
2009
- 2009-08-11 US US12/539,417 patent/US8291295B2/en active Active
-
2012
- 2012-08-28 US US13/596,926 patent/US20130111113A1/en not_active Abandoned
Cited By (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10691344B2 (en) | 2013-05-30 | 2020-06-23 | Hewlett Packard Enterprise Development Lp | Separate memory controllers to access data in memory |
WO2014193376A1 (en) * | 2013-05-30 | 2014-12-04 | Hewlett-Packard Development Company, L.P. | Separate memory controllers to access data in memory |
WO2014204331A1 (en) * | 2013-06-17 | 2014-12-24 | Llc "Topcon Positioning Systems" | Nand flash memory interface controller with gnss receiver firmware booting capability |
US9053015B2 (en) | 2013-06-17 | 2015-06-09 | Topcon Positioning Systems, Inc. | NAND flash memory interface controller with GNSS receiver firmware booting capability |
US9164897B2 (en) * | 2013-06-17 | 2015-10-20 | Topcon Positioning Systems, Inc. | NAND flash memory interface controller with GNSS receiver firmware booting capability |
TWI509622B (en) * | 2013-07-09 | 2015-11-21 | Univ Nat Taiwan Science Tech | Fault bits scrambling memory and method thereof |
TWI553641B (en) * | 2013-12-09 | 2016-10-11 | 慧榮科技股份有限公司 | Data storage device and mode detection method thereof |
DE102015105414B4 (en) | 2014-04-15 | 2023-12-07 | Infineon Technologies Ag | Editing a destination storage |
US9886378B2 (en) | 2014-04-29 | 2018-02-06 | Samsung Electronics Co., Ltd. | Nonvolatile memory system using control signals to transmit varied signals via data pins |
US10489313B2 (en) | 2016-10-31 | 2019-11-26 | Alibaba Group Holding Limited | Flash storage failure rate reduction and hyperscale infrastructure robustness enhancement through the MRAM-NOR flash based cache architecture |
US10936205B2 (en) | 2017-10-05 | 2021-03-02 | International Business Machines Corporation | Techniques for retention and read-disturb aware health binning |
US10824352B2 (en) | 2017-12-06 | 2020-11-03 | International Business Machines Corporation | Reducing unnecessary calibration of a memory unit for which the error count margin has been exceeded |
TWI711930B (en) * | 2018-02-05 | 2020-12-01 | 美商美光科技公司 | Memory systems having controllers embedded in packages of integrated circuit memory |
US11669260B2 (en) | 2018-02-05 | 2023-06-06 | Micron Technology, Inc. | Predictive data orchestration in multi-tier memory systems |
US10782908B2 (en) | 2018-02-05 | 2020-09-22 | Micron Technology, Inc. | Predictive data orchestration in multi-tier memory systems |
WO2019152192A1 (en) | 2018-02-05 | 2019-08-08 | Micron Technology, Inc. | Memory systems having controllers embedded in packages of integrated circuit memory |
US11416395B2 (en) | 2018-02-05 | 2022-08-16 | Micron Technology, Inc. | Memory virtualization for accessing heterogeneous memory components |
US11354056B2 (en) | 2018-02-05 | 2022-06-07 | Micron Technology, Inc. | Predictive data orchestration in multi-tier memory systems |
CN111684406A (en) * | 2018-02-05 | 2020-09-18 | 美光科技公司 | Memory system with controller embedded in integrated circuit memory package |
US11099789B2 (en) | 2018-02-05 | 2021-08-24 | Micron Technology, Inc. | Remote direct memory access in multi-tier memory systems |
US11706317B2 (en) | 2018-02-12 | 2023-07-18 | Micron Technology, Inc. | Optimization of data access and communication in memory systems |
US10880401B2 (en) | 2018-02-12 | 2020-12-29 | Micron Technology, Inc. | Optimization of data access and communication in memory systems |
US10552063B2 (en) | 2018-06-21 | 2020-02-04 | International Business Machines Corporation | Background mitigation reads in a non-volatile memory system |
US10877892B2 (en) | 2018-07-11 | 2020-12-29 | Micron Technology, Inc. | Predictive paging to accelerate memory access |
US11573901B2 (en) | 2018-07-11 | 2023-02-07 | Micron Technology, Inc. | Predictive paging to accelerate memory access |
US10699791B2 (en) | 2018-08-24 | 2020-06-30 | International Business Machines Corporation | Adaptive read voltage threshold calibration in non-volatile memory |
US10949101B2 (en) | 2019-02-25 | 2021-03-16 | Micron Technology, Inc. | Storage device operation orchestration |
US11768614B2 (en) | 2019-02-25 | 2023-09-26 | Micron Technology, Inc. | Storage device operation orchestration |
WO2020176183A1 (en) * | 2019-02-25 | 2020-09-03 | Micron Technology, Inc. | Storage device operation orchestration |
US10852949B2 (en) | 2019-04-15 | 2020-12-01 | Micron Technology, Inc. | Predictive data pre-fetching in a data storage device |
US11740793B2 (en) | 2019-04-15 | 2023-08-29 | Micron Technology, Inc. | Predictive data pre-fetching in a data storage device |
US11184030B2 (en) | 2019-12-11 | 2021-11-23 | Samsung Electronics Co., Ltd. | Storage controller for correcting error, storage device including the same, and operating method thereof |
Also Published As
Publication number | Publication date |
---|---|
US8291295B2 (en) | 2012-10-16 |
US20100023800A1 (en) | 2010-01-28 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8291295B2 (en) | NAND flash memory controller exporting a NAND interface | |
USRE46201E1 (en) | Method and controller for performing a sequence of commands | |
USRE46013E1 (en) | Method and controller for performing a copy-back operation | |
US20110040924A1 (en) | Controller and Method for Detecting a Transmission Error Over a NAND Interface Using Error Detection Code | |
US20110041039A1 (en) | Controller and Method for Interfacing Between a Host Controller in a Host and a Flash Memory Device | |
US20110041005A1 (en) | Controller and Method for Providing Read Status and Spare Block Management Information in a Flash Memory System | |
US8375257B2 (en) | ECC control circuits, multi-channel memory systems including the same, and related methods of operation | |
US7886212B2 (en) | NAND flash memory controller exporting a NAND interface | |
US8266367B2 (en) | Multi-level striping and truncation channel-equalization for flash-memory system | |
JP5032027B2 (en) | Semiconductor disk control device | |
JP5495074B2 (en) | Logical unit operation | |
US8250403B2 (en) | Solid state disk device and related data storing and reading methods | |
US9905314B2 (en) | Storage module and method for datapath bypass | |
US20190354478A1 (en) | On-Chip Copy with Data Folding in Three-Dimensional Non-Volatile Memory Array | |
US9990149B2 (en) | Memory device for internally performing read-verify operation, method of operating the same, and memory system including the same | |
US20130173848A1 (en) | Controller and Method for Using a Transaction Flag for Page Protection | |
CN113741798A (en) | Data storage device and operation method thereof | |
CN112905107A (en) | Data storage device and operation method thereof |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: INNOVATIVE MEMORY SYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SANDISK IL LTD.;REEL/FRAME:034437/0799 Effective date: 20140618 |