US20100325353A1 - Flash memory system control scheme - Google Patents

Flash memory system control scheme Download PDF

Info

Publication number
US20100325353A1
US20100325353A1 US12/855,171 US85517110A US2010325353A1 US 20100325353 A1 US20100325353 A1 US 20100325353A1 US 85517110 A US85517110 A US 85517110A US 2010325353 A1 US2010325353 A1 US 2010325353A1
Authority
US
United States
Prior art keywords
flash memory
data
programming
pages
memory devices
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
Application number
US12/855,171
Inventor
Jin-Ki Kim
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mosaid Technologies Inc
Original Assignee
Mosaid Technologies Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mosaid Technologies Inc filed Critical Mosaid Technologies Inc
Priority to US12/855,171 priority Critical patent/US20100325353A1/en
Assigned to MOSAID TECHNOLOGIES INCORPORATED reassignment MOSAID TECHNOLOGIES INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KIM, JIN-KI
Assigned to MOSAID TECHNOLOGIES INCORPORATED reassignment MOSAID TECHNOLOGIES INCORPORATED CHANGE OF ADDRESS Assignors: MOSAID TECHNOLOGIES INCORPORATED
Publication of US20100325353A1 publication Critical patent/US20100325353A1/en
Assigned to ROYAL BANK OF CANADA reassignment ROYAL BANK OF CANADA U.S. INTELLECTUAL PROPERTY SECURITY AGREEMENT (FOR NON-U.S. GRANTORS) - SHORT FORM Assignors: 658276 N.B. LTD., 658868 N.B. INC., MOSAID TECHNOLOGIES INCORPORATED
Assigned to CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC. reassignment CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC. CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: MOSAID TECHNOLOGIES INCORPORATED
Assigned to CONVERSANT IP N.B. 868 INC., CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC., CONVERSANT IP N.B. 276 INC. reassignment CONVERSANT IP N.B. 868 INC. RELEASE OF SECURITY INTEREST Assignors: ROYAL BANK OF CANADA
Assigned to CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC. reassignment CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC. CHANGE OF ADDRESS Assignors: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.
Assigned to ROYAL BANK OF CANADA, AS LENDER, CPPIB CREDIT INVESTMENTS INC., AS LENDER reassignment ROYAL BANK OF CANADA, AS LENDER U.S. PATENT SECURITY AGREEMENT (FOR NON-U.S. GRANTORS) Assignors: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.
Assigned to CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC. reassignment CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC. RELEASE OF U.S. PATENT AGREEMENT (FOR NON-U.S. GRANTORS) Assignors: ROYAL BANK OF CANADA, AS LENDER
Abandoned legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C16/00Erasable programmable read-only memories
    • G11C16/02Erasable programmable read-only memories electrically programmable
    • G11C16/04Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C7/00Arrangements for writing information into, or reading information out from, a digital store
    • G11C7/10Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers
    • G11C7/1015Read-write modes for single port memories, i.e. having either a random port or a serial port
    • G11C7/1042Read-write modes for single port memories, i.e. having either a random port or a serial port using interleaving techniques, i.e. read-write of one part of the memory while preparing another part
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F12/00Accessing, addressing or allocating within memory systems or architectures
    • G06F12/02Addressing or allocation; Relocation
    • G06F12/0223User address space allocation, e.g. contiguous or non contiguous base addressing
    • G06F12/023Free address space management
    • G06F12/0238Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
    • G06F12/0246Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C16/00Erasable programmable read-only memories
    • G11C16/02Erasable programmable read-only memories electrically programmable
    • G11C16/06Auxiliary circuits, e.g. for writing into memory
    • G11C16/10Programming or data input circuits
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C16/00Erasable programmable read-only memories
    • G11C16/02Erasable programmable read-only memories electrically programmable
    • G11C16/06Auxiliary circuits, e.g. for writing into memory
    • G11C16/32Timing circuits
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C7/00Arrangements for writing information into, or reading information out from, a digital store
    • G11C7/10Input/output [I/O] data interface arrangements, e.g. I/O data control circuits, I/O data buffers
    • G11C7/1015Read-write modes for single port memories, i.e. having either a random port or a serial port
    • G11C7/1018Serial bit line access mode, e.g. using bit line address shift registers, bit line address counters, bit line burst counters
    • G11C7/1021Page serial bit line access mode, i.e. using an enabled row address stroke pulse with its associated word line address and a sequence of enabled column address stroke pulses each with its associated bit line address
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/10Providing a specific technical effect
    • G06F2212/1032Reliability improvement, data loss prevention, degraded operation etc
    • G06F2212/1036Life time enhancement
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2212/00Indexing scheme relating to accessing, addressing or allocation within memory systems or architectures
    • G06F2212/72Details relating to flash memory management
    • G06F2212/7211Wear leveling
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C2216/00Indexing scheme relating to G11C16/00 and subgroups, for features not directly covered by these groups
    • G11C2216/12Reading and writing aspects of erasable programmable read-only memories
    • G11C2216/22Nonvolatile memory in which reading can be carried out from one memory bank or array whilst a word or sector in another bank or array is being erased or programmed simultaneously
    • GPHYSICS
    • G11INFORMATION STORAGE
    • G11CSTATIC STORES
    • G11C2216/00Indexing scheme relating to G11C16/00 and subgroups, for features not directly covered by these groups
    • G11C2216/12Reading and writing aspects of erasable programmable read-only memories
    • G11C2216/24Nonvolatile memory in which programming can be carried out in one memory bank or array whilst a word or sector in another bank or array is being erased simultaneously

