<?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>Zephyr: BLE connection refused</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91898/zephyr-ble-connection-refused</link><description>Hi, 
 I am having a connectivity problem with a central Bluetooth device (nrf52832) that has to be connected to a peripheral (nrf52840), previously this connectivity worked correctly with zephyr 2.5.0 but now that I wanted to update to zephyr 2.7.0 it</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Sep 2022 11:43:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91898/zephyr-ble-connection-refused" /><item><title>RE: Zephyr: BLE connection refused</title><link>https://devzone.nordicsemi.com/thread/385943?ContentTypeID=1</link><pubDate>Tue, 13 Sep 2022 11:43:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c22bb3ad-39b5-4507-a58b-96232a9dfca6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Apica,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Are you using Nordic&amp;#39;s softdevice controller or you are using Zephyr controller ?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You may&amp;nbsp;need to create git issue if it&amp;#39;s not related to Nordic.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Have you tried to test with the default Bluetooth example in v2.7.0 ?&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Error 2 means&amp;nbsp;BT_HCI_ERR_UNKNOWN_CONN_ID and according to the documentation of the call back :&amp;nbsp;&lt;/p&gt;
&lt;p&gt;- @ref BT_HCI_ERR_UNKNOWN_CONN_ID Creating the connection started by&lt;br /&gt; * @ref bt_conn_le_create was canceled either by the user through&lt;br /&gt; * @ref bt_conn_disconnect or by the timeout in the host through&lt;br /&gt; * @ref bt_conn_le_create_param timeout parameter, which defaults to&lt;br /&gt; * @kconfig{CONFIG_BT_CREATE_CONN_TIMEOUT} seconds.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Could you check&amp;nbsp;&lt;span&gt;CONFIG_BT_CREATE_CONN_TIMEOUT configuration in your project ? By default it&amp;#39;s 3 seconds.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I would suggest to capture &lt;a href="https://www.nordicsemi.com/Products/Development-tools/nrf-sniffer-for-bluetooth-le"&gt;a sniffer trace&lt;/a&gt; to get more information about the connect attempts.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>