RealView® Debugger Target Configuration Guide A.3. Generic groups and settings

A.3. Generic groups and settings

There are several board file entries that are common to many of the settings groups, shown in the example CONNECTION=RealView-ICE entry in Figure A.2.

Figure A.2. Viewing generic settings

These settings are found in CONNECTION groups. In some cases, some or all of these settings are also found in other groups, for example BOARD=AP in the AP.bcd entry. This section describes these generic groups and settings:

Connect_with

Specifies the vehicle making the connection. It includes the settings values:

Manufacturer

The name and the type of the connection.

Right-click to see a list of available connection types, but you also require an appropriate license and the hardware to use them.

IOdevice

This field contains additional information about the target hardware.

Not available in the current release of RealView Debugger.

Speed

You can set the emulation speed for some emulators.

Not available in the current release of RealView Debugger.

Remote

This specifies how remote connections are configured. It includes the settings values:

Hostname: The hostname, or IP address, of the remote workstation.
Port: Specifies that a non-default TCP/IP port is used to make the connection to the remote workstation.

Advanced_Information

Provides ETV target configuration information about the debug target.

This feature is described in detail in The Advanced_Information block.

Configuration

Specifies a named configuration file.

The default is to search for the .jtg file with the same name as this group (after the = sign). The name in this field does not have to be the same as the name of this group. If the file specified here is a full pathname, then only that location is used. Otherwise, it is searched for.

When working with RealView ICE targets, .jtg files are replaced by .rvc configuration files. When working with RDI targets, .jtg files are replaced by .cnf configuration files. When working with custom simulator connections, .jtg files are replaced by .auc configuration files.

Aux_Configuration

Not supported in this release.

Auto_connect

If set to True, this expands the list of devices on the debug target. The list of devices comes from the .jtg file specified by the BOARD or CHIP group. The list of devices is shown in the Connection Control window. You can then connect to the devices with a single click.

Pre_connect

Forces an order for device connection. When you connect to a device within the .jtg file, this ensures that one or more specific devices are connected first regardless of which device is selected for connection. This enables pre-setup of the specific devices to guarantee correct operation, such as initializations. You can specify the device(s) to connect to first by name, by processor name, or by processor type, as used in .cnf files that contain target configuration settings.

Description

Description of what board, processor, or emulator this is for.

Project

Opens one or more projects automatically when connecting to this board. If more than one device is in the scan chain and they are the same processor type, you must set the Specific_device field of the project to bind the project to the correct device(s). If the devices are different processor types, this is not necessary.

See RealView Debugger v1.8 Project Management User Guide for details on working with projects in RealView Debugger.

Disabled

Disables this entry so that it is grayed out in the Connection Control window.

Shared

Enables the sharing of target configurations for remote connections.

BoardChip_name

Refers to the BOARD, CHIP, or COMPONENT group this connection is derived from, using its name. If the group has more than one name separated by a slash, such as ID/name, any of them can be used. If not specified, the name of this group is used to match a board or chip.

Family_select

Ensures the correct family member is used (for example, for memory mapping, and registers) when the silicon ID is ambiguous. Some chip families do not use different silicon IDs for different members of the family, and this field enables you to specify which you are using. Specify the family member using one of these formats:

name=family_name: This enables you to specify the name of the device. Use either the name defined in the .jtg file or the processor name. This is used when multiple chips are housed on the same target but from different families.
family_name: Choose from the preconfigured list.
silicon_id: Can be expressed as num.num.num.num, for example 15.255.15.15, or as a value, for example 41029401.

For information about connection configuration, including the CONNECTION and DEVICE entries, see Custom connection reference.

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