BLE_GATT_STATUS_ATTERR_ATTRIBUTE_NOT_FOUND not found error in nrf52

[sharmelaraju]

Hi,

I am using NRF52840 DK in our project . I  am using 15.3.0 SDK  and soft device s140 in our project .Here the nrf52840 dk board is client and other controller bluetooth is used as slave which as 1 base uuid and 4  128 bit characteristics uuid .I am able to connect to the peripheral by scanning device name.Now  i successfully connected to the peripheral devuce. But while doing service discovery i am getting BLE_GATT_STATUS_ATTERR_ATTRIBUTE_NOT_FOUND  in service discovery. can you tell me  how to resolve this issue. as i know only 128 bit base uuid and i dont know the service uuid . Plz help me to resolve this issue.

[Vidar Berg]

Hi,

The BLE_GATTS_EVT_SYS_ATTR_MISSING (MSC) event must be handled by your application if you don't use the Peer manager module. Try to include the following code in your ble_evt_handler (copied from ble_app_uart example):

/**@brief Function for handling BLE events.
 *
 * @param[in]   p_ble_evt   Bluetooth stack event.
 * @param[in]   p_context   Unused.
 */
static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    uint32_t err_code;

    switch (p_ble_evt->header.evt_id)
    {
    
     ...
    case BLE_GAP_EVT_SEC_PARAMS_REQUEST:
            // Pairing not supported
            err_code = sd_ble_gap_sec_params_reply(m_conn_handle, BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP, NULL, NULL);
            APP_ERROR_CHECK(err_code);
            break;

    case BLE_GATTS_EVT_SYS_ATTR_MISSING:
            // No system attributes have been stored.
            err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
            APP_ERROR_CHECK(err_code);
            break;
     ...

[sharmelaraju]

Thanks for the reply.

I have tried to include the BLE_GATTS_EVT_SYS_ATTR_MISSING event but still it is getting attribute not found and service not found at the peer. Plz  help me.

[Vidar Berg]

The SSP Service base UUID seems to be added with the correct byte order in your code so that is good, but I can't see from your code snippets if you use the 16-bit Service UUID for the Service discovery (0x9AC4). Can you upload your entire project here so I can take a look?

[sharmelaraju]

Thank you very much  for the reply and sorry for the late reply as i was on the holiday.

I  had discovered the services and characteristics now. The problem was on the peripheral side as i had forgot to register the service. Now i can discover the service and characteristics now.

Now the problem is when i pressed the button 1 it is sending the data but at the peripheral side i am not reading the data as it is showing 0 bytes are received.

can you tell me what is the problem. plz  help me to resolve the issue.

[Vidar Berg]

I need more information to understand why it's not working.

E.g.,

 1. Are you using the send function from the LBS example? In that case, have you modified it according to your requirements?

 2. Are you checking the return value for error codes? Does it return NRF_SUCCESS?

 3. Are you using the attribute handle found during service discovery?

[sharmelaraju]

Yes ,I am using send function in the example.

I didn't try the attribute handle and the err code.

I will try .

Thanks

[sharmelaraju]

It is working now. I have changed the attribute handle number  found during service discovery.

Thanks for the help.