PIC Device Programmer Speed Comparison

The table below indicates the elapsed real time in seconds from when a programming operation is initiated by the user until the the programmer ceases performing operations on the target.  This includes any verification of the programmed data. 

The Verify column indicates the number of verify passes performed by that programmer.  Unless otherwise noted, two verify passes indicates the programmer verifies at both Vdd limits of the device, and one verify pass means the programmer verifies at the programming voltage or the supplied Vdd voltage. 

There are two values for each target PIC type.  The first is how long it takes to program an empty PIC and the second how long to program a full PIC.  Empty means that all programmable bits are set to the erased state, even though they may be specified in the HEX file.  Full means that all of program and data memory (when available) was programmed with random number sequences.  This is intended to prevent any optimizations or compression of data, and should represent the worst case upper limit on programming time. 

The purpose of the chart is to compare various PIC programmer products.  It is therefore limited to programmers that are currently available to the general public or were in the past and therefore have an installed base.  A programmer need not be for sale as a commercial product.  For example, it could be a publicly available reference design. 

The programming times listed in the chart are in seconds.  Entries are blank if we have no information about that combination of programmer and PIC. 

A number preceeded by a star (*) indicates the note of that number applies.  The notes are listed below the table. 

To be listed here, all test must be run using the same HEX files.  Click on the link and unpack the ZIP file to get the HEX files used.  For each PIC listed there are two files, one for the full case and one for the empty case. 

Notes

1. Data provided by "Jinx" on the PIClist, 4 October 2005.  Using Window XP Pro, 2.4GHz AMD Athlon processor, MPLAB 6.40, Picstart+ PUM firmare 2.4. 

2. A Tait-style programmer uses the signals directly from a standard PC parallel port to control the PIC programming lines.  It is not separately powered and contains no controller.  The driving software toggles the individual parallel port lines directly.  There are many variants of this programmer type, usually home built.  Comparisons are difficult because they depend heavily on the operating system, parallel port driver (if any), and controlling software. 

3. Data provided by Gaston Gagnon on the PIClist, 4 October 2005.  Using PICALL / P16PRO version 0.15alpha dec 2003 software. 

4. May not verify locations programmed to the erased state. 

5. Data provided by Xiaofan Chen on the PIClist, 8 October 2005.  Using Wisp628 1.09 firmware and xwisp2w 1.7.2 on Windows XP SP2 Professional, AMD64 3000+ (1.8GHz) PC with NForce 3 chipset. 

6. Olimex PIC-PG2C

7. Data provided by Denny Esterline on the PIClist, 8 October 2005.  Using IC-Prog 1.05D and a "real" serial port on a 1.3 Ghz Athalon under Win98. 

Comments:

• 
  Using a PICkit2 (1 Verify) to program a 12F675, I get times of 10.6 seconds for both the full and empty cases. This is using PICkit2 software version 1.21.
  
  Cheers,
  Howard Winter
  +
• Here's data for the PICkit 2 v1.20 and pyk version 1.42 (on 64-bit Linux):
  
  10F206: 5.8 seconds
  12F675: 5.1 seconds
  16F876a: 50.0 seconds
  18F2520: 39.6 seconds
  
  pyk performs one readback only. The only M'chip references I could find for multi-voltage readback were for OTP parts. pyk has code to do low-voltage readback, but it is not used because pyk doesn't support OTP parts.
  
  pyk doesn't filter out "blank" data, so the times are the same with blank data and random data.
  
  Regards,
  Mark Rages
  markrages@gmail+
• ***Comments by Xiaofan***
  
  Here are some test results for Wisp628 (using "go" command").
  
  Wisp628 1.09 firmware and xwisp2w 1.7.2 on Windows XP SP2 Professional.
  AMD64 3000+ (1.8GHz) PC with NForce 3 chipset.
  
  18f252.hex: 63.61 sec
  18252_empty.hex: 1.58 sec
  
  E:\Coding\XWISP2172>xwisp2w port 1 go hex\18f252.hex
  xwisp2 version 1.7.02 for Windows (Sep 25 2005, Open Watcom C 1.30)
  File hex\18f252.hex loaded and is Intel Hex format conforming
  Programmer Wisp628, firmware version 1.10
  Detected target: 18F252 revision 04 (ID=0404)
  Target erased
  Transferring image to 18F252 via Wisp628
  Transferring program memory...OK!
  Verifying program memory......OK!
  Transferring ID memory........OK!
  Verifying ID memory...........OK!
  Transferring data memory......OK!
  Verifying data memory.........OK!
  Transferring fuses memory.....OK!
  Verifying fuses memory........OK!
  Write-Verify terminated successfully in 62.23 seconds
  Putting target in run mode
  xwisp2 terminated successfully in 63.61 seconds
  
  E:\Coding\XWISP2172>xwisp2w port 1 go hex\18f252_empty.hex
  xwisp2 version 1.7.02 for Windows (Sep 25 2005, Open Watcom C 1.30)
  File hex\18f252_empty.hex loaded and is Intel Hex format conforming
  Programmer Wisp628, firmware version 1.10
  Detected target: 18F252 revision 04 (ID=0404)
  Target erased
  Transferring image to 18F252 via Wisp628
  Transferring program memory...OK!
  Verifying program memory......OK!
  Transferring ID memory........OK!
  Verifying ID memory...........OK!
  Transferring data memory......OK!
  Verifying data memory.........OK!
  Transferring fuses memory.....OK!
  Verifying fuses memory........OK!
  Write-Verify terminated successfully in 0.19 seconds
  Putting target in run mode
  xwisp2 terminated successfully in 1.58 seconds+

  .