Proper setup of m_adv_uuids for custom service

RE: Proper setup of m_adv_uuids for custom service

ejg2putt — Fri, 15 Jul 2016 18:04:43 GMT

Yes, 7 is Invalid Parameter. It was invalid because advertising_init() was being called before service_init() - which we took directly from the hrs app. Swapping the order fixes the problem.

So to summarize to advertise a custom service UUID:

Initialize the 128 bit UUID with sd_ble_uuid_vs_add().
If you're not using scan data for ble_advertising_init(), m_adv_data goes in advdata, but you'll probably need a short name
You can use scan data in ble_advertising_init() for one custom UUID, not room for more.
The UUID you put into m_adv_uuids[] is the 16 bit short version of your long UUID.
Make sure you call service_init() before advertising_init() .

Thanks again Rols, please edit my bullet points if any of them are not correct.

RE: Proper setup of m_adv_uuids for custom service

RK — Fri, 15 Jul 2016 12:51:45 GMT

If you're using a segger you can use RTT for debugging, very easy and requires no setup.

7 is 'Invalid Parameter' I believe, there aren't many thing which will return that from the advertising encoder, but there are a few. if all you put in was the list of ids I don't see why you'd get that error message, have you set some other options too?

The easiest thing to do is single step the advertising data encode function and find out where it's blowing up.

RE: Proper setup of m_adv_uuids for custom service

ejg2putt — Fri, 15 Jul 2016 11:17:52 GMT

Thanks for the quick response Rols. ble_advertisting_init() is returning a "7". I don't have a lot of detail beyond that, as we're using the UART for a different comm channel, and we don't have TWI fully functional yet (i.e. TWI will be our debugging interface).

sd_ble_uuid_vs_add() returns a ble_uuid.type of "2", which is the same as BLE_UUID_TYPE_VENDOR_BEGIN, which of course, produces the same results.

RE: Proper setup of m_adv_uuids for custom service

RK — Fri, 15 Jul 2016 00:41:57 GMT

What errors are you getting? What are the actual error codes, just saying you get errors is too vague to really help.

of course your UUID is the 128 bit version, all custom UUIDs are 128 bits.

Don't use BLE_UUID_TYPE_VENDOR_BEGIN, use the actual value returned from the sd_ble_uuid_vs_add() function.

Apart from that, you have the correct way of adding a list of UUIDs to the scan response data, so you need to tell us which function is producing and error and what the error is.