<?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>MTU agree size on peers</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/113428/mtu-agree-size-on-peers</link><description>Hi, 
 We are working on nRF5340 with TF-M enabled and iOS application. 
 What we are observing is the peripheral device MTU TX and RX are configured to 512 bytes whereas the agreed MTU TX and RX are 293 and 508 respectively. 
 My questions are 
 
 Why</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 03 Oct 2024 13:27:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/113428/mtu-agree-size-on-peers" /><item><title>RE: MTU agree size on peers</title><link>https://devzone.nordicsemi.com/thread/504846?ContentTypeID=1</link><pubDate>Thu, 03 Oct 2024 13:27:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2ac95e25-123a-4e04-ae35-7d7bdaca02a8</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hi Jithin,&lt;/p&gt;
&lt;p&gt;Have you the&amp;nbsp;&lt;span&gt;&lt;span dir="ltr"&gt;configured the CONFIG_BT_BUF_ACL_RX_SIZE value in both the appcore and netcore image.?&amp;nbsp;The buffer size must also be configured in the network core image to match the host settings.&amp;nbsp;We have often been using ATT MTU of 247 as max MTU size because it aligns with the max. radio packet length (251), but larger MTUs are supported, and we do that in the throughput sample. Please do compare the setting in your applications against the settings used in our throughput sample:&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/throughput/README.html"&gt;https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/bluetooth/throughput/README.html&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;Best Regards,&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;span dir="ltr"&gt;Swathy&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MTU agree size on peers</title><link>https://devzone.nordicsemi.com/thread/503699?ContentTypeID=1</link><pubDate>Wed, 25 Sep 2024 09:22:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e28d6f8d-2ca2-40ae-a0f3-96888be25b97</guid><dc:creator>Jithin A</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Why I always getting notified about engineer assigned.&lt;/p&gt;
&lt;p&gt;Am I asking any wrong question here? Can anyone please guide me correctly.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MTU agree size on peers</title><link>https://devzone.nordicsemi.com/thread/500507?ContentTypeID=1</link><pubDate>Fri, 30 Aug 2024 06:15:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:027a5639-8af5-4638-a73c-750479452cdc</guid><dc:creator>Jithin A</dc:creator><description>&lt;p&gt;Hi, any update on this.&lt;/p&gt;
&lt;p&gt;Can anyone please suggest how can I increase the MTU size on the peripheral end and also it should support on the central device.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MTU agree size on peers</title><link>https://devzone.nordicsemi.com/thread/499546?ContentTypeID=1</link><pubDate>Fri, 23 Aug 2024 11:59:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fc49f8d5-0f58-4326-89f6-9989bedbb39b</guid><dc:creator>Jithin A</dc:creator><description>&lt;p&gt;Hi SwRa,&lt;/p&gt;
&lt;p&gt;Thank you for the reply&lt;/p&gt;
[quote userid="107732" url="~/f/nordic-q-a/113428/mtu-agree-size-on-peers/499536"]The maximum MTU size supported by nRF5340 is 247 bytes. [/quote]
&lt;p&gt;If so, how come RX size is agreed to 512?&lt;/p&gt;
[quote userid="107732" url="~/f/nordic-q-a/113428/mtu-agree-size-on-peers/499536"]However, the final decision is made by the central device.[/quote]
&lt;p&gt;This answers my q2, thank you.&lt;/p&gt;
[quote userid="107732" url="~/f/nordic-q-a/113428/mtu-agree-size-on-peers/499536"]Could you let me know what you are trying to achieve with higher mtu values.?[/quote]
&lt;p&gt;We need to support DFU, and we cannot use the DFU GATT service because of some security reasons. It takes a lot of time to transfer ~400KB with MTU being 247 bytes. If we can have large MTU we can reduce the DFU download time and also save power.&lt;/p&gt;
&lt;p&gt;This is very time consuming for our application.&lt;/p&gt;
[quote userid="107732" url="~/f/nordic-q-a/113428/mtu-agree-size-on-peers/499536"]Is both the peripheral and central based on Nordic SoC.?[/quote]
&lt;p&gt;No, Central is basically mobile device.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Can you please suggest any solution to increase the MTU size?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MTU agree size on peers</title><link>https://devzone.nordicsemi.com/thread/499536?ContentTypeID=1</link><pubDate>Fri, 23 Aug 2024 11:42:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4a49fab5-d5c3-4384-b837-ab47664c0e1f</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hi Jithin,&lt;/p&gt;
&lt;p&gt;Sorry for the delay..&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The maximum MTU size supported by nRF5340 is 247 bytes. This is set by the configuration&amp;nbsp;&lt;/span&gt;&lt;code dir="ltr"&gt;CONFIG_BT_L2CAP_TX_MTU=247&lt;/code&gt;&lt;span&gt;.&lt;/span&gt;The MTU (Maximum Transmission Unit) size in a Bluetooth Low Energy (BLE) connection is determined by both the central and peripheral devices. However, the final decision is made by the central device.&lt;/p&gt;
&lt;p&gt;Could you let me know what you are trying to achieve with higher mtu values.? Is both the peripheral and central based on Nordic SoC.? You could take a look at this blog post for a better understanding:&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/building-a-bluetooth-application-on-nrf-connect-sdk-part-3-optimizing-the-connection"&gt;Building a Bluetooth application on nRF Connect SDK - Part 3 Optimizing the connection&lt;/a&gt;&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Swathy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MTU agree size on peers</title><link>https://devzone.nordicsemi.com/thread/497554?ContentTypeID=1</link><pubDate>Fri, 09 Aug 2024 06:48:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e79f093e-e220-4442-92e9-1029d83af23b</guid><dc:creator>Jithin A</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Anyone can you please explain how the MTU size are handled in NRF5340.&lt;/p&gt;
&lt;p&gt;Thank you in advance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MTU agree size on peers</title><link>https://devzone.nordicsemi.com/thread/495929?ContentTypeID=1</link><pubDate>Mon, 29 Jul 2024 06:49:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:27dc4005-924b-4ae8-b998-5a312ea2c7d9</guid><dc:creator>Jithin A</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Any update on this.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;Can anyone please explain me how MTU size effect on data exchanges over BLE.&lt;/p&gt;
&lt;p&gt;And I want to have same TX and RX size, we have some large data transfers to and from so, the above makes our peripheral looks slow when sending data to the mobile application (central)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>