No firmware found for file

[icondev]

I am having trouble updating a product with the firmware update file using NRFconnect app for ios version 2.5.3 using iphone se 2020.

We have been running successful updates for 7 years on the nRF51822.

I have used NRF apps in the past to update products. Several days ago our product was failing to update using our custom app. When this happened I decided to try with the NRFconnect app and I got this error (see attached image).

Please let me know what causes the error.

What other information do you need to diagnose this problem?

Thanks

[icondev]

I try to use the nRF Connect for desktop and found this error:

I haven't used the PCA10056 before. I connected the JLink to the debug in port.

Is the idea to use the nRFchip on the dev board as a master device to send a DFU image to the product?

Would I need to flash the device on the dev board with a particular image to do this?

Our particular codebase does not support the NRF52 so I can't create an OTA file for that device.

The image is created using mergehex we first merge the bootloader and softdevice then merge that image with the application in order to create application.hex.

We then use a 14 byte application.bin file as a template and replace the checksum with the current checksum.

I transfer the file to phone by using itunes which is how I have done it in the past. I used to use NRF toolbox but I assume NRF connect can also work for this.

[Edvin]

Hello,

Sorry. I was out of office for the last couple of weeks.

icondev said:

I transfer the file to phone by using itunes which is how I have done it in the past.

How does that work? Is that something that Nordic Semiconductor has implemented? (I assume not). So when it says that the file is not found, are you sure that this is not because itunes has changed the way they upload files? 

Is there some way for me to reproduce what you are seeing? Or is this something that you have implemented yourself? (To transfer files from a computer to your phone application)? I am just trying to figure out whether this is something that Nordic is actually involved in, or if it is a completely custom solution that you have made).

It looks like the question is not really related to the bootloader running on the nRF, since the process never reaches the point where the DFU transfer is actually started.

Best regards,

Edvin

[icondev]

I think the question is on hold for now since the proprietary application still works with the bootloader. The question is whether the NRF app is not backward compatible. Maybe the firmware format has been updated.

I am not using a proprietary app to load the file to the phone. I am just using itunes to make the file available to the Nordic app.

[Edvin]

The nRF Connect for iOS/Android is not backwards compatible to the first versions of the bootloader, but I think the difference is only the UUID of the bootloader's UUID. 

As for transferring images to the phone, the common way today is to send it via email, and then send the file to nRF Connect for iOS/Android from the email attachment.

BR,

Edvin