dsPIC33 Debugger | 13
©
1989-2022
Lauterbach
Typically the
command is the first command of a debug session where communication with
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
window to display all error messages.
•
If the target has no power or the debug cable is not connected to the target, this results in the
error message “target power fail”.
•
Did you select the correct core type with
<cpu>
?
•
There is an issue with the debug interface. Maybe there is the need to set jumpers on the target
to connect the correct signals to the debug connector. The debugger will not work, for example, if
PGEC signal is directly connected to ground on target side.
•
The target is in an unrecoverable state. Re-power your target and try again.
•
The default debug clock prescaler is too low. In this case try
0xA0
and
optimize the speed when you got it working.
•
The target was not prepared for debugging with TRACE32. In this case try
.
•
There are no pull-down resistors connected to the communication lines. For further information
see the chapter
.
•
The core has no clock.
•
The core is kept in reset.
•
There is a watchdog which needs to be deactivated.
FAQ
Please refer to our Frequently Asked Questions page on the Lauterbach website.
