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

Dave — Thu, 21 Nov 2019 21:08:28 GMT

Thank you Kenneth.
This worked.

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

Kenneth — Wed, 20 Nov 2019 13:26:12 GMT

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}};