| Copyright © 2002-2007 ARM Limited. All rights reserved. | ARM DUI 0182I |
| Non-Confidential | |
 PDF version | |
| Home > Configuring Custom Memory Maps, Registers and Peripherals > Linking a board, chip, or component group to a Debug Configuration |
| |||
| Home > Configuring Custom Memory Maps, Registers and Peripherals > Linking a board, chip, or component group to a Debug Configuration | |||
The settings in a *.bcd file are only
used if:
The .bcd file
is referenced from a Debug Configuration.
An Advanced_Information block
name is one of the following:
The whole or part of the name of the target being connected.
For example, settings in blocks named either ARM9 or ARM940T are
used if you connect to an ARM940T processor. However, when multiple
block names have a common string (ARM9 in this
example), then the block with the longest match is always used, ARM940T in
this case.
Default
All.
Typically, groups named Default and All are
not used in a BCD file.
The identification string, id_match,
specified in the Advanced_Information group, matches
the hardware ID string returned by the target.
If more than one linked configuration group matches the target hardware, the group with the longest match is used.
This section describes how you make these links in the board file for a connection. These examples assume that you are linking configuration groups to a connection that uses RealView ICE.
If this is the first time you have used RealView ICE, make sure that you configure the debug interface before trying to connect.
The examples in this section use existing target descriptions. However, you can create and use your own target descriptions.
| Copyright © 2002-2007 ARM Limited. All rights reserved. | ARM DUI 0182I |
| Non-Confidential | |
| PDF version | |
| Home > Configuring Custom Memory Maps, Registers and Peripherals > Linking a board, chip, or component group to a Debug Configuration |