From: Neil MacMunn <neil@gumstix.com>
To: unlisted-recipients:; (no To-header on input)@casper.infradead.org
Cc: linux-media@vger.kernel.org
Subject: Re: omap3-isp segfault
Date: Fri, 04 Feb 2011 14:33:54 -0800 [thread overview]
Message-ID: <4D4C7ED2.4060600@gumstix.com> (raw)
In-Reply-To: <201101271328.05891.laurent.pinchart@ideasonboard.com>
Thanks Laurent.
I've appended console output to the commands you've suggested.
On 11-01-27 04:28 AM, Laurent Pinchart wrote:
> Hi again,
>
> On Thursday 27 January 2011 02:43:15 Neil MacMunn wrote:
>> Ok I solved the segfault problem by updating some of my v4l2 files
>> (specifically v4l2-common.c). Now I only get nice sounding console
>> messages.
>>
>> Linux media interface: v0.10
>> Linux video capture interface: v2.00
>> omap3isp omap3isp: Revision 2.0 found
>> omap-iommu omap-iommu.0: isp: version 1.1
>> omap3isp omap3isp: hist: DMA channel = 4
>> mt9v032 3-005c: Probing MT9V032 at address 0x5c
>> omap3isp omap3isp: isp_set_xclk(): cam_xclka set to 28800000 Hz
>> omap3isp omap3isp: isp_set_xclk(): cam_xclka set to 0 Hz
>> mt9v032 3-005c: MT9V032 detected at address 0x5c
>
> As you're using an MT9V032 sensor, I can help you with the pipeline setup. You
> can run the following commands to capture 5 raw images.
>
> ./media-ctl -r -l '"mt9v032 2-005c":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'
ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]'
Resetting all links to inactive
Setting up link 16:0 -> 5:0 [1]
Setting up link 5:1 -> 6:0 [1]
> ./media-ctl -f '"mt9v032 2-005c":0[SGRBG10 752x480], "OMAP3 ISP CCDC":1[SGRBG10 752x480]'
CCDC":1[SGRBG10 752x480]'
Setting up format SGRBG10 752x480 on pad mt9v032 3-005c/0
Format set: SGRBG10 752x480
Setting up format SGRBG10 752x480 on pad OMAP3 ISP CCDC/0
Format set: SGRBG10 752x480
Setting up format SGRBG10 752x480 on pad OMAP3 ISP CCDC/1
Format set: SGRBG10 752x480
> ./yavta -p -f SGRBG10 -s 752x480 -n 4 --capture=5 --skip 4 -F $(./media-ctl -e "OMAP3 ISP CCDC output")
$(./media-ctl -e "OMAP3 ISP CCDC output")
Device /dev/video2 opened: OMAP3isp_video_pix_to_mbus: mbus->code=0x0000
ISP CCDC output (media).
isp_video_mbus_to_pix: mbus->code=0x300A
Video format set: width: 752 height: 480 buffer size: 721920
Video format: BA10 (30314142) 752x480
4 buffers requested.
length: 721920 offset: 0
Buffer 0 mapped at address 0x402e6000.
length: 721920 offset: 724992
Buffer 1 mapped at address 0x40427000.
length: 721920 offset: 1449984
Buffer 2 mapped at address 0x405bc000.
length: 721920 offset: 2174976
Buffer 3 mapped at address 0x40704000.
Press enter to start capture
isp_video_mbus_to_pix: mbus->code=0x300A
And then it hangs. I'm trying to run a bt but I think mbus->code=0x0000
is the problem. Not sure where it stems from though. Thoughts?
--
Neil
next prev parent reply other threads:[~2011-02-04 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-26 19:32 omap3-isp segfault Neil MacMunn
2011-01-27 1:43 ` Neil MacMunn
2011-01-27 12:25 ` Laurent Pinchart
2011-01-27 12:28 ` Laurent Pinchart
2011-01-27 22:44 ` Neil MacMunn
2011-01-28 22:19 ` Eino-Ville Talvala
2011-02-01 12:53 ` Teemu Tuominen
2011-02-04 22:33 ` Neil MacMunn [this message]
[not found] ` <4D4C7E24.6000004@gumstix.com>
2011-02-09 23:44 ` Laurent Pinchart
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=4D4C7ED2.4060600@gumstix.com \
--to=neil@gumstix.com \
--cc=linux-media@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox