Keil Logo

µVISION DEBUGGER: J-LINK CAUSES RDI ERRORS AT DEBUG START


Information in this article applies to:

  • MDK-ARM All Versions

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

Last Reviewed: Tuesday, January 31, 2012


Did this article provide the answer you needed?
 
Yes
No
Not Sure
 
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.