Secure Fault

RE: Secure Fault

Vidar Berg — Fri, 24 May 2024 04:39:31 GMT

Good to hear that you found the problem. Thanks for the update. I was a bit quick to assume what the issue was and overlooked that the violation occured for address 0x200. If it had been that SPIM1 was not configured as NS, as I initially suspected, then the fault would have occurred during initialization before any SPIM1 events could have been triggered.

RE: Secure Fault

mmelv — Thu, 23 May 2024 16:36:16 GMT

I already had those in my prj.conf, but I was able to resolve the issue independently.

RE: Secure Fault

Vidar Berg — Thu, 23 May 2024 12:18:21 GMT

Hello,

The crash log shows that the secure fault exception was raised while handling the SPIM1_SPIS1_TWIM1_TWIS1_UARTE1_IRQn, so likely in the SPIM1 ISR based on the result you got from addr2line.

Please try to disable logging in TF-M as explained in this thread RE: I2C problems in SDK v2.6.0 on nRF5340DK and see if you still get the same error. This will ensure the UARTE1 and the other peripherals sharing the same peripheral ID (see Peripherals with shared ID) will become configured as non-secure and become available to your application.

Best regards,

Vidar

RE: Secure Fault

Michal — Wed, 22 May 2024 21:59:31 GMT

Hello,

Just wanted to inform you that I most likely won't be able to look more into it until the next week.

Best regards,

Michal