S110 sticks for Service discovery from iPhone

RE: S110 sticks for Service discovery from iPhone

bin simon — Mon, 25 Jan 2016 13:02:48 GMT

I read this thread(devzone.nordicsemi.com/.../) and changed the S110 version into v7.1.0 on trial. As a result, it works fine. I read the s110_nrf51822_7.1.0 release note and at BLE Buf fixes section it is written like this:Fixed an issue sending data after the link had been disconnected might lead to reduce maximum throughput for the next connection. I wonder if this bug has a relation with my problem. Dose anyone help me?

RE: S110 sticks for Service discovery from iPhone

bin simon — Tue, 19 Jan 2016 05:05:27 GMT

Hi, RK.

I checked all events from softdevice. When the the phenomenon occurs, i confirmed only two events as below:

BLE_GAP_EVT_CONNECTED
BLE_EVT_TX_COMPLETE

I suppose that BLE_EVT_TX_COMPLETE is for the last sd_ble_gatts_hvx() before disconnecting from iPhone.

RE: S110 sticks for Service discovery from iPhone

RK — Tue, 19 Jan 2016 02:14:42 GMT

that was the only event I could think of. If it was me debugging here I'd add some code to break/crash/something on ANY event which I don't explicitly handle and see if there's another one being sent in the failing case which needs handling. I wrote a huge GATTS event logger which prints details of every event out of Segger RTT, helps out a lot in times like this.

RE: S110 sticks for Service discovery from iPhone

bin simon — Tue, 19 Jan 2016 02:09:28 GMT

Hi, RK.

Thanks for your reply. I'm handling BLE_GATTS_EVT_SYS_ATTR_MISSING event. But when the phenomenon occurs, BLE_GATTS_EVT_SYS_ATTR_MISSING event is not notified from the softdevice. When the phenomenon occurs and re-connection fails(1st re-connection fails), but 2nd re-connetion succeeds and I can confirm that BLE_GATTS_EVY_SYS_ATTR_MISSSING event is notified from the softdevice. Do you have any ideas what is happening in softdevice inside?

best regards.

RE: S110 sticks for Service discovery from iPhone

RK — Tue, 19 Jan 2016 01:18:22 GMT

After disconnection / reconnection are you receiving an event you're not handling? Perhaps BLE_GATTS_EVT_SYS_ATTR_MISSING. I think the softdevice is waiting for you to reply to something and it sending out empty packets whilst it's waiting .. until the phone finally gives up and disconnects you.