Thread (12 messages) read the whole thread 12 messages, 4 authors, 2012-03-08
  • (off-list ancestor, not in this archive)
  • I.MX35 PDK · Fabio Estevam <hidden> · 2012-03-06
  • I.MX35 PDK · Alex Gershgorin <hidden> · 2012-03-06
  • I.MX35 PDK · festevam@gmail.com (Fabio Estevam) · 2012-03-07
  • I.MX35 PDK · Alex Gershgorin <hidden> · 2012-03-07
  • I.MX35 PDK · festevam@gmail.com (Fabio Estevam) · 2012-03-07
  • RE: I.MX35 PDK · Alex Gershgorin <hidden> · 2012-03-08
  • Re: I.MX35 PDK · Fabio Estevam <festevam@gmail.com> · 2012-03-08
  • RE: I.MX35 PDK · Alex Gershgorin <hidden> · 2012-03-08
  • RE: I.MX35 PDK · Alex Gershgorin <hidden> · 2012-03-08
  • Re: I.MX35 PDK · Fabio Estevam <festevam@gmail.com> · 2012-03-08
  • RE: I.MX35 PDK · Guennadi Liakhovetski <hidden> · 2012-03-08
  • RE: I.MX35 PDK · Alex Gershgorin <hidden> · 2012-03-08

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!
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help