-->
Page 2 of 3

Re: A new kid on the block - NodeMCU PyFlasher

PostPosted: Sun Jan 08, 2017 3:31 pm
by jankop
I believe for your ESP8266 you should use DIO rather than QIO?


Why? I never had any problem with esp8266-01, 12F or Sonoff and nodemcu-flasher, that works well.


I tested now DIO mode with the same result.

Re: A new kid on the block - NodeMCU PyFlasher

PostPosted: Sun Jan 08, 2017 3:39 pm
by marcelstoer
jankop wrote:Why? I never had any problem with esp8266-01, 12F or Sonoff and nodemcu-flasher, that works well.


That's fine, of course it depends on the specs of your specific module(s) but the NodeMCU documentation says

mode is qio for 512 kByte modules and dio for >=4 MByte modules (qio might work as well, YMMV)

Re: A new kid on the block - NodeMCU PyFlasher

PostPosted: Sun Jan 08, 2017 4:05 pm
by jankop
I dare say that this is not entirely accurate. I've never had esp8266 > 4MB but most of the programmed modules 4MB run as QIO.

Re: A new kid on the block - NodeMCU PyFlasher

PostPosted: Thu Jan 12, 2017 12:51 pm
by jankop
Hi Marcel,
I tested a new version 0.2.0 of flasher.
It's good, but it does not work when using extension "wipes all data".
It hangs on the connecting.
Could not this program remember the last used COM port please?
Thanx
Pavel