Reducing program verification for multi-level nand cells
By dynamically adjusting the number of verification steps in a multi-level NAND cell, the problem of inaccurate estimation of programming verification steps in the prior art is solved, thereby optimizing programming time and improving performance.
Patent Information
- Application Number
- CN202110640905.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-06-22
- Filing Date
- 2021-06-09
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2041-06-09
AI Technical Summary
In the programming verification process of multi-level NAND cells, existing technologies make it difficult to accurately estimate and skip the number of verification steps, resulting in programming time that is too long or too short, affecting device performance.
By characterizing the device during manufacturing and dynamically adjusting the number of verification steps, the programming and verification cycle can be adjusted in real time according to changes in device characteristics, reducing unnecessary verification steps and improving programming efficiency.
The programming verification process has been optimized, programming time has been reduced, the performance and efficiency of NAND devices have been improved, and performance fluctuations caused by unchanged hard-coded values have been avoided.
Smart Images

Figure CN113903387B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of this disclosure generally relate to multi-level NAND cells, and more specifically, to skipping the programming verification level for multi-level NAND cells. Background Technology
[0002] A single-level cell (SLC) maintains a voltage above or below a threshold and stores one bit of information. A multi-level cell (MLC) has multiple possible voltage ranges. For example, an MLC with four possible states can hold two bits of information; while an MLC with eight possible states can hold four bits of information.
[0003] To set the MLC value, a write voltage is applied. After applying the write voltage, the MLC value is checked, and if necessary, the write voltage is applied again. This process continues until the MLC reaches the desired voltage. Summary of the Invention
[0004] In one aspect, this disclosure provides a system comprising: a multilevel cell (MLC) NAND flash memory array; and a memory controller coupled to the MLC NAND flash memory array and configured to perform a programming operation on the MLC NAND flash memory array, including: applying a first programming voltage to a first word line of the MLC NAND flash memory array during a first programming operation, the word line forming a control gate for a first set of memory cells in the array; performing a first verification operation to determine a first programming validity metric including a first amount of the first set of memory cells successfully programmed to a first level in response to the first programming voltage; and determining, based on the first programming validity metric and a predetermined threshold, whether to perform a second verification operation to determine a second programming validity metric including a second amount of the first set of memory cells successfully programmed to a second level by the first programming voltage.
[0005] In another aspect, this disclosure further provides a non-transitory machine-readable medium storing instructions that, when executed by a system, cause the system to perform operations including: applying a first programming voltage to a first word line of an MLC NAND flash memory array during a first programming operation, the word line forming a control gate of a first set of memory cells in the array; performing a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells successfully programmed to a first level in response to the first programming voltage; and determining, based on the first programming validity measure and a predetermined threshold, whether to perform a second verification operation to determine a second programming validity measure including a second amount of the first set of memory cells successfully programmed to a second level by the first programming voltage.
[0006] In another aspect, this disclosure further provides a method comprising: applying a first programming voltage to a first word line of an MLC NAND flash memory array during a first programming operation, the word line forming a control gate of a first set of memory cells in the array; performing a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells successfully programmed to a first level in response to the first programming voltage; and determining, based on the first programming validity measure and a predetermined threshold, whether to perform a second verification operation to determine a second programming validity measure including a second amount of the first set of memory cells successfully programmed to a second level by the first programming voltage. Attached Figure Description
[0007] This disclosure will be more fully understood from the detailed description given below and the accompanying drawings of various embodiments thereof. However, the drawings should not be construed as limiting this disclosure to the specific embodiments, but are for explanation and understanding only.
[0008] Figure 1 This is a block diagram of an example system of a memory device containing programming verification suitable for reducing multi-level NAND cells.
[0009] Figure 2 A schematic diagram illustrating an example of a three-dimensional (3D) NAND architecture semiconductor memory array.
[0010] Figure 3 A schematic diagram illustrating an example of a three-dimensional (3D) NAND architecture semiconductor memory array.
[0011] Figure 4 Illustrate an example block diagram of a memory module.
[0012] Figure 5 This is a flowchart illustrating the operation of a method performed by a circuit in programming verification of a reduced-level NAND cell according to some embodiments of the present disclosure.
[0013] Figure 6 This is a flowchart illustrating the operation of a method performed by a circuit in programming verification of a reduced-level NAND cell according to some embodiments of the present disclosure.
[0014] Figure 7 This is a flowchart illustrating the operation of a method performed by a circuit in programming verification of a reduced-level NAND cell according to some embodiments of the present disclosure.
[0015] Figure 8 This is a block diagram of an example computer system in which embodiments of the present disclosure can be operated. Detailed Implementation
[0016] For example, a typical N-channel metal-oxide-semiconductor field-effect transistor (MOSFET) has a constant threshold voltage. The threshold voltage is the minimum voltage applied to the gate of the transistor that allows current to flow from the source to the drain. Therefore, a typical transistor is a control device, not a storage device. A NAND cell contains a charge storage element, the charge of which affects the threshold voltage of the NAND cell. Such a charge storage element can be, for example, a charge trap region or structure that selectively stores charge in a dielectric material; or alternatively, a floating gate, which typically selectively stores charge in a polysilicon structure. All of the above charge storage structures or regions are generally referred to herein as "charge storage elements". Therefore, by applying a voltage to the gate and detecting whether current flows from the source to the drain, a NAND cell can be used as a data storage device.
[0017] Furthermore, multiple different charge levels of the charge storage element are possible, allowing multiple data bits to be stored in a single NAND cell. For example, the cell can hold a value of 00 at a threshold voltage of 0V; a value of 01 at a threshold voltage of 0.5V; a value of 10 at a threshold voltage of 1.0V; and a value of 11 at a threshold voltage of 1.5V.
[0018] Due to the physical differences within individual NAND cells, the programming process for MLCs is iterative. A programming voltage is applied to add or remove charge from the charge storage element. A verification voltage is applied to determine the threshold voltage of the programmed NAND cell. If the threshold voltage corresponds to the expected stored value, programming is complete. Otherwise, the process is repeated. In this way, each NAND cell can be successfully programmed even if the NAND cells in the device have different physical characteristics.
[0019] To save time in executing programming / verification cycles, multiple programming cycles can be executed without intervening in the verification cycle. If the number of skipped verification steps is higher than optimal, successful programming will not be immediately confirmed, and more programming steps than necessary will be executed. If the number of skipped verification steps is lower than optimal, more verification steps will be executed than necessary. Therefore, accurately estimating how many verification steps to skip reduces the write time of the NAND device, thereby improving performance.
[0020] One method for estimating the number of verification steps to skip is to characterize the device during manufacturing. This characterization estimate is hardcoded into the device, and over the device's lifetime, the number of verification steps to skip during data writing is determined. However, over time, the number of write cycles required to successfully program the MLC decreases. Because the hardcoded values do not change throughout the device's lifetime, the device may perform too many verification steps at one stage of its lifetime and wait too long to begin verification at another stage, thus reducing device performance.
[0021] As discussed herein, verification for programming at higher voltage levels (e.g., 1.0V) is delayed until verification for programming at lower voltage levels (e.g., 0.5V) reaches at least the success threshold level. Since the number of programming / verification cycles executed to reach the success threshold level is a measure of the device's physical performance, the number of verification cycles skipped for higher voltage programming levels will dynamically vary with device characteristics. Consequently, performance drawbacks associated with skipping a number of hard-coded verification cycles are unlikely.
[0022] Figure 1 A block diagram of an example system 100 including a memory system 110 (e.g., an SSD storage device, an SD / MMC card, etc.) having a memory controller 140 with a control module 142 suitable for implementing the write verification optimization techniques discussed herein. In this example, the functionality of the control module 142 may be implemented in a corresponding module in the firmware of the memory controller 140. However, it should be understood that the controller 140 may utilize various forms of software, firmware, and hardware to implement the control module 142 (e.g., to implement the functionality of programmable control 160) and other techniques discussed herein.
[0023] As shown, memory system 110 includes NAND memory device 130 having a plurality of dies (dies 1-N), wherein each die includes one or more blocks (blocks 1-N). Each of the one or more blocks may include further subdivided portions, such as one or more word lines (not shown) per block; and depending on the number of data states that the memory cells of the word line are configured to store, each of the one or more word lines may further consist of one or more pages (not shown) per word line.
[0024] In this example, the block of memory cells in memory device 130 comprises at least one of the following groups: single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), or quad-level cell (QLC) NAND memory cells. Furthermore, in this example, memory device 130 is arranged as a stack of three-dimensional (3D) NAND dies. For simplicity, [the text is incomplete]. Figure 1The configuration and other detailed components of memory device 130 are described herein. However, memory device 130 may incorporate these features or any features described above with reference to 3D NAND architecture devices or other forms of NAND storage devices.
[0025] In 3D architecture semiconductor memory technology, vertical structures are stacked, thereby increasing the number of layers, physical pages, and thus the density of memory devices (e.g., storage devices). In one example, memory system 110 may be a discrete memory or storage device component of host device 120. In other examples, memory system 110 may be part of an integrated circuit (e.g., a system-on-a-chip (SoC) or the like) that is stacked with or otherwise includes one or more other components of host device 120.
[0026] In a NAND flash memory array, each flash memory cell can be programmed to have two or more programmed states. For example, an SLC can represent one of two programmed states (e.g., 1 or 0), representing one data bit. Flash memory cells can also represent more than two programmed states, allowing for the fabrication of higher-density memory without increasing the number of memory cells, since each cell can represent more than one binary digit (e.g., more than one bit). Such cells may be referred to as multi-state memory cells, multi-digit cells, or multi-level cells (MLCs). In some instances, an MLC may refer to a memory cell that can store two data bits per cell (e.g., one of four programmed states), a TLC may refer to a memory cell that can store three data bits per cell (e.g., one of eight programmed states), and a QLC may store four data bits per cell. In its broader context, MLC is used herein to refer to any memory cell that can store more than one data bit per cell (i.e., can represent more than two programmed states; therefore, the term MLC is used in its broader context herein to refer to memory cells that store 2, 3, 4 or more data bits per cell).
[0027] Memory system 110 is shown operatively coupled to host 120 via a controller 140 for the memory devices. Controller 140 is adapted to receive and process host I / O commands 125, such as read operations, write operations, erase operations, etc., to read, write, erase, and manage data stored in memory device 130. In other instances, memory controller 140 may be physically decoupled from individual memory devices and may receive and process commands from one or more individual memory devices. For simplicity, various other components of memory system 110 (e.g., memory manager and other circuitry or operational components) and controller 140 are not depicted.
[0028] The controller 140 is depicted as including a memory 144 (e.g., volatile memory), a processing circuitry 146 (e.g., a microprocessor), and a storage medium 148 (e.g., non-volatile memory). The controller is used to execute instructions (e.g., instructions hosted by the storage medium 148, loaded into the memory 144, and executed by the processing circuitry 146) to implement the control module 142 for managing and using the memory device 130. The functionality provided by the control module 142 may include, but is not limited to: I / O operation monitoring 150 (e.g., monitoring read and write I / O operations originating from host commands); host operation processing 155 (e.g., interpreting and processing host I / O commands 125 and issuing other commands to the memory array 530 to perform corresponding read, write, erase, or other host-initiated operations); programming control 160 (e.g., controlling the timing, criteria, conditions, and parameters of corresponding programming verification operations 185 on the memory device 130); programming voltage control 170 (e.g., establishing, setting, and utilizing programming voltage levels to program specific portions of the memory device 130); verification calibration 180 (e.g., operating a calibration procedure to identify new programmed voltage levels for one or more specific portions of the memory device 130); and error detection processing 190 (e.g., identifying and correcting errors from data obtained in read operations, identifying one or more raw bit error rates (RBER) for a specific read operation or set of operations, etc.).
[0029] Host commands 125 can be transmitted between the memory system 110 and one or more other components of the host device 120 using one or more communication interfaces, such as Serial Advanced Technology Attachment (SATA) interfaces, Peripheral Component Interconnect High Speed (PCIe) interfaces, Universal Serial Bus (USB) interfaces, Universal Flash Memory (UFS) interfaces, eMMC™ interfaces, or one or more other connectors or interfaces. The host device 120 may include a host system, electronic devices, a processor, a memory card reader, or one or more other electronic devices external to the memory system 110. In some instances, the host device 120 may be a device with a reference... Figure 8 The machine 800 is a component of the machine, either a part or all of it.
[0030] In this example, host operation processing 155 interprets and processes host I / O commands 125 (e.g., read and write commands) and accompanying commands in start controller 140 and memory device 130 to implement host I / O commands 125. Furthermore, host operation processing 155 can coordinate the timing, conditions, and parameters of programmable control 160 in response to host I / O commands 125, I / O operation monitoring 150, and error detection processing 190.
[0031] In some example embodiments, I / O operation monitoring 150 is used to track reads and writes to memory device 130 initiated by host I / O commands. I / O operation monitoring 150 is also used to track accompanying I / O operations and states, such as host I / O activity or inactivity (e.g., where an active state corresponds to the controller 140 and memory device 130 actively performing a read or write operation initiated from host 120, and where an inactive state corresponds to the absence of such I / O operations initiated from host 120). I / O operation monitoring 150 may also be used in conjunction with parameters of the programming control 160 as discussed herein to monitor voltage levels and read error rates associated with I / O operations initiated from host 120.
[0032] Programming control 160 may include, in particular, circuitry or components (hardware and / or software) configured to control memory operations associated with writing data to, reading data from, or erasing data from one or more memory cells of memory device 130 coupled to memory controller 140. In an example, programming control 160 is used to identify parameters in memory device 130 and controller 140 for scheduling and performing programming verification operation 185, such as based on I / O conditions (e.g., indicated by I / O operation monitoring 150) or error conditions (e.g., indicated by error detection processing 190). Programming control 160 is further used to initiate and execute programming verification operation 185 based on these or other parameters via synchronous or asynchronous event processing.
[0033] In some example embodiments, programming voltage control 170 is used to establish, modify, and provide voltage values for programming specific regions of the memory (e.g., corresponding blocks in memory device 130). For example, programming voltage control 170 may implement various positive or negative offsets to program corresponding memory cells and memory locations (e.g., pages, blocks, dies) containing the corresponding memory cells.
[0034] In this example, verification calibration 180 is used to determine (e.g., whether a verification operation should be performed after a programming operation, such as a change, update, or reset). Verification calibration 180 may be performed based on the number or percentage of bits in the NAND memory device 130 that were successfully programmed at a lower voltage level.
[0035] In some example embodiments, the error detection process 190 can detect recoverable error conditions (e.g., RBER values or RBER trends), unrecoverable error conditions, or other measurements or error conditions (e.g., averages or samples from blocks, block groups, dies, die groups, etc.) of a larger area of a memory cell, cell group, or memory array.
[0036] Additionally, the sampling and reading operations performed during the read scan by the programming control 160 may allow configurations based on specifications (e.g., determined settings or calculations) such as: the size of the programmed data (e.g., data corresponding to pages, blocks, block groups, or dies); the total number of programmed pages; the number of pages within a programmed block; and whether certain units, pages, blocks, dies, or certain types of such units, pages, blocks, or dies are programmed. Similarly, the programming control 160 may control or allow configurations of: the number of programming cycles executed before the first verification cycle; the number of programming cycles executed between verification cycles; and the number of bits that will be successfully programmed at each level before the start of the next level verification.
[0037] In addition to the techniques discussed herein, other types of maintenance operations may be performed by the control module 142 in the controller 140. Such operations may include garbage collection or recycling, wear leveling, block management, and other forms of background activity performed on the memory device 130. Such background activity may be triggered during idle states detected by the I / O operation monitoring 150 (e.g., immediately following or simultaneously with a read scan operation).
[0038] The programming control 160 may include an error correction code (ECC) component, which may in particular include an ECC engine or other circuitry configured to detect or correct errors associated with writing or reading data from one or more memory cells of the memory device 130 coupled to the memory controller 140. The memory controller 140 may be configured to effectively detect and recover from errors associated with various operations or data storage (e.g., bit errors, operational errors, etc.), while maintaining the integrity of data transferred between the host device 120 and the memory system 110, or maintaining the integrity of stored data (e.g., using redundant RAID storage, etc.), and may remove (e.g., deactivate) faulty memory resources (e.g., memory cells, memory arrays, pages, blocks, etc.) to prevent future errors.
[0039] Memory device 130 may include a number of memory cells arranged, for example, in multiple devices, planes, sub-blocks, blocks, or pages. As an example, a 48GB TLC NAND memory device may contain 18,592 bytes (B) of data per page (16,384 + 2208 bytes), 1536 pages per block, 548 blocks per plane, and four or more planes per device. As another example, a 32GB MLC memory device (each cell storing two data bits (i.e., four programmable states)) may contain 18,592 bytes (B) of data per page (16,384 + 2208 bytes), 1024 pages per block, 548 blocks per plane, and four planes per device, but requires half the write time and twice the program / erase (P / E) cycles compared to the corresponding TLC memory device. Other examples may contain other numbers or arrangements. In some examples, the memory device or portions thereof may operate selectively in SLC mode or in a desired MLC mode (e.g., TLC, QLC, etc.).
[0040] In operation, data is typically written to or read from memory system 110 in pages and erased in blocks. However, one or more memory operations (e.g., read, write, erase, etc.) may be performed on larger or smaller groups of memory cells as needed. The data transfer size of NAND memory system 110 is typically referred to as a page; while the data transfer size of the host is typically referred to as a sector.
[0041] While a data page may contain multiple bytes of user data (e.g., a data payload comprising multiple data sectors) and its corresponding metadata, the page size often refers only to the number of bytes used to store the user data. As an example, a data page with a page size of 4KB may contain 4KB of user data (e.g., eight sectors of a sector size assuming 512B) and multiple bytes of metadata corresponding to the user data (e.g., 32B, 54B, 224B, etc.), such as integrity data (e.g., error detection or correction code data), address data (e.g., logical address data, etc.), or other metadata associated with the user data.
[0042] Different types of memory cells or memory devices 130 may offer different page sizes or require different amounts of metadata associated with them. For example, different memory device types may have different bit error rates, which may result in different amounts of metadata being required to ensure the integrity of data pages (e.g., a memory device with a higher bit error rate may require more bytes of error correction code data than a memory device with a lower bit error rate). As an example, a multi-level cell (MLC) NAND flash device may have a higher bit error rate compared to a corresponding single-level cell (SLC) NAND flash device. Therefore, an MLC device may require more bytes of metadata for erroneous data than a corresponding SLC device.
[0043] Figure 2 The description includes multiple memory cell strings (e.g., first to third A0 memory strings 205A0-207A0, first to third A0). n Memory String 205A n -207A n The first to third B0 memory strings are 205B0-207B0, the first to third B0 n Memory String 205B n -207B n A schematic diagram of an example of a 3D NAND architecture semiconductor memory array 200, wherein the memory cell strings are organized into blocks (e.g., block A 201A, block B 201B, etc.) and sub-blocks (e.g., sub-block A0 201A0, sub-block A0 201A0, etc.). n 201A n Sub-block B0201B0, Sub-block B n 201B n (etc.). Memory array 200 represents a portion of a large number of similar structures that are typically found in blocks, devices, or other units of a memory device.
[0044] Each memory cell string contains multiple layers of charge storage transistors (e.g., floating gate transistors, charge trap structures, etc.), which are stacked in the Z direction from source to drain on the source line (SRC) 235 or the source-side selected gate (SGS) (e.g., first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 SGS 231A0-233A0, first to third A0 233A0-233A0, 231 ... n SGS 231A n -233A n First to third B0 SGS 231B0-233B0, first to third B n SGS 231B n -233B n(etc.) and drain-side selected gate (SGD) (e.g., first to third A0 SGD 226A0-228A0, first to third A n SGD 226A n -228A n First to third B0 SGD 226B0-228B0, first to third B n SGD 226B n -228B n Between (etc.). Each string of memory cells in a 3D memory array can be arranged as data lines (e.g., bit lines (BL) BL0 220 to BL2 222) along the X direction and as physical pages along the Y direction.
[0045] Within a physical page, each level represents a row of memory cells, and each string of memory cells represents a column. A sub-block may contain one or more physical pages. A block may contain multiple sub-blocks (or physical pages) (e.g., 128, 256, 384, etc.). Although described herein as having two blocks, each block having two sub-blocks, each sub-block having a single physical page, each physical page having three strings of memory cells, and each string having eight levels of memory cells, in other instances, the memory array 200 may contain more or fewer blocks, sub-blocks, physical pages, strings of memory cells, memory cells, or levels. For example, each string of memory cells may contain more or fewer levels as needed (e.g., 16, 32, 64, 128, etc.), and one or more additional levels of semiconductor material above or below charge storage transistors (e.g., select gates, data lines, etc.). As an example, a 48GB TLC NAND memory device may contain 18,592 bytes (B) of data per page (16,384+2208 bytes), 1536 pages per block, 548 blocks per plane, and 4 or more planes per device.
[0046] Each memory cell in the memory array 200 includes a control gate (CG) coupled to (e.g., electrically or otherwise operably connected to) access lines (e.g., word lines (WL) WL00 210A to WL70 217A, WL01 210B to WL71 217B, etc.), which, as needed, jointly couple the control gate (CG) across a specific level or a portion of a level. The respective access lines can be used to access or control a specific level in the 3D memory array, and thus access or control a specific memory cell in a string. Various select lines can be used to access select gate groups. For example, the A0 SGD line SGDA0 225A0 can be used to access the first to third A0 SGD 226A0-228A0, and A... n SGD line SGDA n 225An To access the first to third A n SGD 226A n -228A n You can use B0 SGD lines SGDB0 225B0 to access the first to third B0 SGD226B0-228B0, and you can use B n SGD line SGDB n 225B n To access the first to third B n SGD 226B n -228B n The first to third A0 gates (SGS 231A0-233A0) and the first to third A0 gates (SGS 231A0-233A0) can be accessed using the gate select lines SGS0 230A. n SGS231A n -233A n Furthermore, the first to third B0 SGS 231B0-233B0 and the first to third B0 can be accessed using the gate select lines SGS1 230B. n SGS 231B n -233B n .
[0047] In an example, memory array 200 may comprise a multi-level semiconductor material (e.g., polysilicon, etc.) configured to couple a control gate (CG) or select gate (or a portion of a CG or select gate) to each memory cell at a corresponding level of the array. A combination of bit lines (BLs) and select gates, etc., can be used to access, select, or control a specific string of memory cells in the array, and one or more access lines (e.g., word lines) can be used to access, select, or control a specific memory cell at one or more levels within a specific string.
[0048] Figure 3 The illustration shows an example of a portion of a NAND-based semiconductor memory array 300, comprising multiple memory cells 302 arranged in a two-dimensional array of strings (e.g., first to third strings 305-307) and layers (e.g., illustrated as corresponding word lines (WL) WL0 310 to WL7 317, drain-side selected gate (SGD) line 325, source-side selected gate (SGS) line 330, etc.) and a sense amplifier or device 360. For example, the memory array 300 may illustrate, for instance... Figure 2 The diagram illustrates an example of a portion of a physical page of a memory cell in a 3D NAND architecture semiconductor memory device.
[0049] Each memory cell string is coupled to a source line (SRC) using a corresponding source-side selected gate (SGS) (e.g., first to third SGS 331-333) and to a corresponding data line (e.g., first to third bit lines (BL) BL0 320 to BL2 322) using a corresponding drain-side selected gate (SGD) (e.g., first to third SGD 326-328). Although in Figure 3 The example is described as having 8 levels (e.g., using word lines (WL) WL0 310 to WL7 317) and three data lines (BL0 326 to BL2 328), but other examples may contain strings of memory cells with more or fewer levels or data lines as needed.
[0050] In a NAND architecture semiconductor memory array, such as instance memory array 300, the state of a selected memory cell 302 can be accessed by sensing current or voltage changes associated with a specific data line containing the selected memory cell. Memory array 300 can be accessed using one or more drivers (e.g., control circuitry, one or more processors, digital logic, etc.). In this instance, depending on the type of operation to be performed on a specific memory cell or set of memory cells, one or more drivers can activate a specific memory cell or set of memory cells by driving a specific potential to one or more data lines (e.g., bit lines BL0-BL2), access lines (e.g., word lines WL0-WL7), or a select gate.
[0051] To program or write data to a memory cell, a programming voltage (Vpgm) (e.g., one or more programming pulses, etc.) is applied to the selected word line (e.g., WL4), and thus to the control gate of each memory cell coupled to the selected word line (e.g., the first to third control gates (CG) 341-343 of the memory cell coupled to WL4). For example, the programming pulse may begin at or near 15V, and in some instances, the amplitude may increase during each programming pulse application. When the programming voltage is applied to the selected word line, a potential such as ground potential (e.g., Vss) may be applied to the data line (e.g., bit line) and the substrate of the memory cell targeted for programming (and therefore, the channel between the source and drain), resulting in charge transfer from the channel to the charge storage element of the target memory cell (e.g., direct injection or Fowler-Nordheim (FN) tunneling, etc.).
[0052] In contrast, a pass voltage (Vpass) can be applied to one or more word lines having memory cells that are not targeted for programming, or a suppressor voltage (e.g., Vcc) can be applied to data lines (e.g., bit lines) having memory cells that are not targeted for programming, to, for example, suppress charge transfer from the channel to charge storage elements of such non-target memory cells. The pass voltage can vary, for example, depending on the proximity of the applied pass voltage to the word line that is targeted for programming. The suppressor voltage can include a supply voltage (Vcc), such as a voltage from an external source or power source (e.g., a battery, an AC-to-DC converter, etc.) relative to a ground potential (e.g., Vss).
[0053] As an example, if a programming voltage (e.g., 15V or higher) is applied to a specific word line, such as WL4, a 10V pass-through voltage can be applied to one or more other word lines, such as WL3, WL5, etc., to suppress programming of non-target memory cells or to preserve values stored in such memory cells that are not intended for programming. As the distance between the applied programming voltage and the non-target memory cell increases, the pass-through voltage required to avoid programming the non-target memory cell can decrease. For example, with a 15V programming voltage applied to WL4, a 10V pass-through voltage can be applied to WL3 and WL5, an 8V pass-through voltage to WL2 and WL6, a 7V pass-through voltage to WL1 and WL7, etc. In other examples, the pass-through voltage or the number of word lines can be higher or lower, more or fewer.
[0054] The sensing amplifier 360 coupled to one or more (e.g., first, second, or third bit lines (BL0-BL2) 320-322) in the data lines can detect the state of each memory cell in the corresponding data line by sensing the voltage or current on the specific data line.
[0055] Between the application of one or more programming pulses (e.g., Vpgm), a verification operation can be performed to determine whether the selected memory cell has reached its intended programmed state. If the selected memory cell has reached its intended programmed state, further programming of it can be suppressed. If the selected memory cell has not yet reached its intended programmed state, additional programming pulses can be applied. If the selected memory cell has not reached its intended programmed state after a certain number of programming pulses (e.g., a maximum number), the selected memory cell or the string, block, or page associated with such selected memory cell can be marked as defective.
[0056] The verification operation is performed by applying a verification voltage to the control gate of each transistor being verified, applying a bias voltage to source line 335, and providing a sensed current (e.g., 3 μA) to each of bit lines 320-322. As a result, the gate-to-source voltage Vgs of each transistor is equal to the verification voltage minus the bias voltage, and current will only be turned on or conducted if the transistor's threshold voltage Vt is less than or equal to Vgs. The verification voltage and bias voltage should ensure that Vgs is at least equal to the desired threshold voltage. Determining whether any current flows through the NAND string indicates whether all transistors have been properly programmed, i.e., each transistor has a threshold voltage greater than or equal to the desired threshold voltage.
[0057] Figure 4 The illustrated block diagram of a memory device 400 includes a memory array 402 having a plurality of memory cells 404, and one or more circuits or components for providing communication with the memory array 402 or performing one or more memory operations on the memory array. The memory device 400 may include a row decoder 412, a column decoder 414, a sense amplifier 420, a page buffer 422, a selector 424, input / output (I / O) circuitry 426, and a memory control unit 430.
[0058] The memory cells 404 of the memory array 402 can be arranged in blocks, such as a first block 402A and a second block 402B. Each block can contain sub-blocks. For example, the first block 402A can contain a first sub-block 402A0 and a second sub-block 402A0. n Furthermore, the second sub-block 402B may contain the first sub-block 402B0 and the second sub-block 402B. n Each subblock may contain multiple physical pages, and each page contains multiple memory cells 404. Although described herein as having two blocks, each block having two subblocks, and each subblock having multiple memory cells 404, in other instances, the memory array 402 may contain more or fewer blocks, subblocks, memory cells, etc. In other instances, the memory cells 404 may be arranged in multiple rows, columns, pages, subblocks, blocks, etc., and accessed using, for example, access lines 406, first data lines 410, or one or more select gates, source lines, etc.
[0059] The memory control unit 430 can control the memory operation of the memory device 400 according to one or more signals or instructions received on the control line 432. These signals or instructions include, for example, one or more clock signals or control signals indicating the operation to be performed (e.g., write, read, erase, etc.), or address signals (A0-AX) received on one or more address lines 416. One or more devices external to the memory device 400 can control the values of the control signals on the control line 432 or the address signals on the address lines 416. Examples of devices external to the memory device 400 may include, but are not limited to, a host, a memory controller, a processor, or... Figure 4 One or more circuits or components not specified in the text.
[0060] The memory device 400 may use access lines 406 and first data lines 410 to transfer data to (e.g., write or erase) or from (e.g., read) one or more memory cells 404. Row decoder 412 and column decoder 414 may receive and decode address signals (A0-AX) from address lines 416 to determine which memory cells 404 will be accessed, and may provide signals to, for example, one or more of the access lines 406 (e.g., one or more of multiple word lines (WL0-WLm)) or the first data lines 410 (e.g., one or more of multiple bit lines (BL0-BLn)) as described above.
[0061] The memory device 400 may include a sensing circuitry system, such as a sense amplifier 420, configured to use a first data line 410 to determine (e.g., read) the value of data on the memory cell 404, or to determine the value of data to be written to the memory cell. For example, in a selected string of memory cells 404, one or more of the sense amplifiers 420 may read the logic level in the selected memory cell 404 in response to a read current flowing through the selected string to the data line 410 in the memory array 402.
[0062] One or more devices external to memory device 400 may communicate with memory device 400 using I / O lines (DQ0-DQN) 408, address lines 416 (A0-AX) or control lines 432. Input / output (I / O) circuitry 426 may use I / O lines 408 to transfer data values to or from memory device 400, for example, to or from page buffer 422 or memory array 402, according to, for example, control lines 432 and address lines 416. Page buffer 422 may store data received from one or more devices external to memory device 400 before data is programmed into the relevant portion of memory array 402, or may store data read from memory array 402 before data is transmitted to one or more devices external to memory device 400.
[0063] Column decoder 414 can receive address signals (A0-AX) and decode them into one or more column select signals (CSEL1-CSELn). Selector 424 (e.g., selector circuitry) can receive column select signals (CSEL1-CSELn) and select data in page buffer 422 representing data values to be read from or programmed into memory cell 404. The selected data can be transferred between page buffer 422 and I / O circuitry 426 using a second data line 418.
[0064] The memory control unit 430 may receive positive and negative power signals from an external source or power supply (e.g., an internal or external battery, an AC-to-DC converter, etc.), such as a power supply voltage (Vcc) 434 and a negative power supply (Vss) 436 (e.g., ground potential). In some instances, the memory control unit 430 may include a regulator 428 to internally provide positive or negative power signals.
[0065] Figure 5 This is a flowchart illustrating the operation of method 500 performed by a circuit in programming verification of a reduced-level NAND cell according to some embodiments of the present disclosure. Method 500 includes operations 510, 520, 530, 540, and 550. By way of example and not limitation, method 500 is described as being performed by... Figure 1-4 The device performs the operation.
[0066] In operation 510, programming control 160 applies a programming voltage to the word line of the MLC flash memory (e.g., ...). Figure 3 Word lines 317), the word lines forming the control gates of the first group of memory cells in the array. As described above relative to... Figure 3 As discussed, when a programming voltage (e.g., 15V) is applied to the selected word line, a potential such as ground potential can be applied to the bit line and the substrate of the memory cell targeted for programming (and therefore, the channel between the source and drain), resulting in charge transfer from the channel to the charge storage element of the target memory cell. Simultaneously, a transfer voltage or a suppression voltage (e.g., a voltage equal to the programming voltage) can be applied to the bit line having memory cells not targeted for programming to suppress charge transfer from the channel to the charge storage element of such non-target memory cells.
[0067] In operation 520, programming control 160 performs a first verification operation to determine a first measure of programming validity, including a first amount of a first set of cells successfully programmed to a first level by a first programming voltage. For example, programming verification operation 185 may be performed against the first level to test whether the threshold voltage of each programmed transistor has risen to at least the first level. In each iteration of programming, it is likely that only a subset of the memory cells coupled to the word line is programmed. Programming verification operation 185 determines the amount (e.g., the number of memory cells or the percentage of memory cells) of memory cells that have been successfully programmed in the current and previous iterations. Once a bit has been successfully programmed, those memory cells are removed from the set of memory cells for programming in further iterations. Therefore, the threshold voltage of a successfully programmed transistor will not be affected by later programming passes.
[0068] In operation 530, programming control 160 determines whether a first programming validity metric meets a predetermined threshold (e.g., whether at least 30% of a first set of memory cells programmed to a first level has been successfully programmed). The predetermined threshold can be accessed from a non-volatile storage device within controller 140 (e.g., a non-volatile portion of storage medium 148), which is programmed before power-on of memory system 110 (e.g., during production). Alternatively, the predetermined threshold may have already been received from host 120 via a bus and stored in volatile memory (e.g., a volatile portion of memory 144) for access by programming control 160.
[0069] If the threshold is met, method 500 continues to operation 540, and programming control 160 performs a programming verification operation for the second level. For example, if a first memory cell of at least the threshold amount is successfully programmed to the first level, programming verification operation 185 determines the amount of first memory cells that have been successfully programmed to the second level. Alternatively, based on the first amount and the predetermined threshold, programming control 160 skips the programming verification operation for the second level and returns to operation 510. For example, if a first memory cell less than the threshold amount is successfully programmed to the first level, operation 540 is not performed. Therefore, if the amount of memory cells successfully programmed to the first level is less than the threshold, the step of verifying programming to the second level is skipped, saving time compared to a method that performs programming verification operations at all levels after each programming iteration.
[0070] Using operation 550, where programming control 160 determines whether programming is complete, method 500 is repeated until all MLCs are successfully programmed to the expected level. The meanings of "first level" and "second level" can change between iterations. For example, once all cells programmed to the first level have been successfully programmed to that level, further verification of the original "first level" is not required. In subsequent iterations, the second level is verified in operation 520, and the third level is conditionally verified in operations 530 and 540. In this way, unnecessary verification steps (e.g., verifying the set of bits that have been 100% verified) are skipped, thereby reducing the time used to write lines to the MLC.
[0071] As described above, method 500 is executed by programming control 160 of controller 140, which controls memory device 130 within memory system 110. Alternatively, method 500 may be executed by memory control unit 430 within memory device 400, which communicates with memory controller (e.g., controller 140).
[0072] Figure 6 This is a flowchart illustrating the operation of method 600 performed by circuitry in programming verification of reduced-level NAND cells according to some embodiments of the present disclosure. Method 600 includes operations 540, 610, 620, and 550. By way of example and not limitation, method 600 is described as being performed by... Figure 1-4 The device performs the operation.
[0073] As discussed above, method 500 can be performed iteratively by repeating operations 510-550 until all levels are successfully programmed. In some example embodiments, operations 610 and 620 are inserted between operations 540 and 550.
[0074] In operation 610, programming control 160 compares a first programming validity metric determined in operation 520 with a second threshold. If the second threshold is met, the programming voltage is increased in operation 620. Otherwise, method 600 continues to operation 550.
[0075] In this way, verification of programming to the second level (in operation 540) is delayed until at least a first predetermined threshold of the line has been successfully programmed to the first level, and the programming voltage is increased when at least a second predetermined threshold of the cell group (e.g., 50%, 60%, 70%, 80%, or 90%) has been successfully programmed to the first level. Increasing the programming voltage increases the probability of programming cells to a higher voltage level, but also carries the risk of overprogramming cells to a lower voltage level. By waiting until at least a second threshold amount of cells has been successfully programmed to the first level (and thus biased for programming in future iterations) before increasing the programming voltage, the risk of overprogramming is reduced, thereby reducing the error rate. By not waiting until 100% of the cells have been successfully programmed to the first level, the number of iterations required to complete programming is reduced, thereby improving responsiveness.
[0076] As described above, method 600 is executed by programming control 160 of controller 140, which controls memory device 130 within memory system 110. Alternatively, method 600 may be executed by memory control unit 430 within memory device 400, which communicates with memory controller (e.g., controller 140).
[0077] Figure 7 This is a flowchart illustrating the operation of method 700 performed by a circuit in programming verification of a reduced-level NAND cell according to some embodiments of the present disclosure. Method 700 includes operations 710, 720, 730, 740, 750, 760, and 770. By way of example and not limitation, method 700 is described as being performed by... Figure 1-4 The device performs the operation.
[0078] In operation 710, the PVSTOP variable is initialized to 1. This variable later controls the verification step in method 700.
[0079] In operation 720, programming control 160 applies a programming voltage to the word line of the MLC flash memory (e.g., Figure 3 Word lines 317), the word lines forming the control gates of the first group of memory cells in the array. As described above relative to... Figure 3 As discussed, when a programming voltage (e.g., 15V) is applied to the selected word line, a potential such as ground potential can be applied to the bit line and the substrate of the memory cell targeted for programming (and therefore, the channel between the source and drain), resulting in charge transfer from the channel to the charge storage element of the target memory cell. Simultaneously, a transfer voltage or a suppression voltage (e.g., a voltage equal to the programming voltage) can be applied to the bit line having memory cells not targeted for programming to suppress charge transfer from the channel to the charge storage element of such non-target memory cells.
[0080] In operation 730, programming control 160 verifies the amount of cell groups successfully programmed to the PVSTOP level and below the PVSTOP level. Therefore, in the first iteration, programming control 160 only verifies the first amount of cell groups successfully programmed to the first level by the programming voltage. In iterations where PVSTOP = LMAX, the maximum number of MLC levels for cell groups and the amount of cell groups successfully programmed to each level are determined.
[0081] If, in operation 740, PVSTOP equals LMAX (i.e., if verification is performed for all levels) and programming at all levels has been verified, then programming is complete and method 700 ends. Otherwise, method 700 continues to operation 750.
[0082] If PVSTOP is equal to LMAX in operation 750, then the next iteration begins and method 700 returns to operation 720. Otherwise, method 700 continues to operation 760.
[0083] In operation 760, if the stop criterion of the PVSTOP level is not met, several cells at the next level will be successfully programmed, and the next iteration (at operation 720) begins without changing PVSTOP. However, if the stop criterion of the PVSTOP level has been met, programming control 160 increases PVSTOP before starting the next iteration (operation 770). In this case, since PVSTOP has been increased, operation 730 will attempt to verify the higher programming level during the next iteration.
[0084] As described above, method 700 is executed by programming control 160 of controller 140, which controls memory device 130 within memory system 110. Alternatively, method 700 may be executed by memory control unit 430 within memory device 400, which communicates with memory controller (e.g., controller 140).
[0085] Figure 8This block diagram illustrates an instance machine 800 on which any one or more of the techniques (e.g., methods) discussed herein can be performed. As described herein, an instance may contain, or be operated by, logic or multiple components or mechanisms in machine 800. A circuit (e.g., a processing circuit system) is a collection of circuits implemented in a tangible entity of machine 800, which includes hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership can become flexible over time. A circuit includes components that can perform a specified operation individually or in combination during operation. In an instance, the hardware of the circuit system may be perpetually designed to perform a specific operation (e.g., hardwired). In an instance, the hardware of the circuit system may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) that include machine-readable media that are physically modified (e.g., invariant magnetism of concentrated particles, electrically movable placement, etc.) to encode instructions for a specific operation. When connecting physical components, the underlying electrical characteristics of the hardware configuration change, for example, from an insulator to a conductor or vice versa. Instructions enable embedded hardware (e.g., an execution unit or a loading mechanism) to generate components of a circuit system within the hardware via variable connections to perform specific operations when in operation. Thus, in an example, a machine-readable media element is part of the circuit system or communicatively coupled to other components of the circuit system during device operation. In an example, any one of the physical components can be used in more than one component within more than one circuit system. For instance, in operation, an execution unit can be used at one point in time in a first circuit of a first circuit system and reused by a second circuit in the first circuit system, or reused at a different time by a third circuit in the second circuit system. Further examples of these components of machine 800 are given below.
[0086] In alternative embodiments, machine 800 may operate as a standalone device or be connected (e.g., networked) to other machines. In a networked deployment, machine 800 may operate as a server machine, a client machine, or both in a server-client network environment. In an example, machine 800 may act as a peer-to-peer (P2P) (or other distributed) network environment. Machine 800 may be a personal computer (PC), tablet PC, set-top box (STB), personal digital assistant (PDA), mobile phone, network device, network router, switch, or bridge, or any machine capable of (sequentially or otherwise) executing instructions specifying actions to be taken by said machine. Furthermore, while only a single machine is described, the term "machine" should also be considered as encompassing any collection of machines that individually or collectively execute a set of instructions (or multiple sets of instructions) to perform any one or more of the methods discussed herein (e.g., cloud computing, Software as a Service (SaaS), other computer cluster configurations).
[0087] Machine (e.g., computer system) 800 may include a hardware processor 802 (e.g., a central processing unit (CPU), graphics processing unit (GPU), hardware processor core, or any combination thereof), main memory 804, static memory (e.g., firmware, microcode memory or storage device, basic input / output (BIOS), unified extensible firmware interface (UEFI), etc.) 806, and mass storage device 808 (e.g., hard disk drive, tape drive, flash memory device, or other block device), some or all of which may communicate with each other via interconnect (e.g., bus) 830. Machine 800 may further include a display unit 810, an alphanumeric input device 812 (e.g., keyboard), and a user interface (UI) navigation device 814 (e.g., mouse). In an example, the display unit 810, input device 812, and UI navigation device 814 may be a touchscreen display. Machine 800 may additionally include a storage device (e.g., a drive unit) 808, a signal generating device 818 (e.g., a speaker), a network interface device 820, and one or more sensors 816, such as a Global Positioning System (GPS) sensor, a compass, an accelerometer, or other sensors. Machine 800 may include an output controller 828, connected serially (e.g., USB), in parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.).
[0088] The registers of processor 802, main memory 804, static memory 806, or mass storage device 808 may be or contain machine-readable medium 822, on which one or more sets of data structures or instructions 824 (e.g., software) embody or be utilized by any one or more of the techniques or functions described herein. Instructions 824 may also reside wholly or at least partially in any of the registers of processor 802, main memory 804, static memory 806, or mass storage device 808 during execution by machine 800. In an example, one or any combination of hardware processor 802, main memory 804, static memory 806, or mass storage device 808 may constitute machine-readable medium 822. Although machine-readable medium 822 is described as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and / or associated cache memory and server) configured to store one or more instructions 824.
[0089] Machine-readable media 822 can be implemented as Figure 1 Storage media 148 or Figure 4 The components of the memory control unit 430.
[0090] The term "machine-readable media" can include any medium capable of storing, encoding, or transmitting instructions for execution by machine 800 and causing machine 800 to perform any one or more of the technologies disclosed herein, or capable of storing, encoding, or transmitting data structures used by or associated with such instructions. Examples of non-limiting machine-readable media include solid-state memory, optical media, magnetic media, and signals (e.g., radio frequency signals, other photon-based signals, sound signals, etc.). In examples, non-transitory machine-readable media includes machine-readable media having a plurality of particles having invariant (e.g., rest) mass and thus being a component of matter. Therefore, non-transitory machine-readable media is machine-readable media that does not contain transiently propagating signals. Specific examples of non-transitory machine-readable media include: non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
[0091] In an example, information stored or otherwise provided on machine-readable medium 822 may represent instructions 824, such as instructions 824 itself or a format from which instructions 824 can be derived. This format from which instructions 824 can be derived may include source code, encoded instructions (e.g., in compressed or encrypted form), packaged instructions (e.g., split into multiple packets), etc. Information representing instructions 824 on machine-readable medium 822 may be processed by a processing circuitry system into instructions to perform any of the operations discussed herein. For example, deriving instructions 824 from information (e.g., by processing circuitry system) may include: compiling (e.g., from source code, object code, etc.), interpreting, loading, organizing (e.g., dynamically or statically linking), encoding, decoding, encrypting, decrypting, packaged, depackaged, or otherwise manipulating information into instructions 824.
[0092] In an example, deriving instruction 824 may involve assembling, compiling, or interpreting information (e.g., by processing a circuit system) to produce instruction 824 from some intermediate or preprocessed format provided by machine-readable media 822. When provided in multiple parts, information may be combined, unpacked, and modified to produce instruction 824. For example, the information may be in multiple compressed source code packages (or object code, or binary executable code, etc.) on one or more remote servers. The source code packages may be encrypted when transmitted over a network and, if necessary, decrypted, decompressed, assembled (e.g., linked), compiled or interpreted on the local machine (e.g., into a library, standalone executable, etc.), and executed by the local machine.
[0093] The system can further utilize any of several transmission protocols (e.g., Frame Relay, Internet Protocol (IP), Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), etc.) to transmit or receive commands 824 on the communication network 826 via the network interface device 820 using the transmission medium. Example communication networks may include, in particular, local area networks (LANs), wide area networks (WANs), packet data networks (e.g., the Internet), mobile phone networks (e.g., cellular networks), conventional telephone (POTS) networks, and wireless data networks (e.g., the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of standards, referred to as… The IEEE 802.16 series of standards are called... This includes standards such as IEEE 802.15.4 series and peer-to-peer (P2P) networks. In an example, network interface device 820 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to communication network 826. In an example, network interface device 820 may include multiple antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) technologies. The term "transmitting medium" should be considered as any intangible medium capable of storing, encoding, or transmitting instructions for execution by machine 800, and includes digital or analog communication signals or other intangible media to facilitate communication of such software. Transmitting medium is machine-readable medium.
[0094] Some exemplary embodiments of this disclosure have been described in the foregoing specification. Therefore, the specification and drawings should be viewed in an illustrative rather than restrictive sense. The following is a non-exhaustive list of examples of embodiments of this disclosure.
[0095] Example 1. A system comprising:
[0096] Multilevel cell (MLC) NAND flash memory array; and
[0097] A memory controller, coupled to the MLC NAND flash memory array and configured to perform programming operations on the MLC NAND flash memory array, includes:
[0098] During the first programming operation, a first programming voltage is applied to the first word line of the MLC NAND flash memory array, the word line forming the control gate of the first set of memory cells of the array;
[0099] Perform a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells successfully programmed to a first level in response to the first programming voltage; and
[0100] Based on the first programming validity metric and a predetermined threshold, it is determined whether to perform a second verification operation to determine a second programming validity metric that includes a second quantity of the first group of memory cells successfully programmed to a second level by the first programming voltage.
[0101] Example 2. The system according to Example 1, wherein the operation further includes:
[0102] Perform the second verification operation to determine the second programming validity measure; and
[0103] Based on the second programming validity metric and the predetermined threshold, it is determined whether to perform a third verification operation to determine a third programming validity metric that includes a third amount of the first group of memory cells successfully programmed to a third level by the first programming voltage.
[0104] Example 3. The system according to Example 1 or Example 2, wherein the operation further includes:
[0105] The predetermined threshold is received via the bus.
[0106] Example 4. The system according to any one of Examples 1 to 3, wherein the first quantity of the first group of memory cells is the number of the first group of memory cells successfully programmed to the first level.
[0107] Example 5. A system according to any one of Examples 1 to 4, wherein the first quantity of the first group of memory cells is the percentage of the first group of memory cells successfully programmed to the first level.
[0108] Example 6. The system according to any one of Examples 1 to 5, wherein the operation further includes:
[0109] Based on the first programming validity metric and the second predetermined threshold, a second programming voltage is applied to the line of the MLC flash memory, the second programming voltage being higher than the first programming voltage.
[0110] Example 7. A system according to any one of Examples 1 to 6, wherein the MLC NAND flash memory array comprises a vertical string of memory cells having memory cells at a plurality of vertically arranged layers, wherein the plurality of memory cells at a respective layer are coupled to a respective word line.
[0111] Example 8. A non-transitory machine-readable medium storing instructions that, when executed by a system, cause the system to perform operations including:
[0112] During the first programming operation, a first programming voltage is applied to the first word line of the MLC NAND flash memory array, the word line forming the control gate of the first set of memory cells of the array;
[0113] Perform a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells successfully programmed to a first level in response to the first programming voltage; and
[0114] Based on the first programming validity metric and a predetermined threshold, it is determined whether to perform a second verification operation to determine a second programming validity metric that includes a second quantity of the first group of memory cells successfully programmed to a second level by the first programming voltage.
[0115] Example 9. The non-transitory machine-readable medium according to Example 8, wherein the operation further includes:
[0116] Perform the second verification operation to determine the second programming validity measure; and
[0117] Based on the second programming validity metric and the predetermined threshold, it is determined whether to perform a third verification operation to determine a third programming validity metric that includes a third amount of the first group of memory cells successfully programmed to a third level by the first programming voltage.
[0118] Example 10. The non-transitory machine-readable medium according to Example 8 or Example 9, wherein the operation further includes:
[0119] The predetermined threshold is received via the bus.
[0120] Example 11. A non-transitory machine-readable medium according to any of Examples 8 to 10, wherein the first quantity of the first set of memory cells is the number of the first set of memory cells successfully programmed to the first level.
[0121] Example 12. A non-transitory machine-readable medium according to any of Examples 8 to 11, wherein the first quantity of the first set of memory cells is the percentage of the first set of memory cells successfully programmed to the first level.
[0122] Example 13. A non-transitory machine-readable medium according to any of Examples 8 to 12, wherein the operation further includes:
[0123] Based on the first programming validity metric and the second predetermined threshold, a second programming voltage is applied to the line of the MLC flash memory, the second programming voltage being higher than the first programming voltage.
[0124] Example 14. A non-transitory machine-readable medium according to any of Examples 8 to 13, wherein the MLCNAND flash memory array comprises a vertical string of memory cells having memory cells at a plurality of vertically arranged layers, wherein the plurality of memory cells at the respective layers are coupled to respective word lines.
[0125] Example 15. A method comprising:
[0126] During the first programming operation, a first programming voltage is applied to the first word line of the MLC NAND flash memory array, the word line forming the control gate of the first set of memory cells of the array;
[0127] Perform a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells successfully programmed to a first level in response to the first programming voltage; and
[0128] Based on the first programming validity metric and a predetermined threshold, it is determined whether to perform a second verification operation to determine a second programming validity metric that includes a second quantity of the first group of memory cells successfully programmed to a second level by the first programming voltage.
[0129] Example 16. The method according to Example 15, wherein the operation further includes:
[0130] Perform the second verification operation to determine the second programming validity measure; and
[0131] Based on the second programming validity metric and the predetermined threshold, it is determined whether to perform a third verification operation to determine a third programming validity metric that includes a third amount of the first group of memory cells successfully programmed to a third level by the first programming voltage.
[0132] Example 17. The method according to Example 15 or Example 16 further includes:
[0133] The predetermined threshold is received via the bus.
[0134] Example 18. The method according to any one of Examples 15 to 17, wherein the first quantity of the first group of memory cells is the number of the first group of memory cells successfully programmed to the first level.
[0135] Example 19. The method according to any one of Examples 15 to 18, wherein the first quantity of the first group of memory cells is the percentage of the first group of memory cells successfully programmed to the first level.
[0136] Example 20. The method according to any one of Examples 15 to 19, further comprising:
[0137] Based on the first programming validity metric and the second predetermined threshold, a second programming voltage is applied to the line of the MLC flash memory, the second programming voltage being higher than the first programming voltage.
Claims
1. A system comprising: Multilevel cell (MLC) NAND flash memory array; as well as A memory controller, coupled to the MLC NAND flash memory array and configured to perform programming operations on the MLC NAND flash memory array, including: During the first programming operation, a first programming voltage of a single value is applied to the word line of the MLC NAND flash memory array during the first iteration, the word line forming the control gate of the first set of memory cells of the MLC NAND flash memory array; Perform a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells that were successfully programmed to a first level in the first iteration in response to the first programming voltage; Determine whether the first programming validity metric meets a predetermined threshold; If the first programming validity metric meets the predetermined threshold, a second verification operation is performed to determine a second programming validity metric including a second amount of the first group of memory cells successfully programmed to a second level by the first programming voltage in the first iteration; and If the first programming validity metric is less than the predetermined threshold, the execution of the second verification operation is delayed until the subsequent programming validity metric reaches the predetermined threshold in a subsequent iteration.
2. The system according to claim 1, wherein the operation further comprises: Perform the second verification operation to determine the second programming validity measure; as well as Based on the second programming validity metric and the predetermined threshold, it is determined whether to perform a third verification operation to determine a third programming validity metric that includes a third amount of the first group of memory cells successfully programmed to a third level by the first programming voltage.
3. The system according to claim 1, wherein the operation further comprises: The predetermined threshold is received via the bus.
4. The system of claim 1, wherein the first quantity of the first group of memory cells is the number of the first group of memory cells successfully programmed to the first level.
5. The system of claim 1, wherein the first quantity of the first group of memory cells is the percentage of the first group of memory cells successfully programmed to the first level.
6. The system of claim 1, wherein the operation further comprises: Based on the first programming validity metric and the second predetermined threshold, a second programming voltage is applied to the word line of the MLC flash memory in the second iteration, wherein the second programming voltage is higher than the first programming voltage.
7. The system of claim 1, wherein the MLC NAND flash memory array comprises a vertical string of memory cells having memory cells at a plurality of vertically arranged layers, wherein the plurality of memory cells at a respective layer are coupled to a respective word line.
8. A non-transitory machine-readable medium storing instructions, which, when executed by a system, cause the system to perform operations including: During the first programming operation, a first programming voltage of a single value is applied to the word line of the MLC NAND flash memory array during the first iteration, the word line forming the control gate of the first set of memory cells of the MLC NAND flash memory array; Perform a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells that were successfully programmed to a first level in the first iteration in response to the first programming voltage; Determine whether the first programming validity metric meets a predetermined threshold; If the first programming validity metric meets the predetermined threshold, a second verification operation is performed to determine a second programming validity metric that includes a second amount of the first group of memory cells that were successfully programmed to a second level by the first programming voltage in the first iteration; as well as If the first programming validity metric is less than the predetermined threshold, the execution of the second verification operation is delayed until the subsequent programming validity metric reaches the predetermined threshold in a subsequent iteration.
9. The non-transitory machine-readable medium of claim 8, wherein the operation further comprises: Perform the second verification operation to determine the second programming validity measure; as well as Based on the second programming validity metric and the predetermined threshold, it is determined whether to perform a third verification operation to determine a third programming validity metric that includes a third amount of the first group of memory cells successfully programmed to a third level by the first programming voltage.
10. The non-transitory machine-readable medium of claim 8, wherein the operation further comprises: The predetermined threshold is received via the bus.
11. The non-transitory machine-readable medium of claim 8, wherein the first quantity of the first set of memory cells is the number of the first set of memory cells successfully programmed to the first level.
12. The non-transitory machine-readable medium of claim 8, wherein the first quantity of the first set of memory cells is the percentage of the first set of memory cells successfully programmed to the first level.
13. The non-transitory machine-readable medium of claim 8, wherein the operation further comprises: Based on the first programming validity metric and the second predetermined threshold, a second programming voltage is applied to the word line of the MLC flash memory in the second iteration, wherein the second programming voltage is higher than the first programming voltage.
14. The non-transitory machine-readable medium of claim 8, wherein the MLC NAND flash memory array comprises a vertical string of memory cells having memory cells at a plurality of vertically arranged layers, wherein the plurality of memory cells at a respective layer are coupled to a respective word line.
15. A method comprising: During the first programming operation, a first programming voltage of a single value is applied to the word line of the MLC NAND flash memory array during the first iteration, the word line forming the control gate of the first set of memory cells of the MLC NAND flash memory array; Perform a first verification operation to determine a first programming validity measure including a first amount of the first set of memory cells that were successfully programmed to a first level in the first iteration in response to the first programming voltage; Determine whether the first programming validity metric meets a predetermined threshold; If the first programming validity metric meets the predetermined threshold, a second verification operation is performed to determine a second programming validity metric that includes a second amount of the first group of memory cells that were successfully programmed to a second level by the first programming voltage in the first iteration; as well as If the first programming validity metric is less than the predetermined threshold, the execution of the second verification operation is delayed until the subsequent programming validity metric reaches the predetermined threshold in a subsequent iteration.
16. The method of claim 15, further comprising: Perform the second verification operation to determine the second programming validity measure; as well as Based on the second programming validity metric and the predetermined threshold, it is determined whether to perform a third verification operation to determine a third programming validity metric that includes a third amount of the first group of memory cells successfully programmed to a third level by the first programming voltage.
17. The method of claim 15, further comprising: The predetermined threshold is received via the bus.
18. The method of claim 15, wherein the first quantity of the first set of memory cells is the number of the first set of memory cells successfully programmed to the first level.
19. The method of claim 15, wherein the first quantity of the first set of memory cells is the percentage of the first set of memory cells successfully programmed to the first level.
20. The method of claim 15, further comprising: Based on the first programming validity metric and the second predetermined threshold, a second programming voltage is applied to the word line of the MLC flash memory in the second iteration, wherein the second programming voltage is higher than the first programming voltage.
Citation Information
Patent Citations
Nonvolatile memory devices and program methods thereof in which a target verify operation and a pre-pass verify operation are performed simultaneously using a common verify voltage
US20110007571A1
Programming method of non volatile memory device
US20170110185A1
