5.2.1. Multi-ICE server messages

These are the server error messages:

An error occurred while attempting to set up the TAP configuration.

The hardware cannot be configured, or the application ran out of memory.

An error occurred while opening the selected port.

An unexpected software error has occurred. Contact technical support.

An error occurred while retrieving the hardware details. This application will now terminate.

Contact technical support at your supplier.

An error prevented retrieval of hardware details.

Contact technical support at your supplier.

Hardware Interface Timeout.

See The debugger reports “Hardware interface timeout”.

Auto-Configuration failed. Check the target power is on. Your chip may require manual configuration.

This might be because:

  • The power is off.

  • The Multi-ICE directory does not exist, or cannot be written to. Check that the directory exists and that you have sufficient access to it.

  • The chip might not be an ARM chip. You must write a manual configuration file. See Server configuration.

Could not clean D-Cache - memory may appear incoherent in writeback regions.

For targets that have separate data and instruction caches (such as the ARM920T), Multi-ICE uses the Cache clean code address setting in the Multi-ICE configuration dialog (see Processor Settings Tab) to specify memory it can use to store and execute the cache cleaning code. Multi-ICE downloads and runs relocatable code into this memory the first time it is required. If it cannot download the code correctly, it displays this warning message.

Multi-ICE can fail to download the code to the target for one or more of the following reasons:

  • There is no memory at the Cache clean code address

  • The memory at Cache clean code address is in read only memory (either true ROM or memory that requires a special write procedure, such as EEPROM)

  • There is an active Memory Management Unit (MMU) and the page containing Cache clean code address is marked read-only.

You can take one or more of the following steps to correct this:

  • You can change Cache clean code address to an address in RAM that Multi-ICE can access and that is not used by the application

  • You can ensure that the MMU page descriptor for the memory you specified enables data reads, data writes and instruction reads.

You can force Multi-ICE to download the cache clean code again by changing the Cache clean code address setting in the Multi-ICE configuration dialog.

If you ignore the error, you must be aware of the following:

  • The Data Cache (DCache) uncachable bit is not set, and the DCache is not cleaned while in debug state.

    This means that memory is still read precisely as the processor sees it, so there is no inconsistency even when the DCache has dirty data in it. However, any data read in cachable regions causes DCache linefills to occur, so new addresses are written into the DCache and old data is evicted.

  • Any data that is written to memory is written as normal.

    This means that any writes that hit addresses in the DCache do not get into memory, but only into the cache. This matters if the data is actually code.

    A side-effect of this is that software breakpoints set on addresses that have been cached in the DCache are not read correctly on processor instruction fetches and so are not taken.

Note

If the Fault Address Register (FAR) and Fault Status Register (FSR) are implemented by the system coprocessor, they are read on debug state entry. The values are available in the system coprocessor (number 15) register display and get restored before leaving debug state, unless you write new values. If you perform a debug action that causes a memory abort, then an error is returned that includes the FSR and FAR values just after the abort.

TAP configuration failed. Please check that the target hardware and the Multi-ICE unit are properly connected and powered up.

Check that the Multi-ICE interface unit has power, and is connected to the workstation using the cable supplied with Multi-ICE.

The Multi-ICE parallel port driver requires that the parallel port interface on the host workstation is at one of the two standard addresses. This is 0x378 for LPT1, and 0x278 for LPT2. If your hardware uses a different address, the Multi-ICE interface unit cannot be used.

If you are using Multi-ICE with a 14-way connector on the target board:

  • If power is being supplied by the target, check that jumper J3 on the 14-way JTAG adaptor is linking +5V and TP and that, if necessary, the series resistor on your target has been shorted. See Connecting to nonstandard hardware.

  • If power is being supplied externally, check that the supply voltage is correct and switched on. See Connecting the Multi-ICE hardware.

Failed to open parallel port. The port may be in use.

This might be because:

Multi-ICE device driver failure. Please check that the Multi-ICE device driver is installed and running and there is no other Multi-ICE Server running.

The Multi-ICE parallel port driver is not present or has not started. The driver is started in different ways depending on the operating system:

Windows NT 4.0

In the devices control panel look in the device list for the name Multi-ICE and check the driver is present and has started.

Windows 95, 98, Me, and 2000

The Multi-ICE driver is started automatically by the server.

The server could not initialize correctly. Please close down one or more applications and re-start.

Other applications are using system resources required by the Multi-ICE server, for example, system timers, graphics resources, or main memory. Close down other applications if there are any. If not, the error might indicate that Windows must be restarted.

The server installation is incomplete or damaged. You may wish to re-install the software.

The server cannot find a required entry in the system registry. This might happen if:

  • this version of Multi-ICE has not been installed on this computer

  • the Windows system registry of the computer has been damaged.

If you have an existing installation of Multi-ICE, you must first uninstall it. You must then reinstall the Multi-ICE software.

Note

It is recommended that you check for any wanted configuration files stored in the Multi-ICE directory before uninstalling.

The attached device is not compatible with this server.

The hardware attached to the parallel port is either:

  • not a Multi-ICE interface unit

  • a faulty Multi-ICE interface unit.

Check that the Multi-ICE interface unit is connected to the correct parallel port. If it is, check that the unit is connected as indicated in Connecting the Multi-ICE hardware and that the cable is working properly. If the error persists you must contact technical support at your supplier.

The decision to read core information has been re-specified in file filename at line number.

It has been specified more than once in the configuration file whether core information is automatically read from the connected devices. You must remove one of the two entries from the configuration file.

The selected server is not compatible with this debugger.

The ARM Multi-ICE DLL can only be used with the ARM Multi-ICE server.

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