Device and method for managing a flash memory

Information

  • Patent Grant
  • 8819385
  • Patent Number
    8,819,385
  • Date Filed
    Monday, July 27, 2009
    16 years ago
  • Date Issued
    Tuesday, August 26, 2014
    10 years ago
Abstract
A method for accessing a flash memory, the method includes: receiving a read request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells; accessing multiple mapping data structures of different granularity to obtain the physical address of the set of flash memory cells; wherein during at least one point in time at least one mapping data structure is stored in an erase block and wherein the erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner; and reading a content of the set of flash memory cells.
Description
FIELD OF THE INVENTION

The invention relates to field of non volatile memories and especially to managing a flash memory.


BACKGROUND OF THE INVENTION

Due to inaccuracies during the programming procedure and charge loss due to time and temperature (also known as retention), the measured levels during a Read operation suffers from detection errors. The small dimensions of the Flash cells result in cells that can store very small amounts of charge, enhancing the effects of inaccuracies due to programming and retention. Thus, new single level cells (SLC) and multi level cells (MLC) devices have significantly increased bit error rate (BER), decreasing the reliability of the device.


BER is a parameter that a flash memory device manufacturer commits to vis a vis its customers, expressing the maximum proportion of wrongly read bits (wrongly read bits/total number of bits) that users of the flash memory device need to expect at any time during the stipulated lifetime of the flash memory device e.g. 10 years.


MLC means that the physical levels in the cell are, to an acceptable level of certainty, statistically partitionable into multiple distinguishable regions, plus a region corresponding to zero, such that digital values each comprising multiple bits can be represented by the cell. In contrast, in single-level cells, the physical levels in the cell are assumed to be statistically partitionable into only two regions, one corresponding to zero and one other, non-zero region, such that only one bit can be represented by a single-level cell.


Flash devices are organized into (physical) pages. Each page contains a section allocated for data (512 bytes-8 Kbytes) and a small amount of bytes (16-32 bytes for every 512 data bytes) containing redundancy and back pointers. The redundancy bytes are used to store error correcting information, for correcting errors which may have occurred during the page Read. Each Read and Program operation is performed on an entire page. A number of pages are grouped together to form an Erase Block (EB). A page cannot be erased unless the entire EB which contains it is erased.


An important measure of a Flash device quality is the number of times (Np) it may be reprogrammed and the period that it can store information (usually 10 years) before irrecoverable errors occur.


The higher the number of program-erase cycles, the higher the BER. Thus, today's MLC with 2 bits per cell devices can perform around Np=10,000 cycles and 10 years retention before the allocation of 16 bytes of redundancy per 512 bytes of data bytes becomes insufficient to correct errors.


SLC devices usually perform better but obtain a much lower density and hence their prices are much higher. Note that following Np program-erase cycles the device is still operational but the BER is higher.


One factor that increases the number of program-erase cycles is the fact that an entire block must be erased at once. For example, when a single page of a programmed block is to be modified, in many cases (e.g. SD cards and USB drives), the block is copied to an erased block and the relevant page is replaced in the process. Thus, a single page change required the programming of an entire block and an erasure of a block. This process is usually referred to as a read modify write operation.


SUMMARY OF THE INVENTION

A method for accessing a flash memory, the method includes: (i) receiving a read request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells; (ii) accessing multiple mapping data structures of different granularity to obtain the physical address of the set of flash memory cells; wherein during at least one point in time at least one mapping data structure is stored in an erase block and wherein the erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner; and (iii) accessing the set of flash memory cells.


A method for writing to a flash memory, the method includes: receiving a write request to write content, wherein the write request is associated with a logical address; writing the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to; and updating at least one mapping data structure out of multiple mapping data structures to reflect the writing to the new set of flash memory cells; wherein the multiple mapping data structures are of different granularity; wherein during at least one point in time at least one mapping data structure is stored in an erase block and wherein the erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner.


A mapping data structure of a certain granularity can store only information associated with the certain granularity.


The logic address of the set of flash memory cells includes a logical erase block address and a logical inter erase block address. The method can include accessing a first mapping data structure that maps logical erase block addresses to physical erase block addresses and accessing a second mapping data structure that maps logical inter erase block addresses to physical inter erase block addresses.


The second data can be stored in the flash memory.


The method can include generating the multiple mapping data structures; wherein the second mapping data structure is written to the flash memory after a predefined number of physical pages of the erase block were written.


The second mapping data structure maps logical addresses of pages to physical addresses of pages; wherein evenly sized logical pages are stored in evenly sized physical pages.


The first mapping data structure can be stored, during at least one period, in memory unit that differs from the flash memory.


The method can include accessing a first mapping data structure, a second data structure and a third data structure; wherein the first mapping data structure maps logical erase block addresses to physical erase block addresses, the second mapping data structure maps logical page addresses to indexes into the third mapping data structure; wherein the third data structure maps the indexes to locations of sets of flash memory cells; wherein at least one erasure block includes two sets of flash memory cells that differ from each other by their size.


The at least two sets of memory cells can store information that is encoded by a variable encoding process.


The method can include fetching a mapping data structure from a memory unit that differs from the flash memory and storing the fetched mapping data structure in the flash memory.


A system having flash memory management capabilities, the system includes a management module that is coupled to a flash memory, another memory unit, and an interface; wherein the interface receives a read request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells; wherein the flash memory includes multiple erase blocks; wherein the management module is adapted to: access multiple mapping data structures of different granularity to obtain the physical address of the set of flash memory cells; wherein at least one mapping data structure is stored in an erase block and wherein the erase block includes multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner; and access the set of flash memory cells.


A system having flash memory management capabilities, the system includes a management module that is coupled to a flash memory, another memory unit, and an interface; wherein the interface receives a write request to write content, wherein the write request is associated with a logical address; wherein the flash memory comprises multiple erase blocks. The management module is adapted to: write the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to; and update at least one mapping data structure out of multiple mapping data structures to reflect the writing to the new set of flash memory cells; wherein the multiple mapping data structures are of different granularity; wherein during at least one point in time at least one mapping data structure is stored in an erase block and wherein the erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner.


A mapping data structure of a certain granularity can store only information associated with the certain granularity.


The logic address of the set of flash memory cells can include a logical erase block address a logical inter erase block address. The management module can access a first mapping data structure that maps logical erase block addresses to physical erase block addresses and access a second mapping data structure that maps logical inter erase block addresses to physical inter erase block addresses.


During at least one point in time the second data can be stored in the flash memory.


The management module can generate the multiple mapping data structures; wherein the system writes the second mapping data to the flash memory after a predefined number of physical pages of the erase block were written.


The second mapping data structure can map logical addresses of pages to physical addresses of pages; wherein evenly sized logical pages are stored in evenly sized physical pages.


