<?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>BLE Connection Issue: Immediate Disconnection Between PC and nRF5340 DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117468/ble-connection-issue-immediate-disconnection-between-pc-and-nrf5340-dk</link><description>Hi, 
 I am encountering an issue with the BLE connection on my nRF5340 DK. When I attempt to connect the device to my PC, the pairing process takes a significant amount of time. Additionally, even after pairing is successful, the connection disconnects</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 20 Dec 2024 14:19:24 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117468/ble-connection-issue-immediate-disconnection-between-pc-and-nrf5340-dk" /><item><title>RE: BLE Connection Issue: Immediate Disconnection Between PC and nRF5340 DK</title><link>https://devzone.nordicsemi.com/thread/515943?ContentTypeID=1</link><pubDate>Fri, 20 Dec 2024 14:19:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bb823256-c4b8-4ee3-93f4-0064290417fa</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I see that there is a non-empty packet sent from the master before the peripheral start advertising again. This is encrypted so I cannot se the content, but I assuem that is a disconnect packet. As the link is encrypted with LESC the sniffer cannot decode it unless you provide the LTK, so you would either have to do that (see &lt;a href="https://devzone.nordicsemi.com/support-private/support/338017/CONFIG_BT_LOG_SNIFFER_INFO"&gt;CONFIG_BT_LOG_SNIFFER_INFO&lt;/a&gt;). Alternatively, you can check and possibly add logging in your application to see what the disconnect reaon is. That said, based on what we know so far it seems that the central (PC in this case) decided to disconnect for some reason.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>