Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

only1chi — Wed, 08 Jul 2020 11:54:50 GMT

I did finally figure it out looking at other posts. As it turns out, I was not registering my base uuid. I fixed this by calling services_init() function first before calling advertising_init().

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

Kenneth — Wed, 08 Jul 2020 07:54:01 GMT

I recommend to check out some of the threads with similar problems:

https://devzone.nordicsemi.com/f/nordic-q-a/17312/nrf52-returning-error-code-7-when-trying-to-set-proprietary-uuid-in-advertising-data

The description from the error code is:
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.api.v7.0.1/group___b_l_e___c_o_m_m_o_n___f_u_n_c_t_i_o_n_s.html#ga2e55f7d7e631d072c24f2d6bc0860cc8

NRF_ERROR_INVALID_PARAM

Invalid UUID type.

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

only1chi — Wed, 08 Jul 2020 02:00:06 GMT

Hi Kenneth,

I don't think that too much data is the problem.

The error code is

NRF_ERROR_INVALID_PARAM

This is from the function

sd_ble_uuid_encode(&uuid, &encoded_size, NULL)

I don't quite understand why this function is returning an error_code = 7;

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

Kenneth — Thu, 02 Jul 2020 09:38:29 GMT

I think you are trying to put to much data into the advertising packet, and you get an error due to size.

Have you tried to debug to find where the error code that is causing the crash is coming from? Typically by checking app_error_fault_handler().

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

only1chi — Wed, 01 Jul 2020 14:00:57 GMT

I configured NRF_SDH_BLE_VS_UUID_COUNT count to 7.
The failure happens in during advertising initialization, in function ble_advdadta_encode.
The failure goes away if I don't include my custom service in the m_adv_uuids[] array.

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

Kenneth — Wed, 01 Jul 2020 13:57:19 GMT

What have you configured to NRF_SDH_BLE_VS_UUID_COUNT to?

Have you tried to debug to find where the error code that is causing the crash is coming from? Typically by checking app_error_fault_handler().

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

only1chi — Wed, 01 Jul 2020 13:49:58 GMT

I do have one more question:

My application has three services, including battery service and device information service.
In my main.c file, I try to add the services, along with my custom service for advertising. However, this causes a crash.
This is the piece of code that adds my service uuid. How do I make my custom service advertise its UUID?

// YOUR_JOB: Use UUIDs for service(s) used in your application.
static ble_uuid_t m_adv_uuids[] =                                               /**< Universally unique service identifiers. */
{
    {BLE_UUID_DEVICE_INFORMATION_SERVICE, BLE_UUID_TYPE_BLE},
    {BLE_UUID_BATTERY_SERVICE, BLE_UUID_TYPE_BLE},
    {BLE_UUID_VECTOR_PUMP, BLE_UUID_TYPE_VENDOR_BEGIN}
};

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

only1chi — Wed, 01 Jul 2020 13:38:46 GMT

Hi,

Thank you. Your suggestion worked. I can now see all my 6 characteristics attached to the same service.

Chiz

RE: Attaching Custom 128 bit Characteristic UUIDS to Custom 128 bit Service UUID where the base does not match

Kenneth — Wed, 01 Jul 2020 11:20:01 GMT

I believe this should work.

You need to call sd_ble_uuid_vs_add for all 6 UUIDs, make sure that you buffer away the uuid_type for each of the calls, since the uuid_type is the handle that you need to reference later when adding the characteristics (or services).

When you later want to add the charactertistics you use sd_ble_gatts_characteristic_add() as normal, however make sure that the p_attr_char_value now reference the uuid_type (e.g. UUID) that you want to use in p_attr_char_value:

infocenter.nordicsemi.com/.../structble__uuid__t.html