16bits to 12bits UUID conversion problem on PC

RE: 16bits to 12bits UUID conversion problem on PC

jpo38 — Fri, 03 Jul 2015 14:28:03 GMT

It works! I can then remove my local map. Thanks again!

RE: 16bits to 12bits UUID conversion problem on PC

Hung Bui — Fri, 03 Jul 2015 14:07:25 GMT

btw, an easy workaround that can avoid the assertion is to set the value of "len" to something >16 for example 17. Then it should be fine to call sd_ble_uuid_encode().

RE: 16bits to 12bits UUID conversion problem on PC

jpo38 — Fri, 03 Jul 2015 14:04:34 GMT

Great! Thanks for the quick investigation!

RE: 16bits to 12bits UUID conversion problem on PC

Hung Bui — Fri, 03 Jul 2015 14:00:31 GMT

@jpo38: I got the confirmation from the R&D team that it was a bug in the serialization library in the BLE driver. We did a wrong assertion and throw error code 12 because of that bug.

This explained why I couldn't reproduce it when I tried directly on the nRF51 chip.

This only affects sd_ble_uuid_encode. So sd_ble_uuid_vs_add() works just fine.

I have reported the bug in the system, and it will be fixed in the next release of the SDK and the BLE driver.

I'm glad that you already found the workaround. Thanks for reporting the issue.

RE: 16bits to 12bits UUID conversion problem on PC

jpo38 — Fri, 03 Jul 2015 13:46:29 GMT

Great, good to know you could duplicate this. Waiting for a fix, I simply saved the mapping between types and corresponding 128bits mask on my side and do the resolution myself instead of calling sd_ble_uuid_encode...so I'm not stuck with that anymore. But it would be nice to have it be fixed for good on your side.

RE: 16bits to 12bits UUID conversion problem on PC

Hung Bui — Fri, 03 Jul 2015 12:10:54 GMT

@jpo38: I tried with the BLE drive, and reproduced your issue. I am talking with the developer to find the root cause. It could be an issue with the serialization library we have.

I will let you know when we figure out.