16.2.2. Configuration entries

Target configuration entries enable you to describe the target architecture to RealView Debugger. This makes it possible for the debugger to present peripheral registers in a more human-readable format, and enables operations involving target memory to take account of the target memory map, for example so that flash memory can be treated as flash memory.

Target configuration is possible using the Advanced_Information group that is found in almost all the main groups. For example, there is an Advanced_Information group in the CONNECTION=RVI-ME entry of the ARM-ARM-USB group, and there is also one in the BOARD=MCUeval entry of the (*.bcd) Board/Chip Definitions group.

However, to minimize the potential for mistakes, it is suggested that you only modify the Advanced_Information settings of the following group types:

These groups names can be used to define a hierarchy, starting from the general board-level and becoming more specific, through whole chips to component modules on a chip. However, RealView Debugger does not distinguish, functionally, between the different group names and you can use them as you require.

Within the top-level board file, rvdebug.brd, you can have as many BOARD, CHIP, or COMPONENT entries as you require. However, there is a better way to store them. When RealView Debugger starts up, it searches for files with the extension bcd and loads them into a group called *.bcd Board/Chip Definitions. Configuration entries in files loaded into this group can be referenced from any other connection, which makes the target description independent of the connection used to access it, and makes it easier to use target descriptions in multiple instances of the debugger.

Note

In the board file, both target connection groups, for example CONNECTION=RVI-ME, and target configuration groups, for example BOARD=MCUeval, have an Advanced_Information group. Although you can use the Advanced_Information group of the target connection, it is suggested that you use target configuration groups and then reference these from the connection entry you are using.

The search procedure, the way files are referenced, and the configuration options are described in more detail in Chapter 17 Configuring Custom Targets.

Copyright © 2003, 2004 ARM Limited. All rights reserved.ARM DUI 0234B
Non-Confidential