Boot esp8266 app firmware from custom address
Posted: Mon Oct 09, 2023 10:58 am
Hello Forum!
In general, I would like to make app firmware rollback mechanism for OTA updates for esp8266.
Right now, I am trying to load app firmware from custom address.
1) Updated eboot bootloader to load app firmware from 0x00080000 addr
2) Built two apps with different debug output strings ("Hello, Loop 111!" and "Hello, Loop 222!").
Uploaded two apps to flash, first app to 0x0 addr, second app to 0x00080000 addr
Second app loads and works as expected.
3) Made more changes between apps.
Added additional output string to second app. ("Additional string that will break app!")
Second app does not works correctly.
There is garbage in output.
Why does loading the second app have such dependencies on the first app?
How to broke these dependence and load second different app?
Any suggestions are greatly appreciated! Thank you!
In general, I would like to make app firmware rollback mechanism for OTA updates for esp8266.
Right now, I am trying to load app firmware from custom address.
1) Updated eboot bootloader to load app firmware from 0x00080000 addr
2) Built two apps with different debug output strings ("Hello, Loop 111!" and "Hello, Loop 222!").
Uploaded two apps to flash, first app to 0x0 addr, second app to 0x00080000 addr
Second app loads and works as expected.
3) Made more changes between apps.
Added additional output string to second app. ("Additional string that will break app!")
Second app does not works correctly.
There is garbage in output.
Why does loading the second app have such dependencies on the first app?
How to broke these dependence and load second different app?
Any suggestions are greatly appreciated! Thank you!