<?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>SDK 12.2, S132 v3.1.0, softdevice_fault_handler at PC=0x10A62</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/59559/sdk-12-2-s132-v3-1-0-softdevice_fault_handler-at-pc-0x10a62</link><description>I searched in this forum about softdevice_fault_handler errors, but could not find the cause of my problem. I need to obtain more information for a softdevice_fault_handler at PC=0x10A62 . This assert error coming from the SoftDevice occurs at random</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 30 Mar 2020 10:34:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/59559/sdk-12-2-s132-v3-1-0-softdevice_fault_handler-at-pc-0x10a62" /><item><title>RE: SDK 12.2, S132 v3.1.0, softdevice_fault_handler at PC=0x10A62</title><link>https://devzone.nordicsemi.com/thread/242359?ContentTypeID=1</link><pubDate>Mon, 30 Mar 2020 10:34:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:92e30a2b-c326-4a1d-ad00-4733a4058781</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;This assert is inside the softdevice handler scheduler at the time when the radio timeslot ends. The scheduler sees that the radio timeslot is ending later than the time allocated for it.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If your application is not using radio timeslot API, then this means that softdevice did not manage to end the timeslot allocated to itself in time. This will happen, if your application has some activity in interrupt service routine with a priority that is not allowed by the softdevice.&lt;/p&gt;
&lt;p&gt;I would advise you to check all the enabled interrupts in your application and see if you have set the priority of the interrupt to the one allowed by the softdevice. If you forget to set the interrupt priority of any interrupt, then it by default takes the highest priority (value 0) which is not allowed for applications using softdevice.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>