Nordic nRF52-DK disconnects from computer when I upload the BIN file

[Keith Hammock]

I am attempting to run my first bit of code on my Nordic nRF52-DK and every time I have attempted to upload the code to the board, the board disconnects in the middle of the upload process and then reconnects without the file on it. When I first move the file to the board, the LED is blinking as if it is ready to run code, but then after it disconnects and reconnects, it is no longer blinking, and pressing the reset button does nothing. I explicitly followed the instructions to upgrade the firmware of the device, and I wouldn't think that was a problem anyway since the board recognizes the code file instantly when I upload it as can be seen by the flickering LED. Also, the board will randomly disconnect and reconnect when I am doing other things on my computer. The cable I am using is brand new.

[AmbystomaLabs]

The nRF development environment uses nRFGoStudio to load application files and soft devices for BLE or proprietary wireless communications.

On the link you sent me you will find information on that if you follow the links for the development environment. This is NOT an Mbed development environment. The normal nRF environment creates native C applications for the ARM processor. Normally an OS is not utilized, though some developers do use an RTOS.

In order to use Mbed the correct version of the Segger firmware needs to be installed. The segger is the programming interface IC that has USB enabled on it.

I do not personally do any Mbed development, but based on my reading you should verify that your DK has the correct firmware installed as it was updated several times while the nRF52DK was in production.

The Mbed link for nRF52DK is here: os.mbed.com/.../

If you have further problems with Mbed on the nRF52DK, I recommend you repost your questions stating clearly that you are doing Mbed work and wait for the Nordic team to address it on Monday.