Please note: Friday June 18 is a holiday celebrating Juneteenth, please allow extra time for your order to arrive and plan accordingly.
0

Can't upload code or access Serial port of Feather HUZZAH ES
Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.

Can't upload code or access Serial port of Feather HUZZAH ES

by norrissd on Fri Apr 16, 2021 10:26 am

I'm having an issue with the Feather HUZZAH ESP8266. I'm using it to control a bunch of vibration motors. I was testing it with a circuit on a breadboard for a while, but have since soldered it into a custom PCB that I designed in Fritzing based on the circuit I was sucessfully using in the breadboard. Since soldering the Huzzah into the PCB with the rest of the components, attempts to upload any new code (including the basic Blink example) result in the following verbose output in the IDE console, (see the "error: espcomm_upload_mem failed" and other errors at the bottom):
Code: Select all | TOGGLE FULL SIZE
Arduino: 1.8.7 (Mac OS X), TD: 1.45, Board: "Adafruit HUZZAH ESP8266, 80 MHz, 115200, 4M (3M SPIFFS)"

Sketch uses 222189 bytes (21%) of program storage space. Maximum is 1044464 bytes.
Global variables use 31532 bytes (38%) of dynamic memory, leaving 50388 bytes for local variables. Maximum is 81920 bytes.
/Users/seannorris/Library/Arduino15/packages/esp8266/tools/esptool/0.4.9/esptool -vv -cd nodemcu -cb 115200 -cp /dev/cu.SLAB_USBtoUART -ca 0x00000 -cf /var/folders/9q/lszwnrtj7sz2qpqncz5bwtmr0000gp/T/arduino_build_477622/Blink.ino.bin
esptool v0.4.9 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>
   setting board to nodemcu
   setting baudrate from 115200 to 115200
   setting port from /dev/tty.usbserial to /dev/cu.SLAB_USBtoUART
   setting address from 0x00000000 to 0x00000000
   espcomm_upload_file
   espcomm_upload_mem
opening port /dev/cu.SLAB_USBtoUART at 115200
   tcgetattr
   tcsetattr
   serial open
opening bootloader
resetting board
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
resetting board
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
resetting board
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
trying to connect
   espcomm_send_command: sending command header
   espcomm_send_command: sending command payload
warning: espcomm_sync failed
error: espcomm_open failed
error: espcomm_upload_mem failed
error: espcomm_upload_mem failed


The PCB is relatively simple, so I've included a screenshot of the layout from Fritzing:
Screen Shot 2021-04-16 at 15.13.39.png
Screen Shot 2021-04-16 at 15.13.39.png (450 KiB) Viewed 120 times

As you can see on the PCB, GPIO #0 and #2 are both used in the circuit to control a motor each. The overview for the Huzzah states that #0 and #2 are both used by the ESP8266 to detect bootmode. Am I somehow interrupting the start up checks that the ESP8266 carries out by improperly using these pins?

Some other strange behaviour, if it is helpful in diagnosing the problem: When I connect 5v DC to the VCC connection on the PCB (used to power the motors) and then connect the huzzah to the USB port on my computer, the motors connected to pins #0 and #16 start buzzing. Does this indicate some issue with the start up process?

norrissd
 
Posts: 3
Joined: Sat Mar 06, 2021 7:21 am

Please be positive and constructive with your questions and comments.