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.

[Andreas]

---

-----------------EDIT----------------------

Finally JLINK showed up in Keil after following this procedure:

(Not all of the steps may be required. Probably 7-10 will do the trick, as JLINK still was not detected after 6.)

1. Deinstalled all Keil, nrf and segger tools
2. Manually deleted all jlink related registry entries (by using "jlink" search in regedit)
3. Restarted windows machine
4. Unplugged nRF51-DK
5. Installed Keil 5.13
6. Installed Segger 4.96f
7. Manually deinstalled all JLINK devices in device manager (use view all devices mode)
8. Delete all jlink files in Windows/system32 and subfolders (use i.e. fileassassin when deletion is denied by system)
9. Restarted machine
10. Manually installed jlink drivers in device manager (updateDriver/searchComputer/listOfDevices/disk and point to \SEGGER\JLink_V496f\USBDriver)

At least JLink shows up in Keil now, but still CDC device has yellow exclamation mark in device manager and driver installation fails with strange error:

1. According to logfile \windows\dpinst.log installer is missing some jlink inf file (ah, yes, I deleted mentioned folder in past couple of days...)
2. Manually created folder \Windows\System32\DriverStore\FileRepository\jlinkcdc.inf_amd64_8134dd13435f192f
3. Then copied all cdc files from segger\usbdriver\cdc to folder above
4. installed segger cdc driver by executable in segger\usbdriver\cdc folder without error

Now, after one week of nrf51-dk installation its time to do some work on it...

Hope this helps.

---

-----------------/EDIT---------------------

Can anyone confirm that download and debugging with Keil on nrf51-dk and win8.1 machine is working fine?

[Nguyen Hoan Hoang]

I work with Keil 5.12 on Win 8.1. Works fine.
Do you have nRFGo open at the sea time ? Only one application can connect to the jlink at one time.

[Andreas]

Ok, thanks for your confirmation on win8.1. Let's see if I could get Keil 5.12 somewhere.

nrfGo was closed before trying to download in Keil.

[srobison]

I'm having the same problems and behavior as @Andreas. I tried downgrading uVision to 5.12 as suggested but nothing changed. I've also seen no difference in any version of J-Link I've tried (4.94j, 4.96b, 4.96f). Reinstalling nRFgo studio and uVision hasn't helped. Please let me knwo if anyone solves this. Thanks!

[Sam]

I have nRF51-DK PCA10028. This works for my personal macbook pro, not for my work macbook pro. I'll have to try again on my work laptop; I suspects the fix could be in step #10. My person Macbook Pro System environment: OSX 10.9 Parallels Desktop 10 with Win 7 professional. Keil 5.13 Segger J-Link v4.94j (C:\Keil_v5\ARM\Segger\JLink.exe)

[Asbjørn]

This is really good news. I'm glad you figured it out even though we never were able to re-produce it here at Nordic. Hopefully it's not a problem that will occur to more people. Thank you very much for the update.