You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I mean by dual OTA is one OTA will responsible for checking any OTA provisioned by the things board ide, and another OTA will update the OTA updater!
If we make changes to the device token or wifi config we can send a new OTA to the device to adapt those changes into the 1st OTA partition and the same bin file will be responsible if there are any changes in pin config to the device OTA? Can we do that?
The text was updated successfully, but these errors were encountered:
Sorry the question is slightly confusing, just to be sure.
First of all I am assuming you are using an ESP32.
From what I can discern from your text you want to change the configuration of your device, because you want to use OTA for that process I am assuming those variables are hardcoded in the code itself.
same bin file will be responsible if there are any changes in pin config to the device OTA
I sadly do no quite understand what you mean with this part.
What I've done in the past, is copy all the firmware functions and strings, rename it to software.
This way you are able to use the update software function on thingsboard server.
The only difference is the last stage, where I save it to spiffs. Then I use a RPC to transfer the file to a STM32F connected to the ESP32.
What I mean by dual OTA is one OTA will responsible for checking any OTA provisioned by the things board ide, and another OTA will update the OTA updater!
If we make changes to the device token or wifi config we can send a new OTA to the device to adapt those changes into the 1st OTA partition and the same bin file will be responsible if there are any changes in pin config to the device OTA? Can we do that?
The text was updated successfully, but these errors were encountered: