Home
last modified time | relevance | path

Searched refs:watchdog (Results 1 – 25 of 443) sorted by relevance

12345678910>>...18

/Zephyr-latest/drivers/watchdog/
DKconfig21 Disable watchdog at Zephyr system startup.
24 module-str = watchdog
34 Enable multistage operation of watchdog timeouts.
37 bool "Counter based watchdog"
44 that context. This watchdog can be used along hardware watchdog to
45 overcome hardware watchdog limitations, e.g. Nordic devices reset
46 unconditionally at fixed time after hitting watchdog interrupt, leaving
49 hardware based watchdog.
59 supported by the counter device which is used for watchdog.
63 source "drivers/watchdog/Kconfig.stm32"
[all …]
DKconfig.nxp_fs265 bool "NXP FS26 SBC watchdog driver"
11 Enable the NXP FS26 SBC watchdog driver.
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
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.
51 and challenger watchdog configurations. In simple watchdog
53 watchdog configuration, value 0x0000 is not allowed.
[all …]
DKconfig.gd325 bool "GD32 Free watchdog timer (FWDGT) driver"
11 Enable the Free watchdog timer (FWDGT) driver for GD32 SoCs.
14 bool "GD32 Window watchdog timer (WWDGT) Driver"
19 Enable the Window watchdog timer (WWDGT) driver for GD32 SoCs.
DKconfig.it8xxx215 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.
DKconfig.npcx14 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
DKconfig.xmc4xxx17 int "Default watchdog timeout to use at startup"
20 Default watchdog timeout to use if the watchdog is not disabled
DKconfig.ene5 bool "ENE KB1200 watchdog driver"
10 This option enables the KB1200 watchdog driver.
DKconfig.rpi_pico11 int "Default watchdog timeout in us"
16 Sets the default watchdog timeout at start-up, the feed function must
/Zephyr-latest/subsys/task_wdt/
DKconfig1 # 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 …]
/Zephyr-latest/samples/drivers/watchdog/
DREADME.rst1 .. zephyr:code-sample:: 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
47 Feeding watchdog 5 times
48 Feeding watchdog...
[all …]
/Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/
DREADME.txt2 Test scenarios validate that invalid use of 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.
35 Every test assumes that watchdog is disabled at startup.
41 2. There are three watchdog flags that can be passed to wdt_install_timeout():
[all …]
/Zephyr-latest/samples/subsys/task_wdt/
DREADME.rst2 :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
/Zephyr-latest/soc/nxp/mcx/mcxc/
DKconfig41 bool "Keep watchdog timer enabled at boot"
43 Leave SOC watchdog timer enabled at boot. The specific timeout
44 and clock configuration of the watchdog at boot is SOC dependent.
45 Note: if the watchdog timer is enabled at boot, the user will
46 need to configure the watchdog using z_arm_watchdog_init, as
47 the SOC requires watchdog configuration before initial expiration
49 # Enable watchdog configuration function if watchdog is left enabled at boot
DCMakeLists.txt18 # CMSIS SystemInit will disable watchdog unless instructed not to.
19 # Add a compiler definition here to leave watchdog untouched
/Zephyr-latest/doc/services/task_wdt/
Dindex.rst9 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,
29 Instead, the task watchdog API can be accessed globally to add or delete new
/Zephyr-latest/soc/nxp/kinetis/ke1xf/
DKconfig47 bool "Keep watchdog timer enabled at boot"
49 Keep the watchdog timer enabled at boot with the internal
52 watchdog timer after boot and install a different timeout,
56 int "Initial timeout for the watchdog timer in milliseconds"
61 Initial timeout value for the watchdog timer in
/Zephyr-latest/dts/arm64/intel/
Dintel_socfpga_agilex.dtsi164 watchdog0: watchdog@ffd00200 {
165 compatible = "snps,designware-watchdog";
171 watchdog1: watchdog@ffd00300 {
172 compatible = "snps,designware-watchdog";
178 watchdog2: watchdog@ffd00400 {
179 compatible = "snps,designware-watchdog";
185 watchdog3: watchdog@ffd00500 {
186 compatible = "snps,designware-watchdog";
Dintel_socfpga_agilex5.dtsi181 watchdog0: watchdog@10d00200 {
182 compatible = "snps,designware-watchdog";
189 watchdog1: watchdog@10d00300 {
190 compatible = "snps,designware-watchdog";
197 watchdog2: watchdog@10d00400 {
198 compatible = "snps,designware-watchdog";
205 watchdog3: watchdog@10d00500 {
206 compatible = "snps,designware-watchdog";
213 watchdog4: watchdog@10d00600 {
214 compatible = "snps,designware-watchdog";
/Zephyr-latest/tests/drivers/build_all/watchdog/boards/
Dqemu_cortex_m3.overlay8 watchdog: watchdog@88888888 {
/Zephyr-latest/tests/kernel/threads/no-multithreading/src/
Dmain.c14 uint32_t watchdog = CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC; in ZTEST() local
18 watchdog--; in ZTEST()
19 if (watchdog == 0) { in ZTEST()
/Zephyr-latest/soc/nxp/kinetis/
DCMakeLists.txt16 # CMSIS SystemInit will disable watchdog unless instructed not to.
17 # Add a compiler definition here to leave watchdog untouched
DKconfig140 bool "Keep watchdog timer enabled at boot"
142 Leave SOC watchdog timer enabled at boot. The specific timeout
143 and clock configuration of the watchdog at boot is SOC dependent.
144 Note: if the watchdog timer is enabled at boot, the user will
145 need to configure the watchdog using z_arm_watchdog_init, as
146 the SOC requires watchdog configuration before initial expiration
148 # Enable watchdog configuration function if watchdog is left enabled at boot
/Zephyr-latest/dts/arm/nxp/
Dnxp_s32z27x_rtu0_r52.dtsi57 swt0: watchdog@76000000 {
66 swt1: watchdog@76010000 {
75 swt2: watchdog@76220000 {
84 swt3: watchdog@76230000 {
93 swt4: watchdog@76140000 {
Dnxp_s32z27x_rtu1_r52.dtsi57 swt0: watchdog@76800000 {
66 swt1: watchdog@76810000 {
75 swt2: watchdog@76a20000 {
84 swt3: watchdog@76a30000 {
93 swt4: watchdog@76940000 {
/Zephyr-latest/tests/drivers/build_all/watchdog/
Di2c_devices.overlay31 npm6001_ek_wdt: watchdog {
40 npm2100_wdt: watchdog {

12345678910>>...18