What Now - Broadcom WICED Quick Start Manual

Quick Start Guide
WICED
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® Systems, by
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® Task Manager, then select the Processes tab.
Search for, and terminate, all 'arm-none-eabi-gdb' processes.

What Now?

Now you have a basic understanding of how to compile, download and debug a WICED application, we
recommend that you try to build and run each of the snippet and demo applications provided in the WICED SDK
Applications directory.
Each snippet application provides a relatively simple example demonstrating how to use a particular API or
feature of the WICED SDK. The more sophisticated demo applications combine multiple APIs and features to
demonstrate advanced functionality.
To help you use the WICED IDE, Appendix B contains some quick hints and tips that will save you time
navigating around the WICED code base. Read these now, then move onto trying WICED applications.
Broadcom
®
January 15, 2014 • MMPWICED-QSG203-R
Using the WICED IDE
Page 18