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

nRFgo Studio: No device detected and the Recover button greyed

The nRFgo Studio showed "No device detected" when the nRF51-DK board was plugged to the USB port. And the Recover button was greyed.

When the board was plugged in, nRFgo Studio detected the Segger device and the correct Segger ID. The green LED next to the Segger chip was on (continuously). When I clicked the Segger ID on nRFgo studio, the LED became off. After the "No device detected" appeared, the LED was one again.

Is the nRF51422 damaged as the recovery is not possible (greyed button)?

There was no problem the day before when I downloaded S100 v8.0 to the board.

I also tried a different USB cable but to no avail. nRFgo Studio could detect the nRF51-Dongle though.

I also downloaded and installed nRFgo studio v1.20. (The previous version was 1.17.) This time, it did not even detect the Segger ID on the nRF51-DK or the nRF51-Dongle.

  • use the command tool nrfjprog and try if any of the below commands work

    1. nrfjprog.exe -e 2)nrfjprog.exe --recover

    If 1) works, you do not need to do the step 2)

    if none of them work, then probably you have interrupted the segger firmware update. in that case , uninstall jlink software from your computer , go to segger and download the latest jlink driver for chip. again go to command line and type

    nrfjprog -i

    when it prompts you to update firmware on the chip, select ok. It normally helps if you skip when windows is "Searching driver in the windows update" as this will make the firmware upgrade timeout.

    It is not very easy to destroy the chip by one wrong flash.

  • I worked out what was wrong -> I was an idiot!

    I cut SB9 and placed a 10 Ohm resistor on R6 a long time ago. Recently, the resistor was removed and so no current was going to VDD_nRF.

    After placing a jumper across the 2-pin header (P22), nRFgo Studio could detect the chip again.

Related