<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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>Connect with Autoconnect on Central</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/88200/connect-with-autoconnect-on-central</link><description>Hello, 
 On a BLE Central, how can I enable connect with auto connect to a peripheral with previously saved bonding information. 
 Once paired and bonded, I can recall bonding address information on boot. I use this address to configure the scanning filters</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Wed, 25 May 2022 16:03:41 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/88200/connect-with-autoconnect-on-central" /><item><title>RE: Connect with Autoconnect on Central</title><link>https://test-devzone.nordicsemi.com/thread/369603?ContentTypeID=1</link><pubDate>Wed, 25 May 2022 16:03:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:026d82d1-a65a-4661-be41-4ef520811280</guid><dc:creator>user102664</dc:creator><description>&lt;p&gt;I am still not able to get extended advertising to work but I was able to get it to work using bt_le_filter_accept_list_add on both the central and peripheral bond addresses to filter connectable addresses.&lt;/p&gt;
&lt;p&gt;On the central I was then able to use bt_conn_le_create_auto to create an automatic reconnect connection.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connect with Autoconnect on Central</title><link>https://test-devzone.nordicsemi.com/thread/369504?ContentTypeID=1</link><pubDate>Wed, 25 May 2022 11:26:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:889bb0b9-4cfd-4759-925f-0f91be1c877e</guid><dc:creator>user77782</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I would try to use&amp;nbsp;&lt;span&gt;bt_le_ext_adv_start. Take a look at the example in&lt;a href="https://test-devzone.nordicsemi.com/f/nordic-q-a/84756/directed-advertising-not-seen-by-the-addressed-device/353816#353816"&gt; this post&lt;/a&gt;.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;-Amanda&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connect with Autoconnect on Central</title><link>https://test-devzone.nordicsemi.com/thread/369357?ContentTypeID=1</link><pubDate>Tue, 24 May 2022 16:02:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b5ebf94-6f4d-462d-856e-7b5c511b7237</guid><dc:creator>user102664</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve added the config option&amp;nbsp;CONFIG_BT_EXT_ADV to my peripheral prj.conf &lt;span&gt;added CONFIG_BT_CTLR_ADV_EXT=y to child_image/hci_rpmsg.conf&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I have also tried adding BT_LE_ADV_OPT_EXT_ADV to the options which caused an -&lt;span&gt;EINVAL error which was strange since when the config option is enabled, bt_le_adv_start_ext is always called not bt_le_adv_start_legacy.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I traced this error back to bt_le_adv_start_ext calling&amp;nbsp;valid_adv_param instead of&amp;nbsp;valid_adv_ext_param which seems like a bug. Therefore I also applied the following patch which fixes the -EINVAL error.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;diff --git a/subsys/bluetooth/host/adv.c b/subsys/bluetooth/host/adv.c
index ecd0de3371..df35e5d6f6 100644
--- a/subsys/bluetooth/host/adv.c
+++ b/subsys/bluetooth/host/adv.c
@@ -1223,7 +1223,7 @@ int bt_le_adv_start_ext(struct bt_le_ext_adv *adv,
 		return -EAGAIN;
 	}
 
-	if (!valid_adv_param(param)) {
+	if (!valid_adv_ext_param(param)) {
 		return -EINVAL;
 	}
 &lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;When testing this configuration with the mobile app, I cannot find the device listed. Only when I remove&amp;nbsp;&lt;span&gt;BT_LE_ADV_OPT_EXT_ADV&amp;nbsp;and use the following as a adv does it show up during scan.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;adv_param = *BT_LE_ADV_CONN;
adv_param.options |= BT_LE_ADV_OPT_ONE_TIME;

err = bt_le_adv_start(adv_param,
		      ad, ARRAY_SIZE(ad),
		      sd, ARRAY_SIZE(sd));&lt;/pre&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;However now it seem the issue is when connecting, a bus fault is generated in the kernel work.c flag_clear() function. This also occurs without the patch.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Connect with Autoconnect on Central</title><link>https://test-devzone.nordicsemi.com/thread/369295?ContentTypeID=1</link><pubDate>Tue, 24 May 2022 13:19:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3f064224-a79f-459f-97f1-734375838857</guid><dc:creator>user77782</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
[quote user=""]When attempting to do the same on an embedded central scanning for the address and connecting to a match I cannot connect to a directed advertisement. However, I can get the central scanning in address filtered mode to connect to a peripheral advertising in regular mode that uses the following advertisement:[/quote]
&lt;p&gt;&lt;a href="https://test-devzone.nordicsemi.com/f/nordic-q-a/84756/directed-advertising-not-seen-by-the-addressed-device/354293#354293"&gt;This post&lt;/a&gt; might help.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Amanda&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>