syslink failing with gstreamer pipes -- need complete restart for M3 firmware?

HI all,

we are seeing syslink errors with duplicate entries and such, if in a real system we are using e.g. kill <process> -9, which is more aggressive than just <ctrl>c, which could on a gst-launch clean up the pipe and also bring the M3 firmware into a good state to restart another gstreamer pipe. On e.g kill <process> -9, it is very likely that while the process is clean up, the M3 firmware sits in a state where the MessageQs are still all up, so when the next gstreamer pipe starts MessageQ_create will run into the Nameserver duplicate issues. I think what we really need is a good way to completely restart the M3 firmware (without unloading/loading it), just a restart signal/API. Is this available??

Or is there a best recommended way to prevent the Nameserver issues with a proper clean-up.

The Nameserver issues are reported here also

http://e2e.ti.com/support/embedded/linux/f/354/t/181466.aspx

There is a post to try to "fix" the Nameserver issues, but one seems to assume that if an existing MessageQ exists already, then just use it. The statement was made that it looks like a "hack", so we are looking for proper clean-up.

http://e2e.ti.com/support/embedded/linux/f/354/t/227388.aspx

Here is our log that shows duplicates for

syslink duplicate name ServiceMgr_inMsgs

syslink duplicate name ServiceMgr_outMsgs

syslink duplicate name uiaMaster

*** MessageQ_registerHeap: Specified heap is already registered.!

Error [0xfffffffc] at Line no: 1685 in file /home/builder/autobuilds/default/openembed/touchlink.1-tmp/work/touchlink-none-linux-gnueabi/ti-syslink-2_10_03_20-r24j/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/MessageQ.c

*** MessageQ_registerHeap: Specified heap is already registered.!

Found SGX/MBX driver, enabling FullClearOnEveryFrame

Found v1.4 driver, enabling brokenTexSubImage

*** NameServer_add: duplicate entry found!enFBOReadBack

Error [0xfffffffe] at Line no: 1055 in file /home/builder/autobuilds/default/openembed/touchlink.1-tmp/work/touchlink-none-linux-gnueabi/ti-syslink-2_10_03_20-r24j/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/utils/hlos/knl/NameServer.c

*** MessageQ_create: Failed in NameServer_addUInt32

Error [0xffffffff] at Line no: 738 in file /home/builder/autobuilds/default/openembed/touchlink.1-tmp/work/touchlink-none-linux-gnueabi/ti-syslink-2_10_03_20-r24j/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/MessageQ.c

Assertion at Line no: 425 in /home/builder/autobuilds/default/openembed/touchlink.1-tmp/work/touchlink-none-linux-gnueabi/ti-syslink-2_10_03_20-r24j/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/syslink/ipc/hlos/knl/Linux/MessageQDrv.c: (cargs.args.create.handle != NULL) : failed

*** NameServer_add: duplicate entry found!

*** MessageQ_create: Failed in NameServer_addUInt32

*** NameServer_add: duplicate entry found!

*** MessageQ_create: Failed in NameServer_addUInt32

Assertion at Line no: 1244 in /home/builder/autobuilds/default/openembed/touchlink.1-tmp/work/touchlink-none-linux-gnueabi/ti-syslink-2_10_03_20-r24j/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : failed