mirror of
https://github.com/espressif/esp-idf.git
synced 2024-10-05 20:47:46 -04:00
628b633e50
Closes https://github.com/espressif/esp-idf/issues/11049 Closes https://github.com/espressif/esp-idf/pull/11057 Signed-off-by: KonstantinKondrashov <konstantin@espressif.com> Result from an example in 11057: When this option is not enabled: 1000 iterations took 10914 microseconds (10.9 microseconds per invocation) 1000 iterations took 10909 microseconds (10.9 microseconds per invocation) When this option is enabled: 1000 iterations took 10960 microseconds (10.9 microseconds per invocation) 1000 iterations took 107 microseconds (0.1 microseconds per invocation)
138 lines
5.4 KiB
Plaintext
138 lines
5.4 KiB
Plaintext
menu "Log output"
|
|
|
|
choice LOG_DEFAULT_LEVEL
|
|
bool "Default log verbosity"
|
|
default LOG_DEFAULT_LEVEL_INFO
|
|
help
|
|
Specify how much output to see in logs by default.
|
|
You can set lower verbosity level at runtime using
|
|
esp_log_level_set function.
|
|
|
|
By default, this setting limits which log statements
|
|
are compiled into the program. For example, selecting
|
|
"Warning" would mean that changing log level to "Debug"
|
|
at runtime will not be possible. To allow increasing log
|
|
level above the default at runtime, see the next option.
|
|
|
|
config LOG_DEFAULT_LEVEL_NONE
|
|
bool "No output"
|
|
config LOG_DEFAULT_LEVEL_ERROR
|
|
bool "Error"
|
|
config LOG_DEFAULT_LEVEL_WARN
|
|
bool "Warning"
|
|
config LOG_DEFAULT_LEVEL_INFO
|
|
bool "Info"
|
|
config LOG_DEFAULT_LEVEL_DEBUG
|
|
bool "Debug"
|
|
config LOG_DEFAULT_LEVEL_VERBOSE
|
|
bool "Verbose"
|
|
endchoice
|
|
|
|
config LOG_DEFAULT_LEVEL
|
|
int
|
|
default 0 if LOG_DEFAULT_LEVEL_NONE
|
|
default 1 if LOG_DEFAULT_LEVEL_ERROR
|
|
default 2 if LOG_DEFAULT_LEVEL_WARN
|
|
default 3 if LOG_DEFAULT_LEVEL_INFO
|
|
default 4 if LOG_DEFAULT_LEVEL_DEBUG
|
|
default 5 if LOG_DEFAULT_LEVEL_VERBOSE
|
|
|
|
choice LOG_MAXIMUM_LEVEL
|
|
bool "Maximum log verbosity"
|
|
default LOG_MAXIMUM_EQUALS_DEFAULT
|
|
help
|
|
This config option sets the highest log verbosity that it's possible to select
|
|
at runtime by calling esp_log_level_set(). This level may be higher than
|
|
the default verbosity level which is set when the app starts up.
|
|
|
|
This can be used enable debugging output only at a critical point, for a particular
|
|
tag, or to minimize startup time but then enable more logs once the firmware has
|
|
loaded.
|
|
|
|
Note that increasing the maximum available log level will increase the firmware
|
|
binary size.
|
|
|
|
This option only applies to logging from the app, the bootloader log level is
|
|
fixed at compile time to the separate "Bootloader log verbosity" setting.
|
|
|
|
config LOG_MAXIMUM_EQUALS_DEFAULT
|
|
bool "Same as default"
|
|
config LOG_MAXIMUM_LEVEL_ERROR
|
|
bool "Error"
|
|
depends on LOG_DEFAULT_LEVEL < 1
|
|
config LOG_MAXIMUM_LEVEL_WARN
|
|
bool "Warning"
|
|
depends on LOG_DEFAULT_LEVEL < 2
|
|
config LOG_MAXIMUM_LEVEL_INFO
|
|
bool "Info"
|
|
depends on LOG_DEFAULT_LEVEL < 3
|
|
config LOG_MAXIMUM_LEVEL_DEBUG
|
|
bool "Debug"
|
|
depends on LOG_DEFAULT_LEVEL < 4
|
|
config LOG_MAXIMUM_LEVEL_VERBOSE
|
|
bool "Verbose"
|
|
depends on LOG_DEFAULT_LEVEL < 5
|
|
endchoice
|
|
|
|
config LOG_MAXIMUM_LEVEL
|
|
int
|
|
default LOG_DEFAULT_LEVEL if LOG_MAXIMUM_EQUALS_DEFAULT
|
|
default 0 if LOG_MAXIMUM_LEVEL_NONE
|
|
default 1 if LOG_MAXIMUM_LEVEL_ERROR
|
|
default 2 if LOG_MAXIMUM_LEVEL_WARN
|
|
default 3 if LOG_MAXIMUM_LEVEL_INFO
|
|
default 4 if LOG_MAXIMUM_LEVEL_DEBUG
|
|
default 5 if LOG_MAXIMUM_LEVEL_VERBOSE
|
|
|
|
config LOG_MASTER_LEVEL
|
|
bool "Enable global master log level"
|
|
default "n"
|
|
help
|
|
Enables an additional global "master" log level check that occurs
|
|
before a log tag cache lookup. This is useful if you want to
|
|
compile in a lot of logs that are selectable at runtime, but avoid the
|
|
performance hit during periods where you don't want log output. Examples
|
|
include remote log forwarding, or disabling logs during a time-critical
|
|
or CPU-intensive section and re-enabling them later. Results in
|
|
larger program size depending on number of logs compiled in.
|
|
|
|
If enabled, defaults to LOG_DEFAULT_LEVEL and can be set using
|
|
esp_log_set_level_master().
|
|
This check takes precedence over ESP_LOG_LEVEL_LOCAL.
|
|
|
|
config LOG_COLORS
|
|
bool "Use ANSI terminal colors in log output"
|
|
default "y"
|
|
help
|
|
Enable ANSI terminal color codes in bootloader output.
|
|
|
|
In order to view these, your terminal program must support ANSI color codes.
|
|
|
|
choice LOG_TIMESTAMP_SOURCE
|
|
prompt "Log Timestamps"
|
|
default LOG_TIMESTAMP_SOURCE_RTOS
|
|
help
|
|
Choose what sort of timestamp is displayed in the log output:
|
|
|
|
- Milliseconds since boot is calulated from the RTOS tick count multiplied
|
|
by the tick period. This time will reset after a software reboot.
|
|
e.g. (90000)
|
|
|
|
- System time is taken from POSIX time functions which use the chip's
|
|
RTC and high resoultion timers to maintain an accurate time. The system time is
|
|
initialized to 0 on startup, it can be set with an SNTP sync, or with
|
|
POSIX time functions. This time will not reset after a software reboot.
|
|
e.g. (00:01:30.000)
|
|
|
|
- NOTE: Currently this will not get used in logging from binary blobs
|
|
(i.e WiFi & Bluetooth libraries), these will always print
|
|
milliseconds since boot.
|
|
|
|
config LOG_TIMESTAMP_SOURCE_RTOS
|
|
bool "Milliseconds Since Boot"
|
|
config LOG_TIMESTAMP_SOURCE_SYSTEM
|
|
bool "System Time"
|
|
endchoice
|
|
|
|
endmenu
|