The multiple processor solution may well be the way to go.  Especially
when the projects specs are fuzzy, as it lets you design the parts that
are known while the marketing people dither about the rest.  Each little
part can be trouble shot separately and new features are easy to add.
        A few years ago I inherited a failing project with a 386 processor and
an FPGA handling ten timing signals.  I replaced it all with ten PICs
one for each channel, and one 68HC11 "Traffic Cop" to coordinate.  It
was up and running in no time.  Whenever one of the timing channels
changes, we just make up a new channel PIC.

Flexibility wins!

Sherpa Doug

> -----Original Message-----
> From: Olin Lathrop [mailto:olin_piclist@EMBEDINC.COM]
> Sent: Tuesday, July 10, 2001 11:07 AM
> To: PICLIST@MITVMA.MIT.EDU
> Subject: Re: [PIC]: Hardware Design Challenge
>
>
> This message was sent using a character set not supported on
> the Internet Mail Connector. The message text has been placed
> into the attachment: ATT00333.txt. To view, double-click on
> the attachment. If the text isn't displayed correctly, save
> the attachment to disk, and then use a viewer that can
> display the original character set.
>

--
http://www.piclist.com hint: To leave the PICList
mailto:piclist-unsubscribe-request@mitvma.mit.edu