<?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>During debug, I often get the softdevice calling app_error_fault_handler</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/45064/during-debug-i-often-get-the-softdevice-calling-app_error_fault_handler</link><description>This keeps happening every time I stop the program for a while and then resume execution. 
 
 N.B. I did put a breakpoint trying to catch the problem. 
 Softdevice s132 6.0.0 using SDK 15.0.0. 
 I wonder what is it about and how can I avoid this when</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 19 Mar 2019 16:03:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/45064/during-debug-i-often-get-the-softdevice-calling-app_error_fault_handler" /><item><title>RE: During debug, I often get the softdevice calling app_error_fault_handler</title><link>https://devzone.nordicsemi.com/thread/177139?ContentTypeID=1</link><pubDate>Tue, 19 Mar 2019 16:03:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9ed277d5-84f5-4685-993e-a368df4284b8</guid><dc:creator>David Fernandez</dc:creator><description>&lt;p&gt;OK, thanks.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: During debug, I often get the softdevice calling app_error_fault_handler</title><link>https://devzone.nordicsemi.com/thread/177126?ContentTypeID=1</link><pubDate>Tue, 19 Mar 2019 15:27:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8813479b-c215-45e3-a1ca-7e93e810599e</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It&amp;#39;s not possible to disable the assert checks inside the Softdevice unfortunately. But you can overcome this limitation by using monitor mode debugging as Awneil suggested. Daniel who is one of our FAEs has written&amp;nbsp;a blog post on how to set it up for GDB/Eclipse:&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/b/blog/posts/monitor-mode-debugging-with-j-link-and-gdbeclipse"&gt;https://devzone.nordicsemi.com/b/blog/posts/monitor-mode-debugging-with-j-link-and-gdbeclipse&lt;/a&gt;. You can use it with just GDB as well; the difference is that you run the monitor commands directly in GDB.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: During debug, I often get the softdevice calling app_error_fault_handler</title><link>https://devzone.nordicsemi.com/thread/177054?ContentTypeID=1</link><pubDate>Tue, 19 Mar 2019 13:43:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dea874f1-f23c-4de2-b19e-384ded2d47d3</guid><dc:creator>David Fernandez</dc:creator><description>&lt;p&gt;Hi Owneil,&lt;/p&gt;
&lt;p&gt;Thanks for clarifying.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll try to add that to my project.&lt;/p&gt;
&lt;p&gt;My most immediate problem is that I am running low on memory until I get the new hardware, o I am wondering if there is a way to tell the softdevice to not assert on that, as the problem I am debugging won&amp;#39;t care if the cooms get disrupted due to expired timers that did not run or missing events.&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: During debug, I often get the softdevice calling app_error_fault_handler</title><link>https://devzone.nordicsemi.com/thread/176939?ContentTypeID=1</link><pubDate>Tue, 19 Mar 2019 10:17:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0ee6469a-a65e-4ede-a1ad-83afbbe46c70</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;It&amp;#39;s because the SoftDevice has timing requirements, and stopping the CPU with the debugger breaks them - so the SoftDevice crashes.&lt;/p&gt;
&lt;p&gt;You need to use Monitor Mode debugging:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/23657/improved-softdevice-debugging/148486#148486"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/23657/improved-softdevice-debugging/148486#148486&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/38438/a-working-demo-of-monitor-mode-debug-mmd-on-sdk-15-please"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/38438/a-working-demo-of-monitor-mode-debug-mmd-on-sdk-15-please&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.segger.com/products/debug-probes/j-link/technology/monitor-mode-debugging/"&gt;https://www.segger.com/products/debug-probes/j-link/technology/monitor-mode-debugging/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>