Definitions

  • the present invention relates generally to Flash memory. More particularly, the present invention relates to a multi-device Flash memory system for mass storage applications.
  • Flash memory is a commonly used type of non-volatile memory in widespread use as mass storage for consumer electronics, such as digital cameras and portable digital music players for example.
  • the density of a presently available Flash memory chip can be up to 32 Gbits (4 GB), which is suitable for use in popular USB Flash drives since the size of one Flash chip is small.
  • Flash memory devices are combined together into a memory system to effectively increase the available storage capacity. For example, Flash storage densities of 20 GB may be required for such applications.
  • FIG. 1 is a block diagram of a prior art Flash memory system 10 integrated with a host system 12 .
  • Flash memory system 10 includes a Flash memory controller 14 in communication with host system 12 , and multiple non-volatile memory devices 16 .
  • the host system will include a processing device such as a microcontroller, microprocessor, or a computer system.
  • the Flash memory system 10 of FIG. 1 is configured to include one channel 20 , where memory devices 16 are connected in parallel to channel 20 .
  • the memory system 10 will have any number of memory devices connected to it.
  • Channel 20 includes a set of common buses, which include data and control lines that are connected to all its corresponding memory devices. While not shown, each memory device is enabled/disabled with a respective chip select signal provided by Flash memory controller 14 .
  • the Flash controller 14 is responsible for issuing commands and data, via the channel, to a selected memory device based on the operation of the host system 12 . Data read from the memory devices is transferred via the channel back to the Flash memory controller 14 and host system 12 .
  • Flash memory system 10 is generally referred to as a multi-drop configuration, in which the memory devices 16 are connected in parallel with respect to channel 20 .
  • non-volatile memory devices 16 are identical to each other, and are typically implemented as NAND Flash memory devices. Those skilled in the art will understand that Flash memory is organized into banks, and each bank is organized into blocks to facilitate block erasure. Most commercially available NAND Flash memory devices are configured to have two banks of memory. Prior to a discussion of the operation of Flash memory system 10 , a brief overview of a single NAND Flash memory device memory core is described.
  • FIG. 2 is a general block diagram of one bank of a known NAND Flash memory.
  • Bank 30 is organized into k+1 blocks. Each block consists of NAND memory cell strings, having up to i+1 Flash memory cells serially connected to each other. Accordingly, wordlines WL 0 to WLi are connected to the gates of each Flash memory cell in the memory cell string.
  • a string select device connected to signal SSL selectively connects the memory cell string to a bitline
  • GSL ground select line
  • the string select device and the ground select device are n-channel transistors.
  • each bitline is connected to one NAND memory cell string in each of blocks [0] to [k].
  • Each wordline (WL 0 to WLi), SSL and GSL signal is connected to the same corresponding transistor device in each NAND memory cell string in the block.
  • data stored in the Flash memory cells along one wordline is referred to as a page of data.
  • a data register 32 Connected to each bitline outside of the bank 30 is a data register 32 for storing one page of write data to be programmed into one page of Flash memory cells.
  • Data register 32 also includes sense circuits for sensing data read from one page of Flash memory cells.
  • the data registers perform program verify operations to ensure that the data has been properly programmed into the Flash memory cells connected to the selected wordline. Programming within a block typically starts at the page corresponding to WL 0 , and proceeds sequentially up to WLi to fill the present block. Then programming continues with WL 0 of a new block. Within a device, blocks are programmed in sequence.
  • Flash memory system 10 of FIG. 1 there are specific issues that will adversely impact performance of the system. Some are physical while others are architectural.
  • Flash memory system 10 imposes physical performance limitations. With the large number of parallel signals running across the system, the signal integrity of the signals they carry will be degraded by crosstalk, signal skew, and simultaneous switching noise (SSN). Power consumption in such a configuration becomes an issue as each signal track between the flash controller and flash memory devices is frequently charged and discharged for signaling. With increasing system clock frequencies, the power consumption will increase as well.
  • Flash controller 14 A primary function of the Flash controller 14 is to manage the writing of data to the memory devices in the system. In the Flash memory context, writing of data is more commonly referred to as programming data. There are two significant issues related to Flash programming. First, Flash programming is slow relative to volatile memories such as DRAM and SRAM, and other non-volatile memories such as hard disk drives. Programming data to Flash memory cells requires high voltages and a stepped programming sequence to obtain a tight programmed threshold voltage distribution. In a NAND Flash memory device having two banks of memory, two pages of data are concurrently programmed, one for each bank. Since there is only one data register per bank, further programming operations must wait until the current pages have been successfully programmed. Therefore, programming large quantities of data to the Flash devices 16 may require a significant amount of time.
  • FIG. 3 is an illustration of the conventional file structure for a Flash memory system 50 having four memory devices.
  • each memory device 52 , 54 , 56 and 58 has a total of n physical pages of storage space, which are divided among any number of blocks. In the presently shown example, it is assumed that the n pages are divided equally between two banks.
  • Most Flash memory systems will store a data file consisting of a number of data pages, linearly within one memory device. For example, the first page of the data file is stored in Page 0 of device 52 , and successive data pages are progressively stored in subsequent pages. Once device 52 is full, then further data files to be stored in system 50 starts at Page 0 in device 54 , and so forth.
  • Arrow 60 shows the storage pattern of data being written to the Flash memory system 50 .
  • the first memory device 52 in FIG. 3 endures more program and erase cycles than any of the other memory devices, memory device 52 will likely fail before the others.
  • memory device 52 fails, the entire system 50 is no longer usable since the memory devices are packaged together and replacement of a single memory device is impractical. This is an unfortunate waste of memory devices, as the remaining devices in the system are still useful and may have significant life left.
  • Flash memory An inherent technical architecture of most Flash memory is that the smallest unit of memory which is erasable is a block of memory. This means that if even one page within the block is to be modified, the entire block must be re-programmed along with the new page. This is referred to as block re-programming, which requires significant programming time and hence negatively impacts performance of the system.
  • Flash memory systems have slow throughput for programming data, and due to the unequal program and erase wearing across the devices, the entire system will have a lifespan limited to the first memory device to fail.
  • the present invention provides a method for controlling first and second Flash memory devices connected to a channel.
  • the method includes executing a first operation in the first Flash memory device in response to a first command, and initiating a second operation in the second Flash memory device in response to the a second command, while the first Flash memory device is executing the first operation.
  • the first Flash memory device and the second Flash memory device are serially connected to each other, and the second command is passed to the second Flash memory device through the first Flash memory device before the step of initiating.
  • the step of executing the first operation includes programming at least one page of a data file in the first memory device.
  • the second operation includes initiating programming of at least one other page of the data file in the second memory device, while the method further includes initiating a third operation in the first Flash memory device in response to a third command.
  • the second operation includes initiating a read operation of data in the second memory device or initiating an erase operation in the second memory device.
  • executing the first operation includes one of a read operation and an erase operation in the first memory device.
  • the present invention provides a method for high speed wear leveling programming in a Flash memory system having a plurality Flash memory devices.
  • the method includes receiving a data file having k pages, k being an integer greater than 0; selecting a programming profile corresponding to the size of k and configuration parameters of the Flash memory system; and programming at least one of the k pages of the data file in each of to at least two of the plurality of Flash memory devices in accordance with the selected programming profile.
  • the configuration parameters includes j Flash memory devices, and each of the j Flash memory devices have i pages per block, where j and i are integer values greater than 0.
  • the step of programming includes sequentially providing program commands to each of the z Flash memory devices for programming the k pages, where each program command programs the at least one of the k pages.
  • the programming profile includes a multiple file structure when z is greater than j.
  • the multiple file structure includes storing m units of j*i pages of the data file in j Flash memory devices, and storing k ⁇ (m*(j*i)) pages of the data file in z of j Flash memory devices when z is less than or equal to j, where m is an integer value greater than 0.
  • the step of programming includes sequentially providing program commands to each of the j Flash memory devices for programming the j*i pages of the data file, where each program command programs the at least one of the k pages.
  • the step of programming further includes sequentially providing program commands to each of the z Flash memory devices for programming the k ⁇ (m*(j*i)) pages, where each program command programs the at least one of the k pages.
  • the present invention provides a data file storage architecture for a memory system having at least two memory devices connected to the same channel.
  • the data file storage architecture includes portions of the data file stored in two of the at least two memory devices.
  • the portions are substantially equal in size to each other, and the portions are stored in each of the at least two memory devices of the memory system.
  • the present invention provides a method for high speed wear leveling programming in a Flash memory system having j Flash memory devices, where each of the j Flash memory devices has i pages per block, where j and i are integer values greater than 0.
  • the present invention provides a Flash memory system.
  • the Flash memory system includes a controller, a first Flash memory device, and a second Flash memory device.
  • the controller has a channel for providing a first command and a second command.
  • the first Flash memory device is coupled to the channel for executing a first operation in response to the first command.
  • the second Flash memory device is coupled to the channel for initiating a second operation in response to the second command while the first Flash memory device is executing the first operation.
  • the first Flash memory device and the second Flash memory device are serially connected to each other, and the second command is passed to the second Flash memory device through the first Flash memory device.
  • the first operation includes a programming operation, and the first Flash memory device programs at least one page of a data file.
  • the second operation includes another programming operation, and the second Flash memory device programs at least one other page of the data file.
  • FIG. 1 is a block diagram of a prior art Flash memory system
  • FIG. 2 is a schematic of a prior art NAND Flash memory core
  • FIG. 3 is an illustration of a conventional file structure for a Flash memory system
  • FIG. 4 is a block diagram of a Flash memory system according to an embodiment of the present invention.
  • FIG. 5 is a timing diagram of program commands issued by the Flash controller of FIG. 4 , according to an embodiment of the present invention.
  • FIG. 6 is a timing diagram showing program commands received by each memory device of the Flash memory system in FIG. 4 ;
  • FIG. 7 is a flow chart illustrating a high speed interleaved programming method, according to an embodiment of the present invention.
  • FIG. 8 is a graphical illustration of a file structure in the Flash memory system in FIG. 4 resulting from the high speed interleaved programming method of FIG. 7 ;
  • FIG. 9 is a flow chart illustrating a high speed wear leveling programming method, according to an embodiment of the present invention.
  • FIG. 10 is a timing diagram showing interleaved program and read operations.
  • a Flash memory system architecture having serially connected Flash memory devices to achieve high speed programming of data is achieved by interleaving pages of the data amongst the memory devices in the system, such that different pages of data are stored in different memory devices.
  • a memory controller issues program commands for each memory device in a bitstream having one or more signal lines. As each memory device receives a program command, it either begins a programming operation or passes the command to the next memory device. Therefore, the memory devices in the Flash system sequentially program pages of data one after the other, thereby minimizing delay in programming each page of data into the Flash memory system.
  • the memory controller executes a wear level control algorithm to optimize programming performance and endurance for data of any size.
  • FIG. 4 is a block diagram of a Flash memory system having serially connected memory devices for executing high speed data programming operations with wear level control, according to an embodiment of the present invention.
  • Flash memory system 100 includes a Flash memory controller 102 in communication with host system 104 , and four serially connected Flash memory devices 106 , 108 , 110 and 112 . While four memory devices are shown in the present embodiment, the embodiments of the present invention will be effective for memory systems having at least two memory devices.
  • Each of the four Flash memory devices have a serial input/output interface circuit for facilitating serial operation between memory devices.
  • An example of a such a Flash memory device is described in commonly owned U.S. patent application Ser. No. 11/324,023, filed on Dec. 30, 2005, and commonly owned U.S. patent application Ser.
  • the Flash memory device of U.S. patent application Ser. No. 11/324,023 is referred to as a multiple independent serial link device (MISL).
  • MISL multiple independent serial link device
  • the host system will include a processing device such as a microcontroller, microprocessor, or a computer system.
  • Flash memory device 106 is the first device in the chain, and receives commands, such as read, program and erase commands, from Flash memory controller 102 .
  • commands such as read, program and erase commands
  • MISL Flash device of U.S. patent application Ser. No. 11/324,023 all commands, data and address information are received as a serial bitstream.
  • the commands include data information, address information, and any other information required by the memory device for executing a particular operation.
  • each Flash memory device should include flow-through logic circuitry, any received command not intended for a particular device is passed to the next Flash memory device, and so forth, until it is acted upon by the intended Flash memory device.
  • the last Flash memory device 112 in the chain has outputs connected to the Flash memory controller 102 , for providing read data in response to a read command.
  • FIG. 4 has one channel for sending and receiving data from the chain of Flash memory devices.
  • Flash memory controller 102 will optionally have multiple channels for accommodating a corresponding number of Flash memory device chains. Since each Flash memory device is preferably positioned in close proximity with the other, conducting wires interconnecting the Flash memory devices to each other will be minimized. Therefore, there are no physical performance limitations related to bus line length, as in Flash memory system 10 of FIG. 1 .
  • the Flash memory controller 102 is responsible for issuing program commands for each Flash memory device.
  • pages of a data file are programmed to different memory devices. This is done by issuing program commands serially one after the other to initiate program operations in each Flash memory device in rapid succession.
  • FIGS. 5 and 6 will help illustrate how such high speed programming is achieved.
  • FIG. 5 is a timing diagram illustrating the issuance of program commands by the Flash memory controller 102 for maximizing overall programming speed for the Flash memory system 100 , according to an embodiment of the present invention.
  • four program commands Data[ 0 ], Data[ 1 ], Data[ 2 ] and Data[ 3 ] are issued serially at respective time periods t 1 to t 4 by Flash memory controller 102 to program one data file.
  • the identification number within square brackets for each program command indicates the sequential order the program command was issued from the Flash memory controller 102 .
  • Each programming command will include, but is not limited to, a command 200 and at least one page of data 202 for a specific memory device.
  • the command 200 includes an address to which the page of data is to be programmed, and a device identifier for matching the programming command to the specific memory device.
  • Flash memory devices 106 , 108 , 110 and 112 are responsive to program commands Data[ 0 ], Data[ 1 ], Data[ 2 ] and Data[ 3 ] respectively. Since the Flash memory devices are serially connected and the program commands are issued serially, the core programming operations of each Flash memory device overlap with the operations of the subsequent Flash memory device, with the exception of the last Flash memory device that receives a programming command.
  • each programming command requires about 85 microseconds to transfer to the memory device (time t 1 )
  • the 200 microsecond programming time is contributed by the last memory device to receive a programming command. In contrast, programming 4 pages to the same memory device will take 1140 microseconds.
  • the overlapping programming operations of the Flash memory devices is more clearly shown in the expanded timing diagram of FIG. 6 .
  • FIG. 6 is an expanded timing diagram showing the operations of Flash memory devices 106 , 108 , 110 and 112 in response to respective program commands Data[ 0 ], Data[ 1 ], Data[ 2 ] and Data[ 3 ].
  • the time periods t 1 to t 4 correspond to the same time periods shown in FIG. 5 .
  • the programming sequence of FIG. 6 will now be described with reference to the flow chart of FIG. 7 .
  • the Flash system programming control embodiment described in FIG. 7 will be referred to as a high speed interleaved programming method, whereby programming operations are interleaved between different memory devices.
  • the method begins at step 300 where at least two program commands are provided serially to the first memory device 106 in the system.
  • the first program command corresponds to program command Data[ 0 ] while the second program command corresponds to program command Data[ 1 ].
  • memory device 106 receives program command Data[ 0 ] during a first time period t 1 , which is followed by a program operation at step 304 .
  • program command Data[ 0 ] is transferred to memory device 106 while memory devices 108 , 110 and 112 remain in a no operation (NOP) state.
  • NOP no operation
  • the second program command Data[ 1 ] is received by memory device 108 during a second time period t 2 at step 306 .
  • a program operation follows at step 308 , and because the programming operation for memory device 106 has already commenced at the end of time period t 1 , there is a period of time where both memory devices 106 and 108 are executing programming operations at the same time. The process would repeat in the same manner for the next program command and memory device.
  • programming operations in memory devices 106 and 108 will have been completed by the end of time period t 4 .
  • the programming operation in memory device 110 will be completed as the programming operation in memory device 112 continues.
  • the above example presents a scenario where the first memory device to receive a command is 106 .
  • any one of the memory devices in the system can be the first memory device to receive the first program command.
  • a fifth program command is issued to memory device 106 after time period t 4 , provided that device 106 has finished its programming operation.
  • Flash memory devices will have varying programming times.
  • memory device 106 has finished programming its data at the beginning of time period t 4 , therefore it is ready to receive the next program command Data[ 4 ] as soon as memory device 112 has finished receiving program command Data[ 3 ].
  • Flash memory controller will need to wait until memory device 106 has completed programming operations before issuing the Data[ 4 ] program command. Flash memory devices will typically provide a ready status signal to the Flash memory controller to indicate when a programming operation is completed.
  • FIG. 8 is a graphical file structure illustration of Flash memory devices 106 , 108 , 110 and 112 after the high speed programming sequence described in FIG. 6 and FIG. 7 has been executed for program commands Data[ 0 ], Data[ 1 ], Data[ 2 ], Data[ 3 ] and Data[ 4 ].
  • the file structure shown in FIG. 8 assumes that memory blocks of devices 106 , 108 and 112 are empty prior to programming. This is why pages are programmed to physical page 0 of these devices.
  • the memory block may have other data in physical pages 0 and 1 . Therefore, Data[ 2 ] is programmed to the next available page in the block, which is in physical page 2 .
  • FIG. 8 is a graphical file structure illustration of Flash memory devices 106 , 108 , 110 and 112 after the high speed programming sequence described in FIG. 6 and FIG. 7 has been executed for program commands Data[ 0 ], Data[ 1 ], Data[ 2 ], Data[ 3 ] and Data[ 4 ].
  • physical page 1 of memory device 106 is the last page to be programmed in the presently shown high speed programming sequence.
  • the next programming sequence will start programming data at physical page 1 of memory device 108 , and will proceed in the same manner as previously described for the programming sequence shown in FIG. 6 . Therefore, maximum programming speed of Flash memory system 100 is obtained when program commands are serially issued to consecutive serially connected memory devices.
  • a file structure in which data is distributed across the maximum number of memory devices in the serially interconnected Flash memory system will result in highest speed programming of a data file. It should be noted that data does not necessarily need to be programmed in the same physical page number across all the memory devices.
  • the file structure shown in FIG. 8 will not maximize program/erase wear across all memory devices, mainly due to the block erase architecture of Flash memory devices. For example, if a 20 page data file is interleaved programmed across one block in each memory device, then there is a possibility that all four memory devices will need to perform a block erase before updating the data file. In contrast, if all 20 pages were stored in one block of one memory device, then only that block needs to be erased.
  • the above described high speed programming control method is adjusted to minimize program/erase wear, or to optimize programming performance and program/erase wear.
  • the Flash controller 102 of FIG. 4 executes a program control algorithm for optimizing program performance and program/erase wear based on predetermined criteria.
  • This predetermined criteria will include characteristics of the data to be programmed and characteristics of the memory devices of the Flash memory system. Data characteristics include the number of pages of the data to be programmed, and memory device characteristics include the number of pages per block.
  • FIG. 9 is a flow chart illustrating an embodiment for programming multiple Flash memory devices in a Flash memory system with high speed and with wear leveling control.
  • This program control embodiment will be referred to as a high speed wear leveling programming method.
  • Wear leveling refers to a scheme for prolonging the life of the Flash memory system.
  • the presently described embodiment will optimize wear leveling and performance for any data file to be programmed, by using a variety of programming profiles.
  • a programming profile generally corresponds to a programming sequence for storing pages of a data file with a specific file storage structure. Ultimately, the programming profile distributes pages of the data file across the memory devices of the Flash memory system.
  • the presently described method is executable by a memory controller, such as Flash controller 102 of FIG. 4 , in a system of serially connected memory devices.
  • the high speed wear leveling programming method starts at step 400 where a variable i is set to be the number of pages per block in each memory device of the Flash memory system, and a variable j is set to be the number of memory devices in the Flash memory system. It is presumed that all the memory devices in the Flash memory system are identical to each other, and have the same block size. This information is pre-programmed into the memory controller.
  • a data file consisting of a number of pages k, is received by the memory controller for programming. Proceeding to step 404 , a calculation is made to determine if k is less than or equal to i.
  • k is less than or equal to i, meaning that the data file is less than or equal to one block of storage space in a memory device
  • all k pages of the data file are programmed to one block of one memory device at step 406 .
  • This is an example of a programming profile having a single file structure.
  • the memory controller selects the specific memory device to which the data file will be programmed to in accordance with one or more selection parameters. For example, one selection parameter is the memory device with the highest number of remaining program/erase cycles, while another selection parameter includes the last memory device to be programmed to.
  • step 408 a calculation is made to determine if k/i is less than or equal to j. It should be noted that the calculation of k/i should yield integer numbers only. Since the present method determines the minimum number of blocks required for storing the k data, a non-integer result having a whole number and decimal portion (ie. a real number) indicates that one block more than the whole number is required. This is done through known mathematical functions such as a ceiling function. Those skilled in the art will understand that a ceiling function returns the smallest integer that is not less than the real number. On the other hand, a direct integer result from k/i does not require further mathematical processing. From this point forward, reference to the k/i result will presume that a ceiling function has been applied to it.
  • the k pages of the data file are interleave programmed between k/i memory devices in step 410 .
  • the interleave programming will proceed as previously described in the method of FIG. 7 .
  • the memory controller selects any two memory devices in the Flash memory system, whether they are directly connected together or indirectly connected together. Two indirectly connected memory devices can have at least one intervening memory device connected between them. Since the data file is programmed within two memory devices, about half of the pages are programmed in one memory device and the remainder is stored in the other memory device.
  • k/i is at least j, the number of memory devices in the system, then different optimization programming sequences, will be used for programming differently sized groups of the data file. More specifically, very large data files are treated as multiple units of smaller data files, which are programmed according to any one of the previously described programming sequences.
  • all page locations in one block of each memory device is programmed with j*i pages of the k pages of the data file, according to the interleaved programming sequence of step 410 .
  • the number of pages k is updated by setting it equal to k ⁇ (j*i). Therefore, the remaining number of pages to be programmed is calculated.
  • the method loops back to step 404 to repeat the decision tree processing and programming sequences based on the updated value of k.
  • the present method will iteratively program multiple units of j*i pages of the data file using the same file structure for each unit of j*i pages, and then program the remaining k ⁇ (j*i) pages using a different file structure.
  • the present method has a programming profile consisting of multiple file structures for the data file.
  • the presently described high speed wear leveling programming method has been described for a Flash memory system having a single channel, such as the embodiment shown in FIG. 4 .
  • the previously described embodiments of the invention are executed in a Flash memory system having two or more channels.
  • at least two data files are concurrently programmed; a first data file in one channel and a second data file in another channel.
  • memory devices having a single memory bank have been described in operation with memory devices having a single memory bank.
  • memory devices having two or more memory banks can be used. With two memory banks, there will be two available page buffers for storing up to two pages of data.
  • several programming options are available. In a first option, all the pages of data to be programmed to one memory device are programmed to one block within one bank of the memory device. The operation would be analogous to a memory device having only one memory bank.
  • two pages of the data file are loaded into one memory device concurrently, or in a single program command. This will effectively increase programming throughput as each memory device will program two pages at the same time.
  • programming operations are interleaved between banks of the memory devices.
  • programming pages to two memory devices will proceed in the following sequence: device 1 [bank 1 ], device 2 [bank 1 ], device 1 [bank 2 ], and device 2 [bank 2 ].
  • the programming sequence should be obvious for memory devices having more than 2 banks.
  • FIG. 10 is a timing diagram illustrating high speed interleaved read and program operations for the Flash memory system of FIG. 4 .
  • memory devices 106 and 112 are to be programmed with data, while memory devices 108 and 110 are to provide read data.
  • memory device 106 receives a program command Data[ 0 ], and then immediately commences core internal sequences for programming the data.
  • a read command is received by memory device 108 , and internal data transfer operations (xfer) proceed.
  • An internal data transfer operation will take 20 micro seconds for example, for reading out the data and loading the data registers, after which time the Flash controller will issue the read command for memory device 110 at the beginning of time period t 3 .
  • An internal NOP period 500 is entered by memory device 108 to allow flow-through of a command to a downstream memory device before outputting data from its data registers.
  • Memory device 110 will commence its internal data transfer operation after receiving its respective read command. However, now that the signal lines between memory devices 108 and 110 are unused, upstream memory device 108 will begin outputting the data in its data registers to memory device 110 , which passes the data through to memory device 112 . This is done in a sequential manner, for example. At the end of time period t 3 , memory device 108 will have finished outputting all its read data, thereby allowing memory device 110 to start outputting its read data at the start of time period t 4 . Since memory device 110 cannot output its data until memory device 108 has finished outputting its data, an internal NOP period 502 is entered.
  • interleaved read and program operations have been illustrated, interleaved read, program and erase operations are executable in any combination.
  • High speed interleaved programming method is used to maximize programming performance in a Flash memory system having serially connected memory devices.
  • High speed interleaved programming is applied to data files of any size.
  • a high speed wear leveling programming method is used to distribute the pages of a data file with a file structure based on a size of the data file. While the embodiments are directed to Flash memory devices, the embodiments of the invention are applicable to other memory devices in which pages of data files are programmed or written to at least two memory devices.
  • Embodiments of the invention can be represented as a software product stored in a machine-readable medium (also referred to as a computer-readable medium, a processor-readable medium, or a computer usable medium having a computer-readable program code embodied therein).
  • the machine-readable medium can be any suitable tangible medium, including magnetic, optical, or electrical storage medium including a diskette, compact disk read only memory (CD-ROM), memory device (volatile or non-volatile), or similar storage mechanism.
  • the machine-readable medium can contain various sets of instructions, code sequences, configuration information, or other data, which, when executed, cause a processor to perform steps in a method according to an embodiment of the invention.
  • Those of ordinary skill in the art will appreciate that other instructions and operations necessary to implement the described invention can also be stored on the machine-readable medium.
  • Software running from the machine-readable medium can interface with circuitry to perform the described tasks.

