<?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>Central + peripheral in nrf52805 &amp;amp; Connection issue in BLE UART example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/82052/central-peripheral-in-nrf52805-connection-issue-in-ble-uart-example</link><description>Dear Nordic Team, 
 
 Is it possible to have dual role (one at a time) on nrf52805? Is any such stack available? 
 I am very new to BLE and i am facing a problem in BLE Uart example where TCU is not connecting if connection is not made within some period</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 25 Nov 2021 09:04:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/82052/central-peripheral-in-nrf52805-connection-issue-in-ble-uart-example" /><item><title>RE: Central + peripheral in nrf52805 &amp; Connection issue in BLE UART example</title><link>https://devzone.nordicsemi.com/thread/340666?ContentTypeID=1</link><pubDate>Thu, 25 Nov 2021 09:04:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3ee35b48-428f-460d-8c43-3d6acd293290</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;The nRF52805 is only qualified with the S112 and S113 softdevice stacks:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52805/COMP/nrf52805/nrf52805_ble_qdid.html"&gt;https://infocenter.nordicsemi.com/topic/comp_matrix_nrf52805/COMP/nrf52805/nrf52805_ble_qdid.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Neither of these softdevice stacks support central mode:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/struct_nrf52/struct/s112.html"&gt;https://infocenter.nordicsemi.com/topic/struct_nrf52/struct/s112.html&lt;br /&gt;&lt;/a&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/struct_nrf52/struct/s113.html"&gt;https://infocenter.nordicsemi.com/topic/struct_nrf52/struct/s113.html&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The softdevice will provide events to the application for instance on disconnect event and timeout:&lt;br /&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s112.api.v7.3.0/group___b_l_e___g_a_p___a_d_v___m_s_c.html"&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s112.api.v7.3.0/group___b_l_e___g_a_p___a_d_v___m_s_c.html&lt;br /&gt;https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s112.api.v7.3.0/group___b_l_e___g_a_p___c_o_n_n___m_s_c.html&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;How you handle these events are entirely up to you, but you can for instance use them to start advertisment again. Or start an app_timer that can start advertisment again in future.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>