<?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>Bus Fault caused by write data to fds</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/122602/bus-fault-caused-by-write-data-to-fds</link><description>I&amp;#39;m developing my application with nrf 52832 and nrf SDK v17. 
 I know NCS is more powerful. I&amp;#39;m currently learning how to use it. 
 But now.I still need my application with nrf SDK. 
 When I was running my application, I found that the peer_manager returned</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 02 Jul 2025 06:02:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/122602/bus-fault-caused-by-write-data-to-fds" /><item><title>RE: Bus Fault caused by write data to fds</title><link>https://devzone.nordicsemi.com/thread/541108?ContentTypeID=1</link><pubDate>Wed, 02 Jul 2025 06:02:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30e8df19-7cbb-4093-a1cd-1e3aed1fb492</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The blog explains how you can make the error precise by&amp;nbsp;writing the&amp;nbsp;DISDEFWBUF bit with GDB, but you can do the same from your code:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;int main(void)
{
    /*
     *  &amp;quot;Make all memory stores precise at the cost of performance
     *   by setting DISDEFWBUF in the Cortex M3/M4 ACTLR reg&amp;quot; 
     *   (Ref. https://interrupt.memfault.com/blog/cortex-m-hardfault-debug#analysis-after-making-the-imprecise-error-precise) 
     */
    SCnSCB-&amp;gt;ACTLR |= SCnSCB_ACTLR_DISDEFWBUF_Msk;
    
    ...&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bus Fault caused by write data to fds</title><link>https://devzone.nordicsemi.com/thread/541093?ContentTypeID=1</link><pubDate>Wed, 02 Jul 2025 01:13:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:522e7944-06eb-4a25-aa42-1ac7138af207</guid><dc:creator>Chaoyue Ying</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I have finished reading all the relevant content in this blog.&lt;/p&gt;
&lt;p&gt;It is mentioned that&amp;nbsp;&lt;span&gt;there is a trick we can use for the Cortex-M4 to make all memory stores precise.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t know what this technique refers to.Do you have any suggestions?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bus Fault caused by write data to fds</title><link>https://devzone.nordicsemi.com/thread/541026?ContentTypeID=1</link><pubDate>Tue, 01 Jul 2025 11:51:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6871139c-2577-4f40-b521-853b68d758ba</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not familiar with the&amp;nbsp;&lt;span&gt;cmbacktrace tool, but the&amp;nbsp;bfsr reg value (536916996) suggests that the &amp;quot;imprecise&amp;quot; bit is set.&amp;nbsp; Please have a look at this blog post here&amp;nbsp;&lt;a href="https://interrupt.memfault.com/blog/cortex-m-hardfault-debug#imprecise-error-code-example"&gt;https://interrupt.memfault.com/blog/cortex-m-hardfault-debug#imprecise-error-code-example&lt;/a&gt;&amp;nbsp;which explains the meaning of this and what you can do to debug such faults.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Vidar&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>