3.17. Preparing Debug Configurations for distribution

You must prepare the RealView Debugger Debug Configurations that you want to distribute to other members of a development team.

If you intend to create Debug Configurations for use by multiple users, you are recommended to follow these steps:

  1. Create a home directory that you want to use to hold the Debug Configuration files to be distributed, for example, C:\RVD_home\DevTeam.


    The home directory can be on a remote machine that you access through a mapped drive, for example, H:\RVD_home\DevTeam.

  2. Start RealView Debugger using the following command (replace ... with the version and build number of your installation):

    "C:\Program Files\ARM\RVD\Core\...\win_32-pentium\bin\rvdebug.exe"
    --install="C:\Program Files\ARM\RVD\Core\...\win_32-pentium"

    RealView Debugger copies the default configuration files into the home directory. Table 3.10 lists the default configuration files.

    Table 3.10. Default configuration files in the home directory

    armreg.sigRequired by the ARM simulators (ISSM, RVISS, and SoC Designer). Do not edit this file.
    default.aucDefault configuration file for RVISS targets.
    ISSM_0.smcTarget configuration file for ISSM Cortex-A8 target.
    rvdebug.awsThe RealView Debugger user-specific workspace file.

    The RealView Debugger user-specific board file containing the Debug Configurations. This contains Debug Configurations for the following targets:

    • ISSM Cortex-A8


    • RVISS ARM926EJ-S

    • RVISS ARM1176JZF-S.

    rvdebug.iniThe RealView Debugger initialization file.
    RVISS_0.aucTarget configuration file for the RVISS ARM7TDMI target.
    RVISS_1.aucTarget configuration file for the RVISS ARM926EJ-S target.
    RVISS_2.aucTarget configuration file for the RVISS ARM1176JZF-S target.

  3. Create your own Debug Configurations.


    All users have the default configuration files listed in Table 3.10. It is recommended that you do not customize these default Debug Configurations, but rather create new ones.

  4. If the default memory map BCD files supplied with RealView Development Suite (RVDS) do not meet your requirements, then create your own custom memory maps.

    If you have to create your own custom memory maps for your development platforms, then:

    1. Store the BCD files containing the memory map definitions in the home directory.

    2. Assign the BCD files to the appropriate Debug Configurations.

  5. If you want users to keep their own rvdebug.brd file, then change the name of the rvdebug.brd file. For example, change the name to devteam.brd. Each user can then switch between their own board file and the common board file.

    If you want all users to use the same rvdebug.brd file, then you do not have to change the file name.

  6. Exit RealView Debugger.

    When you exit RealView Debugger, the following files might be created:

    • exphist.sav

    • rvdebug.sav

    • settings.sav.

    Remove these files if they exist. Also remove any *.bak files.

  7. Remove any additional files that you do not want to distribute. These include the following user-specific files:

    • armreg.sig

    • rvdebug.aws

    • rvdebug.ini.


    Be aware that these files are recreated when you next start RealView Debugger using this home directory. Also, if you have renamed the rvdebug.brd file, then a new default rvdebug.brd file is created.

See also:

Copyright © 2002-2011 ARM. All rights reserved.ARM DUI 0182N