peer_manager_sm: Could not perform security procedure. smd_params_reply() or smd_link_secure() returned NRF_ERROR_INVALID_ADDR.

[Luke.L]

I am using the example from ble_app_att_mtu_throughput_pca10056_s140, changing the values for:

#define SEC_PARAM_BOND                  1                                       /**< Perform bonding. */
#define SEC_PARAM_MITM                  1                                      /**< Man In The Middle protection not required. */
#define SEC_PARAM_LESC                  1                                       /**< LE Secure Connections not enabled. */
#define SEC_PARAM_KEYPRESS              0                                       /**< Keypress notifications not enabled. */
#define SEC_PARAM_IO_CAPABILITIES       BLE_GAP_IO_CAPS_DISPLAY_ONLY                    /**< No I/O capabilities. */

And adding a default passkey of "000000"

returns an error during bonding:

<error> peer_manager_sm: Could not perform security procedure. smd_params_reply() or smd_link_secure() returned NRF_ERROR_INVALID_ADDR. conn_handle: 1
<error> app: ERROR 16 [NRF_ERROR_INVALID_ADDR]

Any assistance will be greatly appreciated!

[Einar Thorsrud]

Hi,

Neither smd_params_reply() nor smd_link_secure() should return NRF_ERROR_INVALID_ADDR. Which SDK version do you use? Can you put a breakpoint in events_send_from_err_code() and check the call stack so that we see where it comes from (either link_secure() or smd_params_reply_perform()? Can you debug any further? If this does not shed more light, could you upload your project with all modifications here so that I can test on my side?

[Luke.L]

Hi Einar,

Thanks for replying!

It seems to stem from this particular call:

        case PM_EVT_CONN_SEC_PARAMS_REQ:
            params_req_process(p_event);

[Luke.L]

Please kindly see the attached. I am using SDK 15.20,

[Luke.L]

Sorry zip file didn't attach, here you goble_app_att_mtu_edited.zip

[Einar Thorsrud]

Hi,

I just tested your example (after doing a few slight modifications to remove warnings and change logger backend to RTT) but I was not able to reproduce the issue. What do I need to do to reproduce it?

[Luke.L]

I am using segger and my device is NRF52840. I start the application then connect to the device using android NRF connect. The error is thrown during the bonding phase

[Luke.L]

Ok the solution is to include the cc310 encryption libraries.

Best to base the project off the ble_gls example as it already has all the nrf_crypto libraries for you