Specifications

Table Of Contents
ARM Debugger 11 Troubleshooting
©1989-2014 Lauterbach GmbH
Troubleshooting
Communication between Debugger and Processor can not be established
Typically the SYStem.Up command is the first command of a debug session where communication with the
target is required. If you receive error messages like “debug port fail” or “debug port time out” while executing
this command this may have the reasons below. “target processor in reset” is just a follow-up error message.
Open the “AREA” window to see all error messages.
The target has no power or the debug cable is not connected to the target. This results in the
error message “target power fail”.
You did not select the correct core type SYStem.CPU <type>.
There is an issue with the JTAG interface. See ”ARM JTAG Interface Specifications”
(arm_app_jtag.pdf) and the manuals or schematic of your target to check the physical and
electrical interface. Maybe there is the need to set jumpers on the target to connect the correct
signals to the JTAG connector.
There is the need to enable (jumper) the debug features on the target. It will e.g. not work if
nTRST signal is directly connected to ground on target side.
The target is in an unrecoverable state. Re-power your target and try again.
The target can not communicate with the debugger while in reset. Try SYStem.Mode Attach
followed by “Break” instead of SYStem.Up or use SYStem.Option EnReset OFF.
The default JTAG clock speed is too fast, especially if you emulate your core or if you use an
FPGA based target. In this case try SYStem.JtagClock 50kHz and optimize the speed when you
got it working.
Your core needs adaptive clocking. Use the RTCK mode: SYStem.JtagClock RTCK.
The core is used in a multicore system and the appropriate multicore settings for the debugger
are missing. See for example SYStem.CONFIG IRPRE. This is the case if you get a value
IR_Width > 5 when you enter “DIAG 3400” and “AREA”. If you get IR_Width = 4 (ARM7, ARM9,
Cortex) or IR_Width = 5 (ARM11), then you have just your core and you do not need to set these
options. If the value can not be detected, then you might have a JTAG interface issue.
The core has no clock.
The core is kept in reset.
There is a watchdog which needs to be deactivated.
Your target needs special debugger settings. Check the directory \demo\arm\hardware if there is
an suitable script file *.cmm for your target.