-
Notifications
You must be signed in to change notification settings - Fork 6.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CCC does not get cleared when CONFIG_BT_KEYS_OVERWRITE_OLDEST is enabled #23961
Comments
@joerchan I redid the test as follows:
Connect using smartphone with (nrfconnect).
Connect device 2 (bluetoothctl) and perform
Corresponding output from device:
Connect again with device 1 (nrfconnect)
|
I am still seeing this issue occasionally, but I am using bluetooth mesh. I connect to the bearer successfully but the bearer does not open. And my device is outputting the following: bt_gatt: No space to store CCC cfg I'm not exactly sure how to reproduce. It seems to be happening pretty randomly and I can't pinpoint exactly when it happens. |
@johnsmithecon Please find out how to reproduce your issue and open a new bug-report if you can |
Describe the bug
When CONFIG_BT_KEYS_OVERWRITE_OLDEST is enabled, a warning gets thrown by bt_gatt saying no space to store CCC cfg.
To Reproduce
Steps to reproduce the behavior:
git apply prj.conf.patch && west build -b nrf52_pca10040 samples/bluetooth/peripheral_hr
west flash
Expected behavior
Expected is that the CCC can be normally subscribed to without warning messages from
bt_gatt
Impact
This leads to all notifications being broken once in this situation. If the device is power cycled the state is returned to normal.
Screenshots or console output
Environment (please complete the following information):
commit 9518bd19b7a736bd649fa2fc8d8d52967c0b486f (HEAD, tag: zephyr-v2.2.0, tag: v2.2.0)
Additional context
Short discussion with Joakim revelead this could be an issue in CONFIG_BT_KEYS_OVERWRITE_OLDEST, as it's quite a new feature
patch:
The text was updated successfully, but these errors were encountered: