BLE - NUS data communication problem

[air]

• environment 1 - nrf51822/SDK 10/SD110/NUS peripheral/device manager use

  • SEC_PARAM_BOND 0
  • SEC_PARAM_MITM 1
  • SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_DISPLAY_ONLY
  • SEC_PARAM_OOB 0
  • SEC_PARAM_MIN_KEY_SIZE 7
  • SEC_PARAM_MAX_KEY_SIZE 16
  • sec_param.kdist_central.enc = 0;
  • sec_param.kdist_central.id = 1;
  • sec_param.kdist_central.sign = 0;
  • sec_param.kdist_periph.enc = 1;
  • sec_param.kdist_periph.id = 1;
  • sec_param.kdist_periph.sign = 0;

• environment 2 - nrf51822/SDK 12.1.0/SD130/NUS peripheral/peer manager use

  • SEC_PARAM_BOND 1
  • SEC_PARAM_MITM 1
  • SEC_PARAM_LESC 0
  • SEC_PARAM_KEYPRESS 0
  • SEC_PARAM_IO_CAPABILITIES BLE_GAP_IO_CAPS_DISPLAY_ONLY
  • SEC_PARAM_OOB 0
  • SEC_PARAM_MIN_KEY_SIZE 7
  • SEC_PARAM_MAX_KEY_SIZE 16
  • sec_param.kdist_own.enc = 1;
  • sec_param.kdist_own.id = 1;
  • sec_param.kdist_peer.enc = 1;
  • sec_param.kdist_peer.id = 1;

• question - 1 : BOND (0) and MITM (1) can be set in environment-1, but BOND (0) and MITM (1) can not be set in environment-2. Is there a way to set like environment-1?

• question - 2 : In environment - 1, the first passkey is used for pairing. After that without pairing BLE_GAP_EVT_SEC_PARAMS_REQUEST and Sd_ble_gap_sec_params_reply(m_conn_handle, BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP, NULL, NULL) are used for NUS data communication. I tried the same procedure in environment-2, but NUS data communication fails. Is there anything I missed?

• question - 3 : Can peer_manager_init() be re-used during NUS data communication?

[Petter Myhre]

1. Why can it not be set?

2. What behavior do you want? Pairing with passkey first, and then deny pairing after that? Then you can call pm_sec_params_set(NULL) after the first pairing.

3. If you can initialize Peer Manager twice? Why would do that?