Byron A Jeff wrote:
> Building infrastructure to start a project is a chore. Something that
> facilitates rapid prototyping for early success would be the ticket.

That's part of the concept behind the QuickProto series
(http://www.embedinc.com/products), coming Real Soon Now (units supposedly
on their way to me from China right now).

> The prototyper would of course have to double as a code dumper so that
> finished project can be transferred off the prototyper.

I don't agree with this at all.  You only need one programmer, or code
dumper if you want to go that route, but you will probably do multiple
projects.  It doesn't make sense to burden each prototyping board with a
programmer.  Besides, my concept of a prototyping board is that it *is* the
finished project for a one-off.  The prototyping board takes care of the
standard infrastructure without dictating the project to the extent
possible, and leaves generous room for you to add your project-specific
stuff.  Of course any infrastructure provided will limit some choices for
the end project, so some judgements and tradeoffs need to be made.  There is
no single right answer.  That's why I plan on making a series of different
QuickProto boards, but also realize that I'll never make everyone happy all
the time.  The QuickProto-01 is my judgement of the most widely appealing
prototyping board for the most common unspecialized middle of the road
project.


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist