Stuck on first attempt using MPLAB X (PICkit4)

[Demon]

SOLVED: Result in post 35.

SUMMARY:

- no SPACES in folder and file name.
- use IPECMD.EXE with command line options (read CommandLineReadmes in C:\MPLABX\v6.05\docs for details).
- use W command line option when PIC is powered by programmer, this was probably the most important thing, my PIC wasn't powered.
- use tool serial number or generic name in command line.

-----------------------------------------------------------------------

Trying to get a simple program working using PBP3, MPLAB X with PICKIT4 and a 16F877 on the Lab X1, but keep getting:

make -f nbproject/Makefile-default.mk SUBPROJECTS= .build-conf
make[1]: Entering directory 'C:/PBP3/Test_programs/Test1_16F877_LabX1'
make[1]: *** No rule to make target '.build-subprojects', needed by '.build-conf'. Stop.
make: *** [.build-impl] Error 2
make[1]: Leaving directory 'C:/PBP3/Test_programs/Test1_16F877_LabX1'
nbproject/Makefile-impl.mk:39: recipe for target '.build-impl' failed

BUILD FAILED (exit value 2, total time: 104ms)

.

REM   ASM
REM       @ DEVICE PIC16F877, HS_OSC, WDT_OFF, PWRT_ON, BOD_ON, LVP_OFF, CPD_OFF, WRT_OFF, DEBUG_OFF, PROTECT_OFF
REM   ENDASM

#CONFIG
    __config _XT_OSC & _WDT_OFF & _WRT_ON & _BODEN_ON & _LVP_OFF  & _CPD_OFF & _PWRTE_OFF & _DEBUG_ON
#ENDCONFIG

DEFINE  OSC     20

TRISD = %00000000

LED0    VAR     PortD.0

        LOW LED0

START:  HIGH    LED0
        PAUSE   500
        LOW     LED0
        GOTO    START

Finish: end

I converted ASM to CONFIG, but that didn't help. I've used that youtube video to include the compiler in MPLAB X, that went super well until I tried an example.

Does our code have to sit in a special folder now?

I read that PBP3 migration PDF, can't see what else I forgot. I'd really like to stick with MPLAB and not return to MCSP+.

[Demon]

Pic of the stuff on the left, and loading error.

[richard]

to the best of my knowledge the last mplabx that was pbp3 compliant was ver 2.35 [and just barely at that] , from ver 5.5 on
mplabx no longer uses the mpasm [mpasmwin] assembler that pbp can only compile from

[Demon]

Then I don't get at all why we can select PBP3 as compiler without getting some sort of incompatibility warning...?

(distant sound of rummaging in a box for MCS+...)

Oh great, MCS+v4 isn't compatible with PBP3, I'd need MCS+ v5.

Might as well check if I can use PICKIT4 with that...

[richard]

its compatible in that smoke is not released when connected

[Demon]

Aaaaaaand I learn on google that MPLAB and MPLAB X is not the same thing. I always thought MPLAB X was just a latest thing, apparently it's not.

Found a post by Acetronics on MeLabs that points to MPLAB.

https://support.melabs.com/forum/pic...=8877#post8877

Gonna try that and see how things go.

[richard]

Might as well check if I can use PICKIT4 with that...

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

[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.