<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NRF52 nrfjprog: ERROR: There is no debugger connected to the PC</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/25286/nrf52-nrfjprog-error-there-is-no-debugger-connected-to-the-pc</link><description>------------ 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</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 21 Sep 2017 18:40:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/25286/nrf52-nrfjprog-error-there-is-no-debugger-connected-to-the-pc" /><item><title>RE: NRF52 nrfjprog: ERROR: There is no debugger connected to the PC</title><link>https://devzone.nordicsemi.com/thread/99637?ContentTypeID=1</link><pubDate>Thu, 21 Sep 2017 18:40:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a7ceef25-2343-43f5-b28b-e5b85e4a203a</guid><dc:creator>zoltan</dc:creator><description>&lt;p&gt;Solved using Linux! I will edit the post to include a writeup/guide to what I did to work around the issue. Thank you Jørgen for your help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 nrfjprog: ERROR: There is no debugger connected to the PC</title><link>https://devzone.nordicsemi.com/thread/99636?ContentTypeID=1</link><pubDate>Thu, 21 Sep 2017 11:26:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a16e366b-d8e7-4ffa-88fe-796f7c5a010f</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;It sounds like there could be some issues with the J-Link OB firmware on the board. On our DK&amp;#39;s, this can be reflashed by pitting the chip in bootloader mode using the method &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52/dita/nrf52/development/nrf52_dev_kit/boot_reset_but.html?cp=2_1_4_4_0"&gt;described here&lt;/a&gt;, and drag&amp;#39;n drop the &lt;a href="http://www.nordicsemi.com/eng/nordic/Products/nRF52-DK/nRF5x-OB-JLink-IF/52275"&gt;firmware&lt;/a&gt; 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 &lt;a href="https://rigado.zendesk.com/hc/en-us"&gt;contact their support&lt;/a&gt; to check if this is possible on their board as well, or if they have some other solutions to your issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 nrfjprog: ERROR: There is no debugger connected to the PC</title><link>https://devzone.nordicsemi.com/thread/99634?ContentTypeID=1</link><pubDate>Wed, 20 Sep 2017 21:48:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c1a617f4-1902-4851-b9d7-d7491f202ca4</guid><dc:creator>zoltan</dc:creator><description>&lt;p&gt;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.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 nrfjprog: ERROR: There is no debugger connected to the PC</title><link>https://devzone.nordicsemi.com/thread/99633?ContentTypeID=1</link><pubDate>Wed, 20 Sep 2017 13:07:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:edbcdb5c-9361-4acc-9a9b-babb46ec60b9</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;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 &lt;a href="https://www.segger.com/downloads/jlink/"&gt;J-Link drivers&lt;/a&gt;, removing the J-Link device from device manager, and reconnect the device?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 nrfjprog: ERROR: There is no debugger connected to the PC</title><link>https://devzone.nordicsemi.com/thread/99635?ContentTypeID=1</link><pubDate>Tue, 19 Sep 2017 20:20:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9b948ffb-a29b-4a14-92f5-99f07be239ed</guid><dc:creator>zoltan</dc:creator><description>&lt;p&gt;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 &amp;#39;Details&amp;#39; tab might offer you a clue, and i can post them.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 nrfjprog: ERROR: There is no debugger connected to the PC</title><link>https://devzone.nordicsemi.com/thread/99632?ContentTypeID=1</link><pubDate>Tue, 19 Sep 2017 10:59:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e8ecac5-1c90-4a54-8c5c-d8015fe2a943</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;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?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>