The Connection Control window, shown in Figure 12.1, uses the connection entries in the board file to create a tree of possible connections. The entries in the board file reference device configuration files (such as .jtg and .rvc) that specifies the processors that can be reached using that connection, for example ARM940T_0.

To see these connection entries you must install other ARM products because RealView Debugger does not include any connection software of its own. However, the debugger does include connection interface components, or target vehicles, to provide the interface to each target. For example, as shown in Figure 12.1, the ARM-ARM-USB vehicle provides the interface to RVI-ME targets.

Figure 12.1 shows the Connection Control window generated by the board file entries shown in Figure 12.2. Each connection entry in the board file has a corresponding entry in the Connection Control window.

You can create your own target connection groups, for example CONNECTION=testconn3 shown in Figure 12.2. This new connection appears as an entry in the Connection Control window, that is testconn3, shown in Figure 12.1. You can create new groups based on existing connection groups or set these up using RealView Debugger defaults. You can also add any groups that are missing when you run RealView Debugger. See Chapter 14 Configuring Custom Connections for details on how to do this.