| |||
| Home > Introduction > About target connections and configuration > Comparing target connection and target configuration | |||
RealView Debugger makes a distinction between:
Describes how the debugger accesses your debug target.
Describes your debug target to the debugger, for example how memory is mapped.
Specifically, the board file enables you to specify high-level connection details such as:
debugger to target connection details, such as interface type and instance, TAP controller positions, and connection interface address
debugger actions taken when a connection is made, for example running commands and opening projects.
And low-level, target configuration details such as:
target processor characteristics, for example processor type and endianness
target peripheral register and memory configuration.
To do this, the default board file contains a series of elements arranged in a hierarchy. At the top level are connection entries or target vehicles that enable RealView Debugger to connect to different targets. As you drill down the connection, you can modify entries, or create new elements, that define the target configuration in more detail.
At the lowest level, RealView Debugger is able to access Extended
Target Visibility (ETV) information about your debug
target using a special group of settings, the Advanced_Information block
that is found in all the main groups.
RealView Debugger can also access Board/Chip definition files that contain ETV information about a particular board or chip as supplied by the manufacturer, including peripheral registers and memory regions.