This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SDK12 DFU service not found

I am developing software for a custom hardware based on NRF52. Previously I was tasked on updating the old NRF51 based software (used on older version of the device) for NRF52 using SDK11. Once that was done my next task was updating the software for SDK12. The software is otherwise working fine but I am having problems with DFU. I tried creating a zip of the application and flashed the combined softdevice/bootloader from SDK12 examples folder (dfu/ble_dfu_send_hex) to the device. The device shows as DfuTest on the mobile DFU app but when I try to upload the zip all I get is "DFU service not found". I also tried compiling the secure DFU bootloader example and using that instead but the result is the same.

Do I need to also have DFU support in the application for that to work ? Currently the application has some kind of DFU functionality from the earlier SDK 11 implementation but I'm guessing that wont work. Any examples to study so that I can implement the functionality ?

Parents
  • No, the device is not shown at all. I tried it with the demo and it worked without problems. It would appear that the problem lies with advertising initialisation method used in the application. It is done in completely nonstandard way that probably has trouble with DFU usage. The advertising initialisation used in the application is pretty much unchanged from the original implementation (originally from SDK 8, AFAIK). Basically the initialisation just sets the advertising data using ble_advdata_set (custom data, the device is a multisensor IoT device). I guess I should try to modify that next.

Reply
  • No, the device is not shown at all. I tried it with the demo and it worked without problems. It would appear that the problem lies with advertising initialisation method used in the application. It is done in completely nonstandard way that probably has trouble with DFU usage. The advertising initialisation used in the application is pretty much unchanged from the original implementation (originally from SDK 8, AFAIK). Basically the initialisation just sets the advertising data using ble_advdata_set (custom data, the device is a multisensor IoT device). I guess I should try to modify that next.

Children
No Data
Related