Hi, Right. It should be upset to get a reboot after hours of a bug reproduction. Shall we bring it as a topic to the forum next week to discuss the error handling and its configuration methods?
The best, Anton
From: Andrej Butok via TF-M tf-m@lists.trustedfirmware.org Sent: Friday, February 11, 2022 1:52 PM To: Bøe, Sebastian Sebastian.Boe@nordicsemi.no Cc: tf-m@lists.trustedfirmware.org Subject: [TF-M] Re: halting or rebooting on faults
Agree, In our TM-M code we have replaced the reset to a loop, to avoid annoying infinite reboots.
Thanks, Andrej
From: Bøe, Sebastian via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Sent: Friday, February 11, 2022 2:44 PM To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org Subject: [TF-M] halting or rebooting on faults
Hi,
it seems we could try to be more consistent with fault handling.
The current default behaviour is:
Error code returned from an SPE function? Reboot. MemFault/HardFault/SecureFault in the SPE? Halt.
Null-pointer dereference from the NSPE? (results in a secure fault for cortex-m) Halt.
Should we perhaps consistently halt or consistently reboot for these three cases and allow this to be configurable?
It is not clear to me why an error returned from a function results in a reboot, whereas a Hardfault does not. They both indicate a fault in the SPE.
At the very least the behaviour should be configurable, which this PR is a step towards: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/13839https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freview.trustedfirmware.org%2Fc%2FTF-M%2Ftrusted-firmware-m%2F%2B%2F13839&data=04%7C01%7Candrey.butok%40nxp.com%7C7ec234046e02411a600808d9ed64a4b6%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637801838783803687%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=YEimlM9Wj%2F6gPLFMdc%2BXYw6qK%2FC%2FhQwkWJiujAAHfSs%3D&reserved=0