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.

MT9V136 videostream (imager) capturing problem.



Hi.

I am trying to capture a composite video signal from MT9V136 camera (imager output) using the modified demo application "encode " from DVSDK, running on DM36x EVM board. Unfortunately, the capture of the stream does not happen - the capture thread (captureThrFxn) is stoped in the Capture_get () function - videobuf_waiton() function calls the scheduler in line:

if (vb->state == STATE_ACTIVE || vb->state == STATE_QUEUED)
{
   schedule();
}

I am out of ideas how to debug it, please, give me some idea!

Thank you & Best Regards,

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

P.S. My setup is:

Linux kernel version is 2.6.18, DVSDK version is 2.10.00.17

MT9V136 video outputs are connected to dm365 Y[7..0] inputs

MT9V136 video outputs measurement (oscilloscope):

PIXCLK 27 MHz
HSYNC 25 Hz
VSYNC 15.6 KHz

Lines Y0..Y7 have random signal.

DM365 registers value:

DM365_CPLD_REGISTER3 0x42  (IMAGER)
MODESET     0x00002004
REC656IF     0x00000003
CCDCFG       0x00000812
PINMUX0       0x00FD0000

 

  • can you pl dump all register contents of ISIF(CCDC)?

  • Thank you!.

    There is the dump:

    SYNCEN      0x00000000
    MODESET     0x00002004
    HDW         0x00000000
    VDW         0x00000000
    PPLN        0x00000000
    LPFR        0x00000000
    SPH         0x00000000
    LNH         0x000004FF
    SLV0        0x00000001
    SLV1        0x00000001
    LNV         0x000001DF
    CULH        0x0000FFFF
    CULV        0x000000FF
    HSIZE       0x00000028
    SDOFST      0x00000000
    CADU        0x00000000
    CADL        0x00000000
    CCOLP       0x00000000
    CRGAIN      0x00000200
    CGRGAIN     0x00000200
    CGBGAIN     0x00000200
    CBGAIN      0x00000200
    COFSTA      0x00000000
    FLSHCFG0    0x00000000
    FLSHCFG1    0x00000000
    FLSHCFG2    0x00000000
    VDINT0      0x000001DF
    VDINT1      0x000000F1
    VDINT2      0x00000000
    CGAMMAWD    0x00000000
    REC656IF    0x00000003
    CCDCFG      0x00000812
    DFCCTL      0x00000000
    VDFSATLV    0x00000000
    DFCMEMCTL   0x00000000
    DFCMEM0     0x00000000
    DFCMEM1     0x00000000
    DFCMEM2     0x00000000
    DFCMEM3     0x00000000
    DFCMEM4     0x00000000
    CLAMPCFG    0x00000000
    CLDCOFST    0x00000000
    CLSV        0x00000000
    CLHWIN0     0x00000000
    CLHWIN1     0x00000000
    CLHWIN2     0x00000000
    CLVRV       0x00000000
    CLVWIN0     0x00000000
    CLVWIN1     0x00000000
    CLVWIN2     0x00000000
    CLVWIN3     0x00000000
    FMTSPH      0x00000000
    FMTLNH      0x00000000
    FMTSLV      0x00000000
    FMTLNV      0x00000000
    FMTRLEN     0x00000000
    FMTHCNT     0x00000000
    CSCCTL      0x00000000
    CSCM0       0x00000000
    CSCM1       0x00000000
    CSCM2       0x00000000
    CSCM3       0x00000000
    CSCM4       0x00000000
    CSCM5       0x00000000
    CSCM6       0x00000000
    CSCM7       0x00000000

  • What does sensor is configured to output? NTSC? PAL? VIDINT register setting look wrong to me. For NTSC, line number should not exceed (480)/2 - 1 and for PAL, (576/2) -1. Pl refer to section 5.4.3.1 of VPFE user guide.

    VDINT0      0x000001DF
    VDINT1      0x000000F1

     

  • Thank you, I should check the issue!

  • Ok, my camera produced BT656 output format: progressive YCbCr 640x480 so VDINT0 and VDINT1 are conigured as:

    VDINT0 = 01DF = 479 i.e. image_win->height (480) - 1
    VDINT1 = 00F1 = 241 i.e. 1 + image_win->height (480) / 2

     

  • sinomatic,

    YCbCr 640x480 progressive is not BT656 standard.  Pl refer to BT.656 spec. You can set REC656IF register only in case of BT.656 input(NTSC/PAL).

     

  • Thank you!

    I'll change the camera settings to get a PAL signal and check BT.656 again.