You can download many of the older MBLABX versions, V5.35 is the last one that supported assembly programming.
Fortunately, most of the Pic's I use are supported in MPLAB 8.92 which I use with Pickit-2 successfully.

That is very interesting thanks so much. The pickit-2 sounds good i'll have to check if it can do the chips i would like to migrate to.
Believe it or not, i have been using Pickit-1 for 10 years or so, and most people dont even know there was a pickit-1 (ha ha).
It's very good for sure, an entire dev board and was not more than $40 USD, but the chips it can do is VERY limited. In fact, maybe around 20 chips but that's it. Luckily i was able to hack some files to get to some bigger multi-pin chips i needed. Well i should say ONE chip i needed, but it was worth it.
I was going to hack the Vpp pulse voltage but i dont think it will allow the chips i want to do anyway.

Funny though when i went to install MpLab 8.60 over top of 7.60 it said it could not allow it because the former was 'enabled'. I think i have to uninstall 7.60 first.

I love assembler but i did get a little lazy using the Arduino C language with the regular IDE. I noticed much faster turn around. I just dont like the chips as much like the 328p. It's good but not great.

 

MPLAB IDE V8.92 is the last one avail here https://pic-microcontroller.com/mplab-ide-v8-92-free-download/

 

That is very interesting thanks so much. The pickit-2 sounds good i'll have to check if it can do the chips i would like to migrate to.
Believe it or not, i have been using Pickit-1 for 10 years or so, and most people dont even know there was a pickit-1 (ha ha).
It's very good for sure, an entire dev board and was not more than $40 USD, but the chips it can do is VERY limited. In fact, maybe around 20 chips but that's it. Luckily i was able to hack some files to get to some bigger multi-pin chips i needed. Well i should say ONE chip i needed, but it was worth it.
I was going to hack the Vpp pulse voltage but i dont think it will allow the chips i want to do anyway.

Funny though when i went to install MpLab 8.60 over top of 7.60 it said it could not allow it because the former was 'enabled'. I think i have to uninstall 7.60 first.

I love assembler but i did get a little lazy using the Arduino C language with the regular IDE. I noticed much faster turn around. I just dont like the chips as much like the 328p. It's good but not great.

Don't get a Pickit-2/3 unless you have a specific legacy need. The Pickit-4 is highly recommended if you want to use the modern IDE and programming languages.

 

I hope the Pickit 4 works better than the Pickit 3 if using MPLAB IDE, When I have used it I have to jump thro hoops to get it connected and recognized OK.
It seems to want a certain power up-connect sequence.
Pickit 3 works fine on MPLABX V5.35.

 

I hope the Pickit 4 works better than the Pickit 3 if using MPLAB IDE, When I have used it I have to jump thro hoops to get it connected and recognized OK.
It seems to want a certain power up-connect sequence.
Pickit 3 works fine on MPLABX V5.35.

I've used the Pickit-4 extensively on 8, 16, 32-bit chips. It's IMO light-years ahead of the 3 for reliable connections and utility.

Having an external programming socket is a nice accessory too.
https://forum.allaboutcircuits.com/...mixed-signal-oscilloscope.188997/post-1805948

 

Well I guess for now, until I run in to a stumbling block with what I have which is working OK, I may look into an Upgrade!
I am just a bit disappointed that Microchip seems to have abandoned the assembly support that they used to offer.

 

Well I guess for now, until I run in to a stumbling block with what I have which is working OK, I may look into an Upgrade!
I am just a bit disappointed that Microchip seems to have abandoned the assembly support that they used to offer.

When they changed the 8-bit tool chain to support 64-bit hosts the old MPASM days were numbered.

https://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB XC8 PIC Assembler User's Guide 50002974A.pdf
https://ww1.microchip.com/downloads...8 PIC Assembler Migration Guide 50002973A.pdf

 

I hope the Pickit 4 works better than the Pickit 3 if using MPLAB IDE, When I have used it I have to jump thro hoops to get it connected and recognized OK.
It seems to want a certain power up-connect sequence.
Pickit 3 works fine on MPLABX V5.35.

Oh, so you think most of the problems with PK-3 were because of the newer IDE, or just some power connect sequence?

Does PK-4 work with MPLAB IDE at all? I thought it was with just the "X" version.

 

Well I guess for now, until I run in to a stumbling block with what I have which is working OK, I may look into an Upgrade!
I am just a bit disappointed that Microchip seems to have abandoned the assembly support that they used to offer.

That's crummy too. Also not sure what that subscription for C compilers is all about.
My guess is that they saw that C and related compilers allow a faster turn around time for applications. I am also wondering if that gets rid of the pesky bank switching problems.
They also stuck with the "35" instruction set but then moved to "49" or something like that.

I also found it very strange that they would put the TRISIO in a different bank which means longer time to switch between an i/o input and output. In some apps it is better to switch input to output and vice versa rather than use definite high and low outputs, such as in I2C where we should have open drain outputs. Maybe they improved this in later chips.
I am still working with the most ancient chips maybe from as long ago as 2005. They are still very useful though that's amazing. I thought of updating again recently but it's a huge step apparently.

 

IMHO most of the problems with PICkit3 is weak power supply capacity and very sensitive programming circuit. So you must often power circuit with external power and keep programming leads short and straight avoiding long parallel connections to PGD and PGC lines.

 

