• State Verified Answer
  • Replies 9 replies
  • Subscribers 62 subscribers
  • Views 7185 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

  • 0

    Same story on my end. Suggestion to my request was trying uVision 5.12. That was confirmed working with nrf51-dk by other users (at least for windows version different to win8).

    I hvae been looking around on the Keil site, but wasn't able to download older versions so far.

  • 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.

  • 0

    @srobison: I think your issue is related to the J-Link Interface MCU Firmware on your Rigado module. I initially thought that your issue and the one that @Andreas reported was the same thing, but they can't be. So in order to fix your Rigado module you should download the latest J-Link interface MCU firmware from here: www.nordicsemi.com/.../38671

    Put your Segger into bootloader and then drag and drop or copy the new file into the Bootloader disk driver that will appear. A few seconds (5 seconds) after you have copied the file into the bootloader drive, you can toggle power on the board and you should be asked for updating the Segger drivers next time you start Keil and everything should be working. On the nRF51-DK you can enter bootloader through holding down the "reset" button on the Segger when you toggle power on the nRF51-DK itself. The LED (LD5) will start blinking slowly when it's in bootloader mode. I assume there's a similar mode on the Rigado board as well.

  • 0 in reply to Asbjørn

    As stated, my Rigado module works as expected, there's no need to fix it. The problem is with the nRF51 DK. I did try flashing the nRF51 interface MCU firmware with J-Link OB-SAM3U128-V2-NordicSemi 140918.bin, but it didn't fix the problem. Thanks

  • 0 in reply to Asbjørn

    Sorry, you are correct, I misunderstood your setup. You say that you have tried it on three different computers in total. On one it works, on the other two it doesn't? Are there any differences when it comes to these computers? I'm just trying to figure out how I can reproduce the issue here. Can you post screen shot of the view/error messages you get in Keil when it's not working?

Related

core_v2_widget.Hide()