From 79d6ed101873befe1c2ebe3b54f1dc7178b405c1 Mon Sep 17 00:00:00 2001 From: Filip Jagodzinski Date: Fri, 14 Jun 2019 16:15:02 +0200 Subject: [PATCH] Relax watchdog timing requirements --- docs/porting/target/Watchdog.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/porting/target/Watchdog.md b/docs/porting/target/Watchdog.md index 92be2d0c65..554fe84bfa 100644 --- a/docs/porting/target/Watchdog.md +++ b/docs/porting/target/Watchdog.md @@ -11,7 +11,8 @@ Implement the ResetReason API when implementing the Watchdog API. The ResetReaso - Sleep and debug modes don't stop the watchdog timer from counting down. - The function `hal_watchdog_init` is safe to call repeatedly. The function's implementation must not do anything if `hal_watchdog_init` has already initialized the hardware watchdog timer. - Maximum supported timeout is `UINT32_MAX` milliseconds; minimum timeout is 1ms. -- The timeout must be accurate to the nearest millisecond. +- The watchdog should trigger at or after the timeout value. +- The watchdog should trigger before twice the timeout value. ### Undefined behavior @@ -20,7 +21,6 @@ Implement the ResetReason API when implementing the Watchdog API. The ResetReaso ### Notes - A software reset may not stop the watchdog timer; the behavior is platform specific. -- Timing on most platforms is based on the timeout registers and a prescaler value. They should be accurate to the nearest millisecond but may be off my a several µs. ## Dependency