Abstract

A Flash memory system architecture having serially connected Flash memory devices to achieve high speed programming of data. High speed programming of data is achieved by interleaving pages of the data to be programmed amongst the memory devices in the system, such that different pages of data are stored in different memory devices. A memory controller issues program commands for each memory device. As each memory device receives a program command, it either begins a programming operation or passes the command to the next memory device. Therefore, the memory devices in the Flash system sequentially program pages of data one after the other, thereby minimizing delay in programming each page of data into the Flash memory system. The memory controller can execute a wear leveling algorithm to maximize the endurance of each memory device, or to optimize programming performance and endurance for data of any size.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • This is a Continuation application of U.S. patent application Ser. No. 11/693,027 filed on Mar. 29, 2007, which claims the benefit of priority of U.S. Provisional Patent Application No. 60/788,083 filed Mar. 31, 2006, which is incorporated herein by reference in its entirety.
  • FIELD OF THE INVENTION
  • The present invention relates generally to Flash memory. More particularly, the present invention relates to a multi-device Flash memory system for mass storage applications.
  • BACKGROUND OF THE INVENTION
  • Flash memory is a commonly used type of non-volatile memory in widespread use as mass storage for consumer electronics, such as digital cameras and portable digital music players for example. The density of a presently available Flash memory chip can be up to 32 Gbits (4 GB), which is suitable for use in popular USB Flash drives since the size of one Flash chip is small.
  • The advent of 8 mega pixel digital cameras and portable digital entertainment devices with music and video capabilities has spurred demand for ultra-high capacities to store the large amounts of data, which cannot be met by the single Flash memory device. Therefore, multiple Flash memory devices are combined together into a memory system to effectively increase the available storage capacity. For example, Flash storage densities of 20 GB may be required for such applications.
  • FIG. 1 is a block diagram of a prior art Flash memory system 10 integrated with a host system 12. Flash memory system 10 includes a Flash memory controller 14 in communication with host system 12, and multiple non-volatile memory devices 16. The host system will include a processing device such as a microcontroller, microprocessor, or a computer system. The Flash memory system 10 of FIG. 1 is configured to include one channel 20, where memory devices 16 are connected in parallel to channel 20. Those skilled in the art will understand that the memory system 10 will have any number of memory devices connected to it.
  • Channel 20 includes a set of common buses, which include data and control lines that are connected to all its corresponding memory devices. While not shown, each memory device is enabled/disabled with a respective chip select signal provided by Flash memory controller 14. The Flash controller 14 is responsible for issuing commands and data, via the channel, to a selected memory device based on the operation of the host system 12. Data read from the memory devices is transferred via the channel back to the Flash memory controller 14 and host system 12. Flash memory system 10 is generally referred to as a multi-drop configuration, in which the memory devices 16 are connected in parallel with respect to channel 20.
  • In Flash memory system 10, non-volatile memory devices 16 are identical to each other, and are typically implemented as NAND Flash memory devices. Those skilled in the art will understand that Flash memory is organized into banks, and each bank is organized into blocks to facilitate block erasure. Most commercially available NAND Flash memory devices are configured to have two banks of memory. Prior to a discussion of the operation of Flash memory system 10, a brief overview of a single NAND Flash memory device memory core is described.
  • FIG. 2 is a general block diagram of one bank of a known NAND Flash memory. Bank 30 is organized into k+1 blocks. Each block consists of NAND memory cell strings, having up to i+1 Flash memory cells serially connected to each other. Accordingly, wordlines WL0 to WLi are connected to the gates of each Flash memory cell in the memory cell string. A string select device connected to signal SSL (string select line) selectively connects the memory cell string to a bitline, while a ground select device connected to signal GSL (ground select line) selectively connects the memory cell string to a source line, such as VSS. The string select device and the ground select device are n-channel transistors. There are j+1 bitlines common to all blocks of bank 30, and each bitline is connected to one NAND memory cell string in each of blocks [0] to [k]. Each wordline (WL0 to WLi), SSL and GSL signal is connected to the same corresponding transistor device in each NAND memory cell string in the block. As those skilled in the art should be aware, data stored in the Flash memory cells along one wordline is referred to as a page of data.
  • Connected to each bitline outside of the bank 30 is a data register 32 for storing one page of write data to be programmed into one page of Flash memory cells. Data register 32 also includes sense circuits for sensing data read from one page of Flash memory cells. During programming operations, the data registers perform program verify operations to ensure that the data has been properly programmed into the Flash memory cells connected to the selected wordline. Programming within a block typically starts at the page corresponding to WL0, and proceeds sequentially up to WLi to fill the present block. Then programming continues with WL0 of a new block. Within a device, blocks are programmed in sequence.
  • Returning to the Flash memory system 10 of FIG. 1, there are specific issues that will adversely impact performance of the system. Some are physical while others are architectural.
  • The configuration of Flash memory system 10 imposes physical performance limitations. With the large number of parallel signals running across the system, the signal integrity of the signals they carry will be degraded by crosstalk, signal skew, and simultaneous switching noise (SSN). Power consumption in such a configuration becomes an issue as each signal track between the flash controller and flash memory devices is frequently charged and discharged for signaling. With increasing system clock frequencies, the power consumption will increase as well.
  • From an architectural perspective, programming operations will take too much time. A primary function of the Flash controller 14 is to manage the writing of data to the memory devices in the system. In the Flash memory context, writing of data is more commonly referred to as programming data. There are two significant issues related to Flash programming. First, Flash programming is slow relative to volatile memories such as DRAM and SRAM, and other non-volatile memories such as hard disk drives. Programming data to Flash memory cells requires high voltages and a stepped programming sequence to obtain a tight programmed threshold voltage distribution. In a NAND Flash memory device having two banks of memory, two pages of data are concurrently programmed, one for each bank. Since there is only one data register per bank, further programming operations must wait until the current pages have been successfully programmed. Therefore, programming large quantities of data to the Flash devices 16 may require a significant amount of time.
  • A second issue with the conventional Flash memory system 10 is the linear file structure of the program data. FIG. 3 is an illustration of the conventional file structure for a Flash memory system 50 having four memory devices. In FIG. 3, each memory device 52, 54, 56 and 58 has a total of n physical pages of storage space, which are divided among any number of blocks. In the presently shown example, it is assumed that the n pages are divided equally between two banks. Most Flash memory systems will store a data file consisting of a number of data pages, linearly within one memory device. For example, the first page of the data file is stored in Page 0 of device 52, and successive data pages are progressively stored in subsequent pages. Once device 52 is full, then further data files to be stored in system 50 starts at Page 0 in device 54, and so forth. Arrow 60 shows the storage pattern of data being written to the Flash memory system 50.
  • This linear file structure coupled with the relatively long programming time per page of the data file per memory device, results in a Flash memory system that requires significant time to store data. Another issue which is related to the linear file structure is device reliability, and more specifically, program/erase wearing of one memory device relative to the other memory devices in the system. Program/erase wearing refers to a progressive degradation of a Flash memory cell due to cumulative program and erase operations. The effect of such cumulative program and erase operations is the alteration of the program and erase characteristics of the memory cell beyond optimal parameters. When memory cells are degraded, higher program and erase voltages are needed to program or erase the memory cells to the desired threshold voltages. Eventually, the memory cells will fail to function properly. This is the reason that Flash memory are rated for a limited number of erase-program cycles, which is between 10,000 and 100,000 cycles.
  • If for example, the first memory device 52 in FIG. 3 endures more program and erase cycles than any of the other memory devices, memory device 52 will likely fail before the others. When memory device 52 fails, the entire system 50 is no longer usable since the memory devices are packaged together and replacement of a single memory device is impractical. This is an unfortunate waste of memory devices, as the remaining devices in the system are still useful and may have significant life left.
  • An inherent technical architecture of most Flash memory is that the smallest unit of memory which is erasable is a block of memory. This means that if even one page within the block is to be modified, the entire block must be re-programmed along with the new page. This is referred to as block re-programming, which requires significant programming time and hence negatively impacts performance of the system.
  • Therefore, presently known Flash memory systems have slow throughput for programming data, and due to the unequal program and erase wearing across the devices, the entire system will have a lifespan limited to the first memory device to fail.
  • It is, therefore, desirable to provide a high speed Flash memory system architecture having a scheme for maximizing the lifespan of the system.
  • SUMMARY OF THE INVENTION
  • It is an object of the present invention to obviate or mitigate at least one disadvantage of previous control schemes for Flash memory systems. In particular, it is an object of the present invention to improve Flash memory system programming throughput by interleaving programming operations in each Flash memory device of the system.
  • In a first aspect, the present invention provides a method for controlling first and second Flash memory devices connected to a channel. The method includes executing a first operation in the first Flash memory device in response to a first command, and initiating a second operation in the second Flash memory device in response to the a second command, while the first Flash memory device is executing the first operation.
  • In an embodiment of the present aspect, the first Flash memory device and the second Flash memory device are serially connected to each other, and the second command is passed to the second Flash memory device through the first Flash memory device before the step of initiating. In further embodiments, the step of executing the first operation includes programming at least one page of a data file in the first memory device. The second operation includes initiating programming of at least one other page of the data file in the second memory device, while the method further includes initiating a third operation in the first Flash memory device in response to a third command. The second operation includes initiating a read operation of data in the second memory device or initiating an erase operation in the second memory device. In yet another embodiment, executing the first operation includes one of a read operation and an erase operation in the first memory device.
  • In a second aspect, the present invention provides a method for high speed wear leveling programming in a Flash memory system having a plurality Flash memory devices. The method includes receiving a data file having k pages, k being an integer greater than 0; selecting a programming profile corresponding to the size of k and configuration parameters of the Flash memory system; and programming at least one of the k pages of the data file in each of to at least two of the plurality of Flash memory devices in accordance with the selected programming profile.
  • According to an embodiment of the present aspect, the configuration parameters includes j Flash memory devices, and each of the j Flash memory devices have i pages per block, where j and i are integer values greater than 0. The step of selecting includes calculating a ceiling function of z, where z=k/i, and the programming profile includes a single file structure for storing k pages of the data file in z of j Flash memory devices when z is less than or equal to j. The step of programming includes sequentially providing program commands to each of the z Flash memory devices for programming the k pages, where each program command programs the at least one of the k pages.
  • In another embodiment of the present aspect, the programming profile includes a multiple file structure when z is greater than j. The multiple file structure includes storing m units of j*i pages of the data file in j Flash memory devices, and storing k−(m*(j*i)) pages of the data file in z of j Flash memory devices when z is less than or equal to j, where m is an integer value greater than 0. The step of programming includes sequentially providing program commands to each of the j Flash memory devices for programming the j*i pages of the data file, where each program command programs the at least one of the k pages. The step of programming further includes sequentially providing program commands to each of the z Flash memory devices for programming the k−(m*(j*i)) pages, where each program command programs the at least one of the k pages.
  • In a third aspect, the present invention provides a data file storage architecture for a memory system having at least two memory devices connected to the same channel. The data file storage architecture includes portions of the data file stored in two of the at least two memory devices. According to embodiments of the present aspect, the portions are substantially equal in size to each other, and the portions are stored in each of the at least two memory devices of the memory system.
  • In a fourth aspect, the present invention provides a method for high speed wear leveling programming in a Flash memory system having j Flash memory devices, where each of the j Flash memory devices has i pages per block, where j and i are integer values greater than 0. The method includes receiving a data file having k pages, k being an integer greater than 0; providing commands for programming k pages within z of j memory devices if a ceiling function of z=k/i is less than or equal to j; providing commands for programming ri pages within j memory devices if the ceiling function of z=k/i is greater than j; updating k by setting k=k−(j*i); and repeating the step of programming updated k pages.
  • In a fifth aspect, the present invention provides a Flash memory system. The Flash memory system includes a controller, a first Flash memory device, and a second Flash memory device. The controller has a channel for providing a first command and a second command. The first Flash memory device is coupled to the channel for executing a first operation in response to the first command. The second Flash memory device is coupled to the channel for initiating a second operation in response to the second command while the first Flash memory device is executing the first operation.
  • According to embodiments of the present aspect, the first Flash memory device and the second Flash memory device are serially connected to each other, and the second command is passed to the second Flash memory device through the first Flash memory device. The first operation includes a programming operation, and the first Flash memory device programs at least one page of a data file. The second operation includes another programming operation, and the second Flash memory device programs at least one other page of the data file.
  • Other aspects and features of the present invention will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments of the invention in conjunction with the accompanying figures.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • Embodiments of the present invention will now be described, by way of example only, with reference to the attached Figures, wherein:
  • FIG. 1 is a block diagram of a prior art Flash memory system;
  • FIG. 2 is a schematic of a prior art NAND Flash memory core;
  • FIG. 3 is an illustration of a conventional file structure for a Flash memory system;
  • FIG. 4 is a block diagram of a Flash memory system according to an embodiment of the present invention;
  • FIG. 5 is a timing diagram of program commands issued by the Flash controller of FIG. 4, according to an embodiment of the present invention;
  • FIG. 6 is a timing diagram showing program commands received by each memory device of the Flash memory system in FIG. 4;
  • FIG. 7 is a flow chart illustrating a high speed interleaved programming method, according to an embodiment of the present invention;
  • FIG. 8 is a graphical illustration of a file structure in the Flash memory system in FIG. 4 resulting from the high speed interleaved programming method of FIG. 7;
  • FIG. 9 is a flow chart illustrating a high speed wear leveling programming method, according to an embodiment of the present invention; and
  • FIG. 10 is a timing diagram showing interleaved program and read operations.
  • DETAILED DESCRIPTION
  • A Flash memory system architecture having serially connected Flash memory devices to achieve high speed programming of data. High speed programming of data is achieved by interleaving pages of the data amongst the memory devices in the system, such that different pages of data are stored in different memory devices. A memory controller issues program commands for each memory device in a bitstream having one or more signal lines. As each memory device receives a program command, it either begins a programming operation or passes the command to the next memory device. Therefore, the memory devices in the Flash system sequentially program pages of data one after the other, thereby minimizing delay in programming each page of data into the Flash memory system. The memory controller executes a wear level control algorithm to optimize programming performance and endurance for data of any size.
  • FIG. 4 is a block diagram of a Flash memory system having serially connected memory devices for executing high speed data programming operations with wear level control, according to an embodiment of the present invention. Flash memory system 100 includes a Flash memory controller 102 in communication with host system 104, and four serially connected Flash memory devices 106, 108, 110 and 112. While four memory devices are shown in the present embodiment, the embodiments of the present invention will be effective for memory systems having at least two memory devices. Each of the four Flash memory devices have a serial input/output interface circuit for facilitating serial operation between memory devices. An example of a such a Flash memory device is described in commonly owned U.S. patent application Ser. No. 11/324,023, filed on Dec. 30, 2005, and commonly owned U.S. patent application Ser. No. 11/496,278, filed on Jul. 31, 2006., the contents of which are incorporated herein by reference. The Flash memory device of U.S. patent application Ser. No. 11/324,023 is referred to as a multiple independent serial link device (MISL). As in the system shown in FIG. 1, the host system will include a processing device such as a microcontroller, microprocessor, or a computer system.
  • Flash memory device 106 is the first device in the chain, and receives commands, such as read, program and erase commands, from Flash memory controller 102. In the MISL Flash device of U.S. patent application Ser. No. 11/324,023, all commands, data and address information are received as a serial bitstream. The commands include data information, address information, and any other information required by the memory device for executing a particular operation. As each Flash memory device should include flow-through logic circuitry, any received command not intended for a particular device is passed to the next Flash memory device, and so forth, until it is acted upon by the intended Flash memory device. The last Flash memory device 112 in the chain has outputs connected to the Flash memory controller 102, for providing read data in response to a read command. The presently shown embodiment of FIG. 4 has one channel for sending and receiving data from the chain of Flash memory devices. Those skilled in the art will understand that Flash memory controller 102 will optionally have multiple channels for accommodating a corresponding number of Flash memory device chains. Since each Flash memory device is preferably positioned in close proximity with the other, conducting wires interconnecting the Flash memory devices to each other will be minimized. Therefore, there are no physical performance limitations related to bus line length, as in Flash memory system 10 of FIG. 1.
  • As previously discussed, the Flash memory controller 102 is responsible for issuing program commands for each Flash memory device. For high speed programming of data according to an embodiment of the present invention, pages of a data file are programmed to different memory devices. This is done by issuing program commands serially one after the other to initiate program operations in each Flash memory device in rapid succession. FIGS. 5 and 6 will help illustrate how such high speed programming is achieved.
  • FIG. 5 is a timing diagram illustrating the issuance of program commands by the Flash memory controller 102 for maximizing overall programming speed for the Flash memory system 100, according to an embodiment of the present invention. In the presently shown example, four program commands Data[0], Data[1], Data[2] and Data[3] are issued serially at respective time periods t1 to t4 by Flash memory controller 102 to program one data file. The identification number within square brackets for each program command indicates the sequential order the program command was issued from the Flash memory controller 102. Each programming command will include, but is not limited to, a command 200 and at least one page of data 202 for a specific memory device. The command 200 includes an address to which the page of data is to be programmed, and a device identifier for matching the programming command to the specific memory device. Flash memory devices 106, 108, 110 and 112 are responsive to program commands Data[0], Data[1], Data[2] and Data[3] respectively. Since the Flash memory devices are serially connected and the program commands are issued serially, the core programming operations of each Flash memory device overlap with the operations of the subsequent Flash memory device, with the exception of the last Flash memory device that receives a programming command.
  • If it is assumed that each programming command requires about 85 microseconds to transfer to the memory device (time t1), then the total sequence for transferring the four program commands will require 4×85 microseconds=340 microseconds. The time required for programming the at least one page of data per memory device is fixed, and assumed to be about 200 microseconds. Therefore, the total elapsed time for programming all the data to the Flash memory system 100 will be about 340 microseconds+200 microseconds=540 microseconds. The 200 microsecond programming time is contributed by the last memory device to receive a programming command. In contrast, programming 4 pages to the same memory device will take 1140 microseconds. The overlapping programming operations of the Flash memory devices is more clearly shown in the expanded timing diagram of FIG. 6.
  • FIG. 6 is an expanded timing diagram showing the operations of Flash memory devices 106, 108, 110 and 112 in response to respective program commands Data[0], Data[1], Data[2] and Data[3]. The time periods t1 to t4 correspond to the same time periods shown in FIG. 5. The programming sequence of FIG. 6 will now be described with reference to the flow chart of FIG. 7. The Flash system programming control embodiment described in FIG. 7 will be referred to as a high speed interleaved programming method, whereby programming operations are interleaved between different memory devices. The method begins at step 300 where at least two program commands are provided serially to the first memory device 106 in the system. The first program command corresponds to program command Data[0] while the second program command corresponds to program command Data[1]. At step 302, memory device 106 receives program command Data[0] during a first time period t1, which is followed by a program operation at step 304. During time period t1, program command Data[0] is transferred to memory device 106 while memory devices 108, 110 and 112 remain in a no operation (NOP) state.
  • As soon as program command Data[0] has been transferred to memory device 106, the second program command Data[1] is received by memory device 108 during a second time period t2 at step 306. A program operation follows at step 308, and because the programming operation for memory device 106 has already commenced at the end of time period t1, there is a period of time where both memory devices 106 and 108 are executing programming operations at the same time. The process would repeat in the same manner for the next program command and memory device. In the present example, programming operations in memory devices 106 and 108 will have been completed by the end of time period t4. The programming operation in memory device 110 will be completed as the programming operation in memory device 112 continues.
  • The above example presents a scenario where the first memory device to receive a command is 106. Alternately, any one of the memory devices in the system can be the first memory device to receive the first program command. A fifth program command is issued to memory device 106 after time period t4, provided that device 106 has finished its programming operation. Those skilled in the art will understand that different Flash memory devices will have varying programming times. In the presently shown example of FIG. 6, memory device 106 has finished programming its data at the beginning of time period t4, therefore it is ready to receive the next program command Data[4] as soon as memory device 112 has finished receiving program command Data[3]. If the Flash memory device has a very long core programming time, then the Flash memory controller will need to wait until memory device 106 has completed programming operations before issuing the Data[4] program command. Flash memory devices will typically provide a ready status signal to the Flash memory controller to indicate when a programming operation is completed.
  • FIG. 8 is a graphical file structure illustration of Flash memory devices 106, 108, 110 and 112 after the high speed programming sequence described in FIG. 6 and FIG. 7 has been executed for program commands Data[0], Data[1], Data[2], Data[3] and Data[4]. The file structure shown in FIG. 8 assumes that memory blocks of devices 106, 108 and 112 are empty prior to programming. This is why pages are programmed to physical page 0 of these devices. In memory device 110 on the other hand, the memory block may have other data in physical pages 0 and 1. Therefore, Data[2] is programmed to the next available page in the block, which is in physical page 2. As shown in FIG. 8, physical page 1 of memory device 106 is the last page to be programmed in the presently shown high speed programming sequence. The next programming sequence will start programming data at physical page 1 of memory device 108, and will proceed in the same manner as previously described for the programming sequence shown in FIG. 6. Therefore, maximum programming speed of Flash memory system 100 is obtained when program commands are serially issued to consecutive serially connected memory devices. In otherwords, a file structure in which data is distributed across the maximum number of memory devices in the serially interconnected Flash memory system will result in highest speed programming of a data file. It should be noted that data does not necessarily need to be programmed in the same physical page number across all the memory devices.
  • While high speed programming is beneficial to systems using Flash memory system 100, some systems may require maximized endurance of the Flash memory system 100. The file structure shown in FIG. 8 will not maximize program/erase wear across all memory devices, mainly due to the block erase architecture of Flash memory devices. For example, if a 20 page data file is interleaved programmed across one block in each memory device, then there is a possibility that all four memory devices will need to perform a block erase before updating the data file. In contrast, if all 20 pages were stored in one block of one memory device, then only that block needs to be erased.
  • Therefore, according to another embodiment of the invention, the above described high speed programming control method is adjusted to minimize program/erase wear, or to optimize programming performance and program/erase wear. More specifically, the Flash controller 102 of FIG. 4 executes a program control algorithm for optimizing program performance and program/erase wear based on predetermined criteria. This predetermined criteria will include characteristics of the data to be programmed and characteristics of the memory devices of the Flash memory system. Data characteristics include the number of pages of the data to be programmed, and memory device characteristics include the number of pages per block.
  • FIG. 9 is a flow chart illustrating an embodiment for programming multiple Flash memory devices in a Flash memory system with high speed and with wear leveling control. This program control embodiment will be referred to as a high speed wear leveling programming method. Wear leveling refers to a scheme for prolonging the life of the Flash memory system. The presently described embodiment will optimize wear leveling and performance for any data file to be programmed, by using a variety of programming profiles. A programming profile generally corresponds to a programming sequence for storing pages of a data file with a specific file storage structure. Ultimately, the programming profile distributes pages of the data file across the memory devices of the Flash memory system. The presently described method is executable by a memory controller, such as Flash controller 102 of FIG. 4, in a system of serially connected memory devices.
  • The high speed wear leveling programming method starts at step 400 where a variable i is set to be the number of pages per block in each memory device of the Flash memory system, and a variable j is set to be the number of memory devices in the Flash memory system. It is presumed that all the memory devices in the Flash memory system are identical to each other, and have the same block size. This information is pre-programmed into the memory controller. At step 402, a data file consisting of a number of pages k, is received by the memory controller for programming. Proceeding to step 404, a calculation is made to determine if k is less than or equal to i. If k is less than or equal to i, meaning that the data file is less than or equal to one block of storage space in a memory device, then all k pages of the data file are programmed to one block of one memory device at step 406. This is an example of a programming profile having a single file structure. The memory controller selects the specific memory device to which the data file will be programmed to in accordance with one or more selection parameters. For example, one selection parameter is the memory device with the highest number of remaining program/erase cycles, while another selection parameter includes the last memory device to be programmed to.
  • On the other hand, if k is greater than i, meaning that the data file includes more pages than one block of storage space in a memory device, then the method proceeds to step 408. At step 408, a calculation is made to determine if k/i is less than or equal to j. It should be noted that the calculation of k/i should yield integer numbers only. Since the present method determines the minimum number of blocks required for storing the k data, a non-integer result having a whole number and decimal portion (ie. a real number) indicates that one block more than the whole number is required. This is done through known mathematical functions such as a ceiling function. Those skilled in the art will understand that a ceiling function returns the smallest integer that is not less than the real number. On the other hand, a direct integer result from k/i does not require further mathematical processing. From this point forward, reference to the k/i result will presume that a ceiling function has been applied to it.
  • If the k/i integer value is less than j, the number of memory devices in the Flash memory system, then the k pages of the data file are interleave programmed between k/i memory devices in step 410. This is another example of a programming profile having a single file structure. The interleave programming will proceed as previously described in the method of FIG. 7. In a practical example, if i=32, j=4 and k=61, then k/i=1.90. Since k/i results in a real number, a ceiling function applied to 1.90 results in the integer number 2. Hence in step 410, all k=61 pages are interleave programmed across 2 memory devices. The memory controller selects any two memory devices in the Flash memory system, whether they are directly connected together or indirectly connected together. Two indirectly connected memory devices can have at least one intervening memory device connected between them. Since the data file is programmed within two memory devices, about half of the pages are programmed in one memory device and the remainder is stored in the other memory device.
  • If k/i is at least j, the number of memory devices in the system, then different optimization programming sequences, will be used for programming differently sized groups of the data file. More specifically, very large data files are treated as multiple units of smaller data files, which are programmed according to any one of the previously described programming sequences. Continuing at step 412, all page locations in one block of each memory device is programmed with j*i pages of the k pages of the data file, according to the interleaved programming sequence of step 410. Following at step 414, the number of pages k is updated by setting it equal to k−(j*i). Therefore, the remaining number of pages to be programmed is calculated. The method loops back to step 404 to repeat the decision tree processing and programming sequences based on the updated value of k. In summary, the present method will iteratively program multiple units of j*i pages of the data file using the same file structure for each unit of j*i pages, and then program the remaining k−(j*i) pages using a different file structure. Hence the present method has a programming profile consisting of multiple file structures for the data file.
  • A practical example will now be used to illustrate this embodiment. If i=32, j=4 and k=192, then the first 128 pages will be programmed across all the memory devices as described in step 412. At step 414, k is updated to be 192−(128)=64. Then the remaining 64 pages are programmed across two memory devices as described in step 410. As previously mentioned, any two memory devices are selected for programming the remaining 64 pages. While the presently described embodiment illustrates a method where programming is followed by recalculation of k, the entire sequence can be determined by the Flash controller in advance and before any programming operations begin by employing the above described calculations. While it is presumed that the first pages of the data file to be programmed are the j*i pages, the first pages to be programmed can be the k−(j*i) pages instead, followed by the multiple units of j*i pages.
  • The presently described high speed wear leveling programming method has been described for a Flash memory system having a single channel, such as the embodiment shown in FIG. 4. The previously described embodiments of the invention are executed in a Flash memory system having two or more channels. In such alternate embodiments, at least two data files are concurrently programmed; a first data file in one channel and a second data file in another channel.
  • Additionally, the present embodiment has been described in operation with memory devices having a single memory bank. Of course, memory devices having two or more memory banks can be used. With two memory banks, there will be two available page buffers for storing up to two pages of data. In a multi-bank device configuration, several programming options are available. In a first option, all the pages of data to be programmed to one memory device are programmed to one block within one bank of the memory device. The operation would be analogous to a memory device having only one memory bank. In a second option, two pages of the data file are loaded into one memory device concurrently, or in a single program command. This will effectively increase programming throughput as each memory device will program two pages at the same time. In a third option, programming operations are interleaved between banks of the memory devices. For example, programming pages to two memory devices will proceed in the following sequence: device 1 [bank 1], device 2 [bank 1], device 1 [bank 2], and device 2 [bank 2]. The programming sequence should be obvious for memory devices having more than 2 banks.
  • Furthermore, while the previously described high speed wear leveling programming method has been described for Flash memory systems having serially connected, or daisy-chained memory devices, the embodiments are applicable to multi-drop configured Flash systems such as the one shown in FIG. 1. This is done by enabling the appropriate memory device and providing the corresponding command data onto the common busses at different times.
  • The previously described embodiments of the invention illustrate examples where programming operations in the Flash memory system of FIG. 4 are interleaved. According to another embodiment of the invention, interleaved program and read operations are executed by the Flash memory system of FIG. 4.
  • FIG. 10 is a timing diagram illustrating high speed interleaved read and program operations for the Flash memory system of FIG. 4. In this example, memory devices 106 and 112 are to be programmed with data, while memory devices 108 and 110 are to provide read data. During time period t1, memory device 106 receives a program command Data[0], and then immediately commences core internal sequences for programming the data. At the beginning of time period t2, a read command is received by memory device 108, and internal data transfer operations (xfer) proceed. An internal data transfer operation will take 20 micro seconds for example, for reading out the data and loading the data registers, after which time the Flash controller will issue the read command for memory device 110 at the beginning of time period t3. An internal NOP period 500 is entered by memory device 108 to allow flow-through of a command to a downstream memory device before outputting data from its data registers.
  • Memory device 110 will commence its internal data transfer operation after receiving its respective read command. However, now that the signal lines between memory devices 108 and 110 are unused, upstream memory device 108 will begin outputting the data in its data registers to memory device 110, which passes the data through to memory device 112. This is done in a sequential manner, for example. At the end of time period t3, memory device 108 will have finished outputting all its read data, thereby allowing memory device 110 to start outputting its read data at the start of time period t4. Since memory device 110 cannot output its data until memory device 108 has finished outputting its data, an internal NOP period 502 is entered. At the end of time period t4, the signal lines between memory devices 110 and 112 will be unused as all the data from memory device 110 has been outputted through memory device 112. Hence at the beginning of time period t5, memory device 112 will receive program command Data[1].
  • While interleaved read and program operations have been illustrated, interleaved read, program and erase operations are executable in any combination.
  • The previously described high speed interleaved programming method is used to maximize programming performance in a Flash memory system having serially connected memory devices. High speed interleaved programming is applied to data files of any size. However, to improve endurance of all the memory devices, a high speed wear leveling programming method is used to distribute the pages of a data file with a file structure based on a size of the data file. While the embodiments are directed to Flash memory devices, the embodiments of the invention are applicable to other memory devices in which pages of data files are programmed or written to at least two memory devices.
  • In the preceding description, for purposes of explanation, numerous details are set forth in order to provide a thorough understanding of the embodiments of the invention. However, it will be apparent to one skilled in the art that these specific details are not required in order to practice the invention. In other instances, well-known electrical structures and circuits are shown in block diagram form in order not to obscure the invention. For example, specific details are not provided as to whether the embodiments of the invention described herein are implemented as a software routine, hardware circuit, firmware, or a combination thereof.
  • Embodiments of the invention can be represented as a software product stored in a machine-readable medium (also referred to as a computer-readable medium, a processor-readable medium, or a computer usable medium having a computer-readable program code embodied therein). The machine-readable medium can be any suitable tangible medium, including magnetic, optical, or electrical storage medium including a diskette, compact disk read only memory (CD-ROM), memory device (volatile or non-volatile), or similar storage mechanism. The machine-readable medium can contain various sets of instructions, code sequences, configuration information, or other data, which, when executed, cause a processor to perform steps in a method according to an embodiment of the invention. Those of ordinary skill in the art will appreciate that other instructions and operations necessary to implement the described invention can also be stored on the machine-readable medium. Software running from the machine-readable medium can interface with circuitry to perform the described tasks.
  • The above-described embodiments of the invention are intended to be examples only. Alterations, modifications and variations can be effected to the particular embodiments by those of skill in the art without departing from the scope of the invention, which is defined solely by the claims appended hereto.

