WICED User Manual
5. Run to a breakpoint: To run the application to the 'wiced_init' breakpoint configured in Step 1, click the yellow/
green pause/play button in the Debug tab. The Debug tab control buttons are highlighted in yellow in the
following screen capture.
6. View a breakpoint: When the debugger halts at a breakpoint, the WICED IDE does not automatically switch
to the current thread as the context for the debugger. It is necessary to manually check the current task in
the running thread is selected before analyzing debug information.
To find the breakpoint, click on the 'application_start()' function under Thread[2] in the Debug tab. The
'ping.c' source file opens and the wiced_init function is highlighted in green to show where the program
halted.
7. Step program execution: Step Into, Step Over and Step Return options are available in the WICED IDE Run
menu. Alternately, Step shortcut icons are provided in the Debug tab, and on Windows
pressing F5, F6 and F7, respectively.
8. Stop debugging: To stop debugging, click the square red stop button in the Debug tab.
Note: If the debugger fails to launch, it may be necessary to terminate an existing debug process. On
®
Windows
, press Ctrl-Alt-Delete to open the Windows
Search for, and terminate, all 'arm-none-eabi-gdb' processes.
Broadcom
®
November 19, 2015 • WICED-UM200-R
Debugging an App on the Demo Platform
®
Task Manager, then select the Processes tab.
®
Systems, by
Page 41
Need help?
Do you have a question about the WICED 4343W and is the answer not in the manual?