Characteristic limit

RE: Characteristic limit

Pertti Kasanen — Thu, 13 Aug 2015 14:53:37 GMT

I run into the same problem. Cannot increase the attribute table enough to add a 10th attribute. Neither with _STACK nor with _USER. Will have to do similar consolidation as RK.

RE: Characteristic limit

Susheel Nuguru — Tue, 21 Jul 2015 12:02:18 GMT

andrey, could you please update this thread with latest info, if this answer helped you then please click the ✓ to the left of the answer so that others can come and look here.

RE: Characteristic limit

RK — Sat, 27 Jun 2015 00:59:02 GMT

My assumption, having read about this problem a few times, is that there is still some fixed-size table somewhere unaffected by the free memory you give to the attribute table. eg perhaps you can store the attribute data there and increase the size for that, however the internal data for the characteristics themselves can't use the extra room.

Why don't you file a support case on this and see if you can get some help from engineering.

RE: Characteristic limit

andrey — Fri, 26 Jun 2015 18:45:51 GMT

I understand that BLE_GATTS_VLOC_USER changes only the location of the value and everything else stays in the table. What I don't understand is why increasing it's size doesn't help.

RE: Characteristic limit

pastisprologue — Fri, 26 Jun 2015 18:25:48 GMT

Hi Andrey,

I've run into a similar issue. I think the issue is that while you do employ BLE_GATTS_VLOC_USER, that only moves the location of the actual value itself to the application memory. Everything else about that characteristic, it's UUID, handle, properties, characteristic properties, descriptors, etc., still live in the ATT table (which is in the memory region of the softdevice).

I resolved it on my end by consolidating characteristics common to all of my services into their own service with only that single, common characteristic. Of course, this was my workaround, and highly specific. You will have to be more creative in your own resolution.

Hope this helps, past