Feature request: new DFU bootloader callback to dfu_observer after transports are initialized, but before loop_forever() is called

[eric-appion]

In the secure DFU bootloader, I have some custom initialization that I need to happen after the BLE transport is initialized in nrf_dfu_init(), but before loop_forever() in nrf_bootloader.c is called. I'd prefer to do that initialization in main.c rather than having to modify your nrf_dfu_init(). Currently nrf_dfu_init() calls the dfu_observer function with an event NRF_DFU_EVT_DFU_INITIALIZED right before it initializes the transports. Could you please add a new event such as NRF_DFU_EVT_DFU_TRANSPORTS_INITIALIZED, and call the dfu observer with that event right after the transports are initialized?

[Einar Thorsrud]

Hi,

I have not seen any similar request earlier, but I will make an internal feature request describing your reasoning for wanting this event. You should not expect this to be included in an updated SDK anytime soon though, so if you need it you should implement it yourself (even if that means that you have to modify the SDK code).

[Andy]

Hi, I had a situation where I needed exactly this feature and I had to modify the SDK code.

See this:

devzone.nordicsemi.com/.../timer-v2-in-bootloader-sdk15

[eric-appion]

I had similar problems with using timers. Sigh.