Claims (6)

1. A method for programming in a Flash memory system having a plurality Flash memory devices, the method comprising:
receiving a data file having a plurality of pages;
if all of the plurality of pages of the data file can fit into a single block of one of the plurality of Flash memory devices, programming all of the plurality of pages of the data file into the single block of the one of the plurality of Flash memory devices;
otherwise, if all of the plurality of pages of the data file can fit into a plurality of blocks including one block in each of the plurality of memory devices, interleave programming all of the plurality of pages of the data file across the plurality of blocks including one block in each of the plurality of memory devices; and
otherwise, interleave programming a subset of the plurality of pages of the data file into a plurality of blocks including one block in each of the plurality of memory devices and removing the subset of the plurality of pages of the data file from the data file.
2. The method as claimed in claim 1 further comprising repeating interleave programming of the subset of the plurality of pages of the data file into the plurality of blocks including one block in each of the plurality of memory devices and removing the subset of the plurality of pages of the data file from the data file.
3. The method as claimed in claim 1 further comprising selecting the single block of the one of the plurality of Flash memory devices according to a highest number of remaining program/erase cycles remaining for the memory device.
4. The method as claimed in claim 1 further comprising selecting the single block of the one of the plurality of Flash memory devices according to a last memory device programmed.
5. The method as claimed in claim 1 wherein interleave programming comprises sequentially providing program commands to each of the plurality of memory devices.
6. The method as claimed in claim 5, wherein the sequentially provided program commands are executed in overlapping time periods.
US12/855,171 2006-03-31 2010-08-12 Flash memory system control scheme Abandoned US20100325353A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/855,171 US20100325353A1 (en) 2006-03-31 2010-08-12 Flash memory system control scheme

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US78808306P 2006-03-31 2006-03-31
US11/693,027 US7802064B2 (en) 2006-03-31 2007-03-29 Flash memory system control scheme
US12/855,171 US20100325353A1 (en) 2006-03-31 2010-08-12 Flash memory system control scheme

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/693,027 Continuation US7802064B2 (en) 2006-03-31 2007-03-29 Flash memory system control scheme

