ESP8266 Community Forum

- Mon Apr 27, 2015 1:38 pm #15829

Is the ESP 12 different to ESP 01 when printing the boot message?
My ESP 01 print the boot message at 74880 baud, then switch to 115200 (normally no output if boots ok, RTC MEM CHECK errors sometimes or FATAL EXCEPTION on dsleep wakeup (see other thread))
and then switch to the baud rate defined in the nodemcu startup code, typically 9600 baud.

I don't think they are different in that aspect. I just used the ESP-12 module to conveniently be able to connect XPD_DCDC to EXT_RSTB.

Same here on Reset caused by pressing the reset button: boot message at 74880 baud, then Lua prompt.

But the WDT reset message seems to be sent at 115200 baud. I tried this on an ESP-01 board:

Code: Select all> tmr.delay(7000000); for i = 1, 1000000, 1 do a=1 end


So I have 7 seconds to switch the Termite terminal to 115200 baud after sending the line. The for loop then causes the WDT to bite, and the message is sent at 115200 baud.

In reality I change the NodeMCU default baud rate from 9600 to 115200 in user_main.c, so no switching is necessary. 9600 baud is needlessly slow anyways.

- Tue Apr 28, 2015 3:12 am #15886

I didn't managed to play with my ESP 12 yet.

You can also reproduce this with an ESP-01 module:

* Enter

Code: Select allwifi.sleeptype(wifi.MODEM_SLEEP)
node.dsleep(1000000, 4)

* After one second the module sends the boot message and remains unresponsive due to not having XPD_DCDC connected to EXT_RSTB.

* Now reset the board manually by pulling EXT_RSTB to low and release it again.

The chip will get noticeably cooler now due to only consuming 13 mA. You can enter commands at the Lua prompt, and after 20 minutes, the WDT bites, sends the message at 112500 baud, and the current consumption rises to 70 mA again.

Performing another manual reset lowers the current consumption again, and after 20 minutes everything repeats.

- Wed Apr 29, 2015 2:08 am #15973 I have XPD_DCDC connected to EXT_RSTB on my ESP 01.

I will try when I find some minutes.

Cal

Get your modules here:

https://www.banggood.com/custlink/KvGGhGF4wG

- Fri May 01, 2015 9:57 am #16189 Moin,

I was able to reproduce your problem with firmware version based on current dev version.

I does NOT happen using this SDK 1.0 based firmware I am looking at.
(https://github.com/chadouming/nodemcu-firmware, more or less dev096 branch, some modules deactivated , Makefile optimizations, SDK 1.0 libs (I didn't check exact version)I.

So your problem may be already fixed in newer SDK.

I open a new thread on SDK 1.0 issue:
viewtopic.php?f=24&t=2826

Cal

Get your modules here:

https://www.banggood.com/custlink/KvGGhGF4wG