# US 2021/0173568 A1 · Integrity check of a memory

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

- Number: US 2021/0173568 A1
- Document ID: US20210173568A1
- Status: Published application
- Kind: A1
- Application number: 17/111,778
- Filed: 2020-12-04
- Published: 2021-06-10
- Earliest claimed: 2019-12-05
- Assignees: STMicroelectronics (Grenoble 2) SAS
- Applicants: STMicroelectronics (Grenoble 2) SAS
- Inventors: Gerald BRIAT; Stephane MARMEY
- Web page: https://patentgrep.com/patent/US20210173568A1

## CPC

- G06F 3/0619: {in relation to data integrity, e.g. data losses, bit errors}
- G06F 21/79: in semiconductor storage media, e.g. directly-addressable memories
- G06F 3/0652: {Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket}
- G06F 3/0659: {Command handling arrangements, e.g. command buffers, queues, command scheduling}
- G06F 3/0679: {Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP]}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The integrity of a memory is checked by: storing data representative of an operation to be executed in the memory; executing the operation; and erasing the data once the execution is complete.

## Claims

### Claim 1

A method for checking the integrity of a memory, comprising the following steps:
storing data representative of an operation to be executed in the memory;
executing the operation; and
erasing the data once the execution of the operation is completed.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising a step of reading the data before executing another operation in the memory.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising a step of reading the data after resetting the memory.

### Claim 4 (depends on 1)

The method according to claim 1, further comprising a step of detecting, as a function of the data, whether an interruption has occurred during the execution of the operation.

### Claim 5 (depends on 4)

The method according to claim 4, further comprising a step of repeating execution of the operation if an interruption is detected.

### Claim 6 (depends on 5)

The method according to claim 5, further comprising a step, before the repeating execution of the operation, of completely erasing a memory page subsequently configured to be modified by execution of the operation.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the data include an operation code that is a function of a nature of operation to be executed in the memory.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the operation code is assigned a value chosen from a group of values consisting of:
a first set of values, if no operation is being executed in the memory;
a second set of values, if a write operation is being executed in the memory;
a third set of values, if an erase operation is being executed in the memory; and
a fourth set of values, in case of configuration operation of the microcontroller,
wherein the first and fourth sets of values are each preferably being made up of a single value.

### Claim 9 (depends on 8)

The method according to claim 8, wherein the second set of values comprises:
a first value, if a write operation of a word is being executed in the memory; and
a second value, if a write operation of several words, preferably eight words, is being executed in the memory.

### Claim 10 (depends on 8)

The method according to claim 8, wherein the third set of values comprises:
a third value, if an erase operation of a memory page is being executed in the memory;
a fourth value, if an erase operation of a memory bank is being executed in the memory; and
a fifth value, if an erase operation of several memory banks is being executed in the memory.

### Claim 11 (depends on 1)

The method according to claim 1, wherein the data further include:
an address pointing to a memory area where the operation is executed;
an identifier of a memory bank where the operation is executed; and
an identifier of a memory chip where the operation is executed.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the memory is part of a microcontroller including:
a processor; and
at least two memory chips, wherein each memory chip comprises at least two memory banks.

### Claim 13 (depends on 12)

The method according to claim 12, wherein the data are stored in a register of one of the memory chips.

### Claim 14 (depends on 1)

The method according to claim 1, further comprising, as long as the execution of the operation is not complete, causing a hardware circuit coupled to connecting pads of the memory to continue to impose command signals corresponding to the operation.

### Claim 15 (depends on 1)

The method according to claim 1, wherein the memory is a flash memory.

### Claim 16 (depends on 1)

A finite state machine configured to implement the method according to claim 1.

### Claim 16 (depends on 1)

A system, comprising at least one memory configured to implement the method according to claim 1.

### Claim 17

A method, comprising:
in response to a command to execute an operation to write data in, or erase data in, a memory, storing data in a data register that is representative of the operation to be executed;
performing the operation; and
in response to an interruption which occurs during performing of the operation which causes a reset of the memory:
restarting the memory;
reading the data that is representative of the operation to be executed from the register to confirm that the operation was not completed;
repeating performing of the operation; and
following completion of performing the operation, erasing the data from data register.

### Claim 18 (depends on 17)

The method according to claim 17, further comprising, before the repeating performing the operation, completely erasing a memory page subsequently configured to be modified by performing the operation.

### Claim 19 (depends on 17)

The method according to claim 17, wherein the data that is representative of the operation includes an operation code that is a function of a nature of operation to be performed in the memory.

### Claim 20 (depends on 19)

The method according to claim 19, wherein the operation code is assigned a value chosen from a group of values consisting of:
a first set of values, if no operation is being executed in the memory;
a second set of values, if a write operation is being executed in the memory;
a third set of values, if an erase operation is being executed in the memory; and
a fourth set of values, in case of configuration operation of the microcontroller,
wherein the first and fourth sets of values are each preferably being made up of a single value.

### Claim 21 (depends on 20)

The method according to claim 20, wherein the second set of values comprises:
a first value, if a write operation of a word is being executed in the memory; and
a second value, if a write operation of several words, preferably eight words, is being executed in the memory.

### Claim 22 (depends on 20)

The method according to claim 20, wherein the third set of values comprises:
a third value, if an erase operation of a memory page is being executed in the memory;
a fourth value, if an erase operation of a memory bank is being executed in the memory; and
a fifth value, if an erase operation of several memory banks is being executed in the memory.

### Claim 23 (depends on 17)

The method according to claim 17, wherein the memory is a flash memory.

### Claim 24 (depends on 17)

The method according to claim 17, further comprising causing a hardware circuit coupled to the memory to continue to impose command signals corresponding to the operation on connecting pads of the memory in response to said reset.

### Claim 25 (depends on 17)

A finite state machine configured to implement the method according to claim 17.
