5.5.2. Elements of the Connection Control window

The Connection Control window includes a Connect tab. In single processor debugging mode, this is the only tab.

The Connect tab includes a tree control, which comprises:

Target execution vehicle

The top-level group is the supported target execution vehicle. It corresponds to the physical connection, and identifies:

  • the manufacturer

  • the type of physical connection.

For example, for RealView ICE it is ARM-ARM-NW, which indicates that this vehicle is manufactured by ARM® Limited, and is connected across the network.

Access-provider connection

The second-level group shows the type of vehicle, or the debug target interface used to support the connection. For RealView ICE, this is the ARM JTAG debug tool for embedded systems.

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, a different icon is used to distinguish it from the default localhost connection.

Endpoint connections

The third-level entry shows the target processors that are available, for example, ARM7TDMI_0.

The endpoint connection is accompanied by a check box to show the current state of the connection. When connected, this check box is checked. When disconnected, the check box is blank.

Endpoint connections usually have a numerical suffix (for example, _0). If you are licensed to use multiprocessor debugging, each connection is numbered consecutively, starting at zero. This suffix ensures a unique identification for your connections in case you have two processors the same. For example, if your board contains two ARM7TDMI® processors and an ARM940T processor, then the connections might be named ARM7TDMI_0, ARM7TDMI_1, and ARM940T_2.

Note

If you are licensed to use RealView Debugger extensions, the Connection Control window includes additional tabs. For example, in multiprocessor debugging mode, the window includes a Connect tab and a Synch tab. See the chapter that describes connecting to targets in RealView Debugger v1.8 Target Configuration Guide for full details on how to use this window. Also, see the chapter that describes working with multiple target connections in RealView Debugger v1.8 Extensions User Guide.

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