<?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>Advertising processing too long =&amp;gt; crash</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10323/advertising-processing-too-long-crash</link><description>Hello, 
 I do connections between nRF51 in my application. 
 When the central detect an advertising frame, it ask to a server is the device is allowed (few ms). When server response is late, the central crash on connection try. Is there any way to have</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Nov 2015 19:42:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10323/advertising-processing-too-long-crash" /><item><title>RE: Advertising processing too long =&gt; crash</title><link>https://devzone.nordicsemi.com/thread/38323?ContentTypeID=1</link><pubDate>Wed, 18 Nov 2015 19:42:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0109f985-0569-4a9b-bd77-a878f10fef31</guid><dc:creator>shibshab</dc:creator><description>&lt;p&gt;I assume you are using a softdevice in your nRF51 application.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure that I understand the problem, is the CONNECT_REQ packet send too late?&lt;/p&gt;
&lt;p&gt;The softdevice will not issue the CONNECT packet immediately after the &amp;#39;sd_ble_gap_connect&amp;#39; call is performed. It will make sure to time the packet correctly (150 micro seconds after ADV).&lt;/p&gt;
&lt;p&gt;Do you have a sniffer trace?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>