I've been working on porting an application from the DM6446 to the OMAP3530. On the DaVinci the CCDC was used for for general data acquisition - a straight passthrough of RAW16 (8-data lines x 2, we use 12-bits) which is then acquired in the application space as a v4l2 buffer.
However, with the ISP on the OMAP this has been much more difficult than originally expected. I've traced up and down through `isp.c`, `ispccdc.c`, `omap34xxcam.c`, `board-omap3beagle-camera.c`, `v4l2_int_device.h`, `videodev2.h`, and others trying my best to create a configuration that simply let's the data through the ISP with a stripped down version of the `mt9t111` (renamed to `fsr172x`), but I keep getting hung up on `isp_wait` and `Ouch!` errors.
The deadline for this project is coming up in just a few short days and I would really appreciate the help.
Current Patches: http://github.com/fastr/fsr172x/tree/master/patches/
Simple Capture Application: http://github.com/fastr/fidcap
Development Blogpost: http://fastr.github.com/articles/dummy-isp-ccdc-driver.html
Specifications:
- RAW 12-bit capture
- 128x16000 resolution (4mb)
- 1 fps
- Vendor-specific extensions for V4L2 params - format, colorspace, etc
- VD/HD can be either master or slave (we can turn signal generation on or off on our sensor)
- As little latency as possible
In addition to benefiting our project, the final documentation would be very beneficial for any TI customer tweaking the ISP/CCDC with vendor specific extensions.
