-->
Page 3 of 3

Re: Problem flashing NodeMCU

PostPosted: Tue Jan 24, 2017 1:10 am
by marcelstoer
alex_g wrote:I think I've done all the right things


Almost...

The default baud rate is 115'200, the rest seems fine. However,

  • With recent esptool.py versions you don't even need the '-fs' parameter as it detects the correct flash size automatically.
  • With recent NodeMCU versions (anything after 20161201, see https://github.com/nodemcu/nodemcu-firmware/releases) you don't need to flash esp init data. The firmware does that for you.

Also, if ESPlorer says "Please, reset module or continue." just reboot the device.

Re: Problem flashing NodeMCU

PostPosted: Tue Jan 24, 2017 7:48 am
by alex_g
Wow, that's all I had to do? Change the baud rate!?

It works a treat my the way, and it's SO much nicer working with ESPlorer at 115200 rather than 9600.

Many, many thanks Marcel, beer is in order... ;)

Re: Problem flashing NodeMCU

PostPosted: Tue Jan 24, 2017 7:59 am
by marcelstoer
115'200 is just the default but NodeMCU has actually got auto-baud detection. See http://nodemcu.readthedocs.io/en/latest ... art-module and http://nodemcu.readthedocs.io/en/latest/en/upload.

Re: Problem flashing NodeMCU

PostPosted: Tue Jan 24, 2017 12:48 pm
by alex_g
Ah, OK, thanks.
It's just that it definitely was not woring under 9600 baud.

Otherwise I'd never have made the above post! :D