Trouble connecting to iOS

RE: Trouble connecting to iOS

Wavecake — Fri, 12 Oct 2018 19:38:25 GMT

It ended being that noise introduced by an LED pattern caused the disconnect events. The LED pattern on connection was driven by PWM which impacted the RF signal integrity. The loss of communication resulted in missed packets which led to the HCI timeout.

The recommended steps in this post helped the most. In particular, I took an example from the Nordic SDK and ported to our new board. When I saw the example program worked, I had something to go off of. From there, I just commented out initialization code to make it look similar. Eventually, nothing was left except for the LED pattern. Thanks for all your help Kenneth.

stackoverflow.com/.../ios-how-to-discover-unadvertised-services-on-a-ble-peripheral

RE: Trouble connecting to iOS

Wavecake — Thu, 11 Oct 2018 21:55:23 GMT

I also noticed that I am receiving an unhandled BLE_EVT code 4. The header files for common evts don't have an event defined for that value. Any ideas what that could mean?

RE: Trouble connecting to iOS

Wavecake — Thu, 11 Oct 2018 16:15:03 GMT

Yes, I updated to S132v3.1

Here's a screen shot of from the debugger. The reason shows up as BLE_HCI_CONNECTION_TIMEOUT.

I also noticed the last GATTC event has an error code. Is that a valid event? Or is it wrong to interpret that event since the current event is a GAP_EVT disconnect?

RE: Trouble connecting to iOS

Kenneth — Thu, 11 Oct 2018 06:48:32 GMT

I assume you have updated to S132v3.1.

What is the disconnect reason when disconnecting (e.g. on BLE_GAP_EVT_DISCONNECTED check p_ble_evt->evt.gap_evt.params.disconnected.reason)?

Best regards,
Kenneth

RE: Trouble connecting to iOS

Wavecake — Wed, 10 Oct 2018 19:22:07 GMT

So far I've narrowed some things down.

1. The BLE HTS example runs on my hardware and allows an iOS connection without any issues.

2. I realized that I don't have an external LFC. Instead of using the SYNTH setting, I switched to the RC clk with recommended 16/2 settings. This didn't fix any issues, but I believe it is the right thing to do.

I think the next step is to identify some error codes related to when the device disconnects. Are there any variables I should be looking at in particular?

RE: Trouble connecting to iOS

Kenneth — Tue, 02 Oct 2018 16:58:55 GMT

The log is indeed odd, do you see this issue only when running on your own hardware or also when running on nRF52832-DK?

In any case I recommend to update to S132v3.1, you can download S132v3.1 from here:
https://www.nordicsemi.com/eng/nordic/Products/nRF52832/S132-SD-v3/56261

Make sure to update your project with the S132v3.1 softdevice header files, then re-compile your application, and you should be able to program both S132v3.1 softdevice and application.

I recommend to check the known issue list:
https://devzone.nordicsemi.com/f/nordic-q-a/16156/what-are-sdk-12-x-0-known-issues

Best regards,
Kenneth