There is no bootloader information in Device Manager apps when doing the DFU via BLE

RE: There is no bootloader information in Device Manager apps when doing the DFU via BLE

Elfving — Wed, 19 Nov 2025 08:38:18 GMT

Great! Glad to hear that you got it solved, as well as that you shared the solution with the rest of the community! Let us know if there is anything else!

Regards,

Elfving

RE: There is no bootloader information in Device Manager apps when doing the DFU via BLE

Valeth — Tue, 18 Nov 2025 09:39:00 GMT

Ok, I have found out the root cause. It is because I did not let my application thread to sleep mode to release the resource for the DFU. Once I add the k_sleep after connecting, everything works as expected. Thanks.

RE: There is no bootloader information in Device Manager apps when doing the DFU via BLE

Valeth — Tue, 18 Nov 2025 04:00:53 GMT

Hi,

When I do the custom project, the device manager app can find the advertisement. But when I connect to it, it shows that the device is connect but the bootloader is unknown when click the "Check for updates".

If I use the example firmware, the bootloader name will be "Mcuboot" instead of unknown.

And I have followed the link you have indicated in your post to enable the bootloader in the custom project and it is not working. Please advice if any other setting I should check. Thanks.

RE: There is no bootloader information in Device Manager apps when doing the DFU via BLE

Elfving — Mon, 17 Nov 2025 12:26:14 GMT

Hi,

If I am understanding you correctly, everything works when you try the academy lesson, even the steps with device manager. But when you do the same with a custom project, the device manager app can't find your advertisement? And I am not sure if I understood that last part; your phone can connect to it?

There are some other tips that might be relevant to your issue here.

Regards,

Elfving