ESP8266 Community Forum

- Tue Nov 11, 2014 12:01 pm #2478

If it'd be of any help for you, I could send you a working example of OTA update?

No need, it will be redone from scratch. Basically I want it to be like this: You type 'upgrade http://192.168.0.1 80', it fetches all firmware files from external webserver, does any needed security checks and copies them to upper 256KiB of flash. Once the transfer is complete - copies it from the upper to the lower part of flash and erases the upper flash part. Later you can instruct your ESPs to do that automagically once in a while.

Blog|github

- Tue Nov 11, 2014 1:18 pm #2480

aha, and how you handling then the configuration for the SoC once spi flash wiped out?

Nope. I just used that to reproduce endless exceptions/reboots on my modules. Once wiped, blobs will write ap configuration into thelast few KiBs of flash no matter what. actually, each time you configure AP or join a network - blobs write thatdata to SPI flash. With password in plain text (Doh!).

i said "SoC configuration", not firmware configuration.

SoC config is something like e.g. crystal frequency, test signal en/disable, bt co-existence, etc.

I don't want to be human! I want to see gamma rays, I want to hear X-rays, and I want to smell dark matter ...
I want to reach out with something other than these prehensile paws and feel the solar wind of a supernova flowing over me.

- Tue Nov 11, 2014 1:42 pm #2482 Thats cool i hope we get it soon

upgrade http://192.168.0.1 80

ESP8266.com Moderator
Lets get the party started and +1

[url=https://www.banggood.com/custlink/KvGGhGF4wG[/url]

I like ESP8266 and ESP8285 and ESP32

- Tue Nov 11, 2014 2:22 pm #2483

i said "SoC configuration", not firmware configuration.

SoC config is something like e.g. crystal frequency, test signal en/disable, bt co-existence, etc.

Did I miss something? Is that really stored in spi flash? For I've wiped my module's flash clean several times already during development, and checked that with flashrom (Btw, wonder if it will chew up the 8MiB flash upgrade). If that's really stored there, my module would have been pretty much screwed, but it works. The only thing I found in flash that's bot actually handled by user firmware - something at the last 8KiB of SPI flash, where all AP and sta settings go automagically. As far as I could see - There were 2x4KiB erase blocks for them. One for STA, one for AP.

Blog|github