The present invention relates generally to non-volatile memory devices, and more specifically, to data programming operations for non-volatile memory devices.
Flash memory is a common type of non-volatile semiconductor memory device. Non-volatile refers to the trait of retaining stored data when power is turned off. Because Flash memory is non-volatile, it is commonly used in power conscious applications, such as in battery powered cellular phones, personal digital assistants (PDAs), and in portable mass storage devices such as memory sticks.
Flash memory devices typically include multiple individual components formed on or within a substrate. Such devices often comprise a high density section and a low density section. For example, a Flash memory may include one or more high density core regions and a low density peripheral portion formed on a single substrate. The high density core regions typically include arrays of individually addressable, substantially identical floating-gate type memory cells. The low density peripheral portion may include input/output (I/O) circuitry, circuitry for selectively addressing the individual cells (such as decoders for connecting the source, gate and drain of selected cells to predetermined voltages or impedances to effect designated operations of the cell such as programming, reading or erasing), and voltage regulation and supply circuitry.
In one particular type of Flash memory architecture, called NOR Flash memory, memory cells within the core portion are coupled together in a circuit configuration in which each memory cell has a drain, a source, and a stacked gate. In operation, memory cells in the core portion may be addressed by circuitry in the peripheral portion to perform functions such as reading, erasing, and programming of the memory cells.
When programming NOR-type Flash memory cells, multiple memory cells may be programmed at once. In a programming operation, each cell being programmed is a load to the power generation circuitry in the memory device. In such a programming architecture, it is desirable to efficiently use power during programming.
One aspect is directed to a memory device configured for simultaneous programming of a number of memory cells in a multi-bit programming operation. The memory device includes at least one array of non-volatile memory cells, each of the memory cells being connected to a source bit line and a drain bit line. The memory device further includes control logic configured to program the memory cells. The programming includes floating select ones of the source bit lines that were grounded in a previous programming operation, where the select ones of the source bit lines are selected based on a data pattern present in the multi-bit programming operation.
Another aspect is directed to a method of programming a non-volatile memory array. The method includes obtaining data bits corresponding to a program window that is to be written to the memory array and dividing the obtained data bits into sub-windows. The method further includes simultaneously programming memory cells corresponding to one or more of the sub-windows. The programming includes floating source bit lines of memory cells that are not to be programmed based on a pattern of the data bits in the sub-window so that a distance between source and drain voltages of different memory cells is maximized.
Reference is made to the attached drawings, wherein elements having the same reference number designation may represent like elements throughout.
Techniques described below relate to a Flash memory programming technique in which voltages applied to memory cells that are not being programmed depend on a programming pattern of the memory cells. The voltages are applied so as to minimize leakage current in the device.
As shown in
The memory cells in area 102 may be implemented such that each memory cell can store two or more bits. In one such multi-bit per memory cell technology, called MirrorBit™, the intrinsic density of a Flash memory array can be doubled by storing two physically distinct charges on opposite sides of a memory cell. Each charge, representing a bit within a cell, serves as a binary unit of data (e.g. either “1” or “0”). Reading or programming one side of a memory cell occurs independently of the data that is stored on the opposite side of the cell.
Although shown as a single block in
Y-decoder 108 may also include appropriate sense amplifier circuitry. Sense \amplifiers may be used to sense the programmed or non-programmed state of the memory cells in core area 102.
Random access memory (RAM) 104 may include memory, such as static dynamic random access memory (SRAM) or dynamic random access memory (DRAM) type memory, that can serve as a memory cache between core area 102 and I/O lines 114. Relative to the memory cells in core area 102, RAM 104 may be a higher speed memory and may be a volatile memory (i.e., loses its data when powered down). I/O lines 114 may provide buffering to facilitate data transfer between RAM 104 and memory device 100 and/or between core area 102 and RAM 104.
Voltage supply generator 112 may act as a power supply for the program, read, and erase functions performed on the memory cells in core area 102. Programming and erasing the memory cells, in particular, may require supply voltages larger than those supplied to memory device 100. For example, memory device 100 may be powered from a 3.5 volt source while a program operation may require a nine volt source. Voltage supply generator 112 may use one or more charge pumps to generate these higher voltages.
Control logic 106 may generally control X-decoder 110, Y-decoder 108, RAM 104, voltage supply generator 112, and I/O lines 114 to control the read, program, and erase of memory cell core area 102. Control logic 106 may include a state machine that appropriately manipulates memory cell core area 102 based on input address, data, and control signals received by memory device 100 through I/O lines 114.
As illustrated in
Although the memory cells 201 in core area 102 are shown as NOR memory cells, in some implementations, the circuitry in the peripheral regions of memory device 100 may provide an external interface that mimics an external interface normally provided by NAND-type Flash memories. In this situation, memory device 100, from the point of view of the user/circuit designer, can effectively be thought of as a NAND-type Flash device even though core area 102 includes NOR-type Flash memory.
Although only four global bit lines and four word lines are shown in
As shown in
Charge storage layer 322 may be formed on gate dielectric layer 320 and may include a dielectric material, such as a nitride (e.g., a silicon nitride). Layer 322 acts as a charge storage layer for the memory cell.
Charge storage layer 322 may be used to store one or more bits of information. In an exemplary implementation, charge storage layer 322 may store charges representing two separate bits of data by localizing the first and second charges to the respective left and right sides of charge storage layer 322. Each of the two charges of the memory cell 201 may be programmed independently by, for example, channel hot electron injection, to store a charge on each respective side of the charge storage layer 322. In this manner, the charges in charge storage layer 322 become effectively trapped on each respective side of charge storage layer 322 and the density of the resulting memory array may be increased as compared to memory devices that store only one bit of data per cell. In alternate implementations, charge storage layer 322 may store charges representing three or more bits of data for each memory cell 201.
Second dielectric layer 324 may be formed on layer 322 and may include a multi-layer structure, such as a first silicon oxide layer 325 and a second high dielectric constant (high-K) layer 326. High-K layer 326 may include, for example, an alumina, such as Al2O3. Dielectric layers 325 and 326 may together function as an inter-gate dielectric for memory cells 201. In alternate implementations, dielectric layer 324 may include a single layer, such as a silicon oxide or alumina.
Control gate 328 may be formed above second dielectric layer 324. Control gate 328 may be formed of, for example, polysilicon and may be connected to the word line of memory cell 201.
In operation, core area 102 of memory device 100 may be programmed by a channel hot electron injection process that injects electrons into charge storage layer 322. The injected electrons become trapped in charge storage layer 322 until an erase operation is performed.
In operation, memory cells 201 in core array 102 may be programmed by applying a relatively high voltage (e.g., 9 volts) to one of the word lines WL, such as WL1, which effectively applies the voltage to control gates 328 of the memory cells that are coupled to WL1. Simultaneously, a voltage may be applied across drain 202 and source 203 of one of the memory cells in a group 225. For example, approximately five volts may be applied to GBLi and GBLi+1 may be grounded. Also, select transistors S0 and S1 may be turned on by applying an appropriate voltage to S0 and S1. These voltages generate a vertical and lateral electric field in the activated memory cell(s) (e.g., the circled memory cell in
When two bits are stored in charge storage layer 322, the second bit is programmed in a manner similar to the first bit, except that the source and drain terminals are reversed in both directions.
As previously mentioned, multiple memory cells 201 in a row (i.e., the memory cells 201 having a common word line) can be simultaneously programmed by activating a word line and pairs of select transistors S0 through S7 in different groups 225. Simultaneously programming multiple memory cells 201 can be conceptually thought of as programming multiple memory cells within a “program window.” In the exemplary implementation described herein, the program window size will be described as being 256 bits wide. That is, programming is performed in 256-bit chunks. One of ordinary skill in the art will recognize that other program window sizes could be used.
A programming window 515 is illustrated in
Memory programming will be further described herein as being based on a 64-bit sub-window 520. One or ordinary skill in the art will recognize that other programming sub-window sizes could be used. Also, the concept of having a programming window including sub-windows may alternatively be implemented as a single programming window without sub-windows.
Although sub-window 520 includes 64 bits, a program technique referred to herein as an inverse programming method may be used, which ensures that at most, only half of these bits (i.e., 32) will actually need to be programmed to their respective memory cells. Additionally, memory configuration bits that are not related to the substantive data programmed to memory cells 201 may also need to be programmed with these 32 (maximum) number of bits. These configuration bits may include bits such as a spare bit, an indication bit, and a dynamic reference bit. In one implementation, a maximum of five configuration bits may need to be programmed for each sub-window 520, giving 37 total maximum bits for programming for each 64-bit sub-window 520.
The inverse programming method dynamically selects how to interpret a programmed cell 201 based on the data in sub-window 520. For example, if a non-programmed memory cell 201 (i.e., a cell with no stored charge) is normally interpreted as being a logical one, and sub-window 520 includes all logical zeros, instead of programming all the bits in sub-window 520 (i.e., 64 bits), the non-programmed memory cells 201 in sub-window 520 may instead be interpreted as corresponding to a logic zero. In this manner, instead of programming all 64 bits of sub-window 520, none of the bits in sub-window 520 need to be programmed. In this example, as few as one configuration bit may be programmed, such as the dynamic reference bit, to indicate that the memory cells in the sub-window are to be interpreted with non-programmed memory cells being a logic zero.
In one implementation, multiple sub-windows 520 may be simultaneously programmed. The number of sub-windows 520 that are simultaneously programmed in a particular programming operation may be based on the total number of bits that need to be programmed within the sub-windows 520. For example, assume that voltage supply generator 112 can supply enough voltage to simultaneously program a maximum of approximately 40 bits at any one time. In this situation, if the total number of memory cells 201 in 256-bit window 515 that are to be programmed is less than this number (e.g., 40), all four sub-windows 520 may be simultaneously programmed. If the total number of memory cells 201 in 256-bit window 515 that are to be programmed is greater than the maximum, however, a subset of the four sub-windows 520 may be simultaneously programmed. For example, if the total number of memory cells 201 in 256-bit window 515 that are to be programmed is 100, with 25 memory cells in each sub-window 520, sub-windows 520 may be programmed one after the other until all four sub-windows 520 are programmed.
As an example of voltages applied to the bit lines in
With the voltages applied as shown in
As a second example of programming memory cells in groups 225-1 through 225-3, consider the situation in which program bit 10 of memory cell c2 in groups 225-1 and 225-3 is to be programmed, but not memory cell c2 in group 225-2. Conventionally, voltages may be applied through select switches in groups 225-1 through 225-3 in a manner similar to when program bit 10 of cell c2 in each of groups 225-1 through 225-3 are to be programmed, except that the drain voltages (DD) are not applied in group 225-2. This situation is illustrated in
The grounded source (SS) bit lines in group 225-2 create a voltage potential with the drain bit lines (DD) in group 225-1. In the example shown in
For select sub-windows 520 that are to be written, logic in memory device 100, such as, for example, logic in Y-decoder circuitry 108 or control logic 106, may determine which bits in the selected sub-window require programming (act 703). The inverse programming method, as described previously, may be used to minimize the required number of memory cells 201 that need to be programmed. Data corresponding to the sub-windows 520 may then be sequentially written to the memory cells. Depending on the data pattern within program window 515, multiple sub-windows 520 may be simultaneously written (act 703).
In addition, based on the data pattern that is being programmed, source bit lines that were grounded in the previous programming operation may be floated to increase or maximize the drain to source distance along a row (act 704). An example of this concept was described above with reference to
Acts 703 and 704 may be repeated for the other sub-windows in programming window 515 (act 705).
Data dependent programming techniques were described above in which source lines of memory cells are controlled to maximize bit line distance between drain and source voltages. Advantageously, leakage current can be reduced.
The foregoing description of exemplary embodiments of the invention provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention.
Moreover, while series of acts have been described with regard to
No element, act, or instruction used in the description of the invention should be construed as critical or essential to the invention unless explicitly described as such. Also, as used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise.
Number | Name | Date | Kind |
---|---|---|---|
5291446 | Van Buskirk et al. | Mar 1994 | A |
5301097 | McDaniel | Apr 1994 | A |
5430674 | Javanifard | Jul 1995 | A |
5539688 | Yiu et al. | Jul 1996 | A |
5638326 | Hollmer et al. | Jun 1997 | A |
5748534 | Dunlap et al. | May 1998 | A |
5751637 | Chen et al. | May 1998 | A |
5757711 | Nakaoka et al. | May 1998 | A |
5890192 | Lee et al. | Mar 1999 | A |
5892710 | Fazio et al. | Apr 1999 | A |
6044022 | Nachumovsky | Mar 2000 | A |
6101125 | Gorman | Aug 2000 | A |
6163483 | Pasotti et al. | Dec 2000 | A |
6259635 | Khouri et al. | Jul 2001 | B1 |
6272670 | Van Myers et al. | Aug 2001 | B1 |
6295228 | Pawletko et al. | Sep 2001 | B1 |
6327181 | Akaogi et al. | Dec 2001 | B1 |
6424570 | Le et al. | Jul 2002 | B1 |
6426893 | Conley et al. | Jul 2002 | B1 |
6452869 | Parker | Sep 2002 | B1 |
6487121 | Thurgate et al. | Nov 2002 | B1 |
6496410 | Parker | Dec 2002 | B1 |
6515903 | Le et al. | Feb 2003 | B1 |
6519180 | Tran et al. | Feb 2003 | B2 |
6535419 | Parker et al. | Mar 2003 | B2 |
6538923 | Parker | Mar 2003 | B1 |
6563745 | Ilkbahar | May 2003 | B1 |
6570785 | Mangan et al. | May 2003 | B1 |
6597619 | Stubbs et al. | Jul 2003 | B2 |
6665215 | Thomas et al. | Dec 2003 | B2 |
6687159 | Pasotti et al. | Feb 2004 | B2 |
6724662 | Manea | Apr 2004 | B2 |
6735117 | Ott | May 2004 | B2 |
6747900 | Park et al. | Jun 2004 | B1 |
6775187 | Hamilton et al. | Aug 2004 | B1 |
6816001 | Khouri et al. | Nov 2004 | B2 |
6842388 | Origasa et al. | Jan 2005 | B2 |
6906966 | Shor et al. | Jun 2005 | B2 |
6914835 | Nakamura et al. | Jul 2005 | B2 |
6947347 | Fujioka | Sep 2005 | B2 |
6952366 | Forbes | Oct 2005 | B2 |
6996021 | Derner et al. | Feb 2006 | B2 |
7020018 | Hsieh et al. | Mar 2006 | B2 |
7057939 | Li et al. | Jun 2006 | B2 |
7149110 | Tran et al. | Dec 2006 | B2 |
7151701 | Combe et al. | Dec 2006 | B2 |
7154794 | Ahne et al. | Dec 2006 | B2 |
7177184 | Chen | Feb 2007 | B2 |
7190616 | Forbes et al. | Mar 2007 | B2 |
20010040836 | Mori et al. | Nov 2001 | A1 |
20020167844 | Han et al. | Nov 2002 | A1 |
20030046481 | Kushnarenko | Mar 2003 | A1 |
20030093233 | Rajguru | May 2003 | A1 |
20030142544 | Maayan et al. | Jul 2003 | A1 |
20030172309 | Cioaca | Sep 2003 | A1 |
20040027857 | Ooishi | Feb 2004 | A1 |
20040037113 | Ooishi | Feb 2004 | A1 |
20040109354 | Wang et al. | Jun 2004 | A1 |
20070035991 | Chen et al. | Feb 2007 | A1 |
Number | Date | Country |
---|---|---|
WO 03063167 | Jul 2003 | WO |
WO 2005106891 | Nov 2005 | WO |
Entry |
---|
2002 IEEE International Solid-State Circuits Conference, Session 6, “SRAM and Non-Volatile Memories”, Feb. 4, 2004, 6 pages. |
2002 IEEE International Solid-State Circuits Conference, 29 pages. |
Co-pending U.S. Appl. No. 11/212,614, filed Aug. 29, 2005, entitled: “Voltage Regulator with Less Overshoot and Faster Settling Time,” Yonggang Wu et al.; 30 pp. |
Co-pending U.S. Appl. No. 11/229,664, filed Sep. 20, 2005, entitled: “Flash Memory Programming Using an Indication Bit to Interpret State,” Takao Akaogi et al.; 25 pp. |
International Search Report and Written Opinion dated Jan. 15, 2007. |