SparkFun Forums

[Arctic_Eddie]

I received two of these boards today and neither one will upload blink or any other example sketch. The boards show up as com41 or com42 depending on which one is plugged in. The baud value is set to 115200 on the comport and matches the value the uploader wants to use. Nothing else is using the port but the upload makes nine attempts and blinks the light then fails with the following message. I tried to update the driver but W7-64 shows a window that says it's downloading the driver file but never completes. At this point, I would prefer to return the boards as opposed to cutting traces and installing jumpers. If this is what you have to do to get it working then the product is not really reading for sale.

Code: Select all

Sketch uses 219,267 bytes (50%) of program storage space. Maximum is 434,160 bytes.
Global variables use 31,464 bytes (38%) of dynamic memory, leaving 50,456 bytes for local variables. Maximum is 81,920 bytes.
C:\Users\xxxx\AppData\Roaming\Arduino15\packages\esp8266\tools\esptool\0.4.8/esptool.exe -vv -cd nodemcu -cb 115200 -cp COM42 -ca 0x00000 -cf C:\Users\xxxx\AppData\Local\Temp\build507896959865733368.tmp/Blink.cpp.bin 
esptool v0.4.8 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
	setting board to nodemcu
	setting baudrate from 115200 to 115200
	setting port from COM1 to COM42
	setting address from 0x00000000 to 0x00000000
	espcomm_upload_file
	espcomm_upload_mem
	setting serial port timeouts to 1000 ms
opening bootloader
resetting board
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
resetting board
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
resetting board
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
trying to connect
	flush start
	setting serial port timeouts to 1 ms
	setting serial port timeouts to 1000 ms
	flush complete
	espcomm_send_command: sending command header
	espcomm_send_command: sending command payload
	read 0, requested 1
warning: espcomm_sync failed
error: espcomm_open failed
error: espcomm_upload_mem failed

[Ross Robotics]

What have you tried when Googling the error?

[skimask]

Funny how the rest of the world doesn't seem to have a problem...
Odd how that works.

[Arctic_Eddie]

Very odd, maybe they're defective.

[Dejan.Camilovic]

It is very strange that the port number is too high?! You're using micro USB or FTDI connection?

[Arctic_Eddie]

The comport number is the one assigned by W7-64 when I connect the USB cable directly from the ESP board to the PC. This of course happens when any Arduino is connected to the PC with numbers ranging from 17 to 45 in recent months. My two Teensy 3.2 boards and an FTDI will get a similar number when connected. That part does not appear to be the problem as all of my other devices work. I've had as many as six connected at the same time with each having it's own IDE window and serial monitor. Add to this, a Lazarus IDE with the shore station code and it becomes quite messy.

I sent the two ESP boards to my grandson in NC. He sent me an email this afternoon and said he had a similar problem and it appeared to be a corrupted ESP core support installation. I also had driver hang up problems when attempting to sort this out. He reinstalled the package from the same URL in the preferences file and it's now working. He will mail the boards back to me tomorrow so I'll be able to test them this coming weekend. In the meantime, I'll reinstall the board package and test them upon arrival.

Now I'm looking for a simple example of a client and server that will talk to each other. I want to send a short binary request packet containing a coded command, device number, and data from client to server and get a large binary packet, 128 bytes, in return. This will be repeated 64 times until I retrieve 8192 bytes of sonar data from an RC controlled boat.