disable SD

RE: disable SD

michalmmz — Sun, 13 Dec 2015 15:58:09 GMT

it's works! Thank you.

RE: disable SD

Ole Bauck — Wed, 09 Dec 2015 16:28:56 GMT

That should be all yes. Does the device hardfault if you don't step through the code in debug? Debug stepping the SoftDevice functions may lead to a hardfault sometimes.

RE: disable SD

michalmmz — Tue, 08 Dec 2015 21:16:35 GMT

I did like you said, I wait for BLE_GAP_EVT_DISCONNECT, but still after sd_disable next step in debugger is going to hardfault. What i need to do before i use softdevice_handler_sd_disable()?

disconect
wait for BLE_GAP_EVT_DISCONNECT
and not go into advertising. some thing more? I will be grateful for your response. Regards

RE: disable SD

Ole Bauck — Fri, 04 Dec 2015 09:37:10 GMT

You should wait for BLE_GAP_EVT_DISCONNECT after calling disconnect before disabling the SoftDevice, and not go into advertising which is the default behaviour of the SDK examples, see ble_advertising_on_ble_evt(...) in ble_advertising.c.

RE: disable SD

michalmmz — Thu, 03 Dec 2015 22:11:14 GMT

Thank you for answer. But its still not work. After collect my data i use function sd_ble_gap_disconnect and softdevice_handler_sd_disable. When i want to take another step in debug after this function, its going to hardfault. its look like this:

	test=sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION );
	
	test=softdevice_handler_sd_disable();
	
	ppi_init();
	rtc_config();
	timer1_init();

Do i need call other function before sd disable?

Regrads Michal,

RE: disable SD

Ole Bauck — Thu, 03 Dec 2015 11:41:51 GMT

Yes, you can use blocked hardware after disabling the SoftDevice. Using blocked hardware while SoftDevice is enabled will lead to hardfault.

You are sure you are not calling any SoftDevice functions? A common mistake is to call power_manage(), which will call sd_app_evt_wait(). This have to be changed to this if the SoftDevice is disabled:

__SEV();
__WFE();
__WFE();