NRF52 nrfjprog: ERROR: There is no debugger connected to the PC

[zoltan]

------------ EDIT Sep-21-2017 ----------------

I was able to work around the issue by trying on a Linux distribution. Here is a written guide to the package install and board connect process on Ubuntu 16.04: Warning! the guide is written for a total beginner to Linux/git/terminal and the software.

nRF52_with_Openocd.docx

---

Hello!

I am attempting to flash firmware to a nRF52 using the BMD-300-eval dev board using an JLink connection, also using openOCD. My software versions are as follows:

nrfjprog: version 8.5.0 JLinkARM.dll: version 6.20a (also tried 5.12f) OpenOCD version 0.10.0 nRF52_sdk: version 11.0.0

J-link USB driver: libwdi version 6.1.7600.16385

This has been working on another computer, but I am having trouble on my Windows 10 Home edition laptop.

After merging some binaries for the nRF5_SDK_11.0.0 BLE_peripheral example for the pca 10040, and successfully building the example, I tried to flash with the following command and output:

After researching the "invalid command name nrf52" error, I was lead to try instead "nrfjprog" commands. My next attempt was using basic nrfjprog commands found at:

infocenter.nordicsemi.com/index.jsp

The results were:

This error is strange because I CAN see the Segger J-link in my Windows "Device Manager" window. The driver version is stated above. I also tried switching and updating the drivers. Jlink Commander cannot establish a connection either.

Any help would be very much appreciated! Thanks!

-------------------------------------------- EDIT -------------------------------------------

Here are images of the properties and detail options as seen in Device Manager: nRF52 Jlink Debugger Issue.pdf

[Jørgen Holmefjord]

Do you see the MSD device named JLINK in computer, or SEGGER MSD Volume USB Device in Device Manager? Are you still able to program the board on the PC where it worked before?

[zoltan]

I do not see any MSD JLINK device in computer next to my C: drive or anything. In device manager I see a USB device called J-Link. Its properties are described as a SEGGER USB device. It does still work on the other computer, however that computer is running a Linux distribution. I will edit the question to include images of the properties of the device as shown in Device Manager, and the menus it offers. Let me know if any of the characteristics in the 'Details' tab might offer you a clue, and i can post them.

[Jørgen Holmefjord]

I do not have a BMD-300 EVAL board to test with, but are you sure it is supposed to use libwdi USB driver? Have you tried installing J-Link drivers, removing the J-Link device from device manager, and reconnect the device?

[zoltan]

Yes, I believe I did download my drivers from the Software and Documentation Pack on that page. I did try removing the device, and its drivers, and reinstalling them. Today I made a partition for Ubuntu 16.04, went through a similar software suite install, and ran into similar problems. I will make a separate post about the linux process. I will provide the link to that post here when I make it.

[Jørgen Holmefjord]

It sounds like there could be some issues with the J-Link OB firmware on the board. On our DK's, this can be reflashed by pitting the chip in bootloader mode using the method described here, and drag'n drop the firmware to the BOOTLAODER MSD drive. I cannot find any information about this on Rigados pages, or if they use the same J-Link OB firmware. I would recommend you to contact their support to check if this is possible on their board as well, or if they have some other solutions to your issue.