ad0e3a40e8
Use the actual minimum timeout used by the sample for task watchdog channels (100 ms) as the configuration value for the fallback hardware watchdog, to avoid unnecessary executions of the timer handler. Add missing indentation in the documentation of the sample so that the console output is rendered correctly. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>
49 lines
1.2 KiB
ReStructuredText
49 lines
1.2 KiB
ReStructuredText
.. _task_wdt_sample:
|
|
|
|
Task Watchdog Sample
|
|
####################
|
|
|
|
Overview
|
|
********
|
|
|
|
This sample allows to test the task watchdog subsystem.
|
|
|
|
Building and Running
|
|
********************
|
|
|
|
It should be possible to build and run the task watchdog sample on almost any
|
|
board. If a hardware watchdog is defined in the devicetree, it is used as a
|
|
fallback. Otherwise the task watchdog will run independently.
|
|
|
|
Building and Running for ST Nucleo L073RZ
|
|
=========================================
|
|
The sample can be built and executed for the
|
|
:ref:`nucleo_l073rz_board` as follows:
|
|
|
|
.. zephyr-app-commands::
|
|
:zephyr-app: samples/subsys/task_wdt
|
|
:board: nucleo_l073rz
|
|
:goals: build flash
|
|
:compact:
|
|
|
|
For other boards just replace the board name.
|
|
|
|
Sample output
|
|
=============
|
|
|
|
The following output is printed and continuously repeated (after each
|
|
reset):
|
|
|
|
.. code-block:: console
|
|
|
|
Task watchdog sample application.
|
|
Main thread still alive...
|
|
Control thread started.
|
|
Main thread still alive...
|
|
Main thread still alive...
|
|
Main thread still alive...
|
|
Control thread getting stuck...
|
|
Main thread still alive...
|
|
Task watchdog channel 1 callback, thread: control
|
|
Resetting device...
|