PROCESSOR-SDK-OMAPL138: Issue connecting to LAD daemon from DSP application

Hello Kim,

It might take a couple of days for us to get back to you on this thread. Please ping us if we have not replied by next week.

Regards,

Nick

Hi Nick

Sounds great.
I will also be out of office during next week.

Regards,
Kim

Hi Kim,

Have you tried the built-in examples of the Processor-SDK? The page that you mentioned above has a link to a video about how to build and run the IPC examples: Building and Running Inter-Processor Communication (IPC) Examples on the AM572x GP EVM.

I briefly looked at your dsp.cfg and it seems you were using Ipc.ProcSync_PAIR, instead of BIOS.addUserStartupFunction('&IpcMgr_ipcStartup') which is used by the IPC examples. Was there any particular reason why you did that?

Thanks,

Jianzhong

Hi Jianzhongxu,

Thank you for getting back to me.

Video:
I noticed that the video does not mention the LAD daemon. Is the Daemon not required for the AM572x GP EVM?

CFG script:
Previously, I have tried without "Ipc.ProcSync_PAIR" and used BIOS.addUserStartupFunction('&IpcMgr_ipcStartup') instead.
This merely results in the same error as seen in the log file for the LAD daemon, namely "NameServer_attach: connect failed: procId=1, errno=22 (Invalid argument)".

Thanks & Regards,
Kim

Hi Kim,

The LAD daemon should run in background. Can you try the out-of-box IPC examples according to IPC Quick Start Guide? Please pay special attention to OMAP-L138 specific instruction:

For OMAP-L138 platform, Modify the symblic link in /lib/firmware of the default image names to the build binary

DSP image files: rproc-dsp-fw

Hi Jianzhongxu,

Running ex02_messageq example

I have tried out the “ex02_messageq” IPC example. I get the following output from the example:

The output looks ok, but the “trace0” file under “debug/remoteproc/remoteproc0/trace0” is empty.

Daemon & Symbolic link name
I am running the LAD Daemon in the background and “Before” I start the DSP application with remoteproc and the ARM/Linux application.

I am using “rproc-dsp-fw” as the name of the symbolic link under “lib/firmware”.

My procedure
I load the following kernel modules in this order:

$ modprobe remoteproc

$ modprobe da8xx_remoteproc

$ modprobe virtio_rpmsg_bus

$ modprobe rpmsg_proto

I am starting the LAD Daemon in the following way:

$ usr/bin/lad_omapl138 -l /app/log.txt

I am starting the DSP application with remoteproc in the following way:

$ cd /lib/firmware

$ ln -sf server_dsp.xe674 rproc-dsp-fw

$ echo start > /sys/class/remoteproc/remoteproc0/state

I am starting the Linux application in the following way:

$ cd /app

$ ./app_host HOST

Output from log.txt file

After all of the steps above, the log for the LAD Daemon still contains the error:

“NameServer_attach: connect failed: procId=1, errno=22 (Invalid argument)”

Thanks and regards,

Kim

Hi Kim,

Glad that the IPC example works well for you. In your other experiment, were you following the "IPC Install Guide Linux" document in <ipc_installation_root>/docs folder? Do you need to manually start LAD Daemon which I think is started when the board boots?

I tried to start the LAD Daemon as you did but got error message below:

root@omapl138-lcdk:~# /usr/bin/lad_omapl138 -l log.txt
Multiple instances of LAD are not supported!

What's the difference between the IPC example and your own application?

Thanks and regards,

Jianzhong

Hi Jianzhongxu,

Yes, I followed the "IPC Install Guide Linux" guide.

That is strange. I always start the LAD daemon manually.
When I build the IPC library the LAD daemon is generated. I transferred it to the OMAPL138 with scp to /usr/bin.

I get the same error if I try to run the LAD daemon and it is already running.
Is your LAD daemon starting during boot?

If you boot the board, the following cmd should indicate if the LAD is started during boot:
$ ps aux|grep LAD

Regards,
Kim

Hi Jianzhongxu,

DSP traces:
I am still doing some testing with the "ex02_messageq" ipc example. I managed to get the printf statements for the DSP to also work now.
My trace0 file says:

I guess the output looks ok.
I also noticed that the Socket connect failed error in the LAD log is no longer present...

MessageQ:
I have a MessageQ related question.

In my own application I just create a MessageQ queue on the ARM side with MessageQ_create().
I call it "HOST:dspsystem".


On the DSP side I wish to simply open this queue with MessageQ_open() like the following:


