Hi Robert,

MemManage fault indicates an MPU violation -- it's hard to say where it might come from, but it's a good idea to check that the MPU configuration is correct and matches actual code/data layout of your binary.

In your exception context, the stacked PC (i.e. the address of the instruction that caused the fault) is 0x000358D1. If you check the disassembly at that address in a debugger then it may shed some light, and if you set a breakpoint there and run to it then you will be able to see more of the context that led to that point. Also, in the stacked context, the LR looks like another EXC_RETURN value, so it may be that the MemManage fault occurred inside another fault.

Kind regards, Jamie

-----Original Message----- From: robert.sari.ext--- via TF-M tf-m@lists.trustedfirmware.org Sent: Wednesday, January 10, 2024 4:29 PM To: tf-m@lists.trustedfirmware.org Subject: [TF-M] MemManage Fault during TF-M Secure Firmware Initialization

Hello,

I am currently having an issue during TF-M initialization where a MemManage fault is being triggered during secure FW initialization (most likely when the SPM is initialized). It appears to be an error during unstacking/returning from an exception as the MUNSTKERR bit of the MMFSR register is set.

I receive the following exception context and exception frame when the error occurs: __________________________________________________________ FATAL ERROR: MemManage fault Here is some context for the exception: EXC_RETURN (LR): 0xFFFFFFFD Exception came from secure FW in thread mode. xPSR: 0x20000004 MSP: 0x20000BF8 PSP: 0x20002518 MSP_NS: 0x20042DF8 PSP_NS: 0xFFFFFFFC Exception frame at: 0x20002518 (Note that the exception frame may be corrupted for this type of error.) R0: 0x00000000 R1: 0x00000000 R2: 0x00000000 R3: 0x00000000 R12: 0x00000000 LR: 0xFFFFFFFE PC: 0x000358D1 xPSR: 0x01000000 CFSR: 0x00000008 BFSR: 0x00000000 BFAR: Not Valid MMFSR: 0x00000008 MMFAR: Not Valid UFSR: 0x00000000 HFSR: 0x00000000 SFSR: 0x00000000 SFAR: Not Valid __________________________________________________________

Other Information: - I am running Nordic Semiconductor's "tfm_psa_template" sample: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.2.0/nrf/samples/tfm/t... - The Secure MPU is enabled (only the background region) before TF-M initialization begins - Board: nRF5340dk - TF-M Version: v1.8.0 - TF-M Isolation Level: 2

My questions are: - What part of the TF-M FW could be the cause of this MemManage fault? - Is there any way to solve this issue (such as a different TF-M configuration) so that TF-M will initialize properly?

Regards, Robert Sari -- TF-M mailing list -- tf-m@lists.trustedfirmware.org To unsubscribe send an email to tf-m-leave@lists.trustedfirmware.org