<?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>nRF52 DK - radio not functional</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9562/nrf52-dk---radio-not-functional</link><description>I am using
nrfgo studio ver 1.20.0.2
s132_nrf52_1.0.0-3.alpha_softdevice.hex
nrf52832_xx_aa_s132.hex supplied by Nordic (ble_app_template)
emIDE 2.20 
 The firmware runs with the LED flashing every second but no blue tooth at all. I have tried more</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Oct 2015 13:14:40 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9562/nrf52-dk---radio-not-functional" /><item><title>RE: nRF52 DK - radio not functional</title><link>https://devzone.nordicsemi.com/thread/35314?ContentTypeID=1</link><pubDate>Mon, 05 Oct 2015 13:14:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ecb6e993-8bd7-4042-8cc3-678f83c36292</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;That cannot be possible, only error codes that this function can return errors starting from 0X2000 or NRF_SUCCESS&lt;/p&gt;
&lt;p&gt;Can you please check the place where this error code is returned, have you compiled your code with &amp;quot;Level 0&amp;quot; optimizations to enable proper debugging?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK - radio not functional</title><link>https://devzone.nordicsemi.com/thread/35315?ContentTypeID=1</link><pubDate>Mon, 05 Oct 2015 10:39:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96d99971-eaca-4862-b9e4-3b51babbf04f</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;After executing sd_softdevice_enable ending up in app_error_handler means that the call has failed returning an error code (not NRF_SUCCESS). The next line checks the error code &lt;code&gt;APP_ERROR_CHECK&lt;/code&gt; and executes app_error_handler if the error code is not NRF_SUCCESS.&lt;/p&gt;
&lt;p&gt;the documentation says what can go wrong, copy paste from header file is below&lt;/p&gt;
&lt;pre&gt;&lt;code&gt; * @retval ::NRF_SUCCESS
 * @retval ::NRF_ERROR_INVALID_STATE SoftDevice is already enabled, and the clock source and assertion handler cannot be updated.
 * @retval ::NRF_ERROR_SDM_INCORRECT_INTERRUPT_CONFIGURATION SoftDeviceinterrupt is already enabled, or an enabled interrupt has an illegal priority level.
 * @retval ::NRF_ERROR_SDM_LFCLK_SOURCE_UNKNOWN Unknown low frequency clock source selected.
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>