Roman Black wrote:
>I think it is an absolutely brilliant idea Dan, dual
>processing in a very clever form. It also goves the option of
>having different code in each pic for further control of
>energy use vs performance.


Hi Roman, thanks for the nice comments. OK, at your insistence, I
will accept the 2nd gold star for the week - the 1st going to
Tobie Horswill for his desire to be the first to navigate a PIC
around world in a bottle or small boat.
==================


>The ram/eeprom issue may be a problem, as the two PIC would
>not have the same memory, but for some apps this might not
>matter, and in other apps an external eeprom etc would be
>useful anyway, they could share it.


Yes, already thought of this. Details would depend upon the
app.
============


>The only bad point? Maybe the price of two PICs? Maybe you could
>"push me pull me" with a 12xx pic and a f877 or something, with
>them sharing some essential pins like the input/buttons,
>but only the big pic having the output power driver stuff.
>That might work cool too. "big brain small brain" stuff. :o)
>

Yeah, already thought of this, related in my other msg, before
reading your msg. The is the "PICcyBackWartPoacher". Cool, you
saw it, too. Come up with a really weird idea, wait about 10
minutes, and suddenly something more realistic springs to mind.

best regards,
- dan michaels
==============

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.