7.1.1. Working with multiple targets and connections

RealView Debugger supports the debugging of multiprocessor applications in different ways, such as:

By default, the last connection you make to a target is the current connection. However, if you have connections to multiple targets you can change the current connection if required. RealView Debugger enables you to easily switch between connections without having to disconnect and reconnect the debugger.

When working with multiple connections, you might want to open multiple Code windows, and have the details for a different connection in each window. To do this, you must change the current connection and attach each Code window in turn to that connection. Only unattached Code windows show details of the current connection.

Target-specific connection settings

When you are working with multiple connections, you might want to use different connection settings for each target. For example, you might want to have semihosting enabled on one target, and disabled on all other targets.

Considerations when working with multiple connections

When working with multiple connections you can use a single Code window to view the connections, or set up multiple Code windows:

  • If none of the processors performs semihosting operations, you can use a single, unattached Code window. You can cycle through the connections to see the debug state of each processor.

  • You can use a single Code window if one processor performs semihosting operations. In this case, it is recommended that you attach the Code window to this processor. However, to view the state of any other processor, you might want to use at least one additional, unattached Code window. This enables you to cycle through the connections to see the debug state of each processor.

  • If semihosting operations are to be performed by more than one processor connection then, for these connections at least, it is recommended that you:

    • use a separate Code window

    • attach each Code window to a different connection.

    In this way, any application or debugger messages associated with the processor connections are displayed in the corresponding Code window.

See also

Copyright © 2002-2011 ARM. All rights reserved.ARM DUI 0153N
Non-ConfidentialID052111