nrf52 does not reset after DFU

[chaitz]

Hi,

From this link https://devzone.nordicsemi.com/f/nordic-q-a/34224/device-does-not-reset-after-dfu I understand that the compiler option flto caused reset issues. Is this still an issue and is this a problem with nRF52832 too?

Apologies for starting a similar thread. But the above is over a year old and on a different processor.

[bjorn-spockeli]

Which SDK version are you using?

The Link Time Optimization(LTO) issue occured when using a GCC version that was not production tested with the nRF5 SDK, e.g. using GCC ARM Embedded 7 instead of GCC ARM Embedded 6.3. We also do not see any issues with LTO when using the correct GCC version. 

The latest SDK(v15.3.0) has been production tested with GCC ARM Embedded 7.2018q2.update and as far as I know we have not seen any issues with enabling LTO when compiling the SDK examples. 

Best regards

Bjørn

[chaitz]

The SDK version is v15.2 and the issue seems to be related to connection params. The connection interval counts were modified from the default 12 to 10 (min) and 30 (max) and the script we used for DFU started behaving inconsistently when compared to earlier settings of 12. We have a requirement to get DFU working on 4 different platforms (windows, macOS, iOS, Android). Keeping it at 12 causes issues with windows and sometimes with Android too. Do you have any recommended connection param settings which work for all the platforms? 

[bjorn-spockeli]

I would recommend not setting a too narrow window, I would suggest using the default values in the bootloader example.