Nitrogen6x w/ OV5642

Nitrogen6x w/ OV5642

[Sébastien Taylor]

I am having issues interfacing the OV5642 sensor with the Nitrogen6x board using the fsl-community-bsp.

On bootup I see that the OV5642 driver is installed, but doing a modprobe mxc_v4l2_capture gives me a no slaves found error.

Module                  Size  Used by
wl12xx_sdio             3523  0 
ov5642_camera          74186  0 
camera_sensor_clock      721  1 ov5642_camera

root@nitrogen6x:~# modprobe mxc_v4l2_capture
root@nitrogen6x:~# ERROR: v4l2 capture: slave not found!

Re: Nitrogen6x w/ OV5642

[Eric Nelson]

Hi Sébastien,

On 05/22/2013 01:57 PM, Sébastien Taylor wrote:
> I am having issues interfacing the OV5642 sensor with the Nitrogen6x board using the fsl-community-bsp.
>
> On bootup I see that the OV5642 driver is installed, but doing a modprobe mxc_v4l2_capture gives me a no slaves found error.
>
> Module                  Size  Used by
> wl12xx_sdio             3523  0
> ov5642_camera          74186  0
> camera_sensor_clock      721  1 ov5642_camera
>
> root@nitrogen6x:~# modprobe mxc_v4l2_capture
> root@nitrogen6x:~# ERROR: v4l2 capture: slave not found!
>

I've confirmed this as well. It used to work, and I'll try to piece
together what happened...

Oh. Never mind.

For me at least, the error messages about missing slaves are
meaningless, and the mxc_v4l2_capture module continues
to load:

	root@nitrogen6x:~# lsmod
	Module                  Size  Used by
	mxc_v4l2_capture       21077  1
	ipu_bg_overlay_sdc      3929  1 mxc_v4l2_capture
	ipu_still               1707  1 mxc_v4l2_capture
	ipu_prp_enc             4685  1 mxc_v4l2_capture
	ipu_csi_enc             2941  1 mxc_v4l2_capture
	ipu_fg_overlay_sdc      4760  1 mxc_v4l2_capture
	ov5642_camera          74186  0
	camera_sensor_clock      721  1 ov5642_camera
	vivante                  943  1
	drm                   140600  2 vivante

I can also verify camera preview using the trivial
gst-launch command:

	root@nitrogen6x:~# gst-launch mfw_v4lsrc ! mfw_v4lsink

Which branch are you using?

Please advise,


Eric

Re: Nitrogen6x w/ OV5642

[Sébastien Taylor]

I'm on the Dylan branch and I've tried with both the default linux-boundary kernel as well as updating the .bb to use the latest 1.1.1 branch from boundary.  Looks like I'll have to dig a little deeper to see what's causing mfw_v4lsrc to fail (mfw_v4lsink works fine with a videotestsrc).

On 2013-05-22, at 4:11 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:

> Hi Sébastien,
> 
> On 05/22/2013 01:57 PM, Sébastien Taylor wrote:
>> I am having issues interfacing the OV5642 sensor with the Nitrogen6x board using the fsl-community-bsp.
>> 
>> On bootup I see that the OV5642 driver is installed, but doing a modprobe mxc_v4l2_capture gives me a no slaves found error.
>> 
>> Module                  Size  Used by
>> wl12xx_sdio             3523  0
>> ov5642_camera          74186  0
>> camera_sensor_clock      721  1 ov5642_camera
>> 
>> root@nitrogen6x:~# modprobe mxc_v4l2_capture
>> root@nitrogen6x:~# ERROR: v4l2 capture: slave not found!
>> 
> 
> I've confirmed this as well. It used to work, and I'll try to piece
> together what happened...
> 
> Oh. Never mind.
> 
> For me at least, the error messages about missing slaves are
> meaningless, and the mxc_v4l2_capture module continues
> to load:
> 
> 	root@nitrogen6x:~# lsmod
> 	Module                  Size  Used by
> 	mxc_v4l2_capture       21077  1
> 	ipu_bg_overlay_sdc      3929  1 mxc_v4l2_capture
> 	ipu_still               1707  1 mxc_v4l2_capture
> 	ipu_prp_enc             4685  1 mxc_v4l2_capture
> 	ipu_csi_enc             2941  1 mxc_v4l2_capture
> 	ipu_fg_overlay_sdc      4760  1 mxc_v4l2_capture
> 	ov5642_camera          74186  0
> 	camera_sensor_clock      721  1 ov5642_camera
> 	vivante                  943  1
> 	drm                   140600  2 vivante
> 
> I can also verify camera preview using the trivial
> gst-launch command:
> 
> 	root@nitrogen6x:~# gst-launch mfw_v4lsrc ! mfw_v4lsink
> 
> Which branch are you using?
> 
> Please advise,
> 
> 
> Eric
> 
> 

Re: Nitrogen6x w/ OV5642

[Eric Nelson]

Hi Sébastien,

