| /Zephyr-Core-3.7.0/drivers/watchdog/ |
| D | Kconfig | 1 # Watchdog configuration options
7 menuconfig WATCHDOG config
8 bool "Watchdog drivers"
12 if WATCHDOG
21 Disable watchdog at Zephyr system startup.
24 module-str = watchdog
34 Enable multistage operation of watchdog timeouts.
37 bool "Counter based watchdog"
42 Watchdog emulated with counter device. If counter device supports using
44 that context. This watchdog can be used along hardware watchdog to
[all …]
|
| D | Kconfig.nxp_fs26 | 5 bool "NXP FS26 SBC watchdog driver"
11 Enable the NXP FS26 SBC watchdog driver.
23 int "Watchdog error counter limit"
26 Sets the maximum value of the watchdog error counter. Each time a
27 watchdog failure occurs, the device increments this counter by 2. The
28 watchdog error counter is decremented by 1 each time the watchdog is
34 int "Watchdog refresh counter limit"
37 Sets the maximum value of the watchdog refresh counter. Each time the
38 watchdog is properly refreshed, this counter is incremented by 1. Each
41 there is a bad watchdog refresh, this counter is reset to 0.
[all …]
|
| D | Kconfig.it8xxx2 | 5 bool "ITE it8xxx2 Watchdog Timer (WDT) driver"
10 This option enables the Watchdog Timer driver for ITE it8xxx2.
15 int "Number of ms before generating watchdog event/signal"
19 This option defines the window in which a watchdog event must be
20 handled. After this time window, the watchdog reset triggers
27 Once warning timer triggered, if watchdog timer isn't reloaded,
29 more warning messages before watchdog reset.
|
| D | Kconfig.npcx | 7 bool "Nuvoton NPCX embedded controller (EC) Watchdog Timer driver"
12 This option enables the Watchdog Timer driver for NPCX family of
14 Say y if you wish to use watchdog on NPCX MCU.
17 int "Milliseconds before generating watchdog event/signal"
21 This option defines the window in which a watchdog event must be
22 handled. After this time window, the watchdog reset triggers
|
| D | wdt_npcx.c | 11 * @brief Nuvoton NPCX watchdog modules driver
13 * This file contains the drivers of NPCX Watchdog module that generates the
15 * system. It also provides watchdog reset signal generation in response to a
25 * +--->| Watchdog Prescale |--->| 8-Bit Watchdog |-----> Watchdog Event/Reset
37 #include <zephyr/drivers/watchdog.h>
45 /* Watchdog operating frequency is fixed to LFCLK (32.768) kHz */
49 * Maximum watchdog window time. Keep the timer and watchdog clock prescaler
50 * (TWCP) to 0x5. Since the watchdog counter is 8-bits, maximum time supported
51 * by npcx watchdog is 256 * (32 * 32768) / 32768 = 8192 sec.
53 * Thus, the maximum time of watchdog set here is 64 sec.
[all …]
|
| D | wdt_dw_common.h | 14 * @brief Check watchdog configuration options
16 * Check options value passed to a watchdog setup function. Returns error if unsupported option
19 * @param options options value passed to a watchdog setup function.
25 * @brief Configure watchdog device
37 * @param [in]clk_freq frequency of a clock used by watchdog device
38 * @param [in]config pointer to a watchdog configuration structure
47 * @brief Watchdog probe
52 * @param reset_pulse_length Length of a reset pulse produced by watchdog
58 * @brief Watchdog disable function
|
| D | wdt_cmsdk_apb.c | 10 * @brief Driver for CMSDK APB Watchdog.
16 #include <zephyr/drivers/watchdog.h>
21 /* offset: 0x000 (r/w) watchdog load register */
23 /* offset: 0x004 (r/ ) watchdog value register */
25 /* offset: 0x008 (r/w) watchdog control register */
27 /* offset: 0x00c ( /w) watchdog clear interrupt register */
29 /* offset: 0x010 (r/ ) watchdog raw interrupt status register */
31 /* offset: 0x014 (r/ ) watchdog interrupt status register */
34 /* offset: 0xc00 (r/w) watchdog lock register */
37 /* offset: 0xf00 (r/w) watchdog integration test control register */
[all …]
|
| D | wdt_sam.c | 10 * @brief Watchdog (WDT) Driver for Atmel SAM MCUs
13 * - Once the watchdog disable bit is set, it cannot be cleared till next
14 * power reset, i.e, the watchdog cannot be started once stopped.
16 * is set default at boot and watchdog module is disabled in the MCU for
17 * systems that don't need watchdog functionality.
18 * - If the application needs to use the watchdog in the system, then
22 #include <zephyr/drivers/watchdog.h>
61 * @brief Calculates the watchdog counter value (WDV)
62 * to be installed in the watchdog timer
90 /* since Watchdog mode register is 'write-once', we can't disable if in wdt_sam_disable()
[all …]
|
| D | Kconfig.npm6001 | 5 bool "nPM6001 Watchdog driver"
11 Enable nPM6001 Watchdog driver
14 int "nPM6001 Watchdog driver initialization priority"
18 Initialization priority for the nPM6001 Watchdog driver.
|
| D | Kconfig.smartbond | 1 # Smartbond watchdog driver config
7 bool "Watchdog Driver for Smartbond family of MCUs"
12 Enable watchdog driver for Smartbond line of MCUs
20 Watchdog timer generates NMI at value 0, and WDOG (SYS)
24 Watchdog timer generates a WDOG (SYS)
|
| D | Kconfig.npm1300 | 5 bool "nPM1300 Watchdog driver"
11 Enable nPM1300 Watchdog driver
14 int "nPM1300 Watchdog driver initialization priority"
18 Initialization priority for the nPM1300 Watchdog driver.
|
| /Zephyr-Core-3.7.0/subsys/task_wdt/ |
| D | Kconfig | 1 # Software watchdog configuration
7 bool "Task-level software watchdog"
10 Enable task watchdog
12 The task watchdog allows to have individual watchdog channels
13 per thread, even if the hardware supports only a single watchdog.
17 int "Maximum number of task watchdog channels"
25 bool "Use hardware watchdog as a fallback"
28 This option allows to specify a hardware watchdog device in the
30 watchdog itself gets stuck.
33 int "Minimum timeout for task watchdog (ms)"
[all …]
|
| D | task_wdt_shell.c | 23 shell_fprintf(sh, SHELL_INFO, "Init task watchdog ...\n"); in cmd_init()
28 shell_fprintf(sh, SHELL_ERROR, "Failed to init task watchdog: %d\n", ret); in cmd_init()
42 shell_fprintf(sh, SHELL_INFO, "Add task watchdog channel\n"); in cmd_add()
49 shell_fprintf(sh, SHELL_ERROR, "Failed to add task watchdog channel: %d\n", ret); in cmd_add()
53 shell_fprintf(sh, SHELL_INFO, "Task watchdog channel: %d\n", ret); in cmd_add()
70 shell_fprintf(sh, SHELL_INFO, "Feed task watchdog channel %s\n", argv[1]); in cmd_feed()
75 shell_fprintf(sh, SHELL_ERROR, "Failed to add task watchdog channel: %d\n", ret); in cmd_feed()
89 shell_fprintf(sh, SHELL_INFO, "Delete task watchdog channel %s\n", argv[1]); in cmd_del()
94 shell_fprintf(sh, SHELL_ERROR, "Failed to delete task watchdog channel: %d\n", ret); in cmd_del()
103 SHELL_CMD(init, NULL, "Initialize task watchdog", cmd_init),
[all …]
|
| /Zephyr-Core-3.7.0/samples/drivers/watchdog/ |
| D | README.rst | 1 .. zephyr:code-sample:: watchdog
2 :name: Watchdog
5 Use the watchdog driver API to reset the board when it gets stuck in an infinite loop.
10 This sample demonstrates how to use the watchdog driver API.
12 A typical use case for a watchdog is that the board is restarted in case some piece of code
18 In this sample, a watchdog callback is used to handle a timeout event once. This functionality is u…
19 restarts due to a timeout event in the watchdog driver.
21 The watchdog peripheral is configured in the board's ``.dts`` file. Make sure that the watchdog is …
31 :zephyr-app: samples/drivers/watchdog
45 Watchdog sample application
[all …]
|
| D | sample.yaml | 2 name: Watchdog Driver Sample
6 - watchdog
12 - "Watchdog sample application"
13 - "Feeding watchdog..."
15 - "Watchdog sample application"
16 depends_on: watchdog
18 sample.drivers.watchdog:
25 sample.drivers.watchdog.stm32_wwdg:
27 filter: dt_compat_enabled("st,stm32-window-watchdog")
48 sample.drivers.watchdog.stm32h7_wwdg:
[all …]
|
| /Zephyr-Core-3.7.0/tests/drivers/watchdog/wdt_basic_api/ |
| D | testcase.yaml | 2 depends_on: watchdog
5 - watchdog
7 drivers.watchdog:
9 not (CONFIG_WDT_SAM or dt_compat_enabled("st,stm32-window-watchdog")
10 or dt_compat_enabled("st,stm32-watchdog") or CONFIG_SOC_FAMILY_LPC or
22 drivers.watchdog.stm32wwdg:
23 filter: dt_compat_enabled("st,stm32-window-watchdog") or dt_compat_enabled("st,stm32-watchdog")
47 drivers.watchdog.stm32wwdg_h7:
48 filter: dt_compat_enabled("st,stm32-window-watchdog") or dt_compat_enabled("st,stm32-watchdog")
53 drivers.watchdog.stm32iwdg:
[all …]
|
| /Zephyr-Core-3.7.0/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 1 This test suite contains negative test cases for the Watchdog driver.
2 Test scenarios validate that invalid use of the watchdog driver
15 These tests were written to increase test coverage for the Watchdog driver.
16 Since, coverage data is stored in the RAM, it is lost when watchdog fires.
17 Therefore, in all test cases watchdog shall NOT expire.
18 Use other sample to verify positive scenario for the watchdog driver.
26 Tests are based on the watchdog API documentation available here:
27 https://docs.zephyrproject.org/latest/hardware/peripherals/watchdog.html
33 target that supports disabling the watchdog.
34 Multiple tests call wdt_setup() which starts the watchdog.
[all …]
|
| /Zephyr-Core-3.7.0/include/zephyr/drivers/ |
| D | watchdog.h | 12 * @brief Watchdog Interface
13 * @defgroup watchdog_interface Watchdog Interface
29 * @name Watchdog options
34 /** @brief Pause watchdog timer when CPU is in sleep state. */
37 /** @brief Pause watchdog timer when CPU is halted by the debugger. */
43 * @name Watchdog behavior flags
49 /** @brief Watchdog reset flag bit field mask shift. */
51 /** @brief Watchdog reset flag bit field mask. */
65 * @brief Watchdog timeout window.
68 * otherwise the watchdog will trigger. If the watchdog instance does not
[all …]
|
| /Zephyr-Core-3.7.0/include/zephyr/task_wdt/ |
| D | task_wdt.h | 9 * @brief Task watchdog header file
11 * This header file declares prototypes for the task watchdog APIs.
13 * The task watchdog can be used to monitor correct operation of individual
14 * threads. It can be used together with a hardware watchdog as a fallback.
25 * @brief Task Watchdog APIs
26 * @defgroup task_wdt_api Task Watchdog APIs
37 /** Task watchdog callback. */
41 * @brief Initialize task watchdog.
43 * This function sets up necessary kernel timers and the hardware watchdog (if
47 * @param hw_wdt Pointer to the hardware watchdog device used as fallback.
[all …]
|
| /Zephyr-Core-3.7.0/doc/services/task_wdt/ |
| D | index.rst | 3 Task Watchdog
9 Many microcontrollers feature a hardware watchdog timer peripheral. Its purpose
11 malfunctions. Once initialized, the watchdog timer has to be restarted ("fed")
13 and does not manage to feed the watchdog anymore, the corrective action is
17 single watchdog instance may not be sufficient anymore, as it can be used for
18 only one task. This software watchdog based on kernel timers provides a method
19 to supervise multiple threads or tasks (called watchdog channels).
21 An existing hardware watchdog can be used as an optional fallback if the task
22 watchdog itself or the scheduler has a malfunction.
24 The task watchdog uses a kernel timer as its backend. If configured properly,
[all …]
|
| /Zephyr-Core-3.7.0/dts/bindings/watchdog/ |
| D | espressif,esp32-watchdog.yaml | 5 ESP32 watchdog. ESP32 contains 3x Watchdog timers, 2x Main System Watchdog
6 Timer (MWDT), 1x RTC Watchdog Timer (RWDT). RWDT is not supported yet.
8 compatible: "espressif,esp32-watchdog"
|
| D | nxp,fs26-wdog.yaml | 5 FS26 System Basis Chip (SBC) watchdog driver.
10 watchdog counter to ensure the microcontroller is able to communicate with the
12 state. This driver covers only the watchdog functionality of FS26. The rest
23 fs26_wdt: watchdog@0 {
35 bad watchdog refresh (BAD_WD_M). The GPIO pin where the interrupt signal is
52 Watchdog type enabled on this device.
54 The Challenger watchdog monitoring feature is enabled for ASIL D devices.
57 The Simple watchdog monitoring feature is enabled for ASIL B devices. This
|
| /Zephyr-Core-3.7.0/samples/subsys/task_wdt/ |
| D | README.rst | 2 :name: Task watchdog
5 Monitor a thread using a task watchdog.
10 This sample allows to test the :ref:`task watchdog <task_wdt_api>` subsystem.
15 It should be possible to build and run the task watchdog sample on almost any
16 board. If a hardware watchdog is defined in the devicetree, it is used as a
17 fallback. Otherwise the task watchdog will run independently.
40 Task watchdog sample application.
48 Task watchdog channel 1 callback, thread: control
|
| D | sample.yaml | 2 name: Task Watchdog Subsytem Sample
11 - "Task watchdog sample application."
15 - "Task watchdog channel 1 callback, thread: control"
17 - "Task watchdog sample application."
18 depends_on: watchdog
|
| /Zephyr-Core-3.7.0/soc/nxp/kinetis/kv5x/ |
| D | wdog.S | 9 * @brief Watchdog initialization for kv5x platform
11 * This module initializes the watchdog for the kv5x platform.
22 /* watchdog register offsets */
26 /* watchdog command words */
32 * @brief Watchdog timer disable routine
34 * This routine will disable the watchdog timer.
46 * First unlock the watchdog so that we can write to registers.
61 * Disable the watchdog.
|
