<?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 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/81495/ncs-1-6-1-peripheral_uart-difference-between-nrfconnect-for-mobile-and-nrftoolbox-uart</link><description>Hi, 
 I work with win10 laptop, Toolchain nrf Connect SDK 1.6.1 on a nrf5340dk. 
 I modifyed peripheral_uart to use 240 bytes like it&amp;#39;s explain into &amp;quot;ncs 1.6.1 peripheral_uart example - increasing NUS size&amp;quot; ticket: 
 https://devzone.nordicsemi.com/f/nordic</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 Nov 2021 11:54:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/81495/ncs-1-6-1-peripheral_uart-difference-between-nrfconnect-for-mobile-and-nrftoolbox-uart" /><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/338548?ContentTypeID=1</link><pubDate>Thu, 11 Nov 2021 11:54:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d3b25eb4-c195-4404-84a7-c3ec48af7f14</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Great,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The IOS version I have does not seem to support this.functionality.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/338245?ContentTypeID=1</link><pubDate>Tue, 09 Nov 2021 15:52:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2fbf3f00-46d2-4fe2-88cf-a343673f751b</guid><dc:creator>RHeine</dc:creator><description>&lt;p&gt;Hi Susheel,&lt;/p&gt;
&lt;p&gt;I find this post:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/74604/in-connect-sdk-v1-5-0-nrf-samples-bluetooth-peripheral_uart-data-number-is-limited-20-bytes-more-than-20bytes-ble-will-part-data-in-two-or-more-packs-to-send-or-receive/309239#309239"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/74604/in-connect-sdk-v1-5-0-nrf-samples-bluetooth-peripheral_uart-data-number-is-limited-20-bytes-more-than-20bytes-ble-will-part-data-in-two-or-more-packs-to-send-or-receive/309239#309239&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;That explain how to modify MTU size on the app nRFConnect, on the top right the there is 3 dots ranged verticaly, there I can modify &amp;quot;request MTU&amp;quot;. I put 239 and I no more error, I can send enougth bytes with nRFConnect now !&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Capture-d_2700E900_crans_5F00_20211109_2D00_165102.png" alt=" " /&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Capture-d_2700E900_crans_5F00_20211109_2D00_165110.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/338203?ContentTypeID=1</link><pubDate>Tue, 09 Nov 2021 14:13:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ad7c84ac-dbc9-4133-b731-f266e2d6ec81</guid><dc:creator>RHeine</dc:creator><description>&lt;p&gt;Additionnal information:&lt;/p&gt;
&lt;p&gt;I resolved the log inf: &amp;lt;log_strdup alloc failed&amp;gt;, by insering in prj.conf file:&lt;/p&gt;
&lt;p&gt;CONFIG_LOG_STRDUP_MAX_STRING=251&lt;br /&gt;CONFIG_LOG_STRDUP_BUF_COUNT=15&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;but I still have the problem with:&lt;/p&gt;
&lt;p&gt;[00:00:41.223,632] &amp;lt;wrn&amp;gt; bt_att: No ATT channel for MTU 30&lt;br /&gt;[00:00:41.223,632] &amp;lt;wrn&amp;gt; bt_gatt: No buffer available to send notification&lt;br /&gt;[00:00:41.223,632] &amp;lt;wrn&amp;gt; peripheral_uart_256a: Failed to send data over BLE connection&lt;/p&gt;
&lt;p&gt;I cannot send from the computer to the smartphone more then 19 bytes with nRFConnect.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/338131?ContentTypeID=1</link><pubDate>Tue, 09 Nov 2021 10:53:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:61572482-316a-4bf8-8b03-fa79c8d16a82</guid><dc:creator>RHeine</dc:creator><description>&lt;p&gt;Hi Susheel,&lt;/p&gt;
&lt;p&gt;Thank you for your help.&lt;/p&gt;
&lt;p&gt;I managed to get the sniffer to work.&lt;/p&gt;
&lt;p&gt;There is the communication and the log with nRF ToolBox UART:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/nrfToolBox_5F00_UART_5F00_peripheral_5F00_uart_5F00_256a.pcapng"&gt;devzone.nordicsemi.com/.../nrfToolBox_5F00_UART_5F00_peripheral_5F00_uart_5F00_256a.pcapng&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/nrfToolBox_5F00_UART_5F00_peripheral_5F00_uart_5F00_256a.txt"&gt;devzone.nordicsemi.com/.../nrfToolBox_5F00_UART_5F00_peripheral_5F00_uart_5F00_256a.txt&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I can see on line 1285 a sent write request where I send a packet 246 bytes (reassambled) and on line 4313 I received handle value notification a packet of 247 bytes (reassambled).&lt;/p&gt;
&lt;p&gt;There is the communication and the log with nRFConnect:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/nrfConnect_5F00_peripheral_5F00_uart_5F00_256a.pcapng"&gt;devzone.nordicsemi.com/.../nrfConnect_5F00_peripheral_5F00_uart_5F00_256a.pcapng&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/nrfConnect_5F00_peripheral_5F00_uart_5F00_256a.txt"&gt;devzone.nordicsemi.com/.../nrfConnect_5F00_peripheral_5F00_uart_5F00_256a.txt&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I can see on line 9365 I received handle value notification a packet of 18 bytes.&lt;/p&gt;
&lt;p&gt;I cannot see the packet with more then 20 bytes send, where you have the warning &amp;quot;bt_att: No ATT channel for MTU 30 / bt_gatt: No buffer available to send notification / peripheral_uart_256a: Failed to send data over BLE connection&amp;quot; on the log message.&lt;/p&gt;
&lt;p&gt;I can see on line 10799 a sent write request where I send a packet of 18 bytes,&lt;/p&gt;
&lt;p&gt;line 10805 18 bytes more, line 10811 18bytes more, line 10817 18 bytes more..&lt;/p&gt;
&lt;p&gt;For a total 12 packet of 18 bytes where send (216 bytes).&lt;/p&gt;
&lt;p&gt;There is my project:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3162.prj.conf"&gt;devzone.nordicsemi.com/.../3162.prj.conf&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/4743.nrf5340dk_5F00_nrf5340_5F00_cpuapp.overlay"&gt;devzone.nordicsemi.com/.../4743.nrf5340dk_5F00_nrf5340_5F00_cpuapp.overlay&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/6862.CMakeLists.txt"&gt;devzone.nordicsemi.com/.../6862.CMakeLists.txt&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/4452.Kconfig.txt"&gt;devzone.nordicsemi.com/.../4452.Kconfig.txt&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/4857.main.c"&gt;devzone.nordicsemi.com/.../4857.main.c&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Rob.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/337985?ContentTypeID=1</link><pubDate>Mon, 08 Nov 2021 15:40:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:89ec633c-8cf8-47c3-a6b6-318df7e8f85c</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Not sure what is happening on the receiver end. A sniffer log would help a lot to understand the issue looking at the communication in detail. The logs are not very informative. Please share your modifications so that i can reproduce this or add detail sniffer logs for this communication.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/337911?ContentTypeID=1</link><pubDate>Mon, 08 Nov 2021 12:37:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b885a76-8022-4885-a2de-a1039477decb</guid><dc:creator>RHeine</dc:creator><description>&lt;p&gt;Additionnal information:&lt;/p&gt;
&lt;p&gt;With &amp;quot;CONFIG_BT_ATT_PREPARE_COUNT=6&amp;quot; I &amp;#39;m limited to 108 bytes on Rx characteristic.&lt;/p&gt;
&lt;p&gt;I put &amp;quot;CONFIG_BT_ATT_PREPARE_COUNT=15&amp;quot; then I can send more then 239 bytes on Rx characteristic, but I have a log inf:&lt;/p&gt;
&lt;p&gt;&amp;lt;log_strdup alloc failed&amp;gt;&lt;/p&gt;
&lt;p&gt;What does it mean ?&lt;/p&gt;
&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/CONFIG_5F00_BT_5F00_ATT_5F00_PREPARE_5F00_COUNT_5F00_15.png" /&gt;&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Rob.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/337889?ContentTypeID=1</link><pubDate>Mon, 08 Nov 2021 11:15:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:12801eb2-93e0-4cd3-afe1-683e6cbf7c20</guid><dc:creator>RHeine</dc:creator><description>&lt;p&gt;Hi Susheel,&lt;/p&gt;
&lt;p&gt;Thank you for your answer.&lt;/p&gt;
&lt;p&gt;I put &amp;quot;CONFIG_BT_ATT_PREPARE_COUNT=6&amp;quot;, now I can send more data on RX charateristic with nRFConnect,&lt;/p&gt;
&lt;p&gt;I will have a look of the limit.&lt;/p&gt;
&lt;p&gt;But on Tx characteristic I can&amp;#39;t send more then 19 bytes I still have the same problem.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/TX_5F00_error_5F00_nrfConnect.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;I have a problem with python on my computer, I not able to make the sniffer work on it.&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Rob.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: ncs 1.6.1 peripheral_uart difference between nRFConnect for Mobile and nRFToolBox UART</title><link>https://devzone.nordicsemi.com/thread/337880?ContentTypeID=1</link><pubDate>Mon, 08 Nov 2021 10:40:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fe677d71-340d-429c-9184-add25d8b5006</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;It seems like more prepare writes are being performed than the config (CONFIG_BT_ATT_PREPARE_COUNT=2) set. Try to increase this size. It would be really good get a sniffer trance of the whole transaction in the not working setup (mobile) to get an even deeper understanding of the communication between your device and the mobile app.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>