Tom Sefranek wrote:
> Which PIC are you not able in include the whole alphabet?
> I've never run out of  code space... ever!

But Tom, didn't you start with the 18C252 (before it was ready) and then
move up from there?  There's a whole world of "little" PICs out there.
You're doing very low volume high cost stuff, but when it's the other way
around the cost of a PIC matters.  Most of my PIC projects are either
pushing cycles, RAM, or code space, although usually not all those together.

I do have this one 16F630 project where everything is tight, but this is a
high volume product and the customer absolutely doesn't want a more
expensive PIC in there.  The feature set is basically defined by what I can
cram into the PIC.  Personally I think this is the fun part.  It's not so
hard to design something when plenty of resources are available.  The real
challenge is optimising capability together with cost.  That's why I
sometimes say our motto is "20 pounds of firmware in a 10 pound PIC".


*****************************************************************
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