RealView Debugger Target Configuration Guide: 4.1.3. Board, chip, and component groups

4.1.3. Board, chip, and component groups

Configuring a board/chip definition requires that you create a BOARD, a CHIP, or a COMPONENT group. RealView Debugger uses these groups in the same way regardless of the type you create. However, it is recommended that you use them as follows so that it is clear what the group describes:

BOARD: Use this to define target boards as a whole, such as the memory map and peripheral components.
For example, the CP.bcd file in yor default settings directory describes the memory map, registers, and peripherals registers of the Integrator™/CP motherboard. It contains the BOARD=CP group, which defines the CP board/chip definition.
CHIP: Use this to define significant devices on your development board.
For example, the supplied BCD file for the Evaluator-7T development board (...\Eval7T.bcd) references the ARM processor-based KS32C50100 to define the processor and ASIC components of that device. It contains the CHIP=KS32C50100 group, which defines the KS32C50100 board/chip definition.
It is recommended that you use a CHIP entry if you want to use a device on more than one board, or if the device is in itself complex.
COMPONENT: Other components that are not covered by a BOARD or CHIP group.

When you start RealView Debugger, the name of each group is added to:

the related BoardChip_name context menu
the associated List Selection dialog box.

You use the Available Files list or context menu when assigning a board/chip definition to a Debug Configuration.

Note

You must only configure settings that relate to memory map or memory mapped registers in these groups. All other settings must be configured at the CONNECTION level.

Copyright © 2002-2009 ARM Limited. All rights reserved.	ARM DUI 0182K
Non-Confidential
PDF version

4.1.3. Board, chip, and component groups

Note

See also