4.3.3. Advanced configuration tab

The Advanced configuration tab contains items that enable you to configure the debugger to match the memory endianness of your target, whether to cache information, and the debugger software interface method. The tab is shown in Figure 4.13.

Figure 4.13. Multi-ICE Advanced settings tab

Multi-ICE Advanced settings tab

The dialog box contains the following items:

Target Settings

You can specify whether the target is Little-endian or Big-endian using the Target Settings radio buttons in the target configuration dialog.

These buttons are unavailable if you are using older software, such as SDT 2.51 or ADU. You must instead:

  1. Choose Configure Debugger from the Options menu of your debugger.

  2. Click the Debugger tab.

  3. Select one of the Endian buttons.

Read-ahead Cache

This is a check box allowing you to enable or disable caching target memory in the host while the processor is stopped. The checkbox setting is the initial value of internal_cache_enabled. You can flush the cache at a specific time by setting the debugger internal variable internal_cache_flush to 1. You can switch the cache off temporarily by setting the debugger internal variable internal_cache_enabled to 0. See Internal variable descriptions for more information.

Read-ahead caching improves memory read performance by reading more memory than the debugger requests, and caching the rest in case it is required. This improves performance considerably for some operations, such as when you are stepping through code with a lot of string variables displayed in a debugger window.

Initially the DLL does not read ahead. When the first successful read request is made for a region of memory, the DLL learns it can safely access that region. It then caches that region until the debugger restarts.

All of the ADS debuggers save the read ahead setting between sessions, but the version of ADW in SDT 2.51 does not.


Read-ahead caching is on by default. You must switch this feature off if:

  • you are trying to debug a system with demand paged memory

  • you are using the debugger to read hardware registers, and you do not want to unintentionally read neighboring registers.

Debugger Interface Settings

Multi-ICE supports debuggers that conform to RDI 1.5.1 and also allows you to connect to debuggers that conform to RDI 1.5. This item shows you the RDI version that is currently in use.

You can select the RDI version to be used from the dialog box.


Selects the most appropriate mode for the debugger, using an automatic version negotiation scheme. This is the default setting.

RDI 1.5

Forces the Multi-ICE DLL to use RDI version 1.5.

RDI 1.5.1

Forces the Multi-ICE DLL to use RDI version 1.5.1.

If you are using an ARM debugger, it is recommended that you use the Automatic setting, because this works correctly with all ARM debuggers.


AXD only supports RDI 1.5.1, and Automatic version negotiation selects RDI 1.5.1. If you force AXD to connect to Multi-ICE using RDI 1.5, the AXD Stop button does not work.

Report non-fatal errors on startup

This setting relates to errors that occur while the debugger is first connecting to a Multi-ICE target. If you check this option, then both fatal and non-fatal errors are reported. This is the default, and means that you are informed of any problems that Multi-ICE detects.

Some debuggers consider that any error detected during configuration is fatal, and this can prevent you from being able to connect to your target. If this happens, you must uncheck this item, so that Multi-ICE only reports fatal errors.

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