Having problems after initiate disconnect from slave side

RE: Having problems after initiate disconnect from slave side

Susheel Nuguru — Mon, 18 May 2015 15:14:25 GMT

When you initiated your disconnect right after CONNECTED event, did you check for error returns? Seems to me that disconnect event did not go through successfully

RE: Having problems after initiate disconnect from slave side

Kramer — Mon, 18 May 2015 14:46:33 GMT

Hey shibshab

The problem is that I initiate disconnect right after CONNECTED event, and I don't get BLE_GAP_EVT_DISCONNECTED event after that.

RE: Having problems after initiate disconnect from slave side

shibshab — Mon, 18 May 2015 05:22:21 GMT

You are correct, you should be able to disconnect from the slave.

You need to handle the BLE_GAP_EVT_DISCONNECTED event in order for the slave to be able to function after performing the disconnect procedure. The reason is that the softdevice needs to know that it is in a valid state before advertising.

Try adding this to your BLE event handler:

static void on_ble_evt(ble_evt_t * p_ble_evt)
{
    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_DISCONNECTED:
        {
            m_conn_handle = BLE_CONN_HANDLE_INVALID;
        }
    }
}