nodemcu starting to act funny...

[eradicatore]

So not sure what changed, but up till now I've been doing the following to "watch" the board running and whatever print statements I have with a serial terminal based on the following steps:

1) plug in the board usb to PC
2) start up termite serial terminal
3) connect to com12 at 115200 bps
4) hit the little nodeMCU reset button
5) watch a bunch of garbage chars spit out (always about the same it seems)
6) then watch my prints show up fine

Now I get errors like this:

Code: Select all

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

load 0x40100000, len 32028, room 16 
tail 12
chksum 0x40
ho 0 tail 12 room 4
load 0x3ffe8000, len 1092, room 12 
tail 8
chksum 0x17
load 0x3ffe8450, len 3000, room 0 
tail 8
chksum 0x56
csum 0x56

Any idea? sometimes this happens and then a repeated wdt reset happens??

[pythoncoder]

What version of firmware are you running?

[eradicatore]

I'm using this command to flash (which by they way I did try to totally wipe and start over):

esptool.py --port /dev/ttyUSB0 --baud 460800 write_flash --flash_size=detect -fm dio 0 esp8266-20170108-v1.8.7.bin

[eradicatore]

Maybe I should also mention I am using the cross compiler for windows called mpy-cross_pycom.exe. I actually just tried using the latest firmware based on your question, and now I get "imcompatible .mpy file"? Hmmmm

[pythoncoder]

I'm not a Windows user but as a general point the version of cross compiler should match the version of firmware. This is because the bytecode format is subject to change, giving rise to the error message you're seeing.

[eradicatore]

Sure, thanks. I'm going to give it a go to use docker (https://github.com/dockcross/dockcross) to cross compile mpy-cross for windows and see if I can get an updated mpy-cross.exe that works for the latest firmware. I'm not familiar though with the "Pycom" version that roberthh has on his github https://github.com/robert-hh/Shared-Stuff I'll have to see if mpy-cross has options when building for pycom I guess.