lkml.org 
[lkml]   [2012]   [Mar]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    SubjectRe: I.MX35 PDK
    From
    On 3/8/12, Alex Gershgorin <alexg@meprolight.com> wrote:
    ...
    > Yes this I2C problem, all I2C slave device need response to Host CPU by
    > pulls I2C data bus to low, in other words generate ACK, the clock pulse for
    > the acknowledge bit is always created by the bus master.
    >
    > In this case, the camera tries to reset the data bus and generate an ACK,
    > but the voltage drops to the area of two volts, although it should be reset
    > to zero.
    > I replaced R172 with 10K on CPU board and got a good result, but there are
    > other surprises

    Ok, good.

    Can you try to change the I2C1 pad settings in software, so that the
    board can work with the original resistor?

    >
    > Linux video capture interface: v2.00
    > soc-camera-pdrv soc-camera-pdrv.0: Probing soc-camera-pdrv.0
    > mx3-camera mx3-camera.0: MX3 Camera driver attached to camera 0
    > ov2640 0-0030: ov2640 Product ID 26:42 Manufacturer ID 7f:a2
    > i2c i2c-0: OV2640 Probed
    > mx3-camera mx3-camera.0: MX3 Camera driver detached from camera 0
    > dmaengine: failed to get dma1chan0: (-22)
    > dmaengine: failed to get dma1chan1: (-22)
    > dmaengine: failed to get dma1chan2: (-22)
    > dmaengine: failed to get dma1chan3: (-22)
    > dmaengine: failed to get dma1chan4: (-22)
    > dmaengine: failed to get dma1chan5: (-22)
    > dmaengine: failed to get dma1chan6: (-22)
    > dmaengine: failed to get dma1chan7: (-22)
    > dmaengine: failed to get dma1chan8: (-22)
    > dmaengine: failed to get dma1chan9: (-22)
    > dmaengine: failed to get dma1chan10: (-22)
    > dmaengine: failed to get dma1chan11: (-22)
    > dmaengine: failed to get dma1chan12: (-22)
    > dmaengine: failed to get dma1chan13: (-22)
    > dmaengine: failed to get dma1chan14: (-22)
    > dmaengine: failed to get dma1chan15: (-22)
    > dmaengine: failed to get dma1chan16: (-22)
    > dmaengine: failed to get dma1chan17: (-22)
    > dmaengine: failed to get dma1chan18: (-22)
    > dmaengine: failed to get dma1chan19: (-22)
    > dmaengine: failed to get dma1chan20: (-22)
    > dmaengine: failed to get dma1chan21: (-22)
    > dmaengine: failed to get dma1chan22: (-22)
    > dmaengine: failed to get dma1chan23: (-22)
    > dmaengine: failed to get dma1chan24: (-22)
    > dmaengine: failed to get dma1chan25: (-22)
    > dmaengine: failed to get dma1chan26: (-22)
    > dmaengine: failed to get dma1chan27: (-22)
    > dmaengine: failed to get dma1chan28: (-22)
    > dmaengine: failed to get dma1chan29: (-22)
    > dmaengine: failed to get dma1chan30: (-22):

    This is something that needs to be solved, but it does not prevent the
    camera to work though.

    On my mx31pdk I get the same dmaengine errors and the ov2640 does work fine.

    I think you can go ahead and try to use the camera on the mx35pdk now.

    You can try:

    gst-launch -v v4l2src device=/dev/video0 !
    video/x-raw-yuv,width=320,height=240,framerate=25/1 ! ffmpegcolorspace
    ! fbdevsink

    Regards,

    Fabio Estevam


    \
     
     \ /
      Last update: 2012-03-08 12:29    [W:0.025 / U:4.348 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site