I am trying to set CONFIG_TFM_BL2 and it seems like it cannot be set to 'y' because CONFIG_TFM_BL2_NOT_SUPPORTED is also set to 'y' in ${prj_name}/build/${prj_name}/zephyr/.config
SDK version is 2.9.2
The board is nrf9160 w/ custom outputs.
the prj.conf
# # Copyright (c) 2020 Nordic Semiconductor ASA # # SPDX-License-Identifier: LicenseRef-Nordic-5-Clause # # General CONFIG_LOG=y CONFIG_LOG_BUFFER_SIZE=2048 CONFIG_HW_ID_LIBRARY=y CONFIG_ASSERT=y CONFIG_JSON_LIBRARY=y CONFIG_REBOOT=y # Heap and stacks CONFIG_HEAP_MEM_POOL_SIZE=8192 CONFIG_MAIN_STACK_SIZE=4096 CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048 # Network CONFIG_NETWORKING=y CONFIG_NET_NATIVE=y CONFIG_NET_IPV4=y CONFIG_NET_CONNECTION_MANAGER=y # AWS IoT library CONFIG_AWS_IOT=y CONFIG_AWS_IOT_CLIENT_ID_STATIC="my-thing" CONFIG_AWS_IOT_BROKER_HOST_NAME="xxx.amazonaws.com" CONFIG_AWS_IOT_TOPIC_UPDATE_DELTA_SUBSCRIBE=y CONFIG_AWS_IOT_TOPIC_GET_ACCEPTED_SUBSCRIBE=y CONFIG_AWS_IOT_TOPIC_GET_REJECTED_SUBSCRIBE=y # MQTT helper library CONFIG_MQTT_HELPER=y CONFIG_MQTT_HELPER_SEC_TAG=201 CONFIG_MQTT_HELPER_LAST_WILL=y CONFIG_MQTT_HELPER_STACK_SIZE=4096 # MQTT - Maximum MQTT keepalive timeout specified by AWS IoT Core CONFIG_MQTT_KEEPALIVE=1200 CONFIG_MQTT_CLEAN_SESSION=y # LTE link control CONFIG_LTE_LINK_CONTROL=y CONFIG_LTE_NETWORK_MODE_LTE_M=y CONFIG_LTE_LC_PSM_MODULE=y CONFIG_LTE_LC_EDRX_MODULE=y ############################ CONFIG_DATE_TIME=y CONFIG_CJSON_LIB=y CONFIG_LOG=y CONFIG_MODEM_INFO=y CONFIG_FLASH=y CONFIG_FLASH_MAP=y CONFIG_STREAM_FLASH=y CONFIG_IMG_MANAGER=y CONFIG_BUILD_WITH_TFM=y CONFIG_TFM_BL2=y CONFIG_TFM_KEY_FILE_S="C:/nordicsemi/v2.9.2/modules/tee/tf-m/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072.pem" CONFIG_TFM_KEY_FILE_NS="C:/nordicsemi/v2.9.2/modules/tee/tf-m/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072_1.pem"
Part of the build output which says TFM_BL2 and TFM_KEY_FILE were not set; The build itself is successful overall.
warning: TFM_BL2 (defined at C:/nordicsemi/v2.9.2/nrf/modules/trusted- firmware-m\Kconfig.tfm.defconfig:18, C:/nordicsemi/v2.9.2/zephyr/modules/trusted- firmware-m/Kconfig.tfm:207, modules\trusted-firmware-m\Kconfig.tfm:207) was assigned the value 'y' but got the value 'n'. See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_TFM_BL2 and/or look up TFM_BL2 in the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too. warning: TFM_KEY_FILE_S (defined at C:/nordicsemi/v2.9.2/zephyr/modules/trusted- firmware-m/Kconfig.tfm:249, modules\trusted-firmware-m\Kconfig.tfm:249) was assigned the value 'C:/nordicsemi/v2.9.2/modules/tee/tf-m/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072.pem' but got the value ''. Check these unsatisfied dependencies: ((TFM_BL2 && BUILD_WITH_TFM) || (TFM_BL2 && BUILD_WITH_TFM && 0)) (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_TFM_KEY_FILE_S and/or look up TFM_KEY_FILE_S in the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too. warning: TFM_KEY_FILE_NS (defined at C:/nordicsemi/v2.9.2/zephyr/modules/trusted- firmware-m/Kconfig.tfm:258, modules\trusted-firmware-m\Kconfig.tfm:258) was assigned the value 'C:/nordicsemi/v2.9.2/modules/tee/tf-m/trusted-firmware-m/bl2/ext/mcuboot/root-RSA-3072_1.pem' but got the value ''. Check these unsatisfied dependencies: ((TFM_BL2 && BUILD_WITH_TFM) || (TFM_BL2 && BUILD_WITH_TFM && 0)) (=n). See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_TFM_KEY_FILE_NS and/or look up TFM_KEY_FILE_NS in the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.
Is there anything I can do to set TFM_BL2 and TFM_KEY_FILE in the build output?
