• State Verified Answer
  • Replies 5 replies
  • Subscribers 66 subscribers
  • Views 1533 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 300365
Options

Building nRF5340_audio example for nRF5340-DK (not NRF5340-AUDIO-DK)

hakved_vea

Hi,

is it possible to build the nRF5340_audio application for the nRF5340-DK?

What I'm currently is investigating is the possibility of finding and connecting to other LE Audio equiment (supports the new 5.2 spesifications).

In this stage it is not that important to transfer audio, but only establish the connection.

I just want to scan for devices and find the other equiment, maybe another example is more suitable for my preliminary case?

BR,

Håkon

Parents
  • 0

    I have ordered some nRF5340-Audio-DK kits, however my main goal still stand as I want to connect a nRF5340-Audio-DK in receiver mode to a 3rd party transmitter.

    So my question, a little more refined is:

    Is there a standard way of pairing a transmitter and a receiver and does the nRF5340_audio application support this?

    Thanks in advance for any help on this,

    Håkon

  • 0 in reply to hakved_vea

    Hello Håkon,

    Apologies for the delay.

    is it possible to build the nRF5340_audio application for the nRF5340-DK?

    The nRF5340 Audio application is made specifically for the nRF5340 Audio DK, and you would need equivalent hardware for it to work on another board without making changes to the application.

    I just want to scan for devices and find the other equiment, maybe another example is more suitable for my preliminary case?

    Yes, you can use the zephyr samples Unicast Audio Server and Unicast Audio Client to test scanning and connecting.

    hakved_vea said:
    Is there a standard way of pairing a transmitter and a receiver and does the nRF5340_audio application support this?

    For the current state of the nRF5340 Audio application in Connected Isochronous Stream (CIS) mode, once a headset device and a gateway device has been connected once, they are bonded, and will connect to each other on every subsequent restart.

    Regards,
    Maria

  • 0 in reply to Maria Gilje

    Hi Maria,

    That's okay, thanks for your reply Slight smile

    I received my nRF5340 Audio DK boards today, so I have played around with the examples.

    However, neither of the applications, Unicast Audio Server, Unicast Audio Client or the nRF5340_audio was able to stream data to the other LE Audio equipment, or receive from a broadcast stream.

    At this point, are most of the Auracast equipment proprietary in the way they establish the connection? is there any specification on how devices from different vendors should connect to each other? 

    Regards,

    Håkon

Reply
  • 0 in reply to Maria Gilje

    Hi Maria,

    That's okay, thanks for your reply Slight smile

    I received my nRF5340 Audio DK boards today, so I have played around with the examples.

    However, neither of the applications, Unicast Audio Server, Unicast Audio Client or the nRF5340_audio was able to stream data to the other LE Audio equipment, or receive from a broadcast stream.

    At this point, are most of the Auracast equipment proprietary in the way they establish the connection? is there any specification on how devices from different vendors should connect to each other? 

    Regards,

    Håkon

Children
  • +1 in reply to hakved_vea

    Hi Håkon,

    hakved_vea said:
    However, neither of the applications, Unicast Audio Server, Unicast Audio Client or the nRF5340_audio was able to stream data to the other LE Audio equipment, or receive from a broadcast stream.

    For the Unicast samples, the cause could be the controller which is on the network core. In my previous answer I forgot to add that Nordic's SoftDevice controller does not support Isochronous channels, so you need to use the precompiled hex found in <ncs-installation>\nrf\applications\nrf5340_audio\bin and flash it to the network core of nRF5340. By default, the Unicast samples will build rpmsg for the network core, and this should be disabled with these lines in prj.conf:

    CONFIG_NCS_INCLUDE_RPMSG_CHILD_IMAGE=n

    CONFIG_BT_HCI_VS_EXT=n

    Another consideration to take is which role each device has in the Bluetooth connection. The headset/client device is the central in both Unicast and nRF5340 Audio. Make sure that the third party device is set up as a peripheral device or change the role of the nRF5340 Audio DK to be peripheral.

    hakved_vea said:
    At this point, are most of the Auracast equipment proprietary in the way they establish the connection? is there any specification on how devices from different vendors should connect to each other? 

    There are some variations on how different vendors want to make connections, so there may be a mismatch here. Are you able to find out how the LE Audio device you want to connect to is set up to make connections? Examples are a filter to match a name or address.

    Regards,
    Maria

  • 0 in reply to Maria Gilje

    Thank for the reply, I thought this got a little off-topic so I started a new ticket:
    Connecting nRF5340 LE Audio to other LE Audio equipment 

    Thank you for the help, I was able to build the LE Audio example and got it to work whit two nRF5340-Audio-DK kits :)

    Håkon

Related