# US 2025/0147672 A1 · Method and System of Dynamic Loading of Software from 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/0147672 A1
- Document ID: US20250147672A1
- Status: Published application
- Kind: A1
- Application number: 18/591,959
- Filed: 2024-02-29
- Published: 2025-05-08
- Earliest claimed: 2023-11-03
- Applicants: Texas Instruments Incorporated
- Inventors: Mihir Narendra Mody; Prithvi Shankar Y.A.; Sriramakrishnan Govindarajan; Mohd Asif Farooqui; Shailesh Ganapat Ghotgalkar; Sai Karthik Rajaraman; Pratheesh Gangadhar TK; David Smith; Niraj Nandan
- Web page: https://patentgrep.com/patent/US20250147672A1

## CPC

- G06F 3/0617: {in relation to availability}
- G06F 3/065: {Replication mechanisms}
- 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

Systems and methods for servicing read requests may include receiving a transaction from a processing unit while mirroring contents from an external memory to an on-chip RAM. Such systems and methods may monitor a progress of the mirroring and, based on the monitoring, access code or data values for the transaction from either the external memory or the on-chip RAM. Such systems and methods may further provide the code or data values to the processing unit according to the transaction. Such systems and methods may allow for execution of software before software has been fully downloaded to internal memory.

## Claims

### Claim 1

A method comprising:
copying a set of data from a first memory to a second memory;
monitoring a progress of the copying of the set of data;
receiving a transaction from a processing unit during the copying of the set of data; and
determining, based on the monitoring, whether to perform the transaction using the set of data as stored in the first memory or the set of data as stored in the second memory; and
performing the transaction.

### Claim 2 (depends on 1)

The method of claim 1, wherein the transaction comprises a read request identifying an address and a size of a subset of the set of data.

### Claim 3 (depends on 2)

The method of claim 2, wherein the address comprises an address within the second memory.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining that a subset of the set of data is not available in the second memory;
translating an address received from the processing unit to an address corresponding to a location in the first memory; and
accessing the subset of the set of data from the first memory according to the address corresponding to a location in the first memory.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
determining that a subset of the set of data is available in the second memory; and
accessing the subset of the set of data from the second memory according to an address received from the processing unit.

### Claim 6 (depends on 1)

The method of claim 1, wherein the first memory comprises external memory and wherein the second memory comprises on-chip random access memory (RAM).

### Claim 7 (depends on 1)

The method of claim 1, wherein the copying comprises:
sequentially reading contents from a first plurality of addresses of the first memory; and
writing the contents to a second plurality of addresses of the second memory in a same order in which the contents were read from the first plurality of addresses.

### Claim 8 (depends on 7)

The method of claim 7, wherein the transaction is associated with execution of an application, further wherein the set of data is associated with the application, and wherein the first plurality of addresses correspond to an order in which the set of data is accessed during execution of the application.

### Claim 9 (depends on 1)

The method of claim 1, wherein the transaction is associated with execution of an application, and further wherein the set of data is associated with the application and includes machine code instructions and data values, the method further comprising:
at the processing unit, beginning executing the application before the set of data has been written to the second memory in its entirety.

### Claim 10

A system on-chip (SoC) comprising:
a central processing unit (CPU);
first memory; and
hardware logic disposed within a communication path between the CPU and the first memory, wherein the hardware logic is configured to:
perform a mirroring operation on data from a second memory to the first memory;
receive a request from the CPU, wherein the request references an address in the first memory;
determine whether to respond to the request using the data as stored in the first memory or the data as stored in the second memory based on whether the address referenced by the request has been written by the mirroring operation; and
respond to the request.

### Claim 11 (depends on 10)

The SoC of claim 10, wherein the hardware logic is configured to:
translate the address in the first memory to an address in the second memory.

### Claim 12 (depends on 10)

The SoC of claim 10, wherein the CPU is configured to:
begin executing an application, associated with the data, before the mirroring operation is complete.

### Claim 13 (depends on 10)

The SoC of claim 10, wherein the hardware logic comprises direct memory access (DMA) logic configured to perform the mirroring operation, further wherein the first memory comprises on-chip random access memory (RAM) and the second memory comprises external memory.

### Claim 14 (depends on 13)

The SoC of claim 13, wherein the hardware logic is configured to, as part of the mirroring operation:
sequentially read the data from a first plurality of addresses of the second memory; and
write the data to a second plurality of addresses of the first memory in a same order in which the data was read from the first plurality of addresses.

### Claim 15

A software programming tool comprising:
a compiler configured to:
produce machine code instructions and data values and to produce pseudo-addresses for the machine code instructions and the data values, further wherein the machine code instructions and the data values correspond to a software application; and
a linker configured to:
receive the machine code instructions and the data values from the compiler;
perform a test run on the software application, including determining an execution order of a plurality of discrete software functions of the software application; and
write the machine code instructions and the data values to a nonvolatile memory, including placing the machine code instructions and the data values according to the execution order of the plurality of discrete software functions.

### Claim 16 (depends on 15)

The software programming tool of claim 15, wherein the linker is configured to write the machine code instructions and the data values to the nonvolatile memory by writing to an external memory associated with a system on-chip.

### Claim 17 (depends on 15)

The software programming tool of claim 15, wherein the data values include read-only data values and read and write data values.

### Claim 18 (depends on 17)

The software programming tool of claim 17, wherein the linker is configured to write the machine code instructions and the read-only data values and read and write data values into address ranges of the nonvolatile memory, wherein an order of the address ranges corresponds to the execution order.

### Claim 19 (depends on 15)

The software programming tool of claim 15, wherein the linker is configured to perform the test run by determining the execution order of the plurality of discrete software functions at startup time of the software application.

### Claim 20 (depends on 15)

The software programming tool of claim 15, wherein the plurality of discrete software functions include a branching instruction, wherein the linker is configured to perform the test run by determining the execution order by determining a result of the branching instruction at startup time of the software application.
