there are various boot modes which can be chosen by different GPIO voltage levels. Is there also a way to change the currently running user binary?
Let's assume I use OTA firmware updates. One day I accidentally upload a new version which has broken OTA support. Ooops. Now I cannot correct my mistake: The firmware has a correct checksum and it starts fine. So the bootloader will run it on every power on. What options do I have besides re-flashing the module?
It would be cool if there was a special GPIO setting to force either user1 or user2...
to finalize the OTA upgrade.
Question: Is there a way to boot the new image ONLY ONCE? So that its functionality can be verified BEFORE the change becomes permanent?
Question 2: How does the bootloader (1.7) determine the current image is "broken"? I understand it reverts the change and goes back to the other image if something is wrong. But what must be wrong? I've seen it boot one image that caused an exception over and over and over again with no attempt to go to the other image. I had to reflash manually via UART.
Who is online
Users browsing this forum: Google [Bot] and 5 guests
Newbies Start Here
Are you new to ESP8266?
Unsure what to do?
Dunno where to start?
Start right here!
We also have a RTOS version and a MESH version too!
Complete listing of the official ESP8266 related documentation release by ESPRESSIF!
Must read here!