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

Creating the unicast group before both ISO connections have been configured might cause issue #45374

Closed
rick1082 opened this issue May 5, 2022 · 1 comment · Fixed by #46168
Assignees
Labels
area: Bluetooth Audio area: Bluetooth bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@rick1082
Copy link
Collaborator

rick1082 commented May 5, 2022

Describe the bug
I try to modify the unicast_audio_client and unicast_audio_server for creating TWS scenario demo (one client connects to two servers).
And if the unicast group is created before both ISO connections have been configured, then the CIG creating parameter will be wrong.

I'm using controller from here with the application in https://github.com/rick1082/zephyr/tree/multilink_audio

And running the on nRF5340-DK.

To Reproduce
Steps to reproduce the behavior:

  1. Checkout the unicast_audio_client from above branch and program to one nRF5340-DK as client
  2. Checkout the unicast_audio_server from above branch, and program to nRF5340-DK as left headset server
  3. Checkout the unicast_audio_server from above branch, remove following line and program to nRF5340-DK as right headset server
    https://github.com/rick1082/zephyr/blob/multilink_audio/samples/bluetooth/unicast_audio_server/src/main.c#L60
  4. Program all the DKs with ble5-ctr-rpmsg_3247.hex on the network core
  5. Turn on both of servers, and then turn on the client
  6. Then we see the client shows following log

[00:00:10.104,827] bt_hci_core: opcode 0x2064 status 0x0c
[00:00:10.104,858] bt_iso: bt_iso_chan_connect: Failed to connect CISes: -5
[00:00:10.104,858] bt_unicast_client: bt_audio_stream_connect: -5

  1. And in the HCI traffic log, it shows following log indicated the CIG only created with one CIS

< HCI Command: LE Set Connected I.. (0x08|0x0062) plen 24 #185 [hci0] 5.555816
CIG ID: 0x00
Master to Slave SDU Interval: 10000 us (0x002710)
Slave to Master SDU Interval: 10000 us (0x002710)
SCA: 201 - 500 ppm (0x00)
Packing: Sequential (0x00)
Framing: Unframed (0x00)
Master to Slave Maximum Latency: 10 ms (0x000a)
Slave to Master Maximum Latency: 10 ms (0x000a)
Number of CIS: 1
CIS ID: 0x00
Master to Slave Maximum SDU Size: 40
Slave to Master Maximum SDU Size: 0
Master to Slave PHY: LE 2M (0x02)
Slave to Master PHY: LE 2M (0x02)
Master to Slave Retransmission attempts: 0x02
Slave to Master Retransmission attempts: 0x00
HCI Event: Command Complete (0x0e) plen 8 #186 [hci0] 5.559716
LE Set Connected Isochronous Group Parameters (0x08|0x0062) ncmd 1
Status: Success (0x00)
CIG ID: 0x00
Number of Handles: 1
Connection Handle: 2

Expected behavior
The bt_audio API should work for creating the unicast group before both ISO connections been configured.

Logs and console output
The btmon format HCI log from client as following:
client_hci.log
The application log from client as following
client_application.log

@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

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

Successfully merging a pull request may close this issue.

3 participants