# US 2025/0147752 A1 · Method and System for FOTA Update for Higher Performance MCU with External Flash

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

- Number: US 2025/0147752 A1
- Document ID: US20250147752A1
- Status: Published application
- Kind: A1
- Application number: 18/659,615
- Filed: 2024-05-09
- Published: 2025-05-08
- Earliest claimed: 2023-11-03
- Assignees: Texas Instruments Incorporated
- Applicants: Texas Instruments Incorporated
- Inventors: Sai Karthik Rajaraman; Mihir Narendra Mody; Prithvi Y.A.; Deepshikha Gusain; Niraj Nandan; Mohd Asif Farooqui
- Web page: https://patentgrep.com/patent/US20250147752A1

## CPC

- G06F 8/654: using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for updating firmware may include using wait states to reduce or eliminate polling by an executing firmware component. An example includes dedicated firmware update hardware logic components, including a firmware update processing unit that executes firmware update code. The firmware update code may be paused between request of a hardware event and completion of a hardware event and under control of one or more of the hardware logic components. Once a hardware event has been completed, a hardware logic component may determine completion and, in response, restart execution of the firmware update code.

## Claims

### Claim 1

A method comprising:
updating firmware by:
using a first processing unit, initiating a first data write operation to a memory via a memory controller, wherein the first data write operation is configured to write a portion of a first version of the firmware to a first bank of the memory;
determining a duration of a timer between the initiating of the first data write operation and polling to determine a status of the first data write operation;
during the duration of the timer, accessing a second version of the firmware from a second bank of the memory;
after expiration of the timer, using the first processing unit, polling the memory for completion of the first data write operation; and
subsequent to the polling, determining whether a response to the polling indicates completion of the first data write operation.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first data write operation is associated with a firmware over the air (FOTA) update of the firmware.

### Claim 3 (depends on 1)

The method of claim 1, wherein updating the firmware further comprises:
reporting completion of the first data write operation to a second processing unit, wherein the first processing unit and the second processing unit are separate processing units of a system on a chip (SoC);
receiving an instruction to perform a second data write operation, wherein the second data write operation is configured to write a further portion of the first version of the firmware to the first bank of the memory;
performing the second data write operation; and
reporting completion of the second data write operation to the second processing unit.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
setting the timer based on historical write completion data.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
setting the timer based on historical write completion data and according to a Kalman filter.

### Claim 6 (depends on 1)

The method of claim 1, wherein updating the firmware further comprises:
prior to writing the portion to the memory controller, accessing a data bus and a configuration bus, wherein the data bus and the configuration bus are configured to provide access to the memory controller; and
subsequent to writing the portion to the memory controller, releasing access to the configuration bus and the data bus.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
determining whether the configuration bus and the data bus are available for access by the first processing unit, including determining for a particular instruction cycle whether the configuration bus and the data bus are not used for reading the second version of the firmware.

### Claim 8 (depends on 6)

The method of claim 6, further comprising:
during a wait state of the first processing unit, releasing access to the configuration bus and the data bus; and
after exiting the wait state by the first processing unit, releasing access to the configuration bus and the data bus.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
causing the first processing unit to enter a wait state during a time in which the memory controller changes to a first memory controller setting; and
causing the first processing unit to exit the wait state subsequent to completion of the memory controller changing to the first memory controller setting.

### Claim 10

A circuit device comprising:
a first processing resource coupled to an interconnect;
firmware update hardware coupled to the interconnect;
a memory; and
a memory controller coupled to the firmware update hardware, the interconnect, and the memory, the memory controller being configured to read from and write to the memory;
wherein the firmware update hardware includes a second processing resource configured to access computer-readable code, which when executed by the second processing resource, causes the second processing resource to update firmware stored on the memory, including:
requesting access to a bus, wherein the bus is shared with the first processing resource and is coupled to the memory controller;
entering a wait state, under control of the firmware update hardware, during a time in which the firmware update hardware operates to receive access to the bus; and
exiting the wait state, under control of the firmware update hardware, upon access to the bus being received.

### Claim 11 (depends on 10)

The circuit device of claim 10, wherein the computer-readable code is operable to cause the second processing resource to update the firmware, including:
controlling the firmware update hardware to change settings of the memory controller to either allow the second processing resource to write to the memory or to allow the first processing resource to read from the memory; and
entering the wait state, under control of the firmware update hardware, during a time in which the firmware update hardware makes changes to the settings of the memory controller.

### Claim 12 (depends on 10)

The circuit device of claim 10, wherein the second processing resource is further configured to:
initiating a first data write operation to the memory;
pausing execution of the computer-readable code, under control of the firmware update hardware, during a time in which the first data write operation is being completed;
restarting execution of the computer-readable code; and
polling the memory controller for status of the first data write operation.

### Claim 13 (depends on 12)

The circuit device of claim 12, wherein the computer-readable code is operable to cause the second processing resource to update the firmware, including:
programming a timer, according to an adaptive algorithm and historical data, wherein a timing of the polling is performed according to the timer.

### Claim 14 (depends on 12)

The circuit device of claim 12, wherein the computer-readable code is operable to cause the second processing resource to update the firmware, including:
programming a timer, according to a Kalman filter, wherein a timing of the polling is performed according to the timer.

### Claim 15 (depends on 10)

The circuit device of claim 10, wherein the memory controller comprises a flash memory controller configured to read from and write to the memory according to transactions from the first processing resource and the second processing resource.

### Claim 16 (depends on 10)

The circuit device of claim 10, wherein the first processing resource is configured to execute further computer-readable code to cause the first processing resource to trigger the second processing resource to initiate a second data write operation after completion of a first data write operation that is associated with access to the bus.

### Claim 17

A system comprising:
a first processing resource coupled to an interconnect;
a memory;
firmware update hardware that includes a second processing resource configured to execute computer-readable code, which when executed by the second processing resource causes the second processing resource to update firmware stored on the memory; and
a memory controller coupled to the firmware update hardware, the interconnect, and the memory, the memory controller being configured to read from and write to the memory;
wherein the firmware update hardware is configured to:
receive a first instruction from the second processing resource to access a bus, wherein the bus is shared with the first processing resource and is coupled to the memory controller;
cause the second processing resource to enter a wait state coinciding with a time in which the firmware update hardware operates to receive access to the bus; and
cause the second processing resource to exit the wait state in response to access to the bus having been received.

### Claim 18 (depends on 17)

The system of claim 17, wherein the firmware update hardware is further configured to:
receive a second instruction from the second processing resource to change a setting on the memory controller from read operation to write operation;
cause the second processing resource to enter the wait state coinciding with a time in which the firmware update hardware operates to change the setting; and
cause the second processing resource to exit the wait state in response to determining that the setting has been changed.

### Claim 19 (depends on 18)

The system of claim 18, wherein the firmware update hardware is configured to determine that the setting has been changed by receiving a hardware-level signal from the memory controller.

### Claim 20 (depends on 17)

The system of claim 17, wherein the firmware update hardware is configured to determine that access to the bus has been received in response to a hardware-level signal.
