Multi-ICE® User Guide 5.1. Troubleshooting

Multi-ICE^® User Guide

Version 2.2

Home > Troubleshooting > Troubleshooting

5.1. Troubleshooting

This section describes the following situations:

The Multi-ICE server fails to autoconfigure the chip
The debugger reports “Attempt to force the processor to enter debug state failed - execution continues”
The debugger reports “Target processor would not enter debug state when requested. Do you want to try asserting System Reset with a breakpoint on address 0?”
The debugger reports “*** Data abort ***” in the execution window
Random stopping or failure to start the debugger
The debugger reports “Hardware interface timeout”
The debugger reports “Unable to set vector catch breakpoints on exception vectors”
Data aborts or crashes when loading or running applications
DCC semihosting, the channel viewer, or the DCC fails
A program that prints strings seems to load and run, but displays garbled text
A 'C' program including string handling or uses char arrays works on some ARM processors but not on others
When trying to connect Multi-ICE and a logic analyzer to an ARM Integrator board to trace a program, Multi-ICE continually reports "The target is being reset, unable to connect"
My application works using ARMulator but quickly crashes when I use Multi-ICE
Running the Multi-ICE server makes my computer run very slowly
I cannot connect to a Multi-ICE server from the computer that is running it.

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

Home > Troubleshooting > Troubleshooting