Skip to content

Relax watchdog timing requirements #1088

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 1 commit into from
Jul 1, 2019
Merged

Relax watchdog timing requirements #1088

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 2 additions & 2 deletions docs/porting/target/Watchdog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -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

Expand Down