This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf51 DK JLink not detected by Keil

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) installed drivers in win8.1 image description

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

Thanks very much in advance.

Parents
  • I was having similar problems. I tried everything suggested here but nothing helped. I finally did find a solution though. My problem turned out to be caused by an old version of JLinkARM.dll that was being used by Keil from C:\Windows\SysWOW64 instead of C:\Keil_v5\ARM\Segger where I assumed it was pulling from. I manually updated it (copy/paste) to the one from the Keil directory and the board was recognized.

Reply
  • I was having similar problems. I tried everything suggested here but nothing helped. I finally did find a solution though. My problem turned out to be caused by an old version of JLinkARM.dll that was being used by Keil from C:\Windows\SysWOW64 instead of C:\Keil_v5\ARM\Segger where I assumed it was pulling from. I manually updated it (copy/paste) to the one from the Keil directory and the board was recognized.

Children
Related