* Re: yavta - Broken pipe
[not found] <CAJRKTVqnB6-8itbr3Cu-jnJo-zz3dYQeJ98sLnD-Eo9hvNS5iQ@mail.gmail.com>
@ 2013-01-22 15:31 ` Laurent Pinchart
2013-01-22 15:48 ` Adriano Martins
0 siblings, 1 reply; 5+ messages in thread
From: Laurent Pinchart @ 2013-01-22 15:31 UTC (permalink / raw)
To: Adriano Martins; +Cc: linux-media
Hi Adriano,
On Tuesday 22 January 2013 09:31:58 Adriano Martins wrote:
> Hello Laurent and all.
>
> Can you explain me what means the message in yavta output:
>
> "Unable to start streaming: Broken pipe (32)."
This means that the ISP hardware pipeline hasn't been properly configured.
Unlike most V4L2 devices, the OMAP3 ISP requires userspace to configure the
hardware pipeline before starting the video stream. You can do so with the
media-ctl utility (available at http://git.ideasonboard.org/media-ctl.git).
Plenty of examples should be available online.
> I'm using omap3isp driver on DM3730 processor and a ov5640 sensor. I
> configured it as parallel mode, but I can't get data from /dev/video6
> (OMAP3 ISP resizer output)
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: yavta - Broken pipe
2013-01-22 15:31 ` yavta - Broken pipe Laurent Pinchart
@ 2013-01-22 15:48 ` Adriano Martins
2013-01-22 23:29 ` Laurent Pinchart
0 siblings, 1 reply; 5+ messages in thread
From: Adriano Martins @ 2013-01-22 15:48 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: linux-media
Hi Laurent,
2013/1/22 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
> Hi Adriano,
>
> On Tuesday 22 January 2013 09:31:58 Adriano Martins wrote:
>> Hello Laurent and all.
>>
>> Can you explain me what means the message in yavta output:
>>
>> "Unable to start streaming: Broken pipe (32)."
>
> This means that the ISP hardware pipeline hasn't been properly configured.
well, I already configured it before, with:
media-ctl -V '"OMAP3 ISP CCDC":2 [UYVY 640x480], "OMAP3 ISP preview":1
[UYVY 640x480], "OMAP3 ISP resizer":1 [UYVY 640x480]'
and
media-ctl -r -l '"ov5640 3-003c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP
CCDC":2->"OMAP3 ISP preview":0[1], "OMAP3 ISP \
preview":1->"OMAP3 ISP resizer":0[1], "OMAP3 ISP resizer":1->"OMAP3
ISP resizer output":0[1]'
Do you think it can be a hardware problem or wrong frame format from
sensor? Or media-ctl commands is wrong.
> Unlike most V4L2 devices, the OMAP3 ISP requires userspace to configure the
> hardware pipeline before starting the video stream. You can do so with the
> media-ctl utility (available at http://git.ideasonboard.org/media-ctl.git).
> Plenty of examples should be available online.
>
>> I'm using omap3isp driver on DM3730 processor and a ov5640 sensor. I
>> configured it as parallel mode, but I can't get data from /dev/video6
>> (OMAP3 ISP resizer output)
>
> --
> Regards,
>
> Laurent Pinchart
>
Regards
Adriano
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: yavta - Broken pipe
2013-01-22 15:48 ` Adriano Martins
@ 2013-01-22 23:29 ` Laurent Pinchart
2013-01-23 11:05 ` Adriano Martins
0 siblings, 1 reply; 5+ messages in thread
From: Laurent Pinchart @ 2013-01-22 23:29 UTC (permalink / raw)
To: Adriano Martins; +Cc: linux-media
Hi Adriano,
On Tuesday 22 January 2013 13:48:40 Adriano Martins wrote:
> 2013/1/22 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
> > On Tuesday 22 January 2013 09:31:58 Adriano Martins wrote:
> >> Hello Laurent and all.
> >>
> >> Can you explain me what means the message in yavta output:
> >>
> >> "Unable to start streaming: Broken pipe (32)."
> >
> > This means that the ISP hardware pipeline hasn't been properly configured.
>
> well, I already configured it before, with:
>
> media-ctl -V '"OMAP3 ISP CCDC":2 [UYVY 640x480], "OMAP3 ISP preview":1
> [UYVY 640x480], "OMAP3 ISP resizer":1 [UYVY 640x480]'
> and
> media-ctl -r -l '"ov5640 3-003c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP
> CCDC":2->"OMAP3 ISP preview":0[1], "OMAP3 ISP \
> preview":1->"OMAP3 ISP resizer":0[1], "OMAP3 ISP resizer":1->"OMAP3
> ISP resizer output":0[1]'
> Do you think it can be a hardware problem or wrong frame format from
> sensor? Or media-ctl commands is wrong.
The ISP doesn't support YUV formats at its input. If you sensor generates UYVY
640x480 you should capture video directly at the output of the CCDC. You will
need a recent version of the OMAP3 ISP driver (v3.6 or newer).
> > Unlike most V4L2 devices, the OMAP3 ISP requires userspace to configure
> > the hardware pipeline before starting the video stream. You can do so with
> > the media-ctl utility (available at
> > http://git.ideasonboard.org/media-ctl.git). Plenty of examples should be
> > available online.
> >
> >> I'm using omap3isp driver on DM3730 processor and a ov5640 sensor. I
> >> configured it as parallel mode, but I can't get data from /dev/video6
> >> (OMAP3 ISP resizer output)
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: yavta - Broken pipe
2013-01-22 23:29 ` Laurent Pinchart
@ 2013-01-23 11:05 ` Adriano Martins
0 siblings, 0 replies; 5+ messages in thread
From: Adriano Martins @ 2013-01-23 11:05 UTC (permalink / raw)
To: Laurent Pinchart; +Cc: linux-media
Hi Laurent,
2013/1/22 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
> On Tuesday 22 January 2013 13:48:40 Adriano Martins wrote:
>> 2013/1/22 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
>> > On Tuesday 22 January 2013 09:31:58 Adriano Martins wrote:
>> >> Hello Laurent and all.
>> >>
>> >> Can you explain me what means the message in yavta output:
>> >>
>> >> "Unable to start streaming: Broken pipe (32)."
>> >
>> > This means that the ISP hardware pipeline hasn't been properly configured.
>>
>> well, I already configured it before, with:
>>
>> media-ctl -V '"OMAP3 ISP CCDC":2 [UYVY 640x480], "OMAP3 ISP preview":1
>> [UYVY 640x480], "OMAP3 ISP resizer":1 [UYVY 640x480]'
>> and
>> media-ctl -r -l '"ov5640 3-003c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP
>> CCDC":2->"OMAP3 ISP preview":0[1], "OMAP3 ISP \
>> preview":1->"OMAP3 ISP resizer":0[1], "OMAP3 ISP resizer":1->"OMAP3
>> ISP resizer output":0[1]'
>> Do you think it can be a hardware problem or wrong frame format from
>> sensor? Or media-ctl commands is wrong.
>
> The ISP doesn't support YUV formats at its input. If you sensor generates UYVY
> 640x480 you should capture video directly at the output of the CCDC. You will
> need a recent version of the OMAP3 ISP driver (v3.6 or newer).
>
Ok, I will try change the sensor output format, if it is not possible,
I will get the recent version of the OMAP3 ISP driver and try capture
directly from CCDC output.
>> > Unlike most V4L2 devices, the OMAP3 ISP requires userspace to configure
>> > the hardware pipeline before starting the video stream. You can do so with
>> > the media-ctl utility (available at
>> > http://git.ideasonboard.org/media-ctl.git). Plenty of examples should be
>> > available online.
>> >
>> >> I'm using omap3isp driver on DM3730 processor and a ov5640 sensor. I
>> >> configured it as parallel mode, but I can't get data from /dev/video6
>> >> (OMAP3 ISP resizer output)
Thanks
Regards
Adriano Martins
^ permalink raw reply [flat|nested] 5+ messages in thread
* yavta - Broken pipe
@ 2013-01-22 11:39 Adriano Martins
0 siblings, 0 replies; 5+ messages in thread
From: Adriano Martins @ 2013-01-22 11:39 UTC (permalink / raw)
To: linux-media
Hello Laurent and all.
Can you explain me what means the message in yavta output:
"Unable to start streaming: Broken pipe (32)."
I'm using omap3isp driver on DM3730 processor and a ov5640 sensor. I
configured it as parallel mode, but I can't get data from /dev/video6
(OMAP3 ISP resizer output)
Thanks
Regards
Adriano Martins
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-01-23 11:05 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAJRKTVqnB6-8itbr3Cu-jnJo-zz3dYQeJ98sLnD-Eo9hvNS5iQ@mail.gmail.com>
2013-01-22 15:31 ` yavta - Broken pipe Laurent Pinchart
2013-01-22 15:48 ` Adriano Martins
2013-01-22 23:29 ` Laurent Pinchart
2013-01-23 11:05 ` Adriano Martins
2013-01-22 11:39 Adriano Martins
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox