Datasheet
Emulator User’s Guide for MPLAB X IDE
DS52085A-page 50 2013 Microchip Technology Inc.
5.3 VIEWING PROCESSOR MEMORY AND FILES
MPLAB X IDE provides several windows for viewing debug and various processor
memory information, selectable from the Window menu. See MPLAB IDE online help
for more information on using these windows.
• Window>PIC Memory Views - View the different types of device memory.
Depending on the selected device, memory types include Program Memory
SRFs, Configuration Memory, etc.
• Window>Debugging - View debug information. Select from varibles, watches, call
stack, breakpoints, stopwatch, and trace.
Trace is discussed more thoroughly in upcoming chapters.
To view your source code, find the source code file you wish to view in the Project win-
dow and double click to open in a File window. Code in this window is color-coded
according to the processor and build tool selected. To change the style of color-coding,
select Tools>Options
, Fonts & Colors, Syntax tab.
For more on the Editor, see NetBeans Help, IDE Basics>Basic File Features.
5.4 BREAKPOINTS AND STOPWATCH
Use breakpoints to halt code execution at specified lines in your code. Use the
stopwatch with breakpoints to time code execution.
• Breakpoint Resources
• Hardware or Software Breakpoint Selection
• Breakpoint and Stopwatch Usage
5.4.1 Breakpoint Resources
For 16-bit devices, breakpoints, data captures, and runtime watches use the same
resources. So, the available number of breakpoints is actually the available number of
combined breakpoints/triggers.
For 32-bit devices, breakpoints use different resources than data captures and runtime
watches. So, the available number of breakpoints is independent of the available
number of triggers.
The number of hardware and software breakpoints available and/or used is displayed
in the Dashboard window (Window>
Dashboard). See the MPLAB IDE documentation
for more on this feature. Not all devices have software breakpoints.
For limitations on breakpoint operation, including the general number of hardware
breakpoints per device and hardware breakpoint skidding amounts, see “Limitations”
in the online help file.