https://devzone.nordicsemi.com/f/nordic-q-a/51901/bootloader-dfu-timeout-issueHello, It looks like if there is an issue with bootloader DFU. If no connection timeout is right. But if you starts a DFU late (near the end of the timeout), il will cut during the update. How to fix that please (report timeout when connected to smartphoneen-USTelligent Community 13Wed, 11 Sep 2019 07:31:48 GMThttps://devzone.nordicsemi.com/thread/209078?ContentTypeID=1Wed, 11 Sep 2019 07:31:48 GMT137ad170-7792-4731-bb38-c0d22fbe4515:06f7de37-6df8-4d60-a28d-dc97169b0a8aFabien Comte<p>Ok thank you.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/208662?ContentTypeID=1Mon, 09 Sep 2019 11:57:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6c884c06-d978-4fcf-8ce9-5a0dbddd1c15Einar Thorsrud<p>Hi,</p> <p>Which SDK version are you using? And which timeout is happening, inactivity timeout or watchdog timeout? I will assume SDK 15.3 and inactivity timeout for now.</p> <p>The inactivity timer that is started and reset every time a DFU object is received (see nrf_bootlaoder.c, line 162). You will see &quot;Inactivity timeout.&quot; if there is a timeout and you are testing with the debug bootloader. Since this is based on the reception of a BLE packet, simply connecting is not enough to reset the device. You can, of course, change this if you like, by calling&nbsp;nrf_bootloader_dfu_inactivity_timer_restart() from somewhere else, if desirable. For instance, when handling the BLE_GAP_EVT_CONNECTED event in&nbsp;ble_evt_handler() in nrf_dfu_ble.c.</p><div style="clear:both;"></div>