Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
PSoC® 3, PSoC 4, and PSoC 5LP Breakpoints and Watchpoints - KBA84801
How many breakpoints and watchpoints are supported in PSoC® Creator™ for PSoC 3, PSoC 4, and PSoC 5LP?
The PSoC 3 device supports eight hardware program address breakpoints and one data address watch point.
PSoC 4 supports four hardware program address breakpoints and two data address watch points.
PSoC 5LP supports six hardware program address breakpoints and four data address watch points.
However, PSoC Creator reserves one breakpoint to use it to perform operations such as step, jump, and run-to-cursor. After all the hardware breakpoints are exhausted, PSoC Creator automatically uses software breakpoints for all future breakpoints, which is implemented on the host PC side.
A breakpoint is used to cause the debugger to halt the next time its location is reached. If you set a hardware breakpoint, a red dot appears in the left margin of the source/disassembly corresponding to the line in which the breakpoint is assigned. If the number of hardware breakpoints has been exhausted, and if you attempt to add another, the debugger displays an information message to announce that the maximum number of breakpoints has been reached. You will be prompted to place a software breakpoint instead. Software breakpoint is indicated by a green dot in the left margin of the source/disassembly corresponding to the line in which the breakpoint is assigned.
A watchpoint is used to set a breakpoint on a place in data memory as opposed to the standard breakpoint, which is used for program memory. Instead of setting the breakpoint on a line of code, you set it on a variable in the code. This watchpoint is hit each time the address that the variable is located at is read, written, or accessed based on your selection for Break on.