OpenMAX VFCC capture port configuration

Can someone at TI please provide some support for this and respond?

24 hours on and still no reply from TI.

Anyone?

I assume you are using EZSDK. The VFCC configuration is explained here:

ti-ezsdk_dm814x-evm_5_05_01_04/component-sources/omx_05_02_00_46/src/ti/omx/docs/OpenMax_DM814x_UserGuide.pdf section 2.2 Video Frame Capture Component (VFCC)

Regards,

Pavel

Hi Pavel,

Yes I am using EZSDK 5.05.01.04.

I have looked at the document you refer to but i'm still unclear on how to configure the ports for VFCC capture.

In the OMX_PARAM_VFCC_HWPORT_ID struct there is a member called OMX_VIDEO_CAPTURE_HWPORT_ID eHwPortId. This can be set to one of the ports mentioned in my original post.

There is another struct called OMX_PARAM_CTRL_VIDDECODER_INFO. This has a member called OMX_CTRL_VID_DECODER_ID videoDecoderId, which can be set to one of:

OMX_VID_DEC_Unused = 0x00000000,
OMX_VID_DEC_SII9135_DRV,
OMX_VID_DEC_TVP7002_DRV,
OMX_VID_DEC_TVP5158_DRV,
OMX_VID_DEC_TIExtensions = 0x6F000000,
OMX_VID_DEC_VendorStartUnused = 0x7F000000,
OMX_VID_DEC_Max = 0x7FFFFFFF

In the capture_encode OMX sample app the following is set:

sHwPortId.eHwPortId = OMX_VIDEO_CaptureHWPortVIP1_PORTA;

sVidDecParam.videoDecoderId = OMX_VID_DEC_TVP7002_DRV;

So this would lead me to believe that the TVP7002 is connected to VIP1 Port A.

If I set the following:

sVidDecParam.videoDecoderId = OMX_VID_DEC_TVP5158_DRV;

Then what port should I use in the sHwPortId.eHwPortId setting?

Is this defined somewhere?

Thanks,

Steven

Are any TI employees able to answer this question?

TI, please respond!

Hi,

eHwPortId depends on where TVP5158 is connected. Can you please tell us which port you are using for TVP5158 input?

Regards,

Brijesh Jadav

Hi,

These isnt a TVP5158 on the DM8148 EVM but i'm trying to see if, by selecting OMX_VID_DEC_TVP5158_DRV as the videoDecoderId if I can get the TVP5147 working. I dont know which port OMX uses to point to the TVP5147. I was hoping someone at TI could tell me?

Thanks,

Steven

Hi Steven,

These two are completely different decoders, requires different configuration. Why don't you use TVP5147 itself. check the OMX/ezSDK use guide/release notes and if it supports TVP5147, you could directly set decoder id to 5147.

Thanks,

Brijesh Jadav

Hi,

There is no decoder ID for the 5147. The only options are:

OMX_VID_DEC_Unused = 0x00000000,
OMX_VID_DEC_SII9135_DRV,
OMX_VID_DEC_TVP7002_DRV,
OMX_VID_DEC_TVP5158_DRV,
OMX_VID_DEC_TIExtensions = 0x6F000000,
OMX_VID_DEC_VendorStartUnused = 0x7F000000,
OMX_VID_DEC_Max = 0x7FFFFFFF

Which seems a bit silly given the DM8148 EVM has a TVP5147 and NO TVP5158.

Thanks,

Steven

So it looks like similar to the V4L2 route, there is no support for the standard definition decoder (TVP5147) in the OMX stack provided by TI. However, I have V4L2 system working fine with the standard definition decoder (TVP5151 on our custom board), so is it trivial to the get OMX to use the driver?

On our custom board, the TVP7002 is connected to VIN0 and TVP5151 to VIN1. 

Can anyone from TI provide a straightforward and quick answer to this?

~Ashwin