• State Not Answered
  • Locked Locked
  • Replies 16 replies
  • Subscribers 67 subscribers
  • Views 10817 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 104496
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to revert nRF51-DK interface MCU firmware back to the J-Link image?

aaronxu

As nRF51-DK User Guide said: "If you have swapped to the mbed image and want to revert back to the J-Link image, download the latest SEGGER J-Link software from www.segger.com and open a debug session to update to the latest J-Link OB firmware version."

I press Reset button and plug in the USB cable, then the LED5 is blinking. After that, the USB identification changed from MBED to JLINK. But it still can not be recognize by nRFgo or Keil. that means I can not use nRFgo studio to flash or erase nRF51822, or even use Keil to debug it. It's still looks like mbed interface.

PS: nRFgo studio Version 1.17.1 Keil Version 5.12 Segger J-link ARM V4.74b

Thanks.

  • 0 in reply to K. Townsend

    Yes ... 4.94f ... but I think it can't be a driver problem from Segger anyway since the device constantly enumerates with the mbed bootloader, which the J-Link wouldn't do. I'm just hoping someone somewhere can confirm that this actually worked for them, or to know if no one has been able to switch to the J-Link to know if this is an isolated incident or not???

  • 0 in reply to K. Townsend

    Hi Kevin. The mbed bootloader or drag and drop does not work with OSX 10.10 at the moment. But you shouldn't have had any issues with windows 7. Are ou sure you downloaded the correct firmware from the nordic mypage? they provide both the jlink and cmsis dap firmware image and it's easy to confuse the one with other.

  • 0 in reply to K. Townsend

    Hi Tuze. I've tried on Win 7 (native) as well with the same results, but I'll try again just to be sure. I double checked of course that I'm using the JLink firmware downloaded again from the My Pages account just to be sure.

    ... Just tested again and whenever I drop the jlink .bin file onto the bootloader driver (with or without holding down the 'IF BOOT/RESET' switch) it accepts the images, the bootloader window closes and I get a very fast blinky, and then next power cycle it's still on the mbed image (the bootloader shows up again). Strange, but I'm not sure how else to explain it. Is the fast blinky perhaps an error code indicating that the binary wasn't accepted?

  • 0 in reply to K. Townsend

    This is the file I'm using for reference sake: 'J-Link OB-SAM3U128-V2-NordicSemi 140918.bin' ... perhaps I can try without spaces in the filename.

  • 0 in reply to K. Townsend

    That seems to have worked ... not sure why, but I see a J-Link now.

Related