# US 2013/0254465 A1 · Solid state memory formatting

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

- Number: US 2013/0254465 A1
- Document ID: US20130254465A1
- Status: Published application
- Kind: A1
- Application number: 13/783,971
- Filed: 2013-03-04
- Published: 2013-09-26
- Earliest claimed: 2009-01-21
- Assignees: Micron Technology, Inc.
- Applicants: Micron Technology, Inc.
- Inventors: Mehdi Asnaashari; William E. Benson
- Web page: https://patentgrep.com/patent/US20130254465A1

## CPC

- G06F 3/0652: {Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket}
- G06F 3/0608: {Saving storage space on storage systems}
- G06F 3/064: {Management of blocks}
- G06F 3/0643: {Management of files}
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/0688: {Non-volatile semiconductor memory arrays}
- G06F 12/0246: {in block erasable memory, e.g. flash memory}
- G11C 16/10: Programming or data input circuits
- G06F 2212/7202: Allocation control and policies
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G11C: STATIC STORES (semiconductor memory devices H10B)

## Abstract

The present disclosure includes methods and devices for solid state drive formatting. One device embodiment includes control circuitry coupled to a number of memory arrays, wherein each memory array has multiple physical blocks of memory cells. The memory arrays are formatted by the control circuitry that is configured to write system data to the number of memory arrays, where the system data ends at a physical block boundary; and write user data to the number of memory arrays, where the user data starts at a physical block boundary.

## Claims

### Claim 1

A memory controller, comprising:
control circuitry coupled to a number of memory arrays, wherein each of the number of memory arrays has multiple physical blocks of memory cells, wherein the control circuitry is configured to:
write file allocation data to the number of memory arrays such that user data starts at a beginning of one of the multiple physical blocks.

### Claim 2 (depends on 1)

The memory controller of claim 1, wherein the control circuitry is configured to write the file allocation data so that a file allocation table ends at a physical block boundary.

### Claim 3 (depends on 2)

The memory controller of claim 2, wherein the control circuitry is configured to provide a padding of erased memory cells between reserved data and the file allocation table such that the file allocation table ends at a physical block boundary.

### Claim 4 (depends on 3)

The memory controller of claim 3, wherein the control circuitry is configured to provide a padding of erased memory cells between a first file allocation table and a second file allocation table.

### Claim 5 (depends on 1)

The memory controller of claim 1, wherein a host device is coupled to the control circuitry to cause the control circuitry be configured to write the file allocation data to the number of memory arrays such that user data starts at the beginning of one of the multiple physical blocks.

### Claim 6 (depends on 1)

The memory controller of claim 1, wherein the control circuitry has memory and a processor to cause the control circuitry be configured to write the file allocation data to the number of memory arrays such that user data starts at the beginning of one of the multiple physical blocks.

### Claim 7 (depends on 1)

The memory controller of claim 1, wherein the number of memory arrays is one.

### Claim 8

A method for formatting a number of memory arrays in a memory system, the method comprising:
indicating physical parameters associated with the number of memory arrays;
allocating a number of memory cells in the number of memory arrays as a storing system data;
allocating a number of memory cells in the number of memory arrays as a storing user data; and
writing user data such that the user data starts at a beginning of a physical block of the number of memory cells in the number of memory arrays.

### Claim 9 (depends on 8)

The method of claim 8, wherein the system data includes a partition boot record, reserved data, a first file allocation table, and a second file allocation table.

### Claim 10 (depends on 8)

The method of claim 8, including providing a number of erased memory cells between reserved data and a first file allocation table such that a second file allocation table ends at a physical block boundary.

### Claim 11 (depends on 8)

The method of claim 8, including indicating one or more physical parameters associated with the number of memory arrays via an inquiry command.

### Claim 12 (depends on 8)

The method of claim 8, including indicating one or more physical parameters associated with the number of memory arrays by receiving the physical parameters from a memory in a memory controller.

### Claim 13 (depends on 8)

The method of claim 8, including calculating a modulus for the number of memory arrays based on the indicated physical parameters.

### Claim 14

A method for formatting a solid state drive in a memory system, the method comprising:
writing data to a public boot record of a particular memory array of a number of memory arrays in a solid state drive, wherein the particular memory arrays includes a number of physical blocks of memory cells;
writing first file allocation data of the particular memory array and second file allocation data of the particular memory array; and
padding a portion of the particular memory array by not writing data in a number of memory cells between those storing reserved data and the first file allocation data such that the second file allocation data ends at a physical block boundary and such that user data starts at a physical block boundary.

### Claim 15 (depends on 14)

The method of claim 14, including padding a portion of the particular memory array by not writing data in a number of memory cells between the first file allocation data and the second file allocation data such that the second file allocation data ends at a physical block boundary and such that user data starts at a physical block boundary.

### Claim 16 (depends on 14)

The method of claim 14, including padding a portion of the particular memory array by not writing data in a number of memory cells between the second file allocation data and the user data such that the second file allocation data ends at a physical block boundary and such that user data starts at a physical block boundary.

### Claim 17 (depends on 14)

The method of claim 14, including user writing data to a beginning of a page when writing the user data.

### Claim 18 (depends on 14)

The method of claim 14, including writing user data starting at a physical block boundary based, at least partially, on one or more physical parameters of the particular memory array and a modulus for writing to the particular memory array.

### Claim 19 (depends on 18)

The method of claim 18, wherein the one or more physical parameters are selected from the group including memory array size, block size, page size, and cell type.

### Claim 20

A solid state memory system, comprising:
a number of memory arrays, wherein each of the number of memory arrays include a number of memory cells forming a number of physical blocks, wherein each of the physical blocks is organized into a number of pages;
a memory controller, wherein the memory controller includes control circuitry coupled to the number of memory arrays;
a host device coupled to the memory controller and including a memory access device and memory, the memory access device configured to execute instructions stored on the memory to:
write user data at a beginning of a physical block when writing data to an erased physical block selected from the number of physical blocks; and
write user data at a beginning of a page when writing data to an erased page.

### Claim 21 (depends on 20)

The solid state memory system of claim 20, wherein a number of physical parameters of the number of memory arrays are sent from the memory controller to the memory access device in response to an inquiry command.

### Claim 22 (depends on 21)

The solid state memory system of claim 21, wherein the number of physical parameters are used by the memory access device to calculate a modulus for the number of memory arrays.

### Claim 23 (depends on 21)

The solid state memory system of claim 21, wherein the physical parameters are used by the memory access device to calculate a logical block address to write system data.

### Claim 24 (depends on 20)

The solid state memory system of claim 20, wherein the physical parameters are used by the memory access device to calculate a logical block address to write user data.
