nRF7002-DK occurs SECURE FAULT when running https-client example

[thien]

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 anybody help me? Thanks for advance.

[runsiv]

Hi

Which version of NCS are you using and what is your build target?

Did you include the certificate to the server? 

Could you please upload your prj.conf

Regards

Runar

[thien]

I am using NCS version 2.7.0.
I included the certificate (it was there when i first came to this example)
I forgot to tell you, the function "err = conn_mgr_all_if_connect(true);" always lead to FATAL ERROR: HardFault so I comment all these lines and then the SECURE FAULT happens

Here is my prj.conf:

CONFIG_PM=n

CONFIG_MAIN_STACK_SIZE=10240

CONFIG_MBEDTLS_CFG_FILE="mcuboot-mbedtls-cfg.h"

CONFIG_BOOT_SWAP_SAVE_ENCTLV=n

CONFIG_BOOT_ENCRYPT_IMAGE=n

CONFIG_BOOT_UPGRADE_ONLY=n

CONFIG_BOOT_BOOTSTRAP=n

### mbedTLS has its own heap

# CONFIG_HEAP_MEM_POOL_SIZE is not set

### We never want Zephyr's copy of tinycrypt.  If tinycrypt is needed,

### MCUboot has its own copy in tree.

# CONFIG_TINYCRYPT is not set

# CONFIG_TINYCRYPT_ECC_DSA is not set

# CONFIG_TINYCRYPT_SHA256 is not set

CONFIG_FLASH=y

CONFIG_FPROTECT=y

### Various Zephyr boards enable features that we don't want.

# CONFIG_BT is not set

# CONFIG_BT_CTLR is not set

# CONFIG_I2C is not set

CONFIG_LOG=y

CONFIG_LOG_MODE_MINIMAL=y # former CONFIG_MODE_MINIMAL

### Ensure Zephyr logging changes don't use more resources

CONFIG_LOG_DEFAULT_LEVEL=0

### Use info log level by default

CONFIG_MCUBOOT_LOG_LEVEL_INF=y

### Decrease footprint by ~4 KB in comparison to CBPRINTF_COMPLETE=y

CONFIG_CBPRINTF_NANO=y

CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT=0

### Use the minimal C library to reduce flash usage

CONFIG_MINIMAL_LIBC=y

#core should be on a clean state when TF-M starts

CONFIG_MCUBOOT_CLEANUP_ARM_CORE=y

[runsiv]

Thanks, I have recreated it on my end and will investigate

Regards

Runar

[runsiv]

Update: I suspect it will work on your end if you disable IPV6 support in prj.conf. As of yet Im' not sure why this is the case but it fixed the hardfault on my end. 

Regards

Runar