Version 3.0.8 released.

[Ioannis]

Henrik is right, no problem with the update.

As for the MPLABX there is no problem in "messing" with it. Just download the beast, install it with a lot of patience and forget it. Also you do not need to uninstall the old version (8.xx) you have.

Ioannis

[aratti]

Eureka! I found the text file with all the registration keys. It was burried into an archive of an old computer that is a couple of years that I don't use it anymore. I was planning to take it to the Council Eco rabbish collector. Thank you Henrik for this thread, that gaves me the opportunity to recover these important documents.

Any way, thank you both for the advice, which are always useful.

Cheers
Al.

[HenrikOlsson]

Great news Al!

I downloaded and installed MPLABX v3.00 and then PBP3.0.8.4. After a reboot the PBP-MPASM tool started and found the MPASMX folder. Now compiling from within Micro Code Studio is using MPASMX (5.62) and my simple test program compiles fine. However, if I don't have the option MPASM Close after assemble ticked I get an Access Violation error after assembly. Ticking that option (which is the way I usually have it) makes the problem go away. Anyone else seeing this?

Then I thougt I'd give MPLABX yet another go.
Needless to say I didn't get far....
I remember needing to download a plugin from MeLabs, can't find it.
Then I remembered this thread (which is for v1.95) and it says to select Tools->Plugins->Available Plugins and choose the PBP Toolchain. No such thing in my installation. In fact, there's nothing in the Available plugins pane.

Skipping that and trying to go Tools->Options->Embedded->Add and pointing it to the PBP3 folder is a no go. Base directory does not contain a toolchain.

Then I messed around a bit with Tools->Options->Embedded->Build Tools->Add Custom Compiler and pointed IT to the PBP3 folder, gave it the location and filename of PBP3, MPASMX and MPLINK etc.
Created a new project, selected PBP3, PICKit3 etc, added a source file to the source folder and clicked Run->Build project at which point it told me the project was empty.

Bloody hell, this is the THIRD time I try to get this thing off the ground but it's so freeking convoluted and instructions is either non existant or not applicable.

Please, anyone with enough knowhow on MPLABX, can you do a detailes step by step guide on how to set it up to work with PBP3. I'll buy you a couple of beers.

/Henrik.

[Acetronics2]

Please, anyone with enough knowhow on MPLABX, can you do a detailes step by step guide on how to set it up to work with PBP3. I'll buy you a couple of beers.

/Henrik.

Hi Henrik

tried MPLABX 3.00 and 3.05 : Both are Buggy, and I cannot open any PbP source file with them.
( files can be opened if you unload PBP plugin ... but no more compiling ! )

so ... MPLABX 2.35 works fine with PBP : keep this version until something really usable is released ...

Alain

[HenrikOlsson]

Thanks Alain!
I can't believe this crap. Melabs says that PBP requires MPLAB X and links to a version (the latest). They say:

PBP includes a purpose-built IDE called MicroCode Studio, but many prefer to work in the well-known MPLAB IDE from Microchip. We include a language tool plugin for MPLAB to allow seamless development using Microchip’s development tools from within MPLAB. Debugging in this environment can be switched from Source to Assembly level for full access to the generated code.

Where's the plugin? Where's the instructions on how to use it?
Never mind, it's doesn't work anyway - with the version MeLabs is linking to.

I'm usually on the defending side when it comes to the what PBP is, what it does and what it can do but when it comes to this MPLAB integration it just sucks.
Apparently it can be made to work, you're the evidence of that, but they're sure ain't helping you out.

Sorry for the rant, had to let off some steam before the morning cofee....

/Henrik.

[Ioannis]

And, out of curiosity, why are you bothering with this MPLABX monster? I installed it just because PBP needs it, and still use MCS to edit and compile the source.

Maybe you need it for Debuging?

Ioannis

[HenrikOlsson]

To get away from MicroCodeStudio which is crashing on me now and again.
To to be able to use source level debugging.
To be able to use revision control (that is of course possible outside of any IDE)
To get code folding in the editor.
To be able to easily see how much RAM is being used.

But mainly to get source level debugging.