A method is provided for using a multi-level cell memory device. The method includes writing first data to a first portion of a memory array using a first number of state levels for memory cells of the first portion of the memory array. The method further includes re-writing second data to a second portion of the memory array using a second number of state levels for memory cells of the second portion of the memory array. The second number is different from the first number.
|
1. A method of using a multi-level cell memory device, the method comprising:
responsive to a first instruction, writing first data to a first portion of a memory array using a first number of threshold voltage values corresponding to a respective first number of states, wherein the first instruction includes a first operating parameter indicating particular values of the first number of threshold voltage values; and
responsive to a second instruction, writing second data to a second portion of the memory array using a second number of threshold voltage values corresponding to a respective second number of states, wherein the second instruction includes a second operating parameter indicating particular values of the second number of threshold values, and wherein the second number of states is different from the first number of states.
10. A memory device comprising:
a plurality of multi-level memory cells; and
circuitry to:
responsive to a first instruction, write first data to a first portion of a memory array using a first number of threshold voltage values corresponding to a respective first number of states, wherein the first instruction includes a first operating parameter indicating particular values of the first number of threshold voltage values; and
responsive to a second instruction, write second data to a second portion of the memory array using a second number of threshold voltage values corresponding to a respective second number of states, wherein the second instruction includes a second operating parameter indicating particular values of the second number of threshold values, wherein the second number of states is different from the first number of states.
15. A memory system comprising:
a memory device comprising a plurality of multi-level memory cells and a memory controller to:
responsive to a first instruction, write first data to a first portion of a memory array using a first number of threshold voltage values corresponding to a respective first number of states, wherein the first instruction includes a first operating parameter indicating particular values of the first threshold voltage values;
responsive to a second instruction, write second data to a second portion of the memory array using a second number of threshold voltage values corresponding to a respective second number of states, wherein the second instruction includes a second operating parameter indicating particular values of the second number of threshold values, and wherein the second number of states is different from the first number of states; and
a processor configured to provide access to the plurality of multi-level memory cells.
2. The method of
3. The method of
reading the first data from the first portion of the memory array in response to receiving a third instruction comprising a first read command and at least the first operating parameter; and
reading the second data from the second portion of the memory array in response to receiving a fourth instruction comprising a second read command and at least the second operating parameter.
4. The method of
5. The method of
6. The method of
7. The method of
8. The method of
9. The method of
11. The memory device of
12. The memory device of
reads the first data from the first portion of the memory array in response to receiving a third instruction comprising a first read command and at least the first operating parameter; and
reads the second data from the second portion of the memory array in response to receiving a fourth instruction comprising a second read command and at least the second operating parameter.
13. The memory device of
14. The memory device of
16. The memory system of
17. The memory system of
reads the first data from the first portion of the memory array in response to receiving a third instruction comprising a first read command and at least the first operating parameter; and
reads the second data from the second portion of the memory array in response to receiving a fourth instruction comprising a second read command and at least the second operating parameter.
18. The memory system of
19. The memory system of
|
This application is a continuation of U.S. patent application Ser. No. 14/283,117, filed May 20, 2014 and incorporated in its entirety by reference herein, which is a divisional of U.S. patent application Ser. No. 13/770,881, filed Feb. 19, 2013 and incorporated in its entirety by reference herein, which is a continuation of U.S. patent application Ser. No. 12/949,728, filed Nov. 18, 2010 and incorporated in its entirety by reference herein.
1. Field
Subject matter disclosed herein relates to techniques to operate memory.
2. Information
Memory devices are employed in many types of electronic devices, such as computers, cell phones, PDA's, data loggers, and navigational equipment, just to name a few examples. Among such electronic devices, various types of nonvolatile memory devices may be employed, such as NAND or NOR flash memories, SRAM, DRAM, and phase-change memory, just to name a few examples. In general, writing or programming operations may be used to store information in such memory devices, while a read operation may be used to retrieve stored information.
Parameters with which a memory operates may be established by a manufacturer of the memory. For example, such parameters may include current, voltage, and/or resistance reference values for memory operations such as read, program, erase, verify, and so on.
Non-limiting and non-exhaustive embodiments will be described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of claimed subject matter. Thus, the appearances of the phrase “in one embodiment” or “an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in one or more embodiments.
In an embodiment, a technique for operating a memory device may involve a memory instruction directed to the memory device that includes an operating parameter to affect a physical operating condition of the memory device. In particular, such an operating parameter may affect a physical operating condition of peripheral circuitry in a memory device. Peripheral circuitry internal to a memory device, for example, may comprise one or more power sources, sense amplifier circuitry, timing circuitry (e.g., a clock circuit), row/column decoders, and other such circuitry exclusive of an array of memory cells. Inclusion of such an operating parameter in a memory instruction may provide an opportunity for a user of the memory device to selectively manage such physical operating conditions of the memory device. For example, decreasing a margin between logic levels of a multilevel memory device (e.g., resulting in increased storage capacity at the expense of decreased precision) may be beneficial to a user for one application while increasing such a margin (e.g., resulting in increased precision at the expense of decreased storage capacity) may be beneficial for another application. In an example, applying a memory instruction READ, which includes an address and an operating parameter VREAD, may result in 1 or 0 depending on a threshold voltage being lower or higher than operating parameter value VREAD, respectively. An ability of a user to use other operating parameters may affect reliability and/or performance of a memory device and/or memory device characteristics such as write speed, adjustable margin with respect to program/read levels, number of levels stored in any memory cell, data encryption, and so on. A value of such an operating parameter may be selected by a user and/or instructions executed by a processor, for example. According to a communication protocol of a memory device, in an embodiment, specific bits of instruction code may be devoted to operating parameter information. For example, in a parallel device specific input/output terminals may receive/send the operating parameter's bits. However, in the case of a serial device such information may be input/output during pre-defined clock cycles in an instruction sequence, for example. A mixed serial-parallel protocol may be used in some cases to input an instruction including an operating parameter at memory pins. In one implementation, a physical operating condition used during execution of a command may assume one among a pre-defined set of possible values depending, at least in part, on corresponding information provided with the operating parameter. Such a correspondence may be established by a look-up table, for example.
A memory device that may be operated using a memory instruction as described above may comprise volatile or nonvolatile memory including flash NAND, flash NOR, phase change memory (PCM), single level cell (SLC) memory, multilevel cell (MLC) memory, and so on. In particular, an instruction directed to a memory device may comprise a number of elements including a command such as a read command, a write or program command, an erase command, and so on. Such elements of an instruction may also include an address of a location in a memory array of the memory device to where data is to be written or from where data is to be read, for example. Accordingly, an instruction to write to a memory array may also comprise such data. In addition to such elements of an instruction (e.g., a command, address, data, and so on), such an instruction may additionally include one or more operating parameters to be used during execution of the instruction and/or subsequent instructions, as explained in detail below. Such operating parameters may comprise a voltage reference level of a memory cell in a memory array, a margin between or among logic levels of the memory cell, or a ramp speed of a bias signal to be applied to the memory cell, just to name a few examples. In one implementation, the memory device may perform the instruction including interpreting the operating parameter, generating one or more physical quantities that correspond to the operating parameter, and applying the one or more physical quantities to appropriate nodes/circuits of the memory device.
In one embodiment, such an operating parameter included in a memory instruction may be received by a memory device as a digital or analog value or as a code to be interpreted by the memory device to determine one or more physical operating conditions and/or operating modes of the memory device. Such a memory device may include a parameter management block used to perform a memory instruction by interpreting operating parameters and affecting operating conditions of peripheral circuitry in the memory device corresponding to the operating parameters, as described in further detail below.
In one embodiment, an operating parameter included in a memory instruction may be used to program memory cells, e.g., modify the program cells' threshold voltage, to a level specified by the operating parameter; this may be achieved by affecting a physical operating condition used in a program verification phase to end the program operation. For example, such an operating parameter may be used to set the threshold voltage reference value to a desired value corresponding to the input operating parameter. In a similar fashion, an operating parameter included in a memory read instruction may be used to retrieve data previously stored at a memory address under specific physical operating conditions, such as a wordline read voltage, specified by the operating parameter. Among other advantages, a user may benefit from the operations described above because, being the only one aware of the programming conditions, a user may also be the only one able to correctly retrieve the stored data at a later time, as it will be explained below.
In one embodiment, such an operating parameter included in a memory instruction may be useful during a process of bit manipulation. Bit manipulation may be used if writing data in a page of memory is to be performed in different steps or stages. In such cases, additional bits are to be programmed on pages of memory already partly programmed. For example, bit manipulation may be used for partial programming, such as during testing various functions or operations of a computing system, wherein additional programming may be performed at a later time (e.g., during further testing). In another example, bit manipulation may be used by a user to personalize or customize a memory device. In such a case, data and/or code may be only partially loaded into the memory device by the manufacturer at the end of a fabrication process before shipment, and the user may subsequently insert additional information (e.g., passwords, code, and so on) to increase security, for example. In yet another example, bit manipulation may be used in situations where data is to be relatively frequently changed (e.g., in a region of memory maintaining headers or in a File Allocation Table pointing to the memory and representing an internal organization of the memory). In such a case, bit manipulation may provide an opportunity to avoid erasure of and/or re-programming an entire block of memory. Of course, such details of techniques to operate a memory device using an operating parameter are merely examples, and claimed subject matter is not so limited.
Bit manipulation may or may not involve error correction code (ECC) for intermediate stages of the bit manipulation process. In one implementation, ECC may be computed and programmed only after complete data have been stored (e.g., at the end of a bit manipulation process). In such a case, however, a first portion of data may not be ECC protected, resulting in a risk of error during data read-out at intermediate stages (and consequent mistakes in ECC computation at later stages of the bit manipulation process). In contrast, if a first portion of data resulting from an early stage of a bit manipulation process is to be ECC protected, additional memory cells may be provided to store ECC during such an early stage of the bit manipulation process. Such additional memory cells may be an undesirable additional cost if it is not possible to write “1” over “0” in memory without erasing a whole block of memory, for example. As discussed in detail below, an operating parameter included in a memory instruction may be useful for bit manipulation and ECC processes. Of course, such details of bit manipulation are merely examples, and claimed subject matter is not so limited.
Though embodiments described herein include memory instructions comprising one or more operating parameters (e.g., operating parameters comprising input information), operating parameters may also comprise information that is a result of an execution of a command (e.g., operating parameters comprising output information). Such one or more operating parameters may also accompany results of an execution of a command. For example, one or more operating parameters may accompany read data resulting from execution of a read command. In an implementation, an operating parameter may represent a read voltage at which an operation was carried out.
In an embodiment, upon receiving a memory instruction that includes a command and operating parameter information, microcontroller 135 may interpret the command and use the operating parameter information to execute the memory instruction. To list a few examples, such an operating parameter may represent a voltage, such as a wordline (WL) read voltage, a WL program voltage, a WL verification voltage, a voltage difference, a voltage margin with respect to a pre-defined value (e.g., as used in a program verify operation), and/or a voltage step during a program/erase ramp. However, such an operating parameter may also represent a current value (e.g., for use in flash or floating gate memories) or other physical quantity, such as a resistance value (e.g., for use in PCM), or a time duration or delay, such as, for example, a lapse of time between a bitline pre-charging and a bitline sensing in a NAND memory. In one implementation, such an operating parameter may comprise a code corresponding to one among a pre-defined set of allowed values for a particular quantity (depending on the command to which the operating parameter refers). For example, one of sixteen possible voltage (or current, or resistance, etc.) levels may be chosen according to the value of a four-bit parameter code. In another implementation, such an operating parameter may comprise a combination of a code and a value. For example, during a program operation it may be possible to select a value for verification voltage (specified by code 1), or for margin (code 2) with respect to a pre-defined verification voltage, or a voltage step amplitude (code 3), or a step duration (code 4) to be used in a programming voltage ramp. Correspondingly, the code-value combination may result in the specified one among the possible physical operating conditions being affected by the value of the operating parameter.
In an embodiment, upon receiving operating parameter information via port 155, operating parameter management block 150 may internally generate a physical quantity corresponding to the operating parameter information. For example, in one implementation, operating parameter management block 150 may include a voltage (or current) generator to generate a voltage (or current) with a specified precision that corresponds to the operating parameter information. Such a physical quantity may be applied to relevant circuit portions, such as a wordline in memory array 120, timing circuitry (not shown), and so on.
TABLE 1 illustrates an example of an instruction set comprising a number of memory instructions including WRITE ENABLE, READ, PAGE PROGRAM, SECTOR ERASE, and CHIP ERASE. Each such memory instruction may be represented by an instruction code; it may also include an address, operating parameter(s), and data, as described above. A dummy portion, which may be useful in some applications, may also be included.
TABLE 1
One-byte
Descrip-
instruction
Address
Parameter
Dummy
Data
Instruction
tion
code
bytes
bytes
bytes
bytes
WREN
Write
06h
0
0
0
0
Enable
READ
Read
03h
3
1
0
1 to ∞
Data
Bytes
PP
Page
02h
3
2
0
1 to 256
Program
SE
Sector
D8h
2
1
0
0
Erase
CE
Chip
60h
0
3
0
0
Erase
or C7h
For example, WRITE ENABLE memory instruction may be represented by a one-byte hexadecimal code 06, READ memory instruction by 03, PAGE PROGRAM memory instruction by 02, and SECTOR ERASE memory instruction by D8 and CHIP ERASE memory instruction by 60 or C7. READ memory instruction may include a three-byte address and a one-byte operating parameter code, which may comprise a wordline read voltage, for example. PAGE PROGRAM memory instruction may include a three-byte address and a two-byte operating parameter code, which may comprise two different parameters. One parameter may comprise an encryption encoding scheme and the other parameter may comprise a program verify (WL) voltage, for example. SECTOR ERASE memory instruction may include a two-byte address and a one-byte operating parameter code, which may represent a voltage step (or step duration) in an erase voltage ramp. CHIP ERASE memory instruction may include three one-byte operating parameter codes, which may represent a reference current level, a wordline read voltage, and/or a well or body read voltage to be used in verifying the memory cells during an erase operation of the entire memory, for example. Of course, such details are merely examples, and claimed subject matter is not so limited.
In an embodiment, operating parameters included in a memory instruction may be used to select, for example, one or more threshold voltage values of a MLC memory device. As mentioned above, such operating parameters may be user-selectable. Though such MLC memory devices may have been manufactured to have substantially the same electrical and/or operating characteristics as one another, various operating conditions, such as threshold voltage reference values, may be modified differently for different MLC memory devices, subsequent to such user selection of operating parameters. For example, threshold voltage reference values α, β, γ, δ, η, φ may be established in response to a user selecting particular operating parameters in a memory instruction to program the MLC memory device. As mentioned above, an operating parameter may comprise a code comprising a set of pre-defined values representing a physical quantity associated with the parameter. For example, for a three-bit parameter, bits 001 may correspond to 0 volts, 010 may correspond to a volts, 011 may correspond to β volts, 100 may correspond to γ volts, 101 may correspond to δ volts, 110 may correspond to η volts, and 111 may correspond to φ volts, though claimed subject matter is not so limited. Such an opportunity for a user to select threshold reference voltage values may lead to customization of the MLC memory device for particular application requirements of a user, for example. Also, such an opportunity for a user to select threshold reference voltage values may include implementation of password protection of data stored in the MLC memory. For example, only a user having knowledge of threshold voltage values used to write particular data into the MLC memory device may subsequently be able to read the particular data (using the threshold voltage reference values used during program operation). In an implementation, a threshold voltage value VT need not have a unique logic value associated with it. For example, α<VT<β may represent a “0” with respect to α, but α<VT<β may represent a “1” with respect to β. In such a case, for example, only the user may know with respect to which reference level a read operation should be performed at any particular address. Accordingly, only the user may be able to retrieve the correct datum (e.g., whether a memory cell at a particular address was programmed with α<VT<β to mean “0” or “1”). It may therefore be possible for the user to define and establish encoding schemes suitable for encryption. For example, the user may freely assign logical values to threshold voltage ranges measured with respect to particular reference levels in the bit position in the byte or word. At read-out the correct parameter code(s) may be input in order to retrieve meaningful data. In a particular implementation, to increase security of stored data, read data may be considered valid only if such data falls within a specified range, which may only be known to a user. Such ranges, for example, may comprise read data between α and δ, between β and φ, or between γ and η. Also, by selecting one or more operating parameters in a memory instruction, a user may define different logic values (e.g., “0” or “1”) in different threshold voltage ranges. For example, “1” may be represented by VT<α or γ<VT<δ, and “0” may be represented by α<VT<γ or δ<VT<φ. In one implementation, threshold voltage values α, β, γ, δ, η, φ may be stored in the MLC memory device to be used as a “key” to read the particular data. Moreover, it is noted that correspondence between logic values and threshold voltage ranges may be independently defined for different portions of the memory array, resulting in still further increased flexibility and security. Of course, such details of operating parameters are merely examples, and claimed subject matter is not so limited.
In an embodiment, a varying amount of information may be stored in a memory array by redefining (e.g., for individual memory cells of the memory array) a number of allowed state levels during a program operation to write data to the memory array. Subsequently, such data may be read based on a defined number of allowed state levels. For example, a portion of memory cells in a memory array may comprise two-level (1 bit) encoding memory cells, another portion of memory cells may comprise three-level (1.5 bits) encoding memory cells, yet another portion of memory cells may comprise four-level (2 bits) encoding memory cells, and so on. In this case, using
In an embodiment, during a process of bit manipulation, described above, logic content of multi-level memory cells may be defined so as to allow for overwriting “1” onto “0” in the memory. For example, a user, being aware of pending steps in a bit manipulation process, may use different operating parameters to access (e.g., program or read) multi-level memory cells so that different allowed threshold voltage ranges may be associated with logical values stored therein. Returning to
During a second program operation of the bit manipulation process, additional bits may be programmed, which may result in ECC bits being subject to change, including otherwise forbidden “0” to “1” transitions. A user may select (via one or more operating parameters in a memory instruction) two VT distributions different from the VT distributions used in the first program operation described above. Thus, for example, “1” may be stored using VT distribution 240 and “0” may be stored using VT distribution 270. Previously programmed data may be copied from distribution 210 to distribution 240 and from distribution 220 to distribution 270, to maintain consistency in the association between threshold voltage ranges and logical values. Programming a “0” may be carried out by providing an instruction that comprises a program command, an address, data, and a first operating parameter and a second operating parameter. The first operating parameter may comprise a wordline program verify level for an “erased” state (e.g., VT=γ in
The following example describes a particular process of bit manipulation involving ECC, according to an embodiment. Such a process of bit manipulation may include more than two program operations. In the case of the following example, a process of bit manipulation includes three program operations. In a first program operation, a portion of data may be written to a page. In the first program operation, a user may select (via one or more operating parameters in a memory instruction) two lowest VT distributions (target distributions) 210 and 220 to store the data. For example, “1” may be stored using VT distribution 210 and “0” may be stored using VT distribution 220 (un-programmed data may remain in a “1” state). As explained above, programming a “0” may be carried out by providing an instruction that comprises a program command, an address, data, and an operating parameter that represents a wordline program verify level, such as VT=α in
During a second program operation of a bit manipulation process, target VT distributions (e.g., selected by a user via operating parameters) may comprise the VT distribution 220, which may represent a “0” for already-programmed data that are not changed (e.g., writing “0” onto “0”) and for newly programmed data (e.g., writing “0” onto “1”). Also, another target VT distribution may comprise the VT distribution 240, which may represent a “1” for already-programmed data that are not changed (e.g., writing “1” onto “1”) and for newly programmed data (e.g., writing “1” onto “0”). In such a case, an operating parameter included in a memory instruction may represent a program-verify voltage for “1” (e.g., γ). Also in such a case, in the second program operation, “0” may be associated with a lower threshold voltage than that of “1”. Accordingly, such data may be read from pages of memory subject to bit manipulation by using an instruction that comprises a read command, an address, and an operating parameter that represents a wordline read voltage, such as VT=γ, for example.
During a third program operation of a bit manipulation process, target VT distributions (e.g., selected by a user via operating parameters) may comprise the VT distribution 240, which may represent a “1” for already-programmed data that are not changed (e.g., writing “1” onto “1”) and for newly programmed data (e.g., writing “1” onto “0”). Also, another target VT distribution may comprise the VT distribution 270, which may represent a “0” for already-programmed data that are not changed (e.g., writing “0” onto “0”) and for newly programmed data (e.g., writing “0” onto “1”). In such a case, an operating parameter included in a memory instruction may represent a program-verify voltage for “0” (e.g., φ). Also in such a case, in the third program operation, “1” may be associated with a lower threshold voltage than that of “0”. Accordingly, such data may be read from pages of memory subject to bit manipulation by using an instruction that comprises a read command, an address, and an operating parameter that represents a wordline read voltage, such as VT=φ (or VT=η, to increase the read margin with respect to programmed cells in VT distribution 270), for example. Of course, such details of bit manipulation are merely examples, and claimed subject matter is not so limited.
In one implementation, one portion of a memory array may be affected by one or more operating parameters differently than another portion of the memory array. In other words, operating parameters need not affect all portions of a memory array in the same fashion. Thus, for example, different blocks, pages, words, or bytes may have different encoding based, at least in part, on one or more operating parameters included in a memory instruction, as described above.
In an embodiment, a process to write information to a PCM cell may comprise setting or resetting the PCM cell to one state or another. For example, a PCM cell may be reset by melting phase change material by applying a relatively high amplitude, relatively short duration electrical programming pulse. In contrast, a PCM cell may be set by applying a relatively smaller sub-melt amplitude electrical programming pulse having a relatively longer duration, which may include a relatively abrupt drop, for example. A PCM cell may also be set by applying a higher over-melt amplitude electrical programming pulse, possibly having a gradual, sloping drop in voltage or current over time, to allow molten phase change material to crystallize. Such a reset and/or set pulse and process may be applied as a “write” or “program” pulse and a “write” or “program” process. In an implementation, one or more operating parameters may accompany a write command in a memory instruction, as described above. Values of such operating parameters may affect various elements of a programming pulse, such as magnitude, duration, slope, and so on. Of course, such details of a programming pulse are merely examples, and claimed subject matter is not so limited.
It is recognized that all or part of the various devices shown in system 600, and the processes and methods as further described herein, may be implemented using or otherwise including hardware, firmware, software, or any combination thereof. Thus, by way of example but not limitation, computing device 604 may include at least one processing unit 620 that is operatively coupled to memory 622 through a bus 640 and a host or memory controller 615. Processing unit 620 is representative of one or more circuits configurable to perform at least a portion of a data computing procedure or process. By way of example but not limitation, processing unit 620 may include one or more processors, controllers, microprocessors, microcontrollers, application specific integrated circuits, digital signal processors, programmable logic devices, field programmable gate arrays, and the like, or any combination thereof. Processing unit 620 may include an operating system configured to communicate with memory controller 615. Such an operating system may, for example, generate memory instructions including commands, addresses, and/or operating parameters to be sent to memory controller 615 over bus 640. Such commands may comprise read, write, or erase commands. In response to such memory instructions, for example, memory controller 615 may perform process 500 described above, to perform the command and/or modify one or more physical operating conditions of memory device 610. For example, memory controller 615 may increase a magnitude of a bias signal applied to at least one of an array of PCM cells in response to an operating parameter included in a memory instruction.
Memory 622 is representative of any data storage mechanism. Memory 622 may include, for example, a primary memory 624 and/or a secondary memory 626. Primary memory 624 may include, for example, a random access memory, read only memory, etc. While illustrated in this example as being separate from processing unit 620, it should be understood that all or part of primary memory 624 may be provided within or otherwise co-located/coupled with processing unit 620.
Secondary memory 626 may include, for example, the same or similar type of memory as primary memory and/or one or more data storage devices or systems, such as, for example, a disk drive, an optical disc drive, a tape drive, a solid state memory drive, etc. In certain implementations, secondary memory 626 may be operatively receptive of, or otherwise configurable to couple to, a computer-readable medium 628. Computer-readable medium 628 may include, for example, any medium that can carry and/or make accessible data, code, and/or instructions for one or more of the devices in system 600.
Computing device 604 may include, for example, an input/output 632. Input/output 632 is representative of one or more devices or features that may be configurable to accept or otherwise introduce human and/or machine inputs, and/or one or more devices or features that may be configurable to deliver or otherwise provide for human and/or machine outputs. By way of example but not limitation, input/output device 632 may include an operatively configured display, speaker, keyboard, mouse, trackball, touch screen, data port, etc.
The terms, “and,” “and/or,” and “or” as used herein may include a variety of meanings that will depend at least in part upon the context in which it is used. Typically, “and/or” as well as “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of claimed subject matter. Thus, the appearances of the phrase “in one embodiment” or “an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in one or more embodiments.
While there has been illustrated and described what are presently considered to be example embodiments, it will be understood by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from claimed subject matter. Additionally, many modifications may be made to adapt a particular situation to the teachings of claimed subject matter without departing from the central concept described herein. Therefore, it is intended that claimed subject matter not be limited to the particular embodiments disclosed, but that such claimed subject matter may also include all embodiments falling within the scope of the appended claims, and equivalents thereof.
Patent | Priority | Assignee | Title |
10126968, | Sep 24 2015 | International Business Machines Corporation | Efficient configuration of memory components |
10748619, | Apr 28 2019 | SanDisk Technologies LLC | Memory device with different bits per cell on different word lines in a block |
Patent | Priority | Assignee | Title |
5768287, | Oct 24 1996 | Round Rock Research, LLC | Apparatus and method for programming multistate memory device |
6564288, | Nov 30 2000 | CONVERSANT INTELLECTUAL PROPERTY MANAGEMENT INC | Memory controller with temperature sensors |
6851018, | Mar 27 2002 | SAMSUNG ELECTRONICS CO , LTD | Exchanging operation parameters between a data storage device and a controller |
6862217, | Sep 20 2002 | MONTEREY RESEARCH, LLC | Control method of non-volatile semiconductor memory cell and non-volatile semiconductor memory device |
6903974, | Oct 05 2001 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Flash memory device with a variable erase pulse |
7180775, | Aug 05 2004 | Western Digital Israel Ltd | Different numbers of bits per cell in non-volatile memory devices |
7426138, | Dec 06 2002 | SAMSUNG ELECTRONICS CO , LTD | Parallel programming of multiple-bit-per-cell memory cells by controlling program pulsewidth and programming voltage |
7539053, | Sep 04 2006 | Kioxia Corporation | Non-volatile semiconductor memory device |
7545677, | Jun 14 2007 | Samsung Electronics Co., Ltd. | Nonvolatile memory device and methods of programming and reading the same |
7551480, | Sep 13 2006 | Samsung Electronics Co., Ltd. | Multi-bit flash memory device and memory cell array |
7551486, | May 15 2006 | Apple Inc. | Iterative memory cell charging based on reference cell value |
7616483, | Jul 03 2006 | Western Digital Israel Ltd | Multi-bit-per-cell flash memory device with an extended set of commands |
7773417, | Jul 05 2007 | Kioxia Corporation | Semiconductor memory device with memory cell having charge accumulation layer and control gate and memory system |
7791939, | Mar 14 2008 | Hynix Semiconductor Inc. | Non-volatile memory device |
7808819, | Apr 29 2008 | Western Digital Israel Ltd | Method for adaptive setting of state voltage levels in non-volatile memory |
7916543, | Oct 22 2007 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Memory cell operation |
7920427, | Feb 13 2009 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Dynamic soft program trims |
7924623, | May 27 2008 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Method for memory cell erasure with a programming monitor of reference cells |
8001320, | Apr 22 2007 | Apple Inc | Command interface for memory devices |
8072804, | Jul 22 2008 | Samsung Electronics Co., Ltd. | Multi-bit flash memory devices and methods of programming and erasing the same |
8085586, | Dec 27 2007 | Apple Inc | Wear level estimation in analog memory cells |
8228735, | Feb 17 2010 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Memory array having memory cells coupled between a programmable drain select gate and a non-programmable source select gate |
8243520, | Nov 02 2009 | Infineon Technologies AG | Non-volatile memory with predictive programming |
8902650, | Aug 30 2012 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Memory devices and operating methods for a memory device |
20080198651, | |||
20080263262, | |||
20090091979, | |||
20090273977, | |||
20100142284, | |||
20100208523, | |||
20100332729, | |||
20110304874, | |||
20120047320, | |||
20120239858, | |||
CN101000794, | |||
DE102007032780, | |||
DE10335060, | |||
JP10125087, | |||
JP2000321332, | |||
JP2002117692, | |||
JP2002208286, | |||
JP2002519808, | |||
JP2003196988, | |||
JP2004333246, | |||
JP2006065973, | |||
JP2008016112, | |||
JP2008541487, | |||
JP2009537056, | |||
JP2009540432, | |||
JP2010529677, | |||
JP9069294, | |||
JP9509518, | |||
KR1020120017911, | |||
WO983, | |||
WO2006125051, | |||
WO2007145967, | |||
WO2010074876, | |||
WO9608823, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jun 02 2015 | Micron Technology, Inc. | (assignment on the face of the patent) | / | |||
Apr 26 2016 | Micron Technology, Inc | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | CORRECTIVE ASSIGNMENT TO CORRECT THE REPLACE ERRONEOUSLY FILED PATENT #7358718 WITH THE CORRECT PATENT #7358178 PREVIOUSLY RECORDED ON REEL 038669 FRAME 0001 ASSIGNOR S HEREBY CONFIRMS THE SECURITY INTEREST | 043079 | /0001 | |
Apr 26 2016 | Micron Technology, Inc | MORGAN STANLEY SENIOR FUNDING, INC , AS COLLATERAL AGENT | PATENT SECURITY AGREEMENT | 038954 | /0001 | |
Apr 26 2016 | Micron Technology, Inc | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 038669 | /0001 | |
Jun 29 2018 | U S BANK NATIONAL ASSOCIATION, AS COLLATERAL AGENT | Micron Technology, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 047243 | /0001 | |
Jul 03 2018 | MICRON SEMICONDUCTOR PRODUCTS, INC | JPMORGAN CHASE BANK, N A , AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 047540 | /0001 | |
Jul 03 2018 | Micron Technology, Inc | JPMORGAN CHASE BANK, N A , AS COLLATERAL AGENT | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 047540 | /0001 | |
Jul 31 2019 | JPMORGAN CHASE BANK, N A , AS COLLATERAL AGENT | MICRON SEMICONDUCTOR PRODUCTS, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 051028 | /0001 | |
Jul 31 2019 | JPMORGAN CHASE BANK, N A , AS COLLATERAL AGENT | Micron Technology, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 051028 | /0001 | |
Jul 31 2019 | MORGAN STANLEY SENIOR FUNDING, INC , AS COLLATERAL AGENT | Micron Technology, Inc | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 050937 | /0001 |
Date | Maintenance Fee Events |
Oct 26 2016 | ASPN: Payor Number Assigned. |
Feb 28 2020 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Feb 27 2024 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Sep 06 2019 | 4 years fee payment window open |
Mar 06 2020 | 6 months grace period start (w surcharge) |
Sep 06 2020 | patent expiry (for year 4) |
Sep 06 2022 | 2 years to revive unintentionally abandoned end. (for year 4) |
Sep 06 2023 | 8 years fee payment window open |
Mar 06 2024 | 6 months grace period start (w surcharge) |
Sep 06 2024 | patent expiry (for year 8) |
Sep 06 2026 | 2 years to revive unintentionally abandoned end. (for year 8) |
Sep 06 2027 | 12 years fee payment window open |
Mar 06 2028 | 6 months grace period start (w surcharge) |
Sep 06 2028 | patent expiry (for year 12) |
Sep 06 2030 | 2 years to revive unintentionally abandoned end. (for year 12) |