This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Differences between Application_Update and Download_Client

Hello everyone,

I was wanting to perform FOTA on the nRF9160 DK, so I decided to implement the Application_Update example, I uploaded the app_update.bin binary to our cloud, but I was not successful, the application always returns the same error:

I: Downloading: app_update.bin [0]

E: Unexpected HTTP response: 404 not found

E: Download client error

The given link has been tested and is working, you can check it by going to: http://files.wnology.io/6166de5d349eb6000894aef2/app_update.bin

In order to verify the device's ability to access and download files from our cloud, I decided to test the Download_Client example. Through this example the download link worked perfectly and the file was downloaded:

Downloading http://files.wnology.io/6166de5d349eb6000894aef2/app_update.bin

[ 1% ] | | (2048/162500 bytes)

[ 2% ] |= | (4096/162500 bytes)

[ 3% ] |= | (6144/162500 bytes)

...

Download completed in 17225 ms @ 9433 bytes per sec, total 162500 bytes

So I would like to know what is the main difference between the examples capable of causing the download not to work in the Application_Update example. I see that both use the same library (Download Client), and in the update example this library is used indirectly through the Fota_Download lib. What changes should I make to application_update to make it work correctly?

Thank you.

Parents Reply Children
Related