Enable/Disable BLE Stack and Softdevice -- SDK 15.3 S132

RE: Enable/Disable BLE Stack and Softdevice -- SDK 15.3 S132

Guilherme de Paula — Thu, 18 Jul 2019 17:42:01 GMT

The soft reset will not leave your variables intact. The variables will be reset to their power-up state and the modules will be re-initialized.

As long as your are not connected, not advertising and not scanning, a blocking function (Ints disabled) will not interfere with the stack scheduling of those BLE events (since they are not running).

RE: Enable/Disable BLE Stack and Softdevice -- SDK 15.3 S132

Vidar Berg — Fri, 03 May 2019 14:13:10 GMT

Can you clarify what you mean by blocking? Is the function running in an interrupt context with priority '0' (highest)? The Softdevice should not assert if it's not doing any timing critical (maintaining a BLE connection, advertising, etc). Have you seen any errors from the Softdevice when running this function?

A soft reset (call to nvic_systemreset() from the code) will make the device reboot and everything will be re-initialized.

RE: Enable/Disable BLE Stack and Softdevice -- SDK 15.3 S132

cemerick — Fri, 03 May 2019 13:13:10 GMT

If I just stop the scanning (and stack ?) will that allow blocking functions that take >100ms to run without causing an exception ? I will certainly change the lfclk per your suggestions, thanks. Sorry, I am not following/understanding what you mean by performing a soft reset. Does that take the system back to a state where all the variables are still intact but all the modules need to be re-initialized ? I will research but would appreciate a little more info on what you have in mind in that area.

Thanks so much for the help.

RE: Enable/Disable BLE Stack and Softdevice -- SDK 15.3 S132

Vidar Berg — Fri, 03 May 2019 11:10:14 GMT

Hi,

Are you sure that you need to completely disable the Softdevice? I think it should be sufficient to stop scanning/advertising. That said, if you need to disable the Softdevice you can call nrf_drv_clock_lfclk_request() before ble_stack_init(). This will tell the clock driver that there is another user/module that relies on the LF clock so it won't be released when you disable the Softdevice.

1. I think it should work if you keep the LF clock running. Sounds like the SPIM and RTC may have to be re-initialized otherwise (have not verified it here).

3. Would it be acceptable to perform a soft reset to recover instead of disabling the Softdevice?