The first mapping data structure can be stored, during at least one period, in the other memory unit.


The management module can access a first mapping data structure, a second data structure and a third data structure; wherein the first mapping data structure maps logical erase block addresses to physical erase block addresses, the second mapping data structure maps logical page addresses to indexes into the third mapping data structure; wherein the third data structure maps the indexes to locations of sets of flash memory cells; wherein at least one erasure block includes two sets of flash memory cells that differ from each other by their size.


The at least two sets of memory cells can store information that is encoded by a variable encoding process.


The management module can fetch a mapping data structure from the other memory unit and can store the fetched mapping data structure in the flash memory.





BRIEF DESCRIPTION OF THE DRAWINGS

Further details, aspects, and embodiments of the invention will be described, by way of example only, with reference to the drawings.



FIG. 1 illustrates a system according to an embodiment of the invention;



FIG. 2 illustrates a system according to an embodiment of the invention;



FIG. 3 illustrates a method according to an embodiment of the invention; and



FIG. 4 illustrates a method according to an embodiment of the invention.





DETAILED DESCRIPTION OF THE DRAWINGS

The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings.


It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.


In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.


Because the apparatus implementing the present invention is, for the most part, composed of electronic components and circuits known to those skilled in the art, circuit details will not be explained in any greater extent than that considered necessary as illustrated above, for the understanding and appreciation of the underlying concepts of the present invention and in order not to obfuscate or distract from the teachings of the present invention.


In the following specification, the invention will be described with reference to specific examples of embodiments of the invention. It will, however, be evident that various modifications and changes may be made therein without departing from the broader spirit and scope of the invention as set forth in the appended claims.


Furthermore, those skilled in the art will recognize that boundaries between the functionality of the above described operations are merely illustrative. The functionality of multiple operations may be combined into a single operation, and/or the functionality of a single operation may be distributed in additional operations. Moreover, alternative embodiments may include multiple instances of a particular operation, and the order of operations may be altered in various other embodiments.


The following terms may be construed either in accordance with any definition thereof appearing in the prior art literature or in accordance with the specification, or as follows:


Cell: A component of flash memory that stores one bit of information (in single-level cell devices) or n bits of information (in a multi-level device having 2n levels). Typically, each cell includes a floating-gate transistor. The variable n may or may not be an integer.


Flash memory: A non volatile memory (NVM) that includes cells that are erased block by block, each block typically comprising more than one page, but are written into and read from, page by page. Includes NOR-type flash memory, NAND-type flash memory, and PRAM, e.g. Samsung PRAM, inter alia, and flash memory devices with any suitable number of levels per cell, such as but not limited to two four or eight.


Logical page: a portion of typically sequential data, whose amount is typically less than or equal to a predetermined amount of data defined to be a page full of data, which has typically been defined by a host (data source/destination) or user thereof, as a page, and which is sent by the host to a flash memory device for storage and is subsequently read by the host from the flash memory device.


Physical Page: A portion, typically 512 or 2048 or 4096 bytes in size, of a flash memory e.g. a NAND or NOR flash memory device. Writing and reading is typically performed physical page by physical page, as opposed to erasing which can be performed only erase sector by erase sector. A few bytes, typically 16-32 for every 512 data bytes are associated with each page), for storage of error correction information. A typical block may include 32 512-byte pages or 64 2048-byte pages. Alternatively, a physical page is an ordered set (e.g. sequence or array) of flash memory cells which are all written in simultaneously by each write operation. The set typically includes a predetermined number of typically physically adjacent flash memory cells containing actual data written by the host and subsequently read by the host, as well as, typically error correction information and back pointers used for recognizing the true address of a page.


It has been shown that in order to decrease erase the number of program-erase cycles and in order to decrease BER several physical pages of an erase block should written in a sequential manner. In order to allow an assignment of logical addresses in a random manner—that is not bounded by the sequential writing manner—a mapping of logical to physical addresses is provided. For example, assuming that an erase block include physical pages PP(1)-PP(J) then a sequence of J write requests will result in writing content to the first physical page PP(1), to second physical page PP(2), till the J'th physical page—regardless of the logical addresses associated with the write requests. The sequence of write requests can include read request that do not interfere with the sequential writing to physical pages PP(1)-PP(J). The sequence of write requests usually follows an erasing of the erase block. If more than L write requests are received then more than an erase block is written to. Multiple mapping data structure are generated and maintained in order to facilitate the sequential writing and the random allocation of logical addresses.


One or more mapping data structure can be stored (at one or more point in time) in the flash memory and can be stored (during one or more periods) at another memory. A mapping data structure can be stored in the flash memory before a device is shut down, while the device remains shut down or after the entire erase block is written to.


Different ways to manage a logical to physical table may be implemented, according to different embodiments of the invention. One possibility is mapping logical to physical addresses in a page resolution. This can simplify the mapping scheme but can require a large space. For example, a flash memory of 16 GB with 4 KB long pages includes 4 Million pages. This requires a logical to physical table that include four million entries, each of three bytes long. This amount in 12 MB logical to physical table. Storing this table or even a small fraction of the table in SD/MMC controller is not practical and can result in a very high miss rate. For example—if the available space for storing mapping information us about 128 KB than only about one percent of the logical to physical table can be stored in that available space. It means that for almost each read page request, two pages should read from flash, one for data and one for table.


Therefore, other solutions may be required for system with area limitations. According to an aspect of the invention, an improved solution with respect to RAM size is suggested. Instead of mapping all the logical space into physical space in page resolution, it can be done by generating multiple mapping data structure of different granularity.


A mapping data structure stores information that maps between addresses. It can map between a logical address to a physical address, between a physical address to a semi-physical address, between a semi-physical address and a physical address and the like. A non limiting example of a mapping data structure is a mapping table although other data structures can be provided. Sets of flash memory cells are written in a sequential manner while mapping data structure facilitate the random allocation of logical addresses.



FIG. 1 illustrates system 10 according to an embodiment of the invention.


System 10 includes management module 20 that is connected to flash memory 30, another memory unit 40, and interface 50.


Interface 50 can receive an access request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells. Interface 50 can receive the request from a software or hardware components such as a host, an application, and the like.


Flash memory 30 includes multiple erase blocks such as erase blocks 32(1)-32(K). Each erase block can include multiple pages. For example. FIG. 1 illustrates erase block 32(1) as including multiple physical pages (PPs) such as 34(1)-34(J). Each physical page includes multiple flash memory cells.


Flash memory 30 can include multiple flash memory cell sets. A set of flash memory cells can include one or more flash memory cells. A set of flash memory cells can be a physical page, a portion of a physical page, can include at least one memory page, include multiple physical memory page, and the like.


A physical page can store a representation of an information unit, a fraction of a representation of an information unit, more than a single representation of an information unit and the like. Accordingly—in one case information unit representations are aligned with physical page boundaries (this is referred to as an aligned scenario) but in some cases information unit representations are not aligned with physical page boundaries (this is referred to as the misaligned scenario). The non-aligned scenario can occur, for example, when applying variable rate encoding.


The mapping between logical addresses and physical addresses should take into account the alignment (or misalignment) between information unit representations and physical pages. Accordingly—the aligned scenario can be managed by using two mapping data structures while misaligned scenario can be managed by using three mapping data structures.


Management module 20 can include software components, hardware components or a combination thereof. It can include at least one of the following circuitries or be connected to one or more of the following circuitries without including them: (i) erasing circuitry, (ii) writing circuitry, and (iii) reading circuitry.



FIG. 1 illustrates management module 20 as including microcontroller 22, erasing circuitry 24, writing circuitry 26 and reading circuitry 28.


Interface 50 can receive a read request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells.


Management module 20 receives the read request and in response accesses multiple mapping data structures of different granularity to obtain the physical address of the set of flash memory cells.


At least one mapping data structure is stored in an erase block and wherein the erase block includes multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner.


Management module 20, in response to information obtained from the multiple mapping data structures access the set of flash memory cells and can read the set of flash memory cells.



FIG. 1 illustrates multiple mapping data structures as including first mapping data structure 61 and second mapping data structure 62. FIG. 1 illustrates second mapping data structure 62 as being stored in erase block 32(1) and first mapping data structure 61 as being stored at other memory unit 40. This is not necessarily so. For example, second mapping data structure 62 can be fetched from other memory unit 40.


A mapping data structure (such as first and second mapping data structures 61 and 62) of a certain granularity can store only information associated with the certain granularity. For example—first mapping data structure 61 does not store memory page level information and second mapping data structure 62 does not store erase block level mapping information.


First mapping data structure 61 can maps logical erase block addresses to physical erase block addresses. Second mapping data structure 62 can map logical inter erase block addresses to physical inter erase block addresses.


The logic address of the set of flash memory cells can include a logical erase block address a logical inter erase block address. Management module 40 can access first mapping data structure 61 with the logical erase block address and can access second mapping data structure 62 with the logical inter erase block address.


Management module 40 or another component (now shown) can generate the multiple mapping data structures. System 10 (or one of its components) can write the second mapping data structure 62 to flash memory 30 after a predefined number of physical pages of the erase block were written.


Interface 50 can receive a write request to write content, wherein the write request is associated with a logical address. Management module 20 can write the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to; and to update at least one mapping data structure to reflect the writing to the new set of flash memory cells.


Management module 20 can receive multiple write requests associated with the same logical address. It should update the one or more mapping data structures to point to the last (most updated) physical address that stores information associated with that logical address. This update can be perform in various manners. For example, management module 20 can invalidate all entries of the mapping data structure associated with that same logical address except the last entry of the group of entries.



FIG. 2 illustrates system 11 according to another embodiment of the invention.


System 11 of FIG. 2 stores three mapping data structures 61, 62 and 63 while system 10 of FIG. 1 stores two mapping data structures 61 and 62.


Management module 40 can access first mapping data structure 61, second data structure 62 and third data structure 63.


First mapping data structure 61 maps logical erase block addresses to physical erase block addresses. Second mapping data structure 62 maps logical page addresses to indexes into third mapping data structure 63. Third data structure 63 maps the indexes to locations of sets of flash memory cells. Third data structure 63 is used to manage the misaligned scenario. FIG. 2 illustrates third mapping data structure 63 as being stored at erase block 32(1).


Referring back to FIG. 1, management module 40 can retrieve, in response to the logical address, a block physical address of a target erase block of a flash memory from a first mapping table that stored information that differs from page level information; retrieve, in response to the logical address, a page address from a second mapping table that stored information that differs from block level information; wherein the target erase block stored the second mapping table; and write to a set of cells of the flash memory in response to the page address. The page address can be a start address of the set of flash memory cells.



FIG. 3 illustrates method 300 according to an embodiment of the invention.


Method 300 starts by stage 310 of initialization. This stage can include receiving mapping data structure, generating mapping data structures, erasing one or more erase blocks and the like.


Stage 310 is followed by stage 320 of receiving a read request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells.


Stage 320 is followed by stage 330 of accessing multiple mapping data structures of different granularity to obtain the physical address of the set of flash memory cells. During at least one point in time at least one mapping data structure is stored in an erase block. For example, a second mapping data that stores page level information can be written to an erase block after all the multiple physical pages of the erase block were written to. The multiple physical pages are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner.


Stage 330 can include checking, for an accessed mapping data structure, whether it is stored in the flash memory or in another memory bank. Stage 330 can also include fetching a mapping data structure to the flash memory or vice verse. For example—mapping data structures can be fetched from the flash memory after a device is power up and sent to the flash memory when the device is powered down.


Stage 330 is followed by stage 340 of accessing the set of flash memory cells. Stage 340 includes reading the content of the set of flash memory cells. Stage 340 uses the address of the set of memory cells that was retrieved during stage 330.


A mapping data structure of a certain granularity can store only information associated with the certain granularity.


The logic address of the set of flash memory cells can include a logical erase block address and a logical inter erase block address. In this case stage 340 can include accessing a first mapping data structure that maps logical erase block addresses to physical erase block addresses and accessing a second mapping data structure that maps logical inter erase block addresses to physical inter erase block addresses.


At a certain point in time the second data can be stored in the flash memory.


Method 300 can include one or more stage of method 400 (of FIG. 4) of writing content to sets of flash memory cells. For example, stage 310 can include (or can be followed by) a stage of generating the multiple mapping data structures. The stage of generating can include writing the second mapping data structure to the flash memory after a predefined number of physical pages of the erase block were written.


The second mapping data structure can map logical addresses of pages to physical addresses of pages. Evenly sized logical pages can be stored in evenly sized physical pages.


During at least one period a mapping data structure can be stored in another memory unit that differs from the flash memory. The other memory unit can be a Random Access Memory unit that temporarily stores the mapping data structure. while the


According to another embodiment of the invention logical pages are of different length than physical pages—they can even be of a varying length. In this case there is a need in additional mapping information that can assist in reading pages of different sizes. Accordingly, stage 430 can include accessing a first mapping data structure, a second data structure and a third data structure; wherein the first mapping data structure maps logical erase block addresses to physical erase block addresses, the second mapping data structure maps logical page addresses to indexes into the third mapping data structure. The third data structure maps the indexes to locations of sets of flash memory cells.



FIG. 4 illustrates method 400 for writing to a flash memory, according to an embodiment of the invention.


Method 400 starts by stage 410 of initialization.


Stage 410 is followed by stage 420 of receiving a write request to write content, wherein the write request is associated with a logical address.


