RealView Debugger uses a board file to access information about the debugging environment and the debug target available to you. You can use RealView Debugger with the default board file that is installed for you, and is called rvdebug.brd. This is copied into your home directory, from the default settings directory program_directory\etc, when you first use RealView Debugger after installation. This means that if you damage your personal board file, you only have to delete it from your home directory and a new copy of the original default board file is placed there.

The board file defines the debug target configuration settings for the current session. For the target, it describes the type of target, the emulator being used, and any custom connection information.

RealView Debugger must have a board file to make connections. If you work with a variety of targets and connections, you might set up, and save, several board files so that you can easily switch RealView Debugger from one to another. You can use the default board file as a basis for any number of further copies, each edited for a particular purpose.

You can use a text editor to display or print the contents of a board file, and all associated configuration files, but it is recommended that you never edit these files with a text editor or word processor. Use only the Connection Properties window to make changes to a board file, or to create a new one.

The configuration file .rvc is used for built-in emulators such as RVI-ME direct connect. This file defines the JTAG (Joint Test Action Group) boundary scan architecture for your target and so describe the number and types of hardware devices in the scan chain that are available for connection.

Whenever RealView Debugger reads a .brd file, it also searches for any of these related files and reads them. In this way, the information held in the JTAG files becomes part of the configuration settings for this session.

See the RealView ICE Micro Edition v1.1 User Guide for more details on using the RVConfig dialog box to make changes to the configuration file.

Board/Chip definition files contain ETV information about a particular board or chip as supplied by the manufacturer, including peripheral registers and memory regions. The files are usually stored in one location so that they can be referred to from as many places as necessary, but only a single copy requires maintenance.

Each board or chip is defined using a file named processor_name.bcd. By default, .bcd files are stored in program_directory\etc, but you can specify a different location in your board file.

In general, you do not have to edit these files but you can specify their location so that they are included in the configuration settings. However, where changes are required, use the Connection Properties window to make the necessary changes.