CaspaPX - Revision history

Searchworks: relink

2011-03-01T00:53:07Z

relink

Searchworks: relink

2011-03-01T00:52:03Z

relink

Searchworks: relay

2011-03-01T00:38:18Z

relay

Show changes

Neil at 22:49, 21 February 2011

2011-02-21T22:49:07Z

Neil: /* MT9V032 Driver */

2011-02-21T22:27:18Z

‎MT9V032 Driver

Neil: /* 2.6.34 */

2011-02-21T22:24:12Z

‎2.6.34

Neil: /* Bitbake */

2011-02-21T22:07:19Z

‎Bitbake

Neil: /* Test */

2011-02-21T22:05:38Z

‎Test

Neil: /* Install Pre-built Kernel */

2011-02-21T22:05:09Z

‎Install Pre-built Kernel

Ashcharles: Reverted edits by Ashcharles (talk) to last revision by Neil

2011-02-14T23:49:12Z

Reverted edits by Ashcharles (talk) to last revision by Neil

← Older revision		Revision as of 00:53, 1 March 2011
Line 1:		Line 1:
−	For information about the Caspa camera boards, go to the [http://wiki.gumstix.org/index.php?title=Caspa_camera_boards ~~Caspa Camera Boards~~ wiki page].	+	For information about the Caspa camera boards, go to the [http://wiki.gumstix.org/index.php?title=Caspa_camera_boards wiki page].

← Older revision		Revision as of 00:52, 1 March 2011
Line 1:		Line 1:
−	For information about the Caspa camera boards, go to the [http://wiki.gumstix.org/index.php?title=Caspa ~~Caspa~~ wiki page].	+	For information about the Caspa camera boards, go to the [http://wiki.gumstix.org/index.php?title=Caspa_camera_boards Caspa Camera Boards wiki page].

← Older revision		Revision as of 22:49, 21 February 2011
Line 128:		Line 128:

	This is useful for adjusting the filters, white balance, and color blending coefficients used by the ISP preview module. The preview module is used for doing hardware conversion from 10-bit Bayer to YUV. If you are having color problems - especially under certain lighting conditions but not others - look at '''isppreview.c''' and the gamma correction tables in '''drivers/media/video/isp/'''		This is useful for adjusting the filters, white balance, and color blending coefficients used by the ISP preview module. The preview module is used for doing hardware conversion from 10-bit Bayer to YUV. If you are having color problems - especially under certain lighting conditions but not others - look at '''isppreview.c''' and the gamma correction tables in '''drivers/media/video/isp/'''
		+
		+	== Tuning ==
		+
		+	=== Module Parameters ===
		+	By default, auto exposure, auto gain, and high dynamic range are all enabled. You can disable any or all of these to suit your needs by reloading the driver.
		+
		+	Get a list of driver parameters.
		+	# modinfo mt9v032
		+	filename: /lib/modules/2.6.34/kernel/drivers/media/video/mt9v032.ko
		+	license: GPL
		+	author: Ignacio Garcia Perez <iggarpe@gmail.com>
		+	description: mt9v032 camera sensor driver
		+	srcversion: A46920FD64C35A2645E0D54
		+	alias: i2c:mt9v032
		+	depends:
		+	vermagic: 2.6.34 mod_unload modversions ARMv7
		+	parm: sensor_type:Sensor type: "color" or "mono" (charp)
		+	parm: auto_exp:Initial state of automatic exposure (int)
		+	parm: auto_gain:Initial state of automatic gain (int)
		+	parm: hdr:High dynamic range (int)
		+	parm: low_light:Enable companding (int)
		+	parm: hflip:Horizontal flip (int)
		+	parm: vflip:Vertical flip (int)
		+
		+	Depending on the light level, auto exposure might reduce the framerate as low as 15 frames per second. You can disable auto exposure like so:
		+	# rmmod mt9v032;
		+	# insmod /lib/modules/2.6.34/kernel/drivers/media/video/mt9v032.ko auto_exp=0
		+
		+	If this makes your image too dark you can disable auto gain and enable companding mode (more information [http://www.aptina.com/assets/downloadDocument.do?id=668 here]).
		+	# rmmod mt9v032
		+	# insmod /lib/modules/2.6.34/kernel/drivers/media/video/mt9v032.ko auto_exp=0 auto_gain=0 low_light=1
		+
		+	<!-- === Userspace control (IOCTL) === -->

	== External Links ==		== External Links ==

@@ Line 104: / Line 104: @@
 === MT9V032 Driver ===
-If you want to take advantage of an unimplemented sensor feature, change defaults, etc., you need to modify the driver source. First, make sure that you change your kernel configuration to build the MT9V032 as a module unless you're only making a minor change. This will allow you to test your changes
+If you want to take advantage of an unimplemented sensor feature, change defaults, etc., you need to modify the driver source. After you've made a change you can use a script like the following to quickly test your new driver.
   #! /bin/bash <br>
   TARGET_OVERO="root@10.0.1.15"
@@ Line 112: / Line 111: @@
   ssh $TARGET_OVERO 'rmmod mt9v032'
   scp drivers/media/video/mt9v032.ko $TARGET_OVERO:/lib/modules/2.6.34/kernel/drivers/media/video/
-  ssh $TARGET_OVERO 'modprobe mt9v032'
+  ssh $TARGET_OVERO 'insmod /lib/modules/2.6.34/kernel/drivers/media/video/mt9v032.ko'
 === Image Signal Processor ===

@@ Line 72: / Line 72: @@
   $ patch -p1 < mt9v032-2.6.34.patch
-Get the defconfig.
+Get the kernel configuration. This is the same one used for the linux-omap3-caspapx image.
   $ wget http://cumulus.gumstix.org/sources/mt9v032-2.6.34.defconfig
   $ cp mt9v032-2.6.34.defconfig .config
-Add the cross compiler to your path and configure the kernel. The cross compiler location depends on the architecture of your build machine. If you haven't done so yet, you'll need to [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html set up your build environment].
+If you haven't done so yet, you'll need to [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html set up your build environment]. Build the console image. This will ensure that the cross compiler, binutils, and libraries need to compile the kernel are installed.
-−
 Build the console image. This will ensure that the cross compiler, binutils, and libraries need to compile the kernel are installed.
   $ bitbake omap3-console-image
-Add the cross tools to your path.
+Add the cross compiler to your path and configure the kernel. The cross compiler location depends on the architecture of your build machine.
   ''32-bit processors''
   $ export PATH=/home/<username>/overo-oe/tmp/sysroots/i686-linux/usr/armv7a/bin:${PATH} <br />
   ''64-bit processors''
   $ export PATH=/home/<username>/overo-oe/tmp/sysroots/x86_64-linux/usr/armv7a/bin:${PATH}
 Build kernel and modules

@@ Line 48: / Line 48: @@
 == Bitbake ==
-You can build the kernel and modules using bitbake. This allows you to incorporate the kernel with camera drivers into an image of your design.
+You can build the kernel and modules using bitbake. This allows you to incorporate the kernel with camera driver into an image of your design.
   $ bitbake linux-omap3-caspapx
-The kernel and modules will appear in ~/overo-oe/tmp/deploy/glibc/images/overo
+When the build completes, the kernel and modules will appear in ~/overo-oe/tmp/deploy/glibc/images/overo.
 == Customization ==

← Older revision		Revision as of 22:05, 21 February 2011
Line 44:		Line 44:

	# depmod		# depmod
−	~~# modprobe omap34xxcam~~
	# modprobe mt9v032		# modprobe mt9v032

@@ Line 9: / Line 9: @@
 === Install Pre-built Kernel ===
-The easiest way to get started is to replace the kernel and modules of an existing image. This was tested on an Overo Fire with a Tobi expansion board using the desktop image available [http://www.sakoman.com/feeds/omap3/glibc/images/overo/201011150741/ here].
+The easiest way to get started is to replace the kernel and modules of an existing image. This has been tested on an Overo Fire with a Tobi expansion board using the desktop image available [http://www.sakoman.com/feeds/omap3/glibc/images/overo/201011150741/ here].
 Get the kernel and modules.
- $ mkdir ~/caspakernel
+  $ wget http://cumulus.gumstix.org/images/angstrom/misc/caspapx/uImage-2.6.34
- $ cd ~/caspakernel
+  $ wget http://cumulus.gumstix.org/images/angstrom/misc/caspapx/modules-2.6.34.tgz
-  $ wget http://cumulus.gumstix.org/images/caspapx/uImage-2.6.34-r100-overo.bin
- $ mv uImage-2.6.34-r100-overo.bin uImage
-  $ wget http://cumulus.gumstix.org/images/caspapx/modules-2.6.34-r100-overo.tgz
-−
-Extract the modules.
- $ tar -xzf modules-2.6.34-r100-overo.tgz
 Copy to a bootable microSD card.
-  $ cp -r lib /media/mmcblk0p2
+  $ tar -xf modules-2.6.34.tgz -C /media/mmcblk0p2/
-  $ cp uImage /media/mmcblk0p1/uImage
+  $ cp uImage-2.6.34 /media/mmcblk0p1/uImage
-  $ cp uImage /media/mmcblk0p2/boot/uImage
+  $ cp uImage-2.6.34 /media/mmcblk0p2/boot/uImage
 Alternatively, if you have a network connection, you can copy the files without removing the microSD.
   $ scp -r lib root@overo:/
-  $ scp uImage root@overo:/boot/uImage
+  $ scp uImage-2.6.34 root@overo:/boot/uImage
-  $ scp uImage root@overo:/media/mmcblk0p1/uImage
+  $ scp uImage-2.6.34 root@overo:/media/mmcblk0p1/uImage
   $ ssh root@overo 'depmod; shutdown -r now'

← Older revision		Revision as of 23:49, 14 February 2011
Line 1:		Line 1:
−	~~{{Infobox~~
−	~~\|title = CaspaPX Infobox~~
−	~~\|image = [[Image:Altoids.jpg\|200px]]~~
−	~~\|header1 = content1~~
−	~~\|header2 = First set of data~~
−	~~\|label2 = Label~~
−	~~\|data2 = Data~~
−	~~\|header3 = Remove this line (optional)~~
−	~~\|label3 = More Label~~
−	~~\|data3 = More data~~
−	}}
−
	The MT9V032 sensor at the heart off the CaspaPX is not yet supported in the kernel, so a little work is necessary to get the camera up and running.		The MT9V032 sensor at the heart off the CaspaPX is not yet supported in the kernel, so a little work is necessary to get the camera up and running.