<?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>Possible to reset the Soft Device only, without resetting entire device?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/30360/possible-to-reset-the-soft-device-only-without-resetting-entire-device</link><description>In the event that a Nordic soft device library call fails (as determined by APP_ERROR_CHECK() macro) and our application level app_error_fault_handler () function is called, is there a way of cleanly resetting the soft device only , without resetting</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 09 Feb 2018 11:59:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/30360/possible-to-reset-the-soft-device-only-without-resetting-entire-device" /><item><title>RE: Possible to reset the Soft Device only, without resetting entire device?</title><link>https://devzone.nordicsemi.com/thread/120414?ContentTypeID=1</link><pubDate>Fri, 09 Feb 2018 11:59:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3a5810bd-0702-4968-92bb-f359d8f1560b</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi JC,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The app_error_fault_handler() is generic and does not distinguish the sources of the assertion (only if it comes from SD or application), and the operation that makes sense to do in a generic &amp;quot;catch-all assertion handler&amp;quot; is a system-reset to ensure a known starting point.&lt;/p&gt;
&lt;p&gt;What I&amp;#39;d recommend is to evaluate functions that are prone to give a return !=NRF_SUCCESS, like a &amp;quot;uart_put()&amp;quot; command, which might return _BUSY. If you get a _BUSY return code, it does not always require the application to do a soft-reset. Same applies for other scenarios where the buffer is full. Retrying (with a timeout) can be a better way of handling such return codes.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>