7d5c9fa7a9
Starting with commit b9b43a0eb772a464bba13833d11e3a31fbf4e09e, printk() messages are handled by the logging subsystem. This can cause trouble in watchdog related samples if the deferred logging mode is used (and currently it is by default), because those samples are ended by a reset and some messages may not get a chance to be outputted. Since the same problem concerns also the ordinary logging messages that may be produced during execution of the samples, this commit fixes it by switching to the immediate logging mode, not by just disabling the LOG_PRINTK option. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
12 lines
189 B
Plaintext
12 lines
189 B
Plaintext
CONFIG_LOG=y
|
|
CONFIG_LOG_MODE_IMMEDIATE=y
|
|
|
|
CONFIG_WATCHDOG=y
|
|
CONFIG_WDT_LOG_LEVEL_DBG=y
|
|
CONFIG_WDT_DISABLE_AT_BOOT=y
|
|
|
|
CONFIG_TASK_WDT=y
|
|
CONFIG_TASK_WDT_MIN_TIMEOUT=500
|
|
|
|
CONFIG_THREAD_NAME=y
|