Ok if you want a factory partition that can do ota then you just need 1 factory partition and 1 ota partition. Factory reset will clear otadata partition and boot from factory and after ota will boot from ota. Then you have to decide how to reset user data.

If you just want to reset some data why can't you build all the necessary functionality into one app?

Thanks for sharing. You didn't like console component?

WiFive, the output of "espsecure.py digest_secure_bootloader " is the digest with the image appended, so secure_bootloader.bin should be OK to flash at offset 0x0. Oh, that's not really clear in docs To generate a bootloader digest: espsecure.py digest_secure_bootloader --keyfile ./securebootkey.bi...

mikemoy wrote: ↑

Fri Nov 30, 2018 3:16 am

https://www.mouser.com/ProductDetail/Es ... 8ezw%3d%3d

Those are only 4MB but it is cool they have 24k in stock.

Try grid connect?

I still don't see where you are writing the actual bootloader to 0x1000

Right but base-increment.local is not as useful as base-knownvalue.local. how does a browser mediate conflicts for multiple base.local responders? First to reply? It could be a different device every time.

1. Don't let anybody get unencrypted bin file
2. It will always be backwards compatible (unless release notes say otherwise)

Also possible the touch fsm is not getting disabled/reset during those reset events. You could modify the bootloader to make sure touch is deinit and rtc gpio is deinit.