User manual

mikroC PRO for PIC32
MikroElektronika
121
Breakpoints are divided into two groups: hardware and software breakpoints. The hardware breakpoints are placed
in the MCU and provide fastest debugging. Number of hardware breakpoints is limited to 8 (6 instruction, 2 data).
If all hardware brekpoints are used, then the next breakpoint will be software breakpoint. These breakpoints are
placed inside the mikroICD and simulate hardware breakpoints. Software breakpoints are much slower than hardware
breakpoints. These differences between hardware and software breakpoints are not visible in the mikroICD software
but their different timings are quite notable. That’s why it is important to know that there are two types of breakpoints.
The picture below demonstrates step-by-step execution of the code used in above mentioned examples.
Common Errors:
- Trying to program the MCU while the mikroICD is active.
- Trying to debug Release build version of the program with the mikroICD debugger.
- Trying to debug program code which has been changed, but has not been compiled and programmed into the MCU.
- Trying to select line that is empty for Run to cursor [F4] and Toggle Breakpoints [F5] functions.
- Trying to debug MCU with mikroICD while Watch Dog Timer is enabled.
- Trying to debug MCU with mikroICD while Power Up Timer is enabled.
- Trying to Step Into [F7] the mikroC PRO for PIC32 Library routines. Use Step Over [F8] command for these
routines.
- It is not possible to force Code Protect while trying to debug MCU with mikroICD.
- Trying to debug MCU with mikroICD with pull-up resistors set to ON on RB6 and RB7.
Related topics: mikroICD Debugger, mikroICD Debug Windows, mikroICD Debugger Options