Debug configuration settings
Before running a debugger from Eclipse, create a debug launch configuration.
Name – Configuration name, which is shown in the list of configurations on the left.
Project – The project, to which the configuration belongs to.
C/C++ Application – The output file, which will be downloaded to the target.
Stop on start up at - Defines if the execution should stop after start up, and where it should stop.
Verify after download - Specifies whether to perform a verification of the file downloaded to the target system.
Analyze source files - When checked, source files will be analyzed after download.
Show winIDEA - You can hide/show winIDEA. You can also bring it to the top.
Close winIDEA after debug session termination - When checked winIDEA will be closed after debug session termination. You can also check if you want to save the winIDEA workspace at shutdown.
Verbose log output - If checked, a detailed log of debugger execution is stored into a log file. Since it takes some space and time, usually leave this unchecked. In case of problems, you can check this option and send the log file to the support team.
Workspace file - Path to the workspace file that will be opened by winIDEA. Its extension must be either 'xjrf' or ‘xqrf’. Path can be absolute or relative, if relative then is relative to the selected project. You can choose an existing winIDEA workspace (recommended). If a workspace file does not exist, a new one will be automatically created. In this case, the Workspace creation section must be filled in with all the information.
Device - Select the used MCU.
Hardware - Choose which BlueBox are you using (or other hardware).
Communication - Select the communication type with the selected hardware (options: USB, Ethernet).
Use Image Checker - You can select the use of image checker, which analyzes the download file(s) at download to prevent misconfiguration of MCU, which could result in incorrect boot or bricked MCU.
Create SMP Configuration - If checked winIDEA will create SMP configuration on all cores (excluding Security cores).
To show this dialog, winIDEA must be started. This will start the winIDEA specified in the Preferences and use the workspace, which path has been set in the iSYSTEM Debugger / Workspace file. If you have specified for winIDEA to stay hidden, then it will start in the background and never be shown.