-
Notifications
You must be signed in to change notification settings - Fork 8k
tests: Bluetooth: Tester: Set controller ACL buffer size #89680
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
tests: Bluetooth: Tester: Set controller ACL buffer size #89680
Conversation
Change the ACL buffer sizes to be a higher value than the default, as that caused some issues with the CIS established event. Signed-off-by: Emil Gydesen <[email protected]>
#AutoPTS run zephyr nrf53 CAP/INI/UST/BV-01-C |
Scheduled PR #89680 (comment), board: nrf53, estimated start time: 19:24:29, test case count: 1, estimated duration: 0:10:50 Test cases to be runCAP/INI/UST/BV-01-C |
AutoPTS Bot results: Successful tests (1)CAP CAP/INI/UST/BV-01-C PASS |
|
|
|
||
# ACL data sizes | ||
CONFIG_BT_BUF_ACL_TX_SIZE=251 | ||
CONFIG_BT_BUF_ACL_RX_SIZE=255 | ||
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be use of 27 bytes as max ACL data size exposes a bug in the Zephyr Controller? This should be easily reproducible in bsim CI tests with the hci_ipc and nrf52_bsim audio tests with 27 byte ACL configured, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like a bug in the controller, yes, but not sure how to properly determine that yet.
I did try to run the test from #87207 which would also connect the CIS using the same BT Tester build, but at least in BSIM it doesn't seem to fail. Could be due to timing and availability of buffers?
Change the ACL buffer sizes to be a higher value than the default, as that caused some issues with the CIS established event.
Relates to #88300.