PicKit3 Fun with MPLAB8 & MPLABX when reloading firmware to change device - Page 1
Forum section: electronics / general

author: fourtytwo42
author_rank: Super Contributor
timestamp: January 07, 2024, 04:35:32 pm
content: I apologize if this has already been covered here but I did look!I don't use PICs heavily so I just stick to my old PicKit3 rather than buying anything new, I have a mixture of projects some still using MPLAB8 under windows and some later ones using MPLABX under Linux together with a mixture of targets including PIC16F, PIC18F & PIC24EP.So recently I went to re-program a PIC24EP under MPLAB8/WIN and got the cryptic "programing failure" with no other message , of course I assumed it was hardware and set of to test everything but could find no fault. During testing I tried a PIC18F project again under MPLAB8/WIN and got the even more shocking, device id zero!! making it look even more like dead hardware.To cut a long story short the problem was the use of MPLABX, it had changed something in the PicKit3 making it no longer compatible with the firmware used by MPLAB8,My work around for now is to reload the firmware when changing device using MPLABX even if programming with MPLAB8.I cannot find out where X stores it's firmware files else it might be possible to import them into 8. Unfortunatly Microchip seem to have removed all PicKit3 firmware files from there siteFor reference the versions I am using are MPLAB8.92 with PicKit firmware 01.28.90 & MPLABX5.35 with PicKit firmware 01.56.07MPLAB8.92 is I believe the last version & MPLABX5.35 is the last version I found supporting PicKit3 AND MPASM!Hope this helps someone with the same problem

author: coromonadalix
author_rank: Super Contributor
timestamp: January 07, 2024, 06:12:25 pm
content: you have some other pickit2 pickit3 software, no need of mplab ... cant recall the thread, but it doesnt cost a lot and receives updates

author: 8goran8
author_rank: Contributor
timestamp: January 07, 2024, 07:07:11 pm
content: I am using PICKit3 and MPLAB Integrated Programming Environment (IPE) for Microchip PIC microcontrollers .https://www.microchip.com/en-us/tools-resources/production/mplab-integrated-programming-environment

author: mikeselectricstuff
author_rank: Super Contributor
timestamp: January 07, 2024, 07:19:30 pm
content: If you really need you use MPLAB8, best to keep a PICkit3 specifically for that - cheap clones generally work fine.It's not usually too hard to migrate to MPLABX. Pickit4 avoids the whole changing firmware for different devices thing, which is a PITA

author: fourtytwo42
author_rank: Super Contributor
timestamp: January 07, 2024, 07:46:25 pm
content: Quote from: 8goran8 on January 07, 2024, 07:07:11 pmHi you did not quote the version of IPE but anyway I need a full IDE (debugging, compilation as well) not just a programmer.

author: fourtytwo42
author_rank: Super Contributor
timestamp: January 07, 2024, 07:48:47 pm
content: Quote from: mikeselectricstuff on January 07, 2024, 07:19:30 pmAs much as I agree with you unfortunately MPLABX has already semi-bricked my PK3 but I want it to work on both MPLAB8 & MPLABX.As far as PK4 is concerned it's sooooooooo overpriced I could not possibly justify it!

author: fourtytwo42
author_rank: Super Contributor
timestamp: January 07, 2024, 07:49:43 pm
content: Quote from: coromonadalix on January 07, 2024, 06:12:25 pmAre you talking about a clone ? if so link please.

author: jpanhalt
author_rank: Super Contributor
timestamp: January 07, 2024, 08:33:01 pm
content: Your comment about MPLabX bricking your PK3 brought back painful memories of something similar happening to my ICD3. It was traced to an updated .jam file that I did not want. I use MPLab 8.92.I checked the PK3 .jam file in my system. It is: PIC3FW_012890.jam with a date of 06/13/2013. Check what you have. If you want, I can zip it and upload it here (I hope). There is also a Microchip archive site where it might also be found.

author: Andy Chee
author_rank: Super Contributor
timestamp: January 08, 2024, 07:02:34 am
content: I've been using X with Pckt3 for quite some time now and always wondered what that automatic firmware upgrade was all about. Now I know. And now I know not to interrupt it!

author: fourtytwo42
author_rank: Super Contributor
timestamp: January 08, 2024, 09:48:06 am
content: Quote from: jpanhalt on January 07, 2024, 08:33:01 pmThanks for the reply, mine is exactly the same BUT the problem is it no longer works after the PK3 has been used in conjunction with MPLABX as it changes some other piece of firmware that is not restored when you reload it using MPLAB, so be very careful if you ever decide to try MPLABX, don't be in a hurry to plug your PK3 in to it!!

author: fourtytwo42
author_rank: Super Contributor
timestamp: January 08, 2024, 09:49:39 am
content: Quote from: Andy Chee on January 08, 2024, 07:02:34 amYou are ok if you continue using just MPLABX BUT the PK3 will no longer work with firmware loaded by MPLAB