Stage 420 is followed by stage 430 of writing the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to. Stage 430 implements a sequential writing scheme—one set of flash memory cells is written after the other.


Stage 430 is followed by stage 440 of updating at least one mapping data structure out of multiple mapping data structures to reflect the writing to the new set of flash memory cells. The multiple mapping data structures are of different granularity; wherein during at least one point in time at least one mapping data structure is stored in an erase block and wherein the erase block includes multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner.


Stage 440 can include generating a mapping data structure. A mapping data structure can be generated, for example, when physical pages of a new erase block are written or when a previous mapping data structure can not serve a new writing sequence.


Conveniently, a mapping data structure of a certain granularity stores only information associated with the certain granularity.


The logic address of the set of flash memory cells can include a logical erase block address and logical inter erase block address. Stage 440 can include updating or generating a first mapping data structure that maps logical erase block addresses to physical erase block addresses and updating or generating a second mapping data structure that maps logical inter erase block addresses to physical inter erase block addresses.


During at least one point in time the second data is stored in the flash memory.


Stage 440 can include generating the multiple mapping data structures; wherein the second mapping data structure is written to the flash memory after a predefined number of physical pages of the erase block were written.


The second mapping data structure maps logical addresses of pages to physical addresses of pages; wherein evenly sized logical pages are stored in evenly sized physical pages.


During at least one period the first mapping data structure is stored in memory unit that differs from the flash memory.


Stage 440 can include updating or generating a first mapping data structure, a second data structure and a third data structure; wherein the first mapping data structure maps logical erase block addresses to physical erase block addresses, the second mapping data structure maps logical page addresses to indexes into the third mapping data structure; wherein the third data structure maps the indexes to locations of sets of flash memory cells; wherein at least one erasure block comprises at least two sets of flash memory cells that differ from each other by their size but store representations of information units of the same size.


The at least two sets of memory cells store information that is encoded by a variable encoding process.


Stage 440 can include writing a mapping data structure to a memory unit that differs from the flash memory and storing the fetched mapping data structure in the flash memory.


Any combination of methods 300 and 400 can be provided. System 10 and 11 can execute either one of these methods or a combination thereof.


The methods and/or processes may be implemented as a computer readable medium having a computer readable code embodied therein, the computer readable code including instructions for the carrying out of at least one of the above disclosed methods and processes.


While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.


Each module can include software, hardware, firmware, middleware or a combination thereof.


The processor and RAM unit can belong to a memory controller unit, but this is not necessarily so.


Thus, it is to be understood that the architectures depicted herein are merely exemplary, and that in fact many other architectures can be implemented which achieve the same functionality. In an abstract, but still definite sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality.


In addition, the invention is not limited to physical devices or units implemented in non-programmable hardware but can also be applied in programmable devices or units able to perform the desired device functions by operating in accordance with suitable program code. Furthermore, the devices may be physically distributed over a number of apparatuses, while functionally operating as a single device.


However, other modifications, variations, and alternatives are also possible. The specifications and drawings are, accordingly, to be regarded in an illustrative rather than in a restrictive sense.


In the claims, the word ‘comprising’ does not exclude the presence of other elements or steps from those listed in a claim. Moreover, the terms “front,” “back,” “top,” “bottom,” “over,” “under” and the like in the description and in the claims, if any, are used for descriptive purposes and not necessarily for describing permanent relative positions. It is understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the invention described herein are, for example, capable of operation in other orientations than those illustrated or otherwise described herein.


Furthermore, the terms “a” or “an,” as used herein, are defined as one or more than one. Also, the use of introductory phrases such as “at least one” and “one or more” in the claims should not be construed to imply that the introduction of another claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an.” The same holds true for the use of definite articles. Unless stated otherwise, terms such as “first” and “second” are used to arbitrarily distinguish between the elements such terms describe. Thus, these terms are not necessarily intended to indicate temporal or other prioritization of such elements. The mere fact that certain measures are recited in mutually different claims does not indicate that a combination of these measures cannot be used to advantage.

