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.

Interrupting GPP side of a DSP Link Example Application

Other Parts Discussed in Thread: OMAP3530

I am working with OMAP3530 Gumstix, modified so that I can use a JTag XDS debugger.

Using the basic Frame Work which is given with the DSPLink Example Applications (Message Queue) I've created my own DSPLink Application which I am able to start on the DSP Core.  Following suit, I used PROC_setup (setup the PROC subsystem in DSP Link) PROC_attach (attach to my DSP Core) PROC_load (Load the DSP Application) and PROC_start (set up the entry address and begin execution.)  I can start a Jtag session with the DSP Core, and I can single step execute from Code Composer Studio.

My question:  Why must the user space application on the GPP be left running in order for the DSP application to continue to work?  If I suspend/resume my GPP application, the DSP continues to execute.  But if I interrupt (ctrl-c) the GPP Application, the debugger session attached to the DSP Core crashes.  Why?  How does killing the user-space application on the GPP effect the execution of the BIOS DSP task?