1.1.5. Connect to Target window

The Connect to Target window enables you to:

Connection groupings

There are two connection groupings available in the Connect to Target window:

  • A Target grouping, which lists the individual targets available for each Debug Interface. The Target grouping corresponds to the Debug Interface that is used to access the debug target, for example RealView ICE. Figure 1.2 shows an example.

    Figure 1.2. Connect to Target window (Target grouping)

    Connect to Target window (Target grouping)

  • A Configuration grouping, which lists the targets for each Debug Configuration. Each Debug Configuration is listed under the related Debug Interface. RealView Debugger gives each Debug Configuration a default name, which you can change to a more meaningful name if required. Figure 1.3 shows an example.

    Figure 1.3. Connect to Target window (Configuration grouping)

    Connect to Target window (Configuration grouping)

Note

A RealView ARMulator® ISS (RVISS) Debug Configuration (RVISS in this example) can contain only a single processor. However, you can create multiple RVISS Debug Configurations, each with a different processor type.

Connections to trace components

If your development platform contains trace components, then you must add the trace components when you configure the Debug Interface targets.

If your development platform comprises a single processor with an Embedded Trace Macrocell (ETM™) and, optionally, an Embedded Trace Buffer (ETB™), then you do not have to connect to the trace components. For development platforms with more complex trace components, you must connect to and configure all trace components if you want to perform tracing. When the current connection is to a trace component, then for that connection:

  • the Code window supports only the Registers view, and Memory view where appropriate

  • all execution-related debugging operations are disabled.

See also

Copyright © 2002-2009 ARM Limited. All rights reserved.ARM DUI 0153K
Non-Confidential