79e6b0e0f6
As of today <zephyr/zephyr.h> is 100% equivalent to <zephyr/kernel.h>. This patch proposes to then include <zephyr/kernel.h> instead of <zephyr/zephyr.h> since it is more clear that you are including the Kernel APIs and (probably) nothing else. <zephyr/zephyr.h> sounds like a catch-all header that may be confusing. Most applications need to include a bunch of other things to compile, e.g. driver headers or subsystem headers like BT, logging, etc. The idea of a catch-all header in Zephyr is probably not feasible anyway. Reason is that Zephyr is not a library, like it could be for example `libpython`. Zephyr provides many utilities nowadays: a kernel, drivers, subsystems, etc and things will likely grow. A catch-all header would be massive, difficult to keep up-to-date. It is also likely that an application will only build a small subset. Note that subsystem-level headers may use a catch-all approach to make things easier, though. NOTE: This patch is **NOT** removing the header, just removing its usage in-tree. I'd advocate for its deprecation (add a #warning on it), but I understand many people will have concerns. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| README.rst | ||
| prj.conf | ||
| 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...