Doing this, the DSP never breaks out of the loop.

Any ideas, why this is happening?
Should I create a new thread based on this question?

/* root of the configuration object model */
var Program = xdc.useModule('xdc.cfg.Program');

//var Reset 	 					           = xdc.useModule('xdc.runtime.Reset');
//var Startup 					           = xdc.useModule('xdc.runtime.Startup');
var BIOS 	 					             = xdc.useModule('ti.sysbios.BIOS');
var Main 	 					             = xdc.useModule('xdc.runtime.Main');
var Defaults 					           = xdc.useModule('xdc.runtime.Defaults');
var System 	 					           = xdc.useModule('xdc.runtime.System');
var Mailbox                      = xdc.useModule('ti.sysbios.knl.Mailbox');
var HeapBuf                      = xdc.useModule('ti.sysbios.heaps.HeapBuf');
var Timestamp                    = xdc.useModule('xdc.runtime.Timestamp');
var Hwi 	 					             = xdc.useModule('ti.sysbios.hal.Hwi');
var ti_sysbios_family_c64p_Hwi   = xdc.useModule('ti.sysbios.family.c64p.Hwi');
var Cache 						           = xdc.useModule('ti.sysbios.hal.Cache');
var ti_sysbios_family_c64p_Cache = xdc.useModule('ti.sysbios.family.c64p.Cache');

var Memory 	 					           = xdc.useModule('xdc.runtime.Memory');
var HeapMem                      = xdc.useModule('ti.sysbios.heaps.HeapMem');

/* Uncomment to debug before main() */
//Reset.fxns[Reset.fxns.length++] 			        = '&myReset';
//Startup.firstFxns[Startup.firstFxns.length++] = '&myFirst';
//Startup.lastFxns[Startup.lastFxns.length++]   = '&myLast';

/* application uses the following modules and packages */
xdc.useModule('xdc.runtime.Assert');
xdc.useModule('xdc.runtime.Diags');
xdc.useModule('xdc.runtime.Error');
xdc.useModule('xdc.runtime.Log');
xdc.useModule('xdc.runtime.Registry');

xdc.useModule('ti.sysbios.knl.Semaphore');
xdc.useModule('ti.sysbios.knl.Task');

/*
 *  ======== IPC Configuration ========
 */
//var Ipc = xdc.useModule('ti.ipc.Ipc');
//Ipc.ProcSync_ALL;

xdc.useModule('ti.ipc.ipcmgr.IpcMgr');

/* describe the processors in the system */
var MultiProc = xdc.useModule('ti.sdo.utils.MultiProc');
MultiProc.setConfig("DSP", ["HOST", "DSP"]);

var BIOS      = xdc.useModule('ti.sysbios.BIOS');
BIOS.addUserStartupFunction('&IpcMgr_ipcStartup');

/*
 *  ======== SYS/BIOS Configuration ========
 */
if (Program.build.profile == "debug") {
    BIOS.libType = BIOS.LibType_Debug;
} else {
    BIOS.libType = BIOS.LibType_Custom;
}

/* System stack size (used by ISRs and Swis) */
Program.sectMap[".stack"] = new Program.SectionSpec();
Program.sectMap[".stack"].loadSegment = "IRAM";
Program.stack = 0x2000;
Program.heap  = 32768;

var Task = xdc.useModule('ti.sysbios.knl.Task');
Task.common$.namedInstance = true;

/* default memory heap */
var Memory = xdc.useModule('xdc.runtime.Memory');
var HeapMem = xdc.useModule('ti.sysbios.heaps.HeapMem');
var heapMemParams = new HeapMem.Params();
heapMemParams.size = 0x10000;
Memory.defaultHeapInstance = HeapMem.create(heapMemParams);

/* IRAM Heap Configuration */
var iramHeapParams  	     = new HeapMem.Params;
iramHeapParams.size 	     = 0x00005000;
iramHeapParams.sectionName = "IRAM_HEAP";
Program.global.iramHeap	   = HeapMem.create(iramHeapParams);

/* DDR Heap Configuration */
var ddrHeapParams  	   		 = new HeapMem.Params;
ddrHeapParams.size 	   		 = 0x005000;
ddrHeapParams.sectionName  = "DDR_HEAP";
Program.global.ddrHeap     = HeapMem.create(ddrHeapParams);

