3.7.1. Debugger configuration

The Debugger Configuration dialog consists of three tabbed screens:

These are described below. Select Configure Debugger from the Options menu to open the Debugger Configuration dialog.

Target environment

Follow these steps to configure the target environment:

  1. Click the Target tab of the Debugger Configuration dialog (Figure 3.15).

    Figure 3.15. Configuration of target environment

    Configuration of target environment
  2. Change the following configuration options, as required:

    Target Environment

    The target environment for the image being debugged.

    Add

    Display an Open dialog to add a new environment to the debugger configuration.

    Remove

    Remove a target environment.

    Configure

    Display a configuration dialog for the selected environment.

    Display a more detailed description of the selected environment.

  3. Save or discard your changes:

    • click OK to save any changes and exit

    • click Apply to save any changes

    • click Cancel to ignore all changes not applied and exit.

Note

Apply is disabled for the Target page because a successful RDI connection must be made first. When you click OK an attempt is made to make your selected RDI connection. If this does not succeed, the ARMulate setting is restored.

Debugger

Follow these steps to change the configuration used by the debugger:

  1. Click the Debugger tab of the Debugger Configuration dialog (Figure 3.16)

    Figure 3.16. Configuration of debugger

    Configuration of debugger
  2. Change the following configuration settings, as required:

    Profile Interval

    This is the time between pc sampling in microseconds. It is applicable to ARMulator and Angel only. Lower values have a higher performance overhead, and slow down execution. Higher values are not as accurate as lower values.

    Source Tab Length

    This specifies the number of space characters used for tabs when displaying source files.

    Endian

    Determines byte sex of the target.

    Little

    low addresses have the least significant bytes.

    Big

    high addresses have the least significant bytes.

    Disable

    Allows you to turn off the following display features:

    Splash screen

    When selected, stops display of the splash screen (the ARM Debugger startup box) when the debugger is first loaded.

    Remote Startup warning

    Turns on or off the warning that debugging is starting with Remote_A enabled. If the warning is turned off and debugging is started without the necessary hardware attached, there is a possibility that the ARM Debugger may hang. If the warning is enabled, you have the opportunity to start in ARMulate.

  3. Save or discard your changes:

    • click OK to save any changes and exit

    • click Apply to save any changes

    • click Cancel to ignore all changes not applied and exit.

Note

When you make changes to the Debugger configuration the current execution is ended and your program is reloaded.

Memory Maps

Follow these steps to configure Memory Maps:

  1. Click the Memory Maps tab of the Debugger Configuration dialog (Figure 3.17).

    Figure 3.17. Configuration of ARM Debugger memory maps

    Configuration of ARM Debugger memory maps
  2. Change the following configuration settings, as required:

    Memory Map

    This allows you to specify a memory map file, containing information about a simulated memory map that the ARMulator uses. It is applicable to ARMulator only. The file includes details of the databus widths and access times for each memory region in the simulated system. See Chapter 12 ARMulator for more information.

    You can select one of three Memory Map options:

    • do not use a memory map

    • use a global memory map, which means using the specified memory map for every image that is loaded during the current debug session

    • use a local memory map, which means using a memory map that is local to a project.

    The three Memory Map options are explained in greater detail as follows:

    No Map File

    Select this Memory Map option to use the ARMulator default memory map. This is a flat 4GB bank of ideal 32-bit memory, having no wait states.

    Global Map File

    Select this option to use the specified memory map file for every image loaded during the current debug session.

    A box allows you to enter a filename or to select a filename from a pull down list. Use this box to add new map files to the list, or select a map file from the list. When you have selected a map file, the debugger checks that the file exists and is of a valid format. Any file that fails these checks is removed from the list. The dialog remains, however, so you can correct an error or select another map file if necessary.

    Use the Remove button to remove the currently selected file from the list.

    The browse button

    allows you to select a memory map file using a dialog.

    Local Map File

    Select this option to use a memory map file that is local to a project.

    If a local memory map file is required when the debugger is initialized, the current working directory is searched. If a re-initialization occurs after the debugger has started and loaded an image, the directory containing the image is searched.

    A box allows you to enter a filename or to select a filename from a pull down list. Use this box to add new map files to the list or select a map file from the list. You must not specify an absolute path name, but you can specify a memory map file relative to the current image path.

    The browse button

    allows you to select a memory map file using a dialog.

    When you have selected a filename, or typed in a filename, the debugger does not check for the existence of the file or the validity of its format. If the format of the file is found to be invalid at re-initialization, the debugger displays an error message. In that case, or if the file does not exist, the debugger defaults to the No Map File option and uses the ARMulator default settings.

    Use the Remove button to remove the currently selected file from the list.

    Note

    Map files are used only at re-initialization, not when a program is loaded. When you select the Local Map File option, the map file in the working directory of the current image is used. If you load a new image, the same map file is used. To use a map file that is associated with the new image, you must re-initialize the debugger by selecting Configure Debugger… from the Options menu and clicking OK.

  3. Save or discard your changes:

    • click OK to save any changes and exit

    • click Apply to save any changes

    • click Cancel to ignore all changes not applied and exit.

Copyright © 1997, 1998 ARM Limited. All rights reserved.ARM DUI 0040D
Non-Confidential