# US 2010/0077132 A1 · Memory devices and access methods thereof

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2010/0077132 A1
- Document ID: US20100077132A1
- Status: Published application
- Kind: A1
- Application number: 12/260,139
- Filed: 2008-10-29
- Published: 2010-03-25
- Earliest claimed: 2008-09-25
- Assignees: Silicon Motion, Inc.
- Inventors: Chi-Hsiang Hung
- Web page: https://patentgrep.com/patent/US20100077132A1

## CPC

- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G06F 11/1068: {in sector programmable memories, e.g. flash disk (G06F11/1072 takes precedence)}
- G11C 16/349: {Arrangements for evaluating degradation, retention or wearout, e.g. by counting erase cycles}
- G06F 2212/7211: Wear leveling
- G11C 2029/0411: {Online error correction}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)

## Abstract

Methods and devices capable of erasing a flash memory evenly are provided, in which a flash memory comprises a data region with a plurality of data blocks and a spare region with a plurality of spare blocks, and a controller retrieves a corresponding data with a check code from a first data block of the flash memory according to a read command from a host, performs a predetermined check to the corresponding data by the check code, determines whether an error is correctable when a check result of the predetermined check represents that the error has occurred, and increases an erase count of the first data block by a predetermined value when the error is correctable.

## Claims

### Claim 1

An access method for a flash memory, wherein the flash memory comprises a data region and a spare region, the data region comprises a plurality of data blocks and the spare region comprises a plurality of spare blocks, comprising:
retrieving a corresponding data with a check code from a first data block of the flash memory according to a read command from a host;
performing a predetermined check to the corresponding data by the check code;
determining whether an error is correctable when a check result of the predetermined check represents that the error has occurred; and
increasing an erase count of the first data block by a predetermined value when the error is correctable.

### Claim 2 (depends on 1)

The method as claimed in claim 1, further comprising marking the first data block as a failed block when the error is uncorrectable.

### Claim 3 (depends on 1)

The method as claimed in claim 1, wherein the check code is an error correction code (ECC).

### Claim 4 (depends on 1)

The method as claimed in claim 1, wherein the predetermined value exceeds two.

### Claim 5 (depends on 1)

The method as claimed in claim 1, further comprising:
receiving data corresponding to a logical address linked to a second data block of the data region when receiving a write command from the host;
popping a spare block from the spare region; and
writing the data into the popped spare block and linking a physical address of the popped spare block to the logic address.

### Claim 6 (depends on 5)

The method as claimed in claim 5, further comprising performing data integration to the data blocks of the data region before popping the spare block.

### Claim 7 (depends on 5)

The method as claimed in claim 5, further comprising:
erasing the second data block; and
pushing the second data block into the spare region.

### Claim 8

An access method for a flash memory, wherein the flash memory is divided into a data region with a plurality of data blocks and a spare region with a plurality of spare blocks, comprising:
retrieving a corresponding data with a check code from a first data block of the flash memory according to a read command from a host;
performing a predetermined check to the corresponding data by the check code;
determining whether an error is correctable when a check result of the predetermined check represents that the error has occurred;
increasing an erase count of the first data block by a predetermined value when the error is correctable;
receiving data corresponding to a logical address linked to a second data block of the data region when receiving a write command from the host;
popping a first spare block from the spare region; and
writing data stored in a third data block to the first spare block and re-mapping the third data block and the first spare block when an erase count of the first spare block reaches a default value and the data region has the third data block with an erase count of zero.

### Claim 9 (depends on 8)

The method as claimed in claim 8, further comprising decreasing the erase count of the all data blocks in the data region and the all spare blocks in the spare region by one, when the erase count of the first spare block reaches the default value and the data region does not have the third data block with the erase count of zero.

### Claim 10 (depends on 9)

The method as claimed in claim 9, further comprising:
popping a second spare block from the spare region; and
writing the data corresponding to the logical address into the second spare block and linking a physical address of the second spare block to the logic address, when the erase count of the second spare block is less than the default value.

### Claim 11

A memory device, comprising:
a flash memory comprising a data region with a plurality of data blocks and a spare region with a plurality of spare blocks; and
a controller retrieving a corresponding data with a check code from a first data block of the flash memory according to a read command from a host, performing a predetermined check to the corresponding data by the check code, determining whether an error is correctable when a check result of the predetermined check represents that the error has occurred, and increasing an erase count of the first data block by a predetermined value when the error is correctable.

### Claim 12 (depends on 11)

The memory device as claimed in claim 11, wherein the controller marks the first data block as a failed block when the error is uncorrectable.

### Claim 13 (depends on 11)

The memory device as claimed in claim 11, wherein the check code is an error correction code (ECC).

### Claim 14 (depends on 11)

The memory device as claimed in claim 11, wherein the predetermined value exceeds two.

### Claim 15 (depends on 11)

The memory device as claimed in claim 11, wherein the controller receives data corresponding to a logical address linked to a second data block when receiving a write command from the host, and the controller pops a spare block from the spare region, and writes the data into the popped spare block and links a physical address of the popped spare block to the logical address when the erase count of the popped spare block is less than a default value.

### Claim 16 (depends on 15)

The memory device as claimed in claim 15, wherein the controller further performs a data integration to the data blocks of the data region before popping the spare block.

### Claim 17 (depends on 15)

The memory device as claimed in claim 15, wherein the controller erases the second data block and pushes the erased second data block into the spare region when the erase count of the popped spare block is less than the default value.

### Claim 18 (depends on 15)

The memory device as claimed in claim 15, wherein, when an erase count of the popped spare block reaches the default value and the data region has a third data block with an erase count of zero, the controller writes data stored in the third data block to the popped spare block and re-maps the third data block and the popped spare block.

### Claim 19 (depends on 18)

The memory device as claimed in claim 18, wherein, when the erase count of the first spare block reaches the default value and the data region does not have the third data block with the erase count of zero, the controller decreases the erase count of the all data blocks in the data region and the all spare blocks in the spare region by one.

### Claim 20 (depends on 18)

The memory device as claimed in claim 18, wherein the controller further erases the third data block and pushes the erased third data block into the spare region, when the erase count of the popped spare block reaches the default value and the data region has the third data block with the erase count of zero.
