This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

AWS FOTA Update inconsistent

Hi dev team,

I am using a Thingy91 device along with the NCS v1.5.1.

I used the AWS FOTA example for firmware upgrades and I integrated the example in my code.

The FOTA update works for me but sometimes it hangs. It works for me once and the next time it hangs and says job rejected. 

I am attaching the log of the behavior I am seeing. The FOTA works the first time and then when I try to do a FOTA once again, it says job rejected.

FOTA updates once, fails once.txt

I also tried using the AWS_FOTA sample and experienced the same behavior. Can anyone in the team who has used FOTA through AWS try and check this out ?

Regards,

Adeel. 

  • Hi Adeel,

    Good to hear that you figured out what was causing the issue, and that you were able to create a workaround for now.

    Have you tested how this works with the AWS FOTA sample, is the behavior the same there when you have a job in queue before your device connects? It might be related to how AWS IoT notifies your device about a job. As I have mentioned before, in the sample the device receives notifications about available jobs through MQTT, by subscribing to the app_fw_update job topic. So it might be that AWS IoT only sends a notification on this topic when the job is created. If so, you should see the same behavior in the AWS FOTA sample as well, and you will have to implement something so that it will notify your device later if it is not connected when the job is created. The other possibility is that there is something on the application side that causes you to not receive this notification.

    Modem trace is used by us to look at the communication with the modem, to try and figure out what is wrong if for example a disconnect happens. Since it seems like you have figured out what the problem it, I am not sure a modem trace is necessary, but you can still get one if you are still seeing errors from the modem in your log. You must use the Trace Collector in nRF Connect for Desktop to get a modem trace. The guide for doing this with Thingy:91 can be found here. Make sure that you have updated the board controller firmware and enabled tracing in the application.

    Best regards,

    Marte

Related