Datasheet

PSoC Designer IDE Guide, Document # 001-42655 Rev *B 125
Debugger
cally. A hex file generated with Debug Mode enabled will not run on the PSoC device unless it is con-
nected to the Debugger. Before generating production code, disable debug mode.
Figure 7-12. Debug Mode Enabled
7.6.3 Downloading to the Device
Before you begin a debug session you need to download your project .hex file to the target device.
To download the .hex file to the device:
1. Click the Download to Emulator (Pod) icon .
The system downloads the project .hex file located in the …\output folder of your project direc-
tory. A progress indicator reports download status.
2. Once the download is complete, the pod can be directly connected to and debugged on your spe-
cific circuit board.
7.6.4 Debug Strategies for I
2
C Debugger
Debug strategies for the I
2
C debugger are similar to those shown in the current IDE guide, except
that Trace and Events are not available. Debugging using the I
2
C debugger supports fewer break
points than an external emulator does. The section “Watch Variables” on page 118 is not specific to
the I
2
C debugger, but is a new feature that is not yet documented in the PSoC Designer IDE Guide.
7.6.5 Break Points
The Break Point feature allows you to stop program execution at predetermined address locations.
When a break point is encountered, the program stops at the address of the break point, without
executing the address code. Once halted, the program is restarted using the available menu or icon
options.
To set break points, first open the file to debug. Do this from the Workspace Explorer. (If your project
file Workspace Explorer is currently not showing, click View > Workspace Explorer.) Break points are
created by right clicking your mouse at targeted points and selecting Insert Break Point. You can
view and remove active break points in the Break Points window. To open the Break Points window,
select Debug > Windows > Break Points.