<?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>nRF7002-DK occurs SECURE FAULT when running https-client example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/115876/nrf7002-dk-occurs-secure-fault-when-running-https-client-example</link><description>I am running https-client example: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/net/https_client/README.html . After connecting to wifi, it runs to this SECURE FAULT: 
 
 I run debug and see that it occurs at this function 
 
 Could</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 28 Oct 2024 13:36:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/115876/nrf7002-dk-occurs-secure-fault-when-running-https-client-example" /><item><title>RE: nRF7002-DK occurs SECURE FAULT when running https-client example</title><link>https://devzone.nordicsemi.com/thread/508176?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2024 13:36:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:28ea08bc-4f41-40e4-99c7-5454ff4443b3</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Update: I suspect it will work on your end if you disable IPV6 support in prj.conf. As of yet Im&amp;#39; not sure why this is the case but it fixed the hardfault on my end.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF7002-DK occurs SECURE FAULT when running https-client example</title><link>https://devzone.nordicsemi.com/thread/508137?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2024 12:16:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:747efe02-4893-4a7e-809d-73d23059813a</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Thanks, I have recreated it on my end and will investigate&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF7002-DK occurs SECURE FAULT when running https-client example</title><link>https://devzone.nordicsemi.com/thread/508078?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2024 07:57:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f3e7981d-c0d2-4574-bf26-6767bad380bc</guid><dc:creator>thien</dc:creator><description>&lt;p&gt;I am using NCS version 2.7.0.&lt;br /&gt;I included the certificate (it was there when i first came to this example)&lt;br /&gt;I forgot to tell you, the function &amp;quot;&lt;span&gt;err&lt;/span&gt;&lt;span&gt; = &lt;/span&gt;&lt;span&gt;conn_mgr_all_if_connect&lt;/span&gt;&lt;span&gt;(&lt;/span&gt;&lt;span&gt;true&lt;/span&gt;&lt;span&gt;);&lt;/span&gt;&amp;quot; always lead to&amp;nbsp;FATAL ERROR: HardFault so I comment all these lines and then the SECURE FAULT happens&lt;br /&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1730102180124v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Here is my prj.conf:&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_PM&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MAIN_STACK_SIZE&lt;/span&gt;&lt;span&gt;=10240&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MBEDTLS_CFG_FILE&lt;/span&gt;&lt;span&gt;=&lt;/span&gt;&lt;span&gt;&amp;quot;mcuboot-mbedtls-cfg.h&amp;quot;&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BOOT_SWAP_SAVE_ENCTLV&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BOOT_ENCRYPT_IMAGE&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BOOT_UPGRADE_ONLY&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_BOOT_BOOTSTRAP&lt;/span&gt;&lt;span&gt;=n&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;### mbedTLS has its own heap&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_HEAP_MEM_POOL_SIZE is not set&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;### We never want Zephyr&amp;#39;s copy of tinycrypt. &amp;nbsp;If tinycrypt is needed,&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;### MCUboot has its own copy in tree.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_TINYCRYPT is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_TINYCRYPT_ECC_DSA is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_TINYCRYPT_SHA256 is not set&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_FLASH&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_FPROTECT&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;### Various Zephyr boards enable features that we don&amp;#39;t want.&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_BT is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_BT_CTLR is not set&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;# CONFIG_I2C is not set&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;CONFIG_LOG&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_LOG_MODE_MINIMAL&lt;/span&gt;&lt;span&gt;=y &lt;/span&gt;&lt;span&gt;# former CONFIG_MODE_MINIMAL&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;### Ensure Zephyr logging changes don&amp;#39;t use more resources&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_LOG_DEFAULT_LEVEL&lt;/span&gt;&lt;span&gt;=0&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;### Use info log level by default&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MCUBOOT_LOG_LEVEL_INF&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;### Decrease footprint by ~4 KB in comparison to CBPRINTF_COMPLETE=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_CBPRINTF_NANO&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT&lt;/span&gt;&lt;span&gt;=0&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;### Use the minimal C library to reduce flash usage&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MINIMAL_LIBC&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;br /&gt;
&lt;div&gt;&lt;span&gt;#core should be on a clean state when TF-M starts&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_MCUBOOT_CLEANUP_ARM_CORE&lt;/span&gt;&lt;span&gt;=y&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF7002-DK occurs SECURE FAULT when running https-client example</title><link>https://devzone.nordicsemi.com/thread/508071?ContentTypeID=1</link><pubDate>Mon, 28 Oct 2024 07:42:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f5a9d358-4125-458a-81bf-8dade096f5ed</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;Which version of NCS are you using and what is your build target?&lt;/p&gt;
&lt;p&gt;Did you include the certificate to the server?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Could you please upload your prj.conf&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>