Difference between revisions of "CaspaPX"
(Created page with "== Quickstart == The MT9V032 sensor at the heart off the CaspaPX isn't supported in the mainstream kernel yet, so a little work is necessary to get the camera up and running. =…") |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
The MT9V032 sensor at the heart off the CaspaPX isn't supported in the mainstream kernel yet, so a little work is necessary to get the camera up and running. | The MT9V032 sensor at the heart off the CaspaPX isn't supported in the mainstream kernel yet, so a little work is necessary to get the camera up and running. | ||
| − | == | + | == Quickstart == |
| + | The first steps are important to verify your hardware setup and so you know how to test your customizations later. | ||
| + | === Pre-built Image === | ||
The easiest way to get the camera working is to download a pre-built image from [http://somelink here]. Once your image has booted do one of the following from the serial console: | The easiest way to get the camera working is to download a pre-built image from [http://somelink here]. Once your image has booted do one of the following from the serial console: | ||
| Line 17: | Line 17: | ||
=== Bitbake === | === Bitbake === | ||
| − | |||
If you want a more control over the packages included in your image, you can modify the bitbake recipe used to generate the pre-built image. | If you want a more control over the packages included in your image, you can modify the bitbake recipe used to generate the pre-built image. | ||
| Line 23: | Line 22: | ||
<make your modifications> | <make your modifications> | ||
$ bitbake caspapx-image.bb | $ bitbake caspapx-image.bb | ||
| + | |||
| + | == Customization == | ||
| + | |||
| + | === Hardware Overview === | ||
| + | The OMAP35X processors have dedicated hardware for capturing and processing data from image sensors. The CaspaPX camera sensor outputs raw 10-bit Bayer images which is transfered to the Image Signal Processor (ISP) via a parallel interface. The ISP contains a previewer module that converts the Bayer data to YUYV. This data is accessible as a V4L2 device in /dev/video0. | ||
| + | |||
| + | === Image Signal Processor === | ||
| + | To get the best performance from the camera under other lighting conditions we need to get our hands dirty in the kernel source. | ||
| + | |||
| + | === MT9V032 Driver === | ||
Revision as of 15:49, 21 January 2011
The MT9V032 sensor at the heart off the CaspaPX isn't supported in the mainstream kernel yet, so a little work is necessary to get the camera up and running.
Contents
Quickstart
The first steps are important to verify your hardware setup and so you know how to test your customizations later.
Pre-built Image
The easiest way to get the camera working is to download a pre-built image from here. Once your image has booted do one of the following from the serial console:
# export -DISPLAY :0.0 # gst-launch v4l2src ! xvimagesink
or
# mplayer tv:// -tv driver=v4l2:device=/dev/video0
Or you can open cheese:
<left-click on desktop> Applications > Multimedia > Cheese
Bitbake
If you want a more control over the packages included in your image, you can modify the bitbake recipe used to generate the pre-built image.
$ nano ~/overo-oe/org.openembedded.dev/recipes/images/caspapx-image.bb <make your modifications> $ bitbake caspapx-image.bb
Customization
Hardware Overview
The OMAP35X processors have dedicated hardware for capturing and processing data from image sensors. The CaspaPX camera sensor outputs raw 10-bit Bayer images which is transfered to the Image Signal Processor (ISP) via a parallel interface. The ISP contains a previewer module that converts the Bayer data to YUYV. This data is accessible as a V4L2 device in /dev/video0.
Image Signal Processor
To get the best performance from the camera under other lighting conditions we need to get our hands dirty in the kernel source.
