When I connect to my device with an iPhone, using the nRF Connect app, I am experiencing an immediate disconnect. The part does not have time to start pairing. I have shared the Wireshark log in this post. Could someone please help me interpret the log and see what issues I may be experiencing? The log from the app states: "[System] Error disconnect from peripheral _____. The connection has timed our unexpectedly."
I have tried to adjust the clock PPM setting for my boarder some of the previous forum posts, but this does not help the issue.
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
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?
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)?
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?
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?