From: Eric Nelson <eric.nelson@boundarydevices.com>
To: "Sébastien Taylor" <me@staylor.ca>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Nitrogen6x w/ OV5642
Date: Wed, 22 May 2013 15:11:50 -0700 [thread overview]
Message-ID: <519D42A6.6010707@boundarydevices.com> (raw)
In-Reply-To: <CE13C247-9B44-48C0-93E2-B498AC4BC622@staylor.ca>
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
next prev parent reply other threads:[~2013-05-22 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 20:57 Nitrogen6x w/ OV5642 Sébastien Taylor
2013-05-22 22:11 ` Eric Nelson [this message]
2013-05-22 22:43 ` Sébastien Taylor
2013-05-22 23:01 ` Eric Nelson
2013-05-22 23:56 ` Sébastien Taylor
2013-05-23 0:02 ` Eric Nelson
2013-05-23 18:48 ` Sébastien Taylor
2013-05-24 0:57 ` Sébastien Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=519D42A6.6010707@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=me@staylor.ca \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.