ARM Technical Support Knowledge Articles

J-LINK CAUSES RDI ERRORS AT DEBUG START

Applies to: uVision Debugger

Answer


Information in this article applies to:


SYMPTOM

After I upload my program, and before the debugger starts, the RDI driver reports errors coming from my J-link.

CAUSE

The hardware needs time to "synch up" to the J-link, at the beginning of a debug session.

RESOLUTION

In the J-Link RDI Configuration dialog, go to the CPU page, and set the value in the Delay After (delay after reset) control to 200 ms. That should give the hardware plenty of time to stabilize, after the reset.

You may need to update to the latest Segger drivers, in order to set this option. You can find them at The Segger Site

Starting with MDK-ARM version 3.50 and later, support was added for the SEGGER Microcontroller J-Link and J-Trace hardware debug units. The recommended debugging solution is using the Keil-provided J-link drivers - not the RDI interface.

STATUS

MORE INFORMATION

Article last edited on: 2012-01-31 05:42:12

Rate this article

[Bad]
|
|
[Good]
Disagree? Move your mouse over the bar and click

Did you find this article helpful? Yes No

How can we improve this article?

Link to this article
Copyright © 2011 ARM Limited. All rights reserved. External (Open), Non-Confidential