Espruino JavaScript
[Resolved] Flashing an ESP8266EX results in garbage output on boot #6314
Replies: 1 comment
-
|
Posted at 2019-11-22 by Robin 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:
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 that reset() is being used without an argument. Was this intentional?
Has Is 'Erase Flash' being used between version changes? Were these the instructions that are being followed? > http://forum.espruino.com/conversations/335394/ What PC/OS is in use? *(Win10,Mac,Linux)* Posted at 2019-11-22 by AkosLukacs 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. What board do you have? Posted at 2019-11-22 by mcdonnelldean Hi Robin, thanks for your response, to answer you questions in order:
Posted at 2019-11-22 by mcdonnelldean 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 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). Posted at 2019-11-22 by mcdonnelldean 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: I 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. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Posted at 2019-11-21 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?
Attachments:
Beta Was this translation helpful? Give feedback.
All reactions