Hi,
The servo control sounds like a job for the PRU. PRU I/O is also suitable
for interfacing OV7670. Here is a rough but working example for Beaglebone
White:
https://github.com/dinuxbg/pru-gcc-examples/tree/master/ov7670-cam/pru .
Note that the example loader uses Linux and uio_pruss driver
Greetings Dimitar,
I can't thank you enough for the direction (I was afraid no one would want
to slog through all that). I'm also interested in the hardware part of it.
Are there any schematics for interfacing the camera to the board (will I
need caps, resistors, voltage translations)? The few
If you download the above project you'll find:
README.md - general notes on the OV7670 example
ov7670-cam/pru-ov7670-cape/kicad/ - KiCad schematic and PCB design
ov7670-cam/pru-ov7670-cape/releases/ - PDF schematic and gerbers
I did not put buffers because straight connection works fine for me. Bu
Hi Dimitar,
This is perfect! Thanks again for all the info. I'll post back with my
experiences once I have the equipment and get it going. You rock!
On Thursday, April 30, 2015 at 5:06:54 PM UTC-4, din...@gmail.com wrote:
> If you download the above project you'll find:
> README.md - general no
Hi Dimitar,
I wanted to thank you again. With your advice and help, I was able to get
the OV7670 camera working with the BBB. I borrowed some of the code from
your project, and got everything working bare metal. It isn't pretty, but
it works. I posted about the results at
https://groups.google
Greetings Dimitar,
I was wondering if you could offer me some more guidance? I managed to get
an OV7670 working with the PRU (I'm using PRU1), but I have noticed an
issue. If the VSYNC, HREF, PCLK, and XCLK wires are more than 4 inches
long, I get some incomplete or corrupted scan lines. Shorte
Hi,
For prototyping I used 4inch cables, dispersed as far apart from each other
as possible. I had issues due to crosstalk between the wires.
You could try using a ribbon cable where every second wire is connected to
ground (akin to 80-wire 40-pin IDE cables). Try to keep all wire lengths
roug
Hi Dimitar, Thanks for the suggestion. It looks like crosstalk was/is the
issue, but I was thinking it was just the timing wires doing it to one
another. It turns out it is the parallel pixel lines that are doing it to
the timing wires. I moved them away from the timing lines, and the picture
c
Greetings Dimitar,
Sorry to bother you again. Were you able to get the I2C working with the
OV7670? I have it wired up as you do and am trying to read it in Debian
using i2cdetect. Should i2cdetect be able to read the SCCB bus? Any help
appreciated.
Thanks,
Bill
On Thursday, July 9, 2015 at
Oh, but I don't have the PWDN and RESET pins on the OV7670 connected.
On Saturday, August 1, 2015 at 4:41:55 PM UTC-4, Bill M wrote:
> Greetings Dimitar,
>
> Sorry to bother you again. Were you able to get the I2C working with the
> OV7670? I have it wired up as you do and am trying to read it i
Yes, i2cdetect should detect the camera. The C code in host/ov7670-i2c.c
is tested and works.
But there are important prerequisites for the OV7670 I2C communication:
- Ensure XCLK is running.
- Pulse the RESET line and leave it set to VCC.
- Either leave PWDN Not Connected (it has a built
Thanks a million Dimitar! You are, as always, awesome. That did the trick.
The only problem I'm having now is with the color from the modules, it is
practically non-existent. I have tweaked various registers, without much
success (I've gotten a bit of orange for things that are bright red, but
Greetings
I am looking at robotic control systems for something I wish to fabricate.
Downloaded the files listed earlier and I can see that they are programs.
Being a non programmer I may be missing something but I'm not seeing
anything
about the hardware used for control and the software looks a
Hi,
Thanks for taking a look at my code!
The software I've written is not meant to be a comprehensive software
package. There is a folder each for the CM-5 controller and the CM-530
controller. When these are compiled and uploaded to the respective
controller, then when the controller boots up
On Fri, May 1, 2015 at 11:29 AM, Bill M wrote:
> Hi,
>
> Thanks for taking a look at my code!
>
> The software I've written is not meant to be a comprehensive software
> package. There is a folder each for the CM-5 controller and the CM-530
> controller. When these are compiled and uploaded to th
15 matches
Mail list logo
