OTA update #611
mauroForlimpopoli
started this conversation in
Ideas
OTA update
#611
Replies: 1 comment 9 replies
-
In theory what you describe is possible.
That's impractical, at best. But why would you need to do that? You can build one firmware image for the small partition and a another one for the larger partition. They are entirely separate firmware builds so you can configure each separately. |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I will partition my memory in Ota_0 e Ota_1. If I have understand right, before the OTA the program run from Ota_0 and after the OTA, the program will start from Ota_1, if I do a new OTA the program starts from Ota_0...and so on. Can I split the memory in different size of OTA? In other hands, I wish to set Ota_0 to 300kB, and Ota_1 to 3MB and when the device starts, do an automatic update of (upbin). In the new program there is a manual request of OTA. When another OTA is request, bootbin will be charged and it will do another automatic OTA of up.bin. So I can have more space for the main program. Is it possible ? Parts of memory partition is defined in the manifest (stack...static...keys). Is there a way to change them dinamically ?
Beta Was this translation helpful? Give feedback.
All reactions