<?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>&amp;quot;FATAL ERROR: SecureFault&amp;quot; directly after flashing when calling one function? (Is it possibly caused by memory use?)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/112318/fatal-error-securefault-directly-after-flashing-when-calling-one-function-is-it-possibly-caused-by-memory-use</link><description>When i call the custom-code certify() function inside my code in a secure partition i can build the programm, but after clicking flash/running the secure uart-output prints &amp;quot;FATAL ERROR: SecureFault&amp;quot;. My program in the non-secure world and in the secure</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 24 Jun 2024 15:05:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/112318/fatal-error-securefault-directly-after-flashing-when-calling-one-function-is-it-possibly-caused-by-memory-use" /><item><title>RE: "FATAL ERROR: SecureFault" directly after flashing when calling one function? (Is it possibly caused by memory use?)</title><link>https://devzone.nordicsemi.com/thread/490387?ContentTypeID=1</link><pubDate>Mon, 24 Jun 2024 15:05:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e2f8a782-11c6-4276-b220-8fb19d0571cf</guid><dc:creator>gdl</dc:creator><description>&lt;p&gt;Thanks a lot.&lt;br /&gt;(This thread can be closed from my side.)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: "FATAL ERROR: SecureFault" directly after flashing when calling one function? (Is it possibly caused by memory use?)</title><link>https://devzone.nordicsemi.com/thread/490080?ContentTypeID=1</link><pubDate>Sat, 22 Jun 2024 11:22:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1962e7f2-e417-4d5f-81d2-ca1c183bf5c1</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;You can find some information about secure vs. non-secure here in general:&lt;br /&gt;&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-3-elements-of-an-nrf-connect-sdk-application/topic/configuration-files/#multi-image-build"&gt;https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/lessons/lesson-3-elements-of-an-nrf-connect-sdk-application/topic/configuration-files/#multi-image-build&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In terms of the violation in your case in specific. I suggest to check the Program Counter (PC) address that trigger the SecureFault. You can take the program counter (PC) and use addr2line of the .elf file you built the application to find where it actually triggered the secure fault. Description on how to use addr2line is found here:&lt;br /&gt;&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-2-debugging/topic/exercise-2-11/"&gt;https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-2-debugging/topic/exercise-2-11/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In your case you should likely check what is happening at address&amp;nbsp;0x0001FC20.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>