• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 479 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

OMAP 4 Encoder throw an OMX_EventError (data1 = 0x80001001 anda data2 = 0) on restart encoder case .

Podun Yu
Prodigy 10 points

Hello,

This is the configuartion I am using:-

Android Release:- IcecreamSandwich 4.0.4 (MR1.1)

Profile:-BaseLine

Resolution: -1080p(Encoder)

Board:-Blaze tablet 2(OMAP4460 platform

When I make video call from Blaze to Video conferencing endpoint ,it works for the first time, and when after disconnect and reconnect the video call

I found encoder hangs(does not start) . and the encoder throw an OMX_EventError (data1 = 0x80001001 , data2 = 0) .

I am getting omx camera buffer (12bytes) and send this to encoder , and i found something different from log on dependency 

 camera using  :

02-21 06:52:42.069 E/CameraHal(  127): (7ed680)   hardware/ti/omap4xxx/camera/OMXCameraAdapter/OMXAlgo.cpp:1153 setVFramerate - Error while setting VFR min = 5, max = 27, error = 0x80001005

and something else  maybe encoder using

02-21 06:53:20.506 D/DOMX    (  127): hardware/ti/domx/domx/omx_proxy_common/src/omx_proxy_common.c:1444 __PROXY_SetConfig() 

 

and i have check ducati log and it looks similar describe on topic http://e2e.ti.com/support/omap/f/849/t/204223.aspx

As there is too much logs on application , i simplify the logs and attach it .

0513.APP-Log-simplify.log

3348.trace1-ducati.log

 

 

 

 

 

  • 0
    TI__Intellectual 805 points

    Hi Yu,

    It seems that the encoder crash is caused by incorrect parameter set - especially VFR ranges.The 0x80001005 is standart OMX error - "OMX_ErrorBadParameter".
    It's returned by OMX_SetConfig(mCameraAdapterParameters.mHandleComp,(OMX_INDEXTYPE)OMX_TI_IndexConfigVarFrmRange,&vfr);
    in OMXAlgo.cpp (hardware/ti/omap4xxx/camera/OMXCameraAdapter).

    You should find out why the ranges are invalid...As a quick workaround you could skip the section with setting VFR ranges(as removing it's functionality), and try the use case again.