RE: ble_gatts_service_add error code 0x0000000c

Sigurd — Fri, 17 Nov 2017 14:58:44 GMT

Add the vendor specific UUID in the scan response packet instead. See the ble_app_uart example on how this is done there.

RE: ble_gatts_service_add error code 0x0000000c

RK — Thu, 16 Nov 2017 20:54:14 GMT

If you just single-stepped into the function you'd find very quickly where the error is coming from. My guess would be

#define NRF_ERROR_DATA_SIZE     (NRF_ERROR_BASE_NUM + 12) ///< Invalid Data size

ie you're trying to encode more data than fits in the packet probably because you have added long UUIDS to short UUIDS and there's never enough space for that.

And i just noticed .. BLE_UUID_TYPE_VENDOR_BEGIN. Do not use this. I really don't know where this incorrect practice came from. You register the UUID base you want, but then you need to use the identifier returned (which may well be equal to BLE_UUID_TYPE_VENDOR_BEGIN and may not). You can't assume equal too the vendor start.

ps your title is rather misleading as you say the error comes from the advertising init function and not the service add one.

pps if you'd typed 'ble_advertising_init 12' into the search box at the top you'd have found 20 answers to this.