Claims
  • 1. A method for accessing a flash memory, the method comprises: receiving a read request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells;accessing multiple mapping data structures of different granularity to obtain the physical address of the set of flash memory cells;wherein the accessing comprises accessing a first mapping data structure that maps logical erase block addresses to physical erase block addresses and accessing a second mapping data structure that comprises mapping information relating to multiple physical or logical pages;wherein the flash memory comprises multiple erase blocks, each erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner;reading a content of the set of flash memory cells;writing to an erase block of the flash memory the second mapping data structure only after all the multiple physical pages of the erase block were written to the erase block;accessing the first mapping data structure, the second mapping data structure and a third mapping data structure;wherein the second mapping data structure maps logical page addresses to indexes into the third mapping data structure;wherein the third mapping data structure maps the indexes to locations of sets of flash memory cells to overcome misalignments between information unit representations stored in the physical pages of the flash memory and physical page boundaries of the flash memory; andwherein at least one erasure block comprises at least two sets of flash memory cells that differ from each other by their size but store representations of information units of the same size.
  • 2. The method according to claim 1 wherein a mapping data structure of a certain granularity stores only information associated with the certain granularity.
  • 3. The method according to claim 1, wherein the second mapping data structure stores mapping information relating to all of the multiple physical pages of the erase block.
  • 4. The method according to claim 1, wherein the set of the flash memory cells is a single flash memory cell.
  • 5. The method according to claim 1 wherein evenly sized logical pages are stored in evenly sized physical pages.
  • 6. The method according to claim 1 wherein during at least one period the first mapping data structure is stored in memory unit that differs from the flash memory; and wherein the second mapping data structure maps logical inter erase block addresses to physical inter erase block addresses.
  • 7. The method according to claim 1 wherein the at least two sets of memory cells store information that is encoded by a variable encoding process resulting in the misalignment between information unit representations stored in the physical pages of the flash memory and physical page boundaries of the flash memory.
  • 8. The method according to claim 1 comprising storing the third mapping data structure in an erase block that further stores the second mapping data structure.
  • 9. The method according to claim 1 comprising receiving a write request to write content, wherein the write request is associated with a logical address; writing the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to; and updating at least one mapping data structure to reflect the writing to the new set of flash memory cells.
  • 10. The method according to claim 9 comprising invalidating all entries except a last entry of a group of entries of a mapping data structure that are associated with the same logic address.
  • 11. A system having flash memory management capabilities, the system comprises a management module that is coupled to a flash memory, another memory unit, and an interface; wherein the interface receives a read request that is associated with a logical address that is mapped to a physical address of a set of flash memory cells; wherein the flash memory comprises multiple erase blocks;wherein the management module is adapted to: access multiple mapping data structures of different granularity to obtain the physical address of the set of flash memory cells; wherein the multiple mapping data structures comprise a first mapping data structure that maps logical erase block addresses to physical erase block addresses and a second mapping data structure that comprises mapping information relating to multiple physical or logical pages;wherein the erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner;access the set of flash memory cells; and write to an erase block of the flash memory the second mapping data structure only after all the multiple physical pages of the erase block were written to the erase block;wherein the management module accesses the first mapping data structure, the second mapping data structure and a third mapping data structure; wherein the second mapping data structure maps logical page addresses to indexes into the third mapping data structure to overcome misalignments between information unit representations stored in the physical pages of the flash memory and physical page boundaries of the flash memory; wherein the third data structure maps the indexes to locations of sets of flash memory cells; wherein at least one erasure block comprises two sets of flash memory cells that differ from each other by their size but store representations of information units of the same size.
  • 12. The system according to claim 11 wherein a mapping data structure of a certain granularity store only information associated with the certain granularity.
  • 13. The system according to claim 11, wherein the second mapping data structure stores mapping information relating to all of the multiple physical pages of the erase block.
  • 14. The system according to claim 11, wherein the flash memory cells are eight bit per cell flash memory cells.
  • 15. The system according to claim 11 wherein evenly sized logical pages are stored in evenly sized physical pages.
  • 16. The system according to claim 11 wherein during at least one period the first mapping data structure is stored in memory unit that differs from the flash memory and wherein the second mapping data structure maps logical inter erase block addresses to physical inter erase block addresses.
  • 17. The system according to claim 11 wherein the at least two sets of memory cells store information that is encoded by a variable encoding process resulting in the misalignment between information unit representations stored in the physical pages of the flash memory and physical page boundaries of the flash memory.
  • 18. The system according to claim 11 wherein the management module is arranged to store the third mapping data structure in an erase block that further stores the second mapping data structure.
  • 19. The system according to claim 11 wherein the interface is adapted to receive a write request to write content, wherein the write request is associated with a logical address; wherein the management module writes the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to; and to update at least one mapping data structure to reflect the writing to the new set of flash memory cells.
  • 20. The system according to claim 19 wherein the management module invalidates all entries except a last entry of a group of entries of a mapping data structure that are associated with the same logic address.
  • 21. A system having flash memory management capabilities, the system comprises a management module that is coupled to a flash memory, another memory unit, and an interface; wherein the interface receives a write request to write content, wherein the write request is associated with a logical address; wherein the logical address comprises a logical erase block address and a logical inter erase block address;wherein the flash memory comprises multiple erase blocks;wherein the management module is adapted to: write the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to; andupdate at least one mapping data structure out of multiple mapping data structures to reflect the writing to the new set of flash memory cells;wherein the multiple mapping data structures are of different granularity;wherein the multiple mapping data structures comprise a first mapping data structure that maps logical erase block addresses to physical erase block addresses and a second mapping data structure that maps inter erase block addresses to physical inter erase block addresses of an entire erase block; andwrite to an erase block of the flash memory the second mapping data only after all the multiple physical pages of the erase block were written to the erase block;wherein the erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner;wherein the management module accesses the first mapping data structure, the second mapping data structure and a third mapping data structure; wherein the second mapping data structure maps logical page addresses to indexes into the third mapping data structure to overcome misalignments between information unit representations stored in the physical pages of the flash memory and physical page boundaries of the flash memory; wherein the third data structure maps the indexes to locations of sets of flash memory cells; wherein at least one erasure block comprises two sets of flash memory cells that differ from each other by their size but store representations of information units of the same size.
  • 22. A method for writing to a flash memory, the method comprises: receiving a write request to write content, wherein the write request is associated with a logical address;writing the write content to a new set of flash memory cells that follow a last set of flash memory cells that were written to;updating at least one mapping data structure out of multiple mapping data structures to reflect the writing to the new set of flash memory cells; wherein the multiple mapping data structures are of different granularity; wherein the multiple mapping data structures comprise a first mapping data structure that maps logical erase block addresses to physical erase block addresses and a second mapping data structure that comprises mapping information relating to multiple physical or logical pages;writing to an erase block of the flash memory the second mapping data structure only after all the multiple physical pages of the erase block were written to the erase block;wherein the erase block comprises multiple physical pages that are written in a sequential manner and are associated with logical page addresses that are assigned in a random manner; andaccessing the first mapping data structure, the second mapping data structure and a third mapping data structure; wherein the second mapping data structure maps logical page addresses to indexes into the third mapping data structure; wherein the third mapping data structure maps the indexes to locations of sets of flash memory cells to overcome misalignments between information unit representations stored in the physical pages of the flash memory and physical page boundaries of the flash memory; wherein at least one erasure block comprises at least two sets of flash memory cells that differ from each other by their size but store representations of information units of the same size.
RELATED APPLICATIONS

This application claims priority from U.S. provisional patent application Ser. No. 61/166,814, dated Apr. 6, 2009 which is incorporated herein.

