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.
hello , i have omap-l138 and tvp5150 and i want to capture a frame with yavta or gstreamer (or anything that works)
my sdk version is mcsdk_1 and using linux 3.3.0.
so for that i copied some config from board config of da850 for register vpif and tvp5150.
i copied everything related to vpif and tvp514x and changed all tvp514x to tvp5150. (i attached my board config).
after these changes,vpif and tvp5150 successfully starts and i have video0 and video1 in my dev directory.
but when i run following commands it hangs:
v4l2-ctl --device /dev/video0 -s 0x4
./yavta -F /dev/video0 -c 1 -i 0
this is dmesg output for last command: (i attached full output log)
and same thing happens to gstreamer and it stuck.
what am doing wrong ? where should i look for the problem?
Please make sure you read the forum guidelines first.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Yordan Kovachev:
In reply to dzhou:
In reply to Arash fz:
Issue may be the switch from TVP514x to TVP5150.
Those two encoder are pretty different, for instance issue may be here related to the fact that
- TVP514x generates V4L2_FIELD_INTERLACED video buffer
- TVP5150 generates V4L2_FIELD_ALTERNATE video buffer
Refer to https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/field-order.html for more details.
In summary - V4L2_FIELD_INTERLACED means both fields is presented in a single buffer
Whereas V4L2_FIELD_ALTERNATE means each field is presented as separate buffer.
The obvious issue here as far as QBUF is concerned is the buffer geometry (or size) between the two types.
For the VPIF and TVP5150 to work together, they both need to support the same interlaced format. Please check your code around that.
In reply to manisha:
thanks for your quick reply.
i will check what you mentioned and post the result.
Please read OMAPL138 TRM on conditions when VPIF generates interrupts. If the conditions aren't met, then interrupt won't be generated. Typically that may mean, VSYNC signal not seen or the VPIF didn't receive the number of lines/pixels as configured etc. Please read the VPIF chapter of TRM with respect to interlace capture capabilities and how video signals are expected by it and conditions on which it generates the interrupts.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.