Publications (1)

Publication Number Publication Date
US20100325353A1 true US20100325353A1 (en) 2010-12-23

Family

ID=38563033

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/693,027 Active 2028-12-16 US7802064B2 (en) 2006-03-31 2007-03-29 Flash memory system control scheme
US12/855,171 Abandoned US20100325353A1 (en) 2006-03-31 2010-08-12 Flash memory system control scheme

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US11/693,027 Active 2028-12-16 US7802064B2 (en) 2006-03-31 2007-03-29 Flash memory system control scheme

Country Status (10)

Country Link
US (2) US7802064B2 (en)
EP (2) EP2002442B1 (en)
JP (1) JP5214587B2 (en)
KR (1) KR101194965B1 (en)
CN (2) CN101410906B (en)
AT (1) ATE488009T1 (en)
DE (1) DE602007010439D1 (en)
ES (1) ES2498096T3 (en)
TW (2) TWI456582B (en)
WO (1) WO2007112555A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090268521A1 (en) * 2008-04-28 2009-10-29 Koki Ueno Non-volatile semiconductor memory device
US9292210B1 (en) 2014-08-29 2016-03-22 International Business Machines Corporation Thermally sensitive wear leveling for a flash memory device that includes a plurality of flash memory modules
US9501437B2 (en) 2012-11-15 2016-11-22 Empire Technology Development Llc Scalable storage system having multiple storage channels

