All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Philippe BALLEYDIER <PBalleydier@visionsystems.fr>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: What image should I build on the SabreLite?
Date: Fri, 07 Nov 2014 06:55:29 -0700	[thread overview]
Message-ID: <545CCF51.7040800@boundarydevices.com> (raw)
In-Reply-To: <31DEF1477DD8ED418B35D5485DECBE6F010DFC51@SRV-MAIL1.dom-rbe.local>

Hi Philippe,

On 11/07/2014 03:00 AM, Philippe BALLEYDIER wrote:
> Hi
> 
> I did the same as you on fsl-image-multimedia-full
> Here's what i get:
> 
> root@nitrogen6x:~# cat /proc/version
> Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (philippe@philippe-HP-ProBook-4730s) (gcc version 4.9.1 (GCC) ) #1 SMP Fri Nov 7 08:50:50 CET 2014
> root@nitrogen6x:~# dmesg | grep ov5642
> update_device_addr: ov5642 ret=-110
> ov5642_read_reg:write reg error:reg=300a
> camera ov5642 is not found

This indicates a problem with the camera or cabling.

> root@nitrogen6x:~# dmesg | grep ov5640
> ov5640_mipi 1-003e: found pwm2, period=45
> ov5640_read_reg:write reg error:reg=300a
> camera ov5640 is not found
> update_device_addr: ov5640_mipi ret=-110
> ov5640_read_reg(mipi):reg=300a ret=-110
> camera ov5640_mipi is not found

You don't have one of these connected, right?

> root@nitrogen6x:~# gst-launch --gst-debug-level=2 mfw_v4lsrc ! mfw_v4lsink
> MFW_GST_V4LSRC_PLUGIN 3.0.11 build on Nov  7 2014 09:23:30.
> mxc_v4l_open: Mxc Camera no sensor ipu0/csi0
> mxc_v4l_open: Mxc Camera no sensor ipu1/csi0
> mxc_v4l_open: Mxc Camera no sensor ipu1/csi1

If the cameras were "not found", I think you knew what was going
to happen here!

> 
> <snip>
> 
> Is it possible that my camera is dead? How can i make sure of that?
>
It's most likely a cabling issue. It's quite easy for the flex cables
to become dislodged since there aren't any cable stays.

> I managed to make it work once on fsl-image-gui (dora branch). I
> guess i will rebuild this one just to make sure the camera is still working fine.
> 
I'd recommend using a pre-built image to shave some time.

There are quite a few on O.S. Systems CI server:
	http://ci.ossystems.com.br/public/fsl-community-bsp/master

This Ubuntu image also contains full camera support:
	http://boundarydevices.com/ubuntu-trusty-mx6-boards-september-2014/

> 
> I added the CONFIG_USB_AUDIO to the kernel and i now have a
> UAC2_Gadget appearing in alsamixer, but no element is showing up: This
> sound device does not have any controls.
> 
I'm not sure what you mean by "no element".

Can you clarify?

You mentioned that the SABRE SD board was able to operate with
your hardware. You might want to compare the defconfig files
between the two.  Perhaps something is missing.

Regards,


Eric


  reply	other threads:[~2014-11-07 13:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 11:11 What image should I build on the SabreLite? Philippe BALLEYDIER
2014-11-04 15:04 ` Eric Nelson
2014-11-04 15:16   ` Wally Yeh
2014-11-04 15:29     ` Otavio Salvador
2014-11-04 19:07       ` Daiane Angolini
2014-11-04 19:46         ` Otavio Salvador
2014-11-04 22:25           ` Wally Yeh
2014-11-04 18:50     ` Eric Nelson
2014-11-05  8:42   ` Philippe BALLEYDIER
2014-11-06  9:31     ` Philippe BALLEYDIER
2014-11-06 15:55       ` Eric Nelson
2014-11-06 18:11         ` Eric Nelson
2014-11-06 21:38           ` Eric Nelson
2014-11-07 10:00           ` Philippe BALLEYDIER
2014-11-07 13:55             ` Eric Nelson [this message]
2014-11-13 11:09               ` Philippe BALLEYDIER
2014-11-13 13:50                 ` Philippe BALLEYDIER
2014-11-06 21:47         ` Eric Nelson

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=545CCF51.7040800@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=PBalleydier@visionsystems.fr \
    --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.