Electronics > Microcontrollers

I think my ICD3 is shagged

<< < (3/4) > >>

AaronLee:

--- Quote from: SiliconWizard on July 22, 2021, 05:38:28 pm ---
--- Quote from: NorthGuy on July 22, 2021, 02:35:03 pm ---
--- Quote from: SiliconWizard on July 20, 2021, 04:41:27 pm ---But dev tools really started annoying the heck out of me.

--- End quote ---

About half a year ago, it finally got me when it took 3 minutes to open because it was doing "background scanning of projects". So, I switched to a text editor and it works much better for me.

I don't think MPLAB X is so much worse than others. Most all bloated and buggy. And this is not likely to change any time soon :(

--- End quote ---

Yep. I didn't care much about this - when I was still using Microchip MCUs, I never used MPLAB X either. But too bad most Microchip MCUs didn't support standard tools, so you still had to use MPLAB X for certain things. I would use their standalone programming software for flashing the MCUs, much lighter than launching MPLAB X, but still pretty annoying to use.

Oh, and how much I hated all Microchip programmers (from the entry-level ones to the ICD4) requiring a firmware update every time you wanted to connect to a different family of PIC... lasting a couple minutes sometimes. How fricking annoying. To the point that if you were ever working with several PIC families at the same time, you would usually end up buying several programmers. Seriously Microchip...  :--

--- End quote ---
Ditto for most of what you said. MPLAB had lots of bugs/issues and could be annoying at times, but MPLAB X was a huge step backwards in my opinion. I'm forced to use it because MPLAB doesn't support the newer parts/tools, but I'd gladly choose MPLAB over MPLAB X if it supported everything.

Yeah, it's so annoying how it has to redownload firmware, not just when changing to a different PIC family, but also when changing between MPLAB and MPLAB X, or even a different version of MPLAB X. I ended up buying several PIC KIT 3's for the same reason as you did, and marked each one for which family it's for, and then just used those for programming using a fixed version of their IPE, so that I didn't need to wait for reprogramming the firmware each time.

AaronLee:

--- Quote from: Pineapple Dan on July 22, 2021, 01:21:00 pm ---Thx for replies everyone. I will try the old mplab. Am using it with 8bit MCUs the past few day and has been fine, will see what happens when I go back to the 16

--- End quote ---

If it's working with 8-bit PICs, then your ICD3 is probably fine. If you use MPLAB, realize you almost certainly can't just load a project from MPLAB X and have it work in MPLAB. They're not compatible. If you want to use MPLAB, you'll need to remake your projects in MPLAB and I'm not sure if MPLAB can use the newest compilers or not. MPLAB also can't be used with the newest PIC MCUs that came after the last version of MPLAB was released.

Now if you switch between MPLAB and MPLAB X, it's imperative when using the ICD3 to run Microchip's driver switcher and tell it if you're using MPLAB or MPLAB X with the ICD3. If you don't do that, it'll almost certainly not work. I think the PIC Kits work ok without switching, but not the ICD3. And as I mentioned earlier, if you still have a problem manually force the reprogramming of the ICD3 firmware. I run into this issue almost weekly where the programmer doesn't work until I manually do it, rather than letting MPLAB / MPLAB X do it automatically.

I had a customer who had a box of a dozen Microchip programmers he claimed were all dead. He gave them to me and not one of them were dead, but all of them magically started working again just by manually downloading the firmware. I gave him back his box of programmers, all working, told him what to do if they stopped working again, but a year later he told me they all stopped working. I asked him if he manually downloaded the firmware, and he gave me a puzzled look. Sure enough, he didn't take my words seriously, and manually downloading the firmware once again magically fixed all his "broken" programmers. If you're just using one dedicated PIC series, and one fixed version of MPLAB or MPLAB X, this typically isn't an issue. But if you're switching around, the problem will almost certainly rear it's ugly head and you must manually reprogram the firmware to clear it.

Sal Ammoniac:

--- Quote from: AaronLee on July 23, 2021, 12:34:28 am ---Ditto for most of what you said. MPLAB had lots of bugs/issues and could be annoying at times, but MPLAB X was a huge step backwards in my opinion. I'm forced to use it because MPLAB doesn't support the newer parts/tools, but I'd gladly choose MPLAB over MPLAB X if it supported everything.
--- End quote ---

I was so glad to leave MPLAB behind when MPLAB X came out. I hated its dated, Windows 3.1-style MDI interface. Yuck.  :palm:

AaronLee:

--- Quote from: Sal Ammoniac on July 27, 2021, 04:08:08 pm ---
--- Quote from: AaronLee on July 23, 2021, 12:34:28 am ---Ditto for most of what you said. MPLAB had lots of bugs/issues and could be annoying at times, but MPLAB X was a huge step backwards in my opinion. I'm forced to use it because MPLAB doesn't support the newer parts/tools, but I'd gladly choose MPLAB over MPLAB X if it supported everything.
--- End quote ---

I was so glad to leave MPLAB behind when MPLAB X came out. I hated its dated, Windows 3.1-style MDI interface. Yuck.  :palm:

--- End quote ---

But MPLAB was fast. I can't overemphasize how the speed of an IDE is a critical factor for me. A slow IDE slows my productivity way down. For minor changes, the edit/build/debug cycle on MPLAB is several times faster than with MPLAB X. I don't need all the bloated functions of most modern IDEs. Just give me a basic one built for speed, and without major bugs, and I'm happy. I couldn't care less how dated the GUI is, as long as it gets the job done, and it functions like all standard Windows applications.

SteveyG:
Newer versions of MPLAB have increased the programming speed. Make sure the PGC and PGD lengths are short - even the original 200mm programming cables that used to come with the ICD2 no longer work. On the latest version of MPLAB total length usually needs to be less than 150mm.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version