2.1.1. Groups in the Connection Control window

Figure 2.2 shows the Connection Control window for the default board file, stored in \home\My_user_name\rvdebug.brd, in the root installation. In this example, some groups have been expanded and a connection has been made (see Expanding and collapsing groups for details). If you select a group, a box is drawn around it.

Figure 2.2. Groups in the Connection Control window

Groups in the Connection Control window

The Connection Control window is arranged in two columns or panes, Name and Description. Connection and target details are displayed in the left pane as a hierarchical tree with node controls, + and -. Connection and target details are displayed in the Name column as a hierarchy of entries:

Target vehicles

Top-level groups are supported target vehicles as specified by the target configuration settings, for example Server for targets that use the RealView® Connection Broker or ARM-ARM-NW for RealView ICE targets.

See Working with target vehicles for more details on working with top-level groups.

Access-provider connections

Second-level groups show the type of vehicle, or the debug target interface used to support the connection, for example RealView-ICE, the ARM® JTAG debug tool for embedded systems, or Remote_A, the Angel debug monitor. The ARM RDI second-level groups are also enabled in your board file when you install ARM ADI, RealMonitor, or Multi-ICE®.

Simulator Broker connections can be local or remote:

local

Connections to simulators that are installed on the local host machine. By default, these are accessed using the localhost connection.

remote

Connections to simulators that are installed on a remote host machine. Although you can modify the localhost connection to access simulators on a remote host, you might want to create a separate connection group, for example remotehost.

When you create another Simulator Broker connection group, a different icon is used to distinguish it from the default localhost connection.

See Working with access-providers for more details on working with second-level groups.

Endpoint connections

Third-level entries show the target processors that are made available by the access provider, for example the ARM940T core connected using RealView ICE.

Each endpoint connection is accompanied by a check box to show the current state of the connection. When connected, this check box is checked, shown in Figure 2.2. Where no connections have been made, the check boxes are unchecked.

RealView Debugger uses icons to help you identify the types of entries in the Name column.

Copyright © 2002-2005 ARM Limited. All rights reserved.ARM DUI 0182G
Non-Confidential