Espcomm_sync failure Wemos D1R2

[igrr]

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]

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 notifications@github.com 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]

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]

Some Chines flashes are bad. Using them on PCB may result that. The rejected flashes sold in very low prices and can use for FAT voice storage, not as Firmware flash and boot devices. Kind regards, Dr. Nissim Zur Bluetooth Smart, IoT expert <http://www.elinistech.com/> CTO Elinistech Tel 0544 500635 Tel 03 5716699 Skype <callto:nissim.test> nissim.test Follow <https://goo.gl/CXY35s> Linkedin https://goo.gl/CXY35s Email nissim@elinistech.com <http://www.elinistech.com/> www.elinistech.com From: Ivan Grokhotkov [mailto:notifications@github.com] Sent: Wednesday, May 10, 2017 8:19 AM To: igrr/esptool-ck Cc: Subscribed Subject: [igrr/esptool-ck] Espcomm_sync failure Wemos D1R2 (#52) From @johnwa27 <https://github.com/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 <esp8266/Arduino#3224> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#52> , or mute the thread <https://github.com/notifications/unsubscribe-auth/ADgOR5O99tPLi-4y2WLgoNpwx5kWkK46ks5r4UiqgaJpZM4NWMHM> . <https://github.com/notifications/beacon/ADgORxSMK7kjz_eLuwsUFRNxymiKoa9cks5r4UiqgaJpZM4NWMHM.gif>

[igrr]

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.