<?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>understanding softdevice_fault_handler error</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24553/understanding-softdevice_fault_handler-error</link><description>Hello! 
 I am using a nRF52832 with the S132 v4.0.3 softdevice. But I get an error from the softdevice via softdevice_fault_handler. 
 It gives me id 1(which suggest a NRF_FAULT_ID_SD_ASSERT error).
the program counter (pc) is set to 0x11A18.
info</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 23 Sep 2019 05:09:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24553/understanding-softdevice_fault_handler-error" /><item><title>RE: understanding softdevice_fault_handler error</title><link>https://devzone.nordicsemi.com/thread/211091?ContentTypeID=1</link><pubDate>Mon, 23 Sep 2019 05:09:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aae90373-7d23-4232-93f0-8afe18f521b0</guid><dc:creator>jwx</dc:creator><description>&lt;p&gt;I&amp;nbsp;encounter&amp;nbsp;the same problem,&lt;/p&gt;
&lt;p&gt;id=1,pc=18640,info=0,the system auto reset about 129 seconds per time,waht&amp;#39;s the priblem?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: understanding softdevice_fault_handler error</title><link>https://devzone.nordicsemi.com/thread/96655?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2017 12:54:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:47dc03d9-9321-44e4-98c1-f9d21d000d1f</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Great! Thanks for sharing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: understanding softdevice_fault_handler error</title><link>https://devzone.nordicsemi.com/thread/96654?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2017 12:47:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8276704e-42c6-4667-a818-12695e959d3f</guid><dc:creator>Martijn</dc:creator><description>&lt;p&gt;Found it! I disabled the global interrupts to long accidentally.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: understanding softdevice_fault_handler error</title><link>https://devzone.nordicsemi.com/thread/96652?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2017 12:27:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2ae5e9f-f665-4d6b-ae99-d4be980c2cfa</guid><dc:creator>Martijn</dc:creator><description>&lt;p&gt;I only use RTC1 and I never used the timeslot Api.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: understanding softdevice_fault_handler error</title><link>https://devzone.nordicsemi.com/thread/96653?ContentTypeID=1</link><pubDate>Wed, 23 Aug 2017 09:09:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2a3e7e22-3ea1-4ba8-b1b3-fcb0eada6d4e</guid><dc:creator>MartinBL</dc:creator><description>&lt;p&gt;Your PC value suggests that you may have used RTC0 in your application? RTC0 is used by the Softdevice so you will have to use RTC1 or 2 in your application.&lt;/p&gt;
&lt;p&gt;It can also be an issue with the Timeslot API if you are using that?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>