This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

about service change can't receive BLE_GATTS_EVT_WRITE

nrf52832     SDK14.2       s132_nrf52_5.0.0_softdevice     PCA10040       ble_app_hids_keyboard  

I modify the project : 

two  service :  one  is   hid   another  is  different  hid_1 

press button 2  init  hid

presss button 3  init  hid_1

connect  the  android  phone , press button2   reset ,and ,init  hid;  press button3   reset  ,and, init  hid_1, reconnect  the phone,

turn  off and on the bluetooth(android  phone),but I can‘t receive   BLE_GATTS_EVT_WRITE(gcm_ble_evt_handler),  I  enable  the  NRF_SDH_BLE_SERVICE_CHANGED

I  can’t  know the reason,  but  SDK15.2   it  succeed,  why?   How  can  i do?

Parents
  • Hi

    I've found that the only change between the gcm_ble_evt_handler in SDK14.2 and SDK15.2 is that the #if PM_SERVICE_CHANGED_ENABLED is present in SDK15.2. So, the most obvious fix would be to add this into your SDK14.2 project. You'll have to define it in gatt_cache_manager.c and in your sdk_config.h file as well as implement it just like in SDK15.2 in order to patch this. That's the patch we provided to the gatt_cache_manager from SDK 14.2 to SDK 15.2, so that would be what fixes this in SDK 14.2 as well.

    I must admit that I still don't see why you can't use SDK 15.2 as your actual project, seeing how it's fixed there already, but that's up to you to decide.

    Best regards,

    Simon

Reply
  • Hi

    I've found that the only change between the gcm_ble_evt_handler in SDK14.2 and SDK15.2 is that the #if PM_SERVICE_CHANGED_ENABLED is present in SDK15.2. So, the most obvious fix would be to add this into your SDK14.2 project. You'll have to define it in gatt_cache_manager.c and in your sdk_config.h file as well as implement it just like in SDK15.2 in order to patch this. That's the patch we provided to the gatt_cache_manager from SDK 14.2 to SDK 15.2, so that would be what fixes this in SDK 14.2 as well.

    I must admit that I still don't see why you can't use SDK 15.2 as your actual project, seeing how it's fixed there already, but that's up to you to decide.

    Best regards,

    Simon

Children
Related