dfu of nrf connect IOS doesn t work

[sarah_sdw]

Hello,

we are developing a machine that is in pre-production. We need to be able to update the firmware and until now all works well on android. but on IOS the dfu does not work.

I use the same device with the same firmware to update. it's ok on android nRF Connect for Mobile version 4.22.3

but does not work on IOS nRF Connect Version 2.0.2

it seems to me that it worked on IOS with version 1.8.8

I use:

nrf52832, SDK version: 15.3.0, Soft Device version: S132 V6.1.1

the device does not start in dfu target mode.. 

is there a problem with the IOS application? do I have to change something in my firmware to be compatible with the new version? 

thanks for the quick help ... we must soon produce our device.

[sarah_sdw]

Hi, 

I try with the new IOS application (V2.0.3). I use ble_dfu_unbonded.c, and exactly the same firmware that runs on android.

But it does not work on IOS v2.0.3. in the set_adv_name function, the nrf_dfu_set_adv_name function generates a hard fault.

i have p_adv_name with the following parameters:
CRC: 0x00
len: 0x08
name "D,f,u,3,1,0,0,9"

[Hung Bui]

Hi Sarah, 

Could you try disable "Enable Alternative Advertising Mode" inside Settings-> DFU in the app ? This should disable the name change request. 

Note that, if you wan to do name change, you have to make sure in the bootloader you don't enable NRF_DFU_BLE_REQUIRES_BONDS in the configuration of the bootloader. 

You only enable it if you want to use bond both in the app and in the bootloader, and when doing that you need to turn off the Alternative Advertising Mode. 

[sarah_sdw]

Hi 

thank you!  it works now ;) 

however i have had to remove my watchdog for it to work. I did not find a way to disable the watchdog before doing a firmware update. how to have a watchdog without this annoys the dfu?

[Hung Bui]

Hei Sarah, 

Great that it working for you now. WDT should be handled by the bootloader automatically unless you have made a modification in the bootloader. 

You can find nrf_bootloader_wdt_feed() is called inside loop_forever() and wdt_feed_timer_handler()

How do you configure the WDT ? Have you configured to run when the CPU is sleeping ? What is the WDT timeout ? 

[sarah_sdw]

I have the function nrf_bootloader_wdt_feed() inside loop_forever. this function feeds all channels ?

I have configured with .behavior = 1, and .reload_value = 1000.

is it possible that 1 second is too small to pass between the bootloader and the application?I think the problem occurs at the end of the download of the new firmware. just before going back into the app.

can I reconfigure it when I start the dfu, to put a bigger reload value?