Lines Matching full:secure

33 	bool "Build with TF-M as the Secure Execution Environment"
44 	  additionally generate a TF-M image for the Secure Execution
46 	  itself is to be executed in the Non-Secure Processing Environment.
48 	  ensures that the Zephyr image is built as a Non-Secure image. Both
57 	    while performing a secure function call.
195 	string "Version of the Secure Image"
199 	  Version of the secure image. This version is also used for merged
200 	  secure + non-secure builds (TFM_MCUBOOT_IMAGE_NUMBER == 1).
203 	string "Version of the Non-Secure Image"
207 	  Version of the non-secure image.
218 	bool "Use the TF-M Non-Secure application"
221 	  The main one is the TF-M secure firmware. Optionally the TF-M
222 	  non-secure application can be built.
223 	  Usually the TF-M non-secure application is not used since the
224 	  zephyr application is the non-secure application.
225 	  With this option enabled this is reversed and the TF-M non-secure
226 	  application is used instead of the Zephyr non-secure application.
256 	string "The signature type used to sign the secure and non-secure firmware images."
262 	string "Path to private key used to sign secure firmware images."
266 	  that should be used by the BL2 bootloader when signing secure
267 	  firmware images. This key file is also used for merged secure +
268 	  non-secure builds (TFM_MCUBOOT_IMAGE_NUMBER == 1).
271 	string "Path to private key used to sign non-secure firmware images."
275 	  that should be used by the BL2 bootloader when signing non-secure
338 	  for Secure Partitions.
347 	  In this model each Secure Partition processes signals in any order,
360 	  In this model each Secure Partition is made up of a collection of
361 	  callback functions which implement secure services.
369 	bool "TF-M Secure Regression tests"
372 	  the Secure domain regression tests.
373 	  The regression tests will be included in the TF-M secure firmware.
376 	bool "TF-M Non-Secure Regression tests"
379 	  the Non-Secure domain regression tests.
380 	  The regression tests will be included in the TF-M non-secure
449 # TF-M (Secure), and application (Non-Secure).
454 	  binary consisting of the TF-M Secure firmware image, optionally, the
455 	  BL2 image (if building with TFM_BL2 is enabled), and the Non-Secure
459 	bool "TF-M Disable secure logging"
463 	  the secure domain and reduce the uart driver's flash usage.
482 	  On fatal errors in the secure firmware, capture info about the exception.