3.2.2. Manual device configuration

You configure the Multi-ICE server manually by creating a server configuration file and loading it into the Multi-ICE server. A complete description of the structure and contents of the configuration file is provided in Device configuration file. To create the file:

  1. Start by checking proclist.txt to determine if the device you are configuring is supported by Multi-ICE:

    • If the device type is not supported, you can name the device by creating a device entry that tells Multi-ICE how long the scan chain select register for the device is. See Naming an unsupported device.

    • If the device type is supported, note the name of the device entry in the file IRlength.arm. See The IRlength.arm configuration file for more information about this file.

  2. Open a text file editor, and create a new file, using the file extension .cfg.

  3. Enter entries in the text file for at least:

    • A TITLE section.

    • A TAP 0 section, containing the name used in IRlength.arm for the first device.

    Additional sections in the file might be required depending on the devices you are configuring. Refer to Device configuration file for more information.

  4. Save the file.

  5. In the Multi-ICE server, click File ? Load Configuration....

  6. Locate the configuration file you created, and click Open.

  7. The Multi-ICE server is configured to expect the devices you put in the configuration.

    Note

    When you load a manual configuration, the Multi-ICE server does not check that the devices you configure match the actual scan chain. It is your responsibility to ensure this.

Naming an unsupported device

To name a single UNKNOWN device:

  1. You must find out the length of the TAP controller instruction register (IR) in the unknown device. You can do this by:

    1. Autoconfiguring the target.

    2. Double clicking on the UNKNOWN device box in the Multi-ICE server window. A dialog box appears that includes the IR length.

  2. Create a text file called USERDRVn.TXT (where n is the IR length of the unknown device) to the Multi-ICE installation directory. The file must contain the name of the device.

For example, to name a target that included a TAP controller for a DSP that had an IR length of 4 bits, you would create a file called USERDRV4.TXT containing the text DSP.

Note

You cannot name multiple devices that have the same IR length because the Multi-ICE server cannot distinguish between them.

The IRlength.arm configuration file

The Multi-ICE server calculates the length of the scan chain by adding the length of each IR register it finds in the JTAG chain. This information is held in a file called IRlength.arm. You can edit this to store information on other devices that you use, for example a DSP. This file is stored in the Multi-ICE installation directory. An extract from the IRlength.arm file is shown in Example 3.2.

Example 3.2. Extract from irlength.arm configuration file

;ARM7 series cores
ARM7TDMI=4
ARM7TDMI-S=4
ARM740T=4
;ARM9 series cores
ARM9TDMI=4
ARM920T=4
Copyright © 1998-2002 ARM Limited. All rights reserved.ARM DUI 0048F
Non-Confidential