Use jack input with BLE audio

RE: Use jack input with BLE audio

Karl Ylvisaker — Wed, 24 Jan 2024 14:07:11 GMT

Oh, I just saw your latest update.
Thank you for letting me know! :)

I am glad to read that you were able to resolve the issue, and that it now works as intended! :)

Please do not hesitate to open another ticket if you should encounter any other issues or questions in the future.

Best regards,
Karl

RE: Use jack input with BLE audio

Karl Ylvisaker — Wed, 24 Jan 2024 14:05:53 GMT

Thank you for providing the log, this is very helpful.
Everything looks as it should from here, and so I think the issue could be with the playback itself.

Does the 'steam pause' and 'stream started' events show up as expected in your headphones log when you press the play/pause button?

Please also keep in mind that the audio jack on the nRF5340 Audio DK only outputs on the Left channel (since the onboard cirrus logic hardware codec is a single-channel codec), and so if you are using wired earbuds for your testing you will only hear the music in the left earbud.
There is no technical limitation on the nRF5340 on outputting stereo, but you will then need to use an external stereo codec instead of the onboard one, following these steps:

Best regards,
Karl

RE: Use jack input with BLE audio

JJ_N — Wed, 24 Jan 2024 13:31:20 GMT

I have found the issue, it's my mistake, I used the wrong configuration file.

Thank you for your support

Regards

RE: Use jack input with BLE audio

JJ_N — Wed, 24 Jan 2024 09:22:23 GMT

Find below the gateway logfile after few minutes :

*** Booting nRF Connect SDK v2.5.1 ***
GW [00:00:00.259,063] <inf> fw_info:
         nRF5340 Audio nRF5340 Audio DK cpuapp
         NCS base version: 2.5.1
         Cmake run : Mon Jan 22 16:05:28 2024
GW [00:00:00.259,063] <inf> fw_info: ------- DEBUG BUILD -------
GW [00:00:00.259,094] <inf> fw_info: Compiled for GATEWAY device
GW [00:00:00.269,714] <inf> board_version: Compatible board/HW version found: 1.0.0
GW [00:00:00.316,131] <inf> bt_mgmt_ctlr_cfg: Controller: LL_ACS_NRF53. Version: 3424
GW [00:00:00.318,023] <inf> bt_mgmt: Local identity addr: ED:6F:1C:80:E2:B6 (random)
GW [00:00:00.319,702] <inf> bt_mgmt_scan: All bonded slots filled, will not accept new devices
GW [00:00:00.443,786] <inf> bt_mgmt_scan: Local addr: 74:F9:57:35:64:F9 (random). May time out. Updates not printed
GW [00:00:00.443,817] <inf> bt_mgmt_scan: Scanning successfully started
GW [00:00:01.014,495] <inf> bt_mgmt_scan: Creating connection to bonded device: F5:9D:9A:9D:D0:DA (random)
GW [00:00:01.112,213] <inf> bt_mgmt: Connected: F5:9D:9A:9D:D0:DA (random)
GW [00:00:01.112,335] <inf> bt_mgmt_scan: All bonded slots filled, will not accept new devices
GW [00:00:01.123,016] <inf> bt_mgmt_scan: Local addr: 62:4A:8B:5E:D9:90 (random). May time out. Updates not printed
GW [00:00:01.123,016] <inf> bt_mgmt_scan: Scanning successfully started
GW [00:00:01.123,291] <inf> streamctrl_unicast_client: Device connected
GW [00:00:01.297,790] <inf> streamctrl_unicast_client: Security changed
GW [00:00:01.697,998] <inf> bt_rend_vol: VCS discover finished
GW [00:00:03.099,243] <inf> unicast_client: LEFT sink stream configured
GW [00:00:03.139,801] <inf> unicast_client: Enable stream 0x20002c60
GW [00:00:03.578,063] <inf> unicast_client: Stream 0x20002c60 started

RE: Use jack input with BLE audio

Karl Ylvisaker — Wed, 24 Jan 2024 09:14:00 GMT

Hello,

Thanks for providing the logs. It seems that the gateway log is quite short, compared to the headset one. The gateway one seems to stop at the scanning, so we dont see anything of the connection itself.
Could you let it run for a couple of minutes, and share these logs? I just want to see if any clues could show up in the logs.
You can use the Insert->Code or Insert->File to share the logs here on DevZone.

Best regards,
Karl

RE: Use jack input with BLE audio

JJ_N — Wed, 24 Jan 2024 08:33:20 GMT

Hello,

Thank you for your reply.

Log from headset :

