<?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>HardFault in SoftDevice, PC=0x10000000</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91960/hardfault-in-softdevice-pc-0x10000000</link><description>I&amp;#39;m trying to investigate a HardFault that happens within half an hour of using our product. 
 Device is nRF52832, SDK is 17.1.0, SD is S132 7.2.0 
 So far, I never managed to have the issue trigger while debugging with SES/Ozone. It does happen, however</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 15 Sep 2022 16:34:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91960/hardfault-in-softdevice-pc-0x10000000" /><item><title>RE: HardFault in SoftDevice, PC=0x10000000</title><link>https://devzone.nordicsemi.com/thread/386446?ContentTypeID=1</link><pubDate>Thu, 15 Sep 2022 16:34:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:061ae010-0f1e-4edc-b829-5e4f641edadb</guid><dc:creator>Marco</dc:creator><description>&lt;p&gt;Thank you so much, that was indeed the issue and I would have never figured it out.&lt;/p&gt;
&lt;p&gt;As a workaround, I picked the option to disable the FPU (by setting gcc to use the &amp;quot;Soft&amp;quot; floating point ABI), since I don&amp;#39;t need it anyway.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: HardFault in SoftDevice, PC=0x10000000</title><link>https://devzone.nordicsemi.com/thread/386255?ContentTypeID=1</link><pubDate>Wed, 14 Sep 2022 18:36:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97668fcf-628b-4d7e-aaba-509009851567</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;It looks like you have been unfortunate enough to run into errata 220 (&lt;span&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/errata_nRF52832_Rev3/ERR/nRF52832/Rev3/latest/anomaly_832_220.html?cp=4_2_1_0_1_59"&gt;[220] CPU: RAM is not ready when written&lt;/a&gt;&lt;/span&gt;). This issue is very rare, but it does happen in certain FW configurations. &amp;nbsp; Please have a look at the discussion here: &amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/84283/random-bad-instruction-faults-at-0x16274-with-softdevice-s132-version-7-0-1-sdk-16-0-0"&gt;Random bad instruction faults at 0x16274 with softdevice s132 version 7.0.1. SDK 16.0.0&lt;/a&gt;&amp;nbsp;where I proposed a workaround for this.&lt;/p&gt;
[quote user=""]As far as I understand, this indicates that the CPU tried to jump to 0x10000000 and the LR was 0x16299, which is in the SoftDevice region.[/quote]
&lt;p&gt;Yes, that is how I interpret the stack dump as well.&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></channel></rss>