nRF9160 modem FW FOTA Updates

[Jack Panetta]

Hi,

I have a few questions regarding the modem FW updates on the nRF9160.

1. It is my understanding that for new major versions of modem FW (i.e. Feature releases) there is no way to update the modem firmware via FOTA. So lets say I release a device into the field with modem FW version 1.x.x. Whenever the carrier (in my case its Verizon) mandates a modem firmware update, will Nordic continue to release modem FW delta updates for the lifetime of the device? Will there ever be a scenario where Nordic stops supporting 1.x.x and I have to physically retrieve the device from the field in order to update to some new major version (i.e. 2.x.x)?

2. Is there any way to do a modem FW delta image update via serial instead of http? For example, is it possible to modify the AWS FOTA sample so that the delta image is passed over via a UART connection and then sent to be programmed into the modem?

3. What does the modem FW process as a whole look like. For example I want to know the steps that all parties involved take from mandating a modem fw update to it actually being applied on the device. For example, i think it looks something like this:

1. The carrier mandates a modem FW update
2. Nordic takes those required updates and creates a delta image for the modem FW
3. Nordic releases that image to all customers (me)
4. The customer (me) deploys that update to some cloud hosted platform
5. The device sees there is a delta image and downloads that image
6. The device updates the modem FW with the delta image

Any help in this would be greatly appreciated.

- Jack Panetta

[Heidi-Irene Harvey Sollie]

Hi!

I'll need a few days to gather answers to all the questions as they touch on a lot of different areas of the company.

Best regards,

Heidi

[Jack Panetta]

Great, thanks for the heads up!

[Jack Panetta]

Any updates on this yet?

[Heidi-Irene Harvey Sollie]

Hi, I'm still gathering some answers with a deadline by the end of this week. Is that okay?

[Heidi-Irene Harvey Sollie]

Hi, I apologize for the delay. I hope we have answered your questions sufficiently. Let me know if you need more information or something is unclear.

1) Nordic's current nrF91 modem FOTA is designed to fix bugs and corrections to keep devices in the field running. These are differential updates that can update minor updates, i.e from 1.1.x to 1.1.x+1. It is correct that this will not cover major updates and feature additions, i.e transitions from 1.1.x to 1.2.x. 

We intend to support all certified modem firmware for the lifetime of the product. This means that if a carrier mandates a firmware update Nordic will release a delta image and certify as needed. Delta images are small to limit the cost of updates

 

2) 

We do not have that today, but it is possible to change our FOTA to a serial DFU instead. Take a look at the DFU target library here. It would look something like this:

 

int img_type = dfu_target_img_type(serial_buffer, len);
dfu_target_init(img_type, file_size); 
while(serial_buffer != empty)

{ dfu_target_write(serial_buffer, len_available_bytes); }

dfu_target_done(true);

3) 

In practice, the carriers will not mandate sudden updates unless a bug or issue is discovered. It will first be a process between the end-customer (who is likely to experience the issue first) and Nordic. Then with the carrier in the end, if we conclude a new modem firmware is needed to fix the issue. 

If we conclude new modem firmware is needed, we will develop, test and if needed also certify that with the carriers. Once done the delta image is made available to customers either as a mandatory update or not.

Deployment can happen in different ways:

a) Carriers can push the firmware through their device management system. Verizon has this capability

b) Some carriers demand that Nordic have a way to update devices. We are working to get such a solution in place both for specific carriers and as a generic service as different carriers now are forming their requirements

c) We provide it to customers who have their own update server/device management. This could be in networks where carriers do not have specific requirements or customers who want to use their own device management. We are looking into how to create an automated notification system that can also with directly with other device management system.

Again, this depends on the carrier's requirements and capabilities.