Hi Tomi,

Yes, that I know. Thank you for your information. I am mainly concerned about whether using TF-M main from Zephyr side would affect certification process. Thank you again!

Best regards,

Hao

From: Fontanilles, Tomi <tomi.fontanilles@nordicsemi.no>
Sent: Thursday, October 3, 2024 10:40 AM
To: Zhang, Hao <Hao.Zhang@analog.com>; tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.org>
Subject: Re: [TF-M] PSA Certification for TF-M
 
[External]

Hey Hao,

Just to comment on the Zephyr side. Both v3.7 and main are very closely following TF-M v2.1.
Some patches are applied on top of the upstream, unmodified TF-M, but only for compatibility with Zephyr.
They are very minor modifications.

On Thu, 2024-10-03 at 14:28 +0000, Zhang, Hao via TF-M wrote:
Hi TF-M committee,

I have a question regarding  PSA certification. Am I understanding correctly that if a platform wants to be ported to TF-M and the product wants to pass PSA certified, the TF-M version needs to come from a certain LTS tag release (e.g.TF-M v2.1.0 with commit 0c4c99b that was pushed 5 months ago). However,  Zephyr v3.7.0 is using TF-M version that is updated after TF-M v2.1.0. Does that means efforts need to be done to manually modify west.yml in Zephyr to roll back to the tag release of v2.1.0 for PSA certification?

Thank you very much,

Best,
Primary Git Repository for the Zephyr Project. Zephyr is a new generation, scalable, optimized, secure RTOS for multiple hardware architectures. - zephyrproject-rtos/zephyr
github.com


Read-only mirror for Trusted Firmware-M. Contribute to TrustedFirmware-M/trusted-firmware-m development by creating an account on GitHub.
github.com


Best regards,

Hao