Can IGEP CAM BIRD be accessed through v4l2 interface (/dev/video0)? What kind of format does it provide (RGB, YUV, YCrBr, etc)?
Thanks for your replies in advance,
I'll try to answer your questions.
If IGEP CAM BIRD it's not available in our shop you can contact to sales department for more information.
The demo code is based in kernel 3.6.6, you're right, and all the source is available in our git repositories, see the branch linux-3.6.y-mt9v034
The defconfig used is igep00x0_defconfig, also available in repository.
To get images/videos outputs from the sensor you can use media-ctl, gstreamer, yavta and live. The live application that you can found in
is a typical example to set up the camera pipeline and capturing video from sensor. If you see at the code you'll see all the steps to setup the camera.
The lens holder is a Marshall p/n: V-4303.6-1, please the IGEP CAM BIRD Hardware Manual that can be found in ISEE website.
The maxium length that I have tested is 10cm, others lengths needs to be tested. Note that the highest line has a 27MHz signal.
Both, modprobing omap_vout and omap-vout should work.
The live program (see above for the code), simply configures the sensor and the omap3 ISP pipeline to capture images from resizer and paint to vout device.
Accepted Answer0I have some follow-on questions about the CAM Bird:
1) When will the CAM Bird be available?
2) The demo code you provide appears to be based on a 3.6.6 kernel. Please could you provide the .config file for it?
3) With regards to getting at the various video/image outputs from the sensor, please can you share with us which utilities you used and a typical call sequence? For example, did you use media-ctl and yavta?
4) Is the lens holder on this board also a Marshall part (V-LH4)?
5) How long is the 27-way connector from the COM to board and how critical is the length? That is, could it be made longer?
6) Your instructions for running the CAM Bird say to type: 'modprobe omap_vout', should that not be 'modprobe omap
7) What does the 'live' command do?
Thanks in anticipation.
Accepted Answer0I now have a CAM bird board and am following the instructions on the following link [url]http://labs.isee.biz/index.php/Aptina_mt9v034_sensor_V4L2_based_linux_driver[/url] having created a uSD image using the instructions for impatients here [url]http://labs.isee.biz/index.php/Using_IGEP_CAM_Bird_first_steps[/url].
I am trying to capture a still image from the Sensor->CCDC output path.
If I do:
root@igep00x0:~# dmesg | grep mt9
[ 8.166137] mt9v034 3-005c: Probing MT9V034 at address 0x5c [ 8.174377] mt9v034 3-005c: MT9V034 detected at address 0x5c
Your example shows the sensor at 2-005c.
The '-f' option on the media-ctl command is deprecated and '-V' should now be used instead.
The main problem I have is with the yavta command:
yavta -f SGRBG10 -s 752x480 -n 4 --capture=3 /dev/video4 --file=img_#.bin
which gives me the following response:
Device /dev/video4 opened. Device `OMAP3 ISP preview output' on `media' is a video capture device. Video format set: SGRBG10 (30314142) 752x480 (stride 1504) buffer size 721920 Video format: SGRBG10 (30314142) 752x480 (stride 1504) buffer size 721920 4 buffers requested. length: 721920 offset: 0 Buffer 0 mapped at address 0xb6ecf000. length: 721920 offset: 724992 Buffer 1 mapped at address 0xb6e1e000. length: 721920 offset: 1449984 Buffer 2 mapped at address 0xb6d6d000. length: 721920 offset: 2174976 Buffer 3 mapped at address 0xb6cbc000. Unable to start streaming: Invalid argument (22). 4 buffers released.
I have also tried the same command with /dev/video2 instead of /dev/video4 but get the same error.
Device /dev/video2 opened. Device `OMAP3 ISP CCDC output' on `media' is a video capture device. Video format set: SGRBG10 (30314142) 752x480 (stride 1504) buffer size 721920 Video format: SGRBG10 (30314142) 752x480 (stride 1504) buffer size 721920 4 buffers requested. length: 721920 offset: 0 Buffer 0 mapped at address 0xb6f3b000. length: 721920 offset: 724992 Buffer 1 mapped at address 0xb6e8a000. length: 721920 offset: 1449984 Buffer 2 mapped at address 0xb6dd9000. length: 721920 offset: 2174976 Buffer 3 mapped at address 0xb6d28000. Unable to start streaming: Invalid argument (22). 4 buffers released.
I'm not sure why I'm getting the 'Invalid argument (22)' error.