TOOLSTICKUNIDC Silicon Laboratories Inc, TOOLSTICKUNIDC Datasheet - Page 12

• Manufacturer Part Number: TOOLSTICKUNIDC
• Description: CARD DAUGHTER UNIVRSTY TOOLSTICK
• Manufacturer: Silicon Laboratories Inc
• Series: ToolStickr

Specifications of TOOLSTICKUNIDC

• Accessory Type: Daughter Card
• Interface Type: USB
• Operating Supply Voltage: 2.7 V to 3.6 V
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant
• For Use With/related Products: *
• For Use With: 336-1345 - TOOLSTICK BASE ADAPTER336-1182 - ADAPTER USB DEBUG FOR C8051FXXX
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant
• Other names: 336-1434

To o l St i c k U n i D C
6.6. Setting and Running to Breakpoints
Silicon Laboratories microcontroller devices support up to four hardware breakpoints. A breakpoint is associated
with a specific line of code. When the processor reaches a hardware breakpoint, code execution stops, and the
IDE refreshes all debug and watch windows. The on-chip debug hardware allows for breakpoints to be placed on
any line of executable code, including code in Interrupt Service Routines. This section provides steps to set a
breakpoint on the line of source code that increments the Button_Press_Count variable.
1. If the device is running, stop execution using the “Stop” button or use the Debug → Stop menu option.
2. Scroll to the main function (line 69) and right-click on the Button_Press_Count variable. In the context menu
3. Click the Go button or select the Debug → Go menu option.
4. Press the button labeled P5.0. The IDE will show that the device is halted. A blue line will be placed in the editor
5. Start the processor a few more times, and press the button when the processor is executing. Notice that the
12
shown in Figure 14, select Insert/Remove Breakpoint. On the left side of the line in the editor window shown
in Figure 15, a red circle is added to indicate that a breakpoint has been placed on the source line.
window to indicate where the code execution has stopped.
IDE halts execution whenever the button is pressed. For every time the processor is started and the button is
pressed, the Button_Press_Count variable also increments by one.
Figure 15. Execution Stopped at Breakpoint
Figure 14. Inserting Breakpoint
Rev. 0.1