To be practical, DSP code needs to be made in Code Composer. I know about these necessary linker options for Syslink:
--dynamic
-retain=_Ipc_ResetVector
But the rtos-side code that I build with just these linker options fails to run, I get errors from ProcMgr. What am I missing? I have the EZSDK that came with the c6a816x EVM and the rtos-side apps built in that environment work fine. How do I configure CCS to likewise build Syslink compatible apps?
Here is a possible clue:
I get the following warning when building Syslink/IPC rtos apps in CCS with the above linker options:
<Linking>
warning: creating output section ".plt" without a SECTIONS specification
Lee Holeva