nrf51 DK JLink not detected by Keil

[Andreas]

My nrf51 DK Board is not detected by Keil as jlink probe, but with other tools. As a result I am unable to download demo projects to my board.

1. unmodified nrf51 dk has been equipped with jlink .bin file via USB bootloader (J-Link OB-SAM3U128-V2-NordicSemi 140918.bin)
2. nrf51 dk is detected as Segger xxxxxx in nRFgo Studio
3. nrf51 dk is detected by segger j-link configuration tool
4. Keil download attempt fails with "No JLink Device found"
5. Keil uVision V5.13.0.0 does not detect jlink under project/options/debug
6. Keil JLink Cmd button detects JLink and reports Cortex M0 of nrf51422 in DOS box
7. Windows Restart did not help
8. a second nrf51 dk hardware shows same behaviour
9. I tried segger 4.96d/f, Keil and nrf Installations in all sequence (incl. manual removal of related folders on HDD and computer restarts)
10. By now there are 4 segger entries that cannot be removed by windows anymore (see picture)
11. Some installled Keil driver seems to be pretty old and seems to be reinstalled everytime Keil 5.13 is installed (see picture)
12. During segger installation I am now getting an install error (see picture)

Please help in getting toochain working properly. Any hints appreciated.

Thanks very much in advance.

[Asbjørn]

NEW EDIT: I've been trying to re-create the issue you are seeing. I've un-installed all my tools and re-installed to see if that would trigger it. No luck in creating the same issue. The only way I'm able to see the same "Cortex Jlink/Jtrace target driver setup" as you have posted above is to switch off my kit, but that doesn't make any sense.

You see the board in nRFgo studio and you see it in Jlink commander, so it seems to be an issue with Keil or Keil configurations. Initial thought would be to un-install the Keil version you have or use the "Maintenance Status and Previous Versions" section of this site to access an older version of Keil MDK. The latest drivers from Segger is version V4.96f, but it seems to be fine on my computer with 4.94 as well.

Do you see any difference in Segger activity from different projects from our nRF51 SDK? Are you able to use Keil with for example the pure BLE examples? I'm just trying to narrow down the components that could potentially be creating this on your side.

------------------------------------------------OLD INITIAL POST--------------------------------------------------------
Just wanted to throw a heads up in there. We here at Nordic are working on it, but it's a difficult scenario to re-create as of right now. We have seen a couple of similar scenarios where nRFtools needed to be re-installed for it to work on Keil 5.13 and then re-booting the computer, but we have yet to confirm that this is the main issue here. It could be related to the MDK version from the SDK as well or the Segger drivers, Will report back as soon as possible.

[Andreas]

Thanks for letting me know and good to hear that somebody from Nordic is working on it. Customer project is on hold for now...

[Andreas]

Thanks again. So far, I was not using Keil before. It has been installed together with the Nordic stuff.

In the meantime I also tried Segger 4.96d drivers, but still JLink is not detected by Keil.

Interestingly, when pressing JLink Cmd Button out of Keil, it will report correct driver 4.96d and it also detects the Nordic Cortex M0 chip on nrf51dk... See new picture above...

[Nguyen Hoan Hoang]

Try installing Keil first. Then the latest jlink software. During the jlink installation process you will get a prompt to update DLL ... Select keil and update the DLL. Jlink will then update Keil driver with the new dll.

[Andreas]

Thanks, I have uninstalled all segger and keil related stuff. Then installed Keil 5.13, followed by segger 4.96f. Still no sucess...