Keil Logo

Debug Driver Configuration

To configure the driver:

  1. Options for Target ButtonOpen the dialog Options for Target - Debug:

    Set Use: and select Models Cortex-M Debugger.

    Select Target Driver

  2. Click Settings to open the dialog Models Cortex-M Target Driver Setup.

    Target Driver Screen

    The target driver configuration screen consists of two parts:

    • Use: Launch Simulation - the µVision Debugger starts and finishes a simulation model.
    • Use: Running Simulation - the µVision Debugger connects to an already running simulation model.

Configure Launch Simulation

Launch Simulation mode starts and finishes a simulation model whenever a µVision debugging session is started or finished.

Target Driver Setup

The fields Command, Arguments, Coverage File and Configuration File support absolute and relative path values. µVision Key Sequences and Environment Variables can be used to define more universal configurations not dependent on user-specific paths.

  1. Enable Use: Launch Simulation.
  2. In Command enter the simulation model executable file. Usually an *.exe or *.bat file. MDK-Professional users will find all supported Fixed Virtual Platform models under µVision_installation_path\ARM\FVP. Key sequence $K is helpful to avoid use of absolute path to µVision_installation_path. For example for the Cortex-M4 FVP this could be: "$KARM\FVP\MPS2_Cortex-M\FVP_MPS2_Cortex-M4_MDK.exe"
  3. In Arguments specify the values that µVision will pass to the model executable file. The field is optional.
  4. In Timeout area:
    • In Connection specify the maximum time during which µVision tries to connect and start the simulation model. Default is 10 (Sec).
    • In Communication choose whether the debugger shall run other communication timeouts after debug connection is established. Disabling timeouts may be needed for customized Fast Models that perform some operations longer than internal debug timeouts. In such case if the target is not responsive the user would need to manually close the debug session using µVision controls. Default is On.
  5. For setting the Target, click the Browse button and select the simulation target. The list might contain more than one target. Only model targets that correspond to the CPU type of the project are displayed.

    Select Simulation Target

  6. In Coverage File specify a file name. Default location is the µVision project directory. If a file is specified, then the file is passed to the model executable to dump coverage information that is collected during simulation. The field is optional. Use µVision Key Sequences when generic naming is required. For example "$L@L.cov" will create a coverage file in the same folder and with the same name as the build output file but with extension .cov (could be something as ./Debug/Project.cov).
    • Enable Store Coverage on Disconnect to dump the coverage information in the specified file.
    • Enable Load Coverage at Connect reads the information from the specified coverage file into the µVision debugger when the next debug session is started. Then, coverage information is annotated in the source code and disassembly as explained in the µVision manual.
  7. In Configuration File specify a file name. Default location is the µVision project directory. If a file is specified, then the file is passed to the model executable file using the argument -f config_file. The field is optional. Use µVision Key Sequences or Environment Variables when user-independent path is required for example for central location of a custom Model configurations or a DFP.
    • Click Generate to create a default configuration file. The simulation model is launched with the argument --list-params -o -config_file for generating the file.
    • Click Edit to open the file.

Note

Configure Running Simulation

Allows connecting to an already running Fast Models simulation model.

Select Run Simulation

Where

Target The unique target name within a simulation model. One model can have multiple targets.
CPU CPU core type. Only model targets that correspond to the CPU type of the project are displayed.
Simulation Name of the simulation model.
Sim ID Unique ID for the simulation process. Each simulation model has its own identifier.
Shut Down Simulation Close the simulation model when finishing the debugging session.
Update List Refresh the simulation model target list.

To select a running simulation model for debugging:

  1. Enable Use: Running Simulation.
  2. Enable a Target. One target can be selected at a time.
  3. Optionally enable Shut Down Simulation.

Searching a Remote Simulation Model

By default, models with a CADI server search only the local host. Setting the CADI_TARGET_MACHINE environment variable extends that search for running models to a designated host IP address (IPv4) and port. For example:

set CADI_TARGET_MACHINE=10.34.0.4:7002

When CADI_TARGET_MACHINE is set, running models with a CADI Server on the specified machine with the specified port will be searched for and listed in the Running Simulation dialog.

  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.