All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Longerbeam <steve_longerbeam@mentor.com>
To: Adam Ford <aford173@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>, <jacopo@jmondi.org>,
	Jagan Teki <jagan@amarulasolutions.com>, <p.zabel@pengutronix.de>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	<gstreamer-devel@lists.freedesktop.org>,
	<linux-media@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: i.MX6 MIPI-CSI2 OV5640 Camera testing on Mainline Linux
Date: Tue, 23 Oct 2018 11:11:54 -0700	[thread overview]
Message-ID: <68f892ef-92b1-17ec-525c-af50b027c637@mentor.com> (raw)
In-Reply-To: <CAHCN7xKVUgpyCb5k7s0PNXW-efySSwP25ZGMLdbFnohATPwKhg@mail.gmail.com>


On 10/23/18 10:54 AM, Adam Ford wrote:
> On Tue, Oct 23, 2018 at 12:39 PM Steve Longerbeam
> <steve_longerbeam@mentor.com> wrote:
>>
>> On 10/23/18 10:34 AM, Adam Ford wrote:
>>> On Tue, Oct 23, 2018 at 11:36 AM Steve Longerbeam
>>> <steve_longerbeam@mentor.com> wrote:
>>>> Hi Adam,
>>>>
>>>> On 10/23/18 8:19 AM, Adam Ford wrote:
>>>>> On Mon, Oct 22, 2018 at 7:40 AM Fabio Estevam <festevam@gmail.com> wrote:
>>>>>> Hi Adam,
>>>>>>
>>>>>> On Mon, Oct 22, 2018 at 9:37 AM Adam Ford <aford173@gmail.com> wrote:
>>>>>>
>>>>>>> Thank you!  This tutorial web site is exactly what I need.  The
>>>>>>> documentation page in Linux touched on the media-ctl links, but it
>>>>>>> didn't explain the syntax or the mapping.  This graphical
>>>>>>> interpretation really helps it make more sense.
>>>>>> Is capturing working well on your i.MX6 board now?
>>>>> Fabio,
>>>>>
>>>>> Unfortunately, no.  I built the rootfs based on Jagan's instructions
>>>>> at https://openedev.amarulasolutions.com/display/ODWIKI/i.CoreM6+1.5
>>>>>
>>>>> I tried building both the 4.15-RC6 kernel, a 4.19 kernel and a 4.14 LTS kernel.
>>>>>
>>>>> Using the suggested method of generating the graphical display of the
>>>>> pipeline options, I am able to enable various pipeline options
>>>>> connecting different /dev/videoX options tot he camera.  I have tried
>>>>> both the  suggested method above as well as the instructions found in
>>>>> Documentation/media/v4l-drivers/imx.rst for their respective kernels,
>>>>> and I have tried multiple options to capture through
>>>>> ipu1_csi1_capture, ipu2_csi1_capture, and ip1_ic_prepenc capture, and
>>>>> all yield a broken pipe.
>>>>>
>>>>> libv4l2: error turning on stream: Broken pipe
>>>>> ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could
>>>>> not read from resource.
>>>>> Additional debug info:
>>>>> gstv4l2bufferpool.c(1064): gst_v4l2_buffer_pool_poll ():
>>>>> /GstPipeline:pipeline0/GstV4l2Src:v4l2src0:
>>>>> poll error 1: Broken pipe (32)
>>>>>
>>>>> I can hear the camera click when I start gstreamer and click again
>>>>> when it stops trying to stream.
>>>>>
>>>>> dmesg indicates a broken pipe as well..
>>>>>
>>>>> [ 2419.851502] ipu2_csi1: pipeline start failed with -32
>>>>>
>>>>> might you have any suggestions?
>>>> This -EPIPE error might mean you have a mis-match of resolution, pixel
>>>> format, or field type between one of the source->sink pad links. You can
>>>> find out which pads have a mis-match by enabling dynamic debug in the
>>>> kernel function __media_pipeline_start.
>>> Following Jagan's suggestion, I tried to make sure all the resolution
>>> and pixel formats were set the same between each source and sink.
>>>
>>> media-ctl --set-v4l2 "'ov5640 2-0010':0[fmt:UYVY2X8/640x480
>>> field:none]"
>>> media-ctl --set-v4l2 "'imx6-mipi-csi2':1[fmt:UYVY2X8/640x480
>>> field:none]"
>>> media-ctl --set-v4l2 "'ipu1_csi0_mux':2[fmt:UYVY2X8/640x480
>>> field:none]"
>>> media-ctl --set-v4l2 "'ipu1_csi0':2[fmt:AYUV32/640x480 field:none]"
>>>
>>>> Also make sure you are attempting to stream from the correct /dev/videoN.
>>> I have graphically plotted the pipeline using media-ctl --print-dot
>>> and I can see the proper video is routed, but your dynamic debug
>>> suggestion yielded something:
>>>
>>>      imx-media capture-subsystem: link validation failed for 'ov5640
>>> 2-0010':0 -> 'imx6-mipi-csi2':0, error -32
>>
>> It's what I expected, you have a format mismatch between those pads.
> Is the mismatch something I am doing wrong with:
>
> media-ctl --set-v4l2 "'ov5640 2-0010':0[fmt:UYVY2X8/640x480 field:none]"
> media-ctl --set-v4l2 "'imx6-mipi-csi2':2[fmt:UYVY2X8/640x480 field:none]"
>
> or is there something else I need to do?  I just used Jagan's suggestion.


