Application Development on Remote Cores#

This module discusses how to develop an MCU+ application on a remote core, running alongside a Linux application.

Three main concepts will be covered:#

  • Develop and debug a standalone remote core application through CCS

  • Update the remote core application so that it can be loaded by Linux

  • Launch the application from Linux, and use CCS to debug the application while Linux is running

Note

Some information in this section does NOT apply to applications running on the DM R5F, since the DM R5F is not initialized by Linux. Information specific to DM R5F development will be added in a later version of the academy. For now, basic information about DM R5F development can be found in section Developing on the DM R5F.

For this example, we will use the hello_world project on the

M4F.

Step 1

Development & debug through CCS

This section discusses how to develop and debug a standalone remote core application through CCS.

Step 2

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.

Step 3

Launch the remote core project from Linux

This section will discuss how to load the remote core project from Linux.

Step 4

Debug the remote core alongside Linux

There are multiple tools to debug a remote core application while Linux is running, both from the Linux terminal, and through CCS.

Appendix

Developing on the DM R5F

The development process for applications running on the Device Management (DM) R5F is different from the development process on other remote cores, because the DM R5F is initialized separately and runs the Device Management task.

Appendix

Adding an empty resource table

If the remote core application does not need Linux IPC, you can reduce memory usage by including an empty resource table instead of using the resource table that is auto-generated with Linux IPC.