Error 0x00003002 while sending a notification

RE: Error 0x00003002 while sending a notification

Geoffroy — Thu, 23 May 2019 15:50:16 GMT

i add this :

sd_ble_gatts_sys_attr_set(p_our_service->conn_handle, NULL, 0, 0)

at beginning of my notification function to correct "system attribute missing",

right now i have err : 0x00000008 for NRF_ERROR_INVALID_STATE.

EDIT I changed emplacement where i call notification

NOTIFICATIONS are now working

RE: Error 0x00003002 while sending a notification

Geoffroy — Thu, 23 May 2019 12:02:31 GMT

Hi,

I juste used and compile ble_app_blinky (exemple code nothing from me except traces).

This code is compiling and advertising, i can see characteristics with nRFconnect app.

but notification don't work, and i get err_code 0x00003401 ...

maybe is there a problem in my definitions ?

EDIT in error, 01 stands for system attribute missing

RE: Error 0x00003002 while sending a notification

Kenneth — Wed, 22 May 2019 11:57:06 GMT

ble_app_blinky support notifications, check out ble_lbs.c

Your error code is:

* @retval ::NRF_ERROR_DATA_SIZE Invalid data size(s) supplied.

Best regards,
Kenneth

RE: Error 0x00003002 while sending a notification

Geoffroy — Wed, 22 May 2019 11:49:35 GMT

i increased len : len = 15; (instead of len = 10).

right now err_code (from sd_ble_gatts_hvx) is 0x0000000C do you know what does it stand for ?

RE: Error 0x00003002 while sending a notification

Geoffroy — Wed, 22 May 2019 09:33:25 GMT

Hum ble_app_blinky seems to don't use notifications...

I started from tuto_charac.

Because i have 2 characteristics, i changed the way i handle char_handles :

typedef struct
{
    uint16_t                    conn_handle;    /**< Handle of the current connection (as provided by the BLE stack, is BLE_CONN_HANDLE_INVALID if not in a connection).*/
    uint16_t                    service_handle; /**< Handle of Our Service (as provided by the BLE stack). */
    // OUR_JOB: Step 2.D, Add handles for the characteristic attributes to our struct
    //ble_gatts_char_handles_t char_handles;
    ble_gatts_char_handles_t first_char_handles;
    ble_gatts_char_handles_t second_char_handles;
}ble_os_t;

Then i checked, right now hvx_params.handle that value_handle after sd_ble_gatts_characteristic_add.

now err_code is 0x00003401.

here is how i create my charac :

ble_uuid_t          char_uuid_2;
	char_uuid_2.uuid      = BLE_UUID_CHARACTERISTIC_READER_RESULT;
	err_code = sd_ble_uuid_vs_add(&base_uuid, &char_uuid_2.type);
	APP_ERROR_CHECK(err_code);
    
    // OUR_JOB: Step 2.F Add read/write properties to our characteristic
    ble_gatts_char_md_t char_md_2;
    memset(&char_md_2, 0, sizeof(char_md_2));
    char_md_2.char_props.read = 1;
    char_md_2.char_props.write = 1;

    
    // OUR_JOB: Step 3.A, Configuring Client Characteristic Configuration Descriptor metadata and add to char_md structure
    ble_gatts_attr_md_t cccd_md_2;
    memset(&cccd_md_2, 0, sizeof(cccd_md_2));
	BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md_2.read_perm);
	BLE_GAP_CONN_SEC_MODE_SET_OPEN(&cccd_md_2.write_perm);
	cccd_md_2.vloc                = BLE_GATTS_VLOC_STACK;
	char_md_2.p_cccd_md           = &cccd_md_2;
	char_md_2.char_props.notify   = 1;


    
    // OUR_JOB: Step 2.B, Configure the attribute metadata
    ble_gatts_attr_md_t attr_md_2;
    memset(&attr_md_2, 0, sizeof(attr_md_2));  
	attr_md_2.vloc        = BLE_GATTS_VLOC_STACK;
    
    
    // OUR_JOB: Step 2.G, Set read/write security levels to our characteristic
	BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md_2.read_perm);
	BLE_GAP_CONN_SEC_MODE_SET_OPEN(&attr_md_2.write_perm);

    // OUR_JOB: Step 2.C, Configure the characteristic value attribute
    ble_gatts_attr_t    attr_char_value_2;
    memset(&attr_char_value_2, 0, sizeof(attr_char_value_2));
	attr_char_value_2.p_uuid      = &char_uuid_2;
	attr_char_value_2.p_attr_md   = &attr_md_2;


	SEGGER_RTT_printf(0, "value handle dans char_add 1A : 0x%#08x\n", p_our_service->second_char_handles.value_handle);
    // OUR_JOB: Step 2.H, Set characteristic length in number of bytes
	attr_char_value_2.max_len     = 10;
	attr_char_value_2.init_len    = 10;
	uint8_t value_2[10]            = {0x44,0x6f,0x6e,0x65,0x44,0x6f,0x6e,0x65,0x44,0x6f};
	//uint8_t value_2[10];
	attr_char_value_2.p_value     = value_2;
    // OUR_JOB: Step 2.E, Add our new characteristic to the service
	err_code = sd_ble_gatts_characteristic_add(p_our_service->service_handle,
                               &char_md_2,
                               &attr_char_value_2,
                               &p_our_service->second_char_handles);
	APP_ERROR_CHECK(err_code);

so it looks like hvx_params.handle is right and i support notification ...

RE: Error 0x00003002 while sending a notification

Kenneth — Wed, 22 May 2019 07:50:30 GMT

You may also find \examples\ble_peripheral\ble_app_blinky useful as reference.

If you call sd_ble_gatts_hvx() and the return error code is:

* @retval ::BLE_ERROR_GATTS_INVALID_ATTR_TYPE Invalid attribute type(s) supplied, only characteristic values may be notified and indicated.

Then I think either hvx_params.handle is wrong (maybe it's not the correct handle to the characteristic that can notify values), or the handle you are using is pointing to a characteristic that don't support notifications (char_props.notify).

RE: Error 0x00003002 while sending a notification

Geoffroy — Tue, 21 May 2019 13:01:38 GMT

Thank you Kenneth,

I tryed to notify before my gatt is connected.

so right now i call this notification function after connection.

now i get err_code 0x00003400 which stand for BLE_ERROR_GATTS_INVALID_ATTR_TYPE (with NRF_GATTS_ERR_BASE).

i don't know where is the problem, here i have :

// Use UUIDs for service(s) used in your application.
static ble_uuid_t m_adv_uuids[] =                                               /**< Universally unique service identifiers. */
{
	{BLE_UUID_OUR_SERVICE_UUID, BLE_UUID_TYPE_BLE}
	{BLE_UUID_OUR_SERVICE_UUID, BLE_UUID_TYPE_VENDOR_BEGIN}//originaly but don't advertise
};

here if i declare BLE_UUID_TYPE_VENDOR_BEGIN for ble_uuid_t type, my module doesn't advertise

RE: Error 0x00003002 while sending a notification

Kenneth — Tue, 21 May 2019 09:11:38 GMT

I assume you have updated the connection handle, e.g. somewhere along the lines of:

static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)
{
    ret_code_t err_code;

    switch (p_ble_evt->header.evt_id)
    {
        case BLE_GAP_EVT_CONNECTED:
            p_our_service->conn_handle = p_ble_evt->evt.gap_evt.conn_handle;

Typically the value is 0 on first connection.

You may also find \examples\ble_peripheral\ble_app_blinky useful as reference.