bootloader activate and reset - won't reset

RE: bootloader activate and reset - won't reset

Hung Bui — Mon, 21 Dec 2015 14:21:03 GMT

Hi Bart,

Thanks for pointing that out. I don't think we need to keep that code. You can comment that out (the call for sd_ble_gatts_sys_attr_get) . I have reported this internally.

RE: bootloader activate and reset - won't reset

bart — Mon, 21 Dec 2015 08:12:26 GMT

Ah, sorry, at dfu_transport_ble.c:793. The handling of ble gap disconnect.

RE: bootloader activate and reset - won't reset

Hung Bui — Fri, 18 Dec 2015 17:48:12 GMT

Hi Bart, sd_ble_gatts_sys_attr_get in where ?

RE: bootloader activate and reset - won't reset

bart — Thu, 17 Dec 2015 15:52:19 GMT

Aha, reverting that change did make it work indeed :) So it always just got stuck in that on disconnect event handling. Is there any reason to keep the sd_ble_gatts_sys_attr_get call in there?

RE: bootloader activate and reset - won't reset

Hung Bui — Thu, 17 Dec 2015 12:25:28 GMT

Hi Bart,

You should not edit the dfu_transport_ble.c to trigger system reset when err_code == NRF_SUCCESS. What we do inside dfu_image_activate() is to call m_functions.activate() which is equal to dfu_activate_app(). In this function we will actually do the flash swapping and updating the bootloader information.

What the bootloader does after the dfu_image_activate() call is to wait for the PSTORAGE_STORE_OP_CODE event from the stack in pstorage_callback_handler() in bootloader.c telling the bootloader setting is saved (BOOTLOADER_COMPLETE) and return to main to switch to application (bootloader_app_start() ).

If you test with our DFU example without any modification, would it work ? If not, what was the behaviour ?