ESP8266 Community Forum

- Thu Jan 29, 2015 2:42 pm #8475

AP MAC Waiting MAC
STA MAC Waiting MAC

That's what I get when I forget to restart the esp in firmware update mode. Make sure you start the module in that mode before you open the flashing tool. And make sure you point to a valid firmware file, and the box on the left of it is checked.

Flashes up 'require ("wifi")' and 'connectworld()'

That's what it does when flashing too.

Does it mean the ESP needs to be connected to 'wifi' or the PC connected to wifi?

No, I can flash with no network access.

Anyway, it seems this is not a 'standalone' application. Why not?

Because it needs a .bin file to flash into your esp?

Also how do I know what to set the default 'Flash Speed' to?

I've always used 40MHz, 9600, and 512kB.

Is there more information on this software?

Well, I didn't need much more, but the developer's written in the About tab:

If you have any questions, please contact me.
Vowstar <vowstar@nodemcu.com>

OK, I only got it to work when my PC was wifi enabled. I did have the binary files (from ESP) entered and the config set correctly. It looks to me as if it downloaded the MAC addresses from somewhere. Using a non-wifi PC, I got no further than waiting for the MAC addresses. Anyway, it may have been the sequence (is this described anywhere?) but the ESP was in boot mode when powered up. Also it seems to need the binary files entered before clicking in the Flash bar. This is not entirely obvious as I would have expected it to read the MAC addresses separately from the flashing process. I have used the read_mac command to check for a valid connection before attempting a flash sequence. Does seem a very useful tool and far better than messing around with Python and esptool.py plus a complicated command line.

However, although it completed the update (to 0.9.4) successfully (as did my esptool version) it still doesn't respond to any AT commands. It gives the usual gibberish at 75KB when powered up but there is no blue LED flash when sending AT commands and consequently no answers. The AT commands do get to the ESP OK and it works on a 'virgin' ESP (from Banggood). Is there a problem with any of the ESP AT binary files? How critical is the 3.3V supply and the 3.3V serial input? The modules all work before the attempted update using the same hardware and ESPlorer tool.

From this forum topic header, it does seem as if I am not the only one having this problem?

Mike Bolton

- Thu Jan 29, 2015 4:37 pm #8481

Mike,

you are The HERO! Thank you very much for your write-up! I think it should be on the title page... somewhere. It would be absolutely invaluable for the noobs, such myself.
Also, thanks for the Russian software - it is extremely handy. I was using the serial monitor by ElectroDragon before and could not get any response from the module. It turned out that I was not using the "end of the line" character. The monitor you recommend has it as default and I am communicating to ESP! Moreover, it connected to my router.
Arduino is next.

Thanks for the compliments but I have now found a much better solution as suggested by MeNoGeek. The nodemcu package really is the answer to flashing an ESP in a Windows environment. No command lines, Ptython, esptool etc. Absolutely nothing to set up except just load the program from the ZIP file. Put a 'shortcut' to the exe file on your desktop. Even has a nice icon.

https://github.com/nodemcu/nodemcu-flasher

Just ensure that you load the binary files by clicking on the 'blue blob' at the ends of the green lines in the 'config' menu. (Not obvious, found it by accident). You select the four binary files (from espressif) like you select any Windows file. The default load addresses for these are already set up in the Flasher software but you can change these if you have different binaries.

Also, it seems, you need to power up the ESP in its bootload mode (GPIO0 = 0v) before starting the Flasher. After loading the required binary files, go back to 'Operation' and click on Flash. It will show the MAC addresses and then program it and report with a green blob when finished. You can check what it has done in the 'Log' menu.

A great piece of software for those 'NoGeeks' like me who use Windows. My ESP still doesn't respond to the AT commands though. No blue LED flash. Looking more and more like a problem with the espressif AT binary files as I get the same non-result using different loaders. (unless the ESP8266 modules from Banggood are non-standard or faulty somehow)

Regards

Mike Bolton

- Fri Jan 30, 2015 9:20 am #8519

How critical is the 3.3V supply and the 3.3V serial input?

All digital IO pins should be protected from over-voltage and ESD. However, you might want to check that your serial adapter doesn't output 5V signals. There's a video on how to do that with a multimeter (search the forum with those two words.)
Did you mention what kind of power supply you're using? Most issues are due to a weak PS, and the 3.3V from almost all USB adapters is not good enough unless you add a capacitor to cope for voltage drops.
And why not try the NodeMCU Lua firmware, and see if your module works better with it?

- Fri Jan 30, 2015 4:26 pm #8546

How critical is the 3.3V supply and the 3.3V serial input?

All digital IO pins should be protected from over-voltage and ESD. However, you might want to check that your serial adapter doesn't output 5V signals. There's a video on how to do that with a multimeter (search the forum with those two words.)
Did you mention what kind of power supply you're using? Most issues are due to a weak PS, and the 3.3V from almost all USB adapters is not good enough unless you add a capacitor to cope for voltage drops.
And why not try the NodeMCU Lua firmware, and see if your module works better with it?

I am a professional hardware engineer with many (40) years of experience in this field. The power supply is a local linear regulator rated at 1.5 amps. Input supply is 3.3 amps so regulator is not dropping out. Measured voltage 3.35V. The serial connection is a RS232 IC with the output limited to 3.3V. Serial polarity is correct. All voltages are correct on a good DSO. My ESP modules all work correctly when received so hardware is OK. (9600B default but settable to 115200 using AT+CIOBAUD=115200) . I have used both the esptool.py and your nodemcu-flasher to upgrade to 0.9.4. Same result. No response to AT commands and no blue LED flash. I can repeat the flash process as many times as I like and no errors are reported (no damage apparently). I am not the only one to report this problem. I also have a colleague on the same project who has successfully re-flashed the same make of module with the same binary files but using a Mac PC. Mine is Windows XP. Could this account for the difference? I even have a 'dump' of the whole sequence as a binary file (using the esptool.py) and can't see anything actually wrong with it. Also tried with both a genuine RS232 port and a USB to serial adapter. Same problem. Am now stuck for upgrading and have two non-functional ESP8266-01 modules. My one remaining original works fine, AT commands etc. in the same hardware.

Mike