I.MX35 PDK

12 messages, 4 authors, 2012-03-08 · open the first message on its own page

I.MX35 PDK

From: Fabio Estevam <hidden>
Date: 2012-03-06 15:26:08

Alex Gershgorin wrote:

Hi Fabio,

 

How I can get information about accesses to CMOS_RST_B and CSI_PWDN bits
of MC9S08DZ60 processor.

I need address of this register and bits mapping in this register.

You can check Freescale kernel to get this information:
http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=shortlog;h=refs/heads/imx_2.6.31

Search for "pmic_gpio_set_bit_val"

Wu Guoxing submitted the mc9s08dz60 driver patch to mainline:
drivers/gpio/gpio-mc9s08dz60.c

Regards,

Fabio Estevam

I.MX35 PDK

From: Alex Gershgorin <hidden>
Date: 2012-03-06 15:35:51

Thanks Fabio :-) 

-----Original Message-----
From: Fabio Estevam [mailto:fabio.estevam at freescale.com] 
Sent: Tuesday, March 06, 2012 5:26 PM
To: Alex Gershgorin
Cc: linux-arm-kernel at lists.infradead.org; kernel at pengutronix.de; festevam at gmail.com
Subject: Re: I.MX35 PDK

Alex Gershgorin wrote:

Hi Fabio,

 

How I can get information about accesses to CMOS_RST_B and CSI_PWDN bits
of MC9S08DZ60 processor.

I need address of this register and bits mapping in this register.

You can check Freescale kernel to get this information:
http://opensource.freescale.com/git?p=imx/linux-2.6-imx.git;a=shortlog;h=refs/heads/imx_2.6.31

Search for "pmic_gpio_set_bit_val"

Wu Guoxing submitted the mc9s08dz60 driver patch to mainline:
drivers/gpio/gpio-mc9s08dz60.c

Regards,

Alex Gershgorin

I.MX35 PDK

From: festevam@gmail.com (Fabio Estevam)
Date: 2012-03-07 12:18:55

On 3/6/12, Fabio Estevam [off-list ref] wrote:

Alex Gershgorin wrote:

quoted

Hi Fabio,



How I can get information about accesses to CMOS_RST_B and CSI_PWDN bits
of MC9S08DZ60 processor.

I need address of this register and bits mapping in this register.

CMOS_RESET: Bit 6 of register 0x1a
CMOS_ENABLE: Bit 1 of register 0x20

After the mx35pdk lcd support patch gets applied I will submit a patch
to adding support to all of the registers/bits definitions for
mc9s08dz60 chip.

Regards,

Fabio Estevam

I.MX35 PDK

From: Alex Gershgorin <hidden>
Date: 2012-03-07 14:05:29

Thanks Fabio,

 
________________________________________
From: Fabio Estevam [festevam at gmail.com]
Sent: Wednesday, March 07, 2012 2:18 PM
To: Fabio Estevam
Cc: Alex Gershgorin; linux-arm-kernel at lists.infradead.org; kernel at pengutronix.de
Subject: Re: I.MX35 PDK

On 3/6/12, Fabio Estevam [off-list ref] wrote:

Alex Gershgorin wrote:

quoted

Hi Fabio,



How I can get information about accesses to CMOS_RST_B and CSI_PWDN bits
of MC9S08DZ60 processor.

I need address of this register and bits mapping in this register.

CMOS_RESET: Bit 6 of register 0x1a
CMOS_ENABLE: Bit 1 of register 0x20

quoted

After the mx35pdk lcd support patch gets applied I will submit a patch
to adding support to all of the registers/bits definitions for

quoted

mc9s08dz60 chip.

I use a barebox boot loader which supported mc9s08dz60 driver :-)
Currently this is working, without  driver in the Linux kernel, but I have other problem:
In my I.MX35 pdk personality board on connector CN14 I measure signals CMOS_RST = 1, CSI_PWDN = 0 and all of the correct voltages,
in spite of this I get from ov2640 driver error 
Here Linux Kernel boot message:  

"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: Product ID error fb:fb" 

I cannot understand what the problem is, if someone tested this?

Regards,
Alex Gershgorin

I.MX35 PDK

From: festevam@gmail.com (Fabio Estevam)
Date: 2012-03-07 14:17:55

On 3/7/12, Alex Gershgorin [off-list ref] wrote:

in spite of this I get from ov2640 driver error
Here Linux Kernel boot message:

"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: Product ID error fb:fb"

I cannot understand what the problem is, if someone tested this?

Looks like a I2C issue.

Check the I2C1 pad settings in the mainline kernel.

On FSL kernel we have:

#define PAD_CONFIG (PAD_CTL_HYS_SCHMITZ | PAD_CTL_PKE_ENABLE |
PAD_CTL_PUE_PUD | PAD_CTL_ODE_OpenDrain)

	switch (i2c_num) {
	case 0:
		mxc_request_iomux(MX35_PIN_I2C1_CLK, MUX_CONFIG_SION);
		mxc_request_iomux(MX35_PIN_I2C1_DAT, MUX_CONFIG_SION);

		mxc_iomux_set_pad(MX35_PIN_I2C1_CLK, PAD_CONFIG);
		mxc_iomux_set_pad(MX35_PIN_I2C1_DAT, PAD_CONFIG);

Also check if you are getting the proper voltage levels at the I2C1 lines.

Good luck!

RE: I.MX35 PDK

From: Alex Gershgorin <hidden>
Date: 2012-03-08 11:17:12

Hi Fabio,

Thanks for you response...

in spite of this I get from ov2640 driver error
Here Linux Kernel boot message:

"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: Product ID error fb:fb"

I cannot understand what the problem is, if someone tested this?

quoted

Looks like a I2C issue.

quoted

Check the I2C1 pad settings in the mainline kernel.

quoted

On FSL kernel we have:

#<<define PAD_CONFIG (PAD_CTL_HYS_SCHMITZ | PAD_CTL_PKE_ENABLE |

quoted

PAD_CTL_PUE_PUD | PAD_CTL_ODE_OpenDrain)

	<<switch (i2c_num) {
	<<case 0:
		<<mxc_request_iomux(MX35_PIN_I2C1_CLK, MUX_CONFIG_SION);
		<<mxc_request_iomux(MX35_PIN_I2C1_DAT, MUX_CONFIG_SION);

		<<mxc_iomux_set_pad(MX35_PIN_I2C1_CLK, PAD_CONFIG);
		<<mxc_iomux_set_pad(MX35_PIN_I2C1_DAT, PAD_CONFIG);

quoted

Also check if you are getting the proper voltage levels at the I2C1 lines.

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 

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):


What is the problem? 
Guennadi please help me understand 

Thanks,
 
Alex Gershgorin

Re: I.MX35 PDK

From: Fabio Estevam <festevam@gmail.com>
Date: 2012-03-08 11:26:26

On 3/8/12, Alex Gershgorin [off-list ref] 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

RE: I.MX35 PDK

From: Alex Gershgorin <hidden>
Date: 2012-03-08 12:11:12

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?

In the near future I will check this option:-)

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

 Thank Fabio I'll try to check it.

Regards
Alex Gershgorin

RE: I.MX35 PDK

From: Alex Gershgorin <hidden>
Date: 2012-03-08 15:36:24

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

<<Thank Fabio I'll try to check it.

I tried to test it, everything is fine,  just do not see the video on display.
Here can see messages:

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, interlaced=(boolean)false
Pipeline is live and does not need PREROLL ...
WARNING: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could not get parameters on device '/dev/video0'
Additional debug info:
v4l2src_calls.c(240): gst_v4l2src_set_capture (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
system error: Invalid argument
Setting pipeline to PLAYING ...
New clock: GstSystemClock

It works well :-) 
gst-launch videotestsrc ! fbdevsink

Regards
Alex Gershgorin

Re: I.MX35 PDK

From: Fabio Estevam <festevam@gmail.com>
Date: 2012-03-08 15:46:43

On 3/8/12, Alex Gershgorin [off-list ref] 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, interlaced=(boolean)false
Pipeline is live and does not need PREROLL ...
WARNING: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could not
get parameters on device '/dev/video0'
Additional debug info:
v4l2src_calls.c(240): gst_v4l2src_set_capture ():
/GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
system error: Invalid argument

