Skip to content
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

Getting a Kernel panic when trying to use it with EzTime library #3

Open
witnessmenow opened this issue May 31, 2019 · 9 comments
Open
Labels
bug Something isn't working

Comments

@witnessmenow
Copy link
Collaborator

More info to follow

@tablatronix
Copy link

I have traced these panics to using a timer or ISR and doing too much inside it.
Post anything different if you see it

@witnessmenow
Copy link
Collaborator Author

Will try out your changes on the Matrix panel when I get a change

@ROSW6341
Copy link

I do not know the underlying cause but I was able to circumvent the problem by copying core_esp_main.cpp from
C:\Users<USER>\AppData\Local\arduino15\packages\esp8266\hardware\esp8266\2.5.2\cores\esp8266
into the sketch directory then commenting out the 'panic()' on line 103 of the copied file.

@tablatronix
Copy link

tablatronix commented Jul 26, 2019

Yeah its strange because it is specifically calling panic exception because of the 'in interrupt' check, not sure what the other 2 checks are. Its odd

afaik , this is not in an interrupt

@witnessmenow
Copy link
Collaborator Author

witnessmenow commented Jul 26, 2019 via email

@ROSW6341
Copy link

Worked for me and much cleaner than the core_esp_main.cpp hack I posted above

@tablatronix
Copy link

That is what I did also, but it did still wdt now and then during long draws, but it is probably the easiest fix. Of course you can just not use a timer or use a timer library that just uses timekeeping and a process()

@tablatronix
Copy link

Is it possible to compile with no-exceptions build flag and bypass this also ?

@tablatronix
Copy link

aha

esp8266/Arduino#6283

toblum pushed a commit that referenced this issue Nov 21, 2022
An extra space of indentation caused the file to have an invalid YAML format.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants