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
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].
BR, /th.
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 :-)