ESP8266 F.A.Q.

When I connect stuff to some of the pins, the Huzzah stops working. Whats up with that?

The ESP8266 uses some of the pins as 'boot mode' pins so on boot they must be set to certain values:

  • CH_PD (EN) should be always pulled high (it will disable the entire module if low)
  • RST should be always pulled high (it will disable the entire module if low)
  • GPIO 0 sets whether the bootloader is active, it must be pulled HIGH during power up/reset for the user program to run. If it's pulled LOW, it will activate the bootloader. The built-in red LED on #0 pulls it up
  • GPIO 2 must be pulled high on power up/reset.
  • GPIO 15 must be pulled low on power up/reset.

My Huzzah board keeps crashing and resetting, whats up with that?

The most common reason for crashes is power failure. Make sure you're powering the Huzzah with a good ~5V power supply, and if you're using a USB-Serial cable, that it's plugged into the mainboard of your computer or through a powered hub!

I can't seem to find the Serial port on my computer for the Feather HUZZAH?

Don't forget to install the CP2104 VCP drivers for your computer, they are required!

I still can't seem to find the Serial port on my computer for the Feather Huzzah!

Many cheap electronics come with charge-only USB cables, which cause headaches later. Make sure you are using a proper data/sync USB cable. If you find a cable that is charge-only (not data/sync also) throw it out so you don't have the same problem again.

So, I’m getting a 'no such file' error compiling for ESP8266 on my Mac

If your error message looks like this:

fork/exec /Users/xxxxxxx/Library/Arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/1.20.0-26-gb404fb9-2/bin/xtensa-lx106-elf-g++: no such file or directory
Error compiling.

To fix this problem, do this:

  1. Open the Boards Manager in the Arduino IDE
  2. Uninstall the ESP8266 support
  3. go to your ~LIbrary folder (in the Finder, select "Go::Go to folder:, and enter ~Library ). Find the folder Arduino15.
  4. In the Arduino15 folder, go into packages, and delete the folder esp8266
  5. Go back to the Arduino IDE, and install ESP8266 board support.
  6. Now go back to the Finder, and check that you have the xtensa-lx106-elf-g++ file in the path Arduino15/packages/esp8266/tools/xtensa-lx106-elf-gcc/1.20.0-26-gb404fb9-2/bin/xtensa-lx106-elf-g++
  7. That's it!

Whenever I start or reset the ESP8226 there's a bunch of "gibberish" on the Serial console

This is the ROM debug messages, it's transmitted at 74880 baud so you rarely see it in proper 'ascii output' - instead usually it gets corrupted into a bunch of strange characters.

I'm having difficulties uploading to the HUZZAH with the Arduino IDE

Make sure you're using a good quality USB/Serial cable. Install the official drivers for that cable too! We've also noticed that PL2303-based cables don't work on Macs for some reason. FTDI or CP210x based chipsets work best

I tried that, but I'm still having difficulties uploading with the Arduino IDE

Sometimes, it helps to switch the board type to "Generic ESP8266 Module".  Set the Reset Method to "nodemcu"

See this forum post

I'm stuck in bootloader mode and can't upload

You say your led is stuck on dim and you get an error trying to upload? And you're sure your serial cable is connected and working correctly? Well, here's a potential fix: Connect the GPIO0 pin to GND through a 220 ohm resistor. Leave it connected while you upload.  You may have to try it a couple of times, but it should eventually upload and get the HUZZAH unstuck from bootload mode! You can then remove the resistor connection, and your HUZZAH will be happy ever after!

(Note: you may also have to tie RST and EN (CH_PD) together to get this to work.  Remove the connection once you have the module programmed).

Thanks to forum user misslevania for the tip!

I can't get Lua to respond to my commands

Make sure your terminal software is sending correct line endings! The default PuTTY settings may be wrong when trying to talk to Lua on an ESP8266. Lua expects CRLF "\r\n" line endings, and apparently PuTTY defaults to just LF "\n"!

Last updated on 2017-07-14 at 08.53.48 PM Published on 2015-11-25 at 03.07.09 PM