> ICD2 was mentioned, not sure if that is a programmer or not?
I'll give you my standard programmer summary speech, in my
order of preference, starting with my lowest recommendation:
Wisp628- Wouter's cheap (free) design. Getting the first chip
programmed is the only problem; otherwise, the firmware and
software is available freely on the web. Well supported and
AFAIK, popular even among the professionals on the list.
Does only flash chips, usually through ICSP.
WARP-13a- Getting hard to find, apparently; you may snag one
secondhand on ebay or through other routes- beware of
possible counterfeits. MPLAB compatible, or uses its own
software for VERY fast program times. Has the benefit of
programming the obsolete OTP and EEPROM chips, which
neither the Wisp628 nor the ICD2 can. ICSP with it can be
spotty, but is generally quite "do-able".
ICD2- Has the benefit of being an in-circuit debugger as well
as a programmer. Powered from the USB port (if your circuit
is self powered), which reduces the number of wires on your
desk. Cannot program the older parts, which may or may
not be a problem. I'm also irked by the choice of connector
(RJ-12), which is (IMNSHO) among the worst choices, but
you can change that as you see fit.
Note that the PICStart+ isn't on there. Not by mistake, either.
In fairness, I should also give a nod to Olin's EasyProg and
ProProg, although I haven't extensively investigated them.
EasyProg (I believe) is similar in character to the Wisp628
(i.e., freely available online or you can buy a kit from Olin), but
has a few advantages (multiple programming voltages among
them). DEFINITELY check that information before making
any decisions. IANAL, YMMV.
> Wisp628- Wouter's cheap (free) design. Getting the first chip
> programmed is the only problem; otherwise, the firmware and
> software is available freely on the web. Well supported and
> AFAIK, popular even among the professionals on the list.
> Does only flash chips, usually through ICSP.
some notes:
- the design is free for DIY only. you can spare yourself the hassle of
building (and getting your first chips programmed) by buying the kit.
- the range of chips supported by WISP628 is getting a bit behind. I
hope to do something about this, but I can't promise a fixed date.
> (Warp13) Has the benefit of
> programming the obsolete OTP and EEPROM chips
EEPROM chips? I know only one (16C84) and Wips628 (and AFAIK ICD2 too)
can handle this chip.
Wouter van Ooijen
-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu
>ICD2- Has the benefit of being an in-circuit debugger as well
>as a programmer. Powered from the USB port (if your circuit
>is self powered), which reduces the number of wires on your
>desk. Cannot program the older parts, which may or may
>not be a problem. I'm also irked by the choice of connector
>(RJ-12), which is (IMNSHO) among the worst choices
Not if you are on another planet and you want to Call Home.
I proudly announce (it is NOT an AD) I did enhance the DOS version of
the Wisp driver so it burns 16F876A, 16F877A and 16F630. I have also
removed some smaller bugs from the s/w. It works now like a champ. Of
course, the 95% of the work is done by Wouter. If he does not mind,
I can re-send the new version to him. Am I right it is GPL-ed, isn't it?
>> Wisp628- Wouter's cheap (free) design. Getting the first chip
>> programmed is the only problem; otherwise, the firmware and
>> software is available freely on the web. Well supported and
>> AFAIK, popular even among the professionals on the list.
>> Does only flash chips, usually through ICSP.
>
> some notes:
> - the design is free for DIY only. you can spare yourself the hassle of
> building (and getting your first chips programmed) by buying the kit.
> - the range of chips supported by WISP628 is getting a bit behind. I
> hope to do something about this, but I can't promise a fixed date.
>
>> (Warp13) Has the benefit of
>> programming the obsolete OTP and EEPROM chips
>
> EEPROM chips? I know only one (16C84) and Wips628 (and AFAIK ICD2 too)
> can handle this chip.
>
> Wouter van Ooijen
>
> -- -------------------------------------------
> Van Ooijen Technische Informatica: http://www.voti.nl
> consultancy, development, PICmicro products
> docent Hogeschool van Utrecht: http://www.voti.nl/hvu
>
>
> I proudly announce (it is NOT an AD) I did enhance the DOS version of
> the Wisp driver so it burns 16F876A, 16F877A and 16F630. I have also
> removed some smaller bugs from the s/w. It works now like a champ. Of
> course, the 95% of the work is done by Wouter. If he does not mind,
> I can re-send the new version to him.
Please do so.
> Am I right it is GPL-ed, isn't it?
The header of the source says so, so I guess it is!
Wouter van Ooijen
-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu
> ICD2- Has the benefit of being an in-circuit debugger as well as a
> programmer.
Does anybody know how to control ICD2 programming through the command line?
I'm not developing in MPLAB, and would like to automate programming from my
environment. So far the best I could do is an MPLAB macro that imports the
hex file and starts the programming. But I still have to switch to MPLAB
and run that macro there.
> Powered from the USB port (if your circuit is self powered), which
> reduces the number of wires on your desk.
It can be a bit finnicky, though. The ICD2 driver doesn't work well with
standby cycles of my notebook. So every time I come back from standby, I
have to "plug-cycle" the ICD2. And this needs to be done before MPLAB is
loaded (with the ICD2 enabled), or otherwise the "plug-cycle" won't work.
