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

[Valeth]

Hi,

I am following the below link to enable the FOTA over BLE in our custom project. I have tried the "Peripheral lbs" example and it is working.

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-9-bootloaders-and-dfu-fota/topic/exercise-5-fota-over-bluetooth-low-energy/

And I have add the 2 line into the sysbuild and proj.conf and build to the custom project.

# STEP 2.1 Enable MCUboot
SB_CONFIG_BOOTLOADER_MCUBOOT=y

# STEP 2.2 - Enable FOTA over Bluetooth LE
CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

The "Device Manager" apps can find my custom device's advertisement. But when I click the "check for updates" in the Device Manager apps, it only shows the mobile phone can connect to the device but the bootloader name and bootloader mode is still unknown. And if I click the "start" to trigger the DFU, there is nothing happened. Is there anything I have configured wrongly?

Thanks.

[Valeth]

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.

[Valeth]

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.

[Elfving]

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