> Note that some ICSP programmers (Wisp628 
> comes to mind)
> *by default* releases the PIC *after* programming.
> All 
> I/O goes high-Z and MCLR is raised.
> 
> This is made so you can easily 
> edit/build/flash/test
> in a very short cycle without disconnecting 
> anything.
> 
> That is the default if you just give the host software
> a "GO 
> myfile.hex" command. There might be some
> switch to prevent the 
> automatic "run" of the target,
> I have not checked right now...

With Wisp628 you can specify separate WRITE, VERIFY etc commands instead
of the GO. But a Wisp628 is not designed to operate a 3.3V target, IHMO
it would not be a good choice for what the OP wants. Maybe the OP should
not use an ICSP progger at all: use a bootloader? But I don't know
whether any 14-pin PIC supports self-programming.

Side note: for proggers there is the prototype/production distinction,
which boils down to verification. What about self-programming. Should it
be classified in the protytype league as far as reliability is
concerned?

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