Stuck on first attempt using MPLAB X (PICkit4)

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

[Demon]

So I deleted and created the custom programmer again and paid attention to the NEXT button.

-TSBUR223673449 -P$target-device$ -F$hex-filename$ -E -M -Y -OL -OB

Nope, NEXT button never comes on, and the command line seems complete if I EDIT the programmer again.



I compile and program again, I see HEX FILE NOT FOUND blink, and the command line window keeps closing despite the new command line.

Via the PICKit3 programmer
-TSBUR171738083 -P$target-device$ -F$hex-filename$ -E -M -Y -OL -OB
or
-TPPK3 -P$target-device$ -F$hex-filename$ -E -M -Y -OL -OB

Command Line Options:
-E erase before programming
-M program entire memory
-Y verify after programming
-OL release from reset
-OB batch mode (leaves cmd line window open)

I'm starting to think the command lines for the PK4 are different...?

[Demon]

I started a thread over at MeLabs with my latest findings.

Hoping someone there can fix me up; I bought my PK4 and MCS+5 from them.

https://support.melabs.com/forum/pic...-5-and-pickit4

[Ioannis]

I am sorry for the troubles you face Robert.

I do not have Pickit4 (yet) and for the 2 or 3 I use a very nice standalone program (https://pickitplus.co.uk).

I asked if they will support Pickit 4 too. Will report back.

I think you can update you PBP license to the latest 3.1.6. See melabs site.

Ioannis

[Demon]

I am sorry for the troubles you face Robert.

I do not have Pickit4 (yet) and for the 2 or 3 I use a very nice standalone program (https://pickitplus.co.uk).

I asked if they will support Pickit 4 too. Will report back.

I think you can update you PBP license to the latest 3.1.6. See melabs site.

Ioannis

Yeah, but I've already spent enough and can't even get a blinky working. Updating PBP isn't going to get this solved either, and I'm not likely to use whatever chip they've added since v3.0.8.4.

Hoping to get some help from MeLabs.

[Ioannis]

Its free for you!

Ioannis

[Demon]

Its free for you!

Ioannis

Nope, $50. Or am I missing out on "special promotion to forum moderators"?

https://store.melabs.com/cat/PBPUP.html