On 12 Apr 2018 at 20:43, Forrest Christian wrote:

> A little trick, in the embedded section of options, there is a checkbox
> which says 'maintain active connection to hardware tool'.  You may want t=
o
> try checking this, as it cuts out all of the overhead of connecting to th=
e
> tool each time you program.

Thanks for the tip! It does seem to streamline things. There is a relay in =
the ICD4=20
that be heard to click off/on during the connect procedure, and this settin=
g skips that=20
most of the time. Obviously it still has to do a full connect every now and=
 then, like=20
after closing/re-opening MPLAB, or unplugging the ICD4.

Side issue: Even with "maintain active connection" I still see 2 resets of =
the target=20
for each build/program/run. My code sends a power up message out the UART, =
so=20
in between the two resets it's letting the target uC run more than long eno=
ugh to=20
send 40 characters @ 115200 bd =3D 3.5ms. Difficult to catch accurately on =
scope,=20
but looks like after a few bursts of 9V (high voltage programming) MCLR is =
held=20
low, gets released for maybe 100ms or so (3V, program runs), then is held l=
ow for=20
another ~400ms (0V =3D reset), then finally is released again (3V, program =
runs).

Not loosing any sleep over it, just a little annoying. Same behaviour obser=
ved with=20
ICD3. I hadn't really noticed before, as in most other projects I've droppe=
d in a=20
bootloader first and then done development iterations & debugging using the=
=20
bootloader to load the code & termninal program to debug.

--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.