-
-
Notifications
You must be signed in to change notification settings - Fork 347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTA rBoot v. #2105
Comments
Added the following upon receipt of OTA request Also, the callback never happens so it appears to never switch roms. |
Here is some serial output. First, from flash via UART :
... some minutes ...
|
Turned on debugging and in going through output I see the pertinant parts : Mqtt receives the message, it unsubscribes, and closes TCP, then flash upgrade starts ...
but then MQTT restarts ... this is problem
|
Hmm... ok, removed this problem by having MQTT safe the info to SPIFFS and cause software reboot. On boot, before MqttClient is instanciated, check for OTA param file, then rBoot ... there is no MqttClient in this boot sequence now. The result is the below ... something is still wrong here, it does not switch roms. ''' 130648 mount res: 0 Sending message : 0xa1 20 5 0 0 eb 5e df fa ff ff 14 scandone connected with 21BirchleaAve, channel 1 ip:192.168.1.101,mask:255.255.255.0,gw:192.168.1.1 load fileOpen("ota.txt") = 2 ... 17241447 Nothing in the waiting queue |
Noticed the rom addresses aren't what is specified in the that was fixed with
But still, at the end of loading the file, the callback does not happen. ...
|
Ah! Ok, although the example shows loading a rom and then spiff section ... the rBoot only works with loading ONE file and then rebooting. So, for my case above, I was attempthig to load both roms. If I load just one, it works fine. I suspect the isue may be here ... by using the delegate So, I don't have a fix but call out the issue.
|
I have a project with MQTT client and am attempting to use rBoot also. Config file is thus :
Upon publishing URL to a topic, the MQTT calls :
The ota functions are lifted from the basic sample :
when monitoring the python http server, only rthe following request is made (it completes as per monitoring with wireshark) :
192.168.1.101 - - [26/Aug/2020 00:36:49] "GET /rom0.bin HTTP/1.1" 200 -
Notice that there is no second call to the file
spiff_rom.bin
as the message to mqtt is :and that the callback
OtaUpdate_CallBack
never gets executed.When I attempt to execute the OTA update a second time, the system crashes. Here is the crash report from the dump :
Am I doing something wrong?
The text was updated successfully, but these errors were encountered: