Stuck on first attempt using MPLAB X (PICkit4)

[Demon]

i use mplabx 5.50 with my pk4 , i use mplabx_ipe to pgm with, there probably is a cmdline version that
mcs could use but i cannot be bothered fussing with that junk any longer

Ok, so my dream of using PBP3, MPLAB X and PICKIT4 are not extinguished ... yet.

I must be missing some setting in MPLAB X, or a file somewhere...

These are fresh installs.

I don't want to go back to MCS+, that whole "license only good for a year" bugs me.

[richard]

Ok, so my dream of using PBP3, MPLAB X and PICKIT4 are not extinguished ... yet.

mplabx is not a viable ide for pbp3. its useful to get mpasm and the mplab ipe only for mcs use.
if you want to use it as an ide for pbp3 then use ver 2.35 or older , none of which will allow use a pk4 of course

or use xc8 "C" with latest mplabx

[Demon]

mplabx is not a viable ide for pbp3. its useful to get mpasm and the mplab ipe only for mcs use.
if you want to use it as an ide for pbp3 then use ver 2.35 or older , none of which will allow use a pk4 of course

or use xc8 "C" with latest mplabx

Yeah, just found out the latest MPLAB stops at PICKIT3. What a freaking mess.



I was out of the game for nearly 15 years; the talk of losing MPASM confused me. I thought they were talking about PM, so I just hunched my shoulders and kept on trying.

Going to dish out $50 for MCS+ v5 and give that a try. At least they seem intent on supporting us for now.

[Demon]

So I get MCS+ v5, compiles like a charm, things are so simple again, tried to program, no PICKIT4 from dropdown.



ARGH...

[Demon]

mplabx is not a viable ide for pbp3. its useful to get mpasm and the mplab ipe only for mcs use.
if you want to use it as an ide for pbp3 then use ver 2.35 or older , none of which will allow use a pk4 of course

or use xc8 "C" with latest mplabx

Ah, that's why you use MPLAB IPE, as a programmer software to use PICKIT4. I don't get how you do in-circuit debugging though...?

MPLAB IPE keeps saying

The configuration is set for the target board to supply its own power but no voltage has been detected on VDD. Please ensure you have your target powered up and try again.

My Lab-X1 is powered, the LCD displays the old text from my last project on it. I must have something wired wrong, or I'm not configuring the IPE properly.

Gonna check that tomorrow. Time for bed. I can't even imagine how confusing this must be for newcomers.

[richard]

The configuration is set for the target board to supply its own power but no voltage has been detected on VDD. Please ensure you have your target powered up and try again.

the only over priced dev boards i have are a easypic7 and a handful of curiosity boards [ i usually home brew them ] so you are on your own re dev board connections and settings.

I don't get how you do in-circuit debugging though...?

that has been impossible since mplabx 2.35 [for a poor result] , you need to go back to mplab to do it well


xc8 is the answer , forget pbp

[Ioannis]

If you want all the goodies a modern IDE provides, as Richard noted, forget ancient basic laguage. Go for a new C compiler that supports all new and wonderfull PIC that i wish could use right now. Such as the 18F06Q41.

But PBP3.1 can work with MPLABX 5.35, not beyond that version.

There are other compilers, for example Swordfish that supports only 18F series, but is updating regularly the PIC that it supports. Also Proton Compiler is also a nice solution as it gets support by a large group of users and supports even dsp and 24 series.

I am very sorry to say that PBP is dead and we have to accept that. It won't evolve any more. It was a great compiler and could be the greater of all but people are getting old, retired or leaving this vain world...

Ioannis

[richard]

re icsp directly from mcs see below, a snap is pretty much a pk4, microchip cmd-line i/f for programmers is pretty standard(ish) [for microchip]
not difficult just awkward
https://www.picbasic.co.uk/forum/sho...t=command+line
also
https://support.melabs.com/forum/pic...ity-board-pkob

and hardly worth the effort

[Demon]

Thanks for the links Richard!


UPDATE:

I've since simpified things further to a single blink using internal oscillator.

#CONFIG
    __config _HS_OSC & _WDT_OFF & _WRT_ON & _BODEN_ON & _LVP_OFF  & _CPD_OFF & _PWRTE_OFF & _DEBUG_OFF
#ENDCONFIG

DEFINE  OSC     4

ADCON1 = 7              ' A/D off, all digital

TRISD = %00000000

LED0    VAR     PortD.0

        LOW LED0

START:  HIGH    LED0
        PAUSE   500
        LOW     LED0
        GOTO    START

Finish: end

I've added a custom programmer in MCS+5 using the instructions for IPECMD.EXE.

I now compile and program in MCS+5. A black command box appears, everything seems normal, than FLASH, a message shows up for a millisecond about HEX FILE NOT FOUND (pretty sure that's what it says).

Not sure what's going on, cause I delete all objects in my folder except the source right before I compile, just to make sure everything gets created. The HEX and ASM are right there, I opened them, they look "normal".

The light stays blue on the PICkit4; it doesn't go red like when I tried with MPLAB IPE. I must be messing up my connection to the adapter board. I also remember reading about resistors and capacitors for the PK4, gotta find that again...

UPDATE SOME MORE:

I went back to update the command line to keep the command line window open like this.

And I noticed that it's not letting me complete the EDIT process, the NEXT button doesn't come on, I must have missed that the first time around.