DFU Update not working for IOS11

[inghowe83]

Hi,

DFU update with android ver of nRF Connect working but for IOS ver of nRF Connect not working.

HW: Custom nRF52840

SW: nRF5_SDK_15.2.0_9412b96

demo: (ble_app_buttonless_dfu + blinky_rtc_FreeRTOS) , 

dfu\secure_bootloader\pca10056_ble

Step of generating the package:

2. Generate a private key by running this command in cmd in your SDK 15 folder:`
nrfutil keys generate priv.pem

3. Generate a public key file from that private key by running this command in cmd in your SDK 15 folder:
nrfutil keys display --key pk --format code priv.pem --out_file dfu_public_key.c

4. copy dfu_public_key.c into \nRF5_SDK_15.2.0_9412b96\examples\dfu to replace the dummy dfu_public_key.c

5. Compile \dfu\secure_bootloader\pca10056_ble\ses example and copy the output secure_bootloader_ble_s140_pca10056.hex to the nrfutil folder

6. Open the folder \components\softdevice\s140\hex, and copy the .hex file s140_nrf52_6.1.0_softdevice.hex to nrfutil folder

7. Copy \project\peripheral\MWDS\pca10056\s140\ses\Output\Release\Exe, named blinky_rtc_FreeRTOS_pca10056.hex into nrfutil folder

8. Generate a bootloader settings page in nrfutil folder:
nrfutil settings generate --family NRF52840 --application blinky_rtc_FreeRTOS_pca10056.hex --application-version 1 --bootloader-version 1 --bl-settings-version 1 settings.hex

9. Generate merged bootloader hex
mergehex.exe --merge settings.hex secure_bootloader_ble_s140_pca10056.hex --output my_bootloader.hex

10. Generate DFU package
nrfutil pkg generate --hw-version 52 --application-version 1 --application blinky_rtc_FreeRTOS_pca10056.hex --softdevice s140_nrf52_6.1.0_softdevice.hex --bootloader my_bootloader.hex --bootloader-version 1 --sd-req 0xAE --sd-id 0xAE --key-file private.pem mwds_app_dfu_package.zip

11. Setup DFU environment with clean dfu bootloader
nrfjprog.exe -e

nrfjprog.exe --program s140_nrf52_6.1.0_softdevice.hex --verify

nrfjprog.exe --program my_bootloader.hex --verify –r

[Vidar Berg]

Hi,

This is a limitation with the nRF connect app on iOS, it will not continue with the app update if the init packet for sd+bl was rejected (similar question). A workaround is to split the zip into packages, one with sd+bl image, and the other with only the app. 

[inghowe83]

Hi,

When nordic will fix this bug, was this bug limited to nRF connect only? In another post "However, as I understand it, it's not a limitation in the DFU library itself, so you can change this behavior if you plan to integrate the library in a custom app." <- may I know what does it means by "change this behavior" , do we need to customize something on the DFU lib? If yes where can we find the best reference source to "change the behavior", Our release mobile app must able to support IOS full update which include sd+bl+app.

Thanks.

[Vidar Berg]

Hi,

You do not need to customize the DFU lib for this. The solution for your custom app is to just start application update even if the sd+bl update was rejected. 

inghowe83 said:

Our release mobile app must able to support IOS full update which include sd+bl+app.

This is supported. The reason it's not updated in your case is that the bootloader version is the same so there is no upgrade to be done. 

[inghowe83]

Thanks. My team have tested the lib, we encounter some problem. We notice if we combine APP+BL+SD, we will need to manually sent 0x01 into characteristics 8EC90003-F315-4F60-9FB8-838830DAEA50 enable DFUTarg 0xFE59 service. After that we need to connect to 0xFE59 and run the IOS DFU lib. Its very inconvenience, may I know there is any other method to get this works in single step?

[Vidar Berg]

The bootloader should stay in DFU mode even if the prevalidation fails. But wouldn't it be possible to automate this step in the app to make it transparent to the user?