NRF_ERROR_NO_MEM during call to sd_ble_uuid_vs_add

[SteveHx]

I can use standard UUIDs and successfully add a Service and several characteristics, so I think the error message above is a red herring. When I attempt to create a custom UUID (since none of the BLE-standardized UUIDs actually fit my application), I get the above error returned from the call to  sd_ble_uuid_vs_add. I have plenty of memory, and indeed the linker offers that it has more than enough:

<warning> nrf_sdh_ble: RAM starts at 0x20005668, can be adjusted to 0x200020E0.
<warning> nrf_sdh_ble: RAM size can be adjusted to 0xDF20.
<error> app: ERROR 4 [NRF_ERROR_NO_MEM] at GlucoseControl.c:170

The above function call traces to an SVCALL macro and there the trail goes cold, so I can't even see what's really happening inside the function. Surely I'm not the only one who has tried following the tutorial at https://devzone.nordicsemi.com/tutorials/b/bluetooth-low-energy/posts/ble-characteristics-a-beginners-tutorial. What am i missing?

[Kevin_L]

I had a similar issue when going through this tutorial:
devzone.nordicsemi.com/.../ble-services-a-beginners-tutorial

Even after increasing the Ram ORIGIN and LENGTH in my .ld file, I still got the error.  In the end, I found that it was adding another custom base UUID (it was buried in NUS_BASE_UUID in ble_nus.c, which is the example I was adapting for my program), so then when I tried to add my own custom base UUID, it was running out of memory.

In the end, I changed NUS_BASE_UUID to match BLE_UUID_OUR_BASE_UUID, and that fixed the issue.

[Kevin_L]

Actually, I just found a better solution.  In sdk_config.h, I just increased NRF_SDH_BLE_VS_UUID_COUNT, and that solved the issue.

[SteveHx]

That value is defined as 0 in the sample apps. Hey, Nordic, why isn't that documented anywhere in the tutorials? Would have saved me an awful lot of time and frustration.