https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6274

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6249

It got obsoleted due to CMake refactor.

To elaborate the "Support for binary psa-arch-tests (design in progress)​" point mentioned above.

In T834#9670, @ainh wrote:

MCU boot platforms (like Musca-A) images are singed as a part of the mcuboot build. For the platforms that do not use TFM's MCU boot (e.g. PSoC64), the images have to be signed manually.
Some time ago we had a discussion on adding hooks for running a custom post-build scripts (https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/2588). Can we consider adding this now with the new build system introduction?
thanks

MCU boot platforms (like Musca-A) images are singed as a part of the mcuboot build. For the platforms that do not use TFM's MCU boot (e.g. PSoC64), the images have to be signed manually.
Some time ago we had a discussion on adding hooks for running a custom post-build scripts (https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/2588). Can we consider adding this now with the new build system introduction?
thanks

The change for this issue had been merged

Fixed in a separate commit

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6016
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6017
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6018

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5976

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5878/

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5874
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5539
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4951
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4953
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5875
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5876
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5877

https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5905
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5906

I haven't looked at in much detail but I think the shareability attributes would need to be exposed by the mm module, and then converted by ffa_memory_permissions_to_mode.

Persistent key support has been added as part of TFMv1.1. Clsoing this issue.

SMMUv3.2 supports secure Stage-2 translations and that's the feature we intend to enable as a first step.
The IP also supports "nested translations" aka S-EL1 SMMU paravirtualization although we're not looking at this option immediately.

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5775

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5759

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5695
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5696
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5697
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5698
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5699

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5669

Description: 'Short circuit signature test of attest token'

Test logs:

Thanks for your reply, so there is Stage-2 SMMU support, right? And i think we can support passthrough io support in Secure-EL1 with Stage-2 SMMU

Notes, missing features for current uploaded source changes:
• No support for isolation level2 on SSE-200
• Protected Storage is an Application RoT partition, but PS also moved to Secure Enclave
• Some regression tests running on secure side of SSE-200 fail as all messages are forwarded with the same client ID to Secure Enclave
• All IPC message forwarding is a blocking call
• Only one message is put into the mailbox at a time
• Musca-B1 related documentation is not complete yet
• Generated files are not committed, manifest parser should be run before build.
• The BL0 component mentioned in the tech forum presentation is not uploaded, as it is based on the new cmake system, and not so interesting right now
• Cmake changes are rudimentary, will be rebased to new cmake system.

This does not seem to be an issue with the new build system.

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5609

Patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5598

The patches are merged.

The change is merged.

We're considering the SMMUv3.2 support which covers the Secure Stage-2 mappings (https://developer.arm.com/documentation/ihi0070/latest).
This is still in initial investigation phases, but we hope to share design details and early patches by end of Q4'20.

Several preparation patches including scatter file adjustments.
Starts with:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5571

Several patches for adjusting the manifests:
https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5567
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5568
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5569

Patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5566