arch: arm: define the ARM_SECURE_FIRMWARE option
This commit introduces the ARM_SECURE_FIRMWARE k-option, which indicates that we are building an ARM Secure application. Signed-off-by: Ioannis Glaropoulos <Ioannis.Glaropoulos@nordicsemi.no>
This commit is contained in:
parent
a01e7903b2
commit
5475de105b
1 changed files with 17 additions and 0 deletions
|
@ -42,6 +42,23 @@ config ARM_STACK_PROTECTION
|
|||
This option enables MPU stack guard to cause a system fatal error
|
||||
if the bounds of the current process stack are overflowed.
|
||||
|
||||
config ARM_SECURE_FIRMWARE
|
||||
bool
|
||||
default n
|
||||
help
|
||||
This option enables Zephyr to include code that executes in
|
||||
Secure state, as well as to exclude code that is designed to
|
||||
execute only in Non-secure state. The option is only applicable
|
||||
to ARMv8-M MCUs that implement the Security Extension.
|
||||
|
||||
Code executing in Secure state has access to both the Secure
|
||||
and Non-Secure resources of the Cortex-M MCU.
|
||||
|
||||
Code executing in Non-Secure state may trigger Secure Faults,
|
||||
if Secure MCU resources are accessed from the Non-Secure state.
|
||||
Secure Faults may only be handled by code executing in Secure
|
||||
state.
|
||||
|
||||
menu "Architectue Floating Point Options"
|
||||
depends on CPU_HAS_FPU
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue