• State
  • Locked Locked
  • Replies 0 replies
  • Subscribers 98 subscribers
  • Views 187 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.

DSP side development in EZSDK

longxiao zhang
Intellectual 500 points

Hi,

I'm working with EZSDK 5.02. I'm very curious about how ARM app invokes DSP side algorithm.

For example, in 'ti/omx/demo/C6xtest':

        OMX_GetHandle( &pAppData->pVlpbHandle,
                       ( OMX_STRING ) "OMX.TI.C67X.VLPB", pAppData->vlpbILComp,
                       &pAppData->pCb );

Looks like we use this to invoke DSP side algorithm.

And I also know there's an omx component name 'ti/omx/comp/vlpb', which is compiled by cl6x. It looks as if this is the DSP side algorithm. I examined the makefile and only found:

MODULE_NAME = vlpb

I guess this makes DSP side alg can be seen by ARM app.

My question is: how we make the link between ARM app call 'OMX.TI.C67X.VLPB' and DSP side 'ti/omx/comp/vlpb'? And how we use openmax interface like OMX_SetParameter(), then DSP side OMX_TI_VLPB_GetParameter() is called? What rules should I obey, if I want to do DSP development?