Two calls to sd_ble_uuid_vs_add with same parameter fails

RE: Two calls to sd_ble_uuid_vs_add with same parameter fails

Ulrich Myhre — Mon, 09 Nov 2015 12:23:35 GMT

I, personally, cannot speak for the nrf51-ble-driver, but the latest SoftDevices already have this change. Once a driver based on these is out, it should be included. For now you should avoid adding things multiple times, or expect NRF_ERROR_FORBIDDEN to occur every now and then.

RE: Two calls to sd_ble_uuid_vs_add with same parameter fails

jpo38 — Mon, 09 Nov 2015 10:48:17 GMT

Thanks, if that's already adressed in next versions, it's great.

RE: Two calls to sd_ble_uuid_vs_add with same parameter fails

Ulrich Myhre — Sat, 07 Nov 2015 15:48:44 GMT

Hi,

This is all according to the documentation. The return values for sd_ble_uuid_vs_add are described like this:

NRF_SUCCESS	Successfully added the Vendor Specific UUID.
NRF_ERROR_INVALID_ADDR	If p_vs_uuid or p_uuid_type is NULL or invalid.
NRF_ERROR_NO_MEM	If there are no more free slots for VS UUIDs.
NRF_ERROR_FORBIDDEN	If p_vs_uuid has already been added to the VS UUID table.

In a later version of the SoftDevices, this has been changed to simply return NRF_SUCCESS and the already-assigned type.

Please also do a search for "sd_ble_uuid_vs_add" here and you will find many similar questions with helpful answers.