US10714197B1 - Memory device and program verification method thereof - Google Patents

Memory device and program verification method thereof Download PDF

Info

Publication number
US10714197B1
US10714197B1 US16/388,300 US201916388300A US10714197B1 US 10714197 B1 US10714197 B1 US 10714197B1 US 201916388300 A US201916388300 A US 201916388300A US 10714197 B1 US10714197 B1 US 10714197B1
Authority
US
United States
Prior art keywords
read data
data
input data
redundant block
bit count
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.)
Active
Application number
US16/388,300
Inventor
Ya-Jui Lee
Kuan-Fu Chen
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Macronix International Co Ltd
Original Assignee
Macronix International Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Macronix International Co Ltd filed Critical Macronix International Co Ltd
Priority to US16/388,300 priority Critical patent/US10714197B1/en
Assigned to MACRONIX INTERNATIONAL CO., LTD. reassignment MACRONIX INTERNATIONAL CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHEN, KUAN-FU, LEE, YA-JUI
Priority to CN201910395681.9A priority patent/CN111833953B/en
Application granted granted Critical
Publication of US10714197B1 publication Critical patent/US10714197B1/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
    • G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
    • G11C29/12—Built-in arrangements for testing, e.g. built-in self testing [BIST] or interconnection details
    • 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
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1446—Point-in-time backing up or restoration of persistent data
    • G06F11/1448—Management of the data involved in backup or backup restore
    • G06F11/1451—Management of the data involved in backup or backup restore by selection of backup contents
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0602—Interfaces specially adapted for storage systems specifically adapted to achieve a particular effect
    • G06F3/0614—Improving the reliability of storage systems
    • G06F3/0619—Improving the reliability of storage systems in relation to data integrity, e.g. data losses, bit errors
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0658—Controller construction arrangements
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/0668—Interfaces specially adapted for storage systems adopting a particular infrastructure
    • G06F3/0671—In-line storage system
    • G06F3/0683—Plurality of storage devices
    • G06F3/0688—Non-volatile semiconductor memory arrays
    • 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/26—Sensing or reading circuits; Data output circuits
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
    • G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
    • G11C29/12—Built-in arrangements for testing, e.g. built-in self testing [BIST] or interconnection details
    • G11C29/18—Address generation devices; Devices for accessing memories, e.g. details of addressing circuits
    • G11C29/30—Accessing single arrays
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/56—External testing equipment for static stores, e.g. automatic test equipment [ATE]; Interfaces therefor
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/04—Detection or location of defective memory elements, e.g. cell constructio details, timing of test signals
    • G11C29/08—Functional testing, e.g. testing during refresh, power-on self testing [POST] or distributed testing
    • G11C29/12—Built-in arrangements for testing, e.g. built-in self testing [BIST] or interconnection details
    • G11C2029/1202—Word line control
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11C—STATIC STORES
    • G11C29/00—Checking stores for correct operation ; Subsequent repair; Testing stores during standby or offline operation
    • G11C29/56—External testing equipment for static stores, e.g. automatic test equipment [ATE]; Interfaces therefor
    • G11C29/56008—Error analysis, representation of errors

