Author Topic: TL866A issue: "OverCurrent Protection actions!..." trying to program PIC12F675  (Read 1700 times)

0 Members and 1 Guest are viewing this topic.

Offline tupinambaTopic starter

  • Newbie
  • Posts: 5
  • Country: fr
Hi everyone!

This is my first post so thank you for welcoming me aboard.

I've had a TL866CS (upgraded to TL866A a while ago) for about 5 years. I'm running the Minipro app on Win XP (through Virtualbox, on a Linux or a Mac OS, same Win XP image). It has always been working so far.

I did not have the use of it for a year or so and, when I opened the app (v6.16), it read that the app was obsolete and needed to be updated. I did so, upgrading to v6.85... unfortunately. The app demanded i upgrade the firmware, which I did.

Then, when trying to read a PIC 12F675, I got the following message: "OverCurrent Protection actions! External short circuit / IC reverse or damaged!"
Of course, the IC is not reversed. And I've tried multiple new ICs. Reading, Erasing... every action gives the same result.

I read about issues with v 6.85 and corresponding firmware and found Radioman's firmware updater (thank you Radioman!).

I successfully performed the "reverse" firmware update to v 6.82 (firmware 3.2.85). The same error happened after the upgrade.

I also noticed, performing the "System self-check", that there was an error on the Ground Testing #16. I  solved the issue with my soldering iron (probably a cold solder joint) and now everything is OK with the Self-check.

But I still get the same message... And I cannot program my PIC IC...

Any idea about what's going on here?...

Thank you in advance!
 

Online Andy Watson

  • Super Contributor
  • ***
  • Posts: 2130
I also noticed, performing the "System self-check", that there was an error on the Ground Testing #16. I  solved the issue with my soldering iron (probably a cold solder joint) and now everything is OK with the Self-check.
If there was one bad joint, there will likely be others. Have a good look at the pcbs - with a magnifying glass if possible.

With regard to the software/firmware, can you revert to your original configuration?

 

Offline tupinambaTopic starter

  • Newbie
  • Posts: 5
  • Country: fr
Thanks Andy!

I've refluxed a lot of solder joints on the PCBs (preventively). Now the self-check gives no error message.

My original configuration was not working anymore: a message informed me that the app and firmware were obsolete and had to be upgraded when I tried to read / write / ... an IC and I COULD NOT ignore the message and run it anymore (I tend to avoid upgrades when I have a working configuration: in this case I did not have a choice...)

I wonder if I should not disable the overcurrent protection by shorting C22, as I've read. I'm just trying to flash son PICs off-circuit here... the risk seems to me to be pretty low.
But I still don't understand why I get this message.

I may also try to flash using the open-source app developed by David Griffith (https://gitlab.com/DavidGriffith/minipro). I've installed it already, it can get info on mu 12F675 without any overcurrent protection message. I'm just not that comfortable with command lines... And I've found an "issue" on the Gitlab page specifically with the 12F675 https://gitlab.com/DavidGriffith/minipro/-/issues/12 (due to its last bit that is reserved for osc calibration... :scared:
 

Offline tupinambaTopic starter

  • Newbie
  • Posts: 5
  • Country: fr
A little update on my issue...
I've finally managed to get the right syntax with the David Griffith open-source app (thank you David!)

I get the same error message when trying to flash or even read : "Overcurrent protection actions..."

If I try to bypass the protection (I installed a switch to short C22), I have another error message which is not quite reassuring...

Quote
Code: [Select]
minipro -p "PIC12F675" -w m2d2m-mod-v4.HEX
Found TL866A 03.2.85 (0x255)
Warning: Firmware is out of date.
  Expected  03.2.86 (0x256)
  Found     03.2.85 (0x255)
Invalid Chip ID: expected 0x0FC0, got 0x7300 (unknown)
(use '-y' to continue anyway at your own risk)

I did not try to continue....

So my TL866 definitely has an issue, but I don't know where to begin to solve this...
 

Offline coromonadalix

  • Super Contributor
  • ***
  • Posts: 6856
  • Country: ca
the 6.8x versions detects if you have a counterfeit  tl866  or a genuine one

for you pic   do you know someone  with another / any brand programmer ? to do some tests, other pic ic's models ?

are they genuine of fakes ?

and pls upgrade your FW to the latest version,  minipro will nag you time over time

i have 6.85   absolutely no problems since i got a genuine tl866, because the fakes uses compromised serial numbers if i recall 

for the FW upgrades i had in the past, i used a 32bit machine, on 64bit  the FW upgrade failed ??
 

Offline tupinambaTopic starter

  • Newbie
  • Posts: 5
  • Country: fr
Thank you for your answer Coromonadalix!

I'm afraid there's a good chance that my TL866 is not a genuine one... (but not 100% sure)

I've tried multiple types of PICs (again, not 100% sure they are all genuine...)

I used to have another programmer before the TL866, a K150 if I can recall, but I'd have to look for it and I think I changed because it did not work very good...

I'm looking for someone with a programmer in my area (but I moved in recently so I don't now lots of people)

I'm afraid I don't have a 32bit machine anymore... But maybe I should get an old laptop in a thrift shop for this purpose!
 

Offline coromonadalix

  • Super Contributor
  • ***
  • Posts: 6856
  • Country: ca
maybe the upgrade is now doing better  for the last version 6.85  ????

I just had many FW upgrades problems before, and was rendered useless in win64,  until i used a 32 bit machine

you may not suffer from this ?

i know there is some tools floating around to change the tl866 model  to add the isp connector, cant recall if they can change the serial number ??

 

Offline tupinambaTopic starter

  • Newbie
  • Posts: 5
  • Country: fr
Actually I did the thing to change it and add the ISP functionality, worked great...
Yes I might as well try to update the FW again, with a 32 bit machine this time. From where I'm standing, no more harm could be done to a useless programmer !
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf