Hi,
I am integrating the DM355 MP4V Encoder codec into my application. I have successfully integrated the DM355 JPEG Encoder codec (works great!) and I am reusing a lot of the same framework code for MP4V. I can successfully create and allocate resources for the codec, and I have called control() with parameters and dynamic parameters with success. When I call process() with my first video frame, the codec does not appear to make forward progress. When I monitor the interrupt status, neither VENCINT or ASQINT occur. However, both IMXINT and IMCOPINT occur.
My system is not based on Linux, and I have been unsuccessful in determining what the exact behavior of VICP_wait should be in response to the above interrupts. For the JPEG codec, VICP_wait should respond to ASQINT for correct operation (we determined this from the older DVSDK code, comments, and empirically.) For MP4V, I have not found a way of determining which interrupts to respond to! Is anyone familiar with this part of the code, can you point me in the right direction?
(The test app code provided in the DVSDK has a funciton Host_int_handler() which is called in response to a VICP interrupt. I cannot find any other reference to this function in the DVSDK.)