Families Citing this family (70)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7644239B2 (en) 2004-05-03 2010-01-05 Microsoft Corporation Non-volatile memory cache performance improvement
US7490197B2 (en) 2004-10-21 2009-02-10 Microsoft Corporation Using external memory devices to improve system performance
US8914557B2 (en) 2005-12-16 2014-12-16 Microsoft Corporation Optimizing write and wear performance for a memory
US9003354B2 (en) * 2006-07-20 2015-04-07 Texas Instruments Incorporated Optimizing memory usage and system performance in a file system requiring entire blocks to be erased for rewriting data
TW200828320A (en) * 2006-12-28 2008-07-01 Genesys Logic Inc Method for performing static wear leveling on flash memory
US8631203B2 (en) 2007-12-10 2014-01-14 Microsoft Corporation Management of external memory functioning as virtual cache
KR20100114086A (en) * 2008-01-25 2010-10-22 램버스 인코포레이티드 Multi-page parallel program flash memory
KR20100114540A (en) * 2008-02-10 2010-10-25 램버스 인코포레이티드 Segmentation of flash memory for partial volatile storage
US8275970B2 (en) * 2008-05-15 2012-09-25 Microsoft Corp. Optimizing write traffic to a disk
US8032707B2 (en) 2008-09-15 2011-10-04 Microsoft Corporation Managing cache data and metadata
US9032151B2 (en) 2008-09-15 2015-05-12 Microsoft Technology Licensing, Llc Method and system for ensuring reliability of cache data and metadata subsequent to a reboot
US7953774B2 (en) 2008-09-19 2011-05-31 Microsoft Corporation Aggregation of write traffic to a data store
US8825940B1 (en) 2008-12-02 2014-09-02 Siliconsystems, Inc. Architecture for optimizing execution of storage access commands
US8880970B2 (en) * 2008-12-23 2014-11-04 Conversant Intellectual Property Management Inc. Error detection method and a system including one or more memory devices
US9176859B2 (en) * 2009-01-07 2015-11-03 Siliconsystems, Inc. Systems and methods for improving the performance of non-volatile memory operations
US8412880B2 (en) 2009-01-08 2013-04-02 Micron Technology, Inc. Memory system controller to manage wear leveling across a plurality of storage nodes
US8924661B1 (en) * 2009-01-18 2014-12-30 Apple Inc. Memory system including a controller and processors associated with memory devices
EP2394221A4 (en) * 2009-02-09 2012-11-21 Rambus Inc Multiple plane, non-volatile memory with synchronized control
TWI396090B (en) * 2009-02-18 2013-05-11 Silicon Motion Inc Flash memory apparatus, data storage system, and method for sending special instructions to a flash memory apparatus
US10079048B2 (en) * 2009-03-24 2018-09-18 Western Digital Technologies, Inc. Adjusting access of non-volatile semiconductor memory based on access time
US8832354B2 (en) 2009-03-25 2014-09-09 Apple Inc. Use of host system resources by memory controller
US8341501B2 (en) 2009-04-30 2012-12-25 International Business Machines Corporation Adaptive endurance coding of non-volatile memories
US8639877B2 (en) 2009-06-30 2014-01-28 International Business Machines Corporation Wear leveling of solid state disks distributed in a plurality of redundant array of independent disk ranks
US8234520B2 (en) 2009-09-16 2012-07-31 International Business Machines Corporation Wear leveling of solid state disks based on usage information of data and parity received from a raid controller
US8327092B2 (en) * 2009-09-21 2012-12-04 Freescale Semiconductor, Inc. Memory device configurable as interleaved or non-interleaved memory
US9244836B2 (en) * 2009-11-23 2016-01-26 Agiga Tech Inc. Flash memory organization for reduced failure rate
TWI486769B (en) * 2010-05-26 2015-06-01 Netac Technology Co Ltd Storage device and method for polling the storage device
CN101923570B (en) * 2010-07-21 2012-07-04 中国电子科技集团公司第三十八研究所 Method for establishing large-page NAND Flash storage system under Windows CE condition
EP2418584A1 (en) 2010-08-13 2012-02-15 Thomson Licensing Method and apparatus for storing at least two data streams into an array of memories, or for reading at least two data streams from an array of memories
US8769374B2 (en) 2010-10-13 2014-07-01 International Business Machines Corporation Multi-write endurance and error control coding of non-volatile memories
WO2012048444A1 (en) 2010-10-14 2012-04-19 Freescale Semiconductor, Inc. Are Memory controller and method for accessing a plurality of non-volatile memory arrays
US8539139B1 (en) 2010-12-17 2013-09-17 Teradota Us, Inc. Managing device wearout using I/O metering
US8797799B2 (en) * 2012-01-05 2014-08-05 Conversant Intellectual Property Management Inc. Device selection schemes in multi chip package NAND flash memory system
US11249652B1 (en) 2013-01-28 2022-02-15 Radian Memory Systems, Inc. Maintenance of nonvolatile memory on host selected namespaces by a common memory controller
US10445229B1 (en) 2013-01-28 2019-10-15 Radian Memory Systems, Inc. Memory controller with at least one address segment defined for which data is striped across flash memory dies, with a common address offset being used to obtain physical addresses for the data in each of the dies
US9229854B1 (en) 2013-01-28 2016-01-05 Radian Memory Systems, LLC Multi-array operation support and related devices, systems and software
US10642505B1 (en) 2013-01-28 2020-05-05 Radian Memory Systems, Inc. Techniques for data migration based on per-data metrics and memory degradation
US9652376B2 (en) 2013-01-28 2017-05-16 Radian Memory Systems, Inc. Cooperative flash memory control
US9092353B1 (en) 2013-01-29 2015-07-28 Pmc-Sierra Us, Inc. Apparatus and method based on LDPC codes for adjusting a correctable raw bit error rate limit in a memory system
US9813080B1 (en) 2013-03-05 2017-11-07 Microsemi Solutions (U.S.), Inc. Layer specific LDPC decoder
US10230396B1 (en) 2013-03-05 2019-03-12 Microsemi Solutions (Us), Inc. Method and apparatus for layer-specific LDPC decoding
US9397701B1 (en) 2013-03-11 2016-07-19 Microsemi Storage Solutions (Us), Inc. System and method for lifetime specific LDPC decoding
US9450610B1 (en) 2013-03-15 2016-09-20 Microsemi Storage Solutions (Us), Inc. High quality log likelihood ratios determined using two-index look-up table
US9454414B2 (en) 2013-03-15 2016-09-27 Microsemi Storage Solutions (Us), Inc. System and method for accumulating soft information in LDPC decoding
US9590656B2 (en) 2013-03-15 2017-03-07 Microsemi Storage Solutions (Us), Inc. System and method for higher quality log likelihood ratios in LDPC decoding
US9728526B2 (en) 2013-05-29 2017-08-08 Sandisk Technologies Llc Packaging of high performance system topology for NAND memory systems
US9324389B2 (en) * 2013-05-29 2016-04-26 Sandisk Technologies Inc. High performance system topology for NAND memory systems
KR102254099B1 (en) 2014-05-19 2021-05-20 삼성전자주식회사 Method for processing memory swapping operation, and host device, storage device and data processing system adopting the same
US9417804B2 (en) * 2014-07-07 2016-08-16 Microsemi Storage Solutions (Us), Inc. System and method for memory block pool wear leveling
US10552085B1 (en) 2014-09-09 2020-02-04 Radian Memory Systems, Inc. Techniques for directed data migration
US9542118B1 (en) 2014-09-09 2017-01-10 Radian Memory Systems, Inc. Expositive flash memory control
US10332613B1 (en) 2015-05-18 2019-06-25 Microsemi Solutions (Us), Inc. Nonvolatile memory system with retention monitor
US10552058B1 (en) 2015-07-17 2020-02-04 Radian Memory Systems, Inc. Techniques for delegating data processing to a cooperative memory controller
US9799405B1 (en) 2015-07-29 2017-10-24 Ip Gem Group, Llc Nonvolatile memory system with read circuit for performing reads using threshold voltage shift read instruction
KR102296740B1 (en) * 2015-09-16 2021-09-01 삼성전자 주식회사 Memory device and memory system including the same
US9886214B2 (en) 2015-12-11 2018-02-06 Ip Gem Group, Llc Nonvolatile memory system with erase suspend circuit and method for erase suspend management
US9892794B2 (en) 2016-01-04 2018-02-13 Ip Gem Group, Llc Method and apparatus with program suspend using test mode
US9899092B2 (en) 2016-01-27 2018-02-20 Ip Gem Group, Llc Nonvolatile memory system with program step manager and method for program step management
US10291263B2 (en) 2016-07-28 2019-05-14 Ip Gem Group, Llc Auto-learning log likelihood ratio
US10157677B2 (en) 2016-07-28 2018-12-18 Ip Gem Group, Llc Background reference positioning and local reference positioning using threshold voltage shift read
US10236915B2 (en) 2016-07-29 2019-03-19 Microsemi Solutions (U.S.), Inc. Variable T BCH encoding
US9928907B1 (en) * 2017-01-27 2018-03-27 Western Digital Technologies, Inc. Block erase schemes for cross-point non-volatile memory devices
US10600484B2 (en) 2017-12-20 2020-03-24 Silicon Storage Technology, Inc. System and method for minimizing floating gate to floating gate coupling effects during programming in flash memory
US10552319B2 (en) * 2018-06-01 2020-02-04 Intel Corporation Interleave set aware object allocation
KR20200121654A (en) 2019-04-16 2020-10-26 삼성전자주식회사 Memory controller and memory system improving threshold voltage distribution characteristic and operating method of memory system
US11315649B2 (en) 2019-04-16 2022-04-26 Samsung Electronics Co., Ltd. Memory controller, memory device and memory system having improved threshold voltage distribution characteristics and related operating methods
US11163482B2 (en) 2019-06-26 2021-11-02 International Business Machines Corporation Dynamic performance-class adjustment for storage drives
US11049570B2 (en) 2019-06-26 2021-06-29 International Business Machines Corporation Dynamic writes-per-day adjustment for storage drives
US11137915B2 (en) 2019-06-27 2021-10-05 International Business Machines Corporation Dynamic logical storage capacity adjustment for storage drives
US11175984B1 (en) 2019-12-09 2021-11-16 Radian Memory Systems, Inc. Erasure coding techniques for flash memory

