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: http://www.keil.com/support/docs/3576.htm . I also tried installing the software on 2 other machines; one behaves the same way, the other works normally. Does anyone know why the V2 device would behave differently under uVision?
Thanks
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. Is there a way to force uVision to look in it's own directory first?
Thank you for the solution I had the same Problem for 3 days. You saved my day xD
Have a nice day