5.4.3. Configuring a new simulator connection

Simulator Broker connections to local host simulators are configured with custom settings by default. However, you might want to create new connections to simulate other peripherals and custom memory systems. For example, during the early stages of your development project, you might want to simulate an RTOS-enabled connection to reference a vendor-supplied board file. This enables accurate benchmarking of software targeted at ARM core-based processors although performance is slower than with real hardware.

This example creates a new local host connection using RVISS. It uses the default configuration file for ARM simulators, default.auc, created in your RealView Debugger home directory when you installed the base product. This simulates an ARM7TDMI core. It is recommended that you back up this file before starting the example, so that you can restore your original configuration later. If you want to create different simulator connections, for example to simulate an ARM940T core, make copies of this file using appropriate names.

For details on using RealView Connection Broker in remote mode, and how to create a connection to a remote host, see Chapter 6 Working with Remote Targets.

The example is split into the following sections:

Creating the configuration file

To create a configuration for the new connection:

  1. Locate the file default.auc in the directory that RealView Debugger is using for your session.

    See The home directory for more information about the location of your debugger home directory.

  2. Copy the file.

  3. Rename the copy, for example Tst_SIM_Broker_ARM940T.auc.

It is not necessary but it is recommended that you create a new .auc file when you create a new simulator connection.

Creating the new connection

To define the new connection:

  1. Select Target ? Connection Properties... to display the Connection Properties window.

  2. Right-click on the ...\rvdebug.brd entry, in the left pane, to display the context menu.

  3. Select Make New Group... from the context menu, to display the Group Type/Name selector dialog box, shown in Figure 5.13.

    Figure 5.13. Specifying a new CONNECTION group

    Specifying a new CONNECTION group
  4. Define the new group:

    • Leave the type of the new entry unchanged as CONNECTION.

    • In the Group Name data field change the name from new to something suitable for your target, using only alphanumeric characters, underscore _, and dash -, for example New_Test_SIM.

      This can be a descriptive name or the name of the .auc file that you are going to select, but without the .auc extension.

  5. Click OK to confirm your settings and to close the Group Type/Name selector dialog box.

    The new entry appears in the left pane of the Connection Properties window. It is automatically selected, and its details are displayed in the right pane. These details are the default for a new CONNECTION and you must change at least the Connect_with/Manufacturer, the Configuration filename and target Description. These changes are described in the following steps.

  6. In the right pane of the Connection Properties window, right-click on the Configuration entry and select Edit as Filename... from the context menu.

    The Enter New Filename dialog box is displayed to enable you to locate the required .auc file, for example default.auc or Tst_SIM_Broker_ARM940T.auc, the processor-specific file created in Creating the configuration file.

    If RealView Debugger cannot locate the specified file, you are offered the option to create the copy now or to define a new file for this connection.

  7. Click Save to confirm your entries and to close the Enter New Filename dialog box.

    The new pathname is displayed in the right pane.

  8. In the right pane of the Connection Properties window, right-click on the new *Configuration entry and select Edit Configuration-File Contents... from the context menu.

    Use the configuration dialog box, shown in Figure 5.12, to configure your new RVISS connection (see Configuring RealView ARMulator ISS for details).

    In this example, specify that the ARM940T core is simulated.

    Click OK to save your changes and close the configuration dialog box.

  9. In the right pane of the Connection Properties window, right-click on the Description field, and select Edit Value from the context menu.

    Type ARM940T + RVISS to new test hardware in the entry area and press Enter.

    This is the description displayed in the Connection Control window and Connection Properties window to identify the new target.

  10. In the right pane of the Connection Properties window, right-click on the Connect_with entry and select Explore from the context menu.

  11. In the right pane of the Connection Properties window, right-click on the Manufacturer entry and select the required connection type from the context menu, that is ARM-A-SW.

    If you do not specify this setting, the new connection appears in the Connection Control window but, when you try to connect, RealView Debugger prompts for the connection type.

  12. If you want to configure your target, for example by defining ARM configuration settings such as semihosting, make these changes now.

    Expand the following entries in turn:

    1. CONNECTION=New_Test_SIM

    2. Advanced_Information

    3. Default

    4. ARM_config

  13. Select File ? Save and Close to save your changes and close the Connection Properties window.

    Your new simulator is now displayed in the Connection Control window where you can connect in the usual way, shown in Figure 5.14.

    Figure 5.14. Connecting to a new simulator

    Connecting to a new simulator

Viewing details of the new connection

When you connect to the new simulator, the Output pane shows details about the connection to RVISS, shown in Figure 5.15.

Figure 5.15. Simulator details in the Output pane

Simulator details in the Output pane

Here you can see that the RVISS is simulating the ARM940T core specified in the new .auc file.

Connecting to the new simulator also creates a new entry in the Connection Control window under localhost Simulator Broker, shown in Figure 5.14. If you try to click on this entry to connect, this fails. The Output pane displays details of the error, for example:

Error: Failed on remote SIM/EMU/EVM. In use by my_user_name

This is because Simulator Broker views this as a remote connection. When you disconnect from the new connection, this entry also disappears.

Copyright © 2002-2005 ARM Limited. All rights reserved.ARM DUI 0182G
Non-Confidential