Could not create unicast group (err -134)

RE: Could not create unicast group (err -134)

Maria Gilje — Thu, 23 Feb 2023 15:49:07 GMT

Hello again,

I have not been able to completely resolve this. But I will share the progress I had.

I modified the Unicast Audio Client and Unicast Audio Server directories by doing the following.

This configuration was added to <ncs-installation>/zephyr/samples/bluetooth/unicast_audio_server/child_image/hci_rpmsg.conf:

CONFIG_IPC_SERVICE=y
CONFIG_MBOX=y

CONFIG_HEAP_MEM_POOL_SIZE=8192

CONFIG_MAIN_STACK_SIZE=512
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=512

CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_HCI_RAW_RESERVE=1

CONFIG_BT_CTLR_ASSERT_HANDLER=y

# Workaround: Unable to allocate command buffer when using K_NO_WAIT since
# Host number of completed commands does not follow normal flow control.
CONFIG_BT_BUF_CMD_TX_COUNT=10

CONFIG_BT_BROADCASTER=n
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_OBSERVER=n
CONFIG_BT_CENTRAL=n
CONFIG_BT_EXT_ADV=y
CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_PER_ADV=y
CONFIG_BT_ISO_BROADCASTER=y
CONFIG_BT_ISO_MAX_CHAN=2

# ISO Broadcast Controller
CONFIG_BT_LL_SW_SPLIT=y
CONFIG_BT_CTLR_ADV_PERIODIC=y
CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=191
CONFIG_BT_CTLR_ADV_ISO=y
CONFIG_BT_CTLR_ADV_ISO_PDU_LEN_MAX=251
CONFIG_BT_CTLR_ISO_TX_BUFFERS=16
CONFIG_BT_CTLR_ISO_TX_BUFFER_SIZE=251
CONFIG_BT_CTLR_ADV_ISO_STREAM_MAX=2

This configuration was added to <ncs-installation>/zephyr/samples/bluetooth/unicast_audio_client/child_image/hci_rpmsg.conf:

CONFIG_IPC_SERVICE=y
CONFIG_MBOX=y

CONFIG_HEAP_MEM_POOL_SIZE=8192

CONFIG_MAIN_STACK_SIZE=512
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=512

CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_HCI_RAW_RESERVE=1

CONFIG_BT_CTLR_ASSERT_HANDLER=y

# Workaround: Unable to allocate command buffer when using K_NO_WAIT since
# Host number of completed commands does not follow normal flow control.
CONFIG_BT_BUF_CMD_TX_COUNT=10

CONFIG_BT_BROADCASTER=n
CONFIG_BT_PERIPHERAL=n
CONFIG_BT_OBSERVER=n
CONFIG_BT_CENTRAL=y
CONFIG_BT_EXT_ADV=y
CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_PER_ADV_SYNC=y
CONFIG_BT_ISO_SYNC_RECEIVER=y
CONFIG_BT_ISO_MAX_CHAN=2

# ISO Receive Controller
CONFIG_BT_LL_SW_SPLIT=y
CONFIG_BT_CTLR_SYNC_PERIODIC=y
CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX=191
CONFIG_BT_CTLR_SYNC_ISO=y
CONFIG_BT_CTLR_SYNC_ISO_PDU_LEN_MAX=251
CONFIG_BT_CTLR_SYNC_ISO_STREAM_MAX=2
CONFIG_BT_CTLR_ISOAL_SINKS=2

This resolved the "Failed to set advertising data (err -5)" error. Unfortunately it resulted in another error: BT_HCI_ERR_UNKNOWN_CONN_ID, which occurs when the client attempts to connect to the server.

To get further help with this I advise you to contact the Zephyr Project on Discord. The reason for this being that the samples and the controller was all created by Zephyr.

Best Regards,
Maria

RE: Could not create unicast group (err -134)

Maria Gilje — Wed, 15 Feb 2023 07:30:19 GMT

Hello,

I am very sorry for taking so long to get back to you.

Have you been able to solve your issue while you were waiting?

I will strive to give you a further response within end of day.

Best Regards,
Maria

RE: Could not create unicast group (err -134)

Maria Gilje — Fri, 03 Feb 2023 14:49:59 GMT

Hello,

Sorry for the delay.

I have reproduced your issue, but I need to do some more tests to figure out why this fails. Thank you for your patience.

Best Regards,
Maria

RE: Could not create unicast group (err -134)

mul — Tue, 31 Jan 2023 13:47:41 GMT

Maria Gilje Thanks for your reply. However, there is still an issue. The server fails to set advertising data. Here is my output

*** Booting Zephyr OS build v3.2.99-ncs1-1547-ge2bec540218d ***
[00:00:00.395,599] <inf> bt_hci_core: hci_vs_init: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.395,660] <inf> bt_hci_core: hci_vs_init: HW Variant: nRF53x (0x0003)
[00:00:00.395,690] <inf> bt_hci_core: hci_vs_init: Firmware: Standard Bluetooth controller (0x00) Version 3.2 Build 99
[00:00:00.397,796] <inf> bt_hci_core: bt_dev_show_info: Identity: E6:15:13:0B:35:CD (random)
[00:00:00.397,827] <inf> bt_hci_core: bt_dev_show_info: HCI: version 5.3 (0x0c) revision 0x0000, manufacturer 0x05f1
[00:00:00.397,857] <inf> bt_hci_core: bt_dev_show_info: LMP: version 5.3 (0x0c) subver 0xffff
Bluetooth initialized
Location successfully set
Available contexts successfully set
[00:00:00.399,291] <wrn> bt_hci_core: bt_hci_cmd_send_sync: opcode 0x2037 status 0x0c
Failed to set advertising data (err -5)

RE: Could not create unicast group (err -134)

Maria Gilje — Tue, 31 Jan 2023 10:43:48 GMT

Ok. If you don't have nRF Connect SDK (NCS) installed, please follow these instructions to install it.

Then you can find unicast_server and unicast_client located at <ncs-installation>/zephyr/samples/bluetooth. Include CONFIG_BT_LL_SW_SPLIT to the prj.conf for both samples as Karl described and build the modified sample.

Regards,
Maria

RE: Could not create unicast group (err -134)

mul — Mon, 30 Jan 2023 08:00:23 GMT

Maria Gilje I am using the Zephyr from the examples from here: github.com/.../bluetooth

RE: Could not create unicast group (err -134)

Maria Gilje — Fri, 27 Jan 2023 14:29:04 GMT

Hello,

I am taking over this case from Karl. I can look closer into it over the weekend, but I have some initial thoughts.

I can see that you are linking to both Zephyr and NCS documentation, and I want to clear up which SDK you are using.

Are you using Zephyr from Zephyr Project or the Zephyr samples from nRF Connect SDK? NCS uses a downstream version of Zephyr, and the different version could be a factor for your error.

Kind Regards,
Maria

RE: Could not create unicast group (err -134)

mul — Tue, 24 Jan 2023 14:34:00 GMT

Hi Karl Ylvisaker

When I add CONFIG_BT_LL_SW_SPLIT=y to the proj.conf of the hci_rpmsg sample and flash the network core with it, then the server can't even create an advertising set. With this disabled, it can create an advertising set, but then the client is unable to create a unicast group.

*** Booting Zephyr OS build v3.2.99-ncs1 ***
Bluetooth initialized
Location successfully set
Available contexts successfully set
Failed to create advertising set (err -5)

RE: Could not create unicast group (err -134)

Karl Ylvisaker — Mon, 23 Jan 2023 08:31:45 GMT

Hello,

By default the NCS SDK samples will use the SoftDevice Controller, unless you have the CONFIG_BT_LL_SW_SPLIT config in your prj.config file.
I dont see this in your shared prj.conf file, so I would assume that you are also using the SoftDevice Controller.
Please try to add the CONFIG_BT_LL_SW_SPLIT config to switch to the Zephyr LL Controller, and see if this issue persists.

Best regards,
Karl

RE: Could not create unicast group (err -134)

mul — Thu, 19 Jan 2023 16:30:55 GMT

Karl Ylvisaker Thanks for your reply. I am using the Zephyr controller ( I believe ). I build the following sample and flash it to the network core.

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/samples/bluetooth/hci_rpmsg/README.html

My proj.conf for the hci_rpmsg sample is as follows :

CONFIG_IPC_SERVICE=y
CONFIG_MBOX=y

CONFIG_HEAP_MEM_POOL_SIZE=8192

CONFIG_MAIN_STACK_SIZE=512
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=512

CONFIG_BT=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_HCI_RAW_RESERVE=1
CONFIG_BT_MAX_CONN=16

CONFIG_BT_CTLR_ASSERT_HANDLER=y

# Workaround: Unable to allocate command buffer when using K_NO_WAIT since
# Host number of completed commands does not follow normal flow control.
CONFIG_BT_BUF_CMD_TX_COUNT=10

CONFIG_BT_EXT_ADV=y
CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_PER_ADV=y

RE: Could not create unicast group (err -134)

Karl Ylvisaker — Thu, 19 Jan 2023 15:11:44 GMT

Hello,

Which controller are you using, the Zephyr Controller or the SoftDevice controller?

The SoftDevice controller does not support ISO channels, so you will have to use the Zephyr controller to test these samples. The -134 error code means Unsupported Value, and would be returned if you were using the SoftDevice controller, for instance.

Best regards,
Karl