US Referenced Citations (325)
Number Name Date Kind
4430701 Christian et al. Feb 1984 A
4463375 Macovski Jul 1984 A
4584686 Fritze Apr 1986 A
4589084 Fling et al. May 1986 A
4777589 Boettner et al. Oct 1988 A
4866716 Weng Sep 1989 A
5003597 Merkle Mar 1991 A
5077737 Leger et al. Dec 1991 A
5297153 Baggen et al. Mar 1994 A
5305276 Uenoyama Apr 1994 A
5592641 Doyle et al. Jan 1997 A
5623620 Alexis et al. Apr 1997 A
5640529 Hasbun Jun 1997 A
5657332 Auclair et al. Aug 1997 A
5663901 Harari et al. Sep 1997 A
5724538 Morris et al. Mar 1998 A
5729490 Calligaro et al. Mar 1998 A
5740395 Wells et al. Apr 1998 A
5745418 Hu et al. Apr 1998 A
5778430 Ish et al. Jul 1998 A
5793774 Usui et al. Aug 1998 A
5920578 Zook et al. Jul 1999 A
5926409 Engh et al. Jul 1999 A
5933368 Hu et al. Aug 1999 A
5956268 Lee Sep 1999 A
5956473 Hu et al. Sep 1999 A
5968198 Balachandran Oct 1999 A
5982659 Irrinki et al. Nov 1999 A
6011741 Harari et al. Jan 2000 A
6016275 Han Jan 2000 A
6038634 Ji et al. Mar 2000 A
6081878 Estakhri et al. Jun 2000 A
6094465 Stein et al. Jul 2000 A
6119245 Hiratsuka Sep 2000 A
6182261 Haller et al. Jan 2001 B1
6192497 Yang et al. Feb 2001 B1
6195287 Hirano Feb 2001 B1
6199188 Shen et al. Mar 2001 B1
6209114 Wolf et al. Mar 2001 B1
6259627 Wong Jul 2001 B1
6272052 Miyauchi Aug 2001 B1
6278633 Wong et al. Aug 2001 B1
6279133 Vafai et al. Aug 2001 B1
6301151 Engh et al. Oct 2001 B1
6370061 Yachareni et al. Apr 2002 B1
6374383 Weng Apr 2002 B1
6504891 Chevallier Jan 2003 B1
6532169 Mann et al. Mar 2003 B1
6532556 Wong et al. Mar 2003 B1
6553533 Demura et al. Apr 2003 B2
6560747 Weng May 2003 B1
6637002 Weng et al. Oct 2003 B1
6639865 Kwon Oct 2003 B2
6674665 Mann et al. Jan 2004 B1
6675281 Oh et al. Jan 2004 B1
6704902 Shinbashi et al. Mar 2004 B1
6751766 Guterman et al. Jun 2004 B2
6772274 Estakhri Aug 2004 B1
6781910 Smith Aug 2004 B2
6792569 Cox et al. Sep 2004 B2
6873543 Smith et al. Mar 2005 B2
6891768 Smith et al. May 2005 B2
6914809 Hilton et al. Jul 2005 B2
6915477 Gollamudi et al. Jul 2005 B2
6952365 Gonzalez et al. Oct 2005 B2
6961890 Smith Nov 2005 B2
6968421 Conley Nov 2005 B2
6990012 Smith et al. Jan 2006 B2
6996004 Fastow et al. Feb 2006 B1
6999854 Roth Feb 2006 B2
7010739 Feng et al. Mar 2006 B1
7012835 Gonzalez et al. Mar 2006 B2
7038950 Hamilton et al. May 2006 B1
7068539 Guterman et al. Jun 2006 B2
7079436 Perner et al. Jul 2006 B2
7149950 Spencer et al. Dec 2006 B2
7177977 Chen et al. Feb 2007 B2
7188228 Chang et al. Mar 2007 B1
7191379 Adelmann et al. Mar 2007 B2
7196946 Chen et al. Mar 2007 B2
7203874 Roohparvar Apr 2007 B2
7212426 Park et al May 2007 B2
7290203 Emma et al. Oct 2007 B2
7292365 Knox Nov 2007 B2
7301928 Nakabayashi et al. Nov 2007 B2
7315916 Bennett et al. Jan 2008 B2
7388781 Litsyn et al. Jun 2008 B2
7395404 Gorobets et al. Jul 2008 B2
7441067 Gorobets et al. Oct 2008 B2
7443729 Li et al. Oct 2008 B2
7450425 Aritome Nov 2008 B2
7454670 Kim et al. Nov 2008 B2
7466575 Shalvi et al. Dec 2008 B2
7533328 Alrod et al. May 2009 B2
7558109 Brandman et al. Jul 2009 B2
7593263 Sokolov et al. Sep 2009 B2
7610433 Randell et al. Oct 2009 B2
7613043 Cornwell et al. Nov 2009 B2
7619922 Li et al. Nov 2009 B2
7697326 Sommer et al. Apr 2010 B2
7706182 Shalvi et al. Apr 2010 B2
7716538 Gonzalez et al. May 2010 B2
7804718 Kim Sep 2010 B2
7805663 Brandman et al. Sep 2010 B2
7805664 Yang et al. Sep 2010 B1
7844877 Litsyn et al. Nov 2010 B2
7911848 Eun et al. Mar 2011 B2
7961797 Yang et al. Jun 2011 B1
7975192 Sommer et al. Jul 2011 B2
8020073 Emma et al. Sep 2011 B2
8060719 Radke et al. Nov 2011 B2
8108590 Chow et al. Jan 2012 B2
8122328 Liu et al. Feb 2012 B2
8159881 Yang Apr 2012 B2
8190961 Yang et al. May 2012 B1
8250324 Haas et al. Aug 2012 B2
8300823 Bojinov et al. Oct 2012 B2
8305812 Levy et al. Nov 2012 B2
8327246 Weingarten et al. Dec 2012 B2
8407560 Ordentlich et al. Mar 2013 B2
8417893 Khmelnitsky et al. Apr 2013 B2
20010034815 Dugan et al. Oct 2001 A1
20020063774 Hillis et al. May 2002 A1
20020085419 Kwon et al. Jul 2002 A1
20020154769 Petersen et al. Oct 2002 A1
20020156988 Toyama et al. Oct 2002 A1
20020174156 Birru et al. Nov 2002 A1
20030014582 Nakanishi Jan 2003 A1
20030065876 Lasser Apr 2003 A1
20030101404 Zhao et al. May 2003 A1
20030105620 Bowen Jun 2003 A1
20030177300 Lee et al. Sep 2003 A1
20030192007 Miller et al. Oct 2003 A1
20040015771 Lasser et al. Jan 2004 A1
20040030971 Tanaka et al. Feb 2004 A1
20040059768 Denk et al. Mar 2004 A1
20040080985 Chang et al. Apr 2004 A1
20040153722 Lee Aug 2004 A1
20040153817 Norman et al. Aug 2004 A1
20040181735 Xin Sep 2004 A1
20040203591 Lee Oct 2004 A1
20040210706 In et al. Oct 2004 A1
20050013165 Ban Jan 2005 A1
20050018482 Cemea et al. Jan 2005 A1
20050083735 Chen et al. Apr 2005 A1
20050117401 Chen et al. Jun 2005 A1
20050120265 Pline et al. Jun 2005 A1
20050128811 Kato et al. Jun 2005 A1
20050138533 Le Bars et al. Jun 2005 A1
20050144213 Simkins et al. Jun 2005 A1
20050144368 Chung et al. Jun 2005 A1
20050169057 Shibata et al. Aug 2005 A1
20050172179 Brandenberger et al. Aug 2005 A1
20050213393 Lasser Sep 2005 A1
20050243626 Ronen Nov 2005 A1
20060059406 Micheloni et al. Mar 2006 A1
20060059409 Lee Mar 2006 A1
20060064537 Oshima Mar 2006 A1
20060101193 Murin May 2006 A1
20060195651 Estakhri et al. Aug 2006 A1
20060203587 Li et al. Sep 2006 A1
20060221692 Chen Oct 2006 A1
20060248434 Radke et al. Nov 2006 A1
20060268608 Noguchi et al. Nov 2006 A1
20060282411 Fagin et al. Dec 2006 A1
20060284244 Forbes et al. Dec 2006 A1
20060294312 Walmsley Dec 2006 A1
20070025157 Wan et al. Feb 2007 A1
20070063180 Asano et al. Mar 2007 A1
20070081388 Joo Apr 2007 A1
20070098069 Gordon May 2007 A1
20070103992 Sakui et al. May 2007 A1
20070104004 So et al. May 2007 A1
20070109858 Conley et al. May 2007 A1
20070124652 Litsyn et al. May 2007 A1
20070140006 Chen et al. Jun 2007 A1
20070143561 Gorobets Jun 2007 A1
20070150694 Chang et al. Jun 2007 A1
20070168625 Cornwell et al. Jul 2007 A1
20070171714 Wu et al. Jul 2007 A1
20070171730 Ramamoorthy et al. Jul 2007 A1
20070180346 Murin Aug 2007 A1
20070223277 Tanaka et al. Sep 2007 A1
20070226582 Tang et al. Sep 2007 A1
20070226592 Radke Sep 2007 A1
20070228449 Takano et al. Oct 2007 A1
20070253249 Kang et al. Nov 2007 A1
20070253250 Shibata et al. Nov 2007 A1
20070263439 Cornwell et al. Nov 2007 A1
20070266291 Toda et al. Nov 2007 A1
20070268754 Lee et al. Nov 2007 A1
20070271494 Gorobets Nov 2007 A1
20070297226 Mokhlesi Dec 2007 A1
20080010581 Alrod et al. Jan 2008 A1
20080028014 Hilt et al. Jan 2008 A1
20080049497 Mo Feb 2008 A1
20080055989 Lee et al. Mar 2008 A1
20080082897 Brandman et al. Apr 2008 A1
20080092026 Brandman et al. Apr 2008 A1
20080104309 Cheon et al. May 2008 A1
20080112238 Kim et al. May 2008 A1
20080116509 Harari et al. May 2008 A1
20080126686 Sokolov et al. May 2008 A1
20080127104 Li et al. May 2008 A1
20080128790 Jung Jun 2008 A1
20080130341 Shalvi et al. Jun 2008 A1
20080137413 Kong et al. Jun 2008 A1
20080137414 Park et al. Jun 2008 A1
20080141043 Flynn et al. Jun 2008 A1
20080148115 Sokolov et al. Jun 2008 A1
20080158958 Shalvi et al. Jul 2008 A1
20080159059 Moyer Jul 2008 A1
20080162079 Astigarraga et al. Jul 2008 A1
20080168216 Lee Jul 2008 A1
20080168320 Cassuto et al. Jul 2008 A1
20080181001 Shalvi Jul 2008 A1
20080192539 Choi et al. Aug 2008 A1
20080198650 Shalvi et al. Aug 2008 A1
20080198652 Shalvi et al. Aug 2008 A1
20080201620 Gollub Aug 2008 A1
20080209114 Chow et al. Aug 2008 A1
20080219050 Shalvi et al. Sep 2008 A1
20080225599 Chae Sep 2008 A1
20080250195 Chow et al. Oct 2008 A1
20080263262 Sokolov et al. Oct 2008 A1
20080282106 Shalvi et al. Nov 2008 A1
20080285351 Shlick et al. Nov 2008 A1
20080301532 Uchikawa et al. Dec 2008 A1
20090024905 Shalvi et al. Jan 2009 A1
20090027961 Park et al. Jan 2009 A1
20090043951 Shalvi et al. Feb 2009 A1
20090046507 Aritome Feb 2009 A1
20090072303 Prall et al. Mar 2009 A9
20090091979 Shalvi Apr 2009 A1
20090103358 Sommer et al. Apr 2009 A1
20090106485 Anholt Apr 2009 A1
20090113275 Chen et al. Apr 2009 A1
20090125671 Flynn May 2009 A1
20090132755 Radke May 2009 A1
20090144598 Yoon et al. Jun 2009 A1
20090144600 Perlmutter et al. Jun 2009 A1
20090150599 Bennett Jun 2009 A1
20090150748 Egner et al. Jun 2009 A1
20090157964 Kasorla et al. Jun 2009 A1
20090158126 Perlmutter et al. Jun 2009 A1
20090168524 Golov et al. Jul 2009 A1
20090187803 Anholt et al. Jul 2009 A1
20090199074 Sommer Aug 2009 A1
20090213653 Perlmutter et al. Aug 2009 A1
20090213654 Perlmutter et al. Aug 2009 A1
20090228679 Jiang Sep 2009 A1
20090228761 Perlmutter et al. Sep 2009 A1
20090240872 Perlmutter et al. Sep 2009 A1
20090282185 Van Cauwenbergh Nov 2009 A1
20090282186 Mokhlesi et al. Nov 2009 A1
20090287930 Nagaraja Nov 2009 A1
20090300269 Radke et al. Dec 2009 A1
20090323942 Sharon et al. Dec 2009 A1
20100005270 Jiang Jan 2010 A1
20100025811 Bronner et al. Feb 2010 A1
20100030944 Hinz Feb 2010 A1
20100058146 Weingarten et al. Mar 2010 A1
20100064096 Weingarten et al. Mar 2010 A1
20100088557 Weingarten et al. Apr 2010 A1
20100091535 Sommer et al. Apr 2010 A1
20100095186 Weingarten Apr 2010 A1
20100110787 Shalvi et al. May 2010 A1
20100115376 Shalvi et al. May 2010 A1
20100122113 Weingarten et al. May 2010 A1
20100124088 Shalvi et al. May 2010 A1
20100131580 Kanter et al. May 2010 A1
20100131806 Weingarten et al. May 2010 A1
20100131809 Katz May 2010 A1
20100131826 Shalvi et al. May 2010 A1
20100131827 Sokolov et al. May 2010 A1
20100131831 Weingarten et al. May 2010 A1
20100146191 Katz Jun 2010 A1
20100146192 Weingarten et al. Jun 2010 A1
20100149881 Lee et al. Jun 2010 A1
20100172179 Gorobets et al. Jul 2010 A1
20100174853 Lee et al. Jul 2010 A1
20100180073 Weingarten et al. Jul 2010 A1
20100199149 Weingarten et al. Aug 2010 A1
20100211724 Weingarten Aug 2010 A1
20100211833 Weingarten Aug 2010 A1
20100211856 Weingarten Aug 2010 A1
20100241793 Sugimoto et al. Sep 2010 A1
20100246265 Moschiano et al. Sep 2010 A1
20100251066 Radke Sep 2010 A1
20100253555 Weingarten et al. Oct 2010 A1
20100257309 Barsky et al. Oct 2010 A1
20100269008 Leggette et al. Oct 2010 A1
20100293321 Weingarten Nov 2010 A1
20100318724 Yeh Dec 2010 A1
20110051521 Levy et al. Mar 2011 A1
20110055461 Steiner et al. Mar 2011 A1
20110093650 Kwon et al. Apr 2011 A1
20110096612 Steiner et al. Apr 2011 A1
20110099460 Dusija et al. Apr 2011 A1
20110119562 Steiner et al. May 2011 A1
20110153919 Sabbag Jun 2011 A1
20110161775 Weingarten Jun 2011 A1
20110194353 Hwang et al. Aug 2011 A1
20110209028 Post et al. Aug 2011 A1
20110214029 Steiner et al. Sep 2011 A1
20110214039 Steiner et al. Sep 2011 A1
20110246792 Weingarten Oct 2011 A1
20110246852 Sabbag Oct 2011 A1
20110252187 Segal et al. Oct 2011 A1
20110252188 Weingarten Oct 2011 A1
20110271043 Segal et al. Nov 2011 A1
20110302428 Weingarten Dec 2011 A1
20120001778 Steiner et al. Jan 2012 A1
20120005554 Steiner et al. Jan 2012 A1
20120005558 Steiner et al. Jan 2012 A1
20120005560 Steiner et al. Jan 2012 A1
20120008401 Katz et al. Jan 2012 A1
20120008414 Katz et al. Jan 2012 A1
20120017136 Ordentlich et al. Jan 2012 A1
20120051144 Weingarten et al. Mar 2012 A1
20120063227 Weingarten et al. Mar 2012 A1
20120066441 Weingarten Mar 2012 A1
20120110250 Sabbag et al. May 2012 A1
20120124273 Goss et al. May 2012 A1
20120246391 Meir et al. Sep 2012 A1
Foreign Referenced Citations (1)
Number Date Country
WO2009053963 Apr 2009 WO
Non-Patent Literature Citations (37)
Entry
Search Report of PCT Patent Application WO 2009/118720 A3.
Search Report of PCT Patent Application WO 2009/095902 A3.
Search Report of PCT Patent Application WO 2009/078006 A3.
Search Report of PCT Patent Application WO 2009/074979 A3.
Search Report of PCT Patent Application WO 2009/074978 A3.
Search Report of PCT Patent Application WO 2009/072105 A3.
Search Report of PCT Patent Application WO 2009/072104 A3.
Search Report of PCT Patent Application WO 2009/072103 A3.
Search Report of PCT Patent Application WO 2009/072102 A3.
Search Report of PCT Patent Application WO 2009/072101 A3.
Search Report of PCT Patent Application WO 2009/072100 A3.
Search Report of PCT Patent Application WO 2009/053963 A3.
Search Report of PCT Patent Application WO 2009/053962 A3.
Search Report of PCT Patent Application WO 2009/053961 A3.
Search Report of PCT Patent Application WO 2009/037697 A3.
Yani Chen, Kcshab K. Parhi, “Small Area Parallel Chien Search Architectures for Long BCH Codes”, Ieee Transactions on Very Large Scale Integration(VLSI) Systems, vol. 12, No. 5, May 2004.
Yuejian Wu, “Low Power Decoding of BCH Codes”, Nortel Networks, Ottawa, Ont., Canada, in Circuits and systems, 2004. ISCAS '04. Proceeding of the 2004 International Symposium on Circuits and Systems, published May 23-26, 2004, vol. 2, pp. II-369-II-372 vol. 2.
Michael Purser, “Introduction to Error Correcting Codes”, Artech House Inc., 1995.
Ron M. Roth, “Introduction to Coding Theory”, Cambridge University Press, 2006.
Akash Kumar, Sergei Sawitzki, “High-Throughput and Low Power Architectures for Reed Solomon Decoder”, (a.kumar at tue.nl, Eindhoven University of Technology and sergei.sawitzki at philips.com).
Todd K.Moon, “Error Correction Coding Mathematical Methods and Algorithms”, A John Wiley & Sons, Inc., 2005.
Richard E. Blahut, “Algebraic Codes for Data Transmission”, Cambridge University Press, 2003.
David Esseni, Bruno Ricco, “Trading-Off Programming Speed and Current Absorption in Flash Memories with the Ramped-Gate Programming Technique”, Ieee Transactions on Electron Devices, vol. 47, No. 4, Apr. 2000.
Giovanni Campardo, Rino Micheloni, David Novosel, “VLSI-Design of Non-Volatile Memories”, Springer Berlin Heidelberg New York, 2005.
John G. Proakis, “Digital Communications”, 3rd ed., New York: McGraw-Hill, 1995.
J.M. Portal, H. Aziza, D. Nee, “EEPROM Memory: Threshold Voltage Built in Self Diagnosis”, ITC International Test Conference, Paper 2.1.
J.M. Portal, H. Aziza, D. Nee, “EEPROM Diagnosis Based on Threshold Voltage Embedded Measurement”, Journal of Electronic Testing: Theory and Applications 21, 33-42, 2005.
G. Tao, A. Scarpa, J. Dijkstra, W. Stidl, F. Kuper, “Data retention prediction for modern floating gate non-volatile memories”, Microelectronics Reliability 40 (2000), 1561-1566.
T. Hirncno, N. Matsukawa, H. Hazama, K. Sakui, M. Oshikiri, K. Masuda, K. Kanda, Y. Itoh, J. Miyamoto, “A New Technique for Measuring Threshold Voltage Distribution in Flash EEPROM Devices”, Proc. IEEE 1995 Int. Conference on Microelectronics Test Structures, vol. 8, Mar. 1995.
Boaz Eitan, Guy Cohen, Assaf Shappir, Eli Lusky, Amichai Givant, Meir Janai, Ilan Bloom, Yan Polansky, Oleg Dadashev, Avi Lavan, Ran Sahar, Eduardo Maayan, “4-bit per Cell NROM Reliability”, Appears on the website of Saifun.com.
Paulo Cappelletti, Clara Golla, Piero Olivo, Enrico Zanoni, “Flash Memories”, Kluwer Academic Publishers, 1999.
Jedec Standard, “Stress-Test-Driven Qualification of Integrated Circuits”, JEDEC Solid State Technology Association. JEDEC Standard No. 47F pp. 1-26.
Dempster, et al., “Maximum Likelihood from Incomplete Data via the EM Algorithm”, Journal of the Royal Statistical Society. Series B (Methodological), vol. 39, No. 1 (1997), pp. 1-38.
Mielke, et al., “ Flash EEPROM Threshold Instabilities due to Charge Trapping During Program/Erase Cycling”, IEEE Transactions on Device and Materials Reliability, vol. 4, No. 3, Sep. 2004, pp. 335-344.
Daneshbeh, “Bit Serial Systolic Architectures for Multiplicative Inversion and Division over GF (2)”, A thesis presented to the University of Waterloo, Ontario, Canada, 2005, pp. 1-118.
Chen, Formulas for the solutions of Quadratic Equations over GF (2), IEEE Trans. Inform. Theory, vol. IT-28, No. 5, Sep. 1982, pp. 792-794.
Berlekamp et al., “On the Solution of Algebraic Equations over Finite Fields”, Inform. Cont. 10, Oct. 1967, pp. 553-564.
Related Publications (1)
Number Date Country
20100257309 A1 Oct 2010 US
Provisional Applications (1)
Number Date Country
61166814 Apr 2009 US