ESP8266 Community Forum

- Sat Aug 19, 2017 8:39 pm #69306

What eduperez says...
You have to build in debug code into your sketch.

Often made mistakes in (Arduino - ESP8266 core) code is starving the WiFi core (long delays/while loops without yield() ), resulting in watchdog resets and not correctly dealing with connection losses.

eduperez, can you ping me offline please at wmweis45@hotmail.com.

- Sat Aug 19, 2017 9:43 pm #69309

is there a easy way to check firmware on new NodeMCU ESP8266 E12 development chips you just opened up?

You could connect an ESP (any model) to your PC, open a terminal program (PuTTY or just the monitor inside the Arduino IDE), set the speed to 74880 Baud (not a typo; this really is not a standard speed) and power up the ESP (or reset the ESP).
You should get information like this:

Code: Select all ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 1856, room 16
tail 0
chksum 0x63
load 0x3ffe8000, len 776, room 8
tail 0
chksum 0x02
load 0x3ffe8310, len 552, room 8
tail 0
chksum 0x79
csum 0x79

2nd boot version : 1.5
  SPI Speed      : 40MHz
  SPI Mode       : DIO
  SPI Flash Size & Map: 8Mbit(512KB+512KB)
jump to run user1 @ 1000

rf cal sector: 249
rf[112] : 00
rf[113] : 00
rf[114] : 01

SDK ver: 1.5.4.1(39cb9a32) compiled @ Jul  1 2016 20:04:35
phy ver: 972, pp ver: 10.1

This is the output from a fresh ESP-01 with default NON-OS SDK firmware, but the result *should* be similar with other ESP's.

Assumption is the mother of all f*ckups. At least: that's what I'm assuming.

- Sun Aug 20, 2017 9:09 am #69325

is there a easy way to check firmware on new NodeMCU ESP8266 E12 development chips you just opened up?

You could connect an ESP (any model) to your PC, open a terminal program (PuTTY or just the monitor inside the Arduino IDE), set the speed to 74880 Baud (not a typo; this really is not a standard speed) and power up the ESP (or reset the ESP).
You should get information like this:

Code: Select all ets Jan  8 2013,rst cause:2, boot mode:(3,6)

load 0x40100000, len 1856, room 16
tail 0
chksum 0x63
load 0x3ffe8000, len 776, room 8
tail 0
chksum 0x02
load 0x3ffe8310, len 552, room 8
tail 0
chksum 0x79
csum 0x79

2nd boot version : 1.5
  SPI Speed      : 40MHz
  SPI Mode       : DIO
  SPI Flash Size & Map: 8Mbit(512KB+512KB)
jump to run user1 @ 1000

rf cal sector: 249
rf[112] : 00
rf[113] : 00
rf[114] : 01

SDK ver: 1.5.4.1(39cb9a32) compiled @ Jul  1 2016 20:04:35
phy ver: 972, pp ver: 10.1

This is the output from a fresh ESP-01 with default NON-OS SDK firmware, but the result *should* be similar with other ESP's.

This is what I got, but how do you determine the firmware from this?
ets Jan 8 2013, rst, cause:2, boot mode:(3,6)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09f0c112
~1d

- Sun Aug 20, 2017 1:50 pm #69332 I had same problem too. Bought new ESP8266-12s, connected via Esplorer and had no AT command problems.
Updated and flashed new firmware using Esptool - no problem.

Opened up Esplorer - can't use AT commands and can't see firmware version.

Old firmware is set up to be at 9600 baud.

Need to change port speed to 115200 for new firmware

Method

Close Esplorer port.

Turn off ESP8266

Set Esplorer port at 115200 and power up Esplorer.

Firmware results in Esplorer now:

NodeMCU custom build by frightanic.com
branch: dev
commit: 569628789cdf83fa6b0e27bafa5624c6b29b701d
SSL: false
modules: adc,dht,ds18b20,file,gpio,i2c,mqtt,net,node,ow,rtctime,tmr,uart,wifi
build built on: 2017-08-20 17:45
powered by Lua 5.1.4 on SDK 2.1.0(116b762)
lua: cannot open init.lua

AT Commands

AT module was not selected when I built the firmware at frightanic.com