-
Notifications
You must be signed in to change notification settings - Fork 1k
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
alarm pool can appear to stop working #1953
Milestone
Comments
peterharperuk
added a commit
to peterharperuk/pico-sdk
that referenced
this issue
Sep 25, 2024
kilograham
pushed a commit
that referenced
this issue
Sep 26, 2024
* Avoid setting an alarm in the past Fixes #1953 * Call ta_time_us_64 when needed Remove local "now" variable.
Fixed in |
peterharperuk
added a commit
to peterharperuk/pico-sdk
that referenced
this issue
Oct 7, 2024
Merged
peterharperuk
added a commit
that referenced
this issue
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have an issue with a program on RP2040 that we communicate with via a USB, it was occasionally unresponsive. After some investigation a repeated alarm callback that is used to call tud_task_ext was not happening. This only seems to be a problem on sdk 2.0. Further investigation suggests it's possible for the alarm pool to register an alarm in the past, so it'll only go off in ~71 minutes. The attached program seems to reproduce the problem.
The suggested fix to alarm_pool_irq_handler is to update "now" after the call to "ta_time_us_64"
alarm_test.zip
The text was updated successfully, but these errors were encountered: