> > One part of the grunt work is that debugging the programmer would
> > require a know-working blink-a-led program for every taget chip.
> 
> Why?  I don't run code on the target PIC as part of testing a new
> programming algorithm.  Maybe you think that's irresponsible, 
> but don't see how requiring code to run is relevant.

Hmmm. Maybe you are right to some extent. That is, after one program has
run correctly on a set of similar PICs. There are things that
writing/verifying random patterns won't catch, like errors in the
interpretation of the .hex file (generating the .hex file yourself would
not help, you could make the same error!).

But for newbies a set of blink-a-led files is certainly usefull, and it
is also usefull for me to convice a customer that the programming
process works for his particular PIC!

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