Hi Bohdan,

This API is dual-core specific. When dual-core was implemented, it was v6/v7 specific, and being put in SPM.

As the dual-core design get updated, (See https://tf-m-user-guide.trustedfirmware.org/technical_references/design_docs/mailbox_ns_agent_update.html), these dual-core specific API should get moved out of SPM, to be part of Mailbox NS Agent specific files.

Hence the final solution is moving these dual-core files out of SPM, then v6/v7 won’t need this symbol, either.

I am seeking a place to put these files, the candidates from my side are two: secure_fw/partitions/lib/mailbox/ (To make it sharable for other dual-core implementations as now mailbox NS Agent is similar to a partition), or platform/ext/common (As the content in this file is quite platform hardware specific).

Any comments?

Thanks.

/Ken

From: Bohdan.Hunko--- via TF-M <tf-m@lists.trustedfirmware.org>
Sent: Wednesday, May 25, 2022 6:10 PM
To: tf-m@lists.trustedfirmware.org
Subject: [TF-M] tfm_arch_is_priv() is not available for v8arch

Hi everyone,

While looking through TFM code I have noticed that tfm_arch_is_priv() is defined for v6 and v7 in secure_fw/spm/cmsis_psa/arch/tfm_arch_v6m_v7m.h but not defined for v8.

Also tfm_arch_v6m_v7m.h is located in secure_fw/spm/cmsis_psa/arch/ folder, while tfm_arch_v8m.h is located in secure_fw/spm/include/.

I think that tfm_arch_is_priv() should also be defined for v8 and also tfm_arch_v6m_v7m.h should be moved to secure_fw/spm/include/. If file will be moved then we can clean up some target_include_directories() which used secure_fw/spm/cmsis_psa/arch/ folder.

Any thoughts on this?

Regards,

Bohdan Hunko

Cypress Semiconductor Ukraine

Engineer

CSUKR CSS ICW SW FW

Mobile: +38099 50 19 714
Bohdan.Hunko@infineon.com