<?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>Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/116023/guidance-on-implementing-concurrent-central-and-peripheral-roles-for-nrf52832-using-nrf5-sdk-17-0-2</link><description>Hi, 
 We are currently planning to start a project using the nRF52832 as our controller, SEGGER Embedded Studio version 5.42a as the IDE, and nRF5 SDK version 17.0.2 as our SDK. Our requirement is to have an nRF52832 device that behaves as both a central</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 26 Nov 2024 12:29:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/116023/guidance-on-implementing-concurrent-central-and-peripheral-roles-for-nrf52832-using-nrf5-sdk-17-0-2" /><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/512098?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 12:29:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d1211d2c-2fb3-4800-947e-fc061432f63b</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Siltvm,&amp;nbsp;&lt;br /&gt;Thanks for letting me know. I&amp;#39;m happy to help. From what I read everything is working as expected, right ?&amp;nbsp;&lt;br /&gt;If it&amp;#39;s the case you can either close the ticket or just leave it at the current state.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/512076?ContentTypeID=1</link><pubDate>Tue, 26 Nov 2024 10:51:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f055df69-9b08-436c-94ef-1176075eb613</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;We added the NUS_C and NUS parts from the ble_app_uart_c and ble_app_uart examples to the ble_app_hrs_rscs example project and made some necessary corrections in the event handlers of the central and peripheral side handlings. Now, we are able to send data to the APK through the gateway and vice versa. We have implemented bidirectional data transfer through the gateway. We are greatly appreciative of your valuable suggestions&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/510744?ContentTypeID=1</link><pubDate>Fri, 15 Nov 2024 14:59:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d53ef368-3f06-4d0d-8ba0-308dcb8314c3</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Siltvm,&amp;nbsp;&lt;br /&gt;Yes if you add more service/characteristic to the table, it will require larger stack inside the softdevice. Please adjust the stack accordingly.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/510605?ContentTypeID=1</link><pubDate>Fri, 15 Nov 2024 07:13:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f55dea0-f5d7-4f0d-b709-997ef260037e</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;&amp;nbsp;hi ,&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/members/hungbui"&gt;Hung Bui&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Hope you are doing well.&lt;/p&gt;
&lt;p&gt;We previously informed you that we started integrating the Nordic UART Service into the &lt;code&gt;ble_app_hrs_rscs&lt;/code&gt; example project. We added the Nordic UART Service central and peripheral code regions from the &lt;code&gt;ble_app_uart_c&lt;/code&gt; and &lt;code&gt;ble_app_uart&lt;/code&gt; BLE central and peripheral example projects. We have not yet tested the modified code.&lt;/p&gt;
&lt;p&gt;After the integration, we flashed the modified &lt;code&gt;ble_app_hrs_rscs&lt;/code&gt; example project onto the PCA10040 nRF52832 development board. After flashing, we observed a &amp;quot;no memory&amp;quot; error. I will share the log output.&lt;/p&gt;
&lt;p&gt;My question is: is a RAM address change necessary when adding the Nordic UART central part? I had already changed the RAM address when adding the Nordic UART peripheral part.&lt;pre class="ui-code" data-mode="text"&gt;
12:27:11.592 -&amp;gt; &amp;lt;warning&amp;gt; nrf_sdh_ble: Insufficient RAM allocated for the SoftDevice.

12:27:11.592 -&amp;gt; &amp;lt;warning&amp;gt; nrf_sdh_ble: Change the RAM start location from 0x20002DB0 to 0x20004718.

12:27:11.592 -&amp;gt; &amp;lt;warning&amp;gt; nrf_sdh_ble: Maximum RAM size for application is 0xB8E8.

12:27:11.639 -&amp;gt; &amp;lt;error&amp;gt; nrf_sdh_ble: sd_ble_enable() returned NRF_ERROR_NO_MEM.

12:27:11.639 -&amp;gt; &amp;lt;error&amp;gt; app: Fatal error

