https://devzone.nordicsemi.com/f/nordic-q-a/6583/nrf51822-not-detectedHello I have a nrf51822 mbed kit PCA 10024 V1.0.0. When I connect the kit to the PC (Windows 7 64 bits) the Mkit enumerates as an MSD named MBED: I updated the firmware to version 2018following the instructions stated in the following link: developeren-USTelligent Community 13Wed, 22 Apr 2015 06:44:31 GMThttps://devzone.nordicsemi.com/thread/22989?ContentTypeID=1Wed, 22 Apr 2015 06:44:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6565150f-0fa5-4423-aa14-088f395897eeMartinBL<p>Can you please try this:</p> <ul> <li>Unplug mkit from the usb.</li> <li>Press and hold down the reset button and connect the usb while doing so</li> <li>Mkit should now enumerate as an MSD named “BOOTLOADER”</li> <li>Copy the binary file attached to the BOOTLOADER drive.</li> <li>Wait until the drive dismounts and the mbed LED is flashing continuously</li> <li>Unplug the board and plug in again, and the board should enumerate as usual.</li> </ul> <p>To erase an NRF chip on a bricked board (this will only work after the attached firmware update is done):</p> <ul> <li>Connect the mkit via usb and make sure it enumerates as an MBED drive.</li> <li>Press and hold down the reset button for ~5s</li> <li>The mbed LED will start flashing while the reset button is pressed, and after 5 seconds the LED will flash at a faster rate to indicate the NRF chip erase.</li> <li>Once the above step is complete the nrf chip should be fully erased and the board unblocked.</li> </ul><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/22988?ContentTypeID=1Tue, 21 Apr 2015 12:52:59 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2ef24522-b0ba-42d7-a6d2-497643f6d093guillermo<p>Hi Many thanks for your answer. I&#39;m still trying to detect the nrf51822 mbed kit PCA 10024 V1.0.0.</p> <p>I don&#39;t have a nrf518922 DK, but a nrf51822 mbed kit, I&#39;m trying to reprogram the</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/22987?ContentTypeID=1Mon, 20 Apr 2015 07:58:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:65c2fab1-6daf-45d0-b609-3e93cc51b0f6MartinBL<p>Can it be that the J-link driver is not present on the Segger chip anymore? Try to reprogram the J-link driver with the following steps:</p> <ul> <li>Download the J-link driver from the <a href="https://www.nordicsemi.com/eng/nordic/Products/nRF51-DK/nRF51-DK-J-Link-IF/38671">nrf51 product page</a>.</li> <li>Enter bootloader mode on the Segger chip by keeping IF BOOT presset at startup</li> <li>Drag and drop the downloaded bin file, then do a power-cycle.</li> </ul> <p>The board should now be visible in nrfGo studio. This question on <a href="https://developer.mbed.org/questions/5223/How-to-revert-interface-MCU-firmware-bac/">developer.mbed.org</a> might also be relevant to you.</p><div style="clear:both;"></div>