Yeah, that looks correct, media-ctl _should_ automatically propagate the 
format at 'ov5640 2-0010':0 to 'imx6-mipi-csi2':0. What version of 
media-ctl are you using? If you have an older version of media-ctl tool 
that doesn't propagate formats from source->sink pads, you'll have to 
explicitly set the format at 'imx6-mipi-csi2':0, and at all the other 
sink pads in your pipeline. Better yet, upgrade! :)

Steve


>
>>> I am assume this means the interface between the camera and the csi2
>>> isn't working.  I am going to double check the power rails and the
>>> clocks.  i can hear it click when activated and deactivated, so
>>> something is happening.
>>>
>>> adam
>>>
>>>> Steve
>>>>

  reply	other threads:[~2018-10-23 18:12 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-31 15:09 i.MX6 MIPI-CSI2 OV5640 Camera testing on Mainline Linux Jagan Teki
2018-05-31 16:10 ` Nicolas Dufresne
2018-05-31 16:25   ` Jagan Teki
2018-05-31 19:06 ` Philipp Zabel
2018-06-01  5:19   ` Jagan Teki
2018-06-01  9:53     ` Sakari Ailus
2018-06-01 11:41       ` Jagan Teki
2018-06-29 21:46     ` Fabio Estevam
2018-06-29 21:46       ` Fabio Estevam
2018-07-03 18:41       ` jacopo mondi
2018-07-03 18:41         ` jacopo mondi
2018-07-04  0:18         ` Fabio Estevam
2018-07-04  0:18           ` Fabio Estevam
2018-07-04  5:18         ` Jagan Teki
2018-07-04  5:18           ` Jagan Teki
2018-07-04  6:57           ` Jagan Teki
2018-07-04  6:57             ` Jagan Teki
2018-07-04 14:26             ` Fabio Estevam
2018-07-04 14:26               ` Fabio Estevam
     [not found]           ` <588A2275-4D45-442D-8B38-7A17C27BED10@gmail.com>
2018-07-04  6:59             ` Jagan Teki
2018-07-04  6:59               ` Jagan Teki
2018-07-04  7:11               ` chain256
2018-07-04  7:11                 ` chain256
2018-09-20 14:56 ` jacopo mondi
2018-09-20 14:56   ` jacopo mondi
2018-10-16 19:46   ` Adam Ford
2018-10-17  0:13     ` Steve Longerbeam
2018-10-17  8:01       ` jacopo mondi
2018-10-19 13:45         ` Adam Ford
2018-10-19 19:42           ` Adam Ford
2018-10-22 11:33             ` jacopo mondi
2018-10-22 12:25               ` Adam Ford
2018-10-22 12:40                 ` Fabio Estevam
2018-10-22 12:40                   ` Fabio Estevam
2018-10-23 15:19                   ` Adam Ford
2018-10-23 16:36                     ` Steve Longerbeam
2018-10-23 17:34                       ` Adam Ford
2018-10-23 17:39                         ` Steve Longerbeam
2018-10-23 17:54                           ` Adam Ford
2018-10-23 18:11                             ` Steve Longerbeam [this message]
2018-10-23 23:03                             ` jacopo mondi
2018-10-24 13:53                               ` Adam Ford
2018-10-24 14:08                                 ` jacopo mondi
2018-10-24 14:17                                   ` Adam Ford
2018-10-28 18:57                                     ` Adam Ford
2018-10-29 13:49                                       ` Fabio Estevam
2018-10-29 13:49                                         ` Fabio Estevam
2018-11-05 22:32                                         ` Adam Ford
2018-11-06  8:27                                           ` jacopo mondi

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=68f892ef-92b1-17ec-525c-af50b027c637@mentor.com \
    --to=steve_longerbeam@mentor.com \
    --cc=aford173@gmail.com \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=gstreamer-devel@lists.freedesktop.org \
    --cc=jacopo@jmondi.org \
    --cc=jagan@amarulasolutions.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    /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.