This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

omapl138 syslink run problems

Other Parts Discussed in Thread: OMAPL138

hello,

 i encounter a problem that puzzled me many days,i can't find out the answer,i used the syslink2_21_01_05 ,to communicate dsp with arm, the example is ex02 messageQ of omapl138.

DSP compile options as follow  describled:

sysbios6_34_03_19

xdctools3_24_5_48

ipc1_25_01_09

ccs 5.3.0.0092,

ARM linux kernel is 3.1.

the ex02 messageQ,the side of dsp is compiled in ccsv5.3.

firstly,ARM used slaveloader to load dsp executable file,then,ARM load the arm executable file.

the problem is app_create failed.dsp cannot wait the  remote core has also registered notify callback,stop at signed red colors

/* 2. register notify callback */
status = Notify_registerEventSingle(HalfRms_Module.hostProcId, HalfRms_Module.lineId,
HalfRms_Module.eventId, HalfRmsMessageQ_Server_notifyCB, (UArg)&HalfRms_Module);

if (status < 0) {
Log_error0("Server_create: Device failed to register notify event");
goto leave;
}

/* 3. wait until remote core has also registered notify callback */
do {
status = Notify_sendEvent(HalfRms_Module.hostProcId,HalfRms_Module.lineId,
HalfRms_Module.eventId, APP_CMD_NOP, TRUE);

if (status == Notify_E_EVTNOTREGISTERED) {
Task_sleep(100);
}
} while (status == Notify_E_EVTNOTREGISTERED);

if (status < 0 ) {
Log_error0("Server_create: Host failed to register callback");
goto leave;
}

by the way ,the ex07 GateMP, it is succeed,arm and dsp exchange data smoothly(the run process is samed as messageQ compiled)

best wishes