nrf_desktop: keyboard cannot pair with dongle after device description changed.

Paring was successful when using nrf_desktop's default device description configs, but after I modified those lines in "prj_keyboard.conf" of keyboard:
CONFIG_DESKTOP_DEVICE_PRODUCT="Blueism Keyboard"
CONFIG_DESKTOP_DEVICE_MANUFACTURER="Helix Lab"
CONFIG_DESKTOP_DEVICE_VID=0x484C
CONFIG_DESKTOP_DEVICE_PID=0x9B26
and those lines in "prj_release.conf" of nRF52840dongle:
CONFIG_DESKTOP_DEVICE_PRODUCT="Dongle Blueism Keyboard"
CONFIG_DESKTOP_DEVICE_MANUFACTURER="Helix Lab"
CONFIG_DESKTOP_DEVICE_VID=0x484C
CONFIG_DESKTOP_DEVICE_PID=0x9B14
my dongle cannot pair with it.
Parents
  • Hello,

    My first thought is for instance that one of the peers have some bonding information cached/stored from previous communication, and when you now have updated some configuration, then one of the peers have at the same time erased it's bonding information, and thereby you end up in a situation where you are not able to successfully bond again (for security reasons).

    My suggestion would be to do a full eraseall on both peers before you reprogram them, if that doesn't solve the problem my next suggestion would be to check for any errors in the application log which may provide further details of what is failing.

    Kenneth

Reply
  • Hello,

    My first thought is for instance that one of the peers have some bonding information cached/stored from previous communication, and when you now have updated some configuration, then one of the peers have at the same time erased it's bonding information, and thereby you end up in a situation where you are not able to successfully bond again (for security reasons).

    My suggestion would be to do a full eraseall on both peers before you reprogram them, if that doesn't solve the problem my next suggestion would be to check for any errors in the application log which may provide further details of what is failing.

    Kenneth

Children
Related