A.2.1. Syntax

A device configuration file is a text file with the file suffix.cfg. The syntax is similar to the Windows INI file format:

The contents of each section of the configuration file is as follows:


The title string.

Tap n

The name of the device (which must have an entry in IRlength.arm) as shown in Example A.2. If the software requires a device alias this must be placed on the next line in the same format. The syntax is:

Name DriverOptions, DriverVersion

The DriverOptions field is an optional text string passed to the driver for a specific device. There must be a space between the driver name and the driver options, but the driver options can contain spaces. The field is terminated by a comma or newline.

If there is at least one asterisk * in the option string, the Multi-ICE server does not display the status indicator [X] in the TAP window.

The DriverVersion field is an integer number. Specifying a value indicates that only drivers with this version number or higher are acceptable.

Example A.2. Configuration file TAP section

[TAP 0]
ARM7TDMI 				;Plain, no options
[TAP 1]
ARM7TDMI , 2				;Requires V2 or higher
[TAP 2]
ARM7TDMI *ABC				;Driver=ARM7TDMI, Options="ABC", no status


The section contains one or both of the words, as shown in Example A.3:


Resetting the system involves asserting nSRST.


Resetting the system involves asserting nTRST.

If no reset section is present then resetting the system using the Multi-ICE server GUI asserts both signals.

Example A.3. Configuration file Reset section



The timing section defines how the TCK signal is generated as shown in Example A.4. The following name value pairs are allowed in this section:


The period for which TCK is HIGH (positive voltage), specified as a value from TCK frequencies.


The period for which TCK is LOW (zero voltage), specified as a value from TCK frequencies.


YES if the target drives RTCK, NO if it is not driven.

The HIGH and LOW values correspond to those in the server Settings ? JTAG Settings dialog box.

Example A.4. Configuration file Timing section



The TAPINFO section (see Example A.5) tells the server whether to read additional information from the device after loading the configuration file. If the section contains YES then the server reads any additional information, otherwise it does not. You can view the information by double-clicking on a TAP controller within the server Configuration window.

Example A.5. Configuration file Tapinfo section


A TAPINFO option is included in a configuration file to provide flexibility for ASIC developers during testing. When the Auto-configure facility is used, TAPINFO is always provided. By default, when loading a configuration file TAPINFO is not provided.

Copyright © 1998-2002 ARM Limited. All rights reserved.ARM DUI 0048F