TMAP peripheral sample not advertising after flashing on nrf5340-Audio DK board

[pal_722]

Hi, 

I am new to nrf and have started working with nrf5340 audio dk board. I am using VS Code for programming and the SDK version used is v2.6.1.

I tested the board with blinky sample and it works fine.

I then started with TMAP peripheral code, as my application or use case in based on BLE audio transfer.
I was able to build and flash the code, but the board is not advertising and throws the below shown error.

In the build configuration, I selected nrf5340_audio_dk_anrf5340_cpuapp and chose prj.conf as configuration.

I did follow few threads in the forum, but see no difference. 
Could you please help me solve this issue?

[Maria Gilje]

Hello,

The nRF5340 Audio DK is a complex starting point when you are new to Nordic products. I recommend that you start with the nRF5340 DK instead and get to know nRF Connect SDK by going through the nRF Connect SDK Fundamentals course. After that, the Bluetooth Low Energy fundamentals course gives a great insight into our Bluetooth Low Energy solutions.

For LE Audio, we have the nRF5340 Audio applications which are applications specifically made for the nRF5340 Audio DK. When starting with the application you start with a functioning LE Audio device. Note that the applications have the experimental tag in the latest release which means they are not production ready as is and needs to be thoroughly tested before moving to certification.

Your specific error is ENOTSUP, that is: the controller does not support the requested feature. I suspect that this is because the SoftDevice Controller only supports ISO for multirole devices. See the full list of supported features for the SoftDevice Controller here: https://docs.nordicsemi.com/bundle/ncs-latest/page/nrfxlib/softdevice_controller/README.html.

Let me know if you need more assistance with finding the correct Kconfig symbols to enable the needed features in the SoftDevice Controller.

I do still recommend that you get to know nRF Connect SDK in general by going through the DevAcademy courses linked above if you haven't already.

Best regards,

Maria

[pal_722]

Hi 

Maria Gilje said:

The nRF5340 Audio DK is a complex starting point when you are new to Nordic products. I recommend that you start with the nRF5340 DK instead and get to know nRF Connect SDK by going through the nRF Connect SDK Fundamentals course. After that, the Bluetooth Low Energy fundamentals course gives a great insight into our Bluetooth Low Energy solutions.

I have worked with BLE Audio using other controller(STM), and am aware of the technicalities. I’m a bit swamped with deliverables at the moment, so I won’t be able to explore the boards just yet.

Maria Gilje said:

For LE Audio, we have the nRF5340 Audio applications which are applications specifically made for the nRF5340 Audio DK. When starting with the application you start with a functioning LE Audio device. Note that the applications have the experimental tag in the latest release which means they are not production ready as is and needs to be thoroughly tested before moving to certification.

I did work with nrf5340_audio sample. The device got successfully connected with my mobile, but when I streamed audio, the below errors were displayed

Maria Gilje said:

Let me know if you need more assistance with finding the correct Kconfig symbols to enable the needed features in the SoftDevice Controller.

I’d love for the board to function like an earphone, allowing me to stream audio and make calls from my phone. From what I understand, the TMAP profile would be perfect for this application.

Could you please assist me with this?

Maria Gilje said:

I do still recommend that you get to know nRF Connect SDK in general by going through the DevAcademy courses linked above if you haven't already.

I’ll try to work on this concurrently.

Hi Maria Gilje 

I have some update regarding TMAP example, I added child image folder to the TMAP folder, built the code and reflashed my board. This is what I get

The ISO error still persists.

The device advertises, and I am able to connect to my mobile. But I am unable to control volume and stream audio.

Can you please help me with this? does it have something to do with Kconfig symbols?

Thank you

Regards