config ARCH_ARM
bool "ARM"
select ARCH_HAVE_INTERRUPTSTACK
- select ARCH_HAVE_DABORTSTACK
select ARCH_HAVE_VFORK
select ARCH_HAVE_STACKCHECK
select ARCH_HAVE_CUSTOMOPT
to used more priority levels so that we can make a cleaner distinction
with the standard interrupt handler.
-comment "Exception stack options"
-
-config ARCH_HAVE_DABORTSTACK
- bool
- default n
-
-config ARCH_DABORTSTACK
- int "Dabort Stack Size"
- depends on ARCH_HAVE_DABORTSTACK
- default 0
- ---help---
- This architecture supports an data abort stack. If defined, this symbol
- will be the size of the data abort stack in bytes. If not defined (or
- defined to be zero or less than 512 bytes), the user task stacks
- will be used during data abort handling. Recommended data abort stack
- size is 1K.
-
comment "Boot options"
default n
select ARCH_HAVE_MPU
select ARCH_HAVE_COHERENT_DCACHE if ELF || MODULE
+ select ARCH_HAVE_DABORTSTACK
config ARCH_FAMILY
string
output is sometimes helpful when debugging difficult hard fault problems,
but may be more than you typcially want to see.
+comment "Exception stack options"
+
+config ARCH_HAVE_DABORTSTACK
+ bool
+ default n
+
+config ARCH_DABORTSTACK
+ int "Dabort Stack Size"
+ depends on ARCH_HAVE_DABORTSTACK
+ default 0
+ ---help---
+ This architecture supports an data abort stack. If defined, this symbol
+ will be the size of the data abort stack in bytes. If not defined (or
+ defined to be zero or less than 512 bytes), the user task stacks
+ will be used during data abort handling. Recommended data abort stack
+ size is 1K.
+
if ARCH_CORTEXM3 || ARCH_CORTEXM4
source arch/arm/src/armv7-m/Kconfig
endif