Dear TF-M Community,

I have a question regarding a specific use case involving interrupt handling and domain preemption in a TrustZone-enabled system using TF-M.

In the scenario where the processor is executing within a Secure user context (e.g., during Secure Partition execution), is it possible for an interrupt assigned to the Non-Secure domain to pre-empt this Secure execution?

• Does TF-M support such preemption by default?
• If not supported out-of-the-box, what modifications or configuration changes would be required within TF-M to enable this behavior?

Any guidance on how TF-M manages interrupt priority and security attribution in this context would be greatly appreciated.

Best regards,

Waqar Ali

Waqar Ali Tahir

(He / Him / His)

Embedded SW Engineer

Phone: +433124 299160

Email: waqar.tahir@nxp.com

NXP Semiconductors Austria GmbH & Co KG | Mikronweg 1, 8101 Gratkorn | Austria |

Sitz: Gratkorn, Österreich | Firmenbuchgericht: Landesgericht für ZRS Graz | Firmenbuchnummer: FN 541474 k | VAT: ATU76231908

Unless otherwise recorded in a signed, written agreement, all sales transactions by NXP are exclusively subject to NXP’s Terms and Conditions of Commercial Sale (“NXP Terms”) published at: www.nxp.com/profile/terms/index.html. NXP explicitly rejects and disregards any terms and conditions of customer that add to, or differ from, NXP’s Terms irrespective of when customer raises its terms.  The information contained in this message is confidential. The message is intended solely for the addressee(s). If you are not the intended recipient, any use, dissemination, or reproduction is strictly prohibited and may be unlawful and you are asked to please contact the sender by return e-mail and destroy all copies of the original message.