Problem detecting 128-bit service w/ 16-bit char using BLE driver.

RE: Problem detecting 128-bit service w/ 16-bit char using BLE driver.

Hung Bui — Mon, 04 Jul 2016 11:03:08 GMT

Hi Leon,

Do you have the same issue that the descriptor was wrong when discovering the stock HRM example ?

Could you take a screenshot of the service discovery result when you use Master Control Panel on PC/Android ?

It's a little bit complicated to debug this because we need to track down to the serialization library that the python code based on, and then if the issue doesn't lie there, we need to get to the service discovery code.

RE: Problem detecting 128-bit service w/ 16-bit char using BLE driver.

Leon Woestenberg — Fri, 01 Jul 2016 11:53:34 GMT

This is no bug fix for the issue I am seeing. Instead I am now going to try the SD 2.0.1 that comes with the pc-ble-driver-py release which has a newer SD 2.0.1, newer lib/includes and SDK11 patch.

RE: Problem detecting 128-bit service w/ 16-bit char using BLE driver.

Leon Woestenberg — Wed, 29 Jun 2016 21:15:55 GMT

By pure luck I found this patch lurking in the pc-ble-driver-py folder /usr/local/lib/python2.7/dist-packages/pc_ble_driver_py/hex/SD20_SDK11.patch, which seems a likely candidate for a fix of the (wrong) behaviour I am seeing:

diff --git a/components/serialization/application/codecs/s130/middleware/app_mw_ble_gatts.c b/components/serialization/application/codecs/s130/middleware/app_mw_ble_gatts.c
--- a/components/serialization/application/codecs/s130/middleware/app_mw_ble_gatts.c
+++ b/components/serialization/application/codecs/s130/middleware/app_mw_ble_gatts.c
@@ -586,7 +586,8 @@ static uint32_t gatts_attr_get_rsp_dec(const uint8_t * p_buffer, uint16_t length
     const uint32_t err_code = ble_gatts_attr_get_rsp_dec(
         p_buffer,
         length,
-        (ble_gatts_attr_md_t **)&mp_out_params[0],
+        (ble_uuid_t **)&mp_out_params[0],
+        (ble_gatts_attr_md_t **)&mp_out_params[1],
         &result_code);