Posts: 276
Joined: Aug. 31, 2007
From: here
Status: offline
Hi
Today I plugged my PICKit 2 in ans started the pickit software. The PICKit isn't bieng detected. The last time I used it I had no problems whatsoever, and after that I packed it into some bubblewrap as I usually do, so nothing happens to it :P
I've tried it on different USB ports, but it still doesn't work. Whats going on? Why has it stopped all of a sudden?
PS. only power LED comes on.
thanks
pinout
< Message edited by PICkit2Dev -- Sep. 11, 2008 10:16:31 AM >
Did you tried push and hold the button then power up your device? this will verify if the micro is functioning or not. Normally the PICkit2 will flash a LED to indicate it needs downloading a new os. If not, probably you need check the USB interface on the PICKit2. Make sure no short-circuit on D(+) pin or Vusb pin on the micro.
Posts: 276
Joined: Aug. 31, 2007
From: here
Status: offline
Hi
The Busy LED blinks when I keep it the button pressed. I downloaded the new firmware for the pickit, but I can't transfer it to it. When I start the pickit software, it says 'pickit 2 not found', and I cannot import a HEX file. I've checked the connections.
Posts: 276
Joined: Aug. 31, 2007
From: here
Status: offline
Hi
When I keep the button pressed and plug in the busy LED blinks and nothing else happens. I tried this with the PICKit plugged into my circuit and I could download the OS to the PICKit. Apparantly my PICKit had no OS when I plugged it in (works now).
I think I read somewhere that pressing the red button when it's plugged in erases the firmware?
Hi, Pinout, Would you please check the USB pin signal on your PICkit2? Normally the D+ pin will measured around 3V. If not, there might be a short-circuit on your board or sth wrong on the on-chip voltage regulator. Best wish,
I have the same issue with the PICKIT 2, so I think I have to buy a new one, but how can I buy a new tool that suddenly stop responding and nothing to do neither microchip?
exactly the same experience here: Red button PICkit2 looses firmware without any reason. Works well recently and is not detected when I want to use it next time.
Had a black button PICkit2 before - this one didn't show up with taht behaviour.
If someone can read the PIC18F2550 in a PICkit 2 with this problem before reprogramming (with another PICkit 2 or ICD 2), save the hex file and post it or email it to me along with the last known firmware version, it would be helpful in tracking down this problem.
ORIGINAL: jmpp O.k. people, just few minutes ago I Posted looking for a solution for this issue and I found. I connected another programmer in the PICkit 2 "J1 Conector" and Download the PIC18F2550 hex file directly, so everything works fine now.
If not, then the bootloader firmware is corrupted for some reason and you have to use another programmer (I use another PICkit 2) to program the PICkit 2 firmware again.
During normal operation, I have never encountered this problem. However, during beta testing of some PC application for Linux, I've encountered this problem a few times and I have the old black button PICKit 2. I believe this is due to the beta PC host software I was testing.
The question is then why the firmware (especially the bootloader firmware) will corrupt?
The Busy LED blinks when I keep it the button pressed. I downloaded the new firmware for the pickit, but I can't transfer it to it. When I start the pickit software, it says 'pickit 2 not found', and I cannot import a HEX file. I've checked the connections.
What should I do?
thanks
It seems Pinout's PICKit2 still got the bootloader partially working.
The same (or at least similar) situation happened to me. After working a couple of times my brand new red button PK2 was not recognized by the PICKIT2 software. Because it was non-responsive there was no way to resquirt the OS. The LED blinked when I held the red button down on power up. I didn't know if it were a firmware or hardware issue. I popped the case on the non-responsive one and attached one of my other PK2s to it via the internal ICSP connector J1. This setup connected OK and I read out the code in the comatose unit. I wrote down the checksum and then I then imported the current OS (PK2V021000.hex) into the PICKIT2 software from the PICKIT2 directory.In doing this I noticed the checksums were a bit different. Before I squirted the current firmware into the comatose unit I read it out and saved it. I did a file compare on the the comatose and valid hex files and this was the result:
The config bits were different. This gave me some hope that it was a firmware issue and not a hardware issue.The modified config bits had changed the BOV from 2 to 4.2 V, and disabled the USB voltage regulator. After rewriting the firmware version PK2V021000.hex the unit came out of the coma and responded to the PICKIT software, and appears to be working OK.
Although I'm not sure of the exact mechanism, here's what I think is the source of this issue: There were a build of PICkit 2 units that were factory programmed with the Brown-out Reset enabled. When enabled, the BOR can cause spurious resets of the PICkit 2 under certain but not uncommon target VDD current conditions. To address this, the PICkit 2 firmware (starting with v2.02) checks CONFIG2L to see if the BOR is enabled, and rewrites it with the BOREN bits cleared. Since this is the bad Config in your dead unit (VREGEN being off will kill it) I suspect this operation is getting corrupted somehow leading to this problem. I'll make sure to address this in the next FW rev (2.30)
In the meantime, possible ways to fix this are: 1) (PREFERRED) Open the problem PICkit 2 unit and reprogram it using firmware version 2.10 or later with another PICkit 2 or ICD 2. The PIC18F2550 ICSP port is the unpopulated J1 header along the side of the PCB. 2) Put in a ticket on support.microchip.com to try to get it replaced. 3) If another unit is not available and you prefer not to do 2), the following can be tried to resurrect a dead unit: (Schematic is in Appendix A of PICkit 2 User Guide) Add a 3-terminal 3.3v regulator to power VUSB (Be sure enough in/out capacitance exists for the chosen regulator) Connect IN to +5V_USB Connect GND to ground Connect OUT to the VUSB (PIC18F2550 pin 14) side of C7
NOTE:Before attempting suggestion #3, verify if this the issue with your PICkit 2 unit. To do this, measure the voltage on pin 14 of the PIC18F2550 while the PICkit 2 is plugged into USB. If you measure 3.3V, this is not the problem with your unit. If you measure no voltage, this may be the issue.
This is strange. Supposely the red button fixed the issue by adding the bleeding resistor.
Wouter's fix is to let the bootloader initiaze the USB stack every time. It seems to me that it is more geared toward the old black button PICkit 2 units.
This is strange. Supposely the red button fixed the issue by adding the bleeding resistor.
Wouter's fix is to let the bootloader initiaze the USB stack every time. It seems to me that it is more geared toward the old black button PICkit 2 units.
This isn't really strange - the problem is likely the corrupted config bits and reprogramming is what fixed it. I doubt it mattered that he used Wouter's bootloader or the standard.
The red button change fixes the "unrecognized device" enumeration problem. However, this problem is different - totally dead unit. No enumeration error. Most likely cause: corrupted config turning off VUSB.
ORIGINAL: tmig The config bits were different. This gave me some hope that it was a firmware issue and not a hardware issue.The modified config bits had changed the BOV from 2 to 4.2 V, and disabled the USB voltage regulator.
This explained why the 3.3V and D+ signal are gone. Very good catch.
I have tried the way 3, and it does work. I wonder if it is possible to remove the 3.3v regulator if I renew the pickit operating system, I tried but failed. So that means I need to add the 3.3V regulator forever?
< Message edited by davidyxw -- Dec. 5, 2007 12:41:45 AM >
Printable Version
All Forums >> [Development Tools] >> Programmers (MPLAB PM3, PICSTART Plus, PICkit 2) >> Dead PICKit 2 problem 
Dead PICKit 2 problem - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread