![]() Note that calculations might be different than PICkit 2 the PICkit 2 did not handle multiple code-protect regions or "Zero on CP" devices correctly. ![]() If you want to see them anyway, add the argument "/debug:checksum" (without quotes) to the command line when executing the app. Checksum calculations are disabled in this version while I sort out mismatches with MPLAB.They will both try sending messages to the programmer, causing it much confusion. Do not enable the PICkit 3 as a programmer or debugger in MPLAB while this application is running.Unplugging the PICkit 3 seems to fix the issue (you can then use "Tools" > "Check Communication" to enable the tool). I've been noticing occasional delays when starting the application (the UI does not present itself). ![]() No crash should be fatal to the system you should be able to unplug and replug the tool and restart the app to get going again. Generally, they come when something goes wrong with the tool, such as unplugging it in the middle of an operation. Tracking these down is my biggest goal right now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |