SDK 15.3 pairing issue

RE: SDK 15.3 pairing issue

skulkarni — Tue, 01 Oct 2019 09:25:16 GMT

Handling the PM_EVT_CONN_SEC_CONFIG_REQ in pm_evt_handler solved the issue.

case PM_EVT_CONN_SEC_CONFIG_REQ:
{
    // Reject pairing request from an already bonded peer.
    pm_conn_sec_config_t conn_sec_config; // = {.allow_repairing = true};
    conn_sec_config.allow_repairing = true;
    pm_conn_sec_config_reply(p_evt->conn_handle, &conn_sec_config);
} break;

RE: SDK 15.3 pairing issue

Simonr — Tue, 24 Sep 2019 07:28:51 GMT

Again, you'll need to delete the bonds from your nRF. You should be able to do so by pressing button 2 while the nRF is asleep according to the BSP BLE Button Assignments, which is included in the ancs_c example according to the Infocenter.

Best regards,

Simon

RE: SDK 15.3 pairing issue

skulkarni — Mon, 23 Sep 2019 09:16:33 GMT

devzone.nordicsemi.com/.../Paring_5F00_fails.pcapng

Hi I am attaching the sniffer log. In packet #471 pairing fails.

Please help me to fix the issue.

RE: SDK 15.3 pairing issue

Simonr — Thu, 12 Sep 2019 11:43:23 GMT

I see. You'll have to delete the bonding information on the nRF side as well. Please see pm_peer_delete for how to do this. Heed the warning to only use this function when not connected to the peer.

Best regards,

Simon

RE: SDK 15.3 pairing issue

skulkarni — Thu, 12 Sep 2019 07:35:07 GMT

Hi Simon,

I am working nRF52 Development kit.

I have just taken the example code, and followed the below steps

1. Erase the complete flash <nrfjprog tool>

2. Load the ANCS example code

3. Connect from the smart phone.

4. Unpair the device from phone.

5. Try to connect again

In the 5th step i get the error.

Since I have not done any changes I expect at least repairing should happen.

RE: SDK 15.3 pairing issue

Simonr — Thu, 12 Sep 2019 06:29:15 GMT

This error could occur for a multitude of reasons, so you'll have to be a bit more specific. What device(s) are you testing this on, and how often does this error occur? One common issue that's seen from error 133 is that the LF crystal isn't configured correctly. If you're using a third-party module that ships without the external LF crystal, you have to change the LF_CLK settings in sdk_config.h in order to configure the internal RC oscillator instead, as our SDK examples use the external LF clock by default.

Best regards,

Simon

RE: SDK 15.3 pairing issue

skulkarni — Thu, 12 Sep 2019 06:04:21 GMT

Dear team,

Any updates on this? I could see many of them facing this issue but no concrete solution for this.

If you feel duplicate please share the link for the solution.