sd_ble_gap_disconnect error

RE: sd_ble_gap_disconnect error

Chocol8 — Tue, 24 Oct 2017 10:29:18 GMT

Thank you. This helps a lot!

RE: sd_ble_gap_disconnect error

Jørgen Holmefjord — Tue, 24 Oct 2017 10:26:17 GMT

Yes, you can set m_conn_handle = BLE_CONN_HANDLE_INVALID after calling sd_ble_gap_disconnect(). By default this is set in on_ble_evt() handler, when a BLE_GAP_EVT_DISCONNECTED event is received, but this event might come after your code has had time to call sd_ble_gap_disconnect() multiple times. By setting it right after starting diconnect procedure, you make sure disconnect function is not called again.

RE: sd_ble_gap_disconnect error

Chocol8 — Tue, 24 Oct 2017 09:49:39 GMT

Hello, Jorgen. Thank you for coming in help. Before I have read your comment I have tried various things to solve it and came across this question once again: devzone.nordicsemi.com/.../ Joris Roussel proposed solution by inserting m_conn_handle = BLE_CONN_HANDLE_INVALID; after sd_ble_gap_disconnect(). While debugging it like this I have not received error.

Now I understand why placing a break point makes no sense. Break point at statement if (err_code != NRF_SUCCESS)shows that m_conn_handle is 0x0000 which is not equal to BLE_CONN_HANDLE_INVALID (0xFFFF).

It's my unskillfulnes fault by saying that NRF_UART application does not show. It is unnecessery information.

I would like to hear from you if setting m_conn_handle = BLE_CONN_HANDLE_INVALID after sd_ble_gap_disconnect() is correct solution.

RE: sd_ble_gap_disconnect error

Jørgen Holmefjord — Tue, 24 Oct 2017 08:42:44 GMT

Most likely, your application tries to call sd_ble_gap_disconnect() multiple times before m_conn_handle = BLE_CONN_HANDLE_INVALID is set, after ble_tx_complete = 1 is set. You should set the breakpoint on the if (err_code != NRF_SUCCESS) check. When you set the breakpoint on return err_code;, you will only break when a non-success error code is received. Can you try to set a flag after calling disconnect, to avoid calling this multiple times? What do you mean by "Application does not show it was disconnected to board"? Only that it does not print disconnect to UART? If you get a hardfault from calling disconnect function multiple times, the application will not continue.

RE: sd_ble_gap_disconnect error

Chocol8 — Tue, 24 Oct 2017 06:59:01 GMT

I have tried this approach:

{
          if (ble_tx_complete == 1)						
 {
	err_code = sd_ble_gap_disconnect(m_conn_handle, 
         BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
		 if (err_code != NRF_SUCCESS)
			 {
			  return err_code;
			 }
	 }
}

Application does not show it was disconnected to board. Debugging still get err_code =0x00000008 which led to hard fault handler.