[riot-notifications] [RIOT-OS/RIOT] drivers/include: add header definition for wdt (#11527)

Kaspar Schleiser notifications at github.com
Wed May 15 16:02:29 CEST 2019


kaspar030 commented on this pull request.



> + */
+void wdt_stop(void);
+
+/**
+ * @brief    Reset the watchdog timer counter, delay system reset
+ */
+void wdt_kick(void);
+
+/**
+ * @brief    Set up the wdt timer, only use max_time if normal operation
+ *           set min_time and max_time for windowed timer.
+ *
+ * @param[in] min_time       lower bound for windowed watchdog in us
+ * @param[in] max_time       upper bound for windowed watchdog in us, time before
+ *                           reset for normal watchdog
+ * @param[in] wdt_cb         wdt callback

Well, we might have to make some concessions to a generic API here. The behaviour needs to be *the same* on all platforms implementing the interface. That's why I think it makes sense to split reboot and callback functionality.

How do other platforms handle callbacks/interrupts from the WDT?

(skimming datasheets)

STM32F4 seems to have a reset-only watchdog (IWDG) and a windowing one with reset + early warning interrupt.

nrf52 also has an early warning interrupt, but the datasheet says "Once the TIMEOUT event has been generated, the impending watchdog reset will always be effectuated.", suggesting that the watchdog cannot be reset from the interrupt.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11527#discussion_r284271265
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190515/b11eab9d/attachment.html>


More information about the notifications mailing list