zephyr

History

Andrzej Głąbek bc26629ba8 dts: nrf: Rename "nordic,nrf-watchdog" compatible to "nordic,nrf-wdt" For consistency with the scheme used for other nRF peripherals, use the peripheral name that nRF Product Specifications use. In this case, it is WDT, not WATCHDOG. Also remove the requirement for the label property in the binding. It is no longer needed. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>		2022-04-02 15:14:38 +02:00
..
src	dts: nrf: Rename "nordic,nrf-watchdog" compatible to "nordic,nrf-wdt"	2022-04-02 15:14:38 +02:00
CMakeLists.txt
prj.conf	samples: task_wdt: Increase min watchdog timeout	2022-02-09 14:07:26 -06:00
README.rst
sample.yaml

README.rst

.. _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...