Helpful ReplyPICKIT3 Programmer-to-go can brick PIC32 chips

Page: 12 > Showing page 1 of 2
Author
Tim hutcheson
Starting Member
  • Total Posts : 24
  • Reward points : 0
  • Joined: 2010/09/18 04:42:26
  • Location: 0
  • Status: offline
2012/02/21 12:21:24 (permalink)
4.33 (3)

PICKIT3 Programmer-to-go can brick PIC32 chips

All,
 
After repeatedly bricking my PIC32MX795F512L's using the PicKit3 programmerand being locked out with "PK3Err0035: Failed to get Device ID" when attempting to connect, I determined that this catastrophic failure (requires new chip) is related to inadvertenly pushing the black Programmer-to-go feature button on the device.  I placed a support ticket regarding this and Microchip was able to confirm that indeed this failure mode is a critical problem and will be resolved by firnmware upgrade as early as possible.
 
Apparently the programmer to go can attempt to program the device without a valid program in memory and consequently leaves the device in a bad state.  I have not tried this with any other chips than the PIC32.
 
So be careful of pushing the button until the firmware updates is available.
 
Tim Hutcheson
#1
Tomw
Starting Member
  • Total Posts : 59
  • Reward points : 0
  • Joined: 2010/11/12 16:48:50
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/02/21 16:26:21 (permalink) ☄ Helpfulby josef2600 2017/01/19 13:04:55
5 (3)
About a million years ago, before I retired, my company had a product with a similar button. We called it the ROAD button, Roll Over And Die. The simple fix was a faucet washer, rubber, 3/16" thick with a hole big enough for the button. Glue it on with some rubber cement. You won't hit it by accident, but can still push it with a pencil point if you need to.
#2
Brick
Super Member
  • Total Posts : 1684
  • Reward points : 0
  • Joined: 2006/05/25 09:10:40
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/02/21 20:47:26 (permalink)
0
Noted!
#3
nmorini
New Member
  • Total Posts : 3
  • Reward points : 0
  • Joined: 2009/06/16 12:42:14
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/02/29 04:59:59 (permalink)
0
Hello all!

I'm having the same problem with 2 UBW32 boards (PIC32MX795F512L). The first board was accidentally "bricked" by a software development team. The second one was "bricked" by me trying to reproduce the fault.

I have opened a support ticket (4 days ago), but I don't have any response from Microchip yet. Would you mind sharing the response you got from Microchip Tim?

Has anyone ever been able to resurrect any of the "Failed to get device ID"  PIC32s? About 5 months ago I had this problem with another UBW32 board and after an afternoon of trying to reprogram it (and a staring contest with the PIC32 and PICkit3), it started working again (and has been since then).

I hope this gets solved soon.

Nicolás
post edited by nmorini - 2012/02/29 18:15:05
#4
newfound
Super Member
  • Total Posts : 1803
  • Reward points : 0
  • Joined: 2003/11/07 12:35:49
  • Status: online
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/02/29 17:56:31 (permalink)
0
Are there any specific technical details as to exactly what "brick" means with regard to the PIC32MX and the PK3?

Does this happen with the PK2 software and firmware?

I am currently doing a port of my programmer software and firmware to the PK2 and plan to add full support for the PIC32MX families.  It just seems a little odd to me that the PK3 cannot recover the PIC32MX. Actually, given other issues with the PK3 maybe it is not so strange at all.

Any insights anyone has as to the exact failure mode would be appreciated so that I may be able to avoid it problem or even offer a PK2 clone that does "unbricking."

 


#5
gmurfitt
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2012/03/03 07:58:35
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/03 08:16:01 (permalink)
5 (1)
This seems ridiculous, I have been using a PICKit3 with a PIC32MX795F512L for the last few weeks and then out of the blue it no longer programs (probably caused by accidently pressing the black button) and I get the famous PK3Err0035 message. 
  
I have an urgent job to get finished and am now dead in the water. It’s amazing when you google this problem just how many people are reporting it; we need a solution to this problem as replacing the chip is not an option and in all honesty is no solution. 
  
Have you had any feedback from Microchip? 
  
Has anybody out there actually found a solution to this problem other than swapping the chip? 
  
