<?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>Bonding &amp;amp; Connection Error</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34728/bonding-connection-error</link><description>Currently, we are testing Bonding &amp;amp; Connect. 
 Please see the attached log below. 
 If Click 「Bond」 on Android App (nRF Connect), disconnection occurs after &amp;quot;PM_EVT_CONN_SEC_SUCCEEDED&amp;quot; as shown below, and fast advertisement with whiterliset. This is similar</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 04 Jun 2018 11:56:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34728/bonding-connection-error" /><item><title>RE: Bonding &amp; Connection Error</title><link>https://devzone.nordicsemi.com/thread/134540?ContentTypeID=1</link><pubDate>Mon, 04 Jun 2018 11:56:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9d8d1147-6df9-490a-a3ce-404550bab5d2</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Unfortunately, the generic &amp;ldquo;remote user terminated connection&amp;rdquo; code does not give much information about why the mobile&amp;nbsp;decided to disconnect.&lt;/p&gt;
&lt;p&gt;A sniffer trace might give us some more information about what is going on. If you have an extra nRF5 DK or dongle, you can use &lt;a href="https://www.nordicsemi.com/eng/Products/Bluetooth-low-energy/nRF-Sniffer"&gt;nRF Sniffer&lt;/a&gt; to capture a sniffer log. I recommend using the 2.0.0-1.beta version.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You should also check if you get any information in the nRFConnect log on the mobile side.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bonding &amp; Connection Error</title><link>https://devzone.nordicsemi.com/thread/133782?ContentTypeID=1</link><pubDate>Tue, 29 May 2018 09:53:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2336aa2d-fdc1-4238-bcdf-8cc337f6f9b1</guid><dc:creator>cw-park</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for your reply.&lt;/p&gt;
&lt;p&gt;1) I know the meaning of BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION.&lt;br /&gt;We know that this BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION occurs immediately after the Bonding happens in the other examples as well.&lt;br /&gt;So this part looks normal, but what I want to know is why this sequence happens.&lt;br /&gt;I hope the intention of my question is well communicated.&lt;/p&gt;
&lt;p&gt;2) Although the connection terminated due to MIC failure seems to be a problem,&lt;br /&gt;We are not touching the encryption keys because we use the bonding parameter as follows (we know that the encryption keys are mutually exchanged information when they are bonded).&lt;br /&gt;It is also irrelevant to Bonding Erase.&lt;br /&gt;This is because nrfjprog writes all new flash writes.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;#define SEC_PARAM_BOND 1 // Perform bonding.&lt;br /&gt;#define SEC_PARAM_MITM 0 // Man In The Middle protection not required.&lt;br /&gt;#define SEC_PARAM_LESC 0 // Enable LE Secure Connection pairing.&lt;br /&gt;#define SEC_PARAM_KEYPRESS 0 // Enable generation of keypress notifications.&lt;br /&gt;#define SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_NONE // No I / O capabilities.&lt;br /&gt;#define SEC_PARAM_OOB 0 // Out Of Band data not available.&lt;br /&gt;#define SEC_PARAM_MIN_KEY_SIZE 7 // Minimum encryption key size.&lt;br /&gt;#define SEC_PARAM_MAX_KEY_SIZE 16&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Please let me know if you have any other guesses.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bonding &amp; Connection Error</title><link>https://devzone.nordicsemi.com/thread/133778?ContentTypeID=1</link><pubDate>Tue, 29 May 2018 09:35:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b44bca5b-eaeb-4365-80a5-65a2a2334f68</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;You can find the Bluetooth status code list here.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;0x13 is &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.0.0/group___b_l_e___h_c_i___s_t_a_t_u_s___c_o_d_e_s.html#gad4caeb4bcc901a4f1b00068c498a090c"&gt;BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION&lt;/a&gt;&lt;/span&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;0x3D is &lt;span&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.0.0/group___b_l_e___h_c_i___s_t_a_t_u_s___c_o_d_e_s.html#gafe4d349d8ff3edc71dad285d867c4d14"&gt;BLE_HCI_CONN_TERMINATED_DUE_TO_MIC_FAILURE&lt;/a&gt;&lt;/span&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;strong&gt;1)&lt;/strong&gt;&amp;nbsp;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.0.0/group___b_l_e___h_c_i___s_t_a_t_u_s___c_o_d_e_s.html#gad4caeb4bcc901a4f1b00068c498a090c"&gt;BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION&lt;/a&gt;&amp;nbsp;means that the phone has disconnected the link.&amp;nbsp;If you take a look at the log on the phone side (swipe from left to right in nRFConnect)&amp;nbsp;perhaps you could fine some more information there about why the phone disconnected.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;strong&gt;2)&lt;/strong&gt; You could get &lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v6.0.0/group___b_l_e___h_c_i___s_t_a_t_u_s___c_o_d_e_s.html?cp=2_3_1_1_0_2_0_0_3#gafe4d349d8ff3edc71dad285d867c4d14"&gt;BLE_HCI_CONN_TERMINATED_DUE_TO_MIC_FAILURE&lt;/a&gt; (Connection Terminated due to MIC Failure) if you&amp;nbsp;use incorrect encryption keys when you try to encrypt the link with a bonded device. Try to delete the bond information on both the phone and the nRF52, and try to bond again.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bonding &amp; Connection Error</title><link>https://devzone.nordicsemi.com/thread/133554?ContentTypeID=1</link><pubDate>Mon, 28 May 2018 02:19:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:665bd072-aba3-4aed-bf7b-14f2371af6b1</guid><dc:creator>cw-park</dc:creator><description>&lt;p&gt;Is there anyone to answer?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>