• State Verified Answer
  • Replies 9 replies
  • Subscribers 63 subscribers
  • Views 7229 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 105397
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

"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

Parents
  • 0

    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.

Reply
  • 0

    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.

Children
No Data
Related