PICkit 2 version 2.40 Released (VPP1st, Cal & ID, EEs, UART)

PICkit 2 version 2.40 has been released and is available for download on the PICkit 2 page here.

Updates include:

- New menu option "Tools -> Use VPP First Program Entry" for parts with nMCLR off and ICSP pins as outputs.
- VDD set value retained across application sessions.
- Calibrate Vdd & Set Unit ID
- OSCCAL instruction verification for devices with OSCCAL values in the last Program Memory location.
- UART Communication Tool ""Tools -> UART Tool" allows PICkit 2 to connect to MCU TX and RX pins for debug & development IO.

- Serial EEPROM device programming support for selected devices.
- KEELOQ HCS part programming support for selected devices.
- New MCU Part Support.

See the PICkit 2 v2.40 Readme file for more information.

Dear friend:

I downloaded the new 2.4 version and all works OK. However, after a succesfull build, I  receive a error: PK2Error0027:Failed verify(Address=0x100-Expected value 0x2001 -Value read 0x0).
This is after several builds end emulations. I need to inicialize the computer and some times works OK again. I am working with a 16F887(44Pin demo board,the last MPLAB (7.61a).
Any hints...?
Another question: Can I set the Voltage of the PicKit to other voltage than 5 Volts...
?
Thanks in advance...
Ruben de la Pena

Ruben,
 
For the Verify Failed problem, be sure that LVP is OFF in the configuration bits.  Also be sure that your PICkit 2 VDD output is actually greater than 4.5Volts.  Because it is dependent on the USB port voltage, it can be lower.  This could cause the PIC16F887 not to erase properly.
 
The voltage cannot be set to other than 5 Volts when using with the MPLAB IDE.  However, you can externally power your target at other than 5 Volts and the MPLAB IDE will detect this.
 
 
Please note: To explain the inherent contradiction here on VDD voltages- If the MPLAB *believes* that the PICkit 2 voltage is over 4.5 Volts, it will use the Bulk Erase method which is faster but will not work correctly if the voltage is actually below 4.5 Volts.  If the target is powered externally and MPLAB IDE sees a voltage less than 4.5Volts, it will use the Row Erase method which is slower but works at lower voltages.

The download links seem to be broken as of August 5, 2007.
 
http://ww1.microchip.com/downloads/en/DeviceDoc/PICkit%202%20Setup%20v2.40a.zip
http://ww1.microchip.com/downloads/en/DeviceDoc/PICkit%202%20Setup%20v2.40a%20dotNET.zip

The download links seem to be broken as of August 5, 2007.

 
This appears to be a site-wide problem with downloads.

I updated MPLAB to V7.62 a couple of days ago, thought I'd try to let it work directly with PICKIT2 hardware as a programmer (I usually use the separate PICKIT2 utility V1.21). When I selected PICKIT2 as the programmer it prompted me to download a new OS (V2.xx) to the PICKIT2, so I let it go ahead.
 
For reasons that I can't remember I couldn't get MPLAB just to programme and run the code which I was trying to run on the low pin count demo board, so I sighed and went back to the PICKIT V1.21 utility which, to my dismay, then resolutely refused to work with the PICKIT2. I surmised that the problem must be an incompatibility between PICKIT2 V1.21 utility and PICKIT firmware V2.xx.
 
Only problem was, as PICKIT2 V1.21 was no longer talking to the PICKIT hardware, I couldn't use it to reprogramme the PICKIT2 hardware back to V1.21.
 
So I came to Microchip's site, discovered that there was a hitherto unknown (to me) V2.xx of the PICKIT2 utility. When I downloaded and installed that, it then prompted the download of an absolutely enormous microsoft update (.net version 2). After that, it all worked. But... Only on windows XP.
 
I've just recently started running XP as my main OS here (98SE worked fine, so why not) but at work I just have to make do with whatever old PCs I can lay my hands on and there is not one single XP machine available to me there. In one sudden, unadvertised step you've taken a perfectly good multi-OS compatible utility and made it XP - only. This is a terrible development.
 
For my own situation, I've had to use PICKIT V2.xx to programme the PICKIT2 hardware back to V1.21 so I can continue to use it with with the V1.21 utility both here (where I use XP) and on the 98SE machines at work.
 
I'd rather see the newest versions of firmware for the PICKIT2 hardware tweaked to include a V1.21 emulation / compatibility mode which kicks in whenever the PICKIT V1.21 utility tries to talk to it. That way I'd still be able to use it at work with V1.21, but would have the improved functionality of V2 here at home.
 
I notice that the compatibility / tested section in the readme for the new V2.xx utility only mentions XP. Does that mean it doesn't work with Vista?
 
Regards,
 
Graham 
 
 
 
 
 
 
 

My solution is to have two PICkit 2. One used the new firmware for Windows XP. You can use the other with the old firmware for your old Windows OS or in my case Linux.

The PICkit 2 v2.xx software runs on WIN 98SE and up, although it isn't tested on that OS.  Microchip no longer officially supports Win 98 or Win ME.  I'm not aware of a current issue with Vista, and Vista testing will begin with the next release.
 
Also, it can always be reprogrammed by an version SW by putting it in Bootloader mode per the User's Guide.  (hold the button down while plugging in to USB.)

The new serial EEPROM programming support is a great bonus in this new version, so I will be buying the PICkit 2, instead of the ICD 2. However, I have a question regarding this unit:
 
- I am planning to use the PICkit 2 only as a programmer (since I do not want to upgrade to a newer version of MPLAB IDE other than 7.21 for now), and I do not use debugging at all. I do not like to program my PICs into the final target circuit. I always preferred the old ZIF socket inserting/programming/removing. So I will build a PCB with a 40-pin DIP ZIF socket and several jumpers for connections to different pins (I believe that a similar unit it is used with the ICD 2, but I do not remember the part number and if it is compatible also with the PICkit 2). But my main concern is when it is safe to insert any PIC in the ZIF socket. I do not know if the Vdd from the PICkit 2 is always on. Some programmers mantain all of their lines low or tristated before and after any operation, so there is no problem of spikes into the PIC when inserting/removing. Also, I like to use an external +5 volts power supply since I do not like to experiment problems just because my USB is dropping voltage. Has the PICkit 2 some option to mantain his Vdd to Vss? It does not matter to me if I have to use some transistors to switching my external power supply everytime I want to program a PIC.
 
Thank you very much for any help.

jc40,
 
PICkit 2 allows the user to select whether VDD is always on or only on during programming operations.  The latter allows you to use it with a ZIF socket for programming where all signals are inactive except during programming.
 
PICkit 2 may also be used with an external voltage supply.  It would be possible to drive a switch for this supply from the PICkit 2 VDD pin so the external supply is turned on/off with the PICkit 2 VDD.  However, it is important to be sure the switching delay is very short to avoid timing problems during programming.  I would suggest 5us maximum.
 
Finally, there is the AC162049 Universal Programming Adapater that can be used with PICkit 2 with the AC164110 RJ-11 to ICSP adapter.  One other item of importance is that the resistor R1 must be removed from the Universal Programming Adapter for PICkit 2 use, as the PICkit 2 VPP pin can't support the current to drive the LED.
 
See the low cost demo board page, linked to from the main PICkit 2 webpage.
 

Some vendors supply cheap universal programming modules for ICD2 and PICkit 2.

Eg 1: http://www.pic16.com/wzcapi/mcd2ad.htm (In Chinese)
The cheap one uses  3M ZIF socket (green color) and cost RMB50 (US$1 is about RMB7.8, about US$6.40). The more expensive one uses exchangable ChipTool ZIF (black color) sockets and cost RMB100 (about US$13). I got the cheaper one when one friend bought the ICD2 clone and got it as a pacakge. The problem is that normally the shipment cost from China is quite expensive.

The nice thing about this is that it has a DIP switch to select different PICs. It also has both ICD2 style and PICkit 2 style connector. It also has the capacitors across Vcc/GND in place.

Eg 2: build you own:
http://www.hobbypic.com/index.php?option=com_content&task=view&id=12&Itemid=27



[image]local://29174/5A1D98E4EF91456C95EBD9BF369869E6.jpg[/image]

Attached Image(s)

Thank you for your replies.
 
I will be using PICkit 2 without an external power supply. I really hope that my USB power would be good enough for reliable programming at all times.
 
I reviewed carefully the situation that Graham G explains in this thread. I am using Windows 98 SE too, and I do not plan to upgrade to XP because some legacy issues (software and development tools that I really like and that work better or only in non-XP computers). And if the new -and best- 2.40 version of PICkit should not work in Win98SE, it is useless for me.
 
So I downloaded the "PICkit 2 V2.40 Install with .NET Framework" file (28.3 MB) from the main PICkit web page, and installed it in my Win98SE computer.
 
First, the .NET (2.0) Framework is installed, taking a lot of time, and showing a message telling that "Installation is taking more time than expected", (or something like that). The installation progress bar go the the beginning several times, and I started to believe that in fact, it should be impossible to install it in Win98SE. However, be patient. The .NET 2.0 Framework installs and then the PICkit 2 installation starts and takes only a seconds.
 
Then I executed the "PICkit 2 v2.40" from their desktop icon and the stand-alone programmer application launch without problems (only takes a few seconds to inform that obviously the PICkit 2 is not found).
 
So, I should conclude that the PICkit 2 version 2.40 works in Win98SE (I hope that when I get the PICkit 2 programmer, everything works ok). I do not know if Graham G experienced problems with the installation of .NET or if the stand-alone programmer application is explicity showing some message that XP is required.