• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 102 subscribers
  • Views 936 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

DM365 board connect with bt.656 video input

Jing1
Intellectual 580 points
hi,
  I have a cmos sensor(MT9V136) connected with DM365 board that can output the video of ITU-R BT.656 (YCbCr) formats (progressive scan).
The MT9V136 outputs interlaced-scan images at 30 or 25 fps, supporting both NTSC and PAL video formats.
 
  However when I configure the VPFE driver and application to interlaced BT.656 format(format PAl or NTSC) input mode, I get some register value, that are MODESET:0x2084 CCDCFG:0x812 REC656IF:0x3.
By Setting pixel format to CCDC_PIXFMT_YCBCR_8BIT, I have a problem in my output image,which is the same as display on screen from resize.

My output image is following:
Btw: When i connect other cmos sensores(MT9P031 & MT9D131) in my DM365 board, there is no unusual image.
pic:1
this image is focus on some lights,as you can identify them.
 
pic:2
this image is focus on a colour chart,and the color can be identified correctly, but they are dirty.
 
1,What is problem result in these unusual images?
2,I get the image that is not the full NTSC or PAL resolution,missing some view.
Waitting for your help,thanks.
  • 0
    TI__Mastermind 19985 points

    Katee,

    I would suspect the hardware connections between your sensor and DM365. If the video data lines are swapped or not connected in the correct order, such result can happen. Is your sensor configured to give out 8 bits per pixel clock?

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Intellectual 580 points

    Anshuman,

    I check the hardware connections between my sensor and DM365.then I check my sensor configuration(8 bits per pixel) at the same time.It is all right.

    Are there other case can cause this result? or how to debug it.

    Thanks

  • 0
    TI__Intellectual 1870 points

    Hi

     It is difficult to tell the cause based on the images.

    Are the images from YUV input or from Display (or after resizer)?

    For tracking, I recommend for you to capture the input YUV (after ISIF) if you didn't.

    If you did, then please check the sensor spec and check whether you can check the sensor output in different way.

    Aptina may have some tools.

     

    regards,

    Sang-Yong 

     

     

  • 0 in reply to SANG-YONG
    Intellectual 580 points

    Hi ,  Sang-Yong ,

    Thanks for  your  help .  Now the problem has been resolved , some hardware  errors. 

    I do appreciate all the help . Thanks again.

    regards,

    katee.