| ||||
| Home Products Events Support | ||||
Technical Support
Support Resources
- Support Knowledgebase
- Product Manuals
- Application Notes
- File Download Area
- Product Updates
- Discussion Forum
- Books
Product Information
µVISION DEBUGGER: SUPPORT FOR J-LINK
Information in this article applies to:
- MDK-ARM Developer Kit versions 3.15a and earlier
QUESTION
I have a version of Segger J-LINK (or SAM-ICE or MIDAS-LINK) and want to work on a Philips LPC2148 device. However, it appears that the RDI driver from Keil does not allow programming of this device. What can be wrong?
ANSWER
There are different versions of the Segger J-LINK and these versions are locked to specific devices. You must purchase a full J-LINK together with a Segger RDI interface to get unlimited device support. Make sure you have the latest J-LINK ARM driver, and (for J-LINK) the proper Segger licenses. Segger requires separate, add-on licenses for:
- Debugging
- Setting Flash Breakpoints
- Flash Programming
As an alternative, we recommend purchasing a Keil ULINK. ULINK is not restricted and can be used with any target hardware (provided that you have the correct adapter cable).
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.
MORE INFORMATION
- Getting Started User's Guide, RDI Interface Driver
- Refer to the J-Link/J-Trace User's Guide.
SEE ALSO
- µVision DEBUGGER: USING SAM-ICE WITH µVision
- µVision DEBUGGER: ATMEL SAM-ICE SUPPORT
- µVision DEBUGGER: SUPPORT FOR SEGGER J-LINK
- µVision DEBUGGER: J-LINK CAUSES RDI ERRORS AT DEBUG START
FORUM THREADS
The following Discussion Forum threads may provide information related to this topic.
Last Reviewed: Wednesday, April 21, 2010
| Contact Site Map Press Privacy | Copyright © 2010 ARM Ltd and ARM Germany GmbH. All rights reserved. |
