This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

rf51 dongle dev kit - sd_rpc_open hangs

Hello,

I just got an rf51 dongle (usb) dev kit. I have installed the latest SDK, JLINK drivers, nrfgo studio. I copied the firmware .hex file into the JLINK drive as per the readme file. I built the multilink example using MS Visual Studio Community 2015. When I run the sample, the call to sd_rpc_open never returns. Am running Windows 7 64bit.

Note sure if this is relevant but when I run nrfgostudio, it detects the dongle, asks if I want to update the firmware to the latest version. When I say yes, the firmware update always fails right at the end (last 5% or so).

Thx

  • I would make sure that the firmware on the Segger chip is correct. You can download the firmware here. You have to start the nRF51 Dongle in bootloader mode by holding down the button while inserting it into your computer( should now appear as BOOTLAODER). Then copy the firmware image into the BOOTLOADER drive, pull it out and then re-insert.

  • Bjorn, Thanks for your suggestion. I managed put it in BOOTLOADER mode using the switch. But in this mode, there isnt enough space (Windows reports 112K free) on the device to copy the firmware HEX file (470K). In the normal JLINK mode, Windows reports there is 10GB free.

    Something worth noting - if I copy the .hex file (connectivity_115k2_with_s130_1.0.0.hex) in JLINK mode, the file gets copied, the device disappears from windows list of devices, then a few seconds later it reappears (and this file I copied is not there anymore) - seems like there is some detection of this file being copied and I thought perhaps it is accepting the file and rebooting with it?

    nrfgoStudio managed to update the firmware to s120_nrf51_1.0.0(Id:0x0067)

    fwiw, i tried running the sample program and it still hangs in the same sd_rpc_open call.

    Thx!

  • Ok, I got past this problem - the sample was trying to connect to the wrong COM port. For the benefit of others who might hit this issue, go to control panel, device manager and under the COM ports node, you can see the JLINK device with its COM port # (in my case it was COM5).

Related