3.6.1. Setting up an Integrator board and core module

This example demonstrates how to use the Connection Properties window to create a specific Integrator/AP and core module target configuration. It shows how to use a predefined Board/Chip definition file, with extension .bcd, to set up your target.

After you set up your target, the example also demonstrates how you can connect to it using RealView ICE with the Connection Control window, and verify that RealView Debugger can connect to the target.

The example is split into the following sections, which must be executed in this sequence:

  1. Setting up the hardware and debug interface

  2. Configuring the new target

  3. Connecting to the new target

  4. Viewing the new target definition.

Setting up the hardware and debug interface

The first stage is to set up the hardware and configure the RealView ICE unit:

  1. Ensure that your Integrator/AP and core module are connected and switched on. This example uses the ARM940T processor, but you can use any core module supported by the Integrator/AP.

  2. Ensure that you have RealView ICE installed, and that the RealView ICE unit is connected and configured for use with RealView Debugger. If you have not configured the RealView ICE unit, do so now.

    Note

    • RealView ICE version 1.0.1 works with RealView Debugger with some limitations. The examples assume that you are using RealView ICE version 1.2. See the release notes accompanying the software for the latest details.

    • See RealView ICE User Guide for more details on configuring RealView ICE.

Using Multi-ICE

If you are using Multi-ICE to complete the examples, ensure that you have Multi-ICE installed, and that the Multi-ICE server is running on the workstation connected to the target. If you have not yet configured the target with Multi-ICE, do so now.

See Multi-ICE User Guide for more details on configuring Multi-ICE.

Configuring the new target

The next stage is to configure the new target:

  1. Start RealView Debugger without connecting to a target.

  2. Select Target ? Connect to Target... to display the Connection Control window.

  3. Right-click on the RealView-ICE entry and select Connection Properties... from the context menu to display the Connection Properties window.

  4. Right-click on the CONNECTION=RealView-ICE entry and select Make Copy... from the context menu.

    If the RealView-ICE target vehicle is not visible in the Connection Properties window, you must add it before continuing with this example. See the chapter that describes configuring a RealView ICE connection in RealView ICE User Guide for full details on how to do this.

  5. Use the Group Type/Name selector dialog box, shown in Figure 3.22, to name the new connection. For this example, enter MP3Player.

    Figure 3.22. Creating a new connection

    Creating a new connection
  6. Click OK. The new entry, CONNECTION=MP3Player, is added to the List of Entries in the Connection Properties window.

  7. Right-click on the Configuration setting for the new connection to display the context menu.

  8. Select Reset to Empty to delete the current value.

  9. Right-click on the Configuration setting again and select Edit Configuration-File Contents... the context menu. You are prompted to create a new configuration file either from an existing one, or from an empty one.

  10. From the prompt dialog, select Copy to copy an existing configuration file. The Select file to copy from dialog box is displayed.

  11. Set the Files of type field to All [*.*] , and locate the existing rvi.rvc in the directory install_directory\RVD\Core\...\etc\.

  12. Click Open. A Select Name of new file dialog box is displayed. The filename is automatically set to the connection name you specified in step 6. In this example, MP3Player.rvi.

  13. Locate your home directory, and click Save to save the file. The RVConfig dialog box is displayed.

  14. Click File ? Save to save the configuration file.

  15. Click File ? Exit to exit the RVConfig dialog box. The location of the MP3Player.rvi file is inserted into the Configuration setting.

  16. In the Connection Properties window, select File ? Save and Close to save your changes. The new target is added to the Connection Control window.

  17. Right-click on the new MP3Player connection and select Connection Properties... from the context menu. This displays the Connection Properties window showing the contents of the new connection, shown in Figure 3.23.

    Figure 3.23. Displaying the new MP3Player connection properties

    Displaying the new MP3Player connection properties
  18. Right-click on Description in the right pane to display the context menu. Select Edit Value and enter a short description for the new connection, for example Integrator/AP with ARM940 for MP3 product.

    Note

    Remember to press Enter to complete the entry.

  19. Select File ? Save and Close to save your changes. The new target description is added to the Connection Control window.

Linking board groups to the connection

The next stage is to link board groups to the new connection. This is not necessary but gives extended target visibility and enables you to view register contents and manipulate memory.

Note

The connection created in this example is used in other examples in the rest of this chapter. If you do not link the board groups, the contents of the Register pane differ from those shown here.

To link board groups:

  1. Right-click on the MP3Player entry and select Connection Properties... from the context menu to display the Connection Properties window.

  2. Right-click on BoardChip_name in the right pane to display the BoardChip context menu.

  3. Select AP from the context menu to select the Integrator/AP description. A new entry *BoardChip_name AP is added to the pane.

  4. Right-click on BoardChip_name (not on *BoardChip_name). The context menu is displayed again.

  5. Select <More...> to display the List Selection dialog box.

  6. Select CM940T from the list to select the ARM940T core module description, then click OK. The Connection Properties window now shows two BoardChip_name settings, shown in Figure 3.24.

    Figure 3.24. Board groups linked to the new connection

    Board groups linked to the new connection

    Target configuration settings were copied from the source connection. However, depending on the target hardware, you might have to configure other settings, for example to enable semihosting or to set stack size. See Configuring a memory map for details. If required, you can do this now for the new connection.

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

Connecting to the new target

The next stage is to connect to the new target board and core module:

  1. Select Target ? Connect to Target... to display the Connection Control window.

  2. Expand the new MP3Player entry.

    The relevant processor name entry is displayed, shown in Figure 3.25.

    Figure 3.25. Connecting to the new target

    Connecting to the new target
  3. Click the check box for the processor entry under the new MP3Player entry to connect to the target. RealView Debugger retrieves information specific to the target.

Viewing the new target definition

To view details about the new target hardware:

  1. In the Code window, select View ? Registers to display the Register pane. Two new tabs are included at the bottom of the pane, AP and CM940T.

  2. Click on the AP tab. RealView Debugger shows the abstraction of the hardware information specific to the Integrator/AP board, shown in Figure 3.26.

    Figure 3.26. AP tab in the Register pane

    AP tab in the Register pane

    This tab view enables you to modify your Integrator/AP board features, such as the memory mapped peripherals.

  3. To illustrate how RealView Debugger communicates directly with your Integrator/AP board, right-click on the text OFF directly beneath the L2 entry in the Register pane, and select ON from the context menu. The relevant LED display on your Integrator/AP board is turned on.

  4. Select the CM940T tab to see the abstraction of the hardware specific to the core module. The PRESENT status of the Motherboard indicates that the core module is connected to the Integrator/AP board.

    For more details on the Register pane, see the section on working with registers in the chapter that describes debug views in RealView Debugger v1.8 User Guide.

  5. In the Output pane at the bottom of the Code window, click on the Cmd tab. The display includes the line Advanced_info searched...BOARD=AP, BOARD=CM940T indicating that RealView Debugger is using the Integrator/AP and the CM940T board files.

    Note

    This information is only displayed when you first connect to the target after expanding the access-provider entry (MP3Player in this example).

    As a result, the memory map now contains the definitions required to use the Flash memory on the Integrator. See Flash programming for details.

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