Definitions

  • the invention relates to a memory device and a program verification method thereof, and more particularly, relates to a memory device and a program verification method capable of verifying a word line leakage.
  • NAND flash memories face process variation and reliability challenges that impact product performance and yield, and these challenges are especially important in automotive markets with high reliability requirements.
  • various solutions have been proposed to reduce process defects such as the word line leakage.
  • certain word line leakages can be detected at wafer end.
  • P/E cycle program-erase cycle
  • a solution for the above problem is to detect the word line leakage before erasing, but writing errors may still occur since the word line leakage cannot be completely detected by such solution.
  • the invention provides a memory device and a program verification method thereof, which are capable of detecting word line defects during a write verification and quickly backing up the data of the bits with the word line defects, so as to improve quality and reliability of the memory.
  • a program verification method used by a memory device includes, but not limited to, reading a previous page to obtain first read data. Input data is written to a current page. The previous page or the current page is read to obtain second read data. At least one of the first read data and the second read data is analyzed to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory device.
  • a memory device is provided according to the embodiments of the invention.
  • the memory device includes, but not limited to, a memory array and a controller.
  • the memory array includes a plurality of pages.
  • the controller is coupled to the memory array, the controller being configured as: reading a previous page to obtain first read data; Input data is written to a current page. The previous page or the current page is read to obtain second read data. At least one of the first read data and the second read data is analyzed to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory array.
  • the memory device and the program verification method thereof can improve quality and reliability of the memory device.
  • pre-reading the previous page, and reading and analyzing at least one of the previous page and the current page after writing the current page whether to back up the data to the redundant block of the memory device or not can be determined so that the process defects can be detected in the program verification and a failure rate of the memory device can be also significantly reduced.
  • FIG. 1 is a schematic diagram illustrating a memory device according to an embodiment of the invention.
  • FIG. 2 is a schematic diagram illustrating a word line leakage according to an embodiment of the invention.
  • FIG. 3 is a flowchart illustrating a program verification method according to an embodiment of the invention.
  • FIG. 4 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 5 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 6 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 7 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 8 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 9 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 10 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 11 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • FIG. 1 is a schematic diagram illustrating a memory device according to an embodiment of the invention.
  • a memory device 100 includes a memory array 110 and a controller 120 , but not limited thereto.
  • the memory array 110 includes a plurality of pages (not illustrated).
  • the pages include, for example, a first page, a second page, . . . , an (N ⁇ 1)th page, an Nth page etc., each of which is used to store data.
  • the controller 120 is coupled to the memory array 110 , the controller 120 is configured to perform a program verification to the pages.
  • the memory array 110 further includes redundant blocks (not illustrated), and the redundant blocks can be used to store backup data.
  • FIG. 2 is a schematic diagram illustrating a word line leakage according to an embodiment of the invention.
  • a word line 210 includes an (N ⁇ 2)th word line, an (N ⁇ 1)th word line, an Nth word line and an (N+1)th word line, but not limited thereto.
  • each word line includes a control gate 220 and a floating gate 230 . It should be noted that, in the memory device, defects between the word lines may sometimes occur due to a high electric field during a write operation and cause the word line leakage. For instance, before writing the Nth word line, there is no word line leakage between the (N ⁇ 1)th word line and the Nth word line.
  • the defects occur between the floating gate 230 of the (N ⁇ 1)th word line and the floating gate of the Nth word line due to the high electric field and cause a word line leakage 240 . Consequently, errors will occur when reading data from the (N-)th word line and/or the Nth word line. Leakages also possible occur between the control gate 220 of the (N ⁇ 1)th word line and the control gate of the Nth word line.
  • FIG. 3 is a flowchart illustrating a program verification method according to an embodiment of the invention.
  • the controller pre-reads data of a previous page to obtain first read data, wherein the previous page is a previous page of a current page.
  • the controller writes input data of the current page to the current page.
  • the controller reads data of the previous page or the current page to obtain second read data.
  • the controller analyzes at least one of the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory device.
  • FIG. 4 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • the controller pre-reads data of an (N ⁇ 1)th page to obtain read data of the (N ⁇ 1)th page (i.e., the first read data).
  • the controller writes input data of the Nth page to the Nth page.
  • the controller reads the Nth page to obtain read data of the Nth page (i.e., the second read data).
  • the controller compares the read data and the input data of the Nth page to generate a failure bit count FBC.
  • the controller can include a counter (not illustrated). The controller determines whether the read data and the input data of the Nth page are equal by comparing the read data and the input data of the Nth page and uses the counter to calculate the failure bit count FBC of the Nth page. For instance, each time when the controller determines that bit data in the read data and the input data of the Nth page are different, the counter adds one to the failure bit count FBC. Each time when the controller determines that the bit data in the read data and the input data of the Nth page are identical, the failure bit count FBC remains unchanged.
  • step S 450 the controller determines whether to back up the read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device according to the failure bit count FBC.
  • the failure bit count FBC is less than or equal to a preset threshold X
  • the controller does not back up the read data of (N ⁇ 1)th page and the input data of Nth page and step S 470 is executed.
  • step S 460 is executed.
  • the preset threshold X is a preset value based on design requirements, and the invention does not limit a size of the preset threshold X.
  • step S 460 the controller backs up the read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown.
  • the present invention does not limit the device or location for showing (or outputting) the writing state.
  • step S 470 the program verification for the Nth page is ended. In this embodiment, the controller compares the input data with the read data of the Nth page to determine whether to back up the data of the (N ⁇ 1)th page and the Nth page before writing the Nth page.
  • the controller when the controller backs up at least one of the read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block, the controller turns on all word lines of the redundant block for performing a one-shot writing with determining whether to verify or not, and it will be based on the backup time which is long or short. Specifically, when backing up the data, since the first read data of the (N ⁇ 1)th page and the input data of the Nth page are preset to be correct and thus no verification is required, the controller can turn on all the word lines in the redundant block so the input data can be written to the redundant block all at once via bit lines.
  • the word lines are turned on all at once with determining whether to verify or not, and it will based on the backup time which is long or short, if no program verification, the page only needs about 20 ⁇ s extra time for backup, which can reduce program verification time overall.
  • the controller When reading the (N ⁇ 1)th page or the Nth page, the controller turns on all word lines of the redundant block for performing a one-shot reading. Specifically, when reading the data, the controller can turn on all the word lines of the redundant block so the data can be read from the bit lines of the redundant block all at once. Since the word lines are turned on all at once, the page only needs about 25 ⁇ s more time for reading. The program verification for the entire page only requires extra 60 to 80 ⁇ s time based on design requirements, so the program verification time can be reduced overall.
  • FIG. 5 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • steps S 510 to step S 550 can refer to the related description for FIG. 4 .
  • step S 560 the controller backs up the read data of the (N ⁇ 1)th page to the redundant block of the memory device, and a writing failure is shown.
  • step S 570 the program verification for the Nth page is ended. In this embodiment, the controller compares the input data with the read data of the Nth page to determine whether to back up the data of the (N ⁇ 1)th page before writing the Nth page.
  • FIG. 6 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • the controller pre-reads data of an (N ⁇ 1)th page to obtain first read data of the (N ⁇ 1)th page.
  • step S 620 the controller writes input data of the Nth page to the Nth page.
  • step S 630 the controller re-reads the (N ⁇ 1)th page to obtain second read data of the (N ⁇ 1)th page.
  • the controller compares the first read data and the second read data of the (N ⁇ 1)th page to generate a failure bit count FBC.
  • the controller can include a counter. The controller determines whether read data of the (N ⁇ 1)th page before the write operation for the Nth page (the first read data) and read data of the (N ⁇ 1)th page after the write operation for the Nth page (the second read data) are equal by comparing the first read data and the second read data of the (N ⁇ 1)th page, and uses the counter to calculate the failure bit count FBC of the (N ⁇ 1)th page. For instance, each time when the controller determines that bit data in the first read data and the second read data are different, the counter adds one to the failure bit count FBC.
  • the controller determines that the bit data in the first read data and the second read data are identical. Accordingly, when data of all bits in the first read data and the second read data are compared, the comparison for the read data of the (N ⁇ 1)th page is ended, and the failure bit count FBC of the (N ⁇ 1)th page is obtained. It is worth noting that, when the controller determines that the bit data in the first read data and the second read data are different, it means that the write operation for the Nth page already causes the defects located on the memory cells of the (N ⁇ 1)th page or between the word lines so that the read data of the (N ⁇ 1)th page is incorrect.
  • step S 650 the controller determines whether to back up the first read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device according to the failure bit count FBC.
  • the failure bit count FBC is less than or equal to a preset threshold X
  • the controller does not back up the first read data of (N ⁇ 1)th page and the input data of the Nth page and step S 670 is executed.
  • step S 660 is executed.
  • the preset threshold X is a preset value based on design requirements, and the invention does not limit a size of the preset threshold X.
  • step S 660 the controller backs up the first read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown.
  • step S 670 the program verification for the Nth page is ended. In this embodiment, the controller compares the read data of the (N ⁇ 1)th page before and after writing the Nth page to determine whether to back up the data of the (N ⁇ 1)th page and the Nth page before writing the Nth page.
  • FIG. 7 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • steps S 710 to step S 750 can refer to the related description for FIG. 6 .
  • step S 760 the controller backs up the first read data of the (N ⁇ 1)th page to the redundant block of the memory device, and a writing failure is shown.
  • step S 770 the program verification for the Nth page is ended. In this embodiment, the controller compares the read data of the (N ⁇ 1)th page before and after writing the Nth page to determine whether to back up the data of the (N ⁇ 1)th page before writing the Nth page.
  • FIG. 8 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • the controller pre-reads data of an (N ⁇ 1)th page to obtain first read data.
  • the controller writes input data of the Nth page to the Nth page.
  • the controller reads the Nth page to obtain second read data.
  • step S 840 the controller compares the second read data and the input data of the Nth page to generate a first failure bit count FBC 1 .
  • the controller can include a counter. The controller determines whether the read data and the input data of the Nth page are equal by comparing the read data and the input data of the Nth page and uses the counter to calculate the first failure bit count FBC 1 of the Nth page. For instance, each time when the controller determines that bit data in the second read data and the input data of the Nth page are different, the counter adds one to the first failure bit count FBC 1 . Each time when the controller determines that the bit data in the second read data and the input data of the Nth page are identical, the first failure bit count FBC 1 remains unchanged.
  • step S 850 the controller determines whether to back up the read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device according to the first failure bit count FBC 1 .
  • step S 890 is executed.
  • step S 860 is executed.
  • the first preset threshold X 1 is a preset value based on design requirements, and the invention does not limit a size of the first preset threshold X 1 .
  • step S 860 the controller re-reads the (N ⁇ 1)th page to obtain third read data.
  • step S 870 the controller compares the first read data and the third read data to generate a second failure bit count FBC 2 .
  • the controller can include a counter. The controller determines whether read data of the (N ⁇ 1)th page before the write operation for the Nth page (the first read data) and read data of the (N ⁇ 1)th page after the write operation for the Nth page (the third read data) are equal by comparing the first read data and the third read data, and uses the counter to calculate the second failure bit count FBC 2 .
  • the counter adds one to the second failure bit count FBC 2 .
  • the second failure bit count FBC 2 remains unchanged. Accordingly, when data of all bits in the first read data and the third read data are compared, the comparison for the read data of the (N ⁇ 1)th page is ended, and the second failure bit count FBC 2 is obtained.
  • the controller determines that the bit data in the first read data and the third data are different, it means that the write operation for the Nth page already causes the defects located on the memory cells of the (N ⁇ 1)th page or between the word lines so that the read data of the (N ⁇ 1)th page is incorrect.
  • step S 880 the controller determines whether to back up the first read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device according to the second failure bit count FBC 2 .
  • the controller does not back up the first read data of the (N ⁇ 1)th page and the input data of the Nth page and step S 895 is executed.
  • step S 890 is executed.
  • the second preset threshold X 2 is a preset value based on design requirements, and the invention does not limit a size of the second preset threshold X 2 .
  • step S 890 the controller backs up the first read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown.
  • step S 895 the program verification for the Nth page is ended.
  • the controller first compares the input data with the read data of the Nth page and then compares the read data of the (N ⁇ 1)th page before and after writing the Nth page to determine whether to back up the data of the (N ⁇ 1)th page and the Nth page before writing the Nth page.
  • FIG. 9 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • the controller pre-reads data of an (N ⁇ 1)th page to obtain first read data of the (N ⁇ 1)th page.
  • step S 920 the controller writes input data of the Nth page to the Nth page.
  • step S 930 the controller re-reads the (N ⁇ 1)th page to obtain second read data of the (N ⁇ 1)th page.
  • step S 940 the controller compares the first read data and the second read data of the (N ⁇ 1)th page to generate a first failure bit count FBC 1 .
  • the controller can include a counter. The controller determines whether read data of the (N ⁇ 1)th page before the write operation for the Nth page (the first read data) and read data of the (N ⁇ 1)th page after the write operation for the Nth page (the second read data) are equal by comparing the first read data and the second read data of the (N ⁇ 1)th page, and uses the counter to calculate the first failure bit count FBC 1 of the (N ⁇ 1)th page.
  • the counter adds one to the first failure bit count FBC 1 .
  • the first failure bit count FBC 1 remains unchanged. Accordingly, when data of all bits in the first read data and the second read data are compared, the comparison for the read data of the (N ⁇ 1)th page is ended, and the first failure bit count FBC 1 of the (N ⁇ 1)th page is obtained.
  • the controller determines that the bit data in the first read data and the second read data are different, it means that the write operation for the Nth page already causes the defects located on the memory cells of the (N ⁇ 1)th page or between the word lines so that the read data of the (N ⁇ 1)th page is incorrect.
  • step S 950 the controller determines whether to back up the first read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device according to the first failure bit count FBC 1 .
  • step S 960 is executed.
  • step S 990 is executed.
  • the first preset threshold X 1 is a preset value based on design requirements, and the invention does not limit a size of the first preset threshold X 1 .
  • step S 960 the controller re-reads the Nth page to obtain third read data.
  • step S 970 the controller compares the third read data and the input data of the Nth page to generate a second failure bit count FBC 2 .
  • the controller can include a counter. The controller determines whether the third read data and the input data of the Nth page are equal by comparing the third read data and the input data of the Nth page and uses the counter to calculate the second failure bit count FBC 2 of the Nth page. For instance, each time when the controller determines that bit data in the third read data and the input data of the Nth page are different, the counter adds one to the second failure bit count FBC 2 .
  • the controller determines that the bit data in the third read data and the input data of the Nth page are identical. Accordingly, when data of all bits in the third read data and the input data of the Nth page are compared, a verification for the read data of the Nth page is ended and the second failure bit count FBC 2 is obtained. It should be noted that, when the controller determines that the bit data in the third read data and the input data of the Nth page are different, it means that a write operation for the Nth page already causes the defects located on the memory cells of the Nth page or between the word lines so that the read data of the Nth page is incorrect.
  • step S 980 the controller determines whether to back up the first read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device according to the second failure bit count FBC 2 .
  • the controller does not back up the first read data of (N ⁇ 1)th page and the input data of the Nth page and step S 995 is executed.
  • step S 990 is executed.
  • the second preset threshold X 2 is a preset value based on design requirements, and the invention does not limit a size of the second preset threshold X 2 .
  • step S 990 the controller backs up the first read data of the (N ⁇ 1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown.
  • step S 995 the program verification for the Nth page is ended.
  • the controller first compares the read data of the (N ⁇ 1)th page before and after writing the Nth page and then compares the input data with the read data of the Nth page to determine whether to back up the data of the (N ⁇ 1)th page and the Nth page before writing the Nth page.
  • FIG. 10 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • steps S 1010 to step S 1080 can refer to the related description for FIG. 8 .
  • step S 1090 the controller backs up the first read data of the (N ⁇ 1)th page to the redundant block of the memory device, and a writing failure is shown.
  • step S 1095 the program verification for the Nth page is ended.
  • the controller first compares the input data with the read data of the Nth page and then compares the read data of the (N ⁇ 1)th page before and after writing the Nth page to determine whether to back up the data of the (N ⁇ 1)th page before writing the Nth page.
  • FIG. 11 is a flowchart illustrating a program verification method according to another embodiment of the invention.
  • steps S 1110 to step S 1180 can refer to the related description for FIG. 9 .
  • step S 1190 the controller backs up the first read data of the (N ⁇ 1)th page to the redundant block of the memory device, and a writing failure is shown.
  • step S 1195 the program verification for the Nth page is ended.
  • the controller first compares the read data of the (N ⁇ 1)th page before and after writing the Nth page and then compares the input data with the read data of the Nth page to determine whether to back up the data of the (N ⁇ 1)th page before writing the Nth page.
  • the memory device and the program verification method thereof can improve quality and reliability of the memory device.
  • pre-reading the previous page before writing the current page and reading and analyzing at least one of the previous page and the current page after writing the current page, whether to back up the data to the redundant block of the memory device can be determined so that the process defects can be detected in the program verification. It leads to a significant reduction of failure rate of the memory device.
  • the one-shot writing and backup for the redundant block can reduce the program verification time overall.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Read Only Memory (AREA)
  • For Increasing The Reliability Of Semiconductor Memories (AREA)

Abstract

A memory device and a program verification method thereof are provided. The write verification method includes: reading a previous page to obtain first read data, writing input data to a current page, reading the previous page or the current page to obtain second read data, and analyzing at least one of the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory device.

Description

BACKGROUND OF THE INVENTION 1. Field of the Invention
The invention relates to a memory device and a program verification method thereof, and more particularly, relates to a memory device and a program verification method capable of verifying a word line leakage.
2. Description of Related Art
As process nodes evolve, NAND flash memories face process variation and reliability challenges that impact product performance and yield, and these challenges are especially important in automotive markets with high reliability requirements. In device level size, various solutions have been proposed to reduce process defects such as the word line leakage. Among those solutions, certain word line leakages can be detected at wafer end. However, since a long time high electric field during write and erase processes can lead to the defects, some word line leakages only appear after a program-erase cycle (P/E cycle) and cannot be detected at the wafer end. A solution for the above problem is to detect the word line leakage before erasing, but writing errors may still occur since the word line leakage cannot be completely detected by such solution.
SUMMARY OF THE INVENTION
The invention provides a memory device and a program verification method thereof, which are capable of detecting word line defects during a write verification and quickly backing up the data of the bits with the word line defects, so as to improve quality and reliability of the memory.
A program verification method used by a memory device is provided according to the embodiments of the invention. The program verification method includes, but not limited to, reading a previous page to obtain first read data. Input data is written to a current page. The previous page or the current page is read to obtain second read data. At least one of the first read data and the second read data is analyzed to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory device.
A memory device is provided according to the embodiments of the invention. The memory device includes, but not limited to, a memory array and a controller. The memory array includes a plurality of pages. The controller is coupled to the memory array, the controller being configured as: reading a previous page to obtain first read data; Input data is written to a current page. The previous page or the current page is read to obtain second read data. At least one of the first read data and the second read data is analyzed to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory array.
Based on the above, according to the embodiments of the invention, the memory device and the program verification method thereof can improve quality and reliability of the memory device. By pre-reading the previous page, and reading and analyzing at least one of the previous page and the current page after writing the current page, whether to back up the data to the redundant block of the memory device or not can be determined so that the process defects can be detected in the program verification and a failure rate of the memory device can be also significantly reduced.
To make the above features and advantages of the disclosure more comprehensible, several embodiments accompanied with drawings are described in detail as follows.
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.
FIG. 1 is a schematic diagram illustrating a memory device according to an embodiment of the invention.
FIG. 2 is a schematic diagram illustrating a word line leakage according to an embodiment of the invention.
FIG. 3 is a flowchart illustrating a program verification method according to an embodiment of the invention.
FIG. 4 is a flowchart illustrating a program verification method according to another embodiment of the invention.
FIG. 5 is a flowchart illustrating a program verification method according to another embodiment of the invention.
FIG. 6 is a flowchart illustrating a program verification method according to another embodiment of the invention.
FIG. 7 is a flowchart illustrating a program verification method according to another embodiment of the invention.
FIG. 8 is a flowchart illustrating a program verification method according to another embodiment of the invention.
FIG. 9 is a flowchart illustrating a program verification method according to another embodiment of the invention.
FIG. 10 is a flowchart illustrating a program verification method according to another embodiment of the invention.
FIG. 11 is a flowchart illustrating a program verification method according to another embodiment of the invention.
 DESCRIPTION OF THE EMBODIMENTS
Reference will now be made in detail to the present preferred embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers are used in the drawings and the description to refer to the same or like parts.
FIG. 1 is a schematic diagram illustrating a memory device according to an embodiment of the invention. With reference to FIG. 1, a memory device 100 includes a memory array 110 and a controller 120, but not limited thereto. In an embodiment of the present disclosure, the memory array 110 includes a plurality of pages (not illustrated). The pages include, for example, a first page, a second page, . . . , an (N−1)th page, an Nth page etc., each of which is used to store data. However, the invention does not limit the architecture of the memory array. The controller 120 is coupled to the memory array 110, the controller 120 is configured to perform a program verification to the pages. In an embodiment, the memory array 110 further includes redundant blocks (not illustrated), and the redundant blocks can be used to store backup data.
FIG. 2 is a schematic diagram illustrating a word line leakage according to an embodiment of the invention. With reference to FIG. 2, a word line 210 includes an (N−2)th word line, an (N−1)th word line, an Nth word line and an (N+1)th word line, but not limited thereto. Here, each word line includes a control gate 220 and a floating gate 230. It should be noted that, in the memory device, defects between the word lines may sometimes occur due to a high electric field during a write operation and cause the word line leakage. For instance, before writing the Nth word line, there is no word line leakage between the (N−1)th word line and the Nth word line. After writing the Nth word line, the defects occur between the floating gate 230 of the (N−1)th word line and the floating gate of the Nth word line due to the high electric field and cause a word line leakage 240. Consequently, errors will occur when reading data from the (N-)th word line and/or the Nth word line. Leakages also possible occur between the control gate 220 of the (N−1)th word line and the control gate of the Nth word line.
FIG. 3 is a flowchart illustrating a program verification method according to an embodiment of the invention. With reference to FIG. 3, in step S310, the controller pre-reads data of a previous page to obtain first read data, wherein the previous page is a previous page of a current page. Next, in step S320, the controller writes input data of the current page to the current page. After writing the current page, in step S330, the controller reads data of the previous page or the current page to obtain second read data. Next, in step S340, the controller analyzes at least one of the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory device.
FIG. 4 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 4, before writing an Nth page, in step S410, the controller pre-reads data of an (N−1)th page to obtain read data of the (N−1)th page (i.e., the first read data). Next, in step S420, the controller writes input data of the Nth page to the Nth page. After writing the Nth page, in step S430, the controller reads the Nth page to obtain read data of the Nth page (i.e., the second read data).
In step S440, the controller compares the read data and the input data of the Nth page to generate a failure bit count FBC. Specifically, in an embodiment, the controller can include a counter (not illustrated). The controller determines whether the read data and the input data of the Nth page are equal by comparing the read data and the input data of the Nth page and uses the counter to calculate the failure bit count FBC of the Nth page. For instance, each time when the controller determines that bit data in the read data and the input data of the Nth page are different, the counter adds one to the failure bit count FBC. Each time when the controller determines that the bit data in the read data and the input data of the Nth page are identical, the failure bit count FBC remains unchanged. Accordingly, when data of all bits in the read data and the input data of the Nth page are compared, a verification for the read data of the Nth page is ended and the failure bit count FBC of the Nth page is obtained. It is worth noting that, when the controller determines that the bit data in the read data and the input data of the Nth page are different, it means that a write operation for the Nth page already causes the defects located on the memory cells of the Nth page or between the word lines so that the read data of the Nth page is incorrect.
In step S450, the controller determines whether to back up the read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device according to the failure bit count FBC. When the failure bit count FBC is less than or equal to a preset threshold X, the controller does not back up the read data of (N−1)th page and the input data of Nth page and step S470 is executed. When the failure bit count FBC is greater than the preset threshold X, step S460 is executed. Here, the preset threshold X is a preset value based on design requirements, and the invention does not limit a size of the preset threshold X. In step S460, the controller backs up the read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown. The present invention does not limit the device or location for showing (or outputting) the writing state. Next, in step S470, the program verification for the Nth page is ended. In this embodiment, the controller compares the input data with the read data of the Nth page to determine whether to back up the data of the (N−1)th page and the Nth page before writing the Nth page.
It should be noted that, when the controller backs up at least one of the read data of the (N−1)th page and the input data of the Nth page to the redundant block, the controller turns on all word lines of the redundant block for performing a one-shot writing with determining whether to verify or not, and it will be based on the backup time which is long or short. Specifically, when backing up the data, since the first read data of the (N−1)th page and the input data of the Nth page are preset to be correct and thus no verification is required, the controller can turn on all the word lines in the redundant block so the input data can be written to the redundant block all at once via bit lines. Accordingly, because the word lines are turned on all at once with determining whether to verify or not, and it will based on the backup time which is long or short, if no program verification, the page only needs about 20 μs extra time for backup, which can reduce program verification time overall.
When reading the (N−1)th page or the Nth page, the controller turns on all word lines of the redundant block for performing a one-shot reading. Specifically, when reading the data, the controller can turn on all the word lines of the redundant block so the data can be read from the bit lines of the redundant block all at once. Since the word lines are turned on all at once, the page only needs about 25 μs more time for reading. The program verification for the entire page only requires extra 60 to 80 μs time based on design requirements, so the program verification time can be reduced overall.
FIG. 5 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 5, steps S510 to step S550 can refer to the related description for FIG. 4. In step S560, the controller backs up the read data of the (N−1)th page to the redundant block of the memory device, and a writing failure is shown. Next, in step S570, the program verification for the Nth page is ended. In this embodiment, the controller compares the input data with the read data of the Nth page to determine whether to back up the data of the (N−1)th page before writing the Nth page.
FIG. 6 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 6, before writing an Nth page, in step S610, the controller pre-reads data of an (N−1)th page to obtain first read data of the (N−1)th page. Next, in step S620, the controller writes input data of the Nth page to the Nth page. After writing the Nth page, in step S630, the controller re-reads the (N−1)th page to obtain second read data of the (N−1)th page.
In step S640, the controller compares the first read data and the second read data of the (N−1)th page to generate a failure bit count FBC. Specifically, in an embodiment, the controller can include a counter. The controller determines whether read data of the (N−1)th page before the write operation for the Nth page (the first read data) and read data of the (N−1)th page after the write operation for the Nth page (the second read data) are equal by comparing the first read data and the second read data of the (N−1)th page, and uses the counter to calculate the failure bit count FBC of the (N−1)th page. For instance, each time when the controller determines that bit data in the first read data and the second read data are different, the counter adds one to the failure bit count FBC. Each time when the controller determines that the bit data in the first read data and the second read data are identical, the failure bit count FBC remains unchanged. Accordingly, when data of all bits in the first read data and the second read data are compared, the comparison for the read data of the (N−1)th page is ended, and the failure bit count FBC of the (N−1)th page is obtained. It is worth noting that, when the controller determines that the bit data in the first read data and the second read data are different, it means that the write operation for the Nth page already causes the defects located on the memory cells of the (N−1)th page or between the word lines so that the read data of the (N−1)th page is incorrect.
In step S650, the controller determines whether to back up the first read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device according to the failure bit count FBC. When the failure bit count FBC is less than or equal to a preset threshold X, the controller does not back up the first read data of (N−1)th page and the input data of the Nth page and step S670 is executed. When the failure bit count FBC is greater than the preset threshold X, step S660 is executed. Here, the preset threshold X is a preset value based on design requirements, and the invention does not limit a size of the preset threshold X. In step S660, the controller backs up the first read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown. Next, in step S670, the program verification for the Nth page is ended. In this embodiment, the controller compares the read data of the (N−1)th page before and after writing the Nth page to determine whether to back up the data of the (N−1)th page and the Nth page before writing the Nth page.
FIG. 7 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 7, steps S710 to step S750 can refer to the related description for FIG. 6. In step S760, the controller backs up the first read data of the (N−1)th page to the redundant block of the memory device, and a writing failure is shown. Next, in step S770, the program verification for the Nth page is ended. In this embodiment, the controller compares the read data of the (N−1)th page before and after writing the Nth page to determine whether to back up the data of the (N−1)th page before writing the Nth page.
FIG. 8 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 8, before writing an Nth page, in step S810, the controller pre-reads data of an (N−1)th page to obtain first read data. Next, in step S820, the controller writes input data of the Nth page to the Nth page. After writing the Nth page, in step S830, the controller reads the Nth page to obtain second read data.
In step S840, the controller compares the second read data and the input data of the Nth page to generate a first failure bit count FBC1. Specifically, in an embodiment, the controller can include a counter. The controller determines whether the read data and the input data of the Nth page are equal by comparing the read data and the input data of the Nth page and uses the counter to calculate the first failure bit count FBC1 of the Nth page. For instance, each time when the controller determines that bit data in the second read data and the input data of the Nth page are different, the counter adds one to the first failure bit count FBC1. Each time when the controller determines that the bit data in the second read data and the input data of the Nth page are identical, the first failure bit count FBC1 remains unchanged. Accordingly, when data of all bits in the second read data and the input data of the Nth page are compared, a verification for the read data of the Nth page is ended and the first failure bit count FBC1 is obtained. It should be noted that, when the controller determines that the bit data in the second read data and the input data of the Nth page are different, it means that a write operation for the Nth page already causes the defects located on the memory cells of the Nth page or between the word lines so that the read data of the Nth page is incorrect.
In step S850, the controller determines whether to back up the read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device according to the first failure bit count FBC1. When the first failure bit count FBC1 is greater than a first preset threshold X1, step S890 is executed. When the first failure bit count FBC1 is less than or equal to the first preset threshold X1, step S860 is executed. Here, the first preset threshold X1 is a preset value based on design requirements, and the invention does not limit a size of the first preset threshold X1.
In step S860, the controller re-reads the (N−1)th page to obtain third read data. Next, in step S870, the controller compares the first read data and the third read data to generate a second failure bit count FBC2. Specifically, in an embodiment, the controller can include a counter. The controller determines whether read data of the (N−1)th page before the write operation for the Nth page (the first read data) and read data of the (N−1)th page after the write operation for the Nth page (the third read data) are equal by comparing the first read data and the third read data, and uses the counter to calculate the second failure bit count FBC2. For instance, each time when the controller determines that bit data in the first read data and the third read data are different, the counter adds one to the second failure bit count FBC2. Each time when the controller determines that the bit data in the first read data and the third read data are identical, the second failure bit count FBC2 remains unchanged. Accordingly, when data of all bits in the first read data and the third read data are compared, the comparison for the read data of the (N−1)th page is ended, and the second failure bit count FBC2 is obtained. It is worth noting that, when the controller determines that the bit data in the first read data and the third data are different, it means that the write operation for the Nth page already causes the defects located on the memory cells of the (N−1)th page or between the word lines so that the read data of the (N−1)th page is incorrect.
In step S880, the controller determines whether to back up the first read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device according to the second failure bit count FBC2. When the second failure bit count FBC2 is less than or equal to a second preset threshold X2, the controller does not back up the first read data of the (N−1)th page and the input data of the Nth page and step S895 is executed. When the second failure bit count FBC2 is greater than the second preset threshold X2, step S890 is executed. Here, the second preset threshold X2 is a preset value based on design requirements, and the invention does not limit a size of the second preset threshold X2. In step S890, the controller backs up the first read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown. Next, in step S895, the program verification for the Nth page is ended. In this embodiment, the controller first compares the input data with the read data of the Nth page and then compares the read data of the (N−1)th page before and after writing the Nth page to determine whether to back up the data of the (N−1)th page and the Nth page before writing the Nth page.
FIG. 9 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 9, before writing an Nth page, in step S910, the controller pre-reads data of an (N−1)th page to obtain first read data of the (N−1)th page. Next, in step S920, the controller writes input data of the Nth page to the Nth page. After writing the Nth page, in step S930, the controller re-reads the (N−1)th page to obtain second read data of the (N−1)th page.
In step S940, the controller compares the first read data and the second read data of the (N−1)th page to generate a first failure bit count FBC1. Specifically, in an embodiment, the controller can include a counter. The controller determines whether read data of the (N−1)th page before the write operation for the Nth page (the first read data) and read data of the (N−1)th page after the write operation for the Nth page (the second read data) are equal by comparing the first read data and the second read data of the (N−1)th page, and uses the counter to calculate the first failure bit count FBC1 of the (N−1)th page. For instance, each time when the controller determines that bit data in the first read data and the second read data are different, the counter adds one to the first failure bit count FBC1. Each time when the controller determines that the bit data in the first read data and the second read data are identical, the first failure bit count FBC1 remains unchanged. Accordingly, when data of all bits in the first read data and the second read data are compared, the comparison for the read data of the (N−1)th page is ended, and the first failure bit count FBC1 of the (N−1)th page is obtained. It is worth noting that, when the controller determines that the bit data in the first read data and the second read data are different, it means that the write operation for the Nth page already causes the defects located on the memory cells of the (N−1)th page or between the word lines so that the read data of the (N−1)th page is incorrect.
In step S950, the controller determines whether to back up the first read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device according to the first failure bit count FBC1. When the first failure bit count FBC1 is less than or equal to a preset threshold X1, step S960 is executed. When the first failure bit count FBC1 is greater than the preset threshold X1, step S990 is executed. Here, the first preset threshold X1 is a preset value based on design requirements, and the invention does not limit a size of the first preset threshold X1.
In step S960, the controller re-reads the Nth page to obtain third read data. Next, in step S970, the controller compares the third read data and the input data of the Nth page to generate a second failure bit count FBC2. Specifically, in an embodiment, the controller can include a counter. The controller determines whether the third read data and the input data of the Nth page are equal by comparing the third read data and the input data of the Nth page and uses the counter to calculate the second failure bit count FBC2 of the Nth page. For instance, each time when the controller determines that bit data in the third read data and the input data of the Nth page are different, the counter adds one to the second failure bit count FBC2. Each time when the controller determines that the bit data in the third read data and the input data of the Nth page are identical, the second failure bit count FBC2 remains unchanged. Accordingly, when data of all bits in the third read data and the input data of the Nth page are compared, a verification for the read data of the Nth page is ended and the second failure bit count FBC2 is obtained. It should be noted that, when the controller determines that the bit data in the third read data and the input data of the Nth page are different, it means that a write operation for the Nth page already causes the defects located on the memory cells of the Nth page or between the word lines so that the read data of the Nth page is incorrect.
In step S980, the controller determines whether to back up the first read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device according to the second failure bit count FBC2. When the second failure bit count FBC2 is less than or equal to a second preset threshold X2, the controller does not back up the first read data of (N−1)th page and the input data of the Nth page and step S995 is executed. When the second failure bit count FBC2 is greater than the second preset threshold X2, step S990 is executed. Here, the second preset threshold X2 is a preset value based on design requirements, and the invention does not limit a size of the second preset threshold X2. In step S990, the controller backs up the first read data of the (N−1)th page and the input data of the Nth page to the redundant block of the memory device, and a writing success is shown. Next, in step S995, the program verification for the Nth page is ended. In this embodiment, the controller first compares the read data of the (N−1)th page before and after writing the Nth page and then compares the input data with the read data of the Nth page to determine whether to back up the data of the (N−1)th page and the Nth page before writing the Nth page.
FIG. 10 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 10, steps S1010 to step S1080 can refer to the related description for FIG. 8. In step S1090, the controller backs up the first read data of the (N−1)th page to the redundant block of the memory device, and a writing failure is shown. Next, in step S1095, the program verification for the Nth page is ended. In this embodiment, the controller first compares the input data with the read data of the Nth page and then compares the read data of the (N−1)th page before and after writing the Nth page to determine whether to back up the data of the (N−1)th page before writing the Nth page.
FIG. 11 is a flowchart illustrating a program verification method according to another embodiment of the invention. With reference to FIG. 11, steps S1110 to step S1180 can refer to the related description for FIG. 9. In step S1190, the controller backs up the first read data of the (N−1)th page to the redundant block of the memory device, and a writing failure is shown. Next, in step S1195, the program verification for the Nth page is ended. In this embodiment, the controller first compares the read data of the (N−1)th page before and after writing the Nth page and then compares the input data with the read data of the Nth page to determine whether to back up the data of the (N−1)th page before writing the Nth page.
In summary, according to the embodiments of the invention, the memory device and the program verification method thereof can improve quality and reliability of the memory device. By pre-reading the previous page before writing the current page, and reading and analyzing at least one of the previous page and the current page after writing the current page, whether to back up the data to the redundant block of the memory device can be determined so that the process defects can be detected in the program verification. It leads to a significant reduction of failure rate of the memory device. Moreover, the one-shot writing and backup for the redundant block can reduce the program verification time overall.
It will be apparent to those skilled in the art that various modifications and variations can be made to the structure of the present invention without departing from the scope or spirit of the invention. In view of the foregoing, it is intended that the present invention cover modifications and variations of this invention provided they fall within the scope of the following claims and their equivalents.

Claims (18)

What is claimed is:
1. A program verification method adapted for a memory device, the program verification method comprising:
reading a previous page to obtain a first read data;
writing input data to a current page;
reading the previous page or the current page to obtain a second read data; and
analyzing at least one of the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory device.
2. The program verification method according to claim 1, further comprising:
analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block,
wherein the step of analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block comprises:
comparing the second read data and the input data to generate a failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count.
3. The program verification method according to claim 2, wherein the step of determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count comprises:
when the failure bit count is greater than the preset threshold, backing up at least one of the first read data and the input data to the redundant block.
4. The program verification method according to claim 1, further comprising:
analyzing the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block,
wherein the step of analyzing the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block comprises:
comparing the first read data and the second read data to obtain a failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count.
5. The program verification method according to claim 4, wherein the step of determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count comprises:
when the failure bit count is greater than the preset threshold, backing up at least one of the first read data and the input data to the redundant block.
6. The program verification method according to claim 1, further comprising:
reading the current page to obtain the second read data; and
analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block,
wherein the step of analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block comprises:
comparing the second read data and the input data to obtain a first failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the first failure bit count,
when the first failure bit count is greater than a first preset threshold, backing up at least one of the first read data and the input data to the redundant block; and
when the first failure bit count is less than or equal to the first preset threshold,
reading the previous page to obtain third read data;
comparing the first read data and the third read data to obtain a second failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the second failure bit count.
7. The program verification method according to claim 6, wherein the step of determining whether to back up at least one of the first read data and the input data to the redundant block according to the second failure bit count comprises:
when the second failure bit count is greater than a second preset threshold, backing up at least one of the first read data and the input data to the redundant block.
8. The program verification method according to claim 1, further comprising:
reading the previous page to obtain the second read data; and
analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block,
wherein the step of analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block comprises:
comparing the first read data and the second read data to obtain a first failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the first failure bit count,
when the first failure bit count is greater than a first preset threshold, backing up at least one of the first read data and the input data to the redundant block; and
when the first failure bit count is less than or equal to the first preset threshold,
reading the current page to obtain third read data;
comparing the third read data and the input data to obtain a second failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the second failure bit count.
9. The program verification method according to claim 8, wherein the step of determining whether to back up at least one of the first read data and the input data to the redundant block according to the second failure bit count comprises:
when the second failure bit count is greater than a second preset threshold, backing up at least one of the first read data and the input data to the redundant block.
10. The program verification method according to claim 8, wherein the step of determining whether to back up at least one of the first read data and the input data to the redundant block according to the second failure bit count comprises:
when the second failure bit count is greater than a second preset threshold, backing up at least one of the first read data and the input data to the redundant block.
11. The program verification method according to claim 1, wherein when backing up at least one of the first read data and the input data to the redundant block, all word lines of the redundant block are turned on for performing a one-shot writing with determining whether to verify or not.
12. A memory device, comprising:
a memory array, comprising a plurality of pages; and
a controller, coupled to the memory array, the controller being configured as:
reading a previous page to obtain a first read data;
writing input data to a current page;
reading at least one of the previous page and the current page to obtain a second read data; and
analyzing at least one of the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to a redundant block of the memory array.
13. The memory device according to claim 12, wherein the controller being further configured:
analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block,
wherein the step of analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block comprises:
comparing the second read data and the input data to generate a failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count.
14. The memory device according to claim 13, wherein the step of determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count comprises:
when the failure bit count is greater than the preset threshold, backing up at least one of the first read data and the input data to the redundant block.
15. The memory device according to claim 12, wherein the controller being further configured:
analyzing the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block,
wherein the step of analyzing the first read data and the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block comprises:
comparing the first read data and the second read data to obtain a failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count.
16. The memory device according to claim 15, wherein the step of determining whether to back up at least one of the first read data and the input data to the redundant block according to the failure bit count comprises:
when the failure bit count is greater than the preset threshold, backing up at least one of the first read data and the input data to the redundant block.
17. The memory device according to claim 12, wherein the controller being further configured:
reading the current page to obtain the second read data; and
analyzing the second read data determine whether to back up at least one of the first read data and the input data to the redundant block,
wherein the step of analyzing the second read data to determine whether to back up at least one of the first read data and the input data to the redundant block comprises:
comparing the second read data and the input data to obtain a first failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the first failure bit count,
when the first failure bit count is greater than a first preset threshold, backing up at least one of the first read data and the input data to the redundant block; and
when the first failure bit count is less than or equal to the first preset threshold,
reading the previous page to obtain third read data;
comparing the first read data and the third read data to obtain a second failure bit count; and
determining whether to back up at least one of the first read data and the input data to the redundant block according to the second failure bit count.
18. The memory device according to claim 11, wherein when backing up at least one of the first read data and the input data to the redundant block, the controller is further configured to turn on all word lines of the redundant block for performing a one-shot writing with determining whether to verify or not.
US16/388,300 2019-04-18 2019-04-18 Memory device and program verification method thereof Active US10714197B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/388,300 US10714197B1 (en) 2019-04-18 2019-04-18 Memory device and program verification method thereof
CN201910395681.9A CN111833953B (en) 2019-04-18 2019-05-13 memory device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US16/388,300 US10714197B1 (en) 2019-04-18 2019-04-18 Memory device and program verification method thereof

Publications (1)

Publication Number Publication Date
US10714197B1 true US10714197B1 (en) 2020-07-14

Family

ID=71519859

Family Applications (1)

Application Number Title Priority Date Filing Date
US16/388,300 Active US10714197B1 (en) 2019-04-18 2019-04-18 Memory device and program verification method thereof

Country Status (2)

Country Link
US (1) US10714197B1 (en)
CN (1) CN111833953B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI775638B (en) * 2021-08-26 2022-08-21 力晶積成電子製造股份有限公司 Failure bit count circuit for memory and method thereof

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113918091B (en) * 2021-09-13 2022-06-07 北京得瑞领新科技有限公司 Control method and device for physical block in NAND flash memory and SSD (solid State disk) equipment

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170278580A1 (en) * 2016-03-23 2017-09-28 Samsung Electronics Co., Ltd. Nonvolatile memory device including page buffer and method for verifying program operation thereof

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100394574B1 (en) * 2001-04-10 2003-08-14 삼성전자주식회사 non-volatile semiconductor memory device having word line defect check circuit
CN1225742C (en) * 2002-04-08 2005-11-02 南亚科技股份有限公司 A Method for Quickly Discriminating Defect Types of Character Lines
CN101281786B (en) * 2008-05-08 2010-08-18 钰创科技股份有限公司 A method and related device for detecting word line damage in memory array
TWI406290B (en) * 2009-06-26 2013-08-21 Etron Technology Inc Word line defect detecting device and method thereof
CN101882471A (en) * 2010-06-08 2010-11-10 钰创科技股份有限公司 Device and method for detecting word line defects
CN102760496A (en) * 2011-04-26 2012-10-31 宜扬科技股份有限公司 Word line leakage detection method, system and storage medium of inverse OR type flash memory device
TWI422844B (en) * 2011-07-06 2014-01-11 Etron Technology Inc Method for detecting connection defects of memory and memory capable of detecting connection defects
US9823880B1 (en) * 2016-09-30 2017-11-21 Intel Corporation Method and apparatus for initiating pre-read operation before completion of data load operation

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170278580A1 (en) * 2016-03-23 2017-09-28 Samsung Electronics Co., Ltd. Nonvolatile memory device including page buffer and method for verifying program operation thereof

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI775638B (en) * 2021-08-26 2022-08-21 力晶積成電子製造股份有限公司 Failure bit count circuit for memory and method thereof
US11513880B1 (en) 2021-08-26 2022-11-29 Powerchip Semiconductor Manufacturing Corporation Failure bit count circuit for memory and method thereof

Also Published As

Publication number Publication date
CN111833953A (en) 2020-10-27
CN111833953B (en) 2022-04-19

Similar Documents

Publication Publication Date Title
US8595593B2 (en) Nonvolatile memory device having a copy back operation and method of operating the same
JP4901348B2 (en) Semiconductor memory device and control method thereof
US8214725B2 (en) Memory access system
CN106158033B (en) memory circuit and operation method thereof
US20080158989A1 (en) Retention margin program verification
US8717813B2 (en) Method and apparatus for leakage suppression in flash memory in response to external commands
US10395753B2 (en) Semiconductor memory device and programming method thereof
TW201501124A (en) Data reading method, and control circuit, and memory storage apparatus using the same
US11183256B2 (en) Semiconductor memory device and memory state detecting method
US20160012916A1 (en) Semiconductor memory device and memory system
JP2005056394A (en) Storage device and memory card
US10714197B1 (en) Memory device and program verification method thereof
US8713406B2 (en) Erasing a non-volatile memory (NVM) system having error correction code (ECC)
JP6115740B1 (en) Semiconductor memory device
US20080158990A1 (en) Retention margin program verification
US9786381B2 (en) Semiconductor memory device that determines a deterioration level of memory cells and an operation method thereof
TWI386939B (en) Retention margin program verification
CN109215716B (en) Method and device for improving reliability of NAND type floating gate memory
US8923068B2 (en) Low margin read operation with CRC comparision
JPH05314783A (en) Erasure method for nonvolatile semiconductor memory provided with erasure function and writing device
JP2016115227A (en) Memory device, storage device, and method for diagnosing storage device
CN115295056A (en) Method and storage device for over-erase repair
TWI893906B (en) Memory device and data erasing method thereof
US12525309B2 (en) Memory system and an operating method thereof
US12374400B2 (en) Memory device controlling pass voltage and operating method thereof

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

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