<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://test-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>Unknown function at 0x00000A80</title><link>https://test-devzone.nordicsemi.com/f/nordic-q-a/88187/unknown-function-at-0x00000a80</link><description>Hi everyone, i have some problems with firmware and i hope someone can help me. I am using nRF52840 microcontroller and SEGGER Embedded Studio. Also I&amp;#39;m using the littlefs library ( github.com/.../littlefs). It happens that sometimes (50% of cases) the</description><dc:language>en-US</dc:language><generator>Telligent Community 13 Non-Production</generator><lastBuildDate>Tue, 24 May 2022 05:38:52 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://test-devzone.nordicsemi.com/f/nordic-q-a/88187/unknown-function-at-0x00000a80" /><item><title>RE: Unknown function at 0x00000A80</title><link>https://test-devzone.nordicsemi.com/thread/369155?ContentTypeID=1</link><pubDate>Tue, 24 May 2022 05:38:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f080000f-6814-47c9-bc43-50ba74eb8413</guid><dc:creator>user6207</dc:creator><description>&lt;p&gt;Thanks for updating this thread on the details of the possible problem.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
[quote user="Stefano1984"] I&amp;#39;ll keep you updated.[/quote]
&lt;p&gt;Great, Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unknown function at 0x00000A80</title><link>https://test-devzone.nordicsemi.com/thread/369024?ContentTypeID=1</link><pubDate>Mon, 23 May 2022 12:40:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cc0f1570-7ad0-40e2-9a55-0394047c4410</guid><dc:creator>user111558</dc:creator><description>&lt;p&gt;Maybe I figured out where the problem was.&lt;br /&gt;Perhaps the WDT timer expires and restarts the microcontroller. It entered the bootloader and gave me the error message.&lt;br /&gt;I will try to increase the time of the WDT. For now it works, I&amp;#39;ll keep you updated.&lt;br /&gt;Thank you very much.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unknown function at 0x00000A80</title><link>https://test-devzone.nordicsemi.com/thread/368997?ContentTypeID=1</link><pubDate>Mon, 23 May 2022 11:36:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c46a9e3-a971-44d1-96a5-04cb2f352624</guid><dc:creator>user6207</dc:creator><description>&lt;p&gt;Also check if there are any possible stack overflows if your application RAM usage is getting close to the limit of available memory.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unknown function at 0x00000A80</title><link>https://test-devzone.nordicsemi.com/thread/368996?ContentTypeID=1</link><pubDate>Mon, 23 May 2022 11:35:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e943c8c6-4634-4a47-bc26-ccc0e9bb7082</guid><dc:creator>user6207</dc:creator><description>&lt;p&gt;0X00000A80 is the hardfault in the softdevice (MBR).&amp;nbsp;&lt;br /&gt;There are a lot of threads &lt;a href="https://test-devzone.nordicsemi.com/search?q=0x00000A80"&gt;here &lt;/a&gt;discussing this. You should start your application in debugger mode and start to trigger this hardfault so that you can &lt;a href="https://test-devzone.nordicsemi.com/f/nordic-q-a/27014/how-can-i-distinguish-the-reason-for-hardfault"&gt;debug the hardfault&amp;nbsp;&lt;/a&gt;&lt;/p&gt;
[quote user=""]How do I know what the problem is? The IDE doesn&amp;#39;t give me much information.[/quote]
&lt;p&gt;If you enable logs, the hardfault handler should normally give the address of the instruction that caused the hardfault. If not, there could be stack corruptions making the exception stack useless to debug. In case of memory corruptions, there is no easy way to debug apart from trying to narrow down the problem in the debugger sessions and adding lot of logs.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>