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
[x ] I have read the documentation at readthedocs and the issue is not addressed there.
[x ] I have tested that the issue is present in current master branch (aka latest git).
I have searched the issue tracker for a similar issue.
[x ] If there is a stack dump, I have decoded it.
[x ] I have filled out all fields below.
Platform
Hardware: WemosD1 and NodeMCU V1.0
Core Version: 12/10/2018 00:34
Development Env: Visual Micro
Operating System: Windows
Problem Description
More of a 'gotcha' than a problem so it turns out.
On previous builds if a SPIFFS region wasn't assigned calling SPIFFS.begin() worked silently (ok, I guess there would have been problems later on).
On the current git calling begin() causes:
Fatal exception 0(IllegalInstructionCause):
epc1=0x4000e25d, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
As I said, more of a gotcha than a bug but it would be kinder if there was some sort of compiler warning.
The text was updated successfully, but these errors were encountered:
without s sketch mostly you cant get more help , try to completely erase your ESP Flash and re-upload your sketch if you still have an issue post your code here to look at it
Set your build up to 4MB (no SPIFFS), build with the lates git and run it - continual crashes.
Do the same with 2.4.2 (or any previous build), no crash.
If you set the build to (for example) 4MB (1MB SPIFFS), no problem.
As I said, it's a gotcha but it would be good to have some sort of warning if this is possible.
Basic Infos
Platform
Problem Description
More of a 'gotcha' than a problem so it turns out.
On previous builds if a SPIFFS region wasn't assigned calling SPIFFS.begin() worked silently (ok, I guess there would have been problems later on).
On the current git calling begin() causes:
Fatal exception 0(IllegalInstructionCause):
epc1=0x4000e25d, epc2=0x00000000, epc3=0x00000000, excvaddr=0x00000000, depc=0x00000000
As I said, more of a gotcha than a bug but it would be kinder if there was some sort of compiler warning.
The text was updated successfully, but these errors were encountered: