Error flashing latest Binaries

[CharlieB]

I am getting an error flashing the latest binaries esp8266-2016-07-31-v1.8.2-77-gbc39129.bin

The previous binaries still loads.

I am using NodeMCU Firmware programer (ESP8266 Flasher) on Windows OS.

[mflmartin]

What error do you get exactly?

Can you post the error output?

[CharlieB]

There is no error but just hangs out and does not complete the full binary transfer.

Once again, I am using ESP8266 Flasher program on a Windows OS.

I am not too sure, but could it be some checksum error , etc.

Goes till the end but does not complete the firmware transfer.

"esp8266-2016-07-12-v1.8.2-8-gdfe056d" successfully loads.

[CharlieB]

Sorry even "esp8266-2016-08-01-v1.8.2-79-g0e4cae5.bin" does not load.

Error : Error:Write flash timeout. (ESP8266 Flasher)

[deshipu]

Have you tried to follow the official flashing instructions? http://docs.micropython.org/en/latest/e ... e-firmware

[CharlieB]

I am on a Windows OS system.

I had/have successfully flashed the first released binary on my ESP201 system using ESPFlasher.

But the new binary does not load at all. Towards the end , it gives an error and returns back.

Is there any other tool on Windows OS to flash the Binary ?

Thank you.

[jms]

If it is reliably very near the end it could be because the binary has put on weight recently running over the file allocation table of where the FAT-based file allocation table WAS and blocks are worn out.

If so slightly nasty solutions are a special build with either some features stripped out or an unused hole placed to cover the broken area which will probably be a very small number of 4k blocks.

If you're using esptool and its default assumed flash size is less than the file size it's a major bug for it to pick up a file that is a bit large for it and not complain.

As elsewhere I recommend the NodeMCU flashing tool not that I've tried it on a >512k image.

See various postings on filesystems and broken flashes.

I have started on SPIFFS interface.

CORRECTION I am at least partly mistaken since the Flashbdev start address is 0x89000 so for now (until it puts on more weight still) the problem is more likely to be the fact 512k has been crossed and whatever you're using doesn't like it or your device doesn't have it and as I have said this is a bug. A smaller build if possible would still work

[CharlieB]

Just wondering, if I'm the only one to face this problem ? Or am I doing something wrong.

BTW, "esp8266-2016-08-01-v1.8.2-80-gb456484.bin" did not flash or work properly.

Sorry.

[CharlieB]

I flashed a ESP12F with this "esp8266-2016-08-01-v1.8.2-80-gb456484.bin" and it flashed OK.

I guess, there could be something wrong with my ESP201 board.

Sorry for the trouble.

[deshipu]

Don't apologize. We use very straightforward language here, but that's not because we are angry at you or anything -- we are just trying to communicate efficiently, and that sometimes has this unpleasant effect of the other person feeling bad.

Yes, people had similar problems to yours. So far, the problem turned out to be either wrong command used to flash, too small flash size on the module, or corrupted flash -- often due to inadequate power supplied to the module.

Are you flashing a bare module (which one?) or a development board such as HUZZAH or WeMos? If it's a bare module, make sure you are powering it from a stable source of 3.3V that can provide at least 300mA of current. Powering it directly from the USB2TTL dongle won't work.

Does your ESP8266 have more than 512kB of flash memory available? The firmware has a lot of features added and grew beyond that size, so modules with less than 1024kB of flash are no longer supported. The flashing tools won't tell you about this, because detecting the flash size is not that simple (it requires them to run some code on the module, afaik).

Finally, the instructions I linked to work perfectly fine on Windows, as long as you have Python installed.