3.1.2. File menu

The File menu allows you to configure the Multi-ICE server and control the logging of TAPOp requests, and is shown in Figure 3.2.

Figure 3.2. The File menu

The File menu

The menu contains the following items:

Load Configuration

Displays a dialog box that you use to enter the name and path of a configuration file. This item is used for the manual configuration of Multi-ICE. This is described in The IRlength.arm configuration file.


Interrogates the device(s) connected to the JTAG scan chain and creates a configuration file containing what was found. See Table 3.1 for the actual frequencies used.

Table 3.1. TCK frequency for autoconfigure

Menu entryTCK frequency during autoconfigureTCK frequency in normal operation
Auto-Configure at 20kHz20kHz20kHz

[1] 1MHz for targets with more than one TAP, or for devices that are known to need a slower frequency unless adaptive clocking is used.

Autoconfiguration is described in Automatic device configuration. Unrecognized devices are marked as UNKNOWN, but you can add these to a lookup table, as described in The IRlength.arm configuration file.


If autoconfiguration of a known processor fails (showing UNKNOWN), reset the processor using a hardware reset button or a power-cycle and try the autoconfigure again.

Auto-Configure at 20kHz

This item does the same as the Auto-Configure item, but uses a TCK frequency that never exceeds 20kHz. See Table 3.1 for the actual frequencies used. This can be useful when the JTAG cable or the device is not capable of reliable operation at higher frequencies, or when the device might be in a sleep mode (when the slow system clock prevents the device responding sufficiently quickly to faster TCKs).

When manual configuration is used, the TCK frequencies indicated for Auto-Configure in Table 3.1 are used unless the configuration file specifies alternate timing parameters.

Reset Target

Resets the target hardware. Clicking the Reset Target button in the toolbar is equivalent to selecting this menu item.

You can control the action of Reset Target, so that it asserts nSRST, nTRST, or both signals. (nSRST and nTRST are explained in the Glossary.) You can do this either from the JTAG Settings dialog (see Figure 3.15) or from a Reset section in the configuration file (see Multi-ICE server device configuration files).

You can also reset the target hardware from the debugger, using the system_reset internal variable (see Debugger internal variables). This method asserts nSRST, but does not assert nTRST.


Turns remote procedure call logging on or off. When turned on, a tick is displayed next to the menu item and text describing the TAPOp protocol requests received by the server are written to a log file.

Use Set Log File to specify the filename that is used.

Set Log File...

Displays a dialog box that you use to enter the name and path of a log file.

Recent File

Displays a list of the eight most recent configuration files you have used.


Closes the Multi-ICE server.

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