-
Notifications
You must be signed in to change notification settings - Fork 1.1k
RP2040 and RP2350 have different maximum watchdog delays #2500
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
base: develop
Are you sure you want to change the base?
Conversation
Updated and force-pushed |
@@ -124,7 +131,7 @@ bool watchdog_enable_caused_reboot(void); | |||
* \brief Returns the number of microseconds before the watchdog will reboot the chip. | |||
* \ingroup hardware_watchdog | |||
* | |||
* \if rp2040_specicifc | |||
* \if rp2040_specific | |||
* On RP2040 this method returns the last value set instead of the remaining time due to a h/w bug. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kilograham Do you know which hardware bug this is referring to? The RP2040 datasheet lists RP2040-E1 (which doesn't cover this) as the only watchdog-related errata.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like I'd forgotten about #1492 🤦
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems a bit better
RP2040-E1 doesn't apply to RP2350 😉 I spotted this whilst investigating #2497