- Fri Aug 12, 2016 7:29 pm
#52812
I got a couple of NodeMCU's yesterday and started playing with them, but I'm having some frustrating issues.
One of the issues is with updating the firmware:
The first thing I did was flash it with the default from the NodeMCU Flasher (I noticed that I didn't need to push any buttons etc [doing so doesn't make any difference], other than resetting it _after_ the flashing), but albeit it has MQTT built in, it doesn't have the modules for DHT etc.
So I used NodeMCU-build to build a "custom" firmware with the standards + dht, mqtt and ws2812*. Since I want to control some "neopixels" + measuring the temperature etc.
But after I've burned it to the unit (using NodeMCU Flasher), it starts acting weird, the LED on the ESP starts flashing like crazy, and when I opened the serial connection all I got was garbage.
I tried some different things and when I set the baud to 115200 I get something that looks a bit like assembler:
The same "code" repeated over and over again (at a full speed)
I find this really weird (and annoying!), the fact that it's actually outputting something legible must mean that the firmware isn't corrupted!?!?
I can then flash the default firmware again and it's back to "normal"...
Any ideas on how to fix this??
(* All modules: dht, file, gpio, mqtt, net, node, tmr, uart, wifi, ws2812 )
One of the issues is with updating the firmware:
The first thing I did was flash it with the default from the NodeMCU Flasher (I noticed that I didn't need to push any buttons etc [doing so doesn't make any difference], other than resetting it _after_ the flashing), but albeit it has MQTT built in, it doesn't have the modules for DHT etc.
So I used NodeMCU-build to build a "custom" firmware with the standards + dht, mqtt and ws2812*. Since I want to control some "neopixels" + measuring the temperature etc.
But after I've burned it to the unit (using NodeMCU Flasher), it starts acting weird, the LED on the ESP starts flashing like crazy, and when I opened the serial connection all I got was garbage.
I tried some different things and when I set the baud to 115200 I get something that looks a bit like assembler:
Code: Select all
ets Jan 8 2013,rst cause:2, boot mode:(3,7)
load 0x40100000, len 23988, room 16
tail 4
chksum 0x81
load 0x3ffe8000, len 2184, room 4
tail 4
chksum 0x9a
load 0x3ffe8888, len 8, room 4
tail 4
chksum 0x19
csum 0x19
rf_cal[0] !=0x05,is 0x00
The same "code" repeated over and over again (at a full speed)
I find this really weird (and annoying!), the fact that it's actually outputting something legible must mean that the firmware isn't corrupted!?!?
I can then flash the default firmware again and it's back to "normal"...
Any ideas on how to fix this??
(* All modules: dht, file, gpio, mqtt, net, node, tmr, uart, wifi, ws2812 )
