John Nall wrote:
> You lost me there, Wouter.  You mean the Wisp628, when programming a
> chip, doesn't check the device ID against the device the hex file was
> assembled for?

I'm not Wouter, but I want to point out that HEX files unfortunately contain
no direct information on what PIC they are intended for.  This is one of the
reasons my programming softwre has the -PIC command line option.  It allows
specifying the target PIC, and the software will refuse the operation if it
finds a different PIC.

While I'm at it, Wouter was showing how compatible the 16F628, 16F628A, and
16F648A are by explaining that he can program any of these chips from the
same HEX file and they all work as controllers for his Wisp628.


******************************************************************
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