You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having problems using the library with the newest ESP8266 release (v2.5.1). Specifically, when trying to call:
voidhandleInterrupt() {
ot.handleInterrupt();
}
It seems others have been having this issue in similar situations as you can see here. I get a very similar error message to the one I linked - something like:
ISR not in IRAM!
Abort called
>>>stack>>>
As I understand it, the correct way to solve this issue is to change the library to move the ISR into IRAM, otherwise the script never proceeds past this interrupt function. However, I'm unsure how you would do this otherwise I would've made a pull request to resolve the issue.
Do you have any ideas?
Kind regards,
Tom
P.S. I am using ESP8266 v2.5.0 for now as the issue is only with the newest version
The text was updated successfully, but these errors were encountered:
I'm not sure if this helps you since I am not using this library, but adding ICACHE_RAM_ATTR to my interrupt handler helped me. If it does not help you, maybe you need to add it to the libraries interrupt handler aswell.
@verner-lall Thank you, that does seem to fix the problem! However, it looks like a bit of a bodge - as you say, I think the better solution is to add it to the library's interrupt handler.
Any ideas on how that could be done within the library?
Hi there,
I'm having problems using the library with the newest ESP8266 release (
v2.5.1
). Specifically, when trying to call:It seems others have been having this issue in similar situations as you can see here. I get a very similar error message to the one I linked - something like:
As I understand it, the correct way to solve this issue is to change the library to move the ISR into IRAM, otherwise the script never proceeds past this interrupt function. However, I'm unsure how you would do this otherwise I would've made a pull request to resolve the issue.
Do you have any ideas?
Kind regards,
Tom
P.S. I am using ESP8266
v2.5.0
for now as the issue is only with the newest versionThe text was updated successfully, but these errors were encountered: