<?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>The ble central device cannot connect some special ble addr</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/90928/the-ble-central-device-cannot-connect-some-special-ble-addr</link><description>Hi, 
 I&amp;#39;m using one board with nrf52832 and sdk 15.3.0,and alter the ble_app_mult_uart_c example as ble center ，there is another ble device(ble addr 4C :42 :44 :49 :43 :4A) as the slave device,the mobile phone can connect it.I try to use the central to</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 12 Aug 2022 11:50:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/90928/the-ble-central-device-cannot-connect-some-special-ble-addr" /><item><title>RE: The ble central device cannot connect some special ble addr</title><link>https://devzone.nordicsemi.com/thread/381347?ContentTypeID=1</link><pubDate>Fri, 12 Aug 2022 11:50:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7820318-0f67-4bdd-bf3a-4cff29a13c0e</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Do the peer device use a public Bluetooth address? The Bluetooth scan module in the SDK had a bug where some&amp;nbsp;public addresses are ignored, as discussed in &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/61512/issues-with-public-address-type-when-applying-scan-filter"&gt;this thread&lt;/a&gt;. This issue is fixed in 17.1.0, so I suggest you refer to the scan module from there (nrf_ble_scan.c). The key point is that the address type was extracted from the 2 most significant bits, but this is not valid for public addresses, so the fix is to ignore the address type.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>