Forum Post: RE: IPC 3.12 MessageQ Linker Issue

I was able to cross compile the example project using Linux and run the application on the OMAP5x EVM, but it would be nice to have an IPC 3.x MessageQ ARM/DSP template that can build under Window using Code Composer. 

I did make some progress by merging the source from "ipc.cfg.xs" and "DspAmmu.cfg" to "Dsp.cfg," which then reports the following error:

ti.ipc.remoteproc.Resource : IpcMemory.loadSegment not found

To temporarily resolve this error, I commented output the following section from Dsp.cfg:

/* Enable Memory Translation module that operates on the BIOS Resource Table */ var Resource = xdc.useModule('ti.ipc.remoteproc.Resource'); Resource.loadSegment = "EXT_CODE";

, which resulted in the following error:

ti.trace.SysMin : .tracebuf section found, but not in Program.cpu.memoryMap

I can't seem to resolve this error. I tried to minimize the configuration file as

var Program    = xdc.useModule('xdc.cfg.Program'); Program.global.procName = "DSP"; Program.argSize         = 100; Program.stack           = 0x1000;  var MessageQ  = xdc.useModule('ti.sdo.ipc.MessageQ'); MessageQ.SetupTransportProxy = xdc.useModule('ti.ipc.transports.TransportRpmsgSetup');  var NameServer = xdc.useModule("ti.sdo.utils.NameServer"); NameServer.SetupProxy = xdc.useModule("ti.ipc.namesrv.NameServerRemoteRpmsg");  var SysMin     = xdc.useModule('ti.trace.SysMin'); SysMin.bufSize  = 0x8000;  Program.sectMap[".tracebuf"] = "TRACE_BUF";  var System = xdc.useModule('xdc.runtime.System'); System.SupportProxy = SysMin;

but the same error is reported..

Any ideas how I resolve these errors? I'm also curious why removing the usage of "xdc.loadCapsule" and just merging in the source seems to change the build behavior.