*** Booting nRF Connect SDK v2.5.1 ***
HR [00:00:00.256,652] <inf> fw_info:
nRF5340 Audio nRF5340 Audio DK cpuapp
NCS base version: 2.5.1
Cmake run : Mon Jan 22 16:03:30 2024
HR [00:00:00.256,652] <inf> fw_info: ------- DEBUG BUILD -------
HR [00:00:00.256,652] <inf> fw_info: HEADSET right device
HR [00:00:00.267,303] <inf> board_version: Compatible board/HW version found: 1. 0.0
HR [00:00:00.311,737] <inf> bt_mgmt_ctlr_cfg: Controller: LL_ACS_NRF53. Version: 3424
HR [00:00:00.313,690] <inf> bt_mgmt: Local identity addr: EC:87:8B:30:DD:2A (ran dom)
HR [00:00:00.345,703] <inf> bt_mgmt_adv: Local addr: 7C:67:FB:67:67:45 (random)
HR [00:00:00.345,794] <inf> bt_mgmt_adv: Adv directed to: ED:6F:1C:80:E2:B6 (ran dom).
HR [00:00:00.346,649] <inf> bt_mgmt_adv: Advertising successfully started
HR [00:00:00.990,234] <inf> bt_mgmt: Connected: ED:6F:1C:80:E2:B6 (random)
HR [00:00:00.990,478] <inf> streamctrl_unicast_server: Connected
HR [00:00:01.150,451] <inf> streamctrl_unicast_server: Security changed
HR [00:00:01.150,634] <wrn> bt_gatt: Device is not subscribed to characteristic
HR [00:00:02.590,972] <inf> bt_content_ctrl_media: Discovery of MCS finished
HR [00:00:02.671,173] <inf> unicast_server: LC3 codec config for sink:
HR [00:00:02.671,173] <inf> unicast_server: Frequency: 48000 Hz
HR [00:00:02.671,173] <inf> unicast_server: Frame Duration: 10000 us
HR [00:00:02.671,203] <inf> unicast_server: Channel allocation: 0x2
HR [00:00:02.671,203] <inf> unicast_server: Octets per frame: 120 (96000 bps )
HR [00:00:02.671,203] <inf> unicast_server: Frames per SDU: 1
HR [00:00:02.751,037] <inf> streamctrl_unicast_server: Presentation delay 10000 us is set by initiator
HR [00:00:03.197,784] <inf> unicast_server: Stream 0x2000d810 started
HR [00:00:08.208,160] <wrn> audio_datapath: In I2S TX underrun condition, total: 5000
H

Log from gateway :

*** Booting nRF Connect SDK v2.5.1 ***
GW [00:00:00.259,185] <inf> fw_info:
nRF5340 Audio nRF5340 Audio DK cpuapp
NCS base version: 2.5.1
Cmake run : Mon Jan 22 16:05:28 2024
GW [00:00:00.259,185] <inf> fw_info: ------- DEBUG BUILD -------
GW [00:00:00.259,185] <inf> fw_info: Compiled for GATEWAY device
GW [00:00:00.269,836] <inf> board_version: Compatible board/HW version found: 1. 0.0
GW [00:00:00.315,979] <inf> bt_mgmt_ctlr_cfg: Controller: LL_ACS_NRF53. Version: 3424
GW [00:00:00.317,932] <inf> bt_mgmt: Local identity addr: ED:6F:1C:80:E2:B6 (ran dom)
GW [00:00:00.319,549] <inf> bt_mgmt_scan: All bonded slots filled, will not acce pt new devices
GW [00:00:00.443,237] <inf> bt_mgmt_scan: Local addr: 69:38:07:03:A1:96 (random) . May time out. Updates not printed
GW [00:00:00.443,267] <inf> bt_mgmt_scan: Scanning successfully started

Regards

RE: Use jack input with BLE audio

Karl Ylvisaker — Wed, 24 Jan 2024 07:45:30 GMT

Hello,

Thank you for clarifying about the LED and the verification of the audio source.
Please make sure that your laptop has selected the nRF5340 Audio as its audio output, and that the audio volume is turned up on the laptop side.

These logs are from the nRF Connect application, not the Gateway and Headset devices themselves.

[quote user="JJ_N"]I will check how to grab log in order to share them with you.[/quote]

You can use a serial monitor like PuTTy, or the nRF Terminal in the Visual Studio Code nRF Connect extensions.
Please share the logs from the gateway and headset devices so that I may take a look to see what may be going wrong here.

Best regards,
Karl

RE: Use jack input with BLE audio

JJ_N — Tue, 23 Jan 2024 10:48:50 GMT

devzone.nordicsemi.com/.../Headset-2024_2D00_01_2D00_23T10_5F00_51_5F00_21.278Z_2D00_log.txt devzone.nordicsemi.com/.../Gateway-2024_2D00_01_2D00_23T10_5F00_51_5F00_21.278Z_2D00_log.txt

There is no sound on the headset device.

I use a laptop for the audio source and I have checked with a headphone that the output is working.

The blue LED are blinking (on the gateway and also on the headset)

I will check how to grab log in order to share them with you.

RE: Use jack input with BLE audio

Karl Ylvisaker — Tue, 23 Jan 2024 10:24:00 GMT

Hello,

What do you mean when you say that it is not working? Does the application do anything unexpected, or is it just that no sound is played on the headset device?
Could you share the log from the gateway and headset device when you run this?
Could you also elaborate on what you are using as the audio source (what is the jack connected to), and whether you have verified that the audio is being output by the source as expected?

Best regards,
Karl