Could a TI employee please confirm that dual capture will function correctly under EZSDK 5_04_00_11 by creating two handles to the "OMX.TI.VPSSM3.VFCC" component?
The first component remains on the tvp7002, while the second is intended to use the tvp514x. Each should have a 16 bit bus on separate inputs. Yes, I know the tvp514x isn't supported in the ezsdk - I have manually taken control over the I2C bus because the M3 support for devices is beyond insufficient and I fixed a kernel bug in the platform code to get that device talking in the first place. It turns out that the chip is held in indefinite reset by default. If anybody would like to know the exact line number, I'm happy to look it up.
For the second capture component, I have basically duplicated the tvp7002 example from capture-encode. Should the buffer allocation be setup as follows:
eError = OMX_AllocateBuffer (pAppData->pCapHandle514x,
&pAppData->capILComp514x->outPortParams->pOutBuff[i],
OMX_VFCC_OUTPUT_PORT_START_INDEX + 1, pAppData,
pAppData->capILComp514x->outPortParams->nBufferSize);
The big difference here is whether or not I should be using OUTPUT_PORT + 1 for the index since this component should represent input 2. This results in a "Capture: Error in OMX_AllocateBuffer() : OMX_ErrorBadParameter" error. If I use OMX_VFCC_OUTPUT_PORT_START_INDEX, I'm having some other erratic behavior / crashes when it comes time to cleanup on shutdown. I'm assuming the latter is due to conflicting with the original port's buffers?