Keyboard can't work

RE: Keyboard can't work

Asbjørn — Tue, 07 Oct 2014 11:38:47 GMT

The information that's changed is bonding information and expected. I don't know what you are pairing with, but the default nRFready Desktop 2 v1.0.5 was not tested with Android, iOS or Win8.1, so we do expect it to have some strange behavior by default with these host when it comes to pairing and bonding. So the recommendations would be to upgrade both kit and SDK version you use if you are starting a new development to ensure that you are able to make use of the latest upgrades and functionality.

RE: Keyboard can't work

Manlio — Mon, 29 Sep 2014 08:45:02 GMT

There SDK is nRFready Desktop 2 v1.0.5. And the softdevice is 5.2.1. Chip version is N51822 QFAAC0 1324BJ.

assert_nrf... s_line_num = 769, s_file_name = ......\common\modules\m_coms_ble_flash.c

assert_nrf... s_line_num = 783, s_file_name = src\ll_lm.s0.c

Beginning, we can connect and bond, and it can work normally. Somtime it can't work suddenly. Then we debug, find that error message and the data in 0x3FC00 to 0x3FC20 is different.

RE: Keyboard can't work

Asbjørn — Wed, 24 Sep 2014 12:14:34 GMT

May I ask you to update the case with information on what code you are running, is it from the SDK, then which version of the SDK, softdevice? Chip revisions/marking?

Does the keyboard start at all when the situation is as in the left part of the picture? Are you able to connect?