3.7.6. Connecting to a SoC Designer target

To connect to a model created with SoC Designer:

  1. Open the required model in Carbon SoC Designer Simulator.

  2. Start RealView Debugger.

  3. In RealView Debugger, select Target → Connect to Target... from the Code window main menu to open the Connect to Target window. Figure 3.10 shows an example.

  4. Select Configuration from the Grouped By drop-down list.

  5. Expand the SoC Designer Debug Interface.

  6. Expand the required SoC Designer Debug Configuration.

    SoC Designer connections are named model.target[n] where:


    Is the name of the SoC Designer model.


    Identifies the target processor being modeled.


    A unique number for the connection, starting at zero.

  7. Double-click on the target to connect. Figure 3.14 shows example targets for an ARM processor model:

    Figure 3.14. SoC Designer model connection in the Connect to Target window

    SoC Designer model connection in the Connect to Target window

Considerations when debugging SoC Designer models

Be aware of the following when debugging SoC Designer models in RealView Debugger:

  • If Carbon SoC Designer Simulator prompts you to load application files when you open a model, then after connecting to the model in RealView Debugger you must load the symbols for the corresponding image (.axf) files that are loaded.

  • When you connect to a SoC Designer target, a new Carbon SoC Designer Simulator session is started if:

    • Carbon SoC Designer Simulator is not currently running

    • you started a Carbon SoC Designer Simulator session after starting RealView Debugger.

  • Any messages and prompts output by an application running on a SoC Designer model are not displayed in the RealView Debugger Output view. Instead, a message is displayed or a prompt dialog box is opened by the Carbon SoC Designer Simulator application. You might have to change focus to Carbon SoC Designer Simulator to see the dialog box.

  • If you exit RealView Debugger with the connection to the SoC Designer model still established, then the next time you launch RealView Debugger the connection is re-established if:

    • the same type of model is being debugged (for example, ARM)

    • the connection number matches a previous connection.

    This occurs even if you are debugging a different processor model to that previously used.

    For example, you might have debugged an application on an ARM926E-S™ processor in a previous RealView Debugger session, which used a connection called mp3_model.arm926e-s[0]. When you exit RealView Debugger with this connection established, the connection is stored in the RealView Debugger workspace. If you subsequently load a model for an ARM966E-S™ processor, and then launch RealView Debugger, the mp3_model.arm966e-s[0] connection is automatically established for the new processor model.

See also

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