• State Not Answered
  • Replies 11 replies
  • Subscribers 64 subscribers
  • Views 3587 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 129487
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

DFU, caching & iOS

gkovelman_tap

Hi,

I know that this is a known issue, but I'm seeing caching issues often with iOS. I'm using S132 v5.0.0, SDK 14.0 against custom application with iOS DFU SDK and often I'm seeing that my device is unusable after DFU unless I toggle the bluetooth button in the iOS Settings window. If the DFU fails, then the device's displayed name continues to be DfuTarg unless bluetooth is toggled.

I'm using bonded devices, services changed characteristic is enabled in both app and BL.

Any reason why wouldn't the iOS discover the services correctly? Any solution for this issue? Workarounds?

I'll appreciate the help

Parents
  • 0

    Continuing debugging, looks like the FW doesn't trigger SC indication at all. I've put breakpoints at gatts_cache_manager.c, line 359, right after sd_ble_gatts_service_changed call and a breakpoint at gatt_cache_manager.c, line 494, at BLE_GATTS_EVT_SC_CONFIRM case and none of them are hit.

    Looks like the FW is not triggering indication. I'm wondering if iOS 11 has anything to do with that.

Reply
  • 0

    Continuing debugging, looks like the FW doesn't trigger SC indication at all. I've put breakpoints at gatts_cache_manager.c, line 359, right after sd_ble_gatts_service_changed call and a breakpoint at gatt_cache_manager.c, line 494, at BLE_GATTS_EVT_SC_CONFIRM case and none of them are hit.

    Looks like the FW is not triggering indication. I'm wondering if iOS 11 has anything to do with that.

Children
No Data
Related