Top-level board files. Normally this is rvdebug.brd. This file includes the filenames of the other configuration files, for example .bcd and .jtg files.

You might change this file when you save settings in the Connection Properties window (see the examples in Creating new target descriptions).

Board/Chip definition files supplied by hardware manufacturers.

Files that contain configuration information for specific targets. By default, these files are used from the default settings directory, \etc.

If you change a supplied file or you create your own, you are recommended to store them in your debugger home directory.

These files contain per-chip and per-board settings as named configurations.

You might change this file when you save settings in the Connection Properties window (see the examples in Creating new target descriptions).

Configuration files for ARM RDI target connections, for example Multi-ICE. You change one of these files when you modify the configuration of an RDI connection using the RDI configuration dialog box.

These files are referenced by the .rbe files.

These files are used if you install new products such as RealView ICE. For example, the first time RealView Debugger runs after you install RealView ICE, the information contained in these files is copied into the board file. After this happens, the .prc file is ignored.

This file references the configuration file for ARM RDI targets. This file is where the *.cnf file is named, and it also extends the RDI settings with chip and board specific configuration settings. You might change this file when you save settings in the Connection Properties window.

Configuration files for RV-msg connections. You change the contents of one of these files when you modify the configuration of an RV-msg connection using the RVConfig dialog box (see the example in Configuring a RealView ICE interface unit).