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.

Linux/LINUXSDK-OMAPL137: Multi Arm Application on same Processor. Syslink_destroy stucks.

Part Number: LINUXSDK-OMAPL137


Tool/software: Linux

Hello Community,

I have a arm application which inits syslink and start the dsp application. They communicate over MessageQs between each other which works fine.


Then I have a second arm application which starts after this on the same arm processor. It calls also SysLink_setup and use a MessageQ to communicate with another task on the DSP.

When the second arm application wants to exit is stucks at syslink_destroy.

Tested Syslink Versions: 2_10_05_26 and 2_21_03_11

1. What's the reason for this behaviour?

2. Is it ok not to call syslink_destroy?

3. Is it allowed to use two arm applications on the same processor?

4. Does the second arm application needs its own MultiProc Id and must the dsp to use ipc_attach to this new id?

Best regards