> > Also I think if you are using the programmer for developing (so that
> > program-reporogram cycles with only small changes between) then it
> > might be possible to do a binary difference between the last HEX and
> > the new one and send only the area that changed. 

some problems:

- some PICs can program an individual code word, others first require an
erase of a block of code words, so even when only one word changes the
whole word must be reprogrammed

- changes that might seem small (at the C level) like adding a line
'i++' or changing 'i += 1' to 'i += 2' will likely add an extra assembly
statement, which causes all subsequent asm statements to shift. This
will likely cause differences in code page set instructions, causing
even more changes.

end conclusion: maybe maybe worth the effort for some very specific
cases, but definitely not worth the effort for the general case.

But something else: As I understand you can read a (code?) checksum
froms a PIC, even when it is read-protected. Do any programmers that for
verification, instead of reading the whole code space? Alternatively,
are there programmers that read the code space but calculate a checksum
locally and send that to the PC?

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: www.voti.nl/hvu
 

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