HCI commands/events via UART to/from nRF5340 Audio DK

Is there an HCI API to control the device and configure it to work with LE Audio?
If so, is there an example of minimal configuration that will allow Audio DK to transmit/receive LE Audio from third party device?

What is the link to install Audio DK extension to nRF connect SDK? Link in documentation doesn't work.

Latest SDK doesn't have "applications/nrf5340_audio" path that is specified in documentation

Parents
  • Hello,

    Is there an HCI API to control the device and configure it to work with LE Audio?
    If so, is there an example of minimal configuration that will allow Audio DK to transmit/receive LE Audio from third party device?

    Not innately - you will need to program the board with the nRF5340_audio application and link controller for it to work for LE Audio. The nrf5340_audio application serves as this minimal configuration for you to get started from, which you may then continue to develop on.

    What is the link to install Audio DK extension to nRF connect SDK? Link in documentation doesn't work.

    Latest SDK doesn't have "applications/nrf5340_audio" path that is specified in documentation

    The Audio application is still only available in the NCS SDK v1.9.99-dev1 tag. If you already have v1.9.1 installed through the toolchain manager you will need to follow the steps in the Get the nRF Connect SDK code and substitute the v1.9.99-dev1 tag in place of the v1.9.1 in the example command:

    $west init -m https://github.com/nrfconnect/sdk-nrf --mr v1.9.99-dev1

    Make sure to also perform the west update and west zephyr-export steps before you proceed to the Audio application documentation.
    You will need to perform the two steps in the nRF5340 Audio documentations Configuration section the first time you begin working with the devtag.
    Once you have added the nrf5340_audio application to the west manifest, the following west update command will prompt you for the github login with access to the LC3 repository, in order to retrieve it.
    If you do not have access to the LC3 repository already you will need to contact your Regional Sales Manager to request this access.

    After the west update completes successfully everything is set up and you may begin to develop with the audio application. Here you may proceed directly to use the buildprog tool to build your application for different configurations, and flash those configurations to multiple different boards concurrently.

    Please do not hesitate to let me know in the case that you should encounter any issues or questions!

    Best regards,
    Karl

    • If I want to use HCI access to the controller, I need to do this via "bt_hci_cmd_send_sync" API? 
      If so, what is an initialization sequence that is a must for HCI to work?
    • How do I activate "gateway to headset" mode with "nrf5340_audio" app? - Using 
      CONFIG_AUDIO_DEV compilation flag?
    • SBC software codec is supported? Or just your proprietary LC3?
  • Evgenye said:
    If I want to use HCI access to the controller, I need to do this via "bt_hci_cmd_send_sync" API? 
    If so, what is an initialization sequence that is a must for HCI to work?

    You would have to do this through the bt_hci (the LE Audio controller supports the HCI commands defined in the Bluetooth Core Specification v5.2) and bt_hci_vsc API, yes.
    You will need to have programmed the network core with the LE Audio controller for these to be available to the application.

    Evgenye said:
    How do I activate "gateway to headset" mode with "nrf5340_audio" app? - Using 
    CONFIG_AUDIO_DEV compilation flag?

    If you would only like to build and flash a gateway you can still use the buildprog tool, with the following command:

    $ python .\buildprog.py -c both -b debug -d gateway -p

    You should also add --pristine whenever you have made changes to the prj.conf file.

    Evgenye said:
    SBC software codec is supported? Or just your proprietary LC3?

    SBC is also supported, please see nRF5340_audio documentation about this.
    In addition to the SBC prj.conf you would also need to remove CONFIG_LC3_ENC_CHAN_MAX=2 and CONFIG_LC3_DEC_CHAN_MAX=1 from your overlay-headset.conf and overlay-gateway.conf.

    Best regards,
    Karl

Reply
  • Evgenye said:
    If I want to use HCI access to the controller, I need to do this via "bt_hci_cmd_send_sync" API? 
    If so, what is an initialization sequence that is a must for HCI to work?

    You would have to do this through the bt_hci (the LE Audio controller supports the HCI commands defined in the Bluetooth Core Specification v5.2) and bt_hci_vsc API, yes.
    You will need to have programmed the network core with the LE Audio controller for these to be available to the application.

    Evgenye said:
    How do I activate "gateway to headset" mode with "nrf5340_audio" app? - Using 
    CONFIG_AUDIO_DEV compilation flag?

    If you would only like to build and flash a gateway you can still use the buildprog tool, with the following command:

    $ python .\buildprog.py -c both -b debug -d gateway -p

    You should also add --pristine whenever you have made changes to the prj.conf file.

    Evgenye said:
    SBC software codec is supported? Or just your proprietary LC3?

    SBC is also supported, please see nRF5340_audio documentation about this.
    In addition to the SBC prj.conf you would also need to remove CONFIG_LC3_ENC_CHAN_MAX=2 and CONFIG_LC3_DEC_CHAN_MAX=1 from your overlay-headset.conf and overlay-gateway.conf.

    Best regards,
    Karl

Children
No Data
Related