<?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>How to incease MTU size form 23 to 50 in nrf52810 with S112 ?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120121/how-to-incease-mtu-size-form-23-to-50-in-nrf52810-with-s112</link><description>Hi. 
 code base is sdk 17.1.0 
 MCU : nrf52810 
 Softdevice : S112 (7.2.0) 
 use SES 5.42a 
 
 step1. modify NRF_SDH_BLE_GATT_MAX_MTU_SIZE form 23 to 50 in sdk_config.h 
 step2. modify RAM_START=0x20001a40 to 0x20001ad0 
 step. Rebuild and ru with PCA10040</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 25 Mar 2025 08:35:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120121/how-to-incease-mtu-size-form-23-to-50-in-nrf52810-with-s112" /><item><title>RE: How to incease MTU size form 23 to 50 in nrf52810 with S112 ?</title><link>https://devzone.nordicsemi.com/thread/528761?ContentTypeID=1</link><pubDate>Tue, 25 Mar 2025 08:35:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4d51ec2a-2688-4790-a78a-b6eb2acfa689</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It should be sufficient to increase the&amp;nbsp;&lt;span&gt;NRF_SDH_BLE_GATT_MAX_MTU_SIZE value as you did as long as you are using the&lt;a href="https://docs.nordicsemi.com/bundle/sdk_nrf5_v17.1.0/page/lib_ble_gatt.html"&gt; GATT module&lt;/a&gt; to handle the MTU negotation for you.&amp;nbsp;&lt;/span&gt;Do you have any debug logs from the device that shows the result of the MTU negotiation?&amp;nbsp;The error message &amp;quot;&lt;span&gt;&amp;nbsp;(Write operation failed : Invalid length 0x010D)&amp;quot; is also a bit strange. I don&amp;#39;t see how the length could have become set to 0x10d = 269 bytes. Are you able to write 47 bytes (50 - 3 byte ATT header) if you use the nRF Connect app on Android or iOS?&amp;nbsp;&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;Vidar&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>