Memory device with user-defined tagging mechanism
By introducing a current monitor and controller into the memory device, identifying and deactivating the bad blocks formed after deployment, the problem of inability to effectively identify and handle bad blocks in the prior art is solved, and the robustness and operational reliability of the memory device are improved. sex.
Patent Information
- Application Number
- CN202010384387.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-05-07
- Filing Date
- 2020-05-07
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-05-07
AI Technical Summary
Existing memory devices cannot effectively identify and deactivate bad memory blocks caused by manufacturing errors or reuse after deployment, resulting in performance degradation and interfering with the operation of health blocks.
The current monitor and controller are introduced into the memory device. After deployment, the defective block is identified by measuring the current, and the deactivated latch is used to disconnect the defective blocks to prevent them from interfering with normal operation in subsequent operations.
Effectively identify and deactivate the bad blocks formed after deployment, preventing them from interfering with the normal operation of the memory device, and improving the robustness and reliability of the memory device.
Smart Images

Figure CN111916139B_ABST
Abstract
Description
Technical Field
[0001] The disclosed embodiments relate to devices, and in particular, to memory devices having a user-defined tagging mechanism for memory blocks. Background Art
[0002] The memory device is usually set as an internal, semiconductor integrated circuit and / or external removable device in a computer or other electronic device. There are many different types of memory, including volatile and non-volatile memory. Volatile memories including random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM) and synchronous dynamic random access memory (SDRAM) may require a power supply to apply power to maintain its data. In contrast, non-volatile memory can maintain its stored data even when there is no external power supply. Non-volatile memory can be used in various technologies, including flash memory (e.g., NAND and NOR) phase change memory (PCM), resistive random access memory (RRAM) and magnetic random access memory (MRAM), etc.
[0003] In some embodiments, a memory device includes circuit cells (e.g., transistors and / or memory cells) configured to store charge levels representing different values. Thus, a memory device can store and access a variety of information via the circuit cells. In one or more embodiments, the circuit cells are configured or connected (via, for example, word lines, bit lines, etc.) to form larger groups, such as pages, blocks, etc. During operation, typically, such as during writing or reading, the circuit cells are accessed according to the larger grouping.
[0004] Since information is processed according to such larger groupings (e.g., memory blocks), defects in one or more circuit cells in such larger groupings may adversely affect the performance of the entire grouping. Because such defects occur during manufacturing and / or due to repeated use (i.e., wear and tear), some of the memory groupings may become unusable. In view of increasing commercial competitive pressures along with growing consumer expectations and the need to differentiate products in the marketplace, there is a growing need to find answers to these questions. Summary of the invention
[0005] In one aspect, the present application provides a memory device comprising: memory blocks, each having a plurality of memory cells configured to store data; one or more current monitors configured to determine a measure of current during post-deployment operation of the memory device; and a controller coupled to the memory blocks and the one or more current monitors, the controller being configured to: identify bad blocks within the memory blocks based on the determined current measurements, and disable the bad blocks to prevent access to the bad blocks during subsequent operation of the memory device.
[0006] In another aspect, the present application provides a memory system comprising: a host device; and a memory device coupled to the host device, wherein: the memory device includes memory blocks each having a plurality of memory cells, and the memory device is configured to: measure current during post-deployment operation of the memory device, identify bad blocks within the memory blocks based on the measured current, and disable the bad blocks to prevent access to the bad blocks during subsequent data operations.
[0007] In yet another aspect, the present application provides a method of operating a memory device including a controller and a memory array, the memory array including memory blocks each having a plurality of memory cells, the method comprising: measuring current consumption of one or more of the memory blocks during post-deployment operation of the memory device; identifying bad blocks within the memory blocks based on the measured current; and disabling the bad blocks to prevent access to the bad blocks during subsequent operation of the memory device. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 is a block diagram of a memory system configured in accordance with an embodiment of the present technology.
[0009] Figure 2 is an example circuit diagram of a memory array according to an embodiment of the present technology.
[0010] Figure 3 is a functional block diagram of a memory device configured in accordance with an embodiment of the present technology.
[0011] Figure 4 The operation of the embodiment according to the present invention is described in Figure 1 A flowchart of an example method for a memory system in FIG.
[0012] Figure 5 is a schematic diagram of a system including a memory device according to an embodiment of the present technology. DETAILED DESCRIPTION
[0013] As described in more detail below, the technology disclosed herein relates to a memory device, a system having a memory device, and a related method for dynamically allowing a user to mark a bad memory block. The marked block can be disabled so that it is removed from use and the user cannot override the mark.
[0014] A memory block may be considered "bad" when it is unable to properly save data and / or reproduce stored data. For example, the oxide layer intended to hold charge may have defects caused by production / manufacturing errors and / or caused by repeated use / access over time. As a result, the corresponding memory cell may fail to hold the correct amount of charge and / or actually cause an undesirable electrical path (e.g., a short circuit).
[0015] In conventional devices, bad blocks are identified during production testing, and the results of this identification are stored in an array. Once the device is deployed (e.g., implemented for intended use, such as by an end user and / or implemented as an assembly for a different device / system), the device can access the stored results and make the identified bad blocks inaccessible. For example, the device can set a disable latch for the bad blocks and / or can ground the block select signal for the bad blocks. In some embodiments, the block select signal can be permanently (i.e., irreversibly during the life of the device) connected to ground for the bad blocks. Therefore, the user cannot read, write, or erase these blocks, thereby preventing the bad blocks from inadvertently interfering with healthy blocks. Since the bad blocks are identified during production testing, memory blocks that are degraded and become bad after deployment do not benefit from this type of marking.
[0016] Compared to conventional devices, the embodiments described below are configured to identify and disable (via, for example, disconnection from corresponding word lines and / or other circuits) blocks that become bad after / during deployment of a memory device. Since identifying only bad blocks allows the possibility of a user inadvertently accessing the bad blocks (e.g., due to user error), the embodiments described below may allow a user to mark bad memory blocks with a tag stored in a predetermined block (e.g., a tag memory block other than a read-only memory (ROM) block and / or a tag memory block in which tags generated by production testing are stored). Thus, a user may disable memory blocks that degrade and become bad after deployment so that the memory blocks do not interfere with normal operation of the memory device.
[0017] Figure 11 is a block diagram of a system 101 having a memory device 100 configured in accordance with an embodiment of the present technology. As shown, the memory device 100 includes a main memory 102 (e.g., NAND flash, NOR flash, chalcogenide PCM, etc.) and a controller 106 that operably couples the main memory 102 to a host device 108 (e.g., an upstream central processing unit (CPU)). The main memory 102 includes a plurality of memory regions or memory cells 120, each of which includes a plurality of memory cells 122. The memory cells 120 may be individual memory dies, memory planes in a single memory die, a stack of memory dies vertically connected with through silicon vias (TSVs), and the like. For example, in one embodiment, each of the memory cells 120 may be formed of a semiconductor die and arranged with other memory cell dies in a single device package (not shown). In other embodiments, a plurality of memory cells 120 may be co-located on a single die and / or distributed across a plurality of device packages. The memory cells 122 may include, for example, floating gate, charge trapping, phase change, ferroelectric, magnetoresistive, and / or other suitable storage elements configured to store data persistently or semi-persistently. The main memory 102 and / or the individual memory cells 120 may also include other circuit components (not shown) for accessing and / or programming (e.g., writing) the memory cells 122 and other functionality, such as for processing information and / or communicating with the controller 106, such as multiplexers, decoders, buffers, read / write drivers, address registers, data output / data input registers, etc.
[0018] The memory cells 122 may be arranged into rows 124 (e.g., each row corresponds to a word line) and columns 126 (e.g., each column corresponds to a bit line). Each word line may include one or more memory pages depending on the number of data states that the memory cells 122 of the word line are configured to store. For example, a single word line of memory cells 122 in which each memory cell 122 is configured to store one of two data states (e.g., SLC memory cells are configured to store one bit each) may include a single memory page. Alternatively, a single word line of memory cells 122 in which each memory cell 122 is configured to store one of four data states (e.g., MLC memory cells are configured to store two bits each) may include two memory pages. Furthermore, in an “even-odd bit line architecture,” memory pages may be interleaved such that a word line including memory cells 122 in which each memory cell 122 is configured to store one of two data states (e.g., SLC memory cells) may span two memory pages, with all memory cells 122 in odd-numbered columns 126 of a single word line grouped as a first memory page, and all memory cells 122 in even-numbered columns 126 of the same word line grouped as a second memory page. When an even-odd bit line architecture is used for word lines of memory cells 122 in which each memory cell 122 is configured to store a larger number of data states (e.g., memory cells configured as MLC, TLC, QLC, etc.), the number of memory pages per word line may be even higher (e.g., 4, 6, 8, etc.).
[0019] Each column 126 may include a string of serially connected memory cells 122 connected to a common source. The memory cells 122 of each string may be connected in series between a source select transistor (e.g., a field effect transistor) and a drain select transistor (e.g., a field effect transistor). The source select transistors may be commonly coupled to a source select line, and the drain select transistors may be commonly coupled to a drain select line.
[0020] In other embodiments, the memory cells 122 may be arranged in different types of hierarchies and / or groups than shown in the illustrated embodiment. Furthermore, although a certain number of memory cells, rows, columns, blocks, and memory cells are shown in the illustrated embodiment for purposes of illustration, the number of memory cells, rows, columns, blocks, and memory cells may vary and, in other embodiments, may be larger or smaller in proportion than shown in the illustrated example. For example, in some embodiments, the memory device 100 may include only one memory cell 120. Alternatively, the memory device 100 may include 2, 3, 4, 8, 10, or more (e.g., 16, 32, 64, or more) memory cells 120. Although the memory cells 120 are shown in the illustrated embodiment, the number of memory cells, rows, columns, blocks, and memory cells may vary and, in other embodiments, may be larger or smaller in proportion than shown in the illustrated example. Figure 11 and 2. In some embodiments, each memory unit 120 includes two memory blocks 128, but in other embodiments, each memory unit 120 may include 1, 3, 4, 8 or more (e.g., 16, 32, 64, 100, 128, 256 or more) memory blocks. In some embodiments, each memory block 128 may include, for example, 2 15 Memory pages, and each memory page in a block may include, for example, 2 12 Memory cells 122 (eg, "4k" pages).
[0021] The controller 106 may be a microcontroller, a dedicated logic circuit (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), etc.), or other suitable processor. The controller 106 may include a processor 130 configured to execute instructions stored in a memory. In the illustrated example, the memory of the controller 106 includes an embedded memory 132, which is configured to execute various processes, logic flows, and routines for controlling the operations of the memory device 100, including managing the main memory 102 and handling communications between the memory device 100 and the host device 108. In some embodiments, the embedded memory 132 may include memory registers that store, for example, memory pointers, extracted data, etc. The embedded memory 132 may include volatile and / or non-volatile memory (e.g., DRAM, SRAM, NAND, NOR, PCM) for storing memory registers, and may also include read-only memory (ROM) (e.g., for storing microcode). Although in Figure 1 In the example described in , the memory device 100 is illustrated as including a controller 106, but in another embodiment of the present technology, the memory device may not include a controller, and may instead rely on external control (e.g., provided by an external host, or by a processor or controller separate from the memory device).
[0022] In operation, the controller 106 may directly write or otherwise program (e.g., erase) various memory areas of the main memory 102, such as by writing to groups of memory pages and / or memory blocks 128. In NAND-based memory, a write operation typically includes programming the memory cells 122 in a selected memory page with a particular data value (e.g., a string of data bits having a value of either logic 0 or logic 1). An erase operation is similar to a write operation, except that an erase operation reprograms an entire memory block 128 or multiple memory blocks 128 to the same data state (e.g., logic 1).
[0023] The controller 106 communicates with the host device 108 via a host-device interface 110. In some embodiments, the host device 108 and the controller 106 may communicate via a serial interface, such as a serial attached SCSI (SAS), a serial AT attachment (SATA) interface, a peripheral component interconnect express (PCIe), or other suitable interface (e.g., a parallel interface). The host device 108 may send various requests (in the form of, for example, packets or packet streams) to the controller 106. The request may include a command to write, erase, return information, and / or perform a specific operation (e.g., a trim (TRIM) operation). The request may also include an interrupt or another command indicating a change in a condition (e.g., a power-off event), which may trigger the implementation of a power-off algorithm.
[0024] Host device 108 may be any of a number of electronic devices capable of utilizing memory for temporary or permanent storage of information, or a component thereof. For example, host device 108 may be a computing device, such as a desktop or portable computer, a server, a handheld device (e.g., a mobile phone, a tablet computer, a digital reader, a digital media player), or a component thereof (e.g., a central processing unit, a coprocessor, a dedicated memory controller, etc.). Host device 108 may be a network connection device (e.g., a switch, a router, etc.) or a recorder of digital images, audio, and / or video, a vehicle, an appliance, a toy, or any of a number of other products. In one embodiment, host device 108 may be directly connected to memory device 100, but in other embodiments, host device 108 may be indirectly connected to memory device 100 (e.g., via a network connection or through an intermediate device).
[0025] Figure 2 is an example circuit diagram of a memory array 200 (e.g., a group of memory cells 120, such as a NAND flash memory array) according to an embodiment of the present technology. As described above, the memory array 200 includes memory cells 122 (e.g., floating gate transistors) arranged according to word lines (e.g., horizontal rows of memory cells 122) and bit lines (e.g., vertical columns of memory cells 122). Figure 2 As illustrated in FIG. 2 , memory array 200 may include word lines WL( 0 )-WL(M) and bit lines BL( 0 )-BL(N).
[0026] As described above, memory cell 122 can be configured to hold various charge levels / amounts representing different data states or values. For example, memory cell 122 can include a floating gate transistor that stores charge within an insulating layer (e.g., an oxide layer), and the stored charge level can be changed via a tunneling operation.
[0027] To access the memory cells 122 and / or the information stored therein, a row decoder (not shown) and a column decoder (not shown) may be provided. The row decoder and column decoder may be configured to receive Figure 1 The host 108 receives (via e.g. Figure 1 The host-device interface 110 (e.g., an address bus) of the memory array 200 and translates the address for accessing a specific memory cell in the memory array 200. When accessing / reading the memory cell 122, the memory device 100 may include a row driver (not shown) configured to activate a selected word line according to the address. A sense amplifier block (not shown) having a plurality of sense amplifiers in line with the column decoder and the memory array 200 may be provided. The sense amplifier block may be configured to sense and amplify the individual values stored in the memory cell 122.
[0028] Because the memory cells 122 may rely on the insulating structure to preserve the stored information, the ability of the memory cells 122 to retain the stored charge breaks down when the insulating structure degrades. Degradation of the insulating layer may occur during production (e.g., during assembly and / or packaging operations) and / or after deployment (e.g., due to use of the memory device 100). For example, the high temperatures used during assembly and packaging of NAND dies may trigger physical changes that may cause defects. Moreover, high temperatures and / or wear due to repeated reads / writes over time during operation of the memory device 100 may cause defects. When severe, such degradation may actually create a short circuit or a path to ground through the memory cell 122.
[0029] Conventional devices test for bad memory blocks that include defective memory cells during manufacturing. The discovered bad blocks are then disabled (via, for example, storing the corresponding block addresses in a predetermined block) before the memory device 100 ends the manufacturing process. However, conventional devices lack the ability to similarly disable memory blocks that become bad (e.g., due to later-generated defects in an insulating layer in one or more memory cells in the memory block) after deployment and / or during the desired operation of the memory device 100.
[0030] Further complicating the issue, other features / operations of the memory device 100 may amplify the operational impact caused by a bad memory block. In some embodiments, for example, the memory device 100 may be configured to bias the word lines, for example, at a voltage level less than the read / write level when the memory array 200 is in a standby mode. In other words, the memory device 100 may apply a predetermined voltage level to the word lines between functional (e.g., read, write, erase, etc.) operations. For example, the memory device 100 may bias the word lines (e.g., when the word lines are not activated for read operations and / or write operations) when the word lines are not activated for read operations and / or write operations. Figure 2) is biased to approximately 2V to provide improved reliability (e.g., by reducing leakage current on the access transistor). Moreover, biasing the word lines can improve the response time for reading / writing information relative to the memory cells 122. However, bad blocks that are not disabled will increase current draw during this biasing operation and interfere with normal operation of the memory device 100 (e.g., operation of other healthy memory blocks). Thus, identifying and disabling bad blocks formed after deployment, for example, by reducing / eliminating the effective short between the word line and ground through the bad blocks, reduces and / or eliminates the negative effects when biasing the word lines. Thus, identifying and disabling bad blocks, for example, by reducing leakage current and preventing violation of one or more operating conditions (e.g., limits on total current draw, operating temperature, etc.), reduces / eliminates interference of bad blocks with normal operation.
[0031] Similarly, identifying and disabling post-deployment bad blocks reduces and / or eliminates potential voltage sags that may occur during reset reads. In some embodiments (e.g., 3-dimensional NAND devices), for example, reset reads may be implemented to reduce the error rate associated with reading a memory block after a long period of inactivity (i.e., a "first page read"). To implement the reset read, the memory device 100 may drive the word lines of a group of blocks (e.g., 8, 16, 32, etc.) in parallel to an internally generated voltage (e.g., about 6V). Although the reset read may interrupt long periods of inactivity and alleviate the first page read problem, the bad block may cause an effective short circuit between the driven word line and ground. As a result, the internally generated voltage will sag, causing the reset read to fail. Disabling the bad block reduces / eliminates the interference of the bad block with the reset read. Although described with reference to the insulator collapse that causes the bad block, embodiments of the present disclosure are also applied to tracking bad blocks caused in other ways.
[0032] Figure 3 1 is a functional block diagram of a memory device (e.g., memory device 100) configured in accordance with an embodiment of the present technology. Memory device 100 may include a memory block 128 (e.g., Figure 1 In some embodiments, the current monitor 304 may be included in Figure 1 in the main memory 102.
[0033] The current monitor 304 can be configured to detect a bad block 310 by measuring a current (e.g., a leakage current and / or a standby current) for a corresponding instance of a memory block 128 (e.g., a memory block 128 connected to a word line and / or accessed by the controller 106). When the measured current exceeds a predetermined threshold, the memory device 100 (e.g., the controller 106 and / or circuitry within the main memory 102) can identify the corresponding memory block 128 as a bad block 310.
[0034] When the current monitor 304 detects an excessive current, the controller 106, the current monitor 304, and / or one or more circuits within the main memory 102 may identify the address of the bad block 310 and store the address in the deployment mark storage 312. In some embodiments, the deployment mark storage 312 may include one or more designated memory blocks configured to store the deployment mark address 322 (i.e., the address of the bad block 310 formed after deployment). In other embodiments, the deployment mark storage 312 may include a storage circuit external to the memory block 128. Moreover, in some embodiments, the memory device 100 (e.g., within the main memory 102 and / or the memory block 128) may include a disable latch 311, which may be configured to disconnect and electrically isolate the bad block 310 from other circuits and / or word lines.
[0035] In some embodiments, the deployment mark storage 312 can be separate from the ROM storage 314 and the production mark storage 316. For example, the ROM storage 314 and the production mark storage 316 can be memory blocks and / or circuits separate from the deployment mark storage 312. The ROM storage 314 can be configured to store trim information, such as programming voltages. The production mark storage 316 can be configured to store production mark addresses 326 corresponding to addresses of bad blocks 310 that are formed to be defective and / or found to be defective prior to deployment. In other embodiments, the deployment mark storage 312 can be part of the ROM storage 314.
[0036] In some embodiments, the memory device 100 can disable bad blocks marked by a user (via, for example, the host device 108 and / or the controller 106). For marking, the system 101 and / or the memory device 100 therein can be configured to transmit a command sequence for marking and disable the bad blocks. In some embodiments, the system 101 and / or the memory device 100 can use the same interface or marking operation as the read / write erase operation.
[0037] In one or more embodiments, the command sequence may include a predetermined operable code (opcode) and / or set (SET) feature command. For example, to specify a block to be marked, a user may dynamically (e.g., during runtime of the memory device 100) use a command sequence that includes an opcode (e.g., 'CMDxy'), followed by a block address (blockaddress), followed by an opcode ('CMDuv'). The first opcode may be a command code for a marking operation (e.g., a newly defined code and / or part of a set feature command), the block address may be a deployment marking address 322 of a bad block, and the second opcode may be used to confirm the marking operation. In some embodiments, the predetermined opcode may be similar to a read command in which a user initiates a command sequence with an opcode (e.g., 'CMD00'), followed by n cycles (e.g., 5 cycles) of block and page addresses, which may be followed by a confirmation (e.g., 'CMD30'). In other embodiments, setting (SET) a feature may be based on a command sequence comprising an operation code (opcode) (e.g., 'CMDef'), followed by a feature address (e.g., for bad block marking), followed by n bytes (e.g., 4 bytes) of data specifying the bad blocks to be marked (e.g., 'CMDuv').
[0038] Based on the command sequence, the memory device 100 (via, for example, NAND internal circuitry, such as a state machine) may set the disable latch 311 associated with the identified bad block. In some embodiments, the setting of the disable latch 311 may be volatile (i.e., the setting may be lost in the event of an interruption of power). Therefore, in other embodiments, the deployment mark address 322 may be stored in the deployment mark storage device 312 (e.g., non-volatile memory) and used to reset the disable latch 311 across a power interruption.
[0039] In other embodiments, a user (via, for example, a host device 108 and / or a controller 106) may program an extended bad block map including a deployment mark address 322. The extended bad block map may be stored in a deployment mark storage device 312 (e.g., a non-volatile memory). Upon issuing an initialization (FF) command, the NAND may read the map and disable bad blocks using a disable latch 311. A user may read, erase, and program the extended bad block map to update bad blocks generated over time. An example command sequence for writing map information may include a map programming (PGM) command, followed by data, followed by a confirm command. In response, the NAND may select a memory block designated as a deployment mark storage device 312 and begin a programming operation to write the map using data. Similarly, an example command sequence for erasing map information may include a map erase command, followed by an empty block address, followed by a confirm command. Moreover, an example command sequence for reading map information may include a map read command, followed by an empty block address, followed by a confirm command, which may be followed by data output caused by the read. The data output may be supplied to a disable latch 311 for use in disabling bad blocks identified in the map.
[0040] The deployment mark storage device 312, the deployment mark address 322 and / or the disable latch 311 provide improved robustness and reduced errors for the memory device 100. The deployment mark storage device 312 and the deployment mark address 322 can be used to maintain the addresses of bad blocks generated during the deployment life of the memory device 100. The deployment mark address 322 and the disable latch 311 can disconnect the deployed bad block 310 from the associated circuits, word lines, etc., similar to the bad blocks identified during production, so that the deployed bad block 310 cannot interfere with the normal operation of the memory device 100. Thus, the bad block 310 can be disabled to guard against accidental attempts by users to access the bad block 310.
[0041] Furthermore, when word line bias and / or reset reads are used in the memory device 100, deploying the tag storage device 312, deploying the tag address 322, and / or disabling the latch 311 can provide increased stability and efficiency for the operation. As described above, unless disabled, the deployed bad block 310 can actually cause a short circuit between the word line and ground. By disabling / disconnecting the bad block, the memory device 100 can prevent the short circuit, thereby ensuring the correct / accurate implementation of the word line bias and / or reset read operations.
[0042] Figure 4 The operation of the embodiment according to the present invention is described in Figure 1 System 101 and / or Figure 1 4. The method 400 may include identifying and disabling memory blocks that are degraded after the memory device 100 is deployed.
[0043] At block 402, the memory device 100 or components therein (eg, dies) may be tested during a production / manufacturing process. For example, a memory device 100 may be tested during a manufacturing process, such as before assembling the memory device 100. Figure 2 2. The memory device 100 may be tested after assembly, for example. At block 404, existing bad blocks (i.e., existing / detected before deployment of the memory device 100) may be identified during the testing process. The testing process may identify Figure 3 At block 406, the address of the identified bad block (eg, the production mark address 326) may be stored in a predetermined location (eg, Figure 3 In some embodiments, the identified bad blocks may be disabled / disconnected before the memory device 100 is deployed.
[0044] Block 412 may represent a power cycle event that occurs as part of normal operation after deployment of the memory device 100 (e.g., by turning power off and on and / or resetting the device / system). At block 414, the memory device 100 may access a flag that identifies a bad block. In some embodiments, the memory device 100 may access a production flag storage 316 for a production flag address 326 and / or access a flag that indicates a bad block that occurred or was generated after deployment. Figure 3 The (post-deployment) bad blocks 310 Figure 3 The deployment tag address 322 Figure 3 The deployment tag storage device 312 may be provided with a deployment tag storage device 312. The tag may be accessed during initialization and / or reset of the memory device 100. In some embodiments, the accessed tag (e.g., the address of the bad memory block) may be provided to one or more circuits (e.g., Figure 3 The disable latch 311) is used to manage bad blocks.
[0045] At block 416, the memory device 100 may disable the bad blocks based on the accessed tags. Figure 1 The controller 106 and / or the main memory 102 of the memory device 100 may disable the bad block 310 to prevent the bad block 310 from being accessed during subsequent operations of the memory device 100. In some embodiments, for example, the memory device 100 may control the disable latch 311 associated with the accessed tag to disconnect the bad block 310 from other circuits and / or corresponding word lines. Thus, the memory device 100 may electrically isolate the bad block 310 from other circuits and / or one or more corresponding word lines. Disconnecting the bad block 310 may prevent voltage (e.g., from word line biasing and / or reset reading) from shorting to ground through defective paths within the bad block 310.
[0046] As described in detail below, the memory device 100 can disable the bad blocks 310 in real time after detecting / identifying the bad blocks formed during the post-deployment operation of the memory device 100. For example, the memory device 100 can disable the bad blocks 310 based on autonomously (e.g., without interaction with the controller 106 and / or the host device 108) detecting the bad blocks 310 and implementing the above-described process of disabling the bad blocks 310. Moreover, the memory device 100 can disable the bad blocks 310 based on implementing the command sequence described above.
[0047] At box 418, the memory device 100 may implement normal post-deployment operations, such as reading, writing, and / or erasing data. In some embodiments, as illustrated at box 442, the memory device 100 may bias one or more of the word lines to a predetermined non-zero voltage level during the standby mode as described above. In some embodiments, as illustrated at box 444, the memory device 100 may implement a reset read as described above. For example, the memory device 100 may track the elapsed time measured since the last access to the memory location and implement a reset read before implementing a read command when the elapsed time exceeds a threshold. For the reset read, the memory device 100 may provide a non-zero voltage to a group of word lines for interrupting the long-term inactivity of the memory block. Disabling / disconnecting the bad connection block 310 may prevent the word line from being shorted to ground through the degraded memory cell, thereby enabling the word line biasing and / or reset read to function properly and reduce associated errors.
[0048] In some embodiments, as illustrated at block 446, the memory device 100 (via, for example, Figure 3 The current monitor 304 can measure the current during post-deployment operation. Figure 3 For example, the memory device 100 can measure the current consumption through the word lines for detecting the occurrence of bad blocks 310. In some embodiments, when the word lines are biased, when memory cells degrade (thus forming bad blocks 310), an increase in current consumption can be caused.
[0049] At block 422, the memory device 100 may identify post-production bad blocks (eg, bad blocks 310). For example, the memory device 100 may identify the bad blocks 310 based on measured current and / or command sequences.
[0050] In some embodiments, as illustrated at block 446, the memory device 100 may identify bad blocks based on the measured current. For example, the memory device 100 and / or the memory block 128 therein may compare the monitored current level with a predetermined threshold and generate a flag when the current level matches and / or exceeds the predetermined threshold. The memory device 100 (via, for example, the controller 106, the current monitor 304, and / or the memory block 128) may identify bad blocks and / or their addresses based on the current measurement. For example, when the flag is triggered, the memory device 100 may identify the deployment tag address 322 as the address of the memory block being accessed and / or connected to the word line.
[0051] At block 424, the identified address (e.g., deployment mark address 322) may be stored in the deployment mark storage device 312. The memory device 100 may store the deployment mark address 322 in a location associated with the deployment mark storage device 312. Figure 3 The deployment mark address 322 may be stored in a location (e.g., one or more designated memory blocks and / or a group of memory circuits) separate from the production mark storage 316 and / or the ROM storage 314. In some embodiments, for example, the deployment mark address 322 may be stored in a portion of the ROM storage 314 designated as the deployment mark storage 312. Thus, the ROM storage 314 may store the deployment mark address 322 and trim data for reading and / or writing data. In other embodiments, the deployment mark address 322 may be stored in a deployment mark storage 312 separate from both the production mark storage 316 and the ROM storage 314. In some embodiments, the deployment mark address 322 may be tracked using an extended bad block map as described above.
[0052] The identified addresses may be used to disable the corresponding bad blocks 310 as described at block 416. In some embodiments, the memory device 100 may autonomously identify and disable bad blocks based on the measured current at the memory device 100 and / or at the memory array 302 without interacting with an external device (e.g., the host device 108 and / or the controller 106, respectively). In other embodiments, the memory device 100 may report the deployment mark address 322 and interact with a user (via, for example, the controller 106 and / or the host device 108) to disable the bad blocks 310. For example, the memory device 100 may receive and implement a command sequence to disable the bad blocks 310 as described above. Moreover, the stored addresses may be used to maintain the disabled bad blocks 310 in the power cycling event described at block 412. Thus, the memory device 100 may access / read the deployment mark address 322 during or after initialization and / or reset of the memory device 100 and disable the bad blocks 310 as described above.
[0053] Figure 5is a schematic diagram of a system including a memory device according to an embodiment of the present invention. Figure 1-4 Any of the above-described memory devices may be incorporated into any of a myriad of larger and / or more complex systems, a representative example of which is in Figure 5 580 is schematically shown in FIG. 580. The system 580 may include a memory device 500, a power supply 582, a driver 584, a processor 586, and / or other subsystems or components 588. The memory device 500 may include a substantially similar Figure 1-4 The system 580 may be configured to have features similar to those of the memory devices described herein, and thus may include various features for performing direct read requests from a host device. The resulting system 580 may perform any of a variety of functions, such as memory storage, data processing, and / or other suitable functions. Thus, representative systems 580 may include, but are not limited to, handheld devices (e.g., mobile phones, tablet computers, digital readers, and digital audio players), computers, vehicles, appliances, and other products. The components of system 580 may be housed in a single unit or distributed across multiple interconnected units (e.g., via a communications network). The components of system 580 may also include remote devices and any of a variety of computer-readable media.
[0054] It should be noted that the methods described above describe possible embodiments, and that the operations and steps may be rearranged or otherwise modified, and other embodiments are possible. Furthermore, embodiments from two or more of the described methods may be combined.
[0055] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Some diagrams may show a signal as a single signal; however, one of ordinary skill in the art will understand that the signal may represent a signal bus, where the bus may have a variety of bit widths.
[0056] The devices discussed herein, including memory devices, may be formed on a semiconductor substrate or die such as silicon, germanium, silicon-germanium alloys, gallium arsenide, gallium nitride, etc. In some cases, the substrate is a semiconductor wafer. In other cases, the substrate may be a silicon-on-insulator (SOI) substrate, such as silicon-on-glass (SOG) or silicon-on-sapphire (SOP), or an epitaxial layer of a semiconductor material on another substrate. The conductivity of the substrate or a sub-region of the substrate may be controlled by doping using various chemical species including, but not limited to, phosphorus, boron, or arsenic. Doping may be performed during the initial formation or growth of the substrate, by ion implantation, or by any other doping method.
[0057] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Other examples and implementations are within the scope of the present disclosure and the appended claims. Features implementing the functions may also be physically located at various locations, including being distributed so that parts of the functions are implemented at different physical locations.
[0058] As used herein (including in the claims), "or" as used in a list of items (e.g., a list of items followed by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, as used herein, the phrase "based on" should not be understood as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted similarly to the phrase "based at least in part on."
[0059] It will be appreciated from the foregoing that specific embodiments of the present invention have been described herein for illustrative purposes, but various modifications may be made without departing from the spirit and scope of the present invention. Specifically, in the above description, numerous specific details are discussed to provide a thorough and illustrative description of embodiments of the present invention. However, those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more of the specific details. In other cases, well-known structures or operations typically associated with memory systems and devices are not shown, or are not described in detail, to avoid obfuscating other aspects of the technology. In general, it should be understood that various other devices, systems, and methods other than those specific embodiments disclosed herein may be within the scope of the present invention.
Claims
1. A memory device, comprising: A memory array comprising: memory blocks each having a plurality of memory cells configured to store data; one or more current monitors configured to determine current measurements during post-deployment operation of the memory device; and a controller coupled to the memory array, the controller being configured to: identifying a bad block within the memory block based on the determined current measurement; disabling the bad block to prevent access to the bad block during subsequent operation of the memory device; as well as implementing a reset read prior to a read command for interrupting a long period of inactivity in one or more of the memory blocks associated with the read command; in: The controller and / or the memory array are configured to isolate the bad blocks from a non-zero bias voltage associated with accessing the data.
2. The memory device of claim 1, wherein: The controller is configured to identify a deployment tag address of the bad block; and The memory device further comprises: A read-only memory ROM is configured to store the deployment mark address and trim data for reading and / or writing data, wherein the controller accesses the deployment mark address after a reset of the memory device for preventing the access to the bad block.
3. The memory device of claim 1 , further comprising: a production mark storage device configured to store a production mark address; a deployment mark storage device configured to store a deployment mark address of the bad block, wherein the controller accesses the deployment mark address after a reset of the memory device for preventing the access to the bad block; and The controller is configured to: identifying the deployment marking address of the bad block based on the determined current measurement, and The production marking address and the deployment marking address are accessed after a reset of the memory device for preventing the access to the bad block.
4. The memory device of claim 3, wherein: The production marking address indicates one of the memory blocks that was found to be defective prior to deployment of the memory device; and The deployment mark address indicates the bad block that is found to be defective after the memory device is deployed.
5. The memory device of claim 1, wherein the memory array comprises one or more designated memory blocks configured to store deployment mark addresses of the bad blocks, wherein the deployment mark addresses are used to prevent the access to the bad blocks.
6. The memory device of claim 1 , wherein the memory array includes a disable latch coupled to the one or more memory blocks and configured to disable the bad blocks based on disconnecting the bad blocks from one or more corresponding word lines and / or other memory blocks in the memory device, wherein the disable latch is volatile and reset based on an interruption in receiving power.
7. The memory device of claim 1 , wherein the controller is configured to: transmitting a command sequence for interacting with a host device coupled to the memory device; and The bad blocks are deactivated based on the command sequence.
8. The memory device of claim 7, wherein the command sequence includes a set (SET) feature command.
9. The memory device of claim 1, wherein: The memory array includes a word line connected to the memory block and configured to provide access to the connected memory block; as well as The memory array is configured to bias one or more of the word lines to the non-zero bias voltage when a corresponding memory block is in a standby mode; and The controller and / or the memory array are configured to isolate the bad block from one or more corresponding word lines for preventing the non-zero bias voltage from being shorted to ground through a defective path within the bad block.
10. The memory device of claim 1, wherein: The memory array includes word lines connected to the memory blocks and configured to provide access to the connected memory blocks; and The controller is configured to: Tracking the elapsed time measured since the memory location was last accessed; Before the elapsed time exceeds a threshold, performing the reset read, wherein performing the reset read comprises providing a non-zero voltage to a set of the word lines; and The bad block is isolated from the group of the word lines for preventing the supplied voltage from being shorted to ground through a defective path within the bad block.
11. A memory system comprising: Host device; and a memory device coupled to the host device, wherein: The memory device includes memory blocks each having a plurality of memory cells configured to store data, and The memory device is configured to: determining a current measurement during post-deployment operation of the memory device; identifying a bad block within the memory block based on the determined current measurement; disabling the bad block to prevent access to the bad block during subsequent data operations; performing a reset read prior to a read command for interrupting a long period of inactivity in one or more of the memory blocks associated with the read command; and The bad blocks are isolated from a non-zero bias voltage associated with accessing the data.
12. The memory system of claim 11, wherein: The memory device is configured to: identifying the bad blocks, When the determined current metric meets or exceeds a threshold, reporting the bad block, and disabling the bad blocks based on interacting with the host device; and The host device is configured to: receiving a report of the bad block from the memory device, and A command sequence for sending a set (SET) feature command to disable the bad block is implemented.
13. The memory system of claim 11, wherein the memory device is configured to autonomously identify and disable the bad blocks based on the determined current measurement without interaction with the host device.
14. The memory system of claim 11, wherein the memory device is a flash memory device.
15. The memory system of claim 14, wherein the flash memory device is a NAND device.
16. A method of operating a memory device including a controller and a memory array, the memory array including memory blocks each having a plurality of memory cells configured to store data, the method comprising: determining a metric consumption of current of one or more of the memory blocks during post-deployment operation of the memory device; identifying bad blocks within the memory block based on the determined current measurement consumption; disabling the bad block to prevent access to the bad block during subsequent operation of the memory device; isolating the bad block from a non-zero bias voltage; as well as When the elapsed time measured since the last access to the memory location exceeds a threshold, a reset read is performed.
17. The method of claim 16, wherein: Identifying the bad block includes identifying an address of the bad block; The method further comprises: storing the address of the bad block; and After a reset of the memory device, the address is provided to a disabling circuit.
18. The method of claim 17, wherein storing the address of the bad block comprises storing the address in one or more of the memory blocks designated for storing addresses of blocks that become defective after deployment of the memory device.
19. The method of claim 17, wherein storing the address of the bad block comprises storing the address in a read-only memory (ROM) configured to store the address and trim data for reading and / or writing data for the memory array.
20. The method of claim 16, wherein disabling the bad block comprises operating a disable latch coupled to the bad block to disconnect the bad block from one or more corresponding word lines and / or other memory blocks in the memory device.
