Device bricks after OTA firmware upgrade

[NG]

Hi, At the moment I am using nRF Toolbox to upload DFU *.zip files to our devices. We have been finding that the devices will become unresponsive after a firmware upload, and need a power cycle to come back to life. This is a problem for us, because our device is designed not to have access to the battery. The biggest problem is that the bricking is intermittent. Sometimes an upgrade works without problems, sometimes it bricks the device, and we cannot detect the pattern. We are using dual-bank BLE with S110, SDK8.1.

Is there a minimum battery voltage required for successful OTA upgrade? How to make sure that BLE advertising always starts after an OTA upgrade?

[NG]

Hi Stian, I've recently migrated to SDK10, and I am now again having a problem with DFU. The DFU completes successfully, however, when main() is re-entered, the device pauses and never returns from: nrf_drv_timer_extended_compare (in app_pwm_init).

nrf_drv_timer_extended_compare(p_instance->p_timer, (nrf_timer_cc_channel_t) PWM_MAIN_CC_CHANNEL,
                                ticks, NRF_TIMER_SHORT_COMPARE2_CLEAR_MASK, true);

[NG]

Hi All, Possibly found the reason for the bricking during OTA DFU - it is related to having an unstopped timer prior to jumping to bootloader, seethis. This is SUPER annoying! Why Nordic did you not document this properly? How is it that you have a function not return in the library code?

[Stian Røed Hafskjold]

Hi, yes you're right that unstopped timers may cause problems. The documentations on older SDK versions are not updated very often unfortunately. I agree that we need a better system for reporting bugs. This is fixed in SDK 12 though.