<?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>NCS: Central UART Sample and Peripheral UART Sample Data Length Extension</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/74475/ncs-central-uart-sample-and-peripheral-uart-sample-data-length-extension</link><description>Hi, I am using the Nordic nRF53DK, with the Segger IDE, in the NCS 1.5.0 release. 
 
 
 
 
 I&amp;#39;m playing around the Data Length Extension with the Sample of the Central UART and Peripheral UAR using nRF53DK both. 
 Acorrding to the sample of through,I</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Jun 2021 14:57:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/74475/ncs-central-uart-sample-and-peripheral-uart-sample-data-length-extension" /><item><title>RE: NCS: Central UART Sample and Peripheral UART Sample Data Length Extension</title><link>https://devzone.nordicsemi.com/thread/315189?ContentTypeID=1</link><pubDate>Mon, 14 Jun 2021 14:57:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3cb0a6b-fc51-4e0c-a8ff-b11fca00395b</guid><dc:creator>Carl Richard</dc:creator><description>&lt;p&gt;Hi again!&lt;br /&gt;&lt;br /&gt;Apologies for the delayed answer here. I think keeping the configuration from the hci_rpmsg child image of the Throughput sample, as well as&amp;nbsp;&lt;span&gt;CONFIG_BT_USER_DATA_LEN_UPDATE=y in the application should be sufficient, but I haven&amp;#39;t tested this properly. Please report back if that doesn&amp;#39;t work!&lt;br /&gt;&lt;br /&gt;You can at least remove the PHY related configurations.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Carl Richard&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS: Central UART Sample and Peripheral UART Sample Data Length Extension</title><link>https://devzone.nordicsemi.com/thread/311324?ContentTypeID=1</link><pubDate>Tue, 25 May 2021 07:38:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a8335e59-e5a8-45bf-9e7a-8eeaa4f807ad</guid><dc:creator>Leo_LYF</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi,Richard!&lt;br /&gt;&lt;br /&gt;Thanks for your answer。In Fact，After&amp;nbsp;&lt;/span&gt;&lt;span&gt;studied the&amp;nbsp;&lt;/span&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/throughput/README.html#bluetooth-throughput"&gt;NCS Throughput sample&lt;/a&gt;，I &amp;#39;ve used the cofiguration to config my&amp;nbsp;&lt;span&gt;project&amp;nbsp;&lt;/span&gt;according the Throughput sample . And it works. But it seemed that there are some&amp;nbsp;&lt;span&gt;cofiguration&amp;nbsp; that I don&amp;#39;t want to. My question is: If i just want to do the&amp;nbsp;&amp;nbsp;Data Length Extension. What exactly configuration I need to do?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Leo&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS: Central UART Sample and Peripheral UART Sample Data Length Extension</title><link>https://devzone.nordicsemi.com/thread/311309?ContentTypeID=1</link><pubDate>Tue, 25 May 2021 07:19:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:247cef1b-a626-4cb2-b451-8ff0d7ca9ff3</guid><dc:creator>William.wei</dc:creator><description>&lt;p&gt;hi Richard,&lt;/p&gt;
&lt;p&gt;i have tested the dle before, just set&amp;nbsp;&lt;span&gt;CONFIG_BT_USER_DATA_LEN_UPDATE=y in central prj.conf is enough . no need that api anymore.(i used sdk&amp;nbsp; ble_app_uart example as peripheral device)&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;William.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS: Central UART Sample and Peripheral UART Sample Data Length Extension</title><link>https://devzone.nordicsemi.com/thread/311304?ContentTypeID=1</link><pubDate>Tue, 25 May 2021 07:08:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ca7172f6-1f8b-4a87-983f-d3d8ad72c91b</guid><dc:creator>Carl Richard</dc:creator><description>&lt;p&gt;This is also important! Thanks for the input.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Carl Richard&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS: Central UART Sample and Peripheral UART Sample Data Length Extension</title><link>https://devzone.nordicsemi.com/thread/311300?ContentTypeID=1</link><pubDate>Tue, 25 May 2021 06:52:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2858ab7b-ce6c-4226-aecb-c936dbe62e70</guid><dc:creator>William.wei</dc:creator><description>&lt;p&gt;well, you need to add childimage in central_uart example(just copy child_image from throughput example should be ok)&lt;/p&gt;
&lt;div&gt;&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NCS: Central UART Sample and Peripheral UART Sample Data Length Extension</title><link>https://devzone.nordicsemi.com/thread/307234?ContentTypeID=1</link><pubDate>Wed, 28 Apr 2021 11:52:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09cf0099-518f-4626-8338-4080195fa57a</guid><dc:creator>Carl Richard</dc:creator><description>&lt;p&gt;Hello, Leo!&lt;br /&gt;&lt;br /&gt;Have you studied the &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/throughput/README.html#bluetooth-throughput"&gt;NCS Throughput sample&lt;/a&gt;? This implements several throughput increasing features, including Data Length Extension. Based on what you write here it seems like both devices are waiting for a data length parameter update, but it&amp;#39;s not initiated by any of them. I suggest checking out the function &lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/d809cec29c96a0c1884e0822fe1377563c5912f4/samples/bluetooth/throughput/src/main.c#L435"&gt;connection_configuration_set&lt;/a&gt;&amp;nbsp;where data length is set using&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/d809cec29c96a0c1884e0822fe1377563c5912f4/samples/bluetooth/throughput/src/main.c#L470"&gt;&lt;span&gt;bt_conn_le_data_len_update&lt;/span&gt;&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Carl Richard&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>