12:27:11.639 -&amp;gt; &amp;lt;warning&amp;gt; app: System reset

12:27:11.873 -&amp;gt; &amp;lt;info&amp;gt; app_timer: RTC: initialized.&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/509811?ContentTypeID=1</link><pubDate>Mon, 11 Nov 2024 08:26:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2ed76e37-6022-4892-97f7-b4d5c3fe48b7</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;I&amp;#39;m glad that you find the fix. It&amp;#39;s the correct fix.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/509591?ContentTypeID=1</link><pubDate>Fri, 08 Nov 2024 06:40:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c898c88-2425-4f04-8a5f-5aac0e23d3a8</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/hungbui"&gt;Hung Bui&lt;/a&gt;&amp;nbsp;, changing the ram address from&amp;nbsp;&amp;nbsp;0x20002DA0 to&amp;nbsp;&amp;nbsp;0x20002DB0 in section placement macros solved the issue&amp;nbsp;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/509589?ContentTypeID=1</link><pubDate>Fri, 08 Nov 2024 05:46:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d86d5686-6b82-48da-91c7-da17851aad90</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/members/hungbui"&gt;Hung Bui&lt;/a&gt;&amp;nbsp;,&lt;/p&gt;
&lt;p&gt;We informed you that we are planning to add the Nordic UART Service (NUS) to the &lt;code&gt;ble_app_hrs_rscs&lt;/code&gt; example project .&lt;/p&gt;
&lt;p data-sourcepos="7:1-7:43"&gt;So far, we have made the following changes:&lt;/p&gt;
&lt;ol data-sourcepos="9:1-55:0"&gt;
&lt;li data-sourcepos="9:1-11:0"&gt;
&lt;p data-sourcepos="9:4-9:33"&gt;&lt;strong&gt;Included Necessary Header:&lt;/strong&gt;&lt;/p&gt;
&lt;ul data-sourcepos="10:4-11:0"&gt;
&lt;li data-sourcepos="10:4-11:0"&gt;Added &lt;code&gt;#include &amp;quot;ble_nus.h&amp;quot;&lt;/code&gt;&amp;nbsp; header files.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li data-sourcepos="12:1-15:0"&gt;
&lt;p data-sourcepos="12:4-12:27"&gt;&lt;strong&gt;Added NUS Component:&lt;/strong&gt;&lt;/p&gt;
&lt;ul data-sourcepos="13:4-15:0"&gt;
&lt;li data-sourcepos="13:4-13:46"&gt;Included &lt;code&gt;ble_nus.c&lt;/code&gt; and its header file.&lt;/li&gt;
&lt;li data-sourcepos="14:4-15:0"&gt;Included &lt;code&gt;ble_link_ctx_manager.c&lt;/code&gt;&lt;code&gt;&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;ul&gt;
&lt;li data-sourcepos="16:1-18:0"&gt;
&lt;p data-sourcepos="16:4-16:34"&gt;&lt;strong&gt;Modified SDK Configuration:&lt;/strong&gt;&lt;/p&gt;
&lt;ul data-sourcepos="17:4-18:0"&gt;
&lt;li data-sourcepos="17:4-18:0"&gt;Set &lt;code&gt;BLE_NUS_ENABLED&lt;/code&gt; to 1 and &lt;code&gt;NRF_SDH_BLE_VS_UUID_COUNT&lt;/code&gt; to 1 in &lt;code&gt;sdk_config.h&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p data-sourcepos="19:4-19:29"&gt;&lt;strong&gt;Declared NUS Instance:&lt;/strong&gt;&lt;/p&gt;
&lt;ul data-sourcepos="20:4-24:0"&gt;
&lt;li data-sourcepos="20:4-24:0"&gt;Declared an NUS instance at the top of &lt;code&gt;main.c&lt;/code&gt;: &lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;
&lt;div class="code-block ng-tns-c3503016650-29 ng-trigger ng-trigger-codeBlockRevealAnimation"&gt;
&lt;div class="code-block-decoration header gmat-subtitle-1 ng-tns-c3503016650-29 ng-star-inserted"&gt;&lt;span class="ng-tns-c3503016650-29"&gt;&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;!--mce:protected %3C%21----%3E--&gt;
&lt;div class="code-block-internal-container ng-tns-c3503016650-29"&gt;
&lt;div class="animated-opacity ng-tns-c3503016650-29"&gt;
&lt;pre class="ng-tns-c3503016650-29"&gt;&lt;code class="code-container ng-tns-c3503016650-29" data-test-id="code-content" data-sourcepos="21:6-23:54"&gt;BLE_NUS_DEF(m_nus, NRF_SDH_BLE_TOTAL_LINK_COUNT);&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p data-sourcepos="25:4-25:23"&gt;&lt;strong&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Initialized NUS:&lt;/strong&gt;&lt;/p&gt;
&lt;ul data-sourcepos="26:4-35:0"&gt;
&lt;li data-sourcepos="26:4-35:0"&gt;Initialized NUS in the &lt;code&gt;service_init()&lt;/code&gt; function: &lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;&lt;!--mce:protected %3C%21----%3E--&gt;
&lt;div class="code-block ng-tns-c3503016650-30 ng-trigger ng-trigger-codeBlockRevealAnimation"&gt;
&lt;div class="code-block-decoration header gmat-subtitle-1 ng-tns-c3503016650-30 ng-star-inserted"&gt;&lt;span class="ng-tns-c3503016650-30"&gt;&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;!--mce:protected %3C%21----%3E--&gt;
&lt;div class="code-block-internal-container ng-tns-c3503016650-30"&gt;
&lt;div class="animated-opacity ng-tns-c3503016650-30"&gt;
&lt;pre class="ng-tns-c3503016650-30"&gt;&lt;code class="code-container ng-tns-c3503016650-30" data-test-id="code-content" data-sourcepos="27:6-34:31"&gt;&lt;span class="hljs-keyword"&gt;ble_nus_init_t&lt;/span&gt; nus_init;
&lt;span class="hljs-comment"&gt;// Initialize NUS.&lt;/span&gt;
&lt;span class="hljs-built_in"&gt;memset&lt;/span&gt;(&amp;amp;nus_init, &lt;span class="hljs-number"&gt;0&lt;/span&gt;, &lt;span class="hljs-keyword"&gt;sizeof&lt;/span&gt;(nus_init));
nus_init.data_handler = nus_data_handler;
err_code = ble_nus_init(&amp;amp;m_nus, &amp;amp;nus_init);
APP_ERROR_CHECK(err_code);&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p data-sourcepos="36:4-36:33"&gt;&lt;strong&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Modified NUS Data Handler:&lt;/strong&gt;&lt;/p&gt;
&lt;ul data-sourcepos="37:4-55:0"&gt;
&lt;li data-sourcepos="37:4-55:0"&gt;Modified the &lt;code&gt;nus_data_handler&lt;/code&gt; function to: &lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;&lt;!----&gt;
&lt;div class="code-block ng-tns-c3503016650-31 ng-trigger ng-trigger-codeBlockRevealAnimation"&gt;
&lt;div class="code-block-decoration header gmat-subtitle-1 ng-tns-c3503016650-31 ng-star-inserted"&gt;&lt;span class="ng-tns-c3503016650-31"&gt;&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;!----&gt;
&lt;div class="code-block-internal-container ng-tns-c3503016650-31"&gt;
&lt;div class="animated-opacity ng-tns-c3503016650-31"&gt;
&lt;pre class="ng-tns-c3503016650-31"&gt;&lt;code class="code-container ng-tns-c3503016650-31" data-test-id="code-content" data-sourcepos="38:6-54:6"&gt;&lt;span class="hljs-function"&gt;&lt;span class="hljs-keyword"&gt;static&lt;/span&gt; &lt;span class="hljs-keyword"&gt;void&lt;/span&gt; &lt;span class="hljs-title"&gt;nus_data_handler&lt;/span&gt;&lt;span class="hljs-params"&gt;(&lt;span class="hljs-keyword"&gt;ble_nus_evt_t&lt;/span&gt; * p_evt)&lt;/span&gt;
&lt;/span&gt;{
    &lt;span class="hljs-built_in"&gt;memset&lt;/span&gt;(Bledatabuff, &lt;span class="hljs-number"&gt;0&lt;/span&gt;, &lt;span class="hljs-keyword"&gt;sizeof&lt;/span&gt;(Bledatabuff));
    &lt;span class="hljs-comment"&gt;// Write the code for NUS data handling.&lt;/span&gt;
    &lt;span class="hljs-keyword"&gt;if&lt;/span&gt; (p_evt-&amp;gt;type == BLE_NUS_EVT_RX_DATA)
    {
        NRF_LOG_DEBUG(&lt;span class="hljs-string"&gt;&amp;quot;Received data from BLE NUS.&amp;quot;&lt;/span&gt;);
        &lt;span class="hljs-comment"&gt;// Copy received data to Bledatabuff array&lt;/span&gt;
        &lt;span class="hljs-keyword"&gt;for&lt;/span&gt; (&lt;span class="hljs-keyword"&gt;uint32_t&lt;/span&gt; i = &lt;span class="hljs-number"&gt;0&lt;/span&gt;; i &amp;lt; p_evt-&amp;gt;params.rx_data.length; i++)
        {
            Bledatabuff[i] = p_evt-&amp;gt;params.rx_data.p_data[i];
        }
    }
    NRF_LOG_INFO(&lt;span class="hljs-string"&gt;&amp;quot;Received BLE data: %s\n&amp;quot;&lt;/span&gt;, Bledatabuff);
}&lt;/code&gt;&lt;/pre&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Before proceeding with further NUS integration, we would like to verify if the current initialization is correct. We are currently encountering a &amp;quot;no memory error&amp;quot; in the &lt;code&gt;nrf_sdh_ble()&lt;/code&gt; function.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;lt;info&amp;gt; app_timer: RTC: initialized.&amp;lt;info&amp;gt; app: nrf_sdh_enable_request : 0&amp;lt;info&amp;gt; app: nrf_sdh_ble_default_cfg_set : 0&amp;lt;warning&amp;gt; nrf_sdh_ble: Insufficient RAM allocated for the SoftDevice.&amp;lt;warning&amp;gt; nrf_sdh_ble: Change the RAM start location from 0x20002DA0 to 0x20002DB0.&amp;lt;warning&amp;gt; nrf_sdh_ble: Maximum RAM size for application is 0xD250.&amp;lt;error&amp;gt; nrf_sdh_ble: sd_ble_enable() returned NRF_ERROR_NO_MEM.&amp;lt;error&amp;gt; app: Fatal error&amp;lt;warning&amp;gt; app: System reset&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Do I need to modify the RAM start and end addresses? If so, what should the new addresses be?&lt;/p&gt;
&lt;p&gt;Your advice is really helpful&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/509202?ContentTypeID=1</link><pubDate>Wed, 06 Nov 2024 08:39:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d3f9405a-dd39-4145-9f66-4e7ee5a3ae81</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It&amp;#39;s most likely&amp;nbsp; because that one of the sides (phone or&amp;nbsp;&lt;code&gt;ble_app_hrs_rscs_relay&lt;/code&gt;&lt;span&gt;&amp;nbsp;board) has the bond information from previous&amp;nbsp;pairing between them when the other doesn&amp;#39;t. Please try to erase the full chip on the nRF52 board (nrfjprog --eraseall) and try to find if the device is in the bonded list on Bluetooth on the phone, click Forget this device.&amp;nbsp;&lt;br /&gt;You can take a look at this ticket:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/55866/peer_manager_handler-connection-security-failed-role-peripheral-conn_handle-0x0-procedure-encryption-error-4102"&gt;devzone.nordicsemi.com/.../peer_manager_handler-connection-security-failed-role-peripheral-conn_handle-0x0-procedure-encryption-error-4102&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/509188?ContentTypeID=1</link><pubDate>Wed, 06 Nov 2024 05:57:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c8648b8-9300-45d5-b870-74f39ed3ac80</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/hungbui"&gt;Hung Bui&lt;/a&gt;&amp;nbsp;,&lt;/p&gt;
&lt;p&gt;We have decided to add the Nordic UART service to the &lt;code&gt;ble_app_hrs_rscs_relay&lt;/code&gt; example project. Before doing that, I am testing the code based on the link you provided.&lt;/p&gt;
&lt;p&gt;I flashed the &lt;code&gt;ble_app_hrs_rscs_relay&lt;/code&gt; example project onto one development board and the &lt;code&gt;ble_app_rscs&lt;/code&gt; example project from the BLE peripheral directory onto another development board. After flashing, the &lt;code&gt;ble_app_hrs_rscs_relay&lt;/code&gt;-flashed board successfully connected with the &lt;code&gt;ble_app_rscs&lt;/code&gt;-flashed board, and it sent speed data to the &lt;code&gt;ble_app_hrs_rscs_relay&lt;/code&gt; board, which I could see in the logs. However, when I try to connect to the &lt;code&gt;ble_app_hrs_rscs_relay&lt;/code&gt;-flashed board using the nRF Connect APK, I am unable to connect. The logs show a warning.&lt;/p&gt;
&lt;p&gt;What could be the possible reason for this issue?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;development board&amp;nbsp; :-&amp;nbsp; nrf52832 pca10040&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;
&amp;lt;info&amp;gt; app: Peripheral connected

&amp;lt;info&amp;gt; app: Speed      = 896

&amp;lt;info&amp;gt; peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x2, procedure: Encryption, error: 4102

&amp;lt;warning&amp;gt; peer_manager_handler: Disconnecting conn_handle 2.

&amp;lt;info&amp;gt; app: Fast advertising.

&amp;lt;info&amp;gt; app: Peripheral disconnected. conn_handle: 0x2, reason: 0x16&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/509104?ContentTypeID=1</link><pubDate>Tue, 05 Nov 2024 12:21:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c7829aba-fd20-4b1f-ab05-4bcef2f0366d</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;My suggestion is to get familiar with the uart sample code.&amp;nbsp;After you get to know how to include the UART service in the code, then you should be able to modify the ble_app_hrs_rxs_relay to remove the HRS service and add NUS service instead.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Please be aware that the nRF5 SDK is deprecated and it&amp;#39;s suggested to use nRF Connect SDK instead. You can find central&amp;amp;peripheral sample in the nRF Connect SDK as well as the NUS service in nRF Connect SDK.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/509098?ContentTypeID=1</link><pubDate>Tue, 05 Nov 2024 11:48:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8479c789-b60e-4609-be6f-2649296048fa</guid><dc:creator>siltvm</dc:creator><description>&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/members/hungbui"&gt;Hung Bui&lt;/a&gt;&amp;nbsp;, in the given example code how can i add nordic uart service , and scan and connect nordic uart service based devices . is there any tutorial for that ?&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Guidance on Implementing Concurrent Central and Peripheral Roles for nRF52832 Using nRF5 SDK 17.0.2</title><link>https://devzone.nordicsemi.com/thread/508919?ContentTypeID=1</link><pubDate>Mon, 04 Nov 2024 10:27:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e278e302-308a-42be-a2fa-a4a51e298acc</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;Please take a look at&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/ble_sdk_app_rscs_relay.html"&gt;\examples\ble_central_and_peripheral\experimental\ble_app_hrs_rscs_relay&lt;/a&gt;&amp;nbsp;example. It does almost exactly the same what you described.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>