Mega (V2.0.0) OTA firmware updates on 1MB modules

[Martinus]

If you have uploaded the newer stock Mega ESP Easy firmware to 1MB modules like the ESP-01 or the Sonoff, you will no longer be able to use OTA because the firmware is a lot larger (533k) and there's not enough free space to hold a temp copy of a newer upload. You can use a workaround by uploading a smaller image and then upload a normal size image after that.

We have provided a very small sketch to use this workaround:
https://www.letscontrolit.com/wiki/inde ... g_firmware

Martinus

[grumpy]

Where can I find this small sketch?

[grovkillen]

From the wiki:

ESPEasyUploaderMega

http://www.letscontrolit.com/downloads/ ... erMega.zip

[RichEO]

I was having major slowdown when I had an MQTT controller enabled. So I decided to update to a newer version.

I uploaded the small sketch, the upload said it completed successfully but the device dropped off my network.

I have power cycled the device (a sonoff SV) and it is not showing up on my router.

Has anyone experienced this? It is inside my gate motor so in a few days I will open it up and reflash it, but maybe before then anyone has any ideas what is wrong?

[kenkoknz]

Hi @grovkillen,

I flashed a sonoff(1m) with normal 1044 bin (716k) and a esp01 (puya) with dev puya 1024bin(785k) just using the normal flashESP8266, and it all seems to work normally. I can access both OTA to cnfig etc. Can you clarify if the special sketch is needed as both the files are over 533k and seems to be working fine with normal flasher?
Thanks,
Ken

[grovkillen]

Current releases are too big for OTA (2 step procedure for 1Mb units). We need to rethink how to support those units. They need to be physically attached using cable and serial programming to be updated. Sorry for any inconveniences but hopefully we can think of something.

[kenkoknz]

Hi,
This is really just a minor inconvenience, there are possible lots more urgent things on your plate to get a stable release 2. Connecting a cable for firmware upgrade is not too much of a hassle, I think we are just getting a bit lazy...

Keep up the good work,

Cheers,
Ken

[sheppy]

I hope a working OTA solution can be found, I have 38 ESP's, many are in difficult to access locations, and I have just discovered a possible DHT Humidity bug in the January Sketch I used

[ewaldharmsen]

I also look forward to be able to update OTA my devices!

[ewaldharmsen]

In the mean time: home can I make a custom build with only the plug-ins included I need?

[grovkillen]

I think we're beyond the point of OTA even with no plugins in the compilation. I might be wrong though.

[TD-er]

Please have a look at the file define_plugin_sets.h and PlatformIO.ini.
Those two make it clear how the different builds are made together.
It should be possible to perform OTA on 1 M modules, when using 2-step flash. But some changes have to be made.

- filesize of the config,dat file has to be reduced to something like 36k (rest is not used)
- Flash layout may have to be changed to 1M.64k (current is 1M.128k)

At least the last step will render existing installations invalid.

[Methuselah]

Current releases are too big for OTA (2 step procedure for 1Mb units). We need to rethink how to support those units. They need to be physically attached using cable and serial programming to be updated. Sorry for any inconveniences but hopefully we can think of something.

What would be helpful is a configure script, a-la linux's "configure" which automatically enables base functionality (based on the type of device the user specifies) and then prompts the user to add in optional modules for those features s/he is going to use. For example I do not use the MQTT functionality whatsoever and could easily eliminate that from a build.

Unfortunately, the size of this project is only going to grow, as more and more functionality is added in... eventually it will get to the point where the builds will be too big for the 1MB modules, and then a whole bunch of people will be orphaned.

[grovkillen]

Current releases are too big for OTA (2 step procedure for 1Mb units). We need to rethink how to support those units. They need to be physically attached using cable and serial programming to be updated. Sorry for any inconveniences but hopefully we can think of something.

What would be helpful is a configure script, a-la linux's "configure" which automatically enables base functionality (based on the type of device the user specifies) and then prompts the user to add in optional modules for those features s/he is going to use. For example I do not use the MQTT functionality whatsoever and could easily eliminate that from a build.

Unfortunately, the size of this project is only going to grow, as more and more functionality is added in... eventually it will get to the point where the builds will be too big for the 1MB modules, and then a whole bunch of people will be orphaned.

We have much in plan for the upcoming autumn and next year will be great. 1MB users are not going to be left in the dust.

[Djoe]

I have try to update a sonoff basic (1m) like this :

- I have build my own firmware with a size of 580kb approximately
- I have uploaded it in the sonoff
- Now I can upload ESPEasyUploaderMega_1024 through OTA, the first step
- The sonoff reboot and I select the same custom firmware (580k)

But after the reboot the new firmware not start... The wiki say that we can upload max 604k, so I think my firmware is okay ?

Is someone have already use ESPEasyUploaderMega_1024 successfully ?

Thank you and have a good day!

[neoseb]

Hi all

Very interested by this topic and by knowing how to build my custom lighter firmware for my Sonoff so that I will be able to update them as they will not be easily accessible in the coming weeks (they'll be used for my covers!)

Is there a tutorial somewhere in the web? Didn't fond anything yet.

Thank you for your help.

[Djoe]

Is there a tutorial somewhere in the web? Didn't fond anything yet..

You can have a look to :

https://www.letscontrolit.com/wiki/inde ... platformio