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
Connect the serial output of some other compatible device (I just use another ESP spitting out some debug information in a loop) to GPIO14 and wait :)
As per the comment in there, if you don't connect to the tcp socket at all then it doesn't crash. But once you connect, the crash comes reasonably quickly (can take a bit of time, depending on the serial datarate I think).
Any idea whats going on here? Some sort of interrupt clash?
There is no exception printed or anything, the ESP just hangs and then reboots. I don't even see a wdt message, oddly.
The text was updated successfully, but these errors were encountered:
Some gitter discussion reveals that this probably is because interrupts are disabled too long (or too often, or a combination of both), done by SoftwareSerial.
if I swap out SoftwareSerial for the real Serial then the problems instantly go away because I don't have to disable interrupts for such a long time.
So this is probably unfixable, just a way the ESP8266 is, unless anyone has any suggestions please feel free to close.
Hi,
I can fairly reproducibly crash the following code:
SoftwareSerial is from https://github.com/plerup/espsoftwareserial
Connect the serial output of some other compatible device (I just use another ESP spitting out some debug information in a loop) to GPIO14 and wait :)
As per the comment in there, if you don't connect to the tcp socket at all then it doesn't crash. But once you connect, the crash comes reasonably quickly (can take a bit of time, depending on the serial datarate I think).
Any idea whats going on here? Some sort of interrupt clash?
There is no exception printed or anything, the ESP just hangs and then reboots. I don't even see a wdt message, oddly.
The text was updated successfully, but these errors were encountered: