Lines Matching full:watchdog

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.
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():
42     - WDT_FLAG_RESET_NONE - when watchdog expires, it's callback is serviced but
44     - WDT_FLAG_RESET_CPU_CORE - when watchdog expires, only one core is reset, while
46     - WDT_FLAG_RESET_SOC - when watchdog expires, target as "a whole" is reset.
56 3. These tests assume that watchdog driver supports multiple timeouts. Set
59 4. When all watchdog timeouts must have exactly the same watchdog timeout value
63 5. Set maximal allowed watchdog timeout value, f.e.:
65    Also, test assumes that minimal allowed watchdog timeout value must be zero.
67 6. There are two watchdog options that can be passed to wdt_setup():