Sorry don’t mean to rant but am frustrated (as I assume are a lot of people) at being stuck in this position. 
  
Thanks 
 
Gary
post edited by gmurfitt - 2012/03/03 08:19:41
#6
rshotbolt
Super Member
  • Total Posts : 192
  • Reward points : 0
  • Joined: 2009/01/09 09:00:31
  • Location: Ramsey, England
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/08 05:40:47 (permalink)
0
I've just had exactly the same problem. Then I suddenly remembered seeing the same thing happen with PIC18F87J50 - I fixed that by putting a 100pF cap between PGC and 0V, and removing my 6" programming ribbbon cable and connecting the PICKit3 directly to the programming pins. Just tried the same with my 'bricked' PIC32 and bingo - it works again!!!

Richard
#7
sparkybg
New Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2011/04/11 04:38:22
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/08 20:38:17 (permalink)
0
Any news about correcting stis issue? I have just potentially "bricked" two PIC32MX575F512H! :(

One of them suddenly stopped programming. I restarted everything and nothing changed. I have programmed maybe 20-30 times before this. In fact it runs as it should with the last firmware in it.

I have tried with another PIC32 on another board, and it refuses to get it's ID either. And the second chip was positively OK. There is not any issue with the power (one board is powered by the PICKIT3, and another one has it'own power supply).

I have tried it on dsPIC30F4012 and it is working perfectly with it. 

