On Sat, 6 Mar 2004, Mike wrote:
> I might give it a try. I already got one Linux programmer to modify, why not
> two? The question is, even though it supports all the algorithms, how hard is
> it to adapt to 16f648? Does it read the hex file and figure out where the code
> and data goes? - something my old winders programmer couldn't do, though I
> found one that does the 648.

  It does support 16f648 even if I myself have not tested that chip.
It should support the following, but certainly there are some parts,
especially OTP or UV erasable c parts that may have bugs.

pic16c84, pic16cr83, pic16cr84, pic16f83, pic16f84, pic16f84a*,
pic16f87*, pic16f88*, pic16c61, pic16c62, pic16c62a, pic16c62b,
pic16c63, pic16c63a, pic16c64, pic16c64a, pic16c65, pic16c65a,
pic16c65b, pic16c66, pic16c66a, pic16c67, pic16cr62, pic16cr63,
pic16cr64, pic16cr65, pic16c620, pic16c620a, pic16cr620a, pic16c621,
pic16c621a, pic16c622, pic16c622a, pic16f627*, pic16f627a*,
pic16f628*, pic16f628a*, pic16f648a*, pic16ce623, pic16ce624,
pic16ce625, pic16c641, pic16c642, pic16c661, pic16c662, pic16c71,
pic16c710, pic16c711, pic16c712, pic16c715, pic16c716, pic16c717,
pic16c72, pic16c72a, pic16cr72, pic16c73, pic16c73a, pic16c73b,
pic16c74, pic16c74a, pic16c74b, pic16c76, pic16c77, pic16f72*,
pic16f73*, pic16f74*, pic16f76*, pic16f77*, pic16c432, pic16c433,
pic16c781, pic16c782, pic16c745, pic16c765, pic16c770, pic16c771,
pic16c773, pic16c774, pic16f870*, pic16f871*, pic16f872*, pic16f873*,
pic16f873a*, pic16f874*, pic16f874a*, pic16f876*, pic16f876a*,
pic16f877*, pic16f877a*, pic16f818*, pic16f819*, pic16c923, pic16c924,
pic16f630*, pic16f676*, pic12c671*, pic12c672, pic12ce673, pic12ce674,
pic12f629*, pic12f675*, pic18f242*, pic18f248*, pic18f252*,
pic18f258*, pic18f442*, pic18f448*, pic18f452*, pic18f458*,
pic18f1220*, pic18f2220*, pic18f4220*, pic18f1320*, pic18f2320*,
pic18f4320*, pic18f6520*, pic18f6620*, pic18f6720*, pic18f8520*,
pic18f8620*, pic18f8720*, pic18f6585*, pic18f8585*, pic18f6680*,
pic18f8680*, pic18f2515*, pic18f2525*, pic18f2585*, pic18f4515*,
pic18f4525*, pic18f4585*, pic18f2610*, pic18f2620*, pic18f2680*,
pic18f4610*, pic18f4620*, pic18f4680*, pic18f6525*, pic18f6621*,
pic18f8525*, pic18f8621*, pic18f2439*, pic18f2539*, pic18f4439*,
pic18f4539*, pic18f2331*, pic18f2431*, pic18f4331*, pic18f4431*,
pic18c242, pic18c252, pic18c442, pic18c452, pic18c658, and pic18c858.

  The devices marked with a star (*) can be autodetected, so they need
not to be specified on command line.

> I think everyone should start naming their programmers with names like Jane,
> Atlas, whatever. I already have "picprg", "progpic2", and your's is "picprog".
> I'm already having a hard time remembering which is which :)

  That's true.  But nobody told me 1996 that I was not the only person in
the world to think that 'picprog' was a good and unique name :-)  There
are a couple of commercial products called Picprog too.

--
Foreca Ltd                                           Jaakko.Hyvatti@foreca.com
Pursimiehenkatu 29-31 B, FIN-00150 Helsinki, Finland     http://www.foreca.com

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