Connection security failed: role: Central in ble_app_rscs_c

RE: Connection security failed: role: Central in ble_app_rscs_c

nvelozsavino — Fri, 17 Jan 2020 14:40:00 GMT

I've created it ere:

devzone.nordicsemi.com/.../central-device-claims-to-have-connected-but-no-connection-event-is-fired-on-the-peripheral

RE: Connection security failed: role: Central in ble_app_rscs_c

Mttrinh — Fri, 17 Jan 2020 13:56:36 GMT

Hi,

This thread is over a year old, I suggest you open a new ticket for your case and this issue will be handled there.

RE: Connection security failed: role: Central in ble_app_rscs_c

nvelozsavino — Fri, 17 Jan 2020 13:26:14 GMT

I'm also having this issue, in my case, the application is based on the multirole example. When acting as a central, it scans and found a peripheral that was already bonded before. The central says that it connected, I'm receiving the PM_EVT_BONDED_PEER_CONNECTED event, and the BLE_GAP_EVT_CONNECTED. I've tested with and without the pm_handler_secure_on_connection call when receiving the PM_EVT_BONDED_PEER_CONNECTED which it will start the Secure connection, when used it doesn't show the PM_EVT_CONN_SEC_START, PM_EVT_CONN_SEC_SUCCEEDED nor PM_EVT_CONN_SEC_CONFIG_REQ.

I don't know if the problem is related to the primary service discovery which is showing me the following logs:
[16:17:34:791] <debug> ble_db_disc: Starting discovery of service with UUID 0xFF80 on connection handle 0x0.
[16:17:34:791] <debug> nrf_ble_gq: Adding item to the request queue
[16:17:34:796] <debug> nrf_ble_gq: GATTC Primary Services Discovery Request
[16:17:34:796] <debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted again later.
[16:17:34:802] <debug> nrf_ble_gq: Processing the request queue...
[16:17:34:802] <debug> nrf_ble_gq: GATTC Primary Service Discovery Request
[16:17:34:802] <debug> nrf_ble_gq: SD is currently busy. The GATT request procedure will be attempted again later.

It disconnects before completing the primary service discovery request

Even if I'm not securing the connection I see this log:
<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Encryption, error: 4352

I've tracked the event up to sm_ble_evt_handler of the security manager, however this event is fired by the Softdevice when calling the ble_evt_handler registered by the peer_manager

Another thing I've noticed is that when debugging the peripheral side I can't see any event of BLE_GAP_EVT_CONNECTED nor PM_EVT_BONDED_PEER_CONNECTED even when the central device is showing me those events. It's like the Central device is receiving false BLE_GAP_EVT_CONNECTED events from the softdevice and it's not sending any actual connection packets to the peripheral

I've tried with both scan_parameter.extended =1 and =0 and it's the same, no BLE_GAP_EVT_CONNECTED event on the peripheral

I'm using nrf52832, SDK 16.0.0, Softdevice s132 7.0.1

It's important to note that after a mass erase on the central, the peripheral connects perfectly (after deleting bonds on the peripheral) but after several successful connection, the problem starts and it never connect again.

RE: Connection security failed: role: Central in ble_app_rscs_c

HSh — Wed, 06 Mar 2019 18:35:30 GMT

Hi, I did so and the problem is still there.

RE: Connection security failed: role: Central in ble_app_rscs_c

BendaEng — Wed, 06 Mar 2019 02:05:36 GMT

Hi,

I was having this same issue. I was able to mitigate this through connecting to the Target (in SES with a development board Target -> Connect J-Link) and Erasing the board and re-flashing (Target -> Erase All). Then I re-flashed and ran my applications. My best guess is their is some corruption that occurs in RAM where the SoftDevice is located. Maybe this solution will work for you too.

Thanks!

RE: Connection security failed: role: Central in ble_app_rscs_c

HSh — Tue, 19 Feb 2019 19:50:16 GMT

Yes, it's almost the same with another iPhone. Although it eventually succeeds, but I need to quickly establish a connection when the user comes to the office and before he/she arrives to the desk. This issue sometimes imposes a long delay and I am not able to reach the design goal.

would appreciate to let me know whenever there's an update.

RE: Connection security failed: role: Central in ble_app_rscs_c

Mttrinh — Mon, 18 Feb 2019 15:43:25 GMT

I don't have any update on this matter for now, but in your case have you tried testing with other iphones to see if it makes any difference? I do manage to reproduce it but it isn't often like you see it. Also, it is working despite the error message, the security will retry until it succeed.

RE: Connection security failed: role: Central in ble_app_rscs_c

HSh — Mon, 11 Feb 2019 23:45:45 GMT

Hello Mttrinh, I was wondering if you have any update for me.

RE: Connection security failed: role: Central in ble_app_rscs_c

Mttrinh — Fri, 25 Jan 2019 13:25:39 GMT

Hi,

I managed to reproduce the issue and have reported this internally. I will update this case when we find the cause of this issue.

RE: Connection security failed: role: Central in ble_app_rscs_c

Mttrinh — Mon, 21 Jan 2019 11:52:24 GMT

Hi,

I will try to reproduce this issue and update you as soon as possible.

RE: Connection security failed: role: Central in ble_app_rscs_c

HSh — Fri, 18 Jan 2019 19:00:13 GMT

This looks similar to my problem. Let's wait for Mttrinh help.

RE: Connection security failed: role: Central in ble_app_rscs_c

Jan Van Moer — Wed, 16 Jan 2019 10:15:34 GMT

Hi,

I have a similar issue, I'm using the ble_app_multirole_lesc example for nRF5_SDK_15.2.0_9412b96.
I have erased 2 dev kits and placed the example on both.

When they try to connect I end up with this error:

<info> app: CENTRAL: Already connected to this device as PERIPHERAL (handle: 0), disconnecting.
<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Encryption, error: 4352
<warning> peer_manager_handler: Disconnecting conn_handle 0.
<info> app: CENTRAL: Disconnected, handle: 0, reason: 0x16

And the other one:

<info> app: PERIPHERAL: Already connected to this device as CENTRAL (handle: 1), disconnecting.
<info> app: PERIPHERAL: Disconnected, handle 1, reason 0x13.

I'm not able to have a connection and receive heart rate data. Any clue what can go wrong ?

Regards,

Jan

RE: Connection security failed: role: Central in ble_app_rscs_c

HSh — Fri, 11 Jan 2019 18:25:53 GMT

Hi Mttrinh,

Yes, I have used a fresh copy of the SDK. I just compiled the template using IAR with no changes.

When I keep the iPhone close to the DK, sometimes, I don't see the error. But if I keep the iPhone 50 cm away, I see the error quiet often. Steps to re-produce:

1. Make sure iPhone is not paired.

2. Erase the flash, burn the softdevice and app.

3. Using LighBlue, advertise BLE_UUID_RUNNING_SPEED_AND_CADENCE

4. Connect and pair (you'll see the pairing request on iPhone).

5. Turn the DK off/on and you will see the error several times before it succeeds.

Thanks

RE: Connection security failed: role: Central in ble_app_rscs_c

Mttrinh — Fri, 11 Jan 2019 13:26:15 GMT

Hi,

I tested the example on my side and aren't able to reproduce the issue. Could you give me a detailed step-by-step procedure on how I can reproduce this?

Have you tried to download a fresh copy of the SDK from our website?