pw_log_zephyr#
Overview#
This interrupt backend implements the pw_log facade. Currently, two
separate Pigweed backends are implemented. One that uses the plain Zephyr
logging framework and routes Pigweed’s logs to Zephyr. While another maps
the Zephyr logging macros to Pigweed’s tokenized logging.
Using Zephyr logging#
To enable, set CONFIG_PIGWEED_LOG_ZEPHYR=y. After that, logging can be
controlled via the standard Kconfig options. All logs made through
PW_LOG_* are logged to the Zephyr logging module pigweed. In this
model, the Zephyr logging is set as pw_log’s backend.
Using Pigweed tokenized logging#
Using the pigweed logging can be done by enabling
CONFIG_PIGWEED_LOG_TOKENIZED=y. At that point pw_log_tokenized is set
as the backend for pw_log and all Zephyr logs are routed to Pigweed’s
logging facade. This means that any logging statements made in Zephyr itself
are also tokenized.
When enabled, a few extra configurations are available to control the tokenized
metadata bits such as log level bits, line number bits, custom flag bits, and
module string bits.
The log format string may also be modified by defining your own PW_LOG_TOKENIZED_FORMAT_STRING.
This can be done in your cmake by including your own header that defines it.
add_library(log_tokenized_config INTERFACE)
target_compile_options(log_tokenized_config INTERFACE -include header_file_that_sets_that_macro.h)
pw_set_module_config(pw_log_tokenized_CONFIG log_tokenized_config)
Setting the log level#
In order to remain compatible with existing Pigweed code, the logging backend
respects PW_LOG_LEVEL. If set, the backend will translate the Pigweed log
levels to their closest Zephyr counterparts:
Pigweed |
Zephyr |
|---|---|
|
|
|
|
|
|
|
|
Alternatively, it is also possible to set the Zephyr logging level directly via
CONFIG_PIGWEED_LOG_LEVEL.