<?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>ble disconnect</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/28877/ble-disconnect</link><description>I am using nRF 52832 (softdevice v2.0). I am writing a code to get data via SPI and then transmit over BLE. 
 I have written my code and SPI is working perfectly. 
 But the connection with the BLE gets&amp;#39; timeout in 3 min. It also stops advertising. </description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 01 Jan 2018 11:40:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/28877/ble-disconnect" /><item><title>RE: ble disconnect</title><link>https://devzone.nordicsemi.com/thread/114312?ContentTypeID=1</link><pubDate>Mon, 01 Jan 2018 11:40:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6bc1c2b3-5724-408f-8ad4-e797b26cc9ce</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Hard to say from source code, that&amp;#39;s not how you debug the aplication (by just reading the source code). If you see disconnects then simply make radio log by some BLE sniffer and look which side and why disconnected. If something weird happens on nRF5x side then enable RTT or UART logging and see what events happen and what error codes are thrown by SD API calls. If you use SPI driver incorrectly (e.g. in blocking mode) you can easily &amp;quot;kill&amp;quot; radio activity and break BLE link etc. There can be so many reasons and this information isn&amp;#39;t showing anything special to judge.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>