Hi Laurent & Michael, On Wed, Dec 21, 2011 at 10:50 AM, James <angweiyang@xxxxxxxxx> wrote: > Hi Michael & Laurent, > > On Thu, Dec 15, 2011 at 6:10 PM, Michael Jones > <michael.jones@xxxxxxxxxxxxxxxx> wrote: >> Hi James, > >> Laurent has a program 'media-ctl' to set up the pipeline (see >> http://git.ideasonboard.org/?p=media-ctl.git). You will find many examples >> of its usage in the archives of this mailing list. It will look something >> like: >> media-ctl -r >> media-ctl -l '"OMAP3 ISP CCDC":1 -> "OMAP3 ISP CCDC output":0 [1]' >> media-ctl -l '"your-sensor-name":0 -> "OMAP3 ISP CCDC":0 [1]' >> >> you will also need to set the formats through the pipeline with 'media-ctl >> --set-format'. >> >> After you use media-ctl to set up the pipeline, you can use yavta to capture >> the data from the CCDC output (for me, this is /dev/video2). >> >> >> -Michael > > I encountered some obstacles with the driver testing of my monochrome > sensor on top of Steve's 3.0-pm branch. An NXP SC16IS750 I2C-UART > bridge is used to 'transform' the sensor into a I2C device. > > The PCLK, VSYNC, HSYNC (640x512, 30Hz, fixed output format) are free > running upon power-on the sensor unlike MT9V032 which uses the XCLKA > to 'power-on/off' it. > > My steps, > > 1) media-ctl -r -l '"mono640":0->"OMAP3 ISP CCDC":0:[1], "OMAP3 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] > > 2) media-ctl -f '"mono640":0[Y12 640x512]", "OMAP3 ISP CCDC":1[Y12 640x512]' > > Setting up format Y12 640x512 on pad OMAP3 ISP CCDC/0 > Setting up format Y12 640x512 on pad OMAP3 ISP CCDC/1 > > 3) yavta -p -f Y12 -s 640x512 -n 4 --capture=61 --skip 1 -F `media-ctl > -e "OMAP3 ISP CCDC output"` --file=./DCIM/Y12 > > Unsupported video format 'Y12' > > Did I missed something? > What parameters did you supplied to yavta to test the Y10/Y12 > > Many thanks in adv. > Sorry if duplicated emails received. > > -- > Regards, > James I changed the parameters for yavta from "-f Y12" to "-f Y16" yavta -p -f Y16 -s 640x512 -n 2 --capture=10 --skip 5 -F `media-ctl -e "OMAP3 ISP CCDC output"` --file=./DCIM/Y16 and there are 2 chunks of message at the console now and it ended with "Unable to request buffers: Invalid argument (22).". I've attached the logfile here. (mono640.log) Hope you can assist me to grab the raw Y12 data to file. Many thanks in adv. -- Regards, James
root@overo:media-ctl -r -v -l '"mono640":0->"OMAP3 ISP CCDC":0[1], "OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]' Opening media device /dev/media0 Enumerating entities Found 16 entities Enumerating pads and links Resetting all links to inactive Setting up link 16:0 -> 5:0 [1] Setting up link 5:1 -> 6:0 [1] root@overo:media-ctl -v -f '"mono640":0[Y12 640x512], "OMAP3 ISP CCDC":1[SGRBG12 640x512]' Opening media device /dev/media0 Enumerating entities Found 16 entities Enumerating pads and links Setting up format Y12 640x512 on pad mono640 3-004d/0 Format set: Y12 640x512 Setting up format Y12 640x512 on pad OMAP3 ISP CCDC/0 Format set: Y12 640x512 Setting up format Y12 640x512 on pad OMAP3 ISP CCDC/1 Format set: Y12 640x512 root@overo:yavta -p -f Y16 -s 640x512 -n 2 --capture=10 --skip 5 -F `media-ctl -e "OMAP3 ISP CCDC output"` --file=./DCIM/Y16 Device /dev/video2 opened. ------------[ cut here ]------------ WARNING: at drivers/media/video/omap3isp/ispvideo.c:218 isp_video_set_format+0x50/0x88 [omap3_isp]() Device `OMAP3 ISP CCDC output' on `media' is a video omaplfb capture device. Modules linked in: bufferclass_ti pvrsrvkm ipv6 mono640 libertas_sdio omap3_isp libertas v4l2_common cfg80211 videodev media lib80211 firmware_class ads7846 [<c0045dc4>] (unwind_backtrace+0x0/0x128) from [<c006ba9c>] (warn_slowpath_common+0x4c/0x64) [<c006ba9c>] (warn_slowpath_common+0x4c/0x64) from [<c006bad0>] (warn_slowpath_null+0x1c/0x24) [<c006bad0>] (warn_slowpath_null+0x1c/0x24) from [<bf099e90>] (isp_video_set_format+0x50/0x88 [omap3_isp]) [<bf099e90>] (isp_video_set_format+0x50/0x88 [omap3_isp]) from [<bf01d778>] (__video_do_ioctl+0x11a4/0x516c [videodev]) [<bf01d778>] (__video_do_ioctl+0x11a4/0x516c [videodev]) from [<bf01c458>] (video_usercopy+0x340/0x450 [videodev]) [<bf01c458>] (video_usercopy+0x340/0x450 [videodev]) from [<bf01b448>] (v4l2_ioctl+0x7c/0x12c [videodev]) [<bf01b448>] (v4l2_ioctl+0x7c/0x12c [videodev]) from [<c00e4110>] (do_vfs_ioctl+0x4b0/0x51c) [<c00e4110>] (do_vfs_ioctl+0x4b0/0x51c) from [<c00e41b4>] (sys_ioctl+0x38/0x5c) [<c00e41b4>] (sys_ioctl+0x38/0x5c) from [<c0041240>] (ret_fast_syscall+0x0/0x30) ---[ end trace 6824b735bee150b5 ]--- ------------[ cut here ]------------ WARNING: at drivers/media/video/omap3isp/ispvideo.c:178 isp_video_mbus_to_pix+0x78/0x144 [omap3_isp]() Modules linked in: bufferclass_ti omaplfb pvrsrvkm ipv6 mono640 libertas_sdio omap3_isp libertas v4l2_common cfg80211 videodev media lib80211 firmware_class ads7846 [<c0045dc4>] (unwind_backtrace+0x0/0x128) from [<c006ba9c>] (warn_slowpath_common+0x4c/0x64) [<c006ba9c>] (warn_slowpath_common+0x4c/0x64) from [<c006bad0>] (warn_slowpath_null+0x1c/0x24) [<c006bad0>] (warn_slowpath_null+0x1c/0x24) from [<bf099bfc>] (isp_video_mbus_to_pix+0x78/0x144 [omap3_isp]) [<bf099bfc>] (isp_video_mbus_to_pix+0x78/0x144 [omap3_isp]) from [<bf099ea0>] (isp_video_set_format+0x60/0x88 [omap3_isp]) [<bf099ea0>] (isp_video_set_format+0x60/0x88 [omap3_isp]) from [<bf01d778>] (__video_do_ioctl+0x11a4/0x516c [videodev]) [<bf01d778>] (__video_do_ioctl+0x11a4/0x516c [videodev]) from [<bf01c458>] (video_usercopy+0x340/0x450 [videodev]) [<bf01c458>] (video_usercopy+0x340/0x450 [videodev]) from [<bf01b448>] (v4l2_ioctl+0x7c/0x12c [videodev]) [<bf01b448>] (v4l2_ioctl+0x7c/0x12c [videodev]) from [<c00e4110>] (do_vfs_ioctl+0x4b0/0x51c) [<c00e4110>] (do_vfs_ioctl+0x4b0/0x51c) from [<c00e41b4>] (sys_ioctl+0x38/0x5c) [<c00e41b4>] (sys_ioctl+0x38/0x5c) from [<c0041240>] (ret_fast_syscall+0x0/0x30) ---[ end trace 6824b735bee150b6 ]--- Video format set: (00000000) 640x512 buffer size 0 Video format: (00000000) 640x512 buffer size 0 Unable to request buffers: Invalid argument (22).
