Skip to content

Update the watchdog timing requirements #1155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/porting/target/Watchdog.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,10 @@ 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.
- `UINT32_MAX` milliseconds is the maximum allowed max_timeout `hal_watchdog_get_platform_features()` returns; minimum timeout is 1 ms.
- The watchdog should trigger at or after the timeout value.
- The uncalibrated watchdog should trigger at or after the timeout value multiplied by the frequency accuracy ratio of its oscillator (typical_frequency divided by max_frequency).
- The calibrated watchdog should trigger at or after the timeout value.
- The watchdog should trigger before twice the timeout value.
- The watchdog may trigger as late as twice the timeout value in deep sleep mode.

### Undefined behavior

Expand Down