Datasheet

120 PSoC Designer IDE Guide, Document # 001-42655 Rev *B
Debugger
4. Fill in the applicable thread fields (i.e., Low Compare, Input Select, High Compare, Input Mask),
as well as state logic fields (i.e., Next State, Match Count).
As you make your selection in the Input Select drop-down, you see details in the grayed-out,
scrollable box below. Also, use Match Count to specify the number of times an event task occurs
before it performs the selected action.
The input mask for 8-bit threads is applied to the high and low range comparison values, as well
as to the input select value. This is done to support range comparisons on subsets of the bits in
the input select value. All comparisons take place within the bits specified by the input mask.
Other bits are ignored.
The range values are masked during event editing when the thread states are saved by the Apply
button or by switching to a thread state. For example, if the entered low compare value is 06 HEX
and the input mask value is 05 HEX, the low compare value after the mask is applied is 04 HEX.
The input select value is masked at run time.
5. When finished, click Apply. The individual event is now configured and its information appears at
row 0.
If you forget to apply your entries, you are prompted to save. Click Yes or No.
To clear all events in the dialog box, click Clear All. To disable all events in the dialog box, click
Disable All.
6. Click row 1 and repeat steps 3-5 to configure another event. Repeat this process for each addi-
tional event. (You can configure up to 65 events.)
7. Click Close to exit the dialog box. All entries are saved.
As you run events, you can view messages regarding the status in the Debug tab of the Output Sta-
tus window. For instance, if you check Break as part of an event, “Hit Event state break” appears in
the Output Status window as the debugger hits the event.
For complete training on debugging and Dynamic Event Points, try PSoC Designer Module 3:
Debugging with PSoC. Review and sign up under Training > On-Demand at
http://www.cypress.com/.
7.5.5.2 Typical Event Uses
The many potential uses for events include:
■ Find a stack overflow. See Stack Overflow Errors under Invalid Memory Reference in PSoC
Designer Online Help System at Help > Help Topics.
■ Detect jmp or call out of program. See Code that will Corrupt Stack under Invalid Memory Ref-
erence in PSoC Designer Online Help System at Help > Help Topics.
■ Trace a specific range of code.
■ Find when a register is written (with optional matching data value).
■ Drive an external signal on interrupt(s) using the ICE-4000.
■ Measure interrupt latency.
■ Break the ‘n’th time a line of code is executed (match count).
■ Break on Carry Flag status.
■ Break on signals from customer target board.
■ Wait for certain number of instructions.
■ Count sleep periods.
■ Break on specific data in Accumulator on certain instructions (PC).
■ Collect trace data reads or writes to specified register.
■ Find memory write.