Configuring nRF5340 Audio uincast client in nRF5340 DK

[Sivakumar128]

Hi,

I try to develop a Bluetooth speaker using the nRF 5340 DK since i do not have a separate audio Dk for this. I am using the sample code Audio unicast client for this . I have downloaded the sample code and build the code , no errors are found . But when i flash the code to the nRF 5340 DK and tried to connect it with my mobile, the device is not visible in the device list.  i also used the nRF connect application to connect the device but failed. i would like to know what are the changes made to the audio unicast client to make Bluetooth visible to all the devices. 
 

[AHaug]

Hi,

The nRF Audio sample has some requirements which you can see here https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/applications/nrf5340_audio/doc/requirements.html. LE Audio is not supported on the nRF5340DK, and you need the Audio DK or a custom board with the nRF5340 that has the same features as the audio DK.

But when i flash the code to the nRF 5340 DK and tried to connect it with my mobile, the device is not visible in the device list.

How did you build it? I.e for what build target? The device is most likely not visible since it is not advertising because it never started. Could you check the device logs and see if the firmware is running?

Kind regards,
Andreas

[Sivakumar128]

Hi,
I have changed from unicast client to unicast server since my objective is to use the nRF5340 DK as a headset/Speaker. Keeping the nRF5340 as a server and the mobile as a client. I have used the same sample mentioned for the Audio DK. I have build the Application using the VS code . After Flashing it to the Development Kit and I try to connect it with the mobile phone. The devices get paired but not remains in a connected state , But i want the device should be connected till the end of my audio plays. I have taken a log and find out that [00:05:46.677,642] <wrn> bt_att: Unhandled ATT code 0x1d . Whenever i try to connect with the nRF connect App, After connecting the log is look like this. Here by attaching the log

*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
[00:00:00.474,548] <inf> bt_hci_core: HW Platform: Nordic Semiconductor (0x0002)
[00:00:00.474,578] <inf> bt_hci_core: HW Variant: nRF53x (0x0003)
[00:00:00.474,609] <inf> bt_hci_core: Firmware: Standard Bluetooth controller (0x00) Version 3.7 Build 99
[00:00:00.476,776] <inf> bt_hci_core: Identity: E7:2F:C3:16:F1:5F (random)
[00:00:00.476,806] <inf> bt_hci_core: HCI: version 5.4 (0x0d) revision 0x0000, manufacturer 0x0059
[00:00:00.476,837] <inf> bt_hci_core: LMP: version 5.4 (0x0d) subver 0xffff
Bluetooth initialized
Location successfully set
Supported contexts successfully set
Available contexts successfully set
Advertising successfully started
Connected: 57:B8:4E:9C:49:8B (random)
[00:00:08.251,495] <wrn> bt_att: Unhandled ATT code 0x1d
Disconnected: 57:B8:4E:9C:49:8B (random), reason 0x13
Advertising successfully started
Connected: 78:AC:37:D3:14:AE (random)
[00:00:55.101,013] <wrn> bt_att: Unhandled ATT code 0x1d
Disconnected: 78:AC:37:D3:14:AE (random), reason 0x13
Advertising successfully started
Connected: 78:AC:37:D3:14:AE (random)
[00:05:46.677,642] <wrn> bt_att: Unhandled ATT code 0x1d

[AHaug]

DK as a gateway should be possible if you're using USB as the audiosource, but there are no support for headset. You will also not be able to get any audio out without adding extra phsyical components. The rest of the project should be possible to do, but I'm fairly limited w.r.t being able to give you more support that what is mentioned in the documentation.

I recommend you to also have a look at the zephyr LE Audio samples, since they support the nRF5340DK (for instance bap_unicast server)

Kind regards,
Andreas