Hi,
I'm in the process of moving my project from Keil uVision v 3.60 to v 4.00 and seem to have lost the option of using "RDI Interface Driver" for debugging, it simply isn't in the list in the new version.
I've checked that the license of both uVision and my J-Link-JTAG device is valid and that debugging still works fine in Keil 3.6. I've also noticed that in Keil 4 the ARM\Segger directory does not contain the jlinkrdi.dll
Is there any way to get this working again or has RDI-debugging support been removed completely?
Any help is appreciated /Ã…ke
yes, the RDI is outdated and not supported anymore.
If you have an ARM9 device, please use the ARM7/9 J-Link driver from the drop down list,
and if you have a Cortex-M3 devide please use the fantastic new Cortex-M3 J-Link driver :-)
That driver is a new development, which is able to do everything the ULINK can do, and supports the complete range of J-Links (except the IDE locked) that is currently out, i.e. J-Link V6 (500kHz SWO), J-Link V8 (6MHz SWO), J-Link Pro (Ethernet support for debugging over eth), SAM-ICE, and also debugging over J-Trace. This driver also autodetects the connected J-Links capabilities to select the best possible mode.
Trace over SWO (PC sampling) and ITM printf is also possible, when tracing over SWO the interrupt Names (Cortex internal and Vendor external) are shown in the Trace Window.
--- The J-Trace CM3 driver is currently in development, but will be avaiable as beta soon. This driver shows the complete trace of code, and also autoconfigures the trace method, dependent on the connected J-Trace (or also fall-back to J-Link SWO if you have configured for J-Trace and connect a J-Link or vice versa).
Please write an email to Keil support if you are interested in beta testing.
--- For what exactly do you need the RDI suport?
BR, /th.
Thanks for the information Thorsten.
RDI is not required for anything special, I'm just trying to get debugging in working order.
Since I have an ARM (Atmel at91sam9261) so I guess the option I should select is "J-Link/J-Trace"?
The settings seem fine for that driver (I can retrieve info about the J-Link device) but gives me the Error message "No ULINK Device found" when I start debugging.
(I have a J-Link v 5.00 and have the latest drivers installed if that might be useful information)
The CM3 driver sounds neat but is not for me =)
Andy: When I for an other issue contacted my local support they refered me to the forum for quick response.
Regards /Ã…ke
you want to use the ARM7/9 driver, ok. Did you know, that you can specify conditional breakpoints?
CMD Line: BS READWRITE myvar; BS READWRITE myvar == 0x12;
But: The ARM7/9 has only 2 WP units, so you can create 2 READ/WRITE/READWRITE BPs or 1 value (i.e. == 0x55) BP.
If you have any problems with the driver, please contact Keil Support Intl by mail and I'll fix it.
If you find something that is a show stopper for your work, you can copy the RDI driver from an old version into the segger folder and add a line in tools.ini simular to the ARM7/9 J-Link driver under [armads].
Hi again and thanks for your help. My problem then seem to be that I my choices for debugging are: ULINK ARM-debugger, Signum Systems JTAGjet and J-Link/J-Trace.
I managed to add the old RDI-driver but debugging won't start this time either. Can I similarly add the J-link ARM driver by adding some dll-file to tools.ini?
I just tried with a ULINK 2 and this one doesn't work either, I think I'll try to reinstall uVision tomorrow morning.
Once more thank you for your assistance and the quick responses.
BR /Ã…ke
> I managed to add the old RDI-driver but debugging > won't start this time either. Can I similarly add the > J-link ARM driver by adding some dll-file to > tools.ini?
jep!
[ARMADS] ... TDRV11=Segger\JLinkRDI.dll("J-LINK RDI Driver") ... CPUDLL0=SARM.DLL(TDRV0,TDRV5,TDRV6,TDRV11) # Drivers for ARM7/9 devices
TDRV_NextNumber :-)