mirror
/
esp-idf
kopia lustrzana https://github.com/espressif/esp-idf
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność
esp-idf/components/freertos/Kconfig

227 wiersze
8.2 KiB
Plaintext
Czysty Zwykły widok Historia

Initial public version
2016-08-17 15:08:22 +00:00
menu "FreeRTOS"
# This is actually also handled in the ESP32 startup code, not only in FreeRTOS.
config FREERTOS_UNICORE
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Run FreeRTOS only on first core"
freertos: enable dual core by default
2016-12-22 05:37:07 +00:00
default n
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
help
This version of FreeRTOS normally takes control of all cores of
the CPU. Select this if you only want to start it on the first core.
This is needed when e.g. another process needs complete control
over the second core.
Initial public version
2016-08-17 15:08:22 +00:00
choice FREERTOS_CORETIMER
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
prompt "Xtensa timer to use as the FreeRTOS tick source"
default CONFIG_FREERTOS_CORETIMER_0
help
FreeRTOS needs a timer with an associated interrupt to use as
the main tick source to increase counters, run timers and do
pre-emptive multitasking with. There are multiple timers available
to do this, with different interrupt priorities. Check
Initial public version
2016-08-17 15:08:22 +00:00
config FREERTOS_CORETIMER_0
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Timer 0 (int 6, level 1)"
help
Select this to use timer 0
Initial public version
2016-08-17 15:08:22 +00:00
config FREERTOS_CORETIMER_1
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Timer 1 (int 15, level 3)"
help
Select this to use timer 1
Initial public version
2016-08-17 15:08:22 +00:00
endchoice
config FREERTOS_HZ
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
int "Tick rate (Hz)"
FreeRTOS KConfig: Limit tick rate to 1000Hz >1000Hz breaks portTICK_PERIOD_MS (see gitlab 4) A working >1000Hz tick rate is possible with some changes, but beyond a certain point it's dimishing returns to preempt tasks this often.
2016-10-05 23:06:01 +00:00
range 1 1000
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
default 100
help
Select the tick rate at which FreeRTOS does pre-emptive context switching.
Initial public version
2016-08-17 15:08:22 +00:00
Add UNTESTED_FUNCTION() call to untested functions, make Kconfig option to enable that to map to assert()
2016-09-27 03:36:30 +00:00
config FREERTOS_ASSERT_ON_UNTESTED_FUNCTION
bool "Halt when an SMP-untested function is called"
default y
help
Some functions in FreeRTOS have not been thoroughly tested yet when moving to
the SMP implementation of FreeRTOS. When this option is enabled, these fuctions
will throw an assert().
Initial public version
2016-08-17 15:08:22 +00:00
choice FREERTOS_CHECK_STACKOVERFLOW
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
prompt "Check for stack overflow"
FreeRTOS: Default to canary byte stack overflow checking Was mistakenly "none" due to name change not being propagated. Closes github issue #181: https://github.com/espressif/esp-idf/issues/181
2016-12-22 03:47:14 +00:00
default FREERTOS_CHECK_STACKOVERFLOW_CANARY
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
help
FreeRTOS can check for stack overflows in threads and trigger an user function
called vApplicationStackOverflowHook when this happens.
Initial public version
2016-08-17 15:08:22 +00:00
config FREERTOS_CHECK_STACKOVERFLOW_NONE
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "No checking"
help
Do not check for stack overflows (configCHECK_FOR_STACK_OVERFLOW=0)
Initial public version
2016-08-17 15:08:22 +00:00
config FREERTOS_CHECK_STACKOVERFLOW_PTRVAL
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Check by stack pointer value"
help
Check for stack overflows on each context switch by checking if
the stack pointer is in a valid range. Quick but does not detect
stack overflows that happened between context switches
(configCHECK_FOR_STACK_OVERFLOW=1)
Initial public version
2016-08-17 15:08:22 +00:00
config FREERTOS_CHECK_STACKOVERFLOW_CANARY
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Check using canary bytes"
help
Places some magic bytes at the end of the stack area and on each
context switch, check if these bytes are still intact. More thorough
than just checking the pointer, but also slightly slower.
(configCHECK_FOR_STACK_OVERFLOW=2)
Initial public version
2016-08-17 15:08:22 +00:00
endchoice
freertos: Move the "set debug watchpoint as stack overflow check" out of debugging internals Place it near the other stack overflow kconfig items, instead.
2017-02-27 00:49:46 +00:00
config FREERTOS_WATCHPOINT_END_OF_STACK
bool "Set a debug watchpoint as a stack overflow check"
default n
help
FreeRTOS can check if a stack has overflown its bounds by checking either the value of
the stack pointer or by checking the integrity of canary bytes. (See FREERTOS_CHECK_STACKOVERFLOW
for more information.) These checks only happen on a context switch, and the situation that caused
the stack overflow may already be long gone by then. This option will use the debug memory
watchpoint 1 (the second one) to allow breaking into the debugger (or panic'ing) as soon as any
of the last 32 bytes on the stack of a task are overwritten. The side effect is that using gdb, you
effectively only have one watchpoint; the 2nd one is overwritten as soon as a task switch happens.
This check only triggers if the stack overflow writes within 4 bytes of the end of the stack, rather than
overshooting further, so it is worth combining this approach with one of the other stack overflow check methods.
When this watchpoint is hit, gdb will stop with a SIGTRAP message. When no OCD is attached, esp-idf
will panic on an unhandled debug exception.
'Merge branch 'thread_local_storage_delete_callbacks' into 'master' The thread-local-storage feature in FreeRTOS attaches an application-usable array of pointers to a thread control block. These pointers usually point to a structure the thread allocates. When a thread gets (voluntarily or involuntarily) destroyed, this memory can leak. This merge adds a matching second array of user-settable pointers to destructor routines. As soon as the task gets cleaned up (which happens in the idle thread), the destructors get called and the memory can be freed. See merge request !19
2016-08-24 05:29:06 +00:00
config FREERTOS_THREAD_LOCAL_STORAGE_POINTERS
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
int "Amount of thread local storage pointers"
range 0 256 if !WIFI_ENABLED
range 1 256 if WIFI_ENABLED
default 1
help
FreeRTOS has the ability to store per-thread pointers in the task
control block. This controls the amount of pointers available;
0 turns off this functionality.
Initial public version
2016-08-17 15:08:22 +00:00
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
If using the WiFi stack, this value must be at least 1.
FreeRTOS thread local storage config: If using WiFi this must be >0
2016-09-06 01:15:28 +00:00
FreeRTOS: Configure configASSERT fail behaviour, abort() by default
2016-08-24 08:01:41 +00:00
choice FREERTOS_ASSERT
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
prompt "FreeRTOS assertions"
default FREERTOS_ASSERT_FAIL_ABORT
help
Failed FreeRTOS configASSERT() assertions can be configured to
behave in different ways.
FreeRTOS: Configure configASSERT fail behaviour, abort() by default
2016-08-24 08:01:41 +00:00
config FREERTOS_ASSERT_FAIL_ABORT
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "abort() on failed assertions"
help
If a FreeRTOS configASSERT() fails, FreeRTOS will abort() and
halt execution. The panic handler can be configured to handle
the outcome of an abort() in different ways.
FreeRTOS: Configure configASSERT fail behaviour, abort() by default
2016-08-24 08:01:41 +00:00
config FREERTOS_ASSERT_FAIL_PRINT_CONTINUE
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Print and continue failed assertions"
help
If a FreeRTOS assertion fails, print it out and continue.
FreeRTOS: Configure configASSERT fail behaviour, abort() by default
2016-08-24 08:01:41 +00:00
config FREERTOS_ASSERT_DISABLE
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Disable FreeRTOS assertions"
help
FreeRTOS configASSERT() will not be compiled into the binary.
FreeRTOS: Configure configASSERT fail behaviour, abort() by default
2016-08-24 08:01:41 +00:00
endchoice
Initial public version
2016-08-17 15:08:22 +00:00
Add symbol needed for OpenOCD to detect FreeRTOS, add feature to break execution when the scheduler is initially started.
2016-08-24 04:23:58 +00:00
config FREERTOS_BREAK_ON_SCHEDULER_START_JTAG
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Stop program on scheduler start when JTAG/OCD is detected"
Fix int wdt iram, fix some fallout of moving panic stuff to esp32
2016-10-28 04:05:42 +00:00
depends on ESP32_DEBUG_OCDAWARE
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
default y
help
If JTAG/OCD is connected, stop execution when the scheduler is started and the first
task is executed.
Initial public version
2016-08-17 15:08:22 +00:00
FreeRTOS: temporary solution for memory canaries and memory debug 1. This is just a temporary solution, it will be removed when umm_malloc is ready 2. Support memory canaries mechanism 2. Add debug code to show allocated memory info
2016-09-07 13:52:24 +00:00
menuconfig ENABLE_MEMORY_DEBUG
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Enable heap memory debug"
default n
help
Enable this option to show malloc heap block and memory crash detect
FreeRTOS: temporary solution for memory canaries and memory debug 1. This is just a temporary solution, it will be removed when umm_malloc is ready 2. Support memory canaries mechanism 2. Add debug code to show allocated memory info
2016-09-07 13:52:24 +00:00
Merge latest master in
2016-10-27 08:18:55 +00:00
config FREERTOS_ISR_STACKSIZE
int "ISR stack size"
range 1536 32768
default 1536
help
The interrupt handlers have their own stack. The size of the stack can be defined here.
Each processor has its own stack, so the total size occupied will be twice this.
Add a more scalable mechanism for the FreeRTOS tick- and idle hooks; idle handler now uses WAITI to reduce power
2016-11-11 11:20:54 +00:00
config FREERTOS_LEGACY_HOOKS
bool "Use FreeRTOS legacy hooks"
default n
help
FreeRTOS offers a number of hooks/callback functions that are called when a timer
tick happens, the idle thread runs etc. esp-idf replaces these by runtime registerable
hooks using the esp_register_freertos_xxx_hook system, but for legacy reasons the old
hooks can also still be enabled. Please enable this only if you have code that for some
reason can't be migrated to the esp_register_freertos_xxx_hook system.
if FREERTOS_LEGACY_HOOKS
config FREERTOS_LEGACY_IDLE_HOOK
bool "Enable legacy idle hook"
default n
help
If enabled, FreeRTOS will call a function called vApplicationIdleHook when the idle thread
on a CPU is running. Please make sure your code defines such a function.
config FREERTOS_LEGACY_TICK_HOOK
bool "Enable legacy tick hook"
default n
help
If enabled, FreeRTOS will call a function called vApplicationTickHook when a FreeRTOS
tick is executed. Please make sure your code defines such a function.
endif #FREERTOS_LEGACY_HOOKS
FreeRTOS: Support setting task name max length Ref: https://esp32.com/viewtopic.php?f=13&t=1297&p=5762
2017-02-27 00:46:16 +00:00
config FREERTOS_MAX_TASK_NAME_LEN
int "Maximum task name length"
range 1 256
default 16
help
Changes the maximum task name length. Each task allocated will
include this many bytes for a task name. Using a shorter value
saves a small amount of RAM, a longer value allows more complex
names.
For most uses, the default of 16 is OK.
Add a more scalable mechanism for the FreeRTOS tick- and idle hooks; idle handler now uses WAITI to reduce power
2016-11-11 11:20:54 +00:00
FreeRTOS: Convert portMUX_DEBUG to a configuration item
2016-08-25 08:30:47 +00:00
menuconfig FREERTOS_DEBUG_INTERNALS
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Debug FreeRTOS internals"
default n
help
Enable this option to show the menu with internal FreeRTOS debugging features.
This option does not change any code by itself, it just shows/hides some options.
FreeRTOS: Convert portMUX_DEBUG to a configuration item
2016-08-25 08:30:47 +00:00
if FREERTOS_DEBUG_INTERNALS
config FREERTOS_PORTMUX_DEBUG
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Debug portMUX portENTER_CRITICAL/portEXIT_CRITICAL"
depends on FREERTOS_DEBUG_INTERNALS
default n
help
If enabled, debug information (including integrity checks) will be printed
to UART for the port-specific MUX implementation.
FreeRTOS: Convert portMUX_DEBUG to a configuration item
2016-08-25 08:30:47 +00:00
lwip/freertos/esp32: add throughput optimization related code 1. Update wifi lib which contains ampdu and other optimizations 2. Add throughput code debug code 3. Other misc modification about throughput optimization
2017-01-02 12:03:10 +00:00
if !FREERTOS_UNICORE
FreeRTOS: Convert portMUX_DEBUG to a configuration item
2016-08-25 08:30:47 +00:00
config FREERTOS_PORTMUX_DEBUG_RECURSIVE
Kconfig: use 4 spaces to instead 1 tab In some Kconfig file, both 4 spaces and 1 tab are used mix, let's just use 4 space, it will be clean in some editor.
2016-09-28 05:24:58 +00:00
bool "Debug portMUX Recursion"
depends on FREERTOS_PORTMUX_DEBUG
default n
help
If enabled, additional debug information will be printed for recursive
portMUX usage.
lwip/freertos/esp32: add throughput optimization related code 1. Update wifi lib which contains ampdu and other optimizations 2. Add throughput code debug code 3. Other misc modification about throughput optimization
2017-01-02 12:03:10 +00:00
endif #FREERTOS_UNICORE
FreeRTOS: Convert portMUX_DEBUG to a configuration item
2016-08-25 08:30:47 +00:00
endif # FREERTOS_DEBUG_INTERNALS
Initial public version
2016-08-17 15:08:22 +00:00
endmenu