readme.txt

sqlite-source-wince源代码学习

This should read:

   Adaptive   ON if the target drives RTCK. OFF if not driven.


Important Note for progcards Users
==================================
To improve the robustness of the Multi-ICE Server, several changes
were made to the TAPOp API in Multi-ICE 2.1. 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 Multi-ICE 2.2 CD. This new version is compatible with
Multi-ICE 2.1 and later.

Please note that no progcards board files are supplied with
Multi-ICE. Board files are supplied with other ARM products, including
ARM Integrator boards and the ARM Firmware Suite.


Important Note for Semihosting Users
====================================
With $semihosting_enabled set to 1, when $semihosting_vector is set to
point at the SWI vector, that is either '0x00000008' or '0xffff0008'
(the 'high vectors' equivalent), Multi-ICE will use the vector catch
hardware of the processor, if present, to trap semihosting
calls. (Vector catch hardware is present on ARM9, ARM10, and XScale
Microarchitecture family processors.)

As a result, semihosting calls are trapped whether or not the 'high
vectors' control bit is set. That is, it is as if Multi-ICE had set
$semihosting_vector to be both 0x00000008 and 0xffff0008
simultaneously.

In previous releases, Multi-ICE would not handle semihosting calls
properly if $semihosting_vector was set to 8 with high vectors set, or
to 0xffff0008 with high vectors cleared. Although vector catch would
be used, semihosting does not function. As the documentation states,
the default value for $semihosting_vector is set in accordance with
the setting on 'high vectors' on start-up; however, this default
value will be immediately overridden by a debugger default value if
using AXD.


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 Windows 2000 Users
=====================================
The Multi-ICE server application does not function correctly on
Windows 2000 if the 'portmap' service is not already running
when the server is started. This can be the case if the 'Start-Up
Options' for the server have been configured with the 'Start Portmap
Service' checkbox unchecked.

Disabling all network connections from the same dialog remedies the
problem, as does manually starting the portmap service from the
Multi-ICE folder on the Windows Start Menu. Note that without the
portmap service running, Multi-ICE cannot accept network connections,
on any operating system.


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.


Important Note for Engineers Integrating ARM Processor Cores
============================================================
Multi-ICE makes use of the JTAG TAPID register when the user selects
auto-configure within the Multi-ICEServer application in order to
identify the processor core being connected to.

The value for TAPID is usually set when integrating the ARM core
into a design. It is not set within the ARM core itself. Please
refer to the technical reference manual for the processor you are
integrating for further information.


Important Note for Users of the ARM eXDI Multi-ICE Driver with
Processors based on Intel XScale Technology
==============================================================
Previous releases of Multi-ICE did not function correctly using
Microsoft Platform Builder, the ARM eXDI Multi-ICE Driver and
Multi-ICE to debug a system using a processor based on Intel XScale
technology.

The new features added to Multi-ICE 2.2.5 improve the support for
users of the ARM eXDI Multi-ICE Driver when connecting to such
XScale processors.

Please refer to the section "Improved Support for Debugging Processors
based on Intel XScale Technology" in "What's New", above.

The settings that should be used when debugging Windows CE are:

  * Low vectors : Set to "Shadow".

  * High vectors : Set to "Preload". Set the "Undef" instruction type
    to "Load pc from", and set the "Undef" address to "0xffff03e4".
    Set all the other exception types to "Use pc table".

    Note: The address used may differ from one Windows CE kernel build
    to the next. This value is believed to be valid for all versions
    up to and including Windows CE 4.2.

You must also ensure that the OAL code for your Windows CE kernel does
not invoke the "idle" low-power mode in the processor. See "Important
Note for XScale Microarchitecture Processors Users," above. Such code
exists in the function "CPUEnterIdle" in the file "pmgrxsc1.s". The
following example replacement code will not use the CPU's idle mode if
debugging:

    LEAF_ENTRY CPUEnterIdle

	mrc		p14, 0, pc, c10, c0, 0
	bmi		%f1
    ldr     r0, =0x01
    mcr     p14, 0, r0, c7, c0, 0
	b		%f3
	IMPORT	fInterruptFlag
1	ldr		r1, =fInterruptFlag
	mov		r0, #0
	str		r0, [r1]
	mrs		r0, cpsr
	bic		r0, r0, #0xc0
	msr		cpsr_c, r0
2	ldr		r0, [r1]
	cmp		r0, #0
	beq		%b2
3
  IF Interworking :LOR: Thumbing
    bx lr
  ELSE
    mov  pc, lr
  ENDIF

in addition, the functions "OEMHandleInterrupt" and
"OEMHandleInterurptFIQ" must have the lines:

    extern volatile BOOL fInterruptFlag;
	fInterruptFlag = TRUE;

near their tops. Note that this code as supplied will still use the
processor's low-power idle mode if a debugger is not connected. However,
there is an overhead added to IRQ and FIQ handlers (setting the flag
variable). This example code is supplied as-is with no implied support or
warranty.


Installation Instructions
=========================
If you are installing this release of Multi-ICE as a patch on top of an
existing Multi-ICE 2.2 installation, then please refer to the
readme_patch.txt file delivered with the patch.

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 un-install the
old version first.

UNIX platforms
--------------
The version of the Multi-ICE DLL for Solaris and HP-UX in this release
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)

The version of the Multi-ICE DLL for Linux in this release 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 un-install this release of Multi-ICE 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 this version of Multi-ICE, leaving this version
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 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 = 1345




buildnumber = 1346