ESP8266 Community Forum

- Wed Nov 02, 2016 6:57 pm #57568 Hi, I've just recently bought a NodeMCU devkit 0.9 and started the tutorial to flash the latest firmware and try to run my first code. So, what I did was to build my fw here:
https://nodemcu-build.com/index.php

Then I uploaded to the device using this command:

Code: Select allesptool.py --port COM6 write_flash -fm dio -fs 4m 0x00000 nodemcu-master-10-modules-2016-11-02-19-01-16-integer.bin

Just for testing I tried to read the mac address, so here it is - it works:

Code: Select allesptool.py --port COM6 read_mac
esptool.py v1.1
Connecting...
MAC: 5c:cf:7f:1b:7a:c2

Cool, so it must work in the IDE too! Haha... No...
After opening ESPlorer all it did was the following screen:

(After pressing the connect button)

After I found this forum, I tried to find another IDE, so I found ESPCut, which seemed to be blazing-simple & amazing, so tried. Failed... Here's the log:

Code: Select allConnected [\\.\COM6], [115200]
Try to recognize firmware...
WD Error. ESP is not responding
Try to recognize firmware...
WD Error. ESP is not responding
Try to recognize firmware...
WD Error. ESP is not responding
Loading files list.
WD Error. ESP is not responding
Disconnected

So, actually I can talk to the ESP module via esptool.py, but nothing else.
Does anyone have any idea what could cause this or how to start debugging? I'm newbie to NodeMCU

My device looks like this (actually this is it):
https://imgur.com/a/LLIP4

Thanks for every comment!

- Wed Nov 02, 2016 11:44 pm #57572 Sounds like what I ran into.
The little red box in the middle of https://nodemcu-build.com/index.php talks about remembering to upgrade the SDK on the ESP8266 when updating the firmware and links to http://nodemcu.readthedocs.io/en/latest ... g-firmware which tells you how to make sure the proper SDK is flashed to the chip.

- Thu Nov 03, 2016 1:06 am #57575

http://nodemcu.readthedocs.io/en/latest/en/flash/#upgrading-firmware

The email you get from the service contains a link to the documentation that explains how to flash properly. That may of course depend on the branch you built the firmware from.

So, the link above ('latest' -> dev branch) may or may not be correct for you. If you built from the master branch then it'd be http://nodemcu.readthedocs.io/en/master ... g-firmware i.e. you'd also have to flash esp init data manually.

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

- Thu Nov 03, 2016 4:25 am #57582 Sorry, totally forgot to mention that I run

Code: Select allesptool.py --port COM6 erase_flash

Every time before flashing any of my image.

According to the guide:

NodeMCU will automatically flash this file to the right place on first boot, if the sector appears to be empty.

So, I didn't burn esp_init_data_default.bin, as I'm trying to burn the latest master (non-dev) firmware.

So, I tried re-flashing with esp_init_data_default, it might help my issue, let's see Here's my code:

Code: Select allesptool.py --port COM6 erase_flash
esptool.py --port COM6 write_flash -fm dio -fs 4m 0x00000 nodemcu-master-10-modules-2016-11-02-19-01-16-integer.bin 0x3fc000 esp_init_data_default.bin

The error message is exactly the same again. Flashing succeed, but I can't connect to the device :/
And I just recently found something really strange... After plugging it off & on from USB, my ESP8266 device's LED is going crazy, it's blinking really fast without stopping and access to the COM6 port became access denied (Wtf?). Plugging to a different port made it possible to erase flash. (Windows bug probably?)