The first PIC32 that gave this error is maybe fried because of button on it, but I have never touched a button on the second one, ant it is not working either.
#8
AllenF
Senior Member
  • Total Posts : 149
  • Reward points : 0
  • Joined: 2012/02/19 11:32:23
  • Location: United Kingdom
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/08 22:31:28 (permalink)
0
K I`m no expert here but i have made a lot of Cock ups and I (as yet) newfound  haven`t had any problem with the PK2  (although I haven`t tried a 32 yet) the pk2 doesnt want to write anything if its not loaded (but theres no info as to whether or not it UNLOADS the memory???  Maybe the PK3 unloads to a blank eeprom then triesto write the blank in.)
Have you tried disabling the programmerto go bit (set it to program on button) and it should (if reading it right only work ON the button  thus taking out the blank area. (or load a basic template into PTG  then use as normal)
#9
sparkybg
New Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2011/04/11 04:38:22
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/09 03:29:35 (permalink) ☄ Helpfulby josef2600 2017/01/19 13:16:07
5 (1)
I will continue the battle tonight. I will try a brand new PIC32MX675F512H. I will try an MPLAB 8 (as far as I remember it can program MCU even if it cannot read the ID, or the ID is wrong.

If nothing works, I will order a Renesas programmer and a couple or RX62Ns and get rid of this microchip crap. I am tired of these battles. This is a total nonsense. I've got an original programmer, original software, I've read all that is needed, the PCBs are perfect, the voltages are perfect, the capacitors are perfect, and still it is not working. This is totaly unacceptable. And microchip is totally quiet about it, despite the fact that there is more than 10 threads for this same problem on this forum.
#10
sparkybg
New Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2011/04/11 04:38:22
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/10 01:52:17 (permalink)
0
One of the PIC32s was dead on programming. The other one is OK. Somehow the PICKit3 reads it's ID now. The dead chip was А0 revision. I replaced it with a new one, A1 revision. For now everything is OK. I also removed the button on the PICKit3.
#11
Ian.M
Super Member
  • Total Posts : 13078
  • Reward points : 0
  • Joined: 2009/07/23 07:02:40
  • Location: UK
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/10 04:59:19 (permalink) ☄ Helpfulby josef2600 2017/01/19 13:17:46
0
That is somewhat self-defeating.  Next time you need to force bootloader mode to recover a corrupted PICkit 3 you are going to miss that button.

TomW's suggestion of sticking a thick rubber washer on as a guard for the button (#2 above) is more appropriate.  Alternatively, why not replace the tactile switch you removed with one with a shorter button that will be below the case surface?
#12
sparkybg
New Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2011/04/11 04:38:22
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/10 12:09:04 (permalink)
0
Ian.M...Alternatively, why not replace the tactile switch you removed with one with a shorter button that will be below the case surface?
 


I have to admit that this would be a better solution. I can even cut the switch button to shorter length with a dremel or just sand it out with a piece of sandpaper. Anyway, I will leave it removed for now.


#13
Skydec
Starting Member
  • Total Posts : 72
  • Reward points : 0
  • Joined: 2010/04/20 07:28:12
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/03/31 00:46:19 (permalink)
0
I had the same problem to, by accedent I pushed the program button and it won't reconize the chip anymore.
But why I'm at the forum now, because suddenly I have a new problem (out of the blue) when I connect the pickit3, it's drawing to much current from the board (with both of the device) voltage detection is 0.0V

I also want to add that in my opinion the pickit 3 is a piece of cr*p, I have used the pickit2 for many years without problems, with the pickit 3 I have spend hours and hours trying to solve the strange problems...
#14
tronchaviones
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2012/06/20 04:13:16
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/06/20 04:42:32 (permalink)
0
Has already been patched this critical bug?
#15
Sciencefiction68
Starting Member
  • Total Posts : 33
  • Reward points : 0
  • Joined: 2012/10/01 06:15:03
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2012/10/09 15:22:36 (permalink)
0
Hi guys did anybody found any possible solution? I just get the same problem with MA320003 PIC32MX795f512L on it. PK3Err0035: Failed to get Device ID....
#16
neopisha
New Member
  • Total Posts : 14
  • Reward points : 0
  • Joined: 2012/02/22 10:25:55
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2014/07/09 04:31:27 (permalink)
0
I have the same problem with my PIC32MX795f512L. I did not push the PicKit3 button. I test 2 PIC32s on 2 boards and the result is same: PK3Err0035: Failed to get Device ID.... for MPLAB IDE and Failed to get Device ID in MPLAB X.
Any suggestion or help?
Why microchip does not contribute on the forum? Supports for Texas Instruments and Xilinx are great! Or EngineerZone from Analog Device! They are engineers from those companies helping guys like us in the forums. But microchip? Where is your support???
#17
Jim Nickerson
User 452 _
  • Total Posts : 4240
  • Reward points : 0
  • Joined: 2003/11/07 12:35:10
  • Location: San Diego, CA
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2014/07/09 06:26:21 (permalink)
0
neopisha
I have the same problem with my PIC32MX795f512L. I did not push the PicKit3 button. I test 2 PIC32s on 2 boards and the result is same: PK3Err0035: Failed to get Device ID.... for MPLAB IDE and Failed to get Device ID in MPLAB X.
Any suggestion or help?
Why microchip does not contribute on the forum? Supports for Texas Instruments and Xilinx are great! Or EngineerZone from Analog Device! They are engineers from those companies helping guys like us in the forums. But microchip? Where is your support???


I wonder if you have opened a support ticket  ?
#18
neopisha
New Member
  • Total Posts : 14
  • Reward points : 0
  • Joined: 2012/02/22 10:25:55
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2014/07/09 09:50:19 (permalink) ☄ Helpfulby josef2600 2017/01/19 13:25:08
5 (1)
Very good, at least a logo appears!
I hope they don't ask about connection between programmer and PIC32 and PDG, PGC, VPP connections and voltage rails and VPP pull up and decoupling capacitors and etc.!
I am designing embedded systems for almost 10 years and this is the first time I have problem with one!
#19
Tatala
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2015/10/26 05:31:49
  • Location: 0
  • Status: offline
Re:PICKIT3 Programmer-to-go can brick PIC32 chips 2015/10/27 05:25:37 (permalink)
0
neopisha
I have the same problem with my PIC32MX795f512L. I did not push the PicKit3 button. I test 2 PIC32s on 2 boards and the result is same: PK3Err0035: Failed to get Device ID.... for MPLAB IDE and Failed to get Device ID in MPLAB X.
Any suggestion or help?
Why microchip does not contribute on the forum? Supports for Texas Instruments and Xilinx are great! Or EngineerZone from Analog Device! They are engineers from those companies helping guys like us in the forums. But microchip? Where is your support???




I had some problem too. I don't push button. I installed program only 1 time. If I want second time, this error comes.
3 pic32mx795f512l are broken.
#20
Page: 12 > Showing page 1 of 2
Jump to:
© 2017 APG vNext Commercial Version 4.5