Jump to bootloader buttonless

[Benjamin Schlegel]

Hi,

I use the SDK12.3 and SD130 with secure_bootloader and my own application. I can flash SD and Bootloader and update my app over OTA with DFU from NRF Toolbox. My app works fine after updating. I implemented the buttonless service to do the buttonless jump back to bootloader if needed (I also have another custom service which works fine). If I use the characteristic from buttonless dfu service to switch to bootloader I get the notification "Response for: Enter Bootloader Status: Success". But I never jump to the bootloader. If I set a breakpoint in my bootloader I never reach it. So I dont know where to search because it seems everything is fine. Couldnt find a similiar case in the dev zone. Any help appreciated, thanks

[Hung Bui]

Hi Benjamin,

If you test with the experimental_ble_app_buttonless_dfu , can you switch to the bootloader ?

What exactly happened when you "never jump to the bootloader" ? The device continue to operate in application as normal ?

Have you check if enter_bootloader() inside ble_dfu.c is called ? What the buttonless dfu example does is to write to bootloader setting , wait for the flash update is complete, then disconnect and on_disconnect() it will trigger a softreset to jump to bootloader.

[Benjamin Schlegel]

with the experimental ble_app_buttonless_dfu example + bootloader it works. After jump to bootloader the device is still in application even the notification states Response for: Enter Bootloader Status: Success"

With the use of breakpoints I can see that the enter_bootloader() is called. The notification is triggered. The s_dfu_settings.enter_buttonless_dfu is set to true and nrf_dfu_settings_write gets called and runs completly. I cant see code where on_disconnect() is used after all of that. Where should on_disconenct() be called?

[Hung Bui]

on_disconnect() is called when BLE_GAP_EVT_DISCONNECTED occurs, this is handled inside ble_dfu_on_ble_evt(). Make sure you put that inside ble_evt_dispatch() in main.c .

[Benjamin Schlegel]

ble_dfu_on_ble_evt() is called in ble_evt_dispatch(). If I set a breakpoint in on_disconnect() it never stops there. Who triggers BLE_GAP_EVT_DISCONNECTED event? It seems that this event never happens. In buttonless example on_disconenct() is called. But I cant see the difference to my app.

[Hung Bui]

It's triggered when the flash updating is finish (writing to bootloader setting), inside flash_callback() , you can find sd_ble_gap_disconnect() called there.

I suspect that flash operation has never been finished.