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.

OMX capture-encode demo problems in 5.04?

Hello All -

I'm having trouble with multiple executions of the OMX capture_encode_a8host_debug.xv5T on 5.04.   The first time I execute the demo, it runs successfully and generates the h264 encoded file.  The second time, I get a syslink assertion failure:

Capture-Encode example 
===============================
 OMX_Init completed
 UIAClient is ready to send a UIA configuration command
UIAClient received UIA_CONFIGURE_ACK
UIAClient is done sending requests
UIAClient is ready to send a UIA configuration command
UIAClient received UIA_CONFIGURE_ACK
UIAClient is done sending requests
 openeing file
 capture compoenAssertion at Line no: 419 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../d
ent is created
capture_encode_a8host_debug.xv5T: OmxRpc.c:624: OmxRpc_Instance_init: Assertion `(OmxRpc_errorNone == retVal)' failed.
Aborted

 

 Ignoring this and trying a third time, I see asserCapture-Encode example

===============================
Assertion at Line no: 419 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/sysld
Assertion at Line no: 419 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/sysld
Assertion at Line no: 419 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/utils/hlos/knl/Linux/../../../../../../ti/sysld
Assertion at Line no: 1244 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : fd
Assertion at Line no: 700 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (queueId != MessageQ_d
ServiceMgr_prime: MessageQ_put failed: status = 0xfffffffe
Assertion at Line no: 1244 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : fd
Assertion at Line no: 700 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (queueId != MessageQ_d
ServiceMgr_prime: MessageQ_put failed: status = 0xfffffffe
Assertion at Line no: 1244 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : fd
Assertion at Line no: 700 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (queueId != MessageQ_d
ServiceMgr_prime: MessageQ_put failed: status = 0xfffffffe
Assertion at Line no: 1244 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : fd
Assertion at Line no: 700 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (queueId != MessageQ_d
ServiceMgr_prime: MessageQ_put failed: status = 0xfffffffe
Assertion at Line no: 1244 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : fd
Assertion at Line no: 700 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (queueId != MessageQ_d
ServiceMgr_prime: MessageQ_put failed: status = 0xfffffffe
Assertion at Line no: 1244 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : fd
Assertion at Line no: 766 in /home/z3/z3-netra-RPS-20120730/ezsdk/component-sources/syslink_2_10_03_20/packages/ti/syslink/ipc/hlos/usr/MessageQ.c: (handle != NULL) : fad
Segmentation faulttion failures and seg fault:

 

On 5.03 I could run the demo multiple times without incidient.  I can also confirm I'm running OMX friendly firmware (not the V4L2 stuff) with i2c_mode=1.

Did the OMX shutdown / clean-up stuff change in 5.04 without the demos getting updated?  What am I missing?

Thanks,

Dave