Multi-ICE readme.txt
                            ====================


Multi-ICE Version 2.2
=====================
This release supports Microsoft Windows NT 4.0, Windows 2000, Windows 95,
Windows 98, Windows Me, Windows XP, Red Hat Linux 6.1, Red Hat Linux 7.2,
Solaris 2.6, 2.7 (7.0), 8.0, HP-UX 10.20, and 11 (see important note below).


Documentation
=============
Refer to the Multi-ICE User Guide for more information about new features and
how to use Multi-ICE. This is available in PDF format in the \docs directory.
If you have the ARM Developer Suite, you can also choose to install the Multi-
ICE User Guide as a DynaText online book. See your ADS documentation for more
information on how to access the online books.

Note: DynaText documentation is not supported on Linux installations.


CD Directory Structure
======================
  \adobe     - installer for the Adobe Acrobat Viewer
  \ads       - updated ADS Processor Definitions
               (see \ads\readme.txt for further details)
  \docs      - Multi-ICE User Guide, license agreement, file list, readme file,
               supported processor list, troubleshooting guide
  \eXDI_1.0  - allows Microsoft Platform Builder for WinCE to connect using
               Multi-ICE (see \eXDI_1.0\readme.txt for further details)
  \progcards - progcards version 2.20
  \unix      - Installation files for UNIX Multi-ICE


FAQs and Application Notes
==========================
Technical Support FAQs : http://www.arm.com/arm/tech_faqs
     Application Notes : http://www.arm.com/arm/documentation


Important Note for ARM7EJ-S/ARM9EJ-S/ARM926EJ-S Users
=====================================================
The ARM7EJ-S rev 1, ARM9EJ-S rev 0, and ARM926EJ-S rev 0 contain an error
that causes hardware breakpoints in the upper 2GB of the address space to be
missed. When using these cores, Multi-ICE attempts to use only software
breakpoints in the upper 2GB of memory.

If a software breakpoint cannot be set, for example because the address lies
within ROM, Multi-ICE uses a hardware breakpoint with a mask set to ignore
bit 31 of the address. As a side-effect, this may cause false breakpoint
hits at the equivalent address in the lower 2GB of memory.


Important Note for Fault Registers on XScale Microarchitecture Processors
=========================================================================
The Fault Address Register (FAR) and Fault Status Register (FSR) may
be corrupted by the debugger on XScale microarchitecture processors.

Additional fault status registers are implemented on some XScale
microarchitecture processors, and these may also be corrupted. For 
example, the Bus Control Unit (BCU) ECC Error Registers of the XScale 
80200 processor.


Important Note for progcards Users
==================================
To improve the robustness of the Multi-ICE Server, several changes have
been made to the TAPOp API. These changes cause progcards version 2.01
and earlier to fail with one of the following errors:

ERROR: Multi-ICE error (8)
ERROR: Multi-ICE error (9)

Version 2.20 of progcards has been supplied in the \progcards directory
on the CD. This new version is compatible with Multi-ICE 2.1 and 2.2.


Important Note for Multiple Parallel Ports
==========================================
When using a PC with more than one parallel port, it has been reported that
running Multi-ICE Server can cause the PC to slow down until it is rebooted.

If you suffer from this problem, the following work-around can be used:
  1) Start Multi-ICE Server. This causes the PC to slow down.
  2) Select the Settings -> Port Settings menu. The Port Settings window opens.
  3) Change the Port Address from AUTO to either LPT1 or LPT2, as appropriate.
  4) Click OK. The Port Settings window closes.
  5) Close the Multi-ICE Server.
  6) Reboot the computer.
  7) Start Multi-ICE Server. This should not cause the PC to slow down.


Important Note for Trace users
==============================
When tracing code which is outside the program image, the trace
decompression tools must have access to this code in order to reconstruct
the trace data. Semihosting SWIs can cause code outside the image to be
traced, for example the instruction at the SWI vector itself, or semihosting
handler code. If the processor is still running when the trace is loaded it
is not possible for this data to be retrieved by Multi-ICE. Trace
synchronization will be lost at this point and possibly not regained for
several hundred cycles. You will see messages like these in the trace
window:

---     Synchronization lost
---     The next instruction could not be read

Note that the precise effects depend on the code being executed, the
processor core being used, the type of semihosting and the revision of ETM.
This problem has been observed when using an OnChipTrace buffer.

There are two possible solutions:
 1) Reload the trace data once the processor has stopped.
 2) Make sure all of the code being traced is available to the debugger in
    your image.


Important Note for Mixed Endianness Debugging 
=============================================
If your host environment and target platforms are of different endianness, 
memory mapped register values displayed in the register window will be reversed.

For example, on a Solaris host with a little-endian target, register values 
0x00000008 and 0xE59FF910 are displayed as 0x08000000 and 0x10F99FE5.

Note: This is only relevant when using the Board tab in the Multi-ICE 
      configuration dialog.


Installation Instructions
=========================
Please see CD insert - Multi-ICE version 2.2 Installation Guide DSI0005 for full
installation instructions.

Windows platforms
-----------------
The recommended free disk space required for a full installation (which includes
the DynaText documentation and TAPOp source files) is 20MBytes.

If you want to install the DynaText version of the Multi-ICE documentation, make
sure you have installed ADS before installing Multi-ICE.

Run the program setup.exe from the root directory on the CD.  Follow the
onscreen instructions.

Note: When installing Multi-ICE software on Windows NT or Windows 2000 you must
be logged on with administrator privileges.  All users who want to run the
Multi-ICE server must have create and write access to the Multi-ICE installation
directory.  The Multi-ICE installer will attempt to grant full control access to
everyone on this directory (this is the default for Program Files directories
under Windows NT).  If you have a strict security policy enforced on your
Program Files directory, it is recommended that you install Multi-ICE in another
directory and modify the permissions as appropriate.  This issue does not affect
Windows 95 or Windows 98.

If you are installing on a Windows platform which already contains an older
version of Multi-ICE it is recommended that you uninstall the old version first.

UNIX platforms
--------------
Version 2.2 of the Multi-ICE DLL for Solaris and HP-UX is compatible with
the following debuggers:
  * AXD (ADS for UNIX version 1.2)
  * AXD (ADS for UNIX version 1.1)
  * ADU (ADS for UNIX version 1.1)

Version 2.2 of the Multi-ICE DLL for Linux is compatible with the following
debuggers:
  * AXD (ADS for UNIX version 1.2)


You must install ADS or ADU before installing Multi-ICE for UNIX. You will
also need a networked PC, running the Multi-ICE server (under Windows), to
connect the Multi-ICE DLL to the target hardware.

To install the UNIX Multi-ICE DLL and its documentation, run the install.sh
script from the /unix directory on the CD and follow the prompts.

The source files for UNIX are in the file /unix/source.tar. To use them,
extract this file to a directory on your development machine.


Windows Uninstallation Instructions
===================================
To uninstall Multi-ICE version 2.2 run 'Setup for Multi-ICE' from the ARM
Multi-ICE v2.2 Windows folder. Then select the Remove option.

If you wish to uninstall an older version of Multi-ICE from a platform which
also contains Multi-ICE version 2.2, leaving version 2.2 working, you must:
1. Uninstall the older version.
2. Run 'Setup for Multi-ICE' from the ARM Multi-ICE v2.2 Windows folder
3. Select the Repair option.


Important Note for Microsoft Windows NT 4.0, Windows 2000 and Windows XP Users
==============================================================================
You may find that it is not possible to use other parallel port devices 
(such as printers) when Multi-ICE is installed on a PC. If you need to use 
such devices, then you will need to either:

a) temporarily uninstall Multi-ICE, or
b) temporarily disable the Multi-ICE driver.

To temporarily disable the Multi-ICE driver:

1) Locate the driver control dialog:
   For Windows NT: Open the Devices window in the Control Panel.
   For Windows 2000: Open the Device Manager from the Control Panel 
   (select System, then the Hardware tab). Use 'View -> Show hidden devices' 
   to reveal the "Non-Plug and Play Drivers"
2) Select the Multi-ICE device, then
3) Click on the Stop button. 

The Multi-ICE device is now stopped, and the printer port can be used by other
programs. To allow Multi-ICE Server to be used again, you must first restart the
Multi-ICE device by clicking the Start button in the Devices window.


Important Note for HP-UX Users
==============================
If you are using Multi-ICE with AXD under HP-UX, you may see the following
warnings printed to your console when you use the Multi-ICE configuration
dialog:-

 Wind/U Error (240): Function DestroyIcon, GDI API's must only be called from 
 the primary thread on this platform.

These warnings are produced because of interactions between Multi-ICE, AXD
multithreading, WinD/U and HP-UX. This is harmless and can be ignored.
They will not occur once you have configured Multi-ICE.



buildnumber = 1095