ESP8266 Community Forum

- Fri Dec 16, 2016 6:02 am #59568 I'm new to NodeMCU and ESPlorer, and I'm meeting some odd behavior, that I suspect are symptoms of deeper problems. I hope you can help me understand this and fix this.

I'm using ESPlorer version 0.2.0-rc5. The firmware is built with https://nodemcu-build.com/. It behaved the same with firmware downloaded from https://github.com/nodemcu/nodemcu-firm ... 150704.bin.

It says it can't autodetect firmware. However, it then writes exactly what firmware it is. Or is it supposed to tell even more about the firmware? But before writing this information it writes a line of gibberish.

I don't do anything at "Please, reset module or continue.", it just continues printing to the terminal without any pause.

To get the printout below, I simply connect the NodeMCU, select baud 115,200, click Connect, and then click the physical reset-button on the NodeMCU.

Code: Select allPORT OPEN 115200

Communication with MCU..Got answer! Communication with MCU established.
AutoDetect firmware...

Can't autodetect firmware, because proper answer not received (may be unknown firmware).
Please, reset module or continue.
Œc„ûgnŸdogœãäc8ä‡lrl;lpû'àƒlcoâ<Œd�|Ç„#Äónoï
>

If I do a soft reset (using the Reset-button in ESPlorer) it also prints a line of gibberish, and furthermore loses the connection (I think). After any soft reset it always ends up with printing "Communication with MCU..", and will only continue after a hard reset. I guess this is not intended behavior?

Code: Select all> Soft restart by user command
node.restart()
>
 ets Jan  8 2013,rst cause:2, boot mode:(3,7)

load 0x40100000, len 25932, room 16
tail 12
chksum 0x76
ho 0 tail 12 room 4
load 0x3ffe8000, len 2264, room 12
tail 12
chksum 0x14
ho 0 tail 12 room 4
load 0x3ffe88d8, len 8, room 12
tail 8
chksum 0xe0
csum 0xe0
Œãäƒoì›;ƒûg|ìlld$`ŒãsÛl„$„äl 

NodeMCU custom build by frightanic.com
   branch: master
   commit: 81ec3665cb5fe68eb8596612485cc206b65659c9
   SSL: false
   modules: file,gpio,http,net,node,tmr,uart,wifi
 build    built on: 2016-12-16 09:17
 powered by Lua 5.1.4 on SDK 1.5.4.1(39cb9a32)
nil
> print(uart.setup(0, 115200, 8, 0, 1, 1 ))
115200
>
Communication with MCU..

- Sun Dec 25, 2016 3:50 pm #59949

The firmware is built with https://nodemcu-build.com/. It behaved the same with firmware downloaded from https://github.com/nodemcu/nodemcu-firm ... 150704.bin.

It's actually good you tried both but just stick with the newer version and ignore the old 0.9.x binaries.

It says it can't autodetect firmware. However, it then writes exactly what firmware it is.

ESPlorer doesn't know you're running NodeMCU. Not sure why that is but I stopped wondering. However, the firmware built with my cloud service is aware of its exact configuration and prints it upon booting.

But before writing this information it writes a line of gibberish.

That gibberish is bootloader output at 74880 before the firmware switches to 115200.

https://frightanic.com/
https://nodemcu-build.com/
https://github.com/marcelstoer/nodemcu-pyflasher