Citations (81)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4174536A (en) * 1977-01-21 1979-11-13 Massachusetts Institute Of Technology Digital communications controller with firmware control
US4733376A (en) * 1984-10-17 1988-03-22 Fujitsu Limited Semiconductor memory device having serial data input circuit and serial data output circuit
US4796231A (en) * 1985-01-22 1989-01-03 Texas Instruments Incorporated Serial accessed semiconductor memory with reconfigurable shift registers
US5126808A (en) * 1989-10-23 1992-06-30 Advanced Micro Devices, Inc. Flash EEPROM array with paged erase architecture
US5136292A (en) * 1989-03-15 1992-08-04 Oki Electric Industry Co., Ltd. Serial data receiving circuit for serial to parallel conversion
US5175819A (en) * 1990-03-28 1992-12-29 Integrated Device Technology, Inc. Cascadable parallel to serial converter using tap shift registers and data shift registers while receiving input data from FIFO buffer
US5243703A (en) * 1990-04-18 1993-09-07 Rambus, Inc. Apparatus for synchronously generating clock signals in a data processing system
US5280539A (en) * 1992-01-15 1994-01-18 Samsung Electronics Co., Ltd. Synchronous circuit for serial input signal
US5365484A (en) * 1993-08-23 1994-11-15 Advanced Micro Devices, Inc. Independent array grounds for flash EEPROM array with paged erase architechture
US5404460A (en) * 1994-01-28 1995-04-04 Vlsi Technology, Inc. Method for configuring multiple identical serial I/O devices to unique addresses through a serial bus
US5440694A (en) * 1992-03-26 1995-08-08 Nec Corporation Interface circuit for allowing receiving serial data input after receiving serial input suspension signal
US5452259A (en) * 1993-11-15 1995-09-19 Micron Technology Inc. Multiport memory with pipelined serial input
US5473563A (en) * 1993-01-13 1995-12-05 Samsung Electronics Co., Ltd. Nonvolatile semiconductor memory
US5473577A (en) * 1993-03-20 1995-12-05 Hitachi, Ltd. Serial memory
US5473566A (en) * 1994-09-12 1995-12-05 Cirrus Logic, Inc. Memory architecture and devices, systems and methods utilizing the same
US5530828A (en) * 1992-06-22 1996-06-25 Hitachi, Ltd. Semiconductor storage device including a controller for continuously writing data to and erasing data from a plurality of flash memories
US5568423A (en) * 1995-04-14 1996-10-22 Unisys Corporation Flash memory wear leveling system providing immediate direct access to microprocessor
US5596724A (en) * 1994-02-04 1997-01-21 Advanced Micro Devices Input/output data port with a parallel and serial interface
US5602780A (en) * 1993-10-20 1997-02-11 Texas Instruments Incorporated Serial to parallel and parallel to serial architecture for a RAM based FIFO memory
US5636342A (en) * 1995-02-17 1997-06-03 Dell Usa, L.P. Systems and method for assigning unique addresses to agents on a system management bus
US5671178A (en) * 1995-02-04 1997-09-23 Samsung Electronics Co., Ltd. Erase verifying circuit for a nonvolatile semiconductor memory with column redundancy
US5721840A (en) * 1993-09-20 1998-02-24 Olympus Optical Co., Ltd. Information processing apparatus incorporating automatic SCSI ID generation
US5740379A (en) * 1994-08-19 1998-04-14 Siemens Aktiengesellschaft Method for generating unique addresses for electrical devices from input bit patterns being verifiable for admissibility
US5761146A (en) * 1995-12-28 1998-06-02 Samsung Electronics Co., Ltd. Data in/out channel control circuit of semiconductor memory device having multi-bank structure
US5771199A (en) * 1995-12-29 1998-06-23 Samsung Electronics Co., Ltd. Integrated circuit memory devices having improved dual memory bank control capability and methods of operating same
US5802006A (en) * 1996-02-21 1998-09-01 Nec Corporation Semiconductor memory of multiple-bank structure having block write function
US5818785A (en) * 1995-12-20 1998-10-06 Kabushiki Kaisha Toshiba Semiconductor memory device having a plurality of banks
US5828899A (en) * 1996-01-04 1998-10-27 Compaq Computer Corporation System for peripheral devices recursively generating unique addresses based on the number of devices connected dependent upon the relative position to the port
US5835935A (en) * 1995-09-13 1998-11-10 Lexar Media, Inc. Method of and architecture for controlling system data with automatic wear leveling in a semiconductor non-volatile mass storage memory
US5859809A (en) * 1996-12-31 1999-01-12 Hyundai Electronics Industries Co., Ltd. Semiconductor device of daisy chain structure having independent refresh apparatus
US5872994A (en) * 1995-11-10 1999-02-16 Nec Corporation Flash memory incorporating microcomputer having on-board writing function
US5937425A (en) * 1997-10-16 1999-08-10 M-Systems Flash Disk Pioneers Ltd. Flash file system optimized for page-mode flash technologies
US5941974A (en) * 1996-11-29 1999-08-24 Motorola, Inc. Serial interface with register selection which uses clock counting, chip select pulsing, and no address bits
US5959930A (en) * 1997-08-22 1999-09-28 Mitsubishi Denki Kabushiki Kaisha Multi-bank synchronous semiconductor memory device
US5995417A (en) * 1998-10-20 1999-11-30 Advanced Micro Devices, Inc. Scheme for page erase and erase verify in a non-volatile memory array
US6000006A (en) * 1997-08-25 1999-12-07 Bit Microsystems, Inc. Unified re-map and cache-index table with dual write-counters for wear-leveling of non-volatile flash RAM mass storage
US6002638A (en) * 1998-01-20 1999-12-14 Microchip Technology Incorporated Memory device having a switchable clock output and method therefor
US6085290A (en) * 1998-03-10 2000-07-04 Nexabit Networks, Llc Method of and apparatus for validating data read out of a multi port internally cached dynamic random access memory (AMPIC DRAM)
US6091660A (en) * 1997-10-02 2000-07-18 Hitachi, Ltd. Semiconductor integrated circuit device
US6107658A (en) * 1997-02-27 2000-08-22 Kabushiki Kaisha Toshiba Non-volatile semiconductor memory device
US6144576A (en) * 1998-08-19 2000-11-07 Intel Corporation Method and apparatus for implementing a serial memory architecture
US6148364A (en) * 1997-12-30 2000-11-14 Netlogic Microsystems, Inc. Method and apparatus for cascading content addressable memory devices
US6178135B1 (en) * 1998-12-28 2001-01-23 Samsung Electronics Co., Ltd. Multi-bank memory devices having bank selection switches therein that enable efficient sense amplifier utilization
US20010007119A1 (en) * 1993-03-11 2001-07-05 Kunihiro Katayama File memory device and information processing apparatus using the same
US6304921B1 (en) * 1998-12-07 2001-10-16 Motorola Inc. System for serial peripheral interface with embedded addressing circuit for providing portion of an address for peripheral devices
US6317352B1 (en) * 2000-09-18 2001-11-13 Intel Corporation Apparatus for implementing a buffered daisy chain connection between a memory controller and memory modules
US6317350B1 (en) * 2000-06-16 2001-11-13 Netlogic Microsystems, Inc. Hierarchical depth cascading of content addressable memory devices
US6438064B2 (en) * 1998-10-30 2002-08-20 Mitsubishi Denki Kabushiki Kaisha Semiconductor memory device capable of efficient memory cell select operation with reduced element count
US6442098B1 (en) * 2000-02-08 2002-08-27 Alliance Semiconductor High performance multi-bank compact synchronous DRAM architecture
US20020188781A1 (en) * 2001-06-06 2002-12-12 Daniel Schoch Apparatus and methods for initializing integrated circuit addresses
US6535948B1 (en) * 2000-05-31 2003-03-18 Agere Systems Inc. Serial interface unit
US6584303B1 (en) * 1997-08-20 2003-06-24 Nokia Corporation Method and apparatus for automatically identifying a function module in a modular transceiver system
US6594183B1 (en) * 1991-09-13 2003-07-15 Sandisk Corporation Wear leveling techniques for flash EEPROM systems
US6601199B1 (en) * 1998-10-28 2003-07-29 Kabushiki Kaisha Toshiba Memory-embedded LSI
US6611466B2 (en) * 2001-07-02 2003-08-26 Samsung Electronics Co., Ltd. Semiconductor memory device capable of adjusting the number of banks and method for adjusting the number of banks
US6658582B1 (en) * 1997-08-26 2003-12-02 Samsung Electronics Co., Ltd. Serial interface circuits having improved data transmitting and receiving capability
US20040001380A1 (en) * 2002-06-28 2004-01-01 Oswald Becca Method and apparatus for interconnecting content addressable memory devices
US6680904B1 (en) * 1999-12-27 2004-01-20 Orckit Communications Ltd. Bi-directional chaining of network access ports
US20040019736A1 (en) * 2002-07-23 2004-01-29 Dug-Soo Kim Portable flash memory with extended memory capacity
US20040024960A1 (en) * 2002-07-31 2004-02-05 Lawrence King CAM diamond cascade architecture
US20040039854A1 (en) * 1998-03-02 2004-02-26 Lexar Media, Inc. Flash memory card with enhanced operating mode detection and user-friendly interfacing system
US6715044B2 (en) * 1991-07-26 2004-03-30 Sandisk Corporation Device and method for controlling solid-state memory system
US6732221B2 (en) * 2001-06-01 2004-05-04 M-Systems Flash Disk Pioneers Ltd Wear leveling of static areas in flash memory
US6754807B1 (en) * 2000-08-31 2004-06-22 Stmicroelectronics, Inc. System and method for managing vertical dependencies in a digital signal processor
US6763426B1 (en) * 2001-12-27 2004-07-13 Cypress Semiconductor Corporation Cascadable content addressable memory (CAM) device and architecture
US20040199721A1 (en) * 2003-03-12 2004-10-07 Power Data Communication Co., Ltd. Multi-transmission interface memory card
US6807103B2 (en) * 2000-11-15 2004-10-19 Stmicroelectronics S.A. Page-erasable flash memory
US6816933B1 (en) * 2000-05-17 2004-11-09 Silicon Laboratories, Inc. Serial device daisy chaining method and apparatus
US20040230738A1 (en) * 2003-01-09 2004-11-18 Samsung Electronics Co., Ltd. Apparatus and method for controlling execute-in-place (XIP) in serial flash memory, and flash memory chip using the same
US6853557B1 (en) * 2000-09-20 2005-02-08 Rambus, Inc. Multi-channel memory architecture
US6853573B2 (en) * 2002-09-02 2005-02-08 Samsung Electronics Co., Ltd. Non-volatile semiconductor memory device for connecting to serial advanced technology attachment cable
US20050120163A1 (en) * 2003-12-02 2005-06-02 Super Talent Electronics Inc. Serial Interface to Flash-Memory Chip Using PCI-Express-Like Packets and Packed Data for Partial-Page Writes
US20050144361A1 (en) * 2003-12-30 2005-06-30 Gonzalez Carlos J. Adaptive mode switching of flash memory address mapping based on host usage characteristics
US20050160218A1 (en) * 2004-01-20 2005-07-21 Sun-Teck See Highly integrated mass storage device with an intelligent flash controller
US20050166006A1 (en) * 2003-05-13 2005-07-28 Advanced Micro Devices, Inc. System including a host connected serially in a chain to one or more memory modules that include a cache
US6928501B2 (en) * 2001-10-15 2005-08-09 Silicon Laboratories, Inc. Serial device daisy chaining method and apparatus
US6950325B1 (en) * 2004-10-07 2005-09-27 Winbond Electronics Corporation Cascade-connected ROM
US20050213421A1 (en) * 2002-11-28 2005-09-29 Salvatore Polizzi Non-volatile memory device architecture, for instance a flash kind, having a serial communication interface
US6967874B2 (en) * 2003-06-30 2005-11-22 Kabushiki Kaisha Toshiba Non-volatile semiconductor memory device and electric device with the same
US20060050594A1 (en) * 2004-09-03 2006-03-09 Park Jin S Flash memory device and method of erasing flash memory cell thereof
US7296112B1 (en) * 2002-12-10 2007-11-13 Greenfield Networks, Inc. High bandwidth memory management using multi-bank DRAM devices

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3178909B2 (en) * 1992-01-10 2001-06-25 株式会社東芝 Semiconductor memory device
US6988154B2 (en) 2000-03-10 2006-01-17 Arc International Memory interface and method of interfacing between functional entities
JP3992960B2 (en) * 2000-10-26 2007-10-17 松下電器産業株式会社 Recording apparatus and program
US7779212B2 (en) * 2003-10-17 2010-08-17 Micron Technology, Inc. Method and apparatus for sending data from multiple sources over a communications bus
JP2007519119A (en) * 2004-01-20 2007-07-12 トレック・2000・インターナショナル・リミテッド Portable data storage device using multiple memory devices
CN1655277A (en) * 2004-02-09 2005-08-17 联想(北京)有限公司 Multifunctional data storage device and method thereof
US8375146B2 (en) * 2004-08-09 2013-02-12 SanDisk Technologies, Inc. Ring bus structure and its use in flash memory systems

