ESP8266 Community Forum

- Sun Oct 30, 2016 5:26 am #57379 I've assembled a prototype that is working well (based on an ESP12 module), and I have designed a PCB that I'm now testing. For the test I'm using new ESP12E modules, and what I've noticed is that I'm not able to enter in the bootloader correctly. When I try to enter in bootloader mode I get the following message:

ets Jan 8 2013,rst cause:2, boot mode:(1,0)

But using arduino it fails to program it:

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 COM1 to COM14
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

In both modules the CH_PD is pulled up, GPIO0 is pulled down and this seems to be ok because they enter in bootloader mode (boot mode 1).

The original prototype I made (based on the ESP12, not the ESP12E) works perfectly and the message I get when I try to enter in bootloader refers boot mode:(1,7) instead of (1,0) I have with the non working module (ESP12E). This is the messag I get with the original prototype based on the ESP12:

ets Jan 8 2013,rst cause:1, boot mode:(1,7)

Any idea of the reason of the bootloader not starting correctly? Since the ESP12E board is soldered on my PCB is not easy to replace it by an older module (and also I don't have any ESP12 spare module, only a few ESP12E modules from the same batch).

Thanks in advance

Fernando

- Sun Oct 30, 2016 8:34 am #57384 Power problems can cause some strange issues. A lot of people have been chasing their tail looking at software when the real cause has been a poor power supply. Since you have not indicated what you have in that regard I thought it was worth mentioning.

- Sun Oct 30, 2016 9:18 am #57385 Hi Rudy, thanks for your reply. I am using a similar circuit for both the initial prototype and the new one, based on a Li-Ion battery (18650, measured to be at about 4V) and a 3.3V voltage regulator (and decoupling capacitor). I'm measuring with a scope the 3.3V at the ESP module and it looks good, similar between both modules. Do you have any idea why with the old module the boot mode is (1,7) and with the new one is (1,0)? Because it is the only difference I see, besides the Arduino IDE not beeing able to program the new module. Could be a power usage difference between the ESP12 and ESP12E? In that case I should see a problem with a scope in the 3.3V voltage.

Best regards

Fernando

- Tue Nov 01, 2016 6:46 pm #57520 I've found what it seems to be the issue, changing the USB/Serial adapter the problem disappears, I'm able to program the node even when it boots in mode (1,0). I'm not seeing a reason for the other adapter have cause this issue, I'm using it with Arduinos (ATMEGA328) and it is working well, and the logic level for all my USB/serial converters are configured to 3.3V, and are all from FTDI. Recently for the ESP8266 I'm using more the NodeMCU so for that I use USB/serial converter that is built on the module

Best regards

Fernando