Modify the remote core application to be loaded by Linux

This module discusses how to modify an MCU+ application, so that the remote core can be initialized by the Linux Remoteproc driver.

Note

There are multiple ways for a remote core to be initialized. For information on other initialization methods, refer to section Booting and Disabling Processor Cores.

Note

The Linux remoteproc driver cannot be used to load firmware into the DM R5F cores. Those cores are loaded by the bootloader before Linux initialization begins.

The MCU+ project can be loaded successfully using CCS. However, if the binary is loaded by the Linux Remoteproc driver, initialization will fail. The Remoteproc driver will fail to initialize the remote core because the MCU+ project does not include a resource table.

Once a resource table has been added and the linker.cmd file has been updated, ensure that Linux and the MCU+ project agree on peripheral and memory allocation.

The resource table

A remote core application must have a resource table in order to be initialized by the Linux Remoteproc driver.

Add Linux IPC to the remote core project

The easiest way to add a resource table to an MCU+ project is to enable IPC with Linux.

Update the linker.cmd file

A memory allocation for the resource table must be added to the remote core’s linker.cmd file.

Allocate peripherals

Ensure that the remote core and Linux request different peripherals.

Allocate memory

Ensure that the memory regions used by the remote core and Linux do not overlap.