"No JLink Device found" nRF51 uVision 5.13

[srobison]

I cannot get uVision to recognize the J-Link OB device on my nRF51 Eval board. uVision DOES work with a different J-Link OB eval board targeting the same device, the Rigado BMD-200. Both work with the SEGGER tools. The only appreciable difference between these boards seems to be that the nRF51 J-Link device has the following name: J-Link OB-SAM3U128-V2-NordicSem V1.00 The BMD-200 device name is: J-Link OB-SAM3U128 V1 The V2/nRF51 J-Link shows up as a disk drive under Windows, V1 does not. I've tried re-installing the SEGGER drivers, changing the JlinkARM.dll version in C:\Keil_v5\ARM\Segger, and verifying the USB ID as described here: www.keil.com/.../3576.htm . I also tried installing the software on 2 other machines; one behaves the same way, the other works normally. The two devices do load slightly different drivers according to their hardware IDs: nRF51-DK: VID/PID = 1366/1015 BMD-200: VID/PID = 1366/0105

Has anyone else experienced and solved this? A Nordic engineer has been assisting me but so far no success.

Thanks

[srobison]

Just tried updating J-Link to 4.96f - no change. I'm having the same problems as @andreas and trying the same troubleshooting steps as described in the post here: devzone.nordicsemi.com/.../

[srobison]

@Asbjørn I can post screen shots, but they would be identical to those in andreas post (except in english). The only difference I'm aware of between the machine on which it works and the others is the Windows version: the working one is Windows Home Premium 64, the others are Windows 7 Professional 64.

[srobison]

SOLVED: 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. Thanks @Asbjørn for your help!

[Asbjørn]

I see that you were able to figure it out completely without my help as well. I'm glad you got the issue resolved at that you can now focus on actually working with the kit. Thank you very much for the update and feedback on what was actually causing this. Hopefully it's not something that more people will run into.