speech1_copy example hanging on signal

matthavener

If I send a regular SIGTERM to the speech1_copy example while it is processing, it will hang. I loaded it up in gdb and it seems that Global_exit is registered for atexit. It seems to be hanging on cleanup().

This is just a vanilla all_codecs server with SPHENC1_COPY and SPHDEC1_COPY from codec_engine_2_10.

Anyone have any ideas? Should I take this directly to TI?

over 16 years ago

0 matthavener over 16 years ago

Prodigy 50 points

I also noticed after enough kills, the example can no longer open the engine and the board needs to be rebooted.

0 Juan Gonzales over 16 years ago

TI__Mastermind 37340 points

Can you tell us where you got the codecs from; do they come bundled in a particular DVSDK release? If so, which one? Also, can you specify which platform this is for (DM644x, DM6437, DM355, DM6467...)?

0 matthavener over 16 years ago in reply to Juan Gonzales

Prodigy 50 points

They are bundled in the 2_10 release of the codec engine. I'm not sure which DVSDK release includes it..

This is for DM6446.

0 matthavener over 16 years ago in reply to matthavener

Prodigy 50 points

bump

0 Juan Gonzales over 16 years ago in reply to matthavener

TI__Mastermind 37340 points

Apologies for the delayed response; I was out last week and just returned to the office. After some investigation, there appears to be an issue with DPSLINK software module handling SIGTERM requests. This is very likely the cause of what you are seeing and it is not specific to the speech1_copy example.

0 matthavener over 16 years ago in reply to Juan Gonzales

Prodigy 50 points

Do you know when TI's going to fix the problem?

0 Juan Gonzales over 16 years ago in reply to matthavener

TI__Mastermind 37340 points

We are investigating this. One of the potential work-arounds we first tried appeared to break something else, hence this is still under investigation. I am told that in the mean time, we have added a note in the releases notes warning of this DSPLINK limitation. As I find out more information, I will add the this thread.

0 Juan Gonzales over 16 years ago in reply to matthavener

TI__Mastermind 37340 points

The SIGTERM issue has been fixed. It will be available in DSPLINK 1.6 version which will likely be included in a future DVSDK. If you cannot wait, you can download the latest DSPLINK here

https://www-a.ti.com/downloads/sds_support/targetcontent/link/index.html

However, I always caution customer with respect to upgrading individual software components. If you can wait for next DVSDK, that would be ideal and ensure adequate testing for software compatibility among the various software components.

0 MinhQuan over 16 years ago in reply to Juan Gonzales

Prodigy 40 points

The new dsplink 1.6 and codec engine 2.21 are not compilable under Montavista Profession Linux 4.0.1.

Could TI give us some hints/tips to make codec engine 2.21 compilable under Montavista Profession Linux 4.0.1?

We have products that are about to release. It's not possible to upgrade to MV 5.0 at this time.

0 Juan Gonzales over 16 years ago in reply to MinhQuan

TI__Mastermind 37340 points

DSPLINK 1.6 does require MV Pro 5; is there a good reason you need to use dsplink 1.6; can you perhaps live with older revision of DSPLINK and Codec Engine found in our official DVSDK releases.

Future DVSDK release will incorporate DSPLINK 1.6 along with MV Pro 5.

0 MinhQuan over 16 years ago in reply to Juan Gonzales

Prodigy 40 points

We try to fix the problem that hangs on signal as stated at the beginning of this thread. Since you mentioned that DSPLINK 1.6 would fix the problem, that's why it's necessary for us to upgrade our current product to DSPLINK 1.6 and Codec Engine 2.21. But the new version is not compatible with the MV 4.0.1. I hope TI has the solution for this problem in MV 4.0.1.

0 Juan Gonzales over 16 years ago in reply to MinhQuan

TI__Mastermind 37340 points

Was the SIGTERM signal part of the original speech1_copy example?

We do recognize that there was an issue with SIGTERM signal and we are working to fix this (hence 1.6 version of DSPLINK); unfortunately, we do no have a full DVSDK solution at this time. A future DVSDK release will incorporate MVpro5 and DSPLINK 1.6, but this is not available yet.

0 MinhQuan over 16 years ago in reply to Juan Gonzales

Prodigy 40 points

Codec Engine 2.21 does include DSPLINK 1.6. This is the package version that we hope will fix the SIGTERM issue. But Codec Engine 2.21 cannot be compiled with MV 4.0.1. We want to fix the problem and stay with MV 4.0.1. We have products that are about to release, and it's not possible to upgrade to MV 5.0 at this time.

Processors

Processors forum

speech1_copy example hanging on signal