OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/tfm_integration/tfm_psa_test/CMakeLists.txt

18 lines
358 B
CMake
Raw Normal View History

samples: Add a sample for running PSA tests Use the Kconfigs in TFM to enable the different suites. Signed-off-by: Øyvind Rønningstad <oyvind.ronningstad@nordicsemi.no>
2021-02-24 22:30:53 +08:00
#
# Copyright (c) 2021 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: Apache-2.0
#
cmake: increase minimal required version to 3.20.0 Move to CMake 3.20.0. At the Toolchain WG it was decided to move to CMake 3.20.0. The main reason for increasing CMake version is better toolchain support. Better toolchain support is added in the following CMake versions: - armclang, CMake 3.15 - Intel oneAPI, CMake 3.20 - IAR, CMake 3.15 and 3.20 Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
2021-08-10 20:44:56 +08:00
cmake_minimum_required(VERSION 3.20.0)
samples: Add a sample for running PSA tests Use the Kconfigs in TFM to enable the different suites. Signed-off-by: Øyvind Rønningstad <oyvind.ronningstad@nordicsemi.no>
2021-02-24 22:30:53 +08:00
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(tfm_psa_storage_test)
target_sources(app PRIVATE src/main.c)
modules: tf-m: do not expose TF-M NS interface include directories publicly Instead of exposing publicly the TF-M NS interface include directories, we include them when we build relevant projects. This is required, as the TF-M include directories contains psa crypto sources that are also provided by the mbedtls crypto module. The downside of this solution is that the TF-M includes need to be added explicitly in each application that uses TF-M APIs. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-05-09 05:40:07 +08:00
target_include_directories(app PRIVATE
modules: tfm: Split trusted-firmware-m repository Split the zephyr project maintained repository trusted-firmware-m into forks of the individual upstream repositories. https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git Upstream: TF-Mv1.4.1 Additions: zephyr: module: Add zephyr module file trusted-firmware-m: platform: lpcxpresso55s69: Update SDK https://git.trustedfirmware.org/TF-M/tf-m-tests.git Upstream: 51ff2bdfae043f6dd0813b000d928c4bda172660 Additions: zephyr: module: Add module file for tf-m-tests https://github.com/ARM-software/psa-arch-tests.git Upstream: 60faad2ead1b967ec8e73accd793d3ed0e5c56bd Additions: zephyr: module: Add module file for psa-arch-tests psa-arch-tests: Allow overriding of toolchain file The organization of folders remain the same with the following exceptions: Moved: root folder moved from modules/tee/tfm to modules/tee/tf-m to avoid problems with west update. zephyr/module.yml to trusted-firmware-m/zephyr/module.yml and ${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR} points to what was previously ${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/trusted-firmware-m. Added: psa-arch-tests/zephyr/module.yml and ${ZEPHYR_PSA_ARCH_TESTS_MODULE_DIR} tf-m-tests/zephyr/module/ and ${ZEPHYR_TF_M_TESTS_MODULE_DIR} Removed: init-git.sh README.rst Fixes: #39353 Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2021-10-19 23:57:44 +08:00
${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/interface/include
modules: tf-m: do not expose TF-M NS interface include directories publicly Instead of exposing publicly the TF-M NS interface include directories, we include them when we build relevant projects. This is required, as the TF-M include directories contains psa crypto sources that are also provided by the mbedtls crypto module. The downside of this solution is that the TF-M includes need to be added explicitly in each application that uses TF-M APIs. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
2021-05-09 05:40:07 +08:00
)