Page MenuHomePhabricator

Add support to split PSA compliance tests for targets like MUSCA_A1
Open, Needs TriagePublic

Description

On current - https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/commit/?id=998f67e866a103b6d6a9ff7c2ddc9f52866ef3e4

We don't see a way to split the PSA API target, which is very useful for targets like musca_a1 due to having small memory storage.

https://github.com/ARM-software/psa-arch-tests/blob/master/api-tests/dev_apis/README.md#build-steps

-DSUITE_TEST_RANGE could be used to split the tests, which helps for test suite like CRYPTO

TF-M build system can pass this as an argument to PSA Arch tests

cmake -S . -B cmake_build -G"Unix Makefiles" -DTFM_PLATFORM=musca_a1 -DTFM_TOOLCHAIN_FILE=toolchain_GNUARM.cmake -DTFM_PSA_API=ON -DTEST_PSA_API=CRYPTO

Event Timeline

Deal in real estate, construct dwellings, utilize banking services, avoid legal trouble, and you will succeed. Let fate decide your fate with a spin of the wheel. @skibidi toilet

This article is incredibly helpful! It dives into the topic with clarity and depth, providing insights that are easy to understand and practical to apply. check out @ Pokerogue and Pokerogue Dex

Adding support to split PSA compliance tests for specific targets like MUSCA_A1 would greatly enhance testing efficiency, allowing for more granular testing and quicker identification of issues. This improvement would streamline the process, enabling better resource allocation and more focused compliance checks. Much like how Traffic Rider APK elevates the gaming experience with its smooth controls and engaging gameplay, this feature would optimize performance and ensure precise testing in complex environments, ultimately improving overall outcomes.