18.1. Working with connection properties

Connection properties, contained in board file entries, define possible connections to debug target systems. A debug target might be a simulator, an emulator, or an evaluation board installed on your host workstation.

There are descriptions of the general layout and controls of the RealView Debugger settings windows, including the Connection Properties window, in the RealView Debugger online help topic Changing Settings. This chapter assumes you are familiar with the procedures described in this help topic.

You can enable and disable each entry in the board file. Disabled entries are grayed out in the left pane, the List of Entries pane. Disabled entries can be edited in the same way as enabled entries and then enabled when available for connection. See Enabling or disabling a board file entry for details on how to do this.

Board file entries that are enabled form the basis of the information displayed in the Connection Control window, shown in Figure 18.1.

Figure 18.1. Connection properties entries in the Connection Control window

If you make changes to values in the Connection Properties window, an asterisk is added to each entry, in the left or the right pane, to show that the defaults have changed. You can restore the default settings and so cancel any changes. See Restoring board file entry defaults for details on how to do this.

Board file entries might have duplicate names because entries are uniquely identified through the combination of three elements:

For example, assume that you have a target board named MP3Player that you want to use with two different emulators. The board file entry name for each is MP3Player to reflect the target. However, the entries are differentiated by the type of connection (emulator type), and I/O device connection addresses.

When you display the Connection Properties window, the left pane shows the top-level entries specifying the supported vehicles, for example CONNECTION. You can create your own custom entries in this hierarchy using other types of entry, for example BOARD, CHIP, COMPONENT, or DEVICE.


If you are creating custom, lower-level entries, it is recommended that you avoid duplicate names.

For full information on the contents and values contained in different types of board file entries, both default and custom, see Appendix C Connection Properties Reference.

Copyright © 2003, 2004 ARM Limited. All rights reserved.ARM DUI 0234B