Difference between revisions of "OV9653"
From ArmadeusWiki
m (→Links) |
(→Usage) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 4: | Line 4: | ||
==Connecting the 22T1 module to the APF27== | ==Connecting the 22T1 module to the APF27== | ||
| − | * Datasheet of the 22T1 module are available [http:// | + | * Datasheet of the 22T1 module are available [http://www.warf.com/download/150_5644_1.pdf here]. They only detail the hardware interface. |
* Omnivision sensors are easily available but when it comes to obtain the datasheet of the sensor it becomes harder. Even if you find some datasheet, the informations inside must be read with caution: some are erronous. So [http://agate.msoe.edu/gf/project/wiicam/scmsvn/?action=browse&path=/trunk/docs/camera/ here is one of those]. | * Omnivision sensors are easily available but when it comes to obtain the datasheet of the sensor it becomes harder. Even if you find some datasheet, the informations inside must be read with caution: some are erronous. So [http://agate.msoe.edu/gf/project/wiicam/scmsvn/?action=browse&path=/trunk/docs/camera/ here is one of those]. | ||
* This modules needs a Kyocera BTB 24 pins 0.4mm pitch connector (10-5802-024-000-829) to be plugged in. No idea where to find it easily. | * This modules needs a Kyocera BTB 24 pins 0.4mm pitch connector (10-5802-024-000-829) to be plugged in. No idea where to find it easily. | ||
| Line 24: | Line 24: | ||
|--- | |--- | ||
|} | |} | ||
| + | |||
| + | ==Usage== | ||
| + | * Bring module out of powerdown by driving SSI3_TX (pin 30 of port C) as GPIO (through [[GPIOlib]]): | ||
| + | <pre class="apf"> | ||
| + | echo 94 > /sys/class/gpio/export | ||
| + | echo out > /sys/class/gpio/gpio94/direction | ||
| + | echo 0 > /sys/class/gpio/gpio94/value; usleep 100000 | ||
| + | </pre> | ||
| + | |||
| + | * Reset it by driving SSI3_CLK (pin 31 of port C) as GPIO (through [[GPIOlib]]): | ||
| + | <pre class="apf"> | ||
| + | echo 95 > /sys/class/gpio/export | ||
| + | echo out > /sys/class/gpio/gpio95/direction | ||
| + | echo 0 > /sys/class/gpio/gpio95/value; usleep 100000 | ||
| + | echo 1 > /sys/class/gpio/gpio95/value; usleep 100000 | ||
| + | echo 0 > /sys/class/gpio/gpio95/value | ||
| + | </pre> | ||
| + | |||
| + | * Load corresponding drivers: | ||
| + | <pre class="apf"> | ||
| + | # modprobe mx27_camera | ||
| + | |||
| + | Linux video capture interface: v2.00 | ||
| + | mx27-camera mx27-camera.0: initialising | ||
| + | mx27-camera mx27-camera.0: Camera clock frequency: 33250006 | ||
| + | mx27-camera mx27-camera.0: Using EMMA | ||
| + | |||
| + | # modprobe ov96xx | ||
| + | # rmmod ov96xx | ||
| + | # modprobe ov96xx | ||
| + | |||
| + | OmniVision ov96xx sensor driver, at your service | ||
| + | camera 0-0: Camera driver attached to camera 0 | ||
| + | mx27-camera mx27-camera.0: mclk_get_divisor not implemented. Running at max speed | ||
| + | camera 0-0: Detected an ov9652 sensor | ||
| + | camera 0-0: Camera driver detached from camera 0 | ||
| + | </pre> | ||
| + | |||
| + | ===Test=== | ||
| + | * You can then use Armadeus "capture" demo tool to get images from the camera. | ||
| + | * First time you will have to set the camera module registers correctly (not done by the driver yet) by using a custom script ''ov9653_regs.sh'' available [here]. Here is how to proceed: | ||
| + | <pre class="apf"> | ||
| + | # capture & usleep 400000 ; ./ov9653_regs.sh | ||
| + | </pre> | ||
==Links== | ==Links== | ||
Latest revision as of 14:59, 21 January 2014
OV9653 is an Omnivision 1,3 Mpixels sensor that can be found in the following commercial camera modules:
- in the 22T1 module from Microjet (Taiwaneese company). This module seems to be no more available for sale :-(. If you were a VirtualCogs (R.I.P.) owner, you may probably have one.
- C139 of SHCHL (Shangai). Seems to be the same module than 22T1 (to confirm). This module seems still available here (US)
Contents
Connecting the 22T1 module to the APF27
- Datasheet of the 22T1 module are available here. They only detail the hardware interface.
- Omnivision sensors are easily available but when it comes to obtain the datasheet of the sensor it becomes harder. Even if you find some datasheet, the informations inside must be read with caution: some are erronous. So here is one of those.
- This modules needs a Kyocera BTB 24 pins 0.4mm pitch connector (10-5802-024-000-829) to be plugged in. No idea where to find it easily.
Description
- CSI port (8 bits data + 4 bits control signals) is used to transmit images. (10 bits mode not usable on i.MX). These signals are available on the APF27Dev J9 connector (2,5V logic).
- I2C bus is used to configure the sensor. This bus is available on the APF27Dev J8 connector.
- Sensor core power supply (1,8V) is derived from 2,8V of J9.
Adaptation board
Usage
- Bring module out of powerdown by driving SSI3_TX (pin 30 of port C) as GPIO (through GPIOlib):
echo 94 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio94/direction echo 0 > /sys/class/gpio/gpio94/value; usleep 100000
- Reset it by driving SSI3_CLK (pin 31 of port C) as GPIO (through GPIOlib):
echo 95 > /sys/class/gpio/export echo out > /sys/class/gpio/gpio95/direction echo 0 > /sys/class/gpio/gpio95/value; usleep 100000 echo 1 > /sys/class/gpio/gpio95/value; usleep 100000 echo 0 > /sys/class/gpio/gpio95/value
- Load corresponding drivers:
# modprobe mx27_camera Linux video capture interface: v2.00 mx27-camera mx27-camera.0: initialising mx27-camera mx27-camera.0: Camera clock frequency: 33250006 mx27-camera mx27-camera.0: Using EMMA # modprobe ov96xx # rmmod ov96xx # modprobe ov96xx OmniVision ov96xx sensor driver, at your service camera 0-0: Camera driver attached to camera 0 mx27-camera mx27-camera.0: mclk_get_divisor not implemented. Running at max speed camera 0-0: Detected an ov9652 sensor camera 0-0: Camera driver detached from camera 0
Test
- You can then use Armadeus "capture" demo tool to get images from the camera.
- First time you will have to set the camera module registers correctly (not done by the driver yet) by using a custom script ov9653_regs.sh available [here]. Here is how to proceed:
# capture & usleep 400000 ; ./ov9653_regs.sh
