[S132 v2] Potential bug on sd_ble_uuid_vs_add()

[planas]

Hi, we are updating our current application to the new nRF5 SDK and S132 v2 softdevice but we got stuck with a issue on the initialization of a custom service.

We narrowed down the problem to the sd_ble_uuid_vs_add() function call which ends resetting the device. Something interesting is that initializing the BAS service (which uses a SIG UUID) before the custom service solves the problem, but still, trying to initialize the DFU service after our custom service, returns a NRF_ERROR_NO_MEM error as a result to sd_ble_uuid_vs_add().

So, to sum up:

• Calling sd_ble_uuid_vs_add() before initializing another SIG service resets the device.
• Looks like it's not possible to add two custom UUIDs. When calling sd_ble_uuid_vs_add() for the second time it returns NRF_ERROR_NO_MEM.

Note that the same code is working just fine on the NRF52 9.0.2 SDK and S132 v1 softdevice.

Thanks

[Petter Myhre]

@sarah_sdw Could you please create a new question and explain more?

[sarah_sdw]

@Petter Myhre devzone.nordicsemi.com/.../