From: anex on
hi.. i want to develop an embedded system using a micro controller and a
cmos sensor.. i have chosen atmega16 and c3088 sensor.. however I am
certain that memory constraints will be a problem for storing the images..i
am aware of avrcam and cmucam and realize that such a system is
possible..however i cannot find a way around the memory problem..can
someone please suggest some way to solve this problem...or kindly tell me
about the procedure that is generally followed or is advised in such a
situation...i am a beginner so please forgive my inexperience with such
matters..

the micro controller and cmos sensor can be changed if needed..

thanks in advance..



---------------------------------------
This message was sent using the comp.arch.embedded web interface on
http://www.EmbeddedRelated.com
From: Frank-Christian Krügel on
Am 16.01.2010 15:05, schrieb anex:
> hi.. i want to develop an embedded system using a micro controller and a
> cmos sensor.. i have chosen atmega16 and c3088 sensor.. however I am
> certain that memory constraints will be a problem for storing the images..i
> am aware of avrcam and cmucam and realize that such a system is
> possible..however i cannot find a way around the memory problem..can
> someone please suggest some way to solve this problem...or kindly tell me
> about the procedure that is generally followed or is advised in such a
> situation...i am a beginner so please forgive my inexperience with such
> matters..
>
> the micro controller and cmos sensor can be changed if needed..

Cortex M3 microcontrollers seem to be a better choice to me. The cost of
the microcontroller is nearly the same, but you get much more processor
speed (72 MHz vs 16 MHz), larger bus width (32 vs 8 bits) and a larger
linear address space (4gb vs 64k) for ram.

I'd suggest using a chip with an external memory interface so you can
easily add external ram if you need. The downside is that those chips
are only available in larger TFQP packages that may be difficult to
solder by hand (it is doable). Use pre-manufactured adapter boards then.

I like the STM32 family of chips. ST Micro provides C libraries for all
peripheral functions like i2c or timers or dma. The STM32F103ZE has 72
MHz Clock, 144 pins, a complete external bus interface, so you can
easily add more ram, 512k flash and 64k internal ram. It's avaliable for
14 euros at Digikey.

Why Cortex M3 and not ARM7? Because the ARM7 always needs a bit of asm
startup code. The Cortex M3 can be programmed completely in C and is a
bit easier to handle, and it has much better interrupt interrupt facilities.

There are many other manufacurers of Cortex M3 microcontrollers: Atmel,
NXP, Luminary Micro/TI,... Just have a look.

--
Mit freundlichen Gr��en

Frank-Christian Kr�gel

From: Paul Carpenter on
In article <qfSdnaQRpY0NWszWnZ2dnUVZ_tGdnZ2d(a)giganews.com>,
anex.stormrider(a)gmail.com says...
> hi.. i want to develop an embedded system using a micro controller and a
> cmos sensor..

To do what?

What you are trying to achieve from the system, will determine if the fit
is right.

> i have chosen atmega16 and c3088 sensor.. however I am

Why?

The application requirements determine what you will need, from
lenses to final output data (even if that is just turn a light on).

> certain that memory constraints will be a problem for storing the images..i

Depends what you need to store.

> am aware of avrcam and cmucam and realize that such a system is
> possible..however i cannot find a way around the memory problem..can

First you will have to understand HOW they work.

> someone please suggest some way to solve this problem...or kindly tell me
> about the procedure that is generally followed or is advised in such a
> situation...i am a beginner so please forgive my inexperience with such
> matters..

You are putting the cart before the horse and picking your components
before working out what you need to do.

> the micro controller and cmos sensor can be changed if needed..
>
> thanks in advance..

Until you have worked out what you want to do, and the algorithms for
processing, you do not know what your memory or processing requirements
are.

Then you know what your timing and processing requirements are.

Then you can define camera, memory, processor and what the output
will be (electrical, format or other).

> ---------------------------------------
> This message was sent using the comp.arch.embedded web interface on
> http://www.EmbeddedRelated.com

Which seems to be the source of many I want to use a camera, but have
not done any basic research posts.

--
Paul Carpenter | paul(a)pcserviceselectronics.co.uk
<http://www.pcserviceselectronics.co.uk/> PC Services
<http://www.pcserviceselectronics.co.uk/fonts/> Timing Diagram Font
<http://www.gnuh8.org.uk/> GNU H8 - compiler & Renesas H8/H8S/H8 Tiny
<http://www.badweb.org.uk/> For those web sites you hate
From: Atilla on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/16/2010 05:42 PM, Paul Carpenter wrote:
> Which seems to be the source of many I want to use a camera, but have
> not done any basic research posts.
I think most of them are hobbyists who just want a camera to play with, like
mounting on a Lego robot or so.

Your post was a bit harsh, but it is the truth.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktUZlkACgkQyjWa9oynuqDM4ACfWyOd/ZIf9IXPJiPWpb/sBsOh
PKkAoIfbxcj89S2Z8QrdvVCISJd/FuJR
=0kt/
-----END PGP SIGNATURE-----
From: Atilla on
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/16/2010 03:05 PM, anex wrote:
> however i cannot find a way around the memory problem..can
> someone please suggest some way to solve this problem...or kindly tell me
> about the procedure that is generally followed or is advised in such a
> situation...

This totally depends on what you need to do. You will read the picture line by
line and many of simple detection things can be done with just storing a couple
of lines. If you want something more complicated, you should look for a micro
controller with external RAM interface.

bottom line: first find out what you want to do, then think over what type of
algorithms you want to use, then pick the hardware.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktUamMACgkQyjWa9oynuqBcYACdHQFs6c5vv0NCJ1r/UXcHvHga
XXoAnAoTKdD81t4qRHTifKL6+MpB5gl2
=CDl6
-----END PGP SIGNATURE-----