>Roland Jollivet  Wrote:
>I'm using ICProg and a AN589 programmer.
>It takes 52s to program the 18F452 (all flash and data)
>
>So I'm wondering if that's reasonable.


Some time ago this was posted on the piclist. Don't know to the day when as 
I just saved the meat of it as a text file. The date of this post is 05/02 
MM/YY

> > Olins programer:
> >       PIC   Program time (sec)   Verify time (sec)
> >   -------   ------------------   -----------------
> >    12F629                 12.9                 2.8
> >    16F628                 23.7                 5.0
> >    16F877                 55.8                18.3
> >    18F452                 36.3                18.3
> >   18F1320                 18.0                 8.6
>
>Hah, some solid figures! Below are the figures for Wisp628/XWisp on an
>XP 2 GHz, via an USB->serial converter. Rob Hamerling will probably be
>able to provide figures that eliminate the XWisp and USB->serial
>aspects.
>
>I just read the chip, saved the file (code,data,fuses, full range of
>each) and timed the 'go' command for that file (= erase, write, verify -
>at one Vcc - Wisp628 is a prototype programmer).
>
>PIC        'go' time (seconds)
>-------    ---
>12F675      18
>16F628      39
>16F877     141
>16F877A     67
>18F452     135
>18F1320     16
>
>Now can anyone create such figures for a bit-banged (parallel port or
>serial port) programmer? And mybe time a PS+ too?
>
>Olin: comparing the figures your writing time for the 18F1320 seems
>high.



>Jan-Erik Soderholm  wrote:
>Is there *any* programmer that doesn't limit the
>programming to the *used* memory ?

Yes, of course. When you can use multi panel mode and write the code full 
code space of a '252 in 2-4 seconds why wouldn't you use it? Down side is 
that you must program the entire code space. Not much of a downside if it 
only takes seconds.

>Roland Jollivet  Wrote:
>Ok, that answers my question, thanks, plus the others' posts.
>If you said, 'gee, I program a F452 in 3s flat, I'd say my 52s is
>unreasonable:)

Well what about 8 seconds flat for a full erase, code, ID, DataEE, config 
write with single pass verify? That is where my latest WARP-13 upgrade is 
at. A "classic" WARP-13 with currently released firmware takes ~22 seconds.


>Olin wrote:
>52 seconds with only a single verify pass is definitely slow, but
>not out of line for a low cost programmer in my opinion.

My thoughts also.

Regards,

Jim





subject=Re:[PIC:] prog time
source= http://www.piclist.com/piclist/2005/02/28/025944a.txt

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist