ESP8266 Community Forum

- Mon May 25, 2015 4:51 pm #18454 Hello everbody
I just can't get my ESP8266-01 to work. After having successfully uploaded the latest NodeMCU, I get error messages when connecting to the board. I'm an using ESPlorer 0.2.0, and when I press the Open button, I get repeated error messages like "ERROR in flash_read: r=1 at 41026000". Does anybody have an idea what may have caused this behaviour?

It seems there are some parallels to the post "Running gibberish lines". The blue LED is constantly on, and sometimes the mouse on my computer starts hopping wildly around until I disconnect the board.

I don't expect the board to be damaged because I'm propperly working with a 3.3 volt output of the USB to serial adapter. However, I'm pretty new, so everything is possible

- Tue May 26, 2015 9:41 am #18510 Moin,

that sounds like the upload of the firmware was not successful.

Check serial connection at 74880 (yes: I mean 74880) and 115200 Baud.

Cal

Get your modules here:

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

- Tue May 26, 2015 3:49 pm #18535 Cal,
I get the same errors as jlessner (I think). I will try to provide a little more information.

Hardware: NodeMCU devkit v0.9
Flash Utils: NodeMCU-flasher (win x64), Flash Download Tools v0.9.6
Binary: nodemcu_latest.bin (from nodemcu-firmware github)

Procedure:

1. Hold down "Flash" button
2. Plug in USB, release "Flash" button after light stops blinking
3. Open up Flash Util
4. Select binary and set offset to 0x00000 (select DIO, 32Mbit for Flash Download Tool)
5. Select "Start"/"Flash"

Output:

1. Output shows flash completed with no errors (for both flash utilities)
2. Open up serial port (putty): 9600, 8n1, no flow control
   1. Code: Select allERROR in flash_read: r=1 at xxxxxxxx
      Where xxxxxxxx is an address that keeps incrementing (cycles through all addresses I guess).
3. Baud at 74880 and 115200 result in nonsense

The connection definitely works at 9600, but I find that odd as well because it seems as though the ESP Flash Download Tool uses a baud of 115200 by default and this appeared to have no problems. Maybe some of this information will help.

- Thu May 28, 2015 2:27 pm #18762 Hi,

I was having the same issue.
It was solved downloading the latest flasher.
https://github.com/nodemcu/nodemcu-flasher

I was using an older one from a tutorial.
I flashed NodeMCU 0.9.6 build 20150406
leaving all default settings for Baud, SPI, etc.
Just setting the path for binary file and COM