Skip to content

Clarify maximum timeout in Watchdog.md #1134

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.

Sign up for GitHub

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 2 commits into from
Aug 23, 2019
Merged

Clarify maximum timeout in Watchdog.md #1134

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dda911a
Clarify maximum timeout in Watchdog.md
Aug 15, 2019
78a7000
Fix typo in Watchdog.md
Aug 23, 2019
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
2 changes: 1 addition & 1 deletion docs/porting/target/Watchdog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ 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.
- `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 watchdog should trigger before twice the timeout value.

Expand Down