<?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>pc-ble-driver-py NRF52 DK &amp;quot;No Response From Device&amp;quot;</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/78786/pc-ble-driver-py-nrf52-dk-no-response-from-device</link><description>I&amp;#39;m attempting to use pc-ble-driver-py on Windows with an NRF52 DK (PCA10040) and running into the error shown below. Using the Heart Rate Collector example, the COM port is able to be opened but the NRF52 doesn&amp;#39;t seem to respond. 
 
 Here is what I&amp;#39;ve</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 20 Aug 2021 13:51:39 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/78786/pc-ble-driver-py-nrf52-dk-no-response-from-device" /><item><title>RE: pc-ble-driver-py NRF52 DK "No Response From Device"</title><link>https://devzone.nordicsemi.com/thread/325993?ContentTypeID=1</link><pubDate>Fri, 20 Aug 2021 13:51:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0cbdd330-9409-4ddc-a694-b00510097aaa</guid><dc:creator>andyknitt</dc:creator><description>&lt;p&gt;That did the trick, working now, thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: pc-ble-driver-py NRF52 DK "No Response From Device"</title><link>https://devzone.nordicsemi.com/thread/325962?ContentTypeID=1</link><pubDate>Fri, 20 Aug 2021 12:26:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6e2a2096-cbe4-46a7-b9d6-58f8201eab03</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;connectivity_4.1.2_usb_with_s132_5.1.0.hex is for the nRF52840 dongle (which has USB). For the nRF52832, you need to use&amp;nbsp;connectivity_4.1.2_1m_with_s132_5.1.0.hex, where UART is the transport (then the onboard debugger on the DK acts as a USB-UART bridge).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>