<?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>nRF52833: MTU Exchange Fails and Connection Terminates</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127643/nrf52833-mtu-exchange-fails-and-connection-terminates</link><description>Hello Team, 
 I am working with nRF52833 configured as a BLE scanner using nRF Connect SDK for VS Code . 
 Here is my prj.conf: 
 
 AND here is scan/conn Implementaion: 
 
 Expected Execution Sequence: 
 
 Scanner starts scanning for nearby devices 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Apr 2026 06:04:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127643/nrf52833-mtu-exchange-fails-and-connection-terminates" /><item><title>RE: nRF52833: MTU Exchange Fails and Connection Terminates</title><link>https://devzone.nordicsemi.com/thread/564430?ContentTypeID=1</link><pubDate>Fri, 03 Apr 2026 06:04:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:60899673-c1bd-495a-93d2-f979cd61c568</guid><dc:creator>Embel_Tech</dc:creator><description>&lt;p data-start="77" data-end="128"&gt;The peripheral in this setup is also an nRF device.&lt;/p&gt;
&lt;p data-start="130" data-end="331"&gt;In my application, I am not storing any bonding information. The scanner-side execution flow, as shared previously, does not include any steps related to bonding or maintaining persistent pairing data.&lt;/p&gt;
&lt;p data-start="333" data-end="486"&gt;Given this, I would appreciate your guidance on how to further investigate and improve the MTU exchange failure observed from the scanner (central) side.&lt;/p&gt;
&lt;p data-start="488" data-end="524"&gt;Looking forward to your suggestions.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52833: MTU Exchange Fails and Connection Terminates</title><link>https://devzone.nordicsemi.com/thread/564343?ContentTypeID=1</link><pubDate>Wed, 01 Apr 2026 06:09:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dfe4a66c-4b4a-4f03-8117-d00e91b9aebf</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;What device is the peripheral here? Is it an nRF device as well or something else? I&amp;#39;m trying to find references to what this -128 error is, which should only point to the devices not being connected.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The multiple 0x3E errors are indeed pointing to connection failed to be established, and this could be due to one of the devices having stored pairing information that the other does not. Can you try erasing the bonding information on both devices before trying to connect again? If you don&amp;#39;t have a way to do so, nrfutil device recover to recover the device before flashing them again should also erase bonding information.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>