How to perform aws_fota using asset tracker application

[venkatesh dyagala]

Hi Team,

We are using nRF9160 DK, we tested that asset tracker application, that was working fine, We also tested the aws_fota (firmware update via AWS) that was also good. But going through asset tracker documentation we found that asset tracker default supports aws_fota.

So here are my questions

1. Do we need to change any files in the asset tracker application to perform aws_fota. If yes what was the modifications we need to do in asset tracker application?
2. Where do update the firmware versions, security tags etc in the asset tracker, do we need to change the parameters like this or we do not ?
3. How to know that the device is connected to the AWS cloud (As we see the device status in nrf connect but not in aws) ?
4. Is there any documentation to perform aws_fota on assert tracker application?

Please guide me through the solution 

Thanks,

venkatesh

[Håkon Alseth]

Hi,

 

Do we need to change any files in the asset tracker application to perform aws_fota. If yes what was the modifications we need to do in asset tracker application?

 No changes needed, its default enabled.

Where do update the firmware versions, security tags etc in the asset tracker, do we need to change the parameters like this or we do not ?

 For updating certifications, please see this blog post:

https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update

 

How to know that the device is connected to the AWS cloud (As we see the device status in nrf connect but not in aws) ?

Do you mean nrfcloud?

If so, it should be in the dashboard on nrfcloud.com.

 

Is there any documentation to perform aws_fota on assert tracker application?

Yes, you can create a "update bundle" by clicking on the hamburger menu in the top right corner when you're logged into nrfcloud.com. When you compile your application, asset_tracker in this case, you can then take the app_signed.hex in your build folder and create a update bundle.

 

Once you click on your device, which should be connected under "devices", there should be an "updates" card where you can select your newly created update bundle and send it to the nRF9160 device.

 

Kind regards,

Håkon

[venkatesh dyagala]

Hi Hakon Alseth,

Thanks for the information, Just a small correction. 

We performed firmware update using  AWS by using the aws_fota application in samples/nrf9160/aws_fota. We also came to know that we can also update by nrf_cloud using device update bundles.

I have some questions regarding that

• Is there a possibility to use AWS and nrfcloud in a single project ?
• So do we have any applications that support AWS iot console and nrfcloud? If yes what are the changes we need to apply?

Thanks,

venkatesh

[Håkon Alseth]

Hi,

 

venkatesh dyagala said:

Is there a possibility to use AWS and nrfcloud in a single project ?

Technically yes, but I am not sure that this will work due to how the library dependencies are written and designed.

 Note also that there are restrictions on the amount of secure sockets, as per the limitations from the modem release notes:

- Up to three simultaneous TLS/DTLS connections are possible.

 

 

venkatesh dyagala said:

So do we have any applications that support AWS iot console and nrfcloud? If yes what are the changes we need to apply?

The asset_tracker uses aws_fota, as shown in the project file (link), but it targets nrfcloud.com API to do this.

The fota libraries aren't designed to have several sources of fota, as the library fota_download isn't re-entrant, meaning that if you initialize it twice, you will overwrite the first configuration.

 

Is there a reason why you need two management platforms for FOTA?

 

Kind regards,

Håkon