<?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>Soft Device fault diagnosis assistance NRF52832</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44446/soft-device-fault-diagnosis-assistance-nrf52832</link><description>Hi, I am running NRF5_SDK_13.0.0_04 and s132_nrf52_4.0.3 on a custom board. 
 I am getting a Soft Device Fault on an NRF52832 device that I am not able to root cause. This occurs randomly and is not isolated to a single board/device. I have went days</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 30 Jun 2020 11:57:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44446/soft-device-fault-diagnosis-assistance-nrf52832" /><item><title>RE: Soft Device fault diagnosis assistance NRF52832</title><link>https://devzone.nordicsemi.com/thread/257561?ContentTypeID=1</link><pubDate>Tue, 30 Jun 2020 11:57:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d5ec98d7-6002-463b-b4b0-9ae9970ac9bf</guid><dc:creator>LMf</dc:creator><description>&lt;p&gt;Hi!&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you tell me further information about your issue? I think I have noticed a similar situation (&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/63172/random-reset-when-ble-advertising" rel="noopener noreferrer" target="_blank"&gt;this&lt;/a&gt;) and if it is related with the softdevice (I also use&amp;nbsp;&lt;span&gt;s132_nrf52_4.0.3&amp;nbsp;) , I would like to know if&amp;nbsp; updating to softdevice 4.0.5 still continue working.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Many thanks!&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Soft Device fault diagnosis assistance NRF52832</title><link>https://devzone.nordicsemi.com/thread/180555?ContentTypeID=1</link><pubDate>Fri, 05 Apr 2019 16:33:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76a29166-3f7b-4d43-aa63-03225a777e52</guid><dc:creator>tdwalker</dc:creator><description>&lt;p&gt;Just to close on this, I did update to softdevice 4.0.5 and have not seen the issue since I did the update.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Tim&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Soft Device fault diagnosis assistance NRF52832</title><link>https://devzone.nordicsemi.com/thread/174613?ContentTypeID=1</link><pubDate>Wed, 06 Mar 2019 15:00:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:de6fa063-8f66-4ebe-a1bf-b5d959b663c8</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I can see that the error occurs in the radio event manager, the error is typically seen if the application for some reason prevent the softdevice interrupts to occur as scheduled, so you should look into if you may be disabling interrupts. Also I recommend to update to S132v4.0.5 (this is simply replacing the softdevice binary from v4.0.3-&amp;gt;v4.0.5) due to various bug fixes.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>