RE: I.MX35 PDK

Thanks for your response, > 1. Back resistor 172 to the default value. > > 2. Removed the resistor 146, through which a voltage was applied from a PMIC > (EXT_3V) on "CMOS_VIO". > > 3. Connecting a resistor 147 which supplies power from the LDO_3V3 on > "CMOS_VIO". > >The camera on the FSL BSP wo

Re: I.MX35 PDK

On 3/12/12, Alex Gershgorin wrote: > 1. Back resistor 172 to the default value. > > 2. Removed the resistor 146, through which a voltage was applied from a PMIC > (EXT_3V) on "CMOS_VIO". > > 3. Connecting a resistor 147 which supplies power from the LDO_3V3 on > "CMOS_VIO". The camera on the FSL

Re: I.MX35 PDK

On 3/8/12, Alex Gershgorin wrote: > Setting pipeline to PAUSED ...mx3-camera mx3-camera.0: MX3 Camera driver > attached to camera 0 > /GstPipeline:pipeline0/GstV4l2Src:v4l2src0.GstPad:src: caps = > video/x-raw-yuv, format=(fourcc)UYVY, framerate=(fraction)25/1, > width=(int)320, height=(int)240,

RE: I.MX35 PDK

>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

RE: I.MX35 PDK

Hi Guennadi, Thanks for you comments... >>>Hi Alex >>>Why is the cc-list mangled again? Why is the V4L list dropped again? >>>What's so difficult about hitting the "reply-to-all" button? You are absolutely right, I hope that now the cc-list valid. > Hi Fabio, > > Thanks for you response... >

RE: I.MX35 PDK

> 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 th

RE: I.MX35 PDK

Hi Alex Why is the cc-list mangled again? Why is the V4L list dropped again? What's so difficult about hitting the "reply-to-all" button? On Thu, 8 Mar 2012, Alex Gershgorin wrote: > Hi Fabio, > > Thanks for you response... > > > in spite of this I get from ov2640 driver error > > Here Linux