Patent Citations (84)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4174536A (en) * 1977-01-21 1979-11-13 Massachusetts Institute Of Technology Digital communications controller with firmware control
US4733376A (en) * 1984-10-17 1988-03-22 Fujitsu Limited Semiconductor memory device having serial data input circuit and serial data output circuit
US4796231A (en) * 1985-01-22 1989-01-03 Texas Instruments Incorporated Serial accessed semiconductor memory with reconfigurable shift registers
US5136292A (en) * 1989-03-15 1992-08-04 Oki Electric Industry Co., Ltd. Serial data receiving circuit for serial to parallel conversion
US5126808A (en) * 1989-10-23 1992-06-30 Advanced Micro Devices, Inc. Flash EEPROM array with paged erase architecture
US5175819A (en) * 1990-03-28 1992-12-29 Integrated Device Technology, Inc. Cascadable parallel to serial converter using tap shift registers and data shift registers while receiving input data from FIFO buffer
US5243703A (en) * 1990-04-18 1993-09-07 Rambus, Inc. Apparatus for synchronously generating clock signals in a data processing system
US6715044B2 (en) * 1991-07-26 2004-03-30 Sandisk Corporation Device and method for controlling solid-state memory system
US6594183B1 (en) * 1991-09-13 2003-07-15 Sandisk Corporation Wear leveling techniques for flash EEPROM systems
US6850443B2 (en) * 1991-09-13 2005-02-01 Sandisk Corporation Wear leveling techniques for flash EEPROM systems
US20050114589A1 (en) * 1991-09-13 2005-05-26 Lofgren Karl M. Wear leveling techniques for flash EEPROM systems
US5280539A (en) * 1992-01-15 1994-01-18 Samsung Electronics Co., Ltd. Synchronous circuit for serial input signal
US5440694A (en) * 1992-03-26 1995-08-08 Nec Corporation Interface circuit for allowing receiving serial data input after receiving serial input suspension signal
US5530828A (en) * 1992-06-22 1996-06-25 Hitachi, Ltd. Semiconductor storage device including a controller for continuously writing data to and erasing data from a plurality of flash memories
US5473563A (en) * 1993-01-13 1995-12-05 Samsung Electronics Co., Ltd. Nonvolatile semiconductor memory
US20010007119A1 (en) * 1993-03-11 2001-07-05 Kunihiro Katayama File memory device and information processing apparatus using the same
US5473577A (en) * 1993-03-20 1995-12-05 Hitachi, Ltd. Serial memory
US5365484A (en) * 1993-08-23 1994-11-15 Advanced Micro Devices, Inc. Independent array grounds for flash EEPROM array with paged erase architechture
US5721840A (en) * 1993-09-20 1998-02-24 Olympus Optical Co., Ltd. Information processing apparatus incorporating automatic SCSI ID generation
US5602780A (en) * 1993-10-20 1997-02-11 Texas Instruments Incorporated Serial to parallel and parallel to serial architecture for a RAM based FIFO memory
US5452259A (en) * 1993-11-15 1995-09-19 Micron Technology Inc. Multiport memory with pipelined serial input
US5404460A (en) * 1994-01-28 1995-04-04 Vlsi Technology, Inc. Method for configuring multiple identical serial I/O devices to unique addresses through a serial bus
US5596724A (en) * 1994-02-04 1997-01-21 Advanced Micro Devices Input/output data port with a parallel and serial interface
US5740379A (en) * 1994-08-19 1998-04-14 Siemens Aktiengesellschaft Method for generating unique addresses for electrical devices from input bit patterns being verifiable for admissibility
US5473566A (en) * 1994-09-12 1995-12-05 Cirrus Logic, Inc. Memory architecture and devices, systems and methods utilizing the same
US5671178A (en) * 1995-02-04 1997-09-23 Samsung Electronics Co., Ltd. Erase verifying circuit for a nonvolatile semiconductor memory with column redundancy
US5636342A (en) * 1995-02-17 1997-06-03 Dell Usa, L.P. Systems and method for assigning unique addresses to agents on a system management bus
US5568423A (en) * 1995-04-14 1996-10-22 Unisys Corporation Flash memory wear leveling system providing immediate direct access to microprocessor
US5835935A (en) * 1995-09-13 1998-11-10 Lexar Media, Inc. Method of and architecture for controlling system data with automatic wear leveling in a semiconductor non-volatile mass storage memory
US5872994A (en) * 1995-11-10 1999-02-16 Nec Corporation Flash memory incorporating microcomputer having on-board writing function
US5818785A (en) * 1995-12-20 1998-10-06 Kabushiki Kaisha Toshiba Semiconductor memory device having a plurality of banks
US5761146A (en) * 1995-12-28 1998-06-02 Samsung Electronics Co., Ltd. Data in/out channel control circuit of semiconductor memory device having multi-bank structure
US5771199A (en) * 1995-12-29 1998-06-23 Samsung Electronics Co., Ltd. Integrated circuit memory devices having improved dual memory bank control capability and methods of operating same
US5828899A (en) * 1996-01-04 1998-10-27 Compaq Computer Corporation System for peripheral devices recursively generating unique addresses based on the number of devices connected dependent upon the relative position to the port
US5802006A (en) * 1996-02-21 1998-09-01 Nec Corporation Semiconductor memory of multiple-bank structure having block write function
US5941974A (en) * 1996-11-29 1999-08-24 Motorola, Inc. Serial interface with register selection which uses clock counting, chip select pulsing, and no address bits
US5859809A (en) * 1996-12-31 1999-01-12 Hyundai Electronics Industries Co., Ltd. Semiconductor device of daisy chain structure having independent refresh apparatus
US6107658A (en) * 1997-02-27 2000-08-22 Kabushiki Kaisha Toshiba Non-volatile semiconductor memory device
US6584303B1 (en) * 1997-08-20 2003-06-24 Nokia Corporation Method and apparatus for automatically identifying a function module in a modular transceiver system
US5959930A (en) * 1997-08-22 1999-09-28 Mitsubishi Denki Kabushiki Kaisha Multi-bank synchronous semiconductor memory device
US6000006A (en) * 1997-08-25 1999-12-07 Bit Microsystems, Inc. Unified re-map and cache-index table with dual write-counters for wear-leveling of non-volatile flash RAM mass storage
US6658582B1 (en) * 1997-08-26 2003-12-02 Samsung Electronics Co., Ltd. Serial interface circuits having improved data transmitting and receiving capability
US6091660A (en) * 1997-10-02 2000-07-18 Hitachi, Ltd. Semiconductor integrated circuit device
US5937425A (en) * 1997-10-16 1999-08-10 M-Systems Flash Disk Pioneers Ltd. Flash file system optimized for page-mode flash technologies
US6148364A (en) * 1997-12-30 2000-11-14 Netlogic Microsystems, Inc. Method and apparatus for cascading content addressable memory devices
US6002638A (en) * 1998-01-20 1999-12-14 Microchip Technology Incorporated Memory device having a switchable clock output and method therefor
US20040039854A1 (en) * 1998-03-02 2004-02-26 Lexar Media, Inc. Flash memory card with enhanced operating mode detection and user-friendly interfacing system
US6085290A (en) * 1998-03-10 2000-07-04 Nexabit Networks, Llc Method of and apparatus for validating data read out of a multi port internally cached dynamic random access memory (AMPIC DRAM)
US6144576A (en) * 1998-08-19 2000-11-07 Intel Corporation Method and apparatus for implementing a serial memory architecture
US5995417A (en) * 1998-10-20 1999-11-30 Advanced Micro Devices, Inc. Scheme for page erase and erase verify in a non-volatile memory array
US6601199B1 (en) * 1998-10-28 2003-07-29 Kabushiki Kaisha Toshiba Memory-embedded LSI
US6438064B2 (en) * 1998-10-30 2002-08-20 Mitsubishi Denki Kabushiki Kaisha Semiconductor memory device capable of efficient memory cell select operation with reduced element count
US6304921B1 (en) * 1998-12-07 2001-10-16 Motorola Inc. System for serial peripheral interface with embedded addressing circuit for providing portion of an address for peripheral devices
US6178135B1 (en) * 1998-12-28 2001-01-23 Samsung Electronics Co., Ltd. Multi-bank memory devices having bank selection switches therein that enable efficient sense amplifier utilization
US6680904B1 (en) * 1999-12-27 2004-01-20 Orckit Communications Ltd. Bi-directional chaining of network access ports
US6442098B1 (en) * 2000-02-08 2002-08-27 Alliance Semiconductor High performance multi-bank compact synchronous DRAM architecture
US6944697B2 (en) * 2000-05-17 2005-09-13 Silicon Laboratories, Inc. Serial device daisy chaining method and apparatus
US6816933B1 (en) * 2000-05-17 2004-11-09 Silicon Laboratories, Inc. Serial device daisy chaining method and apparatus
US6535948B1 (en) * 2000-05-31 2003-03-18 Agere Systems Inc. Serial interface unit
US6317350B1 (en) * 2000-06-16 2001-11-13 Netlogic Microsystems, Inc. Hierarchical depth cascading of content addressable memory devices
US6754807B1 (en) * 2000-08-31 2004-06-22 Stmicroelectronics, Inc. System and method for managing vertical dependencies in a digital signal processor
US6317352B1 (en) * 2000-09-18 2001-11-13 Intel Corporation Apparatus for implementing a buffered daisy chain connection between a memory controller and memory modules
US6853557B1 (en) * 2000-09-20 2005-02-08 Rambus, Inc. Multi-channel memory architecture
US6807103B2 (en) * 2000-11-15 2004-10-19 Stmicroelectronics S.A. Page-erasable flash memory
US6732221B2 (en) * 2001-06-01 2004-05-04 M-Systems Flash Disk Pioneers Ltd Wear leveling of static areas in flash memory
US20020188781A1 (en) * 2001-06-06 2002-12-12 Daniel Schoch Apparatus and methods for initializing integrated circuit addresses
US6611466B2 (en) * 2001-07-02 2003-08-26 Samsung Electronics Co., Ltd. Semiconductor memory device capable of adjusting the number of banks and method for adjusting the number of banks
US6928501B2 (en) * 2001-10-15 2005-08-09 Silicon Laboratories, Inc. Serial device daisy chaining method and apparatus
US6763426B1 (en) * 2001-12-27 2004-07-13 Cypress Semiconductor Corporation Cascadable content addressable memory (CAM) device and architecture
US20040001380A1 (en) * 2002-06-28 2004-01-01 Oswald Becca Method and apparatus for interconnecting content addressable memory devices
US20040019736A1 (en) * 2002-07-23 2004-01-29 Dug-Soo Kim Portable flash memory with extended memory capacity
US20040024960A1 (en) * 2002-07-31 2004-02-05 Lawrence King CAM diamond cascade architecture
US6853573B2 (en) * 2002-09-02 2005-02-08 Samsung Electronics Co., Ltd. Non-volatile semiconductor memory device for connecting to serial advanced technology attachment cable
US20050213421A1 (en) * 2002-11-28 2005-09-29 Salvatore Polizzi Non-volatile memory device architecture, for instance a flash kind, having a serial communication interface
US7296112B1 (en) * 2002-12-10 2007-11-13 Greenfield Networks, Inc. High bandwidth memory management using multi-bank DRAM devices
US20040230738A1 (en) * 2003-01-09 2004-11-18 Samsung Electronics Co., Ltd. Apparatus and method for controlling execute-in-place (XIP) in serial flash memory, and flash memory chip using the same
US20040199721A1 (en) * 2003-03-12 2004-10-07 Power Data Communication Co., Ltd. Multi-transmission interface memory card
US20050166006A1 (en) * 2003-05-13 2005-07-28 Advanced Micro Devices, Inc. System including a host connected serially in a chain to one or more memory modules that include a cache
US6967874B2 (en) * 2003-06-30 2005-11-22 Kabushiki Kaisha Toshiba Non-volatile semiconductor memory device and electric device with the same
US20050120163A1 (en) * 2003-12-02 2005-06-02 Super Talent Electronics Inc. Serial Interface to Flash-Memory Chip Using PCI-Express-Like Packets and Packed Data for Partial-Page Writes
US20050144361A1 (en) * 2003-12-30 2005-06-30 Gonzalez Carlos J. Adaptive mode switching of flash memory address mapping based on host usage characteristics
US20050160218A1 (en) * 2004-01-20 2005-07-21 Sun-Teck See Highly integrated mass storage device with an intelligent flash controller
US20060050594A1 (en) * 2004-09-03 2006-03-09 Park Jin S Flash memory device and method of erasing flash memory cell thereof
US6950325B1 (en) * 2004-10-07 2005-09-27 Winbond Electronics Corporation Cascade-connected ROM

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090268521A1 (en) * 2008-04-28 2009-10-29 Koki Ueno Non-volatile semiconductor memory device
US8081512B2 (en) * 2008-04-28 2011-12-20 Kabushiki Kaisha Toshiba Non-volatile semiconductor memory device
US8310873B2 (en) 2008-04-28 2012-11-13 Kabushiki Kaisha Toshiba Non-volatile semiconductor memory device
US9501437B2 (en) 2012-11-15 2016-11-22 Empire Technology Development Llc Scalable storage system having multiple storage channels
US9292210B1 (en) 2014-08-29 2016-03-22 International Business Machines Corporation Thermally sensitive wear leveling for a flash memory device that includes a plurality of flash memory modules

Also Published As

Publication number Publication date
CN102063931B (en) 2014-07-30
CN101410906B (en) 2015-04-29
WO2007112555A1 (en) 2007-10-11
DE602007010439D1 (en) 2010-12-23
EP2002442A4 (en) 2009-05-06
TWI456582B (en) 2014-10-11
TW201445576A (en) 2014-12-01
US7802064B2 (en) 2010-09-21
KR101194965B1 (en) 2012-10-25
ES2498096T3 (en) 2014-09-24
EP2002442A1 (en) 2008-12-17
KR20090017494A (en) 2009-02-18
CN102063931A (en) 2011-05-18
US20070233939A1 (en) 2007-10-04
EP2242058A3 (en) 2011-05-25
EP2242058A2 (en) 2010-10-20
JP5214587B2 (en) 2013-06-19
JP2009531747A (en) 2009-09-03
EP2002442B1 (en) 2010-11-10
CN101410906A (en) 2009-04-15
TW200805396A (en) 2008-01-16
EP2242058B1 (en) 2014-07-16
ATE488009T1 (en) 2010-11-15

Similar Documents

Publication Publication Date Title
US7802064B2 (en) Flash memory system control scheme
US9330765B2 (en) Non-volatile memory device having configurable page size
US10303370B2 (en) Flash memory system
US8120990B2 (en) Flexible memory operations in NAND flash devices
JP5513289B2 (en) Nonvolatile memory device in which program inhibit voltage changes during programming and programming method thereof
US9281068B2 (en) Nonvolatile memory and related reprogramming method
US8693247B2 (en) Non-volatile memory device and method for programming the device, and memory system

Legal Events

Date Code Title Description
AS Assignment

Owner name: MOSAID TECHNOLOGIES INCORPORATED, CANADA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KIM, JIN-KI;REEL/FRAME:024829/0671

Effective date: 20070327

Owner name: MOSAID TECHNOLOGIES INCORPORATED, CANADA

Free format text: CHANGE OF ADDRESS;ASSIGNOR:MOSAID TECHNOLOGIES INCORPORATED;REEL/FRAME:024829/0862

Effective date: 20090209

AS Assignment

Owner name: ROYAL BANK OF CANADA, CANADA

Free format text: U.S. INTELLECTUAL PROPERTY SECURITY AGREEMENT (FOR NON-U.S. GRANTORS) - SHORT FORM;ASSIGNORS:658276 N.B. LTD.;658868 N.B. INC.;MOSAID TECHNOLOGIES INCORPORATED;REEL/FRAME:027512/0196

Effective date: 20111223

AS Assignment

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.,

Free format text: CHANGE OF NAME;ASSIGNOR:MOSAID TECHNOLOGIES INCORPORATED;REEL/FRAME:032439/0638

Effective date: 20140101

AS Assignment

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.,

Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:ROYAL BANK OF CANADA;REEL/FRAME:033484/0344

Effective date: 20140611

Owner name: CONVERSANT IP N.B. 868 INC., CANADA

Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:ROYAL BANK OF CANADA;REEL/FRAME:033484/0344

Effective date: 20140611

Owner name: CONVERSANT IP N.B. 276 INC., CANADA

Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:ROYAL BANK OF CANADA;REEL/FRAME:033484/0344

Effective date: 20140611

AS Assignment

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC., CANADA

Free format text: CHANGE OF ADDRESS;ASSIGNOR:CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.;REEL/FRAME:033678/0096

Effective date: 20140820

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.,

Free format text: CHANGE OF ADDRESS;ASSIGNOR:CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.;REEL/FRAME:033678/0096

Effective date: 20140820

AS Assignment

Owner name: ROYAL BANK OF CANADA, AS LENDER, CANADA

Free format text: U.S. PATENT SECURITY AGREEMENT (FOR NON-U.S. GRANTORS);ASSIGNOR:CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.;REEL/FRAME:033706/0367

Effective date: 20140611

Owner name: CPPIB CREDIT INVESTMENTS INC., AS LENDER, CANADA

Free format text: U.S. PATENT SECURITY AGREEMENT (FOR NON-U.S. GRANTORS);ASSIGNOR:CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.;REEL/FRAME:033706/0367

Effective date: 20140611

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE

AS Assignment

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC., CANADA

Free format text: RELEASE OF U.S. PATENT AGREEMENT (FOR NON-U.S. GRANTORS);ASSIGNOR:ROYAL BANK OF CANADA, AS LENDER;REEL/FRAME:047645/0424

Effective date: 20180731

Owner name: CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC.,

Free format text: RELEASE OF U.S. PATENT AGREEMENT (FOR NON-U.S. GRANTORS);ASSIGNOR:ROYAL BANK OF CANADA, AS LENDER;REEL/FRAME:047645/0424

Effective date: 20180731