Keil IDE issue with nRF51-DK

RE: Keil IDE issue with nRF51-DK

wade smith — Mon, 03 Jul 2017 22:21:14 GMT

This is very helpful. For whatever reason in Win32 the file JlinkARM.dll was never copied to c:/Windows/System32/

By doing what Danijel said above (copying the file there) allows Keil to use the J-Link / J-TRACE Cortex debug tool; otherwise you get the error that not all the .dlls have been loaded when trying to flash or debug within Keil.

RE: Keil IDE issue with nRF51-DK

Danijel Babic — Fri, 15 May 2015 15:36:07 GMT

Problem finally solved by updating JLinkARM.dll in C:\Windows\SysWOW64 with the latest version from c:\Program Files (x86)\SEGGER\JLink_Vxxx

RE: Keil IDE issue with nRF51-DK

testy — Wed, 04 Feb 2015 12:01:09 GMT

I don't know why, but newer jlink install package (Setup_JLink_V4xxx.exe) is sometimes unable to put its own/right version to the HKEY_CURRENT_USER\Software\SEGGER\J-Link\InstallPath and older version is wrongly used instead (if ever present).

Check this

RE: Keil IDE issue with nRF51-DK

Nick Pelis — Tue, 03 Feb 2015 23:16:34 GMT

On my system, I noticed that when I click the "Jlink Cmd" button in the Target Driver Setup window, the copy of JLink Commander that opens is v4.80, stored in C:\Keil_v5\ARM\Segger\JLINK.exe. This version does NOT detect the nRF51 DK.

However, if I open the copy of JLink Commander installed by nRF Tools, which is v4.92 and installed in C:\Program Files (x86)\SEGGER\JLink_V492, it sees the nRF51 DK just fine.

So I fixed this on my system by copying the new version over the old version as follows:

Rename C:\Keil_v5\ARM\Segger\ to C:\Keil_v5\ARM\Segger.orig.
Copy C:\Program Files (x86)\SEGGER\JLink_V492 to C:\Keil_v5\ARM\Segger.
Copy JL2CM3.dll from C:\Keil_v5\ARM\Segger.orig into C:\Keil_v5\ARM\Segger. You get an error message if this file isn't present.
Make sure to change Port from "JTAG" to "SW".

Hope this helps.

RE: Keil IDE issue with nRF51-DK

Danijel Babic — Tue, 03 Feb 2015 15:19:50 GMT

I'm also using Keil uVision 5.13, Win 8.1 x64. Two other machines have uVision 5.10 on Win 8.0 x64 and they have the same problem. Interestingly, it's working on one machine with uVision 5.13 and Win 8.1 x64

RE: Keil IDE issue with nRF51-DK

Andreas — Tue, 03 Feb 2015 12:57:40 GMT

Yes Stefan, I am using Keil uVision V5.13 with Win8.1.

RE: Keil IDE issue with nRF51-DK

Stefan Birnir Sverrisson — Tue, 03 Feb 2015 12:34:44 GMT

@Andreas: Are you using uVision 5.13?

@Danijel and Moiz: What uVision version are you using and what windows version?

RE: Keil IDE issue with nRF51-DK

Moiz Qureshi — Mon, 02 Feb 2015 15:47:59 GMT

Danijel,

I have not managed to fix this issue. I have been just developing on the computers it is working.

RE: Keil IDE issue with nRF51-DK

Moiz Qureshi — Mon, 02 Feb 2015 15:44:57 GMT

Stefan,

I tried installing latest version of nRF Tools as well, but still did not work. For now I am using computer for which it is working on.

RE: Keil IDE issue with nRF51-DK

Andreas — Mon, 02 Feb 2015 15:07:25 GMT

Thaks a lot for your precise description of my problem ;-).

This exactly matches my experiences with nrf51-dk during last couple of days. JLink is detected by Segger and nrf tools, but not with Keil. I also went through full installation and deinstallation cycles of all tools.

Even though segger installation asks to overwrite Keil drivers, my feeling is that Keil is using its own drivers here... Can anyone confirm that download and debugging with Keil on nrf51-dk and win8.1 machine works fine?

RE: Keil IDE issue with nRF51-DK

Danijel Babic — Mon, 02 Feb 2015 13:51:56 GMT

This does not solve problem for me. Tried latest Segger driver and nRF Tools, no result. I have reinstalled everything (Keil, tools, drivers...) and that also didn't help. Drivers are there and are working, J-Link software and nRF studio can recognize J-Link programmer on dev kit, it doesn't work only in Keil. But if I connect older dev kit (PCA10001) or standalone J-Link programmer they work with Keil without any problems.

RE: Keil IDE issue with nRF51-DK

Stefan Birnir Sverrisson — Mon, 02 Feb 2015 13:39:45 GMT

It seems like Keil sees no Segger device. You need to install new Segger drivers in order for it to work. Install the lates version of nRF Tools, then you will get the new Segger drivers.

Let us know how it turns out for you.

RE: Keil IDE issue with nRF51-DK

Danijel Babic — Wed, 21 Jan 2015 11:57:37 GMT

I have the same problem on 3 of 4 computers. Please let me know if you manage to solve it.