Skip to content
Advertisement

ESP8266 module fails at boot

I have a ESP8266MOD ESP-12-E hooked up to a USB-to-UART module. When I try to communicate with the module I get some intelligible output then an error message and the communication is closed.

For ai-thinker-0.9.5.2-115200 and espressif-nonos-2.0.0-SDK (this is not the actual name of the file):

JavaScript

For a nodeMCU firmware built today (see the date) using their cloud service I get a somewhat shorter message:

JavaScript

Also, the error messages are: For miniterm.py on linux:

JavaScript

For Putty on windows I also get an error at the same stage in the booting process, it seems.

Note 1: I have managed to successfully flash new firmware and I got “verify OK” every time, so the connection is good.

Note 2: When I use the module in the Normal Boot mode (GPIO15 low, GPIO0 and GPIO2 floating), when the EN (enable) pin is high (3.3v), PORT8 on windows and /dev/ttyUSB0 on linux both dissapear. Also when communicating with putty or miniterm on anything similar, I need to keep EN floating so the system sees the module, then connect with the software and then put EN on high (otherwise it gets stuck).

Also tried to use ESPlorer but it was unable to auto-detect the firmware. I’ve got that error on several firmwares and I tried many baud rates.

Advertisement

Answer

The problem was with the power supply for the ESP8266 unit. Instead of supplying 3.6V from the USB-to-UART module, i used another voltage source providing 3.3V, possibly higher current also. Note that the module must be supplied with 3.0V – 3.6V and it may use a few hundred milliamps, so the old supply was a little bit over 3.6V and it might have not been able to provide the required current.

User contributions licensed under: CC BY-SA
9 People found this is helpful
Advertisement