<?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 Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/119828/ble-connection-issues-with-nrf52832-multi-device-setup</link><description>We are currently developing a project using the nRF52832 as the microcontroller, Segger Embedded Studio version 5.42a as the IDE, and the nRF5 SDK 17.0.2. We began by creating a concurrent central and peripheral switching example project. Subsequently</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 Mar 2025 10:01:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/119828/ble-connection-issues-with-nrf52832-multi-device-setup" /><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/529007?ContentTypeID=1</link><pubDate>Wed, 26 Mar 2025 10:01:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:98b2df00-b2bd-4144-843f-f7156dd74029</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Siltvm,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Error 0x28 is a bit strange because it&amp;#39;s indicate an issue in the BLE stack timing ( BT_HCI_ERR_INSTANT_PASSED) either on the nRF52 or on the phone. Which phone did you use ?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I would need to see your &lt;a href="https://www.nordicsemi.com/Products/Development-tools/nRF-Sniffer-for-Bluetooth-LE"&gt;sniffer trace&lt;/a&gt; to be to&amp;nbsp;check what happens there.&amp;nbsp;&lt;br /&gt;You can find the guide on how to use the sniffer here:&amp;nbsp;&lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/"&gt;https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/528963?ContentTypeID=1</link><pubDate>Wed, 26 Mar 2025 06:41:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7ce62930-d1a5-4bfe-ad65-58ce42168514</guid><dc:creator>siltvm</dc:creator><description>&lt;p data-sourcepos="3:1-3:143"&gt;When the submaster gateway initially starts advertising, and when Iam initiates a connection from the APK, it sometimes disconnects and shows:&lt;/p&gt;
&lt;p data-sourcepos="5:1-5:56"&gt;Peripheral disconnected. conn_handle: 0x5, reason: 0x28&lt;/p&gt;
&lt;p data-sourcepos="7:1-7:63"&gt;The APK then shows: Connection failed: write descriptor failed.&lt;/p&gt;
&lt;p data-sourcepos="9:1-9:105"&gt;One more thing: I am not using any kind of bonding here. So, what are the possible causes of this issue?&lt;/p&gt;
&lt;p data-sourcepos="9:1-9:105"&gt;This issue happens only sometimes&amp;nbsp; .&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/528351?ContentTypeID=1</link><pubDate>Fri, 21 Mar 2025 09:19:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce7d8f64-f1ec-4a23-b3b2-ef1fa9c0808a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;I don&amp;#39;t see a problem having a connection and then scan and establish another connection. It&amp;#39;s our fundamental operation for multilink application. So, shouldn&amp;#39;t be a problem.&amp;nbsp;&lt;br /&gt;There is no requirement on the timing. Of course two connection can&amp;#39;t be established at the same time (like exactly the same time) they should be established based on when the scanner catch the advertising packet and send the connect request.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/528112?ContentTypeID=1</link><pubDate>Thu, 20 Mar 2025 04:33:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ffec0002-1abb-45b4-a29c-979996caadeb</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/hungbui"&gt;Hung Bui&lt;/a&gt;&amp;nbsp;Okay, I will proceed as you suggested. I also have a question: are there any issues with scanning for or connecting to a central device while maintaining a peripheral connection? Additionally, what are the standard minimum delays required for a response device, sub-gateway, or super-master gateway to perform scanning and connection?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/528018?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2025 13:31:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:13fe09c2-e40a-470a-9d67-fa53c176ad00</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;If you want such feature, you would need to implement that. The submaster gateway shouldn&amp;#39;t connect to the supermaster gateway as the central. This mean when the submaster scan for advertising packet, it would need a way to detect that it only connect to&amp;nbsp;response node, not the supermaster. I think it&amp;#39;s quite straight forward to do so. Just need to scan for either address, or the advertising name/data.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/527972?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2025 09:20:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a01cf83f-c760-4c43-bb5c-63da902aec59</guid><dc:creator>siltvm</dc:creator><description>&lt;p data-sourcepos="3:1-3:96"&gt;Yes, I modified the central, peripheral, and total link counts to meet my project requirements:&lt;/p&gt;
&lt;p&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;/p&gt;
&lt;div class="code-block ng-tns-c2490284893-50 ng-trigger ng-trigger-codeBlockRevealAnimation"&gt;&lt;!----&gt;
&lt;div class="formatted-code-block-internal-container ng-tns-c2490284893-50"&gt;
&lt;div class="animated-opacity ng-tns-c2490284893-50"&gt;
&lt;pre class="ng-tns-c2490284893-50"&gt;&lt;code class="code-container formatted ng-tns-c2490284893-50 no-decoration-radius" data-test-id="code-content" data-sourcepos="5:1-9:31"&gt;NRF_SDH_BLE_PERIPHERAL_LINK_COUNT=1;
NRF_SDH_BLE_CENTRAL_LINK_COUNT=5;
NRF_SDH_BLE_TOTAL_LINK_COUNT=6;
&lt;/code&gt;&lt;/pre&gt;
&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;p&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;/p&gt;
&lt;p data-sourcepos="11:1-11:570"&gt;Our expectation is that the submaster gateway acts as a peripheral when a connection initiation is received from the supermaster gateway. This means the supermaster gateway should be the central (client) to the submaster gateway and all three response devices. However, the log shows that the supermaster gateway connects as a peripheral to the submaster gateway. The log output is from the supermaster gateway. We expected a central connection here, not a peripheral connection.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/527955?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2025 08:31:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ff02da8-9eaf-454f-9bbf-308ccb1e6517</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;The call is inside nrf_ble_gatt.c.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;Could you try capturing a sniffer trace ?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Have you configured the link count to match with your need ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;NRF_SDH_BLE_PERIPHERAL_LINK_COUNT&lt;/p&gt;
&lt;p&gt;NRF_SDH_BLE_CENTRAL_LINK_COUNT&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;NRF_SDH_BLE_TOTAL_LINK_COUNT&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/527927?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2025 03:45:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2bee4585-e809-44de-aed6-e4579df6ea25</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;The given log is from the super master, and I could not find &lt;code&gt;sd_ble_gatts_exchange_mtu_reply()&lt;/code&gt; within my super master code.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/527606?ContentTypeID=1</link><pubDate>Mon, 17 Mar 2025 12:19:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1a662366-efcb-472b-b051-c226910223a2</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;I would suggest to use a &lt;a href="https://academy.nordicsemi.com/courses/bluetooth-low-energy-fundamentals/lessons/lesson-6-bluetooth-le-sniffer/"&gt;sniffer &lt;/a&gt;to&amp;nbsp;try debugging. You can find why the connection is terminated.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;You can also find the termination reason on the device when it&amp;#39;s disconnected.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Please focus on this:&amp;nbsp;&lt;br /&gt;&amp;lt;error&amp;gt; nrf_ble_gatt: sd_ble_gatts_exchange_mtu_reply() returned NRF_ERROR_INVALID_STATE.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Where do you call&amp;nbsp;&lt;span&gt;sd_ble_gatts_exchange_mtu_reply() ?&amp;nbsp;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Was the log from the Super master or the Sub master ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: BLE Connection Issues with nRF52832 Multi-Device Setup</title><link>https://devzone.nordicsemi.com/thread/527583?ContentTypeID=1</link><pubDate>Mon, 17 Mar 2025 11:05:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:01fa9228-82a0-4960-b26b-ec02612510f8</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;When I disconnect power from all response devices, submaster gateways, and supermaster gateways, and then initially power on the supermaster gateway followed by the submaster gateway, I encounter an error. I believe this is causing disconnections. However, if I power on the submaster gateway and the nearest response devices &lt;em&gt;before&lt;/em&gt; powering on the supermaster gateway, the issue does not occur. What could be the reason for this difference?&lt;pre class="ui-code" data-mode="text"&gt;

&amp;lt;info&amp;gt; app: Connected to target F41493782DCD

&amp;lt;info&amp;gt; app: Peripheral connected

&amp;lt;info&amp;gt; app: Connected device MAC: F4:14:93:78:2D:CD

&amp;lt;info&amp;gt; app: Flash memory is empty. Accepting any device.

&amp;lt;error&amp;gt; nrf_ble_gatt: sd_ble_gatts_exchange_mtu_reply() returned NRF_ERROR_INVALID_STATE.

&amp;lt;info&amp;gt; app: Fast advertising.

&amp;lt;info&amp;gt; app: Peripheral disconnected. conn_handle: 0x5, reason: 0x13&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>