I've attempted to get expand my Syslink/Ipc app so that upon certain notifications from the host a new task is created on the DSP. I managed to get this to work with one new thread, but when I try to create a second task, even after deleting the previous task, I get the following assertion error from Ipc: ti.sdo.ipc.ListMP: line 417: assertion failure: A_nullPointer: Pointer is null ti.sysbios.gates.GateMutex: line 114: assertion failure: A_badContext: bad calling context. See GateMutex API doc for details. xdc.runtime.Error.raise: terminating execution If I remove the task creation code the assertion goes away. What are the current limitions imposed by Syslink and Ipc on multi-threading in the DSP? Is the Syslink/Ipc code thread safe? Instead of having one task that receives notifications and passes messages to the host, is it possible to spread this out over multiple DSP tasks? In other words, can I have multiple instances of Ipc_attach(), one in each task? Each task would deal with its own set of notications and each would have a pair of message queues communicating with the host. Lee Holeva