DFU BLE Service B

RE: DFU BLE Service B

Hung Bui — Thu, 22 Apr 2021 14:05:11 GMT

Ok, so it's the configuration of Web Bluetooth to block the Legacy DFU UUID to avoid the device being updated with malicious web page. This is because the Legacy DFU protocol doesn't have data signing protection to verify that the image is from a trusted source.

I assume you are using the bootloader from SDK v11 and above ?

If you can update the bootloader (and the application ) to SDK v17 I would suggest to do so. If it's not possible to update the application and bootloader to SDK v17, you can think of modifying the Legacy DFU UUID to something else. You can generate a random 128 bit UUID for this purpose. But note that as mentioned in the documentation you would risk the device being updated by attacker without any verification of the image.

RE: DFU BLE Service B

oaketi — Thu, 22 Apr 2021 13:13:55 GMT

This is when i use the UUID "00001534-1212-efde-1523-785feabcd123"

RE: DFU BLE Service B

Hung Bui — Thu, 22 Apr 2021 12:05:03 GMT

Hi Oaketi,

Could you please show a log/screenshot where you see the DFU BLE service UUID being blacklisted ?
Please be aware that to be able to support DFU update you would need to implement a bootloader in the NRF52. In addition, you need to put the device into DFU mode, if you want to do that automatically you would need to implement DFU buttonless service in your application.