<?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>nRF51 DK won&amp;#39;t connect with nRF Toolbox</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20642/nrf51-dk-won-t-connect-with-nrf-toolbox</link><description>Hello, 
 I&amp;#39;m wondering if my nRF DK51 is not broken as it behaves quite strange when trying to connect with a BLE Central (iOS and Android devices). For most of the part everything is ok (flashing, RTT, UART, BLE advertising) but when I try to connect</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 22 Mar 2017 10:29:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20642/nrf51-dk-won-t-connect-with-nrf-toolbox" /><item><title>RE: nRF51 DK won't connect with nRF Toolbox</title><link>https://devzone.nordicsemi.com/thread/80471?ContentTypeID=1</link><pubDate>Wed, 22 Mar 2017 10:29:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f156f838-6176-4819-a5bf-15fddbebf29b</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Okay, I see.&lt;/p&gt;
&lt;p&gt;Yes, whether or not the nRF51822-QFAB has sufficient RAM depends on the application. When I compile ble_app_uart in SDK 12.2.0, it uses 4.34 kB RAM.&lt;/p&gt;
&lt;p&gt;The minimum required RAM by S130 v.2.0.1 is 4.95 kB, and the ble_app_uart example in the SDK doesn&amp;#39;t need to use more than 4.96 kB. So the ble_app_uart will fit in the QFAB version.&lt;/p&gt;
&lt;p&gt;(Total flash: 108 kB (softdevice) + 13.23 kB = 121.23 kB)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51 DK won't connect with nRF Toolbox</title><link>https://devzone.nordicsemi.com/thread/80472?ContentTypeID=1</link><pubDate>Tue, 21 Mar 2017 21:05:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9932ee9d-460c-4890-b496-ef1469792f12</guid><dc:creator>PB</dc:creator><description>&lt;p&gt;Hi Kristin,&lt;/p&gt;
&lt;p&gt;Thank you for your reply. I&amp;#39;ve tested today with one of custom boards I&amp;#39;ve made with nRF51822 and the samples work ok, so most definitely it is something wrong with my DK (which is possible as it&amp;#39;s suffered gont through a lot).&lt;/p&gt;
&lt;p&gt;With my question I also wanted to rule out the possibility that nRF51822 could potentially have not sufficient amount of RAM to handle a BLE connection. If I understand this correctly, that would be the case for AB variant with 16KB RAM, is that right? I can&amp;#39;t seem to fit the &lt;code&gt;app_ble_uart&lt;/code&gt; example even after modifying .ld file to correct values for AB variant.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF51 DK won't connect with nRF Toolbox</title><link>https://devzone.nordicsemi.com/thread/80470?ContentTypeID=1</link><pubDate>Tue, 21 Mar 2017 10:10:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e5c47763-58ab-4fa6-815a-3e1d1996b45b</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;My first thought is that the chip is not damaged. There is a risk of ESD damage, but that doesn&amp;#39;t happen very often.&lt;/p&gt;
&lt;p&gt;If you test one of our examples, place a breakpoint in the error handler, and run the chip in debug mode?  Will the error handler be &amp;quot;called&amp;quot;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>