Receiving internal error on securing BLE link

RE: Receiving internal error on securing BLE link

Petter Myhre — Thu, 02 Mar 2017 12:18:47 GMT

Great! I converted my comment to an answer, appreciate if you accept it. Just click the circle next to it, thx.

RE: Receiving internal error on securing BLE link

John — Thu, 02 Mar 2017 12:17:06 GMT

Hi Peter, I have switched to SDK 11.0.0.0 and that seems to have corrected the issue. Thanks for the advice!

RE: Receiving internal error on securing BLE link

Petter Myhre — Tue, 28 Feb 2017 13:00:16 GMT

Ok. That explains it :) I recommend using a production version of the SDK, not an alpha, if that is inconvenient I recommend porting a newer version of the Peer Manager/FDS/Fstorage, to see if that fixes the issue. If I remember correctly, the Peer Manager library in SDK 10.0.0 (and SDK 11.0.0.2-alpha) was experimental, so quite a lot of changes and bug fixes have been applied in later releases.

RE: Receiving internal error on securing BLE link

John — Tue, 28 Feb 2017 10:19:04 GMT

Sorry, just to clarify I am using the SDK 11.0.0.2-alpha. I believe in SDK 11.0.0 it corresponds to pm_peer_count().

RE: Receiving internal error on securing BLE link

Petter Myhre — Mon, 27 Feb 2017 18:05:16 GMT

Are you sure you are using SDK11.0.0? I couldn't find any pm_n_peers() function in the Peer Manager library there, but I found it it SDK10.0.0, which doesn't support nRF52.