Tamas Rudnai wrote:
> 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. For that maybe you can
> store a version info in the ID locations and check only that one
> shortly before programming (if version or ID differs program in a
> traditional manner).

That would require a bunch of code for that special case, and then there'd
always be the problem of getting it wrong.  Getting the wrong previous
version or whatever just once will probably negate any savings in
programming time over the life of that development.

My current code always does a bulk erase first, then subsequent code counts
on starting with a blank chip.  I wouldn't really want to change all that to
put in the partial update logic.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist