nRF5340_Audio

Hello LE-Audio team,

By any chance, do you have a working code base that supports a headset with 2 end points instead of just one as your sample nRF5340_Audio kit?

If yes, will you please let me know how I can get it?

If not, what do I have to do to change the current nRF5340_Audio project to support a real two channel headset?

Thank you.

Min 

  • Yes, gateway code that supports TWS is the objective.

    Need your team's help so the code base will be able to deal with the following case properly:

    1. GW [00:00:14.345,642] <inf> unicast_client: Discovered 2 source/sink endpoint(s) for device 0 instead of just 1

    So this will not happen:

    ...

    GW [00:00:05.849,029] <dbg> bt_bap_unicast_client: unicast_client_ep_subscribe: ep 0x200059e4 handle 0x62
    GW [00:00:05.849,090] <wrn> unicast_client: More than one sink endpoint found, idx 0 is used by default
    GW [00:00:05.849,090] <dbg> bt_bap_unicast_client: unicast_client_ase_discover: conn 0x20004f08
    GW [00:00:06.050,079] <dbg> bt_bap_unicast_client: unicast_client_ase_discover_cb: conn 0x20004f08 attr 0x2001f74c handle 0x0065 dir sink
    GW [00:00:06.248,931] <dbg> bt_bap_unicast_client: unicast_client_ase_read_func: conn 0x20004f08 err 0x00 len 2
    GW [00:00:06.248,931] <dbg> bt_bap_unicast_client: unicast_client_ase_read_func: handle 0x0065
    GW [00:00:06.248,962] <dbg> bt_bap_unicast_client: unicast_client_ase_read_func: conn 0x20004f08 err 0x00 len 0
    GW [00:00:06.248,962] <dbg> bt_bap_unicast_client: unicast_client_ase_read_func: handle 0x0065
    GW [00:00:06.248,962] <wrn>bt_bap_unicast_client: No space left to parse ASE
    GW [00:00:06.248,962] <err> unicast_client: Discovery failed: -12 

    ...

    The goal is to make the connection and enable the streams.

    Can we do that?

    Thanks.

    Min

  • Hi Min,

    Could you try adding CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SNK_COUNT=20 CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SRC_COUNT=20.?

    Our gateway already supports TWS stereo. Please also let us know which TWS you are working with.

    Regards,

    Swathy

  • Hi Swathy,

    I moved past this, now the issue is as follows:

    GW [00:00:15.574,920] <wrn> bt_hci_core: opcode 0x2062 status 0x07
    GW [00:00:15.574,920] <wrn> bt_iso: Unexpected response to hci_le_set_cig_params
    GW [00:00:15.574,951] <err> bt_bap_unicast_client: bt_iso_cig_create failed: -5
    GW [00:00:15.574,981] <err> unicast_client: Failed to create unicast group: -5
    GW [00:00:15.574,981] <err> unicast_client: Failed to start unicast sink audio: -22

    The root cause is:

    GW [00:00:15.574,920] <wrn> bt_hci_core: opcode 0x2062 status 0x07

    status 0x07 is: #define BT_HCI_ERR_MEM_CAPACITY_EXCEEDED        0x07

    Therefore, I am out of memory for HCI.

    Please help me as how to increase the memory used by HCI. Which memory allocation do I need to increase and in which config file?

    Could you try adding CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SNK_COUNT=20 CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SRC_COUNT=20.?

    If I set to those numbers above, my memory problem is more severe.

    Options I expect:

    1. have do increase the HCI memory, but I don't know how exactly if this is the cause.

    2. do you have a release pull just for this TWS 3rd party earbuds with all the correct settings for NCS3.0.2?

    Thanks.

    Min

    PS. Below is the detailed log for your reference:

    ...

    GW [00:00:14.378,173] <wrn> bt_hci_core: ml: opcode 0x2062 status 0x07

    GW [00:00:14.378,173] <wrn> bt_iso: 1: Unexpected response to hci_le_set_cig_params
    GW [00:00:14.378,204] <err> bt_bap_unicast_client: bt_iso_cig_create failed: -5
    GW [00:00:14.378,204] <dbg> bt_bap_unicast_client: bt_bap_unicast_group_create: bt_audio_cig_create failed: -5
    GW [00:00:14.378,204] <err> unicast_client: Failed to create unicast group: -5
    GW [00:00:14.378,234] <err> unicast_client: Failed to start unicast sink audio: -22

    ...

  • Hi Min,

    Could you please provide the full log.? The "memory capacity exceeded error" doesn't mean the HCI memory, might related with the wrong configuration setting which controller cannot handle. Also include the following:

    CONFIG_UNICAST_CLIENT_LOG_LEVEL_DBG=y
    CONFIG_BT_BAP_UNICAST_CLIENT_LOG_LEVEL_DBG=y
    CONFIG_BT_AUDIO_EP_PRINT=y

    Providing a log like shown below would be helpful:

    Best Regards,

    Swathy

  • Also,

    Please let us know which TWS earbuds you are testing this with.. Our team has tested with a few TWS earbuds with nRF Connect SDK v3.0.2 and that seems to work.

    Regards,

    Swathy

Related