nRF5340_Audio

[Min]

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 

[SwRa]

Hi Min,

Could you let us know if you would like to use the nRf5340 as unicast client to connect with stereo tethering headset, or TWS earbuds.?

Regards,

Swathy

[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