Target connections

Information about possible connections is contained in the file rvdebug.brd, installed in the etc directory, and known as a board file. At installation, this file is copied to your RealView Debugger home directory as your personal copy. Any changes that you make are recorded in your copy. The original default rvdebug.brd resides, unchanged, in the etc directory of your RealView Debugger installation.

The configuration details are contained in .rbe and .cnf configuration files for RDI targets, in the default.auc file for RealView ARMulator ISS, and in rvi.rvc for RealView ICE. These files are created automatically in your RealView Debugger home directory the first time you connect to a target.

You can set up RealView Debugger to use a specific hardware configuration by using board and chip definition files (*.bcd). These files specify information such as memory layout, extra register definitions, and other settings that are specific to your hardware. A set of default files is supplied with RealView Debugger, in the etc directory of your RealView Debugger installation, and rvdebug.brd has pointers to them so that they are listed in the Connection Properties window.

$image\exclaim.gif$ If you want to make changes to the *.bcd files, you should make local copies in your RealView Debugger home directory so that you do not overwrite the installed files.

$image\openred.gif$ For more details on setting up and using the board and chip files, and defining your target system, see the RealView Debugger v1.8 Target Configuration Guide.

You can view the contents of your rvdebug.brd, and make any required changes, in the Connection Properties window.

You connect to a target through the Connection Control window, displayed when you open RealView Debugger.