Keil Logo


The dialog Debug defines options that are applied when a debugging session is started.

Options for Target - Debug

The screen is split into options for the Simulator and for the target driver.

Use Simulator
Configures the µVision Debugger as a software-only product that simulates the instruction set of an Arm Cortex-M based microcontroller. Developers can test and debug embedded applications before the hardware is ready. Refer to Simulation for restrictions and a list of supported Arm Cortex-M cores.
Settings (button)
Configures device specific simulator options such as start-up features and BUS characteristics (only available for some devices).
Limit Speed to Real-Time
Synchronizes the CPU simulation to the PC clock, which is a real-world clock. It limits the speed of the CPU simulation to real-time considering the CPU frequency set in the field Options for Target - Target - Xtal(MHz). This setting is useful only for targets that simulate faster than real-time.
Use: Debug Driver
Selects a driver for debugging the target hardware. Several AGDI drivers are available that use different debug adapters to connect to the target hardware. For example, a ULINK USB-JTAG adapter driver that uses the embedded on-chip debugging hardware.
Settings (button)
Configures target driver options, such as tracing options. Can also manage target options using debug configuration files (dbgconf). For more information, refer to the user's guide of your debug adapter.

Common Options

The dialog consists of two almost identical configuration sections:

Load Application at Startup
Loads the object file specified in the field Options for Target - Output - Name of Executable into the µVision Debugger.
Run to main()
Executes the instructions until main() is reached and stops execution. When disabled, the application stops at the first instruction. Commands defined in Initialization File are executed regardless of this option.
Initialization File
Specifies a file that can contain Debug Commands, Debug Functions, debugger configuration settings, and device initialization commands. For example, Toolbox buttons can be defined. Click Edit to open the file.


  • To exit long running or hanging functions, position the cursor into the command-line of the Output window and press ESC.
Restore Debug Session Settings
Restores the settings defined in the previous debugging session for Breakpoints, Watch Windows and Performance Analyzer, Memory Window, Toolbox, and the System Viewer.
CPU/Driver DLL - Parameter
Preferably, do not modify these settings. Device Database Parameters describe the parameters.
Dialog DLL - Parameter
Preferably, do not modify these settings. Device Database Parameters describe the parameters.
Warn if outdated Executable is loaded
When enabled, µVision performs the following operations when entering debug mode or starting Flash download:
  • Save modified files in the editor and all project files (*.uvprojx, *.uvoptx, *.uvguix)
  • Check if any project option, or source/header files have changed since the last successful build.
When disabled, files are saved according the option settings under Edit – Configuration – Editor
Manage Component Viewer Description Files
Opens the dialog to Manage Component Viewer Description Files.

Sequence of Execution

µVision executes the commands in the following order:

  1. The debugger loads the file set in the field Project - Options Target - Output — Name of Executable when Load Application at Startup is enabled.
  2. Restores Debug Session Settings for enabled dialogs.
  3. Executes the commands in the Initialization File.
  4. Executes the instructions until reaching main() when Run to main() is enabled or the command g, main is found in the Initialization File.

Related Knowledgebase Articles

  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.