On 05/22/2013 03:43 PM, Sébastien Taylor wrote:
> I'm on the Dylan branch and I've tried withboth the default
 > linux-boundary kernel as well as updating the .bb to use
 > the latest 1.1.1 branch from boundary.
 >
 > Looks like I'll have to dig a little deeper to see what's causing
 > mfw_v4lsrc to fail (mfw_v4lsink works fine with a videotestsrc).
>
Can you check the version of the gstreamer plugins?

	root@nitrogen6x# gst-inspect mfw_v4lsrc | head -n 1

Our 1.1.1 branch is confirmed to work with the 3.0.5 package,
but I haven't yet pushed a kernel matching the 4.0.0. BSP
release (I'm hoping to do some clean up along the way).

Please advise,


Eric

Re: Nitrogen6x w/ OV5642

[Sébastien Taylor]

MFW_GST_V4LSRC_PLUGIN 3.0.5 build on May 21 2013 14:49:13.

Running gst-launch with DEBUG=*:3 shows that the failure is caused by being unable to open /dev/video0 though the device is there.

On 2013-05-22, at 5:01 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:

> Hi Sébastien,
> 
> On 05/22/2013 03:43 PM, Sébastien Taylor wrote:
>> I'm on the Dylan branch and I've tried withboth the default
> > linux-boundary kernel as well as updating the .bb to use
> > the latest 1.1.1 branch from boundary.
> >
> > Looks like I'll have to dig a little deeper to see what's causing
> > mfw_v4lsrc to fail (mfw_v4lsink works fine with a videotestsrc).
>> 
> Can you check the version of the gstreamer plugins?
> 
> 	root@nitrogen6x# gst-inspect mfw_v4lsrc | head -n 1
> 
> Our 1.1.1 branch is confirmed to work with the 3.0.5 package,
> but I haven't yet pushed a kernel matching the 4.0.0. BSP
> release (I'm hoping to do some clean up along the way).
> 
> Please advise,
> 
> 
> Eric
> 

Re: Nitrogen6x w/ OV5642

[Eric Nelson]

Hi Sébastien,

Is this the first time you've used the module?

If so, I suspect a cabling issue. The flex connectors can
be a pain to get right the first time:

Theres a photo here of how the cables should be connected
to Nitrogen6X (i.e. blue side up):
	http://boundarydevices.com/wp-content/uploads/2012/05/Camera-to-6X-Small.jpg

I'll try to get a Dylan image built, but that may bleed into
next week, since I'm taking a few days off.

Please advise,


Eric

On 05/22/2013 04:56 PM, Sébastien Taylor wrote:
> MFW_GST_V4LSRC_PLUGIN 3.0.5 build on May 21 2013 14:49:13.
>
> Running gst-launch with DEBUG=*:3 shows that the failure is caused by being unable to open /dev/video0 though the device is there.
>
> On 2013-05-22, at 5:01 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:
>
>> Hi Sébastien,
>>
>> On 05/22/2013 03:43 PM, Sébastien Taylor wrote:
>>> I'm on the Dylan branch and I've tried withboth the default
>>> linux-boundary kernel as well as updating the .bb to use
>>> the latest 1.1.1 branch from boundary.
>>>
>>> Looks like I'll have to dig a little deeper to see what's causing
>>> mfw_v4lsrc to fail (mfw_v4lsink works fine with a videotestsrc).
>>>
>> Can you check the version of the gstreamer plugins?
>>
>> 	root@nitrogen6x# gst-inspect mfw_v4lsrc | head -n 1
>>
>> Our 1.1.1 branch is confirmed to work with the 3.0.5 package,
>> but I haven't yet pushed a kernel matching the 4.0.0. BSP
>> release (I'm hoping to do some clean up along the way).
>>
>> Please advise,
>>
>>
>> Eric
>>
>

Re: Nitrogen6x w/ OV5642

[Sébastien Taylor]

I did previously have the module working in Yocto when I first setup the fsl-image-test.  I then spent a few days customizing a custom layer and porting our applications and when I returned to do more testing is when the camera was no longer working.  It does seem like it's a connection issue though I'm so far not having much luck on that front, but I did capture these logs showing the ov5642_probe failing (extended the debug log slightly).

But it would seem the problem is on my end.

ov5642_probe
camera_reset: power_gp=0x6, reset_gp=0x8 reset_gp2=0xab
mx6_csi0_powerdown: powerdown=0, power_gp=0x6
ov5642_read_reg: write reg error: reg=300a err=-5
ov5642_probe:cannot find camera retval -1 chip_id_high 0x0
ov5642_read_reg: write reg error: reg=300b err=-5
ov5642_probe:cannot find camera retval -1 chip_id_low 0x0
mx6_csi0_powerdown: powerdown=1, power_gp=0x6


On 2013-05-22, at 6:02 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:

> Hi Sébastien,
> 
> Is this the first time you've used the module?
> 
> If so, I suspect a cabling issue. The flex connectors can
> be a pain to get right the first time:
> 
> Theres a photo here of how the cables should be connected
> to Nitrogen6X (i.e. blue side up):
> 	http://boundarydevices.com/wp-content/uploads/2012/05/Camera-to-6X-Small.jpg
> 
> I'll try to get a Dylan image built, but that may bleed into
> next week, since I'm taking a few days off.
> 
> Please advise,
> 
> 
> Eric
> 
> On 05/22/2013 04:56 PM, Sébastien Taylor wrote:
>> MFW_GST_V4LSRC_PLUGIN 3.0.5 build on May 21 2013 14:49:13.
>> 
>> Running gst-launch with DEBUG=*:3 shows that the failure is caused by being unable to open /dev/video0 though the device is there.
>> 
>> On 2013-05-22, at 5:01 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:
>> 
>>> Hi Sébastien,
>>> 
>>> On 05/22/2013 03:43 PM, Sébastien Taylor wrote:
>>>> I'm on the Dylan branch and I've tried withboth the default
>>>> linux-boundary kernel as well as updating the .bb to use
>>>> the latest 1.1.1 branch from boundary.
>>>> 
>>>> Looks like I'll have to dig a little deeper to see what's causing
>>>> mfw_v4lsrc to fail (mfw_v4lsink works fine with a videotestsrc).
>>>> 
>>> Can you check the version of the gstreamer plugins?
>>> 
>>> 	root@nitrogen6x# gst-inspect mfw_v4lsrc | head -n 1
>>> 
>>> Our 1.1.1 branch is confirmed to work with the 3.0.5 package,
>>> but I haven't yet pushed a kernel matching the 4.0.0. BSP
>>> release (I'm hoping to do some clean up along the way).
>>> 
>>> Please advise,
>>> 
>>> 
>>> Eric
>>> 
>> 
> 

Re: Nitrogen6x w/ OV5642

[Sébastien Taylor]

Turns out the connector wasn't soldered on very well, a few of the leads didn't have good contact.

On 2013-05-23, at 12:48 PM, Sébastien Taylor <me@staylor.ca> wrote:

> I did previously have the module working in Yocto when I first setup the fsl-image-test.  I then spent a few days customizing a custom layer and porting our applications and when I returned to do more testing is when the camera was no longer working.  It does seem like it's a connection issue though I'm so far not having much luck on that front, but I did capture these logs showing the ov5642_probe failing (extended the debug log slightly).
> 
> But it would seem the problem is on my end.
> 
> ov5642_probe
> camera_reset: power_gp=0x6, reset_gp=0x8 reset_gp2=0xab
> mx6_csi0_powerdown: powerdown=0, power_gp=0x6
> ov5642_read_reg: write reg error: reg=300a err=-5
> ov5642_probe:cannot find camera retval -1 chip_id_high 0x0
> ov5642_read_reg: write reg error: reg=300b err=-5
> ov5642_probe:cannot find camera retval -1 chip_id_low 0x0
> mx6_csi0_powerdown: powerdown=1, power_gp=0x6
> 
> 
> On 2013-05-22, at 6:02 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:
> 
>> Hi Sébastien,
>> 
>> Is this the first time you've used the module?
>> 
>> If so, I suspect a cabling issue. The flex connectors can
>> be a pain to get right the first time:
>> 
>> Theres a photo here of how the cables should be connected
>> to Nitrogen6X (i.e. blue side up):
>> 	http://boundarydevices.com/wp-content/uploads/2012/05/Camera-to-6X-Small.jpg
>> 
>> I'll try to get a Dylan image built, but that may bleed into
>> next week, since I'm taking a few days off.
>> 
>> Please advise,
>> 
>> 
>> Eric
>> 
>> On 05/22/2013 04:56 PM, Sébastien Taylor wrote:
>>> MFW_GST_V4LSRC_PLUGIN 3.0.5 build on May 21 2013 14:49:13.
>>> 
>>> Running gst-launch with DEBUG=*:3 shows that the failure is caused by being unable to open /dev/video0 though the device is there.
>>> 
>>> On 2013-05-22, at 5:01 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:
>>> 
>>>> Hi Sébastien,
>>>> 
>>>> On 05/22/2013 03:43 PM, Sébastien Taylor wrote:
>>>>> I'm on the Dylan branch and I've tried withboth the default
>>>>> linux-boundary kernel as well as updating the .bb to use
>>>>> the latest 1.1.1 branch from boundary.
>>>>> 
>>>>> Looks like I'll have to dig a little deeper to see what's causing
>>>>> mfw_v4lsrc to fail (mfw_v4lsink works fine with a videotestsrc).
>>>>> 
>>>> Can you check the version of the gstreamer plugins?
>>>> 
>>>> 	root@nitrogen6x# gst-inspect mfw_v4lsrc | head -n 1
>>>> 
>>>> Our 1.1.1 branch is confirmed to work with the 3.0.5 package,
>>>> but I haven't yet pushed a kernel matching the 4.0.0. BSP
>>>> release (I'm hoping to do some clean up along the way).
>>>> 
>>>> Please advise,
>>>> 
>>>> 
>>>> Eric
>>>> 
>>> 
>> 
>