DSP/BIOS task ended on EVMOMAPL137

Jonathan Journo

Hello,

I am working on the evmomapl137, using the OMAPL137_dsp_1_00_00_10 SDK & dsplink 1.61.3. (montavista linux). I am running the dsplink examples fine.I modified an example (LOOP example) to run my own first DSP/BIOS task on the DSP, I have disabled all the CHNL transfers.

on the GPP side, I have created a process that loads the dsp executable and start the DSP and go sleeping.

on the DSP side, the DSP/BIOS task is a forever loop that monitor the DIP switch input and write its state on the LED's.

The DSP task runs OK, but I did not understand why the DSP task stop running when I kill the GPP linux process. the proc_stop / proc_detach/ proc_destroy are not being called by the GPP process.

Is the DSP/BIOS task is dependent on the GPP task that create it?

How can the DSP/BIOS task run even if the GPP process is killed?

Thanks for any help.

over 15 years ago

0 Deepali Uppal over 15 years ago

TI__Expert 4930 points

Jonathon,

DSPLink registers a signal handler by default. When you kill the GPP process, the default signal handler runs The signal handler frees up all DSPLink resources, also calls PROC_detach (puts DSP in reset) , PROC_stop (stops DSP run) etc. This must be causing your DSP task to stop executing.

I would suggest you to disable the DSPLink signal handler. This will ensure the default signal handler does not run when you kill the process. Please look at http://processors.wiki.ti.com/index.php/DSPLink_FAQs#Multi-process_cleanup_support_questions on steps to disable signal handler

Since you are on CE, this link also might be relevant http://processors.wiki.ti.com/index.php/DSPLink_Signal_Handling_in_Codec_Engine

Deepali

0 Jonathan Journo over 15 years ago in reply to Deepali Uppal

Intellectual 475 points

Thank you.

Processors

Processors forum

DSP/BIOS task ended on EVMOMAPL137