A little trick, in the embedded section of options, there is a checkbox which says 'maintain active connection to hardware tool'. You may want to try checking this, as it cuts out all of the overhead of connecting to the tool each time you program. One caveat, during the ICD4 beta with this checked, the ICD4 would not release the target from reset. I think, but don't know, that this has been resolved. A second caveat, by checking this, you may find you have more frequent issues where mplabx gets out of sync with the tool requiring a exit from mplabx and the ICD. It really depends on what you're doing with the tool whether this happens or not. On Thu, Apr 12, 2018 at 8:05 AM, wrote: > Quoting Steve Smith : > > > One more thing. > > ICD4 wont work with MPLAB 8.92 its not currently supported. > > Some of us old hacks still work in assembly > > > > Steve > > > Using ICD4 with assembly right now (under MPLAB-X, of course). Doesn't > seem faster, just the opposite (I suspect it has more overhead but > runs faster once it gets going, but this is just a little bitty 7kB > chip) and suffers some communication glitches compared to ICD3, in my > experience so far. > > The case is heavy enough to hurt if it falls on your foot, and the LEDs > are amusing enough. > > --sp > > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 forrestc@imach.com | http://www.packetflux.com --=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 .