US20170062060A1 - Method and controller for managing memory device - Google Patents
Method and controller for managing memory device Download PDFInfo
- Publication number
- US20170062060A1 US20170062060A1 US15/163,686 US201615163686A US2017062060A1 US 20170062060 A1 US20170062060 A1 US 20170062060A1 US 201615163686 A US201615163686 A US 201615163686A US 2017062060 A1 US2017062060 A1 US 2017062060A1
- Authority
- US
- United States
- Prior art keywords
- memory
- writing command
- specific
- data
- memory cell
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 230000015654 memory Effects 0.000 claims abstract description 182
- 238000012545 processing Methods 0.000 claims description 28
- 230000004044 response Effects 0.000 claims description 16
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 230000005540 biological transmission Effects 0.000 description 7
- 238000012986 modification Methods 0.000 description 6
- 230000004048 modification Effects 0.000 description 6
- 238000012360 testing method Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0653—Monitoring storage devices or systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F12/00—Accessing, addressing or allocating within memory systems or architectures
- G06F12/02—Addressing or allocation; Relocation
- G06F12/0223—User address space allocation, e.g. contiguous or non contiguous base addressing
- G06F12/023—Free address space management
- G06F12/0238—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory
- G06F12/0246—Memory management in non-volatile memory, e.g. resistive RAM or ferroelectric memory in block erasable memory, e.g. flash memory
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/064—Management of blocks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0655—Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
- G06F3/0659—Command handling arrangements, e.g. command buffers, queues, command scheduling
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/08—Address circuits; Decoders; Word-line control circuits
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
- G11C16/14—Circuits for erasing electrically, e.g. erase voltage switching circuits
- G11C16/16—Circuits for erasing electrically, e.g. erase voltage switching circuits for erasing blocks, e.g. arrays, words, groups
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/10—Programming or data input circuits
- G11C16/20—Initialising; Data preset; Chip identification
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/34—Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
- G11C16/3418—Disturbance prevention or evaluation; Refreshing of disturbed memory data
- G11C16/3422—Circuits or methods to evaluate read or write disturbance in nonvolatile memory, without steps to mitigate the problem
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/34—Determination of programming status, e.g. threshold voltage, overprogramming or underprogramming, retention
- G11C16/3436—Arrangements for verifying correct programming or erasure
- G11C16/3454—Arrangements for verifying correct programming or for detecting overprogrammed cells
- G11C16/3459—Circuits or methods to verify correct programming of nonvolatile memory cells
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/04—Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS
- G11C16/0483—Erasable programmable read-only memories electrically programmable using variable threshold transistors, e.g. FAMOS comprising cells having several storage transistors connected in series
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11C—STATIC STORES
- G11C16/00—Erasable programmable read-only memories
- G11C16/02—Erasable programmable read-only memories electrically programmable
- G11C16/06—Auxiliary circuits, e.g. for writing into memory
- G11C16/26—Sensing or reading circuits; Data output circuits
Definitions
- the present invention relates to controlling a flash memory, and more particularly, to a method and controller for managing a memory device.
- NAND flash memories include single level cell (SLC) memories and multiple level cell (MLC) memories.
- SLC flash memory which can be viewed as a memory cell
- MLC flash memory Each transistor in an SLC flash memory (which can be viewed as a memory cell) only has two electric charge levels representing logic 0 and logic 1, respectively.
- the transistors in an MLC flash memory are driven by a higher voltage to record information of multiple bits (e.g. 00, 01, 11, 10) using voltages of different levels.
- the recording density of the MLC flash memory can be more than twice the recording density of the SLC flash memory. This is good news for the manufacturers of NAND flash memories when considering issues in design and research.
- MLC flash memories Since the manufacturing cost of MLC flash memories is cheaper than that of SLC flash memories, and as the MLC flash memories may provide a larger capacity in a limited space, applying MLC flash memories to portable memory devices has become more and more popular.
- the operation of some types of MLC flash memories can be complicated, and introduces various issues. For example, the initialization time of a conventional memory device adopting an MLC flash memory will be greatly increased, making the related cost increase correspondingly.
- a novel method to enhance the control of memory devices which can improve their initialization efficiency without introducing negative side effects.
- An objective of the present invention is to provide a method for managing a memory device, and an associated memory device and controller, which can solve the above issue.
- Another objective of the present invention is to provide a method for managing a memory device and an associated memory device and controller that can improve the operation efficiency of the memory device, and thereby save related costs.
- At least one preferred embodiment of the present invention provides a method for managing a memory device.
- the memory device comprises at least one non-volatile (NV) memory element, wherein each NV memory element comprises a plurality of blocks.
- the method comprises: sending a last writing command to a specific NV memory element within the NV memory element, to write a set of data to a specific block of the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element.
- the first writing command, the second writing command and the last writing command are used to write a same data into a same location in the NV memory element at different times, respectively, to ensure that the same data is stored correctly.
- the method further comprises: after the set of data is written to the specific block, sending a read command to the specific NV memory element to read stored data of the set of data from the specific block, and checking whether the stored data matches the set of data to determine whether the specific block is a bad block.
- the present invention also provides a memory device.
- the memory device comprises at least one NV memory element, each comprising a plurality of blocks; and a controller, arranged to control the NV memory element.
- the controller comprises a processing unit for managing the memory device according to a program code embedded in the processing unit or a program code received from outside the processing unit, wherein the controller sends a last writing command to a specific NV memory element within the NV memory element to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element.
- the first writing command, the second writing command, and the last writing command are used to write a same data into a same location in the NV memory element at different times, respectively, to ensure that the same data is stored correctly.
- the controller sends a read command to the specific NV memory element to read stored data of the set of data from the specific block, and checks whether the stored data matches the set of data to determine whether the specific block is a bad block.
- the present invention also provides a controller of a memory device.
- the memory device comprises at least one NV memory element, each comprising a plurality of blocks.
- the controller comprises a processing unit, arranged to manage the memory device according to a program code embedded in the processing unit or received from outside the processing unit.
- the controller sends a last writing command to a specific NV memory element within the NV memory element to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, wherein the first writing command, the second writing command, and the last writing command are arranged to write a same data to a same location in the NV memory element at different times, to ensure that the same data is correctly stored.
- the controller sends a reading command to the specific NV memory element to read stored data of the set of data from the specific block, and checks whether the stored data matches the set of data to determine whether the specific block is a bad block.
- An advantage provided by the present invention is that, compared with related arts, the method, memory device and controller of the present invention may greatly save the initialization time of the memory device before it leaves the factory, wherein the aforementioned initialization is usually performed at the end of the manufacturing process. Compared with related arts, the present invention may provide a better efficiency, and may save related costs, such as time and human resources.
- FIG. 1 is a diagram illustrating a memory device according to a first embodiment of the present invention.
- FIG. 2 is a flowchart illustrating a method for managing a memory device according to an embodiment of the present invention.
- FIG. 3 is a diagram illustrating a control scheme associated with the memory device shown in FIG. 1 according to an embodiment of the present invention.
- FIG. 4 is a diagram illustrating a control scheme associated with the memory device shown in FIG. 1 according to another embodiment of the present invention.
- FIG. 5 is a diagram illustrating a control scheme associated with the method shown in FIG. 2 according to an embodiment of the present invention.
- FIG. 1 is a diagram illustrating a memory device 100 according to a first embodiment of the present invention.
- the memory device 100 comprises: a processing unit 110 , a volatile memory 120 , a transmission interface 130 , a plurality of non-volatile (NV) memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N (wherein N is a positive integer), such as (N+1) flash chips, and a bus 150 .
- the transmission interface 130 may utilize the transmission interface 130 to access the memory device 100 .
- the host may represent a personal computer (PC), such as a laptop computer or a desktop computer.
- PC personal computer
- the processing unit 110 may refer to a program code (not shown in the figure) embedded in the processing unit 110 or received from outside the processing unit 110 , to manage the memory device 100 .
- the program code may be a hardware code embedded in the processing unit 110 , and more particularly, a read-only memory code (ROM code).
- the program code may be a firmware code received from outside the processing unit 110 .
- the processing unit 110 is arranged to control the volatile memory 120 , the transmission interface 130 , the NV memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N, and the bus 150 .
- the processing unit 110 may be an Advanced Reduced Instruction Set Computer Machine (Advanced RISC Machine, ARM) processor or an Argonaut RISC Core (ARC) processor.
- Advanced RISC Machine ARM
- ARC Argonaut RISC Core
- the processing unit 110 may be another type of processor.
- the processing unit 110 may receive specific commands from an external electronic device (e.g. a PC) other than the memory device 100 , and refer to the specific commands to perform initialization of the memory device 100 before it leaves the factory.
- an external electronic device e.g. a PC
- the aforementioned initialization is performed immediately after the memory device 100 is manufactured.
- the program executed in the external electronic device associated with a corresponding initialization may be viewed as an example of the aforementioned program code received from outside the processing unit 110 .
- the volatile memory 120 may be used to store a Global Page Address Linking Table, the data accessed by the host, and information required for accessing the memory device 100 .
- the volatile memory 120 in this embodiment may be a dynamic random access memory (DRAM) or a static random access memory (SRAM).
- DRAM dynamic random access memory
- SRAM static random access memory
- the volatile memory 120 may be another type of volatile memory.
- the volatile memory 120 may comprise an SRAM.
- the transmission interface 130 shown in FIG. 1 is arranged to transmit data and commands between the host and the memory device 100 , wherein the transmission interface 130 conforms to a specific communications specification, such as the Serial Advanced Technology Attachment (SATA) specification, the Parallel Advanced Technology Attachment (PATA) specification, or the Universal Serial Bus (USB) specification.
- the memory device 100 may be a Solid State Drive (SSD) configured in the host, and the specific communications specification may be used to implement some typical communications specifications of the internal communications of the host, such as the SATA specification or the PATA specification.
- the memory device 100 is an SSD configured outside the host, and the specific communications specification may be arranged to implement some communications specifications of the external communications of the host, such as the USB specification.
- the memory device 100 may be a portable memory device such as a memory card, and the specific communications specification may be arranged to implement some communications specifications of the input/output (I/O) interface of a memory card, such as the Secure Digital (SD) specification or the Compact Flash (CF) specification.
- I/O input/output
- SD Secure Digital
- CF Compact Flash
- the NV memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N are arranged to store data, wherein the NV memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N may be (but are not limited to) NAND flash chips.
- the bus 150 is arranged to couple and provide communicates between the processing unit 110 , the volatile memory 120 , transmission interface 130 , and the NV memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N.
- 140 _N may be integrated as a controller, and more particularly, an integrated circuit (IC) (e.g. a controller chip), wherein the controller is arranged to control at least one NV memory element in the memory device 100 , such as the NV memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N.
- IC integrated circuit
- the controller may be viewed as a controller of the memory device 100 .
- each NV memory element within the NV memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N shown in FIG. 1 may comprise a plurality of blocks, wherein the NV memory element 140 _ n in this embodiment may be realized as a flash chip, and the index n may be an integer within [0, N]. More particularly, each block may comprise a plurality of pages each comprising a plurality of sections. For example, a section may be the smallest reading unit. In other words, during a reading operation, the processing unit 110 may be one or more sections. This is merely for illustrative purposes, and not meant to be a limitation of the present invention.
- FIG. 2 is a flowchart illustrating a method 200 for managing a memory device according to an embodiment of the present invention.
- the method 200 may be applied to the memory device 100 shown in FIG. 1 , and more particularly, to the aforementioned controller (e.g. the memory controller executing the program code through the processing unit 110 ), wherein the controller executing the aforementioned program code is arranged to control the NV memory element such as the NV memory elements 140 _ 0 , 140 _ 1 , . . . , 140 _N shown in FIG. 1 .
- the method 200 is described as follows.
- the controller sends a last writing command to a specific NV memory element (e.g. the NV memory element 140 _ n ) within the NV memory element, to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, wherein the first writing command, the second writing command, and the last writing command are used to write the same data into the same location of the NV memory element at different times to ensure that the same data is correctly stored.
- the set of data may comprise data having a predetermined pattern.
- step 220 after the set of data is written to the specific block, the controller sends a reading command to the specific NV memory element in order to read the stored data of the set of data from the specific block (e.g. the storage result of the set of data), and check whether the stored data matches the set of data, to determine whether the specific block is a bad block.
- the controller determines the specific block as a bad block, and may record the information that the specific block is a bad block.
- the controller determines the specific block as a good block, and may record the information that the specific block is a good block.
- step 230 the controller checks whether the flow should be stopped or not. When it is determined that the flow should be stopped (e.g. all the blocks to be checked are checked), the flow is ended as shown in FIG. 2 ; otherwise, the flow returns to Step 210 .
- operations of Steps 210 and Step 220 may be repeatedly performed to perform the quality scan test block by block. More particularly, the controller may perform the quality scan test on at least a portion (e.g. part or all) of the NV memory element 140 _ n block by block, until the portion of the NV memory element 140 _ n is checked. The controller may also perform the quality scan test on a plurality (e.g. part or all) of NV memory elements within the NV memory element block by block, until all blocks in each NV memory element in the plurality of non-volatile memories are checked.
- the plurality of bits may need to be repeatedly written into the memory cell for a predetermined number of times being more than 1. This is in order to make the memory cell be correctly programmed in the specific NV memory, so that each bit of the plurality of bits is correctly stored in the memory cell for follow-up readings.
- the first writing command is arranged to instruct an inner control circuit of the aforementioned any NV memory element to write the plurality of bits into the memory cell for the first time
- the second writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a second time
- the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for the last time.
- the predetermined times equals three
- the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for the third time.
- the busy duration of operations of the inner control circuit in response to the first writing command is less than the busy duration of operations of the inner control circuit in response to second writing command.
- the busy duration of operations of the inner control circuit in response to the second writing command is less than the busy duration of operations of the inner control circuit in response to the last writing command, wherein the aforementioned busy duration may be determined by detecting a busy signal outputted by the specific NV memory element (e.g. the NV memory element 140 _ n ).
- the controller may utilize the last writing command to control a state of the memory cell corresponding to a portion of a plurality of programmable states, rather than controlling any of the plurality of programmable states.
- the plurality of programmable state may comprise eight programmable states corresponding to three bits, and the number of the portion of programmable states is smaller than eight, wherein the total of the eight programmable states corresponds to 2 3 (i.e. 8).
- the method shown in FIG. 2 may be applied to the memory device 100 shown in FIG. 1 , and more particularly, to the aforementioned controller (e.g. a memory controller operated by utilizing the processing unit 110 to execute the aforementioned program code).
- the aforementioned controller e.g. a memory controller operated by utilizing the processing unit 110 to execute the aforementioned program code.
- the method 200 shown in FIG. 2 may be applied to the external electronic device.
- FIG. 3 is a diagram illustrating a control scheme associated with the memory device 100 shown in FIG. 1 according to an embodiment of the present invention.
- the controller may use the first writing command, the second writing command and/or the last writing command if necessary, without being limited by Step 210 .
- the controller may utilize the first writing command, the second writing command and the last writing command to control the memory cell in the specific block to enter any of the plurality of programmable states, such as any of the eight programmable states represented by eight curves in FIG. 3 .
- the controller may refer to a plurality of thresholds ⁇ AR, BR, CR, DR, ER, FR, GR ⁇ to determine which state of the plurality of programmable states is the current programmable state of the memory cell in the specific block (e.g. the information stored in the memory cell of the specific block), in order to obtain data of all bits (e.g. three bits in this embodiment) stored in the memory cell.
- a plurality of thresholds ⁇ AR, BR, CR, DR, ER, FR, GR ⁇ to determine which state of the plurality of programmable states is the current programmable state of the memory cell in the specific block (e.g. the information stored in the memory cell of the specific block), in order to obtain data of all bits (e.g. three bits in this embodiment) stored in the memory cell.
- FIG. 4 is a diagram illustrating a control scheme associated with the memory device 100 shown in FIG. 1 according to another embodiment of the present invention.
- the controller in this embodiment uses the last writing command only. More specifically, the controller utilizes the last writing command to control the memory cell in the specific block to be in any state of the plurality of programmable states, such as any of the eight programmable states represented by the eight curves shown in FIG. 4 . Note that since the controller merely uses the last writing command, at least one portion of the eight curves shown in FIG. 4 is thus overlapped.
- the controller cannot directly refer to the thresholds ⁇ AR, BR, CR, DR, ER, FR, GR ⁇ to determine which of the plurality of programmable states is the current programmable state of the memory cell in the specific block (e.g. the information stored in the memory cell of the specific block), thus cannot obtain data of all bits stored in the memory cell.
- FIG. 5 is a diagram illustrating a control scheme associated with the method 200 shown in FIG. 2 according to an embodiment of the present invention.
- the controller uses the last writing command only. More specifically, the controller utilizes the last writing command to control the memory cell in the specific block to stay in one state of the portion of the plurality of programmable states only, such as any of the three programmable states represented by the three curves shown in FIG. 5 .
- the controller uses the last writing command only. More specifically, the controller utilizes the last writing command to control the memory cell in the specific block to stay in one state of the portion of the plurality of programmable states only, such as any of the three programmable states represented by the three curves shown in FIG. 5 .
- the plurality of programmable states e.g.
- the controller may utilize the predetermined pattern in the set of data to control the memory cell in the specific block to correspond to one state of the portion of the plurality of programmable states only, such as any of the three programmable state represented by the three curves shown in FIG. 5 .
- the controller may refer to at least one portion of the thresholds ⁇ AR, BR, CR, DR, ER, FR, GR ⁇ to determine which state of the portion of the plurality of programmable states is the current programmable state of the memory cell in the specific block (e.g. the information stored in the memory cell in the specific block), thus obtaining data of all bits (e.g. three bits in this embodiment) stored in the memory cell.
Abstract
A method for managing a memory device includes: sending a last writing command to a specific non-volatile (NV) memory element in the memory device to write a set of data to a specific block of the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, where these writing commands are utilized for writing to the same location at different times, respectively, in order to guarantee data correctness; and after writing the set of data to the specific block, sending a read command to the specific NV memory element to read stored data of the set of data from the specific block, and checking whether the stored data match the set of data to determine whether the specific block is a bad block.
Description
- 1. Field of the Invention
- The present invention relates to controlling a flash memory, and more particularly, to a method and controller for managing a memory device.
- 2. Description of the Prior Art
- Developments in flash memories have led to wide application in portable memory devices, such as memory cards conforming to the SD/MMC, CF, MS and XD specifications. How to control flash memories in these portable memory devices has become an important issue.
- NAND flash memories include single level cell (SLC) memories and multiple level cell (MLC) memories. Each transistor in an SLC flash memory (which can be viewed as a memory cell) only has two electric charge levels representing logic 0 and logic 1, respectively. The transistors in an MLC flash memory are driven by a higher voltage to record information of multiple bits (e.g. 00, 01, 11, 10) using voltages of different levels. Theoretically, the recording density of the MLC flash memory can be more than twice the recording density of the SLC flash memory. This is good news for the manufacturers of NAND flash memories when considering issues in design and research.
- Since the manufacturing cost of MLC flash memories is cheaper than that of SLC flash memories, and as the MLC flash memories may provide a larger capacity in a limited space, applying MLC flash memories to portable memory devices has become more and more popular. The operation of some types of MLC flash memories can be complicated, and introduces various issues. For example, the initialization time of a conventional memory device adopting an MLC flash memory will be greatly increased, making the related cost increase correspondingly. Hence, there is a need for a novel method to enhance the control of memory devices which can improve their initialization efficiency without introducing negative side effects.
- An objective of the present invention is to provide a method for managing a memory device, and an associated memory device and controller, which can solve the above issue.
- Another objective of the present invention is to provide a method for managing a memory device and an associated memory device and controller that can improve the operation efficiency of the memory device, and thereby save related costs.
- At least one preferred embodiment of the present invention provides a method for managing a memory device. The memory device comprises at least one non-volatile (NV) memory element, wherein each NV memory element comprises a plurality of blocks. The method comprises: sending a last writing command to a specific NV memory element within the NV memory element, to write a set of data to a specific block of the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element. The first writing command, the second writing command and the last writing command are used to write a same data into a same location in the NV memory element at different times, respectively, to ensure that the same data is stored correctly. The method further comprises: after the set of data is written to the specific block, sending a read command to the specific NV memory element to read stored data of the set of data from the specific block, and checking whether the stored data matches the set of data to determine whether the specific block is a bad block.
- In addition to the above method, the present invention also provides a memory device. The memory device comprises at least one NV memory element, each comprising a plurality of blocks; and a controller, arranged to control the NV memory element. The controller comprises a processing unit for managing the memory device according to a program code embedded in the processing unit or a program code received from outside the processing unit, wherein the controller sends a last writing command to a specific NV memory element within the NV memory element to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element. The first writing command, the second writing command, and the last writing command are used to write a same data into a same location in the NV memory element at different times, respectively, to ensure that the same data is stored correctly. After the set of data is written to the specific block, the controller sends a read command to the specific NV memory element to read stored data of the set of data from the specific block, and checks whether the stored data matches the set of data to determine whether the specific block is a bad block.
- In addition to the above method, the present invention also provides a controller of a memory device. The memory device comprises at least one NV memory element, each comprising a plurality of blocks. The controller comprises a processing unit, arranged to manage the memory device according to a program code embedded in the processing unit or received from outside the processing unit. The controller sends a last writing command to a specific NV memory element within the NV memory element to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, wherein the first writing command, the second writing command, and the last writing command are arranged to write a same data to a same location in the NV memory element at different times, to ensure that the same data is correctly stored. After the set of data is written to the specific block, the controller sends a reading command to the specific NV memory element to read stored data of the set of data from the specific block, and checks whether the stored data matches the set of data to determine whether the specific block is a bad block.
- An advantage provided by the present invention is that, compared with related arts, the method, memory device and controller of the present invention may greatly save the initialization time of the memory device before it leaves the factory, wherein the aforementioned initialization is usually performed at the end of the manufacturing process. Compared with related arts, the present invention may provide a better efficiency, and may save related costs, such as time and human resources.
- These and other objectives of the present invention will no doubt become obvious to those of ordinary skill in the art after reading the following detailed description of the preferred embodiment that is illustrated in the various figures and drawings.
-
FIG. 1 is a diagram illustrating a memory device according to a first embodiment of the present invention. -
FIG. 2 is a flowchart illustrating a method for managing a memory device according to an embodiment of the present invention. -
FIG. 3 is a diagram illustrating a control scheme associated with the memory device shown inFIG. 1 according to an embodiment of the present invention. -
FIG. 4 is a diagram illustrating a control scheme associated with the memory device shown inFIG. 1 according to another embodiment of the present invention. -
FIG. 5 is a diagram illustrating a control scheme associated with the method shown inFIG. 2 according to an embodiment of the present invention. -
FIG. 1 is a diagram illustrating a memory device 100 according to a first embodiment of the present invention. The memory device 100 comprises: a processing unit 110, a volatile memory 120, a transmission interface 130, a plurality of non-volatile (NV) memory elements 140_0, 140_1, . . . , 140_N (wherein N is a positive integer), such as (N+1) flash chips, and a bus 150. Typically, after the transmission interface 130 is coupled to a host (not shown inFIG. 1 ), the host may utilize the transmission interface 130 to access the memory device 100. The host may represent a personal computer (PC), such as a laptop computer or a desktop computer. - The processing unit 110 may refer to a program code (not shown in the figure) embedded in the processing unit 110 or received from outside the processing unit 110, to manage the memory device 100. The program code may be a hardware code embedded in the processing unit 110, and more particularly, a read-only memory code (ROM code). In another example, the program code may be a firmware code received from outside the processing unit 110. The processing unit 110 is arranged to control the volatile memory 120, the transmission interface 130, the NV memory elements 140_0, 140_1, . . . , 140_N, and the bus 150. In this embodiment, the processing unit 110 may be an Advanced Reduced Instruction Set Computer Machine (Advanced RISC Machine, ARM) processor or an Argonaut RISC Core (ARC) processor. This is merely for illustrative purposes, and not meant to be a limitation of the present invention. According to various modifications of this embodiment, the processing unit 110 may be another type of processor. According to some modifications of this embodiment, the processing unit 110 may receive specific commands from an external electronic device (e.g. a PC) other than the memory device 100, and refer to the specific commands to perform initialization of the memory device 100 before it leaves the factory. In general, the aforementioned initialization is performed immediately after the memory device 100 is manufactured. In this situation, the program executed in the external electronic device associated with a corresponding initialization may be viewed as an example of the aforementioned program code received from outside the processing unit 110.
- The volatile memory 120 may be used to store a Global Page Address Linking Table, the data accessed by the host, and information required for accessing the memory device 100. The volatile memory 120 in this embodiment may be a dynamic random access memory (DRAM) or a static random access memory (SRAM). According to various modifications of this embodiment, the volatile memory 120 may be another type of volatile memory. For example, the volatile memory 120 may comprise an SRAM.
- According to this embodiment, the transmission interface 130 shown in
FIG. 1 is arranged to transmit data and commands between the host and the memory device 100, wherein the transmission interface 130 conforms to a specific communications specification, such as the Serial Advanced Technology Attachment (SATA) specification, the Parallel Advanced Technology Attachment (PATA) specification, or the Universal Serial Bus (USB) specification. The memory device 100 may be a Solid State Drive (SSD) configured in the host, and the specific communications specification may be used to implement some typical communications specifications of the internal communications of the host, such as the SATA specification or the PATA specification. In another example, the memory device 100 is an SSD configured outside the host, and the specific communications specification may be arranged to implement some communications specifications of the external communications of the host, such as the USB specification. According to some modifications of this embodiment, the memory device 100 may be a portable memory device such as a memory card, and the specific communications specification may be arranged to implement some communications specifications of the input/output (I/O) interface of a memory card, such as the Secure Digital (SD) specification or the Compact Flash (CF) specification. - The NV memory elements 140_0, 140_1, . . . , 140_N are arranged to store data, wherein the NV memory elements 140_0, 140_1, . . . , 140_N may be (but are not limited to) NAND flash chips. The bus 150 is arranged to couple and provide communicates between the processing unit 110, the volatile memory 120, transmission interface 130, and the NV memory elements 140_0, 140_1, . . . , 140_N. In this embodiment, in the structure shown in
FIG. 1 , the elements other than the NV memory elements 140_0, 140_1, . . . , 140_N may be integrated as a controller, and more particularly, an integrated circuit (IC) (e.g. a controller chip), wherein the controller is arranged to control at least one NV memory element in the memory device 100, such as the NV memory elements 140_0, 140_1, . . . , 140_N. Hence, the controller may be viewed as a controller of the memory device 100. - In this embodiment, each NV memory element within the NV memory elements 140_0, 140_1, . . . , 140_N shown in
FIG. 1 may comprise a plurality of blocks, wherein the NV memory element 140_n in this embodiment may be realized as a flash chip, and the index n may be an integer within [0, N]. More particularly, each block may comprise a plurality of pages each comprising a plurality of sections. For example, a section may be the smallest reading unit. In other words, during a reading operation, the processing unit 110 may be one or more sections. This is merely for illustrative purposes, and not meant to be a limitation of the present invention. -
FIG. 2 is a flowchart illustrating amethod 200 for managing a memory device according to an embodiment of the present invention. Themethod 200 may be applied to the memory device 100 shown inFIG. 1 , and more particularly, to the aforementioned controller (e.g. the memory controller executing the program code through the processing unit 110), wherein the controller executing the aforementioned program code is arranged to control the NV memory element such as the NV memory elements 140_0, 140_1, . . . , 140_N shown inFIG. 1 . Themethod 200 is described as follows. - In
step 210, the controller sends a last writing command to a specific NV memory element (e.g. the NV memory element 140_n) within the NV memory element, to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, wherein the first writing command, the second writing command, and the last writing command are used to write the same data into the same location of the NV memory element at different times to ensure that the same data is correctly stored. The set of data may comprise data having a predetermined pattern. - In
step 220, after the set of data is written to the specific block, the controller sends a reading command to the specific NV memory element in order to read the stored data of the set of data from the specific block (e.g. the storage result of the set of data), and check whether the stored data matches the set of data, to determine whether the specific block is a bad block. When the stored data does not match the set of data, the controller determines the specific block as a bad block, and may record the information that the specific block is a bad block. In another example, when the stored data matches the set of data, the controller determines the specific block as a good block, and may record the information that the specific block is a good block. - In
step 230, the controller checks whether the flow should be stopped or not. When it is determined that the flow should be stopped (e.g. all the blocks to be checked are checked), the flow is ended as shown inFIG. 2 ; otherwise, the flow returns to Step 210. As shown inFIG. 2 , operations ofSteps 210 andStep 220 may be repeatedly performed to perform the quality scan test block by block. More particularly, the controller may perform the quality scan test on at least a portion (e.g. part or all) of the NV memory element 140_n block by block, until the portion of the NV memory element 140_n is checked. The controller may also perform the quality scan test on a plurality (e.g. part or all) of NV memory elements within the NV memory element block by block, until all blocks in each NV memory element in the plurality of non-volatile memories are checked. - According to this embodiment, under the situation where a memory cell of a block of any NV memory element within the at least one NV memory element is used to store a plurality of bits, the plurality of bits may need to be repeatedly written into the memory cell for a predetermined number of times being more than 1. This is in order to make the memory cell be correctly programmed in the specific NV memory, so that each bit of the plurality of bits is correctly stored in the memory cell for follow-up readings. More particularly, the first writing command is arranged to instruct an inner control circuit of the aforementioned any NV memory element to write the plurality of bits into the memory cell for the first time, the second writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a second time, and the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for the last time. For example, when the predetermined times equals three, the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for the third time.
- Note that, in this embodiment, when writing the same data, the busy duration of operations of the inner control circuit in response to the first writing command is less than the busy duration of operations of the inner control circuit in response to second writing command. Further, when writing the same data, the busy duration of operations of the inner control circuit in response to the second writing command is less than the busy duration of operations of the inner control circuit in response to the last writing command, wherein the aforementioned busy duration may be determined by detecting a busy signal outputted by the specific NV memory element (e.g. the NV memory element 140_n). More particularly, in a situation where the storage capacity of a memory cell (such as the aforementioned memory cell) in the specific block is larger than 1 bit, the controller may utilize the last writing command to control a state of the memory cell corresponding to a portion of a plurality of programmable states, rather than controlling any of the plurality of programmable states. The plurality of programmable state may comprise eight programmable states corresponding to three bits, and the number of the portion of programmable states is smaller than eight, wherein the total of the eight programmable states corresponds to 23 (i.e. 8).
- As mentioned above, the method shown in
FIG. 2 may be applied to the memory device 100 shown inFIG. 1 , and more particularly, to the aforementioned controller (e.g. a memory controller operated by utilizing the processing unit 110 to execute the aforementioned program code). According to some modifications of this embodiment, under the situation where the processing unit 110 may receive some commands from the external electronic device, themethod 200 shown inFIG. 2 may be applied to the external electronic device. -
FIG. 3 is a diagram illustrating a control scheme associated with the memory device 100 shown inFIG. 1 according to an embodiment of the present invention. According to this embodiment, the controller may use the first writing command, the second writing command and/or the last writing command if necessary, without being limited byStep 210. In this situation, the controller may utilize the first writing command, the second writing command and the last writing command to control the memory cell in the specific block to enter any of the plurality of programmable states, such as any of the eight programmable states represented by eight curves inFIG. 3 . Note that the controller may refer to a plurality of thresholds {AR, BR, CR, DR, ER, FR, GR} to determine which state of the plurality of programmable states is the current programmable state of the memory cell in the specific block (e.g. the information stored in the memory cell of the specific block), in order to obtain data of all bits (e.g. three bits in this embodiment) stored in the memory cell. -
FIG. 4 is a diagram illustrating a control scheme associated with the memory device 100 shown inFIG. 1 according to another embodiment of the present invention. The controller in this embodiment uses the last writing command only. More specifically, the controller utilizes the last writing command to control the memory cell in the specific block to be in any state of the plurality of programmable states, such as any of the eight programmable states represented by the eight curves shown inFIG. 4 . Note that since the controller merely uses the last writing command, at least one portion of the eight curves shown inFIG. 4 is thus overlapped. Hence, the controller cannot directly refer to the thresholds {AR, BR, CR, DR, ER, FR, GR} to determine which of the plurality of programmable states is the current programmable state of the memory cell in the specific block (e.g. the information stored in the memory cell of the specific block), thus cannot obtain data of all bits stored in the memory cell. -
FIG. 5 is a diagram illustrating a control scheme associated with themethod 200 shown inFIG. 2 according to an embodiment of the present invention. In this embodiment, the controller uses the last writing command only. More specifically, the controller utilizes the last writing command to control the memory cell in the specific block to stay in one state of the portion of the plurality of programmable states only, such as any of the three programmable states represented by the three curves shown inFIG. 5 . Note that, according to predetermined relationships between all bits in the memory cell (e.g. there is a total of three bits in this embodiment) and the plurality of programmable states (e.g. there are eight programmable states in this embodiment), the controller may utilize the predetermined pattern in the set of data to control the memory cell in the specific block to correspond to one state of the portion of the plurality of programmable states only, such as any of the three programmable state represented by the three curves shown inFIG. 5 . This makes the curves separate from one another. Hence, the controller may refer to at least one portion of the thresholds {AR, BR, CR, DR, ER, FR, GR} to determine which state of the portion of the plurality of programmable states is the current programmable state of the memory cell in the specific block (e.g. the information stored in the memory cell in the specific block), thus obtaining data of all bits (e.g. three bits in this embodiment) stored in the memory cell. - Those skilled in the art will readily observe that numerous modifications and alterations of the device and method may be made while retaining the teachings of the invention. Accordingly, the above disclosure should be construed as limited only by the metes and bounds of the appended claims.
Claims (22)
1. A method for managing a memory device, the memory device comprising at least one non-volatile (NV) memory element, each NV memory element comprising a plurality of blocks, the method comprising:
sending a last writing command to a specific NV memory element within the NV memory element, to write a set of data to a specific block of the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, wherein the first writing command, the second writing command and the last writing command are used to write a same data into a same location in the NV memory element at different times, respectively, to ensure that the same data is stored correctly; and
after the set of data is written to the specific block, sending a read command to the specific NV memory element to read stored data of the set of data from the specific block, and checking whether the stored data matches the set of data to determine whether the specific block is a bad block.
2. The method of claim 1 , wherein under a situation where a memory cell of a block of any NV memory element within the at least one NV memory is arranged to store a plurality of bits, the plurality of bits are repeatedly written to the memory cell for a predetermined number of times, to make the memory cell be correctly programmed in the specific NV memory, so that each bit of the plurality of bits is correctly stored in the memory cell for follow-up readings; and the predetermined number of times is larger than 1.
3. The method of claim 2 , wherein the first writing command is arranged to instruct an inner control circuit in said any NV memory element within the at least one NV memory to write the plurality of bits into the memory cell for a first time, the second writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a second time, and the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a last time.
4. The method of claim 3 , wherein the predetermined number of times is equal to 3; and the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a third time.
5. The method of claim 3 , wherein regarding writing the same data, a busy duration of operations of the inner control circuit in response to the first writing command is less than a busy duration of operations of the inner control circuit in response to the second writing command, and the busy duration of operations of the inner control circuit in response to the second writing command is less than a busy duration of operations of the inner control circuit in response to the last writing command.
6. The method of claim 1 , wherein the storage capacity of a memory cell in the specific block is larger than 1 bit.
7. The method of claim 6 , further comprising:
utilizing the last writing command to control the memory cell to be in a state of a portion of a plurality of programmable states only, rather than any of the plurality of programmable states.
8. The method of claim 1 , wherein the step of checking whether the stored data matches the set of data to determine whether the specific block is a bad block comprises:
when the stored data does not match the set of data, determining the specific block as a bad block.
9. A memory device, comprising:
at least one non-volatile (NV) memory element, each comprising a plurality of blocks; and
a controller, arranged to control the NV memory element, the controller comprising a processing unit for managing the memory device according to a program code embedded in the processing unit or a program code received from outside the processing unit, wherein the controller sends a last writing command to a specific NV memory element within the NV memory element to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, wherein the first writing command, the second writing command, and the last writing command are used to write a same data into a same location in the NV memory element at different times, respectively, to ensure that the same data is stored correctly;
wherein after the set of data is written to the specific block, the controller sends a read command to the specific NV memory element to read stored data of the set of data from the specific block, and checks whether the stored data matches the set of data to determine whether the specific block is a bad block.
10. The memory device of claim 9 , wherein under the situation where a memory cell of a block of any NV memory element within the at least one NV memory is arranged to store a plurality of bits, the plurality of bits are repeatedly written to the memory cell for a predetermined number of times, to make the memory cell be correctly programmed in the specific NV memory, so that each bit of the plurality of bits is correctly stored in the memory cell for follow-up readings; and the predetermined number of times is larger than 1.
11. The memory device of claim 10 , wherein the first writing command is arranged to instruct an inner control circuit in said any NV memory element within the at least one NV memory to write the plurality of bits into the memory cell for a first time, the second writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a second time, and the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a last time.
12. The memory device of claim 11 , wherein the predetermined number of times is equal to 3; and the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a third time.
13. The memory device of claim 11 , wherein when writing the same data, a busy duration of operations of the inner control circuit in response to the first writing command is less than a busy duration of operations of the inner control circuit in response to the second writing command, and the busy duration of operations of the inner control circuit in response to the second writing command is less than a busy duration of operations of the inner control circuit in response to the last writing command.
14. The memory device of claim 9 , wherein the storage capacity of a memory cell in the specific block is larger than 1 bit.
15. The memory device of claim 14 , wherein the controller utilizes the last writing command to control the memory cell to be in a state of a portion of a plurality of programmable states only, rather than any of the plurality of programmable states.
16. A controller of a memory device, the memory device comprising at least one non-volatile (NV) memory element, each comprising
a plurality of blocks, the controller comprising:
a processing unit, arranged to manage the memory device according to a program code embedded in the processing unit or received from outside the processing unit, wherein the controller sends a last writing command to a specific NV memory element within the NV memory element to write a set of data to a specific block in the specific NV memory element, rather than sending either a first writing command or a second writing command to the specific NV memory element, wherein the first writing command, the second writing command, and the last writing command is arranged to write a same data to a same location in the NV memory element at different times, to ensure that the same data is correctly stored;
wherein after the set of data is written to the specific block, the controller sends a reading command to the specific NV memory element to read stored data of the set of data from the specific block, and checks whether the stored data matches the set of data to determine whether the specific block is a bad block.
17. The controller of claim 16 , wherein under a situation where a memory cell of a block of any NV memory element within the at least one NV memory is arranged to store a plurality of bits, the plurality of bits are repeatedly written to the memory cell for a predetermined number of times, to make the memory cell be correctly programmed in the specific NV memory, so that each bit of the plurality of bits is correctly stored in the memory cell for follow-up readings; and the predetermined number of times is larger than 1.
18. The controller of claim 17 , wherein the first writing command is arranged to instruct an inner control circuit in said any NV memory element within the at least one NV memory to write the plurality of bits into the memory cell for a first time, the second writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a second time, and the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a last time.
19. The controller of claim 18 , wherein the predetermined number of times is equal to 3; and the last writing command is arranged to instruct the inner control circuit to write the plurality of bits into the memory cell for a third time.
20. The controller of claim 18 , wherein when writing the same data, a busy duration of operations of the inner control circuit in response to the first writing command is less than a busy duration of operations of the inner control circuit in response to the second writing command, and the busy duration of operations of the inner control circuit in response to the second writing command is less than a busy duration of operations of the inner control circuit in response to the last writing command.
21. The controller of claim 16 , wherein the storage capacity of a memory cell in the specific block is larger than 1 bit.
22. The controller of claim 21 , wherein the controller utilizes the last writing command to control the memory cell to be in a state of a portion of a plurality of programmable states only, rather than any of the plurality of programmable states.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
TW104128979A | 2015-09-02 | ||
TW104128979 | 2015-09-02 | ||
TW104128979A TWI566253B (en) | 2015-09-02 | 2015-09-02 | Method for managing a memory apparatus, and associated memory apparatus thereof and associated controller thereof |
Publications (2)
Publication Number | Publication Date |
---|---|
US9570183B1 US9570183B1 (en) | 2017-02-14 |
US20170062060A1 true US20170062060A1 (en) | 2017-03-02 |
Family
ID=57964968
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/163,686 Active US9570183B1 (en) | 2015-09-02 | 2016-05-25 | Method and controller for managing memory device |
Country Status (4)
Country | Link |
---|---|
US (1) | US9570183B1 (en) |
KR (1) | KR101819014B1 (en) |
CN (2) | CN106484316B (en) |
TW (1) | TWI566253B (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108572924A (en) * | 2018-04-20 | 2018-09-25 | 华中科技大学 | A kind of request processing method of 3D MLC flashes equipment |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
TWI636363B (en) * | 2017-08-08 | 2018-09-21 | 慧榮科技股份有限公司 | Method for performing dynamic resource management in a memory device, and associated memory device and controller thereof |
KR20190032104A (en) | 2017-09-19 | 2019-03-27 | 에스케이하이닉스 주식회사 | Nonvolatile memory device, data storage device including nonvolatile memory device and operating method for the data storage device |
TWI643191B (en) * | 2017-11-13 | 2018-12-01 | 慧榮科技股份有限公司 | Method for controlling operations of memory device, associated memory device and controller thereof, and associated electronic device |
TWI660269B (en) * | 2018-01-26 | 2019-05-21 | 慧榮科技股份有限公司 | Method for performing writing management in a memory device, and associated memory device and controller thereof |
CN110162493B (en) * | 2018-02-12 | 2021-05-18 | 深圳大心电子科技有限公司 | Memory management method and memory controller using same |
TWI664527B (en) * | 2018-03-20 | 2019-07-01 | 慧榮科技股份有限公司 | Method for performing initialization in a memory device, associated memory device and controller thereof, and associated electronic device |
TWI659359B (en) * | 2018-04-27 | 2019-05-11 | 慧榮科技股份有限公司 | Method for controlling storage device |
TWI684860B (en) * | 2018-10-15 | 2020-02-11 | 慧榮科技股份有限公司 | Method for performing read acceleration, and associated data storage device and controller thereof |
TWI696113B (en) * | 2019-01-02 | 2020-06-11 | 慧榮科技股份有限公司 | Method for performing configuration management, and associated data storage device and controller thereof |
US10963385B2 (en) * | 2019-01-18 | 2021-03-30 | Silicon Motion Technology (Hong Kong) Limited | Method and apparatus for performing pipeline-based accessing management in a storage server with aid of caching metadata with cache module which is hardware pipeline module during processing object write command |
TWI696074B (en) | 2019-01-24 | 2020-06-11 | 慧榮科技股份有限公司 | Method for managing flash memory module and associated flash memory controller and electronic device |
US10884642B2 (en) * | 2019-03-27 | 2021-01-05 | Silicon Motion, Inc. | Method and apparatus for performing data-accessing management in a storage server |
Family Cites Families (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5768548A (en) * | 1992-04-15 | 1998-06-16 | Intel Corporation | Bus bridge for responding to received first write command by storing data and for responding to received second write command by transferring the stored data |
US7676562B2 (en) * | 2004-01-20 | 2010-03-09 | Microsoft Corporation | Computer system for accessing instrumentation information |
US7249229B2 (en) * | 2004-03-31 | 2007-07-24 | Gemini Mobile Technologies, Inc. | Synchronous message queues |
US7975109B2 (en) * | 2007-05-30 | 2011-07-05 | Schooner Information Technology, Inc. | System including a fine-grained memory and a less-fine-grained memory |
WO2008150927A2 (en) * | 2007-05-30 | 2008-12-11 | Schooner Information Technology | System including a fine-grained memory and a less-fine-grained memory |
KR100866626B1 (en) * | 2007-07-02 | 2008-11-03 | 삼성전자주식회사 | Nonvolatile memory device including spare array and block erasing method in the same |
KR101662827B1 (en) * | 2010-07-02 | 2016-10-06 | 삼성전자주식회사 | Memory system selecting write mode of data block and data write method thereof |
KR20120030818A (en) * | 2010-09-20 | 2012-03-29 | 삼성전자주식회사 | Non-volatile memory device and erase method thereof |
CN102456401B (en) * | 2010-10-26 | 2015-04-22 | 群联电子股份有限公司 | Block management method, memory controller and memory storage device |
KR101771619B1 (en) * | 2011-02-09 | 2017-08-28 | 삼성전자주식회사 | Nonvolatile memory device and driving method thereof |
TWI444825B (en) * | 2011-03-29 | 2014-07-11 | Phison Electronics Corp | Memory storage device, memory controller thereof, and method for programming data thereof |
CN102737716B (en) * | 2011-04-11 | 2016-11-02 | 群联电子股份有限公司 | Memorizer memory devices, Memory Controller and method for writing data |
US10803970B2 (en) * | 2011-11-14 | 2020-10-13 | Seagate Technology Llc | Solid-state disk manufacturing self test |
CN103186470B (en) * | 2011-12-30 | 2016-04-20 | 群联电子股份有限公司 | Memorizer memory devices and Memory Controller thereof and method for writing data |
KR101984796B1 (en) * | 2012-05-03 | 2019-06-03 | 에스케이하이닉스 주식회사 | Semiconductor memory device, memory system including the same and operating method thereof |
CN108595345B (en) * | 2012-07-25 | 2021-11-23 | 慧荣科技股份有限公司 | Method for managing data stored in flash memory and related memory device and controller |
CN107741913B (en) * | 2013-08-05 | 2021-09-07 | 慧荣科技股份有限公司 | Method for managing a memory device, memory device and controller |
TWI545571B (en) * | 2014-02-18 | 2016-08-11 | 慧榮科技股份有限公司 | Method for accessing flash memory and associated controller and memory device |
-
2015
- 2015-09-02 TW TW104128979A patent/TWI566253B/en active
-
2016
- 2016-05-25 CN CN201610352137.2A patent/CN106484316B/en active Active
- 2016-05-25 CN CN201910468500.0A patent/CN110335635B/en active Active
- 2016-05-25 US US15/163,686 patent/US9570183B1/en active Active
- 2016-06-27 KR KR1020160080056A patent/KR101819014B1/en active IP Right Grant
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108572924A (en) * | 2018-04-20 | 2018-09-25 | 华中科技大学 | A kind of request processing method of 3D MLC flashes equipment |
Also Published As
Publication number | Publication date |
---|---|
TW201711049A (en) | 2017-03-16 |
KR20170027654A (en) | 2017-03-10 |
CN106484316A (en) | 2017-03-08 |
TWI566253B (en) | 2017-01-11 |
CN110335635A (en) | 2019-10-15 |
CN106484316B (en) | 2019-06-28 |
CN110335635B (en) | 2021-03-02 |
KR101819014B1 (en) | 2018-01-16 |
US9570183B1 (en) | 2017-02-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9570183B1 (en) | Method and controller for managing memory device | |
US9514042B2 (en) | Method for managing memory apparatus to perform writing control according to monitored data amount of received data, associated memory apparatus thereof and associated controller thereof | |
US9703698B2 (en) | Data writing method, memory controller and memory storage apparatus | |
US9507708B2 (en) | Method for managing memory apparatus, associated memory apparatus thereof and associated controller thereof | |
CN107402716B (en) | Data writing method, memory control circuit unit and memory storage device | |
US11630768B2 (en) | Method for managing flash memory module and associated flash memory controller and electronic device | |
US9619380B2 (en) | Data writing method, memory control circuit unit and memory storage apparatus | |
US9552287B2 (en) | Data management method, memory controller and embedded memory storage apparatus using the same | |
US20190065361A1 (en) | Method for writing data into flash memory module and associated flash memory controller and electronic device | |
US10748626B2 (en) | Data storage device and operating method thereof | |
US10747660B2 (en) | Method and system for forming and using memory superblocks based on performance grades | |
US9274939B2 (en) | Memory system | |
US11049535B2 (en) | Memory device and method of operating the memory device | |
US20130132640A1 (en) | Data writing method, and memory controller and memory storage apparatus using the same | |
US10629275B2 (en) | Data storage device and operating method thereof | |
US8832358B2 (en) | Data writing method, memory controller and memory storage apparatus | |
US11487655B2 (en) | Method for managing flash memory module and associated flash memory controller and electronic device based on timing of dummy read operations | |
CN114968079A (en) | Electronic system including memory system and host | |
US20230031193A1 (en) | Memory system and operating method thereof | |
TWI523016B (en) | Method for managing a memory apparatus, and associated memory apparatus thereof and associated controller thereof | |
US11954347B2 (en) | Memory system and operating method thereof | |
US10726938B2 (en) | Data storage device and operating method thereof | |
KR20210004613A (en) | Data storage device and operating method thereof | |
US20150205715A1 (en) | Data protecting method, memory storage apparatus and memory control circuit unit |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SILICON MOTION INC., TAIWAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:YANG, TSUNG-CHIEH;REEL/FRAME:038709/0471 Effective date: 20130724 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |