arduino-dw1000-ng
arduino-dw1000-ng copied to clipboard
F-Army
ESP32: delegate interrupt handling into a separate task
This pull request switches the interrupt request handling from a direct ISR into a separate task. This allows the handler more flexibility in how to handle the interrupt, without violating timing limits that may cause lockups or watchdog reboots. For platforms other than ESP32, the behavior of the code has been preserved.
| Q | A |
|---|---|
| Bug fix? | yes |
| New feature? | no |
| Doc update? | no |
| BC breaks? | no |
| Deprecations? | no |
| Relative Issues | # |
Can you please explain the differences between this and #164 ? Are they trying to achieve the same functionality? Sorry if we ask but we didn't use much the ESP32
@zrecore Are you available to try out these improvements (this and #177) ? Thank you
I'll have a look on Saturday. 👍
On Wed, Aug 19, 2020, 1:45 PM Michele Biondi [email protected] wrote:
@zrecore https://github.com/zrecore Are you available to try out these improvements (this and #177 https://github.com/F-Army/arduino-dw1000-ng/pull/177) ? Thank you
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/F-Army/arduino-dw1000-ng/pull/178#issuecomment-676683971, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADIW3G42D4NGCHEUNIPVQ3SBQ2XNANCNFSM4P5M42DA .
Can you please explain the differences between this and #164 ? Are they trying to achieve the same functionality? Sorry if we ask but we didn't use much the ESP32
It seems that #164 has the same purpose as my commit. However, my version does not change the library API, and since the task has a higher priority than the ordinary code, it should be less prone to handling delays.
We are closing pull requests with merging conflicts as we are archiving the repo, feel free to create your own fork if you intend to support the project, we will be happy to add a link on this project.