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/psa_level_1/CMakeLists.txt

21 lines
626 B
CMake
Raw Normal View History

samples: tfm_integration: Add PSA level 1 sample app This commit adds a `tfm_level_1` samples app that shows how to use the PSA APIs in IPC mode in a real-world example. It makes use of the crypto, initial attestation and secure storage modules. Signed-off-by: Kevin Townsend <kevin@ktownsend.com>
2020-05-08 18:05:39 +08:00
# SPDX-License-Identifier: Apache-2.0
cmake_minimum_required(VERSION 3.13.1)
samples: make find_package(Zephyr...) REQUIRED This provides a better error message when building with CMake and forgetting ZEPHYR_BASE or not registering Zephyr in the CMake package registry. See parent commit for more details (split from parent for better readability). Signed-off-by: Marc Herbert <marc.herbert@intel.com>
2020-05-29 12:02:17 +08:00
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
samples: tfm_integration: Add PSA level 1 sample app This commit adds a `tfm_level_1` samples app that shows how to use the PSA APIs in IPC mode in a real-world example. It makes use of the crypto, initial attestation and secure storage modules. Signed-off-by: Kevin Townsend <kevin@ktownsend.com>
2020-05-08 18:05:39 +08:00
project(tfm_psa_level_1)
# Source files in this sample
target_sources(app PRIVATE src/main.c)
target_sources(app PRIVATE src/psa_attestation.c)
target_sources(app PRIVATE src/psa_crypto.c)
target_sources(app PRIVATE src/shell.c)
target_sources(app PRIVATE src/util_app_cfg.c)
target_sources(app PRIVATE src/util_app_log.c)
target_sources(app PRIVATE src/util_sformat.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
${ZEPHYR_TRUSTED_FIRMWARE_M_MODULE_DIR}/trusted-firmware-m/interface/include
)