• AVR Freaks

PICkit4 Question

Author
JKMarchal
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2019/09/27 19:31:04
  • Location: 0
  • Status: offline
2019/11/18 18:33:38 (permalink)
0

PICkit4 Question

I hope I am posting this in the correct place. I am wondering if when you use a PICkit for debugging does it affect the way code executes? For example, if my hardware is using the same pins that the PICkit is using, I suppose I should expect some interactions while debugging? Recently I had a project which seemed to show this issue (a 2x16 LCD display), so I moved the LCD data pins to pins that the PICkit does not use and the code ran, where before with the PICkit hanging on the same lines the display had issues... I know that the PICkit uses pins for serial communication, so I guess this shouldn't be a surprise, but can someone confirm this happens, or point me to a place to learn about the potential issues? The PICkit manual "implies" affects but doesn't really expound on them
 
I'm using MPLABX IDE 5.3, and PIC16F690, PIC18F18344, PIC16F1330, PIC16F14K50 currently.
Thanks.
#1

1 Reply Related Threads

    mbrowning
    USNA79
    • Total Posts : 1565
    • Reward points : 0
    • Joined: 2005/03/16 14:32:56
    • Location: Melbourne, FL
    • Status: offline
    Re: PICkit4 Question 2019/11/19 09:44:27 (permalink)
    4.5 (2)
    Says right in the datasheet (PIC16F18344)
    REGISTER 5-2: CONFIGURATION WORD 2: SUPERVISORS
    bit 13 DEBUG: Debugger Enable bit(1)
    1 = OFF Background debugger disabled; ICSPCLK and ICSPDAT are general purpose I/O pins
    0 = ON Background debugger enabled; ICSPCLK and ICSPDAT are dedicated to the debugger

     
    IOW, in debug mode the debug executive takes over ICSP pins (and uses MCLR). So you can't do anything with them, and if external circuitry interferes with them then debugging fails because the debugger can't communicate with the debug executive.

    Go Navy! Beat Army!
    #2
    Jump to:
    © 2019 APG vNext Commercial Version 4.5