/* STREAMING Heap Configuration */
var streamingDataHeapParams         = new HeapMem.Params;
streamingDataHeapParams.size 	      = 0x005000;
streamingDataHeapParams.sectionName = "STREAMING_DATA_HEAP";
Program.global.streamingDataHeap	  = HeapMem.create(streamingDataHeapParams);

Program.sectMap["DDR_HEAP"]  			                 = new Program.SectionSpec();
Program.sectMap["IRAM_HEAP"] 			                 = new Program.SectionSpec();
Program.sectMap["STREAMING_DATA_HEAP"]             = new Program.SectionSpec();
Program.sectMap["DDR_HEAP"].loadSegment            = "DDR";
Program.sectMap["IRAM_HEAP"].loadSegment           = "IRAM";
Program.sectMap["STREAMING_DATA_HEAP"].loadSegment = "STREAMING_DATA";


/*
 *  ======== MessageQ Configuration ========
 */
/* create a heap for MessageQ messages */
var HeapBuf = xdc.useModule('ti.sysbios.heaps.HeapBuf');
var params = new HeapBuf.Params;
params.align = 8;
params.blockSize = 512;
params.numBlocks = 256;
var msgHeap = HeapBuf.create(params);

var MessageQ  = xdc.useModule('ti.sdo.ipc.MessageQ');
MessageQ.registerHeapMeta(msgHeap, 0);

/* Setup MessageQ transport */
var VirtioSetup = xdc.useModule('ti.ipc.transports.TransportRpmsgSetup');
MessageQ.SetupTransportProxy = VirtioSetup;

/* Setup NameServer remote proxy */
var NameServer = xdc.useModule("ti.sdo.utils.NameServer");
var NsRemote = xdc.useModule("ti.ipc.namesrv.NameServerRemoteRpmsg");
NameServer.SetupProxy = NsRemote;

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

/*  Use SysMin because trace buffer address is required for Linux/QNX
 *  trace debug driver, plus provides better performance.
 */
var System = xdc.useModule('xdc.runtime.System');
var SysMin = xdc.useModule('ti.trace.SysMin');

System.SupportProxy = SysMin;
SysMin.bufSize  = 0x8000;

Program.sectMap[".tracebuf"] = "DDR";
Program.sectMap[".errorbuf"] = "DDR";

var Cache = xdc.useModule('ti.sysbios.family.c64p.Cache');

/* Set 0xc0000000 -> 0xc3ffffff to be non-cached VirtQueue based IPC
 * Set 0xc4000000 -> 0xc4ffffff to be cached. Not currently not used
 */
Cache.MAR192_223 = 0x00000010;

/*  Configure the SYS/BIOS clock to use the lower half of Timer 1 */
var Timer = xdc.useModule('ti.sysbios.timers.timer64.Timer');
var Clock = xdc.useModule('ti.sysbios.knl.Clock');
Timer.timerSettings[1].master = true;
Timer.defaultHalf = Timer.Half_LOWER;
Clock.timerId = 1;

/*
 *  ======== Instrumentation Configuration ========
 */
 /* system logger */
var LoggerSys = xdc.useModule('xdc.runtime.LoggerSys');
var LoggerSysParams = new LoggerSys.Params();
var Defaults = xdc.useModule('xdc.runtime.Defaults');
Defaults.common$.logger = LoggerSys.create(LoggerSysParams);

/* enable runtime Diags_setMask() for non-XDC spec'd modules */
var Diags = xdc.useModule('xdc.runtime.Diags');
Diags.setMaskEnabled = true;

/* override diags mask for selected modules */
xdc.useModule('xdc.runtime.Main');
Diags.setMaskMeta("xdc.runtime.Main",
    Diags.ENTRY | Diags.EXIT | Diags.INFO, Diags.RUNTIME_ON);

var Registry = xdc.useModule('xdc.runtime.Registry');
Registry.common$.diags_ENTRY = Diags.RUNTIME_OFF;
Registry.common$.diags_EXIT  = Diags.RUNTIME_OFF;
Registry.common$.diags_INFO  = Diags.RUNTIME_OFF;
Registry.common$.diags_USER1 = Diags.RUNTIME_OFF;
Registry.common$.diags_LIFECYCLE = Diags.RUNTIME_OFF;
Registry.common$.diags_STATUS = Diags.RUNTIME_OFF;

var Main = xdc.useModule('xdc.runtime.Main');
Main.common$.diags_ASSERT = Diags.ALWAYS_ON;
Main.common$.diags_INTERNAL = Diags.ALWAYS_ON;

Thanks & Regards,
Kim