| |||
| Home > Target Connection > About target connection > The Connect to Target window | |||
The Connect to Target window in RealView Debugger lists the Debug Interfaces that are currently installed on your workstation. An example Connect to Target window is shown in Figure 3.1:
You can use the Connect to Target window to perform all tasks related to target connection.
RealView Debugger remembers the last 10 target connections that you made. These connections are listed in the Home Page tab of the Code window, and in the Recent Connections menu that is available from the Target menu.
The following Debug Interfaces are available:
The following software Debug Interfaces are available:
The DSTREAM Debug Interface is
available if installed, which enables you to debug hardware through
a DSTREAM unit.
The RealView ICE Debug Interface
is available if installed, which enables you to debug hardware through
a RealView ICE unit.
This document assumes that you have installed the DSTREAM and RealView ICE host software, and updated the firmware as required. However, you must purchase the DSTREAM unit or RealView ICE unit separately.
The following software Debug Interfaces are available:
Instruction Set System Model (ISSM),
to connect to simulated Cortex™ processors.
ISSM is always installed with RealView Debugger.
Model Library, to connect to
a Cycle Accurate Debug Interface (CADI) model
defined in a model library file.
Model Process, to connect to
a CADI model that is currently running, such as an Exported Virtual
System.
Real-Time System Model (RTSM),
to connect to models of real-time systems.
Be aware that Emulation Baseboard (EB) RTSMs are not intended to be software implementations of particular revisions of EB hardware.
RealView ARMulator ISS, to connect
to RealView ARMulator® ISS (RVISS) simulated
processors. RVISS is always installed with RealView Debugger.
SoC Designer, to connect to Carbon
SoC Designer Plus models. You must purchase the Carbon SoC Designer
Plus application separately.
Each Debug Interface contains one or more Debug Configurations. A Debug Configuration identifies the targets that are available on the associated development platform. You can display the targets using the following groupings:
All the targets are shown as a single list in each Debug Interface. The targets are listed in the order of the associated Configuration name, shown in Figure 3.2:
The targets are listed under the name of the associated Debug Configuration, shown in Figure 3.3:
You can have multiple Debug Configurations for the same development platform. If you have multiple debugging platforms, then you must create a separate Debug Configuration for each platform. A Debug Configuration enables you to set up a custom debugging environment
The Connect to Target window also contains additional features that enable you to:
configure a selected Debug Interface
connect and disconnect all targets for a selected Debug Configuration
connect and disconnect using different modes.
Connecting to all targets for a specific Debug Configuration
Disconnecting from all targets for a specific Debug Configuration
the following in the RealView Debugger Target Configuration Guide: