17.3.4. Linking a board, chip, or component to a connection

The configuration group you create in a *.bcd file is only used if you reference it from a connection. There are several cases to consider, presented here in order of increasing complexity:

Linking one board group to one processor connection

This configuration is shown as in the form of a tree in Figure 17.7.

Figure 17.7. Linking one connection to one board

To link to this you must first ensure that the *.bcd file contains the required BOARD, CHIP, or COMPONENT groups. Then:

  1. Click on the CONNECTION=RVI-ME entry. The right pane displays a set of properties including BoardChip_name.

  2. Left-click on the BoardChip_name. It becomes highlighted.

  3. Left-click on the BoardChip_name again. This displays a context menu including a list of available .bcd files, shown in Figure 17.8.

    Figure 17.8. Linking a board

    Linking a board

    Note

    The two clicks in steps 3 and 4 must be distinct. A double-click does not work.

  4. Select the name of the board group, for example the CHIP called ARM7TDMI that was created in Creating and naming a board, chip, or component.

  5. Select File → Save and Close.

  6. Restart the debugger. When you connect using RealView ICE Micro Edition, the configuration defined in your board group is applied to the connection.

Linking several board groups to one processor connection

You might want to link several groups to a single processor if the groups represent different, possibly optional, parts of the same target. This kind of layout is shown in tree form in Figure 17.9.

Figure 17.9. Linking one connection to two boards

When you reference multiple boards, RealView Debugger merges the settings from each group in a breadth-first search of the group tree. Therefore the complete configuration is the combined configurations of all of the groups. If the same setting is specified in more than one group, the specification in the group that is listed first in the CONNECTION is used, for example BoardChip_name=MCUeval in Figure 17.9.

To do this you must first ensure that the *.bcd files exist and then reference them from your board file using the required BOARD, CHIP, or COMPONENT groups:

  1. Click on the CONNECTION=RVI-ME entry, so that it is highlighted. The right pane displays a set of properties including BoardChip_name.

  2. Left-click on the BoardChip_name to highlight it.

  3. Left-click on the BoardChip_name once more. A context menu is displayed, shown in Figure 17.8.

    Note

    The two clicks in steps 3 and 4 must be distinct. A double-click does not work.

  4. Select the name of the board group. A new entry is displayed in the right pane with an asterisk * beside it. For example, *BoardChip_name MCUeval.

  5. Right-click on the BoardChip_name that does not have an asterisk to see the context menu, shown in Figure 17.10.

    Figure 17.10. Linking a second board

    Linking a second board
  6. Select the name of the board group. A new entry is added to the right pane with an asterisk * that indicates this value is not a default, for example, *BoardChip_name ARM7TDMI.

  7. Select File → Save and Close.

  8. Restart the debugger. When you connect to RealView ICE Micro Edition, the configuration defined in your board group is applied to the connection.

You can repeat steps 6, 7, and 8 until all of the groups you require are included.

Changing the order of board groups

This procedure describes adding board MCUeval before board ARM7TDMI, so that the structure shown in Figure 17.9 is recreated. New boards are always added at the top of the list and this gives their settings priority over the settings in boards lower down the list.

If you want to reorder the boards in the BoardChip_name list to give the settings a different priority, select the context menu as described above and click on Manage List..., shown in Figure 17.10. Use the Settings: List Manager dialog box to reorder the board groups.

Linking one or more board groups to another board group

You might want to link several groups together so that you can share descriptions or simplify each part of a description. For example, the description of your board provided in board_name.bcd (in this example, MCUeval.bcd) is split into a description of the board, MCUeval, and a description of the processor on the board, ARM7TDMI. This is shown in tree form in Figure 17.11.

Figure 17.11. Linking one board into another board

Groups can contain BoardChip_name references to other groups, so that you can build multi-layered descriptions.

Note

You are not required to split your board up into distinct CHIP descriptions. You can create one BOARD description containing all of the required information. However, splitting your board up into distinct CHIP descriptions can help you later on because it is then easier to share descriptions or reuse a description for another project.

Copyright © 2003, 2004 ARM Limited. All rights reserved.ARM DUI 0234B
Non-Confidential