Set-value failure after bonding and deleting bond information

[RAlexeev]

It's a related issue to my previous question Error set-value failure in a Nordic sample. "west flash --erase" command solves the problem for one time. It erases all data, but after the following pairing and rebooting I had the same errors in UART logs. I built and run Bluetooth: Peripheral HIDS keyboard on nRF52840 DK both using nRF Connect SDK v1.3.0 and master branch. After it, I connected to my board and bond using nRF Connect for Mobile on Android. And after it, I taped "Delete bond information".

Fullscreen first_boot.txt Download

*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Starting Bluetooth Peripheral HIDS keyboard example
I: 8 Sectors of 4096 bytes
I: alloc wra: 0, ff0
I: data wra: 0, 0
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 2.3 Build 0
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: d6:c4:f9:a2:02:ad (random)
I: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
I: LMP: version 5.2 (0x0b) subver 0xffff
NFC configuration start
NFC configuration done
Advertising successfully started
Advertising continued
Connected 6a:f9:ac:1d:99:3a (random)
Passkey for 6a:f9:ac:1d:99:3a (random): 894308
Press Button 1 to confirm, Button 2 to reject.
Numeric Match, conn 0x2000177c
Security changed: 6a:f9:ac:1d:99:3a (random) level 4
Pairing completed: f8:c3:9e:2f:98:21 (public), bonded: 1
Key report send error: -13
Disconnected from f8:c3:9e:2f:98:21 (public) (reason 19)

Then I reset my board by "nrfjprog -r" command. And I saw the following log in UART:

Fullscreen second_boot.txt Download

*** Booting Zephyr OS build v2.3.0-rc1-ncs1  ***
Starting Bluetooth Peripheral HIDS keyboard example
I: 8 Sectors of 4096 bytes
I: alloc wra: 0, fa8
I: data wra: 0, a8
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 2.3 Build 0
I: No ID address. App must call settings_load()
Bluetooth initialized
E: set-value failure. key: bt/ccc/f8c39e2f98210 error(-2)
I: Identity: d6:c4:f9:a2:02:ad (random)
I: HCI: version 5.2 (0x0b) revision 0x0000, manufacturer 0x05f1
I: LMP: version 5.2 (0x0b) subver 0xffff
NFC configuration start
NFC configuration done

You can see this error:

E: set-value failure. key: bt/ccc/f8c39e2f98210 error(-2)

Can someone explain to me how to correctly handle this error or where I can read about it?

[Vidar Berg]

Hi,

Sorry for the delayed response. Looks like this is related to the other question you posted here: https://devzone.nordicsemi.com/f/nordic-q-a/64583/errors-after-unpairing-devices-and-further-attempts-to-bond-them? Let me know if that's not the case.

[RAlexeev]

Unfortunately, it's another issue, as I consider. Simon described a problem of a re-pair process, but the problem of an error kinda "E: set-value failure. key: bt/ccc/2047da12f4e80 error(-2)" after resetting is still actual.

[Vidar Berg]

Hi,

I see it now. I was able to replicate this with NCS v1.3.0, and it appears to only happen after a reset, and only for the CCC settings. I have to investigate further to find out why this is.

[Vidar Berg]

Hello,

This issue appears to be related to the CONFIG_BT_SETTINGS_CCC_LAZY_LOADING feature that's enabled by default. When enabled the bt_ccc handler does not get registered in gatt.c but it still attempts to load CCCD settings on startup as if lazy loading was disabled, hence the error. However, despite the warning, the settings are correctly restored on connection, so it seems like it should be safe to ignore this message for now. I will report it as a bug internally.  

[Joakim Andersson]

Correct, the error message can be ignored, no actual issue exists.

Fix to get rid of the error message is here:
https://github.com/zephyrproject-rtos/zephyr/pull/27984

[RAlexeev]

Many thanks for your response and fix.

[RAlexeev]

Aha, I got it! Thank you very much!