start/stop dfu buttonless service

RE: start/stop dfu buttonless service

Einar Thorsrud — Mon, 19 Sep 2022 06:46:32 GMT

I see. But may I ask why you want that? From a high-level perspective, what is the reasoning for it? The reason I ask is that this is not a common thing to do, and perhaps there would be another way to achieve your main goal (whatever the reason for wanting this feature is).

RE: start/stop dfu buttonless service

xtian — Mon, 19 Sep 2022 02:14:14 GMT

we wanted the buttonless dfu service to be initially disabled/hidden and will only show up after receiving a command and will be hidden/disbled again after a certain time if the user did not update

RE: start/stop dfu buttonless service

Einar Thorsrud — Fri, 16 Sep 2022 11:47:12 GMT

Hi,

[quote user=""]it can only be done if we unintialize and initialize the BLE stack.[/quote]

That is correct.

[quote user=""]is there an example on how to uninitialize/initialize the BLE stack?[/quote]

No, there are no examples of it, but the SoftDevice is disabled using sd_softdevice_disable(). Note that most SDK libraries (like the SoftDevice handler library - SDH) assumes that the SoftDevice is only enabled, so you will need to do a bit of changes to support this.

There is a reason removing services is not supported though. It is not a common thing to do, and it does not fit well with typical Bluetooth LE use cases (for instance, the GATT client will need to do a service discovery to know what has changed). May I ask why you want to do it? What is the end goal? Could it be that there are other and perhaps even better ways to achieve your end goal?