----- Original Message ----- 
From: "Maarten Hofman" <cashimor@gmail.com>
Subject: Re: [EE][PIC] Why programmers use PICs as controllers?


> I can also tell you from experience, that even with a completely
> compatible parallel port and serial port, the JDM and El Cheapo
> programmers are NOT able to program all Microchip devices. I tried

There really are few limitations on what PICs you can program based on the 
programming hardware.  This is generally controlled more by the software. 
Generic hardware typically has an army of people working on the software, 
and will generally allow you to program more different models that 
proprietary hardware.

But if you want to keep up with the latest and greatest, then Microchip iron 
is obviously the best bet.  However, it is important to keep in mind that 
Microchip doesn't guarentee that some particular programmer will program 
every PIC ever available in the future.  Mchip will make business decisions 
to support, or drop support, of any particular device based on business 
considerations.  So in my view, buying a PICkit or ICD2 or whatever, is 
something of a crap shoot, and maybe more risky than buying/building some 
generic programmer.  But the starting out point is often better, and if the 
device you select is relatively new, then the odds are you will have support 
for at least a few years.

But I do think one needs to look at the device and what it will do 
(including what operating system versions are supported), and consider 
whether the price is worth it for "renting" a programmer for a year or two 
or three or whatever your estimate is.

--McD


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist