-
Thr 2019.11.21
Hi @mcdonnelldean haven't played with one of these in quite a while, so just attempting to clarify a comment for others:
'but otherwise works.'
'it always looks like the screenshot provided, hung.'By 'otherwise works' does entering commands in the Left-Hand console side provide expected output?
When does the state 'hung' occur? Could it be related to the comment that follows?
I noticed thatreset()is being used without an argument. Was this intentional?Has
reset(true)been tried before disconnect and the (next) connection attempt?
Is 'Erase Flash' being used between version changes?
Were these the instructions that are being followed?
What PC/OS is in use? (Win10,Mac,Linux) -
• #3
The "garbage" in the beginning is because the ESP8266's sends debug messages through the UART at a different baud rate. So that part is expected.
But (unless you intentionally pressed reset on the ESP when you tried to connect) I think something is not correct with the reset / Serial adapter circuit of your board. It should not start up when it's powered, and that garbage should long be gone by the time you connect to it.
This might be the reason why the web ide hangs: garbage sent first, and that "confuses" the IDE.What board do you have?
-
Hi Robin, thanks for your response, to answer you questions in order:
Otherwise means I can connect to it via a terminal app, I still get garbage but the REPL is usable when I connect with "screen /my/port/here " for instance. If I do a reset(true) in the repl the restart happens and I get no garbage (I only get garbage on connection), again only via a terminal session.
I cannot use the IDE left hand (or right hand at all). The reset bit is a hold over and should not be considered (I simply didn't clear out the editor before screenshot. When in the IDE, neither left or right pane worked as the device is always stuck in "connecting" mode. The splash loads but otherwise the repl is hung.
Yes, I erase using the same baud as I flash too (I don't know if that makes a difference)
Yes and also later threads where "4m-c1" is used (based on observing my chip code and using the reference in the docs). Interestingly my board(s) needs dio, not qio to be set to flash properly.
OSX (esptool v2.8)
-
This is interesting info! I have a bunch of different ones. Specifically this is trying a D1 (big style NodeMCU like board) and a few D1 Mini's. I think they are all using a CH340 chip for serial.
EDIT:
I'd like to confirm that the length of time doesn't matter. The garbage is reproduced for every connection regardless of how long I let it start up and stay idle.I can also confirm the board itself is not hung. I can get it to spit something out on a timeout which does happen even though the IDE says it is still "connecting".
I might have a look through the Web Terminal code tonight. My suspicion is that while it won't fix the issue directly, the IDE problem is likely the garbage tripping up the IDE and making it think it is still waiting for connection, even though in the background it is connected (as evidenced by the timeout test).
-
Hi all, I thought this might help folks out, in the end flashing was not the problem at all, it was using a USB adapter to extend the number of USB's I had available, this seems to have borked the flashing.
I confirmed with a few other folks that they also get the junk at the top which, as was mentioned, is just debug bits with at a different baud.
I am now able to flash all varius ESP boards I have, and can confirm the combined file is fine:
esptool.py --port /dev/cu.wchusbserial1410 --baud 115200 write_flash --flash_freq 80m --flash_mode dio --flash_size 4MB-c1 0x0000 espruino_2v04_esp8266_4mb_combined_4096.binI have another few boards to set up too so I can confirm all is good. But just a note to all others, if your having serial problems and are using a USB hub, that is likely why.
Robin
AkosLukacs-
Post a reply
About
[Resolved] Flashing an ESP8266EX results in garbage output on boot
Posted by
@mcdonnelldean
Hi all,
I see this issue has gone around the houses a few times. I've followed all the threads and tried all the variations of esptools settings. I've also tried a few different versions of Espruino it's something in the flashing process / settings I think.
Board is as so:
Erasing looks like so:
Flashing via best practice examples (1V99 combined):
Screen output:
Flashing to latest (2v04):
Screen Output
In all cases I can connect via the screen terminal app. It spits out garbage at the top but otherwise works. I can use the REPL no problem. However when I use the IDE the connection never fails or succeeds, it always looks like the screenshot provided, hung.
I've done a few things too:
Anyone have any suggestions on what to try next?
1 Attachment