Timeline for Cannot debug project using "MPLAB X IDE" on "PIC32 Bluetooth Audio Development Kit" with "PICkit 3 In-Circuit Debugger"
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Apr 22, 2016 at 3:02 | history | tweeted | twitter.com/StackElectronix/status/723346106667638784 | ||
Apr 21, 2016 at 14:30 | answer | added | Petr Vepřek | timeline score: 4 | |
Apr 20, 2016 at 14:01 | comment | added | Petr Vepřek | I found the problem and will post answer later on. | |
Apr 19, 2016 at 13:14 | comment | added | rdtsc | Is anything using the MCLR, PGD, and/or PGC lines, such as an LED output? Those pins should be considered "dedicated" to debug and not used for anything else. Code or external signals manipulating them can interfere. As can choosing an incorrect powering method in the debugger settings, such as "do not power Vdd of the device" and having the device's own power turned off. (The debugger has the ability to power the target device - with limitations.) Be sure to have the datasheet handy - good idea to print it. | |
Apr 19, 2016 at 12:44 | comment | added | Petr Vepřek | PS: I disabled the watchdog. Pop-up went away. I still get the "not ready for debugging" message. | |
Apr 19, 2016 at 12:24 | comment | added | Petr Vepřek | @rdtsc Thanks. The pop-up says that it will disable the watchdog for the entire session. However, I will experiment further... | |
Apr 19, 2016 at 12:08 | comment | added | rdtsc | You may have to turn off the watchdog timer. With it running, it will expire in a fraction of a second, causing the PIC32 to restart, cancelling debug. That's what the pop-up is implying. | |
Apr 19, 2016 at 7:54 | review | First posts | |||
Apr 19, 2016 at 9:37 | |||||
Apr 19, 2016 at 7:50 | history | asked | Petr Vepřek | CC BY-SA 3.0 |