with custom 128bit uuid custom uuid shows in advertising packet, but dfu service always shows base uuid

[Dave]

we use custom 128bit uuid service and dfu,bas services

when setting uuid as custom 128 bit uuid in advertising_init function, it's base uuid is always based on dfu.

what is the proper way to set advertising packet's base uuid?

here are some our code pieces.in main.c
static ble_uuid_t m_adv_uuids[] = {{BLE_CUSTOM_UUID,BLE_UUID_TYPE_VENDOR_BEGIN}};

in services_init() function
// add bas service
// add hid service
// add dfu service
// add custom 128 bit uuid's service

in advertising_init() function

init.srdata,uuids_complete.uuid_cnt = sizeof(m_adv_uuids) / sizeof(m_adv_uuids[0])

init,srdata.uuids_complete.p_uuids = m_adv_uuids

in custom.h
#define BLE_CUSTOM_UUID 0x8F23
the custom_uuid's base uuid is 175f8f23-a570-49bd-9627-815a6a27de2a
when the adding dfu service in services_init function is removed, then we can get the custom uuid in advertising packet,
but with dfu service we get wrong uuid which is based on dfu services' base uuid

[Kenneth]

I believe that the \SDKversion\examples\ble_peripheral\ble_app_blinky show this?

I think the real problem here is that you are not using the correct uuid_type, because when you add vendor specific 128-bit base UUID's you need to be calling e.g. something like:

err_code = sd_ble_uuid_vs_add(&base_uuid, &p_lbs->uuid_type);

The uuid_type value will increment +1 for each call, and it will start at BLE_UUID_TYPE_VENDOR_BEGIN. However in your case the first is already used by DFU, so I expect in your case you must use:

static ble_uuid_t m_adv_uuids[] = {{BLE_CUSTOM_UUID,BLE_UUID_TYPE_VENDOR_BEGIN+1}};

and/or better something like

err_code = sd_ble_uuid_vs_add(&base_uuid, &p_lbs->uuid_type);
static ble_uuid_t m_adv_uuids[] = {{BLE_CUSTOM_UUID,p_lbs->uuid_type}};