<?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>case about nRF52840 ble_app_hrs  Encryption, error: 4102</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/105301/case-about-nrf52840-ble_app_hrs-encryption-error-4102</link><description>Hi, 
 1.How to resolve this error: 
 peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102 
 2.Test DK: PCA10056 3.0.0 
 Test SDK:nRF5 SDK\nRF5_SDK_17.1.0_ddde560\examples\ble_peripheral</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 07 Nov 2023 07:58:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/105301/case-about-nrf52840-ble_app_hrs-encryption-error-4102" /><item><title>RE: case about nRF52840 ble_app_hrs  Encryption, error: 4102</title><link>https://devzone.nordicsemi.com/thread/454349?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2023 07:58:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03f57900-af28-4f22-bd86-30508b74a26f</guid><dc:creator>peter.min</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Simonr,&lt;/p&gt;
&lt;p&gt;1. Thank you for your reply,&lt;/p&gt;
&lt;p&gt;2. The cause of the problem is:&lt;/p&gt;
&lt;p&gt;After power off, the red box part of the TAB is directly connected to the DK board without closing&lt;/p&gt;
&lt;p&gt;3. It can be regarded as an app bug&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1699343790943v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Thank&amp;ensp;you&amp;ensp;for&amp;ensp;all&amp;ensp;your&amp;ensp;assistance.&lt;br /&gt;Kind regards,&lt;br /&gt;Peter.Min&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: case about nRF52840 ble_app_hrs  Encryption, error: 4102</title><link>https://devzone.nordicsemi.com/thread/454134?ContentTypeID=1</link><pubDate>Mon, 06 Nov 2023 09:26:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:60c321b1-4055-421e-84b2-f4f85a7c2806</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Peter&lt;/p&gt;
&lt;p&gt;In the ble_app_hrs example project, you can see that&amp;nbsp;&lt;strong&gt;&lt;/strong&gt;the&amp;nbsp;&lt;strong&gt;delete_bonds();&amp;nbsp;&lt;/strong&gt;function is called in&amp;nbsp;&lt;strong&gt;advertising_start()&amp;nbsp;&amp;nbsp;&lt;/strong&gt;if the erase_bonds bool is set as it is by default. So upon a power reset the device will erase bonding information when it starts advertising which is why you see this issue on your end I think.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: case about nRF52840 ble_app_hrs  Encryption, error: 4102</title><link>https://devzone.nordicsemi.com/thread/454063?ContentTypeID=1</link><pubDate>Sat, 04 Nov 2023 08:52:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f05e755e-2da1-45ae-a448-7daab3a6fe95</guid><dc:creator>peter.min</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;Simonr,&lt;/p&gt;
&lt;p&gt;1. I know the method you provided can solve this problem.&lt;/p&gt;
&lt;p&gt;2. I provide a method for problem recurrence here.&lt;/p&gt;
&lt;p&gt;3. What I want to investigate is why the binding information is dropped here and whether it is a bug in the sdk.&lt;/p&gt;
&lt;p&gt;4. If this is not a bug in the sdk, how can the customer use the pairing and binding information to avoid interrupting the user&amp;#39;s use?&lt;/p&gt;
&lt;p&gt;5.In the past, I have set up the program to allow repairing, but this is not a good experience for interrupted customers&lt;/p&gt;
&lt;p&gt;Thank&amp;ensp;you&amp;ensp;for&amp;ensp;all&amp;ensp;your&amp;ensp;assistance.&lt;br /&gt;Kind regards,&lt;br /&gt;Peter.Min&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: case about nRF52840 ble_app_hrs  Encryption, error: 4102</title><link>https://devzone.nordicsemi.com/thread/453898?ContentTypeID=1</link><pubDate>Fri, 03 Nov 2023 08:39:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4996422-be5e-4cba-8f78-7b53a369abe2</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Error message 0x4102 comes from one of the devices indicating that it already has stored bonding information on the other device, while the other does not. Either the nRF52840 or the phone has stored bonding information on the other device already, and you need to erase bonding information on that device to resolve this. On the nRF side you can do so by doing an &lt;strong&gt;nrfjprog --recover&lt;/strong&gt; or --&lt;strong&gt;eraseall&lt;/strong&gt;, and on the phone side (in the nRF Connect app) you must select the device in the &amp;quot;BONDED&amp;quot; tab and press &amp;quot;Delete bond information&amp;quot; for the device you&amp;#39;re trying to bond to now.&lt;/p&gt;
&lt;p&gt;More details on this error message is discussed in this ticket:&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/55866/peer_manager_handler-connection-security-failed-role-peripheral-conn_handle-0x0-procedure-encryption-error-4102"&gt;peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Encryption, error: 4102&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>