Closed mkasenberg closed 6 months ago
Please use our bug template when reporting bugs. You need to edit this issue to include the information requested in https://github.com/zephyrproject-rtos/zephyr/blob/main/.github/ISSUE_TEMPLATE/001_bug_report.md
We should add broadcast testing to the existing GMAP and CAP AC tests, which currently only covers unicast.
@mkasenberg is there any pointer to be on "getting started" to be able to reproduce the failures reported?
To Reproduce With the AutoPTS and nRF5340 board.
Assuming a new resource working on this issue, what are the needed steps to reproduce the issue?
@mkasenberg is there any pointer to be on "getting started" to be able to reproduce the failures reported?
To Reproduce With the AutoPTS and nRF5340 board.
Assuming a new resource working on this issue, what are the needed steps to reproduce the issue?
I'll create a PR to add the CAP and GMAP broadcast audio configurations for BSIM
AutoPTS instruction can be found at: https://docs.zephyrproject.org/latest/connectivity/bluetooth/autopts/autopts-win10.html https://docs.zephyrproject.org/latest/connectivity/bluetooth/autopts/autopts-linux.html
Steps to reproduce:
Have nRF5340 board (revision 2.0.0 in my case)
Have 1 PTS dongle (the LE Only one)
Have installed the PTS 8.5.3.4
Have installed the AutoPTS
I use Windows as host, because the PTS starts faster than when I used Linux host + Windows virtual machine. But it should not matter. I have installed Python 3.11.6..
Last Zephyr SHA that I tested and the issue still persisted is c3e8b731eff5beb5b28aef248bbc8ed20a2c7419, so git-checkout on that:
git checkout c3e8b73
west update
Go to the zephyrproject/zephyr/samples/bluetooth/hci_ipc directory, then build and flash the app for the netcore:
west build -b nrf5340dk_nrf5340_cpunet -- -DOVERLAY_CONFIG='nrf5340_cpunet_iso-bt_ll_sw_split.conf;../../../tests/bluetooth/tester/nrf5340_hci_ipc_cpunet.conf'
west flash
Go to the zephyrproject/zephyr/tests/bluetooth/tester directory, then build and flash the app for the appcore:
west build -b nrf5340dk_nrf5340_cpuapp -- -DOVERLAY_CONFIG='nrf5340_hci_ipc.conf;overlay-le-audio.conf'
west flash
Close the PTS, if it is opened.
Go to the auto-pts directory and start the autopts server:
python autoptsserver.py
The autopts server will start the PTS in automation mode. Wait until the autoptsserver prints OK:
$ python autoptsserver.py
(2366879466768) Starting PTS 65000 ...
Local IP address: ('192.168.107.1', 'fe80::f87b:c093:ad28:dae8') DNS None
Local IP address: ('192.168.9.117', 'fe80::a694:4949:87af:e0b1') DNS None
Local IP address: ('192.168.58.1', 'fe80::f0b7:3be5:cc53:1889') DNS None
Serving on port 65000 ...
(2366879466768) OK
00 80 ff 00 00
It is the BTP ready event. You can use the PuTTY or the below python script to check the port output:
import serial
com = 'COM4'
ser = serial.Serial(com, 115200, timeout=5)
ser.flushInput()
ser.flushOutput()
input('Reset board and press enter')
print(ser.read(9999))
ser.close()
There should be no other bytes in the output except those of the BTP Ready event.
For Windows users:
python ./autoptsclient-zephyr.py zephyr-master -t COM4 -b nrf53 -c BAP/BSRC/STR/BV-09-C
For Linux users:
python ./autoptsclient-zephyr.py zephyr-master -t /dev/ACM0 -b nrf53 -l 192.168.2.1 -i 192.168.2.2 -c BAP/BSRC/STR/BV-09-C
where -l is the IP of Linux host and -i is the IP of Windows guest on virtual machine.
Don't hesitate to ask questions under AutoPTS issues or you can reach me on discord, as the first launch can be troublesome.
@cvinayak https://github.com/zephyrproject-rtos/zephyr/pull/67210 adds testing of all audio configurations and low latency presets from the BAP spec. Quite a lot of them are not passing (see the commented out tests).
This does not include the high reliability tests (yet).
@cvinayak #67210 adds testing of all audio configurations and low latency presets from the BAP spec. Quite a lot of them are not passing (see the commented out tests).
This does not include the high reliability tests (yet).
Work in progress addressing failures in #67210 is here: https://github.com/zephyrproject-rtos/zephyr/pull/67392
@mkasenberg Thank you for your instructions, I will switch to reproducing the issues once I get to fix controller for the test in #67210
@mkasenberg is it possible to run the failing PTS tests on a controller on this branch (before I get to setup my PTS)? https://github.com/zephyrproject-rtos/zephyr/pull/67392
Yes, let's try if autopts bot is still operative.
@mkasenberg Looks like PR run has failed, is the failures same as original failures or any improvements seen in the controller fro the PR?
I saw the bot logs and the patch works great, controller has successfully accepted the config settings. The autopts cron has reported fails, because an MMI handler in autopts has a bug and does not send anything, the fix is not merged yet https://github.com/auto-pts/auto-pts/pull/1067/commits/f1453575017757489ef8250dc57a3ca0c95b5181#diff-fc44e218eeb03508ffb17b3eda2ca77928b173334fe43d2c55ff23df09b09e46R315-R323
thank you, added fixes comment for this gh issue in the Pr #67392 .... we can re-open this issue if there are problem when fixes are merged into main.
Describe the bug Not high prio, posting just for the record:
Zephyr controller rejects the LE Create BIG if the fallowing config settings are used:
When the Zephyr controller is built with
CONFIG_BT_CTLR_CONN_ISO_LOW_LATENCY_POLICY=n
the LE Create BIG succeed, but only for the 441_1 setting. Even then the PTS device is not able to synchronize to the broadcast.To Reproduce With the AutoPTS and nRF5340 board.
Expected behavior Zephyr controller accepts each of the mentioned config settings.
Impact Affected PTS test cases: BAP/BSRC/STR/BV-09-C BAP/BSRC/STR/BV-10-C BAP/BSRC/STR/BV-26-C BAP/BSRC/STR/BV-27-C BAP/BSRC/STR/BV-28-C BAP/BSRC/STR/BV-29-C BAP/BSRC/STR/BV-30-C BAP/BSRC/STR/BV-31-C BAP/BSRC/STR/BV-32-C BAP/BSRC/STR/BV-33-C
Logs and console output
Environment
Additional context @cvinayak