<?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 Peer Manager dependency on BLE Connection State Library?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/37356/ble-peer-manager-dependency-on-ble-connection-state-library</link><description>(nRF51 SDK v12.3.0) 
 The function gcm_init() in gatt_cache_manager.c (BLE Peer Manager Lib) calls ble_conn_state_user_flag_acquire() part of the BLE Connection State Lib in order to use User Flags. 
 If BLE is disabled and enabled again (one second time</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 15 Aug 2018 11:52:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/37356/ble-peer-manager-dependency-on-ble-connection-state-library" /><item><title>RE: BLE Peer Manager dependency on BLE Connection State Library?</title><link>https://devzone.nordicsemi.com/thread/144314?ContentTypeID=1</link><pubDate>Wed, 15 Aug 2018 11:52:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:366c3128-8832-4f89-803a-b82d2c5e671b</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The problem is that the user flags are not tied to a connection in a strong way. The user flags are acquired without any connection handle, so it is hard to say when you want to mark them as released. In your use case, where you want to re-initialize the BLE, it would have helped if we could have marked the user flags as free with less overhead than to call ble_conn_state_init().&amp;nbsp;&lt;/p&gt;
&lt;p&gt;But with the current design, your workaround seems safest as it resets the whole state machine.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>