Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Espcomm_sync failure Wemos D1R2 #52

Open
igrr opened this issue May 10, 2017 · 4 comments
Open

Espcomm_sync failure Wemos D1R2 #52

igrr opened this issue May 10, 2017 · 4 comments

Comments

@igrr
Copy link
Owner

igrr commented May 10, 2017

From @johnwa27 on May 10, 2017 2:51

I'm getting this well known failure. All the responses seem to place blame on the users code or wiring. But it's happening to me on a Wemos board with nothing connected to it. It happens randomly, sometimes my code uploads, other times it will take 3 or 4 tries. Closing the serial monitor seems to help a bit.

This is not an issue with my code, my code works when it uploads and it happens with several different working programs.
It's a hardware/ide issue. It's made even worse since it has to recompile every upload attempt.

When is someone going to take this issue seriously?

Copied from original issue: esp8266/Arduino#3224

@igrr
Copy link
Owner Author

igrr commented May 10, 2017

From @davisonja on May 10, 2017 2:58

I think it's fair to say that it is taken seriously, but it has a myriad of
potential causes meaning that there isn't one simple fix for everyone.

For example, I've got a "Wemos D1R2" board (I'm sure it's a clone, but
still) which has a flaky USB socket. It needs to be at just the right angle
in order for the board to appear on my computer as a serial port - the
symptoms, if the USB cable isn't just right are the 'espcomm_sync' errors.
Here it's an easy fault - the USB connector on the board isn't attached
properly, requiring pressure from the connected USB cable to complete the
connection.
Of course, it's a localised hardware fault to that board, so it's not
something that anyone else can either fix, or diagnose for me.

If you've got the same kind of issue you might need to talk to your
supplier.

On Wed, May 10, 2017 at 2:51 PM, johnwa27 [email protected] wrote:

I'm getting this well known failure. All the responses seem to place blame
on the users code or wiring. But it's happening to me on a Wemos board with
nothing connected to it. It happens randomly, sometimes my code uploads,
other times it will take 3 or 4 tries. Closing the serial monitor seems to
help a bit.

This is not an issue with my code, my code works when it uploads and it
happens with several different working programs.
It's a hardware/ide issue. It's made even worse since it has to recompile
every upload attempt.

When is someone going to take this issue seriously?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
esp8266/Arduino#3224, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAN_A3MTEtGNNQsw0nTi4DjlcZl0lX02ks5r4SZEgaJpZM4NWHlb
.

@igrr
Copy link
Owner Author

igrr commented May 10, 2017

Moved to this repo, since the issue is with the esptool. I am sure there are a fair few cases where esptool-ck is "not trying hard enough".
It would be great if someone with access to the said board and capability to get logic analyzer traces and UART logs via a separate adaptor could get a trace for the case when failure occurs.

@nissimzur
Copy link

nissimzur commented May 10, 2017 via email

@igrr
Copy link
Owner Author

igrr commented May 10, 2017

Some Chines flashes are bad. Using them on PCB may result that.

I have seen this as well, but this should not produce espcomm_sync failure, more likely a timeout waiting for flash erase to complete. This issue is specifically about the initial handshake failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants