multiple services error code 0xf

RE: multiple services error code 0xf

RK — Wed, 08 Jul 2015 11:50:30 GMT

Great - thanks for that - I'll go take the global out of my code and just call the registration function as-needed, much better.

RE: multiple services error code 0xf

Ulrich Myhre — Wed, 08 Jul 2015 11:47:10 GMT

Yeah, some information got lost there I think. I will raise this internally so the documentation is fixed. Someone reported this annoyance late 2013, and we agreed and fixed it back then. Looking at the source now, it should populate the handle and return success now.

RE: multiple services error code 0xf

RK — Wed, 08 Jul 2015 11:21:59 GMT

Oh - that's not what the documentation says either, it still says it will return NRF_ERROR_FORBIDDEN if the UUID has already been added to the table. (That's the sdk 8 docs I just checked)

RE: multiple services error code 0xf

Ulrich Myhre — Wed, 08 Jul 2015 10:42:45 GMT

The uuid_vs_add() call will return success and populate the type from s110 7.0 and beyond (and already be in s120 2.x.x and s130 1.x.x). Seems this was not put in the release notes.

RE: multiple services error code 0xf

RK — Wed, 08 Jul 2015 09:59:25 GMT

If you're using the same 'base' UUID for all your services (which is what I do because it makes life a whole lot easier) than you have a couple of options. I keep a global handle to the registered UUID which starts at zero at runtime, and have a function to return the registered handle. When I call the function, if the handle is still zero, I do the registration cache and return it, else I just return the one I cached.

That means you can do your service instantiation in any order, instead of each one doing the uuid_vs_add(), you just call your one-true function and get the handle, whichever is the first will do the registration, the rest will just get the cached value.

That API call is slightly annoying, since it knows the custom UUID was already registered, it must know which handle it was registered under and it could just return it thus meaning you don't really have to care if you register the same one multiple times, you get the same handle. I could live with it returning the 'already registered' return code, but it would be nice if it also put the handle into the variable anyway so I could check for that condition and keep going instead of having to write that one global function.

RE: multiple services error code 0xf

Ulrich Myhre — Wed, 08 Jul 2015 09:05:43 GMT

Hi,

When you switch between major versions of the SoftDevice, you must at the very least recompile against the new headers in the new release. The migration document included in the release should outline the necessary changes needed for the upgrade.

Without doing this, your SVC number mappings might be wrong, and you end up calling different APIs than you think you are (with very wrong variables).