WO2007111688A2 - Method and apparatus for programming/erasing a non-volatile memory - Google Patents
Method and apparatus for programming/erasing a non-volatile memory Download PDFInfo
- Publication number
- WO2007111688A2 WO2007111688A2 PCT/US2006/060671 US2006060671W WO2007111688A2 WO 2007111688 A2 WO2007111688 A2 WO 2007111688A2 US 2006060671 W US2006060671 W US 2006060671W WO 2007111688 A2 WO2007111688 A2 WO 2007111688A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- voltage
- read current
- erase
- nvm
- program
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/34—Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
- G11C16/3436—Arrangements for verifying correct programming or erasure
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
- G11C16/14—Circuits for erasing electrically, e.g. erase voltage switching circuits
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/34—Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
Definitions
- the present invention relates to non- volatile memory, and more particularly, to a method and apparatus for programming/erasing a nonvolatile memory.
- Non- volatile memory which is capable of being programmed and erased multiple times is commonly used in a wide variety of applications.
- the NVM has a maximum number of program/erase cycles that can be performed while ensuring that a data retention specification is met.
- FIG. 1 illustrates, in block diagram form, an integrated circuit in accordance with one embodiment of the present invention
- FIG. 2 illustrates, in block diagram form, an NVM 14 of FIG. 1 in accordance with one embodiment of the present invention
- FIG. 3 illustrates, in flow diagram form, a method for erasing an NVM in accordance with one embodiment of the present invention
- FIG. 4 illustrates, in graph form, a distribution of programmed and erased bits, in accordance with one embodiment of the present invention.
- FIG. 5 illustrates, in graph form, various erase pulses in accordance with one embodiment of the present invention.
- the data retention of an NVM cell is the amount of time that a predetermined data value will remain properly stored so that it is retrievable from the NVM cell.
- the endurance of the NVM cell is the maximum number of program/erase cycles that can be performed before the state of the NVM cell can no longer be reliably changed. Note that there are a variety of techniques that may be used to extend the viability of an NVM array when one or more NVM cells have failed either during testing or during usage (e.g. redundancy, error correction code, etc.).
- NVMs may be programmed with any desired granularity. Although many NVMs are programmed on a per byte basis, alternate embodiments may be programmed on a bit, word, long word, sector, block, or any other desired basis. NVMs may be erased with any desired granularity. Although many NVMs are erased on a per sector basis, alternate embodiments may be erased on a bit, byte, word, long word, block, or any other desired basis.
- NVM array 30 (see FIG. 2) must meet a maximum specification for data retention that is required by a first group of customers, while also meeting a maximum specification for endurance that is required by a second group of customers.
- the first group of customers may be storing software code, e.g. instruction for processor 12 (see FIG. 1), which must remain stored for the lifetime of the product (e.g. twenty years).
- software code e.g. instruction for processor 12 (see FIG. 1)
- One example of such a product is an automobile which uses the NVM to store software code to perform engine control.
- This first group of customers may not require that the NVM perform many program/erase cycles.
- the NVM stores software code, it is likely that the software code may never need to be erased and rewritten once it is initially stored in the NVM.
- Self-modifying software code is generally not used in most applications.
- the second group of customers may be storing data values, e.g. non- volatile but variable data, which need to remain stored for a relatively shorter period of time (e.g. one month to five year).
- data values e.g. non- volatile but variable data
- One example of such a product is an automobile which uses the NVM to store data values to represent engine tuning information.
- This second group of customers will require that the NVM perform many program/erase cycles (e.g. one program/erase cycle every time the automobile ignition is turned off and on). In this example, if the NVM stores data values, it is likely that the data values will be refreshed by a new program/erase cycle and thus do not need to have a long data retention time.
- some customers will require both types of NVM in the same application.
- FIG. 1 illustrates, in block diagram form, an integrated circuit (IC) 10 in accordance with one embodiment of the present invention.
- IC 10 has a processor 12, an NVM 14, optional other memory 16, one or more optional other module(s) 18, and an optional external bus interface 20, each of which is bi-directionally coupled to bus 22.
- bus is used to refer to a plurality of signals or conductors which may be used to transfer one or more various types of information, such as data, addresses, control, or status.
- IC 10 is a stand alone NVM and circuits 12, 16, and 18 are not implemented.
- the external bus interface 20 includes the address and data bus drivers for the NVM 14.
- IC 10 is a microcontroller which has an NVM 14 as just one circuit available on the microcontroller. Any one or more of circuits 12, 14, 16, 18, and 20 may be coupled to one or more integrated circuit terminals (not shown) which may be used to communicate external to IC 10.
- external bus 24 may be used to communicate to circuitry (not shown) that is external to IC 10.
- Other memory 16 may be any type of memory.
- Other modules 18 may include circuitry that is used for any desired purpose. Some examples of circuitry in other modules 18 includes timer circuitry, communication interface circuitry, display driver circuitry, analog to digital converters, digital to analog converters, power management circuitry, etc.
- FIG. 2 illustrates, in block diagram form, an NVM 14 of FIG. 1 in accordance with one embodiment of the present invention.
- NVM 14 has an NVM array 42 having N blocks, wherein N can be any integer greater than or equal to one. Dashed lines are used to represent blocks of NVM array 42. These blocks can be of any size. Control information corresponding to each block may also be stored within each block.
- NVM 14 also includes control circuitry 32, read circuitry 40, verify level generator 26, verify level selector 28, read verify circuitry 30, voltage generator 36, voltage selector 48, program/erase pulse generator 64, and other NVM circuitry 38.
- Verify level generator 26 provides a plurality of verify levels to verify level selector via conductors 51-53.
- Verify level selector 28 provides one of these verify levels via conductor 46 to read verify circuitry 30 based on a select signal received via conductor 44 from control circuitry 32.
- Read circuitry 40 is bi-directionally coupled to NVM array 42 and provides an actual read current via conductor 60 to read verify circuitry 30.
- Read verify circuitry 30 is bidirectionally coupled to control circuitry 32 and provides a verify result to control circuitry 32 via conductor 62.
- Control circuitry 32 is bidirectionally coupled to verify level generator 26, other NVM circuitry 38, voltage generator 36, and program/erase pulse generator 64.
- Voltage generator 36 provides a plurality of voltages via conductors 54-56 to voltage selector 48.
- Voltage selector 48 provides one of these voltages via conductor 58 to program/erase pulse generator 64 based on a select signal received via conductor 50 from control circuitry 32.
- Control circuitry 32 includes program/erase pulse counter 34, maximum pulse counts per voltage 68 and maximum total pulse count 70. Maximum pulse counts per voltage 68 and maximum total pulse count 70 may be stored in storage circuitry, such as, for example, registers, within control circuitry 32, or elsewhere within NVM 14 or IC 10.
- a program/erase cycle may include the programming of all or a portion of NVM array 42 or erasing all or a portion of NVM array 42.
- erase refers to setting a bit or bits to a logic level one
- programming refers to setting an appropriate bit or bits to a logic level one or a logic level zero, as needed, to represent the desired information to be stored in NVM array 42.
- programming a portion of NVM array 42 includes an erase cycle to first erase all bits of the portion to be programmed, and then subsequently changing the state of those bits (to, e.g., a logic level zero) that need to be changed to represent the desired information to be stored.
- a program/erase cycle may include just an erase operation.
- an entire block may be erased at a time, or alternatively, more or less than a block may be erased at once.
- erase may refer to the setting of a bit or bits to a logic level zero rather than a logic level one.
- a subsequent verification is performed to determine that the program/erase cycle was successful.
- a read of the programmed/erased bits is performed and compared to a verify level to determine if the bits were properly programmed/erased.
- read verification circuitry 30 may be used to verify a proper erase of selected bitcells in NVM array 42.
- Read circuitry 40 includes a plurality of sense amplifiers (not shown) which are used to read the selected bitcell or bitcells that are to be verified. Read circuitry 40 senses each selected bitcell and provides an actual read current via conductor 60 to read verify circuitry 30. (Note that the circuitry and operation of read circuitry 40 is known in the art and therefore is not being described in more detail herein.) Read verify circuitry 30 then compares the actual read current received via conductor 60 with a selected verify level provided via conductor 46 and determines whether the actual read current is greater than or equal to the selected verify level. If so, then the stored value of the corresponding erased bitcell is verified as a logic level one, indicating that the erase was successful.
- an erase of a group of bitcells can be verified at once. For example, in the case where all bitcells of a portion of NVM array 42 are erased, they are all expected to be logic level ones after the erase.
- read circuitry 40 may sense each bitcell of the portion of NVM array 42 that was erased, and only provide the minimum actual read current to read verify circuitry 30. If the minimum actual read current in this case is greater than or equal to the selected verify level, then the erase of all the bitcells in the erased portion was successful.
- FIG. 4 illustrates, in graph form, an example distribution of zero ("0") bits and one ("1") bits which may be present in NVM array 42, and various different verify levels VLl- VLN.
- the y-axis represents the number of bits, while the x-axis represents bitcell currents of the bits. Therefore, in the case of "0" bits (bitcells having a stored logic level zero), the bitcell currents of each of the bitcells is less than a 0/1 reading threshold current.
- bitcells having a stored logic level one the bitcell currents of each of the bitcells is greater than the 0/1 reading threshold current (otherwise, any "1" bit whose current is less than the 0/1 reading threshold current would be misread as a "0" bit). Therefore, any bitcell having a current below the 0/1 reading threshold current is read as storing a "0” and any bitcell having a current above the 0/1 reading threshold current is read as storing a "1".
- the "1" bit bitcell currents are a predetermined amount greater than the 0/1 reading threshold current. For example, in FIG.
- the bitcell currents of the "1" bits should be greater than a verify level VLl. Therefore, as seen in FIG. 4, the distribution of "1" bits occurs to the right of VLl. However, over time, the distribution of "1" bits begins shifting to the left, closer to the 0/1 reading threshold, due, for example, to damage to the device oxides caused by program/erase cycles. As illustrated in FIG. 4, note that the distribution of "1" bits may shift closer to the
- verify level VL4 were used to verify "1" bits rather than VLl, more bits would “pass” as validly storing a "1” since a smaller bitcell current is necessary to be considered a valid "1” bit.
- the bitcell current only surpasses VL4 and not VL1-VL3, then the "1" bit is actually a weaker "1” bit having a shorter lifespan left before the NVM degrades to the point that ones can no longer be reliably programmed.
- verify level VLl is used as long as possible to verify a "1" bit, and when that is no longer possible, smaller verify levels such as VL2-VLN may instead be used to verify a "1" bit, thus possibly extending the life of NVM array 42.
- read verify circuitry 30 may use one of a variety of verify levels (provided by verify level selector 28) to verify a "1" bit.
- verify level generator 26 may generate N verify levels (corresponding, for example, to VLl-VLN of FIG. 4) and provide them via conductors 51-53 to verify level selector 28.
- Verify level selector 28 can then select one of these, based on a select signal received from control circuitry 32 via conductor 44, and provide the selected verify level to read verify circuitry 30 via conductor 46 for actually doing the verification.
- Read verify circuitry 30 compares the actual read current received from read circuitry 40 with this selected verify level and provides a result, via conductor 62, to control circuitry 32. Operation of control circuitry 32 will be discussed in more detail in reference to the flow diagram of FIG. 3.
- a plurality of erase pulses are generated, such as, by program/erase pulse generator 64, to erase a portion of NVM array 42.
- An example of these pulses is illustrated in FIG. 5.
- a number of pulses e.g., pulses 100
- EVl first erase voltage
- a number of pulses e.g., pulses 102
- EV2 second erase voltage
- a number of pulses e.g., pulses 104 having approximately a third erase voltage (EV3), etc.
- a verification is performed to determine whether the erase pulse was successful. If not successful, then another erase pulse is provided at the same erase voltage, and it is then verified again. At any point where the verification verifies that the erase was successful, the program/erase cycle ends. However, if, after a predetermined number of pulses at a same erase voltage is performed (such as all of pulses 100), and the erase is still not successful, a pulse is provided at a higher erase voltage (e.g. EV2). Again, after each pulse at this higher erase voltage, verification is performed to see if the erase was successful, and if so, the program/erase cycle successfully ends at that point. However, if after a predetermined number of pulses at that higher erase voltage is performed (such as all of pulses 102), and the erase is still not successful, a pulse is provided at yet a higher erase voltage (e.g., EV3).
- a higher erase voltage e.g., EV3
- the program/erase cycle ends without a successful erase (i.e. a failed erase).
- the predetermined number of pulses provided per each erase voltage prior to moving to a higher erase voltage is the same. For example, a maximum of 5 pulses may be provided for each erase voltage, with a maximum total number of pulses being 20. However, in alternate embodiments, the number of pulses provided per each erase voltage prior to moving to a higher erase voltage is different.
- erase pulse counter 34 may include any number of counters or other circuitry to keep track of the number of pulses per erase voltage and the total number of pulses. Note that the use of pulses having increasingly higher erase voltages may result in less damage to NVM array 42.
- each program/erase cycle may use multiple different erase voltages and multiple different verify levels.
- verify level selector 28 may select a first verify level during a first portion of a program/erase cycle and then select a second verify level during a second portion (which occurs, in time, after the first portion) of the program/erase cycle (if, for example, the erase pulses at the first verify level were unsuccessful). Therefore, during the first portion of the program/erase cycle, read verify circuitry 30 may compare a first actual read current and the first verify level and during the second portion of the program/erase cycle, read verify circuitry 30 may compare a second actual read current to the second verify level.
- other NVM circuitry 38 of FIG. 2 includes all other circuitry necessary for the operation of NVM 14.
- other NVM circuitry 38 has a charge pump, high voltage regulator, high voltage switches, word line drivers, source line drivers, row decoders, column decoders, an interface to bus 22, registers, and any other circuitry that is desired for the functionality of NVM 14 (not shown).
- other NVM circuitry 38 may operate in a conventional manner.
- circuitry similar to read verify circuitry 30 may be used to verify "0" bits where the bitcell currents of "0" bits are compared against a verify level that is typically less than the 0/1 reading threshold current to determine validity.
- bitcells having currents less than the 0/1 reading threshold current may correspond to "1" bits while those bitcells having currents greater than the 0/1 reading threshold current may correspond to "0" bits.
- FIG. 3 illustrates, in flow diagram form, an erase and verify procedure in accordance with one embodiment of the present invention.
- Stimulus external to NVM array 42 may be used to initiate an erase operation of flow 80.
- One example of such an external stimulus may be processor 12 (see FIG. 1) initiating an erase within NVM 14.
- Flow starts with block 82 where an initial erase voltage and an initial verify level are selected.
- control circuitry 32 may indicate to verify level selector 28 (via, e.g., conductor 44) to select a first verify level (e.g. VLl in FIG. 4) from verify level generator.
- control circuitry 32 may indicate to voltage selector 48 (via, e.g., conductor 50) to select a first erase voltage (e.g. EVl) from voltage generator 36.
- an erase pulse is provided using the selected erase voltage (selected in block 82).
- program/erase pulse generator 64 may use the erase voltage provided by voltage selector 48 to generate a pulse, as shown, for example, in FIG. 5.
- control circuitry 32 may also provide control information to program/erase pulse generator 64, such as relating to the duration of the pulse.
- This first pulse is provided to NVM array 42 to erase a selected portion of NVM array 42 (where the selected portion can be indicated, as known in the art, by other NVM circuitry 38).
- read verify circuitry 30 may verify the erase as was described above in reference to FIG. 2.
- read circuitry 40 may provide an actual read current to read verify circuitry 30 which compares it to the selected verify level from verify level selector 28.
- decision diamond 88 it is determined whether the actual read current is greater than or equal to the selected verify level. If so, flow proceeds to block 90 which indicates a successful erase, and thus, a program/erase cycle has been completed. That is, at block 90, the erase operation of flow 80 is completed.
- decision diamond 92 it is determined whether the maximum number of erase pulses at the selected voltage level has been reached. If not, flow returns to block 84 where another erase pulse is provided at the same selected voltage level, and a verify is performed at the same verify level (at block 86). If, at decision diamond 92, it is determined that the maximum number of erase pulses at the selected voltage level has been reached, then flow proceeds to decision diamond 94.
- control circuitry 32 may compare the count of a first erase pulse counter keeping track of the number of pulses at the current erase voltage to the maximum pulse count for the current erase voltage (which may be stored, for example, as part of maximum pulse counts per erase voltage 68).
- control circuitry 32 may compare the count of a second erase pulse counter keeping track of the number of pulses total in the current program/erase cycle to maximum total pulse count 70 to make this determination. If the maximum total number of erase pulses has been reached, then flow proceeds to block 96 which indicates that the current program/erase cycle has ended with an unsuccessful erase (i.e. a failed erase). Note that a failure during erasing or programming may be due to circuitry in NVM array 42 and/or in other NVM circuitry 38.
- block 98 if at decision diamond 94 the maximum total number of erase pulses has not yet been reached, flow proceeds to block 98 where the current program/erase cycle continues.
- a higher erase voltage and a lower verify level is selected, and flow returns to block 84.
- the higher erase voltage and lower verify level may correspond to EV2 and VL2, respectively. With this new higher erase voltage, a stronger erase pulse is provided to NVM array 42 to perform the erase.
- each erase pulse at this higher erase voltage a verify is performed using a lower verify level.
- This lower verify level may make it easier for read verify circuitry 30 to verify a successful erase. That is, each program/erase cycle may use multiple different erase voltages and multiple different verify levels.
- incrementally higher erase voltages e.g., EVl , EV2, ... EVN
- incrementally lower verify levels e.g., VLl , VL2, ... VLN, respectively
- each erase voltage in the sequence of erase voltages to be used may be evenly spaced apart. Alternatively, they may not be equally spaced apart, such that, for example, the jump from EVl to EV2 may be smaller than the subsequent jump from EV2 to EV3. Also, each erase voltage may not necessarily be greater than the previous erase voltage.
- each verify level in the sequence of verify levels to be selected may be evenly spaced apart or not evenly spaced apart. Also, each verify level may not necessarily by lower than the previous verify level.
- the sequence of erase voltages starts at 13 Volts and increments by 200 milivolts each time up to 14 Volts, as follows: 13 Volts, 13.2 Volts,
- the verify level is a reference current which is compared to the actual read current from the NVM cell. Alternate embodiments may use something other than a reference current to represent the verify level.
- the verify level may be a reference voltage.
- the reference may be compared to something other than read current.
- the verify level may be a reference voltage that is compared to an NVM cell voltage (e.g. transistor threshold voltage). Alternate embodiments may use any desired circuit characteristic to represent the verify level. Therefore, in one embodiment, the verify level may be referred to as a read current/voltage threshold, and the actual read current may be referred to as the actual read current/voltage. Also, in one embodiment, verify level selector 28 may be referred to as a threshold selector.
- verify level generator 26 and verify level selector 28 may be implemented in a variety of ways.
- verify level generator 26 may be able to generate any number of verify levels (either currents or voltages, depending on the desired type of comparison), and verify level selector 28 may then select one of these based on a select signal from control circuitry 32.
- verify level 28 may either select from various generated verify levels, or may select the circuitry to be enabled within verify level generator 26 to generate the selected verify level. Alternatively, these functions may be combined into a single block.
- each subsequent verify level may be generated from the initial verify level or any other previous verify level.
- control circuitry 32 may provide any type of control signal(s), as necessary, to indicate which verify level and erase voltage to select or generate.
- any type of known circuitry may be used to implement parts of NVM 14.
- any type of current/voltage level generators may be used to implement verify level generator 26 and voltage generator 36.
- any type of circuitry may be used to implement the selecting function of selectors 28 and 48 (such as, for example, a multiplexer).
- known circuitry may be used to implement the counter or counters of program/erase pulse counter 34 and to implement program/erase pulse generator 64.
- control circuitry 32 may be implemented in software running on processor 12 or as hardware implementing, for example, the control of flow 80, or as a combination of hardware and software. Portions of control circuitry 32 may also be distributed and located throughout NVM 14, and may not be centralized, as illustrated in FIG. 2.
- Control circuitry 32 may also be used to provide control information and signals to any portion of NVM 14 relating to any function of NVM 14. Also, note that the specific portions of NVM 14 described herein, such as, for example, generators 26 and 36, selectors 28 and 48, read verify circuitry 30, program/erase pulse generator 64, and control circuitry 32 may also perform or aid in performing other functions of NVM 14, such as programming or verifying "0" bits. Note also that embodiments of the present invention are applicable to any type of NVM which can be programmed and erased a plurality of times.
- One embodiment of the present invention relates to a method for programming/erasing a non-volatile memory (NVM) including initiating an erase operation of at least a portion of the NVM using a first erase voltage, selecting a first read current/voltage threshold, determining a first actual read current/voltage of the at least the portion of the NVM and comparing the first actual read current/voltage and the first read current/voltage threshold.
- NVM non-volatile memory
- the method further includes applying at least one erase pulse to the at least the portion of the NVM, selecting a second read current/voltage threshold, determining a second actual read current/voltage of the at least the portion of the NVM, and comparing the second actual read current/voltage and the second read current/voltage threshold. If the second actual read current/voltage is not lower than the second read current/voltage threshold, the erase operation is completed.
- the first read current/voltage threshold and the second read current/voltage threshold are different.
- the at least one erase pulse comprises a first plurality of first erase pulses.
- the first plurality of first erase pulses includes N erase pulses, wherein N may be determined by a value stored in the NVM.
- Each of the first plurality of first erase pulses may have approximately a first voltage.
- the method may further include applying a second plurality of second erase pulses to the at least the portion of the NVM wherein each of the second erase pulses has approximately a second voltage and wherein the second voltage is different than the first voltage.
- the second voltage may be more than the first voltage.
- the second plurality may be a same number as the first plurality.
- the NVM may be considered to have failed if the first plurality added to the second plurality has reached a predetermined maximum total number of erase pulses, and if the second actual read current/voltage is lower than the second read current/voltage threshold.
- the second read current/voltage threshold is less than the first read current/voltage threshold.
- NVM non-volatile memory
- a threshold selector which selects a first one of a plurality of read current/voltage thresholds during a first portion of a program/erase cycle, and which selects a second one of a plurality of read current/voltage thresholds during a second portion of said program/erase cycle, wherein the first one of a plurality of read current/voltage thresholds and the second one of a plurality of read current/voltage thresholds are different.
- the first portion of the program/erase cycle occurs in time before the second portion of the program/erase cycle, and wherein the second one of the plurality of read current/voltage thresholds is less than the first one of the plurality of read current/voltage thresholds.
- the integrated circuit further includes a read verify circuitry for comparing a first actual read current/voltage and the first one of a plurality of read current/voltage thresholds during the first portion of a program/erase cycle, said read verify circuitry also comparing a second actual read current/voltage and the second one of a plurality of read current/voltage thresholds during the second portion of said program/erase cycle, wherein said read verify circuitry is coupled to said threshold selector.
- the integrated circuit further includes an erase pulse generator which applies at least one first erase pulse to the NVM if the first actual read current/voltage is lower than the first one of the plurality of read current/voltage thresholds, said erase pulse generator also applying at least one second erase pulse to the NVM if the second actual read current/voltage is lower than the second one of the plurality of read current/voltage thresholds.
- the at least one first erase pulse includes a first plurality of erase pulses having a first voltage
- the at least one second erase pulse comprises a second plurality of erase pulses having a second voltage. The second voltage may be higher than the first voltage.
- NVM non- volatile memory
- means for generating a plurality of read current/voltage thresholds means for selecting a first one of the plurality of read current/voltage thresholds during a first portion of a program/erase cycle, and for selecting a second one of the plurality of read current/voltage thresholds during a second portion of said program/erase cycle
- means for comparing a first actual read current/voltage and the first one of a plurality of read current/voltage thresholds during the first portion of a program/erase cycle, and for comparing a second actual read current/voltage and the second one of a plurality of read current/voltage thresholds during the second portion of said program/erase cycle means for providing a first plurality of first erase pulses to the NVM array if the first actual read current/voltage is lower than the first one of a plurality of read current/voltage thresholds, and providing a second plurality of second erase pulses to the NVM array
- the first portion of the program/erase cycle occurs in time before the second portion of the program/erase cycle, and wherein the second one of the plurality of read current/voltage thresholds is less than the first one of the plurality of read current/voltage thresholds.
- the first plurality of first erase pulses have a first voltage
- the second plurality of second erase pulses have a second voltage.
- the second voltage is higher than the first voltage
- the second plurality is a same number as the first plurality.
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020087012943A KR101285576B1 (en) | 2005-11-30 | 2006-11-08 | Method and apparatus for programming/erasing a non-volatile memory |
JP2008543553A JP5160441B2 (en) | 2005-11-30 | 2006-11-08 | Method and apparatus for programming / erasing non-volatile memory |
CN2006800442547A CN101317231B (en) | 2005-11-30 | 2006-11-08 | Method and apparatus for programming/erasing a non-volatile memory |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/290,321 US7236402B2 (en) | 2005-11-30 | 2005-11-30 | Method and apparatus for programming/erasing a non-volatile memory |
US11/290,321 | 2005-11-30 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2007111688A2 true WO2007111688A2 (en) | 2007-10-04 |
WO2007111688A3 WO2007111688A3 (en) | 2008-04-24 |
Family
ID=38087275
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2006/060671 WO2007111688A2 (en) | 2005-11-30 | 2006-11-08 | Method and apparatus for programming/erasing a non-volatile memory |
Country Status (6)
Country | Link |
---|---|
US (1) | US7236402B2 (en) |
JP (1) | JP5160441B2 (en) |
KR (1) | KR101285576B1 (en) |
CN (1) | CN101317231B (en) |
TW (1) | TWI435330B (en) |
WO (1) | WO2007111688A2 (en) |
Families Citing this family (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2874732A1 (en) * | 2004-08-31 | 2006-03-03 | St Microelectronics Sa | METHOD FOR PROGRAMMING MEMORY CELLS INCLUDING DETECTION OF TRANSCONDUCTANCE DEGRADATION |
US7397703B2 (en) * | 2006-03-21 | 2008-07-08 | Freescale Semiconductor, Inc. | Non-volatile memory with controlled program/erase |
US20090199058A1 (en) * | 2008-02-06 | 2009-08-06 | Christoph Seidl | Programmable memory with reliability testing of the stored data |
US7903462B1 (en) * | 2008-04-04 | 2011-03-08 | Link A Media Devices Corporation | E/P durability by using a sub-range of a full programming range |
KR101423612B1 (en) * | 2008-09-16 | 2014-07-25 | 삼성전자주식회사 | Nonvolatile memory device and operating method thereof, and memory system including the same |
KR101005117B1 (en) * | 2009-01-23 | 2011-01-04 | 주식회사 하이닉스반도체 | Operating method of non volatile memory device |
KR101038991B1 (en) * | 2009-03-10 | 2011-06-03 | 주식회사 하이닉스반도체 | Solid State Storage System For Even Using Of Memory Area and Controlling Method thereof |
US8264890B2 (en) * | 2009-04-09 | 2012-09-11 | Sandisk Technologies Inc. | Two pass erase for non-volatile storage |
KR20110126408A (en) | 2010-05-17 | 2011-11-23 | 삼성전자주식회사 | Nonvolatile memory device, memory system having its and programming method thereof |
CN102034539A (en) * | 2010-10-25 | 2011-04-27 | 上海宏力半导体制造有限公司 | Method for programming/erasing nanocrystalline device |
US8705283B2 (en) * | 2011-07-13 | 2014-04-22 | Vincenzo Ferragina | Erase techniques and circuits therefor for non-volatile memory devices |
CN103390424A (en) * | 2012-05-08 | 2013-11-13 | 北京兆易创新科技股份有限公司 | Erasing/programming method and device of memory |
CN103632725B (en) * | 2012-08-24 | 2016-08-10 | 北京兆易创新科技股份有限公司 | The method for deleting of a kind of flash memory and device |
US9225356B2 (en) * | 2012-11-12 | 2015-12-29 | Freescale Semiconductor, Inc. | Programming a non-volatile memory (NVM) system having error correction code (ECC) |
US9564216B2 (en) * | 2015-01-30 | 2017-02-07 | Macronix International Co., Ltd. | Stress trim and modified ISPP procedures for PCM |
US9679652B2 (en) * | 2015-05-04 | 2017-06-13 | Phison Electronics Corp. | Threshold based multi-level cell programming for reliability improvement |
CN107665724A (en) * | 2016-07-27 | 2018-02-06 | 北京兆易创新科技股份有限公司 | A kind of method for deleting of memory cell |
US10297324B2 (en) * | 2017-05-25 | 2019-05-21 | Western Digital Technologies, Inc. | Physical secure erase of solid state drives |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030076710A1 (en) * | 2001-10-24 | 2003-04-24 | Yair Sofer | Method for erasing a memory cell |
US20040196695A1 (en) * | 2003-04-04 | 2004-10-07 | Renesas Technology Corp. | Nonvolatile memory device and semiconductor device |
Family Cites Families (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4943948A (en) * | 1986-06-05 | 1990-07-24 | Motorola, Inc. | Program check for a non-volatile memory |
US5268870A (en) * | 1988-06-08 | 1993-12-07 | Eliyahou Harari | Flash EEPROM system and intelligent programming and erasing methods therefor |
US5268319A (en) * | 1988-06-08 | 1993-12-07 | Eliyahou Harari | Highly compact EPROM and flash EEPROM devices |
US5361227A (en) * | 1991-12-19 | 1994-11-01 | Kabushiki Kaisha Toshiba | Non-volatile semiconductor memory device and memory system using the same |
JP3348466B2 (en) * | 1992-06-09 | 2002-11-20 | セイコーエプソン株式会社 | Nonvolatile semiconductor device |
JPH10228784A (en) * | 1997-02-12 | 1998-08-25 | Mitsubishi Electric Corp | Non-volatile semiconductor memory |
JP3781240B2 (en) * | 1998-09-07 | 2006-05-31 | 株式会社ルネサステクノロジ | Nonvolatile semiconductor memory and semiconductor integrated circuit incorporating the same |
US6400603B1 (en) * | 2000-05-03 | 2002-06-04 | Advanced Technology Materials, Inc. | Electronically-eraseable programmable read-only memory having reduced-page-size program and erase |
JP2001319486A (en) * | 2000-05-12 | 2001-11-16 | Mitsubishi Electric Corp | Non-volatile semiconductor memory |
JP2002100192A (en) * | 2000-09-22 | 2002-04-05 | Toshiba Corp | Non-volatile semiconductor memory |
JP4040405B2 (en) * | 2002-09-20 | 2008-01-30 | 富士通株式会社 | Nonvolatile semiconductor memory cell control method and nonvolatile semiconductor memory device |
KR100496866B1 (en) * | 2002-12-05 | 2005-06-22 | 삼성전자주식회사 | Flash memory device having uniform threshold voltage distribution without under-programed or over-programed flash cells and program verify method thereof |
JP2005276428A (en) * | 2005-04-11 | 2005-10-06 | Toshiba Corp | Nonvolatile semiconductor storage device |
-
2005
- 2005-11-30 US US11/290,321 patent/US7236402B2/en active Active
-
2006
- 2006-11-08 KR KR1020087012943A patent/KR101285576B1/en not_active IP Right Cessation
- 2006-11-08 WO PCT/US2006/060671 patent/WO2007111688A2/en active Application Filing
- 2006-11-08 CN CN2006800442547A patent/CN101317231B/en active Active
- 2006-11-08 JP JP2008543553A patent/JP5160441B2/en not_active Expired - Fee Related
- 2006-11-10 TW TW095141602A patent/TWI435330B/en not_active IP Right Cessation
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030076710A1 (en) * | 2001-10-24 | 2003-04-24 | Yair Sofer | Method for erasing a memory cell |
US20040196695A1 (en) * | 2003-04-04 | 2004-10-07 | Renesas Technology Corp. | Nonvolatile memory device and semiconductor device |
Also Published As
Publication number | Publication date |
---|---|
TW200733117A (en) | 2007-09-01 |
US20070121387A1 (en) | 2007-05-31 |
US7236402B2 (en) | 2007-06-26 |
KR101285576B1 (en) | 2013-07-15 |
CN101317231B (en) | 2012-03-07 |
KR20080080511A (en) | 2008-09-04 |
CN101317231A (en) | 2008-12-03 |
JP5160441B2 (en) | 2013-03-13 |
JP2009518766A (en) | 2009-05-07 |
WO2007111688A3 (en) | 2008-04-24 |
TWI435330B (en) | 2014-04-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7236402B2 (en) | Method and apparatus for programming/erasing a non-volatile memory | |
USRE45910E1 (en) | Programming non-volatile storage including reducing impact from other memory cells | |
US7010736B1 (en) | Address sequencer within BIST (Built-in-Self-Test) system | |
CN104134459B (en) | non-volatile memory (NVM) with variable verify operation | |
EP1999756B1 (en) | Non-volatile memory with controlled program/erase | |
US8503233B2 (en) | Method of twice programming a non-volatile flash memory with a sequence | |
US20040049724A1 (en) | Built-in-self-test (BIST) of flash memory cells and implementation of BIST interface | |
JP2010535395A (en) | Non-volatile memory having dynamically adjustable soft program verify voltage level and method therefor | |
EP1683159A4 (en) | Method, system and circuit for programming a non-volatile memory array | |
US7292473B2 (en) | Method and apparatus for programming/erasing a non-volatile memory | |
EP1529293B1 (en) | Built-in-self-test of flash memory cells | |
WO2007100939A2 (en) | Non-volatile memory having a multiple block erase mode and method therefor | |
US6707718B1 (en) | Generation of margining voltage on-chip during testing CAM portion of flash memory device | |
WO2008136568A1 (en) | Multi-bit programming device and method of multi-bit programming | |
CN110795270A (en) | Solid state storage device and read retry method thereof | |
CN101800077A (en) | Method and device for carrying out data programming on flash | |
CN107045888B (en) | Data erasing method | |
US7028240B1 (en) | Diagnostic mode for testing functionality of BIST (built-in-self-test) back-end state machine | |
US8923071B2 (en) | Method of programming a multi-bit per cell non-volatile memory | |
CN110473584B (en) | Method for re-verifying erased block in solid state storage device | |
CN107633863B (en) | Memory device and programming method thereof | |
CN112786099A (en) | Memory device and error correction method for multiple entity units thereof | |
EP1782426A4 (en) | Self-adaptive program delay circuitry for programmable memories |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 200680044254.7 Country of ref document: CN |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 06850122 Country of ref document: EP Kind code of ref document: A2 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008543553 Country of ref document: JP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020087012943 Country of ref document: KR |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 06850122 Country of ref document: EP Kind code of ref document: A2 |