I noticed with the current esp8266 builds there's a lot of debug output. There are previous issues about this like #2072 and a mention that perhaps debug output should be suppressed for later firmware builds (see #2072 (comment) ). I'd like to suggest that this behavior to suppress debug output become the default now (perhaps just add a call to esp.osdebug(None) to the _boot.py?).
The reason I raise this issue is that scripts like pyboard.py depend on talking to a 'clean' REPL with no debug output. The esp8266 codebase right now can print out a lot of debug output, like if the chip is trying to connect to a wifi network it can't find, and this wreaks havoc with pyboard.py's parsing which depends on getting exact response strings back from the chip. If debug output sneaks in it's game over and pyboard.py's parsing fails.
I'd like to suggest debug output suppression be the current new default for esp8266 firmware. This will allow folks to use pyboard.py and build tooling, etc. around it to improve the ecosystem. I realize folks can just call esp.osdebug(None) themselves but IMHO it would make the experience much smoother if people can load the firmware and start using tools immediately, not troubleshoot peculiar issues because their esp is in an odd state spewing debug output. Thanks!
I noticed with the current esp8266 builds there's a lot of debug output. There are previous issues about this like #2072 and a mention that perhaps debug output should be suppressed for later firmware builds (see #2072 (comment) ). I'd like to suggest that this behavior to suppress debug output become the default now (perhaps just add a call to esp.osdebug(None) to the _boot.py?).
The reason I raise this issue is that scripts like pyboard.py depend on talking to a 'clean' REPL with no debug output. The esp8266 codebase right now can print out a lot of debug output, like if the chip is trying to connect to a wifi network it can't find, and this wreaks havoc with pyboard.py's parsing which depends on getting exact response strings back from the chip. If debug output sneaks in it's game over and pyboard.py's parsing fails.
I'd like to suggest debug output suppression be the current new default for esp8266 firmware. This will allow folks to use pyboard.py and build tooling, etc. around it to improve the ecosystem. I realize folks can just call esp.osdebug(None) themselves but IMHO it would make the experience much smoother if people can load the firmware and start using tools immediately, not troubleshoot peculiar issues because their esp is in an odd state spewing debug output. Thanks!