> I think programming can be measured by a stopwatch.

Better: for proggers with a command-line interface you can use dos
comamnds.

> But who 
> has the time to
> measure all the chips (on which chip what programmer performs 
> better). It
> might be an interesting project though to create a table on 
> wiki for example
> and put experiences by contributors, like I have this and 
> that programmer
> and measured the following times on those chips... 

Indeed, interesting. But don't forget to factor out things like .hex
file size (some proggers do a small file significantly faster), PC
speed, etc.

Another variable: the pickit2 programming 16F917 code is fast, but
programming the EEPROM is very slow. And the PC software does not
auto-detect whether EEPROm info is present in the .hex file.

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