📄 ecos_default.ecc
字号:
#cdl_option CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 1 # value_source default # Default value: 1 # The following properties are affected by this value # option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # Requires: ! CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT # option CYGBLD_BUILD_GDB_STUBS # Requires: ! CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT};# Chain all interrupts together# Interrupts can be attached to vectors either singly, or be# chained together. The latter is necessary if there is no way# of discovering which device has interrupted without# inspecting the device itself. It can also reduce the amount# of RAM needed for interrupt decoding tables and code.#cdl_option CYGIMP_HAL_COMMON_INTERRUPTS_CHAIN { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 0 # value_source default # Default value: 0 # The following properties are affected by this value # option CYGIMP_KERNEL_INTERRUPTS_CHAIN # Requires: CYGIMP_HAL_COMMON_INTERRUPTS_CHAIN};# Ignore spurious [fleeting] interrupts# On some hardware, interrupt sources may not be de-bounced or# de-glitched. Rather than try to handle these interrupts (no# handling may be possible), this option allows the HAL to simply# ignore them. In most cases, if the interrupt is real it will# reoccur in a detectable form.#cdl_option CYGIMP_HAL_COMMON_INTERRUPTS_IGNORE_SPURIOUS { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 0 # value_source default # Default value: 0};# <# HAL context switch support# A number of configuration options related to thread contexts# are common to most or all HAL packages, even though the# implementations will vary from architecture to architecture.#cdl_component CYGPKG_HAL_COMMON_CONTEXT { # There is no associated value. # The following properties are affected by this value};# ># Use minimum thread context# The thread context switch code can exploit the calling# conventions defined for a given architecture to reduce the# amount of state that has to be saved during a context# switch. Generally this improves performance and reduces# code size. However it can make source-level debugging more# difficult.#cdl_option CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 1 # value_source default # Default value: 1 # The following properties are affected by this value # option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # Requires: ! CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM # option CYGBLD_BUILD_GDB_STUBS # Requires: ! CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM};# <# Explicit control over cache behaviour# These options let the default behaviour of the caches # be easily configurable.#cdl_component CYGPKG_HAL_CACHE_CONTROL { # There is no associated value.};# ># Enable DATA cache on startup# Enabling this option will cause the data cache to be enabled# as soon as practicable when eCos starts up. One would choose# to disable this if the data cache cannot safely be turned on,# such as a case where the cache(s) require additional platform# specific setup.#cdl_component CYGSEM_HAL_ENABLE_DCACHE_ON_STARTUP { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 1 # value_source default # Default value: 1};# ># DATA cache mode on startup# This option controls the mode the cache will be set to# when enabled on startup.#cdl_option CYGSEM_HAL_DCACHE_STARTUP_MODE { # Flavor: data # No user value, uncomment the following line to provide one. # user_value COPYBACK # value_source default # Default value: COPYBACK # Legal values: "COPYBACK" "WRITETHRU" };# <# Enable INSTRUCTION cache on startup# Enabling this option will cause the instruction cache to be enabled# as soon as practicable when eCos starts up. One would choose# to disable this if the instruction cache cannot safely be turned on,# such as a case where the cache(s) require additional platform# specific setup.#cdl_option CYGSEM_HAL_ENABLE_ICACHE_ON_STARTUP { # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 1 # value_source default # Default value: 1};# <# Source-level debugging support# If the source level debugger gdb is to be used for debugging# application code then it may be necessary to configure in support# for this in the HAL.#cdl_component CYGPKG_HAL_DEBUG { # There is no associated value.};# ># Support for GDB stubs# The HAL implements GDB stubs for the target.#cdl_interface CYGINT_HAL_DEBUG_GDB_STUBS { # Implemented by CYGPKG_HAL_ARM_GPS4020, active, enabled # This value cannot be modified here. # Flavor: data # Current_value: 1 # The following properties are affected by this value # option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # ActiveIf: CYGINT_HAL_DEBUG_GDB_STUBS};# Include GDB stubs in HAL# This option causes a set of GDB stubs to be included into the# system. On some target systems the GDB support will be# provided by other means, for example by a ROM monitor. On# other targets, especially when building a ROM-booting system,# the necessary support has to go into the target library# itself. When GDB stubs are include in a configuration, HAL# serial drivers must also be included.#cdl_option CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS { # ActiveIf constraint: CYGINT_HAL_DEBUG_GDB_STUBS # CYGINT_HAL_DEBUG_GDB_STUBS == 1 # --> 1 # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 0 # value_source default # Default value: 0 # Requires: ! CYGSEM_HAL_USE_ROM_MONITOR # CYGSEM_HAL_USE_ROM_MONITOR == GDB_stubs # --> 0 # Requires: ! CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT # CYGDBG_HAL_COMMON_INTERRUPTS_SAVE_MINIMUM_CONTEXT == 1 # --> 0 # Requires: ! CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM # CYGDBG_HAL_COMMON_CONTEXT_SAVE_MINIMUM == 1 # --> 0 # Requires: !CYGSEM_HAL_VIRTUAL_VECTOR_DIAG || CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_COMMS # CYGSEM_HAL_VIRTUAL_VECTOR_DIAG == 1 # CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_COMMS == 0 # --> 0 # The following properties are affected by this value # component CYGDBG_HAL_DIAG_TO_DEBUG_CHAN # DefaultValue: (CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS || CYG_HAL_STARTUP == "RAM") ? 1 : 0 # option CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT # Requires: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT # DefaultValue: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT # ActiveIf: CYGSEM_HAL_USE_ROM_MONITOR || CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT # DefaultValue: !CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_COMMS # DefaultValue: CYGSEM_HAL_VIRTUAL_VECTOR_INIT_WHOLE_TABLE || CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGBLD_BUILD_COMMON_GDB_STUBS # Requires: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGPKG_HAL_GDB_FILEIO # Requires: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGHWR_HAL_ARM_DUMP_EXCEPTIONS # Requires: !CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGHWR_HAL_ARM_ICE_THREAD_SUPPORT # Requires: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # option CYGBLD_BUILD_GDB_STUBS # Requires: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS};# Support for external break support in GDB stubs# The HAL implements external break (or asynchronous interrupt)# in the GDB stubs for the target.#cdl_interface CYGINT_HAL_DEBUG_GDB_STUBS_BREAK { # Implemented by CYGPKG_HAL_ARM_GPS4020, active, enabled # This value cannot be modified here. # Flavor: data # Current_value: 1 # The following properties are affected by this value # option CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT # ActiveIf: CYGINT_HAL_DEBUG_GDB_STUBS_BREAK};# Include GDB external break support for stubs# This option causes the GDB stub to add a serial interrupt handler# which will listen for GDB break packets. This lets you stop the# target asynchronously when using GDB, usually by hitting Control+C# or pressing the STOP button. This option differs from# CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT in that it is used when# GDB stubs are present.#cdl_option CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT { # ActiveIf constraint: CYGINT_HAL_DEBUG_GDB_STUBS_BREAK # CYGINT_HAL_DEBUG_GDB_STUBS_BREAK == 1 # --> 1 # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 0 # value_source default # Default value: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS == 0 # --> 0 # Requires: CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS == 0 # --> 0 # The following properties are affected by this value # option CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT # Requires: !CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT # option CYGOPT_HAL_ARM_SYSCALL_GPROF_SUPPORT # ActiveIf: CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT || CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT # option CYGBLD_BUILD_GDB_STUBS # Requires: CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT};# Platform does not support CTRLC#cdl_interface CYGINT_HAL_DEBUG_GDB_CTRLC_UNSUPPORTED { # No options implement this inferface # This value cannot be modified here. # Flavor: data # Current_value: 0 # The following properties are affected by this value # option CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT # ActiveIf: CYGINT_HAL_DEBUG_GDB_CTRLC_UNSUPPORTED == 0 };# Include GDB external break support when no stubs# This option adds an interrupt handler for the GDB serial line# which will listen for GDB break packets. This lets you stop the# target asynchronously when using GDB, usually by hitting Control+C# or pressing the STOP button. This option differs from# CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT in that it is used when the GDB# stubs are NOT present.#cdl_option CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT { # ActiveIf constraint: CYGSEM_HAL_USE_ROM_MONITOR || CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # CYGSEM_HAL_USE_ROM_MONITOR == GDB_stubs # CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS == 0 # --> 1 # ActiveIf constraint: CYGINT_HAL_DEBUG_GDB_CTRLC_UNSUPPORTED == 0 # CYGINT_HAL_DEBUG_GDB_CTRLC_UNSUPPORTED == 0 # --> 1 # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 1 # value_source default # Default value: !CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS # CYGDBG_HAL_DEBUG_GDB_INCLUDE_STUBS == 0 # --> 1 # Requires: !CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT # CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT == 0 # --> 1 # The following properties are affected by this value # option CYGOPT_HAL_ARM_SYSCALL_GPROF_SUPPORT # ActiveIf: CYGDBG_HAL_DEBUG_GDB_CTRLC_SUPPORT || CYGDBG_HAL_DEBUG_GDB_BREAK_SUPPORT };# Include GDB multi-threading debug support# This option enables some extra HAL code which is needed# to support multi-threaded source level debugging.#cdl_option CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT { # ActiveIf constraint: CYGSEM_HAL_ROM_MONITOR || CYGDBG_KERNEL_DEBUG_GDB_THREAD_SUPPORT # CYGSEM_HAL_ROM_MONITOR == 0 # CYGDBG_KERNEL_DEBUG_GDB_THREAD_SUPPORT == 1 # --> 1 # Flavor: bool # No user value, uncomment the following line to provide one. # user_value 1 # value_source default # Default value: 1 # The following properties are affected by this value # option CYGDBG_KERNEL_DEBUG_GDB_THREAD_SUPPORT # Requires: CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT # option CYGHWR_HAL_ARM_ICE_THREAD_SUPPORT # Requires: CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT # option CYGBLD_BUILD_GDB_STUBS # Requires: CYGDBG_HAL_DEBUG_GDB_THREAD_SUPPORT};# Number of times to retry sending a $O packet# This option controls the number of attempts that eCos programs# will make to send a $O packet to a host GDB process. If it is# set non-zero, then the target process will attempt to resend the# $O packet data up to this number of retries. Caution: use of# this option is not recommended as it can thoroughly confuse the# host GDB process.#cdl_option CYGNUM_HAL_DEBUG_GDB_PROTOCOL_RETRIES { # Flavor: data # No user value, uncomment the following line to provide one.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -