Skip to content
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

Bluetooth: LL/PAC/SLA/BV-01-C fails if Slave-initiated Feature Exchange is disabled #23494

Closed
wopu-ot opened this issue Mar 16, 2020 · 0 comments · Fixed by #23495
Closed

Bluetooth: LL/PAC/SLA/BV-01-C fails if Slave-initiated Feature Exchange is disabled #23494

wopu-ot opened this issue Mar 16, 2020 · 0 comments · Fixed by #23495
Assignees
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug

Comments

@wopu-ot
Copy link
Collaborator

wopu-ot commented Mar 16, 2020

Describe the bug
Bluetooth qualification test LL/PAC/SLA/BV-01-C fails if Slave-initiated Features Exchange is disabled (CONFIG_BT_CTLR_SLAVE_FEAT_REQ=n). This happens because the slave device with that configuration does not respond correctly to an unexpected LL_FEATURE_RSP.

To Reproduce
Run BLE qualification test LL/PAC/SLA/BV-01-C on a device configure with CONFIG_BT_CTLR_SLAVE_FEAT_REQ=n and Slave-initiated Features Exchange disabled in the ICS.

Expected behavior
All qualification tests pass

Impact
Cannot qualify BLE stack with Slave-initiated Features Exchange disabled. Enabling this entails also enabling Connection Parameter Request Procedure (these are for some reason tied together when selecting features), which is highly undesirable in our use case.

Environment (please complete the following information):

  • Zephyr 2.2

Additional context
A possible fix should ideally be back-ported to the 2.2 branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: medium Medium impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants