Disconnecting on Generic Attribute PrimaryService(0x1801) discovery

RE: Disconnecting on Generic Attribute PrimaryService(0x1801) discovery

Yaroslav — Mon, 22 Dec 2014 16:10:19 GMT

Thank you for answer! It works for me.

RE: Disconnecting on Generic Attribute PrimaryService(0x1801) discovery

Jerod — Fri, 14 Nov 2014 20:44:24 GMT

Not sure this is the only reason, as I have exactly the code as you've recommended, and still get disconnect.

I am using S110.

Specifically, I have a "write-only" characteristic defined (handle 10), and Service Discovery using will generate: [15:38:01.7] No response received for ReadRequest on handle 0x0010. Disconnecting.. [15:38:01.7] Lost connection to device. Reason: BTLE_LOCAL_HOST_TERMINATED_CONNECTION

and the debug output shows that the call to sd_ble_gatts_sys_attr_set returned without error:

DEBUG:BLE_GAP_EVT_SYS_ATTR_MISSING(0x52)[on_ble_evt()] DEBUG:am: error_code (0)[on_ble_evt()] DEBUG:BLE_GAP_EVT_DISCONNECTED(0x11)[on_ble_evt()]

I can't find any documentation on what BLE_GATTS_EVT_SYS_ATTR_MISSING actually means. Why am I getting it?

RE: Disconnecting on Generic Attribute PrimaryService(0x1801) discovery

FormerMember — Wed, 12 Nov 2014 09:37:55 GMT

If service discover fails in your application in Master Control Panel, the problem is most likely that the event BLE_GATTS_EVT_SYS_ATTR_MISSING is not being handled. If the application doesn't support boding, it can for example be handled the following way in on_ble_evt(..) in main.c:

case BLE_GATTS_EVT_SYS_ATTR_MISSING:
        err_code = sd_ble_gatts_sys_attr_set(m_peripheral_conn_handle, NULL, 0);
        APP_ERROR_CHECK(err_code);
        break;