<?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>Hard Fault in SPM</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/52745/hard-fault-in-spm</link><description>Hi, 
 I have an application demo using the latest nrf9160 sample lwm2m_client as its basis, and I&amp;#39;m getting a hard fault occasionally (after a few hours or days) in what I think is the SPM code. 
 
 When the hard fault occurs, the SP and MSP are both</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 20 Nov 2019 10:02:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/52745/hard-fault-in-spm" /><item><title>RE: Hard Fault in SPM</title><link>https://devzone.nordicsemi.com/thread/221005?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2019 10:02:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c90629b-6912-4b9e-9d9f-5e61578647ab</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;Read more about optimize options in &lt;a href="https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html"&gt;this link&lt;/a&gt;, Set &lt;a href="https://docs.zephyrproject.org/latest/reference/kconfig/CONFIG_NO_OPTIMIZATIONS.html"&gt;CONFIG_NO_OPTIMIZATIONS&lt;/a&gt;=y to turn of most of the optimizations.&lt;/p&gt;
&lt;p&gt;If you have more questions, please open a new case and present your problem there.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hard Fault in SPM</title><link>https://devzone.nordicsemi.com/thread/221000?ContentTypeID=1</link><pubDate>Wed, 20 Nov 2019 09:44:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f08628cd-b5c1-43fb-bb9c-0845038d8f51</guid><dc:creator>Jagruti</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;What does it mean to compile the application without any optimization?How to do that? Even I am getting the hard fault in UART.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hard Fault in SPM</title><link>https://devzone.nordicsemi.com/thread/213073?ContentTypeID=1</link><pubDate>Wed, 02 Oct 2019 22:35:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fff6b7d8-127f-45ce-9a5f-468290e16cf4</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;I&amp;#39;m sorry for the late reply. Try compiling the application without any optimization (if you aren&amp;#39;t doing it already) and see if the call stack is valid then.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hard Fault in SPM</title><link>https://devzone.nordicsemi.com/thread/212854?ContentTypeID=1</link><pubDate>Tue, 01 Oct 2019 14:39:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:208e306a-f995-4327-8f33-7a482eab5467</guid><dc:creator>jp</dc:creator><description>&lt;p&gt;I&amp;#39;m thinking now that the Stack contents listed are not valid, as the SP is at the top of the interrupt stack, and what I am looking at&amp;nbsp;are variables&amp;nbsp;in the data ram.&lt;/p&gt;
&lt;p&gt;So there doesn&amp;#39;t appear to be any context available for this fault.&lt;/p&gt;
&lt;p&gt;I also note that using the debugger, a similar fault sometimes occurs when resetting/restarting.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Hard Fault in SPM</title><link>https://devzone.nordicsemi.com/thread/212628?ContentTypeID=1</link><pubDate>Mon, 30 Sep 2019 13:39:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5db64e22-beef-4f8d-906e-e1f2a9d6a34d</guid><dc:creator>jp</dc:creator><description>&lt;p&gt;Also from the SPM zephyr.map file, which is consistent with the Stack Pointers RAM space&lt;/p&gt;
&lt;p&gt;noinit 0x20001928 0xd40&lt;br /&gt; *(SORT_BY_ALIGNMENT(.noinit))&lt;br /&gt; *(SORT_BY_ALIGNMENT(.noinit.*))&lt;br /&gt; .noinit.&amp;quot;D:/nrf/SVN/trunk/ncs/zephyr/kernel/init.c&amp;quot;.1&lt;br /&gt; 0x20001928 0x400 spm/zephyr/kernel/libspm_kernel.a(init.c.obj)&lt;br /&gt; 0x20001928 _main_stack&lt;br /&gt; .noinit.&amp;quot;D:/nrf/SVN/trunk/ncs/zephyr/kernel/init.c&amp;quot;.2&lt;br /&gt; 0x20001d28 0x140 spm/zephyr/kernel/libspm_kernel.a(init.c.obj)&lt;br /&gt; 0x20001d28 _idle_stack&lt;br /&gt; .noinit.&amp;quot;D:/nrf/SVN/trunk/ncs/zephyr/kernel/init.c&amp;quot;.3&lt;br /&gt; 0x20001e68 0x800 spm/zephyr/kernel/libspm_kernel.a(init.c.obj)&lt;br /&gt; 0x20001e68 _interrupt_stack&lt;br /&gt; *(SORT_BY_ALIGNMENT(.kernel_noinit.*))&lt;/p&gt;
&lt;p&gt;datas 0x20002668 0x2c load address 0x0001098c&lt;br /&gt; 0x20002668 __data_ram_start = .&lt;br /&gt; *(SORT_BY_ALIGNMENT(.data))&lt;br /&gt; *(SORT_BY_ALIGNMENT(.data.*))&lt;br /&gt; .data._char_out&lt;br /&gt; 0x20002668 0x4 spm/zephyr/libspm_zephyr.a(printk.c.obj)&lt;br /&gt; 0x20002668 _char_out&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>