All I can say is, thank heavens for the single BIN file and the Windows programming tools you’ll find links for here http://www.rei-labs.net/esp8266-update-firmware-to-change-the-baudrate/ and below in my Dropbox link as I’ve just restored my little ESP8266 board to working order after both the new WEB UPDATE AND the MULTIPLE BIN files failed. I have never come across a development with SO MUCH RUBBISH out there on the web. There are now numerous ways to compile code and blow it for the little board, yet go do a search – it seems it is impossible to get past the 0.9.2.2 version as everything else just plain doesn’t work or needs in-depth knowledge of Linux (and even then I’m still not seeing BIN files with any improvements). The little board STILL has error messages like “NO IS FUN” and the pesky “BUSY S” problem and inconsistent responses…despite my own blog reaching record highs with people looking in on the subject.. and if I’m getting those records – other people must be – so lots of people out there are interested but no-one seems to be able to come up with solutions.
So, does any enterprising person out there have a working guide to getting both Windows-based compilations AND Windows-based chip uploading working? I’m more than happy to start working on the code or collaborate with someone else so we can turn the little ESP-01 board into a winner we can all benefit from in our projects. I do not want to scrap my gear and build a Linux box just to get this thing going. SURELY someone has cracked this?
So for those of you struggling, the ESP8266_FLASHER and the v0.9.2.2.AT.bin files will get you out of a mess – and restore a working version – which defaults to 9600 baud and which can then easily be changed with the command AT+CIOBAUD=115200 to permanently run at 115200 baud (and as for folk saying this is too much for Arduinos I don’t buy it – just change the default buffer size for the UART if you think it’s overloading (and sadly the code in Arduino does scrap new stuff once the buffer overflows). Think about it – you don’t need an Ethernet stack any more so you could spare a few more bytes for the serial buffer!.
Here are the two files I use reliably for now – if I get improvements I’ll put them in Dropbox. You need to set the baud rate, point to the right file in order to blow the board. https://www.dropbox.com/sh/zx2ej2ehl1g7r32/AAC5ePIZkK66WFXzJhAJBb6Ta?dl=0
OIncidentally to try to get around the BUSY S problem I’ve reduced my baud rate to 57600 – made no difference at all and in any case the Arduino chips are perfectly able to handle 1156200 – with a 64 byte interrupt driven buffer that can easily be enlarged I would not expect problems there. My power supply is adequate, able to give up an amp at 3v3 but I am able to replicate the problem quite reliably when sending constant requests over WIFI to the unit… simply stop part way through and restart sending commands and there’s a good chance the unit will respond with “ready s” and continue to do that for all subsequent commands – SURELY it is not beyond our grasp to get rid of this issue..