ble_app_hids_keyboard will not run if SEC_PARAM_BOND = 0

Hi Nordic Team,

We have no problem with using ble_app_hids_keyboard app,

However, in some use cases, we would like the application to run as "Just Works" to access other characteristics, say battery voltage characteristics for example. And well in some cases depending on the connected client HID can work without bonding too.

 Testing this just with nrf52 DVK,   When SEC_PARAM_BOND  = 0, the firmware faults.

In debug, runs to the last call in Main.c peer_manager_init();

Appears to be in the peer manager  pm_init(void)?

Any thoughs on how we can get this to run?

Regards,

Eric

Parents
  • Appreciate your refrence for  "difference between pairing and bonding".

    We need "just works" connect without pairing  for this project (when optionally will not be using the HID), such that on disconnect, peripheral and central "forget" about each other.  Just like in the ble_app_template example.

    I do note that the template example has SEC_PARAM_BOND   1  and settings as below - yet behaves as just works. A bit confusing

    SEC_PARAM_BOND                  1
    sec_param.kdist_own.enc  = 1;
    sec_param.kdist_own.id   = 1;
    sec_param.kdist_peer.enc = 1;
     sec_param.kdist_peer.id  = 1;

    Is this requirement going to be impossible to meet?

Reply
  • Appreciate your refrence for  "difference between pairing and bonding".

    We need "just works" connect without pairing  for this project (when optionally will not be using the HID), such that on disconnect, peripheral and central "forget" about each other.  Just like in the ble_app_template example.

    I do note that the template example has SEC_PARAM_BOND   1  and settings as below - yet behaves as just works. A bit confusing

    SEC_PARAM_BOND                  1
    sec_param.kdist_own.enc  = 1;
    sec_param.kdist_own.id   = 1;
    sec_param.kdist_peer.enc = 1;
     sec_param.kdist_peer.id  = 1;

    Is this requirement going to be impossible to meet?

Children
No Data
Related