<?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>lost communication with nRF52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46492/lost-communication-with-nrf52832</link><description>Hi, 
 I am a newbie and just strted first evaluation with nRF52832 board. I am using SEGGER IDE. 
 The example i am using is: C:\nordic_semi\nRF5_SDK_15.3.0_59ac345\examples\ble_peripheral\ble_app_hrs\pca10040\s132\ses (SoftDevice 132). 
 After building</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 May 2019 08:54:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46492/lost-communication-with-nrf52832" /><item><title>RE: lost communication with nRF52832</title><link>https://devzone.nordicsemi.com/thread/188755?ContentTypeID=1</link><pubDate>Thu, 23 May 2019 08:54:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30a43499-23f0-4acc-a224-a06eee180e53</guid><dc:creator>Gil</dc:creator><description>&lt;p&gt;not relevant anymore - please close issue&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: lost communication with nRF52832</title><link>https://devzone.nordicsemi.com/thread/183193?ContentTypeID=1</link><pubDate>Tue, 23 Apr 2019 15:09:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ed442a6-3b84-4c40-bc79-67429bee6a12</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Gil,&lt;/p&gt;
&lt;p&gt;I am not sure what happened. Maybe a device nearby connects to your HRM device? A phone, or someone else running the ble_app_hrs_c example on another DK nearby. Or if a device (e.g. a phone) connected with your ble_app_hrs, and bonded with it, this bonding information is stored on your device, and it will start advertising with a whitelist. This is basically just a flag that indicates that the DK will only connect to devices in this list. Typically, BLE devices, such as mobile phones will ignore devices with this flag if they know they are not bonded them selves, because it knows it won&amp;#39;t be able to connect.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you press button 4 on your DK while power cycling the device, it should delete the bonding information, and it should advertise without the whitelist flag. You will probably see it from other devices at that point.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Alternatively, you can completely erase the chip, using e.g. &amp;quot;nrfjprog --eraseall&amp;quot; if you have the Nordic &lt;a href="https://www.nordicsemi.com/?sc_itemid=%7B56868165-9553-444D-AA57-15BDE1BF6B49%7D" rel="noopener noreferrer" target="_blank"&gt;Command Line Tools&lt;/a&gt; installed, and then program the device again with the softdevice and the example.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>