Looks like some kind of Gstreamer issue.

You could also try:
gst-launch -v v4l2src ! fbdevsink

or gst-launch -v v4l2src ! filesink location= raw.data

If you still get Gstreamer issues you can try v4l2grab utility:
http://git.linuxtv.org/v4l-utils.git/blob/de42be924c5154732bc8dfd1c8bc7812985ab2d6?f=contrib/test/v4l2grab.c

Good luck!

RE: I.MX35 PDK

From: Guennadi Liakhovetski <hidden>
Date: 2012-03-08 11:34:45

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

quoted

in spite of this I get from ov2640 driver error
Here Linux Kernel boot message:

"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: Product ID error fb:fb"

I cannot understand what the problem is, if someone tested this?

quoted

Looks like a I2C issue.

quoted

Check the I2C1 pad settings in the mainline kernel.

quoted

On FSL kernel we have:

#<<define PAD_CONFIG (PAD_CTL_HYS_SCHMITZ | PAD_CTL_PKE_ENABLE |

quoted

PAD_CTL_PUE_PUD | PAD_CTL_ODE_OpenDrain)

	<<switch (i2c_num) {
	<<case 0:
		<<mxc_request_iomux(MX35_PIN_I2C1_CLK, MUX_CONFIG_SION);
		<<mxc_request_iomux(MX35_PIN_I2C1_DAT, MUX_CONFIG_SION);

		<<mxc_iomux_set_pad(MX35_PIN_I2C1_CLK, PAD_CONFIG);
		<<mxc_iomux_set_pad(MX35_PIN_I2C1_DAT, PAD_CONFIG);

quoted

Also check if you are getting the proper voltage levels at the I2C1 lines.

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 

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)

First of all it shows, that you're not using the newest kernel:

http://thread.gmane.org/gmane.linux.ports.sh.devel/11508

Secondly, as Fabio just pointed out, these messages are not fatal, which 
is also the reason, why I changed their priority to "debug"

Please, describe the actual problem, that you're getting (if any) and do 
add the v4l list back to the list of recipients!

Thanks
Guennadi

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):


What is the problem? 
Guennadi please help me understand 

Thanks,
 
Alex Gershgorin

---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

RE: I.MX35 PDK

From: Alex Gershgorin <hidden>
Date: 2012-03-08 13:43:22

Hi Guennadi,

Thanks for you comments...

quoted
quoted
Hi Alex

quoted

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

quoted

in spite of this I get from ov2640 driver error
Here Linux Kernel boot message:

"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: Product ID error fb:fb"

I cannot understand what the problem is, if someone tested this?

quoted

Looks like a I2C issue.

quoted

Check the I2C1 pad settings in the mainline kernel.

quoted

On FSL kernel we have:

#<<define PAD_CONFIG (PAD_CTL_HYS_SCHMITZ | PAD_CTL_PKE_ENABLE |

quoted

PAD_CTL_PUE_PUD | PAD_CTL_ODE_OpenDrain)

      <<switch (i2c_num) {
      <<case 0:
              <<mxc_request_iomux(MX35_PIN_I2C1_CLK, MUX_CONFIG_SION);
              <<mxc_request_iomux(MX35_PIN_I2C1_DAT, MUX_CONFIG_SION);

              <<mxc_iomux_set_pad(MX35_PIN_I2C1_CLK, PAD_CONFIG);
              <<mxc_iomux_set_pad(MX35_PIN_I2C1_DAT, PAD_CONFIG);

quoted

Also check if you are getting the proper voltage levels at the I2C1 lines.

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

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)

quoted

First of all it shows, that you're not using the newest kernel:

quoted

http://thread.gmane.org/gmane.linux.ports.sh.devel/11508

I use Linux version 3.3.0-rc6 it contains the changes.

quoted

Secondly, as Fabio just pointed out, these messages are not fatal, which
is also the reason, why I changed their priority to "debug"

Ok

quoted

Please, describe the actual problem, that you're getting (if any) and do
add the v4l list back to the list of recipients!

At this stage, for me the problem of this type are actual, for the simple reason that I see it the first time.
Thanks for support and patience :-)

What is the problem?
Guennadi please help me understand

Regards, 
Alex Gershgorin

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help