Installing PBP3.1 with MPLAB 8 AND MPLABX

[tumbleweed]

@MikeBZH,

If you're asking about a way of using the K40 with MPLAB8 the answer is you can't. There's no way of extending the devices supported in the MPLAB8 IDE.

I doubt you'll be able to use the PICKIT2 and the K40 with any of the MPLAB versions. MPLAB8 doesn't support it, and MPLABX with the PICKIT2 doesn't even allow some devices that are supported with v8.

[MikeBZH]

I am currently working with a 18F2685 (my old design) . My purpose was to validate the PBP 3.1 + MPLABX + mpasmx with this PIC I know quite well before making a jump to the 18F27K40.
I understand I will have to go to MPLAB X + PikKit 3 with no chance to stay with MPLAB 8, unfortunately.
My current MPLAB X version is 4.05, the last one available.

My next step is to understand the particularities of the 18F27K40 as explained in the .txt files delivered with PBP 3.1. It seems to imply PPS...

MikeBZH

[Ioannis]

Here in this Melabs Link one can visually see what to do for the setup of PBP in MPLABX.

I was able to follow up to the 2.19 of the video. Then, simulator did nothing for the PORTB. Hoped that the new 4.0.5 version would work...

Ioannis

[mpgmike]

That worked up to the point where I clicked on "Recompile & Debug". It wouldn't build (works fine in PBP3.1). There is no color coding for different classes of commands/variables/etc. Didn't work for me either.

[MikeBZH]

Nice video but where does it come from ?

It arrives when the battle is over but according to YouTube it was produced in March 2017.
This material should have been referenced in MeLabs > Support > Videos. It would have saved hours and hours of hesitating work !

MikeBZH

[MikeBZH]

First run with MPLAB X v4.05 + PicKit 2 + 18F2685 on my target (was perfectly working when devlopped under MPLAB 8 )

I am able to program the target and run it normally, not connected to PicKit 2.
I can launch the debug mode, halt and restart the program but each time I halt, MPLAB displays the message :

"No source code lines were found at current PC 0x178. Open program memory view to see instruction code disassembly."

My interpretation is that there is no way to follow the program execution at the PBP source level. Am I right ?
Also, I did not find any way to set up breakpoints. Double-click on source line does not work.

Again digging deeper and deeper !

MikeBZH

[tumbleweed]

I've not had any luck getting debugging to work with MPLABX v4. It seems each new version of MPLABX gets worse and worse.
I'm not sure what's different, but I've lost interest in finding out. They probably changed the .cof debugging format again.

Your best bet is to stick with MPLAB8 if possible. Doesn't help much with newer chips, but it just seems microchip doesn't care much about getting 3rd party stuff working in the MPLABX ide. They keep changing things with no regard for what they're breaking.

[Demon]

I'm just 5 years late to the party. I came here to post that exact video. I had tried MPLAB way back when with a pre-PBP3 version; never got anywhere and stayed with MCS+.

This time I started right off the bat using MPLAB X v6.05, and this page at MeLabs was totally useless (the utility didn't do "everything"). Off to google and that video was the first thing I tried. Worked as a charm, until I tried loading BLINKY, and it wasn't where it was supposed to be. Argh...

Oh well, at least MPLAB X seems happy with the PBP3 compiler now, no more error.

[Ioannis]

I think MPLABX 5.35 is the latest that can work with PBP 3.1

Ioannis

[Demon]

I think MPLABX 5.35 is the latest that can work with PBP 3.1

Ioannis

Yeah, that's confirmed in a multitude of places.

[Ioannis]

If you can get away with older chips then why not stay on 5.35?

Ioannis