<![CDATA[Ability to prevent firmware rewriting]]>Once the code is developed, it would be great if there was a physical way to prevent firmware rewriting (such a fuse to blow or a wire to cut)

]]>https://community.m5stack.com/topic/3818/ability-to-prevent-firmware-rewritingRSS for NodeTue, 28 Apr 2026 23:52:00 GMTSat, 11 Dec 2021 11:08:50 GMT60<![CDATA[Reply to Ability to prevent firmware rewriting on Mon, 12 Sep 2022 11:20:09 GMT]]>@brus
In my opinion, do a hardware fuse is not a good idea, because updating the programm would not be possible anymore.
But to have a password protection would be good.

Becuase when the devices are spread or installed. People could overwrite the firmware or the development using the uiflow webapplication, they just need to know the API number and thats easy to find when booting up and changing the menu.

if on Uiflow you must enter a password, this would also help to protect from overwriting the programm but you would be able to install an update.

]]>https://community.m5stack.com/post/18588https://community.m5stack.com/post/18588Mon, 12 Sep 2022 11:20:09 GMT<![CDATA[Reply to Ability to prevent firmware rewriting on Fri, 01 Jul 2022 08:24:26 GMT]]>Take a look @ https://docs.espressif.com/projects/esp-idf/en/latest/esp32/security/flash-encryption.html

]]>https://community.m5stack.com/post/17862https://community.m5stack.com/post/17862Fri, 01 Jul 2022 08:24:26 GMT