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

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

vincent.zhang — Mon, 30 Mar 2015 07:04:29 GMT

i have the same problem, win7, jlink:V498a,J-Link OB-SAM3U128-V2-NordicSemi 141128.bin, can't see the jlink. does it damaged?

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

minted — Thu, 11 Dec 2014 17:14:20 GMT

I wish I had found this comment earlier ;-) Just finishing my first successful flash on OSX 10.10 for my nRF51 dongle, also using rknrfgo and mbed IDE (compilie .hex) and s110 softdevice flashing.

First I flashed the blinky sample to verify that a .hex is starting
Flashing the S110 softdevice
Using a sample to verify the correct softstack "BLE iBeacon"
Verified working iBeacon with nRF Master Control Panel Android

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

K. Townsend — Fri, 21 Nov 2014 09:16:35 GMT

You're right. Updating the OSX J-Link drivers to 4.94f (latest as of today) finally makes it appear as a J-Link on OS X 10.10 as well (ignoring the mass storage drive issues). Thanks for the tip.

Appreciate the rknrfgo J-Link wrapper as well ... I've been using it for ages as a replacement for nrfjprog, as well as the sniffer utility (although we have enumeration problems with it using these boards since it doesn't recognise FTDI based devices, perhaps because it's looking for a specific VID/PID combo: www.adafruit.com/.../2269 ... I'll have to dig into the Python API myself). Completely off topic, though ... just wanted to say thanks for the tools to make OS X easier.

In summary: update the board on a Windows PC, update the OSX drivers to 4.94+, and the J-Link should be fine on OS X 10.10, other than the annoying dialogue box due to the mass storage drive.

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

RK — Fri, 21 Nov 2014 09:05:10 GMT

That board works fine for me as a JLink device on OSX 10.10. Yes OSX fails to mount it as a mobile disk device and you get an error that it can't be mounted, however it still works perfectly well as a JLink under OSX (with V4.94c). OSX isn't corrupting the image on it, it's the MBED firmware which is reporting a filesystem OSX can't read (and so assumes to be corrupt). MBED is working on that and the same driver is ALSO embedded in the Segger software so that you can switch between them.

So switching between MBED and JLink may be a problem on OSX, but using the board with the JLink software on it as a JLink device works perfectly for me, it's just like the old dev boards in that respect.

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

Tüze — Fri, 21 Nov 2014 08:53:47 GMT

Hi Kevin, Glad it worked! Yes it's not nice being restricted from an environment, but the good news is that the fix for both jlink and mbed/cmsis are on the way to address this issue and will be released soon.

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

K. Townsend — Fri, 21 Nov 2014 08:50:57 GMT

Just as a FYI for anyone else stumbling across this, the issue seems to be anytime I insert the board into my macbook (my main development machine), even with Parallels installed and redirecting to Windows, OS X corrupts the contents of the bootloader and the J-Link firmware is lost. It seems I just need to restrict any development with the new 32KB parts to a Windows only machine until this issue can be addressed, though it's kind of a shame to have to keep two development environment open. Thanks for the heads up on the 10.10 issue, though!

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

K. Townsend — Fri, 21 Nov 2014 08:44:54 GMT

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

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

K. Townsend — Fri, 21 Nov 2014 08:41:23 GMT

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.

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

K. Townsend — Fri, 21 Nov 2014 08:38:40 GMT

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?

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

Tüze — Fri, 21 Nov 2014 08:27:48 GMT

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.

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

K. Townsend — Fri, 21 Nov 2014 05:55:42 GMT

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???

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

aaronxu — Fri, 21 Nov 2014 05:43:26 GMT

Do you use the newest version of Segger J-link driver?

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

K. Townsend — Thu, 20 Nov 2014 23:49:49 GMT

I've tried this on two laptops with two (sort of three) different operating systems.

Dragging and dropping the J-Link binary onto the nRF51-DK doesn't work for me in any of the following situation:

OS X 10.10
Windows 7 x64 running in Parallels on OS X 10.10
Native windows 7 x64

In every case, it shows up as "Bootloader", I drag and drop the latest J-Link firmware downloaded from the My Pages account (as of 20 Nov 2014),and when the file transfer is through the device seems to reset on it's own followed by a fast blinky. When I do another power cycle, it goes back to the CMSIS-DAP firmware and the bootloader shows up again.

I've run through this a dozen times with and without the IF-BOOTLOADER button being pressed, and I'm unable for the life of me to apply the J-Link firmware.

Has anyone been able to switch from CMSIS-DAP back to J-Link? We need a J-Link interface for development here since all of our makefiles and test scripts use the J-Link as the flash interface. I'm currently using an external J-Link, but this is far from an ideal solution any time we need to be mobile with the kit.

The new boards look great ... I just wish I could debug them with the same tools we use on the PCA10001.

Any concrete suggestions, or can anyone confirm they were able to switch?

I have PCA100028 V1.0.0 with the timecode 2014.39.

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

Tüze — Wed, 19 Nov 2014 09:24:15 GMT

Hi!

Did you follow Gaute's response?
developer.mbed.org/.../

Try upgrading your jlink version to the latest: segger.com/jlink-software.html

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

aaronxu — Tue, 18 Nov 2014 07:35:02 GMT

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

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

aaronxu — Tue, 18 Nov 2014 07:00:34 GMT

In addition,I think the nRF-51 Dongle is flashed Jlink interface firmware by default. But I can not use it in nRFgo studio or Keil. It's also looks like mbed interface, just can be used by dragging image file on it.