I am still working with the most ancient chips maybe from as long ago as 2005. They are still very useful though that's amazing. I thought of updating again recently but it's a huge step apparently.

I liked working with baseline PICs, i still remember those old days with tears in my eyes. PICkit1 was my first USB programmer, it was amazing thing after self-made serial or parallel port programmers. Unfortunately i do not have spare time playing with these things, helping one guy with PIC12f509 programming was very fun thing in the last year.

 

I had all kinds of problems with PK3 with MPLABX. I got a PK4, and it solved all the problems. Then I started using my own programming language and I use the command line tool. Both PK3 and PK4 work fine with it!

So I think it was always MPLABX that was the problem. Pretty lame that they could not fix that through many releases of MPLABX when their own command line tool worked fine. I also used ICD3 and it was no better than PK3, cost way more and I managed to brick two of them.

For a new user, I strongly recommend going with PK4. The newer chips it can handle are cheaper, faster and have more and better peripherals than the older chips PK2 and PK3 can handle.

 

When they changed the 8-bit tool chain to support 64-bit hosts the old MPASM days were numbered.

Yes. Because one has something to do with the other.

 

Yes. Because one has something to do with the other.

Mr. D. Head was in control of PK-3 and MPASM.

 

Oh, so you think most of the problems with PK-3 were because of the newer IDE, or just some power connect sequence?
Does PK-4 work with MPLAB IDE at all? I thought it was with just the "X" version.

Under MPLAB IDE, I found that PK-2 is not configured for as many Pic's as the PK-3 , fortunately many of the Pic's I use fall within the PK-2, I found that you have to connect the PK-3 in the order specified in the sheet otherwise you get "Programmer not seen".
PK-4 does not work on the MPLAB IDE.
IOW X ver only.

 

I liked working with baseline PICs, i still remember those old days with tears in my eyes. PICkit1 was my first USB programmer, it was amazing thing after self-made serial or parallel port programmers. Unfortunately i do not have spare time playing with these things, helping one guy with PIC12f509 programming was very fun thing in the last year.

Hi,

I never worked with the baseline PIC's only the midrange. I needed the ADC and i dont think the baseline had that or maybe it's just 8 bit instead of 10. I figure 10 bits should be the minimum or i am wasting my time.
Recently i have seen the newer chips with 12 bit ADC so i got interested in upgrading. Of course other things too that look nice.

 

I had all kinds of problems with PK3 with MPLABX. I got a PK4, and it solved all the problems. Then I started using my own programming language and I use the command line tool. Both PK3 and PK4 work fine with it!

So I think it was always MPLABX that was the problem. Pretty lame that they could not fix that through many releases of MPLABX when their own command line tool worked fine. I also used ICD3 and it was no better than PK3, cost way more and I managed to brick two of them.

For a new user, I strongly recommend going with PK4. The newer chips it can handle are cheaper, faster and have more and better peripherals than the older chips PK2 and PK3 can handle.

That is probably why i did not upgrade sooner. I read about the problems from various sources on the web.
That's good to hear about the PK4. The PK3 problems i think i can attribute to the way big companies work. I dont think they actually USE what they produce sometimes so they have no real idea about the problems that come up. Why they dont pay attention to the user base i cant explain at all.

 

Under MPLAB IDE, I found that PK-2 is not configured for as many Pic's as the PK-3 , fortunately many of the Pic's I use fall within the PK-2, I found that you have to connect the PK-3 in the order specified in the sheet otherwise you get "Programmer not seen".
PK-4 does not work on the MPLAB IDE.
IOW X ver only.

Hello again Max,

Oh that's very interesting. I am wondering now if i should bother with PK3 not only because of the problems but i also want to go with some of the newer chips. I dont want to give up assembler yet though, so not sure what to do right now. It's ridiculous how they change things sometimes. These days every upgrade seems to improve some things and break other things. It's just ideocracy at play.

 

As the embedded development sofware moves ahead faster than some existing embedded systems i decided few years ago keep on one PC MPLAB 8.92 and MPLAB X 4.20 to support old projects if needed (and maybe have fun with old MCUs). On this PC i use PICkit3 and ICD3 with IDEs and PICkit2 with a standalone PK2 app if needed. For the newer projects i use different PC with MPLAB X new versions and ICD4 or PICkit4. Both PCs have Windows 11, no problems so far.

 

Hello again Max,

Oh that's very interesting. I am wondering now if i should bother with PK3 not only because of the problems but i also want to go with some of the newer chips. I dont want to give up assembler yet though, so not sure what to do right now. It's ridiculous how they change things sometimes. These days every upgrade seems to improve some things and break other things. It's just ideocracy at play.

There's a huge amount of inertia in embedded programming and systems. Really old MCU designs are still being used and produced in volume today that are deeply embedded in mission critical systems.
https://www.microchip.com/en-us/products/microcontrollers-and-microprocessors/8-bit-mcus/8051-mcus

Protect the longevity of your 8051-based design by integrating one of our 8051 microcontrollers (MCUs) into your product. While other suppliers have exited this market, we continue to offer an extensive portfolio of proven 8051 devices. Our practice of client-driven obsolescence means that, when possible, we will continue to supply these devices for as long as you need them for use in your new designs as well as in your legacy products.

The most important thing is getting the job done right. There's a lot of really smart people improving products and developments systems for those that require new designs, products and services using feedback from end-users. It's a complex, complicated process that takes time to stabilize, it's not moronic.