winIDEA HelpStart a Debug Session
In this topic:
•Perform Debug | Reset or Debug | Download.
Introduction
In this tutorial, you will explore the most common use cases of starting a debug session, executing a reset, downloading code to your Target, and controlling its execution using Run Control commands to step through the code.
You will also look at how the winIDEA Debug Status in the lower right corner indicates the state of the debug session and the current state of the microcontroller.
Simplified diagram of a Debug Session
Configuration steps
To establish an active debug session, you can:
•Perform reset via Debug | Reset or click the Reset button 
in the Debug Toolbar, and establish control of the device at its reset point. Within an active session, this will only reset the device.
•Download the executable code and the belonging debug information to the microcontroller via Debug | Download or click the Download button 
in the Debug Toolbar and establish control of the device at its reset point and programs Flash and RAM.
winIDEA will show STOP Debug Status.
You can observe debug session initialization details in the Progress window.
After programming, set the device to Run via Debug | Run Control | Run or click the Run button 
in the Debug Toolbar. Run starts or resumes the execution of the application which continuous until the application is:
•Stopped
•Breakpoint is hit
•Other exception / event occurs
winIDEA shows RUN Debug Status.
Follow the Video Tutorial Breakpoint bisecting and see how stepping through the code is used in a real-life example.
See table of Run Control commands.
You can end the Debug Session via Debug | End Session.
winIDEA is now disconnected from the BlueBox. winIDEA will show OFFLINE Debug Status in the bottom right corner.
Next steps
