• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 324 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

How to configed the OV7620 for DM355?

zhenghao chen
Prodigy 90 points
Other Parts Discussed in Thread: TVP5146, OMAP-L138

hi,all

I use the DM355 and DVSK 2.0 to develop products I use the OV7620 to replace the TVP5146.

0V7620 has been configured BT656 mode (9 lines).In the DAVINCI_VPBE.c ,i added support for OV7620,  the OV7620 configure for  the CCDC same as TVP5146 .But I found that did not produce VINT0 suspended, but there is signal output with OV7620.For the ardware connection, I connected YIN0.7 and PCLK.

i use encodedecode to test OV7620. I modify the code to support OV7620.

but the console only dispaly

ARM Load: 1% Video fps: 0 fps Video bit rate: 0 kbps Time: 00:00:01 Demo: Encode Decode Display: D1 NTSC Video Codec: MPEG4 SP Video Resolution: 720x576 
 
ARM Load: 1% Video fps: 0 fps Video bit rate: 0 kbps Time: 00:00:02 Demo: Encode Decode Display: D1 NTSC Video Codec: MPEG4 SP Video Resolution: 720x576

  • 0
    TI__Mastermind 41665 points

    In this case the first area I would check is that the OV7620 is actually outputting a valid bt.656 stream, if there are never any proper embedded syncs coming across the video bus than the VPFE will basically hang waiting for a sync. If you are sure that the OV7620 is providing proper bt.656 output than you may want to put some more debugging printk statements in the driver code that you modified for the OV7620 to make sure the driver is not getting hung up somewhere, for example if there was some code left that was still expecting the TVP5146 and is hanging on some I2C register access.

  • 0 in reply to Bernie Thompson TI
    Prodigy 50 points

    do you solve the problem?

    I  also encounter the same problem in the OMAP-L138 platform and OV7725 CMOS senser

    can you help me ?

    I am grateful for your help!