I'm thinking it's some sort of timing/sync problem. I've got plenty of disk (800G free) and RAM (8G w/ 4G free), and the only other thing plugged into the USB hub is the device I'm debugging (and it's halted). Shutting down the other programs running on the Mac doesn't help. That is what leads me to think it's an MPLAB problem.
CHEAT ENGINE MAC 10.7.5 FULL
Once MPLAB is completely wedged (usually when your brain is full of evidence and you just need that one last test to figure it all out) you have to quit MPLAB, blow away mchpmacusbdevice, fire up MPLAB and all is happy for a while. Unplug the PICkit and let MPLAB pick up the module and it sometimes works, sometimes doesn't pick up the name that has been programmed into the PICkit, and sometimes you get a list of about 6 PICkits to choose from, all with the same name. Invalid command response (sent 0x3f, received 0x71) MPLAB is then hosed, hitting Debug Project gives: If you single step rapidly, it will happen quite quickly. It seems to happen much more quickly if the SFR tab is open and/or you have a lot of variables in that tab. Invalid command response (sent 0x86, received 0x71)
Invalid command response (sent 0x71, received 0圆1)įailed reading bulk data (memory type 13, address 3997 Invalid command response (sent 0圆1, received 0x71) Invalid command response (sent 0x71, received 0x0)įailed reading bulk data (memory type 13, address 3999 Invalid command response (sent 0x71, received 0x0) Single stepping the program, even moderately slowly, will cause MPLAB to get out of sync with the PICkit3 giving output like: I'm debugging my program for a PIC187J50, the output and breakpoint tabs are open with one inactive breakpoint. This problem isn't specific to the 87J50, it also happens with 2620s and others. I haven't seen other reports of this, which is hard to believe, so here we go. It is my opinion (which is mine) that there is a problem in Beta7.12 dealing with the PICkit3.
0 kommentar(er)
