AWS FOTA fails when using my upload.bin file for nrf9160

[hmichel]

Previously I have been successful getting the AWS FOTA update working using the AWS FOTA example project, the example update.bin file and location provided

by Nordic for the nrf9160. I did have excellent help from Nordic to get that working.

Now I have created my own update.bin from the AWS FOTA project

1) Create update.bin by making a build (get its exact file size from Windows Explorer)

2) Create an s3 bucket for the update.bin file (it has logging turned on)

3) Create another s3 bucket for the logging of events from the bucket with update.bin

4) Upload the update.bin file to the s3 bucket

5) Create a json file to point to the update.bin file

6) Upload code to nrf9160 using Segger

7) Wait for LTE connect complete and board ready for update by observing Termite terminal 

8) Create a job to perform FOTA update using the update.bin file

9) Get MQTT disconnect error

here are related screen shots

[Øyvind]

Hello,

First of all, what version of NCS are you running and what is current modem FW?

I see that you have configured your job file for an HTTPS address. Have you configured this accordingly as described in the download client? In the original job file example shown in AWS FOTA library, the address points to a nRFCloud address using HTTP.

Error message -57 is defined as follows:

ENOTCONN 57     /* Socket is not connected */

Kind regards,

Øyvind

[hmichel]

Dear Øyvind

The NCS version is 1.0.0

The Modem Firmware is 1.0.0

[hmichel]

When I change the prefix from HTTPS to HTTP the process starts as before and then get stuck in the "In Progress" state.

Also after I cancel the job there is no log file in my logging S3 bucket but there was one

when the prefix was HTTPS

[Øyvind]

Thanks for the update. First of all, please update your modem version to v1.0.1.

I am currently not able to test the setup, as I am out of the office. Will get back to you within tomorrow. 

Kind regards,
Øyvind

[hmichel]

I will update to V1.0.1 today. Thank you for the help. Especially since you are not at the office

[hmichel]

I updated to Modem version 1.0.1

Then I ran the update using the http prefix in the json file

Then I ran the update using the https prefix in the json file

in both cases the interaction starts when I start the job but then hangs even though I wait several minutes see screen below