RE: Problem reading custom characteristics using CLI example

Jchristf — Mon, 20 May 2019 03:50:34 GMT

I added a very simple extension to the CLi example to allow entering in a UUID type when doing "gatt characteristics <address> <uuid/type>"

That allows me to get then handle range and fire of the SD characteristic discovery for custom services as well (they each have unit UUID type)

The problem is that I get an infinite loop on response event from this discover call: the first has UUID of 0xFFFF and then follows an infinite loop of response events with UUID 0x100. I can see in nrfConnect that I have 3 characteristics: 0xFFFF, 0x100 and 0x200. But it keep reporting the 0x100 infinitely.

Putting in some debug, I can see that handle range is initially 1-8 (yielding 0xFFFF). Then seach continues for handles 4-8, yielding 0x100, which then repeats infinitely...

RE: Problem reading custom characteristics using CLI example

Kenneth — Tue, 07 May 2019 11:01:41 GMT

This may be a limitation of the CLI example project (I can report this as an improvement for future), but in general you can find the following thread on how to work with 128-bit UUID:

https://devzone.nordicsemi.com/f/nordic-q-a/12203/how-can-i-get-128bit-service-uuid-from-peripheral