RealView Debugger Target Configuration GuideVersion 4.1
Home > Customizing a Debug Configuration > Configuring a connection sequence for multiple targets > Specifying a target-specific connection sequence

3.11.2. Specifying a target-specific connection sequence

If a target depends on one or more targets being connected first, then you can use the Pre_connect setting in a target-specific Advanced_Information group.

To configure a target-specific connection sequence:

  1. Select Target → Connect to Target... from the Code window main menu to open the Connect to Target window.

  2. Locate the required Debug Configuration:

    1. Select Configuration from the Grouped By list.

    2. Expand the Debug Interface containing the Debug Configuration of interest. For this example, expand RealView ICE.

    3. Make sure that all targets are disconnected on the Debug Configuration.

  3. Right-click on the required Debug Configuration to display the context menu. For example, right-click on RealView-ICE.

  4. Select Properties... from the context menu to open the Connection Properties dialog box.

  5. Click the Advanced button to open the Connection Properties window.

    The settings group for the Debug Configuration entry is selected, and the contents are displayed in the right pane.

  6. Create a target-specific Advanced_Information block for the target. For example, create a block called ARM940T.

  7. Click the group name you have created. For example, click ARM940T.

  8. For each target that this target depends on, do the following:

    1. In the right pane, right-click on the black Pre_connect setting to display the context menu.

    2. Select Edit Value... from the context menu.

    3. Enter the name of the target. A new Pre_connect setting is added for the target, colored blue.

      Note

      The target name must be the full name that appears in Connect to Target window for the Debug Configuration, for example, ARM940T_1.

    4. Repeat these steps for each target to be added.

    Note

    You must add the targets in the reverse order that they are to connect. However, you can change the order if required.

  9. Select File → Save and Close from the menu to save your changes and close the Connection Properties window.

  10. Click the OK button to close the Connection Properties dialog box.

Example using target-specific Advanced_Information blocks with multiple processors

Your development platform might contain the processors ARM920T, ARM940T, and ARM966EJ-S. These might be shown as ARM920T_0, ARM940T_1, and ARM966EJ-S_2 in the Connect to Target window. You can create an Advanced_Information block for each target, called ARM920, ARM940, and ARM966. To make sure that the targets are connected in the order ARM966EJ-S, ARM920T, and ARM940T, then set up the Advanced_Information block for each target as shown in Table 3.6.

Table 3.6. Pre_connect settings in Advanced_Information block

Advanced_Information blockPre_connect setting
ARM920ARM966EJ-S_2
ARM940ARM966EJ-S_2 ARM920T_0
ARM966Empty, because this target does not rely on another target being connected.

Connection sequence that occurs for each target

How RealView Debugger connects to the targets depends on the target you attempt to connect to first. Table 3.7 summarizes the connect sequence for this example.

Table 3.7. Connection sequence using target-specific Pre_connect setting

Target you connect to firstTarget connect sequence
ARM920TARM966EJ-S ARM920T
ARM940TARM966EJ-S ARM920T ARM940T
ARM966EJ-SARM966EJ-S
Connect all operationARM966EJ-S ARM920T ARM940T

Example using target-specific Advanced_Information blocks for a CoreSight system

Your CoreSight system might contain the following:

  • a Cortex-A8 processor

  • a CoreSight Trace Port Interface Unit (TPIU)

  • a CoreSight ETM

  • a CoreSight Trace Funnel

  • two CoreSight Cross Trigger Interfaces (CTIs).

These might be shown as Cortex-A8_0, CSTPIU_0, CSETM_0, CSTFunnel_0, CSCTI_0, and CSCTI_1 in the Connect to Target window. You can create an Advanced_Information block for the processor, called Cortex-A8. To make sure that the CoreSight devices are connected before the Cortex-A8 processor, then set up the Advanced_Information block for each target as shown in Table 3.8.

Table 3.8. Pre_connect settings in Advanced_Information block

Advanced_Information block namePre_connect setting
Cortex-A8CSTPIU_0 CSTFunnel_0 CSCTI_0 CSCTI_1 CSETM_0

This ensures that the connection to the Cortex-A8 processor is the last connection that is established, and is therefore the current connection.

See also

Copyright © 2002-2011 ARM. All rights reserved.ARM DUI 0182N
Non-ConfidentialID052111
PDF file icon  PDF version
Home > Customizing a Debug Configuration > Configuring a connection sequence for multiple targets > Specifying a target-specific connection sequence