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.

saMmapLoopback.c

Other Parts Discussed in Thread: TVP5146M2, TVP5146

I am using:

1. OMAP35x EVM rev G board.

2. PSP.02.01.03.11

3. CodeSourcery arm-2009q1 toolcchain.

I configured with TVP514x support, omap3 camera support in kernel configuration.

After EVM was booted, I checked dmesg and found the TVP514x is initialized as omap3 camera.

When I ran it, I got:

========================================================

root@omap3evm:/opt# ./saMmapLoopback -u 0
<6>tvp514x 3-005c: tvp5146m2 found at 0xb8 (OMAP I2C adapter)
tvp514x 3-005c: tvp5146m2 found at 0xb8 (OMAP I2C adapter)

Capture: Opened Channel
Capture: Current Input: COMPOSITE
VIDIOC_S_INPUT: Invalid argument
Error in opening capture device for channel 0

=========================================================

If I changed to '-u 1' as usb cam, I got:

==========================================================

root@omap3evm:/opt# ./saMmapLoopback -u 1
<6>tvp514x 3-005c: tvp5146m2 found at 0xb8 (OMAP I2C adapter)
tvp514x 3-005c: tvp5146m2 found at 0xb8 (OMAP I2C adapter)

Capture: Opened Channel
Capture: Current Input: COMPOSITE
Capture: Input changed to: COMPOSITE
Capture: Capable of streaming
Capture: Number of requested buffers = 3
Capture: Init done successfully


Display: Opened Channel
Display: Capable of streaming
Display: Number of requested buffers = 3
Display: Init done successfully

Display: Stream on...
Capture: Stream on...

Display: Stream off!!
Capture: Stream off!!

Loopback Successful

=========================================

It can run as 320x240 usbcam.  Can anyone run saMmapLoopback

with TVP514x as NTSC mode of PAL mode?

Jie Deng

  • Hi Deng,

    The above error message means, the TVP5146 video decoder is not able to lock the input signal. Have you connected the input to the MDC (Multi-media daughter card)? Also I believe you are using <Rev-D revision of EVM's here.

    Also the application tries to switch over to the input, if it detects S-Video input then it tries to switch over to CVBS and vice versa so you also may want to comment this.

    Thanks,

    Vaibhav

  • Hi Vaibhav,

    Thank you very much for your help.

    1.  I am using omap35x evm rev. G board.

    2. I am feeding CVBS with NTSC signal.  I do not use S-Video.

    Regards.

    Jie Deng

  • Deng,

    Is there any specific reason behind using PSP2.x release? Can you migrate to PSP03.x release?

    Natively, PSP2.x release supports <Rev-D revision of EVM's with MDC (Multi-media Daughter card). If I remember correctly I think the support for TVP5146 on RevG version of EVM got added lately in PSP03.x release. So I would suggest you to migrate to PSP03.00.01.06 release which is latest from PSP.

    Thanks,

    Vaibhav

  • Hi Vaibhav,

    I am using psp-02.01.03.11 which supports both old boards and Rev. G board.  See the mux code in arch/arm/mach-omap2/board-omap3evm-dc-v4l.c.

    I am working in a driver for Aptina's sensor.  I tried to use saMmapLoopback.c to try the driver code.

    I can move to psp-03.00.01.06.  I need to make some change in driver code to associate the change of V4L2 code in psp-03.00.01.06.

    In psp-03.00.01.06/Rev.G board/CVBS(NTSC)/LCD display combination, can you run saMmapLoopback.c?

    I can run it at this combination.  Howeve, the video at LCD is miss alligned?  Can you try it?

    Many thanks in advance.

    Jie Deng 

  • Hi Vaibhav,

    I figured out the miss-alligned issue.  The code was hard code with PAL support.

    Jie

  • Jie,

    I am not quite sure about hardcoding to PAL, the saMmapLoopback application doesn't hardcode the standard. It barely enumerates it what hardware has detected.I just verified with PSP02.x release package and I don't think it is hardcoded to PAL.

    Thanks,

    Vaibhav