The present invention relates generally to systems including memories. More particularly, the present invention relates to an apparatus and a method for using a memory as a temporary cache.
Electronic equipment uses memory devices, such as, for example, flash memories, for storing data or information. A flash system including a flash controller and a plurality of flash memory devices in a multi-drop configuration is disclosed in U.S. Patent Application Publication No. 2006/0198202 A1 (Erez). The flash controller sends data to the memory devices and controls operations multiple memory devices. The flash controller employs a memory resource such as static random access memory (SRAM) therein for storing code and/data to execute operations in its central processing unit (CPU).
The memory controller typically has its own data storage, which is used for caching of data for various applications. Increasing the capacity of the data storage elements might be beneficial for some applications due to the increased caching capability by the memory controller. However, increasing the capacity of the data storage results in increased cost.
In accordance with an aspect of the present invention, there is provided a method for communicating with a plurality of memory devices connected in-series, at least one of the memory devices having a temporary store element, the method comprising: selecting a memory device of the plurality of memory devices, writing data stored in a data storage to the temporary store element of the selected memory device; and at a later time, reading the data from the temporary store element of the selected memory device.
The method may further comprise storing the read data back to the data storage. In the data storage, the space storing the data may be freed up after performing the step of writing.
Advantageously, the step of writing comprises: transmitting a write command including the data addressed to the selected memory device. The selected device writes the data to the temporary store element thereof in response to the write command.
The step of reading may comprise: transmitting a read command addressed to the selected memory device, the selected memory device reading the data from the temporary store element thereof in response to the read command; and receiving the read data through the last memory device of plurality of memory devices.
The method may further comprise selecting another memory device of the plurality of memory devices. The data may be written to the temporary store element of the another selected memory device. Later, the data may comprise a plurality of data parts including first and second data parts. The data parts may be temporarily stored separately and read back separately.
In accordance with another aspect of the present invention, there is provided an apparatus in communication with a plurality of memory devices connected in-series, each of the memory devices having a temporary store element, the apparatus comprising a processor for selecting a memory device of the plurality of memory devices, writing data in the temporary store element of the selected memory device; and reading back the data at a later time from the temporary store element of the selected memory device.
In accordance with a further aspect of the present invention, there is provided a system comprising: a plurality of memory devices connected in-series, each of the memory devices having a temporary store element and memory cells; and an apparatus for communicating with the plurality of memory devices. The apparatus comprises a processor for selecting a memory device of the plurality of memory devices, writing data in the temporary store element of the selected memory device; and reading back the data at a later time from the temporary store element of the selected memory device.
In accordance with an embodiment of the present invention, there is provided an apparatus for using a page buffer of a flash memory device as a temporary cache for data. A memory controller writes data to the page buffer and later reads out the data without programming the data into the memory cells of the flash memory device. This allows the memory controller to use the page buffer as temporary cache so that the data does not have to occupy space within the memory controller's local data storage. Therefore, the memory controller can free up space in its own storage to use the space for other operations or overwrite the occupied space with data for other operations.
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.
Embodiments will now be described with reference to the attached drawings in which:
In the following detailed description of sample embodiments of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific sample embodiments in which the present invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the present invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims.
In the particular example shown in
The memory controller 110 has a data storage 112 and a processor 114. The data storage 112 stores various data that includes information on operation instructions, addresses and memory data to be processed and to be stored in the series-connected memory devices. The information on operation instructions is used for controlling the series-connected memory devices. The data storage 112 is, for example, a static random access memory (SRAM) or any type of embedded memory. More generally, any appropriate data storage may be implemented. The processor 114 performs operations of data processing and controlling of the memory devices accessing the data stored in the data storage 112.
In operation, the memory controller 110 sends a command input (CI) signal SC1 to the first device 120-1 and receives a command output (CO) signal SC(M+1) from the last device 120-M of the serial interconnection. Also, the memory controller 110 provides a command strobe input (CSI) signal SCS1 and a data strobe input (DSI) signal SDS1 to the first device 120-1 and provides a clock signal CK to all of the devices 120-1-120-M in a common clock source fashion.
The memory controller 110 has a plurality of connections: a command signal output connection CIO for sending the CI signal SC1; a command signal input connection COI for receiving the CO signal SC(M+1); an input strobe connection CSIO for sending the CSI signal SCS1; an output strobe connection DSIO for sending the DSI signal SDS1; and a clock output connection CKO for providing the clock signal CK.
The memory devices 120-1, 120-2, 120-3, . . . , and 120-M have page buffers 122-1, 122-2, 122-3, . . . , and 122-M, respectively, and flash memory cells 124-1, 124-2, 124-3, . . . , and 124-M, respectively. Each of the memory devices 120-1-120-M has a signal input connection CI for receiving the CI signal SCi (i=1 to M) from a previous device; a signal output connection CO for providing the CI signal SC(i+1) to a succeeding device; an input strobe input connection CSI for receiving the CSI signal SCSi from a previous device; an input strobe output connection CSO for sending an output CSI signal SCS(i+1) to the succeeding device; an output strobe input connection DSI for receiving the DSI signal SDSi from the previous device; and an output strobe output connection DSO for sending an output DSI signal SDS(i+1) to the succeeding device.
Each of the memory devices 120-1-120-M has a unique device address (DA) that is hard wired or pre-assigned, so that one device can be selected or designated at a time in normal operation. Example details of an architecture featuring devices connected in-series are provided in U.S. patent application Ser. No. 11/594,564 entitled “Daisy Chain Cascading Devices” filed Jul. 31, 2006, the disclosure of which is hereby incorporated by reference in its entirety. Other example details of an architecture feature devices connected in-series are provided in U.S. Provisional Patent Application Ser. No. 60/868,773 entitled “System and Method of Operating Memory Devices of Varying Type” filed Dec. 6, 2006, the disclosure of which is hereby incorporated by reference in its entirety. Examples of the device address assignment in a plurality of memory devices that are connected in-series are provided in U.S. Provisional Patent Application No. 60/787,710, filed Mar. 28, 2006; U.S. patent application Ser. No. 11/521,734 filed Sep. 15, 2006; U.S. Provisional Patent Application No. 60/802,645, filed May 23, 2006; and U.S. patent application Ser. No. 11/750,649 filed May 18, 2007, the disclosures of which are incorporated by reference in their entirety.
In the normal operation, the memory controller 110 sends the CI signal SC1 containing commands. A command includes a device address (DA) and an operation code (hereinafter OP code) representing an operation instruction. Some commands additionally include address information, and some commands additionally include data. Each OP code is associated with a respective operation. Each command is also referred to herein as having a type that is associated with the OP code contained in the command. For example, a command containing a read OP code is referred to as a “read command”. Each of the memory devices 120-1-120-M receives commands via its respective CI either directly from the memory controller in the case that a given device is the memory device connected directly to the memory controller (device 120-1 in the illustrated example), or from an adjacent preceding memory device for other devices. Each of the memory devices 120-1-120-M uses its respective CO for forwarding on commands either to the memory controller 110 in the case that a given device is the one having its output connected to the memory controller (device 120-M in the illustrated example), or to an adjacent following device. A command containing a write OP code addressed to a particular flash memory device results in data being written to a page buffer of that device, and then transferred from the page buffer to the flash memory cells of the memory device. A command containing a read OP code addressed to a particular flash memory device results in data being read from the flash memory cells of the memory device to the page buffer of the memory device and then being transferred out of the page buffer.
The memory controller 110 uses the page buffer of a memory device as a temporary cache for data. For example, the memory controller 110 uses the page buffer of a selected memory device as a temporary cache for data when the selected memory device is not presently being used for page programming or page read operations. Note that the selected memory device can be any one of the memory devices 120-1-120-M and is selected by the memory controller 110. Since the data is stored in the page buffer of the selected memory device, the memory controller 110 does not need to locally store the data in the data storage 112 of the memory controller 110. This allows the memory controller 110 to free up space in its data storage 112 that can otherwise be used for storing the data. The memory controller 110 can later read back the data from the page buffer of the selected memory device (the temporary cache) without programming the data into the memory cells of the selected memory device. In this manner, the page buffer of the selected memory device is accessed independently of the program operation. Note that the data may be in respect of any appropriate application in which there is data to be maintained.
In order for the page buffers to operate as temporary caches, three “modular” memory access commands are used. The first is referred to as a “burst data load” command and contains a burst data load OP code. This causes data to be written to the page buffer of a memory device, but this command alone does not cause the data to be transferred to the flash memory cells of the memory device. In the examples that follow, 4×h and 5×h are used for this purpose, but more generally the command structure would be defined on an implementation specific basis. The second is referred to as a “burst data read” command and contains a burst data read OP code. This causes data to be read directly from the page buffer without first reading from the flash memory cells. In the examples that follow, 2×h is used for this, but more generally, the command structure would be defined on an implementation specific basis. The third is referred to as a “page program” command and contains a page program OP code. This causes data that was previously stored in the page buffer to be written to the flash memory cells, destroying the contents of the page buffer in the process for verification purposes. In the examples that follow, 6×h is used for this, but more generally, the command structure would be defined on an implementation specific basis.
In the embodiments, a flexible modular command structure is used. An example command format is detailed
In Table I, DA is a device address; OP code is an operation code; RA is a row address; CA is a column address; and DATA is write data. Examples of commands associated with OP codes are a “burst data load” command and a “burst data read” command. There are cases of: (i) either of row address or column address; (ii) neither row address nor column address; (iii) no data.
A particular example of the above-referenced command structure is provided in commonly assigned and co-pending U.S. patent application Ser. No. 11/840,692 filed Aug. 17, 2007 and U.S. Provisional Patent Application No. 60/892,705 filed Mar. 2, 2007, the contents of which are hereby incorporated by reference in their entirety. The applications disclose different command structures to distinguish core access operations that involve relatively long processing times from page buffer access operations that involve relatively short access times. Further details of the modular command structure will be later described with reference to
In the normal operation, the memory controller 110 can transmit data to the page buffer 122-i without restriction to page programming. Data is written to the page buffer 122-i by the burst data load command as indicated at 133, and at a later time read by the burst data read command as indicated at 134. Note that when a temporary cache operation is performed, page programming is not performed. Therefore, the page buffer 122-i can be accessed relatively quickly. In this manner, the page buffer 122-i can be used as a temporary cache for data and/or instruction.
The device controller 126-i performs a device address match determination and data process. Thus, in the “write” operation, the device controller 126-i determines a device address match and loads the data of the input command to the page buffer 122-i in a case of the device addresses match. If the device addresses do not match, the device controller 126-i forwards the input command to the next memory device 120-(i+1). Also, in the “read back” operation, the device controller 126-i determines a device address match, the data is read from the page buffer 122-i and the read data is transferred to the next memory device 120-(i+1). If no device address match, the device controller 126-i forwards the input command to the next memory device 120-(i+1). The read data is propagated through the rest of the memory devices connected in-series and back to the memory controller 110.
A specific example of the temporary cache function of the page buffer for an architecture with series-connected devices will now be described with reference to
Referring to
Each of the memory devices includes a device address match determiner (DAMD) for determining whether the device address DA contained in the input command matches the device address assigned to that device. The assigned address to each device is held in a register (not shown) thereof. In
An example of data transfer signals used in the system of
In performing the transfer to the page buffer of a memory device, a command strobe input (CSI) signal SCS1 and a command input (CI) signal SC1 are provided by the memory controller 110. The CSI signal and the CI signal are propagated through the series-connected devices. The propagated CSI signal and CI signal are shown as SCSi and SCi, respectively.
To write to the page buffer 122-3 of the third memory device 120-3, the CI signal SCi contains the third device's DA (0010), operation instruction (“Burst Data Load”) represented by OP code, column address CA and data to be written. When the CSI signal SCS3 is asserted to enable the input (i.e., the CI signal SC3) to the third memory device 120-3, the device address match determiner 128-3 determines the device address match. Thus, the third device 120-3 is a designated device to be selected. Note that the data transfer to the third designated memory device 120-3 involves a third ‘Burst Data Load’ OP code addressed to the third designated memory device 120-3, which has an address of “0010” in this example. In the particular example, during the CSI signal being asserted for the third device, the data is transferred from the data storage 112 of the memory controller 110 to the page buffer 122-3 of the designated device 120-3 as indicated by 232 in
A similar transfer is performed for another designated memory device. In another implementation, a single command is issued for writing the same data to more than one memory device. Multiple or all device selection is possible by proper device designation by command or other means. In such example, during the CSI signal SCSi being asserted for the other device, the data is transferred from the data storage 112 of the memory controller 110 to the page buffer of the designated device.
Referring to
Later, when the data stored in any one of the temporary caches is required to be read back, the memory controller 110 sends the read command. The command containing the OP code for ‘Burst Data Read’ is issued, together with the device address for designating the temporary cache. For example, the data temporary stored in the page buffer 122-1 of the first memory device 120-1 is read back. In such a case, the device address DA (“0000”) with the read OP code is sent by the memory controller 110. Upon device address match determination, the memory device 120-1 processes the command and the data is read and the read data is sent back to the memory controller 110 through the remaining memory devices (step 19-4). If reading back of the data temporarily stored in one page buffer is sufficient, no more reading will be necessary (NO at step 19-5) and reading back operation is completed. However, for any reason, another reading back of the data is required (YES at step 19-5), the memory controller 110 sends the command containing the device address DA (0010) and the OP code for ‘Burst Data Read’. The data temporarily stored in the page buffer 122-3 of the third memory device 120-3 is read back (step 19-4). If the second reading back of the data temporarily stored in the page buffer is sufficient, no more reading will be necessary (NO at step 19-5) and reading back operation is completed.
It would be apparent that the data from data storage 112 of the memory controller 110 can be temporarily stored in more than two temporary caches. The data can be read back from any one of the temporary caches.
Alternatively, two or more different data can be loaded in two or more temporary caches.
Referring to
Data 1, 2 and 3 are sequentially stored in three temporary caches. The memory controller 110 issues a command containing a device address DA (0000), a ‘Burst Data Load’ OP code and Data 1 (step-19-1). The first device 120-1 is designated and selected in accordance with the device address DA. Data 1 is stored in the page buffer 122-1 of the selected memory device 120-1 (step 19-2). Then, the memory controller 110 determines whether more cache needs (step 19-3). In this case, another cache is necessary (YES at step 19-3), the memory controller 110 issues a command containing a device address DA (0001), a ‘Burst Data Load’ OP code and Data 2 (step 19-1). The second device 120-2 is designated and selected in accordance with the device address DA. Data 2 is stored in the page buffer 122-2 of the selected memory device 120-2 (step 19-2). Again, the memory controller 110 issues a command containing a device address DA (0010), a ‘Burst Data Load’ OP code and Data 3 (step 19-1). No more cache is necessary (NO at step 19-3) and temporary stores are completed.
In the data recovery operation, Data 1, 2 and 3 temporarily stored in the page buffers 122-1, 122-2 and 122-3 are sequentially read and back to the data storage 112 of the memory controller 110.
The memory controller 110 sends a command containing a device address DA (0000) and OP code for ‘Burst Data Read’. Upon device address match determination, the first memory device 120-1 processes the command and Data 1 temporarily stored in the page buffer 122-1 of the first memory device 120-1 is read and the read data is sent back to the memory controller 110 through the remaining memory devices (step 19-4). More reading back is required (YES at step 19-5), step 19-4 is repeated. Thus, the memory controller 110 sends a command containing a device address DA (0001) and OP code for ‘Burst Data Read’. Upon device address match determination, the second memory device 120-1 processes the command and Data 2 temporarily stored in the page buffer 122-2 of the second memory device 120-2 is read and the read data is sent back to the memory controller 110 through the remaining memory devices (step 19-4). Similarly, the memory controller 110 sends a command containing a device address DA (0010) and OP code for ‘Burst Data Read’. Upon device address match determination, the third memory device 120-3 processes the command and Data 3 temporarily stored in the page buffer 122-3 of the second memory device 120-3 is read and the read data is sent back to the memory controller 110 through the remaining memory devices (step 19-4). No more reading is necessary (NO at step 19-5) and reading back operation is completed.
Another scenario is that while the capacity of the data storage 112 is smaller than that of each page buffer, the character of Data 1, 2 and 3 are different (e.g., instruction command, data value to be stored in the flash memory) and Data 1, 2 and 3 are separately cached. In such a scenario, process is the same as described above.
In some embodiments of the present invention, the systems described herein are implemented using a flexible modular command structure, example details of which have already been provided. Further example details are provided in this section with reference to
All commands, addresses, and data are shifted in and out of the memory device, starting with the most significant bit (MSB). Command input (CI) is sampled at the positive or negative clock edge (i.e., at the crossing point of clocks—CK and /CK) while the command strobe input (CSI) is “high”. Each command includes a 1-byte device address (DA) and 1-byte OP code and/or column-address/row-address/data-input bytes if necessary. Once the CSI transits logic “high”, the 1-byte DA (Device Address) is shifted into a DA register, and then the 1-byte OP code is shifted into an OP code register. In so doing, the most significant bit (MSB) starts first on CI and each bit is latched at the crossing of CK and /CK while CSI is logic-HIGH state. However every input sequence in byte mode starts at a rising edge of CK (=falling edge of /CK). Depending on the command, the OP Code are followed by address bytes, data bytes, both or none as shown in
For the memory devices connected in-series, a special device address (=FFh) is assigned for “Broadcast” operation. More generally, the address that is defined for broadcast mode operation can be defined on an implementation specific basis. This “Broadcast Device Address” may be used with any command. However, using the broadcast device address (FFh) along with the “read-type” commands is not recommended because the read data from the last device is the only valid output data.
In some implementations, the signal bus on a modular command Flash device is fully multiplexed as command, address and data all share the same pin(s). The CSI signal's logic-high state validates the Command Input (CI) which can be an n-bit wide signal containing multiplexed command/address/data information for the memory device. If the CSI signal stays in logic-low state, device ignores signal inputs from CI pins. The command input sequence normally consists of one-byte DA (Device Address) latch cycles, one-byte command latch cycles, address latch cycles (=3-bytes for row address or 2-bytes for column addresses) and/or data-input latch cycles up to 2,112 bytes. In 1-bit link mode, four clock-cycles at DDR (double data rate) make one byte of a serial packet. In 2-bit link mode, two clock-cycles at DDR (double data rate) make one byte of a serial packet. In 4-bit link mode, one clock-cycle at DDR (double data rate) makes one byte of a serial packet. Every set of command instructions may be followed by two extra CK and /CK transitions after CSI makes a HIGH to LOW transition. In some embodiments, an extra number of CK and CK transitions after SCSi transitions to low are used that are equal in number to 2+ the number of devices in the architecture with devices connected together in-series. Every input sequence defined in
Two representative commands to show the feature of modular commands are described below, namely a Page Read (DA and 0×h) and a Burst Data Read (DA and 2×h) command.
Referring to
The core access operations such as page read, page program and block erase take long time and their processing times are varied according to PVT (ProcessNoltage/Temperature) change. So, whenever issuing core access commands, a user can monitor the status of each operation after asserting command without interrupting internal operations. The other purpose of the status register is to check whether or not the page program and block erase are performed without fail. In case of fail, a new row position is determined by the memory controller and it issues a new command containing new row address to write the same data that was written to the old row location that failed to be written. Without monitoring the status register, the memory controller does not know that the program and erase operations are done without fail.
After READ DEVICE STATUS (DA and D0h) command, using DSI, all 8-bit status is read from the status register until DSI goes to low. After the BURST DATA READ (DA and 2×h) command has been issued and then DSI goes to high, the serial output timing as shown in
The BURST DATA READ (DA and 2×h) command referred to above enables the user to specify a column address so the data at the page buffers can be read starting from the given column address within the selected page size while SDSi is high. The burst data read mode is enabled after a normal PAGE READ (DA and 0×h) command and page loading time (=tR). The BURST DATA READ (DA and 2×h) command can be issued without limit within the page. Every BURST DATA READ command can have same or different column address from the previous BURST DATA READ command. Only data on the current page buffers can be read. If a different page is to be read, a new PAGE READ (DA and 0×h) command should be issued. And after tR, a new BURST DATA READ (DA and 2×h) command can be issued to access new page data.
In the embodiments described above, the device elements and circuits are connected to each other as shown in the figures, for the sake of simplicity. In practical applications of the present invention, elements, circuits, etc. may be connected directly to each other. As well, elements, circuits etc. may be connected indirectly to each other through other elements, circuits, etc., necessary for operation of the memory devices or apparatus. Thus, in actual configuration of devices and apparatus, the elements and circuits are directly or indirectly coupled with or connected to each other.
The above-described embodiments of the present invention are intended to be examples only. Alterations, modifications and variations may 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.
This application is a continuation of U.S. patent application Ser. No. 12/029,634 filed Feb. 12, 2008, now U.S. Pat. No. 8,046,527, that claims the benefit of prior U.S. Provisional Patent Application No. 60/891,115 filed Feb. 22, 2007, the disclosures of which are hereby incorporated by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4174536 | Misunas et al. | Nov 1979 | A |
4617566 | Diamond | Oct 1986 | A |
4733376 | Ogawa | Mar 1988 | A |
4796231 | Pinkham | Jan 1989 | A |
4899316 | Nagami | Feb 1990 | A |
5038299 | Maeda | Aug 1991 | A |
5126808 | Montalvo et al. | Jun 1992 | A |
5132635 | Kennedy | Jul 1992 | A |
5136292 | Ishida | Aug 1992 | A |
5175819 | Le Ngoc et al. | Dec 1992 | A |
5204669 | Dorfe et al. | Apr 1993 | A |
5243703 | Farmwald et al. | Sep 1993 | A |
5249270 | Stewart et al. | Sep 1993 | A |
5280539 | Yeom et al. | Jan 1994 | A |
5319598 | Aralis et al. | Jun 1994 | A |
5365484 | Cleveland et al. | Nov 1994 | A |
5404460 | Thomsen et al. | Apr 1995 | A |
5430859 | Norman et al. | Jul 1995 | A |
5437018 | Kobayashi et al. | Jul 1995 | A |
5440694 | Nakajima | Aug 1995 | A |
5452259 | McLaury | Sep 1995 | A |
5473563 | Suh et al. | Dec 1995 | A |
5473566 | Rao | Dec 1995 | A |
5473577 | Miyake et al. | Dec 1995 | A |
5535357 | Moran et al. | Jul 1996 | A |
5596724 | Mullins et al. | Jan 1997 | A |
5602780 | Diem et al. | Feb 1997 | A |
5636342 | Jeffries | Jun 1997 | A |
5671178 | Park et al. | Sep 1997 | A |
5721840 | Soga | Feb 1998 | A |
5729683 | Le et al. | Mar 1998 | A |
5740379 | Hartwig | Apr 1998 | A |
5761146 | Yoo et al. | Jun 1998 | A |
5771199 | Lee | Jun 1998 | A |
5802006 | Ohta | Sep 1998 | A |
5802399 | Yumoto et al. | Sep 1998 | A |
5806070 | Norman et al. | Sep 1998 | A |
5818785 | Ohshima | Oct 1998 | A |
5828899 | Richard et al. | Oct 1998 | A |
5835935 | Estakhri et al. | Nov 1998 | A |
5859809 | Kim | Jan 1999 | A |
5860080 | James et al. | Jan 1999 | A |
5872994 | Akiyama et al. | Feb 1999 | A |
5937425 | Ban | Aug 1999 | A |
5941974 | Babin | Aug 1999 | A |
5959930 | Sakurai | Sep 1999 | A |
5995417 | Chen et al. | Nov 1999 | A |
6002638 | John | Dec 1999 | A |
6085290 | Smith et al. | Jul 2000 | A |
6091660 | Sasaki et al. | Jul 2000 | A |
6107658 | Itoh et al. | Aug 2000 | A |
6144576 | Leddige et al. | Nov 2000 | A |
6148363 | Lofgren et al. | Nov 2000 | A |
6148364 | Srinivasan et al. | Nov 2000 | A |
6178135 | Kang | Jan 2001 | B1 |
6208556 | Akaogi et al. | Mar 2001 | B1 |
6230233 | Lofgren et al. | May 2001 | B1 |
6295618 | Keeth | Sep 2001 | B1 |
6304921 | Rooke | Oct 2001 | B1 |
6317350 | Pereira et al. | Nov 2001 | B1 |
6317352 | Halbert et al. | Nov 2001 | B1 |
6317812 | Lofgren et al. | Nov 2001 | B1 |
6438064 | Ooishi | Aug 2002 | B2 |
6442098 | Kengeri | Aug 2002 | B1 |
6442644 | Gustavson et al. | Aug 2002 | B1 |
6453365 | Habot | Sep 2002 | B1 |
6456528 | Chen | Sep 2002 | B1 |
6535948 | Wheeler et al. | Mar 2003 | B1 |
6564285 | Mills et al. | May 2003 | B1 |
6584303 | Kingswood et al. | Jun 2003 | B1 |
6594183 | Lofgren et al. | Jul 2003 | B1 |
6601199 | Fukuda et al. | Jul 2003 | B1 |
6611466 | Lee et al. | Aug 2003 | B2 |
6643728 | Crutchfield et al. | Nov 2003 | B1 |
6658509 | Bonella et al. | Dec 2003 | B1 |
6658582 | Han | Dec 2003 | B1 |
6680904 | Kaplan et al. | Jan 2004 | B1 |
6697936 | Johnson | Feb 2004 | B2 |
6715044 | Lofgren et al. | Mar 2004 | B2 |
6717847 | Chen | Apr 2004 | B2 |
6732221 | Ban | May 2004 | B2 |
6754807 | Parthasarathy et al. | Jun 2004 | B1 |
6763426 | James et al. | Jul 2004 | B1 |
6788609 | Yamagami et al. | Sep 2004 | B2 |
6799235 | Bormann et al. | Sep 2004 | B2 |
6807103 | Cavaleri et al. | Oct 2004 | B2 |
6807106 | Gonzales et al. | Oct 2004 | B2 |
6816933 | Andreas | Nov 2004 | B1 |
6850443 | Lofgren et al. | Feb 2005 | B2 |
6853557 | Haba et al. | Feb 2005 | B1 |
6853573 | Kim et al. | Feb 2005 | B2 |
6928501 | Andreas et al. | Aug 2005 | B2 |
6944697 | Andreas | Sep 2005 | B2 |
6950325 | Chen | Sep 2005 | B1 |
6967874 | Hosono | Nov 2005 | B2 |
6978402 | Hirabayashi | Dec 2005 | B2 |
6988154 | Latta | Jan 2006 | B2 |
6996644 | Schoch et al. | Feb 2006 | B2 |
7031221 | Mooney et al. | Apr 2006 | B2 |
7032039 | DeCaro | Apr 2006 | B2 |
7062601 | Becca et al. | Jun 2006 | B2 |
7073010 | Chen et al. | Jul 2006 | B2 |
7073022 | El-Batal et al. | Jul 2006 | B2 |
7086785 | Bates, III | Aug 2006 | B1 |
7111085 | Estakhri et al. | Sep 2006 | B2 |
7111140 | Estakhri et al. | Sep 2006 | B2 |
7123541 | Bell et al. | Oct 2006 | B2 |
7130958 | Chou et al. | Oct 2006 | B2 |
7165153 | Vogt | Jan 2007 | B2 |
7190617 | Harari et al. | Mar 2007 | B1 |
7302517 | Lim et al. | Nov 2007 | B2 |
7308524 | Grundy et al. | Dec 2007 | B2 |
7356639 | Perego et al. | Apr 2008 | B2 |
7475174 | Chow et al. | Jan 2009 | B2 |
7496777 | Kapil | Feb 2009 | B2 |
7506098 | Arcedera et al. | Mar 2009 | B2 |
7515471 | Oh et al. | Apr 2009 | B2 |
7603534 | Roohparvar | Oct 2009 | B2 |
7631162 | Gorobets | Dec 2009 | B2 |
7650459 | Eilert et al. | Jan 2010 | B2 |
7652922 | Kim et al. | Jan 2010 | B2 |
7774537 | Pyeon et al. | Aug 2010 | B2 |
7853749 | Kolokowsky | Dec 2010 | B2 |
7908429 | Pyeon et al. | Mar 2011 | B2 |
8046527 | Pyeon et al. | Oct 2011 | B2 |
8060691 | Pyeon et al. | Nov 2011 | B2 |
8086785 | Pyeon et al. | Dec 2011 | B2 |
20010026487 | Koga | Oct 2001 | A1 |
20010045468 | Ikefuji | Nov 2001 | A1 |
20020124129 | Zilberman | Sep 2002 | A1 |
20020161941 | Chue et al. | Oct 2002 | A1 |
20020188781 | Schoch et al. | Dec 2002 | A1 |
20030009612 | Latta | Jan 2003 | A1 |
20030074505 | Andreas et al. | Apr 2003 | A1 |
20040001380 | Becca et al. | Jan 2004 | A1 |
20040019736 | Kim et al. | Jan 2004 | A1 |
20040024960 | King et al. | Feb 2004 | A1 |
20040039854 | Estakhri et al. | Feb 2004 | A1 |
20040148482 | Grundy et al. | Jul 2004 | A1 |
20040199721 | Chen | Oct 2004 | A1 |
20040230738 | Lim et al. | Nov 2004 | A1 |
20040230743 | Ware et al. | Nov 2004 | A1 |
20040256638 | Perego et al. | Dec 2004 | A1 |
20050028057 | Briggs | Feb 2005 | A1 |
20050120157 | Chen et al. | Jun 2005 | A1 |
20050120163 | Chou et al. | Jun 2005 | A1 |
20050160218 | See et al. | Jul 2005 | A1 |
20050166006 | Talbot et al. | Jul 2005 | A1 |
20050207232 | Delfs et al. | Sep 2005 | A1 |
20050213421 | Polizzi et al. | Sep 2005 | A1 |
20050286298 | Hyvonen et al. | Dec 2005 | A1 |
20050289313 | Roohparvar | Dec 2005 | A1 |
20060031593 | Sinclair | Feb 2006 | A1 |
20060050594 | Park | Mar 2006 | A1 |
20060198202 | Erez | Sep 2006 | A1 |
20060224789 | Cho et al. | Oct 2006 | A1 |
20060271605 | Petruzzo | Nov 2006 | A1 |
20070050536 | Kolokowsky | Mar 2007 | A1 |
20070076479 | Kim et al. | Apr 2007 | A1 |
20070076502 | Pyeon et al. | Apr 2007 | A1 |
20070083701 | Kapil | Apr 2007 | A1 |
20070101096 | Gorobets | May 2007 | A1 |
20070109833 | Pyeon et al. | May 2007 | A1 |
20070153576 | Oh et al. | Jul 2007 | A1 |
20070177436 | Davis et al. | Aug 2007 | A1 |
20070233903 | Pyeon | Oct 2007 | A1 |
20070233917 | Pyeon et al. | Oct 2007 | A1 |
20070234071 | Pyeon | Oct 2007 | A1 |
20070288686 | Arcedera et al. | Dec 2007 | A1 |
20080016269 | Chow et al. | Jan 2008 | A1 |
20080028176 | Bartley et al. | Jan 2008 | A1 |
20080049505 | Kim et al. | Feb 2008 | A1 |
20080052449 | Kim et al. | Feb 2008 | A1 |
20080140899 | Oh et al. | Jun 2008 | A1 |
20080155207 | Eilert et al. | Jun 2008 | A1 |
20080205168 | Pyeon et al. | Aug 2008 | A1 |
20100054069 | Shiota et al. | Mar 2010 | A1 |
20100275056 | Pyeon et al. | Oct 2010 | A1 |
20110314206 | Pyeon et al. | Dec 2011 | A1 |
Number | Date | Country |
---|---|---|
1314625 | Sep 2001 | CN |
0952525 | Oct 1999 | EP |
2217056 | Oct 1989 | GB |
04167039 | Jun 1992 | JP |
07014392 | Jan 1995 | JP |
10187549 | Jul 1998 | JP |
2000315185 | Nov 2000 | JP |
200641602 | Dec 2006 | TW |
200707189 | Feb 2007 | TW |
0169411 | Sep 2001 | WO |
0169411 | Sep 2001 | WO |
2005069150 | Jul 2005 | WO |
PCTCA2007001428 | Dec 2007 | WO |
PCTCA2008000250 | Jun 2008 | WO |
2008098349 | Aug 2008 | WO |
PCTCA2008000219 | Aug 2008 | WO |
Entry |
---|
64 Megabit CMOS 3.0 Volt Flash Memory with 50MHz SPI. Spansion, pp. 1-22 (2006). |
M-Systems Flash Disk Pioneers LTD., “DiskOnChip H1 4Gb (512MByte) and 8Gb (1 GByte) High Capacity Flash Disk with NAND and x2 Technology”, Data Sheet, Rev. 0.5 (Preliminary), pp. 1-66,2005. |
Tal, A., “Guidelines for Integrating DiskOnChip in a Host System”, AP-DOC-1004, Rev. 1.0, M-Systems Flash Pioneers Ltd., pp. 1-15,2004. |
Samsung Electronics Co. L To, OneNAND4G(KFW4G16Q2M-DEB6), OneNAND2G(KFH2G16Q2M-DEB6), OneNAND1 G(KFW1 G16Q2M-DEB6) Flash Memory, OneNANDTM Specification Ver. 1.2, pp. 1-125 Dec. 23, 2005. |
Kennedy, J., et al., “A 2Gb/s Point-to-Point Heterogeneous Voltage Capable DRAM Interface for Capacity-Scalable 5 Memory Subsystems”, ISSCC 2004/Session 1IDRAM/11.S, IEEE International Solid-State Circuits Conference, Feb. 15-19, 2004, vol. 1, pp. 214-523. |
Kim, Jae-Kwan, et al., “A 3.6Gb/s/pin Simultaneous Bidirectional (SBD) 110 Interface for High-Speed DRAM”, ISSCC 6 2004/Session 22/DSL and Multi-Gb/s 11022.7, IEEE International Solid-State Circuits Conference Feb. 15-19, 2004 vol. 1, pp. 414-415. |
“HyperTransport TM 110 Link Specification”, Revision 2.00, Document No. HTC20031217-0036-00, Hypertransport Technology Consortium, pp. 1-325,2001. |
Oshima, et ai., “High-Speed Memory Architectures for Multimedia Applications”, Circuits & Devices, IEEE 8755-3996/97, pp. 8-13, Jan. 1997. |
Gjessing, S., et al., “Ram Link: A High-Bandwidth Point-to-Point Memory Architecture”, Proceedings CompCom 1992, IEEE 0/8186-2655-0/92, pp. 328-331, Feb. 24-2S, 1992. |
Gjessing. S., et al., “Performance of the Ram Link Memory Architecture”, Proceedings of the Twenty-Seventh Annual Hawaii International Conference on System Sciences, IEEE 1060-3425/94, pp. 154-162, Jan. 1994. |
Gjessing. S., et al., “A RAM Link for High Speed”, Special ReportlMemory, IEEE Spectrum, pp. 52-53, Oct. 1992. |
Diamond, S.L., “SyncLink: High: High-speed DRAM for the Future”, Micro Standards, IEEE Micro, pp. 74-75, Dec. 1996. |
“HyperTransport TM 1/0 Link Specification”, Revision 3.00, Document No. HTC20051222-0046-0008, Hypertransport Technology Consortium, pp. 1-428, Apr. 2006. |
Samsung Electronics, “DDR2 Fully Buffered DIMM 240pin FBDIMMS based on 512Mb C-die” Rev. 1.3, Sep. 2006, pp. 1-32, Sep. 2006. |
“HyperTransport TM 1/0 Link Specification”, Revision 3.00, Document No. HTC20051 222-0046-0008, Hypertransport Technology Consortium, pp. 1-428, Apr. 2006. |
Intel Corporation, “Intel®Advanced+ Boot Block Flash Memory (C3)”, May 2005, pp. 1-72. |
AMTEL Corp., “High Speed Small Sectored SPI Flash Memory”, pp. 1-22,2006. |
Hara, T. et al., “A 146mm2 8Gb NAND Flash Memory with 70nm CMOS Technology”, ISSCC Session 2 Non-Volatile Memory 2.1, IEEE International Solid-State Circuits Conference, Feb. 2005, pp. 44, 45 and 584. |
Byeon, D. et al., “An 8Gb Multi-Level NAND Flash Memory with 63nm STI CMOS Process Technology”, ISSCC Session 2 Non-Volatile Memory 2.2, IEEE International Solid-State Circuits Conference, Feb. 2005, pp. 46 and 47. |
Tanzawa, T. et al., “Circuit Techniques for a 1.8-V-Only NAND Flash Memory”, IEEE Journal of Solid-State Circuits, vol. 37, No. 1, Jan. 2002, pp. 84-89. |
Saito, et al., “A Programmable 80ns 1Mb CMOS EPROM”, IEEE ISSCC Digest ofTechnical Papers, Feb. 14, 1985, pp. 176-177, 340. |
Momodomi, M. et al., “A 4 Mb NAND EEPROM with tight programmed Vt Distribution”, IEEE Journal of Solid-State Circuits, vol. 26, Issue 4, Apr. 1991, pp. 492-496. |
Ohtsuka, N. et al., “A 4-Mbit CMOS EPROM”, IEEE Journal of Solid-State Circuits, vol. 22, Issue 5, Oct. 1987, pp. 669-675. |
Kim, et al. “A 120-mm2 64 Mb NAND Flash Memory Archieving 180 ns/Byte Effective Program Speed,” IEEE Journal of Solid-State Circuits, vol. 32, No. 5, May 1977, pp. 670-680. |
Suh, K. et al., “A 3.3 V 32 Mb NAND Flash Memory with Incremental Step Pulse Programming Scheme”, IEEE Journal of Solid-State Circuits, vol. 30, No. 11, Nov. 1995, pp. 1149-1156. |
Takeuchi, K. et al., “A multipage cell architecture for high-speed programming multilevelNAND flash memories”, IEEE Journal of Solid-State Circuits, vol. 33, Issue 8, Aug. 1998, pp. 1228-1238. |
Tanzawa, et al., “A dynamic analysis of the Dickson charge pump circuit;” IEEE J. Solid-State Circuits, vol. 32, No. 8, pp. 1231-1240, Aug. 1997. |
Tanaka, T. et al., “A quick intelligent page-programming architecture and a shieldedbitline sensing method for 3 Vonly NAND flash memory”, IEEE Journal of Solid-state Circuits, vol. 29, Issue 11, Nov. 1994, pp. 1366-1373. |
Imamiya, K. et al., “A 125-mm2 1-Gb NAND Flash Memory with 10-MByte/s Program Speed”, IEEE Journal of Solid-State Circuits, vol. 37, No. 11, Nov. 2002, pp. 1493-1501. |
Lee, J. et al., “High-Performance 1-Gb NAND Flash Memory with 0.12-om Technology”, IEEE Journal of Solid-State Circuits, vol. 37, No. 11, Nov. 2002, pp. 1502-1509. |
Jung, T. et al., “A 117-mm2 3.3-V Only 128-Mb Multilevel NAND Flash Memory for Mass Storage Applications,” IEEE Journal of Solid-State Circuits, vol. 31, No. 11, Nov. 1996, pp. 1575-1583. |
Tomita, N. et al., “A 62-ns 16Mb CMOS EPROMm with Voltage Stress Relaxation Technique” IEEE Journal of Solid-State Circuits vol. 26, No. 11, Nov. 1991, pp. 1593-1599. |
Cho, T. et al., “A Dual Mode NAND Flash Memory: 1-Gb Multilevel and High-Performance 512-Mb Single-Level Modes”, IEEE Journal of Solid-State Circuits, vol. 36, No. 11, Nov. 2001, pp. 1700-1706. |
Kirisawa, R. et al., “A NAND Structured Cell with a new Programming Technology for Highly Reliable 5V-Only Flash EEPROM”, 1990 Symposium on VLSI Technology, Jun. 4, 1990, CH 2874-6, 90/0000-0129 1990 IEEE, Honolulu, US, pp. 129-130. |
Aritome, S. et al., “A Reliable Bi-Polarity Write/Erase Technology in Flash EEPROMS”, Inn Electron Devices Meeting, 1990, Technical Digest, Dec. 9-12, 1990, pp. 111-114. |
Shirota, R., et al., “A 2.3um2 Memory Cell Structure for 16Mb NAND EEPROMs”, International Electron Devices Meeting 1990, Technical Digest, (1990), pp. 103-106. |
Hara, T. et al., “A 146-mmA2 8-Gb Multi-Level NAND Flash Memory With 70-nm CMOS Technology”, IEEE Journal of Solid State Circuits, Jan. 2006, vol. 41, No. 1, pp. 161-169. |
Lee, S. et al., “A 3.3V 4Gb Four-Level NAND Flash Memory with 90nm CMOS Technology”, ISSCC 2004/Session 2 Non-Volatile Memory/2.7, IEEE International Solid-State Circuits Conference, Feb. 15-19, 2004,Digest of Technical Papers, pp. 52-513, vol. 1 , XP010722148, ISBN: 0-7803-8267-6. |
Takeuchi, K. et al, “A 56nm CMOS 99mm2 8Gb Multi-level NAND Flash Memory with 10MB/s Program Throughput”, Solid-State Circuits, 2006 IEEE International Conference Digest of Technical Papers, Feb. 6-9, 2006, ISBN: 1-4244-0079-1. |
Samsung Electronics Co. Ltd, “256M×8 BitI128 M×16 BitI512M×8 Bit NAND Flash Memory”, K9K4G08U1M, May 6, 2005, pp. 1-41. |
Samsung Electronics Co. Ltd, “1G×8 BitI1G×8 Bit NAND Flash Memory”, K9F8G08UXM, May 31, 2007, pp. 1-54. |
Samsung Electronics Co. Ltd, “512M×8 BitI1G×8 Bit NAND Flash Memory”, K9XXG08UXA, May 7, 2006, pp. 1-43. |
Samsung Electronics Co. Ltd, “1G×8 BitI2G×8 BitI4G×8 Bit NAND Flash Memory”, K9XXG08UXA, Jul. 18, 2006, pp. 1-50. |
Choi, Young, “16-Gbit MLC NAND Flash Weighs In”, EETimes.com, Jul. 7, 2007, pp. 1-3, http://www.eetimes.com/showArticle.jhtml?articleID=201200825. |
Gal, et al., “Algorithms and data structures for ftash memories”, ACM Computing Surveys (CSUR), vol. 37, No. 2, p. 138-163, Jun. 2005, Tel Aviv University. |
Lee J. et al., “A 90-nm CMOS 1.8-V 2Gb NAND Flash Memory for Mass Storage Applications”, IEEE Journal of Solid-State Circuits, vol. 38, No. 11, Nov. 2003. pp. 1934-1942. |
Samsung Electronics Co. Ltd, “2G×8 Bit NAND Flash Memory”, K9GAG08UOM, Apr. 12, 2006, pp. 1-48. |
Toshiba, “16 GBIT (2G×8 Bit) CMOS NAND E2PROM (Multi-Level-Cell)”, TC58NVG4D1 DTGOO, Nov. 9, 2006. |
Toshiba, “2GB IT (256M×8 Bits) CMOS NAND E2PROM”, TH58NVG1S3AFT05, May 19, 2003. |
IEEE Standard for High-Bandwidth Memory Interface Based on Scalable Coherent Interface (SCI) Signaling Technology (RAMLINK), IEEE STD. 1596.4-1996, The Institute of Electrical Electronics Engineers, Inc., pp. 1-91, (Mar. 1996). |
“K9XXG08UXM Preliminary Flash Memory” Technical Specification, 1-43, May 3, 2005. |
King, Craig, L. et al, Communicating With Daisy Chained MCP42XXX Digital Potentiometers Microchip AN747, 1-8, Jan. 30, 2001. |
“S70GL01GN00 Mirrobit Flash 1024 Megabit, 3.0 Volt-Only Page Mode Flash Memory Featuring 110 NM Mirrorbit Process Technology”, 1-83, Jun. 1, 2005. |
“2 MBIT Low Voltage Serial Flash Memory With 40MHZ SPI Bus Interface”, 1-40, Aug. 1, 2004. |
8-Megabit 2.5 Volt Only or 2.7-Volt Only Data Flash, Technical Specification, Rev. 2225H-DFLSH-10-2004, AT45DB081B, 1-33, Oct. 1, 2004. |
16 MBIT SPI Serial Flash, SST25VF016B, Preliminary Specification, Silicon Storage Technology Inc., 1-28, Apr. 1, 2005. |
High Speed Small Sectored SPI Flash Memory 4M (524,288*8) AT25FS040 Advance Information, 1-23, Sep. 1, 2006. |
Ziaie, Kazem, “International Patent Application No. PCT/CA2007/001428, Search Report”, 1-2, Dec. 6, 2007. |
Czarik, Damien, “European Search Report for European Patent 07800456.1” Jul. 7, 2009, 1-7, Jul. 1, 2009. |
Inoue, Atsushi et al, NAND Flash Applications Design Guide, System Solutions From Toshiba America Electronic Components, Inc., Revision 1.0, 1-29, Apr. 1, 2003. |
Ziaie, Kazem, “International Patent Application No. PCT/US2008/000250, Search Report”, 49-50, Jun. 10, 2008. |
Tung, Thomas KC, “International Patent Application No. PCT/CA2008/000219, Search Report”, 1-2, May 8, 2008. |
Ziaie, Kazem, “International Patent Application No. PCT/CA2007/001428, Search Report”, 62-63, Dec. 6, 2007. |
Diamond, Steven L., Synclink: High-Speed DRAM for the Future, Micro Standards, IEEE MICRO, Dec. 1996, 74-75. |
Samsung Electronics Co. Ltd., 1G×8 Bit/2G×8 Bit NAND Flash Memory, K9F8G08UXM, Technical Specification, 1-54, Mar. 31, 2007. |
Diamond, Steven L., “Synclink: High-Speed Dram for the Future”, Micro Standards, IEEE MICRO, Dec. 1996, 74-75. |
Number | Date | Country | |
---|---|---|---|
20110314206 A1 | Dec 2011 | US |
Number | Date | Country | |
---|---|---|---|
60891115 | Feb 2007 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12029634 | Feb 2008 | US |
Child | 13215789 | US |